-
Notifications
You must be signed in to change notification settings - Fork 281
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add option to switch to undo-fu #1229
Conversation
Nice initiative! A couple of notes:
|
Yeah I'd love for others to test. Wasn't sure yet whether I wanted to rip out undo-tree completely or what. If testing goes well we can take that into account. One problem is that undo-fu has very strict Emacs version requirement. I'll check with the author if that's just because it's untested on older versions. |
Also goto-chg depends on undo-tree but I think it's a soft dependency. |
f893133
to
54278f2
Compare
There's been a new release to undo-tree, which might mitigate some of the problems people have been seeing. I'll leave this PR in limbo for a while. |
I would got on emacs28
I think this hooks should be added after function is defined
can not reach the author of undo-tree |
@jixiuf he responds to email, which you can find on his website: http://www.dr-qubit.org/undo-tree.html That said, I think he is unlikely to make any changes for Emacs28 unless they are totally innocuous for current emacs versions. The error you're seeing is surprising... they're changing the semantics of |
I already reported that to him. I got a fixed version by email but nothing
on git or ELPA yet. If someone else wants to bump it be my guest!
…On Fri, Jan 24, 2020, 05:46 Aaron Jensen ***@***.***> wrote:
@jixiuf <https://github.com/jixiuf> he responds to email, which you can
find on his website: http://www.dr-qubit.org/undo-tree.html
That said, I think he is unlikely to make any changes for Emacs28 unless
they are totally innocuous for current emacs versions.
The error you're seeing is surprising... they're changing the semantics of
#'symbol or add-hook is doing validation now...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1229?email_source=notifications&email_token=AAEXG3Z4U2GSN4XS6KMYXQ3Q7JXCXA5CNFSM4J6MMKRKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJZWWDQ#issuecomment-577989390>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEXG34PD43GVSW7UVCLF3TQ7JXCXANCNFSM4J6MMKRA>
.
|
Undo-tree 0.7.3 is now out and it should have fixed the above mentioned issue. |
Any update on this? Even in the case undo-tree is has been fixed, it's a fairly large and complex package, it installs hooks even when it's disabled.
Undo-fu by comparison:
Since this PR, I've published |
No updates yet. I wrote this to try undo-fu but at that time there were still bugs. Since then undo-tree received a promising update, so I decided I could focus on other things for the moment. I'll get around to it eventually, but of course if someone else wants to implement it I'd be happy to review and merge. I'm pretty sure I actually do want the provider variable though. 😄 |
Note: we also need to double check that goto-chg works fine when undo-tree isn't present. It's supposed to, but since evil for the moment requires undo-tree I'm not sure how much those code paths have been tested. |
Testing This seems more like a feature that could be supported in |
Any updates? |
If there's significant interest in an option for choosing undo provider please feel free to clean up the PR and resubmit. I don't have much time for evil at the moment. I've received no reports of bugs in the newer undo-tree versions so I don't consider it a priority. |
@jixiuf @aaronjensen Do you have a minimal reproduction example for that change in hook functions? I've tried the following on Emacs built from master and failed to reproduce it with the following in a file: (defun my-test () (message "Test"))
(add-hook 'post-command-hook 'my-test) |
Closed in favor of #1360 |
Just a draft branch that I'll be playing around with for a while. Opening this as a heads up.
Hopefully this can end up closing #1074, #418 and #522.