![]() It will probably shave off a couple of nanoseconds from the startup time as well, so that's an added bonus. lua as file extension) and skip all the Lua <<EOF ritual. ![]() You can make your own and your user's life easier by using idiomatic Vim constructs which have been there even since before Neovim existed.ĮDIT: I just noticed that your colors/solarized.vim file is really just a Lua file. For those who have no idea what I’m talking about, here’s some. Solarized comes in 2 flavors, light and dark. Colour scheme configuration should be done through a syntax file: the user can define his own overrides in after/colors/solarized- file looks at the settings and only executes colorscheme where is the name of the real color scheme. Every time I switch to some other theme, I find myself coming back to Solarized.Using the background option (or even worse, a parameter to the setup function) is wrong even though everyone and their mother does it. 7:00 AM The Very Mathematical History of a Perfect Color Combination Solarized creator Ethan Schoonover sought colors that would look good together, have the same apparent. Light and dark variants should be separate colour schemes.Its better to update your terminal color palette instead for more precise colors. I wrote my own version of Solarized a while ago: GitHub - altercation/solarized: precision color scheme for multiple applications (terminal, vim, etc.) with both dark/light modes altercation / solarized Public Notifications Code Issues 153 Pull requests 68 Actions Security master 1 branch 2 tags seils and TrevorBramble Update README. 3 Answers Sorted by: 4 By setting tCo to 256 what youll get is a degraded version of Solarized.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |