From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Multiple styles databases RE: list-colors does not work RE: 3.1.6-dev-18
Date: Mon, 14 Feb 2000 12:32:55 +0100 (MET) [thread overview]
Message-ID: <200002141132.MAA08289@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Andrej Borsenkow"'s message of Mon, 14 Feb 2000 14:16:40 +0300
Andrej Borsenkow wrote:
> > Andrej Borsenkow wrote:
> >
> > > list-colors completely stopped to work after installing dev-18.
> > I now have
> > >
> > > zstyle ':completion:*' menu 'select=0'
> > > zstyle ':completion:*:default' list-colors ''
> > >
> > > Menu works, but list-colors not. I tried all sort of things
> > (:completeion:*,
> > > :completion:*:*:*:*:*) without success.
> > >
> > > Surprisingly enough, menu select works :-)
> >
> > That's a result of the default style for list-colors, which has a far
> > more specific pattern. See the discussion started by Peter about
> > default settings.
>
> So, you mean to say, that
>
> zstyle ':completion:*::::default' ...
>
> is more specific, than
>
> zstyle ':completion:::::default' list-colors ''
>
> ???
Of course not. The `:completion:*:default' you gave is less specific
than the thing currently used as default.
> And the following is not described in current manual:
>
> - what empty part means. Is "::" the same as ":*:" from the matching point
> of view?
> - does '*' match muliple parts or just anything in current part?
These are just normal shell-patterns. So `::' matches only `::' and
`:*:' matches `:anything:' and a `*' of course matches any number of
parts (I'm not too happy about that last one).
> And why not to use multiple style sets (like multiple resources in X11)?
> compinit or functions could define there own "default" styles and users
> would define "user" style. If style is not found in user database, it is
> looked up in default database. this would completely eliminate above
> confusion. If user sets "catch-all" style - it is always used; else we
> finally fallback to default style.
I think I prefer Peter's suggestion to get rid of the default styles
in compinit and just make them the defaults used by the completion
functions that use these styles.
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-02-14 11:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-14 11:32 Sven Wischnowsky [this message]
2000-02-14 11:37 ` Andrej Borsenkow
-- strict thread matches above, loose matches on Subject: below --
2000-02-14 11:43 Sven Wischnowsky
2000-02-14 10:56 Sven Wischnowsky
2000-02-14 11:16 ` Multiple styles databases " Andrej Borsenkow
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=200002141132.MAA08289@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.auc.dk \
/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).