From: Alain Schneble <a.s@realize.ch>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Revise etc/DEBUG documentation
Date: Tue, 6 Sep 2016 18:14:42 +0200 [thread overview]
Message-ID: <8660q9ronh.fsf@realize.ch> (raw)
In-Reply-To: <83h99tawid.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 06 Sep 2016 18:16:58 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> But in that case, this is expected behavior: the SIGINT handler just
> sets a flag and returns; the flag is then processed whenever the Emacs
> event loop cranks one more cycle. This is not specific to MS-Windows.
> In an idle "emacs -Q", you might indeed see a difference between
> Windows and Posix systems, because on the latter pselect will be
> interrupted by SIGINT.
Exactly. This was the unexpected behavior I was referring to.
> But that is not a very interesting use case
> for shutting down Emacs with SIGINT. A real-life Emacs session has
> several timers running, which typically make pselect waits shorter,
> and if Emacs is in the middle of some prolonged computation, you will
> see a delay on Posix platforms as well.
Indeed.
> IOW, Emacs behaves here as expected, on Windows and elsewhere.
I looked at it as a white box, and this was not what /I/ expected. From
a users point of view and when looking at real cases, it doesn't really
matter, I agree.
>> This potential delay is a minor detail. But couldn't we overcome it by
>> pulsing the interrupt_handle event, e.g. by a call to signal_quit in
>> keyboard.c (handle_interrupt_signal), just after having set the
>> Vquit_flag? Of course, that would be for MS Windows only.
>
> I see no reason, see above. In any case, I'd advise against doing
> anything non-trivial in the SIGINT handler, on Windows in particular,
> because Windows runs such handlers in a separate thread, so it's
> unsafe to do there anything non-trivial -- we could easily crash,
> because we are on the wrong stack.
Ok, sure. (Even though I don't think that PulseEvent would do any hurt
here...)
Thanks for your explanations.
next prev parent reply other threads:[~2016-09-06 16:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-03 10:31 Revise etc/DEBUG documentation Alain Schneble
2016-09-03 11:31 ` Eli Zaretskii
2016-09-03 13:14 ` Alain Schneble
2016-09-03 13:45 ` Noam Postavsky
2016-09-03 14:35 ` Eli Zaretskii
2016-09-03 21:56 ` Alain Schneble
2016-09-03 14:34 ` Eli Zaretskii
2016-09-03 15:05 ` Noam Postavsky
2016-09-03 15:27 ` Eli Zaretskii
2016-09-03 21:51 ` Alain Schneble
2016-09-04 14:42 ` Eli Zaretskii
2016-09-04 16:24 ` Alain Schneble
2016-09-05 16:36 ` Eli Zaretskii
2016-09-05 17:00 ` Eli Zaretskii
2016-09-05 19:19 ` Alain Schneble
2016-09-05 19:35 ` Alain Schneble
2016-09-06 2:39 ` Eli Zaretskii
2016-09-06 10:06 ` Alain Schneble
2016-09-06 15:16 ` Eli Zaretskii
2016-09-06 16:14 ` Alain Schneble [this message]
2016-09-06 16:54 ` Alain Schneble
2016-09-06 21:52 ` Davis Herring
2016-09-07 17:39 ` Eli Zaretskii
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=8660q9ronh.fsf@realize.ch \
--to=a.s@realize.ch \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.