From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: What made ticked/unread articles becomes OLD ?!
Date: 24 Apr 1997 13:58:01 +0200 [thread overview]
Message-ID: <m2rag0y6nq.fsf@proletcult.slip.ifi.uio.no> (raw)
In-Reply-To: Danny Siu's message of 21 Apr 1997 15:55:00 -0700
Danny Siu <dsiu@Adobe.COM> writes:
> In my mail folder named "Active" (using nnfolder backend), after I do 'g' in
> the summary buffer,
You mean the group buffer?
> all of the sudden all unread (no mark) and ticked ("!") articles
> becomes old ("O") and hence hidden in the summary buffer! C-u ret
> in that reveals that articles that I ticked and articles with no
> marks has been magically marked old. This doesn't happen every time
> I get mail, though, but it happens like once a month. Does anyone
> know can this happen?
I've never had any reports of this happening with nnfolder groups, and
it sounds rather odd. Hm. Uhm. Nope, I can't think of anything that
would make ticks be wiped out by `g'. Are you sure that's the command
that does it?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1997-04-24 11:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-04-21 22:55 Danny Siu
1997-04-24 11:58 ` Lars Magne Ingebrigtsen [this message]
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=m2rag0y6nq.fsf@proletcult.slip.ifi.uio.no \
--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).