Xref: utzoo comp.unix.wizards:23503 gnu.bash.bug:1707 Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!mips!daver!tscs!tct!chip From: chip@tct.uucp (Chip Salzenberg) Newsgroups: comp.unix.wizards,gnu.bash.bug Subject: Re: cd failure killing script [Re: Interactive 2.2 File zapper] Message-ID: <26CC08F4.5576@tct.uucp> Date: 17 Aug 90 15:10:43 GMT References: <26C2F1A0.205B@tct.uucp> <9118@jpl-devvax.JPL.NASA.GOV> <1990Aug13.211716.5111@chinet.chi.il.us> Organization: Teltronics/TCT, Sarasota, FL Lines: 17 [ Discussion cross-posted to gnu.bash.bug. ] According to les@chinet.chi.il.us (Leslie Mikesell): >[Bash and ksh] will cause serious problems when executing scripts that are >perfectly valid for /bin/sh. They could (should) have required a "set" >option to be done to make them operate differently. What an excellent idea! I intend to change my bash sources to exit on a failed "cd" unless the shell is interactive or the variable "no_exit_on_failed_cd" is set. (Yes, the name is awkward, but it is a logical companion to the already-implemented "no_exit_on_failed_exec" variable.) -- Chip Salzenberg at Teltronics/TCT , "Most of my code is written by myself. That is why so little gets done." -- Herman "HLLs will never fly" Rubin