From: Robert Pluim <rpluim@gmail.com>
To: ding@gnus.org
Subject: Re: sent as read
Date: Wed, 15 Dec 2010 12:37:49 +0100 [thread overview]
Message-ID: <pknpqt3z2pb.fsf@invalid.com> (raw)
In-Reply-To: <okd3p3l4pi.fsf@news.eternal-september.org>
Richard Riley <rileyrg@googlemail.com> writes:
> Using nnimap, my "sent" are appearing as unread. Is there a gnus way to
> either turn off the message count for a group or a cleverer way to mark
> sent as read? I quick google showed all sorts of differing opinions so
> I thought I'd see if there is a built in way. I realise I can hide the
> group completely. I guess I could score myself down too. Other ways?
I guess it depends on how you're putting things in "sent". If using gcc:
`gnus-gcc-mark-as-read' is a variable declared in Lisp.
-- loaded from "gnus-msg"
Value: nil
Documentation:
If non-nil, automatically mark Gcc articles as read.
(I have not tested it with nnimap)
Robert
next prev parent reply other threads:[~2010-12-15 11:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 10:18 Richard Riley
2010-12-15 11:37 ` Robert Pluim [this message]
2010-12-15 11:48 ` Richard Riley
2010-12-15 11:52 ` Dave Goldberg
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=pknpqt3z2pb.fsf@invalid.com \
--to=rpluim@gmail.com \
--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).