This plugin provides IDE-like semantic highlighting for various languages in Neovim.
Currently, C, C++, and Go are supported, and more languages will be added as time permits. Highlighting for other languages is approximated using ctags. This plugin doubles as an automatic tag manager.
Originally, I wrote this to be a simple tag highlighting plugin for Neovim, much like Neotags (https://github.com/c0r73x/neotags.nvim) implemented entirely in C, for no particular reason. Working with Neovim proved so simple and fast that it seemed natural to expand this project to implement true semantic highlighting.
I have (finally) cleaned up my color scheme file enough to include it with plugin. Because the plugin is useless without a custom color scheme, and I haven't bothered to document anything, I've made the foolish decision to enable my color scheme by default with the plugin. This is mainly just to demonstrate it working. This can be disabled by placing this in your init.vim file before the plugin is loaded:
let g:tag_highlight#use_bundled_colors = 0
I have no idea if anyone is actually using this thing. If you are, or you've tried to and something has gone horribly wrong I'd be grateful for any feedback. Heck, it'd make my day even if all you were to say is that you hate my software and/or me. And I'm not even kidding. Please do complain if it doesn't work.
If using dein, installing should be as easy as adding this to your .vimrc.
call dein#add('roflcopter4/tag-highlight.nvim', {'merged': v:false, 'build': 'sh build.sh'})
The little shell script should build the binary and set everything up.
Disclaimer: 'should be'. Odds are it will fail and you'll have to run the script yourself. If that also fails, you'll have to build the cmake project yourself too. This isn't very likely to happen unless you're missing libraries. LLVM with libclang is required, and go must installed to build the go support. The C compiler must be either gcc or clang. Microsoft Visual C++, with it's non-compliant c-preprocessor, will have a stroke if it tries to build this. Therefore MinGW is required on Windows.
Project root directories can and should be marked via the command :THLAddProject <DIR>. They can be deleted again with :THLRemoveProject <DIR>. Doing this makes it much easier to find the whole project, especially the 'compile_commands.json'.
Formerly, Go projects had to be installed for the highlighting to work. Since it's move to using modules for everything this is no longer true, but comes with the downside of now having to parse the source code of every imported package instead of reading a pre-compiled archive. Nothing I can do about this. Sorry.
Different languages are tracked separately. Adding a directory a project for 'C' won't count for, say, Python. As a special case 'C' and 'C++' are considered equivalent for this purpose.
You'll also want to fiddle with the highlight linking to fit your favorite color scheme. The default colors were chosen almost completely at random and I've never even looked at them. For this plugin to make any sense you're going to need more colors than most schemes offer by default. Check my included scheme as an example if you wish.
In lieu of having actually received any questions to form an FAQ, I figured I might as well pre-emptively answer a few I would ask.
Because.
Because reasons.
When I started this, language servers didn't offer any semantic information that I'd need to make this. Maybe they do now? Don't know, haven't checked; don't care.
No promises. It won't break anything though. If it crashes you can restart it with the command :THLInit. If it hangs, try killing it first with :THLStop.
Yeah, probably.