GNU bug report logs -
#44839
27.1; rmail: output to file does not go to next message
Previous Next
Reported by: Francesco Potortì <pot <at> gnu.org>
Date: Tue, 24 Nov 2020 13:36:02 UTC
Severity: minor
Found in version 27.1
Done: Eli Zaretskii <eliz <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your message dated Sat, 28 Nov 2020 19:07:31 +0200
with message-id <83lfelmmuk.fsf <at> gnu.org>
and subject line Re: bug#44839: 27.1; rmail: output to file does not go to next message
has caused the debbugs.gnu.org bug report #44839,
regarding 27.1; rmail: output to file does not go to next message
to be marked as done.
(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)
--
44839: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=44839
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
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 part 3 (message/rfc822, inline)]
> 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.
This bug report was last modified 4 years and 194 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.