GNU bug report logs - #44839
27.1; rmail: output to file does not go to next message

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 44839 in the body.
You can then email your comments to 44839 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Francesco Potortì <pot <at> gnu.org>
To: bug-gnu-emacs <at> gnu.org
Subject: 27.1; rmail: output to file does not go to next message
Date: Tue, 24 Nov 2020 14:35:41 +0100

rmail-output should do its work, then mark the message as deleted, then
go to the next message.  The last step is not done: the filed and
deleted message is still displayed.  This is a regression.

I suppose it should be quite easy to pinpoint, but I don't have time
right now, so I am filing a bug.  Here is the value of the relevant vars
for me:

(setq rmail-output-reset-deleted-flag t
      rmail-delete-after-output t
      rmail-confirm-expunge nil)


In GNU Emacs 27.1 (build 1, x86_64-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
 of 2020-11-08, modified by Debian built on x86-ubc-01
Windowing system distributor 'The X.Org Foundation', version 11.0.12008000
System Description: Debian GNU/Linux bullseye/sid

Message #10 received at 44839-done <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Francesco Potortì <pot <at> gnu.org>
Cc: 44839-done <at> debbugs.gnu.org
Subject: Re: bug#44839: 27.1; rmail: output to file does not go to next message
Date: Sat, 28 Nov 2020 19:07:31 +0200

> From: Francesco Potortì <pot <at> gnu.org>
> Date: Tue, 24 Nov 2020 14:35:41 +0100
> 
> rmail-output should do its work, then mark the message as deleted, then
> go to the next message.  The last step is not done: the filed and
> deleted message is still displayed.  This is a regression.
> 
> I suppose it should be quite easy to pinpoint, but I don't have time
> right now, so I am filing a bug.  Here is the value of the relevant vars
> for me:
> 
> (setq rmail-output-reset-deleted-flag t
>       rmail-delete-after-output t
>       rmail-confirm-expunge nil)

This is indeed a regression introduced by the handling of the new
option rmail-output-reset-deleted-flag, which you have customized.

Should be fixed now.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.