unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Philip Kaludercic" <philipk@posteo.net>,
	"João Távora" <joaotavora@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Externalising 'eglot-server-programs'
Date: Thu, 18 Jul 2024 08:04:38 +0300	[thread overview]
Message-ID: <861q3rgujd.fsf@gnu.org> (raw)
In-Reply-To: <87msmffyjz.fsf@posteo.net> (message from Philip Kaludercic on Wed, 17 Jul 2024 22:23:12 +0000)

> From: Philip Kaludercic <philipk@posteo.net>
> Date: Wed, 17 Jul 2024 22:23:12 +0000
> 
> 
> I have been wondering why all the language servers are currently listed
> in 'eglot-server-programs'?  Isn't it usually the responsibility of a
> major mode to integrate and configure generic functionality (Imenu,
> CAPF, Xref, Outline, Font-Lock, ...) for a language?  Would it be
> imaginable to move towards the expectation that major modes and their
> packages update 'eglot-server-programs', just like they update
> 'auto-mode-alist'?

We should keep in mind that Eglot is also available from ELPA, so it
cannot necessarily rely on what major modes in core do, because
3rd-party major modes might not do that.

Also, I don't see what possible harm could be caused by having all the
known servers listed in that variable.

Adding João to the discussion.



  reply	other threads:[~2024-07-18  5:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-17 22:23 Externalising 'eglot-server-programs' Philip Kaludercic
2024-07-18  5:04 ` Eli Zaretskii [this message]
2024-07-18  7:52   ` João Távora
2024-07-18 10:41   ` Philip Kaludercic

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=861q3rgujd.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=joaotavora@gmail.com \
    --cc=philipk@posteo.net \
    /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).