zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: DEBUG trap and warn_create_global
Date: Mon, 20 Nov 2017 17:45:11 -0800	[thread overview]
Message-ID: <CAH+w=7bqzeHZZDPSSxR4wmueA0BPDgSGL9zi549rO0dHw=dm8Q@mail.gmail.com> (raw)
In-Reply-To: <20171120040845.GA37154@CptOrmolo.darkstar>

On Sun, Nov 19, 2017 at 8:08 PM, Matthew Martin <phy1729@gmail.com> wrote:
>
> I would think ZSH_DEBUG_CMD is local to the trap execution. Otherwise
> DEBUG traps can "break" warn_create_global clean functions.

Hm.  Making it implicitly local would change the behavior with respect
to "unset after the trap."  I don't know how important that is.

However, it should be possible for it to be set without tripping the
warning, we just need to call assignsparam() instead of setsparam().

(Apologies if this gets wordwrapped or something, I don't have access
to my usual email client this week.)

diff --git a/Src/exec.c b/Src/exec.c
index fc6d02d..49da562 100644
--- a/Src/exec.c
+++ b/Src/exec.c
@@ -1319,7 +1319,9 @@ execlist(Estate state, int dont_change_job, int exiting)
            noerrexit = NOERREXIT_EXIT | NOERREXIT_RETURN;
            if (ltype & Z_SIMPLE) /* skip the line number */
                pc2++;
-           pm = setsparam("ZSH_DEBUG_CMD", getpermtext(state->prog, pc2, 0));
+           pm = assignsparam("ZSH_DEBUG_CMD",
+                              getpermtext(state->prog, pc2, 0),
+                              0);

            exiting = donetrap;
            ret = lastval;


  reply	other threads:[~2017-11-21  1:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-20  4:08 Matthew Martin
2017-11-21  1:45 ` Bart Schaefer [this message]
2017-12-06  2:18   ` Matthew Martin

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='CAH+w=7bqzeHZZDPSSxR4wmueA0BPDgSGL9zi549rO0dHw=dm8Q@mail.gmail.com' \
    --to=schaefer@brasslantern.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).