<feed xmlns='http://www.w3.org/2005/Atom'>
<title>nord-vim.git, branch develop</title>
<subtitle>forked from https://github.com/arcticicestudio/nord-vim</subtitle>
<id>https://git.tsegers.com/nord-vim.git/atom?h=develop</id>
<link rel='self' href='https://git.tsegers.com/nord-vim.git/atom?h=develop'/>
<link rel='alternate' type='text/html' href='https://git.tsegers.com/nord-vim.git/'/>
<updated>2022-02-14T19:13:25Z</updated>
<entry>
<title>Add support for indent-blankline.nvim</title>
<updated>2022-02-14T19:13:25Z</updated>
<author>
<name>Tim Segers</name>
<email>tsegers@pm.me</email>
</author>
<published>2022-02-14T19:13:25Z</published>
<link rel='alternate' type='text/html' href='https://git.tsegers.com/nord-vim.git/commit/?id=bcc46d3866fdd36c509d80112375e7cbf785e372'/>
<id>urn:sha1:bcc46d3866fdd36c509d80112375e7cbf785e372</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Improve readability of C language constants (#283)</title>
<updated>2022-01-25T21:50:44Z</updated>
<author>
<name>Julien Voisin</name>
<email>jvoisin@users.noreply.github.com</email>
</author>
<published>2022-01-25T21:50:44Z</published>
<link rel='alternate' type='text/html' href='https://git.tsegers.com/nord-vim.git/commit/?id=b32592eb0842005d1d25de96e3964ccacd537039'/>
<id>urn:sha1:b32592eb0842005d1d25de96e3964ccacd537039</id>
<content type='text'>
Improve readability of C language constants

To improve the readability of C language constants, defined by the
`cConstant` syntax highlighting group [1], these are now colored with
`nord9` for the foreground to make them stand out. This is important in
C, since interesting things are usually happening in their proximity,
like checking/returning an error, passing particular values/flags to
functions and so on.

[1]: https://github.com/vim/vim/blob/0e6adf8a29d5c2c96c42cc7157f71bf22c2ad471/runtime/syntax/c.vim#L313-L375



Co-authored-by: Arctic Ice Studio &lt;development@arcticicestudio.com&gt;
Co-authored-by: Sven Greb &lt;development@svengreb.de&gt;

GH-283</content>
</entry>
<entry>
<title>Add support for LSP textDocument/documentHighlight (#284)</title>
<updated>2022-01-12T22:00:15Z</updated>
<author>
<name>Charles Moscofian</name>
<email>charles.moscofian@mercadolivre.com</email>
</author>
<published>2022-01-12T22:00:15Z</published>
<link rel='alternate' type='text/html' href='https://git.tsegers.com/nord-vim.git/commit/?id=3e4e273d79e512fdcc84b00cd176026c1bf149af'/>
<id>urn:sha1:3e4e273d79e512fdcc84b00cd176026c1bf149af</id>
<content type='text'>
Support for Neovim LSP `documentHighlight` groups

The Neovim LSP `textDocument` / `documentHightlight` groups [1] are
responsible to highlight tokens in a document that are related to each
other, e.g. decalred variables, using the
`vim.buf.lsp.document_highlight()` function.
Also see the LSP specification about "Document Highlights Request" [2]
for more details.

[1]: https://github.com/neovim/neovim/blob/f92a2457c2e7ad14d9a5a907ef4213fa770b6d95/runtime/doc/lsp.txt#L423
[2]: https://microsoft.github.io/language-server-protocol/specification#textDocument_documentHighlight


Co-authored-by: Arctic Ice Studio &lt;development@arcticicestudio.com&gt;
Co-authored-by: Sven Greb &lt;development@svengreb.de&gt;</content>
</entry>
<entry>
<title>Add support for neovim 0.6.0 diagnostic API highlight groups (#282)</title>
<updated>2022-01-01T20:28:50Z</updated>
<author>
<name>Jan Steinke</name>
<email>jan.steinke@gmail.com</email>
</author>
<published>2022-01-01T20:28:50Z</published>
<link rel='alternate' type='text/html' href='https://git.tsegers.com/nord-vim.git/commit/?id=8035ba071b3302c1affcfead48af8a1ced9a41e1'/>
<id>urn:sha1:8035ba071b3302c1affcfead48af8a1ced9a41e1</id>
<content type='text'>
In Neovim `0.6.0` [1] the naming scheme for the highlight groups of the
diagnostic API changed [2]. The new groups have been added as default while
the previous groups are conditionally guarded when using Neovim `0.5.0`.

[1]: https://github.com/neovim/neovim/releases/tag/v0.6.0
[2]: https://github.com/neovim/neovim/pull/15585/commits/a5bbb932f9094098bd656d3f6be3c58344576709#diff-51fab2b766d0a3b606462e95de492190df173b7296147912307cdad636cd492aR77


Co-authored-by: Arctic Ice Studio &lt;development@arcticicestudio.com&gt;
Co-authored-by: Sven Greb &lt;development@svengreb.de&gt;

GH-282</content>
</entry>
<entry>
<title>Merge branch 'release/0.18.0' into develop</title>
<updated>2021-09-12T21:08:31Z</updated>
<author>
<name>Arctic Ice Studio</name>
<email>development@arcticicestudio.com</email>
</author>
<published>2021-09-12T21:08:31Z</published>
<link rel='alternate' type='text/html' href='https://git.tsegers.com/nord-vim.git/commit/?id=df497a7b396d32a721fa72bd9119db2bca3deed6'/>
<id>urn:sha1:df497a7b396d32a721fa72bd9119db2bca3deed6</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Release version 0.18.0</title>
<updated>2021-09-12T21:07:55Z</updated>
<author>
<name>Arctic Ice Studio</name>
<email>development@arcticicestudio.com</email>
</author>
<published>2021-09-12T21:07:55Z</published>
<link rel='alternate' type='text/html' href='https://git.tsegers.com/nord-vim.git/commit/?id=b64dc119b0bfea35c69359f5ff5e0c9026a0890a'/>
<id>urn:sha1:b64dc119b0bfea35c69359f5ff5e0c9026a0890a</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Remove `TSError` syntax highlighting group (#270)</title>
<updated>2021-09-12T20:14:42Z</updated>
<author>
<name>George Tom</name>
<email>georg3tom@gmail.com</email>
</author>
<published>2021-09-12T20:14:42Z</published>
<link rel='alternate' type='text/html' href='https://git.tsegers.com/nord-vim.git/commit/?id=e3e8a75cd38d83b98e9cf2cf83af91d8df76bca7'/>
<id>urn:sha1:e3e8a75cd38d83b98e9cf2cf83af91d8df76bca7</id>
<content type='text'>
The `TSError` group is used to highlight syntax/parser errors [1] which
caused an aggressive styling where the background color of many syntax
elements was rendered with `nord11` during typing. This was caused due
to the fast processing of `tree-sitter` which also resulted in highlight
flickering.
This is a known problem and was fixed by many other themes (e.g. Dracula
[2]) by removing the group again. One of the core maintainers of
`nvim-treesitter` provided a solution by remapping groups [3] and also
mentioned that the group is styled by the `nvim-treesitter` plugin but
the active theme [4].

Syntax errors can still be highlighted through linters and parsers like
Neovim's LSP [5] can still be used instead to highlight errors with the
correct style (e.g. only change the foreground color of a single word).

[1]: https://github.com/nvim-treesitter/nvim-treesitter/blob/fb5d6e04/doc/nvim-treesitter.txt#L493-L495
[2]: https://github.com/dracula/vim/pull/232
[3]: https://github.com/nvim-treesitter/nvim-treesitter/issues/78#issuecomment-647140700
[4]: https://github.com/nvim-treesitter/nvim-treesitter/issues/1016#issuecomment-797049591
[5]: https://github.com/neovim/nvim-lspconfig

Fixes GH-269</content>
</entry>
<entry>
<title>add support for Lsp codelens (#266)</title>
<updated>2021-09-05T19:10:16Z</updated>
<author>
<name>Jan Steinke</name>
<email>jan.steinke@gmail.com</email>
</author>
<published>2021-09-05T19:10:16Z</published>
<link rel='alternate' type='text/html' href='https://git.tsegers.com/nord-vim.git/commit/?id=02ddfadb9e200221f141bcd99ea055e533d67ec0'/>
<id>urn:sha1:02ddfadb9e200221f141bcd99ea055e533d67ec0</id>
<content type='text'>
Support for LSP code lenses

Before LSP code lenses [1] where code lenses were highlighted with the
default color which has been changed to make it less visually intrusive,
like other UI related elements, i.e. messages of linters.

[1]: https://neovim.io/doc/user/lsp.html#lsp-highlight-codelens

GH-266


Co-authored-by: Arctic Ice Studio &lt;development@arcticicestudio.com&gt;</content>
</entry>
<entry>
<title>Add support for pandoc (#220)</title>
<updated>2021-07-11T08:21:00Z</updated>
<author>
<name>Timothée Poisot</name>
<email>timothee.poisot@umontreal.ca</email>
</author>
<published>2021-07-11T08:21:00Z</published>
<link rel='alternate' type='text/html' href='https://git.tsegers.com/nord-vim.git/commit/?id=8d8b9bf86bbc715a055b54cb53f0643fd664caa4'/>
<id>urn:sha1:8d8b9bf86bbc715a055b54cb53f0643fd664caa4</id>
<content type='text'>
Add support for `vim-pandoc/vim-pandoc-syntax`

To improve syntax highlighting for Pandoc [1], support for the
vim-pandoc/vim-pandoc-syntax [2] plugin has been implemented.
Most groups are linked to existing Markdown groups to ensure a
consistent style across languages and different plugins.

Configurations used for testing:

```vim
let g:pandoc#syntax#conceal#cchar_overrides = {"atx": "〉"}
let g:nord_italic = 1
```

Resources:

- `g:pandoc#syntax#conceal#cchar_overrides` docs [3]
- `s:cchars` definition [4]
- Markdown "Extended Syntax" Guide [5]

[1]: https://pandoc.org
[2]: https://github.com/vim-pandoc/vim-pandoc-syntax
[3]: https://github.com/vim-pandoc/vim-pandoc-syntax/blob/68d7249/doc/pandoc-syntax.txt#L45-L50
[4]: https://github.com/vim-pandoc/vim-pandoc-syntax/blob/5056e63/syntax/pandoc.vim#L37-L72
[5]: https://www.markdownguide.org/extended-syntax

Co-authored-by: Arctic Ice Studio &lt;development@arcticicestudio.com&gt;
Co-authored-by: Sven Greb &lt;development@svengreb.de&gt;

Closes GH-220
</content>
</entry>
<entry>
<title>Merge branch 'release/0.17.0' into develop</title>
<updated>2021-07-10T12:38:58Z</updated>
<author>
<name>Arctic Ice Studio</name>
<email>development@arcticicestudio.com</email>
</author>
<published>2021-07-10T12:38:58Z</published>
<link rel='alternate' type='text/html' href='https://git.tsegers.com/nord-vim.git/commit/?id=851322a9cec998ed81c25b653bf9c48c365ec316'/>
<id>urn:sha1:851322a9cec998ed81c25b653bf9c48c365ec316</id>
<content type='text'>
</content>
</entry>
</feed>
