Message-ID: <7963ede9422221b4b93e7292bafd60730bffdac2.camel@riseup.net>
Subject: Re: ~/.gtkrc-2.0 ~/.config/gtk-3.0/settings.ini and other pitfalls
From: Ralf Mardorf <ralf-mardorf@riseup.net>
To: alice <alice@ayaya.dev>, ~alpine/users@lists.alpinelinux.org
Date: Sat, 03 Jun 2023 19:38:57 +0200
In-Reply-To: <CT36WEHPDST6.PUB0MVDBFR9C@sumire>
References: <de355c3181d96f23a2d75cdcf96879f7fea33a37.camel@riseup.net>
	 <CT36WEHPDST6.PUB0MVDBFR9C@sumire>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

On Sat, 2023-06-03 at 19:26 +0200, alice wrote:
> busybox ash does not send anything so you get some default

Thank you,

that explains it.

> > More annoying is, that gtk settings in
> > ~/.gtkrc-2.0 and ~/.config/gtk-3.0/settings.ini are seemingly ignored.
>=20
> they're not, those paths work. though of course some configuration is als=
o found
> in env vars, obscure gsettings, ..
> arch has them documented somewhat comprehensively https://wiki.archlinux.=
org/title/GTK

I don't experience such issues with my Arch install.

On Arch Linux

=E2=80=A2 rocketmouse@archlinux ~=20
$ echo $XDG_CONFIG_HOME

=E2=80=A2 rocketmouse@archlinux ~=20
$

the variable isn't set. I'll take a look if the variable is set by my
Alpine install, if I have some time again to experiment with Alpine.

Regards,
Ralf