zsh-workers
 help / color / mirror / code / Atom feed
From: Mikael Magnusson <mikachu@gmail.com>
To: Peter Stephenson <p.stephenson@samsung.com>
Cc: zsh workers <zsh-workers@zsh.org>
Subject: Re: [BUG]builtin echo error doing arguments parsing
Date: Thu, 22 Feb 2018 20:00:58 +0100	[thread overview]
Message-ID: <CAHYJk3THGAxVRGepVT+eu5_oAHz6Mxv5oPe3rFQ6acaNoQ7QKg@mail.gmail.com> (raw)
In-Reply-To: <20180222172601.2b7cb68b@pwslap01u.europe.root.pri>

On Thu, Feb 22, 2018 at 6:26 PM, Peter Stephenson
<p.stephenson@samsung.com> wrote:
> On Thu, 22 Feb 2018 17:50:48 +0100
> Mikael Magnusson <mikachu@gmail.com> wrote:
>> On Thu, Feb 22, 2018 at 11:32 AM, Peter Stephenson
>> <p.stephenson@samsung.com> wrote:
>> > On Thu, 22 Feb 2018 09:37:11 +0000
>> > Peter Stephenson <p.stephenson@samsung.com> wrote:
>> >> On Wed, 21 Feb 2018 23:23:09 -0800
>> >> wumingxwk@gmail.com wrote:
>> >> > if there is only a '-' as argument,builtin echo won't print it
>> >>
>> >> You might have thought it should at least be turned off in some or most
>> >> of the emulation modes...
>> >
>> > Would look something like this.  Probably a good idea if there aren't
>> > subtleties?
>>
>> If we change it now, people would have to add a version check in
>> addition to their check for zsh to be able to echo things portably (to
>> know if they should add an extra - or not).
>
> The portable option is "--", which has worked for a long time.  Adding -
> would be a zsh kludge, nothing to do with portability.

My point is that if people are already doing "echo - $whatever" when
they detect zsh, and we stop parsing it, their stuff will break
(output their extra dash). I didn't try the patch but currently echo
-- just outputs --, only - terminates options for echo.

-- 
Mikael Magnusson


  reply	other threads:[~2018-02-22 19:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20180222072350epcas2p3185ca17f5f0e3ad69b0a41dbf743f145@epcas2p3.samsung.com>
2018-02-22  7:23 ` wumingxwk
2018-02-22  9:37   ` Peter Stephenson
2018-02-22 10:32     ` Peter Stephenson
2018-02-22 16:50       ` Mikael Magnusson
2018-02-22 17:26         ` Peter Stephenson
2018-02-22 19:00           ` Mikael Magnusson [this message]
2018-02-22 19:04             ` Bart Schaefer
2018-02-22 19:34             ` Peter Stephenson
2018-02-24  8:20               ` Stephane Chazelas
2018-02-24  9:51                 ` Peter Stephenson
2018-02-24 19:41                   ` Peter Stephenson
2019-04-27  6:46                 ` Stephane Chazelas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAHYJk3THGAxVRGepVT+eu5_oAHz6Mxv5oPe3rFQ6acaNoQ7QKg@mail.gmail.com \
    --to=mikachu@gmail.com \
    --cc=p.stephenson@samsung.com \
    --cc=zsh-workers@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).