3 ms·
For most electron apps, you should put the above in ~/.config/electron-flags.conf. Note that VSCode is known not to work with it. Seems like a deal breaker.
by mberger 1y ago
For most electron apps, you should put the above in ~/.config/electron-flags.conf. Note that VSCode is known not to work with it.
Seems like a deal breaker.
- hyperbolablabla 1y agoCode works just fine with Hyprland in my experience, you just need yo tweak the interface scaling. However, I've taken the opportunity to learn neovim since switching to arch/Hyprland, since the emphasis is much more on keyboard-centric input. Can't say I miss vscode much, other than multi cursor.
- TheRoque 1y agoMulti cursors is in the way for 0.12 I think
- bee_rider 1y agoThey clearly managed to make the window manager, so evidently it was not.
- delusional 1y agoIt's pretty common to need to hack stuff for tiling window managers. Java/Swing has required faking being LG3D since forever for example to run some compatibility code paths. Yeah, Looking Glass.
- aorth 1y agoFor the benefit of others, that note comes from this page: https://wiki.hypr.land/Getting-Started/Master-Tutorial/#force-apps-to-use-wayland https://wiki.hypr.land/Getting-Started/Master-Tutorial/#forc... It has been common for years to use such flags for Electron-based apps on Wayland. It's not specific to Hyprland, and it's not as bad as it sounds. Chromium has been working on Wayland support for years and it was behind a feature flag. It's worked well for a while now and will be the default soon. https://www.phoronix.com/news/Chrome-Auto-Ozone-Platform https://www.phoronix.com/news/Chrome-Auto-Ozone-Platform