On Wed, 28 Feb 2001, Tom Roche wrote:
> Bill Pringlemeir <[EMAIL PROTECTED]> 28 Feb 2001 13:43:25
>>> However, you can use the "-pw secret" option to allow plink to
>>> connect. This worked on my NTEmacs 20.7.3.
>
> [EMAIL PROTECTED] Wed, 28 Feb 2001 16:30:10 -0500
>> And for me on GNU Emacs 20.7.1 (i386-*-nt5.0.2195).
>
> I.e. in GNU Emacs 20.7.1 on win2k with (I believe) cmdproxy, I can do
> M-x shell and enter
>
>> plink -ssh -v -pw password [EMAIL PROTECTED]
>
> and connect, and interact. However, with tramp-1.449 and
>
[...]
>
> in my _emacs, when I do
>
> M-x find-file /r@t:[EMAIL PROTECTED]:.emacs
>
> it still fails to connect, with the same *tramp* and *Backtrace*
> buffer contents. Any suggestions on how to fix this?
Hack your profile on the remote machine to *not* spit out ANSI/VT100
when TERM is DUMB. :)
> One thing I'm wondering: since the error is
>
> *Backtrace*
>> Signaling: (error "Couldn't find remote shell or passwd prompt")
>
> is there a problem with my shell-prompt-pattern? It's currently set to
>
>> (setq shell-prompt-pattern "^[^#$%>\n]*[#$>] *")
Yeah, that fails to match:
[...]
>> Running user customized standard startup activities ...
>> End of login--close console.
>> [1m/ncsu/tlroche> [m
Because of the trailing escape sequence "[m".
The right fix, as I said above, is to have the silly tcsh on the remote
machine *not* automatically try to underline your command prompt.
Probably by setting PS1 in the login script.
The wrong fix, but one that makes life for you easier, is to hack the
regexp in `shell-prompt-pattern' to match the escape sequences as well:
(setq shell-prompt-pattern "^\\(\e[1m\\)?[^#$%>\n]*[#$>] *\\(\e[m\\)?")
You can even make the escape sequence matching more generic if you want. :)
Daniel
--
A large number of installed systems work by fiat.
That is, they work by being declared to work.
-- Anatol Holt
