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

Colors problem #29

Closed
nemanjan00 opened this issue Apr 13, 2017 · 10 comments

Comments

Projects
None yet
8 participants
@nemanjan00
Copy link

commented Apr 13, 2017

Hi, guys.

I spent days trying to fix this and am pulling my hair...

Any hints?

I am using urxvt (256 one), neovim and this theme...

My Vim config: https://github.com/nemanjan00/vim/blob/master/vimrc
My .Xresources: https://gist.github.com/16b0484a0281b873ef3e7bacae3da960

Also, I have set TERM to xterm-256color...

SS: http://i.imgur.com/bzXmcsN.png

@nemanjan00

This comment has been minimized.

Copy link
Author

commented Apr 13, 2017

Seams like it is not drawing parts of background. (at least to me)

@filipesf

This comment has been minimized.

Copy link

commented Apr 21, 2017

Mine looks slightly different as well. Though not that bad.

screen shot 2017-04-21 at 17 49 24

My guess is that I'm not using any GUI:

VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Apr 19 2017 09:57:52)
MacOS X (unix) version
Included patches: 1-567
Compiled by Homebrew
Huge version without GUI.  Features included (+) or not (-):
+acl             +file_in_path    +mouse_sgr       +tag_old_static
+arabic          +find_in_path    -mouse_sysmouse  -tag_any_white
+autocmd         +float           +mouse_urxvt     -tcl
-balloon_eval    +folding         +mouse_xterm     +termguicolors
-browse          -footer          +multi_byte      +terminfo
++builtin_terms  +fork()          +multi_lang      +termresponse
+byte_offset     -gettext         -mzscheme        +textobjects
+channel         -hangul_input    +netbeans_intg   +timers
+cindent         +iconv           +num64           +title
-clientserver    +insert_expand   +packages        -toolbar
+clipboard       +job             +path_extra      +user_commands
+cmdline_compl   +jumplist        +perl            +vertsplit
+cmdline_hist    +keymap          +persistent_undo +virtualedit
+cmdline_info    +lambda          +postscript      +visual
+comments        +langmap         +printer         +visualextra
+conceal         +libcall         +profile         +viminfo
+cryptv          +linebreak       +python          +vreplace
+cscope          +lispindent      -python3         +wildignore
+cursorbind      +listcmds        +quickfix        +wildmenu
+cursorshape     +localmap        +reltime         +windows
+dialog_con      -lua             +rightleft       +writebackup
+diff            +menu            +ruby            -X11
+digraphs        +mksession       +scrollbind      -xfontset
-dnd             +modify_fname    +signs           -xim
-ebcdic          +mouse           +smartindent     -xpm
+emacs_tags      -mouseshape      +startuptime     -xsmp
+eval            +mouse_dec       +statusline      -xterm_clipboard
+ex_extra        -mouse_gpm       -sun_workshop    -xterm_save
+extra_search    -mouse_jsbterm   +syntax
+farsi           +mouse_netterm   +tag_binary

Could it be the reason? I'm running Vim straight from iTerm2.

There's any way to enable vim to use GUI colours instead cterm?

In case someone need, here's my vimrc:
https://github.com/filipesf/dotfiles/blob/master/vim/vimrc

@spoike

This comment has been minimized.

Copy link

commented May 9, 2017

Updated the colorscheme today via Plug and got the same problem as @nemanjan00. I'm guessing fairly recent breaking change?

I'm using macvim without GUI.

@spoike

This comment has been minimized.

Copy link

commented May 9, 2017

Seems like this commit breaks it for me: 38d5c9b

ctermbg is set which causes weird background color artifacts (screenshot provided with cowsay from Startify):

image

Current hacky workaround for me is to set it to NONE after the colorscheme line:

colorscheme dracula
highlight Normal ctermbg=NONE

Problem with this workaround for me is that I have to reload my .vimrc file everytime I restart vim (since the highlight line seems to be ignored on startup for some reason). So I have to do this autocmd as well 😭:

autocmd BufEnter * :highlight Normal ctermbg=NONE ctermfg=NONE
@BourgeoisBear

This comment has been minimized.

Copy link

commented May 10, 2017

I'm not sure if I had the same problem, but for most terminals I've tried this with under Linux (xfce4-terminal, urxvt), the dracula theme did not work.

This fixed it for me:

Add set t_Co=256 before let g:colors_name = 'dracula' on line 21.

@zenorocha zenorocha referenced this issue May 11, 2017

Closed

Setting t_Co #229

@dsifford

This comment has been minimized.

Copy link
Contributor

commented May 16, 2017

System: Arch Linux
Terminal: urxvt

@spoike's solution of setting highlight Normal ctermbg=NONE after colorscheme worked for me.

@BourgeoisBear's solution did not.

@5t111111

This comment has been minimized.

Copy link
Contributor

commented May 17, 2017

I had the same problem and it was solved after setting either @spoike's solution or reverting 38d5c9b .

@enosair

This comment has been minimized.

Copy link

commented Nov 3, 2017

I had the same issue as @filipesf.
Finally I found that I forgot to enable truecolor support in vim.

Add set termguicolors into my vimrc did the trick.

@nemanjan00

This comment has been minimized.

Copy link
Author

commented Nov 3, 2017

Shit. 4 years of using Vim and I did not figure it out until now. :D

@cc9226b77c

This comment has been minimized.

Copy link

commented Apr 24, 2018

@enosair Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.