Timeline for How to suspend VIM history?
Current License: CC BY-SA 3.0
20 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 3, 2016 at 18:43 | vote | accept | Luis A. Florit | ||
| Dec 3, 2016 at 18:43 | comment | added | Luis A. Florit |
As you suggested, it seems that I can recover what I need just using g+ and g- instead of u and <CTRL>R each time I cannot get where I want in the undo tree. I was unaware of all this undotree thing, that was introduced in VIM 7. I'm getting too old..... :)
|
|
| Dec 3, 2016 at 18:25 | comment | added | JoL | Don't. Didn't you say that the undo tree is what you needed? There is no need to make my answer work. I wrote my last comment on this question before I saw your last comment on my answer. That makes @SatoKatsura answer the correct one. | |
| Dec 3, 2016 at 18:24 | history | edited | Luis A. Florit | CC BY-SA 3.0 |
added 160 characters in body
|
| Dec 3, 2016 at 18:17 | comment | added | Luis A. Florit |
Sorry if I am not making myself clear. My claim about sed was just to say that the modifications I want to make in the function FF I can make them at the very end of the VIM session, not necessarily every time I write the buffer. Even with sed instead of VIM. Take a look in the second EDIT, to see if I am more clear now. I am trying to make your answer work.
|
|
| Dec 3, 2016 at 18:15 | history | edited | Luis A. Florit | CC BY-SA 3.0 |
added 386 characters in body
|
| Dec 3, 2016 at 17:58 | comment | added | JoL |
The problem you give "all those last 20 history commands are lost" is fixed with the existence of the undo branches, so it's confusing that you then want to fix your problem by avoiding their creation. You say you can get the result you want with sed, but sed can't do your undos, so how's that going to work? If you were able to "suspend history", what kind behaviour would you expect of vim when you do an undo afterwards? The only behaviour I could visualize is to group those changes (along with the undos) in one undo block, hence my answer. But if that's not it, what is?
|
|
| Dec 3, 2016 at 17:55 | history | edited | Luis A. Florit | CC BY-SA 3.0 |
edited body
|
| Dec 3, 2016 at 17:24 | history | edited | Luis A. Florit | CC BY-SA 3.0 |
added 272 characters in body
|
| Dec 3, 2016 at 17:19 | history | edited | Luis A. Florit | CC BY-SA 3.0 |
added 272 characters in body
|
| Dec 3, 2016 at 17:17 | history | tweeted | twitter.com/StackUnix/status/805098591798829056 | ||
| Dec 3, 2016 at 16:39 | answer | added | JoL | timeline score: 0 | |
| Dec 3, 2016 at 15:02 | comment | added | Luis A. Florit |
@Celada: I didn't know about vim.se, I would have tried that. Anyway, it seems Sato knows how to help.
|
|
| Dec 3, 2016 at 14:25 | history | edited | Satō Katsura |
Not the robots you're looking for.
|
|
| Dec 3, 2016 at 13:47 | comment | added | Celada | @SatoKatsura you're absolutely right! | |
| Dec 3, 2016 at 13:44 | comment | added | Satō Katsura | @Celada I believe it's vi.stackexchange.com, or Vi and Vim. | |
| Dec 3, 2016 at 13:43 | answer | added | Satō Katsura | timeline score: 12 | |
| Dec 3, 2016 at 13:30 | comment | added | Celada |
This question is on topic for this site, but since it pertains to a fairly esoteric potential feature of VIM, have you considered trying vim.stackexchange.com instead? I mean, I know UNIX and I know vi, but to me vi's undo command undoes once, and then when you press u again it undoes the undo ("redo"). That's real vi. So I and other users of this site might not know the answer to your question.
|
|
| Dec 3, 2016 at 13:09 | review | First posts | |||
| Dec 3, 2016 at 13:14 | |||||
| Dec 3, 2016 at 13:08 | history | asked | Luis A. Florit | CC BY-SA 3.0 |