From: Filipe Silva <filipe.silva@gmail.com>
To: Peter Stephenson <p.stephenson@samsung.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: make zstyle ignore both _* and __* commands
Date: Tue, 4 Jul 2017 08:22:30 -0300 [thread overview]
Message-ID: <CAEwkUWPj4tmXsYb+4duNnd8QWN2bcpz_UT3v5_mObwfg3Si7Ww@mail.gmail.com> (raw)
In-Reply-To: <20170703124730.16e316a8@pwslap01u.europe.root.pri>
[-- Attachment #1: Type: text/plain, Size: 1150 bytes --]
Hi Peter, this is great, did not know about that.
Is there a way to insert a newline after the headers? I tried \n and \\n
but it did not render the expected result.
On Mon, Jul 3, 2017 at 8:47 AM, Peter Stephenson <p.stephenson@samsung.com>
wrote:
> On Sun, 2 Jul 2017 18:37:14 -0300
> Filipe Silva <filipe.silva@gmail.com> wrote:
> > omg, you are absolutely right. It should do already this because of the
> > regex.
> > I'm so ashamed of myself.
> >
> > All right, I did found a case where this does not work.
> >
> > if I type d_[tab] it shows this: http://imgur.com/ZSBZHvp (notice the
> > __fast_highlight...)
>
> __fast_highlight doesn't occur in the zsh source tree, so that's in some
> library you've got. I would guess it's not being matched as a function
> at all, otherwise it's no different from the other cases. Maybe it's a
> variable; you can complete those in command position for assignment
> purposes.
>
> You'll probably find it helps to have headers for different types of
> match turned on for this sort of purpose --- try:
>
> zstyle ':completion:*' format 'Completing %d'
> zstyle ':completion:*' group-name ''
>
> pws
>
next prev parent reply other threads:[~2017-07-04 11:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 21:39 Filipe Silva
2017-07-02 17:20 ` Peter Stephenson
2017-07-02 21:37 ` Filipe Silva
2017-07-03 11:47 ` Peter Stephenson
2017-07-04 11:22 ` Filipe Silva [this message]
2017-07-04 11:39 ` Daniel Shahaf
2017-07-04 14:05 ` Filipe Silva
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=CAEwkUWPj4tmXsYb+4duNnd8QWN2bcpz_UT3v5_mObwfg3Si7Ww@mail.gmail.com \
--to=filipe.silva@gmail.com \
--cc=p.stephenson@samsung.com \
--cc=zsh-users@zsh.org \
/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).