zsh-workers
 help / color / mirror / code / Atom feed
From: Brian Boonstra <boonstb@cmg.FCNBD.COM>
To: zsh-workers@sunsite.auc.dk
Cc: luomat@kira.peak.org
Subject: Re: 3.1.6 bug in NextStep/OpenStep 4.2
Date: Fri, 27 Aug 99 09:27:22 -0500	[thread overview]
Message-ID: <199908271427.JAA23890@wo1203.cmg.FCNBD.COM> (raw)
In-Reply-To: <199908270713.JAA16491@beta.informatik.hu-berlin.de>

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).


  reply	other threads:[~1999-08-27 14:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-27  7:13 Sven Wischnowsky
1999-08-27 14:27 ` Brian Boonstra [this message]
1999-08-27 19:37   ` NEW BUG: " Brian Boonstra
1999-08-27 19:48     ` Brian Boonstra
  -- strict thread matches above, loose matches on Subject: below --
1999-08-26 18:56 Brian Boonstra

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=199908271427.JAA23890@wo1203.cmg.FCNBD.COM \
    --to=boonstb@cmg.fcnbd.com \
    --cc=luomat@kira.peak.org \
    --cc=zsh-workers@sunsite.auc.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).