bash-modules

You may like bash-modules then: https://github.com/vlisivka/bash-modules/tree/master/bash-mo...

Bash is turing-complete, so it's possible to write automated test cases in bash. Example: https://github.com/vlisivka/bash-modules/blob/master/bash-mo...

Template in article is awful. It's better to use this one, which is a real CLI tool: https://github.com/vlisivka/bash-modules/blob/master/bash-mo...

IMHO, you are mixing TODO lists and task management/planning software. No, I don't know a good task manager or business process manager for command line. Instead, I created a simpler TODO list manager, called `td`[0], which supports flat TODO lists only, and use directories and command-line generators to manage todo's. `td` prints top item only, by default, leaving little room for procrastination. I'm keeping one `TODO.md` file per project instead of one large TODO file for all todo's. [0]: https://github.com/vlisivka/bash-modules/blob/master/bash-mo...

Refactor your terrible and hard to maintain script into a well looking and maintainable script. It's not a bash fault. My bash-modules[0] project[1] may help you with that. Typically, I perform script refactoring in these steps: 1. Split code into few subroutines with clear boundaries between them, or split a large script into multiple simpler scripts. 2. Add an error handler with transparent message to every line of code. 3. Add command line options to override hard-coded things, to be able to test things in isolation. 4. Write documentation (man-page) for script, for future self. 5. Write test cases. 6. Refactor code, following best practices. [0]: http://vlisivka.github.io/bash-modules/ [1]: https://github.com/vlisivka/bash-modules

See my `td` variant for console here: https://github.com/vlisivka/bash-modules/blob/master/bash-mo... They are easy to make.

I'm preparing to release bash-modules 4.0 [0]. Can you give me feedback, please? I'm a non-native English speaker, so I need someone to help fix spelling mistakes, at least. [0]: https://github.com/vlisivka/bash-modules

> (set -e; echo hi); echo $? It works in my shell. :-/ It looks like you forgot to insert `false` command. You are pointing to the problem with -e not working in subshell/deep functions, because of POSIX. Right? It's described in bash documentation: http://www.gnu.org/software/bash/manual/html_node/The-Set-Bu... > I think just defining a die() function and using it after any command that must succeed is more verbose, but less error prone: Yep. It's the style I developed 12 years ago, when working at Bazaarvoice, when I was lead of devops team. I created the whole library for bash, to use this pattern consistently. See https://github.com/vlisivka/bash-modules#error-handling

Bash strict mode forces to write clean scripts, with each potential error handled. I use it for more than decade. I wrote lot of bash scripts at Bazaarvoice. BTW. I developed small set of common functions for strict mode, called bash-modules. Can you look at it and provide some feedback? See https://github.com/vlisivka/bash-modules .

I'm author of bash-modules project. It's my attempt to create set of libraries for easier scripting on bash in strict mode. Most bash libraries are not designed for strict mode, so I created my own. If you prefer sh over bash so much, you can help me to make it compatible with sh, or just fork it. See https://github.com/vlisivka/bash-modules

I wrote library for shell scripts with design goal to work properly in strict mode: https://github.com/vlisivka/bash-modules

Why BATS? Why not something *unit-like? Example: https://github.com/vlisivka/bash-modules/blob/master/main/ba... .

Globing works fine with spaces, but you need to quote variables, e.g. $file -> "$file", to avoid parsing of their content by bash. See Bash-FAQ for details. Problem with shell is that you need to solve same problems again and again. This is why I wrote "bash-modules" script (https://github.com/vlisivka/bash-modules), which allows to write module with common code and then just do ". import.sh module" from script or command line.