all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Re: cc-mode fontification feels random
Date: Sun, 6 Jun 2021 07:33:18 +0200	[thread overview]
Message-ID: <CAO48Bk-_3HqVb6LJJt1_k3Jt0fh-_UuuzDUbsmvAN2dLvMUGLA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]

> Then why use TRAMP at all?  Anyway, this is just an aside, but running
> the server remotely and also editing the files via TRAMP is still
> popular and predates LSP by many years: Many use the SLIME or SLY Common
> Lisp IDEs like that, pretty effectively.  Personally I prefer running an
> Emacs on the remote machine, but there's clearly a share of users who
> like to keep use one local Emacs for everything.

When you are dealing with Virtual Machines that have a very specific
purpose (Network Function Virtualisation comes to my mind where every
specific component and package needs to be certified, and, on top, every
byte counts), I've see the real advantage in TRAMP to access the VM and fix
configurations. Another example can be the different impersonation of
containers, where the environment is even tighter. In all these cases, I
can't see  emacs or LSP running on the target environment.

Best, /PA
-- 
Fragen sind nicht da um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler

[-- Attachment #2: Type: text/html, Size: 1339 bytes --]

                 reply	other threads:[~2021-06-06  5:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAO48Bk-_3HqVb6LJJt1_k3Jt0fh-_UuuzDUbsmvAN2dLvMUGLA@mail.gmail.com \
    --to=paaguti@gmail.com \
    --cc=emacs-devel@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.