Yep... a win-nah! The solution was so obvious as I wrote the question,
having just made a custom bash prompt and seeing it uglify further the
shell mode screen. Chalk this one up to lack of sleep and poor
nutrition.
I have since found also some function, ansi-term (native at least to
my FSF Emacs 20.3) which makes for a nice presentation, and then
there's ansi-color.el, which sorta works...
I took the opportunity to remove the color prompt, et al from the
remote server I have been trying to link to, as well as the local
client. Alas, I get the same result with rcp as before. So, I suppose
that this is not the source of the problem.
I notice, however, that I am able to connect flawlessly to my account
on my ISP via rcp. I guess I ought to investigate further...
Tim
>>>>> Daniel Pittman <[EMAIL PROTECTED]> spake thus:
[snip]
> That would be ANSI color control sequences, produced by the GNU
> ls(1) command. I would imagine that you have an alias in your
> .bashrc or similar that does 'alias ls='ls --color=auto' or
> something similar.
> This causes the pretty blue directories and red broken symlinks
> when you do ls(1) under a VT100. Under an Emacs 'dumb' terminal
> which does not speak ANSI/VT100 escape codes...
> So, to fix this, run up a shell and try 'ls --color=none' and
> see if the problem goes away. If so, you have a winner. Just
> track down what turns that option on and everything will be
> fine.
