Re: [PATCH] Provide completion candidates for remote containers over a TRAMP connection

[Michael Albinus]

Gene Goykhman <gene@indigo1.com> writes:

> Hi Michael,

Hi Gene,

>> For the futere I could imagine more different values. t and nil are fine
>> ATM, but if there are more methods which support this feature, it could
>> be a list. '("docker" "podman" "kubernetes") would enable this for the
>> respective methods, and disable it for all other methods in multi-hop
>> completions. WDYT?
>
> I think this is a great idea. What about calling the variable
> `tramp-completion-multi-hop-methods', with a default of '("docker"
> "podman")? I am not confident including "kubernetes" here as I have
> not tested it but could do so if you are comfortable with that.

Sounds OK to me.

>> What you could perhaps contribute is documentation of
>> tramp-completion-remote-containers (with its changed name) in
>> tramp.texi. Maybe in node "Ad-hoc multi-hops"?
>
> I'll get started on this and an addition to etc/NEWS about the new user 
> option.

Thanks. I will study in parallel, how we could pimp up
tramp-kubernetes--completion-function for this feature. Shouldn't be a
problem, but I'm uncertain whether the other tramp-kubernetes--*
functions will need also some love.

Best regards, Michael.