klonk
codemkin
klonk | codemkin | |
---|---|---|
7 | 1 | |
217 | 2 | |
- | - | |
4.7 | 0.0 | |
22 days ago | almost 4 years ago | |
Java | Rust | |
GNU General Public License v3.0 or later | - |
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.
klonk
-
Undo done the right way!
While surfing the web I came across this blog post: Resolving the Great Undo-Redo Quandary.
- Resolving the Great Undo-Redo Quandary
-
Hacker News top posts: Nov 11, 2022
Resolving the Great Undo-Redo Quandary\ (31 comments)
-
Why is it so hard to see code from 5 minutes ago?
My goofy lil' homemade editor does it this way: If you go back in the past and change it, the future becomes the past. This might sound confusing, but effectively it means that the undo stack contains the actual history of "what happened". This means you can hop to any past or future state linearly with undo & redo alone. I just find this easier than navigating tree GUIs and things that aren't worth the trouble to me. It can still lead to a bit of mental gymnastics in extreme cases.
https://github.com/zaboople/klonk
Note that in theory this can cause an exponential growth of the undo/redo stacks because it makes an upside-down copy of the future when you change the past; but in practice it's never been an issue.
I was thinking of adding a feature to navigate back to "last change-the-past", which wouldn't be hard.
It at least makes more sense than most science fiction time-travel plots...
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
What are some alternatives?
gundo.vim - A git mirror of gundo.vim
undotree - The undo history visualizer for VIM
undo-tree
diodon - Aiming to be the best integrated clipboard manager for the Unity desktop
doomemacs - An Emacs framework for the stubborn martian hacker
xray - An experimental next-generation Electron-based text editor
StyleCopAnalyzers - An implementation of StyleCop rules using the .NET Compiler Platform
vim-mundo - :christmas_tree: Vim undo tree visualizer
local-history - local-history for vscode