From: "Jan D." <jan.h.d@swipnet.se>
Cc: mituharu@math.s.chiba-u.ac.jp, emacs-devel@gnu.org
Subject: Re: alarm_signal_handler is called too frequently
Date: Tue, 02 Nov 2004 22:56:24 +0100 [thread overview]
Message-ID: <41880288.2070706@swipnet.se> (raw)
In-Reply-To: <E1COzLD-0007tm-V8@fencepost.gnu.org>
Richard Stallman wrote:
> I can't say why the do_timer argument is different, the modification was made
> by you almost 2 years ago:
>
> Judging by the date when I made the change, I was probably looking at
> bug reports saved up from the previous months. I didn't mail the
> patch to anyone at the time.
>
> Perhaps it has to do with y-or-n-p-with-timeout.
> Can that operate with a dialog? If so, it now won't work
> correctly; the timeout will be ignored. We could make
> the timeout work once again using some other mechanism,
> I guess.
y-or-n-p-with-timeout will pop up a dialog when invoked with the mouse (i.e.
tool or menu bar). And yes, it will not time out. It never did for GTK or Mac
OSX BTW, as they do not process timers if a dialog is popped up.
Currently there are no such menu or tool bar entries, but I guess other
packages may add such an item.
But I was wondering if the differences in how dialogs and menus are invoked may
make a difference. A menu is invoked as a result of a KeyPress, which arrives
in the signal handler. But a dialog is always popped up by lisp code, not
directly from the signal handler. Does this matter?
Jan D.
next prev parent reply other threads:[~2004-11-02 21:56 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. [this message]
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
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=41880288.2070706@swipnet.se \
--to=jan.h.d@swipnet.se \
--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).