zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@zsh.org
Subject: Re: PATCH: funcstack[-1]  (formerly Suppress tracing of "set +x")
Date: Fri, 5 Feb 2016 09:20:38 -0800	[thread overview]
Message-ID: <160205092038.ZM29758@torch.brasslantern.com> (raw)
In-Reply-To: <20160205164606.7ff9d27d@pwslap01u.europe.root.pri>

On Feb 5,  4:46pm, Peter Stephenson wrote:
} Subject: Re: PATCH: funcstack[-1]  (formerly Suppress tracing of "set +x")
}
} On Fri, 05 Feb 2016 08:14:28 -0800
} Bart Schaefer <schaefer@brasslantern.com> wrote:
} > On Feb 5,  4:02pm, Peter Stephenson wrote:
} > }
} > } My main worry is someone is using ${#funcstack} to decide if they're at
} > } top-level, rather than zsh_eval_context, which would now fail.
} > 
} > There are several uses of $#funcstack in the Completion/ function suite.
} 
} None of them are sensitive to (permanently) adding an extra level at the
} end of the array, as far as I can see.

My concern is that $_tags_level is initialized to 0 in _main_complete
and then compared to $#funcstack later.  If $#funcstack is now always no
less than 1, that will be wrong.

Of course we can fix _main_complete to initialize to 1, but this does
imply that comparisons to $#funcstack are not an unknown programming
technique.


  reply	other threads:[~2016-02-05 17:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-30 10:45 Suppress tracing of "set +x" Dominik Vogt
2015-12-30 15:30 ` Martijn Dekker
2015-12-30 15:55   ` Dominik Vogt
2016-02-05 10:09   ` Dominik Vogt
2016-02-05 10:16     ` Dominik Vogt
2016-02-05 10:27     ` Peter Stephenson
2016-02-05 10:44       ` Peter Stephenson
2016-02-05 16:02         ` PATCH: funcstack[-1] (formerly Suppress tracing of "set +x") Peter Stephenson
2016-02-05 16:14           ` Bart Schaefer
2016-02-05 16:46             ` Peter Stephenson
2016-02-05 17:20               ` Bart Schaefer [this message]
2016-02-05 17:32                 ` Peter Stephenson
2016-02-05 10:37     ` Suppress tracing of "set +x" Martijn Dekker
2016-02-05 18:48     ` Bart Schaefer
     [not found] ` <5683F898.7010907__5021.31003090671$1451490149$gmane$org@inlv.org>
2016-01-01 18:36   ` 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=160205092038.ZM29758@torch.brasslantern.com \
    --to=schaefer@brasslantern.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).