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

Previous Next

Package: emacs;

Reported by: Max Brieiev <max.brieiev <at> gmail.com>

Date: Sat, 9 Jul 2022 07:24:02 UTC

Severity: normal

Tags: moreinfo

Found in version 29.0.50

Fixed in version 30.1

Done: Dmitry Gutov <dgutov <at> yandex.ru>

Bug is archived. No further changes may be made.

Full log


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

From: Dmitry Gutov <dgutov <at> yandex.ru>
To: Eli Zaretskii <eliz <at> gnu.org>
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 18:25:07 +0200
On 28/02/2023 15:04, Eli Zaretskii wrote:
>> 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?

Sure:

1) Visit an .rb file (with ruby-mode).
2) Instrument ruby-smie-rules with edebug.
3) Switch to .rb file again and press TAB somewhere where it would call 
ruby-mode's indentation code.
4) Step through ruby-smie-rules with SPC, not too quickly.

That happens with 'emacs -Q', no extra setup needed.




This bug report was last modified 2 years and 75 days ago.

Previous Next


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