× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Thanks,

  Yes, I'm sure that will help a lot.  I believe those are the details
I've been missing (and not able to find very well explained)
  Right not busy with other higher priority items, should get to that in
a couple days though and I'll let you know if I got it working.

  Yes, that Milwaukee Valve.  Except I'm only at that office maybe once
a week.

-Mike

> -----Original Message-----
> From: linux5250-bounces@xxxxxxxxxxxx 
> [mailto:linux5250-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
> Sent: Friday, March 28, 2003 5:15 PM
> To: Linux 5250 Development Project
> Subject: [LINUX5250] Re: How to remap keyboard
> 
> 
> 
> To add to my last message...
> 
> If you need to use per-user changes (i.e. not everyone on the 
> system uses
> the same keyboard mappings) then probably the ~/.Xdefaults file is the
> best way.
> 
> I think what you may be doing wrong is that you're not including
> everything that belongs in the file.
> 
> It's important to understand that .Xdefaults is not part of 
> TN5250.  It's
> part of X11!  You can use it for a LOT of different things, keyboard
> mapping in tn5250 is just one of many.
> 
> Here is a very simple ~/.Xdefaults file that just changes the Return
> and Right Control keys:
> 
> xt5250*VT100.Translations: #override\n\
>         <Key>Control_R: string("\n") \n\
>         <Key>Return: string("\030")
> 
> note that the \n\ at the end of each line is a "continuation" 
> thing... it
> tells X11 that the following line is part of the same 
> configuration set...
> 
> So, if you had settings for multiple programs, it might look 
> like this:
> 
> xt5250*VT100.Translations: #override\n\
>         <Key>Control_R: string("\n") \n\
>         <Key>Return: string("\030")
> 
> vi*VT100.Translations: #override\n\
>       <Key>KP_Enter: string("\n") \n\
>         <Key>Insert: string("i")
> 
> xterm*VT100.Translations: #override\n\
>       <Key>F9: string("\033OA")
> 
> Maybe that'll help...
> 
> 
> On Fri, 28 Mar 2003, Scott Klement wrote:
> >
> > Ignore the whole ".Xdefaults" and ".Xresources" idea.  Instead, make
> > your changes in /usr/local/share/tn5250/XTerm  (it might be 
> installed
> > somewhere else on your system, tho... you might need to do something
> > like "find / | grep tn5250/XTerm" to find it.
> > (and make sure you capitalize the X & T in XTerm)
> >
> > There are already keyboard mappings set up in that file, so you'll
> > be able to see what needs to be done a little bit better.
> >
> > This only works when using the xterm version of tn5250 
> (xt5250).  For
> > other versions, you need to the keyboard mapping differently.
> >
> _______________________________________________
> This is the Linux 5250 Development Project (LINUX5250) mailing list
> To post a message email: LINUX5250@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/linux5250
> or email: LINUX5250-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/linux5250.
> 


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.