From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7928 invoked by alias); 18 Jan 2014 02:20:47 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 32278 Received: (qmail 2355 invoked from network); 18 Jan 2014 02:20:31 -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=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 From: Bart Schaefer Message-id: <140117182029.ZM7806@torch.brasslantern.com> Date: Fri, 17 Jan 2014 18:20:29 -0800 In-reply-to: <20140118005330.GA27889@sym.noone.org> Comments: In reply to Axel Beckert "dir/* expansion doesn't work with directories with apostrophe in the name" (Jan 18, 1:53am) References: <20140118005330.GA27889@sym.noone.org> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: dir/* expansion doesn't work with directories with apostrophe in the name MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Jan 18, 1:53am, Axel Beckert wrote: } } When the directory contains a single quote (apostrophe) in its name, } pressing the tab key to expand dir/* into a list of files no longer } works. What happens instead is that the tab key doesn't do anything } while cursor is inside the dir/* word. This is the behavior for me as far back as zsh-4.2.0 when starting from zsh -f. It's probably related to changing expand-word to use the same internal routines as completion, which happened somewhere during 4.1.x development. Some discussion of this can be found in the threads leading up to users/18243 and subsequently workers/32186 ... The _expand completer and _expand_word widget via compinit appear to handle these quote marks correctly, as of 5.0.5. It's only the default internal expand-word / expand-or-complete that still get stuck.