Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

10.5: Leopard file duplication and naming behaviors Desktop
Leopard changes the way files are named when duplicated via Optiond-drag (which appends numerical increments) and Command-D (which appends copy first, then numerical increments). To elaborate:

Duplicating a file using Command-D or the menu File » Duplicate will append copy to the filename; if it already ends with copy, then the next available number greater than 1 is used. Here are some examples of Command-D behaviors:
  • myfile.txt creates myfile copy.txt
  • myfile copy.txt creates myfile copy 2.txt. Repeating the command again on myfile.txt creates myfile copy 3.txt, etc.
  • 1.txt creates 1 copy.txt
Option-dragging a file in the same folder will append the next available number, greater than 1, to the file name (even on numerical filenames). Some examples of option-dragging behaviors:
  • myfile.txt creates myfile 2.txt; option-dragging it again creates myfile 3.txt. If you then option-drag myfile copy 2.txt, OS X creates myfile copy 4.txt (because copy 2 and 3 exist)
  • list 58.txt creates list 59.txt
  • 6.txt results in 6 2.txt
[robg adds: I realized the behavior had changed, but I hadn't bothered to figure out exactly how.]
  • Currently 3.20 / 5
  You rated: 3 / 5 (5 votes cast)

10.5: Leopard file duplication and naming behaviors | 2 comments | Create New Account
Click here to return to the '10.5: Leopard file duplication and naming behaviors' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Authored by: boredzo on Nov 08, '07 08:19:42PM

I prefer the Tiger behavior. :\

For those without a Tiger machine, that behavior was:

  1. untitled folder
  2. untitled folder copy
  3. untitled folder copy 1
  4. untitled folder copy 2

It was the same for both ⌘D and option-drag.

[ Reply to This | # ]
10.5: Leopard file duplication and naming behaviors
Authored by: mbpriddy on Feb 11, '08 09:36:18AM

I'd like to know if there's now a way to make either mechanism honor zero-padded version numbers. My workflow currently requires a two-digit version number in the file name. Currently, if I duplicate using option-drag, 05 gets changed to 6 (which is not bad), but I'd like it to get changed to 06 instead.

Any ideas?

[ Reply to This | # ]