From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: why "in_sighandler"?
Date: Sun, 20 Aug 2006 14:22:47 -0400 [thread overview]
Message-ID: <87ejvbclsk.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <44E88FCA.5050705@swipnet.se> (Jan D.'s message of "Sun, 20 Aug 2006 18:37:30 +0200")
>> Could someone explain the difference between `handling_signal' and
>> `in_sighandler'? Depending on the answer I'm likely to suggest a renaming,
>> since it seems that either they are the same and should be merged or they
>> are different and should say so directly in their name.
>>
> handling_signal may be non-zero even if no signal handler is invoked.
> For example, from UNBLOCK_INPUT (via reinvoke_input_signal =>
> handle_async_input). Also if SYNC_INPUT is used. So handling_signal really
> means "handling X11/GUI event". I needed a variable that was only set when
> the signal handler is running. Maybe setting handling_signal is an error in
> the non-signalling cases, I don't really know.
Oh, I see, thanks.
Yes, the distinction is subtle. For what it's worth, I believe that
handling_signal shouldn't need to be set when handle_async_input is called
synchronously via reinvoke_input_signal. I.e. it should behave the same as
in_sighanlder ;-). But we shouldn't try such a change now, of course.
Stefan
next prev parent reply other threads:[~2006-08-20 18:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-20 6:51 why "in_sighandler"? Stefan Monnier
2006-08-20 16:37 ` Jan D.
2006-08-20 18:22 ` Stefan Monnier [this message]
2006-08-21 0:08 ` YAMAMOTO Mitsuharu
2006-08-21 6:18 ` Jan Djärv
2006-08-21 6:44 ` YAMAMOTO Mitsuharu
2006-08-21 7:19 ` Jan Djärv
2006-08-21 8:13 ` YAMAMOTO Mitsuharu
2006-08-21 8:46 ` Jan Djärv
2006-08-21 8:58 ` YAMAMOTO Mitsuharu
2006-08-21 11:32 ` Jan Djärv
2006-08-22 0:22 ` YAMAMOTO Mitsuharu
2006-08-22 6:38 ` Jan Djärv
2006-08-22 7:39 ` YAMAMOTO Mitsuharu
2006-08-22 8:23 ` Jan Djärv
2006-08-22 8:34 ` YAMAMOTO Mitsuharu
2006-08-22 18:00 ` Jan Djärv
2006-08-22 9:43 ` Andreas Schwab
2006-08-21 11:13 ` Richard Stallman
2006-08-21 12:55 ` Jan Djärv
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ejvbclsk.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).