Avoiding shell killing its CHILD processes

[baum]

Hello all,

Most of the applications I open, are opened through the shell, like so:
$ emacs mycode.c &
$ gedit mydoc.txt &

Problem is, that when I close the calling shell, it kills all of its child processes.
This usually happens some time after I've opened the files, and seems to always catch unguarded....

How could this be avoided?

[elrohir]

What I always do is run things using screen. (It's in the repos.)
This is especially useful for logging in via SSH from somewhere else and not having lost all the work in emacs. (For this you have to detatch the screen session using Ctrl-A, D).

For your purposes you can start screen, run gedit, then close the terminal window. Screen will still be running: return to where you started gedit from by opening any old terminal and running "screen -r".