ReNamer:Renaming to another folder
You can optionally move the items to another folder.
Just specify a new folder path in the New Name field in Insert rule.
- You can use either absolute path (e.g. "D:\Utilities\") or relative path (e.g. "..\").
For example, let us imagine that we have just added few files to ReNamer.
| Name |
|---|
| Text.txt |
| Song.mp3 |
| Document.doc |
We want to move those files to a new folder "C:\New Folder". What we need to do is to add a single Insert rule, inserting "C:\New Folder\" as prefix. This will result in the following:
| Name | New Name |
|---|---|
| Text.txt | C:\New Folder\Text.txt |
| Song.mp3 | C:\New Folder\Song.mp3 |
| Document.doc | C:\New Folder\Document.doc |
Now you can proceed with the renaming as usual.
You can also make the New Path column visible in the Files table, where you will see the final destination for each item. This can be extremely useful when working with relative paths, because relative paths, including those which contain ".." (parent folder) and "." (current folder), will be resolved into the full path.
Tips:
- Instead of hard-coding the path, you can use a formula in the path, to distribute the renamed files into multiple folders.
- If the target folders do not exist already, ReNamer will create them and then move the file into these newly created folders.
Instead of moving the file, can we copy them into a new folder?
Well, as we saw above, ReNamer actually changes the path of the file, which effectively moves the file. But copying a file requires creating a new instance of the file, which ReNamer cannot do. The best we can do is to copy the files in the same folder first (with an external application, such as Windows Explorer) and then rename them as shown above to move them.
This method can save you a lot of work, as you can specify a formula in the path (rather than hard-coding the path). This means you can