Sublime Forum

Tree Folder Collapses


After selecting a commit, say you go to the Files->Tree view and you expand directory upon directory and navigate your way to a particular file. When you click on it, you get this awesome blame view of that file at that moment in the commit history.

Now you want to see that file at a different point in time, so you select another commit. Instantly the Tree view collapses back up. You now have to go and navigate to that file again, potentially clicking subdirectory upon subdirectory.

Why is this? Am I missing something? Is there a better way to navigate the versions of a file over time?



If you want to see the history of a single file over time like this, you want the dedicated Blame view; the blame you get by navigating to a file this way is temporary/transient kind of view, meant more for quicker ad-hoc type investigations.

In the dedicated blame view, the view is devoted to a single file, shows you only commits that modified that file, and allows for easier navigation.

One way to do this is to use Navigate > Blame from the menu or the Blame... command from the command palette. That opens up a panel similar to the Sublime Text Goto Anything panel that allows you to enter fuzzy terms to narrow in on a file. Once you pick one, you go into Blame mode. The list of commits on the left can be navigated as you like.

You can also get to the same point by clicking the three dots button at the top right of a file and choosing blame. This allows you to get to the blame view from wherever you are (such as if you wanted to navigate to the file by other means).

Once you’re in blame view, you can get out of it by clicking the close button in the top right.

1 Like


Blame view is very good, but not quite the same thing. It’d be great to see the state of all files in the tree at a particular commit. If the tree did not collapse immediately, you could do this.

What else could you do? Your tree view could show markers like ST does at a particular commit, so you could see all of the files that changed in that commit.

Then, you could go to the next commit and see the state of the tree and all the files that changed.



See my related issue comment: