[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: read and env variables + POSIX => SEGFAULT
From: |
Geir Hauge |
Subject: |
Re: read and env variables + POSIX => SEGFAULT |
Date: |
Sun, 11 Oct 2015 12:59:24 +0200 |
User-agent: |
Mutt/1.5.23 (2014-03-12) |
On Sat, Oct 10, 2015 at 08:01:05PM -0700, Linda Walsh wrote:
> # this is odd: 2vars with content for 2:
> >unset a b
> >a= b= read a b <<< x y
> >declare -p a b
> declare -- a="x"
> declare -- b=""
>
> # -- where did "y" go?
read a b <<< x y
is the same as
read a b y <<< x
If you escape the space, to make it literal instead of syntactical, you'll get
the expected result:
$ a= b= read a b <<< x\ y
$ declare -p a b
declare -- a="x"
declare -- b="y"
- read and env variables, isabella parakiss, 2015/10/10
- Re: read and env variables + POSIX => SEGFAULT, Linda Walsh, 2015/10/10
- Re: read and env variables + POSIX => SEGFAULT,
Geir Hauge <=
- Re: read and env variables + POSIX => SEGFAULT, Chet Ramey, 2015/10/15
- Message not available
- Re: read and env variables + POSIX => SEGFAULT, Linda Walsh, 2015/10/15
- Re: read and env variables + POSIX => SEGFAULT, Greg Wooledge, 2015/10/13
- Re: read and env variables + POSIX => SEGFAULT, Chet Ramey, 2015/10/15
- my confusion on various I/O redirections syntaxes and indirect methods, Linda Walsh, 2015/10/13
- Re: my confusion on various I/O redirections syntaxes and indirect methods, Greg Wooledge, 2015/10/13
Re: read and env variables, Chet Ramey, 2015/10/11