From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21739 invoked by alias); 12 Jan 2013 05:00:48 -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: 30961 Received: (qmail 6542 invoked from network); 12 Jan 2013 05:00:46 -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 Received-SPF: none (ns1.primenet.com.au: domain at closedmail.com does not designate permitted sender hosts) From: Bart Schaefer Message-id: <130111210033.ZM11819@torch.brasslantern.com> Date: Fri, 11 Jan 2013 21:00:33 -0800 In-reply-to: Comments: In reply to Drew Frank "Possible file completion bug when the path contains a backslash" (Jan 11, 11:22am) References: X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: Possible file completion bug when the path contains a backslash MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Jan 11, 11:22am, Drew Frank wrote: } } $ autoload -U compinit } $ compinit } $ ls bad\\dir/[TAB] } } Any idea what's going on here? Is this, in fact, a bug? It appears to be a bug in the (largely undocumented) compfiles builtin, which generates a glob pattern of 'baddir*(-/)' for the directory in question, which then does not match. Special characters other than a backslash appear to be handled correctly, at least in a few minimal tests I tried. Don't have time right now to try to trace this down (and frankly don't care to venture into that part of the code if I don't have to ...).