Question

5

Gedit from terminal - inconsistent behaviour

rated 0 times [ 5] [ 0] / answers: 1 / hits: 15136 / 3 Years ago, thu, june 3, 2021, 7:07:36

I tend to frequently open a text file from the terminal with a command like so:

gedit filename.txt

However, the behaviour is inconsistent; sometimes, the focus will leave the terminal and will not return until I have closed the file. Other times, the terminal will maintain a prompt, as if I had run:

gedit filename.txt &

Why this discrepancy?

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

ligenvirt

Add To Favorites

Follow

Total Points: 238

Total Questions: 98

Total Answers: 100

Location: Senegal

Member since Fri, Aug 21, 2020

4 Years ago

ligenvirt questions

1 Ubuntu Server 20.04.3 LTS won't boot after installation

Tue, Aug 17, 21, 02:28, 3 Years ago

1 How can I customize my GTK theme?

Thu, Sep 23, 21, 17:55, 3 Years ago

1 20.04 vs 20.10 and backup questions

Mon, Oct 18, 21, 03:34, 3 Years ago

1 Files exist, but "cannot open shared object file: No such file or directory" 20.04

Sun, Feb 26, 23, 22:34, 1 Year ago

1 I have python 3 installed on both apt and snap - should I remove one of them?

Fri, Jul 29, 22, 05:03, 2 Years ago

View All

answered 3 Years ago eighethod · Accepted Answer

It usually depends on whether gedit is already running.

If it is, the open jibbery gets sent to the open process and depending on how things are running (Gedit 3.x seems to have some weird behaviours) it'll fork into a new window or just a new tab.

If it's not, a new process is started as a child of the prompt, so it blocks the prompt.

If it really annoys you, you can create an alias, or a ~/bin/ script to override the standard behaviour and force it to fork out with & every time.