Plenty of new features and fixes in the last few KillEmAll releases since v21.11.26 released and posted about on the 26th, see below.
- v21.11.29 (released today, November 29th, 2021)
- Added the option to Press ‘R‘ to Run KillEmAll again after any KillEmAll process termination run, in addition to ‘D‘ for Debug mode, ‘C‘ for Config, and ‘U‘ to check for updates.
- Pressing ‘L‘ to save the log file when prompted will automatically save the entire session (both past and future results) recorded within the same KillEmAll process.
- Fixed process termination result not appearing directly under the process to terminate when selected in Debug mode (a recent problem that only occurred with the previous update.)
- Fixed an annoying issue with occasional new line characters (CRLF) appearing as a character on screen rather than moving the cursor to a new line position, causing confusing/jumbled text on the screen.
- v21.11.27.x (released November 27th, 2021)
- Added config option to automatically terminate processes on startup.
- Added ability to Press ‘C’ for KillEmAll Configuration at any prompt, even during Debug mode.
- Process termination speed increased quite a bit (previously, for each process the text output was written to the console window before moving on to the next process, but writing to the console window each time was proving to be a slow task; with this version all processes are terminated before any output is written to the console window.)
- Added wrapping quotes around search strings when using the WebSearch option in Debug mode.
* Windows XP compatibility has been officially abandoned in these releases, and no future support will be provided. KillEmAll does terminate processes on Windows XP, but whether or not all of the menu prompts work as expected is not guaranteed. The automation-based command line arguments /auto and /log should function as expected.
* Windows Terminal Note: KillEmAll may not function as expected when run from inside Windows Terminal; current versions will terminate the Windows Terminal process altogether and this terminates KillEmAll. Initial attempts at fixing that behavior didn’t go well, and while it’s being worked on for a future release, no guarantees will be made that it will ever be compatible. Note in Windows 11 that even when Windows Terminal is configured as the default Windows terminal application, when double-clicked on from Windows Explorer, KillEmAll will runs under the traditional console in its own window. Since KillEmAll does not start in Windows Terminal like other apps or batch files will, KillEmAll functions completely as expected.
Leave a Reply