[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Feature Request]export extglob from environment

From: Jan Schampera
Subject: Re: [Feature Request]export extglob from environment
Date: Sun, 10 May 2009 11:00:04 +0200
User-agent: Mozilla-Thunderbird (X11/20090103)

Hello Chet,
hello Raph,

I was involved in the discussion on IRC (Freenode / #bash) yesterday,
maybe I can give one or the other comment.

It took a while for us to find out why it happens. When we knew it, and
after some discussion, we agreed that the easiest way would be to make
Bash able to initialize the shopts from the environment, similar to

We discussed other ways, also non-Bash solutions, but they're all more
workarounds than solutions.

>> - the environment needs extglob
> Not really.  In this particular case, you could have used `xterm -e'
> to run bash with the -O extglob option.

This isn't always possible, easy or even wanted. One of those
"workarounds" from above, IMHO.

> None of these are compelling.  Maybe a BASHOPTS analog to SHELLOPTS
> for `shopt' options.  It might be useful to provide a configuration
> option that defaults extglob to on, also.

I'd prefer some own transport variable in environment, like you said.
It's not only extglob that isn't transported, though for the rest it
doesn't result in syntax errors. Transporting these options would make
the behaviour more consistent and less surprising.

If a configure option exists or not is more a matter of taste I'd say.
But this particular problem would have been solved, yes :)

Jan "TheBonsai" Schampera

reply via email to

[Prev in Thread] Current Thread [Next in Thread]