zsh-users
 help / color / mirror / code / Atom feed
From: ml.zsh-workers.454@bitraven.io
To: zsh-users@zsh.org
Subject: change in zstyle file-patterns handling between 5.5.1 & 5.6(.2)?
Date: Sun, 16 Sep 2018 13:50:37 +0200	[thread overview]
Message-ID: <25E31A55-5918-42B8-83B4-DDC58A2D52EA@bitraven.io> (raw)

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

Hi

While I was trying out how to separate folders and files when completing 
`./<tab>` (based on [1]), I noticed a difference in behaviour between 
5.5.1 and 5.6.2.

- **minimal_zshrc.sh**:

	```
autoload -Uz compinit && compinit
zstyle ':completion:*:*:*:*:*' group-name ''
zstyle ':completion:*:descriptions' format '%B%F{red}%d%f%b'
zstyle ':completion:*:*:-command-:*:*' file-patterns 
'*(#q-*):executables:Executables *(-/):directories:Directories'
	```

- 5.5.1:

	```
> /usr/local/Cellar/zsh/5.5.1/bin/zsh -f
% source minimal_zshrc.sh
% ./<tab>
Executables
some_script*
Directories
directory/  folder/
	```

- 5.6.2:

	```
> /usr/local/Cellar/zsh/5.6.2/bin/zsh -f
% source minimal_zshrc.sh
% ./<tab>
executable file
directory/   some_script*  folder/
	```
   Same issue for 5.6 & 5.6.1

Seems like zsh is using a different group in 5.6 ... but a quick look 
through the **NEWS** file in the zsh repo did not give me any idea why 
the versions differ in their behaviour here.
Is this an intentional change?
How can I get the separation back in 5.6 (ideally in a way that also 
works in 5.5)?


[1]: 
https://superuser.com/questions/1326184/why-does-a-value-hyphen-in-tag-order-style-prevent-matching-of-the-exec

             reply	other threads:[~2018-09-16 12:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-16 11:50 ml.zsh-workers.454 [this message]
2018-09-17  2:27 ` Takeshi Banse
2018-09-17  5:58   ` dana
2018-09-17 13:01     ` Daniel Shahaf
2018-09-17 21:09       ` dana
2018-09-25  0:13   ` dana

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=25E31A55-5918-42B8-83B4-DDC58A2D52EA@bitraven.io \
    --to=ml.zsh-workers.454@bitraven.io \
    --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).