Share your ideas on how to improve SmartGit!


This is no support platform! To report bugs or request support, please contact us directly. If in doubt ask us.


First search for a similar request and add your votes or comments there.


Take the time to describe your request as precise as possible, so users will understand what you want.


Follow the stackoverflow.com writing guidelines.

Thank you for your help!

+1

Set different encoding for each file.

Данил «Danatela» Каримов 7 years ago updated 7 years ago 2

We have files in one repository, which are encoded in several different encodings. It would be great if we had possibility to switch their encoding setting for each file like in Eclipse.

Perhaps, encoding could also be detected automatically.

+1

More distinct (colored) file statuses

Peter Slížik 7 years ago updated by Thomas Singer 7 years ago 1

In the past, I got used to the CLI git command line interface. What I like about it is that all staged files are shown in green (no matter if they were added with 'git add', 'git mv' or some other way) and all modified and untracked (non-staged) files are shown in red. This is very convenient, as one can easily see what content is stored in the Git index (stage) and what changes are made in the file system only. Switching to SmartGit, I miss these colors. I need to focus my attention of the text next to file names and actually "read" it ("Staged", "Modified", etc.)


My suggestion is that Syntevo could add an option to show the files in the "Files" view more colorful. Or, even better, to have colorful backgrounds? Or, probably, to make the icons left to the file names to use better colors? Or make the icons more distinct one from another, in general.

+1
Completed

Support Mercurial 4.2+

Cinderblocks 7 years ago updated by Marc Strapetz 6 years ago 1

Really need support for current versions of mercurial. Please don't make me go back to source tree because I can't use hg anymore. :(

+1
Completed

SVN repository: resolve jira tickets does not work [SG-10816]

Vincent Roger 7 years ago updated 7 years ago 7

For Git-SVN clones, it's not possible to resolve JIRA issues when pushing commits.

+1

Copy full first-paragraph of commit message in "Copy Selection in Column"

Sync 7 years ago updated by Thomas Singer 7 years ago 5

I wanted to copy out the first paragraph of each commit's message (for n commits) through the "Copy Selection in Column" feature, for a weekly summary report of what has changed. However, if the column is not wide enough, SmartGit truncates it with an ellipsis. The bad part is the copied text is the truncated version, not the full version.


It would be nice if the copied text is the full first paragraph.

+1

Journal: set default auxiliary branch for new branches

Martin Kirk 7 years ago updated by Pierre Goiffon 7 years ago 2

I recently found began using the Journal window - however, when working in a branch, it's not useful that it displays "Develop" as the auxiliary branch, so i set it to "None" which showed the branch im working on.

However !... when i create new branches, the default view gets reset to Develop and i again need to clear it to None.

Would it be possible to set the default view of this window ??

as a setting somewhere ..

+1

Add file system case-sensitivity sensitivy

gchurchill 7 years ago updated by griscom 3 years ago 3

Detect when the filesystem (Windows) can't sense the filename case differences of a given repo (Linux Kernel) to avoid falsely indicating Example.h is a changed version of exAMple.h. This would avoid indicating that you have uncommitted changes the instant you clone a given repo with only case differences in certain different file names.

+1
Completed

Git Interactive Rebase: use configured comment symbol (core.commentchar)

Gxost 7 years ago updated by Thomas Singer 6 years ago 1

For interactive rebase git generates files containing comments starting from "#". But this character isn't hardcoded, it can be changed in git configuration f any other character: ";", "$" and so on. If core.commentchar is not "#", SmartGit can't parse generated file and interactive rebase fails.

+1
Completed

Log: improved display

stefano niceta 7 years ago updated by Marc Strapetz 7 years ago 1

Image 87


The readability would be better if the straight lines are preferred to the curves.

ex.:

Image 88

+1
Declined

| operator not working in Tools Arguments​

friuns 7 years ago updated by Thomas Singer 7 years ago 1

hello | operator fails to execute here

diff ${commit}^..${commit} -- "${fileOpen}" | ${git} apply --3way

when i execute same command from mingw64 it works correctly

https://www.tutorialspoint.com/unix/unix-io-redirections.htm

|

Takes output from one program, or process, and sends it to another