| |
|---|
| | |
|---|
| | -v Prints the program version number and keeps running. |
|---|
| | |
|---|
| | |
|---|
| | Controlling Program Output |
|---|
| | ========================== |
|---|
| | |
|---|
| | As **tren** runs, it produces a variety of diagnostic and |
|---|
| | status information. There are a number of options you can |
|---|
| | use to control how this works: |
|---|
| | |
|---|
| | -q Set's "quiet" mode and suppresses everthing except |
|---|
| | error messages. |
|---|
| | |
|---|
| | -w # Tells **tren** to wrap lines after '``#``' characters |
|---|
| | have been printed. If you're capturing output to |
|---|
| | a log, set this to a very high number like 999 to |
|---|
| | inhibit line wrapping. |
|---|
| | |
|---|
| | Error and debug messages are sent to '``stderr``'. Normal |
|---|
| | informational messages are sent to '``stdout``'. If you |
|---|
| | want to capture them both in a log, try something like |
|---|
| | this (depending on your OS and/or shell):: |
|---|
| | |
|---|
| | tren.py ..... 2>&1 >tren.log |
|---|
| | |
|---|
| | |
|---|
| | Renaming Building Blocks |
|---|
| | ======================== |
|---|
| | |
|---|
| | **tren** supports a variety of renaming mechanisms. The one thing |
|---|
| |
|---|
| | ----------------------------- |
|---|
| | |
|---|
| | :: |
|---|
| | |
|---|
| | $Id: tren.rst,v 1.146 2010/03/23 22:31:33 tundra Exp $ |
|---|
| | $Id: tren.rst,v 1.147 2010/03/23 22:37:59 tundra Exp $ |
|---|
| | |
|---|
| | You can find the latest version of this program at: |
|---|
| | |
|---|
| | http://www.tundraware.com/Software/tren |
|---|
| |
|---|
| | |
tundra
authored
on 23 Mar 2010