From: Nuno Silva <nunojsilva@ist.utl.pt>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Books about making shell scripts and other nifty commands.
Date: Sun, 08 Jun 2025 01:09:29 +0100 [thread overview]
Message-ID: <1022kbq$mh5$1@ciao.gmane.io> (raw)
In-Reply-To: 207c5259-a7e8-4eca-9fc9-0318d78dba7d@gentoo.org
On 2025-06-05, Eli Schwartz wrote:
> On 6/5/25 2:48 PM, Arve Barsnes wrote:
>> On Thu, 5 Jun 2025 at 19:56, yahoo <mentadent47@yahoo.com> wrote:
>>> Advanced Bash-Scripting Guide (https://tldp.org/LDP/abs/html/)
>>>
>>> Available for free online so you can see if all you need is in, or in
>>> printed version from various resources. Full of code snippets to get you
>>> started.
>>
>> Also the bash book from the bunch of programming books created by the
>> StackOverflow bunch a few years ago. I remember those got good
>> feedback.
>>
>> https://goalkicker.com/BashBook/
>>
>> Regards,
>> Arve
>
>
> https://mywiki.wooledge.org/BashGuide is a must-read, I would say. In
> fact, the entire wiki is an excellent reference manual for both
> beginners and knowledgeable developers.
Seconded, it's the reference I was going to suggest in this thread. It
has not only documentation on at least some Bash features, but also
content about the details one might have to worry about (such as looping
over file names). Random examples:
https://mywiki.wooledge.org/BashPitfalls
https://mywiki.wooledge.org/BashFAQ
https://mywiki.wooledge.org/ParsingLs
https://mywiki.wooledge.org/DontReadLinesWithFor
https://mywiki.wooledge.org/BashGuide/Arrays
The person who asked for suggestions is focused on GNU bash, but this
wiki also has content on portability
https://mywiki.wooledge.org/Bashism
--
Nuno Silva
next prev parent reply other threads:[~2025-06-08 0:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 3:49 [gentoo-user] Books about making shell scripts and other nifty commands Dale
2025-06-05 15:32 ` Mark Knecht
2025-06-05 16:02 ` Eli Schwartz
2025-06-05 16:16 ` Mark Knecht
2025-06-05 17:19 ` Eli Schwartz
2025-06-06 14:14 ` [gentoo-user] " Nuno Silva
2025-06-05 16:59 ` [gentoo-user] " Dale
2025-06-05 17:44 ` eric
2025-06-05 19:50 ` Re[2]: " Stefan Schmiedl
2025-06-06 2:58 ` Dale
2025-06-05 17:03 ` Jay Faulkner
2025-06-05 17:56 ` yahoo
2025-06-05 18:48 ` Arve Barsnes
2025-06-05 19:05 ` Eli Schwartz
2025-06-08 0:09 ` Nuno Silva [this message]
2025-06-05 18:33 ` yahoo
2025-06-10 9:39 ` Dale
2025-06-10 10:33 ` Quico Jurado
2025-06-10 14:33 ` Mark Knecht
2025-06-10 15:01 ` Eli Schwartz
2025-06-10 16:24 ` yahoo
2025-06-10 18:12 ` Dale
2025-06-10 18:07 ` Dale
2025-06-10 18:18 ` Quico Jurado
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='1022kbq$mh5$1@ciao.gmane.io' \
--to=nunojsilva@ist.utl.pt \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox