From: Bart Schaefer <schaefer@tiny.zanshin.com>
To: Bernd Eggink <eggink@uni-hamburg.de>
Cc: Zsh-workers <zsh-workers@math.gatech.edu>
Subject: Re: compctl -v
Date: Wed, 10 Mar 1999 22:32:44 -0800 (PST) [thread overview]
Message-ID: <14055.25484.913379.910845@awayteam.zanshin.com> (raw)
In-Reply-To: <36E6D2CC.7CFCB1DA@uni-hamburg.de>
Bernd Eggink writes:
> compctl -D -v
This means that all default completions should use parameter names and
only parameter names, which is probably not what you intended.
> these commands are nicely completed:
>
> vared xyz<TAB>
> print $xyz<TAB>
Completion following a $ is a special case and doesn't require compctl
to activate it.
> ls xyz<TAB>
>
> all shell parameters starting with 'xyz' also show up, which IMHO is
> nonsense. Any way to prevent this, and get parameter names completed
> only if preceded by '$' or 'vared'?
Yes; you want to get rid of that compctl -D, and instead use
compctl -v vared
A minimal set of sensible compctls using only built-in completions is:
compctl -B builtin
compctl -m command
compctl -v declare integer local readonly read
compctl -aBFw disable
compctl -daBFw enable
compctl -c exec sched whence where -
compctl -F functions unfunction
compctl -Nv getln
compctl -a unalias
compctl -cn unhash
compctl -k signals trap
# These last few are enabled by default in 3.0, but not in 3.1.2 and later
compctl -b bindkey
compctl -v export typeset unset vared
compctl -o setopt unsetopt
compctl -c which
The argument for leaving out all default compctls from 3.1.2+, last time I
heard it, is that the above set isn't "good enough" by comparison to the
collection in Misc/compctl-examples to be worth having. I've been saying
for at least a year now that I think that's a silly reason to have zsh
out-of-the-box default to completing nothing but file names, but I guess
I'm beating a dead horse.
next prev parent reply other threads:[~1999-03-11 6:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-10 20:15 Bernd Eggink
1999-03-11 6:32 ` Bart Schaefer [this message]
1999-03-11 8:25 Sven Wischnowsky
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=14055.25484.913379.910845@awayteam.zanshin.com \
--to=schaefer@tiny.zanshin.com \
--cc=eggink@uni-hamburg.de \
--cc=schaefer@zanshin.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).