* Frank Terbeck <bts@bts.grml.org> [2008-01-28 20:04]:
> > > > +typeset -a conf_dir conf_ignore
> > > Please use 'local' variables.
> > *argh* Sure! But isn't typeset automatically local in functions and
> > such?
> > Or did I miss something here?
> Yeah, but see the docs for the local builtin.
> It forbids -f and -g.
> ...and (more importantly) it is by far more clear, what is meant, if
> you just use local.
Ok, ic. It's indeed the better way to go.

> IMO, *nothing* should *ever* look in 'skel' for anything.
Yes, it is. Now that I think about it. Sure. I guess, I used it for
testing the regex for `_files -g' and just left it then.

Btw, do you think it makes sense cascading the completion for config
files the way it is done in the patch.

-[snip]-
% regex='([^.]##|*gz)(.)'
-[snap]-

And, as speaking of it, why the heck does the completion spit out dir.
While, when executed on the command line, e.g.

-[snip]-
% la {.newsbeuter,/usr/share/doc/newsbeuter/examples}/([^.]##|*gz)(.)
-[snap]-

it's working fine?

And, is there a way to give another description of where the files
come from. Kinda like groups. E.g.

,----
| % newsbeuter -C
| Completing - configfile
| Completing in ~/.newsbeuter
| config           error_log        killfile         saved_articles/
| filter           queue            urls
| Completing in /usr/share/doc/newsbeuter/examples
| config.gz
`----

Kind regards,
z3ttacht