From: mason@primenet.com.au (Geoff Wing)
To: zsh-workers@sunsite.auc.dk
Subject: Re: bug with completion (after 15 oct?)
Date: 25 Oct 2000 07:49:03 GMT [thread overview]
Message-ID: <slrn8vd43f.24b.mason@coral.primenet.com.au> (raw)
In-Reply-To: <200010250714.JAA23634@beta.informatik.hu-berlin.de>
Sven Wischnowsky <wischnow@informatik.hu-berlin.de> typed:
:Geoff Wing wrote:
:Does that mean that amatches is garbled at that point?
No, amatches had some information. From memory, had some
sort of valid information so did ->next , ->next->next was NULL.
This is what I'm currently down to: this is stuff ripped out of my zshrc
though maybe slightly rearranged (the extra stuff in there is because
some is shared with 3.0.x startup) - but I can reproduce it with this
on the second or third go - if the second succeeds it'll also put my
cursor one line too high.
% zsh.new -f
% PROMPT=
_compdir=/usr/local/share/zsh/${ZSH_VERSION}/functions
[[ -z $fpath[(r)$_compdir] ]] && fpath=($fpath $_compdir)
autoload -U compinit
compinit
autoloadflag=-U
zstyle '*' completer _complete _correct _approximate
[[ -n "$fpath" ]] && for dir in $fpath; do [[ -d $dir ]] && autoload $autoloadflag $dir/*~*/_*(N.:t); done
zstyle ':completion:*' format '--> completing %d'
zstyle ':completion:*' menu select=1
setopt menu_complete
unsetopt always_last_prompt
# then do
ls ba<TAB><CTRL-U>ls ba<TAB><CTRL-U>ls ba<TAB>
# core dump
Regards,
--
Geoff Wing : <gcw@pobox.com>
Rxvt Stuff : <gcw@rxvt.org>
Zsh Stuff : <gcw@zsh.org>
next prev parent reply other threads:[~2000-10-25 7:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-25 7:14 Sven Wischnowsky
2000-10-25 7:49 ` Geoff Wing [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-10-25 10:51 Sven Wischnowsky
2000-10-25 8:17 Sven Wischnowsky
2000-10-25 10:24 ` Geoff Wing
2000-10-24 14:33 Geoff Wing
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=slrn8vd43f.24b.mason@coral.primenet.com.au \
--to=mason@primenet.com.au \
--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).