Gnus development mailing list
 help / color / mirror / Atom feed
From: John H Palmieri <John.H.Palmieri.2@nd.edu>
Subject: delay when quitting digest
Date: 18 Feb 1999 09:46:43 -0500	[thread overview]
Message-ID: <yqkkaeybbwh8.fsf@nd.edu> (raw)

Pterodactyl Gnus v0.76, GNU Emacs 20.3.1 (sparc-sun-solaris2.5.1, X
toolkit) of Thu Aug 27 1998 on darwin

Admittedly, my computer is slow in general, but depending on the
circumstances, there is a noticeable delay when quitting digests.
Here's the situation:

Background: I have gnus-auto-select-first set to nil in
gnus-select-group-hook, so I don't automatically get an *Article*
buffer when I enter a group.

Case 1: I enter a mail group which contains a digest, then go to the
digest and hit `C-d' to look at it.  Then when I hit `q', I return to
the *Summary* buffer almost instantaneously.

Case 2: I enter a mail group which contains a digest, read a
non-digest article first (so there is an *Article* buffer around),
then go to the digest and hit `C-d' to look at it.  Then when I hit
`q', there is a delay (perhaps several seconds--the length depends on
the size of the digest), and then I return to the *Summary* buffer,
which now shows the digest in a single *Article* buffer.

First, what's causing this delay?  Probably reading the article from
disk and parsing it for highlighting, etc.

Is there a hook I can set to fix this (maybe so that when I enter or
leave a digest, the *Article* buffer associated to the parent
*Summary* buffer is deleted, or maybe to turn off article highlighting
just for digests)?  Or is there some other fix?  Is there a good
reason to automatically display the digest in an *Article* buffer
after having read it as a digest, or when quitting a digest should the
default be to just go to the *Summary* buffer?

-- 
John H. Palmieri                       e-mail: palmieri.2@nd.edu
$400 million in gold bullion Honduras Ft. Bragg genetic assassination
CIA KGB supercomputer Semtex quiche plutonium counter-intelligence
class struggle smuggle FBI


             reply	other threads:[~1999-02-18 14:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-18 14:46 John H Palmieri [this message]
1999-02-19 17:06 ` Lars Magne Ingebrigtsen
1999-02-19 18:42   ` John H Palmieri
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=yqkkaeybbwh8.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).