Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: unmarking in *Dead Summary* forgotten
Date: Mon, 24 Nov 2008 09:26:48 -0600	[thread overview]
Message-ID: <86wsetta9z.fsf@lifelogs.com> (raw)
In-Reply-To: <87ej13vgy7.fsf@jidanni.org>

On Sun, 23 Nov 2008 00:55:12 +0800 jidanni@jidanni.org wrote: 

j> Mark a message as read, quit that group, then go do the
j> *Dead Summary...* buffer, and unmark it:
j> g <return> d q C-x b * D e <tab> <return> C-p <escape> u q
j> You'll find your unmarking was not remembered by gnus.
j> gnus-version "Gnus v5.11"

Why would Gnus want to remember what you do in a dead summary buffer?

It seems to me like the right approach is to disable article operations
in this buffer, maybe by disconnecting it from the active backend and
mapping it to a special nnreadonly backend.

Ted




  reply	other threads:[~2008-11-24 15:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-22 16:55 jidanni
2008-11-24 15:26 ` Ted Zlatanov [this message]
2008-11-24 18:03   ` Reiner Steib
2008-11-25  3:12     ` jidanni
2008-11-25 17:25       ` Ted Zlatanov

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=86wsetta9z.fsf@lifelogs.com \
    --to=tzz@lifelogs.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).