From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Zsh Hackers' List <zsh-workers@zsh.org>
Subject: Re: vim completion problem after workers/35168
Date: Tue, 19 May 2015 01:34:57 +0000 [thread overview]
Message-ID: <20150519013457.GA2024@tarsus.local2> (raw)
In-Reply-To: <150518173034.ZM2314@torch.brasslantern.com>
Bart Schaefer wrote on Mon, May 18, 2015 at 17:30:34 -0700:
> On May 18, 12:40pm, Peter Stephenson wrote:
> } Subject: Re: vim completion problem after workers/35168
> }
> } On Mon, 18 May 2015 14:22:20 +0300
> } Ismail Donmez <ismail@donmez.ws> wrote:
> } > _vim:7: parse error near `)'
> }
> } Yet another annoyance: in the old hack, you got away with having a
> } pattern beginning with "(" (and containing balanced parentheses)
> } followed by an unbalanced ")". Now you don't.
>
> Hrm. Zsh patterns include "(this|that)", and "case" syntax includes
> "pattern)" without an open paren, so ...?
>
> The "old hack" is one of those "well, it really should have been done
> differently in the first place, but it wasn't, so now what?" issues
> that bug me because *somebody* is going to get bitten in the way _vim
> just was.
Is there any case in which the neither pre-35168 code nor post-35168
code gives a parse error, but the semantics are different?
I'm not as worried about previously-valid code becoming syntax error
(I've already found an instance of that "in the wild") as of valid code
becoming valid-but-semantically-different code.
Daniel
next prev parent reply other threads:[~2015-05-19 1:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 10:29 İsmail Dönmez
2015-05-18 10:53 ` Peter Stephenson
2015-05-18 11:22 ` İsmail Dönmez
2015-05-18 11:40 ` Peter Stephenson
2015-05-18 11:42 ` İsmail Dönmez
2015-05-19 0:30 ` Bart Schaefer
2015-05-19 1:34 ` Daniel Shahaf [this message]
2015-05-19 8:44 ` Peter Stephenson
2015-05-19 6:34 ` Mikael Magnusson
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=20150519013457.GA2024@tarsus.local2 \
--to=d.s@daniel.shahaf.name \
--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).