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

Error detected while processing function magit#show_magit..magit#update_buffer #122

Closed
fpnick opened this issue Feb 28, 2017 · 7 comments
Closed

Comments

@fpnick
Copy link

fpnick commented Feb 28, 2017

Jerome,
now that you've fixed #119 , I get a new error when trying to open vimagit:

Error detected while processing function magit#show_magit..magit#update_buffer..16_airline_refresh..airline#load_theme..airline#highlig
hter#load_theme..airline#highlighter#highlight..airline#highlighter#exec:
line 20:
E421: Color name or number not recognized: ctermfg=-1 ctermbg=-1
E421: Color name or number not recognized: ctermfg=-1 ctermbg=-1
E421: Color name or number not recognized: ctermfg=-1 ctermbg=-1
E421: Color name or number not recognized: ctermfg=-1 ctermbg=-1
E421: Color name or number not recognized: ctermfg=-1 ctermbg=-1
Error detected while processing function magit#show_magit..magit#update_buffer..16_airline_refresh..airline#load_theme..airline#highlig
hter#load_theme..airline#highlighter#highlight..97_exec_separator..airline#highlighter#exec:
line 20:
E421: Color name or number not recognized: ctermfg=-1 ctermbg=-1
E421: Color name or number not recognized: ctermfg=-1 ctermbg=-1
E421: Color name or number not recognized: ctermfg=-1 ctermbg=-1
E421: Color name or number not recognized: ctermfg=-1 ctermbg=-1
E421: Color name or number not recognized: ctermfg=-1 ctermbg=-1

I can hit enter a couple of times an then the buffer opens in a vsplit as desired. My vim-airline commit is fbd791e (current master).

Fabian.

@jreybert
Copy link
Owner

Between vim-airline e7e4769 and fbd791e, I get strange characters in the status line, but no error.

Could you please provide:

  • test with vimagit only loaded plugin, and then vimagit + vim-airline only loaded plugins
  • the version of vim or nvim
  • the version of git
  • the SHA1 of vimagit you're using
  • the OS that you're using, including terminal emulator, GUI vs non-GUI
  • a step by step command to reproduce the bug

@fpnick
Copy link
Author

fpnick commented Feb 28, 2017

I just noticed that I get a very similar error when I use the Ctrl+P plugin.
Until I know any better, I'm gonna assume this is an airline issue and not a vimagit one. (I ran PluginUpdate on friday for the first time in a while, so pretty much everything was updated...)

You can probably close this issue for now, I'll let you know in case I should find any evidence this could be a vimagit issue.

EDIT: Indeed, reverting vim-airline to a (random) old version, solves both this issue and the one with Ctrl+P.

@jreybert
Copy link
Owner

Do you use an airline theme?

@fpnick
Copy link
Author

fpnick commented Feb 28, 2017

Yes: let g:airline_theme='delek'

@jreybert
Copy link
Owner

I can't find any airline theme called delek.

@fpnick
Copy link
Author

fpnick commented Feb 28, 2017

I have to admit I'm not exactly sure what that line is supposed to do in my vimrc. But removing it doesn't help either. Since I found a working commit in airline, I think I'll bisect the issue and see if that can tell me anything.

@fpnick
Copy link
Author

fpnick commented Mar 9, 2017

Does not occur any more with vim-airline at commit 134c0204f3b947276c0e6f26f4fe426b5cba5c06

@fpnick fpnick closed this as completed Mar 9, 2017
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