On 8/21/12 7:45 AM, Ondrej Oprala wrote:
> Hi,
> unless this bug is already fixed in some way
I changed bash-4.1 to remember environment strings that are not valid shell
variable names, like those containing a dot, and add them to the
environment exported to commands. They're not valid shell vari
On 08/21/2012 05:45 AM, Ondrej Oprala wrote:
> Hi,
> unless this bug is already fixed in some way
> https://groups.google.com/forum/?fromgroups=#!topic/gnu.bash.bug/xpZl_-eiFCY
>
> ...I've created a tiny patch that should fix it.
Sorry, but this would violate POSIX, which requires that '.' is not
On Tuesday 21 August 2012 07:45:49 Ondrej Oprala wrote:
> unless this bug is already fixed in some way
yes, please retest with very latest bash-4.2 and the released patchsets
-mike
signature.asc
Description: This is a digitally signed message part.
Hi,
unless this bug is already fixed in some way
https://groups.google.com/forum/?fromgroups=#!topic/gnu.bash.bug/xpZl_-eiFCY
...I've created a tiny patch that should fix it.
Cheers,
Ondrej.
diff -up bash-upstream/general.h.patch bash-upstream/general.h
--- bash-upstream/general.h.patch 20
On Tuesday, August 21, 2012 07:24:31 AM Stephane Chazelas wrote:
> 2012-08-20 19:44:51 +0200, Roman Rakus:
> [...]
> > And how would you achieve to fill array with all file names
> > containing `[1]=' for example.
> [...]
>
> Another interesting question is how to fill the array with all
> the fil
