Re: tramp

[Kim F. Storm]

Miles Bader <address@hidden> writes:

> Since there definitely are parameters which will have to be host/method
> specific, and that you're better off simply making a general mechanism by
> which _all_ parameters can be set on a host/method specific manner.
> 
> E.g., just an alist containing machine/method/user specs, and variables
> and values, which tramp will run down and do
>   (set (make-local-variable VAR) val)
> inside the tramp work buffer.  Then the code can use simple variables,
> but the user still gets max flexibility where needed.
> 
> An example format might be:
> 
>   ((SPEC (VAR . VAL) ...) ...)
> 
> where SPEC is either a regexp matching the hostname, or a tuple like
> (HOST USER METHOD) where the components are regexps or nil (meaning
> match anything).
> 
> That's what I want.
> 

So do I.

I have actually very few remote machines I connect to, so I would
like to be able to configure tramp for each of those with the
optimal set of parameters (and faster connect times).

-- 
Kim F. Storm <address@hidden> http://www.cua.dk