From: "Eli Zaretskii" <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: When is hourglass shown?
Date: Sat, 05 Mar 2005 19:24:15 +0200 [thread overview]
Message-ID: <01c521a8$Blat.v2.4$4d2acc80@zahav.net.il> (raw)
In-Reply-To: <e403a5c5e1bd9f3ee2789a60428371b2@swipnet.se> (jan.h.d@swipnet.se)
> Cc: emacs-devel@gnu.org
> From: "Jan D." <jan.h.d@swipnet.se>
> Date: Sat, 5 Mar 2005 12:17:24 +0100
>
> > I think the easiest way to find out whether the hourglass could be
> > shown in the context of some function is to put a breakpoint on the
> > place where the hourglass timer is set up. Then you will know if
> > Emacs arranges for the hourglass even if the operation itself is fast
> > enough so that no hourglass is actually shown before it finishes.
> >
> > (It might be necessary to change the default handling of SIGALRM by
> > GDB, in order to run this under GDB.)
>
> This does not always work, as in the case of M-x indent-region versus
> C-M-\. Both starts the hourglass timer, but the first stops it
> directly afterwards.
Actually, I think it did work very well: it shows you that the
hourglass was armed, i.e. that Emacs _meant_ for it to appear if the
operation took enough time. If you want to know why it didn't
actually happen, an additional breakpoint where the timer is disabled
would have shown you the code which did that.
next prev parent reply other threads:[~2005-03-05 17:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-04 17:34 When is hourglass shown? Jan D.
2005-03-04 19:33 ` Stefan Monnier
2005-03-04 20:30 ` Jan D.
2005-03-05 10:51 ` Eli Zaretskii
2005-03-05 10:45 ` Eli Zaretskii
2005-03-05 11:17 ` Jan D.
2005-03-05 12:00 ` Lennart Borgman
2005-03-05 12:38 ` Jan D.
2005-03-06 0:41 ` Richard Stallman
2005-03-10 19:10 ` Jan D.
2005-03-05 15:11 ` Jason Rumney
2005-03-05 17:24 ` Eli Zaretskii [this message]
2005-03-05 18:18 ` Jan D.
2005-03-05 20:11 ` Nick Roberts
-- strict thread matches above, loose matches on Subject: below --
2005-03-02 16:05 Lennart Borgman
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='01c521a8$Blat.v2.4$4d2acc80@zahav.net.il' \
--to=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 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).