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 22:12:54 +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="000000000000040f2f05f02eeb24" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="23569"; 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-0005xl-Rq 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 1p7KcR-0003ho-0U; Mon, 19 Dec 2022 13:12:07 -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 1p7KcO-0003g4-13 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-0005vO-Pd 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-0005gB-Fw 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:03 +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.167147350321788 (code B ref 60163); Mon, 19 Dec 2022 18:12:03 +0000 Original-Received: (at 60163) by debbugs.gnu.org; 19 Dec 2022 18:11:43 +0000 Original-Received: from localhost ([127.0.0.1]:39562 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1p7Kc1-0005fG-Pz for submit@debbugs.gnu.org; Mon, 19 Dec 2022 13:11:42 -0500 Original-Received: from mail-lf1-f54.google.com ([209.85.167.54]:35352) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1p7GtD-0002sR-S4 for 60163@debbugs.gnu.org; Mon, 19 Dec 2022 09:13:12 -0500 Original-Received: by mail-lf1-f54.google.com with SMTP id b3so13864747lfv.2 for <60163@debbugs.gnu.org>; Mon, 19 Dec 2022 06:13:11 -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=GOlhaqFD9sy9NpyTtfq1xKpE6JyN0mWPWv3cKC1WsIM=; b=JqkeQrDwazO1sk/bZEOAfbZyySD+bY1Sfhv78/qTwnegIvakHKVcr14EGYeX8s8ow7 tElTt7wlzXtKySMH9zVdkaqcWnq5SXPfSV8Ub74XjQlKkjoQswFLOJKhnMhFc5+fiT4V jBsm5JbSfJ+tRnaFUwPyPHwQ/0upbZIY1paRUovmP8OwjZEgMgf4d6amsP+KvcU3BdwH 9MLrcL6siPgxNHs696ZRksMuoBtqlvlH5DMprSgNKcSZPnvQ9Vk5Oor5x+wr2yhzRxdp 70ILutJFMVrunTVlwwILJHrO0Amuu1oRt4+fIvLfqxvXobAwH1JqOveYb/JPhEFeNiIv 4Fug== 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=GOlhaqFD9sy9NpyTtfq1xKpE6JyN0mWPWv3cKC1WsIM=; b=r/JoLIstQC0DiL35AeXQ6tWHIWx6DD1pjGuCmCf66R9FuXLcjdl+rkVESK3hW8Av7L lQ2CnHJCdVTTJnFCTsfpx25cUBIYPWNn3PbAvxtMITE0hL+P4vn50Z0kpCEc+VHuSU2/ A8njKaqR22OB7SL5Po75SOViAbzaet8IMbDvSbPi7fCLmYkOyjIpBhfFxTjCDT+7h7jY oZ6LTpuqXtGCNoQ9AVHABU7Srjm9d/LAdRBj55tfBZUIYNblPYjhk2bU8MItyZ70gH8A EPUASFhZtom1pAi2EorwsGxRU7XYa/HO9omn4CJEwn5KU+8W50/glkQcCXlBEfo/W4vq qHvA== X-Gm-Message-State: ANoB5pltDZ2msRwKBARM1eYep0YmUjZ3HIYfhxNAR3LhtUxApyd5UcSO xklAGH7v8Qqv4hmpCVgJYtJ8HUcfdObcd3AEmy8= X-Google-Smtp-Source: AA0mqf76vHVTsQy7W2JWCPXbQ10jWRXLrPoQyrxpymWPy5tMZOc6xWvLn15CjjIKPOvUyPeu7f6I68CLXWE+7AoJQ2M= X-Received: by 2002:ac2:4207:0:b0:4b5:afc4:a003 with SMTP id y7-20020ac24207000000b004b5afc4a003mr1577160lfh.680.1671459185625; Mon, 19 Dec 2022 06:13:05 -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:251454 Archived-At: --000000000000040f2f05f02eeb24 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? > --000000000000040f2f05f02eeb24 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=C2=A0= works very well in emacs28 and emacs29 without pgtk feature.=C2=A0
<= /div>
And I think that even if it is a bug in a third-party librar= y, it should not cause emacs to be unable to edit.
<= br>
Eli Zar= etskii <eliz@gnu.org> =E4=BA=8E20= 22=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
> C= c: 60163@debbugs= .gnu.org
> 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?
--000000000000040f2f05f02eeb24--