Stephane Chazelas wrote:
>
> That would be a bug. Looking at the code, it takes a different
> path for colon just because of the fact that in assignment,
> tilde expansion is performed after a colon (as in
> PATH=...:~/bin), if : happens to also be an IFS character, it is
> therefore not internal
Stephane Chazelas wrote:
>> If this is intended behaviour, can you tell me why (it's gone with
>> quoting/escaping, of course)?
> [...]
>
> That would be a bug. Looking at the code, it takes a different
Good to know that I'm not completely mistaken - it smells buggy.
Only Chet knows for sure wh
to behave different. I see that across all my available
> Bash versions. I remember the colon to be special in some way (was it
> hostnames in a file path?), but I don't know.
>
> If this is intended behaviour, can you tell me why (it's gone with
> quoting/escaping, of c
Hi.
In comp.unix.shell [1] somebody wondered about
IFS=: read a b <<< a:b; echo "'$a' '$b'"
ending up in
'a b' ''
Korn and Z seem to behave different. I see that across all my available
Bash versions. I remember the colon to be sp
