From: Eli Zaretskii <eliz@gnu.org>
To: 张云峰 <zhangyunfeng0101@gmail.com>, "Po Lu" <luangruo@yahoo.com>,
"João Távora" <joaotavora@gmail.com>
Cc: 60163@debbugs.gnu.org
Subject: bug#60163: 29.0.60; Error in post-command-hook (winner-save-old-configurations): (wrong-type-argument frame-live-p #<dead frame code action 0x563ea51cbf70>)
Date: Mon, 19 Dec 2022 14:15:53 +0200 [thread overview]
Message-ID: <83v8m7eghy.fsf@gnu.org> (raw)
In-Reply-To: <CA+cG9Gw0CJNsfWViAbU8Zoooo4OJhynhD5k4y0dy_J=Uuu-F-Q@mail.gmail.com> (message from 张云峰 on Mon, 19 Dec 2022 11:46:10 +0800)
[Please use Reply All to reply, to keep the bug tracker on the CC List.]
> From: 张云峰 <zhangyunfeng0101@gmail.com>
> Date: Mon, 19 Dec 2022 11:46:10 +0800
>
> Sorry to reply you so late.
>
> Follow these steps can reproduce this bug:
> 1. compile emacs29 with option --with-pgtk
> 2. edit source code (e.g. rust code) in lsp-bridge-mode
> 3. execute `lsp-bridge-code-action` on a variable, you will see a popup menu, press `Enter ` or just `Ctrl-g`,
> then bug reproducted.
>
> NOTE: When I compile emacs29 without option --with-pgtk, this bug is gone, and everything is fine. so this
> bug may be relative to pgtk feature
Po Lu and João, would you please try to look at this? The combination
of required features to reproduce the problem is beyond my abilities.
next prev parent reply other threads:[~2022-12-19 12:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-17 14:35 bug#60163: 29.0.60; Error in post-command-hook (winner-save-old-configurations): (wrong-type-argument frame-live-p #<dead frame code action 0x563ea51cbf70>) 张云峰
2022-12-17 17:54 ` Eli Zaretskii
[not found] ` <CA+cG9Gw0CJNsfWViAbU8Zoooo4OJhynhD5k4y0dy_J=Uuu-F-Q@mail.gmail.com>
2022-12-19 12:15 ` Eli Zaretskii [this message]
2022-12-19 12:54 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-19 12:58 ` Eli Zaretskii
2022-12-19 13:32 ` 张云峰
2022-12-19 14:28 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-19 15:49 ` 张云峰
2022-12-20 1:40 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-20 2:25 ` 张云峰
2022-12-19 16:11 ` 张云峰
2022-12-19 14:12 ` 张云峰
2022-12-20 8:12 ` martin rudalics
[not found] ` <CA+cG9GwuyL+UxC_L5aRC+MJLFzLMrhYDzOVE8SmJzRrHTmB0NQ@mail.gmail.com>
2022-12-21 9:22 ` martin rudalics
2022-12-21 14:50 ` 张云峰
2022-12-21 17:06 ` martin rudalics
2022-12-22 2:34 ` 张云峰
2022-12-22 10:15 ` martin rudalics
2023-06-07 1:34 ` Michael Heerdegen
2023-09-11 18:10 ` 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=83v8m7eghy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=60163@debbugs.gnu.org \
--cc=joaotavora@gmail.com \
--cc=luangruo@yahoo.com \
--cc=zhangyunfeng0101@gmail.com \
/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).