On Mon, Oct 11, 2010 at 10:08:06AM +0200, Karl Mikaelsson wrote: > On 2010-10-08 15:04, Oswald Buddenhagen wrote: > >>How should unknown escape sequences be handled? I.e. does "\k" > >>mean "\k" or "k"? > >> > >whatever. it's invalid. > > That's the point of the question, what's the preferred action for > dealing with invalid quotes? Should a parser make a best effort > attempt at trying to find out what the user intended, or perhaps > refuse to touch the rest of the file, or anywhere in between? > it's up to you. you can make a best effort or pop up an error message. i would prefer the latter, but it might be bothersome to propagate the condition from the lowest layers all the way up, so whatever.
> What shell quoting rules are you refering to by the way? As you didn't > specify, perhaps someone will interpret shell command as a tcsh shell > command and quote accordingly to that? > "the shell" is a bourne shell (/bin/sh, you know). a c shell is always explicitly referred to as such. > >that's how kde implemented it long before the spec was written, and > >anyone who thinks something different is meant should be shot. ;) > > The problem is that until that is explicitly stated by the spec, > your views are just the opinion of someone on the internet. > it's the opinion of one of those who implemented it on the kde side. if the spec disagrees, then, well, blame the authors of the spec (and me for not shooting them in time :D). _______________________________________________ xdg mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/xdg
