Hi,
I have a question about nullglob bash's shell option. I want to hear
opinions.
The behavior is nicely described in bash reference manual [1]
By default, the nullglob is turned off. And it tends people to use bad
habits in shell scripting.
In my POV the nullglob could be turned on by
On Fri, Jul 13, 2012 at 01:56:29PM +0200, Roman Rakus wrote:
Hi,
I have a question about nullglob bash's shell option. I want to hear
opinions.
The behavior is nicely described in bash reference manual [1]
By default, the nullglob is turned off. And it tends people to use
bad habits in shell
On 07/13/2012 02:06 PM, Scott Schmit wrote:
So ls *.foo should list the entire directory if no files match *.foo?
It's a bad habit for me to expect ls *.foo to return nothing in this
case? You're going to need to convince me.
And if there are directories ending with .foo? Hopefully you are not
On Fri, 2012-07-13 at 13:56 +0200, Roman Rakus wrote:
Hi,
I have a question about nullglob bash's shell option. I want to hear
opinions.
The behavior is nicely described in bash reference manual [1]
By default, the nullglob is turned off. And it tends people to use bad
habits in shell
On 07/13/2012 02:19 PM, Tomas Mraz wrote:
This could cause serious surprising breakages of scripts with strange
consequences. I'm strictly against this change. If something at all
should be changed in this regard to break bad habits then it should be
the failglob option although I am not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/13/2012 01:06 PM, Scott Schmit wrote:
On Fri, Jul 13, 2012 at 01:56:29PM +0200, Roman Rakus wrote:
Hi, I have a question about nullglob bash's shell option. I want
to hear opinions. The behavior is nicely described in bash
reference manual
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/13/2012 01:31 PM, Bryn M. Reeves wrote:
I wouldn't back this change either but that's not the behaviour of
nullglob. If nothing matches the glob the word remains unchanged
(i.e. *.foo - *.foo):
Eh, nevermind.. not enough coffee.
Bryn.
Roman Rakus wrote:
By default, the nullglob is turned off. And it tends people to use bad
habits in shell scripting.
What habits exactly, and why are those habits bad?
In my POV the nullglob could be turned on by default. However, i would
like to hear opinions from others.
Changing a
Roman wrote:
It is possible it can break many scripts even in rpm's
scriptlets, but as I already said, it's because bad
habits. So the main gain will be the people will learn how
is the globbing in bash and in the whole environment
working.
Please don't. If an author or maintainer wants to
