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

glyph not displayed for coc.nvim integration #343

Char-Aznable opened this Issue Jan 9, 2019 · 3 comments


None yet
2 participants
Copy link

Char-Aznable commented Jan 9, 2019

I have followed coc.nvim's doc for putting coc-status in lightline status bar:

  let g:lightline = {
	\ 'colorscheme': 'wombat',
	\ 'active': {
	\   'left': [ [ 'mode', 'paste' ],
	\             [ 'cocstatus', 'readonly', 'filename', 'modified' ] ]
	\ },
	\ 'component_function': {
	\   'cocstatus': 'coc#status'
	\ },
\ }

The problem is that the error glyph does not show up correctly (it's shown as a box of string) even though I have set the error glyph as a capital x (X) in coc.nvim:

"coc.preferences.diagnostic.errorSign": "X",
"coc.preferences.diagnostic.warningSign": "⚠",
"coc.preferences.diagnostic.infoSign": ">>",
"coc.preferences.diagnostic.hintSign": ">>",

The strange thing is that the warning glyph shows up in the status bar correctly. Also, all glyphs show up correctly in the sign column in vim but they just got messed up somehow in the status bar.


This comment has been minimized.

Copy link

Char-Aznable commented Jan 10, 2019

I have tried the suggestion in #281 but it didn't help


This comment has been minimized.

Copy link

itchyny commented Jan 10, 2019

This seems to be an issue of coc.nvim so please report to the repository of coc.nvim. If you still think this is an issue of lightline, please paste the minimal vimrc, screenshots and the precise steps to reproduce the problem (so that anyone who does not know what coc.nvim is for can understand what the problem is and what the reporter expect).


This comment has been minimized.

Copy link

Char-Aznable commented Jan 10, 2019

Never mind. I found the problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment