Re: Default compctls

[Zoltan Hidvegi <hzoli@xxxxxxxxxx>]

> 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:

I think compctls belong to the user-level code.  Adding new default
compctls just increase zsh size and it is quite useless as these are
usually overriden by the user.  Zsh is quite unusable without good startup
files anyway.  I change 28 options define 196 compctl's, 73 aliases and 57
functions and about 25 key bindings in my startup files.  The default
option setting is the worst.  I use the following options:

setopt LIST_TYPES AUTO_LIST LIST_AMBIGUOUS ALWAYS_LAST_PROMPT AUTO_MENU \
        AUTO_PARAM_KEYS EXTENDED_GLOB APPEND_HISTORY AUTO_CD CORRECT \
        NO_HUP MAGIC_EQUAL_SUBST NO_LIST_BEEP PUSHD_MINUS \
        RC_QUOTES LONG_LIST_JOBS HIST_IGNORE_DUPS NUMERIC_GLOB_SORT \
        COMPLETE_IN_WORD BRACE_CCL AUTO_NAME_DIRS NO_PROMPT_CR \
        AUTO_REMOVE_SLASH AUTO_PARAM_SLASH
unsetopt BG_NICE NOTIFY

> 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

I think -- should mean the end of completion flags as it already means that
with extended completions.  Note that Misc/compctl-examples contains better
compctl's for command, exec, moglob, -.  Look at the section near line 52.

> Is there any workaround for the bug noted above?

No, but

compctl -c exec -

works.

Zoltan