From: Stephane Chazelas <stephane.chazelas@gmail.com>
To: zsh-workers@zsh.org
Subject: Re: a way to get the value of the -c option
Date: Thu, 3 Dec 2015 13:49:29 +0000 [thread overview]
Message-ID: <20151203134929.GA9581@chaz.gmail.com> (raw)
In-Reply-To: <20151203124554.3b93281f@pwslap01u.europe.root.pri>
2015-12-03 12:45:54 +0000, Peter Stephenson:
> On Thu, 3 Dec 2015 12:54:49 +0100
> Vincent Lefevre <vincent@vinc17.net> wrote:
> > zsh should provide a way to get the value of the -c option. Under
> > Linux, one can look at /proc/$$/cmdline, but I think that it would
> > be better to get this information in an OS-independent way.
[...]
> +vindex(ZSH_CMD_ARG)
> +item(tt(ZSH_CMD_ARG))(
> +If the shell was started with the option tt(-c), this contains
> +the argument passed to the option. Otherwise it is not set.
[...]
Note that bash calls it $BASH_EXECUTION_STRING
It could be useful to have zsh's equivalent being
$ZSH_EXECUTION_STRING.
Note that bash doesn't clear it from the environment and doesn't
unexport it:
$ echo set | env BASH_EXECUTION_STRING=zzz bash -s | grep zzz
BASH_EXECUTION_STRING=zzz
$ BASH_EXECUTION_STRING=zzz bash -c 'echo $BASH_EXECUTION_STRING; echo set | bash' | grep EXE
echo $BASH_EXECUTION_STRING; echo set | bash
BASH_EXECUTION_STRING='echo $BASH_EXECUTION_STRING; echo set | bash'
Now, if *you* export it to the environment, you're the one to
blame. In the case of bash, it's also affected by the -a
option:
$ bash -ac env | grep BASH
BASH=/bin/bash
BASH_EXECUTION_STRING=env
BASH_VERSION=4.3.11(1)-release
env -i zsh -ac env
shows a lot of variables as well. The intent with "-a" is that
all *newly-declared* (after "set -a" is issued) variables are
automatically exported. It's arguable whether those internal
variables should also be exported or not when the shell is
called with -a. mksh bash zsh export them, dash ksh93 yash
don't.
Cheers,
--
Stephane
next prev parent reply other threads:[~2015-12-03 16:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 11:54 Vincent Lefevre
2015-12-03 12:45 ` Peter Stephenson
2015-12-03 13:36 ` Vincent Lefevre
2015-12-03 14:01 ` Peter Stephenson
2015-12-03 14:23 ` Peter Stephenson
2015-12-03 14:40 ` Peter Stephenson
2015-12-03 14:39 ` Vincent Lefevre
2015-12-03 13:49 ` Stephane Chazelas [this message]
2015-12-03 17:01 ` Peter Stephenson
2015-12-03 14:36 ` Nikolay Aleksandrovich Pavlov (ZyX)
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=20151203134929.GA9581@chaz.gmail.com \
--to=stephane.chazelas@gmail.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).