Added basic support for vim-clap [1], a modern and performant generic finder and dispatcher for Vim and NeoVim.
[1]: https://github.com/liuchengxu/vim-clap
GH-178
Co-authored-by: Arctic Ice Studio <development@arcticicestudio.com>
Co-authored-by: Sven Greb <development@svengreb.de>
Basic highlighting support for TypeScript & TSX
Added basic support to highlight TypeScript & TSX syntax more
consistently through the HerringtonDarkholme/yats.vim plugin [1].
This includes improvements to highlight...
1. ...TypeScript interface an class names using `nord7` as foreground,
where interfaces also use the bold attribute, to match with
structs/classes.
2. ...global methods like e.g. `setTimeout` with `nord8` using the
italic attribute to mark it kind of static.
3. ...regular expressions with `nord13` as foreground color instead of
the normal color for quoted strings (`nord14`) to make it easier to
differ between both.
4. ...global objects like `Error`, `JSON` and `console` with `nord7`.
5. ...primitive/builtin types like `string` with `nord9`.
6. ...TypeScript type references with `nord7`.
7. ...TypeScript specific characters like for type annotations (`:`) and
member optionality (`?`) as operator with `nord9`.
This also includes improvements for "vanilla" JavaScript elements.
[1]: https://github.com/HerringtonDarkholme/yats.vim
Resolves GH-208
Co-authored-by: Arctic Ice Studio <development@arcticicestudio.com>
Co-authored-by: Sven Greb <development@svengreb.de>
The `LineNr` and `CursorLineNr` highlight groups now have a transparent
background in GUI mode.
Before it was set to `nord0_gui` which worked fine in most cases.
However, some plugins use these highlight groups to render their content
in a popup window which can potentially have a different background
color. This caused some issues e.g. for the fuzzy search plugin
LeaderF [1].
The compatibility with the `g:nord_cursor_line_number_background`
theme configuration has been verified to work as expected in both modes
when it is set to `0` or `1`.
This change is not related to the terminal mode or when using
`set notermguicolors` since `ctermbg` for `LineNr` and `CursorLineNr`
is set to `NONE` by default.
[1]: https://github.com/Yggdroot/LeaderF
Consistent `Error` and `MoreMsg` highligh. in term and GUI mode (#202)
Before the `Error` group in GUI mode used `nord0` as foreground color
instead of `nord4` resulting in a bad contrast.
Also after checking ( links to it)
Also since there was also no color defined for terminal mode for the
`MoreMsg` group (see `:help MoreMsg` that link to `:help more-prompt`)
Vim used the default color which was some kind of green.
To ensure it matches Nord's style it has now been changed to use `nord8`
(main accent color) for both terminal and GUI mode.
This can be tested by running `:echon "MESSAGE\n"` taht produces a lot
of lines that won't fit on the current screen space anymore.
Co-authored-by: Arctic Ice Studio <development@arcticicestudio.com>
Co-authored-by: Sven Greb <development@svengreb.de>
Added custom highlight groups of the `vim-startify` (1) plugin to adapt
to Nord's style.
References:
(1) https://github.com/mhinz/vim-startify
Resolves GH-159
The included theme bundles have not supported the "uniform status line" feature (GH-58), which allows to change the background color of the status bar (StatusLine) group to `nord3`.
Related to GH-58
Resolves GH-168
Implemented a nw theme configuration for the rendering of bold font
styles.
This commit adds the new `nord_bold` theme configuration to explicitly
toggle bold font rendering styles.
It is enabled by default when running for both in GUI and terminal mode.
The reason for this standard behavior is the fact that most terminals
and shells are capable to handle bold fonts.
GH-143
All documentations and assets have been moved to the official Nord
website and documentations (1,2).
References:
(1) nordtheme.com/ports/vim
(2) arcticicestudio/nord-docs
GH-158
Previously the `VertSplit` (1) (`:help VertSplit`) key used `nord1` as
background color by default making the line appear to be very lumpy.
This commit changes this style to use `nord0` as bavkground instead to
visually merge with the background so only the separator charaters are
a visual indiciator for the split line whih makes it look more
lightweight and unclutters the overall appeareance.
To allow user who liked the previous implementation to keep the style
this commit also adds a new `nord_bold_vertical_split_line` theme config
that can be assigned to `1` to achieve the legacy design.
The README also include information and hints how to change the
separator character by customizing Vim's `fillchars` (2)
(`:help fillchars`) variable.
References:
(1) http://vimdoc.sourceforge.net/htmldoc/syntax.html#hl-VertSplit
(2) http://vimdoc.sourceforge.net/htmldoc/options.html#'fillchars'
GH-132
Added support for Haskell syntax through the
neovimhaskell/haskell-vim (1) plugin.
This includes better coloring for types/classes using `nord7` instead of
highlighting them like keywords (`nord9`) and pre-processor and pragma
elements are now colorized correctly with `nord10`.
References:
(1) https://github.com/neovimhaskell/haskell-vim
GH-104
-> Please see https://github.com/arcticicestudio/nord/issues/94 for all
details about this design change decision.
Increased the comment color (`nord3`) brightness by 10% from a lightness
level of ~35% to ~45%.
This change also deprecates the comment contrast (1) configuration.
It is not necessary anymore for users to increase the brightness on
their own when the default color has been increased by default.
A deprecation warning will be shown to notify all users who have set a
custom value for the `g:nord_comment_brightness` configuration variable.
References:
(1) https://github.com/arcticicestudio/nord-vim#comment-contrast
GH-145
