Hi Eric, Hi Chet,
> http://thread.gmane.org/gmane.comp.standards.posix.austin.general/8371/focus=8377
Thanks for all these pointers! (I was not aware that
standardization of shell features was so alive today).
Sorry about the noise.
On 10/14/13 9:51 AM, Akim Demaille wrote:
> Hi!
>
> I have this weird behavior that I do not understand: when running
>
> FOO=1 foo
>
> I do not expect FOO to remain in the env after foo was invoked, even
> if foo is a shell function. However it does, _if_ bash is invoked
> in POSIX mode,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/15/13 10:47 PM, Eric Blake wrote:
> On 10/15/2013 06:57 AM, Martin Brugnara wrote:
>> It seams that "cd [/]{1,}" should take you to the root node. (as showed up
>> by 'ls')
>>
>> But when we try with two "/" something goes wrong:
>>ls works a
On 10/14/2013 07:51 AM, Akim Demaille wrote:
> Hi!
>
> I have this weird behavior that I do not understand: when running
>
> FOO=1 foo
>
> I do not expect FOO to remain in the env after foo was invoked, even
> if foo is a shell function. However it does, _if_ bash is invoked
> in POSIX mo
On 10/15/2013 06:57 AM, Martin Brugnara wrote:
> It seams that "cd [/]{1,}" should take you to the root node. (as showed up
> by 'ls')
>
> But when we try with two "/" something goes wrong:
>ls works as to be in the root node,
>pwd report "//" as path instead of "/"
>the bash line repo
Le 14 oct. 2013 à 15:51, Akim Demaille a écrit :
> $ bash --version
> GNU bash, version 3.2.48(1)-release (x86_64-apple-darwin12)
> Copyright © 2007 Free Software Foundation, Inc.
I observe the same thing with less ancient versions of bash.
/tmp % bash --version
GNU bash, version 4.2.45(1)-rel
It seams that "cd [/]{1,}" should take you to the root node. (as showed up
by 'ls')
But when we try with two "/" something goes wrong:
ls works as to be in the root node,
pwd report "//" as path instead of "/"
the bash line report "//" as path too
How to reproduce:
user@pc:/home/user$
Hi!
I have this weird behavior that I do not understand: when running
FOO=1 foo
I do not expect FOO to remain in the env after foo was invoked, even
if foo is a shell function. However it does, _if_ bash is invoked
in POSIX mode, something which I couldn't find documented in the
model (
On 10/15/13 4:44 PM, Joshuah Hurst wrote:
> On Tue, Oct 15, 2013 at 10:36 PM, Chet Ramey wrote:
>> On 10/15/13 4:27 PM, Joshuah Hurst wrote:
>>
> What happened to the patch for cd -@ to handle NFSv4+Windows alternate
> streams? ksh93 already has this feature since quite some time and
>
On Tue, Oct 15, 2013 at 10:36 PM, Chet Ramey wrote:
> On 10/15/13 4:27 PM, Joshuah Hurst wrote:
>
What happened to the patch for cd -@ to handle NFSv4+Windows alternate
streams? ksh93 already has this feature since quite some time and
they're now even extending support even further
On 10/15/13 4:27 PM, Joshuah Hurst wrote:
>>> What happened to the patch for cd -@ to handle NFSv4+Windows alternate
>>> streams? ksh93 already has this feature since quite some time and
>>> they're now even extending support even further to the builtin POSIX
>>> commands...
I have not added it t
On 10/15/13 1:02 PM, Andrey Osipov wrote:
> Chris Down writes:
>
>> On 2013-10-04 09:35, Chet Ramey wrote:
>>> On 10/4/13 3:32 AM, Chris Down wrote:
On 2013-10-02 16:33, Andrey Osipov wrote:
> Is failglob meant to be used in interactive shell?
Basically, you can't use it right
On Sat, Oct 12, 2013 at 10:14 PM, Joshuah Hurst wrote:
> On Sat, Oct 12, 2013 at 8:34 PM, Cedric Blancher
> wrote:
>> On 7 October 2013 02:14, Chet Ramey wrote:
>>> The second beta release of bash-4.3 is now available with the URL
>>>
>>> ftp://ftp.cwru.edu/pub/bash/bash-4.3-beta2.tar.gz
>>>
>>>
Chris Down writes:
> On 2013-10-04 09:35, Chet Ramey wrote:
>> On 10/4/13 3:32 AM, Chris Down wrote:
>> > On 2013-10-02 16:33, Andrey Osipov wrote:
>> >> Is failglob meant to be used in interactive shell?
>> >
>> > Basically, you can't use it right now if you are using completions that
>> > coul
14 matches
Mail list logo
