From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org, storm@cua.dk
Subject: Re: usr1-signal, usr2-signal, etc.
Date: Tue, 05 Dec 2006 19:46:38 -0500 [thread overview]
Message-ID: <E1Grkvm-0004y9-7T@fencepost.gnu.org> (raw)
In-Reply-To: <wlejrfovsc.wl%mituharu@math.s.chiba-u.ac.jp> (message from YAMAMOTO Mitsuharu on Tue, 05 Dec 2006 12:40:03 +0900)
I'm concerned about the case that kbd_buffer_store_event_hold is
called from the signal-handler context while it is also executed in
the normal context. This has already existed for SIGUSR1 and SIGUSR2
before your change, though.
Since people hardly ever use SIGUSR1 and SIGUSR2,
a bug that happens only a small fraction of the time when they
are called might never have happened. But if it happens for
signals that are more common, it will start to occur.
So it is good that you noticed this.
We should fix it now.
next prev parent reply other threads:[~2006-12-06 0:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-03 1:39 usr1-signal, usr2-signal, etc Kim F. Storm
2006-12-04 5:15 ` Richard Stallman
2006-12-04 9:05 ` Kim F. Storm
2006-12-04 13:08 ` Kim F. Storm
2006-12-05 1:45 ` Richard Stallman
2006-12-05 3:40 ` YAMAMOTO Mitsuharu
2006-12-05 22:26 ` David Kastrup
2006-12-05 22:51 ` Kim F. Storm
2006-12-08 10:28 ` YAMAMOTO Mitsuharu
2006-12-11 9:41 ` Kim F. Storm
2006-12-11 14:31 ` YAMAMOTO Mitsuharu
2006-12-12 9:47 ` Kim F. Storm
2006-12-12 13:32 ` YAMAMOTO Mitsuharu
2006-12-12 13:54 ` Kim F. Storm
2006-12-13 9:38 ` YAMAMOTO Mitsuharu
2006-12-13 10:26 ` Kim F. Storm
2006-12-14 9:14 ` YAMAMOTO Mitsuharu
2006-12-14 11:23 ` Kim F. Storm
2006-12-18 16:38 ` Chong Yidong
2006-12-19 2:14 ` YAMAMOTO Mitsuharu
2006-12-19 9:48 ` Kim F. Storm
2006-12-19 15:46 ` Kim F. Storm
2006-12-20 13:01 ` Richard Stallman
2006-12-20 15:58 ` Kim F. Storm
2006-12-12 21:46 ` Richard Stallman
2006-12-06 0:46 ` Richard Stallman [this message]
2006-12-06 9:44 ` Johan Bockgård
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=E1Grkvm-0004y9-7T@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=storm@cua.dk \
/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).