From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?UTF-8?Q?=E5=BC=A0=E4=BA=91=E5=B3=B0?= Newsgroups: gmane.emacs.bugs Subject: bug#60163: 29.0.60; Error in post-command-hook (winner-save-old-configurations): (wrong-type-argument frame-live-p #) Date: Mon, 19 Dec 2022 21:32:08 +0800 Message-ID: References: <83bko1hq5t.fsf@gnu.org> <83v8m7eghy.fsf@gnu.org> <83h6xreeic.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="00000000000044a4a405f02e59e6" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="23540"; mail-complaints-to="usenet@ciao.gmane.io" Cc: luangruo@yahoo.com, joaotavora@gmail.com, 60163@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Dec 19 19:12:37 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1p7Kcu-0005xm-Rj for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 19 Dec 2022 19:12:36 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1p7KcT-0003kW-1m; Mon, 19 Dec 2022 13:12:09 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1p7KcN-0003fw-HU for bug-gnu-emacs@gnu.org; Mon, 19 Dec 2022 13:12:04 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1p7KcN-0005vF-5g for bug-gnu-emacs@gnu.org; Mon, 19 Dec 2022 13:12:03 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1p7KcN-0005g4-10 for bug-gnu-emacs@gnu.org; Mon, 19 Dec 2022 13:12:03 -0500 X-Loop: help-debbugs@gnu.org Resent-From: =?UTF-8?Q?=E5=BC=A0=E4=BA=91=E5=B3=B0?= Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 19 Dec 2022 18:12:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 60163 X-GNU-PR-Package: emacs Original-Received: via spool by 60163-submit@debbugs.gnu.org id=B60163.167147350121781 (code B ref 60163); Mon, 19 Dec 2022 18:12:02 +0000 Original-Received: (at 60163) by debbugs.gnu.org; 19 Dec 2022 18:11:41 +0000 Original-Received: from localhost ([127.0.0.1]:39560 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1p7Kc1-0005fE-8k for submit@debbugs.gnu.org; Mon, 19 Dec 2022 13:11:41 -0500 Original-Received: from mail-lf1-f46.google.com ([209.85.167.46]:39543) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1p7GFn-0002OS-1s for 60163@debbugs.gnu.org; Mon, 19 Dec 2022 08:32:28 -0500 Original-Received: by mail-lf1-f46.google.com with SMTP id bf43so13649494lfb.6 for <60163@debbugs.gnu.org>; Mon, 19 Dec 2022 05:32:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=RIsGzgR0MFPvoEWskdx+snXHRMnDmxLu+P0Bk9nIRnQ=; b=fnFOi4upN4zFe5B6EozDKDYS7j4ZDVWRrGgnuBuhuxcZcu5dS1Oke7mVVYSA/XLc3u dfUdI18GEphFPD2PS6sSGuPTMCT3XcYcxWUmLalylyQ4zLsLGTPOoJHg+EMKQHTbbFTA jmkVT3LhJ+bbQwhNLTZQrfaHIUolkBLbYAsvuxWLSOaWC66wugM1F63gBo+cM4yLIumf ewvOsH1nfCjKB727slXNpUrECZu23A+M4bBYSdfXaS+S+30Nq5gpyM3rnCF3fZfW4Hs0 C/ccftQnnFGfIvRcxaD8LKLONxqB0EN5CRcX/h9Ppa8shhUNcSyOBz64xsSsItuyC+z7 JEnw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=RIsGzgR0MFPvoEWskdx+snXHRMnDmxLu+P0Bk9nIRnQ=; b=wYPzSj4PyuAZuGRKKsIbSmV5A+IcwcpuwYF3UuEaoU2od1G4kkrPtmHNDamZST9NEe PHjjZwsBjVB2oKKUtFvdcb5vHybOO7G6cK7/Q2l7xX/1p2HS1zT6/8ajlqVgIPN5TF8L WNAd7NTsPdncpsA2WsMlcwenyjbC5qgUgfSj5jbpKInSkcajd05nsvYIQPxjQBQsRaOJ XhLcZYABVUj3vx900Gb3HPQslBvVqy56p9mqYUXdZS5/dVrcfhZ2Hq4nv55DAhqiy1qR v/FQeoyATyHYFPL/o3Fh52BkEoWJ+HbVFZVsNRbA5ujojkYm1y4lCPsbbvezg0w2bC+X h74g== X-Gm-Message-State: ANoB5pkssy3lY24Yghez043QyAzWunOLdyK5Ztzr9+GAMM5hKTPnT8pA bMD7K74VUEAPLI5NerJnY0gKiyG7xI1y2hXrmC4= X-Google-Smtp-Source: AA0mqf6To9a+7lBsGFDKJ4Cuh6wk0tV/EOtWJKbGlNVcFKn0XiTVgvkVAKqZO6NjrOsnZZKlXfY932JOW945cWElZCo= X-Received: by 2002:ac2:518f:0:b0:4b4:9227:3565 with SMTP id u15-20020ac2518f000000b004b492273565mr40016754lfi.290.1671456740384; Mon, 19 Dec 2022 05:32:20 -0800 (PST) In-Reply-To: <83h6xreeic.fsf@gnu.org> X-Mailman-Approved-At: Mon, 19 Dec 2022 13:11:39 -0500 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:251453 Archived-At: --00000000000044a4a405f02e59e6 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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. Eli Zaretskii =E4=BA=8E2022=E5=B9=B412=E6=9C=8819=E6=97=A5= =E5=91=A8=E4=B8=80 20:58=E5=86=99=E9=81=93=EF=BC=9A > > Cc: 60163@debbugs.gnu.org > > Date: Mon, 19 Dec 2022 14:15:53 +0200 > > From: Eli Zaretskii > > > > > From: =E5=BC=A0=E4=BA=91=E5=B3=B0 > > > 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=C3=A3o, would you please try to look at this? The combina= tion > > of required features to reproduce the problem is beyond my abilities. > > On second thought, perhaps this is a problem with lsp-mode? Did you > try to report this to the lsp-mode developers? > --00000000000044a4a405f02e59e6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks for your quic= k reply.=C2=A0=C2=A0

Yes, I did, the author of lsp-bridge thinks that this bug belongs to= emacs itself.
What's confusing is that=C2=A0lsp-bridge works very well in = emacs28 and emacs29 without pgtk feature.=C2=A0
And I th= ink that even if it is a bug in a third-party library, it should not cause = emacs to be unable to edit.


Eli Zaretskii &= lt;eliz@gnu.org> =E4=BA=8E2022=E5=B9= =B412=E6=9C=8819=E6=97=A5=E5=91=A8=E4=B8=80 20:58=E5=86=99=E9=81=93=EF=BC= =9A
> Cc: 60163@debbugs.gnu.o= rg
> Date: Mon, 19 Dec 2022 14:15:53 +0200
> From: Eli Zaretskii <eliz@gnu.org>
>
> > From: =E5=BC=A0=E4=BA=91=E5=B3=B0 <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=C3=A3o, would you please try to look at this?=C2=A0 The c= ombination
> of required features to reproduce the problem is beyond my abilities.<= br>
On second thought, perhaps this is a problem with lsp-mode?=C2=A0 Did you try to report this to the lsp-mode developers?
--00000000000044a4a405f02e59e6--