GNU bug report logs - #43103
28.0.50; Default ElDoc composition strategy in Elisp mode (eldoc-documentation-strategy)

Previous Next

Package: emacs;

Reported by: João Távora <joaotavora <at> gmail.com>

Date: Sat, 29 Aug 2020 15:38:01 UTC

Severity: normal

Found in version 28.0.50

Full log


Message #50 received at 43103 <at> debbugs.gnu.org (full text, mbox):

From: João Távora <joaotavora <at> gmail.com>
To: Dmitry Gutov <dgutov <at> yandex.ru>
Cc: 43103 <at> debbugs.gnu.org, larsi <at> gnus.org, monnier <at> iro.umontreal.ca
Subject: Re: bug#43103: 28.0.50; Default ElDoc composition strategy in Elisp
 mode (eldoc-documentation-strategy)
Date: Mon, 31 Aug 2020 23:50:12 +0100
Dmitry Gutov <dgutov <at> yandex.ru> writes:

> On 01.09.2020 00:12, João Távora wrote:
>> Dmitry Gutov <dgutov <at> yandex.ru> writes:
>> 
>>> On 31.08.2020 23:25, João Távora wrote:
>>>
>>>>>>> These is definite wisdom in that.
>>>>>> I see only signs of rudimentary intial design which predates
>>>>>> eldoc-...-multiline-p, composition, Flymake...
>>>>> That doesn't mean the initial design didn't get something right.
>>>>> If it didn't, this aspect would have likely changed by now.
>>>> It couldn't change because there weren't the tools for it to change.
>>>> There are now.
>>> I don't think so. It still uses the echo area.
>> The echo area is not one of the new tools.
> You're making my point here.

If you say so, I really have no clue what your point is.  The echo area
has been there from ElDoc's first design, it is not one of the new tools
that ElDoc offers now.

For your benefit, and to wrap up this exchange, here's a summary of what
I propose: In Elisp mode, I've experimented with the
`eldoc-documentation-compose` strategy and I like the results: it's
useful to have Elisp function signatures, Elisp variable documentation
and Elisp diagnostics displayed somewhere, constantly updated.  I think
other people would like these things, hence my proposal.  I don't mind
the echo area jumping in height one or two lines once in a while, but if
others do, there are tools to control it, which we can leverage to good
effect.  That's it.

>>> One particular way it's unfortunate, is I actually *would* like a
>>> generic "show documentation" feature with an existing key
>>> binding. Shame it doesn't really work for that purpose.
>> Try M-x eldoc and global-set-key and tell us what's missing.
>
> Already told you. I'm not sure how many different ways I can explain
> things, if you keep snipping those explanations out.

You said you wished for a command to "show documentation" and I pointed
you to M-x eldoc, a new command which seems to do what you want, and
that you might not be aware of since it wasn't discussed.  If you don't
wish to pursue this suggestion, fine.  I am in no obligation to waste my
time replying to every new off-topic point you bring up, I do so only
where I think I can add value.  Bickering with you is not one of those
things.

João




This bug report was last modified 4 years and 347 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.