From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11419 invoked by alias); 27 Oct 2010 15:44:17 -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: 28380 Received: (qmail 24424 invoked from network); 27 Oct 2010 15:44:06 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) 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.1 Received-SPF: none (ns1.primenet.com.au: domain at closedmail.com does not designate permitted sender hosts) From: Bart Schaefer Message-id: <101027084345.ZM31119@torch.brasslantern.com> Date: Wed, 27 Oct 2010 08:43:45 -0700 In-reply-to: <20101027110240.16941d1f@pwslap01u.europe.root.pri> Comments: In reply to Peter Stephenson "Re: Prefixed backslash removed when completing command" (Oct 27, 11:02am) References: <4BF51CF3.8010609@kth.se> <4CC7EB88.8020105@kth.se> <20101027110240.16941d1f@pwslap01u.europe.root.pri> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: Mikael Auno , zsh-workers@zsh.org Subject: Re: Prefixed backslash removed when completing command MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Oct 27, 11:02am, Peter Stephenson wrote: } } The internals of completion are complicated. There is no prospect of it } ever being able to preserve quotations in a general way. In particular } there is no prospect of it ever being able to retain backslashes that } have no basic syntactic effect. It strikes me that it might be possible to special-case a backslash as the very first character in $BUFFER, but it's probably not worth the effort ...