When start back through it, the thing which seems to always derail me isn't the writing or the subject matter, it's the rabbit hole of trying to find royalty free, reasonably priced images of things like an actual VT-100. (No, you can't just use images from Wikipedia, even though I stuck it in as a place holder. The vast majority of images on Wikipedia are there in violation of copyright, and without attribution.)
Old paper terminals we used to use for system consoles on the VAX 11/750. An actual photo of Jack Goeken (I seem to have lost mine.) Pictures of other things, I have a list of somewhere, but don't have off top of my head. When I get all of that done I'll push the book out.
As to my rant about the 12 year olds "maintaining" most OpenSource . . .Some years ago I was using Linux Mint. At that time Konsole, the KDE terminal application was __really__ close to VT-100. As I recall there were about 5 keys which were incorrect in EDT. I filed the bug reports and exchanged emails with the "maintainer." He literally told me he removed many of those keys because they conflicted with VIM. I told him to either take VT-100 out of the package description or to test with a real VMS machine before pushing out a new release.
"I don't have access to whatever that machine is.""I will expose my DS-10 Alpha to the Internet and give you an account on it. I will even send you an electronic copy of this book so you know how to use both EDT and LSE."
http://www.theminimumyouneedtoknow.com/app_book.html"No, you aren't helping me and you aren't being very nice about it. I'm the maintainer."
Aaaaaand it went downhill from there.I don't use Mint anymore. In fact, I have written and blogged about the Konsole incident many times and now that I'm thinking of it, will be certain some version of it makes it into PoA.
Bringing this all back around to Jed.Do either the creator of the images or the solution provider mind if I coble all that stuff together in a post on Logikalblog? I've been trying to keep some of the obscure stuff there because searching the list archives is a real PITA and attachments don't always seem to be there.
On 07/06/2018 04:38 PM, Mike Hayes wrote:
You sir, made my day. Especially with the last part. I've been battling VT100 compatibility for ages and the lack of people who actually understand the standard is quite scary. I truly worry that soon, only us few will be those left who have actually read and understood the standards set forth years ago. And to think -- It truly is not that hard of a standard and it works quite well. I think standards compliance is a dying breed and we're one of the casualties of it. On 07/06/2018 08:20 AM, Roland Hughes wrote:Knowing nothing but recognizing something I will offer up this fish. It might be a Red Herring and it might be The Big Kahuna. The VT100 mode of every free terminal on Linux isn't even close to VT100 compatible. You have to hack and override a vast number of definitions. Minor discussion here. https://groups.google.com/forum/#!searchin/comp.os.vms/linux$20vt100$20emulation%7Csort:date/comp.os.vms/WTSEx6j7qTc/3GsFMSAMBgAJ Wee bit of rehash here: http://www.logikalsolutions.com/wordpress/information-technology/xterm-and-vt-emulation/ Even more discussion here https://groups.google.com/forum/#!searchin/comp.os.vms/linux$20vt100$20emulation%7Csort:date/comp.os.vms/9DIFTtYLpn0/SOhgHPFXOAAJ My guess is, with a much older distro, your changes work fine, just like my xterm script worked fine for decades. Recently there has been yet another regression of VT100 support. My script stopped working if my login.com had $ SET TERM/INQ which means to inquire from the terminal what its settings should be and then tell the OS. Those backward question marks are a red flag. Seen them many times trying to use various terminals to communicate with VMS systems. I would suggest trying the VT102 stuff from the first discussion link. It may not be a final answer, but, it should make a big improvement. I will guess this VT100 regression happened the way most of them do. Someone bitched to the 12 year old "maintaining" the package that keystroke blah or terminal string yaha didn't let them use some feature of VIM they really wanted and both of them together knowing less-than-zero about either OpenVMS or a VT100, hacked it, took out whatever automated tests that failed, and checked it in. On 07/06/2018 12:46 AM, Chris wrote:Hi, I've installed XJed and Jed and applied the CBrief patch to create a pretty good Brief clone under Linux. Whilst I'm happy with the result, Jed works very well, XJed however has an issue with the display of menus. I'm assuming that it is something I need to fix, but what do I need to fix/check? As I don't see problems elsewhere, it would be great if I could apply a XJed specific fix, rather than fiddling with a system setting, but if I have to, I will. System details: 32GB RAM, 64-bit laptop running Debian 10 / Buster / Testing / next-stable. It has a hybrid video card, but right now it is running Intel, as I ran into a couple of NVidia nasties. Screenshots of XJed and Jed attached. Rgds Chris-- Roland Hughes, President Logikal Solutions (630)-205-1593 http://www.theminimumyouneedtoknow.com http://www.infiniteexposure.net http://www.johnsmith-book.com http://www.logikalblog.com http://www.interestingauthors.com/blog http://lesedi.us/ http://onedollarcontentstore.com_______________________________________________ For list information, visit <http://jedsoft.org/jed/mailinglists.html>.
-- Roland Hughes, President Logikal Solutions (630)-205-1593 http://www.theminimumyouneedtoknow.com http://www.infiniteexposure.net http://www.johnsmith-book.com http://www.logikalblog.com http://www.interestingauthors.com/blog http://lesedi.us/ http://onedollarcontentstore.com