GNOME Bugzilla – Bug 745282
Add --wait option to wait for terminal to close
Last modified: 2019-04-03 18:26:03 UTC
We have a use-case for the behaviour of the gnome-terminal invocation waiting until the new terminal has closed. We have an option to spawn a new terminal with a specific environment which runs "make menuconfig" on the kernel, and we need to know when the user has finished editing the configuration. Previously it was possible to hack around gnome-terminals behaviour of exiting immediately if another instance was running by using --disable-factory, but this has since been removed. We'd like something along the lines of --wait where the new client waits for the master so say that the new terminal has been closed.
(In reply to Ross Burton from comment #0) > Previously it was possible to hack around gnome-terminals behaviour of > exiting immediately if another instance was running by using > --disable-factory, but this has since been removed. We'd like something > along the lines of --wait where the new client waits for the master so say > that the new terminal has been closed. Are you aware of the hidden --app-id option? That is how I run a separate instance of gnome-terminal while developing. Will that work for you?
As in run the server with a custom app id and then quickly spawn a client with the same id? That's fine for development but not exactly graceful for real use.
This is already implemented in the new client: $ ./gterminal shell --wait (The new client isn't finished however, so it's noinst for now.)