From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: max.brieiev@gmail.com, larsi@gnus.org, 56459@debbugs.gnu.org,
friedman@splode.com
Subject: bug#56459: 29.0.50; Edebug disables Eldoc
Date: Tue, 28 Feb 2023 15:04:38 +0200 [thread overview]
Message-ID: <83edqagcux.fsf@gnu.org> (raw)
In-Reply-To: <5dd202b1-3dfb-022a-d458-c0a13c1a2d59@yandex.ru> (message from Dmitry Gutov on Tue, 28 Feb 2023 04:15:41 +0200)
> Date: Tue, 28 Feb 2023 04:15:41 +0200
> Cc: max.brieiev@gmail.com, eliz@gnu.org, 56459@debbugs.gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
>
> Hi Lars and others,
>
> On 01/08/2022 13:48, Lars Ingebrigtsen wrote:
> >> and the behavior is still that only the edebug results are visible;
> >> that is, eldoc's messages aren't covering up the edebug messages, but
> >> they aren't showing up below them either and they're not even showing
> >> up in any mode line.
> >>
> >> So the practical upshot is, I see no change in behavior; whatever
> >> motivated that change seems to be a non-issue now.
> > If I remove that check, I don't see any problems -- stepping through the
> > code doesn't trigger eldoc, so there's no covering up of messages. (But
> > moving the cursor after stepping triggers eldoc, but that seems fine.)
>
> What I'm seeing now, is stepping through Edebug often does invoke Eldoc,
> which triggers messages which do override edebug evaluations.
>
> Which seems like a problem previously solved by that check.
Maybe. I also sometimes see this, but just now trying Edebug on a
random function doesn't reproduce this. Can you reproduce at will? if
so, can you show a recipe?
next prev parent reply other threads:[~2023-02-28 13:04 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 [this message]
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
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=83edqagcux.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=56459@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--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.