zsh-workers
 help / color / mirror / code / Atom feed
From: Phil Pennock <zsh-workers+phil.pennock@spodhuis.org>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: zsh-workers@zsh.org
Subject: Re: [PATCH] Document echo \c behaviour
Date: Tue, 10 Jan 2017 09:39:31 +0000	[thread overview]
Message-ID: <20170110093931.GA13581@tower.spodhuis.org> (raw)
In-Reply-To: <20170110035259.GA31866@fujitsu.shahaf.local2>

On 2017-01-10 at 03:52 +0000, Daniel Shahaf wrote:
> Thanks; I pushed the first hunk.  I didn't push the second one because
> I don't think it's required.  If you disagree then make your case ;-).

The behaviour is bug-ass crazy nuts and needs justification.  Every
other escape sequence is a character which is inserted; \c was always
a special case for "suppress the following newline", but "truncate
_everything_ else" from an _escape_ sequence is ... face-palm worthy.

It warrants explanation as to why it's so counter-intuitive.

> P.S. Overly-literal-reading corner: doesn't "All characters following...
> will be ignored" mean that «echo 'foo\cbar' 'baz' 'qux'» should be
> equivalent to «echo 'foo\cbar' '' ''»?  I.e., print «foo» followed by
> two trailing spaces?

Sounds right.  Take it up with the Austin Group.  I believe that Bart is
masochistic enough to pay attention in those arenas and might be willing
to raise it as a spec bug.

(I tried following AG for a while, and ran away)


  reply	other threads:[~2017-01-10  9:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-09 20:32 Phil Pennock
2017-01-10  3:52 ` Daniel Shahaf
2017-01-10  9:39   ` Phil Pennock [this message]
2017-01-10 16:05     ` Daniel Shahaf

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=20170110093931.GA13581@tower.spodhuis.org \
    --to=zsh-workers+phil.pennock@spodhuis.org \
    --cc=d.s@daniel.shahaf.name \
    --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).