How TC treats the punctuation and what is its definition for "word" - it is a big mystery for me. When editing in-place long filename consisting of many words with points, comas and spaces, it would be convenient to use keys Ctrl+Left / Ctrl+Right for navigating by words left/right. But for me the big trouble is, that a "word" for TC is a chain of symbols between two spaces, no worry that you may have ten points and hyphens inside this "word". Is it possible to change this behavior? If it is not possible via standard TC's settings, may it be some add-on, script etc. to resolve this task?
Thanks to all!
rename a file in-place - how to change the behavior??
Moderators: Hacker, petermad, Stefan2, white
- StickyNomad
- Power Member
- Posts: 1933
- Joined: 2004-01-10, 00:15 UTC
- Location: Germany
Something like this was already requested, e.g. here.
Unfortunately this hasn't been improved yet. I can only repeat myself from the mentioned thread that I miss this very often.
Usual seperator charachters like dots, underscores and also backslashes (when in branch view) should be included when 'CTRL-jumping' through the file-/dirname when inplace-renaming definetly.
In all filenames of my web projects I generally avoid whitespaces and use underscores '_' instead. Being able to 'CTRL-jump' to the next '_' would save me a noticeable amount of working time.
So: Christian, could please you consider to implement this?
Unfortunately this hasn't been improved yet. I can only repeat myself from the mentioned thread that I miss this very often.
Usual seperator charachters like dots, underscores and also backslashes (when in branch view) should be included when 'CTRL-jumping' through the file-/dirname when inplace-renaming definetly.
In all filenames of my web projects I generally avoid whitespaces and use underscores '_' instead. Being able to 'CTRL-jump' to the next '_' would save me a noticeable amount of working time.
So: Christian, could please you consider to implement this?
...and would cost me additional time, OTOH.StickyNomad wrote:would save me a noticeable amount of working time.
Stopping at backslashes could be useful, however.
Imagine a file name like
orc:\path\host_10-0-0-1_255-255-0-0
Ctrl-left from the end selecting the whole file name would save time.c:\path\http-www-host-com-pub-tools-packer-somename-versions-1-1-2
But if Ctrl-cursor stops every 2 characters, it has no advantage at all over cursor key without Ctrl.
Instead I'd have to press it 9 times - it would be even faster to use the cursor without "accelerator" then.

Stopping at every "-" and "_" and whatever characters is pure torture in my eyes, already driving me mad in other places...
Extreme example here.
[Edit]
A nice suggestion to satisfy all is made now in the thread mentioned first.
Who the hell is General Failure, and why is he reading my disk?
-- TC starter menu: Fast yet descriptive command access!
-- TC starter menu: Fast yet descriptive command access!
You should use Ctrl+Shift+Home (or Ctrl+Shift+End if you are at the beginning of the name) in order to select the whole name as you wish. But Ctrl+Arrow is a conventional key to navigate by words.StatusQuo wrote:c:\path\http-www-host-com-pub-tools-packer-somename-versions-1-1-2
Ctrl-left from the end selecting the whole file name would save time.
But if Ctrl-cursor stops every 2 characters, it has no advantage at all over cursor key without Ctrl.
Instead I'd have to press it 9 times....
Besides I've written about settings or an add-on, I mean stopwords should be assignable by the user.
2leopoldus
IMO "10-0-0-1" is a word; "0" is not (if not surrounded by whitespace).
Different people have different needs in this case, so a configurable solution would be best -
then everybody could define his/her "words" (as suggested in the other thread).
Thanks, but no, this would select the path, too.You should use Ctrl+Shift+Home
Yes, it only depends on how you define a "word".But Ctrl+Arrow is a conventional key to navigate by words.
IMO "10-0-0-1" is a word; "0" is not (if not surrounded by whitespace).
Different people have different needs in this case, so a configurable solution would be best -
then everybody could define his/her "words" (as suggested in the other thread).
Who the hell is General Failure, and why is he reading my disk?
-- TC starter menu: Fast yet descriptive command access!
-- TC starter menu: Fast yet descriptive command access!