flazz / vim-colorschemes Goto Github PK

Please update jellybeans:
https://github.com/nanotech/jellybeans.vim
Last update of colorscheme just a few hours ago.

If I do a fresh git clone [email protected]:flazz/vim-colorschemes.git && cd vim-colorschemes && git status it shows me this.

On branch master
Your branch is up to date with 'origin/master'.

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

	modified:   colors/darkBlue.vim

no changes added to commit (use "git add" and/or "git commit -a")

I've tried the following with no success:

• git checkout -- colors/darkBlue.vim
• git stash && git fetch origin && git reset --hard origin/master
• git mv colors/darkBlue.vim colors/darkblue.vim

All fail.

Any idea why this is? It's borking my plugin manager every time I update.

When solarized applied, spellcheck doesn't seem to work. Any fixes for this?

.
mistake, i made a mistake in the windows.
the heat wave is harmful

closed

If I use colo brogrammer it does not work directly, but if I use colo playroom then colo brogrammer it works fine! Thanks :)

Is the VSCode dark theme available?
This theme, that is by defaults is the Dark Visual Studio theme json file

available here: https://github.com/Microsoft/vscode/blob/5b9ec15ce526decc5dd0488339e798f6bcb4ec46/extensions/theme-defaults/themes/dark_vs.json

Characters are left behind on the screen after the completion suggestions close. Originally thought this was an issue with YouCompleteMe or the vim builtin completion, but the issues are only reproducible with vim-colorschemes installed and active.

Random artifacts:

Filename completions:

I'm on macOS Mojave 10.14.6 and here's my vim --version output.

Thanks in advance for the help.

There's a really nice looking theme for Sublime called afterglow. Does anyone have the time & knows how to convert it to vim? I'd like to see it in vim-colorschemes. Thanks in advance!

[Solved]

Multiple color schemes are affected and changed by the terminal color scheme, like 0x7A69_dark. The text color changes with the terminal settings. Other schemes look almost identical and very similar to the terminal color scheme. Other schemes like C64 are unaffected.
E: Vim version 7.4, Ubuntu 16.04.03 and 16.04.01.

E2: Apparently some schemes are made for Gvim. Source: Fourth reply here https://stackoverflow.com/questions/4325682/vim-colorschemes-not-changing-background-color.

In my terminal i'm seeing the color schemes almost the same.

My .vimrc looks like this:

Syntax on
set t_Co=256

How can I fix this issue?

Hi, if I use gvim, the colorscheme works perfectly fine. If I use vim in lxterminal, it doesn't work at all. any ideas why? thanks.

Hello,

I've installed vim-colorschemes with Vundle. All color schemes are dropped into .vim/bundle/vim-colorschemes/colors.

When I drop colorscheme corn or any other colorscheme, I always get en error:

E185: Cannot find color scheme ...

Is that a bug or am I doing something wrong?

Heya. First of all want to sat thanks for such an amazing pack.

But lets now get to serious things. Rust language has a support in vim. And with the Tomorrow-Night theme I've came with several misunderstandings. First of all some thing that should be colored with different colors, are actually colored with same color.

Second weird thing is that if, for, while, loop etc. are colored same (or nearly same color) as text (variables).

If I install Tomorrow night theme from another source (which is kinda painful) i don't have this issues. And if I use other editor, with same theme, I don't have any Issues either. Any Suggestions?

And the theme itself is kinda different (but still OK)
See screenshots below:

vim:

VSCode:

Rustbook:

Because I'm kind of new to Vim, it wasn't really obvious for me how to change the color schemes. So I'd suggest to add the following to the readme:

To change the color scheme to e.g. Monokai, type the following in Vim

:colorscheme monokai

Can you add this colorscheme? : https://github.com/andreypopp/vim-colors-plain

I've noticed that the themes using an uppercased name are missing out on tab completion (unless uppercase letter is specified) or even just basic colorscheme name cycling. This would be an easy change but would force existing users to update their vimrc.

Please consider updating vividchalk from https://github.com/tpope/vim-vividchalk/blob/master/colors/vividchalk.vim. There are some minor changes related to CursorColumn that greatly improve its experience.

add https://github.com/gregsexton/Atom

I had some trouble getting pseudo transpareny to work in rxvt-unicode. So I edited line 288 in deus.vim. to read:

let bg = s:none

Now when I open vim it uses the terminal background (with pseudo transparency) however it also throws the following error:

Error detected while processing function <SNR>16_HL:
line 43:
E420: BG color unknown
E420: BG color unknown
E420: BG color unknown
Press Enter or type command to continue

Is there a proper way to do this? I was surprised to see how sophisticated the colors file is. I expected something much more simple.

I have followed the installation guide:

git submodule add [email protected]:flazz/vim-colorschemes.git bundle/colorschemes

But my terminal says:

Warning: Permanently added the RSA host key for IP address '192.30.252.131' to the list of known hosts.
Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights and the repository exists.
Clone of '[email protected]:flazz/vim-colorschemes.git' into submodule path 'bundle/colorschemes' failed

Hey all, first of all, thanks for the patience. There seems to be a large set of issues that revolves around the filename conflicting with some internal value or vim feature.

I think biggest challenge is that there are many flavors of this issue and many flavors of proposed solutions. Solving one issue may conflict with solving another.

Instead of modifying the scheme files to for any specific situation we start sharing a set of opt-in scripts to fix these things locally.

If any convergence happens we can work towards a better general case solution; if things stay diverged no harm done, the impact is a set of scripts and words in the readme. Thoughts?

Hi,

Can you provide the color scheme screenshots just like oh-my-zsh, that would be very nice.

Bests,
Michael

add chrishunt/color-schemes

could you add molokai colorscheme ?

I see a couple color-schemes I want that have not been added.

Would fork this to start to add those schemes if it is not being maintained.

Hi, im new to Vim / vim plugins / and also github.
so far i have installed few plugins through vundle and now I am trying to install flazz/vim-colorschemes.
when i run :PluginInstall, it asks me github username and password. After providing the password i get something as follows
fatal: https://github.com/flazz/vim-colourschemes.git/info/refs?service=git-upload-pack not found: did you run git update-server-info on the server?

need help plz.

colorscheme Benokai
Upon entering Vim no colors are applied. Just Black and white colors.
Same happens to some other schemes.

Hi there,

i´ve got an documentation improvement. Perhaps you can add a List of all themes with a Screenshot and some further theme information (256 colors, ...)

This would be great :)

Cu

Robin

Hi,
I am not sure why I am getting the following error:

pptp-212-201-79-219:.vim mypc$ git submodule add [email protected]:flazz/vim-colorschemes.git bundle/colorschemes
Cloning into 'bundle/colorschemes'...
Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
Clone of 'github.com:flazz/vim-colorschemes.git' into submodule path 'bundle/colorschemes' failed

any idea?
thanks

You already include the luna colorscheme but only the GUI version - in https://github.com/Pychimp/vim-luna the GUI and console versions of the colorscheme are in separate files (luna.vim and luna-term.vim) currently you only include luna.vim

This is the ultimate collection of color schemes. The selection can probably satisfy almost anyone. However, I feel that regardless of the aesthetic appeal of a particular color scheme, it should not have unexpected side effects. For example, changing the user's editor window size, font, messing with the editing buffer, etc. 3 color schemes failed the above test:

1. darkroom: messes up the current editing buffer by creating a new scratch buffer
2. potts: tries to set the font to 7x13 (very ugly font)
3. smyck: tries to change the linespace to 2 (many people prefer a tighter line space)

There're other color schemes that also have issues, like scala and ciscoacl, after using these schemes certain colors are stuck, that even if you change to another color scheme they won't get restored. But I feel at a minimum the editor content/window size should not change.

If you agree that these are issues that should be addressed, I can send a pull request with the changes.

One line in xcode.vim is causing an error when vim starts up.

let g:colors_name = "base16-{{scheme-slug}}"

After 90b2526, many colors of Tomorrow-Night were changed. The colors seem not to be included in the original Tomorrow-Night palette, so I thought that 90b2526 improperly updated Tomorro-Night.

before 90b2526:

after 90b2526:

NOTE:

• the source code in the above images is from vimcolors.com

Hi there,

Commit 613bd69 added a new darkBlue.vim scheme, but on Windows, which has a case-insensitive file-system, that conflicts with the existing darkblue.vim (note the lowercase "b").

I don't know if there's a better solution than this, but renaming that new one to darkblue3.vim would definitely be the simplest?

I think it would be cool if this project had a Wiki with screenshots for every theme.

Another idea is to also keep a table in the Wiki that displays whether a theme is supposed to work only on gui, gui and terminals or just terminals.

The file colors/yaml.vim is a syntax file, not a colorscheme.

The theme CandyPaper no longer has the same colour map. It looks like its switched places with CandyCode: if you run :colorscheme vim will report that CandyCode is the active colour scheme. If you set your colour scheme to CandyCode the colour map is roughly what CandyPaper used to be.

I enjoy having hundreds of colorschemes. i see lots of old PRs languishing. I propose my services as a co-maintainer.

However. I will be a very irresponsible maintainer, in that my plan will be to systematically merge all PRs without even the most basic of checks. I figure, if people can be bothered to submit a PR, we can merge it and ask questions later. YOLO.

I do use all the colorschemes myself, so I should spot any major problems before too long...

It would be nice if you could define releases. It is unclear what is stable and what is not.

At vim-pandoc-syntax, we've found that many colorschemes don't have explicit rules for the Conceal group, which creates this sort of issue (see the grey background in the first half of the text):

Checking on the contents of this repo, only a few colorschemes provide correct rules for Conceal: https://github.com/flazz/vim-colorschemes/search?q=Conceal&source=cc

I'm not sure this is the right place to raise this issue, but I thought it would be good to let you know.

We've found adding

hi link Conceal Operator

to the colorschemes works fine in our use-case, but a different rule might be needed in others.

Please add the Atom one colorscheme from here http://vimcolors.com/447/one/dark

It seems, that some of the provided colorschemes (in my case: Iceberg don't use the newest version of said colorscheme.

Here is the diff between the provided iceberg.vim and the one provided by the official repository.

What is the standard procedure to update colorschemes?

nothing here , as title said.

Hi,

Any chance you could sort the color schemes by color support?
For example, put all the 256-color schemes in one directory, and the 16-color schemes in another directory?

It would help people who have different terminals with different levels of color support to quickly find which themes they can apply.

Thanks!

a few colorschemes were downloaded as tarballs zip files or vbas, here is that list

i think the best way to resolve it is to fix it in vim.org

• royal_colorschemes.zip
• jellyx.vim.tar.gz
• neverland-vim-theme.tar.gz
• 285colors-with-az-menu.zip
• Mahewincs.tar.gz
• HiVim.tar.gz
• mimicpak.zip
• changingColor.vba
• colourscheme_bandit.vba
• darkdevel-1.1.2.zip
• _vimrc
• tabula.zip
• dw_colors.zip
• crt.zip
• all_colors.rar
• LoContrastColors.tar.gz
• vim_colors.tar.gz
• nightshade.tar.gz
• HHCS_D_1.3.tar.gz
• white.txt
• fluka-vim.tgz
• rainbow.ZIP
• zenburn.vba
• astronaut.tar.gz
• vimake-1.15.tar.gz
• maroloccio3-v0.1.0.png
• maroloccio2-0.1.0.png
• c16gui.zip
• HHCS_1.2.tar.gz
• xterm16-2.43.tbz2
• ColorSamplerPack.zip
• ColorSchemeMenuMaker.zip