all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Max Brieiev <max.brieiev@gmail.com>,
	Lars Ingebrigtsen <larsi@gnus.org>,
	friedman@splode.com, 56459@debbugs.gnu.org,
	Dmitry Gutov <dgutov@yandex.ru>
Subject: bug#56459: 29.0.50; Edebug disables Eldoc
Date: Wed, 1 Mar 2023 18:25:04 +0000	[thread overview]
Message-ID: <CALDnm50u4=mvATy=uSY58-bZatmpX_Wgad4QNFkKEfkNbnfgmA@mail.gmail.com> (raw)
In-Reply-To: <83bklcflzg.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1741 bytes --]

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ão

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,
> >  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,56459@debbugs.gnu.org,
> > >>   friedman@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 the bug.  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.  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 is
> > > 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).
>
>
>
>

[-- Attachment #2: Type: text/html, Size: 3082 bytes --]

  reply	other threads:[~2023-03-01 18:25 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-09  7:23 bug#56459: 29.0.50; Edebug disables Eldoc Max Brieiev
2022-07-11 10:49 ` Lars Ingebrigtsen
2022-07-11 11:52   ` Eli Zaretskii
2022-08-01  1:59     ` Noah Friedman
2022-08-01  2:52     ` Noah Friedman
2022-08-01 10:48       ` Lars Ingebrigtsen
2022-08-02  0:51         ` Noah Friedman
2022-08-02  9:58           ` Lars Ingebrigtsen
2023-02-28  2:15         ` Dmitry Gutov
2023-02-28 13:04           ` Eli Zaretskii
2023-02-28 16:25             ` Dmitry Gutov
2023-03-01 15:42               ` Eli Zaretskii
2023-03-01 15:49                 ` Eli Zaretskii
2023-03-01 16:06                   ` Dmitry Gutov
2023-03-01 16:57                     ` Eli Zaretskii
2023-03-01 18:25                       ` João Távora [this message]
2023-03-01 18:42                         ` Eli Zaretskii
2023-03-01 19:11                           ` João Távora
2023-03-01 19:19                       ` Dmitry Gutov
2023-03-01 19:25                         ` Eli Zaretskii
2023-03-01 19:39                           ` Dmitry Gutov
2023-03-01 19:58                             ` João Távora
2023-03-01 21:36                               ` Dmitry Gutov
2023-03-02  6:08                             ` Eli Zaretskii
2023-03-04  0:43                               ` Dmitry Gutov

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='CALDnm50u4=mvATy=uSY58-bZatmpX_Wgad4QNFkKEfkNbnfgmA@mail.gmail.com' \
    --to=joaotavora@gmail.com \
    --cc=56459@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=eliz@gnu.org \
    --cc=friedman@splode.com \
    --cc=larsi@gnus.org \
    --cc=max.brieiev@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.