vim-burnttoast256
onedark.vim
Our great sponsors
| vim-burnttoast256 | onedark.vim | |
|---|---|---|
| 1 | 30 | |
| 2 | 3,847 | |
| - | - | |
| 2.6 | 2.5 | |
| almost 3 years ago | 7 months ago | |
| Python | Vim Script | |
| - | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
vim-burnttoast256
-
Whats your favourite colorscheme in Vim/NeoVim?
[burnttoast](https://github.com/quantum-omega/vim-burnttoast256)
onedark.vim
-
Widely supported themes (other than gruvbox)
Onedark has been solid so far for me
-
How to highlight text other than keywords.
As you can see only the langauge keywords are being highlighted but not function and variable names. I am using onedark and coc.nvim.
- [Noob] Need help to install a theme
- Taking the tabline to a new level, without plugins!
-
Neovim: Plugins to get started
Github: joshdick/onedark.vim
-
coc.nvim popum menu doesn't highlight line anymore
It turns out this was an issue with my theme, onedark.vim, which was out of date due to some broken configuration somewhere. I reinstalled it with vim-plug and read the README. I learned that my terminal support truecolor, so I turned it on for onedark. That fixed the problem. There's no highlight in 256-color mode, but the highlight works fine in truecolor mode. Strange.
-
Whats your favourite colorscheme in Vim/NeoVim?
ful1e5/onedark.nvim is completely written in Lua which means it loads way faster. It also supports Treesitter which provides way better syntax highlighting, which dick/onedark.vim doesn't. Lastly, my favourite feature is that it allows you to override/create highlight group configs and pass to the plugin before loading the colorscheme which makes customizing highlight groups super easy (and I would guess faster as well?) compared to calling highlight a bunch of times in your config. Here's What my configuration of it looks like if you're curious.
-
Strange margin in Konsole using vim / nvim
something similar to this but I am using nvim
-
[Arch] Alacritty not displaying truecolor
I know it's not strictly Linux related but I'm not sure where else to post this, sorry. I have been in the process of configuring my setup including Alacritty but the colors for it look off. I'm using the one dark color scheme but the colors in the terminal don't quite match, specifically the yellow/orange looks like a dark brown. I read here that you can check if a terminal is using truecolor by using this command:
-
[FORK] Nerd Galaxyline for Onedark
since it doesn't work with : joshdick/onedark.vim
What are some alternatives?
material.nvim - :trident: Material colorscheme for NeoVim written in Lua with built-in support for native LSP, TreeSitter and many more plugins
vim-one - Adaptation of one-light and one-dark colorschemes for Vim
tokyonight.nvim - 🏙 A clean, dark Neovim theme written in Lua, with support for lsp, treesitter and lots of plugins. Includes additional themes for Kitty, Alacritty, iTerm and Fish.
nord - An arctic, north-bluish color palette.
nightfox.nvim - 🦊A highly customizable theme for vim and neovim with support for lsp, treesitter and a variety of plugins.
python-syntax - Python syntax highlighting for Vim
doom-one.vim - A dark colorschme for vim, ported from doom-emacs' doom-one theme.
one-nvim - Atom one theme
base16-nvim - Neovim plugin for building a sync base16 colorscheme. Includes support for Treesitter and LSP highlight groups.
semshi - 🌈 Semantic Highlighting for Python in Neovim
gruvbox - Retro groove color scheme for Vim - community maintained edition