Hacker News Reader

Comment by yissp | Hacker News Reader

The one feature of perforce (which my current employer uses) that I miss going back to git is the "time lapse" view. It's like git blame but you also have a slider that can scroll through the revisions to a file. This is sorta similar to that, but I still think p4's version is still a better UX.

View on HN

There's a very nice Git History extension for VS Code that will do pretty much what you're describing:

https://marketplace.visualstudio.com/items?itemName=pomber.g...

Emacs' magit blame mode also supports recursive blaming - you can effectively step back and forward in time.

The inferiority of git tooling is the first thing I noticed when I moved from perforce to git for large, old, commercial production code (when using git for personal projects, you're basically only using 1% of the features as you're typically the only committer).

I enjoy git's way of handling version control better than perforce but there's no denying that p4v is an amazing tool for browsing through code that has a lot of history.

This will be a feature that I will be bringing to Git navigation in the future. For example, if you go to

https://public-001.gitsense.com/insights/github/repos?p=comm...

and click on the eslintrc.json file, you'll see all the versions for this file for the last year. And to quickly iterate through them, you can click on the version number on the left hand side.

In the future, I want to create a slider, among other things to make navigating history insanely easy, since blame, as this blog post points out, can result in a lot of context being left out.

Disclaimer: I'm the creator of the tool that I linked to above

It took me a while to find but you can do `gitk file` and it shows the file and revisions that modified that file, and you can use arrow keys to move between revisions.

Yup. P4 timelapse view is a killer feature.

Reply on news.ycombinator.com