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 326224 - Can't type while saving
Can't type while saving
Status: RESOLVED DUPLICATE of bug 722512
Product: gedit
Classification: Applications
Component: general
git master
Other All
: Normal enhancement
: ---
Assigned To: Gedit maintainers
gedit QA volunteers
Depends on:
Blocks:
 
 
Reported: 2006-01-08 17:41 UTC by Murray Cumming
Modified: 2014-08-12 20:42 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Murray Cumming 2006-01-08 17:41:30 UTC 
When editing a file via a gnome-vfs SCP connection (I love that I can do this now), saving takes a few seconds. During this time, I can highlight text, but I can't change the text of the document. This is annoying, because I have a habit of repeatedly pressing Ctrl-S while I work.
Comment 1 Paolo Maggi 2006-01-08 17:58:41 UTC 
This is the expected behavior.

It is a bit unfortunate but supporting editing while saving greatly complicates the code (expecially in the case an error occurs while saving).

I think we can live with this limitation for 2.14. We will try to find a possible solution in the future.
Comment 2 Tom Medhurst 2009-03-31 11:53:22 UTC 
I'm not familiar with this code yet, but...

Could we not take a copy of the content of the editor, and then proceed to save it on a background-thread?

We could either choose to ignore subsequent Saves whilst this is happening, or use a first-in-first-out queue to line up the save requests?

If there was a problem saving we can use the error panel to show the problem and if you need the state, we could offer a button which allows users to revert to the state of the document before the save? (I don't know if this is necessary, but it is an option)
Comment 3 Sébastien Wilmet 2014-08-12 20:42:10 UTC 
Bug #722512 is more precise.

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