grayout.vim is a vim plugin that grays out inactive C/C++/Obj-C preprocessor regions using libclang.
In addition to custom config files, it also supports compile_commands.json compilation databases, allowing quick and easy project setup.
Even though it is intended to be used with C/C++/Obj-C, it should work with all filetypes, as long as the -x <language> compile flag is set.
It was only tested on Linux but should theoretically work on other platforms, too.
This plugin was rewritten from scratch in c378ecb. If you have been using it before, please read the docs again, as many things changed in the new version.
There are some other plugins providing similar functionality, but in different ways.
-
ifdef highlighting adds static vim syntax rules for each manually defined macro. It does not make use of a compiler and requires the user to manually specify which macros are defined, thus being rather unflexible and often fails to properly detect skipped regions.
-
DyeVim integrates with (a custom fork of) YouCompleteMe to retrieve extended syntax information for semantic highlighting, including skipped preprocessor regions. However, it only works with YCM's libclang completer, not the newer and more advanced clangd completer.
-
vim-lsp-inactive-regions integrates with vim-lsp and uses the cquery or ccls language server to retrieve skipped preprocessor regions.
-
vim-lsp-cxx-highlight integrates with various LSP plugins and uses the cquery or ccls language server to provide full semantic highlighting, including skipped preprocessor regions.
-
coc.nvim + clangd provide semantic highlighting similar to the option above. Semantic highlighting support in coc.nvim needs to be enabled first, see
:h coc-semantic-highlights.
Therefore, if you are using LSP for completion or syntax checking, you should try coc.nvim with clangd or alternatively vim-lsp-cxx-highlight with ccls. Otherwise, this plugin is probably the best choice.
- Requirements
- Vim 8.1+ or Neovim
- Python 3
- Clang
- Install the plugin
- Using a plugin manager
- Alternatively, copy the contents of this repository to your vim directory
- Read the docs
- ...
- Profit
- Run
:GrayoutUpdateto parse the current file and apply highlighting. - Run
:GrayoutClearto clear all grayout highlights from current buffer - Run
:GrayoutClearCacheto clear the compile command cache, forcing to reload all config files when needed. - Run
:GrayoutShowCommandto print the current file's compile flags.
" Bind :GrayoutUpdate to F5
nnoremap <F5> :GrayoutUpdate<CR>
" Run GrayoutUpdate when opening and saving a buffer
autocmd BufReadPost,BufWritePost * if &ft == 'c' || &ft == 'cpp' || &ft == 'objc' | exec 'GrayoutUpdate' | endif
" Run GrayoutUpdate when cursor stands still. This can cause lag in more complex files.
autocmd CursorHold,CursorHoldI * if &ft == 'c' || &ft == 'cpp' || &ft == 'objc' | exec 'GrayoutUpdate' | endif" Set default compile flags.
" These are used, when no `compile_commands.json` or `.grayout.conf` file was found.
let g:grayout_default_args = [ '-x', 'c++', '-std=c++11' ]
" Set libclang searchpath. This should point to the directory containing `libclang.so`.
" Leave empty to auto-detect.
let g:grayout_libclang_path = ''
" Enable to print debug messages inside vim.
let g:grayout_debug = 0
" Enable to write debug messages to `grayout.log`.
let g:grayout_debug_logfile = 0As with every compiler, clang needs to know your project's compile flags to compile your code.
There are three ways of defining compile flags, that are prioritized in the respective order.
Note: If you make any changes related to compile flags at runtime, you will need to run :GrayoutClearCache in order to reload those configs.
-
Compilation Database (recommended)
Instruct your build system to generate a
compile_commands.jsonand symlink or move it to your project root.A compilation database contains information on how to compile each translation unit. It can be auto-generated by build systems like cmake, or tools like Bear or compdb.
For example, using cmake, add this line to your
CMakeLists.txt:set(CMAKE_EXPORT_COMPILE_COMMANDS ON)
-
.grayout.confCreate a
.grayout.conffile in your project root containing the compile flags. Linebreaks are ignored.
It is recommended to specify-x <language>in order to avoid ambiguity, especially with header files.Example:
-x c -DENABLE_FEATURE_X -DANOTHER_FLAG -DSOME_CONSTANT=42 -
g:grayout_default_argsThe global
g:grayout_default_argsvariable holds a list of compile flags and is used when no other configs were found. It is recommended to specify-x <language>in order to avoid ambiguity, especially with header files.Example:
let g:grayout_default_args = [ '-x', 'c++', '-std=c++11', '-DFOOBAR_MACRO' ]
If you don't like the default colors for grayouts, you can change them by altering the PreprocessorGrayout style.
By default it links to the Comment style.
Example:
highlight PreprocessorGrayout cterm=italic ctermfg=DarkGray gui=italic guifg=#6c6c6cIf you encounter any bugs or problems, please make sure to read the docs. If the problem persists, open a new issue on Github. Remember to add let g:grayout_debug_logfile = 1 to your vimrc and attach the grayout.log logfile to your issue.
Pull requests are welcome.
- Support
textpropsornvim_buf_add_highlight - Fix edge case where consecutive active if/elif/else lines are grayed out when their contents are inactive
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent