From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "ZSH workers mailing list" <zsh-workers@sunsite.auc.dk>
Subject: Styles usage problem
Date: Thu, 23 Dec 1999 19:14:17 +0300 [thread overview]
Message-ID: <001e01bf4d60$c30a1400$21c9ca95@mow.siemens.ru> (raw)
I just discovered, that completion does not use completers I've just set up.
Look here:
bor@itsrm2% cat ~/.zsh-styles
compstyle '*' completer '_oldlist' '_complete' '_correct' '_approximate'
'_match'
...
but
bor@itsrm2% zstyle -L
zstyle ':completion:*' completer _complete
zstyle ':completion*' completer _oldlist _complete _correct _approximate _match
In other words, I told zsh to use specific completers in every case - but Zsh
installed it's own, "more specific" style - and simply ingnored my settings.
/andrej
next reply other threads:[~1999-12-23 16:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-23 16:14 Andrej Borsenkow [this message]
1999-12-23 22:20 ` Peter Stephenson
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='001e01bf4d60$c30a1400$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--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).