From: Nicolas Graner <nicolas@graner.name>
To: 59206@debbugs.gnu.org
Subject: bug#59206: rmail-summary-apply-filters-consecutively causes wrong-type-argument error
Date: Fri, 11 Nov 2022 23:49:22 +0100 [thread overview]
Message-ID: <875yflumx9.fsf@graner.name> (raw)
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)
next reply other threads:[~2022-11-11 22:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 22:49 Nicolas Graner [this message]
2022-11-12 3:38 ` bug#59206: rmail-summary-apply-filters-consecutively causes wrong-type-argument error Richard Stallman
2022-11-12 9:07 ` Eli Zaretskii
2022-11-12 17:49 ` Andrea Monaco via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-17 20:46 ` Jakub Ječmínek via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=875yflumx9.fsf@graner.name \
--to=nicolas@graner.name \
--cc=59206@debbugs.gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.