srcery-colors/srcery-vim

Srcery is a dark color scheme with clearly defined contrasting colors and a slightly earthy tone.

srcery-vim's Issues

Support for Travis CI

Hi,

Got the idea for this after I saw this. This uses the vint package to lint (no pun intended).

Testing it here on my own fork.

.travis.yml

# vim-srcery .travis.yml

language: python

install:
  - pip install vim-vint

script:
  - vint --verbose --stat $(find . -type f -name '*.vim')

README bug

The directory of Vim 8's native support for plugins should be ~/.vim/pack instead of ~/.vim/plug. Please correct it in the README.

Cannot find color scheme 'srcery'

Hi, before I ask my question, I just wanted to say thanks for this color scheme. I really like it!

My problem is that Vim can't find the color scheme. I have just recently been trying to learn more about Vim, so this may just be an error due to my lack of experience with Vim.

I am using vim-plug to install it. According to :PlugStatus, srcery-vim is installed successfully. Then, I type :color srcery, and it seems to change the color scheme correctly. Since I want srcery to be my default color scheme, I put colorscheme srcery in my .vimrc file. I save and quit. When I reopen the file I am presented with the error.

Thanks for any help.

Rust operator highlight forces background color

I use treesitter-context with neovim and have noticed that the background color of operator characters in the context box is wrong:

Rust.vim over at neovim repository links rustOperator to Operator which is itself linked to Normal here, which has background color set by default. So that probably explains why Rust operators in particular are colored incorrectly. I'm not sure if any other language has a similar issue, C and C++ seem to be alright.

Simply adding something like hi! link rustOperator SrceryWhite in rust.vim makes it all look good.

So anyway, would be nice to have it tweaked. Cheers.

Function names aren't colored

As the title states, function names in C and C++ are left white whilst they should be yellow.

I've checked the installed vimscript file and, indeed, function names are set to be yellow.

Using: Neovim 0.7.2

search result highlight

hello, how can I change the search result (using /), it color is weak, sometime I can't see result clear.

Does the color scheme fully support treesitter

Hello,

I really like this color scheme. Does it support treesitter now? Thank you.

Alternative to underlined text

Hi! A nice theme, thank you!

I wanted to give it a try but I had an issue. By default, spelling errors are underlined with blue curly line(in my GUI frontend app it looks like a blue straight line), and it is hard to notice. At the same time, HTTP links with straight red underline were easy to see at a glance.

I tried to disable underline with g:srcery_underline = 0 but it made things much worse: it removed any signs of incorrect spelling.

As I see, the colorscheme marks all spelling errors with call s:HL('SpellBad', s:none, s:none, s:undercurl, s:blue), in case of disabled underline it becomes call s:HL('SpellBad', s:none, s:none, "", s:blue). Could you add an alternative way to highlight spelling errors?

Color column

Please, add a default color for vim colorcolumn option, for example

highlight ColorColumn ctermbg=8 guibg=#2D2C29

Terminal.app doesn't work on double-click in El Capitan 10.11.6

I got the "...PowerPC applications are no longer supported" message on double-click. Renamed the file to have a .terminal extension then opened it without issue. Nice colorscheme. 👍🏾

background is washed out in terminal vim

Hi, the theme looks great with the GUI MacVim. But when I use it for terminal vim the background seems to not be true black but is some shade of gray, which gives it a washed out, low contrast look. Any ideas why this is?

Visual selection doesn't highlight last character in gvim

First of all: I love, love, LOVE this colorscheme!

But a minor gripe - if I'm selecting in visual mode (or with the mouse), the last character of the selection doesn't get highlighted. Which mean that I'm actually selecting on character extra than it appears.

So for example if the word is 'appears', and I've highlighted up to the 'r', the 's' is actually selected too.

Not a huge issue, but big enough to be annoying.

Thanks again for such an awesome colorscheme!

Customizable xterm colors

It's nice that the 24-bit colors are customizable through globals. I'm trying to override the color scheme with a light palette and while the 16 base colors are inherited from the terminal, the oranges and xgrays are pretty much hard coded:

srcery-vim/autoload/srcery.vim

Lines 192 to 201 in 8ea4c4f

	" xterm colors
	let g:srcery#palette.orange = [g:srcery_orange, 202]
	let g:srcery#palette.bright_orange = [g:srcery_bright_orange, 208]
	let g:srcery#palette.hard_black = [g:srcery_hard_black, 233]
	let g:srcery#palette.xgray1 = [g:srcery_xgray1, 235]
	let g:srcery#palette.xgray2 = [g:srcery_xgray2, 236]
	let g:srcery#palette.xgray3 = [g:srcery_xgray3, 237]
	let g:srcery#palette.xgray4 = [g:srcery_xgray4, 238]
	let g:srcery#palette.xgray5 = [g:srcery_xgray5, 239]
	let g:srcery#palette.xgray6 = [g:srcery_xgray6, 240]

Are you open to supporting 8-bit color override?

errors loading

hi,

I love Srcery! Having some issues recently though.

On my end, commit 34c87e4 works without issue from ~/.vim/pack/plugin/opt/srcery-vim or ~/.vim/pack/plugin/start/srcery-vim.

Checking out the commit after that (27d66bc) I get a bunch of errors like this:

line  240:
E121: Undefined variable: g:srcery_bg_passthrough
E15: Invalid expression: g:srcery_bg_passthrough == 1 && !has('gui_running')
line  261:
E121: Undefined variable: s:bright_white
E116: Invalid arguments for function <SNR>3_HL
line  275:
E121: Undefined variable: s:bright_black
E116: Invalid arguments for function <SNR>3_HL

I'm testing this with a minimal .vimrc:

colorscheme srcery

nvim doesn't seem to have this issue, with a minimal .config/nvim/init.vim:

set runtimepath^=~/.vim runtimepath+=~/.vim/after
let &packpath = &runtimepath
source ~/.vimrc

Though it only works if using ~/.vim/pack/plugin/start/srcery-vim.

I've never had a problem until I pulled from github today and received these errors.

nvim version: 0.8.1
vim version: VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Jan 14 2021 20:35:46)
(this is on macos)

(Maybe I should forget about vim and stick to nvim)

Thanks,
matt

Manual install?

I assume manual install is no longer supported? I'm getting a bunch of undefined variable errors on startup.

Wrong highlighting in Telescope preview window

As is seen the picture, the C function names in the preview panel shouldn't be using the white color, but the bright-white color.

Color scheme doesn't work with Guake terminal

Hi,

first of all, thank you for creating the srcery colorscheme. It looks quite awesome.

However, even after executing the guake.sh script there seems to be a problem with the Guake terminal colors which can be seen here:

On my Gnome terminal it works as expected, if the gnome_terminal.sh has been executed and the profile srcery is selected:

Any idea what's causing this?

Mismatching background color on embedded vim terminal

If you open a terminal inside vim using for example :vert term or :tab term you will see that the background colors mismatch:

This does not happen with themes such as tokyonight.

Preparation for repo cleanup

I preparation for removing all images from the git history for this repo using BFG, I thought I'd start an issue where we could compile other possible changes and pitfalls since we're effectively rewriting the history.

• Remove images
• Notify about rewrite, plugin users probably need delete repo and clone anew

Please add anything else as comments.

For the reasoning behind this change, I noticed a few days ago while moving assets to a separate repo srcery-vim took up a whopping 15M of space, which is unacceptable I think. This is due to assets being tracked for a long time and is contained in the git history.

I'm still very wary about doing this, and any and all input concerning this is welcome.

Background color of your theme looks strange for me

What's wrong here?

Gray color is unclear with black terminal background

Hello!
Thank you for such a wonderful colorscheme!

After the last commits I have encountered with a small issue:
Sections like inline comments, shebangs, etc. in the source code looks too dark to my eyes.

Examples:

Environment:
Editor: NeoVIM: v0.4.3.
Terminal: kitty v0.14.2

Not sure that this is an issue for a lot of people but for me it is crucial.
May you please tell me how I can fix this?
Thanks for reading!

No contrast on floating windows spawned by nvim-lspconfig

Hello!

The latest commit basically made floating windows have the same background as normal windows.

Before:

Now:

nvim-lspconfig by default only adds some padding to the floating window, so it becomes difficult to discern them from normal windows if they all have the same background.

In other colorschemes (gruvbox, rose-pine) floating windows have a visibly different background.

Was it the intention to change that?

Support Lualine

I've ported Lightline's colorscheme to Lualine. It consists of a single lua file at the following path, relative to srcery's:
./lua/lualine/themes/srcery.lua
I've tested that adding the luafile doesn't interfere with vim.
Since this plugin is all in vimscript, I wanted to ask before opening a PR.

ruby var and def...end same has same color

Is it correct ?

Colorscheme applied inconsistently

Hello.

I've been recently configuring syntax highlighting and noticed there are some inconsistencies depending on when the colorscheme is set. It seems to happen only with srcery specifically.

In Vim 8.2.2121 with the most basic config:

set number
set tabstop=4
set shiftwidth=4
set expandtab
set nowrap

packadd! srcery-vim
colorscheme srcery

I get the following highlights in a C file:

If I call colorscheme srcery in the editor AFTER opening the C file the highlights change.

I get the same behavior in Neovim 0.10 with only srcery-vim installed.

Some other filetypes are affected, netrw, for instance.

Font name in the screenshot

May I know what font you are using in the screenshot?

It doesn't support neovim terminal mode.

NeoVim will apparently rewrite color commands, see here. Srcery should have something similar.

Italics not working in gnome-terminal

I'm using Vim 8.1 with Gnome Terminal 3.28.

While writing markdown and using a different colorscheme, italics appear properly. Srcery, with the proper option set (let g:srcery_italic = 1), will conceal the syntax but font does not italicize. Bold works, however.

Please let me know if I can provide any more information!

Support for vim-indent-guides

Tried to add some basic colors to indent guide. Thoughts? Disregard the flashing red error, have fixed it ;)

Based on xgrey2 & xgrey3.

Underline does not work, works fine with other colorschemes

Expected behaviour

When using a colorscheme such as solarized, my coc.nvim-plugin underlines language errors correctly

Actual behaviour

Srcery fails to display the underline.

What I tried

I played around with g:srcery_hard_black_terminal_bg, g:srcery_underline and g:srcery_undercurl. For the moment, I use g:srcery_guisp_fallback but this is not a "real" workaround.

System details

I use konsole as terminal emulator.
I use vim 8.2.5172.

Offer to help

If you need it, I can provide several versions of a .vimrc that may reproduce this behaviour. If needed, I can also try to compare this sourcecode with the sourcecode of the solarized project to see what is wrong.

Support for vim-airline, somewhat working added with post

Hi,

Switched today to srcery, and I fell in love the colors. But I needed support for vim-airline.
Just wanted to share my take on a vim-airline theme for people to build upon.

As shown, some parts are not complete yet. Specially the inactive part is the same as the highlight bar and normal bar.

" srcery airline
" vim: expandtab shiftwidth=2 tabstop=2 :

" Palette {{{

let s:black          = [ '#1C1B19',   0 ]
let s:red            = [ '#EF2F27',   1 ]
let s:green          = [ '#519F50',   2 ]
let s:yellow         = [ '#FBB829',   3 ]
let s:blue           = [ '#2C78BF',   4 ]
let s:magenta        = [ '#E02C6D',   5 ]
let s:cyan           = [ '#0AAEB3',   6 ]
let s:white          = [ '#918175',   7 ]
let s:bright_black   = [ '#2D2C29',   8 ]
let s:bright_red     = [ '#F75341',   9 ]
let s:bright_green   = [ '#98BC37',  10 ]
let s:bright_yellow  = [ '#FED06E',  11 ]
let s:bright_blue    = [ '#68A8E4',  12 ]
let s:bright_magenta = [ '#FF5C8F',  13 ]
let s:bright_cyan    = [ '#53FDE9',  14 ]
let s:bright_white   = [ '#FCE8C3',  15 ]

" xterm colors
let s:orange         = [ '#d75f00', 166 ]
let s:bright_orange  = [ '#FF8700', 208 ]
let s:hard_black     = [ '#121212', 233 ]
let s:xgray1         = [ '#262626', 235 ]
let s:xgray2         = [ '#303030', 236 ]
let s:xgray3         = [ '#3A3A3A', 237 ]
let s:xgray4         = [ '#444444', 238 ]
let s:xgray5         = [ '#4E4E4E', 239 ]

" }}}

let g:airline#themes#srcery#palette = {}
let s:modified = { 'airline_c': [ '#ffb964', '', 215, '', '' ] }

" Normal mode
let s:N1 = [ s:bright_white[0] , s:xgray4[0] , s:bright_white[1] , s:xgray4[1] ]
let s:N2 = [ s:bright_white[0] , s:xgray2[0] , s:bright_white[1] , s:xgray2[1] ]
let s:N3 = [ s:bright_white[0] , s:bright_black[0] , s:bright_white[1] , s:bright_black[1] ]
let g:airline#themes#srcery#palette.normal = airline#themes#generate_color_map(s:N1, s:N2, s:N3)
"let g:airline#themes#srcery#palette.normal_modified = s:modified

" Insert mode
let s:I1 = [ s:black[0] , s:bright_white[0] , s:black[1] , s:bright_white[1] ]
let s:I2 = [ s:black[0] , s:white[0] , s:black[1] , s:white[1] ]
let s:I3 = [ s:bright_white[0] , s:bright_black[0] , s:bright_white[1] , s:bright_black[1] ]
let g:airline#themes#srcery#palette.insert = airline#themes#generate_color_map(s:I1, s:I2, s:I3)
"let g:airline#themes#srcery#palette.insert_modified = s:modified

"" Visual mode
let s:V1 = [ s:black[0] , s:cyan[0] , s:black[1] , s:cyan[1] ]
let s:V2 = [ s:bright_white[0] , s:xgray4[0] , s:bright_white[1] , s:xgray4[1] ]
let s:V3 = [ s:bright_white[0] , s:bright_black[0] , s:bright_white[1] , s:bright_black[1] ]
let g:airline#themes#srcery#palette.visual = airline#themes#generate_color_map(s:V1, s:V2, s:V3)
"let g:airline#themes#srcery#palette.visual_modified = s:modified

"" Replace mode
let s:R1 = [ s:bright_white[0] , s:bright_red[0] , s:bright_white[1], s:bright_red[1] ]
let s:R2 = [ s:black[0] , s:white[0] , s:black[1], s:white[1] ]
let s:R3 = [ s:bright_white[0] , s:bright_black[0] , s:bright_white[1], s:bright_black[1] ]
let g:airline#themes#srcery#palette.replace = airline#themes#generate_color_map(s:R1, s:R2, s:R3)
"let g:airline#themes#srcery#palette.replace_modified = s:modified

"" Inactive mode
let s:IN1 = [ s:white[0] , s:bright_black[0] , s:white[1] , s:bright_black[1] ]
let s:IN2 = [ s:white[0] , s:bright_black[0] , s:white[1] , s:bright_black[1] ]
let s:IN3 = [ s:xgray5[0] , s:bright_black[0] , s:xgray5[1] , s:bright_black[1] ]
let g:airline#themes#srcery#palette.inactive = airline#themes#generate_color_map(s:IN1, s:IN2, s:IN3)
"let g:airline#themes#srcery#palette.inactive_modified = s:modified

How can I set the `ASCII` colors ?

Is it as variables on the ~/.bashrc ? 🤔

I am running mintty on windows. (Running arch linux in vagrant if that helps)

---

In case you wonder I code on this machine in windows 👇

https://github.com/cabaalexander/devagrant

Allow to use status configurations stand alone?

Hi. I really like the lightline colorscheme provided here and wished to use it standalone with other colorschemes, but seems the way it's provided makes it only work when the srcery colorscheme is loaded, it can't work with other colorschemes.

Lua port?

@roosta I was thinking about making a lua port of srcery as a first plugin. But I wanted to ask your opinion, since I have some doubts:

1. Is there actually any demand for this?
2. Would you like for srcery to remain a single, cross-compatible plugin?
3. Would an eventual port officially become part of srcery-colors?

Undercurls stopped working

As the title says, undercurls have stopped working. I think this has been going on for a very long time, but I didn't notice it because in the last year I haven't been using nvim a lot. I'm using the 1.0.0 release, which I modified to make the lsp highlight groups use undercurl, instead of underline (I think that setting the undercurl variable didn't work):

call s:HL('DiagnosticUnderlineError', s:bright_red, s:none, s:undercurl)
call s:HL('DiagnosticUnderlineWarn', s:bright_yellow, s:none, s:undercurl)
call s:HL('DiagnosticUnderlineInfo', s:bright_green, s:none, s:undercurl)
call s:HL('DiagnosticUnderlineHint', s:bright_cyan, s:none, s:undercurl)

I'm pretty sure this worked. Has Neovim changed something with respect to the Lsp Highlight groups?

g:srcery_bg setting is not properly explained

Hi, i've just updated the plugin to the latest version through Vim-plug and noticed that g:srcery_bg_passthrough is no longer a thing now. I've tried setting the value of g:srcery_bg to NONE as the readme explains but errors keep showing up. Later after minutes of trial and error discovered that to achieve the same transparency as before it had to be set to ['NONE', 'NONE'].

I feel like it could have been explained better in the plugin's readme or help files, since it is rather unintuitive for those who don't know much about vimscript!

Thanks for the awesome colorscheme :)

Tag latest release and upload to vim.org

Not sure how many people use that site for plugins anymore, but might be worth drafting a new version and uploading it. Haven't done so in ages.

Possible missing treesitter support for italic, bold, italic, underline and strikethrough

Hello,

first of all I would like to thank you for the amazing color scheme, it is my default one since many years on all my machines.

I am a neovim user and I started using the neorg plugin for note taking. This plugin has the possibility to style text as bold, italic, underline and strikethrough. Sadly, I discovered that those text decorations are not working with srcery. I opened the same file containing the decorations using the kanagawa color scheme and they displayed correctly. This suggests me that the problem may be with srcery. I don't know much about color schemes in vim/neovim but I know that neorg uses Treesitter extensively and for this reason I suppose the lack of decorations is tied to the missing support of some part of it.

I don't know if it would be of any help, but neorg defines the highlighting of text decorations here and they correspond on the values that I see in neovim when I invoke :Inspect on the corresponding decorated word.

For information, I am using neovim 0.9.5-2 and the latest version of both neorg and srcery. I am using srcery with the default configuration except for the srcery_italic variable which I have set to 1.

I understand that this might be a niche user-case and that you might not have neorg nor neovim installed and I would be happy to do anything to help identify the problem.

Thank you in advance!

transparent background, lightline, and certain terminals

Found an issue where if transparent background is enabled, and running termite w/o tmux, the lightline normal colors are not applied until the config is re-sourced.

It works correctly in urxvt, and I've tried gnome terminal and there the issue is present.
The weird thing is that it only happens sometimes, not every time vim is launched.

It works as expected in tmux, and seeing as the only usecase for transparent background involves tmux this isn't a huge issue but annoying none the less.

I do not know how this could be fixed though, but I'll leave this issue here if anyone else experience the same issue.

AirlineTheme not being detected

The Airline theme isn't being detected when using this colorscheme so vim/neovim just uses the default airline theme. Perhaps it's the package management system i'm using? I'm using minpac, which just uses the built-in package management introduced in vim 8 so ideally this would be a supported configuration. I'm using vim/neovim in iterm 2 on macos. Let me know if there's any other info I can provide.

Neovim 0.10.0 Update Breaks Highlight Groups

With the new update to Neovim, 0.10.0, some changes to highlighting groups have caused colors to switch roles, some to turn completely white, etc.

I've personally seen this while using Golang highlighting, both with and without Treesitter.

The related patch notes can be found here:

https://neovim.io/doc/user/news-0.10.html

These Nvim specific highlight groups are now defined in a meaningfully different way and might need an update:
[hl-FloatBorder](https://neovim.io/doc/user/syntax.html#hl-FloatBorder) is linked to [hl-NormalFloat](https://neovim.io/doc/user/syntax.html#hl-NormalFloat) instead of [hl-WinSeparator](https://neovim.io/doc/user/syntax.html#hl-WinSeparator).
[hl-NormalFloat](https://neovim.io/doc/user/syntax.html#hl-NormalFloat) is not linked to [hl-Pmenu](https://neovim.io/doc/user/syntax.html#hl-Pmenu).
[hl-WinBar](https://neovim.io/doc/user/syntax.html#hl-WinBar) has different background.
[hl-WinBarNC](https://neovim.io/doc/user/syntax.html#hl-WinBarNC) is similar to [hl-WinBar](https://neovim.io/doc/user/syntax.html#hl-WinBar) but not bold.
[hl-WinSeparator](https://neovim.io/doc/user/syntax.html#hl-WinSeparator) is linked to [hl-Normal](https://neovim.io/doc/user/syntax.html#hl-Normal) instead of [hl-VertSplit](https://neovim.io/doc/user/deprecated.html#hl-VertSplit).
This also might result into some color schemes looking differently due to them relying on implicit assumptions about how highlight groups are defined by default. To account for this, define all attributes of highlight groups explicitly. Alternatively, use :colorscheme vim or :source $VIMRUNTIME/colors/vim.lua to restore previous definitions.

There's a work-around listed, but it doesn't seem to have any effect for me. A fixing update would be appreciated!

[Color choice] Orange color looks out of place

The current orange color doesn't seem to fit the overall vivid style. I suggest to change from xterm color 166 to 202 as followed (the upper line uses the new 202):

I also notice that green and blue doesn't have the relative luminance (seems to be darker than other ones).

Colours come out with when running in NeoVim with termguicolors.

For some reason, when using NeoVim, and having set termguicolors enabled, the colors don't come out right. Here's what I mean:

This is in NeoVim, with notermguicolors set. Looks as it should.

This is in NeoVim, with termguicolors set. Looks slightly wrong. Note especially the reddish colour of the "bright_white".

gallery

getting error when setting colerscheme

Error detected while processing /home/username/.config/nvim/colors/srcery.vim:
line  201:
E121: Undefined variable: g:srcey_bright_magenta
E15: Invalid expression: [g:srcey_bright_magenta, 13]
line  317:
E121: Undefined variable: s:bright_magenta
E116: Invalid arguments for function <SNR>23_HL
line  357:
E121: Undefined variable: s:bright_magenta
E15: Invalid expression: s:bright_magenta[0]
line  427:
E121: Undefined variable: s:bright_magenta
E116: Invalid arguments for function <SNR>23_HL
Press ENTER or type command to continue

Move functions into helper script