FilePro from Linux xterm or other terminal?

[Brian K. White]

On 8/27/2010 1:10 PM, Bill Campbell wrote:
> On Thu, Aug 26, 2010, John Esak wrote:
>> I don't have a lot of time right now... I'm going to Washington, DC for the
>> bigt gathering on Saturday and the meeting at the Kennedy Center tomorrow
>> night. So, if I get a chance I'll look further on this... But immediately
>> I'm pretty sure about the LY thing. The LY is just the label for BREAK or
>> Ctl-C.  Unfortunately, there is no PY entry to simply change the Break key
>> to something different. But I'm sure you know this... You need to just
>> change the stty setting for INTR.... But are you saying the LY does not
>> reflect whatever string you put in it?
>
> Exactly.  Ctrl-C does the trick, but ``DEL'' is what's displayed.
>
> What I can't figure out is that I think it displays Ctrl-C when
> using the default FP termcap, but not when it's using mine.  My
> previous post showed only the differences between the termcap
> values to make it easy to see what's changed.

> It would be Really Nice(tm) if somebody from FPTech would chime
> in on this as I would think it would be in their interest to get
> a working termcap for xterms in Linux, OS X, and other *nix
> systems.  Not everybody runs Windows and Anzio (sorry Bob :-).

https://www.fptech.com/Products/Docs/fpmanhtm/start.htm
On the left side contents tree: "Terminal Guide"

(Don't use Chrome. It's not Chromes fault. webhelp/robohelp generates 
html and javascript that is ignorant and expects to recognize your 
browser, so, the content doesn't work in browsers that were invented 
after that version of webhelp/robohelp was itself written. firefox and 
safari work, don't know about opera, and of course ie does)

Or, the direct jumps (any browser):
https://www.fptech.com/Products/Docs/fpmanhtm/terminal_guide/adding_new_terminal_types.htm
https://www.fptech.com/Products/Docs/fpmanhtm/terminal_guide/termcap_function_codes.htm
https://www.fptech.com/Products/Docs/fpmanhtm/terminal_guide/termcap_graphic_codes.htm
https://www.fptech.com/Products/Docs/fpmanhtm/terminal_guide/filepro_plus_codes.htm
https://www.fptech.com/Products/Docs/fpmanhtm/terminal_guide/key_label_codes.htm

That, and the knowledge that the break key is defined by stty and not by 
the terminal type, has always been enough for me to make working 
terminals. I have my own linux, xterm, rxvt, putty-in-various-modes, 
scoansi, java-telnet-2.5 all working fine and I periodically try out new 
terminals like various palmos, webos, and now android clients etc. (no I 
have not tried to make a working terminal on an ipad, shudder)

I definitely always have the break key and other keys displaying the 
correct display for the terminal being used just by defining LY to match 
what I know stty will be set to.
But I also definitely have to _ensure_ stty happens in profile or other 
scripting outside of and before fp runs. If I'm using a linux box or a 
linux terminal emulator to connect to a sco box, I have code in 
/etc/profile on the sco box that detects TERM=linux and runs stty to 
alter break to Ctrl-C, so that when I go into filepro on that sco box, 
and the fp termcap assumes that "linux" uses ctrl-c, that in fact my 
session is using ctrl-c at that time even though it normally would not 
be because that's not the default on sco.

I know you know how all that works since decades ago, I'm just reporting 
that I've never seen an inexplicable discrepancy between what filepro 
displays and what the termcap says and what the system actually does. 
I've seen plenty of perfectly explicable ones though. Like not using the 
backslash display codes for the the key labels in handwritten show prompts.
Our own code used to be full of "Press Del to..." until I replaced them 
all with \KY and the other display codes over time.

--
bkw