ido-at-point
vundo
ido-at-point | vundo | |
---|---|---|
1 | 15 | |
50 | 383 | |
- | - | |
10.0 | 7.1 | |
about 8 years ago | 6 days ago | |
Emacs Lisp | Emacs Lisp | |
- | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ido-at-point
-
What have you recently *removed* from your Emacs configuration?
(defun completing-read-at-point (start end col &optional pred) "Inspired by https://github.com/katspaugh/ido-at-point" (if (minibufferp) (completion--in-region start end col pred) (let* ((init (buffer-substring-no-properties start end)) (all (completion-all-completions init col pred (length init))) (completion (cond ((atom all) nil) ((and (consp all) (atom (cdr all))) (car all)) (t (completing-read "Completions: " col pred t init))))) (if completion (progn (delete-region start end) (insert completion) t) (message "No completions") nil)))) (setq completion-category-defaults nil) (setq completion-in-region-function #'completing-read-at-point)
vundo
-
Text Editor Data Structures: Rethinking Undo
vundo is a simpler implementation: it reuses Emacs's tree and just implements the visualisation part.
undo-tree is a reimplementation of Emacs's tree based undo, that supports a visualization.
* undo-tree LOC: 4700. https://gitlab.com/tsc25/undo-tree/-/blob/master/undo-tree.e...
* vundo LOC: 1350. https://github.com/casouri/vundo/blob/master/vundo.el
-
WTF is: "Re-entering top level after C stack overflow"?
Actually I put together vundo diff functionality which I use everyday; it's very simple so you can easily stick in your .emacs. Or perhaps will get added to vundo (maybe with a special color for the "diff-from" circle, or the ability to set a "from" and "to" for diffing across a few undos) . It's "on demand" rather than automatic, but I actually find it easier to get a diff buffer where I want it, then leave it as I move around the tree. Very happy with vundo.
-
Significant performance issues, am I doing anything really stupid?
And if you want a graphical undo without the large underlying data structure, give vundo a try. It just re-uses the same undo data structure emacs already keeps.
-
Is there anything like “undo at this line?”
If you still want undo visualization, there's vundo that gives you a tree display of the state of the built-in undo: https://github.com/casouri/vundo
-
Any winner-mode enhancement? Something like vundo.
Is there anything like vundo for winner-mode? Or is any body have a winner-mode configuration that would behave like vundo?
-
help understanding how to do undo/redo.
Take a look at vundo:
-
Let's share your top 3 packages that you can't live without.
vundo: Visualize the undo tree.
-
What's the best way to use undo-redo on emacs?
You could try vundo
-
What have you recently *removed* from your Emacs configuration?
I switched from undo-tree to vundo and am favorably impressed.
-
Vundo is great! (visual undo-tree for emacs-28)
Submitted a PR to simplify that.
What are some alternatives?
deadgrep - fast, friendly searching with ripgrep and Emacs
emacs-undo-fu
flymake-collection - Collection of checkers for flymake
undo-hl - Highlight undo operations so you never get lost
evil-goggles - Display visual hint on evil edit operations
meow - Yet another modal editing on Emacs / 猫态编辑
elfeed - An Emacs web feeds client
lispy - Short and sweet LISP editing
projectile - Project Interaction Library for Emacs
helm - Emacs incremental completion and selection narrowing framework
evil - The extensible vi layer for Emacs.