🚀 go-pugleaf

On 24 Jul 92 04:36:22 GMT, Chet Ramey wrote

> I wonder whether this problem has been beaten to death in this group 
> before.  I use bash 1.12.1  as login shell on my machines (Sun Sparcs 
> running SunOS 4.1.1) and having problem with rsh and rcp. The symptoms
> are as follows:
> 
>     host1>  rcp localfile host2:remotefile
>     stty: TCGETS: Operation not supported on socket
>     host1>  rsh host2 ls
>     stty: TCGETS: Operation not supported on socket

Chet> I'll bet you have something that does output or manipulates the terminal
Chet> state in your .bashrc.  Bash attempts to source the .bashrc for non-
Chet> interactive shells running rsh and rcp so things like $PATH get set.

 Exactly.  I had for ages the same error message popping up
(I remember it particularly when using shell-command in Emacs) and
after much grief, especially when crypting files as the error message
appeared in the file, I realised I had

stty pass8 ;

 in my .bashrc so I could use the META keys.  I now avoid it by doing:

if [ -n "$-" ] ; then
	stty pass8 ;
fi

 which "tests" for `i' for interactive in $- (the current bash flags)
which thanks to Chet I now realise is a *bit* flaky - I always wanted
to know how to test for an individual flag :-)

 I may be an idiot, but I'm happy.



--
Cheers,

	Ian

-------------------------------------------------------------------------------
Ian Fitchet     				      I.D.Fitchet@cs.bham.ac.uk
School of Computer Science
Univ. of Birmingham, UK, B15 2TT