Oh how I love Ubuntu and all its features, but this "bug" has been making me angry for so long and I've finally decided to ask for help here.
I've assigned all .php
files to be opened with gedit whenever I double-click them in nautilus. Now, the behavior is strange.
- I have no gedit running
- I double click a file to be opened
- A gedit window opens and the file loads
- I double click another file to be opened
Now, there are 2 possible outcomes:
5A) The file opens in the same gedit window in a new tab
5B) The file opens in a new gedit window, resulting in 2 gedits running.
Whether A or B happens seems to be totally random and keeps on going infinitely. That means I double click on 100 files and I might end up with 60 gedits, some of which will have 1 tab, some will have 2 tabs, some will have 3 tabs…
This is extremely annoying and a fix for this would be very appreciated. Anyone ever tried to fix this problem?
This has happened in Ubuntu 10.04, 10.10 and 11.10. All Ubuntu versions I've ever tested.
Best Answer
Why...
gedit
has quite an interesting algorithm to determine whether it opens a new instance or if it opens in a tab in an existing instance.Located in the source file
gedit-app.c
in the functionstatic boolean is_in_viewport
, the algorithm tests if the current gedit instance isIf all are true then gedit opens in the same instance in a new tab otherwise it opens in a new window.
In summary - the only realistic way of changing the behaviour is to change the algorithm...
How...
The following is a quick way to get a consistent way of opening gedit... it will always open a new instance.
install the basic development tools
get the source
make the change
Open gedit-app.c
add
return FALSE;
as shown and save.What this does is to always exit the routine saying "i'm not running in a viewport and therefore always open a new instance"
If you use
return TRUE;
this will always open in an existing instance of gedit in a new tab...give it a unique package name
OK, we need to give the package a unique name to prevent repository updates from overwriting your changed package
now append
+yourname
to the top line version and save the file i.e.Note - to be absolutely sure - after installing the modified package below, lock the version as per the linked question below.
build the package
Go for a coffee...
Linked Question: