From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: zsh-workers@zsh.org
Subject: bug with expansion and backslashes
Date: Sun, 16 Aug 2015 01:14:10 +0200 [thread overview]
Message-ID: <32312.1439680450@thecus.kiddle.eu> (raw)
In-Reply-To: <150425101458.ZM30959@torch.brasslantern.com>
On 25 Apr, Bart wrote:
> } > add backslash to alias expansion matching in _expand
> --- a/Completion/Base/Completer/_expand
> setopt aliases
> eval 'exp=( ${${(e)exp//\\[
> -]/ }//(#b)([
> +]/ }//(#b)([ \\
> ])/\\$match[1]} )' 2>/dev/null
I just noticed that expansion was broken when I tried to expand *\~
(exiftran backs up files with a trailing ~ and I wanted to clean them up)
git bisect led me to 33ff5d06 which is the patch above.
What's not clear to me is what problem this patch was trying to solve.
To reproduce, the following seems to be enough:
zsh -f
autoload -U compinit ; compinit
zstyle ':completion:*::::' completer _expand _complete
bindkey '^I' complete-word
setopt extendedglob
Oliver
next prev parent reply other threads:[~2015-08-15 23:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 3:05 broken parsing with $((`:`)) Mike Frysinger
2015-04-15 9:03 ` Peter Stephenson
2015-04-15 15:13 ` Bart Schaefer
2015-04-15 15:26 ` Peter Stephenson
2015-04-15 16:23 ` Potential 3.0.8 [was Re: broken parsing with $((`:`))] Bart Schaefer
2015-04-22 9:01 ` Peter Stephenson
2015-04-25 17:14 ` Pre-3.0.8 consolidated PATCH Bart Schaefer
2015-04-25 18:29 ` Axel Beckert
2015-04-25 18:46 ` FIVE-ZERO-EIGHT (was Re: Pre-3.0.8 consolidated PATCH) Bart Schaefer
2015-08-15 23:14 ` Oliver Kiddle [this message]
2015-08-16 1:22 ` bug with expansion and backslashes Bart Schaefer
2015-04-15 15:37 ` broken parsing with $((`:`)) Peter Stephenson
2015-04-15 16:13 ` Bart Schaefer
2015-04-15 16:31 ` Peter Stephenson
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=32312.1439680450@thecus.kiddle.eu \
--to=okiddle@yahoo.co.uk \
--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).