From: "João Távora" <joaotavora@gmail.com>
To: Dmitry Gutov <dgutov@yandex.ru>
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: Tue, 01 Sep 2020 12:11:37 +0100 [thread overview]
Message-ID: <87mu29iweu.fsf@gmail.com> (raw)
In-Reply-To: <cbd83df6-8af5-7e98-b2ec-752ee8bc1d4c@yandex.ru> (Dmitry Gutov's message of "Tue, 1 Sep 2020 13:52:00 +0300")
Dmitry Gutov <dgutov@yandex.ru> writes:
>> 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,
>
> I mind. Unfortunately.
>
>> but if
>> others do, there are tools to control it, which we can leverage to good
>> effect. That's it.
>
> What tools?
eldoc-echo-area-use-multiline-p, as I mentiond at least 3 times in this
thread.
>> 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.
> And I told you its semantics are broken.
I think you are still confusing M-x eldoc and M-x eldoc-doc-buffer,
which are two different commands. For the record, both commands and
surrounding functionality can and probably will be improved.
> Showing the text intended to be displayed in the echo area (one line,
> usually; maybe a few) in a full-size window is ridiculous.
This is not true in the generality of ElDoc usage, of course: LSP users
are confronted with very verbose at-point documentation. And a window
and buffer in Emacs are not the same thing, something I assumed you
knew.
>> 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.
>
> If you try actually reading what I wrote, you might find some
> actionable suggestions there.
I told you at least once that it's rude to accuse other people of not
reading your emails. It's a lie and a disrespect for the precious time
they invest in reading them and replying to them as they see fit. Not
to mention wholly unproductive. Because I don't have time for this, I'm
putting you in my ignore list, joined by very few, if anyone. So now
you'll _know_ that I won't be reading what you write, and the reason why
I won't.
João
next prev parent reply other threads:[~2020-09-01 11:11 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
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 [this message]
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=87mu29iweu.fsf@gmail.com \
--to=joaotavora@gmail.com \
--cc=43103@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--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).