xray
klonk
xray | klonk | |
---|---|---|
4 | 7 | |
8,607 | 217 | |
- | - | |
0.0 | 4.7 | |
almost 5 years ago | 12 days ago | |
Rust | Java | |
MIT License | 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.
xray
-
Glad Emacs never will be sunset
Hadn't them already abandoned another one before?
-
Introducing Zed—A lightning-fast, collaborative code editor written in Rust by the creators of Atom.
Im super glad to see that this is probably the continuation of atom-xray and that the devs are still doing new projects! The move from web to full Rust is interesting, I wonder how it will perform.
-
Reject modernity
Even before Microsoft bought them they were focusing on a completely new editor: https://github.com/atom-archive/xray. That's since been scrapped, and from the contribution graph on atom it's pretty clear the only remaining development is from community volunteers.
-
Why is it so hard to see code from 5 minutes ago?
Before Microsoft bought GitHub and killed Atom, they were working on Xray[1] & Memo[2]:
> Memo is an operation-based version control system that tracks changes at the level of individual keystrokes and synchronizes branches in real time.
[1] https://github.com/atom-archive/xray
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...
What are some alternatives?
gundo.vim - A git mirror of gundo.vim
x-ui - 支持多协议多用户的 xray 面板
undo-tree
codemkin - [Moved to: https://github.com/NicholasLYang/codemkin]
NvChad - Blazing fast Neovim config providing solid defaults and a beautiful UI, enhancing your neovim experience.
diodon - Aiming to be the best integrated clipboard manager for the Unity desktop
Atom - :atom: The hackable text editor
doomemacs - An Emacs framework for the stubborn martian hacker
undotree - The undo history visualizer for VIM