News for hackers. Stuff that matters.

A comment on Bash Pitfalls. Parent comment

Re:Bash Pitfalls by pen2l on Sunday August 16, 2015 @02:19PM (#10069742)
The funny thing is, I don't consider myself a very smart person or a programmer, but I've gotten bash down pretty well at this point. And I'm a person who has a looooot of trouble with C++ etc., most of my code is shit, if not just unusable.

Though, I have been using linux command-line daily for 12 years now for sysadmining tasks and such. I know there's a lot of weird stuff to worry about, (especially as is noted in the 'bash pitfalls' guide), but I think with a little bit of practice (about 6 months' worth) and good instruction (I love greycat's guides), anyone can get a reasonable good handle of bash.

[ Parent | on HN ]
Re:Bash Pitfalls by seanp2k2 on Sunday August 16, 2015 @03:00PM (#10069869)
Agree. Also, http://wiki.bash-hackers.org/doku.php has tons of great info. Sad that TLDP gets all the Google ranking for most bash searches when wooledge and BHW typically have much more detailed and modern (e.g. using "${var}" and [[ instead of [ ) explanations.

Lastly, if you're really stuck on a bash problem, head on over to #bash in Freenode and the awesome people there will very likely help! Greycat hangs out there.

[ Parent | on HN ]
Re:Bash Pitfalls by JoshTriplett on Sunday August 16, 2015 @03:51PM (#10070044)
> [[ instead of [

I have yet to see a good rationale for this. If you need the additional operators [[ provides, such as regular expression matching, great. Otherwise, why not just use [ and remain portable?

[ Parent | on HN ]
Re:Bash Pitfalls by a3n on Sunday August 16, 2015 @04:19PM (#10070126)
If you're worried about portability in shell scripts, you should probably be using sh anyway.
[ Parent | on HN ]