From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2430 invoked by alias); 16 Dec 2013 22:40:34 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 18231 Received: (qmail 28586 invoked from network); 16 Dec 2013 22:40:29 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:references:from:content-type:in-reply-to :message-id:date:to:content-transfer-encoding:mime-version; bh=nb5MPLbIBGfpFBpoPwJ9c4HByYnlw8QKQCroLEiUIIk=; b=DJlb2Z6RvSHmD6J7BOxFTKC8YE5np5eoBQXr0qa7e4p4jaa7OhjSQqwFUniO/XCkIA 5TgeDoLM/JOkua6/Juo8lvT/fYCsqrirNyDAgGH64e8kiSl+mnK6D8KBOGKYU+splbCq R2N9DXJMXuECH7906fn9gJdTdpipmEWG9Zs5Cy3fOz4L24hrd3DxZGhCPjLaa2idQO/T IEU069eF3DwGT/HcrwSgzvfzAGa5rRKHcbhuEWlnIR5jpi0D/jmgtmicAjjMna8HrnqH R69aQsYR89dVyr/w7m3pYMppgxWM6+a1LExT9kgK1qwzv/1GfhFC/V2bb5NwW7CVskvv Dzaw== X-Gm-Message-State: ALoCoQkQmQLf54CHF16M4ELwH4Niax4VSmQjcYeY0lUpLyNqjOwIm01Wm6GDvI3TDSQgOnF8Ze/9 X-Received: by 10.66.25.100 with SMTP id b4mr23030700pag.24.1387233625505; Mon, 16 Dec 2013 14:40:25 -0800 (PST) Subject: Re: Pattern problem in the new zsh 5.0.3 References: <52AF6590.9020802@topbug.net> From: Hong Xu Content-Type: text/plain; charset=us-ascii X-Mailer: iPhone Mail (11B554a) In-Reply-To: <52AF6590.9020802@topbug.net> Message-Id: <5622AE48-B272-40C8-9344-0864EE34DEED@topbug.net> Date: Mon, 16 Dec 2013 14:34:43 -0800 To: "zsh-users@zsh.org" Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) I need to mention that these problems don't exist in 5.0.2. Hong > On Dec 16, 2013, at 12:41, Hong Xu wrote: >=20 > Hi all, >=20 > After I upgraded to zsh 5.0.3, I found a few issues. It looks like they ar= e both related to the glob pattern. >=20 > 1. When I tried to use "git push origin " to perform autocompletion, t= he following error occurs: >=20 > __git_complete_remote_or_refspec:33: bad pattern: +* > __git_complete_remote_or_refspec:33: bad pattern: +* > __git_complete_remote_or_refspec:33: bad pattern: +* >=20 > 2. When I tried to use rvm (see https://github.com/wayneeseguin/rvm/issues= /2431), something similar occurs: >=20 > | __rvm_clean_path:12: bad pattern: *:/Users/hong/.rvm/gems/ruby-1.9.3= -p448@global/bin:*| >=20 >=20 > I'm not familiar with the rvm codebase, so I cannot afford any details on t= hat. But my point is, it seems that something related to pattern has broken i= n the new version. >=20 > Can anyone look into this, please? >=20 > Thanks! > Hong