From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-30959-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 14461 invoked by alias); 11 Jan 2013 19:22:51 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 30959
Received: (qmail 8875 invoked from network); 11 Jan 2013 19:22:48 -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.6 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED,RCVD_IN_DNSWL_LOW,
	T_DKIM_INVALID,T_TO_NO_BRKTS_FREEMAIL autolearn=no version=3.3.2
Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.220.54 as permitted sender)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:from:date:message-id:subject:to:content-type;
        bh=XeuNCcFAPRg1XagcYVHxS171E5yWm0QrZejgkXMvXv4=;
        b=rdmglinKS3Od1VittuFkGIxpRoxgFu3FDe8pFsZ5tBPJwm8IMsUHFpeh4F3p9bXMoN
         p4ugTvalZCnEWb01eMkgmNRo8p7gtfJdnTKcIJKCWP/fN6DP04wqzWsqcxPyK7eKkAog
         eX9BC6Idp2sEZCqdiKVV7TgcH6CbeggYXAbqDkxHPvOsRqqF7vlwLxv0JJFc7bRucV0r
         2yJCvflCd+DVMIgPFZJLWJVduau6mIPaH7G/JWbvzlkrMJoaKOT1aBppCE/iulHnGfVl
         qqYinb/pdRdZwrZ9gdyJ/e77fnfliln4lJol/Ttul+m0TqVwhemFmIvKyNHqtyQ5DtXA
         9aIA==
MIME-Version: 1.0
From: Drew Frank <drewfrank@gmail.com>
Date: Fri, 11 Jan 2013 11:22:28 -0800
Message-ID: <CA+pPVKvdEF_uciZ99pcCkpUwyrdrDD3GTLgN+BPqHpDtTEFVXA@mail.gmail.com>
Subject: Possible file completion bug when the path contains a backslash
To: zsh-workers@zsh.org
Content-Type: text/plain; charset=ISO-8859-1

Hi zsh-workers,

Briefly, file completion is not working as expected when (1) the
file's path contains a backslash; and (2) I've run compinit. A small
test case that reproduces the problem is provided in my superuser post
(http://superuser.com/questions/531875/zsh-compinit-breaks-file-completion-when-there-is-a-backslash-in-the-path),
but I will repeat it here for convenience:

$ zsh -f
$ mkdir bad\\dir
$ touch bad\\dir/myfile
$ ls bad\\dir/[TAB]

At this point, the path is completed to "bad\\dir/myfile", which is
the behavior I expect. However:

$ autoload -U compinit
$ compinit
$ ls bad\\dir/[TAB]

After running compinit, the completion no longer works. I originally
thought this was "correct" behavior that I could change via some
setting, but someone on the IRC channel told me that they followed
these steps and could not reproduce the problem. They were using zsh
5.0.0-dev-0. I ran this example using both 5.0.2 and 4.3.10, and in
both cases completion failed after running compinit.

Any idea what's going on here? Is this, in fact, a bug?

Thanks,
Drew