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 559213 - Bad naming when creating "Empty files"
Bad naming when creating "Empty files"
Status: RESOLVED DUPLICATE of bug 618469
Product: nautilus
Classification: Core
Component: general
2.24.x
Other All
: Normal minor
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-11-04 00:22 UTC by Chris Coulson
Modified: 2010-06-27 11:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description Chris Coulson 2008-11-04 00:22:55 UTC
Please describe the problem:
This was originally reported at https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/293343 by Magnus S:

When creating new empty files with Nautilus, the file naming convention does not make sense. I guess the easiest way to describe this is to let you see it for yourself.

Steps to reproduce:
1. On your desktop, right-click > Create Document >Empty File. You now have a file called "new file".
2. Repeat. You now have a file called "new file (copy)". That is bad naming, since this file is not a copy of "new file".
3. Repeat again. This file will be called "new file (another copy)". Also bad naming, since this file is not a copy of "new file" nor "new file (copy)", they are all separate and indepentent files.


Actual results:
The files are named "new file", "new file (copy)" etc

Expected results:
The files should be named "new file", "new file 1", "new file 2" etc. This would make Nautilus consistent with gnome-screenshot, which increments the filename each time you press Print Screen.

Does this happen every time?
Yes

Other information:
Comment 1 Allan Day 2010-06-27 11:04:49 UTC
This bug touches on a more general issue we have with the naming of new files/folders. Am marking as a duplicate - we'll track your issue with the more general report.

Thanks for the bug. :)

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