sainnhe / everforest

🌲 Comfortable & Pleasant Color Scheme for Vim
MIT License
2.83k stars 130 forks source link

E418: Illegal value: nocombine #96

Closed Evilhotdog closed 2 years ago

Evilhotdog commented 2 years ago

I have done the following steps before reporting this issue:

Operating system/version

Debian 11 on ChromeOS (Crostini)

Terminal emulator/version

Crostini terminal emulator (I think an htop fork)

$TERM environment variable

xterm-256color

Tmux version

No response

Feature matrix

health#vimtex#check
========================================================================
## VimTeX
  - OK: Vim version should have full support!
  - WARNING: biber is not executable!
    - ADVICE:
      - Biber is often required so this may give unexpected problems.
  - WARNING: Zathura requires xdotool for forward search!
  - OK: Compiler should work!

health#coc#check
========================================================================
  - OK: nvim version satisfied
  - OK: Environment check passed

  - OK: Javascript bundle build/index.js found
  - OK: Service started

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~

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

## Python 2 provider (optional)
  - 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:
          python2 not found in search path or not executable.
          python2.7 not found in search path or not executable.
          python2.6 not found in search path or not executable.
          python not found in search path or not executable.
  - INFO: Executable: Not found

## Python 3 provider (optional)
  - INFO: `g:python3_host_prog` is not set.  Searching for python3 in the environment.
  - INFO: Multiple python3 executables found.  Set `g:python3_host_prog` to avoid surprises.
  - INFO: Executable: /usr/bin/python3
  - INFO: Other python executable: /bin/python3
  - INFO: Python version: 3.9.2
  - INFO: pynvim version: 0.4.2 (outdated; from /usr/lib/python3/dist-packages/neovim)
  - WARNING: Latest pynvim is NOT installed: 0.4.3

## Ruby provider (optional)
  - WARNING: `ruby` and `gem` must be in $PATH.
    - ADVICE:
      - Install Ruby and verify that `ruby` and `gem` commands work.

## Node.js provider (optional)
  - INFO: Node.js: v18.5.0
  - 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

Minimal vimrc that can reproduce this bug.


call plug#begin()
Plug 'sainnhe/everforest'
call plug#end()

set termguicolors
colorscheme everforest

### Steps to reproduce this bug using minimal vimrc

Launch neovim

### Expected behavior

Neovim opens correctly. The theme is applied

### Actual behavior

Before opening whatever file I had passed, the following error appears:

Error detected while processing function everforest#highlight:
line    1:
E418: Illegal value: nocombine
E418: Illegal value: bold,nocombine
E418: Illegal value: nocombine
antoineco commented 2 years ago

@Evilhotdog could you please share the output of :version? nocombine requires Vim 8 or Neovim v0.3.2.

Evilhotdog commented 2 years ago

Turns out I had been on v0.4.4. Definitely past v0.3.2 but still pretty old. I installed the new version from a deb package and it seems to be working fine now.

Thanks!

antoineco commented 2 years ago

I might have been a bit too optimistic with v0.3.2. I was looking at Neovim's commit history and found a few references to nocombine in that version, but it was probably only partially ported from Vim 8.

Anyway, glad updating to v0.4 solved your issue!