Am 29.03.2013 16:23, schrieb Pierre Gaston: > On Fri, Mar 29, 2013 at 5:10 PM, John Kearney <dethrop...@web.de> wrote: >> consider >> dethrophes@dethace ~ >> $ read -ra vals -d '' <<< $'lkjlksda\n adasd\n:sdasda:' >> >> dethrophes@dethace ~ >> $ echo ${vals[0]} >> lkjlksda >> >> I meant to update your wiki about it but I forgot. >> I guess read uses gets not fread and that truncates the line anyway. >> > you miss the IFS part: > IFS=: read -ra vals -d '' <<< $'lkjlksda\n adasd\n:sdasda:' > echo "${vals[0]}" > > (IFS contains \n by default) Ok that works, I must have somehow misunderstood the description. Oh well thanks that makes he world a little more sane.
- Re: weird problem -- path interpretted/eval'd as numeric... Greg Wooledge
- Re: weird problem -- path interpretted/eval'd as numeric... Linda Walsh
- Re: weird problem -- path interpretted/eval'd as numeric... Dan Douglas
- Re: weird problem -- path interpretted/eval'd as numeric... Linda Walsh
- Re: weird problem -- path interpretted/eval'd as numeric... Greg Wooledge
- Re: weird problem -- path interpretted/eval'd as numeric... Stefano Lattarini
- Re: weird problem -- path interpretted/eval'd as numeric... John Kearney
- Re: weird problem -- path interpretted/eval'd as numeric... Greg Wooledge
- Re: weird problem -- path interpretted/eval'd as numeric... John Kearney
- Re: weird problem -- path interpretted/eval'd as numeric... Pierre Gaston
- Re: weird problem -- path interpretted/eval'd as numeric... John Kearney
- Re: weird problem -- path interpretted/eval'd as numeric... Greg Wooledge
- Re: weird problem -- path interpretted/eval'd as numeric... John Kearney
- Re: weird problem -- path interpretted/eval'd as numeric... John Kearney
- Re: weird problem -- path interpretted/eval'd as numeric... Chet Ramey
- Re: weird problem -- path interpretted/eval'd as numeric... Linda Walsh
- Re: weird problem -- path interpretted/eval'd as numeric... John Kearney
- Re: weird problem -- path interpretted/eval'd as numeric... Linda Walsh