shaunsingh / nord.nvim

Neovim theme based off of the Nord Color Palette, written in lua with tree sitter support

• My coding projects are available on GitHub

Contacts:

• email: [email protected]
• discord: hi_im_bored

nord.nvim's Issues

ColorColumn foreground color

First of all, thank you for this theme.

I was wondering why the foreground color of ColorColumn is set to nord.nord0_gui instead of nord.none? In my opinion it would make more sense to leave the text color as it is. The following image shows a file using markdown syntax with the current foreground color.

Cursorline not visible

Hi,

Firstly, thanks so much for creating this plugin - I've been using Nord for a long time, but the lack of support for treesitter meant I had to move elsewhere, so great to be able to move back :)

Just a question, not necessarily a bug. At the moment, cursorline is currently set to nord.none, so isn't visible. On the original vim plugin, it's set to nord1_gui (https://github.com/arcticicestudio/nord-vim/blob/5867535cea7bb6b4c219fa0726c93e4b055debd2/colors/nord.vim#L170)

However, on the original plugin, colorcolumn & cursorline conflicted as they were both using nord1_gui. As you're using nord.active for colorcolumn, this means that we could use nord.nord1_gui and support both features.

Was it an intentional decision to have cursorline invisible, or would it be possible to have it changed to nord1_gui?

Thanks!

colors are off on MacOS and Alacritty

Hi,
Any idea why some of the colors are completely off on my installation?

OS: MacOS BigSur
alacritty --version
alacritty 0.9.0

nvim --version

Build type: Release
LuaJIT 2.1.0-beta3
Compilation: clang -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DNVIM_TS_HAS_SET_MATCH_LIMIT -O2 -DNDEBUG -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wmissing-prototypes -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fno-common -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -I/tmp/neovim-20210927-1441-demfsz/neovim-0.5.1/build/config -I/tmp/neovim-20210927-1441-demfsz/neovim-0.5.1/src -I/usr/local/include -I/Library/Developer/CommandLineTools/SDKs/MacOSX11.sdk/usr/include -I/usr/local/opt/gettext/include -I/tmp/neovim-20210927-1441-demfsz/neovim-0.5.1/build/src/nvim/auto -I/tmp/neovim-20210927-1441-demfsz/neovim-0.5.1/build/include
Compiled by brew@BigSur

Features: +acl +iconv +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/local/Cellar/neovim/0.5.1/share/nvim"

Run :checkhealth for more info 


--Lua Options
vim.cmd('syntax on')
vim.o.shortmess = vim.o.shortmess .. 'c'
vim.o.laststatus=0
vim.o.hidden = true
vim.o.whichwrap = 'b,s,<,>,[,],h,l'
vim.o.pumheight = 10
vim.o.fileencoding = 'utf-8'
vim.o.cmdheight = 2
vim.o.splitbelow = true
vim.o.splitright = true
vim.opt.termguicolors = true
vim.o.conceallevel = 0
vim.o.showtabline = 2
vim.o.showmode = true
vim.o.backup = false
vim.o.writebackup = false
vim.o.updatetime = 300
vim.o.timeoutlen = 100
vim.o.clipboard = "unnamedplus"
vim.o.hlsearch = false
vim.o.ignorecase = true
vim.o.scrolloff = 8
vim.o.sidescrolloff = 5
vim.o.mouse = "a"
vim.wo.wrap = true
vim.wo.number = true
vim.o.cursorline = true
vim.wo.signcolumn = "yes"
vim.o.rnu=true
vim.o.tabstop = 4
vim.bo.tabstop = 4
vim.o.softtabstop = 4
vim.o.shiftwidth = 4
vim.bo.shiftwidth = 4
vim.o.autoindent = true
vim.bo.autoindent = true
vim.o.expandtab = true
vim.bo.expandtab =true

--Lua Plugins config 

return require('packer').startup(function()
  use 'wbthomason/packer.nvim'

  --  use {
    --'hoob3rt/lualine.nvim',
    --requires = {'kyazdani42/nvim-web-devicons', opt = true}
  --}
  use {'akinsho/bufferline.nvim', requires = 'kyazdani42/nvim-web-devicons'}
  use {
    'kyazdani42/nvim-tree.lua',
    requires = 'kyazdani42/nvim-web-devicons'
  }
  use {'windwp/nvim-ts-autotag'}
  use {'p00f/nvim-ts-rainbow'}
  use {'windwp/nvim-autopairs'}
  use {'folke/which-key.nvim'}
  use {
    'nvim-telescope/telescope.nvim',
    requires = { {'nvim-lua/plenary.nvim'} }
  }
  use 'neovim/nvim-lspconfig'
  use 'hrsh7th/cmp-nvim-lsp'
  use 'hrsh7th/cmp-buffer'
  use 'hrsh7th/nvim-cmp'
  use 'hrsh7th/cmp-vsnip'
  use 'hrsh7th/vim-vsnip'
  use 'onsails/lspkind-nvim'
  use {'nvim-treesitter/nvim-treesitter', run = ":TSUpdate"}
  use 'shaunsingh/nord.nvim'

end)

Screen capture of how neovim looks with nord enabled

Indent Blankline show_current_context not working

Screen.Recording.2021-09-03.at.12.15.31.PM.mov

[thread] Plugin highlight requests

As lua in neovim improves, more and more neovim plugins are starting to pop up. Personally, I try to keep my config light on plugins, so its becoming impossible for me to watch new plugins and add their highlights to the theme quickly

If any of you use plugins that you would like theme highlights for, let me know

1. What plugin it is (link to repo)
2. What highlight groups does it supply
3. What colors would you ideally want

And I will add it as soon as I get time

Php class definition doesn't have enough contrast

Just a minor thing. On PHP projects there's no enough contrast on class definitions and such.

Nord

Spacegray

If this is intended just close the issue.

nord_contrast not working

I have nord_contrast set to true and though it is set that way I still have ivim-tree opening with the same background. I am not sure it this a current bug.

Function names not distinct

Ive noticed that function names in various treesitter languages have the same color as built ins key words, another example is in golang type name struct{} all have the same color.
Is this intended? Ive done a cross comparrison with a few other nord themes, vs code for example, and they do have colors for the functions names, although they have a lot less color for many other things so i do prefer this nvim port.

Italic disappears when Treesitter is enabled

Italic disappears when Treesitter is enabled.
Here is how it looks:

And here is how it looks if I enable additional_vim_regex_highlighting = true:

Is this expected behavior?

Setting `nord_disable_background` has no effect

Using neovim:

NVIM v0.5.0
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3

it appears that I'm doing something wrong or the value I set for nord_disable_background does not reach the relevant code in theme.lua.

I use a vim-script config and tried setting before and after loading the plugin, but no effect:

[ ... truncated ... ]
let g:nord_disable_background = 1

" Load vim-plug plugins
call plug#begin()
Plug 'sheerun/vim-polyglot'
Plug 'ryanoasis/vim-devicons'
Plug 'preservim/nerdtree'
Plug 'pearofducks/ansible-vim'
Plug 'Yggdroot/indentLine'
Plug 'itchyny/lightline.vim'
Plug 'neoclide/coc.nvim', {'branch': 'release'}
Plug 'shaunsingh/nord.nvim'
call plug#end()

colorscheme nord
let g:nord_disable_background = 1
[ ... truncated ... ]

However, when I comment out the if vim.g.nord_disable_background == true then statement in theme.lua so that it unconditionally always sets the editor.Normal color to nord.none, then it works.

Support for italic comments via global setting

I love this colour scheme and have been using it for a few weeks, thanks. There's only one little thing missing from the original Nord theme that I think is very useful, the g:nord_italic_comments setting.

It was implemented here.

YAML not working propoerly

After some debugging, I found that the current theme does not work on YAML files.

Using the normal nord (no treesitter) theme:

Using the normal nord (no treesitter) theme:

With nord.vim:

Am I doing something wrong there?

E5105: Error while calling lua chunk: ~/.config/nvim/plugged/nord.nvim/lua/nord/colors.lua:24: attempt to index field 'g' (a nil value)

got this error when attempting to do :colorscheme nord

colors are washed

Hi,

me again :) after filing the feature request, i saw the intro picture again while my nvim was open.
Now it bugs me, that my colors are not that strong like yours and i don't see why

Do you have any idea what the cause can be?

Kind regards, Alexander

When using `require('nord').set()` the set function is called twice

I was trying to customize a few highlight groups in the packer config function by doing something like this:

config = function()
    require('nord').set()
    local util = require('nord.util')
    local colors = require('nord.colors')
    util.highlight('WhichKey', {bg = colors.nord_gui0})
end

And noticed that highlights weren't sticking. Via the power of print statements I determined that after the config function, the ret function was being called a second time via:

nord.nvim/colors/nord.vim

Line 8 in 296167d

require('nord').set()

I got my highlights working by doing them in a separate module, but I figured that this was probably not desired behavior? Could also be a user error.

when enabled cursorline, my cursor is invisible

when enabled cursorline, my mouse is invisible

this is visible because I have rainbow plugin enabled, it colored the {

the cursor is invisible (the cursor actually at column 1):

Mechanic for customizing individual colors

👋 Thank you for making nord.nvim!

Do you think its possible to add a mechanic to override colours for specific groups?
For example, I'd like to use a different (Nord) colour for structs in Rust.

I'd be happy to contribute 😸

Symbols, that are shown in the beginning of wrapped lines, are almost invisible

Symbols, that are shown in the beginning of wrapped lines (for example: vim.opt.showbreak = '+++ '), are almost invisible with the default settings. Here is a screenshot:

Can this be fixed?
Thanks!

Disable bold style

Right now the theme doesn't seems to have the option to disable bold styles in the code.

How can I have a darker nvim-tree background?

doc/tags is committed to the repo

Please do not commit the file doc/tags to the repo, the tags files will be generated automatically by nvim if helptags is run.

Is it possible to override local syntax highlight group?

Hi!

Is it possible to override local syntax highlight group? I'm trying to make statusline of the active window a little bit brighter. One can modify the StatusLine in theme.lua. But is possible to override its value in init.lua?

I have (unsuccessfully) tried something like this:

use {
  'shaunsingh/nord.nvim',
  config = function() 
    vim.cmd[[colorscheme nord]]
    vim.g.nord_italic = true
    StatusLine = { fg = nord.nord4_gui, bg = nord.nord2_gui }
end,
}

What is the correct way to override StatusLine?

Thank you!

IndentBlanklineChar too bright

I would suggest either making this configurable, or changing it to a darker colour like the nord.comments colour... the current white is way too bright when you have deeply nested code.

Adding transparent background also makes the sidebar transparent

Expected Behaviour

It should just make the editor panel transparent but not the explorer

This is an example, folke's tokyonight theme

Actual Behaviour

It makes both the editor panel and the explorer panel transparent

colorcolumn looks weird

It seems colorcolumns is not supported and showed as two bright blue columns. It think it should be a color that requires less attention.

Disable italics?

Is there an option to disable italics?

Highligh colours contrast

This is what I get when I search for something, here ook. The text could maybe be black or at least darker to contract on the white-ish background. I am not 100% if this is a Nord thing…

Again, ignore the background colour. I changed it to suite my awful tastes.

Any support for vim-signify?

These colors appear to be inverted:

Any way to switch the background and the !?

'nord_disable_background' should apply to all telescope floating windows

First off, thanks for your work on this colorscheme.

I'd like to use my terminal's background colour throughout neovim's UI. I'm reproducing with a minimal init.lua which installs packer, nord.nvim and configures the colorscheme

vim.g.nord_disable_background = true
require("nord").set()

The theme looks correct for the main editing window and telescope's file preview, but the Results and Find Files floating windows aren't using the terminal background.

How can I configure nord.nvim so that all of telescope's floating windows use the terminal background color?

Having issues with installing nord.nvim

Here is the error i get

Error detected while processing /home/ryan/.config/nvim/plugged/nord.nvim/colors/nord.vim:
line    9:
E5105: Error while calling lua chunk: .../ryan/.config/nvim/plugged/nord.nvim/lua/nord/colors.lua:44: attempt to index field 'g' (a nil value)

And then here is my init.vim

call plug#begin()
Plug 'sheerun/vim-polyglot'
Plug 'ryanoasis/vim-devicons'
Plug 'preservim/nerdtree'
Plug 'pearofducks/ansible-vim'
Plug 'Yggdroot/indentLine'
Plug 'itchyny/lightline.vim'
Plug 'neoclide/coc.nvim', {'branch': 'release'}
Plug 'shaunsingh/nord.nvim'
call plug#end()

colorscheme nord

How to override default highlight groups

I'm trying to override the default highlight groups with my custom ones. For example, when trying to change the guifg color of the NvimTreeEndOfBuffer group (to hide the ~ characters like the screenshot in the README), those changes don't take effect. I'm doing the following:

require "nord".set()
vim.cmd[[hi NvimTreeEndOfBuffer guifg=#2E3440]]

Also tried using vim.cmd[[colo nord]] and using the nord.util.highlight function, but none of those worked for me. Any ideas on how to override any highlight group? Thanks.

QuickFixLine is difficult to read

The fg is too similar to the bg.

Confused about color being used in vim files and the bufferline used in the screenshot

Really appreciate you stepping up and creating this project and loving it. I'm confused about one thing though. One of the colors used for files with the vim filetype doesn't seem to belong to the Nord colorscheme and I'm confused if this is because of some misconfiguration on my end or if this is intentional.

Another question I had is what is the tabline/bufferline being used in the screenshot you've shared in the readme. It looks amazing and since nvim-bufferline seems to be the only bufferline that's supported, I tried it out but can't get the look that you have going on.

Mangled LICENSE

f6464fa has several paste errors that mangled the LICENSE file

Issues with colorscheme

1. nord_italic option doesn't work properly.
   • Looks like logic is inverted (need to set it to false in order to enable italics):

     nord.nvim/lua/nord/theme.lua

     Lines 54 to 70 in 5cb83df

     	if vim.g.nord_italic == false then
     	syntax.Conditional = { fg = nord.nord9_gui, bg = nord.none, style = 'italic' } -- italic if, then, else, endif, switch, etc.
     	syntax.Keyword = { fg = nord.nord9_gui, bg = nord.none, style = 'italic' } -- italic for, do, while, etc.
     	syntax.Repeat = { fg = nord.nord9_gui, bg = nord.none, style = 'italic' } -- italic any other keyword
     	syntax.Comment = { fg = nord.nord3_gui_bright, bg = nord.none, style = 'italic' } -- italic comments
     	syntax.Function = { fg = nord.nord8_gui, bg = nord.none, style = 'italic' } -- italic funtion names
     	syntax.Identifier = { fg = nord.nord9_gui, bg = nord.none, style = 'italic' }; -- any variable name
     	syntax.String = { fg = nord.nord14_gui, bg = nord.none, style= 'italic' } -- any string
     	else
     	syntax.Comment = {fg = nord.nord3_gui_bright} -- normal comments
     	syntax.Conditional = { fg = nord.nord9_gui } -- normal if, then, else, endif, switch, etc.
     	syntax.Keyword = { fg = nord.nord9_gui } -- normal for, do, while, etc.
     	syntax.Repeat = { fg = nord.nord9_gui } -- normal any other keyword
     	syntax.Function = { fg = nord.nord8_gui} -- normal function names
     	syntax.Identifier = { fg = nord.nord9_gui}; -- any variable name
     	syntax.String = { fg = nord.nord14_gui } -- any string
     	end

   • Treesitter highlights doesn't use it, so it doesn't work at all if treesitter is enabled:

     nord.nvim/lua/nord/theme.lua

     Line 198 in 5cb83df

     local treesitter = {

   • Is it possible to enable italics only for comments?
2. LSP highlights are white on white:

   nord.nvim/lua/nord/theme.lua

   Lines 281 to 283 in 5cb83df

   	LspReferenceText = { fg = nord.nord4_gui, bg = nord.nord4_gui }, -- used for highlighting "text" references
   	LspReferenceRead = { fg = nord.nord4_gui, bg = nord.nord4_gui }, -- used for highlighting "read" references
   	LspReferenceWrite = { fg = nord.nord4_gui, bg = nord.nord4_gui }, -- used for highlighting "write" references

3. Same for NeogitHunkHeader:

   nord.nvim/lua/nord/theme.lua

   Line 313 in 5cb83df

   NeogitHunkHeader = { fg = nord.nord4_gui, bg = nord.nord4_gui },

4. I think there is pretty poor choice for search highlights. For example IncSearch is highlighted with white. If text is already white, then it's unreadable. And even regular search-highlight changes text color to white with slight background. Usually it's the opposite, highlighted text has prominent background color instead of erasing syntax highlighting. Maybe style = 'reverse' shouldn't be used there?
   Normal color:
   
   Search highlight for nor:
   
5. Also I'd like to point out that "async" is pretty useless here:

   nord.nvim/lua/nord/util.lua

   Line 47 in 5cb83df

   async = vim.loop.new_async(vim.schedule_wrap(function ()

   
   It doesn't improve startuptime at all. It just delays execution of a function to some later time, but you still can't use neovim until it's done. You can try to add os.execute("sleep 10") anywhere in your async function, than run neovim. You'll see, that neovim isn't responding for 10 seconds after startup. So this async just complicates code, trick profiler, but doesn't improve loading time.

Should the highlight of the search be more obvious?

Modifying the background color may be a better choice.

Treesitter support in vim-nord -- link FYI

Nord has an issue/PR for tree sitter support.

This might be of interest and I have linked this repo to the issue there.

Feel free to close this if it is of no interest. ^_^

airline-vim Nord theme colours

The above is using nord-vim with airline-vim's nord theme.

This is what I see using your code.

Note: please do ignore the background colour, I changed it to match my weird and abject tastes.

Folds are way too dark

Hey, I think folds would benefit from more contrast:

Nvim-tree symlinked directories too dark

Hi,

Really enjoying the collection of themes! Any chance you could increase the contrast on symlinked directories in nvim-tree?

Thanks!

feat: styles for romgrk/barbar.nvim

Hi,

can you add styles for romgrk/barbar.nvim? Or can you give me a hint, where i can get and add stylings for bufferlines? (I could pr you then).

Kind regards, Alexander

How to turn off TelescopeSelection by init file

I want to turn this off, which command I should use to overwrite it in init file ?

Thank you :)

None 24-bit color terminal compatibility

It's a great theme and I love it. It works on almost terminal emulators. Although, like some terminals (e.g. Apple Terminal.app) which doesn't support truecolor (24-bit) fails to show the color scheme correctly. Is it possible to modify the theme for such terminal emulators?

Syntax highlighting not working with treesitter!

Image:

Issue: No syntax highlighting for cpp ?

Code :

lua << EOF
require'nvim-treesitter.configs'.setup {
  ensure_installed = {"c", "cpp", "css", "scss", "html", "javascript", "typescript", "json", "vim"}, 
  highlight = {
    enable = true,
    additional_vim_regex_highlighting = false
  },
}
EOF

Neovim HEAD changed LSP highlight groups

A recent change neovim/neovim#15585 replaced LSP diagnostic highlight groups, see neovim/neovim#14090 (comment).

Issue with HTML documents

This only happens when using treesitter. Otherwise it works fine.

add support for barbar buffer picking

the default red might be a bit jarring in barbar.nvim's buffer picking function. can this be changed to another color which fits with the nord theme?

could not override BufferLineFill

because nord async set BufferLineFill, it is ugly

and i could not find a way override it, because it is asynced

Blame in gitsigns not visible when using cursorline

The current-line blame feature of Gitsigns is not visible when cursorline is on. Even with cursorline off, it's very hard to read. In gitsigns that text has a highlight group of GitSignsCurrentLineBlame.

Using cursorline:

No cursorline:

I can push a PR but I'm not sure what to set the colors to.

Incorrect treesitter hightlighting

The syntax highlighting of nord.nvim (nord vim too) don't follow the same syntax highlighting as other themes when using treesitter's highlighting functionality.
Notice the lack of highlighting in the outputsBuilder part.

See below:

• First image - nord.nvim + treesitter
• Second image - nord.nvim only
• Third image - default nvim theme + treesitter
• Fourth image - dracula + treesitter