Changelog of BashSupport Pro 4.2.1

An annotated list of all changes of the 4.x major version is available in the release announcement.

These are all changes since 4.1.5, the intermediary releases were for only for testing.

General

• Fixed Error reports were not sent if the optional telemetry was turned off.
• Fixed “Go to symbol” for variables, functions and Zsh aliases was unavailable in the telemetry. As always, all telemetry is optional, turned off by default and not identifying users.
• Fixed Windows path mapping was unavailable for BashSupport Pro shell run configurations.

Editor

• Fixed On Windows, enforce UNIX-style line separator \n for shell script files in projects with setting “system dependent line separator”.

Run Configurations

• Added In the shell interpreter settings, the detection of Zsh interpreters is now supported on Windows. This includes Zsh installed in the default WSL distribution.
• Updated Sync bashdb updates for Bash 5.2.
• Fixed #167: properly escape quotes and other special characters in run config snippets.
• Fixed Show an error notification for run configurations of type “shell script snippet” with interpreter type “OS”. “OS” is used for files with a shebang line and is unsupported for snippets.
• Fixed Pass -l -c 'snippet text' to Bash to execute shell script snippets. Previously, only -c 'snippet text' was passed, but Cygwin and possibly others do not use the passed environment variables unless -l is used.
• Fixed “Run in terminal” caused exception Thread context was already set: ... on 2024.1.
• Fixed There was no debug menu item shown in the run line markers popup of a file for Zsh shell interpreters with setting “show in menu” enabled.
• Fixed Paths to script file and working directory were not updated if a parent directory was renamed.

Debugger

• Fixed On Linux, it sometimes happened that the IDE terminated unexpectedly after debugging a shell script.
• Fixed Shell script variable values with line separator and other special characters were displayed truncated.
• Fixed String variable values with spaces were shown truncated in the debugger user interface.
• Fixed String variable values with escaped double quotes were shown truncated in the debugger user interface.
• Fixed Variables used internally by bashdb were shown in the list of variables, e.g. filename. This has been fixed in bashdb.
• Fixed Show a notification when debugging of a run configuration with an input file is attempted. The debugger doesn’t work with STDIN redirection.
• Fixed The position was not updated in the UI if the debugger stopped after “Resume” at a position not covered by a breakpoint.
• Fixed Exception about too many created threads when stepping in large shell scripts.
• Fixed “Copy value” for variables in the debugger UI did not copy the actual value for arrays. “View” is now also shown for truncated strings and array variables to view the complete value.
• Fixed Exception “Source position is unavailable for command …”.
• Fixed User interaction with the debugger console broke the debugger integration.
• Fixed Exception when modifying the value of variable of a Zsh script variable.
• Fixed When modifying a variable value, string values were displayed unquoted.
• Fixed When modifying an array value, the current value wasn’t displayed properly.
• Fixed #166: Exception This method is forbidden on EDT because ... after launching a WSL remote run configuration on Windows.
• Fixed Script debugging was always terminated with signal 137 (i.e. SIGKILL) even when the script completed normally.
• Fixed Terminating the debugger process of a WSL remote run configuration failed with “Waiting for process to detach…”, similar to IDEA-351735.

Zsh

• Fixed Arrays were rendered differently compared to bashdb’s rendering.
• Fixed Variable values with escaped characters were not rendered correctly for strings and arrays.
• Fixed On some Windows setups, debugging with WSL Zsh failed with exception “Unable to connect to the debugger”.

Markdown

• Fixed A shell script code block had two run line markers shown, one by the integration with the Markdown plugin and one by BashSupport Pro itself.