nordtheme / vim Goto Github PK

Really love this colorscheme, far and beyond any other. I use it wherever I can.

I realise it's subjective, but it's pretty hard to read comments as it is - and very tough under the cursorline.

Implement the vim-airline theme.

The visual selection colour defined by, call s:hi("Visual", "", s:nord2_gui, "", s:nord3_term, "", "") uses the same colour, s:nord3_term as comments do. This means that when selecting comments with visual regions you cannot read the selected area.

This could be easily resolved by making the visual region use the colour, s:nord1_term. This colour does not appear to clash with other syntax elements, and hence should be a better choice the visual region colour.

Subtask of nordtheme/nord#55

Adapt to the MIT license migration of the main Nord project. Detailed information can be found in the main task ticket.

Tasks

• Update all license SVG badges
• Update the LICENSE.md content
• Update- and simplify all source code comment header

Running :%s/target/replacement/gc will make the cursor disappear. This is due to the highlight groupSearch and IncSearch having identical colors. Base16 had an identical issue and it was resolved in chriskempson/base16-vim#129.

iTerm banner https://cdn.rawgit.com/arcticicestudio/nord/develop/src/assets/nord-iterm2-banner.svg looks the same as GNOME svg banner.

With nord-vim & denite.nvim, it cannot show searching words.

But I don't know this matter is derived from Denite itself, or Nord colorscheme...

reproducing

1. Set iTerm2 colorscheme to Nord.

2. clone plugins

   mkdir /tmp/test
   cd /tmp/test
   git clone https://github.com/arcticicestudio/nord-vim
   git clone https://github.com/Shougo/denite.nvim

3. make minimal vimrc & launch Vim

   set runtimepath+=/tmp/test/denite.nvim,/tmp/test/nord-vim
   colorscheme nord

   vim -N -u vimrc -i NONE

4. launch denite & search some words

   :Denite file
   
   " and type some word to search
   vim

The highlighted word vim disappeared only at top line. (and strange a bit at the second line nord-vim)

case: solarized

But with other colorschemes such as solarized, this does not occur.

1. Set iTerm2 colorscheme to Solarized Dark.

2. clone plugins

   mkdir /tmp/test
   cd /tmp/test
   git clone https://github.com/altercation/vim-colors-solarized
   git clone https://github.com/Shougo/denite.nvim

3. make minimal vimrc & launch Vim

   set runtimepath+=/tmp/test/denite.nvim,/tmp/test/vim-colors-solarized
   colorscheme solarized

   vim -N -u vimrc -i NONE

4. launch denite & search some words

   :Denite file
   
   " and type some word to search
   vim

First off, thanks so much for this colorscheme. This is easily my favorite colorscheme ever. I'm obsessed.

In the screenshot below, there is the same block of text in nord and in elflord. You can see that the $TERM and color_prompt variables are not distinguished by any color.

I would really like to see a color for these bash variables. I don't care which color. You are obviously great at choosing colors. Just anything to distinguish the variables from text.

Could you consider adding the lightline theme to the lightline repository to offer a more seamless experience?

plugDeleted links to Ignore and the result is invisible unless you have :set cursorline enabled and are on that line:

changing ctermfg to s:nord3_term and guibg to s:nord3_gui for Ignore seems like a good fix.

This is a follow up of #12.
Implement support for (DOS) INI.

It should define all groups that are not matching the Nord style guide and groups that are currently using Special as fallback.

Groups:

• dosiniHeader
• dosiniLabel

When using set tgc on Neovim so that I can take advantage of comment brightness, I get the wrong background color when using it inside tmux.

OS X High Sierra
iTerm2 3.1.5 (xterm-256color)
Tmux 2.6 (screen-256color)
neovim 0.2.1 (tgc set)

running in tmux:

no tmux:

Hi,
I got incorrect highlight when editing a javascript file that contains following words require, module. Is there something to do with vim-javascript plugin? I'm using pangloss/vim-javascript

This only occurs in terminal vim, when I try it in macvim, the highlight is correct and the word is in italic. In the readme it is mentioned that italic is disabled by default, but it is only for comments.

Is there any configuration I need to set to get correct highlighting?

Below is the picture, left is iTerm2, right is MacVim

Thanks

Background for Todo isn't set manually and looks bad.

It looks good when cursorline is on, and you're on that line, but it looks bad when you move away.

I'll make pull request when I get home ... I'll just set background for term and gui to NONE, and hopefully, that'll do the trick.

cheers 😄

(ps if you don't see it in vim, I'm in gvim 😢 at work)

I'm using the lightline theme and its appearance is different from the one shown in the screenshot. The screenshot shows triangles at the end of each section (?) whereas the theme, as it is installed now, only uses straight lines for its edges.

Here is what I'm talking about:

Screenshot

Theme

Is this what the theme looks like presently or is something wrong on my end?

To my knowledge there is no simple solution, but I thought I would ask just in case.

I find comments difficult to read due to the low contrast between the comment and background colours. I was wondering if this could be fixed in a similar manner as the solarized theme, with g:solarized_contrast="high".

I believe this is possible, the real question is, what colour should be substituted. Unfortunately the 16-colour palate does not contain a lighter shade of grey!

The only possible solution I could suggest would be to use a 256-colour fallback. However, none of these appear to be a suitable "blue/grey" colour to replace the original.

Another option would be to "personalise" the 16-colour palate, by adjusting the grey.

Would appreciate your thoughts, thanks!

📝 A arctic ... -> An arctic ...

This is a 🔀 sub-task of nord #20.

Is the diff supposed to look like this?

I am trying to think of a better, low-contrast option, but I am not sure I can think of any since all of the colors (besides black) are fairly high contrast.

there is still probably a better option; I might make a pull request tomorrow if I don't hear or get the go-ahead..

Nord-vim does not highlight Constant, Identifier and Special groups, which makes files of several types less readable when using vim's default syntax files that make use of those groups. Especially Special is often used, for example in the default syntax of awk.

Hi,

The same configuration as previous issue without cursorline set:
I am using neovim with colorscheme nord (installed separately in colors/ folder), I removed all plugins and personal configuration.

During the search for a text between quotes, the highlighting color is incorrect (right)
Once I validate my search, the behavior is correct (left)
incsearch is activated by default

Thanks.

Is there any plan to support Italic?

Implement the lightline.vim color scheme.

This theme looks awesome, but the highlight in terminal is invisible and it seems to be set to the terminal background color here: https://github.com/arcticicestudio/nord-vim/blob/develop/colors/nord.vim#L107.

The airline colors also seems a bit off in the terminal:

Works fine in the gui version :)

EDIT: I have also installed themes for my terminal so that is not the problem.

Hello,

Using your awesome vim color theme I have a small issue regarding the tab completion selector.

In fact, there is no different color when doing completion, see screenshot:

I'm running Neovim (NVIM v0.2.0). TODO items are highlighted in a very awful looking yellow color.

Running :highlight Todo:

In the colorscheme we see that guibg is set to "" and ctermbg is set to NONE. We probably want to set this to something relevant.

I'd be happy to submit a pull request. Just need to know what colors we should be using.

This is a follow up of #12.
Implement support for [Lisp](https://en.wikipedia.org/wiki/Lisp_(programming_language).

It should define all groups that are not matching the Nord style guide and groups that are currently using Special as fallback.

Groups:

• lispAtomBarSymbol
• lispAtomList
• lispAtomMark
• lispBarSymbol
• lispFunc

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

Can it be fixed?

Implement the main color theme file.
It should be implemented as 16 colorspace theme with support for the terminal- and GUI mode.

Colorspace design decision

Nord Vim is not designed for the 256 colorspace to keep it faithful to the Nord design guideline. The 256 colorspace limits the possibility to create the same ambient and does not provide the necessary color shades.

Language

Nord Vim should implement optimized styles to achieve a consistent and uniform coloring across languages. This includes support for third-party language plugins for more highlighting groups.

Colors

The order of the colors must reflect the ANSI Escape Code Colors for foreground and background.

Background: nord0
Foreground: nord4

Normal

Bright

Feel the comment contrast is a bit too low:

I'm setting it to hi Comment ctermfg=14 temporarily, but hope you can resolve it.

Not against the idea that comment should be in the same hue as bg, but the contrast needs to be higher.

Now this one uses it to a ridiculous degree.

Two groups are linked to Special: sqlSpecial (which consists just of true, false and null) and the very blanket sqlKeyword, which groups every reserved word that does not start a statement (ie. not select, insert and friends), is not an operator or a type/function name.

This is defined in sqloracle.vim syntax file, which is the one loaded by default if no other sql dialect is explicitly selected.

Hi. I noticed a few color issues that I corrected. I don't have True Color, as I use rxvt-unicode, but I set my term colors (in ~/.Xresources) to the nord palette, and I also checked everything in gvim.

I love nord (switching from solarized and hybrid/hybrid-material), but I noticed that when I first loaded it, I got a lot of wonky colors (as a few others have mentioned).

I saw this (and this is in gvim, but I see the same thing in vim/nvim):

As you can see, the Folds and Comments are almost invisible, and when you search, the IncSearch looks awful as does the Search.

So, I added this to my vimrc:

highlight Folded cterm=italic,bold ctermbg=0 ctermfg=12 guibg=#3B4252 guifg=#81A1C1
highlight Comment ctermfg=12 guifg=#81A1C1
highlight Search ctermbg=3 ctermfg=0 guibg=#EBCB8B guifg=#3B4252
highlight IncSearch ctermbg=8 guibg=#4C566A

The results look like so:

You don't have to incorporate the italic,bold on Folded, but I like it. Moreover, these small highlights seem to make it look much better.

It's quite late; so, I haven't looked at the nord.vim colorscheme file, but if you'd like me to submit a pull request, let me know. If not, hopefully this can help make nord the best!

Thanks for this great palette!
~ dylnmc

When using the block cursor the text is not readable due to the same nord4 color.

Solution
This can be fixed by using nord0 as foreground text color while the block cursor is visible to achieve a optimal contrast.

Currently all filenames appear white when using fugitive.vim's :Gstatus command.

It would be nice to have the filenames appear red/green to mimick the out put of git status using one of the Nord terminal schemes.

The theme is great but when I run it in Gnome Terminal 3.22.1, I get this:

Error detected while processing function <SNR>50_hi:
line 17:
E254: Cannot allocate colour 1
E254: Cannot allocate colour 3
E254: Cannot allocate colour 7
E254: Cannot allocate colour 15

The theme seems to load nonetheless. I suppose it might be about the guisp parameter.

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?

Currently, nord-vim uses the bare :hi command to set up highlight colors, but it should be using :hi def.

From Vim documentation: https://vimhelp.appspot.com/syntax.txt.html#%3Ahighlight-default.

This will make it easier for users to customize coloring.

Right now, any custom modifications must be placed after the :color nord command in the .vimrc file and calling :color nord again erases those modifications.

vs

Hi,

I am using neovim with colorscheme nord (installed separately in colors/ folder), I removed all plugins and personal configuration. cursorline is set to highlight the whole line.

Here is the result for :CheckHealth

Thanks.

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

OTHER:

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

Jedi-vim is a popular Vim plugin for python programming.

One of its features is a live preview of the signature of the function that is being currently typed. Current position in the argument list is highlighted, but in nord-vim this is not visible. That's because jedi-vim assumes that TabLine and CursorLine groups are highlighted differently, but they aren't in nord-vim.

From https://github.com/davidhalter/jedi-vim/blob/master/after/syntax/python.vim:

    if exists('g:colors_name')
        hi def link jediFunction CursorLine
        hi def link jediFat TabLine
    else
        hi jediFunction term=NONE cterm=NONE ctermfg=6 guifg=Black gui=NONE ctermbg=0 guibg=Grey
        hi jediFat term=bold,underline cterm=bold,underline gui=bold,underline ctermbg=0 guibg=#555555
    endif

Either TabLine and CursorLine should be highlighted differently, or the plugin-specific jediFunction and jediFat overridden (jediFat is the one that should stand out more).

g:colors_name is not properly set.

:colorscheme nord
:colorscheme
default

:echo g:colors_name
E121: Undefined variable: g:colors_name

g:colors_name should be set after syntax reset.

Supersedes #50

Add a theme configuration to let the users decide whether they want to use colorful or uniform diff backgrounds.

The colorful diff should be default using the current colors for added, changed and deleted elements and the default background color (nord0). The reverse attribute should be applied which will result in a colored background and a dark foreground.

Setting the g:nord_uniform_diff_background variable to 1 will enable the uniform diff background using nord1.

So I finally found out how the Identifier group seems to be usually used in vim syntax files. It's rather obvious, really. For languages like bash, tcl, perl, php, etc. Identifier is used for sigil-prefixed forms like $var.

Since there are many languages that use sigils like these, I'd once again recommend that the group Identifier should be unconditionally highlighted. I don't think you ever stated what you intended to do with Identifier in #12.

Headers in Markdown files are colored nord7 instead of nord8.

In order to give some context, the vim plugin tmuxline.vim is used to generate a statusline for tmux based off the current vim statusline. This statusline can be either, the vanilla vim statusline, or from the vim plugins, vim-airline or lightline.vim.

I am currently using lightline.vim with the Nord theme. As you can see below, the generated statusline is quite close, but there are some differences. In one segment, the foreground and background colour are the same.

This issue could be manually by exporting the generated statusline and configuring it manually, however this is not an ideal solution.

I managed to track the cause of this issue down to the lightline.vim theme supplied by nord-vim. As seen in the extract below, some of the colours use the identifier "NONE". By replacing all instances of "NONE" with nearest suitable colour (due to the limited terminal colour palate), this fixed the issue. Please note, lines have been omitted in the example below.

" the old nord.vim configuration.
let s:nord0 = ["#2E3440", "NONE"]
let s:nord2 = ["#434C5E", "NONE"]
let s:nord4 = ["#D8DEE9", "NONE"]

" the new nord.vim configuration.
let s:nord0 = ["#2E3440", 0]
let s:nord2 = ["#434C5E", 8]
let s:nord4 = ["#D8DEE9", 7]

This resulted in the fixed statusline, which appears to look as intended.

I am not an expert in vim, and I couldn't find much documentation on the "NONE" property, which appears to make the character pseudo transparent (setting the foreground colour to the previous background color, at least this hypothesis appears to hold true).

It would be great if someone with more experience could try and understand the issue better, but until then my fix appears to work so I will continue using that for the moment.

Here are some notable files which helped me identify the issue,

• https://github.com/arcticicestudio/nord-vim/blob/develop/autoload/lightline/colorscheme/nord.vim
• https://github.com/edkolev/tmuxline.vim/blob/master/autoload/tmuxline/themes/lightline.vim
• https://github.com/edkolev/tmuxline.vim/blob/master/autoload/tmuxline/util.vim

Hope you can help. Thanks!

Related to #36

The fold marker are currently using nord1 as foreground color. This is too dark causing them to be unreadable in bright environments and should be adjusted to match the color of comments.

\cc @syedelec

This is a follow up of #12.
Implement support for AWK.

It should define all groups that not matching the Nord style guide and groups that are currently using Special as fallback.

Groups:

• awkArrayElement
• awkBoolLogic
• awkBrktRegExp
• awkCharClass
• awkComma
• awkExpression
• awkFieldVars
• awkLineSkip
• awkOperator
• awkPatterns
• awkRegExp
• awkSearch
• awkSemicolon
• awkSpecialCharacter
• awkSpecialPrintf
• awkVariables

The contrast (or colour intensity) for brackets under the cursor annoyed me a lot recently.
The problem as you can see from the screenshots below is: when you moving the cursor, the bracket will blink between frame 1 and frame 2. Even worse, frame 1 comes first and has a darker colour without other visual indications. So my eyes are distracted to focus on the matching bracket instead of the bracket at the cursor position.

Nord bracket under cursor frame 1

Nord bracket under cursor frame 2

In contrast, Gruvbox set it in a more intuitive way:

Gruvbox bracket under cursor frame 1

Gruvbox bracket under cursor frame 2

Probably you guys could consider updating the colour a bit?
Thank you for making such a great suites of colour schemes!

The highlighting for Markdown will stop to work once 'plasticboy/vim-markdown' is installed. Could it be because they have a different system of syntax naming? I never had any Markdown highlighting problem with other color schemes before.

Expected:

Actual:

Since you decided not to highlight the blanket Special group, these probably need to be addressed.

There are two groups defined in Python syntax that use Special by default: pythonEscape and pythonDoctest.

pythonEscape should probably be using SpecialChar, since it's for \n and friends. pythonDoctest refers to the >>> (and ...) that start doctests in python docstrings. Perhaps also SpecialChar, or SpecialComment?