No more character by character undo #1606
Comments
|
From a slightly different perspective, it would be nice if breaking the undo up was controllable. In vim's case it groups all characters typed in insert mode into a single undo transaction. |
|
I'm hoping that this enhancement request will be getting more attention. I'm putting up with the character-by-character undo but it annoys me every time. |
|
👍 Is this a thing that can be implemented? The single character undo is not the expected functionality for most text editing, unless you are in say, VIM mode. |
|
Agreed! This is a bit of a deal breaker. I hope it gets resolved soon. |
|
I'm looking forward to this being fixed, it reminds me of early Sublime Text. |
|
Dealbreaker for me as well. I'll keep checking in. |
|
I'm just now trying out Atom, and this is a HUGE bother. |
|
Every time I start using atom for it's other awesome features (such as the good markdown preview), the undo function makes go back to Sublime. I would even pay money for a bounty to have this implemented either natively or as a plugin. |
|
Bump. Is this being worked on at all? |
|
@kevinansfield Not being worked on currently, but it is planned to be included in Atom 1.0 |
|
I am kind of surprised this wasn't built before. Do you use atom to write atom? For a second 8000 I was thinking that perhaps this was done on purpose because everyone uses git, so if they want to undo quickly, they can just checkout the file again...but I do between commit undoes and it appears that others still do as well. |
|
Any (small) guidelines/ideas about how this should be implemented ? |
|
Well, besides being able to do it, it should be able to apply for find-replaces and therefore work across all files. When it just comes to typing in one file, I think most algorithms have some kind of timer that starts when typing stops. It resets if typing starts again before the timer hits 0--but if any mouse action occurs, timer hits 0. All these characters are batched together and effectively regarded as one action. If you want to get fancy, you could start it off at some generic timing, but have an ML algorithm learn how fast the typist typically is and restrict the timer down to that time plus some percentage...but that is probably overly fancy and prone to issues and maintainability complexities. A simple timer will probably work fine. |
|
Similar to vim, you could batch everything that is not saved or since the last activation of a tab...would be "simple" but would require timestamps for events such as opening of a tab. Just throwing ideas out there. |
|
I think it would be sufficient to just consider typing or deleting text a On Wed, Oct 29, 2014 at 6:43 PM, Bean notifications@github.com wrote:
|
|
What about batching changes between pauses, as in when changes start, wait for (an adjustable) pause in editing, then batch changes. |
That would not work for me. I often make a lot of big changes rapidly. On Wed, Oct 29, 2014 at 6:52 PM, James Trinklein notifications@github.com
|
|
This is being implemented in #4071 |
|
This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks! |
https://twitter.com/gnb/status/439155269432774657
Use a debouncer or something. SImilar to the way
content-editedevent works.The text was updated successfully, but these errors were encountered: