Date: Mon, 26 Oct 1998 12:29:46 -0800 (PST) From: David Wolfskill <dhw@whistle.com> To: current@FreeBSD.ORG Subject: Re: sh and ~ expansion Message-ID: <199810262029.MAA02622@pau-amma.whistle.com> In-Reply-To: <7577.909365359@brown.pfcs.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>Date: Sun, 25 Oct 1998 20:29:19 -0500
>From: Harlan Stenn <Harlan.Stenn@pfcs.com>
>I still want to see csh replaced with tcsh.
Though it's not relevant to the original thread, the following excerpt
from my ~/.cshrc may be of interest to those with the above perception:
set tcsh = `which tcsh`
if ( $?HOSTTYPE && ${?tcsh} && "${tcsh}" == "$SHELL" ) then
else if ( $?prompt && { test -x ${tcsh} } ) then
setenv SHELL "$tcsh"
exec tcsh
endif
endif
Naturally, this is done after the $path is set. And /bin/csh is my
defined "login shell" -- but given what I do for a living, sometimes the
machine in question can't get to /usr/local/bin (which is made visible
via NFS & amd). Need to be a little careful, since the "`which tcsh`"
invokes csh all over again.... :-}
david
--
David Wolfskill UNIX System Administrator
dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199810262029.MAA02622>