You are the first one to mention "WSLg" ... so GitKraken is running as Linux process? That's something completely different than running GitKraken on Windows and accessing files from the Linux file system. Did you try to run SmartGit inside WSLg?

What about "git status", with the Git executable being Git for Windows`?

Also, sending periodical thread dumps to investigate the slowness may be helpful: https://docs.syntevo.com/SmartGit/HowTos/Creating-Thread-Dumps.html

You can configure the encoding in Repository|Settings .

In the meanwhile, the GUI design is relying even more on the separation of directory and files control (for example, due to the new split views). Technically, this would require significant effort to implement both options. Hence, it's very unlikely that this will ever be addressed.

Both, Blame and Investigate are dialog-less operations and should stay so; adding some menu item like "Recompare with blame-ignore-revs" also isn't elegant. But I agree that Blame and Investigate should honor "blame.ignoreRevsFile" configuration.

Note that the overall problem seems to be less pressing for SmartGit because both, Blame and Investigate, already allow to go to the previous line once you find yourself located at a reformat commit.

"..."-indicator and tooltip will be present for 22.1 Preview build 19046.

Duplicate of: https://smartgit.userecho.com/en/communities/1/topics/966-

Please give 22.1 build 19042 a try which should now indicate Git-LFS states: "handled", "lockable", "locked by yourself", "locked by <...>" and "should be handled" (but is actually a plain blob).

Will an indicator in the icon, including some more details in the tooltip be sufficient?