Kai Großjohann writes:
> Pete Forman <[EMAIL PROTECTED]> writes:
>
> > Most versons of ls work for me, but I do have an older machine
> > running ISC 4.0 (Interactive Unix) which does not handle -1. How
> > much of a problem is it to parse the results of ls with a
> > whitespace separator rather than newline?
>
> So, should I be doing `ls | cat', instead? What do you think?
That should work.
> > On a related point, my .profile is geared up to being sourced
> > interactively or not. The latter just sets environment variables.
> > Interactive things like calling stty and aliasing cd to change the
> > xterm title are within the condition "if tty -s && [ -z "$DT" ]". The
> > DT variable is set during CDE session startup. Am I going to be able
> > to add a similar test to know when rcp.el is in charge?
>
> Hm. I'm not sure how this could be done. I could add a variable
> to the process environment before starting rsh (or whatever), but I
> think that variable will not propagate to the remote shell, will
> it? Hm. Any ideas?
Correct, no environment variable is set remotely under vanilla rsh.
Rlogin (which rsh drops into with no command specified) only sets TERM
on the remote host. Any command that you might give to the remote
shell, such as "set PS1=/////", cannot happen until after .profile is
sourced.
My question was somewhat rhetorical, I think that making the remote
shell interactive will lead to other problems. My .profile is just an
example.
--
Pete Forman
Western Geophysical
[EMAIL PROTECTED]
