On Tue, Jun 15, 2010 at 8:20 AM, Valery Kondakoff <[email protected]> wrote: > On Tue, Jun 15, 2010 at 4:01 PM, Andy Wokula <[email protected]> wrote: >> Am 15.06.2010 13:53, schrieb Valery Kondakoff: >>>> I'm receiving an error E357 'Matching character missing for a' if I >>>> execute ':set langmap=a\,' form command line. >>> Seems to work well like this: :set langmap=a\\,'. Is this a bug? >> >> No. >> :h option-backslash > > I understand, that if I want to enter a backslash in settings it > should be escaped by another backslash. But currently I'm using > backslash to escape the comma. Why should I enter two backslashes?
Right, and in order for that backslash to be part of the option string so that parsing of the option will see the backslash, you need to escape it. It's not a matter of escaping the comma on the command-line (since that doesn't matter). It's a matter of having a backslash in the resulting string that's used for the option so that the option itself has a backslash before the comma. That is, if you simply do ":set langmap=a\," then after the command-line is parsed you get ":set langmap=a,". The comma isn't escaped. When you do ":set langmap=a\\,", then the backslash still exists after the command-line is parsed and then when the option parsing takes place it will see ":set langmap=a\," and you have an escaped comma. -- James GPG Key: 1024D/61326D40 2003-09-02 James Vega <[email protected]> -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
