Please add an icon/modifier (similar to the green and red arrows) to a repo in the repository view if you are in a local branch that you have not pushed.  We often end up in a situation where a developer has created a release or feature branch but did not push it.  There is not obvious/quick way to spot local branches like you can spot uncommitted changes (red icons) or unpushed commits (red arrow).

Regularly, I fetch, pull, and push multiple repos via the multi-select repo feature.  SG sequentially executes the command for each repo.  Would it reduce the elapsed time for all by having SG execute them concurrently (or in batches, such as 5 repos at a time)?

Our use case for this feature is to retrieve and/or look at old

code that has been removed at some point in the past. Often we don't

know when it was removed and sometimes we don't even remember the name

of the file that we are looking for.The file could have been

removed by another user of the repository and they may not have put the

file name in the commit message. By getting a list of the files deleted

we can see the history of deletion and seeing the file names may also

jog our memory about what the name of the file is. Even with the name,

there isn't a way in Smartgit that I know of to find when the file was

deleted and by which user.For example lets say I delete a

class file from the repository that is no longer referenced or used by

our project. Another user, at a later time is looking for the file but

can't find it anywhere in the project and they would like to at the code

or use the code in something they are working on. They may a vague

recollection that it used to exist 6 months ago but at some point in

time between 6 months ago and now it was deleted. They would then have

to look at the log entry of every commit between now and 6 months ago to

find the deleted file. This could take a long time if there are lots of

commits. A list of deleted files would cut down their search time

dramatically.

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.