vscode-bash-debug
Bash shell debugger extension for VSCode (based on bashdb) (by rogalmic)
sub
a delicious way to organize programs (by qrush)
vscode-bash-debug | sub | |
---|---|---|
2 | 4 | |
210 | 1,733 | |
- | 0.0% | |
0.0 | 0.0 | |
9 months ago | over 2 years ago | |
Shell | Shell | |
MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
vscode-bash-debug
Posts with mentions or reviews of vscode-bash-debug.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-05-03.
-
nvim-dap: Bash debugging.
I installed bash-debug-adapter (which installs vscode-bash-debug ) but I don't know how to configure nvim-dap to use it. Has anyone done this before? Any help is much appreciated.
- Bash-Oneliner: A collection of handy Bash One-Liners and terminal tricks
sub
Posts with mentions or reviews of sub.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-08-12.
-
The Unreasonable Effectiveness of Makefiles
Scripts in bin have no documentation, no easy way to enumerate them, etc. There is definitely a time and a place for bin scripts, especially as things grow in complexity. However the beauty of just is that there's one file (the justfile) that defines all of your project's actions. You don't have to go spelunking into bin to figure out how to tweak a compiler flag, etc. And since just will run anything there's no reason why your complex bin scripts can't just be called from a simple one liner task in a justfile.
Could your write a bash script that does stuff like enumerate all the bin scripts, pull out documentation comments, etc.? Absolutely, and people have followed that pattern for a while (see https://github.com/qrush/sub) but it's a bunch of boilerplate to copy between projects. Just pulls out that logic into a simpler config file.
- Bash-Oneliner: A collection of handy Bash One-Liners and terminal tricks
- Bashly – Create beautiful bash scripts from simple YAML configuration
-
sd: my script directory
Many moons ago Basecamp published sub (github) which runs on a similar idea with different tradeoffs being chosen.
What are some alternatives?
When comparing vscode-bash-debug and sub you can also consider the following projects:
ShellCheck - ShellCheck, a static analysis tool for shell scripts
bashly - Bash command line framework and CLI generator