From: "kassick@gmail.com" <kassick@gmail.com>
To: Jeremy Bryant <jb@jeremybryant.net>
Cc: 71654@debbugs.gnu.org
Subject: bug#71654: [PATCH] Fix display-buffer-override-next-command
Date: Wed, 19 Jun 2024 18:53:08 -0300 [thread overview]
Message-ID: <CAJvJD8gk5hOh0bCsnsj+3SUcgtASsxr5YRBRY586vKLO2936HA@mail.gmail.com> (raw)
In-Reply-To: <87zfrg3a4g.fsf@jeremybryant.net>
[-- Attachment #1: Type: text/plain, Size: 1270 bytes --]
No need for any mode, just
- M-S-: (setq display-buffer-overriding-action (cons #'ignore nil))
RET ;; Eval
- C-x 4 4 ;; (other-window-prefix)
- C-x C-f ;; (find-file)
and you should already see the error.
After that, you probably will end up with an unusable emacs, so just eval
(setq display-buffer-overriding-action (cons nil nil)) and you'll be good
to go.
Em qua., 19 de jun. de 2024 às 18:17, Jeremy Bryant <jb@jeremybryant.net>
escreveu:
> "kassick@gmail.com" <kassick@gmail.com> writes:
>
> > When display-buffer-overriding-action's car is set to a function
> > instead of a list, display-buffer-override-next-command must ensure
> > that the car is a list before pushing a new element to it, otherwise
> > the car will become a itself a cons-cell and the clear-fun will
> > trigger a wrong-type-argumen error when trying to delq the action.
> >
> > The error can be triggered by using some minor mode that
> > updates display-buffer-override-next-command (such as purpose-mode)
> > and then calling other-window-prefix.
> >
>
> To reproduce the bug, what other built-in modes (instead of
> purpose-mode) can be used?
>
--
Rodrigo Virote Kassick
------------------------------------------------------------
[-- Attachment #2: Type: text/html, Size: 1993 bytes --]
next prev parent reply other threads:[~2024-06-19 21:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 15:20 bug#71654: [PATCH] Fix display-buffer-override-next-command kassick
2024-06-19 21:17 ` Jeremy Bryant via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-19 21:53 ` kassick [this message]
2024-06-19 21:32 ` Andrea Corallo
2024-06-19 21:54 ` kassick
2024-06-19 22:11 ` Andrea Corallo
2024-06-19 22:16 ` kassick
2024-06-20 7:55 ` Andrea Corallo
2024-06-20 5:15 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJvJD8gk5hOh0bCsnsj+3SUcgtASsxr5YRBRY586vKLO2936HA@mail.gmail.com \
--to=kassick@gmail.com \
--cc=71654@debbugs.gnu.org \
--cc=jb@jeremybryant.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).