Re: Eglot and Tramp

[João Távora]

On Fri, Jun 19, 2020 at 5:30 PM João Távora <joaotavora@gmail.com> wrote:
>
> On Fri, Jun 19, 2020 at 5:28 PM Michael Albinus <michael.albinus@gmx.de> 
> wrote:
> >
> > João Távora <joaotavora@gmail.com> writes:
> >
> > Hi João,
> >
> > >> No annoyance. But a user of Emacs 26.3 has Tramp 2.3.5 built-in. Because
> > >> of Eglot, Tramp 2.4.4 would be installed for her from GNU ELPA, w/o
> > >> having asked for.
> > >
> > > Well, this user did ask for Eglot.  He will also get an updated
> > > xref.el, project.el eldoc.el, flymake.el as already happens.  I'm
> > > afraid this is just how inter-package dependencies work.
> >
> > The point is that this Tramp upgrade is not mandatory. Only if a user
> > wants to apply Eglot remotely. I'm the last one who would say a Tramp
> > upgrade is bad :-) But a Tramp upgrade w/o a reason?
>
> Yes, but in that vein of thinking then Tramp shouldn't be bundled
> with Emacs too. There are lots of things we can do with Emacs
> that don't require Tramp.  But some of them do, and so we bundle
> Tramp.
>
> And the same thing if we substitute Tramp for any feature X.

Of course, we do take something similar in consideration regarding
the _loading_ of X.  For that, we have just-in-time "autoloads".  But
we don't have just-in-time "autoinstalls" yet.

João