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 123992 - when creating a new folder in list view the option to rename immediately after creating it isn't available
when creating a new folder in list view the option to rename immediately afte...
Status: RESOLVED DUPLICATE of bug 94250
Product: nautilus
Classification: Core
Component: File and Folder Operations
2.4.x
Other other
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 123929 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-10-07 01:16 UTC by quixada
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.3/2.4


Description quixada 2003-10-07 01:16:38 UTC 
This bug is in Nautilus 2.4.0

When I create a new folder in list view using the menu in Nautilus: File
--> New Folder or using shift-ctrl-n, I do not get the option to rename the
folder right away. Instead, I have to rename the file in a separate step.
However, on the desktop or in icon view, it *does* work i.e. if I create a
new folder I can either type the name of the folder I want or press enter
(or click beside) and it will be named ``New Folder''.

Steps to re-create:
1. Open a new window
2. Switch to list view
3. Create a new folder
4. Rename the folder manually

Proper behavior (like on the Desktop):
1. Open new window
2. Switch to list view
3. Create a new folder
4. Be able to type-in the name of the new folder or just press enter to
have it named ''New Folder'' (same behavior as icon view).

Note: I reported this bug for version 2.2.4 (bug #123929) too.
Comment 1 mwehner 2003-10-11 02:44:04 UTC 
*** Bug 123929 has been marked as a duplicate of this bug. ***
Comment 2 mwehner 2003-10-16 15:06:32 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 94250 ***