From: Bart Schaefer <schaefer@brasslantern.com>
To: martin f krafft <madduck@madduck.net>, zsh-users@zsh.org
Subject: Re: Making file-patterns and tag-order work
Date: Wed, 22 Mar 2017 21:13:37 -0700 [thread overview]
Message-ID: <170322211337.ZM6292@torch.brasslantern.com> (raw)
In-Reply-To: <20170322033504.nodq5vk34ehtwa44@fishbowl.rw.madduck.net>
On Mar 22, 4:35pm, martin f krafft wrote:
}
} also sprach Bart Schaefer <schaefer@brasslantern.com> [2017-03-22 14:15 +1300]:
} > } zstyle ':completion:*:argument*' tag-order "
} > } directories
} > } globbed-files files all-files
} > } backup-files
} > } compiled-files
} > } temp-files
} > } vim-swap-files
} > } "
} >
} > This is wrong. If you combine tags into a single string, they
} > will all be sorted together. tag-order is a list -- try without
} > the double quotes around the value (which means you'll need
} > backslashes at the end of each line, or similar).
}
} I also tried that. It makes absolutely no difference, actually.
Oops, my bad. You want group-order here, not tag-order.
group-order
This style is additional to the group-name style to specify the
order for display of the groups defined by that style (compare
tag-order, which determines which completions appear at all).
I'm surprised no one else jumped in on this. The fact that they're both
named "-order" is a bit confusing; for tag-order, it means the order in
which the completions are attempted, and for group-order it means the
order in which the results are displayed.
next prev parent reply other threads:[~2017-03-23 4:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 9:49 martin f krafft
2017-03-22 1:15 ` Bart Schaefer
2017-03-22 3:35 ` martin f krafft
2017-03-23 4:13 ` Bart Schaefer [this message]
2017-03-24 6:59 ` martin f krafft
2017-03-24 9:19 ` Mikael Magnusson
2017-03-24 10:18 ` martin f krafft
2017-03-24 23:15 ` Bart Schaefer
2017-03-25 11:02 ` martin f krafft
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=170322211337.ZM6292@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=madduck@madduck.net \
--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).