Resolving the Great Undo-Redo Quandary

This page summarizes the projects mentioned and recommended in the original post on

Our great sponsors
  • InfluxDB - Collect and Analyze Billions of Data Points in Real Time
  • Mergify - Updating dependencies is time-consuming.
  • SonarQube - Static code analysis for 29 languages.
  • undotree

    The undo history visualizer for VIM

    Plug for the Vim undotree plugin, which exposes Vim’s undo tree in a navigable UI. It’s saved my butt in the rare occasion I need it.

  • klonk

    A text editor with an sort-of-unusual undo/redo algorithm

  • InfluxDB

    Collect and Analyze Billions of Data Points in Real Time. Manage all types of time series data in a single, purpose-built database. Run at any scale in any environment in the cloud, on-premises, or at the edge.

  • Vim

    The official Vim repository

  • consult

    :mag: consult.el - Consulting completing-read

    Emacs does this by default. Anything you delete ends up in the "kill ring", and you can cycle through that when pasting ("yanking") something. Packages like Consult[1] provide version of the yank-pop command that, instead of cycling through the kill ring, make it searchable.


  • diodon

    Aiming to be the best integrated clipboard manager for the Gnome/Unity desktop


    So much cognitive load.

    Just configure Vim to put everything you delete in your clipboard and use a clipboard manager like diodon[1] with 1000 items.

    Of course works also outside of Vim, you just have to copy the part you might want to reuse before deleting/modifying.


  • vim-lsp

    async language server protocol plugin for vim and neovim

    Did you misspell "editor with language intelligence?"

    Because yeah, vim won't beat IntelliJ, but you can get it to be pretty decent with LSP:

  • doomemacs

    An Emacs framework for the stubborn martian hacker

    There is a very opinionated and batteries-included "Vim-y" Emacs called Doom [0]. A decent way to approach this if you don't want to start writing elisp outta the gate to have fancy editor features is to learn enough of the Doom config to tweak it to your liking, then add some elisp customization in as needed. I personally use this approach, usually cribbing config and elisp tweaks from the top contributors' configs.

    The Evil layer that Doom and most everyone seems to use for Vim modes works really well, and has a lot of ways to tweak things (e.g. changing `j` to `gj` for going through line breaks in normal mode; I forgot what that setting is called...).

    There is something to be said by bootstrapping your config entirely from scratch instead of using a "config framework" like Doom, but that can be too daunting and end up preventing one from trying things out.


  • Mergify

    Updating dependencies is time-consuming.. Solutions like Dependabot or Renovate update but don't merge dependencies. You need to do it manually while it could be fully automated! Add a Merge Queue to your workflow and stop caring about PR management & merging. Try Mergify for free.

  • Quicksilver

    Quicksilver Project Source

    For a browsable clipboard history on macOS, I recommend LaunchBar (; docs at I used to use the Clipboard Plugin of the free and open source app Quicksilver (, which worked fine but was slightly less streamlined. Some people prefer Alfred (

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts