From: Dmitry Gutov <dmitry@gutov.dev>
To: "João Távora" <joaotavora@gmail.com>
Cc: 62029@debbugs.gnu.org, Yuan Fu <casouri@gmail.com>
Subject: bug#62029: 29.0.60; Allow users to customize eldoc buffer separator
Date: Thu, 13 Apr 2023 03:20:19 +0300 [thread overview]
Message-ID: <6c64f601-0c28-2993-e55a-042419e1623e@gutov.dev> (raw)
In-Reply-To: <87v8i1jr5v.fsf@gmail.com>
On 12/04/2023 14:06, João Távora wrote:
>>> elisp-mode.el. Do you have something to say about that? Did you try
>>> the patch I showed Yuan?
>> I have applied it. What should I be looking at?
> Right. That's a good sign it itself. Here, have some more patch:
>
> (setq-default eldoc-documentation-strategy 'eldoc-documentation-compose)
> (add-hook 'emacs-lisp-mode-hook
> (lambda () (setq-local eldoc-echo-area-use-multiline-p 1)))
>
> Then go on with elisp your life and maybe peek into M-x eldoc-doc-buffer
> once in a while.
What is the reason to have a special value for Elisp again?
One obvious downside is that if the user customizes it to some different
value (e.g. 2, limiting the height of the window below), it won't be
honored by Elisp without some extra work on the part of the user. So if
we want to do that, we'd need some strong argument for why Elisp is
different from everyone else.
And the thing with window jumping/blinking seems common enough across
the modes. It's easiest to reproduce when just using Eglot with Company
(for some reason or other, the blinking seems absent without the latter;
but I only tested one simple scenario in one configuration).
But in Elisp -- even if I just move the cursor with arrows or C-f/C-b, 1
times out of 2 the echo are window will blink.
It's trivially reproduced even with 'emacs -Q': just add somewhere
inside an Elisp buffer:
(remove-hook asd)
when flymake-mode is enabled and eldoc-documentation-strategy is
'eldoc-documentation-compose, and eldoc-echo-area-use-multiline-p is not
1, and move around 'asd' with C-f and C-b.
Is that bug Elisp-specific? That would seem odd.
next prev parent reply other threads:[~2023-04-13 0:20 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 7:56 bug#62029: 29.0.60; Allow users to customize eldoc buffer separator Yuan Fu
2023-03-08 0:25 ` bug#62030: " Yuan Fu
2023-03-08 17:14 ` bug#62029: " João Távora
2023-03-08 21:28 ` Yuan Fu
2023-03-23 21:33 ` João Távora
2023-03-24 0:12 ` Yuan Fu
2023-03-24 17:44 ` João Távora
2023-03-25 3:04 ` Yuan Fu
2023-03-25 8:10 ` João Távora
2023-03-30 5:22 ` Yuan Fu
2023-03-30 8:13 ` João Távora
2023-03-30 8:25 ` Yuan Fu
2023-04-11 0:04 ` Dmitry Gutov
2023-04-11 11:25 ` João Távora
2023-04-12 1:38 ` Dmitry Gutov
2023-04-12 11:06 ` João Távora
2023-04-13 0:20 ` Dmitry Gutov [this message]
2023-04-13 4:20 ` Yuan Fu
2023-04-13 9:50 ` João Távora
2023-04-13 10:11 ` João Távora
2023-04-13 10:48 ` João Távora
2023-04-13 21:53 ` Dmitry Gutov
2023-04-13 22:13 ` Dmitry Gutov
2023-04-13 23:01 ` João Távora
2023-04-13 23:26 ` Dmitry Gutov
2023-04-14 0:04 ` João Távora
2023-04-14 23:50 ` Dmitry Gutov
2023-04-15 9:41 ` João Távora
2023-10-23 1:39 ` Dmitry Gutov
2023-04-18 0:47 ` Dmitry Gutov
2023-04-18 11:17 ` João Távora
2023-04-18 23:05 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6c64f601-0c28-2993-e55a-042419e1623e@gutov.dev \
--to=dmitry@gutov.dev \
--cc=62029@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=joaotavora@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).