From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: nnimap: gnus-gcc-mark-as-read not working
Date: Tue, 18 Apr 2006 12:34:26 +0200 [thread overview]
Message-ID: <87lku3rx3h.fsf@latte.josefsson.org> (raw)
In-Reply-To: <86ek0036wb.fsf@student.uni-magdeburg.de> (Wolfram Fenske's message of "Fri, 14 Apr 2006 10:20:36 +0200")
Wolfram Fenske <Wolfram.Fenske@Student.Uni-Magdeburg.DE> writes:
> Wolfram Fenske <Wolfram.Fenske@Student.Uni-Magdeburg.DE> writes:
>
>> Hello!
>>
>> I have sent mail Gcc-ed to a folder on my IMAP-server. This mostly
>> works, but the copy in the sent-mail folder is never marked as read.
>> In my .gnus.el I have:
>>
>> --8<---------------cut here---------------start------------->8---
>> (setq gnus-message-archive-group "nnimap+uni:INBOX.sent-mail"
>> gnus-gcc-mark-as-read t)
>> --8<---------------cut here---------------end--------------->8---
>>
>> If I use nnfolder [...], archiving works as it should.
>
> I've tracked it down. The error occurs here:
>
> (defun gnus-group-make-articles-read (group articles)
> "Update the info of GROUP to say that ARTICLES are read."
> (let* ((num 0)
> (entry (gnus-gethash group gnus-newsrc-hashtb))
> ... ; some more initializing
> (when entry
> ... ; do all the work
>
> For my IMAP sent-mail group, "entry" is always "nil" because "group"
> is "nnimap+uni:INBOX.sent-mail" but my ~/.newsrc.eld contains only
> entries like "INBOX.sent-mail", i. e. the prefix "nnimap+uni:" is
> missing.
Doesn't it work to simply drop the 'nnimap+uni:' part above?
> Now the question is: why don't I have the prefixes in ~/.newsrc.eld?
> Is this because nnimap is my primary gnus-select-method? A while back
> I had nnimap as my secondary select method and I think I didn't have
> this problem then.
>
> Also: is there a bug in "gnus-group-make-articles-read" or is it my
> config? I tought
>
> (setq gnus-message-archive-method '(nnimap "my.imap.server.de")
> gnus-message-archive-group "INBOX.sent-mail")
>
> might do the trick, but this didn't fix it, either.
>
> If there really is a bug, and someone can tell me what's going on with
> those prefixes, I'd be happy to write a patch. Until then, I'm using
> this workaround:
I've found that the easiest is to use a nnnil method as the primary
method, and then have all methods being equal.
> *** gnus-sum.el.orig Fri Apr 14 08:01:20 2006
> --- gnus-sum.el Fri Apr 14 10:04:05 2006
> ***************
> *** 5744,5749 ****
> --- 5744,5754 ----
> "Update the info of GROUP to say that ARTICLES are read."
> (let* ((num 0)
> (entry (gnus-gethash group gnus-newsrc-hashtb))
> + (entry (or entry
> + ;; strip the backend prefix and try again
> + (when (string-match "\\([^+]+\\+[^:]+:\\)?\\(.+\\)" group)
> + (setq group (match-string 2 group))
> + (gnus-gethash group gnus-newsrc-hashtb))))
> (info (nth 2 entry))
> (active (gnus-active group))
> range)
>
>
> Regards
> Wolfram
>
> --
> A: Yes.
>>Q: Are you sure?
>>>A: Because it reverses the logical flow of conversation.
>>>>Q: Why is top posting frowned upon?
next prev parent reply other threads:[~2006-04-18 10:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-13 23:55 Wolfram Fenske
2006-04-14 8:20 ` Wolfram Fenske
2006-04-18 10:34 ` Simon Josefsson [this message]
2006-04-18 21:49 ` Bug in gnus-group-make-articles-read? (was: nnimap: gnus-gcc-mark-as-read not working) Wolfram Fenske
2006-04-18 21:52 ` nnimap: gnus-gcc-mark-as-read not working Wolfram Fenske
2006-04-15 2:41 ` Dave Goldberg
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=87lku3rx3h.fsf@latte.josefsson.org \
--to=jas@extundo.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).