From: Thorsten Kampe <thorsten@thorstenkampe.de>
To: zsh-users@sunsite.dk
Subject: Re: .zshrc sanity check
Date: Tue, 6 Apr 2004 01:33:35 +0200 [thread overview]
Message-ID: <m49s1otnjsks$.dlg@thorstenkampe.de> (raw)
In-Reply-To: <17660.1081191572@trentino.logica.co.uk>
* Oliver Kiddle (2004-04-05 20:59 +0100)
> Thorsten Kampe wrote:
>> re-reading the User's guide I have made many changes to my .zshrc and
>
>> zstyle ':completion:*' completer _expand _complete _match _approximate _ignored
>> zstyle ':completion:*:expand:*' glob true
>
> The _match completer is pretty much superfluous if you already use
> _expand to expand any globs.
Okay, I've put "_match" out of "matcher-list".
>> zstyle ':completion:*:approximate:*' insert-unambiguous true
>
> This style is not doing anything. _approximate only looks up that style
> after it has added the number of corrections to the context. I use:
> zstyle ':completion::approximate*:*' insert-unambiguous true
And another one for my .zshrc ;-)
> You might want to think about using more specific contexts for quite a
> few of the styles. It is worth thinking through all the style
> components whenever you set a style.
Yeah, probably. But my understanding of the whole "zstyle" stuff and
syntax is not so deep (for a proof see "This style is not doing
anything" above).
> I prefer to avoid matching anything (with *) in the function component
> with styles that affect completion behaviour.
Why?
>> zstyle ':completion:*:expand:*' subst-globs-only true
>
> You might want to rethink setting that (and your expand styles in
> general since it looks like you've just set everything true).
Yes, almost. Peter Stephenson's description of these options in the
User' Guide is so persuading that I thought: "Sounds good and
reasonable to me. Let's set this to 'true'.".
> Other styles now do a better job with what I tried to do with
> subst-globs-only.
For instance?
> Other than that, it rest comes down to personal preference. I found
> myself thinking "yuk" but not "that's insane" on seeing some of your
> option settings. A couple of options you may want to try setting are
> c_bases and braceccl.
Did that (although I don't know what "yuk" means). I've set most of
these options two and a half years ago when I first got in contact
with zsh and read the User's Guide.
If reading the description of the option made me think "I don't have
the slightest idea what that means", I optioned for the default. And
every time I thought "Wow, looks like some extra functionality", I set
the option.
Shame on me that I had "shwordsplit" set until a few weeks ago ;-)
Thorsten
prev parent reply other threads:[~2004-04-05 23:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-03 12:12 Thorsten Kampe
2004-04-05 18:59 ` Oliver Kiddle
2004-04-05 23:33 ` Thorsten Kampe [this message]
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='m49s1otnjsks$.dlg@thorstenkampe.de' \
--to=thorsten@thorstenkampe.de \
--cc=zsh-users@sunsite.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).