Why a global option to choose style instead of six different colorschemes? about material.nvim HOT 8 CLOSED

@matu3ba That seems like an awesome feature so I'll definitely look into adding it. I just have to figure out how, so it will probably take a few days. If you happen to know how to do it, any help, suggestion or pull request is welcome.

@metalelf0 My plan for this colorscheme in the future is to make it as extensible and configurable as posible. For example being able to toggle theme variations, italic comments, bold variables, underlined error messages etc. I think this is pretty cool since it allows for the user to have more control over the theme and set it up in his/her taste. Later today, I will set up another repo. It will be a clone of this one, but with standalone themes instead of a style variable so you can just use colorscheme oceanic to set a standalone theme. If you want, you can clone it and post it as your own theme to have on your profile.

from material.nvim.

@metalelf0 Here is the new repo: https://github.com/marko-cerovac/material-config-free.nvim you can now just use set colorscheme material-darker to set the darker variant. I've also left the ability to toggle italic comments, italic keywords(while, for, if, else..) and italic function names in the theme and they are off by default.

@matu3ba Until I make this option available (I have some exams coming up in the next couple of days, so I'm really busy), this new repo seams like a good temporary solution, until i can do it the right way. You can map keys to execute something like ":colorscheme material-lighter" and switch themes on the fly.

from material.nvim.

Thanks for the compliment.
Well, I haven't thought about it that much.
The material theme that I was using also did it like this, as well as the original VS Code material theme, so i thought I'd do it the same way.
The good thing in all od this is that there is no code repetition. So for example the color value of the background isn't defined 6 times(once for every style)
Instead it's a basic if-else statment that says:
If material_styles is equal to 'deep ocean'
Blue = #somecolor
Red = #somecolor
...
Elseif material_styles is equal to 'darker'
Blue = #some_other_color
Red = #some_other_color
...
Then, i can just say
g:Cursor = red
g:LineNr = blue
...

If you want, I can create stand-alone colorschemes or I can remove other colors and send you the code so you can make a repo and publish it.

from material.nvim.

@metalelf0 Colorbuddy allows dynamic setting of colors, so its very nice to adjust the colorscheme to you environment light settings.

@marko-cerovac Can you wrap the setup in a function, so that I can put keymaps or commands for that? Would be also very nice. if you would make this as demo. ;-)

from material.nvim.

@matu3ba : yeah, I'm not against different color variations. They are all good. I'm just asking about the opportunity of using a custom variable to choose between colorschemes, which I'm not a big fan of.

@marko-cerovac , yes, I understand it might be better from a dev perspective to have less repetition, but as an user I think it doesn't add any benefit. In the end, it would just be a matter of configuring the pipeline to spit out six colorschemes instead of one, and I could use your colorschemes just like the vast majority of others, without having to set a custom variable.

from material.nvim.

@marko-cerovac thanks a lot for your proposal, I won't hijack your work and post it on my profile :) Maybe you could consider setting up a branch of this repo instead of creating a new one? This could also make it easier to keep them aligned.

from material.nvim.

@marko-cerovac

Some more inspiration, so you dont need to write the rules for every language and you could even async load the color groups, lol. I dont like the setup of zephyr though. And more colors are cooler. :)

from material.nvim.

@matu3ba I've added two functions called change_style() and toggle_style(). The first one takes a style name as a parameter and switches to that style. For example:
lua require('material').change_style('lighter')

The second one takes no parameters and simply toggles the styles.
The function can be called like this:
lua require('material').toggle_style()

The best thing to do is to add key mappings to these functions:
nnoremap :lua require('material').toggle_style()

These instructions are also now in the README

from material.nvim.