From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: delay when quitting digest
Date: 26 Feb 1999 08:47:09 +0100 [thread overview]
Message-ID: <m37lt5fvya.fsf@quimbies.gnus.org> (raw)
In-Reply-To: John H Palmieri's message of "22 Feb 1999 13:13:35 -0500"
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...
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1999-02-26 7:47 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 [this message]
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=m37lt5fvya.fsf@quimbies.gnus.org \
--to=larsi@gnus.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.
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).