docs: reporting opts -> common opts, update query intro

This commit is contained in:
Simon Michael 2013-04-16 14:00:57 -07:00
parent 5cf6e02f8e
commit 4edbb5a589

View File

@ -865,21 +865,20 @@ Examples:
--> -->
## Reporting options ## Common options
Part of hledger's usefulness is being able to report on just a precise The following common features and options work with most subcommands.
subset of your data. The following common features and options work
with most subcommands, allowing you to specify search criteria and
adjust the output.
### Queries ### Queries
Most commands accept an optional query expression, written as arguments Part of hledger's usefulness is being able to report on just a precise subset of your data.
after the command name, to filter the data (or in some cases, to modify Most commands accept an optional query expression, written as arguments after the command name,
the output). The syntax is similar to a Google search expression: one or to filter the data by date, account name or other criteria.
The query syntax is similar to a Google search expression: one or
more space-separated search terms, optional prefixes to match specific more space-separated search terms, optional prefixes to match specific
fields, quotes to enclose whitespace etc. Each query term can be any of fields, quotes to enclose whitespace, etc.
the following: A query term can be any of the following:
- `REGEX` - match account names by this regular expression - `REGEX` - match account names by this regular expression
- `acct:REGEX` - same as above - `acct:REGEX` - same as above