From: Martijn Dekker <martijn@inlv.org>
To: zsh-workers@zsh.org
Subject: Re: ZSH_SCRIPT
Date: Wed, 02 Mar 2016 20:34:59 +0100 [thread overview]
Message-ID: <56D74063.6020202@inlv.org> (raw)
In-Reply-To: <20160301150707.2ee18f01@pwslap01u.europe.root.pri>
Peter Stephenson schreef op 01-03-16 om 16:07:
> On Tue, 1 Mar 2016 09:39:19 -0500
> Greg Klanderman <gak@klanderman.net> wrote:
>> Should we explicitly document that ZSH_SCRIPT is empty rather than
>> unset when not invoked as a script?
>
> That would probably be sensible.
Is there a particular reason why it should be empty rather than unset?
Unset seems more logical; if we're not running a script, the script name
is not the empty string but it doesn't exist. This would also make it
possible to do
[[ -v ZSH_SCRIPT ]]
to check if you're in a script.
- M.
next prev parent reply other threads:[~2016-03-02 19:35 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 17:34 ZSH_SCRIPT Greg Klanderman
2016-02-24 22:31 ` ZSH_SCRIPT Bart Schaefer
2016-02-25 9:33 ` ZSH_SCRIPT Peter Stephenson
2016-02-25 17:59 ` ZSH_SCRIPT Greg Klanderman
2016-02-25 23:04 ` ZSH_SCRIPT Bart Schaefer
2016-02-29 23:36 ` ZSH_SCRIPT Greg Klanderman
2016-03-01 9:27 ` ZSH_SCRIPT Peter Stephenson
2016-03-01 14:39 ` ZSH_SCRIPT Greg Klanderman
2016-03-01 15:07 ` ZSH_SCRIPT Peter Stephenson
2016-03-01 16:36 ` ZSH_SCRIPT Greg Klanderman
2016-03-01 18:36 ` ZSH_SCRIPT Bart Schaefer
2016-03-01 20:14 ` ZSH_SCRIPT Greg Klanderman
2016-03-02 9:30 ` ZSH_SCRIPT Peter Stephenson
2016-03-02 15:48 ` ZSH_SCRIPT Greg Klanderman
2016-03-02 15:56 ` ZSH_SCRIPT Peter Stephenson
2016-03-02 21:33 ` ZSH_SCRIPT Greg Klanderman
2016-03-02 19:34 ` Martijn Dekker [this message]
2016-03-02 21:24 ` ZSH_SCRIPT Greg Klanderman
2016-03-03 9:37 ` ZSH_SCRIPT Peter Stephenson
2016-03-03 17:26 ` ZSH_SCRIPT Greg Klanderman
2016-03-03 17:37 ` ZSH_SCRIPT Peter Stephenson
2016-03-03 19:36 ` ZSH_SCRIPT Greg Klanderman
2016-03-03 20:39 ` ZSH_SCRIPT Peter Stephenson
2016-03-03 20:44 ` ZSH_SCRIPT Bart Schaefer
2016-03-03 20:50 ` ZSH_SCRIPT Bart Schaefer
2016-03-04 2:07 ` ZSH_SCRIPT Greg Klanderman
2016-03-05 16:22 ` ZSH_SCRIPT Bart Schaefer
2016-03-05 20:03 ` ZSH_SCRIPT Greg Klanderman
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=56D74063.6020202@inlv.org \
--to=martijn@inlv.org \
--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).