On Mon, 27 Aug 2001, tonyl wrote: > Here's a wish list request: > > import client access's .kmp (keyboard map) files. Here is vote to *not* import those files. tn5250 by and large doesn't run on windows machines so why waste time trying to import files created on windows machines? Why should we mimic the IBM way? I'm sure that there are easier ways to handle key-mapping on UNIX machines than trying to import Client Access files (even though those files would just tell us how the map should be set up). Just save the map as <insert your favorite text file format here - .Xresources format ain't too bad, use XML if you want>. Or don't even worry about keyboard mapping. Here I've been using tn5250 since it's initial release (back when I could read all the code and understand it in a few hours - and port it to a new arch :) and I don't have any problems about how the keys are setup. Why confuse people by trying to make the right control be the enter key? Just use the key labeled 'Enter' as the enter key. Makes it a lot easier when giving support over the phone and you say "Press enter" and you actually mean to press the enter key. Yes we could go fancy with keyboard mapping - but should we? James Rich email@example.com
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.