Aleksandr Platonov

Seems that we should not call `cppBeginStatement()` here https://github.com/universal-ctags/ctags/blob/master/parsers/cxx/cxx_parser_block.c#L262 : - the fact that we are inside some code block (function, struct, namespace, extern "C", etc.) is not a good...

I think that cmake can be added in addition to existing build systems as experimental feature with future improvements (i.e. we should not replace existing build systems for now). And...

> Our project can build with CMake, it is supported by me, following code show you how to use it: CMake was desined to avoid using compilcated parametrised shell scripts...

> * have a **persistent** preamble cache on disk, rather than considering these files private to the session. This trades latency for disk pretty predictably. Seems preamble on disk is...

I also have found that problem some time ago and could share some thoughts about it. - llvm::sys::fs::real_path() is expensive file system operation. So, after your changes, compile_commands.json file loading...

It looks like `--path-mappings` option might help in your case. ``` --path-mappings=\workspace_root\libs\module=\module ```

> Thank you for bringing this up, but I'm afraid the --path-mappings does not help in this regard, I also swapped the sides desperately :) I successfully tried the following...