Mateus Melchiades

Hello! The second issue should be fixed now, I let this bug slide when I changed the parsing logic a while back. I have an idea on what may be...

Is your custom dashboard a popup? The first issue should be fixed now. If it's ok, could you share how you create the scratchpad on startup so I can check...

I managed to "fix" this issue in [my own plugin](https://github.com/matbme/JABS.nvim) by changing the _relative_ value in the _config_ parameter of `nvim_open_win()` from "win" to "editor". From what I can see...

Also worth noting that (at least for me) spotifyd jumps to 100% CPU usage during the delay and then returns to normal usage. 

> This is only possible with RGB values. Maybe instead of using pure red and pure green, something like `#BC0000` for red and `#00B200` for green would look good in...

I just tested your config and it works for me. What version of Neovim are you on? Also, are you using the latest version of the plugin?

I haven't tested JABS with lazy.nvim yet, maybe the lazy loading is causing issues. Could you try setting the plugin to use `lazy = false`?

> The user of Albius might not expect it to make changes to the LVM configuration if it's not told to do so. True. At most, Albius should warn or...

Weird. I can reproduce this in both a fresh install and an older one after updating. I'll look deeper into this when I have the time.

> @matbme Are you checking right after the upgrade or after the reboot? Both. It's there before and after the reboot.