Skip to content
This repository has been archived by the owner on Nov 22, 2022. It is now read-only.

The same grey colors #10

Closed
krnl0138 opened this issue Mar 26, 2019 · 5 comments
Closed

The same grey colors #10

krnl0138 opened this issue Mar 26, 2019 · 5 comments

Comments

@krnl0138
Copy link

I installed plugin via Plug as usual, functions are working properly, but every time I see the same greyish color output, despite all changes in options it stays the same.
No difference in vim and neovim.

What did I do wrong?

Neovim 0.3.4-2
gvim 8.1.0996-1
A messy vimrc file here: https://pastebin.com/U6CMfSST

@ferk6a
Copy link

ferk6a commented Mar 26, 2019

This plugin works using guifg. If you're working on a terminal, you have to use a terminal that supports true color and you also need to set termguicolors.

I think the author could make this clearer in the documentation, but that's about it, I'm pretty happy with the results myself:
image

@RRethy
Copy link
Owner

RRethy commented Mar 26, 2019

@fer22f is correct, you need :h termguicolors to be on. My bad for not documenting anywhere, I'll add it to README and docs.

@RRethy RRethy closed this as completed in 35e17c9 Mar 26, 2019
@RRethy
Copy link
Owner

RRethy commented Mar 27, 2019

Going to reopen this so that if anyone else has this issue they can see the comments.

@RRethy RRethy reopened this Mar 27, 2019
@crivotz
Copy link

crivotz commented Apr 5, 2019

My two cents
I use vim inside tmux with base16 shell
Enabling termguicolors I lost all my colorscheme, to solve I had to add the following lines:

" set Vim-specific sequences for RGB colors
let &t_8f = "\<Esc>[38;2;%lu;%lu;%lum"
let &t_8b = "\<Esc>[48;2;%lu;%lu;%lum"

@RRethy RRethy closed this as completed in a39b5ae Apr 19, 2019
@RRethy
Copy link
Owner

RRethy commented Aug 31, 2019

I just released v2 of vim-hexokinase. It's scrapes asynchronously and has 6 different methods for displaying the colours in a file!

To upgrade, run git pull && make hexokinase. For more information on migrating to v2, check out :h hexokinase-v1-migration. There are a few fully deprecated options (:h hexokinase-v1-deprecation) but almost everything has a v2 alternative. v1 will still work and can be forced by using :let g:Hexokinase_v2 = 0.

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

No branches or pull requests

4 participants