Changelog of BashSupport Pro 4.3.2

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

Fixed #182: Shell script files without an extension and with Unicode content were sometimes not detected as shell scripts. It happened that the editor closed unexpectedly when this bug manifested.
Fixed Avoid unnecessary CPU and memory usage if the (optional) telemetry is turned off.
Updated Minor performance improvement for file type detection of files without extension.

Fixed Exception Slow operations are prohibited on EDT for incorrect usage of the SDK by 3rd-party plugins, e.g. when opening a bundled shell script stub library file.

Fixed Debugging with 2024.3 was broken in EAP5. This is fixed now.
Fixed #180: Debugging a file on the WSL filesystem, e.g. \\wsl.localhost\Ubuntu\opt, was broken. In this case, the working directory was set to a WSL path.
Fixed #181: For the top-level frame (i.e. the most recent frame) group “Input arguments” now displays the current values of $@, $1, etc. Previously, for functions only the initial values passed with the function call were shown. Changes to $@ were not displayed. For the entry-point frame of the debugged script the path to the file was displayed. Due to limitations of Bash and bashdb, the values of $@ can only be displayed for the top-level frame.
Fixed -- is not passed as first argument to bash anymore. Even though Bash is dropping such argument, it was confusing in the debugger UI.
Fixed Sync with latest bashdb, which includes more of our patches. Less pollution of global variables by bashdb.
Fixed Exception com.intellij.openapi.project.IndexNotReadyException thrown when stepping through a shell script while the IDE is indexing.
Fixed The UI offered to modify the value of positional parameters like $1, but that’s currently unsupported.