From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26053 invoked by alias); 28 Dec 2013 08:23:09 -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: 32191 Received: (qmail 17208 invoked from network); 28 Dec 2013 08:22:53 -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: <131228002311.ZM25536@torch.brasslantern.com> Date: Sat, 28 Dec 2013 00:23:11 -0800 In-reply-to: <131227100556.ZM25175@torch.brasslantern.com> Comments: In reply to Bart Schaefer "While on the subject of expansion ..." (Dec 27, 10:05am) References: <131227100556.ZM25175@torch.brasslantern.com> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: While on the subject of expansion ... MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Dec 27, 10:05am, Bart Schaefer wrote: } } I noticed that the built-in expand-word widget also mishandles the case } with a backslashed quote. Tangentially related, and mentioning it just so it's on the record in case I forget about it later: The "compfiles" builtin is confused by files whose names contain backslashes. This is another pathological case that may not be worth expending much effort.