Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 96216

Summary:	[typing] undo should end compound change earlier
Product:	[Eclipse Project] Platform	Reporter:	Genady Beryozkin <eclipse>
Component:	Text	Assignee:	Platform-Text-Inbox <platform-text-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	eclipse
Version:	3.1
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Genady Beryozkin

2005-05-21 06:18:53 EDT

It looks like the text undo is too eager on combining several changes into one
"compound" change.
I think that moving a cursor, using copy/paste, etc. should break the undo
change into smaller changes.

It is really annoying to be in a situation when its "all or nothing".

Genady

Comment 1 Dani Megert

2005-05-23 05:37:57 EDT

see also bug 49553

Comment 2 David Mansfield

2011-06-30 13:06:25 EDT

this is really important.  at the very least a "save" operation should break the compound change.  please please please!

i've been waiting release after release for this.

Comment 3 David Mansfield

2012-05-24 12:29:39 EDT

hard to imagine that everyone under the sun isn't annoyed by this.

use case:

edit some code. save. build. test. commit. go surf the web for an hour. come back. accidentally hit 'x' is youl editor then 'ctrl-z'.  changes you committed are now "undo'd" along with the "x".

Comment 4 David Mansfield

2014-04-23 10:04:35 EDT

are you kidding me?  am I crazy that I'm the only one hitting this issue?

today I came to work, unlocked my screen, accidentally hit enter in a file with a "properties" file open.  i hit ctrl-z and it erased the newline AND the last word typed yesterday which was saved, committed, and deployed to QA server!

How is it possible that undo can undo something I just typed and something saved and committed yesterday with one press of CTRL-Z, and how is this not affecting every eclipse user?

Comment 5 Eclipse Genie

2019-10-04 15:50:30 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.