bashsupport-pro

bashsupport-pro copied to clipboard

Can't edit default shebang

1

Hello, in my bash scripts I have an error: `Executables must start with #!/bin/bash` but I use environment compatible shebang: `#!/usr/bin/env bash` and I don't want to change it to...

anton-dubrovin

Autoformatting long lines

7

Hi, Not sure if this is a 2025.3 issue, or Bash Support Pro, or a new config setting somewhere, but I've noticed that long lines are now autoformatted to have...

josh-tlw

How to indicate bash style syntax checking in sourced files

5

When sourcing a library from an explicitly written bash script, I'd like to hint/indicate inside Intellij to BashSupport Pro that my library file is actually written in bash style and...

moreaki

Possibly wrong syntax error hinting

3

I think it's self-explanatory: I would not expect a warning here in this case ;).

moreaki

When a shell file contains a variable with the `h` modifier, bashsupport-pro has a few issues matching the usage described in the `ZSHEXPN` man page under the `HISTORY EXPANSION` section,...

emilywilder

Exported variable "could be local"

1

``` #!/bin/bash main() { ROOT="$(dirname -- "$(readlink -f -- "${BASH_SOURCE[0]}")")/.." export ROOT } ``` while you can technically do that, I don't think it's useful to declare exported variables as...

jakub-bochenski

feature: Run validation on shell snippets in MD etc

1

Idea has some validation for snippets found in Markdown documents. E.g. it will flag wrongly formatted YAML or JSON. It would be cool if shellcheck would be run on `shell`...

jakub-bochenski

Running "All tests" does not correctly handle nested test folders

2

Given a structure like this: If you choose to run "All tests" on `test` the setup_suite files will not be called. Running "All tests" on `e2e` gives the expected result....

jakub-bochenski

Variable used in trap "could be local"

2

``` foo() { results=$(mktemp) trap 'rm -f "$results"' EXIT } ```

jakub-bochenski

shellcheck source= directive is processed differently than shellcheck

2

Shellcheck resolves `source` directive relative to the working directory that it was executed, no relative to the file, e.g. ``` src/ - sourcing.sh - source.sh ``` If you run shellcheck...

jakub-bochenski