From: "João Távora" <joaotavora@gmail.com>
To: Robert Pluim <rpluim@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: eglot.el commentary suggestion
Date: Tue, 25 Oct 2022 12:00:53 +0100 [thread overview]
Message-ID: <CALDnm50aaEW3s4UG0=JLRwFruSD_XLaq1gvcQVm+f3NFs_fySw@mail.gmail.com> (raw)
In-Reply-To: <87h6zsp5sl.fsf_-_@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1735 bytes --]
Hi Robert, thanks for reading the commentary,
On Tue, Oct 25, 2022 at 11:16 AM Robert Pluim <rpluim@gmail.com> wrote:
> João> Yes. Be sure to read the commentary on the file's header able
compatibility
> João> with other Emacs versions, and design philosophy in general.
Happy to add
> João> clarifications. Grammar fixes welcome there, too ;-)
> I know we all laugh about how weʼre all pedants, but there are people
> who suffer from debilitating OCD and related syndromes, so perhaps we
> can tone down the humour:
Or we can turn it up to 11 with your other much better suggestion!
-;; of Emacs power users, but these users can use `eglot-stay-out-of'
-;; and `eglot-managed-mode-hook' to quench their OCD.
+;; of Emacs power pedants, but these users can use
+;; `eglot-stay-out-of' and `eglot-managed-mode-hook' to quench their
+;; debilitating OCD and related syndromes.
Then maybe add a heart emoji or fluffy ascii kitten to subdue the
hyperventilation.
I'd focus efforts on making eglot-stay-out-of and e-m-m-hook less necessary
in the first place. For example:
* If the default of eldoc-documentation-strategy were eldoc-d-compose Eglot
could
stop setting eldoc-documentation-strategy and tweak more ElDoc stuff.
* If Eglot supported multiple LSP servers simultaneously, less people would
need to
tweak flymake-diagnostic-functions to add e.g. a ESlint backend to it.
* If Emacs had a decent built-in TUI and GUI completion tooltip with less
baggage, Eglot could stop setting company-backends, etc.
* I _think_ Eglot can already stop setting xref-prompt-for-identifier, but
I'm not
100% sure.
--
João power pedant doctrinaire emeritus III
[-- Attachment #2: Type: text/html, Size: 2066 bytes --]
next prev parent reply other threads:[~2022-10-25 11:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-23 17:55 Minor bug in eglot; managed-major-mode must be a list Stephen Leake
2022-10-24 4:49 ` Theodor Thornhill
2022-10-24 8:54 ` Robert Pluim
2022-10-24 15:54 ` Philip Kaludercic
2022-10-24 16:16 ` Robert Pluim
2022-10-25 8:33 ` João Távora
2022-10-25 10:16 ` eglot.el commentary suggestion Robert Pluim
2022-10-25 11:00 ` João Távora [this message]
2022-10-25 11:16 ` Po Lu
2022-10-25 12:26 ` Robert Pluim
2022-10-25 12:51 ` João Távora
2022-10-25 13:18 ` Robert Pluim
2022-10-25 8:35 ` Minor bug in eglot; managed-major-mode must be a list João Távora
-- strict thread matches above, loose matches on Subject: below --
2022-10-25 12:59 eglot.el commentary suggestion Payas Relekar
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='CALDnm50aaEW3s4UG0=JLRwFruSD_XLaq1gvcQVm+f3NFs_fySw@mail.gmail.com' \
--to=joaotavora@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=rpluim@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).