"Richard A Ryan" <[EMAIL PROTECTED]> writes: > I hope this isn't the wrong place to be sending this, but I would > like to suggest that tramp have the capability of parsing out > banners. Where I work, and I've been told elsewhere as well, there > are banners flashed to screen for every connection made even when > connecting with scp, rcp, rsh, ssh, and so on. This confuses TRAMP. > Maybe TRAMP could have some variable to specify a program that could > be used to filter these things rather than having the filtering > built into TRAMP.
I'm not sure I understand what is happening, but I think that Tramp already tries to deal with it. Could you provide more information, please? The Tramp version would be interesting, as would be the *debug tramp/foo* buffer. You get this buffer with (setq tramp-debug-buffer t). If you type M-x tramp-bug RET you will see more instructions that might be useful. When connecting with ssh or rsh, Tramp expects a message of the day and tries to skip it. (But Tramp can get confused if something in the motd looks like a shell prompt.) When connecting with scp or rcp, Tramp ignores all output from the remote end, I think. kai -- ~/.signature is: umop ap!sdn (Frank Nobis) _______________________________________________ Tramp-devel mailing list [EMAIL PROTECTED] http://mail.freesoftware.fsf.org/mailman/listinfo/tramp-devel
