zsh-workers
 help / color / mirror / code / Atom feed
From: Mikael Magnusson <mikachu@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: vim completion problem after workers/35168
Date: Tue, 19 May 2015 08:34:01 +0200	[thread overview]
Message-ID: <CAHYJk3SHgHMBMv1GiYX5FCEw76dm+2zijRoKV9Rizb9TS9fchA@mail.gmail.com> (raw)
In-Reply-To: <150518173034.ZM2314@torch.brasslantern.com>

On Tue, May 19, 2015 at 2:30 AM, Bart Schaefer
<schaefer@brasslantern.com> wrote:
> 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.

I agree, there are other places in the distributed functions that are
currently broken by this change, and at least one in my own set of
functions. We can't just break backwards compat like this.

-- 
Mikael Magnusson


      parent reply	other threads:[~2015-05-19  6:34 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
2015-05-19  8:44           ` Peter Stephenson
2015-05-19  6:34         ` Mikael Magnusson [this message]

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=CAHYJk3SHgHMBMv1GiYX5FCEw76dm+2zijRoKV9Rizb9TS9fchA@mail.gmail.com \
    --to=mikachu@gmail.com \
    --cc=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).