4 ms·
Speaking of Electron... vscode even intentionally ignores .config/electron-flags.conf (or it's own -flags.conf), so you must pass the ozone flags on the command
by vetinari 3y ago
Speaking of Electron... vscode even intentionally ignores .config/electron-flags.conf (or it's own -flags.conf), so you must pass the ozone flags on the command line (i.e. edit the launcher, which will be replaced on next update).
There were many issues filled on vscode wrt. wayland support, hidpi, fractional scaling... and they all were closed with half-baked solution that are not really solution. It's tragic, how a project like vscode can ignore wayland and it's features for such a long time.
- bravetraveler 3y agoArgh, that's frustrating. That's been my default (uninformed) state -- those flags files never seem to work for me. I override launchers all the time. I've found some comfort by placing my edited copies in ~/.local/share/applications and informing 'fuzzel' (my launcher) of it by ensuring the parent directory is in $XDG_DATA_DIRS As long as the file names match those in the 'system' directories, these will win.