For anyone that uses emacs, there is an excellent plugin "undo-tree" that solves this problem in a slightly different way. Everytime you undo a series of actions and then perform a new action, it creates a branch in the "tree". You can then visualize the tree and move through it quickly your entire buffer history.
Why is it so hard to see code from 5 minutes ago?
71–80 of 424 posts
Re: Why is it so hard to see code from 5 minutes ago?
#72Does anyone know if there’s a good way to do this in VS Code? I often hold cmd-z until I get to some version and copy code from it. Ideally I’d like to have a separate window where I can see a previous version without affecting the current file/view. Before anyone comments, git doesn’t cut it for this because no one commits after every -+1
not super polished nor is it actively maintained but has promise
Re: Why is it so hard to see code from 5 minutes ago?
#73Earlier quoted context omitted.
That's what a git browser is for. It's not like your code is gone forever, unless you are undisciplined.
I certainly don’t commit things every five minutes, so this doesn’t help.
Re: Why is it so hard to see code from 5 minutes ago?
#74Re: Why is it so hard to see code from 5 minutes ago?
#75Does anyone know if there’s a good way to do this in VS Code? I often hold cmd-z until I get to some version and copy code from it. Ideally I’d like to have a separate window where I can see a previous version without affecting the current file/view. Before anyone comments, git doesn’t cut it for this because no one commits after every -+1
https://marketplace.visualstudio.com/items?itemName=Wattenbe...
Re: Why is it so hard to see code from 5 minutes ago?
#76Earlier quoted context omitted.
This is excellent... for Vim users. A lot of developers either are not willing or haven't gotten around to learning the complexities of Vim, and use other IDEs like JetBrains or Eclipse. This workflow won't work for them.
JetBrains' various apps can do this as well with a feature called "Show Local History". I'm not sure where it is in the menus but you can hit shift twice and type it in. It automatically commits after every change since the IDE was opened, and can easily be diffed and reverted as needed. Reverting saves another entry, so you can revert back to the future as well.
Re: Why is it so hard to see code from 5 minutes ago?
#77Re: Why is it so hard to see code from 5 minutes ago?
#78Earlier quoted context omitted.
When I looked, it had the same problem that Dropbox has with this: a textual listing with only timestamps. I need semantic info! Show me the differences. Don't make me choose from this arbitrary list. I want to scan through the versions very, very quickly.
Not sure what you're looking at, but IntelliJ 2020.3 gives me a list w/ timestamps in 1/3 of the modal, then a diff viewer in the other 2/3. I can down-arrow through the versions and the diff updates.
Re: Why is it so hard to see code from 5 minutes ago?
#79For anyone that uses emacs, there is an excellent plugin "undo-tree" that solves this problem in a slightly different way. Everytime you undo a series of actions and then perform a new action, it creates a branch in the "tree". You can then visualize the tree and move through it quickly your entire buffer history.
Re: Why is it so hard to see code from 5 minutes ago?
#80Earlier quoted context omitted.
This is excellent... for Vim users. A lot of developers either are not willing or haven't gotten around to learning the complexities of Vim, and use other IDEs like JetBrains or Eclipse. This workflow won't work for them.
JetBrains' various apps can do this as well with a feature called "Show Local History". I'm not sure where it is in the menus but you can hit shift twice and type it in. It automatically commits after every change since the IDE was opened, and can easily be diffed and reverted as needed. Reverting saves another entry, so you can revert back to the future as well.