Re: [Info-ingres] termcap Issues Under Linux
- From: Karl & Betty Schendel <schendel@xxxxxxxxxxxxxx>
- Date: Tue, 29 Nov 2005 13:11:33 -0500
At 12:22 PM -0500 11/29/2005, Lucky Leavell wrote:
>On Tue, 29 Nov 2005, Betty & Karl Schendel wrote:
>
>>
>> You could use the same mapping file and a termcap entry something like:
>>
>> putty:\
>> k0=\E[11~:k1=\E[12~: ... :tc=konsole
>> (or tc=consolel if line drawing works the same).
>>
>> The trick would be to override the kX entries for the F1-F4 keys.
>> I expect that these are k0..k3 but I don't have it in front of me.
>> You can also override any shifted function key entries, if there are
>> any such in the konsole termcap entry.
>>
>Two more questions:
>
> 1. When the same capability is defined twice, say k0 in putty and
> konsole, which one is effective, teh first one encountered or
> the last?
The first one encountered.
>
> 2. What are the capabilities for shifted function keys (sF1, etc)
> called in the ingres termcap?
>
It doesn't work like that. :-)
In the termcap, you define what selected function keys send, as
capabilities k0, k1, ... k9, kA ... kZ, KA, ... KD which I think is
the last one. YOU pick which function keys you're going to define,
and YOU pick the order. The keys you define in termcap become keys
pf1, pf2, .... up to pf40. (Don't forget to say :ky: and :kn#NN: in
the termcap as well, to say how many keys NN you defined. I don't know
why it can't just count 'em, but it can't.)
Note that the key definitions in termcap are just character sequences.
I can define a "function key" for any multi-key sequence, e.g. control-A
escape A B C if I want to; indeed, this trick is sometimes useful in a
context where the actual terminal or keyboard has a limited number of
distinct sequences that it sends.
Now, in the map file, you map pf keys or control keys to FRS functions:
frskeys, menuitems, and FRS form keys (stuff like nextfield).
You can use any control key, or any "function key" that you mapped in
termcap. You reference the former by saying e.g. controlA, and the latter
using pf1, pf2, and so on. The label in parens (^A, Sh-F1, whatever) is
strictly something that shows up on the screen or in Help Keys.
It's up to YOU to put the right label on the pfN usages in the map file;
you're the one who knows how you put the keys into termcap in the first
place.
By the way, I sent the konsole map and termcap to your reply-to address
earlier today, did you get them?
As to your other question: I've had relatively limited exposure to Solaris-10
on x86 (it was an Opteron box), but what I've seen is all good. From a
developer's perspective, Solaris is infinitely easier to work on than
anything else, thanks to truss, dtrace, pstack, dbx, etc.
Even for a user, I would think that just having dtrace would make
Solaris worth the learning curve.
Karl
.
- Prev by Date: Re: [Info-ingres] Solaris 10 vs SuSE Linux on Intel x86
- Next by Date: Re: [Info-ingres] Solaris 10 vs SuSE Linux on Intel x86
- Previous by thread: Re: [Info-ingres] termcap Issues Under Linux
- Next by thread: Re: [Info-ingres] termcap Issues Under Linux
- Index(es):
Relevant Pages
|
