From: Kai.Grossjohann@CS.Uni-Dortmund.DE (K. ) - 2001-11-20 21:14:04
|
Mike Hardy <mh...@al...> writes: > Got the latest out of CVS about two hours ago and sure enough the > compression/load order msg works. But I still see the same tmp save > behavior I have w/previous revs. I'm going to look at the post that > explains bug submission and file all the data it requests. I also > double-checked tmp vars (Emacs 21.0.102/tramp) you mention and they're > OK. I notice you tried it on what I'll assume is a straight text file; > I'm using an EDA mode so I guess we'll see if that's interfering when I > file this. Hm. Emacs 21.0.102... Hm. Do you think it might be possible that the problem just Goes Away with Emacs 21.1? Hm. Far shot. Can you tell me (again) what exactly is the message that you get when it is doing the `tmp save'? I wonder whether it is autosave. > I notice 'tramp sh program' (customize-group) says it is not used for > remote commands - how come I always have a ~/.sh_history filled w/tramp > cmds on the remote (on the remote I use tcsh)? It also appears to > contain the compressed file (encoded) I transfer each time I read/save > it(?). I've tried (setq tramp-debug-buffer t/nil) - no effect on > this file... Tramp also wants a Bourne-ish shell on the remote host. It says "exec /bin/sh" for a first approximation, then looks if that shell groks tilde expansion. If not, it tries to start a shell (ksh or bash) which does. So that's where your .sh_history file comes from. But Tramp tries to write to a different file .tramp_history or somesuch and to keep that file small. So I wonder why that doesn't work for you. Do you want to find out how to configure the history for the (Bourne-ish) shell on the remote end, then tell me so that I can change Tramp? Of course, Tramp being pretty configurable, it doesn't always do "exec /bin/sh" -- you can set the tramp-remote-sh method parameter for the method you use. (See the variable tramp-methods.) kai -- Simplification good! Oversimplification bad! (Larry Wall) |