From: John Sullivan <john@wjsullivan.net>
To: ding@gnus.org
Subject: Re: New messages marked O before seeing them
Date: Tue, 26 Apr 2011 11:39:48 -0400 [thread overview]
Message-ID: <87oc3t9g3f.fsf@myles.home.wjsullivan.net> (raw)
In-Reply-To: <8739l6q7x4.fsf@myles.home.wjsullivan.net>
John Sullivan <john@wjsullivan.net> writes:
> I have a sneaking suspicion that I may have solved this by setting
> (setq gnus-gcc-mark-as-read nil). It was t before, and my mails are
> GCC'd to the inbox.
>
> My suspicion is that somehow the wrong messages are being marked as
> read, targeting incoming mail instead of the Gcc'd mail just written.
>
> Since I've made that change, I have seen no more new messages marked
> read, despite receiving 1 a minute and using my inbox under
> approximately the same conditions as the ones which produced the
> negative effects before.
I'm quite sure at this point that the Gcc settings are the cause. So
excited to have traced this down!
I should have made this connection before, because I'd noticed that
sometimes, my Gcc'd messages were not getting marked as read, and I
thought that was weird.
Now to fix it :). Any background information about how Gcc works would
be helpful.
-john
next prev parent reply other threads:[~2011-04-26 15:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 17:04 John Sullivan
2011-03-15 15:32 ` Lars Magne Ingebrigtsen
2011-03-15 18:03 ` John Sullivan
2011-03-15 22:08 ` Lars Magne Ingebrigtsen
2011-03-16 4:13 ` John Sullivan
2011-03-17 17:47 ` Lars Magne Ingebrigtsen
2011-03-18 2:57 ` John Sullivan
2011-03-18 7:46 ` Glyn Millington
2011-03-18 15:41 ` John Sullivan
2011-03-18 16:20 ` Glyn Millington
2011-03-18 21:49 ` John Sullivan
2011-03-18 22:23 ` Glyn Millington
2011-04-25 19:04 ` John Sullivan
2011-04-25 22:32 ` John Sullivan
2011-04-26 15:39 ` John Sullivan [this message]
2011-05-01 14:56 ` Lars Magne Ingebrigtsen
2011-05-01 16:18 ` John Sullivan
2011-05-30 21:25 ` Lars Magne Ingebrigtsen
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=87oc3t9g3f.fsf@myles.home.wjsullivan.net \
--to=john@wjsullivan.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).