Comments on: Use BASH nullglob To Verify *.c Files Exists or Not In a Directory

By: Chelsia

Chelsia — Sat, 23 Jul 2011 11:19:57 +0000

Mighty useful. Make no mistake, I aprpceiate it.

By: flabdablet

flabdablet — Wed, 24 Nov 2010 08:51:46 +0000

The for name in pattern construction is good for doing stuff to all matching files, but sometimes all that’s needed is a quick test for whether at least one matching file exists. The stat command can help with that:
if stat -t *.mp3 >/dev/null 2>&1 then echo At least one file matching *.mp3 exists else echo No files match *.mp3 fi
This is portable to shells other than bash, many of which don’t support nullglob.

By: waltz

waltz — Mon, 15 Nov 2010 06:32:10 +0000

great explanation to make complicated things simple!
Nice example too.
Thank you very much

By: jaysunn

jaysunn — Sun, 10 Jan 2010 16:37:08 +0000

Great Lesson,
I was just introduced to this via Vivek. I am planning to use this feature in many ways.

Thanks,

Jaysunn

By: Vivek Gite

Vivek Gite — Sat, 07 Mar 2009 11:43:00 +0000

How do you know these things? Either you must have the memory of an elephant, or know how to use google in some magic way :)

I’ve been using UNIX and Linux for over decade so I know lots of things. bash man page has all the info.

One thing I don’t understand is why certain bash variables are stored with shopt and others with environment variables (like IFS). Historic reasons?

shopt use to toggle the values of variables controlling optional behavior. Usually it can be on or off only. On other hand, IFS value can be anything as per users requirements.

By: bratwurst

bratwurst — Sat, 07 Mar 2009 11:33:49 +0000

How do you know these things? Either you must have the memory of an elephant, or know how to use google in some magic way :)

One thing I don’t understand is why certain bash variables are stored with shopt and others with environment variables (like IFS). Historic reasons?