From: John H Palmieri <John.H.Palmieri.2@nd.edu>
Subject: Re: delay when quitting digest
Date: 19 Feb 1999 13:42:53 -0500 [thread overview]
Message-ID: <yqkkyalus09e.fsf@nd.edu> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "19 Feb 1999 18:06:07 +0100"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> John H Palmieri <John.H.Palmieri.2@nd.edu> writes:
>
> > First, what's causing this delay?
>
> Try `(setq debug-on-quit t)' and then `C-g' while it's working.
I did this several times, just to check. Each time I hit C-g, the
backtrace looks like this (with variations in the regexp being
searched for):
re-search-forward("\\bmailto:\\([^ \n ]+\\)" nil t)
gnus-article-add-buttons()
gnus-treat-article(nil 1 1)
gnus-display-mime()
gnus-article-prepare-display()
gnus-article-prepare(1574 nil)
gnus-summary-display-article(1574 nil)
gnus-summary-select-article(nil force)
gnus-summary-show-article()
gnus-handle-ephemeral-exit((#<buffer *Summary nnml:mail.linux*> . article))
gnus-summary-exit()
call-interactively(gnus-summary-exit)
So I guess if I've just looked at a digest, I want it not to be
displayed in the Article buffer, so that it doesn't get "prepared" or
"treated" or something. So maybe I want to change the state of the
old summary buffer when leaving the ephemeral group?
By the way, there is also a delay of several seconds when entering a
digest. I'm talking about digests of at least 20 articles, totaling
at least 1000 lines. In this case, I get essentially the same
backtrace:
re-search-forward("\\bmailto:\\([^ \n ]+\\)" nil t)
gnus-article-add-buttons()
gnus-treat-article(nil 1 1)
gnus-display-mime()
gnus-article-prepare-display()
gnus-article-prepare(1574 nil)
gnus-summary-display-article(1574 nil)
gnus-summary-select-article()
gnus-summary-enter-digest-group(nil)
call-interactively(gnus-summary-enter-digest-group)
This may be unavoidable, and it may just be a consequence of a slow
computer, slow disk access, and long digests. Or is it avoidable? (I
guess I could unsubscribe from the mailing lists that send me the long
digests, but that wasn't what I had in mind...)
--
John H. Palmieri palmieri.2@nd.edu
I pretend I'm living in a styrofoam packing crate, high in th'
SWISS ALPS, still unable to accept th' idea of TOUCH-TONE DIALING!!
next prev parent reply other threads:[~1999-02-19 18:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-18 14:46 John H Palmieri
1999-02-19 17:06 ` Lars Magne Ingebrigtsen
1999-02-19 18:42 ` John H Palmieri [this message]
1999-02-19 18:49 ` Lars Magne Ingebrigtsen
1999-02-22 18:13 ` John H Palmieri
1999-02-26 7:47 ` Lars Magne Ingebrigtsen
1999-02-26 15:03 ` John H Palmieri
1999-02-26 16:13 ` Lars Magne Ingebrigtsen
1999-02-26 17:23 ` John H Palmieri
1999-02-26 18:05 ` Lars Magne Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yqkkyalus09e.fsf@nd.edu \
--to=john.h.palmieri.2@nd.edu \
/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.
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 NNTP newsgroup(s).