From: Emanuel Berg <embe8573@student.uu.se>
To: info-gnus-english@gnu.org
Subject: Re: Mark own message automatically as read
Date: Tue, 22 Apr 2014 23:29:10 +0200 [thread overview]
Message-ID: <871twpcau1.fsf@nl106-137-194.student.uu.se> (raw)
In-Reply-To: <mailman.20046.1398178711.10748.info-gnus-english@gnu.org>
asjo@koldfront.dk (Adam Sjøgren) writes:
> (setq gnus-gcc-mark-as-read t)
The documentation says:
"If non-nil, automatically mark Gcc articles as read."
To me, it sounds like all Gcc'd messages will be marked
as read. But even so, people very seldom use the Gcc
header anyway - or so it would seem.
I will definitely try this, because I have the same
problem as the OP. I sort of solved it by putting
*myself* in the KILL file, but that doesn't solve the
problem the OP mentions (or sort of) that this only
applies when I *enter* a group - optimally, I would
like all my "kills" applied transparently so I never
hear about them...
--
underground experts united:
http://user.it.uu.se/~embe8573
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2014-04-22 21:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 13:52 Igor Sosa Mayor
2014-04-22 14:58 ` Adam Sjøgren
2014-04-22 21:33 ` Igor Sosa Mayor
2014-04-23 8:07 ` Adam Sjøgren
[not found] ` <mailman.20095.1398240620.10748.info-gnus-english@gnu.org>
2014-04-23 21:45 ` Emanuel Berg
2014-04-25 8:04 ` Igor Sosa Mayor
[not found] ` <mailman.51.1398413107.1147.info-gnus-english@gnu.org>
2014-04-25 15:58 ` Emanuel Berg
[not found] ` <mailman.20046.1398178711.10748.info-gnus-english@gnu.org>
2014-04-22 21:29 ` Emanuel Berg [this message]
2014-04-22 21:34 ` Igor Sosa Mayor
2014-04-23 8:04 ` Adam Sjøgren
2014-04-23 9:16 ` Damien Wyart
2014-04-23 10:17 ` Adam Sjøgren
[not found] ` <mailman.20093.1398240314.10748.info-gnus-english@gnu.org>
2014-04-23 21:42 ` Emanuel Berg
2014-04-24 15:59 ` Adam Sjøgren
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=871twpcau1.fsf@nl106-137-194.student.uu.se \
--to=embe8573@student.uu.se \
--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).