codemkin
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.
codemkin
-
Why is it so hard to see code from 5 minutes ago?
Oh hey, I've built this! My version would watch code files and snapshot a diff every few seconds. It took a little work to tweak the constants to keep the watching performant, but it was super neat being able to replay code. The main problem I faced was that changes often occur in different places in the file, so the history replaying jumps around a lot. With some proper editor integration, I could see it being pretty useful.
My version is super incomplete because I kind of lost steam when I couldn't figure out a really great reason why someone should use this, but hey, maybe it's worth another try: https://github.com/nicholaslyang/codemkin
undo-tree
-
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
-
How to undo the undo
That said, the situations seems murky still: the version in ELPA is newer (0.7.5), but it's still outdated, the home page advertises 0.8.2 as the latest version. And it moved to a different repository location. And looking at its history, it seems to never have included the version 0.7.5: https://gitlab.com/tsc25/undo-tree/-/commit/5da2a7aee98393d26a93c499dc79fcf793f161e1
- Undo-Tree.el
-
Why is it so hard to see code from 5 minutes ago?
It’s easier to mentally map that the default behaviour undo/redo for Emacs (which is not unreasonable, just complex).
The source for undo-tree contains documentation which very effectively describes the way the library works with examples and comparisons with how Emacs does things by default: https://gitlab.com/tsc25/undo-tree/-/blob/master/undo-tree.e...
- undo-tree repository's new home (Gitlab)
-
undo-tree git repository is not available anymore?
Looks like the repo is moved to https://gitlab.com/tsc25/undo-tree
What are some alternatives?
undotree - The undo history visualizer for VIM
emacs-undo-fu
gundo.vim - A git mirror of gundo.vim
klonk - A text editor with an sort-of-unusual undo/redo algorithm
vim-mundo - :christmas_tree: Vim undo tree visualizer
xray - An experimental next-generation Electron-based text editor
emacs-undo-fu-session
StyleCopAnalyzers - An implementation of StyleCop rules using the .NET Compiler Platform
WBO - Online collaborative Whiteboard that is simple, free, easy to use and to deploy
local-history - local-history for vscode