|Summary:||wmconfig has hardcoded -fg and -bg colors for xterms|
|Product:||[Retired] Red Hat Linux||Reporter:||tpoindex|
|Component:||AfterStep||Assignee:||Cristian Gafton <gafton>|
|Status:||CLOSED WONTFIX||QA Contact:|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||1999-04-09 21:29:04 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description tpoindex 1999-03-18 17:00:18 UTC
I believe this is a wmconfig setting somewhere; perhaps it's really an afterstep problem. When starting X with normal 'startx', wmconfig runs, selecting 'afterstep' (in my case.) The afterstep configuration in ~/GNUstep/Library/non-configurable/startmenu always is created with xterm & nxterm using -bg black and -fg peachpuff, thus overriding my preferences in ~/.Xdefaults. I don't care for that particular color combination, and I consider it a bug that wmconfig (or afterstep) continually overrides my preferences. I've tried to eliminate all hard coded values in various config files for wmconfig and afterstep, but can't seem to get rid of the -bg and -fg values. Thanks, Tom Poindexter
Comment 1 David Lawrence 1999-03-21 22:26:59 UTC
Thank you for the suggestion. It has been assigned to a developer for review.
Comment 2 Mike Maher 1999-03-22 23:48:59 UTC
This is an afterstep request.
Comment 3 Michael K. Johnson 1999-04-09 21:29:59 UTC
AfterStep seems to do this kind of thing for every application. It appears to be a style decision on their part and we'd get as much flack for changing it as for leaving it alone, and so there isn't much to be gained from us trying to maintain a patch to change this behaviour, regardless of our personal opinions of the appropriateness of this behaviour. I suggest that you either choose a window manager that is not configured this way or lobby the AfterStep maintainers to change their defaults.