readme.q-and-a

一个通讯程序源码

On Apr 29,  9:21, Clayton Haapala wrote:
> 
> Warren Tucker writes:
> > 
> > Your question inspired a new README, which I just sent to everyone.
> > Does this help any?
> > 
> I run the same ecu binary from two different xterms.  One is from the
> Sun3 console, the other from a DECstation 5000.  I have built keymaps
> with kbdtest3 for each, but I can't get them to intersect enough to have
> them be one common entry.  (I haven't fiddled with the .Xdefaults.)  I
> would like to be able to store the keymaps in funckeymap as "xterm-sunc"
> and "xterm-dec" and have either a command-line switch or environment
> variable such as ECUKEYS select which one I want, since the TERM
> variable just isn't sufficient to choose in this case.
> 
> $TERM is marvelously adequate for doing all the curses stuff.  Nothing
> need be changed there.
> -- 
> Clayton Haapala	([e-mail])	
> Network Systems Corp.			"...and the alligators are on FIRE."
> 7625 Boone Ave N MS10				-- S.E.K.
> Minneapolis, MN 55428-1099

The answer within the current framework is to use xmodmap and/or
override translations to make the keys generate the same
sequences on both systems.

The ultimate answer is, as you suggest, to do something "better."
I just haven't come up with anything yet.

If you are networked so that ~/.ecu becomes the same directory
even on two different machines/xterm implementations, my pitiful
attempts break down.  I have always suggested forcing xterms to
have a consistent keyboard, but this is not always possible.
It is what I do for a SunOS MIT server and a SCO UNIX Roell X386
1.1b.  If I got really motivated, I'd change the Roell code
to match the Sun server.  But then, I wouldn't be able to
make accurate code and recommendations for other Roell users.

This is, in fact, partly a specification deficit and partly a
problem of incomplete porting.  Anyone who has ever ported X
would be very happy when they get down to these small matters
and if they never use the Home or Shift Tab, they'll never know.

Lemme think on this one.