Gnus development mailing list
 help / color / mirror / Atom feed
From: Lloyd Zusman <ljz@asfast.com>
To: ding@gnus.org
Subject: Re: Automatically marking Gcc's as SEEN in nnimap
Date: Wed, 17 Dec 2008 19:57:22 -0500	[thread overview]
Message-ID: <m24p12cnbh.fsf@asfast.com> (raw)
In-Reply-To: <877i5zyw2o.fsf@gmail.com>

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.

Thanks, but I forgot to mention in my original post that I am already
using that variable and it is set to `t' ... and the Gcc'ed messages are
never being marked as SEEN.

Have you actually tested this setting within an nnimap group and an
nnimap Gcc, or are you just going by the docs?

Here's pertinent the code fragment in gnus-msg.el ...

  (when (and group-art
             ;; FIXME: Should gcc-mark-as-read work when
             ;; Gnus is not running?
             (gnus-alive-p)
             (or gnus-gcc-mark-as-read
                 (and
                  (boundp 'gnus-inews-mark-gcc-as-read)
                  (symbol-value 'gnus-inews-mark-gcc-as-read))))
    (gnus-group-mark-article-read group (cdr group-art)))

This fragment appears within the `gnus-inews-do-gcc' function, and there
is no other gnus code which tests the value of the variable
`gnus-gcc-mark-as-read'. Could it be that this variable only applies
when an inews-type function is being performed under nntp, and not under
any other back ends such as nnimap?

However, if this code indeed gets executed in all backends, then I
should point out that gnus is indeed alive when the Gcc is being
performed; therefore, `(gnus-alive-p)' definitely returns `t'. Maybe
`group-art' isn't set? Is there some other setting that controls how
that variable is set?

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 ... ???



-- 
 Lloyd Zusman
 ljz@asfast.com
 God bless you.




  reply	other threads:[~2008-12-18  0:57 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 [this message]
2008-12-18  2:22     ` Dave Goldberg
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=m24p12cnbh.fsf@asfast.com \
    --to=ljz@asfast.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).