Improve Undo, persist history buffer across tab closure

[1hko]

VSCode makes me fearless closing files amongst my crowded tabs, because I know I will never lose work or that work's context, including that work's recent changes. In Zed, when I close a file, all of that history is gone :(

1. Make a change in a file
2. Save it
3. Close the file
4. Reopen the file using command-shift-T
5. Press command-Z to undo.. nothing to undo 👎

It I close an entire project window or quit Zed, I think it's safe to clear file history. That's how VSCode handles it anyway. In any other case, maintaining this valuable history has become essential to my workflow, freely opening and closing files without losing any work.

[towhans]

I store undo history per file in vim. Simple and powerful. I miss that feature in Zed.

" Keep undo history across sessions by storing it in a file
if has('persistent_undo')
    let myUndoDir = expand(vimDir . '/undodir')
    " Create dirs
    call system('mkdir ' . vimDir)
    call system('mkdir ' . myUndoDir)
    let &undodir = myUndoDir
    set undofile
endif

[tintor]

Lack of persistent undo with auto-save is the main thing preventing me from moving from vim to zed.

Persistent undo history that is persisted even if zed is closed.
It is ok to clear versions from undo history older than a month.

[viniciusnevescosta]

I wanted to share a very stressful situation. I just lost an entire file of code because I right clicked on another file name. For some reason the editor selects 2 files (the one I was editing and the one I selected), and this behavior doesn't make sense, if I wanted to select 2 files I would have simply pressed shift or cmd and then clicked on the files. I ended up losing an empty file that I wanted and what I was editing. I'm sorry, but this should be a basic function of an IDE.