Your comments
This could be dangerous if you are in the wrong branch and have already started with a new feature (e.g. created a new file) and then want to switch to the right branch for commit - bang, your changes are lost. I don't want the user to blame us for having added such a dangerous option.
For Git repositories this will be implemented in 17.1 preview 5.
This is expected because | only works in shells. You would have to run a shell script that performs the desired command.
Please contact smartgit@syntevo.com if you need to get support. This is rather for feature requests.
The current work-around, of course, is to apply a full stash (maybe with conflicts) and discard all unnecessary changes. Maybe this also gets obsolete when getting used to stashing selected files.
If you are on Windows, multiple portable installations would help you.
Why do you think you would see more in horizontal alignment? I don't see any reason for this claim.
Let's take a look at the Changes -> Settings dialog. It only effects the belonging view unless you select the "Remember as default" option. This you would lose if you would only have one preferences option.
The Repository | Settings and Remote | Properties dialogs work on the selected repository or remote. Making them available in the Preferences dialog would be very bad UX because the preferences never work on any selection.
I'd rather tend to do the opposite and spread the options to the places where they actually act. One example are the new options in the Branches and Journal views in the 3-lines-popups. I'm sure, this is easier to discover. Options that act on multiple places, I'd try to keep in the preferences.
Currently, we use VM properties for options that should not be exposed to the GUI and because it is easy to implement (calling something like System.getProperty(key, defaultValue)). If this would become harder to implement, we would implement fewer options and hence need to reject some configuration requests.
Customer support service by UserEcho
Why do lots of GIT branching papers use a horizontal layout? I think because it's more intuitive and compact (because text is naturally drawn horizontally).
Because in a text document a horizontal graphic needs less space and because the commit message information is not shown.