This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
RE: Zsh observations
- To: <cygwin at cygwin dot com>
- Subject: RE: Zsh observations
- From: "Andrej Borsenkow" <Andrej dot Borsenkow at mow dot siemens dot ru>
- Date: Thu, 5 Jul 2001 18:25:17 +0400
> -----Original Message-----
> From: cygwin-owner@sources.redhat.com
> [mailto:cygwin-owner@sources.redhat.com]On Behalf Of Christopher Faylor
> Sent: Thursday, July 05, 2001 6:08 PM
> To: cygwin@cygwin.com
> Subject: Re: Zsh observations
>
>
> On Thu, Jul 05, 2001 at 09:59:10AM +0400, Andrej Borsenkow wrote:
> >>
> >> 1. zsh doesn't like it if ...\cygwin\bin is not in the Windows
> >> path. If I
> >> start up zsh without this, it works as long as the current directory is
> >> /usr/bin. If I then do
> >> PATH="/usr/local/bin:/usr/bin:/bin:$PATH"
> >> export PATH
> >> cd $HOME
> >> (either on the command line, or in /etc/zprofile), any
> external command I
> >> run gives:
> >> 0 [main] zsh 2432 sync_with_child: child 2356(0x230)
> >> died before
> >> initialization with status code 0x80
> >> 1288 [main] zsh 2432 sync_with_child: *** child state
> >> waiting for longjmp
> >> /home/mscha/.zshrc:150: fork failed: resource temporarily unavailable
> >>
> >
> >Well ... it does work if you start cmd.exe (I am on NT), and
> then run zsh as
> >e.g. \cygwin\bin\zsh. It does not work if you define shortcut
> and start zsh
> >via shortcut. Both with current snapshot.
> >
> >I am pretty sure it worked at some point (because I did have shortcut to
> >zsh). I cannot recall any changes in zsh that could result in
> this problem,
> >but who knows.
>
> I can't get it to fail in this fashion. I've taken x:\cygwin\bin
> from my path.
> It was being added in my zshenv file anyway. It works just fine.
You have dynamic build (with libzsh)?
-andrej
--
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/