GNU bug report logs - #56459
29.0.50; Edebug disables Eldoc

Previous Next

Full log

Message #40 received at 56459 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Dmitry Gutov <dgutov <at> yandex.ru>
Cc: max.brieiev <at> gmail.com, larsi <at> gnus.org, 56459 <at> debbugs.gnu.org,
 friedman <at> splode.com
Subject: Re: bug#56459: 29.0.50; Edebug disables Eldoc
Date: Tue, 28 Feb 2023 15:04:38 +0200

> Date: Tue, 28 Feb 2023 04:15:41 +0200
> Cc: max.brieiev <at> gmail.com, eliz <at> gnu.org, 56459 <at> debbugs.gnu.org
> From: Dmitry Gutov <dgutov <at> 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?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.