Re: [PATCH] latest ash has broken 'echo' command

To: ajosey@rdg.opengroup.org (Andrew Josey)
Cc: lsb-spec@lists.linuxbase.org, debian-devel@lists.debian.org
Subject: Re: [PATCH] latest ash has broken 'echo' command
From: Daniel Quinlan <quinlan@transmeta.com>
Date: 22 Oct 1999 15:49:36 -0700
Message-id: <[🔎] 6yiu3zhuyn.fsf@sodium.transmeta.com>
In-reply-to: Andrew Josey's message of Fri, 22 Oct 1999 13:57:06 +0100
References: <[🔎] E11ecsK-0005Qn-00@the-village.bc.nu> <[🔎] 991022125705.ZM1158@skye.rdg.opengroup.org>

Andrew Josey <ajosey@rdg.opengroup.org> writes:

> The latest draft of POSIX 1003.1 now has the escape sequences
> mandated ... (of course things could still change before the spec is
> finalised).

The "-n" option needs to work and there should be an option to turn
off escape sequences (GNU uses -E).

Dan

Reply to:

References:
- Re: [PATCH] latest ash has broken 'echo' command
  - From: Alan Cox <alan@lxorguk.ukuu.org.uk>
- Re: [PATCH] latest ash has broken 'echo' command
  - From: Andrew Josey <ajosey@rdg.opengroup.org>

Prev by Date: Re: [PATCH] latest ash has broken 'echo' command
Next by Date: Re: PROPOSAL: API for device locking library.
Previous by thread: Re: [PATCH] latest ash has broken 'echo' command
Next by thread: Re: [PATCH] latest ash has broken 'echo' command
Index(es):
- Date
- Thread