From: Carlos Pita <carlosjosepita@gmail.com>
To: info-gnus-english@gnu.org
Subject: Misbehaving gnus-gcc-mark-as-read while archiving to current group
Date: Tue, 05 Aug 2014 12:38:57 -0300 [thread overview]
Message-ID: <86fvhbkktq.fsf@gmail.com> (raw)
Hi all,
in order to get a "conversation view" a la gmail I've configured gnus as
follows:
(setq gnus-gcc-mark-as-read t)
(setq gnus-message-archive-group
(lambda (g)
(unless (string-match ":" g)
(concat "nnimap+gmail:" g))))
nnimap+gmail is my primary method so I check for lacking of ":" in the
group name (only groups for secondary methods contain a ":", at least in
my case). The generated gcc header is correct: say the group is
"micro2", the gcc will be "nnimap+gmail:micro2". That's fine.
But then there are a lot of quirks I'm not sure what to do about. Say I
reply a message in "micro2" group. My reply is indeed archived to
"micro2" but in the summaries buffer:
1. At first the sent reply is not shown at all.
2. If I press /N, then the reply is shown but as unread.
3. If I press M-g, then the reply is shown read.
In the imap server the behavior is as expected: the reply appears inside
the "micro2" folder and it's marked read. The problem is obviously with
the refreshing of the gnus views/state itself.
Is this a bug? In any case, it seems a very misleading behavior to me.
Cheers
--
Carlos
next reply other threads:[~2014-08-05 15:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 15:38 Carlos Pita [this message]
2014-08-05 22:41 ` Emanuel Berg
2014-08-12 16:28 ` Carlos Pita
2014-08-12 17:11 ` Emanuel Berg
2014-08-12 22:02 ` Carlos Pita
2014-08-12 22:25 ` Emanuel Berg
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=86fvhbkktq.fsf@gmail.com \
--to=carlosjosepita@gmail.com \
--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).