On Fri, Jan 25, 2008 at 06:42:40PM -0800, Daniel Burrows <[EMAIL PROTECTED]> was heard to say: > It's been three years and there's been no reply on this bug, nor is > there a documented way of escaping double-quote characters. Would it be > possible for someone to take a quick look at this patch? I could easily > tweak the code to create a new quoted-string format (eg, using '') that > supports backslash-escapes and not support them in the old format.
Whoops, I edited my mail down until it stopped making sense, apparently. ;-) What I meant to say was: I wonder if the reason my patch hasn't been applied is due to concerns about backwards-compatibility? i.e., if users are already using backslashes in configuration options, then suddenly giving them a new meaning is a bit unkind. One way around this is to also support the use of single quote characters for output, and to support backslash-escapes inside them. OTOH, it looks like single-quotes are currently treated as part of the option value, so I guess there may not be a loophole that you can drive a format fix through without breaking compatibility :-(. Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
