Setting Chromium flags via Plasma app launcher

René J.V. Bertin rjvbertin at gmail.com
Tue Sep 10 14:33:23 BST 2019


On Tuesday September 10 2019 12:03:17 Ave Milia wrote:

>Terminal=false
>TerminalOptions=--disable-font-subpixel-positioning

I think this is for passing options to the terminal emulator programme.

However,

>Exec=CHROMIUM_USER_FLAGS="--disable-font-subpixel-positioning" chromium %u

Have you tried `Exec=chromium --disable-font-subpixel-positioning %u` ?

>export CHROMIUM_USER_FLAGS="--disable-font-subpixel-positioning"
>
>directly into /usr/bin/chromium

You can probably also put it in your ~/.bashrc or ~/.profile, or possiby ~/.login . Putting it in ~/.zshrc likely doesn't have the effect you hope for because the launcher for the desktop environment doesn't use your login shell but either /bin/sh or whatever shell is configured at the top of individual shell scripts.

>Unfortunately, not on my machine: chromium starts faster, loads page elements faster, has better plugin support (after FF killed XUL, developers

How many plugins does one still need nowadays?! FF does have somewhat less extensions but the ones I find crucial do exist or can be adapted from the Chrome version with a (half)automated tool.
FF was more than 2x faster than Google Chrome across several CPUs and operating systems on an HTML5 benchmark that sadly has been retired since (that was 1 or 2 y ago). Even my self-compiled QtWebkit (the rebooted version) was faster, almost 2x. FF is also the only browser that is still kept up-to-date for the OS version I have on my Mac, so that's what I use across the board nowadays.


R




More information about the kde mailing list