Jamy

Ok thanks, no problem :) I don't mind waiting at all. I'll update once 0.8 is merged.

@NotAShelf that's great with the v0.8 branch! Which API for theming plugins has changed? I've looked through `./modules/plugins/theme/*` but things seem the same as they were previously, so I'm probably...

Yeah it's something we can consider. There aren't light + dark variants of every scheme, but that doesn't mean we shouldn't look at the `{scheme_name}-{scheme_variant}.yaml` filename convention. Since a lot...

This PR increased the speed: https://github.com/tinted-theming/tinty/pull/126 Something that would really increase the speed a lot would be to change `.github/workflows/test.yml` ```diff - name: Cargo test - run: cargo test --release...

Hmmm, perhaps we could bundle the tinted gallery html page into the binary (it contains all css/js within it) and when “tinted gallery” is run we write the constant to...

Ah right yeah totally. Hmm, maybe we could rewrite the gallery generator in rust and use that as a lib in tinty to use against cloned schemes.

Looks good to me! We can merge once the themes have been built again (since the `execute "silent !/bin/sh ".g:tinted_shell_path."/{{scheme-system}}/{{scheme-slug}}.sh"` change was a change to the template)

@GordianDziwis it looks like @fnune isn’t on the @tinted-theming/vim team which is the team of maintainers for the repo. Where did you see them as a maintainer?

@GordianDziwis I’m currently at RustConf, but will give more comments about the PR when I get back in a few days.

I think it's ok that fnune is on the `@tinted-theming-team`, that team only gives read access to our repos and the project specific teams like `@tinted-theming/vim` give maintain access to...