[TC 11.00b3] - shift left/right arrow changed when using inplace rename?

[hi5]

To add: if this is intentional behaviour, I would argue that it should be activated by the user, not the default.
So keep in place rename working as it has been up to now, but if you want the new feature, you need to add CtrlArrow=1 to the [configuration]

[ymmv]

I agree. IMO it would be more logical to add a config setting to unlock new functionality than to make the tens or hundreds of thousands of longtime TC users throw their hands in the air at this sudden change because don't know they should add CtrlArrow=0 to a config file.

TC users are used to the idea that upgrading to a new TC version won't break or change anything. This small change is a major change simply because of how often people rename files each and every day.

[Galizza]

if this is intentional behaviour, I would argue that it should be activated by the user, not the default.
So keep in place rename working as it has been up to now

Support

[funkymonk]

The new "default" behavior (in TC11.00b1-3) is indeed very confusing.

I would prefer the original Ctrl+L/R behavior (from 10.52) in combination with
"03.04.23 Added: In place rename, command line: Stop at more non-alphanumeric characters on Ctrl+Left/Right: \/(),.;=''^+-%&!_[ ]{} (32/64)"

[hi5]

22.05.23 Added: The default of the CtrlArrow option in wincmd.ini is now 0 (disabled) (32/64)

[funkymonk]

Looks much better in TC11.00b4. Thank you!