From: Stefan Kamphausen <skampi@gmx.net>
To: help-gnu-emacs@gnu.org
Subject: Re: Gnus with Emacs 23: gnus-gcc-mark-as-read not working anymore
Date: Tue, 06 Oct 2009 13:24:23 +0200 [thread overview]
Message-ID: <87zl84ojdk.fsf@usenet.my.skamphausen.de> (raw)
In-Reply-To: mailman.8078.1254756146.2239.help-gnu-emacs@gnu.org
Hi David,
David Engster <deng@randomsample.de> writes:
> It seems Gnus did not notice yet that a new mail is in in
> mail.2009-10. Since I cannot reproduce this, I don't know why that
> happens. You mentioned that you're using the agent; maybe that's the
> cause of this issue.
I'm not doing so consciously, I never fiddled with any agent
settings. The only setting concerning Gnus agent I have in my
configuration is
(setq gnus-agent-enable-expiration 'DISABLE)
> If you want to further debug this, the best place to start is
> gnus-inews-do-gcc, where the actual sending happens with the call to
> gnus-request-accept-article here:
> (when (or (not (gnus-check-backend-function
> 'request-accept-article group))
> (not (setq group-art
> (gnus-request-accept-article
> group method t t))))
> (gnus-message 1 "Couldn't store article in group %s: %s"
> group (gnus-status-message method)))
I always looked a little bit further down the code:
(when (and (listp method)
(gnus-native-method-p method))
(setq group (gnus-group-short-name group)))
(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)))
And when I change
(setq group (gnus-group-short-name group)))
to just
(setq group group))
(for the moment) everything works as expected.
I tried to trace the functions
* gnus-group-mark-article-read
* gnus-mark-article-as-read
* gnus-group-make-articles-read
with the following result:
;; the following call DID NOT work as expected
======================================================================
1 -> gnus-group-mark-article-read: group="mail.office.all" article=31891
| 2 -> gnus-group-make-articles-read: group="mail.office.all" articles=(31891)
| 2 <- gnus-group-make-articles-read: nil
1 <- gnus-group-mark-article-read: nil
======================================================================
1 -> gnus-group-mark-article-read: group="mail.2009-10" article=65
| 2 -> gnus-group-make-articles-read: group="mail.2009-10" articles=(65)
| 2 <- gnus-group-make-articles-read: nil
1 <- gnus-group-mark-article-read: nil
;; the following call DID work as expected
======================================================================
1 -> gnus-group-mark-article-read: group="nnml:mail.office.all" article=31892
| 2 -> gnus-group-make-articles-read: group="nnml:mail.office.all" articles=(31892)
| 2 <- gnus-group-make-articles-read: #<buffer *acc*>
1 <- gnus-group-mark-article-read: nil
======================================================================
1 -> gnus-group-mark-article-read: group="nnml:mail.2009-10" article=66
| 2 -> gnus-group-make-articles-read: group="nnml:mail.2009-10" articles=(66)
| 2 <- gnus-group-make-articles-read: #<buffer *acc*>
1 <- gnus-group-mark-article-read: nil
> (gnus-request-group group nil method)
>
> after the sending will force Gnus to update the active information. I'm
> not sure.
Hm, I changed that part of gnus-inews-do-gcc to read
(when (or (not (gnus-check-backend-function
'request-accept-article group))
(not (setq group-art
(gnus-request-accept-article
group method t t))))
(gnus-message 1 "Couldn't store article in group %s: %s"
group (gnus-status-message method)))
(gnus-request-group group nil method)
and it doesn't help.
I think, I'll have to live with my own version of gnus-inews-do-gcc
which does not use the short name of the group. At least, *I* do not
see anything that I could do to examine this any further.
Thanks and kind regards,
Stefan
--
Stefan Kamphausen --- http://www.skamphausen.de
a blessed +42 regexp of confusion (weapon in hand)
You hit. The format string crumbles and turns to dust.
prev parent reply other threads:[~2009-10-06 11:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-21 8:06 Gnus with Emacs 23: gnus-gcc-mark-as-read not working anymore Stefan Kamphausen
2009-09-22 7:49 ` Stefan Kamphausen
2009-09-28 15:50 ` Stefan Kamphausen
2009-09-28 18:25 ` David Engster
[not found] ` <mailman.7657.1254162498.2239.help-gnu-emacs@gnu.org>
2009-09-29 11:28 ` Stefan Kamphausen
2009-09-29 12:00 ` David Engster
[not found] ` <mailman.7691.1254225675.2239.help-gnu-emacs@gnu.org>
2009-09-29 13:22 ` Stefan Kamphausen
2009-09-29 21:33 ` David Engster
[not found] ` <mailman.7717.1254260069.2239.help-gnu-emacs@gnu.org>
2009-10-02 14:53 ` Stefan Kamphausen
2009-10-05 15:14 ` David Engster
[not found] ` <mailman.8078.1254756146.2239.help-gnu-emacs@gnu.org>
2009-10-06 11:24 ` Stefan Kamphausen [this message]
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=87zl84ojdk.fsf@usenet.my.skamphausen.de \
--to=skampi@gmx.net \
--cc=help-gnu-emacs@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.