Re: Renaming eglot -- or at least add an alias?

[Eli Zaretskii]

> From: Richard Stallman <rms@gnu.org>
> Cc: emacs-devel@gnu.org
> Date: Wed, 05 Oct 2022 17:35:26 -0400
> 
>   > Eglot doesn't parse code.  It is a client of a protocol designed to
>   > allow applications to send requests about source code and receive
>   > results.  The server which responds to the requests does parse the
>   > code, but Eglot doesn't.
> 
> That's true, but it consists of implementation details.  Users don't
> need to know about them or think in those terms.  For users, the
> simple description of the package's job is to causes various Emacs
> features to work by parsing code.

I think from user's POV Eglot will be related to the features it
enables.  They won't care about code parsing that is the basis of
that.

>   > But it's too early and premature to discuss what we will say in our
>   > menus, because we have no idea what these menus will be and which
>   > features they will activate.  We should delay this discussion until
>   > after the merge, at which point we will be able to talk about concrete
>   > commands, variables, doc strings, and menu items.
> 
> If users ask at some point to "use this package", it is important
> what we call the package.

The name must be Eglot, because that's how the package was called
since 2017.  We cannot possibly rewrite history or change people's
memories.

> How to deal with Eglot and Semantic is not clear to me.
> 
> Is there any programming language which is supported both by Eglot and
> by Semantic?

Yes.