Hello,

I absolutely love this color theme. However one issue I have with it is the comments color is a bit too dark, making the comments hardly visible.

Tweaking the comments color to a slighlty brighter color goes a long way IMHO (window on the bottom contains the tweak)

Now this is probably a matter of opinion :) Happy to make a PR if you think it is worth it

Hi, I'm new to vim and am trying to get your colorscheme to work in my terminal. I am using iTerm2. The colors don't seem to work for me though. I've tried everything I could find about colorschemes, but nothing seems to work. Below is a screenshot of what it looks like.

Any help with this is appreciated.

execute q:, q/, q? in nvim, symbol at the beginning of each line doesn't had the right color.

When using lazygit the cyan colors interfere with the visual selection in the unstaged changes panel.

I got this error everytime I try opening a file:
Error detected while processing /.vim/plugged/coc.nvim/plugin/coc.vim[458]..function 22_Hi[49]..22_AddAnsiGroups:
line 18:
E254: Cannot allocate color 0
E254: Cannot allocate color 0

This only happens with this colorscheme using other colorscheme doesn't show the error

Info

Right now, the default highlighting that comes with the vim plug doesn't do a great job doing the markdown (.md, for example) type files.

For reference, here is what we ended up going with (for now) for the atom syntax markdown:

Currently Shipped w/vim plug

Local vim updates

I can open a PR against the dev branch, if interested

Info

Threw together some additional (easier) ports, looking for feedback on inconsistencies/choices/etc or otherwise "addition to the main theme".

As mentioned in a previous issue, I am not too sure the layout of how y'all are aiming to get things added/maintained in the meantime, so if you want me to break these into separate issues/PRs/other, just let me know. Thanks!

The images here under the preview headers are just a single image from the repos for reference; in each repo, there will likely be additional images/GIFs that showcase that particular port.

DuckDuckGo

• Source code and installation can be found here: https://github.com/bigpick/spaceduck-duckduckgo

Preview

Slack

• Source code and installation can be found here: https://github.com/bigpick/spaceduck-slack

Preview

Google Chrome

Note: The upload to the google chrome store is still pending; I am assuming it will be approved, and I'll have the live link to the page in the Google Chrome Store in about a day or so - I'll update the README with it once I have it, but it has been submitted for official publication. https://chrome.google.com/webstore/detail/spaceduck-an-intergalacti/oagpdnaponfkenfojfkhjmkdeeamjpib

• Source code and installation can be found here: https://github.com/bigpick/spaceduck-chrome

Preview

zsh-syntax-highlighting

• Source code and installation can be found here: https://github.com/bigpick/spaceduck-zsh-syntax-highlighting

Preview

colorls

• Source code and installation can be found here: https://github.com/bigpick/spaceduck-colorls

Preview

Less of a low-hanging fruit as is a bit more involved, I am also working on an Atom-UI and Atom-syntax set of ports as well

Info

https://github.com/alecthomas/chroma/tree/master/styles

If you use Hugo to power a static site (which is common), you can take advantage of the syntax highlighter that ships with Hugo natively, Chroma.

For example, that is what I use on a given website, and it works nice and I find it better supported than using something else, and the list of supported built in languages/lexers is very large.

It would be great to get a Spaceduck theme added to the list of supported styles, so that one would have the ability to leverage spaceduck syntax highlighting on Hugo blogs/websites natively.

For reference; some implemented ones (see full list at initial URL)

• Dracula
• Nord
• Solarized dark

/assignTo me

Hey, I love the color scheme, but there are some issues with it when working with TypeScript / TypeScript React.

Here's some of the issues I've encountered:

• Keywords such as const and typeof don't get highlighted (default foreground color).
• Function keyword is highlighted in the same color as the name of the function.
• Function return type doesn't always get highlighted (JSX.Element in the screenshot).

Here's screenshots for comparison

Default

Spaceduck

It seems like the typescriptVariable / typescriptType / etc Vim values need to be linked to the correct definitions, however, I'm not sure how this works with the Estilo workflow.

I'm also concerned about the color on comments or HTML brackets, as they are quite dark and a bit difficult to read / see.
Perhaps there's something that can be done about this?

Hey, thanks for the great theme !
I made this spaceduck theme for duckduckgo (how ironic lol) but I am not sure if I should put it in the official repo (it may become too crowded) or in spaceduck-terminal (this one is for terminal ports only)

Here is how it looks :

to get it you need to navigate to the settings > click load settings on the right side > type spaceduck-ddg > save and exit.

Not sure if it’s a bug, but it looks too dark

I were just trying to use this plugin, because I do not like the | as vertical fillchars and have this issue.

Seems like it is related to the Spaceduck dev branch and StatusLine and StatusLineNC having the same values. I could fix it by changing line 250

call s:hi('StatusLineNC',     s:palette.bg,          s:palette.grey,       'reverse'  )

to

call s:hi('StatusLineNC',     s:palette.bg,          s:palette.grey,       'underline'  )

there is probably a better solution though.

Here's my screen shot, the keyword's color doesn't look like the screenshot.
e.g. const, document, and NERDTree icons.

Here's screen from spaceduck.

Change color in the middle of #if ... #endif (in C / CPP)

[example] #if 0 .... #end if --> comment color (as of now Foreground color [#ecf0c1] is displayed)

Thanks for this awesome Vim theme. 🙏

I find myself working in bright environment during the day and the current theme is hard to see properly when you have some light shining on your screen. Would you accept a light version of this theme? As Solarized has for example. I've never worked with Vim theme yet so I have no clue how such light version could be distributed or setup but if that's a contribution you'd accept I'd be happy to work on it and contribute.

Thank you.

Hi!

I'm not sure but is it OK?

it seems to me that the colors are somehow faded. Especially the code itself

thank you! :)

Great theme! Loved the font and want to make my setup look the same. Thanks

Change colors according to new changes in dev branch.

The icon is not showing I have copied your code from the README

      \'options' : {
      \  'theme' : 'spaceduck',
      \  'section_separators' : ['', ''],
      \  'component_separators' : ['', ''],
      \  'icons_enabled' : v:true,
      \},
      \'sections' : {
      \  'lualine_a' : [ ['mode', {'upper': v:true,},], ],
      \  'lualine_b' : [ ['branch', {'icon': '',}, ], ],
      \  'lualine_c' : [ ['filename', {'file_status': v:true,},], ],
      \  'lualine_x' : [ 'encoding', 'fileformat', 'filetype' ],
      \  'lualine_y' : [ 'progress' ],
      \  'lualine_z' : [ 'location'  ],
      \},
      \'inactive_sections' : {
      \  'lualine_a' : [  ],
      \  'lualine_b' : [  ],
      \  'lualine_c' : [ 'filename' ],
      \  'lualine_x' : [ 'location' ],
      \  'lualine_y' : [  ],
      \  'lualine_z' : [  ],
      \},
      \'extensions' : [ 'fzf' ],
      \}

  lua require("lualine").setup()

Basically, it messes up the cursorline in a lot of places. Obviously a minor thing, once we get that highlight function going :)

I recently ditched vim-airline due to its utter slowness for lightline.vim but there's no current spaceduck theme for it.

If anyone can make one for lightline, I'll immediately merge it with the dev branch.

Example: VSCode default color scheme

The text of my inactive splits is too dark

I could fix it by changing

let s:inactive1 = [ "#1b1c36", "#16172d", 234, 234 ]
let s:inactive2 = [ "#1b1c36", "#16172d", 234, 234 ]
let s:inactive3 = [ "#1b1c36", "#16172d", 234, 234 ]

to

let s:inactive1 = [ "#3b3c56", "#16172d", 234, 234 ]
let s:inactive2 = [ "#3b3c56", "#16172d", 234, 234 ]
let s:inactive3 = [ "#3b3c56", "#16172d", 234, 234 ]

Not sure if this is a Vim problem. Are the colors right in Neovim?

Handling error cases in JavaScript doesn't look that pleasant:

I've debated whether the Error() object even deserves to be red since it is actually the prudent, future-proofing developer who writes error handling. Maybe Error should be the Special color, SpaceduckPurple? Or we could just make the red color more pleasant to look at by making it brighter.

Also, why should throw be orange? I think it would be more fitting to be green like all other function calls such as return (which is what throw substitutes).

Info

Mirroring issue into the main source repo, for thoughts/tracking here.

See: bigpick/spaceduck-atom-syntax#2

After installing this plugin for vim, I noticed that some of the colors are not showing up like they should, going off by the screenshots posted in the repo. I also downloaded the VSCode version to compare it with my Vim and I saw a difference.

Here is a screenshot of how my vim looks (keep in mind for the color of the comments I modified it to be gray, but that is the only modification I did).

And something that is even more weird is that when I add the
if exists('+termguicolors') let &t_8f = "\<Esc>[38;2;%lu;%lu;%lum" let &t_8b = "\<Esc>[48;2;%lu;%lu;%lum" set termguicolors endif
code to my .vimrc the colors change even more. Here is a screenshot to show what I mean.

This might be some user error from my part, so any help will be appreciated.

Also I am using "VIM - Vi IMproved" version 8.2.2375 if that helps.

Not sure if others have faced it but on windows 3 elements were out of whack, or maybe cause I'm not using vim the scrollbars were ugly. Anyway I have attached the before and after fix screenshots along with the fix. Let me know if you can reproduce the issue, you can use the style to fix it.

Issue

Fixed

Info

If there was a general block of code that could be used for consistency across different ports, I think that'd be a good idea, to have at least somewhat of a basis to base appearance off of. Or, at the very least, so that each port has the same amount of demonstrated code/syntax highlighting.

I tried searching around for the code in the main repo's readme, but it seems like it must be private code/in a private repo somewhere. What do you think about replacing it with a screenshot of a new common block of code (and then also uploading that block of code(s) in a sample/ type folder as well)?

Down the road, could have multiple languages, etc.. but having at least one or two sizable chunks of common code that could be used across various ports would be nice imo.

Although @pineapplegiant and I have focused our efforts on JavaScript, TypeScript is a complete mess right now. I will, in the upcoming days, slowly push out changes to the dev branch to make TypeScript comparable to our JavaScript syntax highlighting is.

Currently there are four colors that are named after Purple, and this hinders development.

Suggestions are welcome for new names for the colors, for example, "Lavender" for the current "Purple" color.

Hi there! I really love this colorscheme - and so I want it everywhere.

It looks like in the README screenshot you use tmux and also have styled it with the spaceduck colors?

I took my best guess and what you are probably using. Maybe it could be added to the README?

set-option -g default-terminal "screen-256color"
set-option -g status-style bg='#30365f',fg='#16172d'
set-option -g window-status-current-style bg='#7a5ccc',fg='#ecf0c1'
set-option -g message-style bg='#7a5ccc',fg='#ecf0c1'
set-option -g message-command-style bg='#7a5ccc',fg='#ecf0c1'

It would be great if you could add support for kitty terminal. Thanks!

Screenshot:

Test code:

import sys
from random import choice

print("hello world!")

def func():
    try:
        a = {'foo': 'bar'}
    except:
        raise KeyError

class Foo:
    def __init__(self, words: list[str]) -> int:
        return len(words)

async def io():
    return await google()

Plugin:

python-syntax

I have some issues with the contours of the preview window of coq_nvim

The same issue happens with symbols-outline.nvim

I have the same issue with the color schemes rusticated and base16-seti, so I suppose the issue is related to the neovim part rather than the vim part.

Thanks in advance !

PS : I love this color scheme, thanks a lot for making it

Info

Heya! Been looking for something to get me away from my main themes (Dracula, snazzy, nord) from time to time, and I really think this colorscheme's palette looks great, while still being functional/able to be easily consumed esp wrt syntax (my main issue with nord). I'm hoping I can contribute some more ports/themes in my spare time, and really hope this theme gets the hype it deserves.

Issue: By default, the inactive colors as part of shipped colors of the vim-airline theme that come with the spaceduck repo are really hard to read:

Using #1b1c36 as the foreground against a #16172d background makes the text have almost no contrast:

I don't think changing the background would be the best move, so changing the foreground color seems to be the best option. Of the ones I tried, I think #30365F looked best:

let s:inactive1 = [ "#30365F", "#16172d", 234, 234 ]
let s:inactive2 = [ "#30365F", "#16172d", 234, 234 ]
let s:inactive3 = [ "#30365F", "#16172d", 234, 234 ]

... though, that said, I'm not sure I think the other colors of the airline bar look the best either, but that is likely just personal preference (and it expecting to match one of the screenshots of the other status bars at least in closeness, but does not)

1. how come the normal background for the bar is Dark Purple2 (#686f9a, which is one of the lighter colors) while most of the other status bars seem to be dark background colored (including the ones in the main screenshot of the repo)?
2. Using the Dark Purple2 as bg for the main parts, the foreground (which is just dark purple #30365F) is also really hard to read imo. If sticking with the dark purple2 background, cursor line #16172d or bg #0f111b seem like better choices imo. Though, I think the better option would being changing the background to be dark, and using lighter foreground coloring to stick with the feel of the theme overall more.
3. why use #000000 for foreground text where provided instead of just the background coloring, #0f111b?
4. I would also suggest once finalized, to get the theme added to the vim-airline-themes repo, too, for extra exposure. I think shipping the airline theme with the repo itself makes sense if the repo is specifically for vim, but if the intent is to have much more ports/etc available, I don't think it'd make sense to keep the contents in here. But I guess this gets more into the organizational/stylistic approach of how the theme is maintained, which probably is a bigger thing to talk about then just this specific part.

Hey first off love your work bro! Not enough kindness and love in the world these days, just wanted to start off with this.

But yeah, I ran the ./update.sh and it didn't move the lightline theme to the right place. I think you want to add this path in there:

/Users/$USER/.local/share/nvim/plugged/lightline.vim/autoload/lightline/colorscheme

Taking inspiration from Nord https://github.com/arcticicestudio/nord-vim/blob/develop/colors/nord.vim:

Think we should also add these comments before every plugin-specific highlight groups

" > HerringtonDarkholme/yats.vim

especially for JavaScript and Typescript since they require these excellent syntax plugins.

I also think we should add this information into the README.md. Oftentimes, after installing a new Vim color scheme and getting wrong colors, I just give up, when I could have just installed the right plugin that the color scheme wants you to use.

Hello, throughout the night I was trying to get colors for FZF preview untill I found out that it pretty much uses integrated terminal colors. After hours of googling, I found out that normal vim probably handles integrated terminal colors differently from neovim.

I wanted to create a PR, but I did not know how to quickly make it work with estilo, so I am just send a code snipped, which you could integrate somehow, if you think it's a good idea.

This is how I got it working.

It may require some tweaking, because it does not work with foreground and background I guess, so it differs from iTerm for example. But maybe I am still missing something.

let g:terminal_ansi_colors = [
        \ '#000000', '#e33400', '#5ccc96', '#b3a1e6', '#00a3cc', '#ce6f8f', '#7a5ccc', '#686f9a',
        \ '#686f9a', '#e33400', '#5ccc96', '#b3a1e6', '#00a3cc', '#ce6f8f', '#7a5ccc', '#ecf0c1']

Have a nice day!

Example (Nord theme):