Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: a way to get the value of the -c option
- X-seq: zsh-workers 37293
- From: Stephane Chazelas <stephane.chazelas@xxxxxxxxx>
- To: zsh-workers@xxxxxxx
- Subject: Re: a way to get the value of the -c option
- Date: Thu, 3 Dec 2015 13:49:29 +0000
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:subject:message-id:mail-followup-to:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=gcoMOdWOPl55SJWqICM3U/Jhfl8iXSFZiQhpTtXpTvk=; b=WQxws9yn6QGFI2U/7zafnLP7KxbywhrLh3xeZyjydl7EB8k5OM/GQsrPLrMURUXib2 W2G75ogYpsFjYFeEDLHaTa2OJOONWlPmGuAiff94phd7T827m7h+TapFxvL+4PppDx0w nvqy4Tt/wdDCBlkqhe4zJsKL0elJS4uZj2eDhQcUp+jDQWKQI1sf9s7780WHNOBolZrR crSaD2a7t41pgzHfZm7OkfQTNT6uJXOOfTMPvKM6i9RfdusWhtZFJUxRMaGtbBnjXf03 Gq5of8N6IrfL9/KP3JmgoVFsOrMVD3aHi9RxFZmNxAmsPnYkril7VhRAgH3lONutyDgQ UwWA==
- In-reply-to: <20151203124554.3b93281f@pwslap01u.europe.root.pri>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mail-followup-to: zsh-workers@xxxxxxx
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <20151203115449.GA19846@zira.vinc17.org> <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@xxxxxxxxxx> 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
Messages sorted by:
Reverse Date,
Date,
Thread,
Author