[Info-vax] JED on OpenVMS

[hb]

On 05/15/2018 05:07 PM, seasoned_geek wrote:
> On Saturday, May 12, 2018 at 7:45:32 AM UTC-5, hb wrote:
>> On 05/12/2018 02:07 AM, seasoned_geek wrote:
>>> I can't say I've ever used the VMS version of JED, but I know quite a few on the JED list who claim to and claim to like its EDT mode/support.
>>>
>>> Could any of you weigh in here with experience and realistic comparisons to other editors on OpenVMS. I must admit to barely scraping the surface of Jed capabilities, but I do like the List function. That's nice. No project needed.
>>>
>>> I would also like to know which terminal software you use Jed with. Do you get the same color display one does locally editing on *nix or is it just "one shade of gray?"
>>>
>>> Another thread here made me curious. Next time I need to boot my DS-10 I'll have to make a note to install Jed and give it a whirl.
>>>
>>> Appreciate your thoughts.
>>>
>>
>> Another thread about editors on VMS? It feels like there are so many. At
>> least JED was mentioned here:
>> https://groups.google.com/d/msg/comp.os.vms/mZiwmIkrTtw/pknxFyfYAAAJ
>>
>> Anyway, JED is more or less the only editor I use on VMS, in EDT mode,
>> with EDT keypad and xterm. More or less the same settings on Linux. Same
>> colors, same look and feel on both platforms.
> 
> Are you starting xterm with a script? If so, could you please share? I've been using an ancient script I found long ago and tweaked slightly. It's okay as long as I don't have SET TERM/INQ in LOGIN.COM. Then again, I've just been using EDT and LSE all of these years.

No script, just a customized .Xmodmap, an XTerm resource file, both in
my home directory, and then just xterm (Version: 312-2). For VMS, if
necessary, I prepend it with LC_ALL=de_DE.ISO-8859-1. My default is
en_US.UTF-8.

As you can see, I use decTerminalID: vt100. By default the newer xterm
versions use vt420. Then SET TERM/INQ takes very long. Also, with this
default, it didn't work for me as expected with VMS: I manually had to
set up the terminal with the number of lines and /noeight_bit to get
something working. I didn't really investigate, I switched to vt100.

.Xmodmap:
! F1..F4 and NumLock..Minus are mapped to KP_F1..KP_F4
keycode 0x43 =  KP_F1
keycode 0x4D =  KP_F1
keycode 0x44 =  KP_F2
keycode 0x6A =  KP_F2
keycode 0x45 =  KP_F3
keycode 0x3F =  KP_F3
keycode 0x46 =  KP_F4
keycode 0x52 =  KP_F4
keycode 0x4F =  KP_7            KP_7            KP_7            KP_7
keycode 0x50 =  KP_8            KP_8            KP_8            KP_8
keycode 0x51 =  KP_9            KP_9            KP_9            KP_9
! keypad Plus
keycode 0x56 =  KP_Subtract
keycode 0x53 =  KP_4            KP_4            KP_4            KP_4
keycode 0x54 =  KP_5            KP_5            KP_5            KP_5
keycode 0x55 =  KP_6            KP_6            KP_6            KP_6
keycode 0x57 =  KP_1            KP_1            KP_1            KP_1
keycode 0x58 =  KP_2            KP_2            KP_2            KP_2
keycode 0x59 =  KP_3            KP_3            KP_3            KP_3
keycode 0x6C =  KP_Enter
keycode 0x5A =  KP_0            KP_0            KP_0            KP_0
keycode 0x5B =  KP_Decimal      KP_Decimal      KP_Decimal      KP_Decimal
! Mode_switch usually is AltGr, which is not present on my old
! LK97W-A2 and LK47W-A2; map the Caps_Lock as Mode_switch and
! map EUR and umlauts to Mode_switch + <key>
remove Lock = Caps_Lock
keycode 66 = Mode_switch
keysym e = e E EuroSign
keysym c = c C cent
keysym a = a A adiaeresis Adiaeresis
keysym o = o O odiaeresis Odiaeresis
keysym u = u U udiaeresis Udiaeresis
keysym s = s S ssharp

XTerm:
XTerm.VT100.rightScrollBar: True
xterm*VT100.geometry: 80x36
xterm.VT100.c132: True
xterm.VT100.cursorBlink: True
xterm.VT100.scrollBar: True
xterm.VT100.foreground: black
xterm.VT100.background: white
xterm.*.renderFont: true
xterm.*.faceName: mono
xterm.*.faceSize: 10
xterm.*.decTerminalID: vt100