[Info-vax] VMS on remote desktops

[VAXman- at SendSpamHere.ORG]

In article <iap2f1$77d$1 at usenet01.boi.hp.com>, "FredK" <fred.nospam at dec.com> writes:
>
><VAXman- @SendSpamHere.ORG> wrote in message 
>news:00AA5DF9.FB8A6183 at SendSpamHere.ORG...
>> In article <iangna$fam$1 at usenet01.boi.hp.com>, "FredK" 
>> <fred.nospam at dec.com> writes:
>>>
>>><VAXman- @SendSpamHere.ORG> wrote in message
>>>news:00AA5D7F.1DF48D65 at SendSpamHere.ORG...
>>>> In article <ian2st$876$1 at usenet01.boi.hp.com>, "FredK"
>>>> <fred.nospam at dec.com> writes:
>>>>
>>>> I use mosy my Linux laptop and my Mac.  I've done plenty with 'xmodmap'
>>>> for
>>>> the keycode hacks.  I've worked around most of the problems using the 
>>>> font
>>>> server.  I access the VMS system(s) with 'ssh -X' but I've also toyed 
>>>> with
>>>> using 'xnest'.
>>>>
>>>> As for fonts, the double-high/double-wide terminal fonts always cause
>>>> issue
>>>> within 'xterm'.  I export $CREATE/TERMINAL for doing debugging and,
>>>> without
>>>> the font server, some of the line drawing stuff and, I believe, the
>>>> reverse
>>>> video use in the character-cell debugger cause issue.   I don't really 
>>>> use
>>>> any of the other GUI toys that came with CDE.  A functional terminal is
>>>> all
>>>> I ask for -- and which I have now with the font server.
>>>>
>>>
>>>Thanks.  I suspect a ot of VMS people (like UNIX folks) are still mostly
>>>command line types.  Care to share your xmodmap tricks?  Do you need to
>>>switch back and forth between settings to use VMS-style vs UNIX/Mac style
>>>input?
>>
>> No.  I have not problem with need to switch back and forth.  I have Linux
>> on a 17" Toshiba laptop (as one example) that has a full alternate keypad.
>> Since the keypak is WEENDOZE biased already, its usefulness in Linux does
>> not mean all that much to me.  However, it does make VMS editing easier as
>> I can approximate things like the EDT keypad.  Of course, it's crippled in
>> that it has the stupidly large [+] key where DEC keyboards had [,] and [-]
>> keys.
>>
>> !!!!!! [+] = [,]    CTRL-[+] = [-]
>> keycode 86 = 0xffac            0xffad
>> !!
>> keycode 82 = 0xff94
>> keycode 63 = 0xff93
>> keycode 106 = 0xff92
>> keycode 77 = 0xff91
>> !!
>> pointer = 3 2 1 4 5 6 7
>>
>> The pointer is leftie mapping for me.  Others may choose not to do this if
>> they are no in their "right mind."
>>
>>
>> On the Mac, I use the Mac full keyboard which has an alternate keypad that
>> looks like the DEC LK style keyboard's alternate keypad.  I don't need any
>> .Xmodmap for that.  I'm using iTerm when I'm not launching a DECterminal.
>> There's a profile section where I have defined the more typical key escape
>> sequences.  On the Mac, the .Xmodmap file is:
>>
>> keycode 79 = 0xff91
>> keycode 89 = 0xff92
>> keycode 83 = 0xff93
>> keycode 75 = 0xff94
>> keycode 77 = 0xffac
>>
>
>Thanks.  On the VMS end when you launch a DECterm - do you do any setup to 
>use a specific VMS keymap file?  There are two types of keymap files for 
>PC-style keyboards on VMS that normally are used when you log into CDE (you 
>would have to set a logical name if you were not in CDE as the "default" 
>keymap).  One type is a "VT" style where we ignore the engravings and map 
>the keys positionally incuding PF1 instead of NumLock and the editing keys 
>in the "right" finger positions - and the other is the "PC" style where we 
>map the engravings including NumLock.

No, nothing special on the VMS side.  I do use the CREATE/TERMINAL quite
often for debugging.  I have a command procedure which does CREATE/TERMINAL
and defines DBG$INPUT/DBG$OUTPUT to the FT created.  I may use an xterm for
most of the other work but I do expect to be able to debug in this fashion,
save for Macro on V8.4. ;) :P

 
-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG

All your spirit rack abuses, come to haunt you back by day.
All your Byzantine excuses, given time, given you away.