Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
From: Bart Schaefer <schaefer@brasslantern.com>
Message-Id: <160219105924.ZM17561@torch.brasslantern.com>
Date: Fri, 19 Feb 2016 10:59:24 -0800
In-Reply-To: <56C4041F.5060602@inlv.org>
Comments: In reply to Martijn Dekker <martijn@inlv.org>
        "Re: [BUG] Sticky-sh POSIX_TRAPS are function-local" (Feb 17,  6:24am)
References: <56C15DF1.8080405@inlv.org> 
	<20160216095744.52cb8389@pwslap01u.europe.root.pri> 
	<56C3B2E7.1090806@inlv.org> 
	<160216202547.ZM3900@torch.brasslantern.com> 
	<56C4041F.5060602@inlv.org>
To: zsh-workers@zsh.org
Subject: Re: [BUG] Sticky-sh POSIX_TRAPS are function-local
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On Feb 17,  6:24am, Martijn Dekker wrote:
}
} But POSIX is irrelevant to function-local traps because they are not
} defined in POSIX, so, once emulation mode is exited, there is nothing
} that compels you to make them wipe out a global POSIX trap.

That's sort of the point -- there's nothing that compels us, hence ...

} > I could see an argument either way

... and your argument is a pretty good one.

} > I could also see an argument
} > that the localtraps option should affect this
} 
} How do you think that option should affect this?

To be pedantic, I didn't say I think that; I said I could understand how
one might argue that position.  To try to frame it -- the implication is
that a trap created under LOCAL_TRAPS should *never* alter traps in any
outer scope.  This ought to include the global scope, regardless of the
context in which the global trap was created.

I.e. given "setopt POSIX_TRAPS LOCAL_TRAPS" this argues that LOCAL_TRAPS
should "win".  With PWS's patch, POSIX_TRAPS prevails.