From: "João Távora" <joaotavora@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 43103@debbugs.gnu.org, larsi@gnus.org, monnier@iro.umontreal.ca
Subject: bug#43103: 28.0.50; Default ElDoc composition strategy in Elisp mode (eldoc-documentation-strategy)
Date: Sun, 30 Aug 2020 16:15:21 +0100 [thread overview]
Message-ID: <878sdwi2ra.fsf@gmail.com> (raw)
In-Reply-To: <83blisxl9o.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 30 Aug 2020 17:26:27 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: João Távora <joaotavora@gmail.com>
>> Cc: 43103@debbugs.gnu.org, larsi@gnus.org, monnier@iro.umontreal.ca
>> Date: Sat, 29 Aug 2020 21:13:31 +0100
>>
>> I will agree with you that displaying the transient error
>> on those situations is alarmist and not very useful, but it's better
>> fixed by adjusting 'flymake-no-changes-timeout'
>
> If we are okay with a large timeout (like 1 sec at least), then maybe
> it's fine.
I'm okay with a 1 sec timeout for flymake-no-changes-timeout, though
before changing that default I'd first pay attention to the feedback of
Flymake+ElDoc users (as you know, Flymake isn't on by default).
Personally, as a Flymake user, I'm not very bothered by the alarmist
messages. They're very similar to what until very recently happened
with the "add a quote" situation (the one that
`jit-lock-antiblink-grace` fixed). Other modes (and other editors,
IIRC) will visually annotate the transient erroneous state as the user
is typing "new code". Though, granted, we shouldn't compare ourselves
with those inferior kind.
>> Anyway, from your statement, it seems you'd be OK (or at least find less
>> problematic) that the two Flymake-unrelated lines:
>>
>> eldoc-idle-delay: Number of seconds of idle time to wait before printing.
>> run-with-idle-timer: (SECS REPEAT FUNCTION &rest ARGS) [SECS is boldface]
>>
>> Being shown when point hovers on the second atom of the form
>>
>> (run-with-idle-timer eldoc-idle-delay nil ...)
>>
>> ?
>
> Expect annoying users due to resizing of mini-window.
Yes, and this is why I mentioned eldoc-echo-area-use-multiline-p in my
original message. It is the current way to control this (at least
before I propose a overhaul of the ElDoc display system).
Its default and original value is `truncate-sym-name-if-fit`, which (but
for one detail) basically amounts to `t` or "yes, do use multiple
lines". So we could
1. greet these annoyed users with this fact and tell
them to set eldoc-echo-area-use-multiline-p to nil or 1
2. set it to such a value by default in emacs-lisp-mode
3. wait for the aforementioned overhaul to somehow give us better
perspective before doing the work of this bug report (i.e. switch to
eldoc-documentation-compose in emacs-lisp-mode).
At any rate, as I wrote earlier:
- the Flymake Eldoc source is last in the list, so it will be the one
edited out if eldoc-echo-area-use-multiline-p is set to nil. In
practice this would amount to no immediately visible change in
behaviour;
- even if eldoc-echo-area-use-multiline-p is set to nil, users can still
get to all the info collecte by ElDoc with the new
`eldoc-documentation-compose` strategy by pressing M-x eldoc-doc-buffer
Hope this clarifies things,
João
next prev parent reply other threads:[~2020-08-30 15:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-29 15:36 bug#43103: 28.0.50; Default ElDoc composition strategy in Elisp mode (eldoc-documentation-strategy) João Távora
2020-08-29 15:58 ` Eli Zaretskii
2020-08-29 16:07 ` João Távora
2020-08-29 18:17 ` Eli Zaretskii
2020-08-29 20:13 ` João Távora
2020-08-30 14:26 ` Eli Zaretskii
2020-08-30 15:15 ` João Távora [this message]
2020-08-31 1:07 ` Dmitry Gutov
2020-08-31 8:38 ` João Távora
2020-08-31 20:03 ` Dmitry Gutov
2020-08-31 20:25 ` João Távora
2020-08-31 20:48 ` Dmitry Gutov
2020-08-31 21:12 ` João Távora
2020-08-31 21:20 ` Dmitry Gutov
2020-08-31 22:50 ` João Távora
2020-09-01 10:52 ` Dmitry Gutov
2020-09-01 11:11 ` João Távora
2020-09-01 11:23 ` Dmitry Gutov
2020-08-31 0:47 ` 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=878sdwi2ra.fsf@gmail.com \
--to=joaotavora@gmail.com \
--cc=43103@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
/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).