Changelog of BashSupport Pro 4.3.0

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

Fixed Minor improvement to memory usage and performance to detect shell script file types while JetBrains Shell is installed.
Fixed Hide message “Code style settings may be modified by BashSupport Pro” to avoid confusion. Only the line feed setting for shell script files are adjusted to match \n.
Updated The build for 2024.2 now requires 2024.2.1 or later because of changes of the available API.
Updated The selected region of the IDE is send as property “ide.region” with the optional telemetry. As before, the telemetry is optional and turned off by default.
Updated Update version of OpenTelemetry library.

Added Setting for inspection “Unused global variable” to use a lighter analysis and not the global reference graph in batch mode. The inspection used for editor highlighting remains unchanged. Building a global reference graph is time consuming and turns the analysis’s background progress into a modal progress. This option is turned off in 2024.2 because the IDE builds the global reference graph if at least one inspection needs it. IDEs like CLion don’t have other inspections which use, which means that the presence of “Unused global variable” made things very slow in such IDEs because the graph was built for every file in the project. If you want the extended analysis for unused global shell script variables, then enable this setting in your inspection profile. IntelliJ IDEA has several other inspection using the reference graph, so it’s built anyway for Java projects with the default settings.
Fixed The name of the inspection instead of “BashSupport Pro” is displayed now for groups of fixes of batch analysis results.

Fixed [#170](https://github.com/BashSupport-Pro/bashsupport-pro/issues/170: Show run configurations compatible with JetBrains Shell as “Shell Script” instead of “Shell Script (by BashSupport Pro)” if JetBrains Shell is not enabled. This improves compatibility with other plugins, which incorrectly use the display name to identify run configurations.

Fixed Hopefully fixed exceptions “shell debugger already terminated” and “disposed in debugger context”.
Fixed Some breakpoints could sometimes not be registered with the debugger with 2024.3 and possibly earlier versions.
Added Basic support to execute run configurations with a script snippet in debug mode. This fixes #179 and prevents that the debug button is disabled for compound run configurations, which reference at least one script snippet run configuration. Setting breakpoints inside the snippet is not yet possible. This is supported for local and remote run target configurations.