From: Michael Albinus <michael.albinus@gmx.de>
To: t@fullmeta.me
Cc: help-gnu-emacs@gnu.org, Manuel Giraud <manuel@ledu-giraud.fr>
Subject: Re: local emacsclient to remote emacs server
Date: Thu, 24 Mar 2022 19:46:12 +0100 [thread overview]
Message-ID: <87ee2rjiiz.fsf@gmx.de> (raw)
In-Reply-To: <3bdba293-340f-4b3f-8d86-8be0d19a9c1c@www.fastmail.com> (t.'s message of "Thu, 24 Mar 2022 10:01:32 +0000")
t@fullmeta.me writes:
Hi,
> Now, do you see the problem with TRAMP? TRAMP is essentially an SSH
> session spawned from local Emacs already running. It ends up talking
> to your login shell over ssh basically. But we need this Guix induced
> or potentially even containerized environment. There needs to be some
> kind of "hop" or additional step after TRAMP establishes an ssh
> connection that puts its shell in appropriate environment. Is there a
> way to do that?
Tramp does not support this (yet). But your use case is not the only
one; Python developers have asked also for Tramp support of virtual
environments.
I have no idea what the best solution will be. Maybe some additional
configuration means for SSH based Tramp methods. Or maybe an additional
"environment hop" for Tramp (interesting idea, btw).
I'm willing to work on that. However, I'm neither a Guix or Python user,
so I need support in order to understand what is needed.
In order to track this, it might help if you could write en Emacs bug.
Best regards, Michael.
next prev parent reply other threads:[~2022-03-24 18:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 16:15 local emacsclient to remote emacs server t
2022-03-21 18:22 ` Eric S Fraga
2022-03-21 20:31 ` Manuel Giraud
2022-03-22 15:22 ` Robert Pluim
2022-03-22 16:03 ` Felix Dietrich
2022-03-22 23:06 ` t
2022-03-23 11:55 ` Manuel Giraud
2022-03-24 10:01 ` t
2022-03-24 18:46 ` Michael Albinus [this message]
2022-03-27 3:58 ` Felix Dietrich
2022-03-24 10:09 ` Robert Pluim
2022-03-24 12:32 ` Robert Pluim
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=87ee2rjiiz.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=help-gnu-emacs@gnu.org \
--cc=manuel@ledu-giraud.fr \
--cc=t@fullmeta.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 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.