;doc:argument files: corrections
This commit is contained in:
parent
de822ae813
commit
a1c4c8bbed
@ -521,13 +521,14 @@ See [Special characters](#special-characters).
|
|||||||
|
|
||||||
You can save a set of command line options and arguments in a file,
|
You can save a set of command line options and arguments in a file,
|
||||||
and then reuse them by writing `@FILENAME` as a command line argument.
|
and then reuse them by writing `@FILENAME` as a command line argument.
|
||||||
Eg: `hledger bal @foo.args`.
|
Eg: `hledger bal @cash.args`.
|
||||||
|
|
||||||
An argument file's format is more restrictive than the command line.
|
The syntax in an argument file is quite restrictive:
|
||||||
Each line should contain just one option or argument.
|
- Each line should contain just one option or argument.
|
||||||
Don't use spaces except inside quotes; write `=` or nothing between a flag and its argument.
|
- An option's flag and value should be joined by `=`.
|
||||||
If you use quotes, they must enclose the whole line.
|
- An option value or an argument may contain spaces.
|
||||||
For the special characters mentioned above, use one less level of quoting than you would at the command line.
|
- But don't use single or double quotes.
|
||||||
|
- And generally use one less level of quoting/escaping than at the command line.
|
||||||
|
|
||||||
## Config files
|
## Config files
|
||||||
|
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user