It's working fine for me. Is Git-LFS properly configured? Can you please provide some small test repository for which the problem is reproducible? Please send to smartgit@syntevo.com.

If you can use Git command line, then you can also use SmartGit. Did you try my above suggestion?

"That's unexpected, if "credential.github.com.useHttpPath" is configured. Can you please check Preferences, Authentication see to whether SmartGit actually stores multiple passwords, one per repository?"

Is this still an issue? Please note that without further replies we will be closing this ticket soon.

Is this still an issue. If so, what exactly is the RFE? Please note that without further replies, we are going to close this ticket soon.

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.