Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Report error message when start #2

Open
tan-wei opened this issue Aug 1, 2022 · 5 comments
Open

Report error message when start #2

tan-wei opened this issue Aug 1, 2022 · 5 comments

Comments

@tan-wei
Copy link

tan-wei commented Aug 1, 2022

处理 ColorScheme 自动命令 "*" 时发生错误: 
E121: Undefined variable: g:colors_name 
E116: Invalid arguments for function CocHelperCallFn_m1_v0_13_0
请按 ENTER 或其它命令继续

It seems something with coc.

@nxvu699134
Copy link
Owner

Is it working with COC now @tan-wei.

@tan-wei
Copy link
Author

tan-wei commented Sep 20, 2022

Sorry for late reply. I'll try it ASAP.

@tan-wei
Copy link
Author

tan-wei commented Sep 21, 2022

No, it still complains the same error. Neovim version: v0.8.0-dev-1112-g6d557e324

@tan-wei
Copy link
Author

tan-wei commented Aug 21, 2023

OK, I think I find the issue:

  • I use a plugin which random choice a theme from a set, the plugin will print the name of the chosen colorscheme by echo g:color_names
  • But vn-night.nvim does not set the variable

It is easy to reproduce without the plugin:

  • Just print the name of current colorscheme by intputing command :colorscheme, neovim will just print default instead of vn-night

So set g:color_names will make this issue closed.

@tan-wei
Copy link
Author

tan-wei commented Aug 21, 2023

For any other colorschemes, the variable is set properly, so should vn-night.nvim, is it?

For example

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants