Newsgroups: comp.unix.aix
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!news.cs.indiana.edu!ux1.cso.uiuc.edu!ux2.cso.uiuc.edu!ejk
From: ejk@ux2.cso.uiuc.edu (Ed Kubaitis - CSO )
Subject: Re: 3003 info on other platforms?
Message-ID: <1991Apr21.144006.13422@ux1.cso.uiuc.edu>
Sender: usenet@ux1.cso.uiuc.edu (News)
Reply-To: ejk@ux2.cso.uiuc.edu (Ed Kubaitis - CSO )
Organization: University of Illinois - Urbana
Date: Sun, 21 Apr 1991 14:40:06 GMT
Lines: 28

  ||> |> 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 
  ||> Jon Alperin
  ||> 
  |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@ux2.cso.uiuc.edu)
Computing Services Office - University of Illinois, Urbana