I have written a small encapsulation of the interface of pseudo.cpp into a C++ class. This allows the use of multiple
PTs per app. If you find it useful, I post it and the changes necessary for (x) gterm to use it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Jeep, it has a bugzilla. Hail to sourceforge! I took the idea from rxvt and xterm to close the terminal when the direct child dies.
Question: Can the read from the PT return 0 bytes? I think this means EOF, but I'm not sure.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have written a small encapsulation of the interface of pseudo.cpp into a C++ class. This allows the use of multiple
PTs per app. If you find it useful, I post it and the changes necessary for (x) gterm to use it.
This would also include the fix for the background process bug.
Sounds great to me. The pseudo.cpp file is "just an example", bu that doesn't mean it can't be a fully-featured one.
What is the "background process bug"?
Bug-ID 647975. I will provide a patch with my changes and the fix to that problem in a few minutes.
Are you saying GTerm has a bugzilla bug tracker, or is that Bug-ID for something else? What package has this bug? I'm a big confused.
Jeep, it has a bugzilla. Hail to sourceforge! I took the idea from rxvt and xterm to close the terminal when the direct child dies.
Question: Can the read from the PT return 0 bytes? I think this means EOF, but I'm not sure.