linux- filepro -putty

[Brian K. White]

Enrique Arredondo wrote:
> ----- Original Message -----
> From: "Bill Vermillion" <fp at wjv.com>
> To: <filepro-list at seaslug.org>
> Sent: Tuesday, March 16, 2004 9:16 AM
> Subject: Re: linux- filepro -putty
>
>
>> On Tue, Mar 16, 2004 at 08:53:13AM -0800, Enrique Arredondo thus
>> spoke:
>>>
>>> ----- Original Message -----
>>> From: "Jay R. Ashworth" <jra at baylink.com>
>>> To: <filepro-list at seaslug.org>
>>> Sent: Monday, March 15, 2004 5:54 PM
>>> Subject: Re: linux- filepro -putty
>>
>>>
>>>> On Mon, Mar 15, 2004 at 07:34:21PM -0500, Fairlight wrote:
>>>>
>>>>> Confusious (Enrique Arredondo) say:
>>>>>
>>>>>> for Red Hat linux running filepro 5.0.13 which is the
>>>>>> best terminal emulation over ssh that would support
>>>>>> instering lines and deleting lines when doing developing.
>>
>>>>> I use PFTERM=xterm with PuTTY.
>>
>>>> Which works ok, as long as you have a sufficiently recent
>>>> version of the filePro termcap file. Since fpTech Release
>>>> Engineering (<roar)) doesn't bother to put release numbers
>>>> in these things, I can't tell you exactly which one it is I
>>>> use, but I'm pretty sure all the 5.0's will let you do that
>>>> unmodified. It *might* need to be from a Linux version of
>>>> filePro -- ISTR that I could do it with 4.8/Linux, but *not*
>>>> with 4.8/SCO.
>>
>>> Could you please decipher the following ,which code means
>>> insert a line :
>>
>> Termcaps aren't that hard to decipher. Note the F1-F4 below,
>> where the F1 inserts char and F3 inserts line.
>>
>> The L0 thru Lx  are the labels used.  Notice that L0-L3 are labeled
>> F1-F4.   The L's match the P's.  So if F3 inserts a line it shows
>> L2=F3.  The L's and P's correspond so the key defined so
>> when the system sees \EOR it is associated with P2.
>>
>>
>>
>>> xterm|xterm-color|rxvt|XFree86 3.3.x xterm or rxvt 2.x:\
>>>
>>> :am:cd=\E[J:ce=\E[K:cl=\E[2J\EH:co#80:dc=\E[P:dl=\E[M:dn=\E[B:\
>>>
>> ho=\E[H:ic=\E[@:li#25:kh=\E[H:ku=\E[A:kd=\E[B:kl=\E[D:kr=\E[C:eo:\
>>>         :GS=\E(0:GE=\E(B:\
>>>         :GV=x:GH=q:G1=k:G2=l:G3=m:G4=j:GZ=:\
>>>         :GU=v:GD=w:GC=n:GR=t:GL=u:RT=^J:\
>>>         :tc=linux:\
>>>         :L0=F1:L1=F2:L2=F3:L3=F4:L4=ESC ESC:L5=F5:\
>>>         :L6=Pg Up:L7=Pg Dn:L8=ESC TAB:L9=TAB:LA=Ctrl-O:\
>>>         :LB=F6:LC=Ctrl-L:LD=F7:\
>>>         :LE=F8:LG=Ctrl-X:LH=F9:LY=Ctrl-C:LZ=Enter:\
>>>         :P0=\EOP:P1=\EOQ:P2=\EOR:P3=\EOS:P4=\E\E:P5=\E[15~:\
>>>         :P6=\E[5~:P7=\E[6~:P8=\E^I:P9=^I:\
>>>         :PA=^O:PB=\E[17~:PC=^L:PD=\E[18~:PE=\E[19~:PG=^X:PH=\E[20~:\
>>>         :PJ=\E[21~:LJ=F10:
>>>
>
>
> Ahhh so if I see that when I hit the F1-F4 keys on putty it display
> 1~ 2~ 3~ 4~ , so then I go to the termcap and change that EOS EOR,
> etc... for 1~ 2~ 3~ 4~ and it will work ?

That just means putty is not in truth emulating an xterm accurately enough
to match the fp termcaps definition of "xterm" which, according to the label
claims to be tuned for the xterm that comes as part of XFree86
The label is a little bogus right off the bat though, because it also claims
to be tuned for rxvt, and the two are not equal so it can only be really
correct for one or the other, not both.

I posted what I think are better-working xterm and rxvt definitions a few
days ago.
Try them.

By default putty sets it's TERM to "xterm"
but on another screen in the putty settings it has a set of options
specifically for the F-keys, and by default, the setting is not "xterm".
It's set so that F1 sends \E[1~ , which is not the standard for any xterm I
know of. But there is a simple check box for "xterm" which causes F1 to send
Xfree's version of xterm F1 key. Try simply changing that setting in putty.

http://www.aljex.com/bkw/tmp/putty_keyboard.gif