From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Nits in compinstall in -dev-22
Date: Mon, 10 Apr 2000 04:56:53 +0000 [thread overview]
Message-ID: <1000410045654.ZM18205@candle.brasslantern.com> (raw)
Patch below for a typo.
The other nit is not exactly with compinstall, but shows up there. One
of the explanatory texts reads:
Completions defined by the new completion system (the one you are
configuring) always take precedence over the old sort defined with compctl.
You can choose whether or not you want to search for a compctl-defined
completion if no new completion was found for a command. The default
behaviour is only to check for compctl-defined completions if the required
library, zsh/compctl, is already loaded. (If not, this implies that
compctl has not been called.) Do you want to test for compctl-defined
completions?
As of -dev-18 (9591), the compctl module is loaded anytime zle is. That's
so that brand-new users, who have never run compinstall or compinit, have
some default completions. One must explicitly unload it to get rid of it.
Perhaps compinstall should offer to unload it?
Index: compinstall
===================================================================
@@ -553,7 +553,7 @@
To have different values for approximation and correction, you should
change the context appropriately. For approximation, use
-\`:completion:*:approxima2te:*' and for correction use
+\`:completion:*:approximate:*' and for correction use
\`:completion:*:correct:*'.
Enter maximum number of errors allowed:
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next reply other threads:[~2000-04-10 4:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-10 4:56 Bart Schaefer [this message]
2000-04-10 5:16 ` Bart Schaefer
2000-04-11 20:18 ` PATCH: " Peter Stephenson
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=1000410045654.ZM18205@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--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).