Comment 24 for bug 776499

I found the workaround in #7 helpful, but it had two problems, one major, one minor: It doesn't dissociate vim from the terminal, so if you close the terminal window vim gets abruptly terminated too; also, vim spits out quite a few GTK warnings on the console, which I'd rather not see. Here's what I'm using now:

function gvim {
    /usr/bin/gvim -f $* > /dev/null 2> /dev/null & disown
}

I tried nohup to begin with, but it didn't seem to help. The process was still killed by a sighup when the terminal closed. The redirect and disown seems to work better.