raddari

Good catch, I never considered this! [There already exists a way to check if a colorscheme is valid when saving](https://github.com/raddari/last-color.nvim/blob/a78c442f9deb493c5220acef56801d4d2279df4b/lua/last-color/init.lua#L52-L57), so it should be simple enough to run this check...

I was able to reproduce this issue, and have a working fix. Can you confirm that #6 works for you too?

Interesting, I'll see what's up

I can't seem to reproduce on my end, do you mind sharing the relevant parts of your config?

Looks like you're right about plugin load order, also explains the non-deterministic aspect. I'm hesitant to handle this issue on the `last-color` side for a few reasons: 1. [Lazy.nvim recommends...

@wroyca @mrs4ndman based on your feedback I've decided to revert the change for now. I apologise for the breaking change, I didn't test how its usage changed enough. Overall I...

Can confirm I'm getting the same issue on neovim-0.8. Interestingly, changing the `project.nvim` setup from: ```lua detection_methods = { 'lsp', 'pattern' } ``` to: ```lua detection_methods = { 'lsp' }...

Hello, thank you for the suggestion! I'm a little busy over the next few days, but I'll think about what you wrote over the weekend and get back to you...

Based on your suggestion and from what I've read about the plugin, does something like this sound right to you? ```lua local last_color = require('last-color') return { "f-person/auto-dark-mode.nvim", config =...

Can you confirm #9 works as you would like? The syntax has changed slightly from my original post: ```lua return { 'f-person/auto-dark-mode.nvim', config = { set_dark_mode = function() local last_color...