unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Artem Smushkov <artyom.smushkov@gmail.com>
Cc: 74219@debbugs.gnu.org
Subject: bug#74219: 29.4; TRAMP uses the same ad-hoc proxy for every docker container on remote hosts
Date: Sat, 09 Nov 2024 10:40:37 +0100	[thread overview]
Message-ID: <87fro0d9t6.fsf@gmx.de> (raw)
In-Reply-To: <87msiaev7g.fsf@gmx.de> (Michael Albinus's message of "Thu, 07 Nov 2024 19:48:35 +0100")

Michael Albinus <michael.albinus@gmx.de> writes:

Hi Artem,

> That's not possible with Tramp. Not with the current design. The proxy
> definitions are kept internally, and they apply in reverse order of
> their appearance in the remote file names.

I've checked the implementation, and it looks like adding this feature
is not as expensive as I thought. So I have implemented it. Pushed to
both Emacs and Tramp git repo, master branch.

The Tramp manual has a new subsection "5.4.1 Using different proxies for
the same destination" which explains this. In short, you must set
tramp-show-ad-hoc-proxies to t.

Do you have a chance to test it?

Best regards, Michael.





  reply	other threads:[~2024-11-09  9:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-05 17:34 bug#74219: 29.4; TRAMP uses the same ad-hoc proxy for every docker container on remote hosts Artem Smushkov
2024-11-07 18:48 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-09  9:40   ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-11-11 10:51     ` Artem Smushkov
     [not found]     ` <CAM9Mw788gEhN+kTv1pS1kLknV1fJgxSCoXK+488sgococXEobQ@mail.gmail.com>
2024-11-29 12:27       ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=87fro0d9t6.fsf@gmx.de \
    --to=bug-gnu-emacs@gnu.org \
    --cc=74219@debbugs.gnu.org \
    --cc=artyom.smushkov@gmail.com \
    --cc=michael.albinus@gmx.de \
    /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).