Bug 204691 - rename by default doesn't start with the original file name
Summary: rename by default doesn't start with the original file name
Status: RESOLVED DUPLICATE of bug 188533
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: openSUSE Linux
: NOR wishlist
Target Milestone: ---
Assignee: Peter Penz
Depends on:
Reported: 2009-08-21 20:07 UTC by rrchan
Modified: 2009-08-22 01:08 UTC (History)
1 user (show)

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


Note You need to log in before you can comment on or make changes to this bug.
Description rrchan 2009-08-21 20:07:24 UTC
Version:           1.3 (using KDE 4.3.0)
OS:                Linux
Installed from:    SuSE RPMs

when a file is renamed in dolphin or konqueror, the a rename dialog pops up, and it shows only the original file's extension, the user has to retype the entire filename even if he/she only wants to change 1 character in the filename.

the rename feature would be more usable if the rename dialog displays the original file name.  The user can then make the file name modification from there.  This behavior is already present on the plasma desktop, but not in dolphin or konqueror
Comment 1 FiNeX 2009-08-21 22:34:04 UTC
Do you mean that the name of the file is removed automatically? 
For example:
1) file is called "testfile.txt"
2) press F2 (or select rename from the menu)
3) the rename dialog displays: ".txt" (without "testfile")

Would you like to test the "rename inline" option? Does it delete the filename?
Comment 2 rrchan 2009-08-21 23:57:03 UTC
Exactly, it leaves the extension and deletes the rest of the filename.
Rename inline option appears to follow the same behavior: delete the filename, leaving only the file extension.
Comment 3 FiNeX 2009-08-22 00:57:09 UTC
Are you using skim/scim? In that case this is dup of bug #188533 .
Comment 4 rrchan 2009-08-22 01:07:58 UTC
yes, I am using SCIM, thanks for pointing that out.
Comment 5 rrchan 2009-08-22 01:08:47 UTC

*** This bug has been marked as a duplicate of bug 188533 ***