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 653409 - Indent Dropped after Pressing Enter on a Blank Line
Indent Dropped after Pressing Enter on a Blank Line
Status: RESOLVED OBSOLETE
Product: gedit
Classification: Applications
Component: general
2.30.x
Other Windows
: Normal normal
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2011-06-25 19:42 UTC by Brian
Modified: 2011-06-26 09:12 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Brian 2011-06-25 19:42:38 UTC 
The current indent level is dropped when pressing the enter key on a blank line.  This issue does not occur when moving between lines using the mouse or arrow keys.  Various combinations of indent settings and plugin settings do not appear to affect this behavior.

I have found this issue in gedit versions 2.30.1-1 and 2.29.4-1 of the MS Windows binary release.  This issue does not occur in the MS Windows 2.28.3-1 or the current Debian binary release.

Having searched for information on this issue, I found the following possible source of the problem.

http://git.gnome.org/browse/gtksourceview/commit/?id=186127e1163236b365d658e7121684ccfa16c3c3
Comment 1 Ignacio Casal Quinteiro (nacho) 2011-06-26 00:39:32 UTC 
Hey, this was indeed due to that, but we removed it again as there were a lot of people complaining about it. Please update your gtksourceview.
Comment 2 Brian 2011-06-26 04:54:45 UTC 
The fix has not made it into the current gedit MS Windows binary release.  Are there plans to release a new gedit MS Windows binary release built using the latest gtksourceview trunk?

I am going to return the status to unconfirmed as it is still appears to be an issue with the product indicated in the bug.

Thanks for the quick response as we at least know the source of the problem.
Comment 3 Ignacio Casal Quinteiro (nacho) 2011-06-26 09:12:56 UTC 
Well the bug is indeed obsolete as it was fixed, for windows, I will try to make a release when I get some time to test gtk+ 3 on windows. Thanks for reporting.

PS: in relation to the 2.30.x series I will not make any more releases.