You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I've been able to get 99% of where I want to be by using this project. On my gnome setup, I have been able to (a) make sure that when I open the Terminal application from launcher, an existing window is raised as long as the window exists already, and (b) make sure that Ctrl+Alt+T (using custom shortcut) raises the existing window or creates a new one. It's a great improvement!
What I can't figure out is this - when no Terminal window is open at all, the launcher will not open a terminal window. Simply nothing happens when trying to use the launcher to open gnome-terminal. I used the jumpappify-desktop command to replace "Exec=gnome-terminal" with "Exec=jumpapp gnome-terminal". It's strange because jumpapp gnome-terminal works to open a new terminal window when using the ctrl+alt+t shortcut, and also when running a command with alt+f2.
I'm wondering if it has something to do with launching a program from inside a program from inside a Desktop file... wondering if there is some kind of process ownership where the parent process dies and therefore gnome-terminal is a child process that also gets killed. Or else it could be because of something weird about the gnome-terminal application itself? The problem does not happen when I put jumpapp in front of other applications.
Have you seen something like this before, or have any suggestions?
The text was updated successfully, but these errors were encountered:
Interesting. I haven't seen that before, but I also haven't tested jumpappify-desktop on a variety of platforms, including recent versions of gnome.
I'm wondering if it has something to do with launching a program from inside a program from inside a Desktop file... wondering if there is some kind of process ownership where the parent process dies and therefore gnome-terminal is a child process that also gets killed.
Something like that sounds plausible. jumpapp already goes through some hoops to detach from the launching process, but it may not be foolproof.
I don't have a gnome desktop readily available to test on currently. If I spin one up maybe I can try it out and see what's going wrong.
Hi,
I've been able to get 99% of where I want to be by using this project. On my gnome setup, I have been able to (a) make sure that when I open the Terminal application from launcher, an existing window is raised as long as the window exists already, and (b) make sure that Ctrl+Alt+T (using custom shortcut) raises the existing window or creates a new one. It's a great improvement!
What I can't figure out is this - when no Terminal window is open at all, the launcher will not open a terminal window. Simply nothing happens when trying to use the launcher to open gnome-terminal. I used the jumpappify-desktop command to replace "Exec=gnome-terminal" with "Exec=jumpapp gnome-terminal". It's strange because jumpapp gnome-terminal works to open a new terminal window when using the ctrl+alt+t shortcut, and also when running a command with alt+f2.
I'm wondering if it has something to do with launching a program from inside a program from inside a Desktop file... wondering if there is some kind of process ownership where the parent process dies and therefore gnome-terminal is a child process that also gets killed. Or else it could be because of something weird about the gnome-terminal application itself? The problem does not happen when I put jumpapp in front of other applications.
Have you seen something like this before, or have any suggestions?
The text was updated successfully, but these errors were encountered: