Closed mesamorpho closed 10 years ago
Thanks for reporting the issue such detail.
Have fixed it, please get the latest version, and try again.
Wow, thanks for fixing this so quickly!!
The tabs are not reloaded anymore when debugging finishes, and the situation I described in my example now works flawlessly. However, in my usual work environment -- with a lot of buffers across several tabs -- the undo history appears to remain intact for all buffers, except for the one in which I set the breakpoint. I have run a few tests in my usual work environment, and sometimes, all buffers seem to have kept their undo history... In other words, for the most part the bug appears to be fixed but on occasion it still occurs for at least one buffer... I've tried to narrow down the exact circumstances but momentarily I don't know how safely reproduce the bug. I'll get back to you if I find a way to reproduce it each time.
Ok, I figured out why VIM sometimes still loses its undo history during debugging. In short, the problem occurs when a file being debugged is open as a split window.
Here's how you can reproduce it:
This should be fixed completely, as the mksession way to save current vim session is not necessary now. A completely new tab is created to be used debugging UI now.
I usually use several VIM tabs holding various files I'm working with. Whenever I complete a debug session, either by letting the program run through (F5) or simply exiting the debugger (F6), the files in all of my tabs are reloaded and as a by-product, my undo history for them is lost.
As a test I did the following:
In this case only the file in the second tab lost its undo history but in my usual working environment (with 49 buffers across 34 tabs) I seem to lose the undo history of all files loaded.