Error reading undo-tree history
- Dominant language
- Emacs Lisp
- Stars
- 22.7k
- Forks
- 3.1k
- Avg merge
- 10h 46m
- Merged PRs (30d)
- 4
Description
### I confirm that...
- [X] I have searched the [issue tracker](https://github.com/doomemacs/doomemacs/issues), [documentation](https://docs.doomemacs.org), [FAQ](https://docs.doomemacs.org/-/faq), [Discourse](https://discourse.doomemacs.org), and [Google](https://google.com), in case this issue has already been reported/resolved.
- [X] I have read "[How to Debug Issues](https://doomemacs.org/d/how2debug)", and will use it to provide as much information about this issue as possible.
- [X] The issue can be reproduced on the **latest** available commit of Doom.
- [X] The issue can be reproduced on a stable release of Emacs, such as 27 or 28. *(Doom does not support development builds like 29+ or any version ending in .50 or .9x)*
### Expected behavior
Undo-tree load at the beginning of each session.
### Current behavior
For a few files, when trying to load the undo-tree after switching off the computer I get the error:
`Error reading undo-tree history from "/home/henrique/.emacs.d/.local/cache/undo-tree-hist/.db1428e98a890a22602b3c780f11ca9a27c0b728.~undo-tree~.zst"
`
There are files that keep the history normally, but for a few it bugs constantly.
I've tried:
`recentf-save-list` before switching off
Also:
`undo-tree-save-history`
I use doom-emacs with daemon. If I kill the server and start again, the undo-tree is loaded normally, the problem is usually after I restart the computer.
(I searched for this particular error and did not find any solution for doom-emacs specifically. Following the behavior of a few files (that is, loading the undo-tree in each session), I understand that doom undo-tree should load for each session)
### Steps to reproduce
1. Open emacs after restart computer.
2. Open previously edited file with a undo-tree history.
3. Depending on the file, the history is not loaded
### System Information
https://pastebin.com/wvNV7UGf
Contributor guide
Assessment
This issue has not been assessed yet.