From: Michael Albinus <michael.albinus@gmx.de>
To: "João Távora" <joaotavora@gmail.com>
Cc: felipelema@mortemale.org,
Tobias Rittweiler <trittweiler@gmail.com>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: Eglot and Tramp
Date: Fri, 19 Jun 2020 18:28:29 +0200 [thread overview]
Message-ID: <87366r10lu.fsf@gmx.de> (raw)
In-Reply-To: <CALDnm5398FciOKMWTuXuGRF+sY2C9Y2Kjo=LHh0cGJNkrj-Syw@mail.gmail.com> ("João Távora"'s message of "Fri, 19 Jun 2020 17:18:27 +0100")
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?
> As long as Tramp 2.4.4 is (mostly) backward compatible to 2.3.5's uses...
> there should be no (little) problem.
It's backward compatible.
> João
Best regards, Michael.
next prev parent reply other threads:[~2020-06-19 16:28 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87y2oocltq.fsf@gmail.com>
[not found] ` <87pn9v19e8.fsf@gmx.de>
2020-06-19 13:23 ` Eglot and Tramp João Távora
2020-06-19 13:44 ` Michael Albinus
2020-06-19 14:09 ` João Távora
2020-06-19 14:43 ` Michael Albinus
2020-06-19 14:45 ` João Távora
2020-06-19 14:54 ` Michael Albinus
2020-06-19 16:18 ` João Távora
2020-06-19 16:28 ` Michael Albinus [this message]
2020-06-19 16:30 ` João Távora
2020-06-19 16:32 ` João Távora
2020-06-19 16:39 ` Michael Albinus
2020-06-19 16:45 ` João Távora
2020-06-19 17:30 ` Michael Albinus
2020-06-19 17:36 ` João Távora
2020-06-19 17:47 ` Dmitry Gutov
2020-06-19 18:01 ` Michael Albinus
2022-11-14 8:20 eglot and tramp Pedro Andres Aranda Gutierrez
2022-11-15 1:18 ` Brian Cully via Emacs development discussions.
2022-11-15 15:33 ` Michael Albinus
2022-11-15 17:45 ` Brian Cully via Emacs development discussions.
2022-11-15 19:46 ` Michael Albinus
2022-11-16 12:29 ` Brian Cully via Emacs development discussions.
2022-11-16 16:14 ` Michael Albinus
2022-11-18 15:51 ` Michael Albinus
2022-11-19 16:24 ` Brian Cully via Emacs development discussions.
2022-11-20 13:50 ` Michael Albinus
2022-11-21 11:51 ` Brian Cully via Emacs development discussions.
2022-11-21 12:11 ` Michael Albinus
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=87366r10lu.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=emacs-devel@gnu.org \
--cc=felipelema@mortemale.org \
--cc=joaotavora@gmail.com \
--cc=trittweiler@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).