Why hold a competition for colourscheme when it obviously should be Jellybeans?
You spelled Zenburn incorrectly.
NeoVim Newsletter Issue #2
11–17 of 17 posts
Re: NeoVim Newsletter Issue #2
#12Why hold a competition for colourscheme when it obviously should be Jellybeans?
You may have spelled xoria256 wrong there.
Re: NeoVim Newsletter Issue #2
#13Why hold a competition for colourscheme when it obviously should be Jellybeans?
You may have spelled xoria256 wrong there.
JellyX: A delicious collision of Jellybeans and Xoria256
Re: NeoVim Newsletter Issue #2
#14Why hold a competition for colourscheme when it obviously should be Jellybeans?
> Why hold a competition for colourscheme [...]?
Re: NeoVim Newsletter Issue #2
#15Why hold a competition for colourscheme when it obviously should be Jellybeans?
[deleted]
Re: NeoVim Newsletter Issue #2
#16I am impressed by how fast Neovim is coming along. I wonder how much faster it would progress if there were more donations? Perhaps those that use it everyday in their jobs or for personal use could donate the cost of the text editor that (Neo)Vim replaced, e.g. Sublime Text?
The fact that the money seems to be being spread around seems to be working well for the project.
Re: NeoVim Newsletter Issue #2
#17The newsletters and general strategy seem great. I was concerned at first that this was a cranky contributor that decided to take his toys and go somewhere else for some superficial feature. After reading the first few updates it's clear that they're initially concerned with the basic foundation of the app (e.g. refactoring, modernization, and testing), which is wildly at odds for a superficial vanity project. I came away thinking that they really love the editor and have its best interests at heart for a modern implementation. Good luck to them!