[Konsole-devel] [Bug 127285] Honor VT100 Remote Printing Sequences

[Michael Trausch]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=127285         




------- Additional Comments From fd0man gmail com  2006-05-22 00:42 -------
That is probably why it shouldn't be enabled by default.  If I could actually work with the source code myself, I would be more then happy to take a look at implementing it.  However, I know very little about C, let alone C++ and the KDE framework.  I was looking into it to see if I'd be able to check out konsole and see how it could be implemented.  I am *still* (several hours later) waiting on SVN to give me a tree of the trunk to look at it.  I'd be happy to wait on the feature, as I work around it right now by simply using PuTTY.  But I rather like the idea of using KDE applications, and Konsole is more aesthetically pleasing, anyway.

It *is* a rather simple feature -- I think that it's being over-thought here.  It is supported by VT100 and ANSI hardware terminals, and so I think it should be supported in the software emulation of them, as well -- optionally.

This also happens to be the way that 'lynx' uses for remote printing -- which I still find useful when I'm using 'lynx' over an ssh or telnet session to a local library's text online catalog.  It still definitely has its uses.  Don't get me wrong, I'm more then willing to be patient and wait for its implementation, because I have neither the know-how nor the money to accelerate its implementation into Konsole, and I do realize that it isn't an often used feature in the 2000's, but it is still useful.

When I have the money, I'd be more then happy to send a bounty on this one -- it is that useful.  It's nothing to do with data channels or anything -- just the simple VT100/ANSI remote-terminal-printing support.  The shell script that I attached is the script that I use nearly every day to use this feature in PuTTY, and that probably shows more concisely what I'm looking for.  At this point in time, executing that script under Konsole just displays on the terminal what should be diverted to a printer, Konsole ignores the ESC sequences.  (This should probably be the default behavior with a toggle option, similar to PuTTY.)

(Also, the script may/may not show up properly when you view it... the START_CODE / END_CODE variables contain the ESC sequences inserted directly into the file via the ^VESC key combination in vim.)