zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: RE: More make check failure
Date: Tue, 30 May 2000 13:21:11 +0200 (MET DST)	[thread overview]
Message-ID: <200005301121.NAA20744@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Andrej Borsenkow"'s message of Tue, 30 May 2000 15:07:14 +0400


Andrej Borsenkow wrote:

> ...
> 
> I am not sure, what should I get:
> 
> bor@itsrm2% zsh -f
> itsrm2% autoload compinit; compinit -D
> itsrm2% {
> cursh>   compdef foo foo
> cursh>   foo() {
> cursh function>     compadd -M 'm:{a-zA-Z}={A-Za-z}
> cursh function quote>                 r:|[.,_-]=*
> r:[^A-Z0-9]||[A-Z0-9]=*
> cursh function quote>                 r:[A-Z0-9]||[^A-Z0-9]=*
> cursh function quote>                 r:[^0-9]||[0-9]=* r:|=*' \
> cursh function>         build.out build.out1 build.out2
> cursh function>   }
> cursh> }
> itsrm2% foo build.out<CURSOR HERE>
> build.out    build.out1   build.out2

You should get exactly that. In the test the cursor was placed after
the `build'.

Damn. I'm still pretty sure this has to do with some uninitialised
memory. But where?

But this should probably not keep us from releasing 3.1.7. If we don't 
want users to see this we could comment the test out. I'll keep it on
my list, although I fear I will never be able to reproduce it.

Bye
 Sven


--
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de


             reply	other threads:[~2000-05-30 11:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-30 11:21 Sven Wischnowsky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-05-30 10:36 Sven Wischnowsky
2000-05-30 11:07 ` Andrej Borsenkow
2000-05-30 10:03 Andrej Borsenkow

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=200005301121.NAA20744@beta.informatik.hu-berlin.de \
    --to=wischnow@informatik.hu-berlin.de \
    --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).