GNOME Bugzilla – Bug 46455
`Duplicate' gives wrong names for files with more than one extension or '.' in name
Last modified: 2005-07-10 19:58:27 UTC
E.g. if I select a file called `foo.tar.gz' and duplicate it, the new file is called `foo.tar (copy).gz' which isn't very useful ------- Additional Comments From sullivan@eazel.com 2001-02-08 15:27:49 ---- I guess if we assume that all periods in the file name are extension separators, then the (copy n) should go before the first period rather than before the last period. Is that a safe assumption? (I guess the real question is, will anything bad happen if we change to use this assumption?) Seems safe to me. Doesn't seem necessary for 1.0 though, so I'm marking this 1.0.1. Complain to Don if you disagree. ------- Additional Comments From jsh@pixelslut.com 2001-02-08 15:35:58 ---- I don't think anything bad will happen from assuming that all dots are extension separators, but it still seems sub-optimal. E.g. a file `some.thing.tar.gz' Assuming that the extensions needs to be retained, then the only other method would be to do something like `copy of foo.tar.gz', (but then the new file wouldn't sort next to the old one..) ------- Additional Comments From pavel@eazel.com 2001-03-16 11:05:12 ---- One alternative would be to compile a list of common extensions like .tar.gz and special case them. The reason why I think this could work fine is because double extensions like .tar.gz are considered an extension rather than .tar being part of the name because they are a well-known convention. ------- Additional Comments From snickell@stanford.edu 2001-07-23 00:39:48 ---- Taking bugs previously assigned to Pavel, assigning them to myself. Will parse them out at my leisure , but many are GnomeVFS bugs we should look at for 2.0 ------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-09-09 20:59 -------
Changing to "old" target milestone for all bugs laying around with no milestone set.
Still in gnome 2.
*** Bug 141212 has been marked as a duplicate of this bug. ***
still in 2.6
Still present in Nautilus 2.9.3 built from CVS HEAD
Thanks for your bug report! This is fixed with Nautilus 2.11. *** This bug has been marked as a duplicate of 306341 ***