From: 张云峰 <zhangyunfeng0101@gmail.com>
To: martin rudalics <rudalics@gmx.at>
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: Wed, 21 Dec 2022 22:50:35 +0800 [thread overview]
Message-ID: <CA+cG9Gxpoe4sSipL7YpomReVPmVO_AcFPLY32zA9rJfVdwmy1Q@mail.gmail.com> (raw)
In-Reply-To: <4fbc4bd2-898a-bd68-c8a5-c722da4a3e73@gmx.at>
[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]
Hello, martin.
There is a simpler way to reproduce the bug
please replace code in *run-me-to-produce-the-bug.sh* with
```
echo "Please make sure 'clangd' has installed!"
cd demo-code
echo "int main() {
/* M-x lsp-bridge-code action */
const int place_cursor_here_then_M_X_lsp_bridge_code_action = 1
}" > code.c
git init
cd ..
emacs -Q -L ./lsp-bridge -L ./posframe -L ./markdown-mode -L ./yasnippet
demo-code/code.c --eval="(require 'lsp-bridge)" --eval="(lsp-bridge-mode)"
```
and run *run-me-to-product-the-bug.sh *to reproduce the bug in c
language.
martin rudalics <rudalics@gmx.at> 于2022年12月21日周三 17:22写道:
> > I can't interact with the minibuffer, and I can't type in emacs also.
>
> Then this bug is more complex than you described. What does
>
> wmctrl -l
>
> tell about Emacs' windows? Is Emacs itself busy looping?
>
> > I have attached code to help you reproduce this bug.
> > Prerequisites: Compile emacs29 with option --with-pgtk.
>
> Sorry but I have neither ts nor npm installed.
>
> martin
>
>
[-- Attachment #2: Type: text/html, Size: 1671 bytes --]
next prev parent reply other threads:[~2022-12-21 14:50 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
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 ` 张云峰 [this message]
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=CA+cG9Gxpoe4sSipL7YpomReVPmVO_AcFPLY32zA9rJfVdwmy1Q@mail.gmail.com \
--to=zhangyunfeng0101@gmail.com \
--cc=60163@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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).