freeo / vim-kalisi Goto Github PK

After following the Vundle section in the Installation instructions I got the following error:

Error detected while processing ~/.vimrc:
line  218:
E185: Cannot find color scheme 'kalisi'
Press ENTER or type command to continue

I looked at various search result for these errors before finding the answer in http://stackoverflow.com/questions/8452779/vim-vundle-colorschemes-vimrc which is that the colorscheme kalisi and following lines need to come after the call vundle#end() line in your vimrc. I'm not sure if that's common knowledge in the vim community, but for new vim users it would be nice if the Installation section mentioned this.

This is probably one of the best vim themes (after solarized) so far I've used, love it, and that's why it is so painful I see it gone after a spf13 git pull update.

I use spf13's vim wholesale configuration solution and month ago I added the "Bundle freeo/vim-kalisi' to the .vimrc.bundles.local (the local one that I can add my own bundles), it works like a charm. But today, when I did a git pull from .spf13-vim-3 (which contains the symlink target of .vim), this theme no longer works. If you just install a new spf13 vim and add this theme, it should reflect what I described as well. I hope you or someone can take a look and see what might be the cause. I'd love to see it back. :) Thanks!

Take python, for example, where def, pass, and None all look the same.

(vim's default is awful.)

This may be a result of my protanomaly, but I have great difficulty distinguishing visual mode-highlighted text in the light theme from the background color.

In the dark theme, the difference is more apparent because of the more obviously different hue of the background color.

If anyone else is having this problem, I imagine that it could be fixed by slightly increasing the contrast of the visual-mode color in the light theme. Of course, if this is just a result of my vision, I'm sure I could tweak a personal fork to suit instead of having the official theme changed. Thanks!

Since a few days ago, I see these annoying markers at the end of every line.

It gets fixed when doing hi NonText NONE or commenting out the line that touches the NonText group in the kalisi.vim file.

Since I'm tracking neovim's master and there hasn't been any changes in this plugin recently, I'm guessing this is a compatibility issue with neovim.

The workaround is good enough for me, but I thought I would share this through an issue, in case it can be fixed or the workaround can help others.

Is there any plan to support true color option?
If you claim "with neovim in mind", so neovim has following option for enabling true color:
set termguicolors

Hello, I like this colorscheme very much. To better understand a problem here's a screen (try any XML you have):

The different colors at opening and closing tags.

I suggest that you define a gradient of colors for quotations in e-mails. Example:
https://github.com/jalvesaq/southernlights/blob/master/colors/southernlights.vim#L122-127

I'm using Konsole and I really like a transparent background. In order to have the background transparent I have to set the background color to 0:

-    hi Normal ctermbg=238 ctermfg=252
+    hi Normal ctermbg=0 ctermfg=252                                                                       

Maybe, you can include an option or sth like that for you color scheme?

It is especially annoying for those of us who keep 'list' option always on to distinguish tabs. Toning it down a bit would help, or even implementing a variable to lower the contrast, like in solarized or gruvbox colorschemes.

Here's an example of making it less annoying:

diff --git a/colors/kalisi.vim b/colors/kalisi.vim
index 730567c..f451784 100644
--- a/colors/kalisi.vim
+++ b/colors/kalisi.vim
@@ -250,7 +250,7 @@ if &background == "dark"
     hi Typedef ctermfg=72
     hi Special ctermfg=194 cterm=none
     hi SpecialChar ctermfg=69 cterm=none
-    hi SpecialKey ctermbg=236 ctermfg=194 cterm=bold
+    hi SpecialKey ctermbg=238 ctermfg=240
     hi Tag cterm=bold ctermfg=39
     hi Delimiter ctermfg=104
     hi SpecialComment cterm=bold ctermfg=67

Screenshots:
before patch - http://i.imgur.com/6IJJGPe.png
after patch - http://i.imgur.com/rTfDcTo.png

see vim-airline/vim-airline#624 for the thread of this problem

Not sure if this is an issue only for me, but trying to read the comments on screenshots with the dark version of kalisi results in significant eye strain / slight physical pain. This could probably be fixed by increasing contrast between background and the comments.

(Note: I've used a lot of dark color schemes but I don't often encounter this kind of problem; I don't have any sight-related ilnesses I know of)

If you like, you could add a short note to the readme.md notifying users of your colorscheme how to enable italic comments if their terminal emulator supports it. They just need to add one line to their .vimrc/init.vim file.

For nvim:

colorscheme kalisi
highlight Comment gui=italic

For Vim:

colorscheme kalisi
highlight Comment cterm=italic

Works for me inside gnome-terminal with tmux and neovim/Vim. To test if your terminal is configured properly to display italics I think you can use

$ echo `tput sitm`test`tput ritm`

In case of a good configuration it should return the word "test" in italic.