3

Anyone knows how to accommodate for new gnome-terminal-server magic?

Before gnome-terminal got its new "client/server" architecture I used to use it as vim wrapper with great success for many years. Since --disable-factory got dropped the following code doesn't lock the process (due to forking) therefore it's useless as an editor for e.g. text areas in browser:

#!/bin/bash
TERMINAL=gnome-terminal
TERMARGS="--disable-factory --full-screen -e"

for ARG in "$@"; do
    # arguments quotation, etc.
    ARGS="$ARGS $ARG"
done

$TERMINAL $TERMARGS "vim $ARGS"
  • What if you start another terminal server (and use your stuff in a new client inside that server)... – don_crissti Aug 18 '16 at 18:45
  • 1
    Did any of you actually try that? It doesn't work. Server just dies after 10 seconds no matter what I do. And if I try to open a terminal in newly created server, it doesn't spawn any windows - the gnome-terminal process just locks until gnome-terminal-server dies. – cprn Aug 19 '16 at 12:56
  • If I somehow manage to spawn a gnome-terminal window with --app-id parameter, I have a feeling, it will not lock the wrapper execution anyway. The idea is for the wrapper to wait until the terminal closes so it could only then give the control back to the parent. – cprn Aug 19 '16 at 15:18
  • 1
    chrisirwin.ca/posts/multiple-instances-of-gnome-terminal Looks helpful... if you're okay with some root-permission setup. – stevesliva Mar 19 '18 at 18:58

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.