Xterm and .Xresources

[jc at trillian.mit.edu (John Chambers,,,781-647-1813)]

Christoph Doerbeck A242369 <cdoerbec at cso.fmr.COM> writes:
	"John Chambers,,,781-647-1813" wrote:
	> There are quite a lot of other apps that  have  similar  undocumented
	> resources.  Is there some general way to learn what I should put into
	> an .app-defaults file?  Is it documented anywhere?
	>

	My way, although crude, when resources aren't documented properly is
	to run the following...

		strings `which xterm` | grep -i font

	And that should list all the font resources your app looks for.
	 
Yah; that's what I do, too.  When I do that with gv on this Redhat 5.2
system, the result is:


: strings `which gv` | grep -i color
GHOSTVIEW_COLORS
Color
color
[-monochrome] [-grayscale] [-color]
   # Color environment:
     [-monochrome] [-grayscale] [-color]
Color
-color
GV*viewClip.borderColor:
GV*page.borderColor:
GV*Scrollbar.pointerColorBackground:
GV*Scrollbar.pointerColor:
GV*beNiceToColormap:
:

I added the above resources to my .Xdefaults file, ran xdb  to  merge
them in, ran "xrdb -query" to verify they were there, and started xv.
I still got the same "Cannot allocate colormap entry"  messages,  and
some  widgets  are  white-on-white.   I also went to my .app-defaults
directory, and added a resources file that I gave various names  such
as gv, GV, ghostview, Ghostview, and GHostview, and added *background
and *foreground colors.  No effect whatsoever.  As far as I can tell,
gv  doesn't  request  any  X resources at all, or if it does, I don't
have a clue as to what the resources are called. I've set *background
in  the  X server to grey50, and gv comes up with a white background.
This would seem to argue that it doesn't ask the  X  server  for  its
background  color  at all.  I also tried *backGround, and that had no
effect at all.

The really annoying part is the white-on-white.  You'd think that  if
they set up defaults, they'd at least try to make them contrast.  But
you'd also think that if they're gonna tell  you  they  can't  get  a
color,  they'd  have  the  brains to tell you why (i.e., the resource
name) they were trying to get that color.  Nope.

The "man gv" page describes -monochrome and -grayscale options.  I did
try gv with these, and it still gives me the warnings:

Warning: Cannot allocate colormap entry for "AntiqueWhite3"
Warning: Cannot allocate colormap entry for "AntiqueWhite2"
Warning: Cannot allocate colormap entry for "AntiqueWhite4"
Warning: Cannot allocate colormap entry for "gray90"
Warning: Cannot allocate colormap entry for "#D3B5B5"

So it isn't even honoring these non-color options.

-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).