FilePro from Linux xterm or other terminal?

[Bill Campbell]

Bottom Posted.

On Mon, Aug 09, 2010, Bill Campbell wrote:
...
>I am adding an xterm-linux entry to a local copy of the fptermcap
>file to be sure that FPtech updates don't nuke my changes, and
>putting a slightly hacked version of the ``pf'' startup script in
>/usr/local/bin which looks at then environment to set the
>environment variable TERM=xterm-linux where appropriate.
>
>The things I'm doing with the xterm-linux entries include:
>
>  1.  Eliminating the terminal initialization string which sets the wierd
>      colors, leaving the xterm window with whatever foreground and
>      background colors the user selects.  This also eliminates the need to
>      reset the xterm after exiting FilePro to get the screen colors back
>      to the user's definition of normal.
>
>  2.  Add ``GZ=~'' to the termcap so that the field ending drawing
>      character is a tiny dot instead of a question mark.
>
>  3.  Fix the function key mappings so the F1->F4 key codes are interpreted
>      properly instead of using the ancient PF key codes as found on the
>      old Wyse and VT100 terminals which only had 4 function keys.
>
>  4.  Eliminate the use of function keys > F7 to avoid conflicts with the
>      Mac OS X use of these keys, using control key sequences in their
>      place.
>
>One thing I have not been able to figure out is why FilePro seems
>to be ignoring the ``LY=Ctrl-C'' entry in the termcap, but says
>to hit the ``DEL'' key to exit various functions.
>
>BTW:  I'm testing here on FP 5.6.

I'm close to being happy with the termcap modifications I have
made, at least when using a gnome-terminal connection (client
likes the little menu bar :-).  There are still a few issues in
addition to my question about why it seems to be ignoring LY for
Ctrl-C as I mentioned above.  The main glitch I have seen so far
is that going down through a list of browse items with the down
arrow keys blanks the left two characters of each line on the
display.  I suspect this has something to do with the ``dn''
entry in the differences below.

Here is a list of the termcap codes that are different between
filepro ``xterm'' and ``xterm-linux''.  My descriptions tend to
be pretty ancient as my termcap comparison program was originally
written on Tandy Xenix systems.  Currently I am remapping any
functions > F7 to avoid conflicts with Apple's use of the high
function keys.  These seem to be developer functions, and I don't
think that normal end-users would be using them.

CD xterm       xterm-linux           Description
bs None        True                  ^h does backspace
CF None        \200                  Tandy Xenix: Cursor Off
CN None        \200                  Multiplan sent by CANCEL key
dc \E[P        None                  delete character
do None        \E[B                  down one line
ei             None                  end insert mode
eo True        None                  can erase overstrikes with a blank
GZ             ~                     FILEPRO-16 field end mark Character
ho \E[H        None                  home cursor (if not cm)
ic \E[@        None                  insert character
im             None                  insert mode (enter)
is None                              terminal initialization string
kb \177        None                  sent by backspace key
ke None        \E[?1l\E>             out of keypad-transmit mode
ks None        \E[?1h\E=             put terminl in keypad-transmit mode
LB F6          Ctrl-F                FILEPRO-16 dmap Display Fields
LE F8          Ctrl-P                FILEPRO-16 dprt Display Print Codes
LG Ctrl-X      Ctrl-Z                FILEPRO-16 crup Up Arrow (DT-1)
LH F9          Ctrl-G                FILEPRO-16 cdwn Down Arrow (DT-1)
LJ F10         Ctrl-X                FILEPRO-16 crgt Right Arrow (DT-1)
ms True        None                  safe to move while in so and ul mode
P0 \EOP        \E[11~                FILEPRO-16 insc Insert Character
P1 \EOQ        \E[12~                FILEPRO-16 delc Delete Character
P2 \EOR        \E[13~                FILEPRO-16 insl Insert Line
P3 \EOS        \E[14~                FILEPRO-16 dell Delete Line

The xterm entries are ancient VT-100 PF1->PF4 keys, and are not
sent by any modern xterm.

PB \E[17~      ^F                    FILEPRO-16 dmap Display Fields
PD \E[18~      ^E                    Multiplan sent by PAGE DOWN key
PE \E[19~      ^P                    FILEPRO-16 dprt Display Print Codes
PG ^X          ^Z                    FILEPRO-16 crup Up Arrow (DT-1)
PH \E[20~      ^G                    FILEPRO-16 cdwn Down Arrow (DT-1)
PJ \E[21~      ^X                    FILEPRO-16 crgt Right Arrow (DT-1)

Remapping high function keys to control codes.

RT ^J          None                  Multiplan sent by RETURN Key
sr None        \EM                   scroll reverse (backwards)
tc linux       None                  goto terminal - must be last
te None        \E[?1l                string to end programs that use cm
ti None        \E>\E[?5l\E[?7h\E[?8h string to begin progs that use cm
dn \E[B        None                  unknown
LD F7          Ctrl-E                unknown
LZ Enter       RETURN                unknown

I don't seem to have definitions for these three entries that
appear in the FilePro xterm.  The ``dn'' entry is the same code
sent by the standard termcap ``kd'' (key down).  Descriptions of
their functions would be nice to add to my comparison script.

Bill
-- 
INTERNET:   bill at celestial.com  Bill Campbell; Celestial Software LLC
URL: http://www.celestial.com/  PO Box 820; 6641 E. Mercer Way
Voice:          (206) 236-1676  Mercer Island, WA 98040-0820
Fax:            (206) 232-9186  Skype: jwccsllc (206) 855-5792

Cutting the space budget really restores my faith in humanity.  It
eliminates dreams, goals, and ideals and lets us get straight to the
business of hate, debauchery, and self-annihilation.  -- Johnny Hart