| |
|---|
| | practice, however.) |
|---|
| | |
|---|
| | These OSs show upper- and lower- case in file names as you request, |
|---|
| | but they do not *distinguish* names on the basis of case. For |
|---|
| | instance, the files '``Foo``', `''foo``', and '``FOO``', are all the |
|---|
| | instance, the files '``Foo``', '``foo``', and '``FOO``', are all the |
|---|
| | same name in these operating systems, and only one of these can exist |
|---|
| | in a given directory. This can cause **tren** to do the unexpected |
|---|
| | when your renaming command is doing nothing more than changing case. |
|---|
| | Suppose you start with a file called '``Aa.txt``' and run this |
|---|
| |
|---|
| | **tren** will immediately complain and tell you that the file |
|---|
| | '``aa.txt``' already exists and it is skipping the renaming. Why? |
|---|
| | Because from the point-of-view of OS X or Windows, '``aa.txt``' (your |
|---|
| | new file name) is the same as '``Aa.txt``' (your original file name). |
|---|
| | you attempt to force the renaming:: |
|---|
| | You can attempt to force the renaming:: |
|---|
| | |
|---|
| | tren.py -frA=a Aa.txt |
|---|
| | |
|---|
| | Guess what happens? Since **tren** thinks the new file name already |
|---|
| |
|---|
| | ----------------------------- |
|---|
| | |
|---|
| | :: |
|---|
| | |
|---|
| | $Id: tren.rst,v 1.143 2010/03/23 21:08:40 tundra Exp $ |
|---|
| | $Id: tren.rst,v 1.144 2010/03/23 21:12:08 tundra Exp $ |
|---|
| | |
|---|
| | You can find the latest version of this program at: |
|---|
| | |
|---|
| | http://www.tundraware.com/Software/tren |
|---|
| |
|---|
| | |
tundra
authored
on 23 Mar 2010