Re: loads but won't save? was: plink and tramp-2.0.2.1: more progress
On 04 Mar 2001, Kai Großjohann wrote: > On 04 Mar 2001, Daniel Pittman wrote: > >> 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. > > That's a good idea. But I think you might not be able to > automatically detect whether you should do inline or out of band > transfer. Hrm. Good point. I will have to think a little more on that... > Well, with multi-hop methods you automatically do inline. Which makes the auto-detection a lot more useful, I guess, especially since one of the main points of the new design is to make connecting multiple hops easy - so that ssh and su connections work. :) > And this reminds me of the todo item which was sent to me by Michael > Kifer: use out of band transfer for large files and inline transfer > for small files. Worth thinking about... which I will do. I don't know how easy or practical it will be, though. Is this really going to be /that/ much more efficient? Daniel -- I hold on to the blissful notion that the journey is worthwhile, and I tip-toe across the chasm with a song and a smile. -- Harry Chapin
Re: loads but won't save? was: plink and tramp-2.0.2.1: more progress
On 04 Mar 2001, Daniel Pittman wrote: > 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. That's a good idea. But I think you might not be able to automatically detect whether you should do inline or out of band transfer. Well, with multi-hop methods you automatically do inline. And this reminds me of the todo item which was sent to me by Michael Kifer: use out of band transfer for large files and inline transfer for small files. kai -- Be indiscrete. Do it continuously.
Re: loads but won't save? was: plink and tramp-2.0.2.1: more progress
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_
Re: loads but won't save? was: plink and tramp-2.0.2.1: more progress
On Sat, 03 Mar 2001, Tom Roche wrote: > When I try to _save_ the buffer, I get the error > >> Method `t' didn't specify tramp args > > which appears to be caused by tramp's desire to call > tramp-rcp-program in order to save the backup file > > /r@t:[EMAIL PROTECTED]:/ncsu/tlroche/.emacs~ > > Any ideas how to fix this? FWIW I tried setting He he, that's a fun typo. It should have been ``didn't specify rcp args''. When I renamed rcp.el into Tramp, I made one substitution too many... 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. kai -- Be indiscrete. Do it continuously.
loads but won't save? was: plink and tramp-2.0.2.1: more progress
[EMAIL PROTECTED] 03 Mar 2001 12:27:10 +0100
> Your method specifies neither encoding/decoding command/function,
> nor rcp-command. You must specify exactly one of those.
Doh! And you had mentioned that earlier. Anyway, I now have in _emacs
(setq tramp-methods
(append
(list
'("t" ; basically ssh with mimencode
; (tramp-connection-function tramp-open-connection-rsh)
(tramp-connection-function HACKED-tramp-open-connection-rsh)
(tramp-rsh-program "plink")
; commenting this out annoys tramp-1.449. It should instead be nil:
; (tramp-rcp-program "pscp")
(tramp-rcp-program nil)
; [EMAIL PROTECTED] 01 Mar 2001 23:55:50 +0100
; > Compare the other methods: they _either_ have rcp-program and
; > rcp-args, _or_ they have encoding and decoding commands/functions,
; > but never both.
(tramp-remote-sh"/bin/sh")
(tramp-rsh-args ; note that each word must be separate!
(
; This may cause buffering problems. Note that in *shell*
; the verbose reports follow logout ...
; "-v"
; don't really wanna do this
; note that options must be separate words!
"-pw" "password"
"-ssh"
))
(tramp-rcp-keep-date-arg"-p")
(tramp-su-program nil)
(tramp-su-args nil)
(tramp-encoding-command "mimencode -b")
(tramp-decoding-command "mimencode -u -b")
(tramp-encoding-functionbase64-encode-region)
(tramp-decoding-functionbase64-decode-region)
(tramp-telnet-program nil))
)
tramp-methods)
) ; end (setq tramp-methods
> Does this help?
Yes! I do C-x C-f /r@t:[EMAIL PROTECTED]:.emacs
and am now thrilled to report: I can load the file! But ...
When I try to _save_ the buffer, I get the error
> Method `t' didn't specify tramp args
which appears to be caused by tramp's desire to call tramp-rcp-program
in order to save the backup file
/r@t:[EMAIL PROTECTED]:/ncsu/tlroche/.emacs~
Any ideas how to fix this? FWIW I tried setting
(tramp-rcp-keep-date-arg nil)
but that made no difference. I copied the contents of *Backtrace* to
http://www4.ncsu.edu/~tlroche/tramp/backtrace_buffer.txt
(though much bytecode does not display identically) and the relevant
portion of my _emacs to
http://www4.ncsu.edu/~tlroche/tramp/_emacs.txt
Approaching success (hopefully not asymptotically), [EMAIL PROTECTED]
