Bug 181213 - Rename a file: "ctrl + arrow" combination should take into account "_" as for space
Summary: Rename a file: "ctrl + arrow" combination should take into account "_" as for...
Status: CONFIRMED
Alias: None
Product: dolphin
Classification: Applications
Component: general (other bugs)
Version First Reported In: 16.12.2
Platform: Compiled Sources Unspecified
: NOR wishlist
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-18 19:33 UTC by mathesis
Modified: 2022-03-07 01:15 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description mathesis 2009-01-18 19:33:48 UTC 
Version:            (using Devel)
Installed from:    Compiled sources

- Create a file named "a_aa a_a aa";
- Select the file;
- Press F2 or right click>Rename or File>Rename;
- Go at the beginning of the name (on the left);
- Press CTRL + right arrow several times.

You jump between blocks separated by " " but not by "_".
As "_" is often used to replace " " in a filename there shouldn't be a different behaviour.
The behaviour with " " is correct.
Comment 1 mathesis 2009-12-28 17:46:20 UTC 
To be noted this is a regression compared to KDE 3.X.

In addition, and as far as I saw, other special caracters are well taken into account except: "/", "@", "|" (pipe), "\", "#", "§", "`".
Comment 2 Peter Penz 2010-01-05 10:56:33 UTC 
Thanks for the report. Did you use inline renaming or does a separate dialog box popup in your case?
Comment 3 mathesis 2010-01-05 19:03:03 UTC 
I use inline renaming (F2).
Comment 4 Jeroen van Meeuwen (Kolab Systems) 2012-08-24 16:19:52 UTC 
Resetting assignee to default as per bug #305719
Comment 5 Justin Zobel 2021-03-09 02:19:06 UTC 
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.
Comment 6 tomashnyk 2022-03-07 01:15:53 UTC 
Yes, the issue still persists in KDE 5.25.2.