Bug 200098 - renaming files and folders leads to weird behavior
Summary: renaming files and folders leads to weird behavior
Status: RESOLVED DUPLICATE of bug 195385
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-13 23:35 UTC by Petr Mrázek
Modified: 2009-07-13 23:45 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed 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 Petr Mrázek 2009-07-13 23:35:41 UTC 
Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

Here's how to reproduce it:
Go into a folder with some files.
Rename one of the files (hit F2).
Copy the renamed file to the same directory by drag&drop.
Instead of asking for a new filename, the copy will have the OLD name - the one before I renamed the original file.

Wrong workaround:
I have to close and reopen the folder I'm working with when I rename things.

How it should work:
Renamed files do ask for a new filename when copied over themselves and do keep their new name when moved or copied.

Note:
I haven't tried other ways of copying and renaming files, so that should be tested for correctness too.
Comment 1 FiNeX 2009-07-13 23:45:51 UTC 

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