Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: 3.1.6 bug in NextStep/OpenStep 4.2
- X-seq: zsh-workers 7519
- From: Brian Boonstra <boonstb@xxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxxxxxx
- Subject: Re: 3.1.6 bug in NextStep/OpenStep 4.2
- Date: Fri, 27 Aug 99 09:27:22 -0500
- Cc: luomat@xxxxxxxxxxxxx
- In-reply-to: <199908270713.JAA16491@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
- References: <199908270713.JAA16491@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Hi Sven (and all)
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.
BTW, Sven, this is especially welcome on OpenStep/NextStep, because
the Terminal application supplied by them is so darn good that few people
ever use anything else. And it does only vt100.
Thanks,
Brian
Sven Wischnowsky wrote:
> Brian Boonstra wrote:
> > However, completion is not quite right. In particular, if I run
> > either the usual binary, I get completion with extra "2" characters, like
> > this:
> 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:
Reverse Date,
Date,
Thread,
Author