Please consider adding an icon or a glyph to display the LFS tracking state of each working tree file/file type. GitKraken, Bitbucket and Gitlab all have a little tag that says LFS next to files being tracked as LFS, it would be nice if Smartgit had the same.

For denoting the LFS-state for *Log* files, see topic 1438.

Situation: after one or more commits you notice you have committed to the wrong branch. Now applying the commits to the correct branch means to:

- checkout the correct branch

- cherry-pick the new commits from the wrong branch

- reset the wrong branch to the commit before the cherry-picked commits

It would be nice if this could be done with one high-level command.

I use a scripting language Autohotkey. And i would love to see Syntax highlighting in smartgit for it. 

Since I have seen several requests for more support of syntax highlighting for other languages, I assume it makes sense tha smartgit should  provide an interface that allows users to „define“ their own syntax highlighting and associate this to a file Extension.

If there is already a possibility to do so, please point me in that direction.

Thanks for considering 

The new feature added on https://smartgit.userecho.com/communities/1/topics/3-compare-show-long-left-and-right-line-above-each-other is useful only for lines up to 200 characters, but still ineffective against very long lines line 1000 characters. 

I personally hate the new vertical line panel which show up eating my scarce vertical screen space. So, the first thing I ever do on a new SmartGit installation is to figure out how to disable that feature, which comes enabled by default.

I agree there is no simple solution when diffing very long lines because enabling word wrap will be bad for long lines line 100~200 characters, because the standard space is by standard constrained, then enabling word-wrap will be more awkward/bad: 

Then I would suggest a feature to only wrap lines which are really by like 1000 characters, and keep the usual lines up to 200 characters not wrapped. Because usually lines up to 1000 characters are not code lines but documentation pages like README.md files or Wiki pages, which are edited on text editors with word-wrap enabled. For example, on SmartGit I would see these documentation lines diff changes very bad:

While on my text editor, they are nicely displayed with the word wrap:

This feature was similarly asked on: 

1. http://smartgit.3668570.n2.nabble.com/Wrap-Long-Lines-in-Diff-View-td7574045.html
2. https://smartgit.userecho.com/communities/1/topics/87-changes-view-optionally-wrap-lines

> It's hard to see what changed within a line if it's really long, scrolling is awkward and it's easy to miss a change when doing a review.

The SmartGit team answer was:

> There is no option available to wrap long lines in SmartGit's file compare. You may configure your own file compare which offers this option in the preferences. 

Regarding this, there is this question on StackOverflow about it: https://stackoverflow.com/questions/51756401/use-git-diff-as-diff-algorithm-in-smartgit

This is related to: https://smartgit.userecho.com/topics/804

But is a more general approach. I would like to choose any state between "only first parents are shown" (proposed in the RFE) and "all parents are shown" (current state). I want to be able to hide any parent of any commit (mostly makes sense for merge commits and second parents). In this way I can exclude any irrelevant branches/commits/lines from the log and concentrate only on those I'm currently investigating.

After clicking on a link in the Log window Details pane (e.g. the "parent commit" link) or after right-click Reveal Commit from the Branches pane, it would be nice if I could go "Back" to the commit that was highlighted before the jump. A button in the Commits toolbar, e.g. next to the Filter box, would be a great place for it. The standard keyboard shortcut (e.g. Alt+Left) would also be nice. "Forward" support would also make sense, but the feature would still be useful without it.

.. this would help finishing feature branches for gitflow and similar workflows.

Currently (version 17.1.6) if you change a file inside a submodule, the change is listed conveniently in the Files panel (I really love that feature!). 

However, nowhere in the UI it is communicated whether this file is inside a submodule or not. This can make it difficult for people not yet familiar with the project to understand what part of the project they've actually changed. For example, if you try to commit that file, you might get an error dialog about detached HEAD, but it does not specify that this is actually the submodule repo, not the main repo leading to much confusion.

The filter submodules button (Ctrl+7) does indeed hide this file, so by that you can deduce that it is inside a submodule.

I suggest adding a some tag or symbol in front of those files that reside inside submodules to make it clear where they belong to.

I have some local commits for a file and wanted to create a patch file which contains the differences to the remote version of the file. When I select the two revisions in the Log view window I can open a File Compare which lists the changes. It would be nice if there was an option in the File Compare view to then create a patch file with the changes.

When a commit message has more than one line it would be great if the full message would be displayed in the tooltip of that line in the journal.