New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Restore-cursor-position is broken #184
Comments
I can't really reproduce the issue with mate-1.15.x gtk3 on fedora 24, but maybe this is a random issue, so i will review your PR. |
Ok, now i see the different :) |
For the record, cursor position is not outside the display window needing a scroll to see it. Instead, a new cursor position fails to be remembered. I've adopted a work-around that seems to force cursor position to be remembered for a file:
This seems to work 100%. Next time this file is opened, the cursor will return exactly where you placed it. Like it should. If step 4) is skipped, the cursor position is never remembered and no dialog appears in step 5). Or, if a cursor position was previously remembered, it doesn't update to the new location as it should. This is very repeatable in Ubuntu-Mate 16.04 with Mate 1.12 or 1.14. Does anyone know where this data is stored? I tried to find it unsuccessfully. |
I guess it is somewhere in home folder because i noticed that using pluma as root will never restore the cursor position with your PR. |
I think it was solved in #191... |
YES. It's fixed in Ubuntu-Mate 16.10 beta 2 which is running Pluma 1.15.2. The symptoms are different than #191 (see my previous comment here) but it is possible the fix for that scrolling race condition is appearing differently to me. So they may be different results from the same bug. Based on Pluma 1.15.2 working perfectly, this can be closed. Thanks! |
The setting is under org.mate.pluma -> restore-cursor-position and defaults in Ubuntu-Mate 16.04 to enabled. I think most have this same default. Same buggy behavior in Mate 1.14.1 just verified.
My workaround is use gedit but that's cheating.
Here's what I found that could point to the problem...
If you go to the end of a line and type: (Space)(Backspace)
This makes Pluma think the file has been altered - it hasn't really, of course.
Now, close the Window by clicking "X" or Ctrl+W or Alt+F4.
Answer "Close without saving".
Now it possibly remembers! Fairly repeatable here. Generating that dialog is a factor?
I'm not sure how long it's been since this worked right but surprised no one else misses this feature like I do.
The text was updated successfully, but these errors were encountered: