G'day, I head up the Sublime Merge team.

Thank you for taking the time to share all this feedback - I genuinely appreciate it and will be looking into this further.

A couple of things to note:

> It puts headings on diff sections. I want to copy text that from Sublime Merge and search for the identifier in my editor. Sorry, S.O.L.

I've just added support for this internally, thank you for the feedback!

> I want to search for things across changes - sorry, S.O.L. - "someIdenifier" doesn't exist in the current code. When was it deleted? Let me search.

You can use the search tool (Ctrl + F) and add the query `contents: someIdentifier`. It will return every commit which contains that term within the changes.

Thanks again for the feedback!

thanks! to be clear tho. searching the commit comment is one thing. I want to search the file contents across history. which files used to contain the word "foo"

also, the tree based folder and file blame. GitHub, the website, shows this info by default. It would be nice if sublime merge had a similar view. The code view on github, the default view for any project, shows a line for each file and folder, followed by the commit msg summary in the middle, and a commit date on the right

G'day, I head up the Sublime Merge team.

I'd love to hear your feedback on how we can improve the blame functionality! I can look into getting anything resolved there.

[Thanks to be opened for suggestions]

- One major improvement would be to provide a button to "View blame prior to this change" like Gitlab blame does (screenshot below):

https://drive.google.com/file/d/1BjXpQNlFgHKIJz-5SmJIxYB6fGD...

Because c++ codebases nowadays are full of commits that just reformat or refactors code (clang-format, update to smart pointers, update to new api, etc) and so if I just want to find out the original commit which introduced that codeline (because I want to know the _original_ motivation for it), it means in Gitlab I just need to click 3 or 4 times on said button to skip all such formats/refactor commits until I get to the one I'm interested in. That is easy in Gitlab, while SublimeMerge just let me click on the SHA of the last change for the codeline, and from there I'm lost I don't know how to keep "blaming back" like Gitlab easily let me.

- In the same vein of easy skipping blame changes until the one you want, it would help a lot supporting the git config setting blame.ignoreRevsFile:

https://git-scm.com/docs/git-config#Documentation/git-config...

Thanks and long life to Sublime!

Thank you! Let me know if anything is missing for you and I can work on getting it added in.

G'day, I head up the Sublime Merge team.

Firstly, thanks for using it and supporting us!

If you haven't already, it would help immensely to get a bug report here: https://github.com/sublimehq/sublime_merge/issues/new/choose

I'll definitely look into this further and get it sorted