Re: Bug in { completion's comma removal

[Peter Stephenson <pws@xxxxxxx>]

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@xxxxxxx>                  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