On Thu, Sep 26, 2013 at 09:19:04AM -0500, guns wrote: > The only reservation I have is that all configuration arguments must now > backslash-escape literal " and \ regardless of whether or not they are > enclosed in double quotes. This is reminiscent of a shell's input parser > correct.
> and is unlike string handling in most other kinds of configuration > files. > i don't think this is really true. the quoting rules of the config formats are totally arbitrary and completely mixed. the example nearest to mbsync (in terms of use cases) is mutt, and it seems to use more shell-like rules. > This allows users to copy and paste ugly passwords like a\b"c\ into > their mbsyncrc without having to think about backslash escaping. > this assumption breaks latest when the password starts with a quote. i really prefer it when the set of quoting rules is minimal and consistently applied. > Another benefit is that this is the convention for generic configuration > syntax highlighting in many text editors, like the `conf` filetype in > vim, so the visual feedback will match the parser. > well, the vim syntax file also assumes single quotes to be parsed, so it's messed up either way. i think a good rule of thumb is "when you use weird characters, quote the whole string". that also works with the conf filetype. ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk _______________________________________________ isync-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/isync-devel
