Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news.sprintlink.net!howland.reston.ans.net!math.ohio-state.edu!magnus.acs.ohio-state.edu!lerc.nasa.gov!purdue!news.bu.edu!acs4.bu.edu!mi From: mi@bu.edu (Mikhail Teterin) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: xterm ignores tcsh (?) Date: 5 Oct 1995 03:06:25 GMT Organization: Boston University Lines: 19 Message-ID: <44vi3h$k23@news.bu.edu> References: <44h6dj$kbf@news.bu.edu> <DFvDGL.2tD@seeware.DIALix.oz.au> NNTP-Posting-Host: acs4.bu.edu X-Newsreader: TIN [version 1.2 PL2] Some time ago (Tue, 3 Oct 1995 11:05:08 GMT) honorable Mark Hannon, residing at mark@putte.seeware.DIALix.oz.au wrote: |In article <44h6dj$kbf@news.bu.edu>, | mi@cs.bu.edu (Mikhail Teterin) writes: |>My login shell is tcsh. Whem X comes up (startx) all the xterms have |>csh in them. The only ways to start tcsh in xterm are `-e login' or |>`-e tcsh'. Thanks for any clue! |> |Make sure that you do a |setenv SHELL /usr/local/bin/tcsh |before you startx. You should be able to put that |in your .tcshrc file. Thanks! I already figured that. Now I'm wondering why does the default .login have `setenv SHELL /bin/csh' in it? Removing that helped, and seems to be a way cleaner solution. Thanks! -mi