On 04 Mar 2001, Kai Großjohann wrote:

[...]

> Tramp is quite anal about having all kinds of method parameters.
> Don't let any of them default to anything.  Specify them all.  So just
> add (tramp-rcp-args nil) into the method spec, and you should be all
> set.  Look at the other methods so you're sure you're not missing
> anything that should be set to nil.
> 
> I agree that this is not nice, but OTOH you don't add a new method
> every day, so maybe it's not too bad.

On the topic of connection methods and their definitions, I want to see
what people think of one of my plans for the tramp2 code.

By default, I want this to have as much automatic configuration as
possible. So, my plan is that, by default, the method for encoding and
decoding files on the remote machine will be auto-detected.

It will be possible to override this in connection definitions but, by
default, all the detection will be automatic.

This, of course, presumes that I don't find any real problems getting
reliable detection of encoding methods remotely working.

        Daniel

-- 
You call this paradise      |    Just take my hand girl
You call these mountains    |    Just take my hand girl
We call this poverty        |    I'll take your tears girl
We call these hills         |    Step aside
        -- Jams Ray and The Performance, _Mountain Voices_

Reply via email to