Zsh Mailing List Archive
Messages sorted by:
Re: NEW BUG: 3.1.6 bug in NextStep/OpenStep 4.2
- X-seq: zsh-workers 7523
- From: Brian Boonstra <boonstb@xxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxxxxxx
- Subject: Re: NEW BUG: 3.1.6 bug in NextStep/OpenStep 4.2
- Date: Fri, 27 Aug 99 14:37:40 -0500
- In-reply-to: <199908271427.JAA23890@xxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
- References: <199908270713.JAA16491@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <199908271427.JAA23890@xxxxxxxxxxxxxxxxxxxx>
Well, I have a compilation that runs, and completion works well.
But now I notice that the terminal hangs after I perform any kind of command
except shell builtins. For example, "ls", "df", and "finger" all hang after
their output, whereas "echo" and "alias" do not hang.
Note that this has nothing to do with the patch Sven supplied to fix
complist.c. I have applied one other set of patches, though, namely the
ones found here:
I doubt they are at fault, since they only patch the necessary (for
me) third argument onto fcntl in utils.c and init.c.
I tried compiling a debug version, but that version always gives a
Bus Error on the first keystroke, so I'm afraid I can't be more specific.
Anybody have ideas?
Brian Boonstra wrote:
> I applied the patch (in 7513 and 7455) and it fixed the problem
> perfectly! Similarly to what Brian H. saw, `print -P "%s"' was not giving
> me any extraneous characters.
> For the benefit of those joining late, in order to get zsh 3.1.6 to
> compile on OpenStep, you also need the patch from 2372.
> Sven Wischnowsky wrote:
> > Brian Boonstra wrote:
> > I don't know about the other things, but I guess this is the same
> > problem mentioned by Brien Harvell (in 7443), only that he got `$<2>'
> > instead of the `2'.
> > To repeat: I think this is caused by the complist code. It prints the
> > termcap string for `%s' (standout off) at those places. What irritated
> > me is that `print -P "%s"' didn't give him those `$<2>' strings.
> > I then suggested the patch in 7455 (which is appended below for your
> > convenience), but got no reply from him after that, so I don't know if
> > it fixes the problem (I guess not).
Messages sorted by: