From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: _approximate and _path_files
Date: Wed, 15 Dec 1999 16:29:08 +0100 (MET) [thread overview]
Message-ID: <199912151529.QAA07056@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Andrej Borsenkow"'s message of Wed, 15 Dec 1999 14:16:21 +0300
Andrej Borsenkow wrote:
> Do they work together? Assuming that I have directory /archive/sni/mr,
>
> cd /archive; l sin<TAB>
>
> gives me `sni'
>
> but simple
>
> l /ar/sin<TAB>
>
> after *very* long time beeps.
>
> If not - it's really a pity.
>
> Actually, enabling _approximate (I have max-erros 3) and trying to complete any
> non-existing partial path takes really long time. Hmm ... looks, like zsh simply
> hangs (or better said, loops) currently. I have to press ^C to be able to enter
> something. ^C then returns to my input I tried to complete.
Damn, damn, damn. We lost this when we made braces in path prefixes
and suffixes work. The problem is that the compadd function
_approximate uses sticks the (#a...) at the beginning of the whole
string and then the C-code thinks that this doesn't match because it
doesn't compare the whole strings (including the prefixes and
suffixes), and that is the other way to look at the problem.
We can't just make the compadd() in _approximate to put the (#a...)
somewhere else because we don't know anything about separator
characters used in the calling function.
So we have to fix it in C... and I don't know yet how this is done
best (without losing too much of, e.g., the prefix matching stuff).
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~1999-12-15 15:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-15 15:29 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-12-15 11:16 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=199912151529.QAA07056@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).