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?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= Newsgroups: gmane.emacs.bugs Subject: bug#56459: 29.0.50; Edebug disables Eldoc Date: Wed, 1 Mar 2023 18:25:04 +0000 Message-ID: References: <87zghieol4.fsf@gmail.com> <871qurzzyv.fsf@gnus.org> <83pmibzx0k.fsf@gnu.org> <20220731195223.90596.FMU217810@trabanten-schwein.prv.splode.com> <87sfmg1bpf.fsf@gnus.org> <5dd202b1-3dfb-022a-d458-c0a13c1a2d59@yandex.ru> <83edqagcux.fsf@gnu.org> <0fc4cf3b-86af-027e-32f4-9c85e2650ae7@yandex.ru> <83ilfkfpgw.fsf@gnu.org> <83h6v4fp3z.fsf@gnu.org> <83bklcflzg.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000001146ac05f5dad620" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="15438"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Max Brieiev , Lars Ingebrigtsen , friedman@splode.com, 56459@debbugs.gnu.org, Dmitry Gutov To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Mar 01 19:26:57 2023 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 1pXRAG-0003nT-QT for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 01 Mar 2023 19:26:56 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pXR9X-0001nA-Cq; Wed, 01 Mar 2023 13:26:11 -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 1pXR9P-0001dk-SP for bug-gnu-emacs@gnu.org; Wed, 01 Mar 2023 13:26:06 -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 1pXR9O-0007Iz-FW for bug-gnu-emacs@gnu.org; Wed, 01 Mar 2023 13:26:03 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pXR9N-0004V4-W2 for bug-gnu-emacs@gnu.org; Wed, 01 Mar 2023 13:26:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: =?UTF-8?Q?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 01 Mar 2023 18:26:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 56459 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: moreinfo Original-Received: via spool by 56459-submit@debbugs.gnu.org id=B56459.167769513517265 (code B ref 56459); Wed, 01 Mar 2023 18:26:01 +0000 Original-Received: (at 56459) by debbugs.gnu.org; 1 Mar 2023 18:25:35 +0000 Original-Received: from localhost ([127.0.0.1]:54899 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pXR8w-0004UO-KS for submit@debbugs.gnu.org; Wed, 01 Mar 2023 13:25:35 -0500 Original-Received: from mail-oa1-f43.google.com ([209.85.160.43]:36547) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pXR8u-0004UA-9s for 56459@debbugs.gnu.org; Wed, 01 Mar 2023 13:25:32 -0500 Original-Received: by mail-oa1-f43.google.com with SMTP id 586e51a60fabf-1755e639b65so3943231fac.3 for <56459@debbugs.gnu.org>; Wed, 01 Mar 2023 10:25:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1677695126; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=rV0zxR3nns7oq9BPJTnRZTY6bWN3BBvKVN+IAqvODnc=; b=pnAodspgk4tci4/ufXYcRrzRpgcTjCseBBsrCaEGaqLt90g09SKvmGMjnzojecYOQx 69hzr1prp9eFGrfBwLHwC/UYnq4EpzY98juih/nCwNsf6XAqCpGZ1lha6PhYzmes9avh S363nSmAUr41l1jjU9QzNUJiaeqfWtT/O7TY7pIcOi8kz0bc2YeFmj/4B4OLTPRqQPxJ MTxgPdlMLtMkNZfaBEpw+CFjZrQBA9xuMWxwTTnQUUIl2ZJ5wmZrE6TM1epYcH9keSPt ERayJFpPEGgPxC8K7rOvBt8gwlUUiVOSZeAds4CuAU94z8Ba2QgK+SebXHucNXay0K5U 6Ynw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1677695126; 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=rV0zxR3nns7oq9BPJTnRZTY6bWN3BBvKVN+IAqvODnc=; b=OrGoHoFyJS5t99j+IPYIsqH5BmG+JSf6kQXKOCe+lDKjuG9xbRBXFMjUZ3BCbWZCwZ tufzS8eAw/5cp6pGGlq6i9t5kCrHBgkS/Fbj7q90/mrfkkVdc+gTG4Cw34HgCmHl06j5 rpPakKIcjGvpGWtkNX0efr+K30XEKcqXQbAIf6M7AHKuPlGh4EszPtf4nQ9pKjPXoRAo haK4pChNlY6qeHc9fAiTMFhVfKagoXVeDotOPUJly+azS0XZCXCJ+ajhCVT4gCLdjXQc igESS33XoY49n5vpKu5tvzVnH/PdCU9zWRXN82nCHXrDDV2f570IniTY7Jn1D+X1QNl7 Du0g== X-Gm-Message-State: AO0yUKXRix8ZEXz+Tho6hKqXIGIpTP2l51caCQLzNu/cwnyvfLRmPZoX innpcUBgBgG/JuvBMVosu3cwOl01JZixuU1gHiA= X-Google-Smtp-Source: AK7set9VqT9qUYi2DC41CCyRgB7smQzMBulu5yqEWZPS6odR6Wxws26IIwJmxV1x/dCsybrXriWvXBeO7NOc0ANnkJE= X-Received: by 2002:a05:6871:8e85:b0:16e:8811:2bb with SMTP id zq5-20020a0568718e8500b0016e881102bbmr2170928oab.8.1677695126682; Wed, 01 Mar 2023 10:25:26 -0800 (PST) In-Reply-To: <83bklcflzg.fsf@gnu.org> 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:257095 Archived-At: --0000000000001146ac05f5dad620 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I think there's a decent place in eldoc.el to do this check, though we should take care not to require edebug.el in eldoc.el. I'll look at it later, but I think if one searches for the phrase "check if we have permission to mess with the echo area at all", or something to that effect, one would see it. Jo=C3=A3o On Wed, Mar 1, 2023, 16:59 Eli Zaretskii wrote: > > Date: Wed, 1 Mar 2023 18:06:56 +0200 > > Cc: max.brieiev@gmail.com, larsi@gnus.org, 56459@debbugs.gnu.org, > > friedman@splode.com > > From: Dmitry Gutov > > > > On 01/03/2023 17:49, Eli Zaretskii wrote: > > >> Cc:max.brieiev@gmail.com,larsi@gnus.org,56459@debbugs.gnu.org, > > >> friedman@splode.com > > >> Date: Wed, 01 Mar 2023 17:42:07 +0200 > > >> From: Eli Zaretskii > > >> > > >> So I've now reverted that change, and I'm reopening the bug. It wil= l > > >> have to be fixed in some other way. > > > One possibility would be to show the ElDoc info on the mode line when > > > Edebug is active. But the difficulty with that is to figure out how > > > to revert the mode line to the original shape when Edebug finishes. > > > We currently show the info on the mdoe line when the current buffer i= s > > > a minibuffer, and remove the info in minibuffer-exit-hook, but how to > > > do that in the Edebug case? > > > > edebug-mode-hook? > > That's a starting point, but I don't think it's enough, because you > could switch to another buffer without exiting Edebug. I tried > something like that and it didn't work well enough. But maybe my > testing was incorrect, so if you are confident that this fixes the > problem, feel free to install (perhaps on master, though). > > > > --0000000000001146ac05f5dad620 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I think there's a decent place in eldoc.el to do= this check, though we should take care not to require edebug.el in eldoc.e= l.

I'll look at it l= ater, but I think if one searches for the phrase "check if we have per= mission to mess with the echo area at all", or something to that effec= t, one would see it.

Jo= =C3=A3o

On Wed, Mar 1, 2023, 16:59 Eli Zaretskii <eliz@gnu.org> wrote:
> Date: Wed, 1 Mar 2023 18:06:56 +0200
> Cc: max.brieiev@gmail.com, larsi@gnus.org, 56459@debbugs.gnu= .org,
>=C2=A0 friedman@splode.com
> From: Dmitry Gutov <dgutov@yandex.ru>
>
> On 01/03/2023 17:49, Eli Zaretskii wrote:
> >> Cc:max.brieiev@gmail.com,larsi@gnus.org,5645= 9@debbugs.gnu.org,
> >>=C2=A0 =C2=A0friedman@splode.com
> >> Date: Wed, 01 Mar 2023 17:42:07 +0200
> >> From: Eli Zaretskii<eliz@gnu.org>
> >>
> >> So I've now reverted that change, and I'm reopening t= he bug.=C2=A0 It will
> >> have to be fixed in some other way.
> > One possibility would be to show the ElDoc info on the mode line = when
> > Edebug is active.=C2=A0 But the difficulty with that is to figure= out how
> > to revert the mode line to the original shape when Edebug finishe= s.
> > We currently show the info on the mdoe line when the current buff= er is
> > a minibuffer, and remove the info in minibuffer-exit-hook, but ho= w to
> > do that in the Edebug case?
>
> edebug-mode-hook?

That's a starting point, but I don't think it's enough, because= you
could switch to another buffer without exiting Edebug.=C2=A0 I tried
something like that and it didn't work well enough.=C2=A0 But maybe my<= br> testing was incorrect, so if you are confident that this fixes the
problem, feel free to install (perhaps on master, though).



--0000000000001146ac05f5dad620--