aks, 1 month ago

@volpeon use kate instesd :tia_pog:

Flaky, 1 month ago

@volpeon ...is there a problem with it on Wayland?

I have clipboard problems with VMware on Wayland, FWIW.

volpeon, 1 month ago

@Flaky By default, it uses XWayland which looks like dogshit on my 4K display because it renders at 1080p. So not using the buggy Wayland support isn't even an option for me. And the problem with that is that maximizing the windows crashes VSCode. Doesn't matter if it's maximized from the start or if you do it later - instant crash.
So what I have to do is removing the Wayland stuff from code-flags.conf, ensuring the windows aren't maximized (which they always are on a fresh desktop session), then re-launching it with the Wayland stuff. It's annoying as hell.

Flaky, 1 month ago

@volpeon Ohhh. I forget that scaling is still not 100% on Linux.

snep, 1 month ago

@volpeon 100% Impossible (GONE WRONG, GONE BLURRY) - Epic Crash Compilation

Johann150, 1 month ago

@volpeon microsoft: (integrates Teams into VS Code) there, i fixed it 😇

Hayden, 1 month ago

@volpeon Wait what's wrong with VSCode on Wayland? I don't have any immediate surface issues

volpeon, 1 month ago

@Hayden See here

RE: https://is-a.wyvern.rip/notes/9r6m4327nu2c0k30

Hayden, 1 month ago

@volpeon Oh, fascinating, I don't have a 4K display myself, but I haven't really had any problems with Wayland yet (And it's so much more responsive than X11 ever was on my laptop), and I've been using it since Plasma 6 released.

freeplay, 1 month ago

@volpeon I've disabled VSCodium falling back to x11 w/ flatseal and it seems to work fine ?

volpeon, 1 month ago

@freeplay Not for me

RE: https://is-a.wyvern.rip/notes/9r6m4327nu2c0k30