Michał

I made changes according to your proposal. You should probably look how to deploy this language server nuget referenced in the bogus csproj: ```xml ``` I cannot help with the...

About the `--debugger` option - this is something for next release. Currently we run bashdb with: `bashdb --quiet --tty ./fifo_file_path -- script.sh arg1 arg2` just wondering how to pass those...

@kooshball - please provide more details, since i cannot reproduce that: - operating system info + vscode bitness if needed - simplest bash script source to reproduce the problem

After investigation it turned out that "bash - - debugger" cannot be used. Hovever, bash 5.0 was supposed to allow setting $0 and this was done as far as I...

Please try following: - use newly released extension from marketplace (v. 3.1) - wont fix your problem but still.. - add/modify "pathBash" in launch config to point to bash version...

@macosbasher : Could you paste here contents of "/usr/local/Cellar/bashdb/4.4-0.94/bin/bashdb" script? I am interested in shebang value (first line)... The newest extension uses internal bashdb with "#!/bin/bash" (if it was not...

Small fix to test under macOS: [bash-debug-0.3.1.vsix.zip](https://github.com/rogalmic/vscode-bash-debug/files/2414693/bash-debug-0.3.1.vsix.zip) - requires proper `pathBash` in `launch.json`, pointing to bash 4.*

I just released version 0.3.2 of extension with fix for launching from terminal (basically using defined bash rather than relying on [shebang](https://en.wikipedia.org/wiki/Shebang_(Unix))). In launch.json, please remove the "pathBashDb", then set...

Please add : `"showDebugOutput": true ` to launch json add paste the full log from debug console here. Step out is not supported yet, while step in should work fine....

Seems that the log does not contain the actual step in/out call. According to this output, the VS Code should show following file/line: ``` (/Users/svenvogel/Sync/VSCode/bash/test.sh:3): ``` Did you press the...