Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Frank Schmitt <ich@frank-schmitt.net>
To: info-gnus-english@gnu.org
Subject: Re: Remembering read mail
Date: Fri, 11 Jun 2010 13:35:13 +0200	[thread overview]
Message-ID: <m3typ994zy.fsf@mid.gehheimdienst.de> (raw)
In-Reply-To: <87d3vxzx73.fsf@ericabrahamsen.net>

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> One thing stopping me is the article summary list. I'm finding it very
> confusing to look at, largely because the "read" status of messages is
> not remembered between Gnus invocations. Every time I open the group all
> the messages are unmarked. As I read them they turn bright blue-green
> and get a "R" in the margin. Next time I open the group they're all
> unmarked again.

That shouldn't happen. Normally, the next time you enter the group, all
previously read message should be hidden and the information, that they
have been read remembered.

Could it be, that you exit Gnus by just closing the Emacs window instead
of shutting down Gnus with the 'q'-Key in summary buffer? In this case
it might happen, that Gnus doesn't write to disk and loses all information...

-- 
Have you ever considered how much text can fit in eighty columns?  Given that a
signature typically contains up to four lines of text, this space allows you to
attach a tremendous amount of valuable information to your messages.  Seize the
opportunity and don't waste your signature on bullshit that nobody cares about.

  parent reply	other threads:[~2010-06-11 11:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-11 10:21 Eric Abrahamsen
2010-06-11 11:20 ` Tim Landscheidt
2010-06-11 11:35 ` Frank Schmitt [this message]
2010-06-11 17:57   ` Eric Abrahamsen

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=m3typ994zy.fsf@mid.gehheimdienst.de \
    --to=ich@frank-schmitt.net \
    --cc=info-gnus-english@gnu.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).