From: romeomedina@libero.it
Subject: Re: Expiration mark 'E' disappearing
Date: 20 Sep 2005 13:39:20 -0700 [thread overview]
Message-ID: <1127248760.807395.260180@g44g2000cwa.googlegroups.com> (raw)
In-Reply-To: <1127226873.986246.101870@g47g2000cwa.googlegroups.com>
Now I installed emacs CVS 22.0.50.1, and the bug
(if a bug it was) seems to be worked out:
in the summary buffer I mark a message with 'E', then get back
to the group buffer with 'q', then get back again into the
summary buffer and the 'E' mark is still there, on the message.
But:
if I quit gnus, and then start gnus again, the 'E' is not there
any more!
Is that normal? It seems strange to me: a message marked as
expirable should remain so until it is deleted or until I change
my mind and want to restore it again.
Any idea?
Thanks,
Rodolfo
next prev parent reply other threads:[~2005-09-20 20:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-20 13:41 romeomedina
2005-09-20 13:46 ` David Kastrup
2005-09-20 14:34 ` romeomedina
2005-09-20 20:39 ` romeomedina [this message]
2005-09-24 16:56 ` romeomedina
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=1127248760.807395.260180@g44g2000cwa.googlegroups.com \
--to=romeomedina@libero.it \
/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).