zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: Bug in { completion's comma removal
Date: Mon, 13 Feb 2006 10:51:53 +0000	[thread overview]
Message-ID: <EXCHANGE03zKQMjWTUU0000c0b2@exchange03.csr.com> (raw)
In-Reply-To: <20060211040001.GG14115@dot.blorf.net>

Wayne Davison wrote:
> On Fri, Jan 06, 2006 at 09:07:19PM +0100, Mikael Magnusson wrote:
> > While we're talking about {} [...] there's no way (that i've figured
> > out) to escape a comma inside the braces.
> 
> I've looked at this, and I'm thinking that the easiest thing to do is to
> sometimes mark a comma with ISPECIAL, just like {, }, space, etc.  Since
> user-typed commas inside a brace are already transformed into "Comma"
> (0x97), this ensures that completing filenames that contain a comma get
> a backslash prefixed, and that a user-typed "\," sequence does not lose
> the backslash.  I'll attach a patch that works, but I'd appreciate some
> input if someone would care to take a look at what I've done.

It's a bit of a hack, but that's hardly a big change around here...

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK                          Tel: +44 (0)1223 692070


To access the latest news from CSR copy this link into a web browser:  http://www.csr.com/email_sig.php


  reply	other threads:[~2006-02-13 10:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-06 18:00 Wayne Davison
2006-01-06 20:07 ` Mikael Magnusson
2006-01-06 20:36   ` Wayne Davison
2006-01-07  4:50     ` Mikael Magnusson
2006-02-11  4:00   ` Wayne Davison
2006-02-13 10:51     ` Peter Stephenson [this message]
2006-02-09 22:17 ` Wayne Davison

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=EXCHANGE03zKQMjWTUU0000c0b2@exchange03.csr.com \
    --to=pws@csr.com \
    --cc=zsh-workers@sunsite.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).