On 2014-01-07 14:09, Brian Schenkenberger, VAXman- wrote:
Sampsa Laine <sampsa at mac.com> writes:
Before this, I did an "xhost +" and ssh'd into RHESUS with X forwarding on.
{RHESUS$} create/term
X11 connection rejected because of wrong authentication.
X connection to _WSA48: broken (explicit kill or server shutdown).
X Error of failed request: BadConnection (fatal error on display connection)
Major opcode of failed request: 1 (X_CreateWindow)
Serial number of failed request: 0
Current serial number in output stream: 0
%XLIB-E-ERROREVENT, error event received from server
Xlib: client uses different protocol version (11) than server (0)!
%DECW-E-CANT_OPEN_DISPL, Can't open display
Any idea what is causing this?
Server and version? (Assuming you're using your Mac? OSX ???)
VMS Arch/Versions? (Assuming a VAX? VMS V?.? TCPIP???)
On 2014-01-07 06:57, Sampsa Laine wrote:
Turns out Terminal.app has built-in support for the keys, being as it derives largely from xterm source code I believe.
Obviously it does not, as it has bugs that xterm don't, when it comes to VT100 emulation...
Anyway, I've now got my frankenkeyboard for the occasional moments when I really need to edit a file on a VMS box..
Good enough for you then, I guess. :-)
Johnny
Sampsa Laine <sampsa at mac.com> writes:
Before this, I did an "xhost +" and ssh'd into RHESUS with X forwarding on.
{RHESUS$} create/term
X11 connection rejected because of wrong authentication.
X connection to _WSA48: broken (explicit kill or server shutdown).
X Error of failed request: BadConnection (fatal error on display connection)
Major opcode of failed request: 1 (X_CreateWindow)
Serial number of failed request: 0
Current serial number in output stream: 0
%XLIB-E-ERROREVENT, error event received from server
Xlib: client uses different protocol version (11) than server (0)!
%DECW-E-CANT_OPEN_DISPL, Can't open display
Any idea what is causing this?
Server and version? (Assuming you're using your Mac? OSX ???)
VMS Arch/Versions? (Assuming a VAX? VMS V?.? TCPIP???)
Before this, I did an "xhost +" and ssh'd into RHESUS with X forwarding on.
{RHESUS$} create/term
X11 connection rejected because of wrong authentication.
X connection to _WSA48: broken (explicit kill or server shutdown).
X Error of failed request: BadConnection (fatal error on display connection)
Major opcode of failed request: 1 (X_CreateWindow)
Serial number of failed request: 0
Current serial number in output stream: 0
%XLIB-E-ERROREVENT, error event received from server
Xlib: client uses different protocol version (11) than server (0)!
%DECW-E-CANT_OPEN_DISPL, Can't open display
Any idea what is causing this?
sampsa
On 06/01/2014 18:35, Johnny Billquist wrote:
On 2014-01-06 18:32, Paul_Koning at Dell.com wrote:
Sure, that would make sense. Color; sixel; other good things. But the first requirement would be strict conformance to the spec.
Yes, which pretty much rules out everything except xterm. :-)
xterm had DEC people involved, so I have at least some confidence that they might have checked it against some specs, and not just made up their own assumptions.
I had a good look at the xterm source code to see how difficult it would be to use it as the basis of a decent java-based terminal emulator.
'There be dragons' was as far as I got...
My second thought would be to write an simulation of a VT320 which was capable of running the VT320 ROM. That seems like a pretty good idea, but that's as far as it's got. There is an terminal emulator called VMSTAR in the Freeware V5.0 archive which some of you may remember - apparently this takes that exact approach.
SLAVE::ARCHIVE$:[MEDIA.DECUS.FREEWAREV50.VMSTAR]
Regards, Mark.
--
http://www.wickensonline.co.ukhttp://hecnet.euhttp://declegacy.org.ukhttp://retrochallenge.nethttps://twitter.com/urbancamo
On 1/7/2014 12:57 AM, Sampsa Laine wrote:
Turns out Terminal.app has built-in support for the keys, being as it derives largely from xterm source code I believe.
Anyway, I've now got my frankenkeyboard for the occasional moments when I really need to edit a file on a VMS box..
Sampsa
Can you do an export of your terminal settings and post the files somehwere? I'd be interested in trying them out.
John H. Reinhardt
Turns out Terminal.app has built-in support for the keys, being as it derives largely from xterm source code I believe.
Anyway, I've now got my frankenkeyboard for the occasional moments when I really need to edit a file on a VMS box..
Sampsa
On 2014-01-06 18:32, Paul_Koning at Dell.com wrote:
Sure, that would make sense. Color; sixel; other good things. But the first requirement would be strict conformance to the spec.
Yes, which pretty much rules out everything except xterm. :-)
xterm had DEC people involved, so I have at least some confidence that they might have checked it against some specs, and not just made up their own assumptions.
As far as "colored terms with graphics" goes, I'm not sure what terminal emulators Sampsa would be thinking of. xterm definitely supports ANSI color sequences, as an extension, and like has been mentioned, there is now also Sixel support (although that is far from perfect yet). If we get that a bit more improved, soft fonts is not that far away afterwards, and then we'll have a proper VT220, and so on. I talked a bit with the person writing the sixel support about soft fonts a few weeks ago. It might happen...
Johnny
paul
On Jan 6, 2014, at 11:59 AM, Sampsa Laine <sampsa at mac.com> wrote:
Well if you're going to go through all that hassle, why not go for one of the coloured terms with graphics?
sampsa <sampsa at mac.com>
mobile +44 7961 149465
On 6 Jan 2014, at 18:43, Paul_Koning at Dell.com wrote:
On Jan 5, 2014, at 10:53 AM, Johnny Billquist <bqt at softjar.se> wrote:
On 2014-01-04 21:08, Sampsa Laine wrote:
Been playing remapping some "slime slim, full size Apple" kbd but the results aren't great. Does anybody have a canonical list of VT220 escape codes, preferably in hex (I think my term's escape sequence is broken)..
Why don't you use xterm? The mappings are already correct. And as a bonus, you actually get a VT100 emulation with less bugs.
Sounds like an interesting project would be to do a proper VT2xx emulator (ideally from the DEC terminal SRM, if a copy can be found, failing that from published VT2xx manuals). Wx would be a good way to do that, since it s a very useable portable development environment. Or to make it even more straightforward, in WxPython?
paul
On 2014-01-06 17:43, Paul_Koning at Dell.com wrote:
On Jan 5, 2014, at 10:53 AM, Johnny Billquist <bqt at softjar.se> wrote:
On 2014-01-04 21:08, Sampsa Laine wrote:
Been playing remapping some "slime slim, full size Apple" kbd but the results aren't great. Does anybody have a canonical list of VT220 escape codes, preferably in hex (I think my term's escape sequence is broken)..
Why don't you use xterm? The mappings are already correct. And as a bonus, you actually get a VT100 emulation with less bugs.
Sounds like an interesting project would be to do a proper VT2xx emulator (ideally from the DEC terminal SRM, if a copy can be found, failing that from published VT2xx manuals). Wx would be a good way to do that, since it s a very useable portable development environment. Or to make it even more straightforward, in WxPython?
Actually, I think except for the soft fonts, xterm does VT220 pretty correctly too.
Johnny