GithubHelp home page GithubHelp logo

bluz71 / vim-nightfly-colors Goto Github PK

View Code? Open in Web Editor NEW
768.0 6.0 53.0 340 KB

A dark midnight theme for modern Neovim & classic Vim

License: MIT License

Shell 1.38% Lua 58.26% Vim Script 40.16% Scheme 0.21%
vim neovim nvim kitty-themes neovim-colorscheme iterm2-theme alacritty-theme vim-colorscheme neovim-theme vim-theme

vim-nightfly-colors's Introduction

nightfly

nightfly is a dark midnight theme for modern Neovim and classic Vim.

Note, all nightfly highlights in Neovim are implemented in Lua, whilst highlights in Vim are implemented in legacy Vimscript.

๐Ÿ‘‰ I maintain another dark theme named moonfly which may be of interest.

Screenshot

screenshot

Styled Features & Plugins

Neovim-only:

Neovim & Vim compatible:

Vim-only:

โšก Requirements

nightfly is a GUI-only colorscheme.

A GUI client or a modern terminal version of Vim or Neovim in a true-color terminal is required. Details about true-color terminals are listed here.

nightfly explicitly does not support the 256 color cterm version of Vim.

Installation

Install the bluz71/vim-nightfly-colors colorscheme with your preferred plugin manager.

lazy.nvim:

{ "bluz71/vim-nightfly-colors", name = "nightfly", lazy = false, priority = 1000 },

vim-plug:

Plug 'bluz71/vim-nightfly-colors', { 'as': 'nightfly' }

Usage

Enable the colorscheme after the plugin declaration.

" Vimscript initialization file
colorscheme nightfly
-- Lua initialization file
vim.cmd [[colorscheme nightfly]]

Statusline

  • The nightfly theme supports lightline. To enable the nightfly lightline theme please add the following to your initialization file:
let g:lightline = { 'colorscheme': 'nightfly' }
  • The nightfly theme supports vim-airline. The nightfly theme will load once vim-airline starts.

  • The nightfly theme supports Lualine. The nightfly theme will automatically load once Lualine starts.

  • My linefly statusline plugin supports the nightfly theme.

  • Lastly, my legacy mistfly-statusline plugin also supports the nightfly theme.

๐Ÿ”ง Options

Option Default State
nightflyCursorColor Disabled
nightflyItalics Enabled
nightflyNormalFloat Disabled
nightflyTerminalColors Enabled
nightflyTransparent Disabled
nightflyUndercurls Enabled
nightflyUnderlineMatchParen Disabled
nightflyVirtualTextColor Disabled
nightflyWinSeparator 1

nightflyCursorColor

The nightflyCursorColor option specifies whether to color the cursor or not. By default the cursor will NOT be colored. If you prefer a colored cursor then add the following to your initialization file:

" Vimscript initialization file
let g:nightflyCursorColor = v:true
-- Lua initialization file
vim.g.nightflyCursorColor = true

nightflyItalics

The nightflyItalics option specifies whether to use italics for comments and certain HTML elements in GUI versions of Vim. By default this option is enabled. If you do not like the appearance of italics then add the following to your initialization file:

" Vimscript initialization file
let g:nightflyItalics = v:false
-- Lua initialization file
vim.g.nightflyItalics = false

nightflyNormalFloat

The nightflyNormalFloat option specifies whether to use nightfly background and foreground colors in Neovim floating windows. By default this option is disabled, hence, Neovim floating windows will usually be styled with popup menu colors. If you would like to use nightfly colors instead then add the following to your configuration:

" Vimscript initialization file
let g:nightflyNormalFloat = v:true
-- Lua initialization file
vim.g.nightflyNormalFloat = true

๐Ÿ’ก If the above option is set then it is highly recommended to enable floating window borders to distinguish between the edit and floating windows in Neovim's LSP client, for example:

  vim.lsp.handlers['textDocument/hover'] = vim.lsp.with(
    vim.lsp.handlers.hover, {
      border = "single"
    }
  )
  vim.lsp.handlers['textDocument/signatureHelp'] = vim.lsp.with(
    vim.lsp.handlers.signatureHelp, {
      border = "single"
    }
  )
  vim.diagnostic.config({ float = { border = "single" } })

๐Ÿ’ก Likewise, nvim-cmp may be configured as follows for nicer display when g:nightflyNormalFloat is enabled:

local winhighlight = {
  winhighlight = "Normal:NormalFloat,FloatBorder:FloatBorder,CursorLine:PmenuSel",
}
require('cmp').setup({
  window = {
    completion = cmp.config.window.bordered(winhighlight),
    documentation = cmp.config.window.bordered(winhighlight),
  }
})

nightflyTerminalColors

The nightflyTerminalColors option specifies whether to use the nightfly color palette in :terminal windows when termguicolors is set. By default this option is enabled. If you prefer not to use the nightfly color palette for the first 16 terminal colors then add the following to your initialization file:

" Vimscript initialization file
let g:nightflyTerminalColors = v:false
-- Lua initialization file
vim.g.nightflyTerminalColors = false

nightflyTransparent

The nightflyTransparent option specifies whether to use an opaque or transparent background in GUI versions of Vim. By default this option is disabled. If you would like a transparent background then add the following to your initialization file:

" Vimscript initialization file
let g:nightflyTransparent = v:true
-- Lua initialization file
vim.g.nightflyTransparent = true

nightflyUndercurls

The nightflyUndercurls option specifies whether to use undercurls for spelling and linting errors in GUI versions of Vim, including terminal Vim with termguicolors set. By default this option is enabled. If you do not like the appearance of undercurls then add the following to your initialization file:

" Vimscript initialization file
let g:nightflyUndercurls = v:false
-- Lua initialization file
vim.g.nightflyUndercurls = false

nightflyUnderlineMatchParen

The nightflyUnderlineMatchParen option specifies whether to underline matching parentheses. By default this option is disabled. If you want to underline matching parentheses then add the following to your initialization file:

" Vimscript initialization file
let g:nightflyUnderlineMatchParen = v:true
-- Lua initialization file
vim.g.nightflyUnderlineMatchParen = true

nightflyVirtualTextColor

The nightflyVirtualTextColor option specifies whether to display diagnostic virtual text in color. By default this option is disabled. If you want to display diagnostic virtual text in color then add the following to your initialization file:

" Vimscript initialization file
let g:nightflyVirtualTextColor = v:true
-- Lua initialization file
vim.g.nightflyVirtualTextColor = true

nightflyWinSeparator

The nightflyWinSeparator option specifies the style of window separators:

  • 0 will display no window separators

  • 1 will display block separators; this is the default

  • 2 will diplay line separators

For example, if line separators are desired then add the following to your configuration:

" Vimscript initialization file
let g:nightflyWinSeparator = 2
-- Lua initialization file
vim.g.nightflyWinSeparator = 2

๐ŸŽ If using Neovim 0.7 (or later), the following configuration will improve the look of line separators (if option 2 has been chosen) by selecting thicker characters for the separators:

" Vimscript initialization file
set fillchars=horiz:โ”,horizup:โ”ป,horizdown:โ”ณ,vert:โ”ƒ,vertleft:โ”จ,vertright:โ”ฃ,verthoriz:โ•‹
-- Lua initialization file
vim.opt.fillchars = { horiz = 'โ”', horizup = 'โ”ป', horizdown = 'โ”ณ', vert = 'โ”ƒ', vertleft = 'โ”ซ', vertright = 'โ”ฃ', verthoriz = 'โ•‹', }

Overriding Highlights

If a certain highlight of this theme does not suit then it is recommended to use an autocmd to override that desired highlight.

For example, if one wishes to highlight functions in bold then simply add the following to your initialization file prior to setting the colorscheme:

" Vimscript initialization file
augroup CustomHighlight
    autocmd!
    autocmd ColorScheme nightfly highlight Function guifg=#82aaff gui=bold
augroup END
-- Lua initialization file
local custom_highlight = vim.api.nvim_create_augroup("CustomHighlight", {})
vim.api.nvim_create_autocmd("ColorScheme", {
  pattern = "nightfly",
  callback = function()
    vim.api.nvim_set_hl(0, "Function", { fg = "#82aaff", bold = true })
  end,
  group = custom_highlight,
})

True Color Terminals

Many modern terminals support 24-bit true colors. Current versions of Vim & Neovim on such terminals support true colors when set termguicolors is enabled.

On terminals that support true colors, and when termguicolors is set, the nightfly colorscheme will emit the correct theme colors.

For the nightfly colorscheme to display correctly inside tmux the following setting will usually be required in ~/.tmux.conf:

set -ga terminal-overrides ',xterm-256color:Tc'

Vim, as against Neovim, inside tmux, will also require the following settings be added to the ~/.vimrc file:

let &t_8f = "\<Esc>[38;2;%lu;%lu;%lum"
let &t_8b = "\<Esc>[48;2;%lu;%lu;%lum"

Extra Themes

A collection of nightfly-flavoured themes are provided:

  • Alacritty users can copy this theme into their alacritty.toml configuration

  • kitty users can use this theme

  • WezTerm users can copy this theme into the colors directory and then select the nightfly color_scheme in their wezterm.lua configuration

  • iTerm2 users on macOS can import this colorscheme

  • Windows Terminal users can copy this theme into their settings.json configuration

  • fish shell users can use this theme

For other terminals please configure appropriately with the following colors:

Type Category Value Color
Background Background #011627 background
Foreground Foreground #bdc1c6 background
Bold Bold #eeeeee background
Cursor Cursor #9ca1aa background
Cursor Text Cursor Text #080808 background
Selection Selection #b2ceee background
Selection Text Selection Text #080808 background
Color 1 Black (normal) #1d3b53 background
Color 2 Red (normal) #fc514e background
Color 3 Green (normal) #a1cd5e background
Color 4 Yellow (normal) #e3d18a background
Color 5 Blue (normal) #82aaff background
Color 6 Purple (normal) #c792ea background
Color 7 Cyan (normal) #7fdbca background
Color 8 White (normal) #a1aab8 background
Color 9 Black (bright) #7c8f8f background
Color 10 Red (bright) #ff5874 background
Color 11 Green (bright) #21c7a8 background
Color 12 Yellow (bright) #ecc48d background
Color 13 Blue (bright) #82aaff background
Color 14 Purple (bright) #ae81ff background
Color 15 Cyan (bright) #7fdbca background
Color 16 White (bright) #d6deeb background

Sponsor

Ko-fi

License

License: MIT

vim-nightfly-colors's People

Contributors

bluz71 avatar bobbleclank avatar gcstr avatar jayphen avatar jbyuki avatar nakakitasota avatar p00f avatar qgadrian avatar strayer avatar uga-rosa avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar

vim-nightfly-colors's Issues

Tmux Version of Nightfly Theme?

Has anyone put together some Tmux settings that look good with Nightfly?

While Tmux itself seems to support true-color, I can't seem to get actual hex color codes to work with Tmux's fg=,bg= color options, it seems to just pick an approximate (somewhat matching but not exact) color for the actual Tmux UI (even though true color apps inside of tmux work fine).

Anyway, even if somebody's got a 256color theme that just is a nice match with nightfly that would be awesome. Right now I've got a tmux theme that's kind of close and so it clashes really badly...

[TS] Unused variables are impossible to see

Hello - after recent updates I've noticed unused variables are almost impossible to see. I suspect it has something to do with this commit: 673d276
which removes the white color for CocUnusedHighlight

now in TS files unused variables look like this:

CleanShot 2021-12-06 at 10 40 05

I'm using nvim 0.6 (linux), nvim-treesitter, nvim-lspconfig, and coc.nvim

Doesn't work with simple ~/.vimrc

zshconfig

The output:

Error detected while processing /home/povilasb/.vimrc:
line    1:
E488: Trailing characters: # pbgroupeu
line    3:
E492: Not an editor command: Plug 'bluz71/vim-nightfly-guicolors'
line    4:
E492: Not an editor command: :PlugInstall
line    6:
E185: Cannot find color scheme 'nightfly'
Press ENTER or type command to continue

Following the official this bistro main branch configuration.

Extremely hard to notice `listchars`

First, ty for this fantastic colorscheme, love it :-)

As you can see below the current listchars highlights makes it extremley hard to notice some listchars (aside from the EOL):

the right side of the screen is the embark colorscheme with transparent background:
image

Not working in vim on iterm2

Problem description
Colors are off in vim 8.2 on iTerm2 3.3.9.

STR

โฏ vim --version
VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Apr 29 2020 01:33:43)
โฏ git clone git clone https://github.com/bluz71/vim-nightfly-guicolors.git ~/.vim/pack/vendor/start/vim-nightfly-guicolors

.vimrc:

set termguicolors
colorscheme nightfly

Expected result

nightfly color scheme glory

Actual result

Colors change, but are awfully off. Looks like an approximation by closest match from the 256 color palette.

vimcolors

E185: Cannot find color scheme 'nightfly'

I used vim-plug to install the plugin and it can see it being installed in .vim/plugged/vim-nightfly-guicolors, and set the color scheme to ' nightfly', but when I start vim it shows:

E185: Cannot find color scheme 'nightfly'

I just can't figure out what I could have missed.

[question] italics in markdown

hello! first of all, absolutely lovely theme, an even better version of solarized, it perfectly scratched the itch I had over a high-contrast blue dark theme.

quick question, why disable markdown italics?
in the default theme, an italic looks like this:
image

which i do concede, orchid is a very nice color choice and as you described here you don't quite like bold fonts (and i wholeheartedly agree, don't like bold text) and hl link is faster than the default hl

wouldn't setting g:nightflyItalics to true enabling it be a better experience?
imho looks quite nice when you patch it
image

how do you feel about letting this be a config?
thanks in advance!

Javascript syntax highlighting issue with vim-jsx and vim-javascript plugins on together

Running:

  • Iterm2 v3.4.5
  • Neovim v0.4.4

I noticed that if I have both the vim-javascript and vim-jsx plugins defined in my init.vim file, I get some weird syntax highlighting issues on the if statement, parenthesis and the string passed into console.log. There could be more discrepancies, but this is the ones I picked up from a quick glance. Not sure if this is an issue with this theme or the actual plugins?

See below

" Snippet of init.vim config
...
Plug 'pangloss/vim-javascript'
Plug 'mxw/vim-jsx'
...
  1. With both vim-javascript and vim-jsx switched on in init.vim

Screenshot 2021-05-24 at 23 01 49

  1. Only vim-javascript switched on in init.vim

Screenshot 2021-05-24 at 23 07 14

`g:nightflyTransparent` is not working

Related to #38

g:nightflyTransparent is breaking by changed color definition in now commit.

This problem is caused by defined bg=NONE in vim script.

So, needs define as "constants" colors in lua script to fix this.

My workaround is here.

Add color hex values to README

Hey! I saw Nightfly on Reddit the other day and am checking it out. It's really great! Very nice work!

I was wondering if you would mind adding the hex values for each color to the table in the README. I'm working on setting up some of my other tools to use the Nightfly color palette as well, and having the hex next to the name and "swatch" for each of them would be really helpful!

In the meantime, I'm reading them from here

https://github.com/bluz71/vim-nightfly-guicolors/blob/7580e56103db6f7c7e92c7c795634663581dff06/colors/nightfly.vim#L49-L75

Provide an option for colourful diagnostic virtual text.

Something like g:nightflyColoredDiagnosticVirtualText that does this when set to true:

highlight(0, "DiagnosticVirtualTextError", { link = "NightflyRed" })
highlight(0, "DiagnosticVirtualTextWarn", { link = "NightflyYellow" })
highlight(0, "DiagnosticVirtualTextInfo", { link = "NightflyBlue" })
highlight(0, "DiagnosticVirtualTextHint", { link = "NightflyWhite" })

JSX tag colors

Hey, thanks for yet another great vim plugin. Have been really enjoying your library for plugins :)
I wanted to ask, whether jsx tags, for opening and closing tags, being of different colors was a design decision you took while creating this color scheme? Note- I am currently using Neovim 0.4x with vim-polygot for syntax highlighting
nightfly

W18: Invalid character in group name

Hi There,

I'm getting an error when entering neovim, specifically

W18: Invalid character in group name

I'm using NVIM .7, and on WSL2 using a ubuntu 20.04 distro.

Would appreciate any help!

Disable airline theme?

Love your theme. Keep it up!

Is there a way to disable the colorscheme for airline since it automatically loads?

'set termguicolors' breaking colors

Similar problem to #6. With set termguicolors not set, The termguicolors option must be set message appears when opening Vim, but colors work correctly. Setting the option in vimrc makes the message go away, but no colors are displayed.

Cant enable theme

Hi! First thing, that i wanna 2 tell about: your project is great, thx 4 it

Your theme working well in Firenvim (in browser). But i cant activate it outside of Chrome... Idk, why. I even removed all text from init.vim, besides:

call plug#begin(has('nvim') ? stdpath('data') . '/plugged' : '~/.vim/plugged')
Plug 'bluz71/vim-nightfly-colors'
call plug#end()

colorscheme nightfly "must be after plugin installation section

That didnt help...

System: Arch/i3
My nvim-config: https://github.com/HappyCthulhu/.config/blob/master/nvim/init.vim

Disruptive changes in treesitter

There has been a major change in treesitter and some of the highlighting (e.g. the built-in function: require, pcall, etc.) has gone wrong.

image

Iterm2 colorscheme

I saw this colorscheme on trending and decided to give it a try and I've been really liking it so far!

I went ahead and made some pretty basic iterm2 colors locally so my terminal would match the theme. I wanted to contribute it back, but wanted to check if you were interested first, and if so, where the best place to put it would be.

I was thinking a contrib folder (or maybe a nightfly-contrib repo?) might make sense but didn't want to open a PR without getting your thoughts first.

Either way, thanks for sharing the theme!

Gigsign inline group

GitSignsChangeInline/AddInline/DeleteInline are enabled when word diff is set to true for git signs plugin
But sometimes I feel it is a bit distracting when I edit the code. All the code I changed will be highlighted as shown in above screenshot.

image

I mean it is great when you want to differ something, but not so great when you edit the code. Is it possible to change the background so it is less obvious?

Thanks!

Unused variables in TypeScript barely legible

I'm running into this issue

Screen Shot 2021-08-26 at 2 32 10 PM

Testing other languages seems to be fine in this case. I'm using coc.nvim. I am using tree-sitter and do not have any other specific syntax plugins for TypeScript. Could something be interfering?

barbar.nvim numbers have wrong colors

Hi,

Nightfly color scheme is my favorite one and I am working with that for over than year already and always had this kind of issue that number colors in barbar.nvim are wrong and have some rectangles around.

2021-09-13_17-24

When I switch to some another split and current one becomes inactive:
2021-09-13_17-25

Is there a way to fix it? I have the same problem on Linux and macOS.

IncSearch is a bit hard to read

Not sure if anyone mentioned it before, but I found the default IncSearch is a bit hard to read.

image

Also the link to LspReferenceText is IncSearch as well. So when my cursor park on a symbol, I am getting this:
image

Feel the contract is a bit too strong...

Is it possible to darker the guibg of IncSearch and link LspReferenceText to something less obvious? Thanks!

Support new treesitter captures

Treesitter was recently updated, which breaks a few colors in vim-nightfly-colors.

Notice of breaking change:
nvim-treesitter/nvim-treesitter#2293 (comment)

More information:
https://www.reddit.com/r/neovim/comments/19aratu/psa_nvimtreesitter_breaking_changes_on_highlight/

Screenshots

As an example, here are some screenshots of ruby code (this file) using nvim-treesitter pinned to 0.9.2 vs unpinned.

nvim-treesitter pinned to version="0.9.2":
nvim-treesitter-0 9 2

nvim-treesitter with no version pin (using current master):
nvim-treesitter-master

TODO labels are not readable

image

Hello! I'm finding my TODO labels in comments to be unreadable. Wondering if I have a terminal color problem or if this is broken for you as well?

Help Needed.

Hi, I am using nightfly theme in vim. It's really awesome, nice work. I'm facing an issue. When i open vim with sudo/root. it showing in default theme not in nightfly theme. can you help me in this?
Thank You.

How to customize (or fix) some elements

Hi,
I love the theme colors and contrast! Thank you!
I know beauty is in the eye of the beholder...

I find the window borders an separators a bit wide and taking up too much real estate, especially vertical windows, and Nvim-tree and toggle-term. For Telescope the border lines and title seem to lack just a bit of contrast. I was trying to get a 'flat' no border look for telescope as described here:

https://www.reddit.com/r/neovim/comments/se377t/telescopenvim_looks_neat/

see also: https://github.com/nvim-telescope/telescope.nvim/blob/39b12d84e86f5054e2ed98829b367598ae53ab41/plugin/telescope.lua#L27-L30

I tried for hours putting the snippets in the telescope.lua config, as well as trying to integrate directly into nightfly.
(I don't know that it would be benefical to include all the code here; Maybe this has become a feature request...!)

It does seem to me that there are a few Telescope items missing in the nightfly/init.lua config, notably:

  | highlight(0, "TelescopeSelectionCaret", { fg = p.red, bg = bg_visual })    
  | highlight(0, "TelescopePromptTitle", { fg = p.orange, bg = "NONE" })    
  | highlight(0, "TelescopeResultsTitle", { fg = p.orange, bg = "NONE" })    
  | highlight(0, "TelescopePreviewTitle", { fg = p.orange, bg = "NONE" })    
  | highlight(0, "TelescopePromptCounter", { fg = p.red, bg = "NONE" })    
  | highlight(0, "TelescopePreviewHyphen", { fg = p.red, bg = "NONE" })    

I was also fiddling around with:

highlight(0, "WinSeparator", { link = "VertSplit" })
highlight(0, "VertSplit", { fg = border, bg = "NONE" })

I have added a couple of screen shots to show the difference between nightfly and 'another' popular theme. Note its not the colors I am wanting to change but the border.

example flat no border for Telegram:
Screenshot from 2023-01-08 10-29-21

nightfly needs some more contrast with the titles and perhaps borders?
Screenshot from 2023-01-08 10-28-25

another theme showing Nvim-tree, buffer, and help window.
Screenshot from 2023-01-08 10-26-07

Note in nightfly the large separation between esp the vertical windows
Screenshot from 2023-01-08 10-23-52

Sorrry for not sending in a merge request. I'll probably eventually find the right way to do this, but in the mean time, it might also be (subject to personal opinion) an improvement to nightfly.

E684: list index out of range: 0

Thanks for making this! I did run into this error though.

Error detected while processing /home/chris/.config/nvim/plugged/vim-nightfly-guicolors/colors/nightfly.vim:
line   20:
E684: list index out of range: 0
E15: Invalid expression: nvim_list_uis()[0]['ext_termcolors'] && !&termguicolors

Error message when nvim starts

Hi there -

Just updated this plugin earlier today and now every time neovim launches I'm getting an error message (see screenshot below)

neovim version: NVIM v0.5.0-dev+1305-g21035cff9

CleanShot 2021-05-07 at 09 41 18

Thanks!

barbar.nvim colors are off

I was recently playing around with romgrk/barbar.nvim but discovered that the colors are way off with nightfly:

grafik

I played a bit the the Buffer* colors used by barbar.nvim based on the line number colors and got to something like this, which I think looks a bit better:

grafik

exec 'highlight TablineFill guibg=bg'
exec 'highlight BufferCurrent cterm=none guibg=' . s:dark_blue . ' guifg=' . s:white . ' gui=none'
exec 'highlight BufferCurrentSign cterm=none guibg=' . s:dark_blue . ' guifg=' . s:blue . ' gui=none'
exec 'highlight BufferVisible cterm=none guibg=' . s:dark_blue . ' guifg=' . s:steel_blue . ' gui=none'
exec 'highlight BufferVisibleSign cterm=none guibg=' . s:dark_blue . ' guifg=' . s:steel_blue . ' gui=none'
exec 'highlight BufferInactive cterm=none guibg=bg guifg=' . s:steel_blue . ' gui=none'
exec 'highlight BufferInactiveSign cterm=none guibg=bg guifg=' . s:steel_blue . ' gui=none'

I don't really like the way the "tab line" looks with the default Tabline colors, but I guess it would fit the theme better if they'd match airline and friends. In the case of barbar I find the Tabline colors too distracting and like how it blends in more like in my screenshot above.

I'd love to open a PR for this, but would like to ask for your feedback first, since this is obviously very subjective.

Otherwise thanks for making this. I'd love to send a small donation for a coffee/beer/whateveryoulike if you're interested!

The termguicolors option must be set

Hi there,

I love the theme, but can't seem to get it to work. I'm not sure what the problem is, I've tried following articles and suggestions from various sources. The issue is when I start vim, it prints out the following and the colour scheme does not change:

The termguicolors option must be set
Press ENTER or type command to continue

I'm using iTerm2 build 3.3.9 and vim version 8.1.1312. My iTerm report terminal type is set to xterm-256color. My OS is macOS Catalina 10.15.3.

My .vimrc: https://github.com/macguirerintoul/dotfiles/blob/master/.vimrc

" Plug setup
call plug#begin()
Plug 'sheerun/vim-polyglot'
Plug '/usr/local/opt/fzf'
Plug 'junegunn/fzf.vim'
Plug 'neoclide/coc.nvim', {'branch': 'release'}
Plug 'preservim/nerdtree'
Plug 'jiangmiao/auto-pairs'
Plug 'dense-analysis/ale'
Plug 'bluz71/vim-nightfly-guicolors'
call plug#end()

" syntax enable
set background=dark

" set Vim-specific sequences for RGB colors
set termguicolors
let &t_8f = "\[38;2;%lu;%lu;%lum"
let &t_8b = "\[48;2;%lu;%lu;%lum"

colorscheme nightfly

" Configure NERDTree
let NERDTreeShowHidden=1

" Configure ALE
let g:ale_fixers = {'javascript': ['eslint'], 'scss': ['stylelint']}
let g:ale_fix_on_save = 1
let g:ale_lint_on_text_changed = 'never'
let g:ale_lint_on_insert_leave = 0

" Ctrl + n toggles NERDTree
map <C-n> :NERDTreeToggle<CR>
" Ctrl + p opens fzf in git files mode
map <C-p> :GFiles<CR>
set tabstop=2 " set display width of tab
set softtabstop=1
set cursorline
set wildmenu
set showmatch
" turn hybrid line numbers on
:set number relativenumber
:set nu rnu

Any suggestions?

Missing License File

Hi, I know you have written in your headers that you're using MIT, but it would be best to add a LICENSE file at the root of the project directory too.

You can find a template for it here.

Lsp Saga Support

In the latest version of LSPSaga, the color of the popup is purple by default, it can be matched with the theme with this piece of code.

-- LSPSaga
highlight(0, "TitleString", { bg = bg, fg = black, bold = true })
highlight(0, "TitleSymbol", { bg = bg, fg = bg })
highlight(0, "TitleIcon", { bg = bg, fg = red })
highlight(0, "SagaBorder", { bg = bg })
highlight(0, "SagaExpand", { fg = red })
highlight(0, "SagaCollapse", { fg = red })
highlight(0, "SagaBeacon", { bg = purple })
highlight(0, "ActionPreviewNormal", { link = "SagaBorder" })
highlight(0, "ActionPreviewBorder", { link = "SagaBorder" })
highlight(0, "ActionPreviewTitle", { fg = black, bg = bg })
highlight(0, "CodeActionNormal", { link = "SagaBorder" })
highlight(0, "CodeActionBorder", { link = "SagaBorder" })
highlight(0, "CodeActionText", { fg = yellow })
highlight(0, "CodeActionConceal", { fg = green })
highlight(0, "FinderSelection", { fg = cyan_blue, bold = true })
highlight(0, "FinderFileName", { fg = white })
highlight(0, "FinderCount", { link = "Title" })
highlight(0, "FinderIcon", { fg = cyan_blue })
highlight(0, "FinderType", { fg = purple })
highlight(0, "FinderSpinnerTitle", { fg = purple, bold = true })
highlight(0, "FinderSpinner", { fg = purple, bold = true })
highlight(0, "FinderPreviewSearch", { link = "Search" })
highlight(0, "FinderVirtText", { fg = red })
highlight(0, "FinderNormal", { link = "SagaBorder" })
highlight(0, "FinderBorder", { link = "SagaBorder" })
highlight(0, "FinderPreviewBorder", { link = "SagaBorder" })
highlight(0, "DefinitionBorder", { link = "SagaBorder" })
highlight(0, "DefinitionNormal", { link = "SagaBorder" })
highlight(0, "DefinitionSearch", { link = "Search" })
highlight(0, "HoverNormal", { link = "SagaBorder" })
highlight(0, "HoverBorder", { link = "SagaBorder" })
highlight(0, "RenameBorder", { link = "SagaBorder" })
highlight(0, "RenameNormal", { fg = orange, bg = bg })
highlight(0, "RenameMatch", { link = "Search" })
highlight(0, "DiagnosticSource", { fg = "gray" })
highlight(0, "DiagnosticNormal", { link = "SagaBorder" })
highlight(0, "DiagnosticBorder", { link = "SagaBorder" })
highlight(0, "DiagnosticErrorBorder", { link = "SagaBorder" })
highlight(0, "DiagnosticWarnBorder", { link = "SagaBorder" })
highlight(0, "DiagnosticHintBorder", { link = "SagaBorder" })
highlight(0, "DiagnosticInfoBorder", { link = "SagaBorder" })
highlight(0, "DiagnosticPos", { fg = grey_blue })
highlight(0, "DiagnosticWord", { fg = blue })
highlight(0, "CallHierarchyNormal", { link = "SagaBorder" })
highlight(0, "CallHierarchyBorder", { link = "SagaBorder" })
highlight(0, "CallHierarchyIcon", { fg = purple })
highlight(0, "CallHierarchyTitle", { fg = red })
highlight(0, "LspSagaLightBulb", { link = "DiagnosticSignHint" })
highlight(0, "SagaShadow", { bg = blue })
highlight(0, "OutlineIndent", { fg = purple })
highlight(0, "OutlinePreviewBorder", { link = "SagaBorder" })
highlight(0, "OutlinePreviewNormal", { link = "SagaBorder" })
highlight(0, "TerminalBorder", { link = "SagaBorder" })
highlight(0, "TerminalNormal", { link = "SagaBorder" })

If you approve it, add it

more information on https://github.com/glepnir/lspsaga.nvim/blob/main/lua/lspsaga/highlight.lua

fzf.vim displaying wrong colors

Hey Dennis,

thanks for this fantastic theme. I really love the color composition! The only problem that I'm having is that my fzf plugin is not handling the colors correctly. Is this the case for you as well? ๐Ÿค”

Screenshot

Screenshot 2020-10-10 at 20 19 33

Replication:

  • iTerm2 with nightfly theme
  • nvim with nightfly theme
  • fzf.vim with the recommended customization for themes:
let g:fzf_colors =
\ { 'fg':      ['fg', 'Normal'],
  \ 'bg':      ['bg', 'Normal'],
  \ 'hl':      ['fg', 'Comment'],
  \ 'fg+':     ['fg', 'CursorLine', 'CursorColumn', 'Normal'],
  \ 'bg+':     ['bg', 'CursorLine', 'CursorColumn'],
  \ 'hl+':     ['fg', 'Statement'],
  \ 'info':    ['fg', 'PreProc'],
  \ 'border':  ['fg', 'Ignore'],
  \ 'prompt':  ['fg', 'Conditional'],
  \ 'pointer': ['fg', 'Exception'],
  \ 'marker':  ['fg', 'Keyword'],
  \ 'spinner': ['fg', 'Label'],
  \ 'header':  ['fg', 'Comment'] }

Sorry to bother you with this ๐Ÿ™ƒ

Nvim-navic highlight support

I've been using this colorscheme for months now and it's without a doubt the best I've ever used! Congrats.

Lately I started using the nvim-navic plugin and unfortunately this colorscheme doesn't support nvim-navic highlights yet, can you add it?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.