From: Richard Stallman <rms@gnu.org>
Cc: mituharu@math.s.chiba-u.ac.jp, emacs-devel@gnu.org
Subject: Re: alarm_signal_handler is called too frequently
Date: Sun, 31 Oct 2004 04:42:27 -0500 [thread overview]
Message-ID: <E1COCEF-0002ON-1f@fencepost.gnu.org> (raw)
In-Reply-To: <41813425.2010001@swipnet.se> (jan.h.d@swipnet.se)
The BLOCK/UNBLOCK_INPUT is needed for the GTK version. This was discussed here
http://lists.gnu.org/archive/html/emacs-pretest-bug/2004-05/msg00155.html
The solution proposed was to do as the menu code does, first build the
structures from Lisp code, then update the GUI. Only the second stage needs to
block input. Unfortunately this has not been done yet (on my todo list).
So the cause is a real bug, albeit not one unknown.
When do you think you'll be able to do make this change?
We need it before the release. (I will add it to FOR-RELEASE.)
next prev parent reply other threads:[~2004-10-31 9:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 1:15 alarm_signal_handler is called too frequently YAMAMOTO Mitsuharu
2004-10-13 14:43 ` Richard Stallman
2004-10-14 5:16 ` YAMAMOTO Mitsuharu
2004-10-17 9:36 ` YAMAMOTO Mitsuharu
2004-10-25 13:13 ` Richard Stallman
2004-10-25 14:38 ` Jan D.
2004-10-27 10:47 ` Richard Stallman
2004-10-28 18:02 ` Jan D.
2004-10-29 1:37 ` YAMAMOTO Mitsuharu
2004-10-29 7:00 ` Jan D.
2004-10-29 8:24 ` YAMAMOTO Mitsuharu
2004-11-01 7:24 ` Richard Stallman
2004-11-01 9:06 ` Jan D.
2004-11-01 12:21 ` Jan D.
2004-11-02 14:08 ` Richard Stallman
2004-11-02 21:56 ` Jan D.
2004-11-03 17:04 ` Richard Stallman
2004-11-03 17:26 ` Jan D.
2004-11-04 20:42 ` Richard Stallman
2004-11-04 22:41 ` Jan D.
2004-11-05 12:36 ` Kim F. Storm
2004-11-06 5:22 ` Richard Stallman
2004-11-04 13:02 ` Jan D.
2004-10-31 9:42 ` Richard Stallman [this message]
2004-10-31 15:11 ` Jan D.
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=E1COCEF-0002ON-1f@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mituharu@math.s.chiba-u.ac.jp \
/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).