From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: 5.0.3 +* -> git completion regression
Date: Mon, 16 Dec 2013 07:56:05 -0800 [thread overview]
Message-ID: <131216075605.ZM1385@torch.brasslantern.com> (raw)
In-Reply-To: <20131216103726.GA25715@redoubt.spodhuis.org>
On Dec 16, 5:37am, Phil Pennock wrote:
}
} % zsh -f
} ilmenite% emulate ksh
} ilmenite% case "$foo" in +*) echo snert;; esac
} zsh: bad pattern: +*
} %
Here's what I get when compiled with debugging turned on:
$ case foo in +*) echo bar;; esac
BUG: character not handled in patcomppiece
zsh: bad pattern: +*
$
(Not sure why there's a leading space on the "BUG:" line, seems odd.)
Anyway it looks like we've triggered lookahead on "+" because of ksh
emulation, but then when the next character is not a paren it fails to
back up and reprocess the "+", or something to that effect.
This is all tangled up with "disable -p" changes, but selectively baking
out chunks that involve the kshchar flag hasn't so far shown anything.
next prev parent reply other threads:[~2013-12-16 15:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 8:14 Phil Pennock
2013-12-16 9:47 ` Peter Stephenson
2013-12-16 10:37 ` Phil Pennock
2013-12-16 15:56 ` Bart Schaefer [this message]
2013-12-16 22:08 ` Peter Stephenson
2013-12-17 17:48 ` Phil Pennock
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=131216075605.ZM1385@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).