After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 148594 - don't return to commandline until gedit quits
don't return to commandline until gedit quits
Status: RESOLVED DUPLICATE of bug 112908
Product: gedit
Classification: Applications
Component: general
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: Gedit maintainers
gedit QA volunteers
Depends on:
Blocks:
 
 
Reported: 2004-07-27 16:19 UTC by Mark Ivey
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.1/2.2



Description Mark Ivey 2004-07-27 16:19:52 UTC
Description of Problem:
The 'gedit' command will return right away if
there is already an existing gedit session.  If
gedit is being used as $EDITOR, this confuses
programs like svn and cvs which wait for the
editor program to return as a cue that the user
has finished editing the commit messages.

Steps to reproduce the problem:
1. Start gedit
2. set $EDITOR to 'gedit'
3. Run a command like 'svn commit'

Actual Results:
gedit connects to the existing session and returns
right away.

Expected Results:
gedit wouldn't return until the user closed the
window.

How often does this happen? 
always

Additional Information:
something like a '--new-session' option would
probably be enough for this to not be a problem. 
Personally, I would prefer if --new-session and
--new-window were the defaults.  Especially when
you have several viewports/desktops, it is pain
when a command like 'gedit blah.txt' steals the
gedit window off a different viewport/desktop.
Comment 1 Paolo Borelli 2004-08-01 10:44:53 UTC
I'm marking this as a dup of 112908 since as far as I can see they're asking for
the same thing... unfortunately this doesn't look easily fixable with the way
gedit works currently. I may well be wrong though...

*** This bug has been marked as a duplicate of 112908 ***