From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: completion tricks
Date: Wed, 21 Mar 2001 09:33:20 +0000 [thread overview]
Message-ID: <1010321093320.ZM16812@candle.brasslantern.com> (raw)
In-Reply-To: <20010320170033.A31547@thelonious.new.ox.ac.uk>
[ Redirected to zsh-workers ]
On Mar 20, 4:36pm, Sven Wischnowsky wrote:
} Subject: Re: completion tricks
}
} > The more I think about it, the more I like the idea of `make install'
} > (or maybe `make install.zwc') taking the most sensible compilation
} > route.
}
} I wouldn't be against that, I just wouldn't know what style to suggest:
} one for all, one for each directory
Probably which of these works best depends on whether memory mapping is
available.
On Mar 20, 5:00pm, Adam Spiers wrote:
} Subject: Re: completion tricks
}
} So far, we have already mentioned [slowness from] _approximate and
} _correct (I still haven't got round to figuring out the difference
} between the two), and match specs.
The difference is that _correct won't treat the word on the line as a
substring of a longer match; it just tries to find matching character
permutations within the existing word.
} (Incidentally there are some rough edges with the caching mechanism
} which I *still* haven't got round to smoothing.)
_perl_modules is a good example of such roughness, because perl can be
invoked by a large number of almost-synonymous names including names
with version numbers. I tried to make it do something sensible, but
I'm not entirely happy with the result.
} Anything else?
Any completion that uses _call is potentially slow, of course. Maybe
we ought to be caching the _is_gnu association, too.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
parent reply other threads:[~2001-03-21 9:34 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20010320170033.A31547@thelonious.new.ox.ac.uk>]
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=1010321093320.ZM16812@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.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).