Why is it so hard to see code from 5 minutes ago?
web.eecs.utk.edu
Why is it so hard to see code from 5 minutes ago?
1–10 of 424 posts
Re: Why is it so hard to see code from 5 minutes ago?
#2Re: Why is it so hard to see code from 5 minutes ago?
#3jetbrains IDEs have a local history feature that seems to do this
Re: Why is it so hard to see code from 5 minutes ago?
#4Having a slider/timeline does sound like an excellent idea. Also just being able to non-destructively go back to a previous state and have a peak without changing the files I'm working on right now would would really well for me I think.
Of course git is an answer to this, but I don't want to think about making a checkpoint.
Re: Why is it so hard to see code from 5 minutes ago?
#5Re: Why is it so hard to see code from 5 minutes ago?
#6Re: Why is it so hard to see code from 5 minutes ago?
#7jetbrains IDEs have a local history feature that seems to do this
Re: Why is it so hard to see code from 5 minutes ago?
#8In Vim you can achieve something quite similar with gundo plugin. Vim tracks all your changes in a tree by default and you can also use the "earlier" and "later" commands with a time delta to go back and forward a specified amount of time. So in Vim, to see the state of the file 5 minutes ago, you type ":earlier 5m" . Gundo is a visualisation on top of the builtin undo. I'm sure Emacs has something similar and probab…
Re: Why is it so hard to see code from 5 minutes ago?
#9Re: Why is it so hard to see code from 5 minutes ago?
#10jetbrains IDEs have a local history feature that seems to do this
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.