2006/2/3, Nick Pilon <[EMAIL PROTECTED]>:
> On 2/3/06, Axel Liljencrantz <[EMAIL PROTECTED]> wrote:
> > Yes, but I'll have to figure out a way to actually actually do forking
> > without using sleep.
>
> Something from the wait() family of functions?
Wait can make a parent wait for a child, I need a way for a child to
stop until the parent gives up control of the terminal and puts the
child in it's own process group. Actually, a child can do both these
things itself and just ignore the parent, but I seem to remember some
kind of problem when setting up a pipeline when the first command
would exit before the parent forks the second command, this would
cause occasional (very rare) strangeness.
>
> > Is this always, or just when using 'status --job-control=none'.
> > Looking at the code, I can see that disabling job control should make
> > the pager go nuts. I've fixed that now.
>
> Ah, yes. That's exactly what was causing it.
Good. One down, one to go.
>
> > > The version of fish from this tarball also goes nuts when it's
> > > executed as the first process in an empty terminal (IE, as the shell).
> > > Again, fish 1.20.1 and 1.20.0 didn't do this.
> > Nuts as in really slow startup, I take it?
>
> No. Nuts as in it complains about not being able to find gettext,
> spews a bunch of unintelligible errors, and then appears to somehow
> get confused and fail to handle the rest of the init files. 1.18 did
> that, 1.20.0 and 1.20.1 worked right.
Does it not find the gettext _command_ or the gettext C function? IS
the former in your PATH?
>
> --
> -Nick Pilon
>
--
Axel
N�HY隊X���'���u���[�������
ަ�k��!�� �W�~�鮆�zk��C� [EMAIL PROTECTED],���� a{�
��,�H��4�m�����Z�� jY�w��ǥrg
