Giter Club home page Giter Club logo

edge's Introduction

Hi ๐Ÿ‘‹, I'm Sainnhe Park

An open source enthusiast from China ๐Ÿ‡จ๐Ÿ‡ณ

Sainnhe's GitHub stats

Top Langs

Loading

edge's People

Contributors

antistic avatar antoineco avatar aonodensetsu avatar danieltdt avatar daquexian avatar echasnovski avatar jdhao avatar jryom avatar markstory avatar mattbui avatar neanias avatar sainnhe avatar zweimach 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

edge's Issues

[Question] What are the differences between styles?

Hi,

nice color scheme, like both dark and light version.
Can you elaborate on differences between styles?

For dark version, I see some differences in background color, but for light version, I don't see anything that's different, at least not eye catching.

I noticed that hex values are a bit different, but can't really figure them out when comparing.

Maybe adding some explanation in readme what the differences are?

Thanks!

Loading edge and its options

This issue is related to sainnhe/gruvbox-material#60

Unless adding packadd! edge before colorscheme edge, the colorscheme becomes officially loaded: echo g:colors_name returns edge but there is no actual colour change.

This is in the doc and I guess there is nothing to do about it.

The issue I'd like to point out is that even with packadd! edge, the options do not get loaded automatically.
I use pack to manage plugin configurations. All options get stored in a file plugin/_pack.vim.
If I want italics I have to manually add let g:edge_enable_italic = 1 in the main vimrc.
Or, I need to type colorscheme edge manually.

Is there anything one can do about this?

Thank you!

Hi there,

zero issues here, I just want to thank you for making this colour scheme!

It looks so fantastic I love it.

Best regards.

Customising colours (help request - not an issue)

I really like this scheme - thanks for sharing!

I need a little more contrast, so I'm trying to make the white whiter and the background a little darker.

Are you able to advise on which shade I need to change in order to modify the background by any chance? I tried a find/replace on #262729 but didn't get anywhere.

zsh: thoughts about adding LS_COLORS and using them for completion

Hey,
First of, thanks a lot for that edge color scheme i love it!
Checking out that zsh part, I'm wondering if you ever thought about creating a custom LS_COLORS themed in the same way ?
I tried a bit (vivid is easier than dircolors), not totally here yet but zsh completion can use LS_COLORS with italics and so on.
Here's an example:
2021-11-12 16_44_16-OpenSSH SSH client

with ~/.zshrc containing an export LS_COLORS='.... and also:

# use LS_COLORS for completion, TODO: 'ma' is the selected item like:
# zstyle ':completion:*:default' list-colors ${(s.:.)LS_COLORS} "ma=48;5;153;1"
zstyle ':completion:*:default' list-colors ${(s.:.)LS_COLORS}

Have a good day!

Any plans to migrate theme to Lua?

Hi @sainnhe, thanks for the great theme! Using it everywhere (vim, neovim, vscode) and absolutely love it!

Are there any plans to migrate the theme to Lua?

More and more people are migrating to neovim with Lua configs these days. There are lots of Lua plugins that are developing more actively than their vimscript counterparts. What do you think?

Curly brace not colored in Template literal

Hey! I wanted to thank you for this amazing colorscheme, I love it. There is just one small issue that is a little bit annoying - in Javascript/Typescript files, the closing curly brace of a placeholder in template literal is not colored. Is there a way to fix this? Thanks!

image

E5113: Error while calling lua chunk: <path> Vim(return):E121: Undefined variable: palette

When setting colorscheme to edge. Neovim gives the following error:

E5113: Error while calling lua chunk: /home/rafa/.config/nvim/lua/main/colorscheme.lua:21: Vim(return):E121: 
Undefined variable: palette

It gives that error and it doesn't set the colorscheme to edge, just fells back to neovim builtin default colorscheme.

I have my config in Lua and this is how I'm setting the colorscheme: vim.cmd("colorscheme edge") And it works with all colorschemes I have, except now for edge. Last time I set my colorscheme to edge was all working fine.

2021-Apr-28

Change guibg not work

Operating system/version

Windows 10

GUI client/version

neovim 0.6

Feature matrix

\ 'bg0': ['#eeeeec', '231'],

Minimal vimrc that can reproduce this bug.

colorscheme edge

Steps to reproduce this bug using minimal vimrc

change bg0 color and restart neovim

Expected behavior

shoud use #eeeeec as guibg

Actual behavior

I changed the light style bg but still use #ffffff as guibg, the file is autoload/edge.vim

let palette = {
      \ 'black':      ['#dde2e7',   '253'],
      \ 'bg0':        ['#**eeeeec**',   '231'],
      \ 'bg1':        ['#eef1f4',   '255'],
      \ 'bg2':        ['#e8ebf0',   '254'],
      \ 'bg3':        ['#e8ebf0',   '253'],
      \ 'bg4':        ['#dde2e7',   '253'],
      \ 'bg_grey':    ['#bcc5cf',   '246'],
      \ 'bg_red':     ['#ef2929',   '167'],
      \ 'diff_red':   ['#cc0000',   '217'],
      \ 'bg_green':   ['#6b8e23',   '107'],
      \ 'diff_green': ['#4e9a06',   '150'],
      \ 'bg_blue':    ['#3465a4',   '68'],
      \ 'diff_blue':  ['#4169e1',   '153'],
      \ 'bg_purple':  ['#9400d3',   '134'],
      \ 'diff_yellow':['#fcaf3e',   '183'],
      \ 'fg':         ['#2e3436',   '240'],
      \ 'red':        ['#cc0000',   '167'],
      \ 'yellow':     ['#f57900',   '172'],
      \ 'green':      ['#608e23',   '107'],
      \ 'cyan':       ['#87ceeb',   '73'],
      \ 'blue':       ['#204a87',   '68'],
      \ 'purple':     ['#8a2be2',   '134'],
      \ 'grey':       ['#888a85',   '245'],
      \ 'grey_dim':   ['#babdb6',   '249'],
      \ 'none':       ['NONE',      'NONE']
      \ }

Too much italic for treesitter

Operating system/version

WSL2

Terminal emulator/version

wezterm

$TERM environment variable

xterm-256color

Tmux version

No response

Feature matrix

NVIM v0.6.0-dev+582-g87a053f12
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Compilation: /usr/bin/gcc-11 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DNVIM_TS_HAS_SET_MATCH_LIMIT -O2 -g -Og -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wmissing-prototypes -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fno-common -fdiagnostics-color=always -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -I/home/runner/work/neovim/neovim/build/config -I/home/runner/work/neovim/neovim/src -I/home/runner/work/neovim/neovim/.deps/usr/include -I/usr/include -I/home/runner/work/neovim/neovim/build/src/nvim/auto -I/home/runner/work/neovim/neovim/build/include
Compiled by runner@fv-az68-363

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

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/share/nvim"

Run :checkhealth for more info

Minimal vimrc that can reproduce this bug.

    require'nvim-treesitter.configs'.setup {
        highlight = {enable = true, disable = {'vim'}},
    }

Steps to reproduce this bug using minimal vimrc

Use the above config

Expected behavior

Like gruvbox-material, some texts are italic

Actual behavior

Almost everything is italic
image

Add theme for exa

It will be awsome if edge can be extended to exa, but I found it difficult to contribute, as exa accepts ANSI escape code instead of HEX. Is it possible to convert HEX to ANSI escape code and keep the color as similar as possible? I would love to learn from the experienced who have contributed to this repo.

Theme doesn't work in standard terminal or iTerm2

I'm trying to use this theme but it's not displaying quite correctly in either macOS terminal app or even iTerm2 (I prefer to use terminal.app but thought I'd check iTerm2 to see if the colour palette was better supported there).

Screenshot 2020-12-16 at 11 59 26

I raised this same issue with another theme I wanted to try out (which appeared visually a lot more broken) and turns out the issue is with the terminal theme being used (see details here).

Vim in terminal mode must be used with a Nord terminal emulator theme in order to work properly! Vim in terminal mode uses the 16 color codes provided by the terminal emulator. When used with another color theme than the one provided by one of Nord's terminal emulator ports, the colors in Vim won't use Nord's color palettes! This will result in different styles than those defined by Nord Vim and could make it appear that there is a problem with the Nord Vim theme while the actual problem are missing Nord colors.

So my question is now, what terminal theme would you recommend I use (either iTerm2 or Terminal.app, preferably the latter) to get your vim theme to work more accurately?

The color quite hard to read in command mode.

I tried to debug the key mapping with :nmap

image

"Edge colorscheme settings
let g:edge_style = 'neon'
let g:edge_enable_italic = 0
let g:edge_disable_italic_comment = 1
let g:edge_lightline_disable_bold = 1

I don't know if problem caused by my config or those are default color. Thanks in advance.

How do I disable the dimming?

this isn't actually a bug, it's just a configuration question

I have done the following steps before reporting this issue:

  • I have searched the existing issues
  • I have read the FAQ in the help doc

Operating system/version

Ubuntu 22.04

GUI client/version

neovim nightly

I'd like to disable this behavior, and keep the background color the same, always.

image

Here is my config:

" True Colors (tm)
set termguicolors

" Dark background is best background
set background=dark

""""""""""""""""""""""""""
" Theme: onedark
"        Plug 'joshdick/onedark.vim'
"
" colorscheme onedark


""""""""""""""""""""""""""
" Theme: Edge
"        Plug 'sainnhe/edge'
"
let g:edge_style = 'neon'
let g:edge_enable_italic = 1
let g:edge_better_performance = 1
let g:edge_dim_foreground = 0
" Don't dim inactive when we have the focus ring
let g:edge_dim_inactive_windows = 0
colorscheme edge

" No theme has 100% of what I want.
" Here is where I override the theme's settings
highlight! link CocExplorerFileDirectory Blue
" default neon bg: 2b2d3a
highlight! Normal guibg=#202230
highlight! Terminal guibg=#202230
highlight! EndOfBuffer guibg=#202230
" default neon bg: 2f3242
highlight! SignColumn guibg=#262836
" disable italic on Type
highlight! Type cterm=NONE gui=NONE guifg=#9988cc
" most themes link TS Groups to Basic AF colors
highlight! TSType guifg=#cc9988
highlight! TSTypeBuiltin guifg=#bbaadd
" Too much red
highlight! TSProperty guifg=#bbccff
" highlight! TSParameter guifg=#ff88cc
highlight! TSVariable guifg=#ff8888
highlight! TSVariableBuiltin guifg=#9999bb
highlight! TSTag guifg=#ff99cc
highlight! TSTagDelimiter guifg=#ffccff
highlight! TSURI guifg=#559999



highlight! CursorLine guibg=#262836
highlight! CursorColumn guibg=#262836

highlight! RedSign guibg=#262836
highlight! YellowSign guibg=#262836
highlight! GreenSign guibg=#262836
highlight! BlueSign guibg=#262836
highlight! PurpleSign guibg=#262836

" nvim-tree.lua
" :help nvim_tree_highlight
highlight NvimTreeIndentMarker guifg=#333333

" The divider lines
highlight! VertSplit guifg=#000000 guibg=NONE
highlight! HorSplit guifg=#000000 guibg=NONE

NvimTree background color is not transparent as before

I have done the following steps before reporting this issue:

  • I have searched the existing issues
  • I have read the FAQ in the help doc

Operating system/version

manjaro

Terminal emulator/version

kitty 0.26.5

$TERM environment variable

xterm-kitty

Tmux version

No response

Feature matrix

diffview: require("diffview.health").check()

Checking plugin dependencies

  • OK: plenary installed.
  • OK: nvim-web-devicons installed.

Checking external dependencies

  • OK: Git found.
  • OK: Git is up-to-date.

gitsigns: require("gitsigns.health").check()

  • OK: git version 2.38.1

hop: require("hop.health").check()

Ensuring keys are unique

  • OK: Keys are unique

Checking for deprecated features

  • OK: All good

nvim: health#nvim#check

Configuration

  • OK: no issues found

Performance

  • OK: Build type: Release

Remote Plugins

  • OK: Up to date

terminal

  • INFO: key_backspace (kbs) terminfo entry: key_backspace=\177
  • INFO: key_dc (kdch1) terminfo entry: key_dc=\E[3~
  • INFO: $COLORTERM='truecolor'

nvim-treesitter: require("nvim-treesitter.health").check()

Installation

  • OK: tree-sitter found 0.20.7 (parser generator, only needed for :TSInstallFromGrammar)
  • OK: node found v18.6.0 (only needed for :TSInstallFromGrammar)
  • OK: git executable found.
  • OK: cc executable found. Selected from { vim.NIL, "cc", "gcc", "clang", "cl", "zig" }
    Version: cc (GCC) 12.2.0
  • OK: Neovim was compiled with tree-sitter runtime ABI version 14 (required >=13). Parsers must be compatible with runtime ABI.

Parser/Features H L F I J

  • make โœ“ . โœ“ . โœ“
  • javascript โœ“ โœ“ โœ“ โœ“ โœ“
  • json โœ“ โœ“ โœ“ โœ“ .
  • rust โœ“ โœ“ โœ“ โœ“ โœ“
  • lua โœ“ โœ“ โœ“ โœ“ โœ“
  • html โœ“ โœ“ โœ“ โœ“ โœ“
  • dockerfile โœ“ . . . โœ“
  • css โœ“ . โœ“ โœ“ โœ“
  • python โœ“ โœ“ โœ“ โœ“ โœ“
  • tsx โœ“ โœ“ โœ“ โœ“ โœ“
  • typescript โœ“ โœ“ โœ“ โœ“ โœ“
  • bash โœ“ โœ“ โœ“ . โœ“
  • cmake โœ“ . โœ“ . .
  • yaml โœ“ โœ“ โœ“ โœ“ โœ“
  • http โœ“ . . . โœ“
  • go โœ“ โœ“ โœ“ โœ“ โœ“
  • rasi โœ“ โœ“ โœ“ โœ“ .

Legend: H[ighlight], L[ocals], F[olds], I[ndents], In[j]ections
+) multiple parsers found, only one will be used
x) errors found in the query, try to run :TSUpdate {lang}

provider: health#provider#check

Clipboard (optional)

  • OK: Clipboard tool found: xclip

Python 3 provider (optional)

  • INFO: Using: g:python3_host_prog = "/usr/bin/python3"
  • INFO: Executable: /usr/bin/python3
  • INFO: Python version: 3.10.8
  • INFO: pynvim version: 0.4.3
  • OK: Latest pynvim is installed.

Python virtualenv

  • OK: no $VIRTUAL_ENV

Ruby provider (optional)

  • INFO: Ruby: ruby 3.0.4p208 (2022-04-12 revision 3fa771dded) [x86_64-linux]
  • INFO: Host: /usr/bin/neovim-ruby-host
  • OK: Latest "neovim" gem is installed: 0.9.0

Node.js provider (optional)

  • INFO: Node.js: v18.6.0
  • INFO: Nvim node.js host: /home/dungtd10/.fnm/node-versions/v18.6.0/installation/lib/node_modules/neovim/bin/cli.js
  • OK: Latest "neovim" npm/yarn/pnpm package is installed: 4.10.1

Perl provider (optional)

  • WARNING: "Neovim::Ext" cpan module is not installed
    • ADVICE:
      • See :help |provider-perl| for more information.
      • You may disable this provider (and warning) by adding let g:loaded_perl_provider = 0 to your init.vim

telescope: require("telescope.health").check()

Checking for required plugins

  • OK: plenary installed.
  • OK: nvim-treesitter installed.

Checking external dependencies

  • OK: rg: found ripgrep 13.0.0
  • OK: fd: found fd 8.5.2

===== Installed extensions =====

Telescope Extension: hop

  • INFO: No healthcheck provided

telescope._extensions.repo: require("telescope._extensions.repo.health").check()

  • OK: Will use bat to preview non-markdown READMEs

  • OK: Will use bat to preview markdown READMEs

  • WARNING: Install glow for a better preview of markdown files

  • OK: locate: found locate
    mlocate 0.26
    Copyright (C) 2007 Red Hat, Inc. All rights reserved.
    This software is distributed under the GPL v.2.

    This program is provided with NO WARRANTY, to the extent permitted by law.

  • INFO: Repos found for :Telescope repo cached_list:
    /home/dungtd10/.cache/yay/apache-tools/.git, /home/dungtd10/.cache/yay/electron8-bin/.git...

  • OK: fd: found fd
    fd 8.5.2

  • INFO: Repos found for :Telescope repo list:
    ...

vim.lsp: require("vim.lsp.health").check()

  • INFO: LSP log level : WARN
  • INFO: Log path: /home/dungtd10/.local/state/nvim/lsp.log
  • INFO: Log size: 1682 KB

vim.treesitter: require("vim.treesitter.health").check()

  • INFO: Runtime ABI version : 14
  • OK: Loaded parser for bash: ABI version 14
  • OK: Loaded parser for cmake: ABI version 13
  • OK: Loaded parser for css: ABI version 13
  • OK: Loaded parser for dockerfile: ABI version 14
  • OK: Loaded parser for go: ABI version 14
  • OK: Loaded parser for html: ABI version 13
  • OK: Loaded parser for http: ABI version 13
  • OK: Loaded parser for javascript: ABI version 13
  • OK: Loaded parser for json: ABI version 13
  • OK: Loaded parser for lua: ABI version 13
  • OK: Loaded parser for make: ABI version 13
  • OK: Loaded parser for python: ABI version 14
  • OK: Loaded parser for rasi: ABI version 13
  • OK: Loaded parser for rust: ABI version 14
  • OK: Loaded parser for tsx: ABI version 13
  • OK: Loaded parser for typescript: ABI version 14
  • OK: Loaded parser for yaml: ABI version 13

Minimal vimrc that can reproduce this bug.

vim.g.edge_style = 'aura'
vim.g.edge_enable_italic = 1
vim.g.edge_dim_foreground = 1
vim.g.edge_disable_italic_comment = 1
vim.g.edge_better_performance = 1
vim.g.edge_disable_terminal_colors = 1
vim.g.edge_menu_selection_background = 'red'

vim.g.edge_colors_override = {
none = { 'NONE', 'NONE' },
black = { '#202023', '232' }, -- window border bg color
bg0 = { '#0a0a0a', '235' }, -- bg color
bg1 = { '#33353f', '235' }, -- status bar > empty bg color
bg2 = { '#202023', '236' }, -- auto complete window bg color
bg4 = { '#202023', '236' }, -- status bar > file name bg color
cyan = { '#5dbbc1', '100' }, -- ts bracket color
purple = { '#d38aea', '100' }, -- ts import color
bg_grey = { '#33353f', '100' }, -- lsp auto complete window scrollbar
bg3 = { '#ec0000', '236' },
green = { '#a0c980', '100' },
bg_green = { '#a0c980', '100' },
diff_green = { '#394634', '100' },
blue = { '#6cb6eb', '100' },
bg_blue = { '#6cb6eb', '100' },
diff_blue = { '#354157', '100' },
-- red = {},
-- bg_red = {},
-- diff_red = {},
-- yellow = {},
-- diff_yellow = {},
}

vim.cmd('colorscheme edge')

vim.cmd('hi BufferLineFill guibg=#33353f') -- buffer line empty space

vim.cmd('hi BufferLineBackground guibg=#070707 guifg=#33353f') -- bufferline not visible
vim.cmd('hi BufferLineSeparator guibg=#070707 guifg=#33353f') -- bufferline sep not visible

vim.cmd('hi BufferLineSeparatorSelected guifg=#33353f') -- bufferline sep selected
vim.cmd('hi BufferLineSeparatorVisible guifg=#33353f guibg=#070707') -- bufferline sep selected

vim.cmd('hi BufferLineBufferVisible guibg=#070707 guifg=#57e1ed') -- bufferline visible
vim.cmd('hi BufferLineBufferSelected guifg=#dfe4ed') -- bufferline selected

vim.cmd('hi BufferLineTab guibg=#202023 guifg=#33353f') -- buffer tab index indicator
vim.cmd('hi BufferLineTabSeparator guibg=#33353f guifg=#202023') -- buffer tab index indicator
vim.cmd('hi BufferLineTabSeparatorSelected guibg=#33353f guifg=#0a0a0a') -- buffer tab index indicator
vim.cmd('hi BufferLineTabSelected guifg=#6cb6eb') -- buffer tab index indicator

vim.cmd('hi PmenuSel guibg=#33353f') -- completion menu custom

Steps to reproduce this bug using minimal vimrc

1.Launch neovim using: nvim
2. Run nvim-tree using: :NvimTreeOpen

Expected behavior

NvimTree background color is transparent as usual:

image

  • I tried using commit: d48ab60 and everything works as expected:
    image

Actual behavior

image

A way to add all Edge colorschemes to Alacritty and select one

Hi there - thanks for the awesome Edge colorscheme. I've been using it quite happily since shortly after you first posted it on GH.

I've been experimenting with Alacritty for the past 2 days, and was thrilled to discover you've already created Edge schemes for it. In your README, you provide 4 separate schemes, and advise users to choose one and paste into their config.

Alacritty does support multiple themes, so as a slight optimization, if you wanted you could present a single pastable block containing all 4 schemes, and then advise users how they can easily switch between them. As an added bonus, if the Alacritty setting live_config_reload: true is active, then they can switch between color schemes with a one-line change, save the file, and see live previews.

The following is the self-documenting configuration I'm using with my Alacritty:

### Define your various colour-schemes here, and then choose one with
### the 'colors:' setting below.
schemes:  

  ### Edge (Light variant)
  edge_light:	  &edge_light
    primary:
      background: "0xFAFAFA"
      foreground: "0x4B505B"

    normal:
      black:	  "0x4B505B"
      red:	  "0xD05858"
      green:	  "0x608E32"
      yellow:	  "0xBE7E05"
      blue:	  "0x5079BE"
      magenta:	  "0xB05CCC"
      cyan:	  "0x3A8B84"
      white:	  "0xFAFAFA"

    bright:
      black:	  "0x4B505B"
      red:	  "0xD05858"
      green:	  "0x608E32"
      yellow:	  "0xBE7E05"
      blue:	  "0x5079BE"
      magenta:	  "0xB05CCC"
      cyan:	  "0x3A8B84"
      white:	  "0xFAFAFA"

  ### Edge (Dark Default variant)
  edge_dark_def:  &edge_dark_default
    primary:
      background: '0x1C1C1C'
      foreground: '0xD9D8D8'

    cursor:
     text:	  '0x1C1C1C'
     cursor:	  '0xE7E7E8'

    normal:
      black:	  '0x737371'
      red:	  '0xFB2608'
      green:      '0xA7E22E'
      yellow:	  '0x66D9EE'
      blue:	  '0x009DDC'
      magenta:	  '0xFF55FF'
      cyan:	  '0xFFD204'
      white:      '0xD9D8D8'

    bright:
      black:      '0x737171'
      red:        '0xFB2608'
      green:      '0xA7E22E'
      yellow:     '0x66D9EE'
      blue:       '0x009DDC'
      magenta:    '0xFF55FF'
      cyan:       '0xFFD204'
      white:      '0xFFFFFF'

  ### Edge (Dark Aura variant)
  edge_dark_aura:  &edge_dark_aura
    primary:
      background: "0x2B2D37"
      foreground: "0xC5CDD9"

    normal:
      black:	  "0x363A49"
      red:	  "0xEC7279"
      green:	  "0xA0C980"
      yellow:	  "0xDEB974"
      blue:	  "0x6CB6EB"
      magenta:	  "0xD38AEA"
      cyan:	  "0x5DBBC1"
      white:	  "0xC5CDD9"

    bright:
      black:	  "0x363A49"
      red:	  "0xEC7279"
      green:	  "0xA0C980"
      yellow:	  "0xDEB974"
      blue:	  "0x6CB6EB"
      magenta:	  "0xD38AEA"
      cyan:	  "0x5DBBC1"
      white:	  "0xC5CDD9"

  ### Edge (Dark Neon variant)
  edge_dark_neon:  &edge_dark_neon
    primary:
      background: "0x2B2D3A"
      foreground: "0xC5CDD9"

    normal:
      black:	  "0x363A4E"
      red:	  "0xEC7279"
      green:	  "0xA0C980"
      yellow:	  "0xDEB974"
      blue:	  "0x6CB6EB"
      magenta:	  "0xD38AEA"
      cyan:	  "0x5DBBC1"
      white:	  "0xC5CDD9"

    bright:
      black:	  "0x363A4E"
      red:	  "0xEC7279"
      green:	  "0xA0C980"
      yellow:	  "0xDEB974"
      blue:	  "0x6CB6EB"
      magenta:	  "0xD38AEA"
      cyan:	  "0x5DBBC1"
      white:	  "0xC5CDD9"

### Choose one of the & tags from the schemes listed above
colors: *edge_dark_neon

termguicolors option, wrong colors?

Hi,

I'm using vim 8.2 with the termguicolors option enabled and alacritty 0.4.2. I have installed your theme, but when I enable termguicolors, the colors are wrong.

This is vim with termguicolors enabled:
Screenshot_20200420_091316
And with termguicolors disabled:
Screenshot_20200420_091338
I think that the theme looks correctly if I have termguicolors disabled, but I'd like your opinion.

Is there something wrong with my vim setup?

Statement on maintenance

Due to some personal reasons gruvbox-material#23, I'll stop maintaining this project for a period of time(maybe about half a year).

This does not mean that this project has been abandoned, issues and PRs are welcome, I'll review them in the future.

If you're interested in this project and would like to become a maintainer, please contact me.

Thanks for your understanding :)

Error: Undefined variable: NAME E116: Invalid arguments for function edge#highlight

Operating system/version

Mac OS Monterrey version 12.4 (21F79)

GUI client/version

VIM - Vi IMproved 8.2

Feature matrix

vim --version
VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Jun 01 2022 14:23:13)
macOS version - x86_64
Included patches: 1-5050
Compiled by Homebrew
Huge version without GUI.  Features included (+) or not (-):
+acl               +file_in_path      +mouse_urxvt       -tag_any_white
+arabic            +find_in_path      +mouse_xterm       -tcl
+autocmd           +float             +multi_byte        +termguicolors
+autochdir         +folding           +multi_lang        +terminal
-autoservername    -footer            -mzscheme          +terminfo
-balloon_eval      +fork()            +netbeans_intg     +termresponse
+balloon_eval_term +gettext           +num64             +textobjects
-browse            -hangul_input      +packages          +textprop
++builtin_terms    +iconv             +path_extra        +timers
+byte_offset       +insert_expand     +perl              +title
+channel           +ipv6              +persistent_undo   -toolbar
+cindent           +job               +popupwin          +user_commands
-clientserver      +jumplist          +postscript        +vartabs
+clipboard         +keymap            +printer           +vertsplit
+cmdline_compl     +lambda            +profile           +vim9script
+cmdline_hist      +langmap           -python            +viminfo
+cmdline_info      +libcall           +python3           +virtualedit
+comments          +linebreak         +quickfix          +visual
+conceal           +lispindent        +reltime           +visualextra
+cryptv            +listcmds          +rightleft         +vreplace
+cscope            +localmap          +ruby              +wildignore
+cursorbind        +lua               +scrollbind        +wildmenu
+cursorshape       +menu              +signs             +windows
+dialog_con        +mksession         +smartindent       +writebackup
+diff              +modify_fname      -sodium            -X11
+digraphs          +mouse             -sound             -xfontset
-dnd               -mouseshape        +spell             -xim
-ebcdic            +mouse_dec         +startuptime       -xpm
+emacs_tags        -mouse_gpm         +statusline        -xsmp
+eval              -mouse_jsbterm     -sun_workshop      -xterm_clipboard
+ex_extra          +mouse_netterm     +syntax            -xterm_save
+extra_search      +mouse_sgr         +tag_binary
-farsi             -mouse_sysmouse    -tag_old_static
   system vimrc file: "$VIM/vimrc"
     user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
      user exrc file: "$HOME/.exrc"
       defaults file: "$VIMRUNTIME/defaults.vim"
  fall-back for $VIM: "/usr/local/share/vim"
Compilation: clang -c -I. -Iproto -DHAVE_CONFIG_H -DMACOS_X -DMACOS_X_DARWIN -g -O2 -D_REENTRANT -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: clang -L. -fstack-protector-strong -L/usr/local/lib -L/usr/local/opt/libyaml/lib -L/usr/local/opt/[email protected]/lib -L/usr/local/opt/readline/lib -L/usr/local/lib -o vim -lm -lncurses -liconv -lintl -framework AppKit -L/usr/local/opt/lua/lib -llua5.4 -mmacosx-version-min=12.0 -fstack-protector-strong -L/usr/local/lib -L/usr/local/Cellar/perl/5.34.0/lib/perl5/5.34.0/darwin-thread-multi-2level/CORE -lperl -L/usr/local/opt/[email protected]/Frameworks/Python.framework/Versions/3.10/lib/python3.10/config-3.10-darwin -lpython3.10 -framework CoreFoundation -lruby.3.1 -L/usr/local/Cellar/ruby/3.1.2/lib

Minimal vimrc that can reproduce this bug.

  1 set number
  2 syntax on
  3 set tabstop=4
  4 set expandtab
  5 "
  6 "search
  7 set incsearch
  8 set hlsearch
  9 ""folding
 10 set foldmethod=indent
 11 set foldnestmax=5
 12 set ruler laststatus=2 number title hlsearch
 13
 14 "vimcolors edge profile installed. ~/.vim/colors
 15 " for dark version
 16 set background=dark
 17 source ~/.vim/autoload/edge.vim
 18 colo edge
 19 if has('termguicolors')
 20 set termguicolors
 21 endif
 22 let g:edge_style = 'edge'
 23 let g:edge_better_performance = 1
 24 colorscheme edge
 25 let g:lightline.colorscheme = 'edge'

Steps to reproduce this bug using minimal vimrc

Whenever I try to use vim to open a file or create a new one, I get many undefined variable errors. The file will open afterward, and I can see the edge profile, but many errors have popped up before. See below:

[edge] Cleaned /Users/name/.vim/after/syntax Error detected while processing /Users/name/.vimrc[24]../Users/name/.vim/colors/edge.vim[11]..function edge#get_palette: line 91: E121: Undefined variable: palette E116: Invalid arguments for function extend(palette, palette_fg) "}}} line 121: E121: Undefined variable: palette E116: Invalid arguments for function extend(palette, a:colors_override) Error detected while processing /Users/name/.vimrc[24]../Users/name/.vim/colors/edge.vim: line 44: E121: Undefined variable: fg E116: Invalid arguments for function edge#highlight line 54: E121: Undefined variable: fg E116: Invalid arguments for function edge#highlight line 55: E121: Undefined variable: grey_dim E116: Invalid arguments for function edge#highlight line 56: E121: Undefined variable: bg0 E116: Invalid arguments for function edge#highlight line 57: E121: Undefined variable: bg0 E116: Invalid arguments for function edge#highlight line 58: E121: Undefined variable: none E116: Invalid arguments for function edge#highlight line 59: E121: Undefined variable: grey_dim E116: Invalid arguments for function edge#highlight line 61: E121: Undefined variable: none E116: Invalid arguments for function edge#highlight line 73: E121: Undefined variable: none E116: Invalid arguments for function edge#highlight line 76: E121: Undefined variable: grey_dim E116: Invalid arguments for function edge#highlight line 80: E121: Undefined variable: grey E116: Invalid arguments for function edge#highlight line 82: E121: Undefined variable: none E116: Invalid arguments for function edge#highlight line 83: E121: Undefined variable: none E116: Invalid arguments for function edge#highlight line 84: E121: Undefined variable: none E116: Invalid arguments for function edge#highlight line 85: E121: Undefined variable: bg0 E116: Invalid arguments for function edge#highlight line 86: E121: Undefined variable: green E116: Invalid arguments for function edge#highlight line 87: E121: Undefined variable: red E116: Invalid arguments for function edge#highlight line 88: E121: Undefined variable: yellow E116: Invalid arguments for function edge#highlight line 89: E121: Undefined variable: fg E116: Invalid arguments for function edge#highlight line 90: E121: Undefined variable: blue E116: Invalid arguments for function edge#highlight line 91: E121: Undefined variable: none E116: Invalid arguments for function edge#highlight line 92: E121: Undefined variable: bg4 E116: Invalid arguments for function edge#highlight line 93: E121: Undefined variable: bg4 E116: Invalid arguments for function edge#highlight line 94: E121: Undefined variable: bg4 E116: Invalid arguments for function edge#highlight line 95: E121: Undefined variable: fg E116: Invalid arguments for function edge#highlight line 96: E121: Undefined variable: none E116: Invalid arguments for function edge#highlight line 98: E121: Undefined variable: bg0 E116: Invalid arguments for function edge#highlight line 105: E121: Undefined variable: none E116: Invalid arguments for function edge#highlight line 106: E121: Undefined variable: fg E116: Invalid arguments for function edge#highlight line 107: E121: Undefined variable: grey E116: Invalid arguments for function edge#highlight line 108: E121: Undefined variable: yellow E116: Invalid arguments for function edge#highlight line 110: E121: Undefined variable: none E116: Invalid arguments for function edge#highlight line 129: E121: Undefined variable: fg E116: Invalid arguments for function edge#highlight line 137: E121: Undefined variable: black E116: Invalid arguments for function edge#highlight line 138: E121: Undefined variable: none E116: Invalid arguments for function edge#highlight line 139: E121: Undefined variable: none E116: Invalid arguments for function edge#highlight line 140: E121: Undefined variable: purple E116: Invalid arguments for function edge#highlight line 141: E121: Undefined variable: yellow E116: Invalid arguments for function edge#highlight line 142: E121: Undefined variable: bg0 E116: Invalid arguments for function edge#highlight line 143: E121: Undefined variable: bg0 E116: Invalid arguments for function edge#highlight line 144: E121: Undefined variable: bg0 E116: Invalid arguments for function edge#highlight line 208: E121: Undefined variable: red E116: Invalid arguments for function edge#highlight line 214: E121: Undefined variable: purple E116: Invalid arguments for function edge#highlight line 215: E121: Undefined variable: purple E116: Invalid arguments for function edge#highlight line 216: E121: Undefined variable: purple E116: Invalid arguments for function edge#highlight line 217: E121: Undefined variable: purple E116: Invalid arguments for function edge#highlight line 218: E121: Undefined variable: purple E116: Invalid arguments for function edge#highlight line 219: E121: Undefined variable: purple E116: Invalid arguments for function edge#highlight line 220: E121: Undefined variable: purple E116: Invalid arguments for function edge#highlight line 221: E121: Undefined variable: purple E116: Invalid arguments for function edge#highlight line 222: E121: Undefined variable: purple E116: Invalid arguments for function edge#highlight line 223: E121: Undefined variable: purple E116: Invalid arguments for function edge#highlight line 224: E121: Undefined variable: yellow E116: Invalid arguments for function edge#highlight line 225: E121: Undefined variable: red E116: Invalid arguments for function edge#highlight line 226: E121: Undefined variable: yellow E116: Invalid arguments for function edge#highlight line 227: E121: Undefined variable: yellow E116: Invalid arguments for function edge#highlight line 228: E121: Undefined variable: yellow E116: Invalid arguments for function edge#highlight line 229: E121: Undefined variable: green E116: Invalid arguments for function edge#highlight line 230: E121: Undefined variable: green E116: Invalid arguments for function edge#highlight line 231: E121: Undefined variable: green E116: Invalid arguments for function edge#highlight line 232: E121: Undefined variable: green E116: Invalid arguments for function edge#highlight line 233: E121: Undefined variable: green E116: Invalid arguments for function edge#highlight line 234: E121: Undefined variable: blue E116: Invalid arguments for function edge#highlight line 235: E121: Undefined variable: purple E116: Invalid arguments for function edge#highlight line 236: E121: Undefined variable: purple E116: Invalid arguments for function edge#highlight line 237: E121: Undefined variable: yellow E116: Invalid arguments for function edge#highlight line 238: E121: Undefined variable: fg E116: Invalid arguments for function edge#highlight line 244: E121: Undefined variable: grey E116: Invalid arguments for function edge#highlight line 248: E121: Undefined variable: grey E116: Invalid arguments for function edge#highlight line 249: E121: Undefined variable: none E116: Invalid arguments for function edge#highlight line 252: E121: Undefined variable: fg E116: Invalid arguments for function edge#highlight line 253: E121: Undefined variable: grey E116: Invalid arguments for function edge#highlight line 254: E121: Undefined variable: red E116: Invalid arguments for function edge#highlight line 255: E121: Undefined variable: yellow E116: Invalid arguments for function edge#highlight line 256: E121: Undefined variable: green E116: Invalid arguments for function edge#highlight line 257: E121: Undefined variable: cyan E116: Invalid arguments for function edge#highlight line 258: E121: Undefined variable: blue E116: Invalid arguments for function edge#highlight line 259: E121: Undefined variable: purple E116: Invalid arguments for function edge#highlight line 268: E121: Undefined variable: red E116: Invalid arguments for function edge#highlight line 275: E121: Undefined variable: red E116: Invalid arguments for function edge#highlight line 276: E121: Undefined variable: yellow E116: Invalid arguments for function edge#highlight line 277: E121: Undefined variable: green E116: Invalid arguments for function edge#highlight line 278: E121: Undefined variable: cyan E116: Invalid arguments for function edge#highlight line 279: E121: Undefined variable: blue E116: Invalid arguments for function edge#highlight line 280: E121: Undefined variable: purple E116: Invalid arguments for function edge#highlight line 287: E121: Undefined variable: none E116: Invalid arguments for function edge#highlight line 314: E121: Undefined variable: red E116: Invalid arguments for function edge#highlight line 315: E121: Undefined variable: yellow E116: Invalid arguments for function edge#highlight line 316: E121: Undefined variable: blue E116: Invalid arguments for function edge#highlight line 317: E121: Undefined variable: green E116: Invalid arguments for function edge#highlight line 321: E121: Undefined variable: none E116: Invalid arguments for function edge#highlight line 330: E121: Undefined variable: bg0 line 368: E121: Undefined variable: none E116: Invalid arguments for function edge#highlight line 369: E121: Undefined variable: none E116: Invalid arguments for function edge#highlight line 370: E121: Undefined variable: none E116: Invalid arguments for function edge#highlight line 371: E121: Undefined variable: bg0 E116: Invalid arguments for function edge#highlight line 372: E121: Undefined variable: bg0 E116: Invalid arguments for function edge#highlight line 373: E121: Undefined variable: bg0 E116: Invalid arguments for function edge#highlight line 425: E121: Undefined variable: none E116: Invalid arguments for function edge#highlight line 426: E121: Undefined variable: green E116: Invalid arguments for function edge#highlight line 539: E121: Undefined variable: green E116: Invalid arguments for function edge#highlight line 540: E121: Undefined variable: green E116: Invalid arguments for function edge#highlight line 541: E121: Undefined variable: blue E116: Invalid arguments for function edge#highlight line 542: E121: Undefined variable: purple E116: Invalid arguments for function edge#highlight line 543: E121: Undefined variable: red E116: Invalid arguments for function edge#highlight line 544: E121: Undefined variable: yellow E116: Invalid arguments for function edge#highlight line 545: E121: Undefined variable: cyan E116: Invalid arguments for function edge#highlight line 546: E121: Undefined variable: bg0 E116: Invalid arguments for function edge#highlight line 547: E121: Undefined variable: bg0 E116: Invalid arguments for function edge#highlight line 548: E121: Undefined variable: fg E116: Invalid arguments for function edge#highlight line 549: E121: Undefined variable: fg E116: Invalid arguments for function edge#highlight line 550: E121: Undefined variable: fg E116: Invalid arguments for function edge#highlight line 551: E121: Undefined variable: fg E116: Invalid arguments for function edge#highlight line 552: E121: Undefined variable: fg E116: Invalid arguments for function edge#highlight line 553: E121: Undefined variable: purple E116: Invalid arguments for function edge#highlight line 554: E121: Undefined variable: bg0 E116: Invalid arguments for function edge#highlight line 555: E121: Undefined variable: bg0 E116: Invalid arguments for function edge#highlight line 568: E121: Undefined variable: red E116: Invalid arguments for function edge#highlight line 569: E121: Undefined variable: none E116: Invalid arguments for function edge#highlight line 570: E121: Undefined variable: purple E116: Invalid arguments for function edge#highlight line 571: E121: Undefined variable: fg E116: Invalid arguments for function edge#highlight line 572: E121: Undefined variable: fg E116: Invalid arguments for function edge#highlight line 573: E121: Undefined variable: red E116: Invalid arguments for function edge#highlight line 574: E121: Undefined variable: yellow E116: Invalid arguments for function edge#highlight line 575: E121: Undefined variable: cyan E116: Invalid arguments for function edge#highlight line 576: E121: Undefined variable: blue E116: Invalid arguments for function edge#highlight line 577: E121: Undefined variable: purple E116: Invalid arguments for function edge#highlight line 578: E121: Undefined variable: green E116: Invalid arguments for function edge#highlight line 579: E121: Undefined variable: red E116: Invalid arguments for function edge#highlight line 619: E121: Undefined variable: green E116: Invalid arguments for function edge#highlight line 620: E121: Undefined variable: green E116: Invalid arguments for function edge#highlight line 621: E121: Undefined variable: green E116: Invalid arguments for function edge#highlight line 622: E121: Undefined variable: purple E116: Invalid arguments for function edge#highlight line 623: E121: Undefined variable: fg E116: Invalid arguments for function edge#highlight line 627: E121: Undefined variable: green E116: Invalid arguments for function edge#highlight line 628: E121: Undefined variable: grey E116: Invalid arguments for function edge#highlight line 629: E121: Undefined variable: grey E116: Invalid arguments for function edge#highlight line 630: E121: Undefined variable: blue E116: Invalid arguments for function edge#highlight line 631: E121: Undefined variable: bg1 E116: Invalid arguments for function edge#highlight line 632: E121: Undefined variable: grey E116: Invalid arguments for function edge#highlight line 661: E121: Undefined variable: none E116: Invalid arguments for function edge#highlight line 662: E121: Undefined variable: none E116: Invalid arguments for function edge#highlight line 663: E121: Undefined variable: none E116: Invalid arguments for function edge#highlight line 670: E121: Undefined variable: bg_purple E116: Invalid arguments for function edge#highlight line 683: E121: Undefined variable: blue E116: Invalid arguments for function edge#highlight line 700: E121: Undefined variable: grey_dim line 701: E121: Undefined variable: grey_dim line 737: E121: Undefined variable: grey_dim line 738: E121: Undefined variable: grey_dim line 741: E121: Undefined variable: green E116: Invalid arguments for function edge#highlight line 742: E121: Undefined variable: blue E116: Invalid arguments for function edge#highlight [edge] Generated /Users/name/.vim/after/syntax Error detected while processing /Users/name/.vimrc: line 25: E121: Undefined variable: g:lightline Press ENTER or type command to continue

Expected behavior

Open or create any file using vim with the edge profile without errors.

Actual behavior

When opening or creating any file using vim and the edge profile. Many errors appear like the one below before I can start using vim.

Undefined variable: grey
E116: Invalid arguments for function edge#highlight

Darkening bground

I tried something like this:
l:palette.bg0 = '#1a1c24'
in s:edge_custom() but it does not work...
Great theme btw, I just would love to make it pop more with 10-20% darker bacground

Signcolumn

My signcolumn doesn't look correct. Is there a way to fix this? Thanks!

image

Edge doesn't appropriate with vim stable 8.2.2824

Operating system/version

Windows 11

GUI client/version

Gvim

Feature matrix

VIM - Vi IMproved 8.2 (2019 Dec 12, compiled May  2 2021 19:00:02)
MS-Windows 32-bit GUI version with OLE support
Included patches: 1-2824
Compiled by mool@tororo
Huge version with GUI.  Features included (+) or not (-):
+acl                +cmdline_hist       +eval               +jumplist           +multi_byte_ime/dyn +python3/dyn        -tag_old_static     +virtualedit
+arabic             +cmdline_info       +ex_extra           +keymap             +multi_lang         +quickfix           -tag_any_white      +visual
+autocmd            +comments           +extra_search       +lambda             +mzscheme/dyn       +reltime            +tcl/dyn            +visualextra
+autochdir          +conceal            -farsi              +langmap            +netbeans_intg      +rightleft          -termguicolors      +viminfo
+autoservername     +cryptv             +file_in_path       +libcall            +num64              +ruby/dyn           +terminal           +vreplace
+balloon_eval       +cscope             +find_in_path       +linebreak          +ole                +scrollbind         -termresponse       -vtp
-balloon_eval_term  +cursorbind         +float              +lispindent         +packages           +signs              +textobjects        +wildignore
+browse             +cursorshape        +folding            +listcmds           +path_extra         +smartindent        +textprop           +wildmenu
++builtin_terms     +dialog_con_gui     -footer             +localmap           +perl/dyn           +sound              -tgetent            +windows
+byte_offset        +diff               +gettext/dyn        +lua/dyn            +persistent_undo    +spell              +timers             +writebackup
+channel            +digraphs           -hangul_input       +menu               +popupwin           +startuptime        +title              -xfontset
+cindent            +directx            +iconv/dyn          +mksession          -postscript         +statusline         +toolbar            -xim
+clientserver       -dnd                +insert_expand      +modify_fname       +printer            -sun_workshop       +user_commands      +xpm_w32
+clipboard          -ebcdic             +ipv6               +mouse              +profile            +syntax             +vartabs            -xterm_save
+cmdline_compl      +emacs_tags         +job                +mouseshape         +python/dyn         +tag_binary         +vertsplit          
   system vimrc file: "$VIM\vimrc"
     user vimrc file: "$HOME\_vimrc"
 2nd user vimrc file: "$HOME\vimfiles\vimrc"
 3rd user vimrc file: "$VIM\_vimrc"
      user exrc file: "$HOME\_exrc"
  2nd user exrc file: "$VIM\_exrc"
  system gvimrc file: "$VIM\gvimrc"
    user gvimrc file: "$HOME\_gvimrc"
2nd user gvimrc file: "$HOME\vimfiles\gvimrc"
3rd user gvimrc file: "$VIM\_gvimrc"
       defaults file: "$VIMRUNTIME\defaults.vim"
    system menu file: "$VIMRUNTIME\menu.vim"
Compilation: cl -c /W3 /GF /nologo  -I. -Iproto -DHAVE_PATHDEF -DWIN32  -DFEAT_CSCOPE -DFEAT_TERMINAL -DFEAT_SOUND -DFEAT_NETBEANS_INTG -DFEAT_JOB_CHANNEL -DFEAT_IPV6   -DFEAT_XPM_W32   -DWINVER=0x0501 -D_WIN32_WINNT=0x0501 /source-charset:utf-8 /MP -DHAVE_STDINT_H /Ox /GL -DNDEBUG /arch:IA32 /Zl /MT /D_CRT_SECURE_NO_DEPRECATE /D_CRT_NONSTDC_NO_DEPRECATE -DFEAT_OLE -DFEAT_MBYTE_IME -DDYNAMIC_IME -DFEAT_GUI_MSWIN -DFEAT_DIRECTX -DDYNAMIC_DIRECTX -DFEAT_DIRECTX_COLOR_EMOJI -DDYNAMIC_ICONV -DDYNAMIC_GETTEXT -DFEAT_TCL -DDYNAMIC_TCL -DDYNAMIC_TCL_DLL=\"tcl86t.dll\" -DDYNAMIC_TCL_VER=\"8.6\" -DFEAT_LUA -DDYNAMIC_LUA -DDYNAMIC_LUA_DLL=\"lua53.dll\" -DFEAT_PYTHON -DDYNAMIC_PYTHON -DDYNAMIC_PYTHON_DLL=\"python27.dll\" -DFEAT_PYTHON3 -DDYNAMIC_PYTHON3 -DDYNAMIC_PYTHON3_DLL=\"python36.dll\" -DFEAT_MZSCHEME -I "E:\Racket\include" -DMZ_PRECISE_GC -DDYNAMIC_MZSCHEME -DDYNAMIC_MZSCH_DLL=\"libracket3m_a36fs8.dll\" -DDYNAMIC_MZGC_DLL=\"libracket3m_a36fs8.dll\" -DFEAT_PERL -DPERL_IMPLICIT_CONTEXT -DPERL_IMPLICIT_SYS -DDYNAMIC_PERL -DDYNAMIC_PERL_DLL=\"perl524.dll\" -DFEAT_RUBY -DDYNAMIC_RUBY -DDYNAMIC_RUBY_DLL=\"msvcrt-ruby240.dll\" -DRUBY_VERSION=24 -DFEAT_HUGE /Fd.\ObjGXOULYHTRZi386/ /Zi
Linking: link  /nologo /opt:ref /LTCG:STATUS oldnames.lib kernel32.lib advapi32.lib shell32.lib gdi32.lib  comdlg32.lib ole32.lib netapi32.lib uuid.lib /machine:i386 gdi32.lib version.lib   winspool.lib comctl32.lib advapi32.lib shell32.lib netapi32.lib  /machine:i386  libcmt.lib oleaut32.lib user32.lib  /nodefaultlib:lua53.lib  /STACK:8388608  /nodefaultlib:python27.lib /nodefaultlib:python36.lib   "E:\ActiveTcl\lib\tclstub86.lib" winmm.lib WSock32.lib Ws2_32.lib xpm\x86\lib-vc14\libXpm.lib /PDB:gvim.pdb -debug

Minimal vimrc that can reproduce this bug.

call plug#begin('~/vimfiles/plugged')
Plug 'https://github.com/sainnhe/edge.git', {'as': 'edge'}
call plug#end()
set termguicolors
colorscheme edge

Steps to reproduce this bug using minimal vimrc

1.Launch vim with minimal vimrc and the background is white like below

image

Expected behavior

It will shows edge theme

Actual behavior

white background

let g:edge_better_performance = 1 cause errors on Windows

Steps to reproduce. Use the following minimal config:

set runtimepath+=C:\Users\Administrator\AppData\Local\nvim-data\plugged\edge
let g:edge_enable_italic = 1
let g:edge_better_performance = 1
colorscheme edge

Open nvim with nvim -u minimal.vim. I am seeing a lot of errors.

Judging from the errors. It seems that edge try to create directory C:\Users\Administrator\AppData\Local\nvim-data\plugged\edge\colors\edge.vim\after\ftplugin. In fact it should create directory: C:\Users\Administrator\AppData\Local\nvim-data\plugged\edge\after\ftplugin.

Support color for fzf.vim

Before I use edge as default color for gui, I used to dracula theme.
Dracula:
image

Edge:
image

I can't find out what happen with the preview box, It disappear.

when LSP loaded, highlight become weird since neovim0.9

I have done the following steps before reporting this issue:

  • I have searched the existing issues
  • I have read the FAQ in the help doc

Operating system/version

macOS Ventura Version 13.3

Terminal emulator/version

iTerm2 3.4.19

$TERM environment variable

xterm-256color

Tmux version

No response

Feature matrix


==============================================================================
lazy: require("lazy.health").check()

lazy.nvim ~
- OK Git installed
- OK no existing packages found by other package managers
- OK packer_compiled.lua not found

==============================================================================
man: require("man.health").check()

- OK plugin/man.vim not in $VIMRUNTIME
- OK autoload/man.vim not in $VIMRUNTIME

==============================================================================
mason: require("mason.health").check()

mason.nvim report ~
- OK neovim version >= 0.7.0
- OK Registry `require("mason-registry.index")` is installed.
- OK Registry `github.com/mason-org/mason-registry version: 2023-04-09-woeful-court` is installed.
- OK **unzip**: `UnZip 6.00 of 20 April 2009, by Info-ZIP.  Maintained by C. Spieler.  Send`
- OK **Go**: `go version go1.20.3 darwin/arm64`
- OK **cargo**: `cargo 1.70.0-nightly (145219a9f 2023-03-27)`
- WARNING **luarocks**: not available
- OK **Ruby**: `ruby 3.2.2 (2023-03-30 revision e51014f9c0) [arm64-darwin22]`
- OK **RubyGem**: `3.4.9`
- WARNING **Composer**: not available
- WARNING **PHP**: not available
- OK **npm**: `9.5.1`
- OK **node**: `v19.8.1`
- OK **python3**: `Python 3.11.2`
- OK **pip3**: `pip 23.0.1 from /opt/homebrew/lib/python3.11/site-packages/pip (python 3.11)`
- OK **javac**: `javac 18.0.2.1`
- OK **java**: `openjdk version "18.0.2.1" 2022-08-18`
- WARNING **julia**: not available
- OK **wget**: `GNU Wget 1.21.3 built on darwin22.1.0.`
- OK **curl**: `curl 7.87.0 (x86_64-apple-darwin22.0) libcurl/7.87.0 (SecureTransport) LibreSSL/3.3.6 zlib/1.2.11 nghttp2/1.51.0`
- OK **gzip**: `Apple gzip 403.100.6`
- OK **tar**: `bsdtar 3.5.3 - libarchive 3.5.3 zlib/1.2.11 liblzma/5.0.5 bz2lib/1.0.8 `
- WARNING **pwsh**: not available
- OK **bash**: `GNU bash, version 3.2.57(1)-release (arm64-apple-darwin22)`
- OK **sh**: `Ok`
- OK GitHub API rate limit. Used: 1. Remaining: 4999. Limit: 5000. Reset: Mon Apr 10 10:19:10 2023.

==============================================================================
nvim: require("nvim.health").check()

Configuration ~
- OK no issues found

Runtime ~
- OK $VIMRUNTIME: /usr/local/share/nvim/runtime

Performance ~
- OK Build type: Release

Remote Plugins ~
- OK Up to date

terminal ~
- key_backspace (kbs) terminfo entry: `key_backspace=^H`
- key_dc (kdch1) terminfo entry: `key_dc=\E[3~`
- $TERM_PROGRAM="iTerm.app"
- $COLORTERM="truecolor"

==============================================================================
nvim-treesitter: require("nvim-treesitter.health").check()

Installation ~
- OK `tree-sitter` found 0.20.8 (parser generator, only needed for :TSInstallFromGrammar)
- OK `node` found v19.8.1 (only needed for :TSInstallFromGrammar)
- OK `git` executable found.
- OK `cc` executable found. Selected from { vim.NIL, "cc", "gcc", "clang", "cl", "zig" }
  Version: Apple clang version 14.0.3 (clang-1403.0.22.14.1)
- OK Neovim was compiled with tree-sitter runtime ABI version 14 (required >=13). Parsers must be compatible with runtime ABI.

OS Info:
{
  machine = "arm64",
  release = "22.4.0",
  sysname = "Darwin",
  version = "Darwin Kernel Version 22.4.0: Mon Mar  6 21:00:41 PST 2023; root:xnu-8796.101.5~3/RELEASE_ARM64_T8103"
} ~

Parser/Features         H L F I J
  - bash                โœ“ โœ“ โœ“ . โœ“
  - bibtex              โœ“ . โœ“ โœ“ .
  - c                   โœ“ โœ“ โœ“ โœ“ โœ“
  - cmake               โœ“ . โœ“ . .
  - comment             โœ“ . . . .
  - cpp                 โœ“ โœ“ โœ“ โœ“ โœ“
  - diff                โœ“ . . . .
  - dockerfile          โœ“ . . . โœ“
  - fish                โœ“ โœ“ โœ“ โœ“ โœ“
  - git_rebase          โœ“ . . . โœ“
  - gitattributes       โœ“ . . . โœ“
  - go                  โœ“ โœ“ โœ“ โœ“ โœ“
  - gomod               โœ“ . . . โœ“
  - gowork              โœ“ . . . โœ“
  - haskell             โœ“ . โœ“ . โœ“
  - json                โœ“ โœ“ โœ“ โœ“ .
  - json5               โœ“ . . . โœ“
  - latex               โœ“ . โœ“ . โœ“
  - llvm                โœ“ . . . .
  - lua                 โœ“ โœ“ โœ“ โœ“ โœ“
  - make                โœ“ . โœ“ . โœ“
  - markdown            โœ“ . โœ“ . โœ“
  - markdown_inline     โœ“ . . . โœ“
  - ninja               โœ“ . โœ“ โœ“ .
  - perl                โœ“ . โœ“ . โœ“
  - proto               โœ“ . โœ“ . .
  - python              โœ“ โœ“ โœ“ โœ“ โœ“
  - query               โœ“ โœ“ โœ“ โœ“ โœ“
  - rst                 โœ“ โœ“ . . โœ“
  - rust                โœ“ โœ“ โœ“ โœ“ โœ“
  - sql                 โœ“ . . . โœ“
  - toml                โœ“ โœ“ โœ“ โœ“ โœ“
  - vim                 โœ“ โœ“ โœ“ . โœ“
  - vimdoc              โœ“ . . . โœ“
  - yaml                โœ“ โœ“ โœ“ โœ“ โœ“

  Legend: H[ighlight], L[ocals], F[olds], I[ndents], In[j]ections
         +) multiple parsers found, only one will be used
         x) errors found in the query, try to run :TSUpdate {lang} ~

==============================================================================
provider: health#provider#check

Clipboard (optional) ~
- OK Clipboard tool found: pbcopy

Python 3 provider (optional) ~
- `g:python3_host_prog` is not set.  Searching for python3.9 in the environment.
- Multiple python3.9 executables found.  Set `g:python3_host_prog` to avoid surprises.
- Executable: /opt/homebrew/bin/python3.9
- Other python executable: /usr/local/bin/python3.9
- Python version: 3.9.16
- pynvim version: 0.4.3
- OK Latest pynvim is installed.

Python virtualenv ~
- OK no $VIRTUAL_ENV

Ruby provider (optional) ~
- Ruby: ruby 3.2.2 (2023-03-30 revision e51014f9c0) [arm64-darwin22]
- WARNING `neovim-ruby-host` not found.
  - ADVICE:
    - Run `gem install neovim` to ensure the neovim RubyGem is installed.
    - Run `gem environment` to ensure the gem bin directory is in $PATH.
    - If you are using rvm/rbenv/chruby, try "rehashing".
    - See :help |g:ruby_host_prog| for non-standard gem installations.
    - You may disable this provider (and warning) by adding `let g:loaded_ruby_provider = 0` to your init.vim

Node.js provider (optional) ~
- Node.js: v19.8.1
- Nvim node.js host: /opt/homebrew/lib/node_modules/neovim/bin/cli.js
- OK Latest "neovim" npm/yarn/pnpm package is installed: 4.10.1

Perl provider (optional) ~
- WARNING "Neovim::Ext" cpan module is not installed
  - ADVICE:
    - See :help |provider-perl| for more information.
    - You may disable this provider (and warning) by adding `let g:loaded_perl_provider = 0` to your init.vim

==============================================================================
telescope: require("telescope.health").check()

Checking for required plugins ~
- OK plenary installed.
- OK nvim-treesitter installed.

Checking external dependencies ~
- OK rg: found ripgrep 13.0.0
- OK fd: found fd 8.7.0

===== Installed extensions ===== ~

==============================================================================
vim.lsp: require("vim.lsp.health").check()

- LSP log level : WARN
- Log path: /Users/mrzleo/.local/state/nvim/lsp.log
- Log size: 16275 KB

vim.lsp: Active Clients ~
- No active clients

==============================================================================
vim.treesitter: require("vim.treesitter.health").check()

- Nvim runtime ABI version: 14
- OK Parser: bash       ABI: 14, path: /Users/mrzleo/.local/share/nvim/lazy/nvim-treesitter/parser/bash.so
- OK Parser: bibtex     ABI: 13, path: /Users/mrzleo/.local/share/nvim/lazy/nvim-treesitter/parser/bibtex.so
- OK Parser: c          ABI: 13, path: /Users/mrzleo/.local/share/nvim/lazy/nvim-treesitter/parser/c.so
- OK Parser: cmake      ABI: 14, path: /Users/mrzleo/.local/share/nvim/lazy/nvim-treesitter/parser/cmake.so
- OK Parser: comment    ABI: 13, path: /Users/mrzleo/.local/share/nvim/lazy/nvim-treesitter/parser/comment.so
- OK Parser: cpp        ABI: 14, path: /Users/mrzleo/.local/share/nvim/lazy/nvim-treesitter/parser/cpp.so
- OK Parser: diff       ABI: 14, path: /Users/mrzleo/.local/share/nvim/lazy/nvim-treesitter/parser/diff.so
- OK Parser: dockerfile ABI: 14, path: /Users/mrzleo/.local/share/nvim/lazy/nvim-treesitter/parser/dockerfile.so
- OK Parser: fish       ABI: 14, path: /Users/mrzleo/.local/share/nvim/lazy/nvim-treesitter/parser/fish.so
- OK Parser: gitattributes ABI: 14, path: /Users/mrzleo/.local/share/nvim/lazy/nvim-treesitter/parser/gitattributes.so
- OK Parser: git_rebase ABI: 14, path: /Users/mrzleo/.local/share/nvim/lazy/nvim-treesitter/parser/git_rebase.so
- OK Parser: go         ABI: 14, path: /Users/mrzleo/.local/share/nvim/lazy/nvim-treesitter/parser/go.so
- OK Parser: gomod      ABI: 13, path: /Users/mrzleo/.local/share/nvim/lazy/nvim-treesitter/parser/gomod.so
- OK Parser: gowork     ABI: 13, path: /Users/mrzleo/.local/share/nvim/lazy/nvim-treesitter/parser/gowork.so
- OK Parser: haskell    ABI: 14, path: /Users/mrzleo/.local/share/nvim/lazy/nvim-treesitter/parser/haskell.so
- ERROR Parser "help" failed to load (path: /Users/mrzleo/.local/share/nvim/lazy/nvim-treesitter/parser/help.so): Failed to load parser: uv_dlsym: dlsym(0x9ae2b5e0, tree_sitter_help): symbol not found
- OK Parser: json       ABI: 13, path: /Users/mrzleo/.local/share/nvim/lazy/nvim-treesitter/parser/json.so
- OK Parser: json5      ABI: 13, path: /Users/mrzleo/.local/share/nvim/lazy/nvim-treesitter/parser/json5.so
- OK Parser: latex      ABI: 14, path: /Users/mrzleo/.local/share/nvim/lazy/nvim-treesitter/parser/latex.so
- OK Parser: llvm       ABI: 13, path: /Users/mrzleo/.local/share/nvim/lazy/nvim-treesitter/parser/llvm.so
- OK Parser: lua        ABI: 13, path: /Users/mrzleo/.local/share/nvim/lazy/nvim-treesitter/parser/lua.so
- OK Parser: make       ABI: 13, path: /Users/mrzleo/.local/share/nvim/lazy/nvim-treesitter/parser/make.so
- OK Parser: markdown   ABI: 13, path: /Users/mrzleo/.local/share/nvim/lazy/nvim-treesitter/parser/markdown.so
- OK Parser: markdown_inline ABI: 13, path: /Users/mrzleo/.local/share/nvim/lazy/nvim-treesitter/parser/markdown_inline.so
- OK Parser: ninja      ABI: 13, path: /Users/mrzleo/.local/share/nvim/lazy/nvim-treesitter/parser/ninja.so
- OK Parser: perl       ABI: 13, path: /Users/mrzleo/.local/share/nvim/lazy/nvim-treesitter/parser/perl.so
- OK Parser: proto      ABI: 13, path: /Users/mrzleo/.local/share/nvim/lazy/nvim-treesitter/parser/proto.so
- OK Parser: python     ABI: 14, path: /Users/mrzleo/.local/share/nvim/lazy/nvim-treesitter/parser/python.so
- OK Parser: rst        ABI: 13, path: /Users/mrzleo/.local/share/nvim/lazy/nvim-treesitter/parser/rst.so
- OK Parser: rust       ABI: 14, path: /Users/mrzleo/.local/share/nvim/lazy/nvim-treesitter/parser/rust.so
- OK Parser: sql        ABI: 14, path: /Users/mrzleo/.local/share/nvim/lazy/nvim-treesitter/parser/sql.so
- OK Parser: toml       ABI: 13, path: /Users/mrzleo/.local/share/nvim/lazy/nvim-treesitter/parser/toml.so
- OK Parser: vim        ABI: 14, path: /Users/mrzleo/.local/share/nvim/lazy/nvim-treesitter/parser/vim.so
- OK Parser: yaml       ABI: 13, path: /Users/mrzleo/.local/share/nvim/lazy/nvim-treesitter/parser/yaml.so
- OK Parser: c          ABI: 13, path: /usr/local/lib/nvim/parser/c.so
- ERROR Parser "help" failed to load (path: /usr/local/lib/nvim/parser/help.so): Failed to load parser: uv_dlsym: dlsym(0x9ae2b5e0, tree_sitter_help): symbol not found
- OK Parser: lua        ABI: 13, path: /usr/local/lib/nvim/parser/lua.so
- OK Parser: query      ABI: 14, path: /usr/local/lib/nvim/parser/query.so
- OK Parser: vim        ABI: 14, path: /usr/local/lib/nvim/parser/vim.so
- OK Parser: vimdoc     ABI: 14, path: /usr/local/lib/nvim/parser/vimdoc.so


Minimal vimrc that can reproduce this bug.

local colorscheme = "edge"

local status_ok, _ = pcall(vim.cmd, "colorscheme " .. colorscheme)
if not status_ok then
    vim.notify("colorscheme " .. colorscheme .. " not found!")
    return
end

Steps to reproduce this bug using minimal vimrc

  1. open a rust file
  2. load rust-analyzer

Expected behavior

Before rust-analyzer finish loading:

image

Actual behavior

After:

image

Dark mode terminal colors

Hello,

today I was using dark mode for a bit (I'm using light mode 99% of the time), and noticed while running some tests that some part of text was not visible. I investigated a bit and noticed that terminal colors are completely the same between 0-7 and 8-15. My test runner uses color8 to display foreground color for the test specs (mocha), which in dark mode causes text and background to be exactly the same.
I don't have this issue in light mode.

I think there should be some difference between 0-7 and 8-15 palette.
For example, if you check kitty color scheme example,it also uses different colors https://sw.kovidgoyal.net/kitty/conf.html#the-color-table

vim-clap support

Would you consider adding support for vim-clap?

The author of the plugin has an example theme here that could be used for reference.

And thanks for the awesome themes. The wide plugin support is really great :)

Lightline Theme is not working on Neovim

After installing lightline and your theme i was setting this in my ~/.config/nvim/init.vi file:

" theme settings 
set background=dark
colorscheme edge

" lightline settings
let g:lightline = {}
let g:lightline.colorscheme = 'edge'

But the result looks like this:
2019-09-03-161543_1919x1079_scrot

Any help would be appreciated! I really like this theme.
Thanks, in advice.


Neovim version:

Build type: Release
LuaJIT 2.0.5
Compilation: /usr/bin/cc -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -Wconversion -O2 -DNDEBUG -DMIN_LOG_LEVEL=3 -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wimplicit-fallthrough -Wvla -fstack-p
rotector-strong -fdiagnostics-color=auto -Wno-array-bounds -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -I/build/neovim/src/build/config -I/build/neovim/src/neovim-0.3.8/src -I/
usr/include -I/build/neovim/src/build/src/nvim/auto -I/build/neovim/src/build/include
Compiled by builduser

NvimTree: bad diagnostics symbols highlight

Operating system/version

linux

Terminal emulator/version

kitty

$TERM environment variable

xterm-kitty

Tmux version

No response

Feature matrix

not related

Minimal vimrc that can reproduce this bug.

Simply install edge

Steps to reproduce this bug using minimal vimrc

  1. Open a file and wait for neovim builtin LSP to start
  2. Type something (some errors) to make diagnostics arise
  3. Open NvimTree buffer :NvimTreeFindFile
  4. Look at the diagnostics symbol near the file name

Expected behavior

This screenshot is taken while using material.nvim, and it shows the correct behavior

error-material

Actual behavior

This screenshot is taken while using edge

error-edge

As you can see error symbol is undercurled and not red

Some suggestions for the choice of colours when using LaTeX

I am a daily user of LaTeX + edge.

As a LaTeX user, I am super grateful that edge has dedicated LaTeX colouring.

There is one case where the choice of colours is not optimal in my opinion:
when drawing a diagram with tikzcd, the block of code is usually a mix of red
and orange.
Red because all texMathCmd are RedItalic.
Orange because texMathZone is Special and texTabularChar is SpecialChar.

I have a couple suggestions to make this easier to read:

  1. (big change) I believe the colour Red is the most visible colour to the human eye and it should be used sparingly. Perhaps, one could assign a different colour to texMathCmd
  2. (small change) The colour assigned to texTabularChar should not be too close to the one of texMathCmd and texMathZone so that the eye can navigate easily in of tabular environments.

Wrong hightling but correct in visual mode

  • Operating system/version: Arch Linux x86_64 (kernal 5.13.9-arch1-1)
  • Terminal emulator/version: alacritty 0.9.0 (fed349aa)
  • echo $TERM: screen
  • tmux -V: tmux 3.2a
  • vim --version or nvim --version:
NVIM v0.5.0
Build type: Release
LuaJIT 2.0.5
Compilation: /usr/bin/cc -D_FORTIFY_SOURCE=2 -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -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=always -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -I/build/neovim/src/neovim-0.5.0/build/config -I/build/neovim/src/neovim-0.5.0/src -I/usr/include -I/build/neovim/src/neovim-0.5.0/build/src/nvim/auto -I/build/neovim/src/neovim-0.5.0/build/include
Compiled by builduser

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

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

Run :checkhealth for more info

Minimal vimrc that can reproduce this bug

I will provide the minimal configuration (and steps) in each case in the Actual behaviour section.

$ nvim -u ~/.config/nvim/mini-init.vim -- the-file.js

Actual behaviour

edge alone

let g:plug_home = '~/.config/nvim/plugins'

call plug#begin(plug_home)
Plug 'sainnhe/edge'
call plug#end()

colo edge

image


edge + nvim-treesitter/nvim-treesitter

let g:plug_home = '~/.config/nvim/plugins'

call plug#begin(plug_home)
Plug 'sainnhe/edge'
Plug 'nvim-treesitter/nvim-treesitter', {'do': ':TSUpdate'}  " We recommend updating the parsers on update
call plug#end()

lua <<EOF
require'nvim-treesitter.configs'.setup {
  ensure_installed = "maintained", -- one of "all", "maintained" (parsers with maintainers), or a list of languages
  -- ignore_install = { "javascript" }, -- List of parsers to ignore installing
  highlight = {
    enable = true,              -- false will disable the whole extension
    -- disable = { "c", "rust" }, -- list of language that will be disabled
    -- Setting this to true will run `:h syntax` and tree-sitter at the same time.
    -- Set this to `true` if you depend on 'syntax' being enabled (like for indentation).
    -- Using this option may slow down your editor, and you may see some duplicate highlights.
    -- Instead of true it can also be a list of languages
    additional_vim_regex_highlighting = true,
  },
  indent = {
    enable = true
  }
}
EOF

colo edge

image


edge + nvim-treesitter/nvim-treesitter + sheerun/vim-polyglot

The props of these tags are blue in, but when it is selected it turns to red.

let g:plug_home = '~/.config/nvim/plugins'

call plug#begin(plug_home)
Plug 'sainnhe/edge'
Plug 'nvim-treesitter/nvim-treesitter', {'do': ':TSUpdate'}  " We recommend updating the parsers on update
Plug 'sheerun/vim-polyglot'
call plug#end()

lua <<EOF
require'nvim-treesitter.configs'.setup {
  ensure_installed = "maintained", -- one of "all", "maintained" (parsers with maintainers), or a list of languages
  -- ignore_install = { "javascript" }, -- List of parsers to ignore installing
  highlight = {
    enable = true,              -- false will disable the whole extension
    -- disable = { "c", "rust" }, -- list of language that will be disabled
    -- Setting this to true will run `:h syntax` and tree-sitter at the same time.
    -- Set this to `true` if you depend on 'syntax' being enabled (like for indentation).
    -- Using this option may slow down your editor, and you may see some duplicate highlights.
    -- Instead of true it can also be a list of languages
    additional_vim_regex_highlighting = true,
  },
  indent = {
    enable = true
  }
}
EOF

colo edge

image

Expected behaviour

In all cases, I expect the selected not selected lines to be the same, but this doesn't happen in the last case.

Unexpected DiagnosticWarn Foreground Color

Operating system/version

macOS Big Sur 11.5.1

Terminal emulator/version

iTerm2 Build 3.4.12

$TERM environment variable

xterm-256color

Tmux version

No response

Feature matrix

$ v --version
NVIM v0.7.0-dev+886-ga88046fe2
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Compilation: /Applications/Xcode_12.4.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DNVIM_TS_HAS_SET_MATCH_LIMIT -DNVIM_TS_HAS_SET_ALLOCATOR -O2 -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wmissing-prototypes -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fno-common -fdiagnostics-color=always -DINCLUDE_GENERATED_DECLARATIONS -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -I/Users/runner/work/neovim/neovim/build/config -I/Users/runner/work/neovim/neovim/src -I/Users/runner/work/neovim/neovim/.deps/usr/include -I/Applications/Xcode_12.4.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk/usr/include -I/Library/Frameworks/Mono.framework/Headers -I/Users/runner/work/neovim/neovim/build/src/nvim/auto -I/Users/runner/work/neovim/neovim/build/include
Compiled by [email protected]

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

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/share/nvim"

Run :checkhealth for more info
:checkhealth
coc: health#coc#check
========================================================================
  - OK: Environment check passed
  - OK: Javascript bundle build/index.js found
  - OK: Service started

nvim: health#nvim#check
========================================================================
## Configuration
  - OK: no issues found

## Performance
  - OK: Build type: RelWithDebInfo

## Remote Plugins
  - OK: Up to date

## terminal
  - INFO: key_backspace (kbs) terminfo entry: key_backspace=^H
  - INFO: key_dc (kdch1) terminfo entry: key_dc=\E[3~
  - INFO: $TERM_PROGRAM='iTerm.app'
  - INFO: $COLORTERM='truecolor'

provider: health#provider#check
========================================================================
## Clipboard (optional)
  - OK: Clipboard tool found: pbcopy

## Python 2 provider (optional)
  - INFO: pyenv: Path: /usr/local/Cellar/pyenv/2.2.3/libexec/pyenv
  - INFO: pyenv: $PYENV_ROOT is not set. Infer from `pyenv root`.
  - INFO: pyenv: Root: /Users/user/.pyenv
  - WARNING: No Python executable found that can `import neovim`. Using the first available executable for diagnostics.
  - ERROR: Python provider error:
    - ADVICE:
      - provider/pythonx: Could not load Python 2:
          /usr/bin/python2 does not have the "neovim" module. :help provider-python
          /usr/bin/python2.7 does not have the "neovim" module. :help provider-python
          python2.6 not found in search path or not executable.
          /usr/local/bin/python is Python 3.9 and cannot provide Python 2.
  - INFO: Executable: Not found

## Python 3 provider (optional)
  - INFO: pyenv: Path: /usr/local/Cellar/pyenv/2.2.3/libexec/pyenv
  - INFO: pyenv: $PYENV_ROOT is not set. Infer from `pyenv root`.
  - INFO: pyenv: Root: /Users/user/.pyenv
  - INFO: `g:python3_host_prog` is not set.  Searching for python3 in the environment.
  - WARNING: pyenv is not set up optimally.
    - ADVICE:
      - Create a virtualenv specifically for Nvim using pyenv, and set `g:python3_host_prog`.  This will avoid the need to install the pynvim module in each version/virtualenv.
  - INFO: Executable: /usr/local/opt/python@3/bin/python3
  - INFO: Python version: 3.9.9
  - INFO: pynvim version: 0.4.3
  - OK: Latest pynvim is installed.

## Python virtualenv
  - OK: no $VIRTUAL_ENV

## Ruby provider (optional)
  - INFO: Ruby: ruby 3.0.3p157 (2021-11-24 revision 3fb7d2cadc) [x86_64-darwin20]
  - INFO: Host: /Users/user/.rbenv/shims/neovim-ruby-host
  - OK: Latest "neovim" gem is installed: 0.9.0

## Node.js provider (optional)
  - INFO: Node.js: v14.16.0
  - INFO: Nvim node.js host: /usr/local/lib/node_modules/neovim/bin/cli.js
  - OK: Latest "neovim" npm/yarn package is installed: 4.10.1

## Perl provider (optional)
  - ERROR: perl provider error:
    - ADVICE:
      - "Neovim::Ext" cpan module is not installed

vim.lsp: require("vim.lsp.health").check()
========================================================================
  - INFO: LSP log level : WARN
  - INFO: Log path: /Users/user/.cache/nvim/lsp.log
  - INFO: Log size: 71 KB

vim.treesitter: require("vim.treesitter.health").check()
========================================================================
  - INFO: Runtime ABI version : 13
  - OK: Loaded parser for c: ABI version 13

Minimal vimrc that can reproduce this bug.

call plug#begin(expand('~/.vim/plugged'))
Plug 'nvim-lualine/lualine.nvim'
Plug 'kyazdani42/nvim-web-devicons'
Plug 'neoclide/coc.nvim', {'branch': 'release'}
Plug 'sainnhe/edge'
call plug#end()
colorscheme edge
"colorscheme default
syntax enable
filetype on
filetype plugin on
filetype indent on
syntax on
set termguicolors

lua << END
require('lualine').setup()
END

Steps to reproduce this bug using minimal vimrc

:cocinstall coc-somelsp then trigger the warning sign in lualine

Expected behavior

colorscheme default
Screen Shot 2022-01-14 at 10 52 49 PM

Actual behavior

Screen Shot 2022-01-14 at 10 49 33 PM

Color Palette difference between `README.md` and `autoload/edge.vim`

Hi, first of all, I have to say that great job with your color themes/palettes. I've enjoyed using them quite a bit!

I noticed that the colors displayed on the README.md and autoload/edge.vim differ slightly. Are these changes on purpose?

Edge Dark:

README.md autoload/edge.vim
"gray_dim": "#535C6A" "bg_grey": "#828A98"
"gray": "#758094"

I noticed that this issue is persistent throughout all of the displayed themes/variations.

I'm currently working on a project called dipc - "Convert your favorite images and wallpapers with your favorite color palettes/themes" and I've implemented a couple of your themes.

Less contrast on DiffText in light mode

Hi,

what do you think about changing the default "DiffText" color for light mode? Current setup has a bit too big contrast:

screenshot

I think having a bit Darker blue would do the trick.

Black background

Hi,

First of all thanks for this great theme.
I'm having some issue to get a complete dark background on neovim. Usually, setting
both highlight Normal ctermbg=NONE and highlight nonText ctermbg=NONE are sufficient to override a them background but it is not the case for edge.

Is there a way to do this directly using via some edge specific configuration ?

image
image

Archlinux info:

$ uname -a
Linux oakfire 5.10.87-1-lts #1 SMP Fri, 17 Dec 2021 10:43:27 +0000 x86_64 GNU/Linux

Neovim info:

$ nvim --version
NVIM v0.6.0-dev+565-g8cbe100fc
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Compilation: /usr/bin/gcc-11 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DNVIM_TS_HAS_SET_MATCH_LIMIT -O2 -g -Og -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wmissing-prototypes -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fno-common -fdiagnostics-color=always -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -I/home/runner/work/neovim/neovim/build/config -I/home/runner/work/neovim/neovim/src -I/home/runner/work/neovim/neovim/.deps/usr/include -I/usr/include -I/home/runner/work/neovim/neovim/build/src/nvim/auto -I/home/runner/work/neovim/neovim/build/include
Compiled by runner@fv-az50-670

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

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/share/nvim"

Run :checkhealth for more info

init.lua snippet:

vim.cmd([[
   set background=dark
   colorscheme edge
   highlight Normal ctermbg=NONE
   highlight nonText ctermbg=NONE
]])

Light version with bigger contrast

Hi,

would you consider adding a light version that has more contrast?
Current light version foreground is a bit too bright, I would like to have more contrast between foreground and background.
Ideally, background would be completely white, and "Normal" foreground would be completely black. This doesn't look good when I change only those 2 values because normal contrast is too big in compare to other colors (Red, blue, etc.).
I've used this colorscheme before https://github.com/habamax/vim-polar which does this nicely, but I want to switch to yours because of the dark version and treesitter support.

If you would consider this, I could make a PR with a light version that has a stronger contrast and we can discuss it.

Most of the text is background-colored in lazygit via toggleterm

Hi !

I'm running neovim with a lazygit setup inside of a floating toggleterm terminal.

Here is a screenshot of what that looks like :
edge_plus_lazygit_in_toggleterm

Most of the text is invisible due to it having the same color as the background. I get the same results when running nvim via Yakuake, Xfce4-terminal, or neovide.

For reference, here is lazygit run directly from cli, with an approximate edge theme recreation in yakuake, where i matched the edge hex colors to the base yakuake light theme :
fake_edge_plus_lazygit

Other than that it looks quite great!

This isn't an urgent problem to solve btw, i can still use git from the command line. I'm not familiar with vimscript or lua enough to figure it out on my own, but if you can point me in the right direction to fix the issue I'd be more than happy to submit a PR.

Wrong coloring with Treesitter

Operating system/version

macOS/Ubuntu

Terminal emulator/version

iTerm2/Kitty

$TERM environment variable

xterm-256color

Tmux version

No response

Feature matrix

NVIM v0.8.0-dev+302-gaf2899aee
Build type: Release
LuaJIT 2.1.0-beta3

Minimal vimrc that can reproduce this bug.

call plug#begin('~/.config/nvim/plugged/')

Plug 'nvim-lua/plenary.nvim'
Plug 'nvim-treesitter/nvim-treesitter', {'do': ':TSUpdate'}
Plug 'sainnhe/edge'

call plug#end()

lua << EOF
    require'nvim-treesitter.configs'.setup {
    ensure_installed = {'python'},
    sync_install = false,
    ignore_install = {},
    highlight = {
          enable = true, -- `false` will disable the whole extension
          additional_vim_regex_highlighting = false,
    },
}
EOF

if (has('termguicolors'))
  let &t_8f = "\<Esc>[38;2;%lu;%lu;%lum"
  let &t_8b = "\<Esc>[48;2;%lu;%lu;%lum"
  set termguicolors
endif

" Edge Theme
let g:edge_style = 'neon'
colorscheme edge

Steps to reproduce this bug using minimal vimrc

  1. nvim +PlugClean +PlugInstall
  2. nvim <any python file>

Expected behavior

I should see the same coloring as I can see on the screenshots provided in the README.

(With vim-polygot it is working fine.)

Actual behavior

I attached the image how it colors my script:

image

Secondary colorscheme versions

Is there any way to use the alternative colorscheme versions(like neon) in kitty or other external programs that aren't vim? Thanks!

Apreciation Issue

I just wanna thank you for this amazing color scheme,
Just the other day I was using markdown and noticed my headers had different colors at each level, this is a small thing I never knew I needed but cannot live without it now, so thanks.

No border in floaterm fzf.

Here is the screenshot using edge as colorscheme. I didn't see the border of floaterm.

image

With gruvbox:

image

With evergreen:

image

Vim-version:

VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Mar 23 2022 23:02:46)
MS-Windows 64-bit GUI version with OLE support
Included patches: 1-4616
Compiled by appveyor@APPVYR-WIN
Huge version with GUI.  Features included (+) or not (-):
+acl                +cmdline_info       +extra_search       +langmap            +num64              +scrollbind         -termresponse       -vtp
+arabic             +comments           -farsi              +libcall            +ole                +signs              +textobjects        +wildignore
+autocmd            +conceal            +file_in_path       +linebreak          +packages           +smartindent        +textprop           +wildmenu
+autochdir          +cryptv             +find_in_path       +lispindent         +path_extra         +sodium/dyn         -tgetent            +windows
+autoservername     +cscope             +float              +listcmds           +perl/dyn           +sound              +timers             +writebackup
+balloon_eval       +cursorbind         +folding            +localmap           +persistent_undo    +spell              +title              -xfontset
-balloon_eval_term  +cursorshape        -footer             +lua/dyn            +popupwin           +startuptime        +toolbar            -xim
+browse             +dialog_con_gui     +gettext/dyn        +menu               -postscript         +statusline         +user_commands      +xpm_w32
++builtin_terms     +diff               -hangul_input       +mksession          +printer            -sun_workshop       +vartabs            -xterm_save
+byte_offset        +digraphs           +iconv/dyn          +modify_fname       +profile            +syntax             +vertsplit          
+channel            +directx            +insert_expand      +mouse              +python/dyn         +tag_binary         +vim9script         
+cindent            -dnd                +ipv6               +mouseshape         +python3/dyn        -tag_old_static     +viminfo            
+clientserver       -ebcdic             +job                +multi_byte_ime/dyn +quickfix           -tag_any_white      +virtualedit        
+clipboard          +emacs_tags         +jumplist           +multi_lang         +reltime            -tcl                +visual             
+cmdline_compl      +eval               +keymap             +mzscheme/dyn       +rightleft          -termguicolors      +visualextra        
+cmdline_hist       +ex_extra           +lambda             +netbeans_intg      +ruby/dyn           +terminal           +vreplace           
   system vimrc file: "$VIM\vimrc"
     user vimrc file: "$HOME\_vimrc"
 2nd user vimrc file: "$HOME\vimfiles\vimrc"
 3rd user vimrc file: "$VIM\_vimrc"
      user exrc file: "$HOME\_exrc"
  2nd user exrc file: "$VIM\_exrc"
  system gvimrc file: "$VIM\gvimrc"
    user gvimrc file: "$HOME\_gvimrc"
2nd user gvimrc file: "$HOME\vimfiles\gvimrc"
3rd user gvimrc file: "$VIM\_gvimrc"
       defaults file: "$VIMRUNTIME\defaults.vim"
    system menu file: "$VIMRUNTIME\menu.vim"
Compilation: cl -c /W3 /GF /nologo -I. -Iproto -DHAVE_PATHDEF -DWIN32  -DFEAT_CSCOPE -DFEAT_TERMINAL -DFEAT_SOUND -DFEAT_NETBEANS_INTG -DFEAT_JOB_CHANNEL -DFEAT_IPV6   -DFEAT_XPM_W32 -DHAVE_SODIUM -DDYNAMIC_SODIUM -DDYNAMIC_SODIUM_DLL=\"libsodium.dll\" /I "C:\libsodium\include" -DWINVER=0x0501 -D_WIN32_WINNT=0x0501 /source-charset:utf-8 /MP -DHAVE_STDINT_H /Ox /GL -DNDEBUG /Zl /MT /D_CRT_SECURE_NO_DEPRECATE /D_CRT_NONSTDC_NO_DEPRECATE -DFEAT_OLE -DFEAT_MBYTE_IME -DDYNAMIC_IME -DFEAT_GUI_MSWIN -DFEAT_DIRECTX -DDYNAMIC_DIRECTX -DFEAT_DIRECTX_COLOR_EMOJI -DDYNAMIC_ICONV -DDYNAMIC_GETTEXT -DFEAT_LUA -DDYNAMIC_LUA -DDYNAMIC_LUA_DLL=\"lua54.dll\" -DFEAT_PYTHON -DDYNAMIC_PYTHON -DDYNAMIC_PYTHON_DLL=\"python27.dll\" -DFEAT_PYTHON3 -DDYNAMIC_PYTHON3 -DDYNAMIC_PYTHON3_DLL=\"python310.dll\" -DFEAT_MZSCHEME -I "C:\racket\include" -DMZ_PRECISE_GC -DDYNAMIC_MZSCHEME -DDYNAMIC_MZSCH_DLL=\"libracket3m_da32rk.dll\" -DDYNAMIC_MZGC_DLL=\"libracket3m_da32rk.dll\" -DFEAT_PERL -DPERL_IMPLICIT_CONTEXT -DPERL_IMPLICIT_SYS -DDYNAMIC_PERL -DDYNAMIC_PERL_DLL=\"perl532.dll\" -DFEAT_RUBY -DDYNAMIC_RUBY -DDYNAMIC_RUBY_DLL=\"x64-msvcrt-ruby300.dll\" -DRUBY_VERSION=30 -DFEAT_HUGE /Fd.\ObjGXOULYHRZAMD64/ /Zi
Linking: link /nologo /opt:ref /LTCG /HIGHENTROPYVA:NO oldnames.lib kernel32.lib advapi32.lib shell32.lib gdi32.lib  comdlg32.lib ole32.lib netapi32.lib uuid.lib user32.lib  /machine:AMD64 version.lib  winspool.lib comctl32.lib  libcmt.lib oleaut32.lib  /nodefaultlib:lua54.lib  /STACK:8388608  /nodefaultlib:python27.lib /nodefaultlib:python310.lib    winmm.lib WSock32.lib Ws2_32.lib xpm\x64\lib-vc14\libXpm.lib  /PDB:gvim.pdb -debug

Platform: Window 11.

Latest update (2020-08-01) causes errors on vim HEAD and nvim HEAD

First, thanks so much for edge. I see that you just updated the colorscheme, and on both vim HEAD and nvim head, it leads to issues:

Error detected while processing /Users/telemachus/.vimrc[82]../Users/telemachus/.vim/pack/bundle/start/edge/colors/edge.vim:
line   21:
E117: Unknown function: edge#get_configuration
line   22:
E121: Undefined variable: s:configuration
E116: Invalid arguments for function edge#get_palette(s:configuration.style)
line   29:
E121: Undefined variable: s:configuration
line   51:
E121: Undefined variable: s:palette
E116: Invalid arguments for function edge#highlight
line   52:
E121: Undefined variable: s:palette
E116: Invalid arguments for function edge#highlight
line   53:
E121: Undefined variable: s:palette
E116: Invalid arguments for function edge#highlight
line   54:
... (followed by many many more of the same errors re s:palette)

I will try to dig into this myself since I saw your post about the maintenance status of edge, but I wanted to let you know.

In case it helps, here are more details about my system and editor versions:

  • macOS 10.15.6
  • NVIM v0.5.0-619-g1153ac903
  • VIM - Vi IMproved 8.2, Included patches: 1-1342

Use lightline/airline cofniguration with Tmuxline

Hello.

I have just set up edge and it is very pleasant, well done.
However, I use the lightline colors to setup the tmux colors using TmuxLine plugin to set up the tmux colorscheme.
The problem is that when I setup edge, lightline is just fine, but tmux is almost absolutely black (or blank...).
Luckily my setup allows me to assing an alternative to a given colorscheme, but I suppose you would want to know about this issue.

Thanks for the scheme; like I said, it's a pleasant one, and this is unusual. :-)

Undercurl highlights rendered as underline

Operating system/version

macOS Big Sur 11.6

Terminal emulator/version

Kitty 0.24.3

$TERM environment variable

xterm-kitty

Tmux version

tmux 3.2a

Feature matrix


compe: health#compe#check
========================================================================
## compe:snippet
  - INFO: snippet engine is not detected.

## compe:mapping
  - INFO: `compe#complete` is not mapped
  - INFO: `compe#confirm` is not mapped
  - INFO: `compe#close` is not mapped
  - INFO: `compe#scroll` is not mapped

nvim: health#nvim#check
========================================================================
## Configuration
  - OK: no issues found

## Performance
  - OK: Build type: Release

## Remote Plugins
  - OK: Up to date

## terminal
  - INFO: key_backspace (kbs) terminfo entry: key_backspace=\177
  - INFO: key_dc (kdch1) terminfo entry: key_dc=\E[3~
  - INFO: $TERM_PROGRAM='tmux'
  - INFO: $COLORTERM='truecolor'

## tmux
  - OK: escape-time: 0
  - INFO: Checking stuff
  - WARNING: `focus-events` is not enabled. |'autoread'| may not work.
    - ADVICE:
      - (tmux 1.9+ only) Set `focus-events` in ~/.tmux.conf:
          set-option -g focus-events on
  - INFO: $TERM: xterm-kitty
  - ERROR: $TERM should be "screen-256color" or "tmux-256color" in tmux. Colors might look wrong.
    - ADVICE:
      - Set default-terminal in ~/.tmux.conf:
          set-option -g default-terminal "screen-256color"
      - https://github.com/neovim/neovim/wiki/FAQ

nvim-treesitter: require("nvim-treesitter.health").check()
========================================================================
## Installation
  - OK: `tree-sitter` found 0.20.2 (parser generator, only needed for :TSInstallFromGrammar)
  - OK: `node` found v16.13.1 (only needed for :TSInstallFromGrammar)
  - OK: `git` executable found.
  - OK: `cc` executable found. Selected from { vim.NIL, "cc", "gcc", "clang", "cl", "zig" }
    Version: Apple clang version 12.0.5 (clang-1205.0.22.11)
  - OK: Neovim was compiled with tree-sitter runtime ABI version 13 (required >=13). Parsers must be compatible with runtime ABI.

## Parser/Features H L F I J
  - toml           โœ“ โœ“ โœ“ โœ“ โœ“ 

  Legend: H[ighlight], L[ocals], F[olds], I[ndents], In[j]ections
         +) multiple parsers found, only one will be used
         x) errors found in the query, try to run :TSUpdate {lang}

provider: health#provider#check
========================================================================
## Clipboard (optional)
  - OK: Clipboard tool found: pbcopy

## Python 2 provider (optional)
  - INFO: pyenv: Path: /opt/homebrew/Cellar/pyenv/2.2.3/libexec/pyenv
  - INFO: pyenv: Root: /Users/markstory/.pyenv
  - WARNING: No Python executable found that can `import neovim`. Using the first available executable for diagnostics.
  - ERROR: Python provider error:
    - ADVICE:
      - provider/pythonx: Could not load Python 2:
          /usr/bin/python2 does not have the "neovim" module. :help |provider-python|
          /usr/bin/python2.7 does not have the "neovim" module. :help |provider-python|
          python2.6 not found in search path or not executable.
          /Users/markstory/code/getsentry/.venv/bin/python is Python 3.8 and cannot provide Python 2.
  - INFO: Executable: Not found

## Python 3 provider (optional)
  - INFO: pyenv: Path: /opt/homebrew/Cellar/pyenv/2.2.3/libexec/pyenv
  - INFO: pyenv: Root: /Users/markstory/.pyenv
  - WARNING: No Python executable found that can `import neovim`. Using the first available executable for diagnostics.
  - ERROR: Python provider error:
    - ADVICE:
      - provider/pythonx: Could not load Python 3:
          /Users/markstory/code/getsentry/.venv/bin/python3 does not have the "neovim" module. :help |provider-python|
          python3.10 not found in search path or not executable.
          /opt/homebrew/bin/python3.9 does not have the "neovim" module. :help |provider-python|
          /Users/markstory/.pyenv/shims/python3.8 does not have the "neovim" module. :help |provider-python|
          python3.7 not found in search path or not executable.
          python3.6 not found in search path or not executable.
          /Users/markstory/code/getsentry/.venv/bin/python does not have the "neovim" module. :help |provider-python|
  - INFO: Executable: Not found

## Python virtualenv
  - INFO: $VIRTUAL_ENV is set to: /Users/markstory/code/getsentry/.venv
  - INFO: Python version: 3.8.12
  - OK: $VIRTUAL_ENV provides :!python.

## Ruby provider (optional)
  - INFO: Ruby: ruby 2.6.3p62 (2019-04-16 revision 67580) [universal.arm64e-darwin20]
  - WARNING: `neovim-ruby-host` not found.
    - ADVICE:
      - Run `gem install neovim` to ensure the neovim RubyGem is installed.
      - Run `gem environment` to ensure the gem bin directory is in $PATH.
      - If you are using rvm/rbenv/chruby, try "rehashing".
      - See :help |g:ruby_host_prog| for non-standard gem installations.

## Node.js provider (optional)
  - INFO: Node.js: v16.13.1
  - WARNING: Missing "neovim" npm (or yarn) package.
    - ADVICE:
      - Run in shell: npm install -g neovim
      - Run in shell (if you use yarn): yarn global add neovim

## Perl provider (optional)
  - ERROR: perl provider error:
    - ADVICE:
      - "Neovim::Ext" cpan module is not installed

vim.lsp: require("vim.lsp.health").check()
========================================================================
  - INFO: LSP log level : WARN
  - INFO: Log path: /Users/markstory/.cache/nvim/lsp.log
  - INFO: Log size: 450 KB

vim.treesitter: require("vim.treesitter.health").check()
========================================================================
  - INFO: Runtime ABI version : 13
  - OK: Loaded parser for toml: ABI version 13

Minimal vimrc that can reproduce this bug.

call plug#begin()

" Theme
Plug 'sainnhe/edge'
-- Default color scheme
vim.g.noshowmode = true
vim.g.termguicolors = true
vim.cmd("set background=light")

-- Theme configuration
vim.g.edge_enable_italic = 1
vim.g.edge_diagnostic_line_highlight = 1

vim.cmd("colorscheme edge")

Steps to reproduce this bug using minimal vimrc

Thank you for publishing this, I'm really loving the colorscheme. This is less of a bug report and more of a question/proposal.

  1. Launch neovim and open a file that contains LSP dignostic errors.

Expected behavior

I was hoping to see undercurls used when the highlight groups say undercurl.

Changing line 156 of the cited block to 'undercurl' updates the output to use undercurls correctly. Would you be open to using actual undercurls used (based on a configuration flag that defaults to the current behavior)?

Actual behavior

I've noticed that the edge#highlight converts undercurl to underline when generating the highlight definition. This results in a straight underline being used:

Screen Shot 2022-03-07 at 2 43 28 PM

I tracked this down to this block:

edge/autoload/edge.vim

Lines 155 to 157 in 825421f

\ (a:1 ==# 'undercurl' ?
\ 'underline' :
\ a:1) :

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.