Bug 79496 - kate wish: undo/redo in a selected region
Summary: kate wish: undo/redo in a selected region
Status: RESOLVED INTENTIONAL
Alias: None
Product: kate
Classification: Applications
Component: general (show other bugs)
Version: 2.2.1
Platform: unspecified FreeBSD
: NOR wishlist
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
: 103021 310676 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-04-12 16:23 UTC by missive
Modified: 2012-11-26 07:38 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description missive 2004-04-12 16:23:58 UTC 
Version:           2.2.1 (using KDE 3.2.1, compiled sources)
Compiler:          gcc version 2.95.4 20020320 [FreeBSD]
OS:          FreeBSD (i386) release 4.9-STABLE

This may fall in to the "impossible" or "extremely difficult" area, but it would be really handy...

What I wish I could do sometimes is to select a region of a file and undo changes only inside of that area.

I use CVS -- and I know I need to learn more about how to use branching and tagging -- but I think this feature would fall somewhere between what we have now and using CVS.
Comment 1 Anders Lund 2004-04-12 17:28:03 UTC 
Nice wish, but you are right, that will not be the easiest thing to do.
Comment 2 Andreas Kling 2006-07-25 22:16:12 UTC 
*** Bug 103021 has been marked as a duplicate of this bug. ***
Comment 3 Dominik Haumann 2010-11-13 22:49:01 UTC 
Showing a list with undo actions from bug #103021 sounds sane. Undoing within a selection is something I've never seen before, and I don't really think this is deadly needed.
So focus should be on showing the undo list (needed for undoing in a selection anyway).
Comment 4 Christoph Cullmann 2012-10-25 23:28:42 UTC 
That wont work that easily, as then the continuity of the undo history doesn't hold and we might end with inconsistent stuff.
Comment 5 Dominik Haumann 2012-11-26 07:38:04 UTC 
*** Bug 310676 has been marked as a duplicate of this bug. ***