From: Dan Davison <davison@stats.ox.ac.uk>
To: <ding@gnus.org>
Subject: Re: missing gnus-unseen-mark
Date: Wed, 01 Jul 2009 11:32:53 -0400 [thread overview]
Message-ID: <87bpo4v2oq.fsf@stats.ox.ac.uk> (raw)
In-Reply-To: <878wkjdi8t.fsf@stats.ox.ac.uk> (Dan Davison's message of "Tue, 26 May 2009 10:57:38 -0400")
This remains a problem for me: if I enter a group, and then leave it
without reading every new message (marked 'N'), and then re-enter, the
unread messages have no mark to differentiate them from read messages,
leading to missed mail. Can anyone suggest which aspects of my setup I
should review in order to get persistent marking of unread messages?
[nnimap with dovecot serving local maildirs populated by getmail]
Thanks a lot,
Dan
Dan Davison <davison@stats.ox.ac.uk> writes:
> I'm using dovecot with nnimap and local maildirs.
>
> I'd like a mark to remain by messages in the summary buffer until I have
> actually read them (presumably that would be gnus-unseen-mark). When I
> enter a group, new messages have the 'N' mark (gnus-recent-mark) in the
> summary buffer. If I leave that group (without reading anything) and
> then re-enter, the 'N' mark has disappeared and is (often) not replaced
> by any mark. Actually I do sometimes get the '.' mark which aIui is
> gnus-unseen-mark, but by no means always.
>
> What should I do in order to reliably get a persistent gnus-unseen-mark
> next to messages until I have read them?
>
> Thanks a lot,
>
> Dan
>
> Here's one possibly relevant variable setting:
>
> (setq gnus-summary-line-format
> (concat
> "%0{%U%R%z%}"
> "%3{│%}" "%1{%d%}" "%3{│%}" ;; date
> " "
> "%4{%-20,20f%}" ;; name
> " "
> "%3{│%}"
> " "
> "%1{%B%}"
> "%s\n"))
prev parent reply other threads:[~2009-07-01 15:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-26 14:57 Dan Davison
2009-07-01 15:32 ` Dan Davison [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=87bpo4v2oq.fsf@stats.ox.ac.uk \
--to=davison@stats.ox.ac.uk \
--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).