+ ProjectRepository Link:|TagHL-ProjectRepository|
+ Store tags and types highlighters in central repository.
+ UseProjectRepository Link:|TagHL-UseProjectRepository|
+ Enable storing of tags and types files in central repository.
+ ProjectRepository *TagHL-ProjectRepository*
+ If the option |TagHL-UseProjectRepository| is set to True or 1 and
+ this option is set to a directory in your file system, then all code
+ that is part of one of the projects documented in the |TagHL-Projects|
+ option will use a separate repository for storing tags, types
+ highlighter files, |taghl_config.txt| files and cscope databases (as
+ applicable). This offers the possibility of keeping your project
+ folder empty of these files. As an example, consider this
+ In this case, when you run |:UpdateTypesFile|, the tags and
+ types highlighter files for DevProj1 will be stored in (and read from)
+ /home/al/.taghl/DevProj1/. The tags, types highlighter files and
+ cscope database will be store in /home/al/.taghl/DevProj2/.
+ Default: None (no project repository)
The python part of |TagHighlight| can be run in a number of ways,
depending on your system configuration. For most users, this should
+ UseProjectRepository |TagHL-UseProjectRepository|
+ This option enables the use of the projects repository. For
+ information on this, please see |TagHL-ProjectRepository|.
If you have some libraries that are used by your code, but which are
not kept with your code, it is possible to highlight keywords used in
Brodsky for producing the scripts that generate these libraries).
* Added SetWorkingDir option to allow control of the working directory for
a buffer with tags highlighted.
+ * Added the ability to store types and tags etc in a central repository
+ rather than with the code itself (thanks to Alexey Radkov for the
+ suggestion and for TagManager plugin that shows how it's done!)