Sometimes I want to open multiple repos (6-15) in windows explorer from the Repository view in the LogGraph view. Therefore I have to right click each one and say "Open in Explorer". It would be nice if that option would also be shown if you select multiple repos which would then of course open also multiple explorer instances.

Now, pressing Ctrl+C on repository group in Repositories windows has no effect.

Ability to visualy separate branch(es) in the branches tree. Like favorite or star whatever you want to call it. I want to have a short list where its easy to pick from

Hello

I miss a smart feature:

If you work in several projects, it is very tedious and time-consuming SmartGit to check in whether there have been changes in one of the repositories: you have to select and check each one manually.

It would be great if you could activate a SmartGit background check for Repositoeries that:

1. Adjustable e.g. every 60 minutes
2. Each repository checks whether:
   1. Local changes have been made
   2. There have been changes on the git server
   3. The authentication is still OK

1. (Annoying Editor: this is 4.)
   The recorded information is then displayed for each repo

Thanks a lot, kind regards,
Thomas

When I work on a feature branch, I always amend a single commit:

- I don't want to have to deal with commit messages each time I push a small change to my feature branch

- In the end, when I merge my feature branch, all commits are squashed to a single one, so the commit messages are lost

Each time I commit, I need to check the "amend" checkbox in the commit dialog.

I would like to have an option "Always amend commit on a feature branch", so this checkbox would always be checked.

It could be turned off by default.

Thank you, I love your product :)

Currently, all the views are tighty packed with text and hard to read. A bit more line spacing might go a long way of making information more readable. Using a slightly smaller font with that still allows for the same amount of information to be on screen.

I just discovered the ability to expand & collapse merge nodes in the "Only current branch" log view, and I love it, thanks!

And now I really wish I had that feature in the "all branches" mode also. Unlike the "only current branch" mode, it would default to expanded as today, but allow merges to be collapsed.

Dear SyntEvo,

I would like to express my appreciation for SmartSynchronize. While I understand it is foremost a diff tool, for me, it has become an indispensable file manager in my daily workflow on Linux. SmartSynchronize (as a file manager) strikes a perfect balance between simplicity and functionality.

However, I've encountered an issue that I believe could enhance the user experience. The navigation bar struggles to handle long paths effectively. Navigating through extensive directory structures is a routine part a programmer's job. Unfortunately, the current design falls short when dealing with paths like:

/build/workdirs/projname-branch-server-native-gcc11-linux-libgen-customer/src/module/submodule/dir/subdir

When I delve into deeper directories like module/submodule, the navigation bar truncates crucial parts of the path, forcing me to rely on memory to recall my location (twice - there are two panels).

To address this issue, I propose two potential solutions:

• to display the end portion of the path instead of its beginning, offering a clearer indication of the current directory; and
• to mplementing a tooltip feature that provides the complete path when hovering over truncated segments.

Combining both approaches would undoubtedly provide the optimal solution. Nothing beats a good tooltip, though. ;-)

Once again, thank you for your attention to this matter and for the continued development of SmartSynchronize.

Best regards,
Peter

As an alternative to Specific word boundary settings for hyphen & underscore detection (https://smartgit.userecho.com/communities/1/topics/1685-specific-word-boundary-settings-for-hyphen-underscore-detection, if link doesn't review it means it's still being reviewed by moderation), we could add commands with customisable shortcuts to navigate per subword (separated by hyphen/underscore *even* if current word boundary setting skips them).

Default shortcuts could be Ctrl+Alt+Left/Right (may conflict with some desktops), or empty. Personally I'd use Alt+Left/Right but I'll have to remove existing competing shortcuts (in fact it's just Alt+Left that is mapped to reveal previous commit, others like File Compare: Take Left/Right Block are more contextual so it's ok).

In this case the best combination would be to set all boundary settings to skip hyphens and underscores (either via options as suggested in the thread linked above, or hardcoded to always skip if everyone agrees), and so users can navigate full words with Ctrl+Left/Right and then more precisely over subwords with the new commands/shortcuts.

And of course both suggestions are compatible: we could define behavior for Ctrl+Left/Right to the most useful ones for us, and use sub-word navigation when we need to.

This is a new request spawned from https://smartgit.userecho.com/communities/1/topics/1562-word-navigation-ctrlleftright-do-not-stop-before-and-after-every-space

Basically, word boundary has two modes based on:
Preferences > Low-level properties > styledtext.useOwnWordBoundaryDetection value

It affects both Ctrl+left/right navigation and double-click selection.

If true, SmartGit own detection is used

- stops at hyphens (not great for kebab-variables, but understandable for plain English compounded-words)

- skips underscores (good for snake_case variables)

- stops at left and right of spaces (annoying)

If false, system detection is used. For instance on Ubuntu 22.04 + Unity desktop I have:

- stops at hyphens (same as above)

- stops at underscores (may be annoying for snake_case variables when you don't want to edit them)

- stops only one at spaces (good)

In most cases I just want to navigate as fast as possible and skip underscores, stop only one at space and possibly stop at hyphens (e.g. in Python I don't use kebab-case so hyphens are just for compounded-words so it's ok to stop at them)

More granular options over how boundaries are defined would make it easier to get the navigation we want. They would only apply when styledtext.useOwnWordBoundaryDetection is true since otherwise system would take over.

Examples:

- styledtext.whenUsingOwnWordBoundaryDetectionStopOnceAtSpace (honestly I think this one should be true by default, and actually wouldn't even need an option to be false, not sure who would really use the "stop at left and right of space" case since in most cases you can just go to either side and press left/right)

- styledtext.whenUsingOwnWordBoundaryDetectionStopAtHyphen (currently true)

- styledtext.whenUsingOwnWordBoundaryDetectionStopAtUnderscore (currently false)

To be fair, if right now SmartGit's own boundary detection was "fixed" to stop only once per space it would be perfect for my setting, and there would be no need for options.

The options may be useful in different settings though.

You may survey other devs to decide whether a hardcoded change or full options (more time to implemented, but more flexible) is better.