From: Dave Goldberg <david.goldberg6@verizon.net>
To: ding@gnus.org
Subject: Re: Automatically marking Gcc's as SEEN in nnimap
Date: Wed, 17 Dec 2008 21:22:33 -0500 [thread overview]
Message-ID: <84ljuecjdi.fsf@incoming.verizon.net> (raw)
In-Reply-To: <m24p12cnbh.fsf@asfast.com> (Lloyd Zusman's message of "Wed, 17 Dec 2008 19:57:22 -0500")
>>>>> On Wed, 17 Dec 2008 19:57:22 -0500, Lloyd Zusman <ljz@asfast.com> said:
> Paul R <paul.r.ml@gmail.com> writes:
>> M-x apropos-variable RET gnus.*gcc.*read RET
>>
>> gnus-gcc-mark-as-read
>> Variable: If non-nil, automatically mark Gcc articles as read.
> Have you actually tested this setting within an nnimap group and an
> nnimap Gcc, or are you just going by the docs?
I have. I use nnimap exclusively at work (meaning no other backends,
not that I run Gnus only at work and not at home :-) and my gcc's are
always marked read when I next enter the gcc'd group.
> Or perhaps the problem is related to nnimap. Maybe marking the messages
> as "read" in gnus isn't the same as marking them as "SEEN" in IMAP. Or
> maybe there is some other problem ... ???
My gcc's are certainly marked "read" but they are not marked "seen".
If I do a `/ .' (gnus-summary-limit-to-unseen) in the group, my gcc
shows up with the other new messages. So there is a difference
between "read" and "seen".
--
Dave Goldberg
david.goldberg6@verizon.net
next prev parent reply other threads:[~2008-12-18 2:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-17 2:29 Lloyd Zusman
2008-12-17 9:45 ` Paul R
2008-12-18 0:57 ` Lloyd Zusman
2008-12-18 2:22 ` Dave Goldberg [this message]
2008-12-18 3:20 ` Lloyd Zusman
2008-12-26 19:27 ` Lloyd Zusman
2009-01-03 17:21 ` David Engster
2009-01-03 20:19 ` Lloyd Zusman
2009-01-03 23:15 ` David Engster
2009-01-04 20:14 ` Lloyd Zusman
2009-01-04 21:21 ` David Engster
2009-01-04 22:30 ` Lloyd Zusman
2009-01-04 23:57 ` David Engster
2009-01-05 1:40 ` Lloyd Zusman
2009-01-05 11:25 ` David Engster
2009-01-06 2:32 ` Lloyd Zusman
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=84ljuecjdi.fsf@incoming.verizon.net \
--to=david.goldberg6@verizon.net \
--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).