Add more word delimiters for file rename

[Nino-kun]

Hello.

I'm encountering an issue when renaming files under the cursor with Shift+F6 shortcut or cm_RenameSingleFile command. When I try to move the cursor by word boundaries using Ctrl+Left or Right, Total Commander doesn't recognize "_.,@#)]" characters as word delimiters. And since underscore and dot characters are often used instead of <space> in filenames, it's REALLY inconvenient.

Some characters, such as <space>, -, !, ( or [, are considered word separators, and cursor stops at them. <minus> are more special when others, cursor stops before and after it.

If I invoke the Copy or Move dialog with F5/F6, and trying to move cursor word by word, it correctly stops at all word separator characters.

Please, consider making changes so more symbols are counted as word delimiters at file rename.

Thank you.

[ghisler(Author)]

That's odd, here is the list of stop characters I currently use:

Code: Select all

\/ (),.;='^+-%&!_[]{}

So the underscore, dot, comma, and closing braces and brackets are definitely included.
Not included are @ and #.

Maybe you are using an older version? Versions before 11.00 used the following only:

Code: Select all

\/ _.-

But even then it included the underscore.

[Nino-kun]

I have ver. 11.57 installed.

For test I install fresh downloaded 64bit 11.57 with all default settings on Windows 11 VM 25H2 (26200.8655) and create file with name

Code: Select all

1 2.3,4_5@6$7%8^9&10(11)12[13]14-15=16.txt

Shift+F6 on file -> name and extension became selected -> Ctrl+Left -> cursor jump before 15 -> after 14 -> after 12 -> after 10 -> before 2 -> and finally before 1

If I press F6 and when start pressing Ctrl+Left cursor stops before txt and when before every number.

On my main installation I have exactly same results.

[ghisler(Author)]

Sorry, I forgot that the internal Ctrl key handler is disabled by default. In this case, it's handled entirely by the Windows edit box.
You can enable the internal handler by adding
CtrlArrow=1
to the wincmd.ini section [Configuration].

F6 behaves differently because there I'm using auto-complete, and the auto-complete handler also takes over the Ctrl+Cursor handling. There is no reasonable usage of auto-complete in Shift+F6, so I can't use it there...

[AntonyD]

You can enable the internal handler by adding
CtrlArrow=1

Even with this trick 6 7 numbers not used((((
F6 behaves correctly - all numbers were used

[ghisler(Author)]

As I wrote above, @ and # are not included in the list.
Any others I should include?

[AntonyD]

for now we can compare behavior only with autocomplete from F6 - so for now only these 2 are needed.
all other possible chars will be already "person-linked" - according to person's current needs.

[Nino-kun]

CtrlArrow did the magic for me.
Thank you!

[ghisler(Author)]

OK, I will add @ and # to the next beta version.

[AntonyD]

IF @ and # WERE added - then I don't understand HOW these chars can help in this:
1 .2 ,3 _4 @5 $6 %7 ^8 &9 (10 )11 [12 ]13 -14 =15 #16 ;17 +18 ~19 !21 {22 }23 '24 `25.txt
in this test string I still can't reach 7 * and 19 and 25
looks like we have to use $ by default and ~ and ` as delimiter?
autocomplete from F6 definitely uses these chars by default.

P.S.
Correction *
Indeed - I was wrong - I can't reach 6.

[ghisler(Author)]

Here I can't reach 6, 19 and 25. But that's because $, ~ and ` aren't in the above list.

[AntonyD]

You are right & I missed. I can't reach 6 too, not 7. And yes - that's because these chars are not delimiters by default.
+ As far as I understand, the question of the topic is whether we are adjusting the encoded behavior for SHIFT+F6 to match
the built-in one for F6 — it turns out that we are also missing exactly these characters. So can we add them?