Changelog of BashSupport Pro 5.0.3

An annotated list of all changes is available in the release announcement.

Fixed Parsing of function x(echo) and function x()(echo) which are valid function definitions with Bash 5.
Fixed Parsing of weird commands $((2)) a b c or $(echo echo) a b c.

Fixed #207: The setting to configure the Google Shell Code Style wasn’t working properly.

Fixed #205: Environment variables do not exist in remote debugging. This was a regression of 5.0.1.

Changed Revert that no indentation is enforced after pressing Enter inside a string. BashSupport Pro 4.x indented with the current indentation level, but version 5.0.1 changed this to no indentation at all to avoid inserting unwanted whitespace. Because this change may be confusing to users, the default behavior was restored. A new setting is now available at Code Style > BashSupport Pro > Tabs and Indents to allow enforcing no indentation in a multiline string. For now, this setting is only used for Enter handling, not for for reformatting.
Fixed A line continuation was not inserted if Enter was pressed right before a quoted string, subshell and similar substituted elements.
Fixed A line continuation was not inserted if Enter was pressed before a redirection.

Added New setting to control wrapping before do of a do ... done command.
Fixed #204: Support to remove trailing semicolon after condition of the if command.
Fixed PsiInvalidElementAccessException when formatting a file.
Fixed Formatting of arithmetic expansions at the level of a command.

Fixed Work around exception Read access is allowed from inside read-action of GitHub Copilot attempting to access bats-core test result without read access.