Related: #192, #210, #248
Also #247 is about `NonText`, which needs investigating.
Issues: `:digraphs`, special keys in `:map` output, and certain parts of
`'listchars'` are "subtle" and hard to read (esp. w/ `cursorline` over
them). Also, vim uses `SpecialKey` for them (instead of `Whitespace` for
`'listchars'` and `SpecialKey` elsewhere, like NeoVim).
Fix: make `SpecialKey` more like special keys (the highlight in vimscript
for, e.g., `map <Space> :echo "hello"<CR>`). This has the side effect of
making digraphs more visible. It also makes certain `'listchars'` pink,
which may be annoying. But there is no way currently to separate the two
in vim.
Rationale: It matches with the special keys in maps. The fact that vim
uses it elsewhere may simply be "wrong" and need changed.
If you don't like it: well, as usual, you can use an autocommand to use
whatever colors you want (`:help dracula-customization`).
Adds LspReference groups so that the reference highlighting feature
works for neovim built-in LSP.
Co-authored-by: Mathew Robinson <mathew@chasinglogic.io>
This adds specific highlight groups for GitGutter-related things.
It piggybacks off of the `Diff*` highlight groups.
The `gitsigns.nvim` maintainer [suggested](https://github.com/lewis6991/gitsigns.nvim/issues/94) that this be
implemented by checking if neovim is >= version 0.5, and if the package is
available (as opposed to a variable like `g:loaded_gitsigns`). This is because
`gitsigns` is essentially lazy-loaded so checking the variable when Dracula loads might be too early.
See these other related links in from [gitsigns](https://github.com/lewis6991/gitsigns.nvim):
https://github.com/lewis6991/gitsigns.nvim/issues/54317750d66a
* Add hightlight groups for nvim-treesitter
The majority of this configuration was taken from
https://github.com/ChristianChiarulli/nvcode-color-schemes.vim/pull/14
by [@nitishvelu](https://github.com/nitishvelu). I made a few minor
tweaks based on a ruby project to make sure most of the original tokens
were colored similarly.
* tree-sitter highlights conform to dracula spec
* Use builtin highlight groups
Co-authored-by: Derek Sifford <dereksifford@gmail.com>
* Apply suggestions from code review
Co-authored-by: Derek Sifford <dereksifford@gmail.com>
Co-authored-by: Derek Sifford <dereksifford@gmail.com>
The variable `g:dracula_undercurl` is not properly defined
when underline attribute is disabled by user configuration:
let g:dracula_underline = 0
The fix always defines missing `g:dracula_undercurl`,
but also disables it when underline is disabled.
* Initial work supporting maxmellon/vim-jsx-pretty
* adding purple for variable declarations
* feat: vim-jsx-pretty syntax support javascript/javascriptreact
* feat: allow typescript.tsx in typescript.vim
* feat: support vim-jsx-pretty in .tsx/typescriptreact
* fix: remove changes outside scope
* fix: return yats to original
* feat: update vim-jsx-pretty support to match expected colors
Co-authored-by: Guillermo Velasquez <guillermo.velasquez@gmail.com>
* Remove duplicated instructions
* Move Vim's 8 instructions to the top and add more detailed steps
* Update INSTALL.md (from review)
* update install instructions for plugin managers
And reformat some markdown
Co-authored-by: D. Ben Knoble <ben.knoble@gmail.com>
Co-authored-by: D. Ben Knoble <ben.knoble+github@gmail.com>
* fix: move back to "typescriptreact" from "typescript.tsx" filetype
This change is in accordance to the now official filetype defined by vim itself.
See: 92852cee3f
* add typescriptreact to should_abort call in typescript ftplugin
