From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: PATCH: README
Date: Mon, 1 Mar 1999 14:23:32 +0100 (MET) [thread overview]
Message-ID: <199903011323.OAA14207@beta.informatik.hu-berlin.de> (raw)
Just some typos and documentation for the new ones in Base.
Bye
Sven
P.S.: "...and will most likely not feel like altering them (or, in
some cases, even reading them, unless you are a shell wizard)",
is it really that... erm... bad? overwhelming? complicated?
badly written?
--- oc/README Mon Mar 1 10:10:07 1999
+++ Completion/README Mon Mar 1 14:19:07 1999
@@ -11,7 +11,7 @@
[[ -f ~/completion/compinit ]] && . ~/completion/compinit -d
This will rebind any keys which do completion to use the new system.
For more detailed instructions, including how to add new completions, see
-the top of Core/compinit .
+the top of Core/compinit.
The subdirectories contain:
@@ -46,7 +46,7 @@
it is wider than just command+argument.)
_path_files
The function usually called to complete filenames and directories. It
- replaces the standard -f and -/ options for the basic completion
+ replaces the standard -f, -g and -/ options for the basic completion
commands: it can do various extra tricks, such as expanding a whole
path at once, e.g. F/C/C/_p<TAB> -> Functions/Completion/Core/_path_files
Base:
@@ -65,22 +65,29 @@
as you wish.
_match_pattern
_match_test
- These are used by Base/_path_files (and hence also Base/_files) for
- file completion with control over matching (whether to complete
- case-insensitively, or to allow insertion before `.', etc.) See
- _match_test for instructions. Note _path_files expects these files
- to be present.
+ These are used by Base/_path_files (and hence also Base/_files)
+ and Base/_comp_parts for file completion with control over
+ matching (whether to complete case-insensitively, or to allow
+ insertion before `.', etc.) See _match_test for instructions.
+ Note _path_files expects these files to be present.
_precommand
Allows completion when the first word on the line has to be ignored,
for example `noglob ...' should ignore the noglob and just complete
as if it wasn't there. Add other such commands to the top line.
_redirect
- Completes after `<' or `<': this version calls _files.
+ Completes after `<' or `>': this version calls _files.
_subscript
For completion in subscripts of parameters, e.g $foo[...].
_vars
Completion for commands which need variables (so this could also be in
the Builtins directory), but also in math environments such as ((...)).
+ _tilde
+ Completion after `~', defaults to user names and named directories.
+ _equal
+ Completion after `=', normally command and alias names are used.
+ _parameter
+ _brace_parameter
+ For completion inside parameter expansions ($... and ${...).
Builtins:
Define completions for various shell builtins. The top line of each file
says which builtins they apply to; in many cases you can guess from the
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~1999-03-01 13:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-01 13:23 Sven Wischnowsky [this message]
1999-03-01 13:16 ` 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=199903011323.OAA14207@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).