pure-sh-bible VS bible_api

The guy who wrote it, also wrote a POSIX Shell bible: https://github.com/dylanaraps/pure-sh-bible

Do you have any specific examples to cite? The snippets are meant to be run in POSIX-compliant shells like dash/yash/ash/etc, not just Bash in compatibility mode.

In fact, there used to be a section which listed workarounds[1] for bugs in dash, but they have since been fixed[2]. If you are still using an old version of dash, you may need to use them.

[1] https://github.com/dylanaraps/pure-sh-bible/commit/70f410ebb...

[2] https://github.com/dylanaraps/pure-sh-bible/issues/13

Personally, I would steer clear of a script that installs dependencies on it's own. Us sysadmins prefer to manage our own dependencies, generally speaking. Instead consider a README that outlines how to meet/install dependencies for the script, or try to find ways to write your script in pure Shell or Bash without using tools like awk, jq, etc. Consider having a look at the Pure Sh Bible for examples of how to do many useful things in pure Sh.

POSIX Shell Tutorial POSIX shell cheat sheet GitHub - dylanaraps/pure-sh-bible: 📖 A collection of pure POSIX sh alternatives to external… Shell Scripting Tutorial

There is the "pure bash bible" but it seems less than maintained these days: https://github.com/dylanaraps/pure-sh-bible

Otherwise you're stuck reading the POSIX standard: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V...

Look at this: https://github.com/dylanaraps/pure-sh-bible

pray-pi() { local cmd failed_cmds book chapter verse fetch_url for cmd in curl jq; do if ! command -v "${cmd}" >/dev/null 2>&1; then failed_cmds+=",${cmd}" fi done if (( "${#failed_cmds}" > 0 )); then printf -- '%s\n' "The following requirements were not found in PATH: ${failed_cmds/,}" >&2 exit 1 fi book="${1:?No book provided}" chapter="${2:?No chapter provided}" verse="${3:?No verse provided}" fetch_url="https://bible-api.com/${book}%20${chapter}:${verse}" curl -s "${fetch_url}" | jq -r '.text' }