From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 张云峰 <zhangyunfeng0101@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
joaotavora@gmail.com, 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 22:28:05 +0800 [thread overview]
Message-ID: <87h6xreadm.fsf@yahoo.com> (raw)
In-Reply-To: <CA+cG9GxvfbnBR9w0wpJwis6+9pR0isqOu9TKG5MmuOqwZs9TYA@mail.gmail.com> ("张云峰"'s message of "Mon, 19 Dec 2022 21:32:08 +0800")
张云峰 <zhangyunfeng0101@gmail.com> writes:
> Thanks for your quick reply.
>
> Yes, I did, the author of lsp-bridge thinks that this bug belongs to emacs itself.
> What's confusing is that lsp-bridge works very well in emacs28 and emacs29 without pgtk feature.
> And I think that even if it is a bug in a third-party library, it should not cause emacs to be unable to edit.
If you put a breakpoint with GDB on delete_frame set to only print a
backtrace and then continue (would someone else please explain the
procedure, as it's 10:30 PM here), what is printed immediately before
the error?
next prev parent reply other threads:[~2022-12-19 14:28 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h6xreadm.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=60163@debbugs.gnu.org \
--cc=eliz@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 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.