From: Dmitry Gutov <dmitry@gutov.dev>
To: "João Távora" <joaotavora@gmail.com>
Cc: 62816@debbugs.gnu.org
Subject: bug#62816: 30.0.50; ElDoc blinks echo area when eldoc-documentation-compose is used
Date: Sat, 15 Apr 2023 04:03:16 +0300 [thread overview]
Message-ID: <38c5efc6-2b28-b09d-eef6-e9e8c97d7bbd@gutov.dev> (raw)
In-Reply-To: <ae9eb43d-b4ad-cbc7-88d3-212b4dffa1f3@gutov.dev>
On 14/04/2023 03:22, Dmitry Gutov wrote:
>>>> Another option is just to temporarily disable eldoc during the duration
>>>> of the Company completion session.
>>>
>>> Right.
>>>
>>> And yet another solution would be to detect that Eldoc will be used,
>>> and try to plug into its documentation functions to display the meta
>>> thingy alongside the other info.
>>>
>>> That's at least 3 potential solutions now.
>>
>> I think you should do the "bookkeeping" one, at least a very simple
>> version. Just record in your concept of a "company session" if there
>> was ever a non-nil :company-docsig sent from anywhere that required
>> echoing. Until there is, never clear on nil :company-docsig.
>> Eventually, if there is something to echo, tough luck: display it and
>> proceed as currently, clearing always on nil, risking flickering.
>> Suspect this should fix 95% of the cases, certainly Eglot usages.
>
> Yeah, that should be the most conservative solution. Maybe I'll start
> with it.
I've pushed a halfway-there solution which still seems to satisfy both
main scenarios (exemplified by Elisp and Eglot), so that seems addressed.
next prev parent reply other threads:[~2023-04-15 1:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 14:47 bug#62816: 30.0.50; ElDoc blinks echo area when eldoc-documentation-compose is used João Távora
2023-04-13 22:58 ` Dmitry Gutov
2023-04-13 23:23 ` João Távora
2023-04-13 23:37 ` Dmitry Gutov
2023-04-14 0:16 ` João Távora
2023-04-14 0:22 ` Dmitry Gutov
2023-04-15 1:03 ` Dmitry Gutov [this message]
2023-04-14 18:03 ` Dmitry Gutov
2023-04-14 18:09 ` João Távora
2023-04-14 18:53 ` Eli Zaretskii
2023-04-14 19:58 ` João Távora
2023-04-15 9:13 ` Eli Zaretskii
2023-04-15 11:04 ` João Távora
2023-04-15 11:40 ` 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=38c5efc6-2b28-b09d-eef6-e9e8c97d7bbd@gutov.dev \
--to=dmitry@gutov.dev \
--cc=62816@debbugs.gnu.org \
--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).