ShellCheck
maam
| ShellCheck | maam | |
|---|---|---|
| 500 | - | |
| 37,699 | 18 | |
| 0.6% | - | |
| 8.0 | 0.0 | |
| 2 months ago | over 9 years ago | |
| Haskell | Haskell | |
| GNU General Public License v3.0 only | BSD 3-clause "New" or "Revised" License |
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.
ShellCheck
-
Debugging Bash Like a Sire
I never thought of the idea of printing out a stack trace and a logging function is an example of such a good idea that is so obvious that I didn't think of it :-)
I use -e sometimes but I really dislike scripts that rely on it for all error handling instead of handling errors and logging them.
https://www.shellcheck.net/
^^ this tool has proven very useful for avoiding some of the most silly mistakes and making my scripts better. If you're maintaining scripts with other people then it is a great way of getting people to fix things without directly criticising them.
- Shellcheck
-
Matanuska ADR 017 - Vitest, Vite, Grabthar, Oh My!
Unfortunately, this did mean that configuration began to sprawl. At this point, I had configurations not just for Vite (shared with Vitest) and tsc, but also for Prettier, ESLint and even ShellCheck. Many of these files had shared settings that needed to match each other. This was somewhat manageable, until Vite was also in the mix.
-
Haskell: A Great Procedural Language
Shellcheck is another useful one (linter for shell scripts)
https://www.shellcheck.net/
-
TIL: Some surprising code execution sources in bash
There's now an issue for it https://github.com/koalaman/shellcheck/issues/3088
-
Top FP technologies
ShellCheck
-
Techniques I Use to Create a Great User Experience for Shell Scripts
It's been so long since I used it seriously I couldn't tell you.
There's over 1000 open issues on the GitHub repo, and over 100 contain "false positive". I recognize several of these at first glance.
https://github.com/koalaman/shellcheck/issues?q=is%3Aissue+i...
-
Advanced Shell Scripting Techniques: Automating Complex Tasks with Bash
Reminder of the handy ShellCheck:
* https://www.shellcheck.net
Even if you don't follow or agree with its advice, it can be a handy and quick second opinion / sanity check.
-
New shell scripting language, a new tablet, and in-product messaging
If you're only occasionally writing shell scripts, Amber may not be a priority for you. In such cases, linting tools like ShellCheck could be more beneficial. However, if you find yourself frequently writing shell scripts, to the point where you're considering Python or Ruby for better re-usability, then Amber is definitely worth your attention.
-
Amber – the programming language compiled to Bash
As carlinigraphy points out, shellcheck [0] exists, and can easily be put into pre-commits, a CI pipeline, etc. This would have almost certainly flagged your problem immediately.
> I would be willing to learn a sane language, but bash isn't one.
It's a general language that has to be both an interactive interpreter and script executor, and it needs to support a huge variety of architectures and kernel versions, as well as historical decisions. It's going to have some cruft.
[0]: https://www.shellcheck.net/
maam
We haven't tracked posts mentioning maam yet.
Tracking mentions began in Dec 2020.
What are some alternatives?
bash-language-server - A language server for Bash
stan - 🕵️ Haskell STatic ANalyser
shellharden - The corrective bash syntax highlighter
camfort - Light-weight verification and transformation tools for Fortran
hdocs - Haskell docs tool
fortran-src - Fortran parsing and static analysis infrastructure