From: John H Palmieri <John.H.Palmieri.2@nd.edu>
Subject: Re: delay when quitting digest
Date: 26 Feb 1999 10:03:15 -0500 [thread overview]
Message-ID: <yqkkbtih437w.fsf@nd.edu> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "26 Feb 1999 08:47:09 +0100"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> John H Palmieri <John.H.Palmieri.2@nd.edu> writes:
>
> > What's the easiest way to avoid this delay? What can I add to which
> > hook so that when I leave the digest, the *Article* buffer associated
> > to the parent *Summary* buffer is deleted, so that the article is
> > never treated for buttons or anything else? Or should I take some
> > other approach?
>
> When leaving an nndoc group, Gnus tries to go to the next article, and
> if there is no next article, it reselects the current one...
But this only seems to be true if there was an article selected before
entering the nndoc group. (I have gnus-auto-select-first set to nil,
in case that makes a difference.) If I don't select any articles, but
go straight to the nndoc group with C-d, then when I quit the nndoc
group, it doesn't select the next article. How do I get this behavior
even if I have read an article before entering the nndoc group?
Select an article, enter the nndoc group, leave the nndoc group -->
long delay when leaving the nndoc group (because it's buttonizing
the long article containing the digest)
Don't select any articles (just enter the mail group from the Group
buffer with SPC, with gnus-auto-select-first set to nil), enter the
nndoc group, leave the nndoc group --> no delay, because it's not
selecting and buttonizing any article.
[I feel thoroughly confused, so pardon me if I'm asking the same thing
over and over again...]
--
John H. Palmieri
e-mail: palmieri.2@nd.edu 205 Computing/Math Bldg.
URL:http://www.nd.edu/~jpalmier/ University of Notre Dame
(219) 631-8846 Notre Dame, IN 46556
next prev parent reply other threads:[~1999-02-26 15:03 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
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 [this message]
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=yqkkbtih437w.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).