On Tue, Jan 08, 2013 at 10:26:19PM +, John Caruso wrote:
> I checked the
> bash source but couldn't suss out (in a brief look) how minor bash
> versions are accounted--there's no 4.2.10 or 4.2.24 source, just 4.2
> source plus a bunch of patches, and it's not clear if those patches have
> made
On 1/8/13 5:26 PM, John Caruso wrote:
> I forgot to mention that I've tested this with bash 4.2.10 and 4.2.24,
> and neither of them appear to have the direxpand option. I checked the
> bash source but couldn't suss out (in a brief look) how minor bash
> versions are accounted--there's no 4.2.10
On 1/8/13 5:38 PM, John Caruso wrote:
> In article , Chet Ramey wrote:
>> On 1/8/13 5:18 PM, John Caruso wrote:
>>> In bash 4.1, if you do "shopt +s dirspell" and type "ls /ect/passwd"
>>> it's corrected to "ls /etc/passwd". In bash 4.2 with dirspell enabled,
>>> the correction doesn't happen.
>>>
Hi!
I found an issue while using array variables in an arithmetical
context. I tried to determine where the problem was, but I didn't
understand expr.c. The backtrace points to expr.c's line 556, in
expassing. I tested both the master and devel branches.
-
The development version of bash seems to handle brace expansion
differently than the stable version.
The relevant code:
---
Code
---
echo "$BASH_
In article , Chet Ramey wrote:
> On 1/8/13 5:38 PM, John Caruso wrote:
>> So just to verify: there's no way in bash 4.2.0 through 4.2.28 to make
>> dirspell work correctly? The only fix is the direxpand option?
>
> Yes. Through 4.2.28, the dirspell option will cause the filename to be
> rewritte
Hi. These were easy for me to reproduce in various versions.
Export to mapfile the variable to be assigned, then run any callback:
$ printf '%s\n' {a..z} | bash -xc 'a= mapfile -tc1 -C : a'
+ a=
+ mapfile -tc1 -C : a
++ : 0 a
Segmentation fault
Set any vari
When expanding simple commands, steps 3 and 4 are reversed unconditionally for
all command types and number of words expanded, even in POSIX mode.
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_09_01
The exceptions allowed by POSIX appear to only apply to ksh93. Ot
I'll lump a few issues together here...
1. Backslash escape adjacent to "$@" expansion separates words.
$ set -- abc def ghi; printf '<%s> ' "123 $@ 456"; echo
<123 abc>
$ set -- abc def ghi; printf '<%s> ' "123 $@\ 456"; echo
<123 abc> <456>
Other shells don't do this (thou
On Wednesday, January 09, 2013 10:15:31 AM Eduardo A. Bustamante López wrote:
> Hi!
>
> I found an issue while using array variables in an arithmetical
> context. I tried to determine where the problem was, but I didn't
> understand expr.c. The backtrace points to expr.c's line 556, in
> expassing
10 matches
Mail list logo