From: Kai Ma <justksqsf@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 61703@debbugs.gnu.org
Subject: bug#61703: 29.0.60; Emacs crashes on C-x 8 RET
Date: Wed, 22 Feb 2023 20:59:54 +0800 [thread overview]
Message-ID: <4651AC01-AA67-492A-893B-B8FF829758DC@gmail.com> (raw)
In-Reply-To: <83fsaxswjk.fsf@gnu.org>
> On Feb 22, 2023, at 20:40, Eli Zaretskii <eliz@gnu.org> wrote:
>
>> From: Kai Ma <justksqsf@gmail.com>
>> Date: Wed, 22 Feb 2023 16:00:29 +0800
>>
>> Emacs sometimes crashes on C-x 8 RET, ie. (insert-char).
>>
>> Sorry, but I didn't find a way to reproduce this issue with emacs -Q.
>>
>> This seems to be related to vertico-posframe-mode (which puts the
>> minibuffer in a separate child frame). I can confirm that if I disable
>> vertico-posframe-mode, this problem disappears.
>
> Please provide at least the information you can provide: what did you
> type at the "C-x 8 RET" prompt, and when exactly it crashed during
> this command. Also, how to setup vertico-posframe-mode like you do.
This is how I reproduce this crash:
1. Create a fresh Emacs instance.
2. Press C-x 8 RET before doing anything else.
If vertico-posframe is displayed successfully at least once (e.g. using M-x)
then Emacs won’t crash from insert-char anymore.
3. Emacs crashes before the child frame appears, so I don’t have a
chance to type anything.
There is a minimal init.el with which I can reproduce this crash:
(package-install 'vertico)
(package-install 'vertico-posframe)
(use-package vertico
:hook (after-init . vertico-mode))
(use-package vertico-posframe
:hook (vertico-mode . vertico-posframe-mode))
> Basically, these problems are impossible to debug without a
> reproducible recipe, so any details count.
>
> Thanks in advance.
next prev parent reply other threads:[~2023-02-22 12:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 8:00 bug#61703: 29.0.60; Emacs crashes on C-x 8 RET Kai Ma
2023-02-22 12:40 ` Eli Zaretskii
2023-02-22 12:59 ` Kai Ma [this message]
2023-02-22 14:08 ` Eli Zaretskii
2023-02-22 18:45 ` Kai Ma
2023-02-22 20:18 ` Eli Zaretskii
2023-02-22 21:29 ` Gregory Heytings
2023-09-05 23:44 ` Stefan Kangas
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=4651AC01-AA67-492A-893B-B8FF829758DC@gmail.com \
--to=justksqsf@gmail.com \
--cc=61703@debbugs.gnu.org \
--cc=eliz@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 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).