On Thu, May 11, 2017 at 11:17 AM, R0b0t1 <[email protected]> wrote: > On Thu, May 11, 2017 at 6:52 AM, Bram Moolenaar <[email protected]> wrote: >> >> Yasuhiro Matsumoto wrote: >> >>> include directive allow to use MACRO. >>> >>> #include <ft2build.h> >>> #include FT_FREETYPE_H >>> >>> This is patch to fix this problem. >>> >>> https://patch-diff.githubusercontent.com/raw/vim-jp/vim-cpp/pull/44.diff >> >> Hmm, is this really useful? We normally highlight valid syntax and >> known errors. This is something in between, we don't know if it is >> valid. Perhaps laeavin it unhighlighted is better. >> > > Admittedly FreeType is doing something a bit strange, but it's valid > C. Most highlighting engines color the include statement the same way > - if a quoted portion follows that it will be highlighted differently. > E.g. in KDevelop the line in question is entirely green. > > This message seems to be in response to > https://github.com/vim-jp/vim-cpp/issues/43, so thank you mattn!
Mattn, I will file another report but I would like it to be recorded in the mailing list as well. In some C/C++ sources it is customary to indent lines containing directives like so: ```C++ #ifdef POSIX # ifdef LINUX # endif #endif ``` Currently Vim's highlighters do not handle this syntax. Thank you for your help, I am still new to the highlighting engine. https://github.com/vim-jp/vim-cpp/issues/49 -- -- 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 --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
