> 1) use shellcheck. Check out shellcheck.net or install locally. It
catches the most common shell scripting problems.
I already do. Thanks for the other recommendations.
On Sat, Jun 9, 2018 at 6:32 PM Evan Gates <evan.gates_AT_gmail.com> wrote:
>
> On Sat, Jun 9, 2018, 08:20 Adrian Grigore <adrian.emil.grigore_AT_gmail.com>
> wrote:
>
> > I sometimes enjoy testing my shell scripts. Opinions?
>
> I'm away from my computer so I can't give full feedback but for now
> I'd recommend
>
> 1) use shellcheck. Check out shellcheck.net or install locally. It
> catches the most common shell scripting problems.
>
> 2) mywiki.wooledge.org has a great guide, faq, and list of pitfalls.
> The pitfalls is a great place to start. It's a list of very common
> problems with explanations of why they are wrong and how to fix them.
>
> 3) #bash on freenode. Helpful if occasionally snarky community. If you
> ask them for feedback and avoid the xy problem you can learn a lot.
>
> emg
>
--
Thanks,
Adi
Received on Sat Jun 09 2018 - 17:34:34 CEST