Date: Tue, 22 Feb 2011 14:38:45 -0700 From: Chad Perrin <perrin@apotheon.com> To: freebsd-questions@freebsd.org Subject: Re: bash can not find most of my commands Message-ID: <20110222213845.GA3829@guilt.hydra> In-Reply-To: <AANLkTiko9sO94=g_JFRimRO-4qXPK5DFEKWF47vjmBYy@mail.gmail.com> References: <4D63E6F2.3050008@alokat.org> <4D63E92C.4060304@ifdnrg.com> <4D63EB2E.3080200@alokat.org> <20110222175313.GD3027@guilt.hydra> <AANLkTimXgCDtS6BdjH4xXW6Bebro2vn6U5azoK3ikhDP@mail.gmail.com> <20110222203906.GA3608@guilt.hydra> <AANLkTiko9sO94=g_JFRimRO-4qXPK5DFEKWF47vjmBYy@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--45Z9DzgjV8m4Oswq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Feb 22, 2011 at 01:10:20PM -0800, David Brodbeck wrote: >=20 > Yeah, I try to avoid bash-specific syntax unless it's for one-off > scripts. csh suffers the same kinds of problems; I only write csh > code under extreme duress, like when forced to maintain the > system-wide csh.login script. ;) I often use tcsh as an interactive shell, but I do not use it for shell scripts. --=20 Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] --45Z9DzgjV8m4Oswq Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAk1kLOUACgkQ9mn/Pj01uKUuYwCfQxgKvLX0oY6I5uNcWdsWeh02 ffgAoKN0C1G5oz6N6Npzoyrg8JCA8veY =Nb3v -----END PGP SIGNATURE----- --45Z9DzgjV8m4Oswq--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110222213845.GA3829>