| |
|---|
| | These tokens are derived from the underlying operating system and |
|---|
| | runtime environment. Notice that, because command interpreters |
|---|
| | (shells) on various systems work differently, the first two of these |
|---|
| | have to be quoted in different ways. |
|---|
| | |
|---|
| | - ``/NAMESOFAR/ Current state of new name`` |
|---|
| | |
|---|
| | ``tren`` allows multiple renaming requests to be |
|---|
| | specified on the command line . Each of these operates |
|---|
| | serially on the renaming target name: The leftmost |
|---|
| | request operates on the original name. The resulting |
|---|
| | name is handed to the next request to the right |
|---|
| | and so on. |
|---|
| | |
|---|
| | ``/NAMESOFAR/`` allows the current state of a new name |
|---|
| | to be included explicitly in a renaming request. i.e., |
|---|
| | You can insert the name a renaming request starts out |
|---|
| | with into its own renaming specification:: |
|---|
| | |
|---|
| | tren.py -rX=y -r=/NAMESOFAR/.text Xray.txt |
|---|
| | |
|---|
| | The first renaming request transforms the name from |
|---|
| | ``Xray.txt`` to ``yray.txt``. This is thus the "name |
|---|
| | so far" with which the second request begins. So, the |
|---|
| | second renaming request transforms the name |
|---|
| | ``yray.txt`` into ``yray.txt.text``. |
|---|
| | |
|---|
| | - ``/$ENV/ Environment variable`` |
|---|
| | |
|---|
| | This token is replaced with the value of the |
|---|
| |
|---|
| | ----------------------------- |
|---|
| | |
|---|
| | :: |
|---|
| | |
|---|
| | $Id: tren.rst,v 1.190 2010/09/07 19:39:08 tundra Exp $ |
|---|
| | $Id: tren.rst,v 1.191 2010/09/07 20:17:23 tundra Exp $ |
|---|
| | |
|---|
| | You can find the latest version of this program at: |
|---|
| | |
|---|
| | http://www.tundraware.com/Software/tren |
|---|
| |
|---|
| | |
tundra
authored
on 7 Sep 2010