An arctic, north-bluish clean and elegant Vim theme.

An arctic, north-bluish clean and elegant Vim color theme.

Information

Category: Linux / Shell Applications
Watchers: 28
Star: 2.5k
Fork: 278
Last update: Nov 29, 2023

Resource links

https://github.com/nordtheme/vim

An arctic, north-bluish clean and elegant Vim color theme.

Designed for a fluent and clear workflow based on the Nord color palette.

Build for Vim's terminal- and GUI mode with true colors with support for many third-party syntax and UI plugins including bundled themes for lightline.vim and vim-airline.

Getting Started

Visit the official website to learn all about the syntax highlighting features, details and elements of UI and editor elements, the various theme configurations and the support for many plugins.

Learn about the installation and activation, how to configure and customize the theme from the official documentations.

Quick Start

Thanks to existing plugin/runtimepath managers for Vim, Nord Vim can be installed for all platforms and the various variants/forks of Vim in a uniform way within a few lines of codes. The recommended manager is vim-plug, but any other manager like pathogen or Vundle can also be used.

To automatically download and activate Nord Vim, follow the install instructions for vim-plug and

add Plug 'arcticicestudio/nord-vim' to your vimrc within vim-plug's plugin loading function
run the :PlugInstall command in Vim
activate the theme by adding colorscheme nord to the vimrc or change it on-the-fly by running :colorscheme nord

See the Nord Vim's documentation for more installation options and how to set it up manually.

Features

A unified UI and editor syntax element design provides a clutter-free and fluidly merging appearance.

Small details with unobtrusive styles for popular and common code editor features like search result marker and brace matching — designed to get out of your way with a visually attractive appearance.

Support for a wide range of programming languages — from bundled plugins up to many popular syntax and UI third-party plugins.

Contributing

Nord is an open source project and we love to receive contributions from the community!

There are many ways to contribute, from writing- and improving documentation and tutorials, reporting bugs, submitting enhancement suggestions that can be added to Nord by submitting pull requests.

Please take a moment to read Nord's full contributing guide to learn about the development process, the project's used styleguides, branch organization and versioning model.

The guide also includes information about minimal, complete, and verifiable examples and other ways to contribute to the project like improving existing issues and giving feedback on issues and pull requests.

41 Open More issues

Closed

Add support for nvim-treesitter/nvim-treesitter

Resolves #235

It adds support for TreeSitter syntax highlighting.

type-feature context-syntax context-plugin target-neovim scope-compatibility scope-ux

opened Mar 15, 2021 by mrswats 30

Closed

Treesitter support

I like this theme but It would be even better with Treesitter support.

Treesitter defines the following highlight groups (the color definitions are from Onedark).

hi! TSError ctermfg=203 guifg=#f44747 hi! TSPunctDelimiter ctermfg=249 guifg=#abb2bf hi! TSPunctBracket ctermfg=249 guifg=#abb2bf hi! TSPunctSpecial ctermfg=249 guifg=#abb2bf hi! TSConstant ctermfg=75 guifg=#61afef hi! TSConstBuiltin ctermfg=173 guifg=#d19a66 hi! TSConstMacro ctermfg=73 guifg=#56b6c2 hi! TSStringRegex ctermfg=114 guifg=#98c379 hi! TSString ctermfg=114 guifg=#98c379 hi! TSStringEscape ctermfg=73 guifg=#56b6c2 hi! TSCharacter ctermfg=114 guifg=#98c379 hi! TSNumber ctermfg=173 guifg=#d19a66 hi! TSBoolean ctermfg=173 guifg=#d19a66 hi! TSFloat ctermfg=114 guifg=#98c379 hi! TSAnnotation ctermfg=180 guifg=#e5c07b hi! TSAttribute ctermfg=73 guifg=#56b6c2 hi! TSNamespace ctermfg=201 guifg=#ff00ff hi! TSFuncBuiltin ctermfg=75 guifg=#61afef hi! TSFunction ctermfg=75 guifg=#61afef hi! TSFuncMacro ctermfg=180 guifg=#e5c07b hi! TSParameter ctermfg=73 guifg=#56b6c2 hi! TSParameterReference ctermfg=73 guifg=#56b6c2 hi! TSMethod ctermfg=75 guifg=#61afef hi! TSField ctermfg=168 guifg=#e06c75 hi! TSProperty ctermfg=180 guifg=#e5c07b hi! TSConstructor ctermfg=73 guifg=#56b6c2 hi! TSConditional ctermfg=175 guifg=#c586c0 hi! TSRepeat ctermfg=175 guifg=#c586c0 hi! TSLabel ctermfg=75 guifg=#61afef hi! TSKeyword ctermfg=175 guifg=#c586c0 hi! TSKeywordFunction ctermfg=175 guifg=#c586c0 hi! TSKeywordOperator ctermfg=175 guifg=#c586c0 hi! TSOperator ctermfg=249 guifg=#abb2bf hi! TSException ctermfg=175 guifg=#c586c0 hi! TSType ctermfg=75 guifg=#61afef hi! TSTypeBuiltin ctermfg=75 guifg=#61afef hi! TSStructure ctermfg=201 guifg=#ff00ff hi! TSInclude ctermfg=175 guifg=#c586c0 hi! TSVariable ctermfg=73 guifg=#56b6c2 hi! TSVariableBuiltin ctermfg=180 guifg=#e5c07b hi! TSText ctermfg=226 guifg=#ffff00 hi! TSStrong ctermfg=226 guifg=#ffff00 hi! TSEmphasis ctermfg=226 guifg=#ffff00 hi! TSUnderline ctermfg=226 guifg=#ffff00 hi! TSTitle ctermfg=226 guifg=#ffff00 hi! TSLiteral ctermfg=226 guifg=#ffff00 hi! TSURI ctermfg=226 guifg=#ffff00 hi! TSTag ctermfg=168 guifg=#e06c75 hi! TSTagDelimiter ctermfg=241 guifg=#5c6370

type-feature context-syntax context-plugin target-neovim scope-compatibility scope-ux

opened Dec 7, 2020 by sudoerwx 22

Closed

Carets in status line

Something weird happens on the fussy search with ctrl-p NORD:

OTHER:

As you can see, the first image shows ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

type-feature context-ui context-config

opened Jul 14, 2017 by deniciocode 16

Closed

Question: Ruby syntax coloring in terminal

For the Ruby language, are the symbols intentionally a white-ish color? If I prefer to have it stand out among other code, can I change it somehow?

type-improvement context-syntax

opened Mar 21, 2017 by hahuang65 16

Closed

Incorrect color contrast on vim with st

I'm using vim 8.1 (with +termguicolors) inside st under dwm. I applied the nord theme to st. I installed nord trough Plug as recommended.

But for some reason some colors are incorrect inside vim... For instance as you can see on the screenshots line numbers and comments color are to close to the background color.

More, there is no visual selection color at all. Everything else looks ok trough...

context-syntax resolution-user-side scope-compatibility type-support

opened Jun 25, 2019 by lucassardois 15

Closed

Pair "brackets" looks bad

In this screenshow cursor is on <div, but looks like it set on >

Can it be fixed?

context-ui resolution-user-side type-support scope-customization

opened Nov 17, 2017 by sivakov512 15

Open

Highligted words in visual mode are invisible in neovim

I am running WSL2 + windows terminal + nvim v0.9.1 and the following plugins.

opened Aug 28, 2023 by jonassvedas 3

Open

PreProc: Use nord10 for all preprocessor-like syntax highlighting

nord10 is the color to use according to the "Colors and Palettes" documentation. This change simplifies to only defining the syntax highlighting for PreProc, which (n)vim links the other related highlight groups by default (see :help group-name).

context-syntax scope-maintainability

opened Jun 15, 2023 by ericvw 1

Open

EditorConfig: Remove max_line_length for all files

Having max_line_length for all files overrides useful line lengths defined (n)vim's ftplugins (e.g., gitcommit.vim sets textwidth=72 for well-formed commit messages.

opened Jun 15, 2023 by ericvw 1

Open

text.diff not working with Nord Theme

I noticed I get no syntax highlighting when tree-sitter-diff is active.

It appears that these are not set https://github.com/nvim-treesitter/nvim-treesitter/issues/4097#issuecomment-1374556679

opened Jun 15, 2023 by dngray 1

Open

Inherit the background color on spelling error highlights

I have the cursorline option enabled, which highlights the line with the cursor. Lines with spelling errors render like this, because the background is set to a specific color (s:nord0_gui).

This PR simply removes the background color, so it's inherited.

context-syntax scope-ux scope-quality

opened Jun 2, 2023 by chaucerbao 1

Open

Different color between text mode and math mode in LaTeX

Currently, the text in math mode and text mode in LaTeX (with or without vimtex or treesitter) are the same color, which makes them hard to distinguish at a glance. I would appreciate it if they were made to have different colors so they can be easily told apart. This behavior is present in all other colorschemes I've seen, so it's odd that Nord doesn't have it.

context-syntax scope-quality

opened Apr 29, 2023 by MithicSpirit 2

v0.19.0(May 14, 2022)

⇅ Show all commits

Features

Syntax

Support for LSP textDocument/documentHighlight — #284 (⊶ 3e4e273d) by @cmoscofian

↠ The Neovim LSP textDocument / documentHightlight groups are responsible to highlight tokens in a document that are related to each other, e.g. declared variables, using the vim.buf.lsp.document_highlight() function. Also see the LSP specification about "Document Highlights Request" for more details.

UI

Support for LSP LSPSignatureActiveParameter — #286 (⊶ a8256787) by @cmoscofian

↠ The vim.lsp.buf.signature_help function is used to highlight the active parameter in the signature help. Before the active parameter was not styled differently to any other parameter which made it hard to distinguish it. This has been improved by adding support for the LspSignatureActiveParameter syntax highlighting group where the active parameter now uses nord8 are foreground color and additionally a font underline with the same color.

Before

After

Improvements

Refactored theme configuration conditions — #295, #305 (⊶ 291e05d9, e3eb2084) by @jvoisin and @svengreb

↠ The conditions and default values of the theme configurations were quite verbose so this commit improves them by…

…using inline ternary operators instead of if/else blocks to reduce the code overhead and make it way more readable.
…using Vim builtin get function instead of if/else blocks.
…inlining the script-scoped logWarning function since it was only used once.
…grouping some blocks where it made sense.

Only call execute function once per syntax group — #303 (⊶ 77fe4b3f) by @jvoisin and @svengreb

↠ Before the custom s:hi function called Vim's execute function for each defined attribute which is quite expensive in terms of performance. To improve this the attributes are now concatenate as string and passed to exec at the end of the function instead.

Syntax

Readability of C language constants — #283 (⊶ b32592eb) by @jvoisin

↠ To improve the readability of C language constants, defined by the cConstant syntax highlighting group, 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.

Before

After

Tasks

Support for Neovim 0.6.0 diagnostic API highlight groups — #282 (⊶ 8035ba07) by @jan-xyz

↠ In Neovim 0.6.0 the naming scheme for the highlight groups of the diagnostic API changed. The new groups have been added as default while the previous groups are conditionally guarded when using Neovim 0.5.0.

The full changelog is available in the repository

Source code(tar.gz)
Source code(zip)

v0.18.0(Sep 12, 2021)

Changelog for Nord Vim — An arctic, north-bluish clean and elegant Vim color theme.

0.18.0

⇅ Show all commits

Features

Syntax

Support for vim-pandoc/vim-pandoc-syntax — #220 (⊶ 8d8b9bf8) by @tpoisot and @BirgerNi

↠ To improve syntax highlighting for Pandoc, support for the vim-pandoc/vim-pandoc-syntax plugin has been implemented. Most groups are linked to existing Markdown groups to ensure a consistent style across languages and different plugins.

UI

Support for LSP code lenses — #266 (⊶ 02ddfadb) by @jan-xyz

↠ Before LSP code lenses were highlighted with the default color which has been changed to make it less visually intrusive, like other UI related elements, e.g. messages of linters.

Before

After

Improvements

Syntax

Prevent aggressive error highlighting — #269 ⇄ #270 (⊶ e3e8a75c) by @jan-xyz

↠ The TSError group is used to highlight syntax/parser errors which caused an aggressive styling where the background color of many syntax elements was rendered with nord11 during typing. This is a known problem and was fixed by many other themes by removing the group again. One of the core maintainers of nvim-treesitter provided a solution by remapping groups and also mentioned that the group is styled by the nvim-treesitter plugin but the active theme.

Syntax errors can still be highlighted through linters and parsers like Neovim's LSP can still be used instead to highlight errors with the correct style, e.g. only change the foreground color of a single word.

The full changelog is available in the repository

Source code(tar.gz)
Source code(zip)

v0.17.0(Jul 10, 2021)

Changelog for Nord Vim — An arctic, north-bluish clean and elegant Vim color theme.

0.17.0

⇅ Show all commits

Features

Syntax

Support for nvim-treesitter/nvim-treesitter — #235 ⇄ #253 (⊶ b3e712a9) by @s-u-d-o-e-r and @mrswats

↠ Neovim version 0.5 is a long-time awaited update that introduces features like support for tree-sitter via nvim-treesitter and LSP via nvim-lspconfig. Even though Neovim divides more and more from Vim through specific features like first-class Lua support with custom APIs, the highlighting for tree-sitter is achieved through “normal“ syntax highlighting groups. Most of the groups are already linked by the nvim-treesitter plugin by default so only a few groups have been adjusted for now to fit the Nord style.

⚠️ Note that this is the first iteration and it is very likely that there will be inconsistencies compared to the current highlighting when using “normal“ Vim plugins per language. Please report any problem you find so that the support for tree-sitter can be improved continuously!

The full changelog is available in the repository

Source code(tar.gz)
Source code(zip)

v0.16.0(Jun 9, 2021)

Changelog for Nord Vim — An arctic, north-bluish clean and elegant Vim color theme.

⇅ Show all commits

Features

API

Public API function NordPalette to get Nord colors — #224 (⊶ 5867535c) by @jandamm

↠ Implemented a new NordPalette pubic API function that returns all Nord colors as dictionary. This allows to use the colors in other Vim scripts without the need to copy & paste the colors from the documentations or the Nord Vim theme sources.

Syntax

Support for the php.vim plugin — #218, #262 ⇄ #263 (⊶ b3c46c87, 07452c71) by @pirey

↠ In arcticicestudio/nord-vim#218 new highlighting groups for the bundled PHP syntax were added to improve the highlighting of classes, function and methods and the overall syntax token detection, but they are actually defined by the php.vim plugin. Therefore the added highlighting calls have been moved to a plugin section. Additionally, the phpClassExtends and phpClassImplements groups have been added to improve the highlighting for classes that implement or extended interfaces/classes. The phpUseClass has also been added to improve the highlighting for imports.

To improve the highlighting with the bundled PHP syntax, the following options can be set:

let php_asp_tags = 1
let php_baselib = 1
let php_htmlInStrings = 1
let php_parent_error_close = 1
let php_parent_error_open = 1

Before

After

Conceal highlighting group support — #149, #207, #211, #256 ⇄ #261 (⊶ f3f28b93)

↠ The Conceal group is was not supported which could resulted in rendering problems for (Unicode) characters that require special encoding like the ones from the Greek alphabet and mathematical expressions that are often used in LaTeX or Pandoc documents. These characters were highlighted with the default background color which made them kind of unreadable with the theme foreground color. See :help conceal and :help concealcursor for more details about concealing in Vim.

To fix the problem, the Conceal group has been added with its background color set to NONE for GUI and terminal mode to either use the terminal default background color or let loaded scripts apply custom styles based on the current runtime context.

The problem has been reported in #149, #207 and #211 with LaTeX and Pandoc being used by the reporters. PR #220 adds support for vim-pandoc/vim-pandoc-syntax specific highlighting groups and can be merged after adding basic support for Conceal.

To get the correct rendering for such elements the following configurations must be set:

let g:pandoc#syntax#conceal#use = 1
set conceallevel=2

Before

After

Updated highlights for Neovim LSP diagnostics — #229, #248 (⊶ a3af928a) by @gbrlsnchs and @thallium

↠ To ensure compatibility with the latest versions of Neovim LSP the highlighting groups for diagnostics have been adapted to the changes of neovim/neovim#12655. See :help lsp-highlight-diagnostics for more details.

Note that LSP will be available as of Neovim 0.5 which is (at the time of this commit) still in development and only available as nightly build. Also see great articles from Nord Vim contributors like “Neovim (0.5) Is Overpowering“ for more information about Neovim 0.5 features, including LSP.

Thanks to @clason, @crispgm and @ojroques for the review support!

UI

Support for the vim-indent-guides plugin — #186 ⇄ #226 (⊶ ea7ff9c3) by @mitinarseny

↠ Added support for the vim-indent-guides plugin. The even and odd highlighting blocks using nord1 and nord2 (nord3in terminal mode) to provide a subtle and non-disturbing style. Note that the custom theme colors are only applied when the indent_guides_auto_colors variable has been set to 0:

let g:indent_guides_auto_colors = 0

Before

After

Improvements

UI

coc.vim error and warning highlighting — #213 (⊶ 8a9754ce) by @butterywombat

↠ Added the coc.nvim highlighting groups for errors and warnings using their respective foreground colors and the undercurl font style.

Bug Fixes

UI

Typo in group Pmenu group names — #252 (⊶ e5a54c7f) by @kunzaatko

↠ Fixed two typos in Pmenu group names:

PMenuSel -> PmenuSel
PMenu -> Pmenu

This mismatch was never really noticed because most of the time users rely on plugins like coc.vim or vim-clap which come with custom highlighting groups and UI libraries.

The full changelog is available in the repository

Source code(tar.gz)
Source code(zip)

v0.15.0(Jul 6, 2020)

Changelog for Nord Vim — An arctic, north-bluish clean and elegant Vim color theme.

Features

Syntax

Extended support for TypeScript and TSX — #208 (⊶ 1bd44ade) by @iamdidev ↠ Added extended support for TypeScript and TSX through the yats.vim plugin. This provides, among many other good changes, better highlighting for syntax elements like decorators, more granular separation of different language elements within a single code line as well as highlighting for…

…interfaces with bold font style, typing characters and types.

…global methods like setTimeout with italic font style.

…regular expressions with nord13 instead of the normal color for quoted strings.

…global elements like Error, JSON and console.

…brackets of types as structural elements.

…TSX/JSX and HTML with a consistent appearance.

UI

Support for vim-clap — #178 (⊶ 7a52f66c) by @meck and @ikalnytskyi ↠ Added basic support for vim-clap, a modern and performant generic finder and dispatcher for Vim and NeoVim.

The full changelog is available here

Source code(tar.gz)
Source code(zip)

v0.14.0(Jun 16, 2020)

Changelog for Nord Vim — An arctic, north-bluish clean and elegant Vim color theme.

Features

UI

Basic support for nvim-lsp (Language Server Protocol) — #198 (⊶ 0ccf70b6) by @alexanderjeurissen ↠ Added basic support for nvim-lsp, a collection of common configurations for the NVim language server protocol client.

Improvements

UI

Consistent error highlighting between GUI and terminal mode — #202 (⊶ 974a9190) by @xulongwu4 ↠ The highlighting of errors in GUI and true color terminal mode now also uses nord4 as foreground color of instead of nord0.

Before

After

Improved highlighting for “More“ separator — #202 (⊶ 974a9190) by @xulongwu4 ↠ The highlighting of the More separator is now highlighted with the nord8 accent color.

Before

After

Transparent line number and cursor line background by default — #204 (⊶ 6323f662) by @xulongwu4 ↠ Before the background color of the LineNr and CursorLineNr highlighting groups were set to nord0 which was fine in most cases, but conflicted with plugins like Yggdroot/LeaderF that renders line numbers in a popup windows with a different background color.

Before