Re: Default compctls

[Zefram <A.Main@dcs.warwick.ac.uk>]

>compctl -c -		# BUG!  `-' has special meaning to `compctl'!

compctl -c - -

compctl -L will list it in this form too.


>Further, there doesn't seem to be any reason not to include the following
>additional defaults:
[...]

Actually, I don't see the point in having any default completions at
all (except for the -C, -D and -T completions, of course).  The
compctl-examples script already has completions for (almost?) all
builtins, and I'd rather not have the shell default to this fairly
arbitrary magic behaviour.  Besides, how clever should the default
completion for, say, `kill` be?  (Include signal names?  Process IDs?)

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

There's already a list of signals available.  $signals[2,-3] is the
list of signals you can actually send to a process.  $signals itself is
the list of trappable `signals'.  I think there's room for a $limits
array, though.

-zefram