zsh-workers
 help / color / mirror / code / Atom feed
From: Stephane Chazelas <stephane.chazelas@gmail.com>
To: Peter Stephenson <p.stephenson@samsung.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: [PATCHv2] [bug] $SHLVL decremented for the last command of a subshell
Date: Tue, 30 Aug 2016 20:54:29 +0100	[thread overview]
Message-ID: <20160830195429.GB50437@chaz.gmail.com> (raw)
In-Reply-To: <20160830180032.199eae0a@pwslap01u.europe.root.pri>

2016-08-30 18:00:32 +0100, Peter Stephenson:
[...]
> When this was introduced in zsh, there was some controversy over whether
> it was the right thing to do.  I decided it was on the basis that the
> "level" is how deep you are in the process hierarchy, rather than how
> many processes have previously been executed to get where you are,
> seeing as the latter isn't really visible in the current context.
> But I'm not aware of any requirement specification [remember those?]
> saying what the purpose of SHLVL is.
[...]

Yes, it's not POSIX. It was probably either a tcsh or bash
invention as both had it in 1990 and ksh88 didn't and still
doesn't have it.

And zsh behaves like tcsh and bash here (in that SHLVL is
decreased in zsh -c 'exec cmd').

-- 
Stephane


  parent reply	other threads:[~2016-09-01  4:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-22  6:17 Stephane Chazelas
2016-08-29 15:51 ` [PATCH] " Stephane Chazelas
2016-08-30  1:55   ` Bart Schaefer
2016-08-30 12:44     ` [PATCHv2] " Stephane Chazelas
2016-08-30 13:04       ` Peter Stephenson
2016-08-30 16:46         ` Stephane Chazelas
2016-08-30 17:00           ` Peter Stephenson
2016-08-30 18:34             ` Mikael Magnusson
2016-08-31  9:02               ` Peter Stephenson
2016-08-30 19:54             ` Stephane Chazelas [this message]
2016-08-30 20:10               ` Stephane Chazelas
2016-08-31 10:06       ` Peter Stephenson
2016-09-04  5:32         ` Stephane Chazelas

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=20160830195429.GB50437@chaz.gmail.com \
    --to=stephane.chazelas@gmail.com \
    --cc=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).