David Novakovic

FWIW I use this setting now: `"editor.defaultFormatter": "esbenp.prettier-vscode",` no need for the extra vscode extension. Just configure eslint correctly with the prettier rules and use `prettier-vscode` as your formatter.

abandonware?

To second what @fuadsaud said - the message is sent in a bunch of irrelevant instances, they are plain to see in the source code. I'm wagering that hocuspocus is...

> You can do so with `pnpm changeset`, and given this is a backward compatible feature you can just create a patch changeset. done, thanks @IMax153 ! btw I know...

> @dpnova - of course! Anytime. > > Also it looks like we have a linting issue in CI. You can fix it locally with `pnpm lint-fix` woops - seems...

> Ehh... Window probably doesn't crash. By default it automatically closes, when it looses focus together with mouse cursor, because under Wayland WM's don't send close request to layer shells...

`className =? "mixxc" --> (doFloat hasBorder False)` this did the trick for me, thanks! I did notice some other weird behaviour, but I suspect that's a result of some weird...

I tested with my mouse follows focus hack disabled, commenting out this: `logHook = updatePointer (0.5, 0.5) (0, 0),` and didn't get the cursor issues, but still have the flickering...

Just noticed that I don't get any of the flickering while the window is "managed" by xmonad - ie I haven't pulled it out of the layout manager. 🤔 noticed...

Seems people have noticed something similar with Reaper: https://www.reddit.com/r/xmonad/comments/18rck0e/reaper_daw_and_xmonad/ EDIT: actually nm - removing ewmh didn't resolve the underlying issue for me In the mean time when i use mixxc...