X weirdness under 3.1.5

[Ed Kubaitis - CSO]

  |>One last comment: I *really* wish (X-based) info wouldn't call xrdb
  |>WITHOUT the -merge flag. I get tired of all of my Xdefaults
  |>disappearing just because I had to look at a man page.
  |
  |Actually, I believe (no promises) that xmodmap is the correct call
  |(which is to say, it works for me).

It didn't work on non-IBM servers at 3003. Here's a 5 week old posting about
it:

 | ||> |> We're having trouble when we run info on platforms other than the
 | ||> |> 6000s - info will come up and be useable, but somehow (xmodmap call in
 | ||> |> /usr/bin/info?) the keyboard mapping gets seriously wedged (remapped),
 | ||> |> making the X session useless thereafter.
 | ||> |>
 | |
 | ||> There was a bug in the info script. Change the xrdb to xmodmap
 | ||>
 | |We did.  We still have the problem described.
 | |Thanks, but any other ideas?
 |
 |When we had trouble due to the xrdb in the script, we commented it out
 |rather than changing it to xmodmap as recommended. We have had no keyboard
 |mapping problems with either IBM or non-IBM servers.
 |
 |If you're running info on some non-IBM servers (such as NCD & HP) but using
 |an IBM system as a font server, you may also have a problem caused by info
 |tampering with your server's font path.
 |
 |IMO, clients should keep hands off of the server font path, key-mapping,
 |resource database, etc. Modifying these are the province of the user
 |or a display manager running on the user's behalf. At least, Info should
 |provide an option to bypass these favors.

----------------------------------
Ed Kubaitis (ejk at ux2.cso.uiuc.edu)
Computing Services Office - University of Illinois, Urbana