From: Simon Josefsson <jas@extundo.com>
Subject: Re: gnus-summary-move-article sets message to unread
Date: Tue, 18 Nov 2003 14:47:05 +0100 [thread overview]
Message-ID: <ilu4qx14wme.fsf@latte.josefsson.org> (raw)
In-Reply-To: <87znetrjrx.fsf@dagobert.moware.at>
Heinrich Moser <usenet@heinzi.at> writes:
> Chris Beggy <chrisb@kippona.com> writes:
>> Heinrich Moser <usenet@heinzi.at> writes:
>>> This is probably a trivial issue for most of you but I could not find
>>> a solution for it yet: When moving a message from my IMAP inbox to
>>> another folder ('B m', i.e. gnus-summary-move-article), the message is
>>> correctly moved to the folder but also marked as unread (in the new
>>> folder). Is there any way to change that behavior? After all, I *did*
>>> read the message before moving it.
>>
>> I'm interested in this issue too. I'm using gnu emacs 21.1.2,
>> gnus 5.10.3, and cyrus21-imap. I see the same behavior with B m
>> or B c between folders on the imap server.
>
> It looks like I found a solution (using emacs 21.2.1, gnus
> 5.9.0). Gnus updates the data on the IMAP server (such as
> "read"-flags) upon leaving the group. Thus, when you read a new
> (i.e. previously unread) message in a group and move it directly after
> reading it, it's still marked "unread" on the server and therefore
> "unread" in the destination folder.
>
> The following works for me (~/.gnus):
>
> (defun my-gnus-move (&optional N)
> "Move article including correct read state."
> (interactive "P")
> (gnus-summary-update-info)
> (gnus-summary-move-article))
>
> (gnus-define-keys (gnus-summary-backend-map "B" gnus-summary-mode-map)
> "m" my-gnus-move)
>
> gnus-summary-update-info saves the updated "read"-flags onto the
> server. I'm not an experienced lisp programmer so any corrections are
> appreciated.
Ah, this makes sense. It is probably a bug in B m and B c, it should
use the data in the summary buffer and not the info in .newsrc.
parent reply other threads:[~2003-11-18 13:47 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <87znetrjrx.fsf@dagobert.moware.at>]
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=ilu4qx14wme.fsf@latte.josefsson.org \
--to=jas@extundo.com \
/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).