From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "ZSH workers mailing list" <zsh-workers@sunsite.auc.dk>
Subject: PATCH: small completion doc fix
Date: Wed, 28 Jun 2000 12:00:57 +0400 [thread overview]
Message-ID: <000001bfe0d6$fe2b58a0$21c9ca95@mow.siemens.ru> (raw)
[-- Attachment #1: Type: text/plain, Size: 157 bytes --]
I believe, we do not rebind keys anymore, but redefine widgets. And
bindkey binds keys to widgets not commands or functions?
-andrej
Have a nice DOS!
B >>
[-- Attachment #2: compsys.yo.diff --]
[-- Type: application/octet-stream, Size: 1174 bytes --]
--- Doc/Zsh/compsys.yo.org Wed Jun 28 11:34:45 2000
+++ Doc/Zsh/compsys.yo Wed Jun 28 11:57:39 2000
@@ -69,15 +69,15 @@
(`tt(autoload -U compinit)' is recommended), and then run simply as
`tt(compinit)'. This will define a
few utility functions, arrange for all the necessary shell functions to be
-autoloaded, and will then re-bind all keys that do completion to use the
+autoloaded, and will then re-define all widgets that do completion to use the
new system. If you use the tt(menu-select) widget, which is part of the
tt(zsh/complist) module, you should make sure that that module is loaded
before the call to tt(compinit) to make sure that that widget is also
-re-bound.
+re-defined.
Should you need to use the original completion commands, you can still
-bind keys to the old functions by putting a `tt(.)' in front of the
-command name, e.g. `tt(.expand-or-complete)'.
+bind keys to the old widgets by putting a `tt(.)' in front of the
+widget name, e.g. `tt(.expand-or-complete)'.
To speed up the running of tt(compinit), it can be made to produce a dumped
configuration which will be read in on future invocations; this is the
reply other threads:[~2000-06-28 8:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='000001bfe0d6$fe2b58a0$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--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).