Re: rcp.el 1.140: bug fixes, work better with XEmacs/EFS?

[Kai Gro�johann]

Erik Arneson <[EMAIL PROTECTED]> writes:

> I think I see what's happening now.  The PATH is being emptied, and
> `test' therefore isn't found.  It is located in /bin/ on that machine,
> and isn't built into the shell.  Could that be the problem?

Oh, my.  Hm.  I empty $PATH in order to get more predictable results.
Hm.  The fact that ls doesn't grok the -n option seems to indicate
you're talking to a BSDish system -- what kind of system is ns1?

I think we can assume that, even if test is a built-in command, there
is a /usr/bin/test which we can use?  If this is true, I could add
stuff to rcp.el that searches for a test binary.

Btw, do you get a message "Danger!  Couldn't find ls which groks -n.
Muddling through anyway." from rcp.el?  (You might wish to have a look
in the *Messages* buffer.)  Do you have an ls binary on the remote
system which groks -n?  How can that binary be found?  (My home system
has FreeBSD, but there is a /usr/local/bin/gnuls which groks -n.)

kai
-- 
I like BOTH kinds of music.