mg.sh
shellcheck-repl
mg.sh | shellcheck-repl | |
---|---|---|
1 | 4 | |
0 | 15 | |
- | - | |
0.0 | 3.5 | |
about 1 month ago | 22 days ago | |
Shell | Shell | |
MIT License | ISC 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.
mg.sh
-
Shell Script Best Practices, from a decade of scripting things
I agree, getting to know where a script "comes from" can be complex though. You can `readlink -f` (or equivalent) in many cases, but when implementing a library this might not be entirely practical. I have had to rely on this ugly if-statement [1] for that purpose.
[1]: https://github.com/Mitigram/mg.sh/blob/cbeb206d67fe08be2107deee50acf877f990dbdf/bootstrap.sh#L6
shellcheck-repl
-
Shell Script Best Practices, from a decade of scripting things
> "Use shellcheck."
(Disclaimer: I'm one of the authors)
After falling in love with ShellCheck several years ago, with the help of another person, I made the ShellCheck REPL tool for Bash:
https://github.com/HenrikBengtsson/shellcheck-repl>
-
Bash Pitfalls
Thank you, and thanks for the suggestion. Yes, it should be possible to keep the SC2154 check. I probably just disabled it as a quick fix when first started out. I'm tracking this in https://github.com/HenrikBengtsson/shellcheck-repl/issues/15.
> You'd also want to take into account special variables like $RANDOM and $HOSTNAME, but that's pretty trivial.
It seems like ShellCheck is already aware of these special Bash variable, e.g. 'echo $RANDOM' will not trigger SC2154 (or even SC2086 that otherwise asks you to quote variables).
-
ShellCheck: A static analysis tool for shell scripts
shellcheck-repl: Validation of Shell Commands Before Evaluation
https://github.com/HenrikBengtsson/shellcheck-repl
This tool validates your commands at the Bash prompt using ShellCheck and refuses to evaluate them if there's a mistake. It ignores a set of rules that doesn't play well with oneliners.
(Disclaimer: I'm one of the authors)
What are some alternatives?
bash-modules - Useful modules for bash
shellharden - The corrective bash syntax highlighter
zx - A tool for writing better scripts
bats-core - Bash Automated Testing System
pip - The Python package installer
pure-bash-bible - 📖 A collection of pure bash alternatives to external processes.
isort - A Python utility / library to sort imports.
ShellCheck - ShellCheck, a static analysis tool for shell scripts
jc - CLI tool and python library that converts the output of popular command-line tools, file-types, and common strings to JSON, YAML, or Dictionaries. This allows piping of output to tools like jq and simplifying automation scripts.
nushell - A new type of shell
dmenu-scripts - Serious fun with dmenu