zsh-users
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.stephenson@samsung.com>
To: <zsh-users@zsh.org>
Subject: Re: print builtin preceded by parameter assignment
Date: Wed, 10 Apr 2019 15:39:46 +0100	[thread overview]
Message-ID: <1554907186.6252.12.camel@samsung.com> (raw)
In-Reply-To: <20190410141113.GD15169@cventin.lip.ens-lyon.fr>

On Wed, 2019-04-10 at 16:11 +0200, Vincent Lefevre wrote:
> 1. If the command name is not a special built-in utility or function,
> the variable assignments shall be exported for the execution environment
> of the command [...]
> 
> In this case, the variable assignments should affect the output.

I see how you're interpreting this --- the "execution environment of the
command" is anything the command happens to do, not just what the
environment itself would show, while "the current execution
environment", which explicitly isn't affected by a bit you didn't quote
and which I assumed included "print" as it is part of the current
execution environment, to you is just what happens after the command
finishes.

In any case, I wasn't planning on changing this --- effectively adding a
full local variable behaviour when the intention of the syntax is to
export a parameter to the environment is a bit perverse.  If anyone else
thinks they can do it without major grief they're welcome to have a go
and we can see if the end justifies the means.  Often (but by no means
necessarily) this sort of thing breaks more than it fixes.

pws


  reply	other threads:[~2019-04-10 14:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20190410125753epcas1p4052249a86c562165e1fe2a485d70e70b@epcas1p4.samsung.com>
2019-04-10 12:55 ` Vincent Lefevre
2019-04-10 13:14   ` Peter Stephenson
2019-04-10 14:11     ` Vincent Lefevre
2019-04-10 14:39       ` Peter Stephenson [this message]
2019-04-10 17:25         ` Bart Schaefer
2019-04-11 10:40           ` Vincent Lefevre
2019-04-11 20:58             ` Bart Schaefer
2019-04-11 21:42               ` Bart Schaefer
2019-04-24 12:31                 ` Vincent Lefevre
2019-04-24 16:00                   ` Bart Schaefer
2019-04-25 19:47                     ` Bart Schaefer
2019-04-11 10:45         ` Vincent Lefevre

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=1554907186.6252.12.camel@samsung.com \
    --to=p.stephenson@samsung.com \
    --cc=zsh-users@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).