Thank you! On Wed, Oct 10, 2012 at 10:39 AM, John Wiegley <[email protected]>wrote:
> >>>>> Craig Earls <[email protected]> writes: > > > 1. 'generate' as a precommand > > Randomly generates syntactically valid Ledger data from a seed. Used by > the > GenerateTests harness. > > > 2. 'template' as a precommand > > Shows the insertion template that a "draft" or "xact" sub-command > generates. > This is a debugging command. > > > 3. --generated > > Whether auto-generated postings (such as those from automated transactions) > should be included in the report, in cases where you normally wouldn't want > them. > > > 4. --forecast-while > > Continue forcasting while the value expression remains true. > > > 5. --forecast-years > > Forecast at most X years in the future. > > > 6. --meta > > In the register report, also show the given metadata field in the first > column. This is just a quicker alternative to using --prepend-format. > > > 7. --only > > See earlier posting. This is a postings predicate that applies after > certain > transforms have been executed, such as periodic gathering. > > > 8. --no-rounding > > Don't output <Rounding> postings. Note that this will cause the running > total > to often not add up! It's main use is for -j and -J reports. > > > 9. --raw > > In the print report, show transactions using the exact same syntax as > specified by the user in their data file. Don't do any massaging or > interpreting. Can be useful for minor cleanups, like just aligning > amounts. > > > 10. --seed > > Used by the generate command above. > > > 11. --truncate (valid arguments are "leading" "middle" and "trailing") > > Indicates how truncation should happen when the contents of columns exceed > their width. The default is smarter than any of these three, as it > considers > sub-names within the account name (that style is called "abbreviate", but > apparently you can't set it using the --truncate option). > > John > -- Craig, Corona De Tucson, AZ enderw88.wordpress.com
