bash script start gedit but don't stop there

Watchin · 10-21-2009, 02:28 AM

This command will stop until gedit is close...

gedit $file

How do you call gedit without it stopping?

lutusp · 10-21-2009, 02:36 AM

Quote:

Originally Posted by Watchin

This command will stop until gedit is close...

gedit $file

How do you call gedit without it stopping?

Code:

$ gedit "$file" &

But this invocation of gedit will exit if you exit the shell that called it. To prevent that happening, do it this way:

Code:

$ nohup gedit "$file" > /dev/null 2>&1

This essentially cuts gedit off from the shell that launched it, e.g. makes it independent.

Watchin · 10-21-2009, 09:52 PM

Thanks!

Watchin · 10-24-2009, 04:22 AM

Executing ./nt test opens the file test. But it still locks the terminal till gedit is closed.

Saved this as nt

Code:

#!/bin/bash
echo "input=$*"
nohup gedit "$*" > /dev/null 2>&1

This does the same.
alias gi='gedit > /dev/null 2>&1'

lutusp · 10-24-2009, 06:55 AM

Quote:

Originally Posted by Watchin

Executing ./nt test opens the file test. But it still locks the terminal till gedit is closed.

Saved this as nt

Code:

#!/bin/bash
echo "input=$*"
nohup gedit "$*" > /dev/null 2>&1

This does the same.
alias gi='gedit > /dev/null 2>&1'

Very sorry! In an earlier post I left off a critical symbol. It should be:

Code:

$ nohup gedit "$*" > /dev/null 2>&1 &

The final "&" causes the line to be spawned as a separate process, essentially disconnecting it from the parent. The only reliable way to close the spawned process is to kill it by its PID, or log out.

To capture the new process PID, do this:

Code:

$ nohup gedit "$*" > /dev/null 2>&1 &
$ mypid=$!

Then you can:

Code:

$ kill $mypid

Later on.

Watchin · 10-29-2009, 02:24 AM

Quote:

Originally Posted by lutusp

Very sorry! In an earlier post I left off a critical symbol. It should be:

Code:

$ nohup gedit "$*" > /dev/null 2>&1 &

The final "&" causes the line to be spawned as a separate process, essentially disconnecting it from the parent. The only reliable way to close the spawned process is to kill it by its PID, or log out.

To capture the new process PID, do this:

Code:

$ nohup gedit "$*" > /dev/null 2>&1 &
$ mypid=$!

Then you can:

Code:

$ kill $mypid

Later on.

Thanks for the update.

Now for the fun part, gedit .mybash, it opened without locking the terminal....

The nohup line doesn't work well in an alias, but this works:

alias ge='nt $*'

alias without the external would me more tidy, but I'm good.

arizonagroovejet · 10-29-2009, 04:55 PM

The wording of the original post makes no sense to me, but given what's been posted since, I'm thinking maybe this will do what you want.

Code:

$ gedit filename & disown

E.g. you open gnome-terminal, type that, then close gnome-terminal and gedit stays running. If you were to omit the 'disown' part then gedit would close along with gnome-terminal.

Watchin · 10-30-2009, 01:39 AM

Quote:

Originally Posted by arizonagroovejet

The wording of the original post makes no sense to me, but given what's been posted since, I'm thinking maybe this will do what you want.

Code:

$ gedit filename & disown

E.g. you open gnome-terminal, type that, then close gnome-terminal and gedit stays running. If you were to omit the 'disown' part then gedit would close along with gnome-terminal.

My original post was a bit ambiguous, this would have been more clear
"This command will stop the terminal until gedit is closed..."

Sweet.
Thanks.