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 699717 - cursor position not retained on reopen when at end of file
cursor position not retained on reopen when at end of file
Status: RESOLVED FIXED
Product: gedit
Classification: Applications
Component: general
git master
Other Linux
: Normal normal
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2013-05-05 17:49 UTC by Adam Dingle
Modified: 2015-05-05 12:57 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Adam Dingle 2013-05-05 17:49:58 UTC 
Klaus Rädecke pointed out this bug on the mailing list:

1. In gedit, create a blank line at the end of a text file.
2. Place the cursor on the blank line.
3. Close the file.
4. Reopen the file in gedit.

The cursor will now be on the first line of the file.  It should be on the last line where it was when you last closed the file.
Comment 1 Sagar Ghuge 2014-01-06 07:36:16 UTC 
I am not able to produce this kind of Bug by doing the steps that you mentioned.
Comment 2 Adam Dingle 2014-01-07 01:24:51 UTC 
I can still reproduce this in gedit 3.10.2.

ghugesss, what version of gedit are you running?  If you follow the steps above, where is the cursor after step 4?
Comment 3 Sagar Ghuge 2014-01-07 08:40:16 UTC 
gedit 3.8.3...cursor appears at the last position where it was.
Comment 4 Sagar Ghuge 2014-04-07 09:04:37 UTC 
Adam, I can also produce this bug. Will try to have look into this. :)
Comment 5 Sébastien Wilmet 2014-12-17 11:35:24 UTC 
I've fixed a related bug recently:
https://git.gnome.org/browse/gedit/commit/?id=bfdad07ae28f08957c73c667c7e811bc7c3b54ef

So maybe this bug is fixed too.

It's *maybe* related to the spell checker plugin, or another plugin.
Comment 6 Sébastien Wilmet 2015-05-05 12:57:25 UTC 
Yes, I think this bug is fixed. Feel free to reopen it if the bug still occurs.