Date: Mon, 21 Jan 2019 10:41:03 -0500 From: Ken Moore <ken@ixsystems.com> To: <freebsd-x11@freebsd.org> Subject: Re: Lumina and env variables Message-ID: <54013c32-3b8e-4911-bc53-faca7d255c7a@ixsystems.com> In-Reply-To: <4c339ec6-b03b-dfe4-f694-af403dc5d89a@gjunka.com> References: <4c339ec6-b03b-dfe4-f694-af403dc5d89a@gjunka.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday, January 19, 2019 9:33:41 AM EST, Grzegorz Junka wrote: > Hello, > Does anyone know how to set an environment variable so that=20 > it's visible when running Lumina applications? Currently I have=20 > QT_QPA_PLATFORMTHEME set in .profile and .cshrc but these are=20 > not visible when I run qt5ct from the Lumina launch menu. They=20 > only take effect when I run qt5ct from the command line=20 > (Konsole). > > This is quite strange because I start Lumina with startx and my=20 > .xinitrc looks like this > > exec /usr/local/bin/start-lumina-desktop > > I would have hoped that these environment variables should be=20 > inherited by the Lumina process and subsequently by all=20 > applications launched from the menu. Unless something overwrites=20 > them later? > > Thanks > GrzegorzJ > The QT_QPA_PLATFORMTHEME environment variable is special to Lumina and will=20= automatically get overwritten when the desktop starts up. Lumina will automatically change that variable to "lthemeengine" (Lumina=20 theme engine), which is a custom fork of the qt5ct theme engine with=20 additional support/features specifically for desktop/application theming=20 (such as more color palette support, ability to scan system-installed=20 palette and theme files for availability, things of that nature). TLDR: Don't use qt5ct with Lumina. Just make your changes in the Lumina=20 theme engine utility instead (nearly identical to qt5ct and behaves the=20 same way). --=20 ~~ Ken Moore ~~ ken@ixsystems.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54013c32-3b8e-4911-bc53-faca7d255c7a>