all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Noah Friedman <friedman@splode.com>
To: eliz@gnu.org
Cc: max.brieiev@gmail.com, larsi@gnus.org, 56459@debbugs.gnu.org
Subject: bug#56459: 29.0.50; Edebug disables Eldoc
Date: Sun, 31 Jul 2022 18:59:49 -0700 (PDT)	[thread overview]
Message-ID: <20220731185949.978182.FMU217810@trabanten-schwein.prv.splode.com> (raw)
In-Reply-To: <83pmibzx0k.fsf@gnu.org> (22-07-11 14:52:59+0300 eliz@gnu.org)

Sorry I didn't see this message sooner.

I seem to recall that the eldoc messages (which would show up as you're
stepping through the debugger because point moves interactively) would
obsure the evaluation results that edebug prints for each sexp.  They both
use the echo area and they're both in the same recursive-edit level but the
echo area isn't currently active, so I'm not sure why `message' would
append below any existing message rather than replacing it.

If that's still the case, and I had to do it again I'd still prefer the
edebug messages over the eldoc ones when both are active at once.


In <83pmibzx0k.fsf@gnu.org> 2022-07-11 14:52:59+0300, Eli Zaretskii <eliz@gnu.org> writes:
>> Cc: 56459@debbugs.gnu.org
>> From: Lars Ingebrigtsen <larsi@gnus.org>
>> Date: Mon, 11 Jul 2022 12:49:12 +0200
>> 
>> Max Brieiev <max.brieiev@gmail.com> writes:
>> 
>> > 5. Observe that while you are typing any expression, eldoc does not
>> >    display any hints in the echo area. (Same issue exists in any other
>> >    elisp buffer with eldoc mode enabled, while Edebug is active.)
>> 
>> This is due to this code:
>> 
>> ;; Check various conditions about the current environment that might make
>> ;; it undesirable to print eldoc messages right this instant.
>> (defun eldoc-display-message-no-interference-p ()
>>   "Return nil if displaying a message would cause interference."
>>   (not (or executing-kbd-macro
>>            (bound-and-true-p edebug-active)
>> 
>> This was added by:
>> 
>> commit 03a9c6d06a177fd9026779bcb952f906a7743690
>> Author:     Noah Friedman <friedman@splode.com>
>> AuthorDate: Mon Jul 24 00:38:34 2000 +0000
>> 
>>     (eldoc-display-message-no-interference-p): Don't interfere with edebug.
>> 
>> But it doesn't say in what way it interferes with edebug -- and removing
>> that line, I don't really see any interference?  But eldoc messages
>> things slightly different now than two decades ago...
>> 
>> Anybody know what this code is trying to do?
>
>AFAIK nowadays 'message' displays echo-area messages in a way that
>doesn't interfere with existing messages (it displays them in brackets
>at the end of the existing text), so I think the original problem
>should no longer exist.
>
>Noah, can you verify that your original problem cannot be reproduced
>if we remove the condition in eldoc-display-message-no-interference-p
>that you added?





  reply	other threads:[~2022-08-01  1:59 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 [this message]
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
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=20220731185949.978182.FMU217810@trabanten-schwein.prv.splode.com \
    --to=friedman@splode.com \
    --cc=56459@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --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.