From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Sven Wischnowsky" <wischnow@informatik.hu-berlin.de>,
<zsh-workers@sunsite.auc.dk>
Subject: RE: More make check failure
Date: Tue, 30 May 2000 15:07:14 +0400 [thread overview]
Message-ID: <000101bfca27$35ad7a40$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <200005301036.MAA20699@beta.informatik.hu-berlin.de>
> How do you have configured the shell? With zsh's allocator? Secure
> free? Memory debugging? Other debugging options?
>
bor@itsrm2% cat =zshconf
#!/tools/bin/zsh
LIBS=-lg
/tools/src/zsh/configure --prefix=/tools --enable-zsh-debug --enable-fun
ction-subdirs
Large integers and LFS are enabled and supported.
> And do you always get that failure?
Two times already at least.
Do you get it with:
>
> compdef foo foo
> foo() {
> compadd -M 'm:{a-zA-Z}={A-Za-z}
> r:|[.,_-]=* r:[^A-Z0-9]||[A-Z0-9]=*
> r:[A-Z0-9]||[^A-Z0-9]=*
> r:[^0-9]||[0-9]=* r:|=*' \
> build.out build.out1 build.out2
> }
>
> and trying `foo bui<TAB><TAB><TAB>'? It should do the same as the
> test, I'm just getting paranoid.
>
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
-andrej
next prev parent reply other threads:[~2000-05-30 11:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-30 10:36 Sven Wischnowsky
2000-05-30 11:07 ` Andrej Borsenkow [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-05-30 11:21 Sven Wischnowsky
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='000101bfca27$35ad7a40$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--cc=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).