On Sun, 06 Jun 2004 16:53:47 +0200 Kai Grossjohann <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] writes: > > At first it really didn't look that tramp-rsh-end-of-line was the > > source of the problem. I tried playing with the > > tramp-shell-prompt-pattern, because I thought that's why the prompt > > isn't recognized. Then I thought > > tramp-open-connection-setup-interactive-shell inserted an > > adiditional \n somewhere, from there I dug into > > tramp-send-command-internal, where I finally found > > tramp-rsh-end-of-line. > > > > Long story short: It's not obvious to change tramp-rsh-end-of-line, > > so a remark somewhere (aside from the documentation of a variable I > > didn't even bother to look at in the beginning) would be nice. > > Yes. Can you say where you started looking? Perhaps it was > tramp-shell-prompt-pattern? If this is the case, then maybe I should > say that it would be good to look in the *tramp/foo* buffer (or is it > the *debug tramp/foo* buffer that you need to look at?) for doubled > prompts. For that case, people are advised to look at > tramp-rsh-end-of-line. I think the error message is already a quite strong indicator: stty -inlcr -echo kill '^U' failed (or something like this). In the debug buffer you can see the double prompt "$ $ " and the tramp-shell-prompt-pattern regex, but I really think the stty failure message is unique enough. Cheers, Greek0 _______________________________________________ Tramp-devel mailing list [EMAIL PROTECTED] http://lists.nongnu.org/mailman/listinfo/tramp-devel