|
On Wed, 30 May 2001, Jay 'Eraserhead' Felice wrote: > > > > 3) a different XTerm file is needed under FreeBSD. The strings > > containing the tilde "~" character don't seem to work with > > FreeBSD's termcap library. I have no idea how I'd check > > that in configure. > > The first question is whether there is a different thing we can put in the > XTerm file that will work on both platforms. If not, then that should > probably be keyed on the X windows version or the xterm version, whichever > is the deciding factor. The one I'm using on FreeBSD would probably work okay in Linux (actually, hang on I'll boot up my RedHat box and try it) Yep... this works on both FreeBSD and RedHat 6.x... If some people running other versions of Linux, and any other OSes that xt5250 works on could try this out and give me feedback, I'd appreciate it: xt5250*VT100.Translations: #override\n\ <Key>KP_Add: string("\030") \n\ <Key>KP_Subtract: string("\033M") \n\ <Key>KP_Multiply: string("*") \n\ <Key>KP_Divide: string("/") \n\ <Key>KP_0: string("0") \n\ <Key>KP_1: string("1") \n\ <Key>KP_2: string("2") \n\ <Key>KP_3: string("3") \n\ <Key>KP_4: string("4") \n\ <Key>KP_5: string("5") \n\ <Key>KP_6: string("6") \n\ <Key>KP_7: string("7") \n\ <Key>KP_8: string("8") \n\ <Key>KP_9: string("9") \n\ <Key>Scroll_Lock: string("\033H") \n\ ~Shift<Key>Print: string("\020") \n\ <Key>Control_L: string("\022") \n\ <Key>Escape: string("\001") \n\ Shift <Key>Print: string("\003") \n\ ~Shift <Key>F1: string("\0331") \n\ ~Shift <Key>F2: string("\0332") \n\ ~Shift <Key>F3: string("\0333") \n\ ~Shift <Key>F4: string("\0334") \n\ ~Shift <Key>F5: string("\0335") \n\ ~Shift <Key>F6: string("\0336") \n\ ~Shift <Key>F7: string("\0337") \n\ ~Shift <Key>F8: string("\0338") \n\ ~Shift <Key>F9: string("\0339") \n\ ~Shift <Key>F10: string("\0330") \n\ ~Shift <Key>F11: string("\033-") \n\ ~Shift <Key>F12: string("\033=") \n\ Shift <Key>F1: string("\033!") \n\ Shift <Key>F2: string("\033@") \n\ Shift <Key>F3: string("\033#") \n\ Shift <Key>F4: string("\033$") \n\ Shift <Key>F5: string("\033%") \n\ Shift <Key>F6: string("\033^") \n\ Shift <Key>F7: string("\033&") \n\ Shift <Key>F8: string("\033*") \n\ Shift <Key>F9: string("\033(") \n\ Shift <Key>F10: string("\033)") \n\ Shift <Key>F11: string("\033_") \n\ Shift <Key>F12: string("\033+") \n\ Shift <Key>Tab: string("\033[Z") \n\ ! Something I did installed a file which turned off underLine ! and turned on colorULMode in my ~/.Xdefaults. This, obviously, is not ! very useful for xt5250. I wish I knew how this works better -JMF xt5250.VT100*underLine: True xt5250.VT100*colorULMode: off > > And do a "--backtitle" feature check in configure.in so that xt5250.in > > uses backtitle only when available. > > This should actually be done from the script which calls dialog (xt5250). You > know, like: > > if dialog --help |grep -q backtitle ; then bt_arg="--backtitle $title" ; fi > > ... > > dialog $bt_arg ... > > For reference, both dialog -h and dialog --help return text containing the > word 'backtitle' on RH7.1. Unfortunately, RH6.2 (which is the version of Linux I have at work) returns a help screen that does NOT show "backtitle", but DOES support it... FreeBSD returns the EXACT SAME help screen, but does NOT support it... :( Still, since backtitle isn't critical, maybe we should use your idea, and if there are some versions of dialog where backtitle doesn't show up, it's not a huge loss... Sound good? Thanks for your input... it's been very helpful! +--- | This is the LINUX5250 Mailing List! | To submit a new message, send your mail to LINUX5250@midrange.com. | To subscribe to this list send email to LINUX5250-SUB@midrange.com. | To unsubscribe from this list send email to LINUX5250-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
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.