Re: Problem with tramp/scp on NT Emacs

[Daniel Pittman]

On 14 Jun 2000, Glenn Proctor [EMAIL PROTECTED] wrote:

 Daniel Pittman [EMAIL PROTECTED] writes:
 
 On 14 Jun 2000, Glenn Proctor [EMAIL PROTECTED] wrote:
 
  Daniel Pittman [EMAIL PROTECTED] writes:

[...]

 That is not a good thing, I believe. Try giving the '-t' argument to
 ssh, which may help. If not, there was a hack floating around on the
 list that would let you get a terminal on the remote system, you
 could check the archives.
 
 I had already tried the -t argument with no success. I have discovered
 that I *can* use scp (but not ssh) from within an emacs shell buffer.

Joe Stoy has a version that does work, and has agreed to work with you
privately on this one. Unfortunately, you *do* need to be able to log in
to an interactive shell on the remote system for TRAMP to work - a
working scp on it's own is not enough

 Hrm. It looks like Emacs tries to run the child ssh process, which
 fails. Can you try running
 
 '(start-process "ssh-test" (current-buffer) "/ssh/ssh" "bacon" "-l"
 "glennp")'
 
 This gives me a similar backtrace to before.

Gah. That's not very good. This looks like a bug with 'start-process.'

Can you send me the output of 'M-x describe-function' for
'start-process'. I want to know if there are different arguments needed
for that version of Emacs.

 Is there anything in that needs to be set up at the remote end?

The backtrack is not while talking to the remote side, it's in the local
Emacs, which fails to create the child ssh process. :/

Daniel

-- 
Machina Improba! Vel Mihi Ede Potum Vel Mihi Redde Nummos Meos!

Re: Problem with tramp/scp on NT Emacs

[Daniel Pittman]

On 14 Jun 2000, Glenn Proctor [EMAIL PROTECTED] wrote:

 Daniel Pittman [EMAIL PROTECTED] writes:
 
 Can you run ssh as an Emacs subprocess and get an interactive shell
 on the remote system? If not, TRAMP will not work quite right, I
 fear.
 
 Hmm - when I try this I get "Pseudo-terminal will not be allocated
 because stdin is not a terminal." and it never returns to the shell
 prompt. :-(

That is not a good thing, I believe. Try giving the '-t' argument to
ssh, which may help. If not, there was a hack floating around on the
list that would let you get a terminal on the remote system, you could
check the archives.

[...]

 I set tramp-debug-buffer to t, but no *debug tramp...* buffer was
 generated. So it's not even getting as far as a remote call.

Gah. Not good. :/

  2. I get a "Spawning child process: invalid argument" error
 
 If you can reproduce this with the debug value set, then send both
 the '*debug tramp/...*' and '*tramp/...*' buffers to the list, that
 would be helpful.
 
 This occurs when trying /r@scp:user@host:file. There is no debug
 buffer (even with the tramp-debug-buffer variable set) but I've
 attached the backtrace below.

[...]

 To clarify: if I use /r@scp:hostname:filename I get the "hang"
 described above. If I use /r:hostname:filename I get the "instant
 return" instead. If I use /r@scp:user@host:filename I get the error
 shown below.

Hrm. It looks like Emacs tries to run the child ssh process, which
fails. Can you try running

'(start-process "ssh-test" (current-buffer) "/ssh/ssh" "bacon" "-l" "glennp")'

Do that in the *scratch* buffer, and use 'C-j' to run it. See what that
says

Daniel

-- 
A good poet is someone who manages, in a lifetime of standing out in
thunderstorms, to be struck by lightning five or six times; a dozen or two
dozen times and he is great.
-- Randall Jarrell