From owner-freebsd-bugs Tue Aug 24 9:29:51 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id C5D8114DBC for ; Tue, 24 Aug 1999 09:29:29 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 11JHvj-000J8B-00; Tue, 24 Aug 1999 16:52:07 +0200 From: Sheldon Hearn To: Thomas Gellekum Cc: chris@calldei.com, Chris Piazza , freebsd-bugs@FreeBSD.ORG Subject: Re: bin/13274: /bin/sh 'read' command does not work correctly In-reply-to: Your message of "24 Aug 1999 16:33:34 +0200." Date: Tue, 24 Aug 1999 16:52:07 +0200 Message-ID: <73542.935506327@axl.noc.iafrica.com> Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 24 Aug 1999 16:33:34 +0200, Thomas Gellekum wrote: > .Pp > -The -e option causes any backslashes in the input to > -be treated specially. If a backslash is followed by > -a newline, the backslash and the newline will be > -deleted. If a backslash is followed by any other > -character, the backslash will be deleted and the following > -character will be treated as though it were > -not in IFS, even if it is. > +The -e option is deprecated and only here for backward compatibility. > +.Pp > +The -r option causes backslashes in the input to be treated > +like ordinary characters. This doesn't help the poor bastard who'd like to know what happens if he _doesn't_ specify -r. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message