From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: 39093 erases variant with slashes (was: Re: Pattern matching with _files vs command line)
Date: Sun, 11 Sep 2016 09:18:11 -0700 [thread overview]
Message-ID: <160911091811.ZM19992@torch.brasslantern.com> (raw)
In-Reply-To: <20160911094221.GA18467@fujitsu.shahaf.local2>
On Sep 11, 9:42am, Daniel Shahaf wrote:
} Subject: 39093 erases variant with slashes (was: Re: Pattern matching with
}
} Bart Schaefer wrote on Fri, Sep 09, 2016 at 19:40:33 -0700:
} > ADDITIONAL ASIDE to -workers: The weird side-effects that result
} > here from having the trailing "/" in the completion results seem
} > to be tangentially related to the thread from 39093 where the whole
} > current word gets erased. When all the completions end in "/", it
} > is the first unambigous character, so
} >
} > % foo <TAB>
} > % foo /
} >
}
} Could you share the reproducer for this please?
Run this anywhere with more than one subdirectory not all of which have
a common prefix; e.g., the zsh source tree:
torch% compinit -D
torch% _f () { _files -g '*(/M)' }
torch% compdef _f f
torch% zstyle \* file-patterns %p:globbed-files
torch% f <TAB>
torch% f /
If the zstyle is omitted, the groups globbed-files and directories contain
identical sets of matches but are for some reason not de-duped against one
another (probably because none of them matches an actual file name) so you
get a listing instead of the unambiguous-insertion behavior.
next prev parent reply other threads:[~2016-09-11 16:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-09 5:39 Pattern matching with _files vs command line Marko Myllynen
2016-09-10 2:40 ` Bart Schaefer
[not found] ` <20160911094221.GA18467@fujitsu.shahaf.local2>
2016-09-11 16:18 ` Bart Schaefer [this message]
2016-09-12 4:30 ` Marko Myllynen
2016-09-12 15:18 ` Bart Schaefer
2016-09-12 15:34 ` Marko Myllynen
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=160911091811.ZM19992@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@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).