From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@math.gatech.edu
Subject: Default compctls
Date: Sat, 6 Jul 1996 10:50:27 -0700 [thread overview]
Message-ID: <960706105029.ZM17352@candle.brasslantern.com> (raw)
Recent changes to compctl and to some other zsh behaviors lead me to ask
whether we should revise the default compctls. Here's the current set:
compctl -b bindkey
compctl -c builtin
compctl -v export
compctl -o setopt
compctl -v typeset
compctl -v unset
compctl -o unsetopt
compctl -v vared
compctl -c which
compctl -C -c
compctl -D -f
compctl -T
First question: Shouldn't that be `compctl -B builtin`? If not, why not?
Next, an observation and (possibly) a bug: The change to make `command',
`exec', `noglob', and `-' into builtins (rather than keywords) has caused
command completion for those words to stop working. This would seem to
call for some new default compctls:
compctl -c - # BUG! `-' has special meaning to `compctl'!
compctl -m command
compctl -c exec
compctl -c noglob
Is there any workaround for the bug noted above?
Further, there doesn't seem to be any reason not to include the following
additional defaults:
compctl -j bg disown fg jobs kill wait
compctl -v declare integer local
compctl -aBFw disable
compctl -daBFw enable
compctl -F functions
compctl -Nv getln read
compctl -pv readonly
compctl -c sched
compctl -a unalias
compctl -F unfunction
compctl -cn unhash
compctl -p unset
compctl -c whence where
Particularly those last; why should `which' get a default completion, but
not `whence' or `where'?
As a final remark, it would be nice if `emulate', `limit', `trap' and
`ulimit' had some built-in equivalents of `compctl -k "(...)"' because
there's no obvious way to generate the lists of emulations or limits;
and `compctl -k "($(kill -l))" trap' is just re-using a list that was
already generated at compile time, so it might as well get compiled in
as a completion as well.
Comments?
--
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 reply other threads:[~1996-07-06 17:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-07-06 17:50 Bart Schaefer [this message]
1996-07-06 18:10 ` Zoltan Hidvegi
1996-07-06 19:07 ` Bart Schaefer
1996-07-06 18:38 ` Zefram
1996-07-06 20:01 ` 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=960706105029.ZM17352@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--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).