zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh workers <zsh-workers@zsh.org>
Subject: Re: Unexpected foo==bar errors
Date: Mon, 08 Feb 2016 09:49:36 +0000	[thread overview]
Message-ID: <20160208094936.4917ff73@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <160207230919.ZM10127@torch.brasslantern.com>

On Sun, 07 Feb 2016 23:09:19 -0800
Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Feb 7,  7:06pm, Peter Stephenson wrote:
> } Subject: Re: Unexpected foo==bar errors
> }
> } The option is called "equals".  "magicequalsubst" is now redundant; it
> } allowed
> } 
> } typeset foo=<whatever>
> } 
> } to exapnd <whatever>
> 
> Hmm, as far as I can tell "typeset" always applied expansion in that
> case, even when it was only a builtin; magicequalsubst is there for
> other commands that take long options like --file=path or arguments
> that have key=value format.
> 
> It's certainly not redundant.

You're right about "magicequalsubst".

I was attempting to describe "kshtypeset", but actually that only
applies to word splitting, not to expansion immediately after the "=".
I'd forgotten the extent to which the full assignment behaviour had
crept up by stealth.

Apart from that...

pws


  reply	other threads:[~2016-02-08  9:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-07 15:57 Mikael Magnusson
2016-02-07 19:06 ` Peter Stephenson
2016-02-08  7:09   ` Bart Schaefer
2016-02-08  9:49     ` Peter Stephenson [this message]
2016-02-07 19:16 ` Bart Schaefer
2016-02-08  3:52   ` Mikael Magnusson
2016-02-08 18:45     ` Bart Schaefer
2016-02-08 19:16       ` Mikael Magnusson
2016-02-14 20:10         ` Failed process substitution on x=$~y (Re: Unexpected foo==bar errors) Bart Schaefer

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=20160208094936.4917ff73@pwslap01u.europe.root.pri \
    --to=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).