From: Mario Peter <empee0@googlemail.com>
To: ding@gnus.org
Subject: Re: stale summary buffer after reading message
Date: Sun, 10 Oct 2010 23:19:29 +0200 [thread overview]
Message-ID: <AANLkTim7n9opECPBC9-2uDV6bF7tgbUOHwRRk2g9Jpbw@mail.gmail.com> (raw)
In-Reply-To: <m3sk0f5oy4.fsf@quimbies.gnus.org>
2010/10/9 Lars Magne Ingebrigtsen <larsi@gnus.org>:
> Mario Peter <empee0@googlemail.com> writes:
>
>> when I close a summary buffer after reading a message, gnus leaves an
>> empty, writable summary buffer, which gets reused when selecting and
>> re-entering the group again.
>
> Do you have `gnus-kill-summary-on-exit' set to nil?
no, gnus-kill-summary-on-exit is t
Mario
next prev parent reply other threads:[~2010-10-10 21:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 22:50 Mario Peter
2010-10-09 16:08 ` Lars Magne Ingebrigtsen
2010-10-10 21:19 ` Mario Peter [this message]
2010-10-11 18:02 ` Lars Magne Ingebrigtsen
2010-10-31 22:10 ` Mario Peter
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=AANLkTim7n9opECPBC9-2uDV6bF7tgbUOHwRRk2g9Jpbw@mail.gmail.com \
--to=empee0@googlemail.com \
--cc=ding@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).