From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Mark Borges <mdb@cdc.noaa.gov>, zsh-workers@math.gatech.edu
Cc: clive@epos.demon.co.uk
Subject: Re: zsh.texi
Date: Wed, 12 Jun 1996 23:55:59 -0700 [thread overview]
Message-ID: <960612235602.ZM31052@candle.brasslantern.com> (raw)
In-Reply-To: Mark Borges <mdb@cdc.noaa.gov> "Re: zsh.texi" (Jun 12, 11:25pm)
On Jun 12, 11:25pm, Mark Borges wrote:
} Subject: Re: zsh.texi
}
} Please take a look if you're interested. We would appreciate any
} suggestions or comments (or better, patches) anyone may have.
I'm just glancing at the programmable completion section at the moment.
Some of it is still pretty hard to decipher. Here's an example:
-d This can be combined with -F, -B, -w, -a, -R and -G to get names of
disabled functions, builtins, reserved words or aliases.
-e Without -d this option has no effect. Otherwise this can be combined
with -F, -B, -w, -a, -R and -G to get names of functions, builtins,
reserved words or aliases even if they are disabled.
That stuff under -e doesn't make sense to me -- Without -d, has no effect?
You mean I have to use `compctl -d -e ...'? Why? -- and it conflicts with
the zshcompctl.man description:
-e Names of executable (and enabled) commands.
Here's another example:
-C controls completion when there is no current command, in other words when
the command word itself is being completed. Without this command, the
names of any executable command (whether in the path or specific to
the shell, such as aliases or functions) are completed.
"Without this command, ..." ?? Without what command? I think it means
"If no `compctl -C' command has been issued in the current shell, ...".
Then there's this:
If the + flag is alone and followed immediately by the command list, the
completion behavior for all the commands in the list is reset to its default
by deleting the command from the list of those handled specially.
I think this means:
If the + flag is alone and followed immediately by a list of command names,
any previous programmable completion for each of those commands is disabled.
This restores the default completions for the listed commands.
As a general remark, this sort of documentation should avoid talking about
how a given operation is accomplished (e.g., above, dump the "by deleting
the command from the list ... handled specially") and just state what the
end result is. Only discuss how something works if that's important for
using the feature correctly; and even then, *first* concisely describe
the end result, and *then* elaborate how it comes to pass.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.nbn.com/people/lantern
New male in /home/schaefer:
>N 2 Justin William Schaefer Sat May 11 03:43 53/4040 "Happy Birthday"
next prev parent reply other threads:[~1996-06-13 7:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-06-10 15:52 zsh.texi Clive Messer
1996-06-10 16:17 ` zsh.texi Hrvoje Niksic
1996-06-10 16:39 ` zsh.texi Zoltan Hidvegi
1996-06-10 19:01 ` zsh.texi Clive Messer
1996-06-13 5:25 ` zsh.texi Mark Borges
1996-06-13 6:26 ` zsh.texi Bart Schaefer
1996-06-13 13:49 ` zsh.texi Clive Messer
1996-06-13 15:30 ` zsh.texi Bart Schaefer
1996-06-13 17:19 ` zsh.texi Mark Borges
1996-06-13 6:55 ` Bart Schaefer [this message]
1996-06-15 1:53 ` zsh.texi Zoltan Hidvegi
1996-06-15 7:44 ` zsh.texi Zefram
1996-06-15 22:08 ` <> redirection operator (was: zsh.texi) Zoltan Hidvegi
1996-06-16 13:23 ` Zefram
1996-06-17 13:10 ` Zoltan Hidvegi
1996-06-17 13:56 ` Peter Stephenson
1996-06-17 15:16 ` Peter Whaite
1996-06-13 7:18 ` zsh.texi Bart Schaefer
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=960612235602.ZM31052@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=clive@epos.demon.co.uk \
--cc=mdb@cdc.noaa.gov \
--cc=schaefer@nbn.com \
--cc=zsh-workers@math.gatech.edu \
/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).