Re: local failure

From	Greg Wooledge <wooledg@eeg.ccf.org>
Newsgroups	gnu.bash.bug
Subject	Re: local failure
Date	2020-06-01 07:40 -0400
Message-ID	<mailman.892.1591011671.2541.bug-bash@gnu.org> (permalink)
References	(3 earlier) <CAH7i3LoKQ_-QMMeMU-=5hcbqZPLfyu0i63f+KcMot+pQ6ruEtw@mail.gmail.com> <CAH+roKX-H_PjDu+UBPDiVUQjnd2eKK0E=L1r=0wg33X5paJpEg@mail.gmail.com> <11340.1590942081@jinx.noi.kre.to> <CAJdN7KgE2xrEDj3bOzVzuEXS0nN+MKXrVm1ksPKa3GNX3TxL-Q@mail.gmail.com> <20200601114040.GL4133@eeg.ccf.org>

Show all headers | View raw

On Sun, May 31, 2020 at 11:57:03PM -0400, John Passaro wrote:
> I think the underlying question here is not exactly "how do I gather this
> from the docs" as much as it is "how was I supposed to know about this and
> act on it before I had to debug it?"

I don't believe the bash documentation is the appropriate place to put
tutorials on how (not) to write bash scripts.

For that, I would consult other sources, such as:

https://shellcheck.net/
https://mywiki.wooledge.org/BashPitfalls

I'm sure there are other excellent places to find instructions, but these
are the two that immediately come to mind.

Back to gnu.bash.bug | Previous | Next | Find similar

Thread

Re: local failure Greg Wooledge <wooledg@eeg.ccf.org> - 2020-06-01 07:40 -0400

csiph-web