unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "João Távora" <joaotavora@gmail.com>
Cc: 61312-done@debbugs.gnu.org, skykanin@proton.me
Subject: bug#61312: Patch for eglot: scala LSP binary name
Date: Thu, 09 Feb 2023 12:18:12 +0200	[thread overview]
Message-ID: <83bkm3m9az.fsf@gnu.org> (raw)
In-Reply-To: <CALDnm52shKMawVe3+UPiVXjrzFM+kti9cMUc=WWLE56frOO2Ag@mail.gmail.com> (message from João Távora on Mon, 6 Feb 2023 18:45:39 +0000)

> From: João Távora <joaotavora@gmail.com>
> Date: Mon, 6 Feb 2023 18:45:39 +0000
> Cc: skykanin <skykanin@proton.me>, 61312@debbugs.gnu.org
> 
> As usual, I defer this decision to you. I think it's reasonable to
> support both names, and I also think it's reasonable to stick to 
> just the one we think is most used or representative of the 
> program.
> 
> In this case, I think "metals-emacs" is a contradiction of LSP's
> stated goal, which is to have editor-agnostic servers. But I 
> don't know what the reasons were for doing this, I haven't
> investigated.
> 
> It would be even more reasonable, I think, if distributions 
> settled -- or mostly settled - on names for their binaries they 
> distribute, much like *nix toolchains do. Of course we do not 
> control that process, but maybe we could influence it instead
> of being constantly influenced by it.

Thanks, I went with supporting both names in Emacs 29.  I cannot see
any harm in supporting both, once "metals" is the first name to check.

With that, I'm closing this bug.





      reply	other threads:[~2023-02-09 10:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-05 21:15 bug#61312: Patch for eglot: scala LSP binary name skykanin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-06 15:46 ` Eli Zaretskii
2023-02-06 18:45   ` João Távora
2023-02-09 10:18     ` Eli Zaretskii [this message]

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=83bkm3m9az.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=61312-done@debbugs.gnu.org \
    --cc=joaotavora@gmail.com \
    --cc=skykanin@proton.me \
    /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).