🚀 go-pugleaf

In article <467@virginia.acc.virginia.edu> mer6g@virginia.UUCP (Marc Rouleau) writes:
>On our 3b2, 3b5, and 3b15 AT&T systems running SYSV.2 and SYSV.3, sh does
>something rather unfortunate when certain built-in functions fail.  For
>example,
>
>	cd nowhere || echo 'cd failure'
>
>where ``nowhere'' is nonexistent does not (as you might expect) cause ``cd
>failure'' to be echoed to the screen.  The expected error message is produced
>and then . . . nothing, a new prompt.
>

Dat's 'cos the first cd fails, so the shell interrupts itself (well, sort of),
and jumps straight back to command level - without executing the second part of
the "||". What you'll have to do is force the first component to be executed
in a subshell so it can't effect the second - like
	if (cd nowhere)		# cd in a subshell
	then cd nowhere		#  it worked, so cd in the main shell
	else echo 'cd failure'  #  otherwise print error message
  	fi
Of course, you still get the error message from the first cd (if it fails),
unless you redirect it's output elsewhere with
	if (cd nowhere) >/dev/null 2>&1

-- 
----------------------------------
| Simon Brown                    | UUCP:  seismo!mcvax!ukc!{lfcs,its63b}!simon
| LFCS                           | JANET: simon@uk.ac.ed.{lfcs,its63b}
| Department of Computer Science | ARPA:  simon%lfcs.ed.ac.uk@cs.ucl.ac.uk
| University of Edinburgh,       |     or simon%its63b.ed.ac.uk@cs.ucl.ac.uk
| Scotland, UK.                  |     or simon%cstvax.ed.ac.uk@cs.ucl.ac.uk
---------------------------------- 
                      "Life's like that, you know"