GNU bug report logs -
#59206
rmail-summary-apply-filters-consecutively causes wrong-type-argument error
Previous Next
Reported by: Nicolas Graner <nicolas <at> graner.name>
Date: Fri, 11 Nov 2022 22:50:02 UTC
Severity: normal
Done: Jakub Ječmínek <kuba <at> kubajecminek.cz>
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 Fri, 17 May 2024 20:46:17 +0000
with message-id <87le48i2uh.fsf <at> kubajecminek.cz>
and subject line Re: bug#59206: rmail-summary-apply-filters-consecutively causes wrong-type-argument error
has caused the debbugs.gnu.org bug report #59206,
regarding rmail-summary-apply-filters-consecutively causes wrong-type-argument error
to be marked as done.
(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)
--
59206: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=59206
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
When the variable rmail-summary-apply-filters-consecutively is non-nil,
if you execute one of the rmail-summary-by-* commands when there is no
existing summary, you get an error.
This is because those commands call
rmail-summary-fill-displayed-messages, which assumes
rmail-summary-buffer is a buffer, but in this case it is nil.
Example (starting from emacs -Q):
C-u M-x rmail [any rmail file]
M-: (setq rmail-summary-apply-filters-consecutively t)<RET>
M-x rmail-summary-from-senders<RET>testing<RET>
Debugger entered--Lisp error: (wrong-type-argument stringp nil)
rmail-summary-fill-displayed-messages()
rmail-summary-by-senders("testing")
funcall-interactively(rmail-summary-by-senders "testing")
call-interactively(rmail-summary-by-senders record nil)
command-execute(rmail-summary-by-senders record)
execute-extended-command(nil "rmail-summary-by-senders" "rmail-summary-by-senders")
funcall-interactively(execute-extended-command nil "rmail-summary-by-senders" "rmail-summary-by-senders")
call-interactively(execute-extended-command nil nil)
command-execute(execute-extended-command)
[Message part 3 (message/rfc822, inline)]
Andrea Monaco <andrea.monaco <at> autistici.org> writes:
> The last patch I sent fixes exactly that (plus it changes the custom
> variable name). Thanks for testing Nicolas!
I was not able to reproduce the original error so I assume that Andrea's
fix resolved this bug. I'm therefore closing this.
Best
This bug report was last modified 1 year and 63 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.