From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6224 invoked from network); 1 Aug 2000 08:12:24 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 1 Aug 2000 08:12:24 -0000 Received: (qmail 29596 invoked by alias); 1 Aug 2000 08:12:12 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 12452 Received: (qmail 29569 invoked from network); 1 Aug 2000 08:12:11 -0000 Date: Tue, 1 Aug 2000 10:12:09 +0200 (MET DST) Message-Id: <200008010812.KAA06451@beta.informatik.hu-berlin.de> From: Sven Wischnowsky To: zsh-workers@sunsite.auc.dk In-reply-to: "Bart Schaefer"'s message of Tue, 1 Aug 2000 07:15:25 +0000 Subject: Re: FW: About word splitting in read (Zsh) Bart Schaefer wrote: > On Aug 1, 9:40am, Andrej Borsenkow wrote: > } Subject: FW: About word splitting in read (Zsh) > } > } In (almost latest) CVS: > } > } bor@itsrm2% read -r foo > } qwert yuiop ! > } bor@itsrm2% print -r $foo > } qwert yuiop ! > } > } So, the question is - should we fix -r or introduce new option? > > Neither. > > zagzig[271] IFS=$'\n' read -r line <<<' this has many spaces ' > zagzig[272] echo %$line% > % this has many spaces % Ouch. I didn't remember that, even though I already used it... But still. The docs are wrong (backslashes inside the string). Should we change the code or the doc? Bye Sven -- Sven Wischnowsky wischnow@informatik.hu-berlin.de