After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 396489 - Rename file/folder bug
Rename file/folder bug
Status: RESOLVED DUPLICATE of bug 345314
Product: gnome-commander
Classification: Other
Component: application
1.2.x
Other All
: Normal normal
: 1.2.4
Assigned To: epiotr
epiotr
Depends on:
Blocks:
 
 
Reported: 2007-01-14 16:02 UTC by Pascariu Olimpiu
Modified: 2007-05-27 18:24 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Pascariu Olimpiu 2007-01-14 16:02:24 UTC 
Please describe the problem:
After a file/folder is renamed using the F2 key, if I want to rename another file/folder from the same folder and panel, and press the F2 key, while the desired file/folder is selected, the previosly renamed file/folder appears, instead the one that I want to rename. 

Steps to reproduce:
1. Rename a file/folder using the F2 key.
2. Select another file from the same folder, in the same paneln and press the F2 key again.



Actual results:
The previously renamed file/folder name appears, instead the one that I want to rename, thus I cannot rename two files from the same folder, without closing the application after I rename the first one.

Expected results:
The name of the selected file should appear.

Does this happen every time?
Yes

Other information:
Comment 1 Paweł Widera 2007-05-27 17:18:54 UTC 
This description is inaccurate. It is true only if "another file from the same folder" is the one being marked after rename. Whenever the mark/focus is moved to different file the rename operation works correctly.

More accurate description has been given in Bug 345314, so please mark this as its duplicate (can't do it myself).
Comment 2 André Klapper 2007-05-27 18:24:21 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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