Is there a nice way of getting the TTY of a new xterm on it's creation semi-auto-magically and suppressing the xterms initial prompts? I am trying to write to the window from C/C++, but I need the pts number of the TTY... So how do I find out what TTY is the new one?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Getting the TTY of a new xterm 2
- Thread starter jstreich
- Start date
-
1
- #2
-
1
- #3
ericbrunson
Technical User
Rather than trying to start an xterm and write from it externally, have the xterm run whatever you need as a subprocess, then the output of stty or tty is available to it.
ericbrunson
Technical User
I meant to say:
Rather than trying to start an xterm and write TO it externally, have the xterm run whatever you need as a subprocess, then the output of stty or tty is available to it.
Rather than trying to start an xterm and write TO it externally, have the xterm run whatever you need as a subprocess, then the output of stty or tty is available to it.
- Thread starter
- #5
indeed I think I have a way to do it by grabbing the tty... But it has a couple of problems that I have yet to solve. The biggest making the new term window sleep for the length of the program execution.
Eric, this is a good idea, but I'm not sure how I'd do it... I'd have to write two programs instead of one, and then get the child process to talk to it's parent using named pipes or some other technology (without talking to other instances of the program).
I think I'm on to something with these suggestions... thank you, both (start to each of you).
Eric, this is a good idea, but I'm not sure how I'd do it... I'd have to write two programs instead of one, and then get the child process to talk to it's parent using named pipes or some other technology (without talking to other instances of the program).
I think I'm on to something with these suggestions... thank you, both (start to each of you).
ericbrunson
Technical User
You might look at the source code for xconsole (part of the X11 code base) and see how they do it.
BTW, using named pipes or sockets to talk in a client server fashion would save a lot of problems that may crop up if the xterm is closed. The 2nd program could be as simple as "cat /var/run/myfifo". You could put that in a script and specify that as the shell the xterm should run, or use the -e switch.
Alternatively, it's not too difficult to code up a scrolling text window in X and skip the xterm completely, the code is all there for the taking.
BTW, using named pipes or sockets to talk in a client server fashion would save a lot of problems that may crop up if the xterm is closed. The 2nd program could be as simple as "cat /var/run/myfifo". You could put that in a script and specify that as the shell the xterm should run, or use the -e switch.
Alternatively, it's not too difficult to code up a scrolling text window in X and skip the xterm completely, the code is all there for the taking.
- Status
Similar threads
- Locked
- Question
- Locked
- Question