This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: Problems using tcsh as default shell
----- Original Message -----
From: "Martin Nilsson (ERV)" <Martin.Nilsson@erv.ericsson.se>
To: <cygwin@cygwin.com>
Sent: Thursday, February 21, 2002 07:02
Subject: Problems using tcsh as default shell
> I have a problem with tcsh when using it as the default shell for cygwin.
I have replaced the bash command line in cygwin.bat with tcsh -l and now my
cygwin.bat have the following content:
>
> @echo off
> C:
> cd \cygwin\bin
> tcsh -l
>
> tcsh does not seem to have any problem reading my startup scripts (like
.tcshrc asf) but it always complains with the following message:
>
> /cygdrive/c/j2sdk1.4.0/bin/sed: No children.
>
> Sometimes "j2sdk1.4.0/bin" is replaced by some other path name. I guess
there is some kind of problem with my path variable when tcsh is trying to
parse it (using sed??). Does anyone have a solution on how to avoid this
error?
>
> This problem does not arise when invoking tcsh from bash (and using bash
as default shell).
>
> cygwin is installed on a WIN2K machine.
It looks like you have something earlier in $path that contains files with
the same names as the utilities provided by Cygwin; probably
c:\j2sdk1.4.0\bin\sed.exe in this example. /etc/csh.cshrc runs before
/etc/csh.login has a chance to fix $path to put Cygwin's bin directories at
the front of the path, so your Win2K path is still in effect.
Running 'type -a sed' (or similar for other tools) in bash may be
enlightening. The output from 'cygcheck -s' may also help you figure out
what's happening.
--
Mac :})
** I normally forward private questions to the appropriate mail list. **
Ask Smarter: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Give a hobbit a fish and he eats fish for a day.
Give a hobbit a ring and he eats fish for an age.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/