KDE does not honor my settings in ~/.Xresources. Why?

Didier Spaier · 11-08-2016, 12:23 PM

On Slackware64-14.2 with all patches applied, I have this in ~/.Xresources:

Code:

XTerm*background:#001b33
XTerm*foreground:white

In all WM/DE that can be set as default by xwmconfig, xterm gets a dark blue background but in KDE xterm has a white background.

However xinitrc.kde merges ~/.Xresources as do other xinitrc.* files.

I have no idea what changes that afterwards and didn't find a clue in /usr/bin/startkde at first look (maybe because my knowledge of KDE is null).

Any clue appreciated.

phenixia2003 · 11-08-2016, 12:38 PM

Hello,

Quote:

Originally Posted by Didier Spaier

On Slackware64-14.2 with all patches applied, I have this in ~/.Xresources:

Code:

XTerm*background:#001b33
XTerm*foreground:white

In all WM/DE that can be set as default by xwmconfig, xterm gets a dark blue background but in KDE xterm has a white background.

However xinitrc.kde merges ~/.Xresources as do other xinitrc.* files.

I have no idea what changes that afterwards and didn't find a clue in /usr/bin/startkde at first look (maybe because my knowledge of KDE is null).

Any clue appreciated.

XTerm*<attr> does not work, but xterm*<attr> works. I use xterm*<attr> syntax, so, I don't know if this is a change or something else.

--
SeB

Didier Spaier · 11-08-2016, 01:13 PM

Merci encore, Sébastien!

You are right, and using only lower case letters works in all WM I tried.

Actually I wrote XTerm because it is spelled this way in "man xterm". Now that you make me think of it, I have read in some document (I can't remember which one right now) that XTerm is the old syntax and now only the first letter may be capitalized (Xterm), but the old syntax is still accepted to spare users the need to rewrite existing resource files. However Xterm doesn't work in KDE either, so I will keep xterm anyway.

jmccue · 11-08-2016, 05:13 PM

Strange, this works for me

Quote:

XTerm*background: black
XTerm*foreground: green

But when using kde, my settings are ignored until I manually issue

Code:

xrdb -load ~/.Xdefaults

and that command exists in my ~/.xinitrc (I use run level 3).

What I did in the past was have a 'startup' script called by kde's startup/stop setup but when I rebuilt the system for 14.2 I have yet to fully setup kde for my use.

I wonder, do all your other ~/.Xresources work as expected ?

John

Didier Spaier · 11-08-2016, 05:29 PM

@John: I have really few settings in ~/.Xresources.

To elaborate a bit: I am preparing the release of Slint-14.2 and want that users get an homogeneous look with all or at least most WM/DE included, regardless of the runlevel. They will also have the same default background of the root window and the same panel and similar root menu layouts in all WM.

Thus, doing something specific for a DE/WM is something that I try to avoid.

But I digress, sorry.

Gerard Lally · 11-08-2016, 07:22 PM

Quote:

Originally Posted by jmccue

Strange, this works for me

But when using kde, my settings are ignored until I manually issue

Code:

xrdb -load ~/.Xdefaults

and that command exists in my ~/.xinitrc (I use run level 3).

What I did in the past was have a 'startup' script called by kde's startup/stop setup but when I rebuilt the system for 14.2 I have yet to fully setup kde for my use.

I wonder, do all your other ~/.Xresources work as expected ?

John

The setting which causes this is System Settings > Application Appearance > Colours > Options > Apply colours to non-KDE4 applications.

This setting means xterm will have a white background if your KDE window background is white. You can turn this option off but it's a clumsy solution which affects all other non-KDE applications as well.