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.

It would be nice if the branch structure in the Standard Windows view could be set like in the Log Windows view where SmartGit shows local branches and remote branches in a tree view. Also branches are grouped by paths:

I think the UI would be more consistent if the layout of "Local Files" and "History" tabs would be similar in the Standard Window:

History in the center of the window and commit messages and changed files to right.

Please allow individual coloring of the entries in the branch window (accessible via CTRL+SHIFT+2). It should be possible to define both the text color and the background color separately for each branch as well as depending on the status "checked out" and "not checked out".

For this purpose, it would be an option to define classes in the settings, e.g. "warn" or "deploy", and then specify "warn" with regular status has red text color, "warn" with status "checked out" has white text color with red background. One can then assign a class to individual branches in the branch list.

This way, branches where a push results in subsequent actions (e.g. deploy to production) can be clearly highlighted ( and their potential impact...).

For those of us who contribute actively to opensource projects based on forgejo(for of gitlab) platform, i.e. codeberg, it would be nice to have some sort of integration, i.e. referencing issues, query issues, list pull requests, etc.

In the following situation, I have to repeat manual work. It could be automated:

• I have a feature branch and merged in develop at some point
• Merging in develop resulted in conflicts that I resolved
• Some time later, the feature branch is rebased on the then-latest develop
• The conflicts I've resolved when merging in develop now appear again and need to be resolved again.

Could the steps to resolve the merge conflicts be recorded and applied again on reabase?

looking for a way to auto add (by script) a group with many repos in it from the command line.
should i edit the repository-grouping.yml ?

Right now, open tabs of submodules are lost, when smartGit is closed. A option to keep them in the tabs until removed manually would be great.

open the log window of a file in one or more branches. 

See https://learn.microsoft.com/en-us/windows/win32/hidpi/setting-the-default-dpi-awareness-for-a-process

The current DpiAware/DpiAwareness level (which is probably 'unaware') leads to the GUI being bitmap scaled (and blurred) when the DPI changes e.g. when moved from a display with 125% display scale to one with 100% display scale.

Scaled to 125% display.

Scaled to 125% display then moved to a display with 100% display scale.