zsh-users
 help / color / mirror / code / Atom feed
From: martin f krafft <madduck@madduck.net>
To: zsh-users@zsh.org
Subject: Re: Making file-patterns and tag-order work
Date: Wed, 22 Mar 2017 16:35:04 +1300	[thread overview]
Message-ID: <20170322033504.nodq5vk34ehtwa44@fishbowl.rw.madduck.net> (raw)
In-Reply-To: <170321181534.ZM1895@torch.brasslantern.com>

[-- Attachment #1: Type: text/plain, Size: 1685 bytes --]

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.

Apart from that, tag-order actually takes "sets of space-separated
lists" and I read Peter's description in the Zsh Guide:

  If you put the tags into the same word by quoting, for example
  "local-directories path-directories", then they would be tried at
  the same time, which in this case gives you the effect of the
  default.

to be exactly what I want, i.e. if the completion can be done from
the set of directories or files already, then I *still* want it to
offer me the other tags, and this is why I think I need to put all
the tags into the same set by quoting. If I didn't do this, then the
remaining sets of tags would simply not be considered.

But again, it actually makes no difference whether I use a single
quoted string of all tags, or each tag separately. I think the
problem is elsewhere…

-- 
@martinkrafft | http://madduck.net/ | http://two.sentenc.es/
 
"nicht durch zorn, sondern durch lachen tötet man."
                                                 - friedrich nietzsche
 
spamtraps: madduck.bogus@madduck.net

[-- Attachment #2: Digital GPG signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current) --]
[-- Type: application/pgp-signature, Size: 1118 bytes --]

  reply	other threads:[~2017-03-22  3:35 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 [this message]
2017-03-23  4:13     ` Bart Schaefer
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=20170322033504.nodq5vk34ehtwa44@fishbowl.rw.madduck.net \
    --to=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).