zsh-workers
 help / color / mirror / code / Atom feed
From: Martijn Dekker <martijn@inlv.org>
To: zsh-workers@zsh.org
Subject: Re: Bug with traps and exit
Date: Fri, 13 Dec 2019 15:26:30 +0100	[thread overview]
Message-ID: <46f2fc10-2f2c-88f1-e4e2-87196a39a37a@inlv.org> (raw)
In-Reply-To: <1576145690.8441.3.camel@samsung.com>

Op 12-12-19 om 11:14 schreef Peter Stephenson:
> On Tue, 2019-12-10 at 20:23 +0100, Martijn Dekker wrote:
>> Op 24-11-19 om 06:54 schreef Martijn Dekker:
>> [...]
>>>   
>>> A related issue (possibly the same?) with a much simpler test case:
>>>   
>>> trap 'echo SIGINT; trap - INT; kill -s INT $$; echo woops' INT
>>> kill -s INT $$
>>>   
>>> zsh prints 'woops', but shouldn't.
>> Ping?
>>   
>> Is this just being missed, or is it considered too unimportant?
> 
> Are you saying there's a fix for this we need to apply?  I haven't seen
> one.

No, I'm saying my nearly year-old bug report seems to be being either 
overlooked or ignored.

I don't have the expertise to fix this myself. Signal handling in C is 
beyond me. I could give it a try, but it would likely be wrong and/or 
broken, so I figure I might as well not waste your time or mine.

So far, zsh maintainers have been receptive to bug reports (mine and 
others) even if the reporter can't provide a fix. Has that changed?

I mean, I'm not trying to criticise anyone. I fully understand if you 
only want bug report with patches. It's just that that isn't how things 
seem to have worked so far.

- M.

-- 
modernish -- harness the shell
https://github.com/modernish/modernish

  reply	other threads:[~2019-12-13 14:27 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-05  7:08 Test release: 5.6.2-test-3 dana
2019-01-05 17:49 ` Peter Stephenson
2019-01-05 18:42   ` dana
2019-01-05 20:58   ` Martijn Dekker
2019-01-05 21:55     ` Daniel Shahaf
2019-01-06  2:37 ` Axel Beckert
2019-01-06 15:12 ` Jun T.
2019-01-06 16:37   ` dana
2019-01-06 16:43     ` Daniel Shahaf
2019-01-06 16:56       ` dana
2019-01-06 21:34     ` Daniel Tameling
2019-01-07  3:25     ` Jun T
2019-01-07  7:02       ` dana
2019-01-21 12:54 ` ETA for zsh 5.7? (was: Test release: 5.6.2-test-3) Axel Beckert
2019-01-21 14:26   ` Peter Stephenson
2019-01-21 19:14     ` Mikael Magnusson
2019-01-21 19:32       ` Mikael Magnusson
2019-01-21 19:32       ` Mikael Magnusson
2019-01-21 21:56         ` Sebastian Gniazdowski
2019-01-22  9:29           ` Peter Stephenson
2019-01-21 23:00 ` Bug with traps and exit Martijn Dekker
2019-11-24  5:54   ` Martijn Dekker
2019-11-25 16:42     ` Sebastian Gniazdowski
2019-12-10 19:23     ` Martijn Dekker
2019-12-11  2:40       ` Daniel Shahaf
2019-12-12 10:14       ` Peter Stephenson
2019-12-13 14:26         ` Martijn Dekker [this message]
2019-12-13 14:49           ` Peter Stephenson
2019-12-14 11:28             ` Daniel Shahaf
2019-12-15 18:59               ` Peter Stephenson
2019-12-16  5:24                 ` Daniel Shahaf
2019-12-16  6:37                   ` Bart Schaefer
2019-12-17  7:31                     ` Daniel Shahaf
2019-12-17 20:29                       ` Peter Stephenson
2019-12-18  0:31                         ` Daniel Shahaf
2019-12-31  2:03                           ` Daniel Shahaf
2019-12-31 13:46                             ` Daniel Shahaf
2019-12-16 10:09                   ` Peter Stephenson
2019-12-16  5:27     ` The bug from workers/44922 (was: " Daniel Shahaf
2020-01-30 13:49       ` The bug from workers/44922 Martijn Dekker
2020-01-30 14:01     ` Bug with traps and exit Martijn Dekker
2020-01-31  4:29       ` Daniel Shahaf
2022-11-26  3:00       ` Bart Schaefer

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=46f2fc10-2f2c-88f1-e4e2-87196a39a37a@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).