[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#31749: 26.1; Improve eldoc message commands heuristic

From: Noam Postavsky
Subject: bug#31749: 26.1; Improve eldoc message commands heuristic
Date: Wed, 13 Jun 2018 20:10:25 -0400
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)

severity 31749 wishlist

Carlos Pita <address@hidden> writes:

> The current criterion essentially removes the echo area message after
> any command not whitelisted in eldoc-message-commands.
> This is problematic since the list of relevant commands is unknown in
> advance for evert possible extension package. One could argue that
> extension package maintainers are responsible then, but I have had many
> problems with eldoc behaving suboptimally in conjunction with company
> mode, elpy mode and others (which are all quality extensions) that I
> wouldn't put the burden of this on the maintainers.
> Now, I might be completely wrong, but why don't you just check if
> (current-message) is nil or not? This way if any command has written to
> the echo area eldoc won't override its message. You can still keep the
> whitelist in order to force override by eldoc (although I don't see much
> value in this). You have probably thought many times about this
> alternative and rejected for reasons I'm unable to see, but it's worth
> to intent ;)

Not sure if anybody's considered this, perhaps you can try it out and
see if there are any drawbacks?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]