slaesvuo/hledger
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

;doc: fixups suggested by afm

Browse Source
This commit is contained in:
Simon Michael 2022-04-14 14:17:53 -10:00
parent 133c54434a
commit 5ee1e1d62f
3 changed files with 13 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
hledger/Hledger/Cli/Commands/Add.md
View File

@ -6,10 +6,10 @@ _FLAGS
Many hledger users edit their journals directly with a text editor, or generate them from CSV.
For more interactive data entry, there is the `add` command,
which prompts interactively on the console for new transactions, and appends
them to the journal file (if there are multiple `-f FILE` options, the first file is used.)
which prompts interactively on the console for new transactions,
and appends them to the main journal file (which should be in journal format).
Existing transactions are not changed.
This is the only hledger command that writes to the journal file.
This is one of the few hledger commands that writes to the journal file (see also `import`).
To use it, just run `hledger add` and follow the prompts.
You can add as many transactions as you like; when you are finished,

6
hledger/Hledger/Cli/Commands/Import.md
View File

@ -1,11 +1,15 @@
import\
Read new transactions added to each FILE since last run, and add them to
the main journal file. Or with --dry-run, just print the transactions
the journal. Or with --dry-run, just print the transactions
that would be added. Or with --catchup, just mark all of the FILEs'
transactions as imported, without actually importing any.
_FLAGS
This command may append new transactions to the main journal file (which should be in journal format).
Existing transactions are not changed.
This is one of the few hledger commands that writes to the journal file (see also `add`).
Unlike other hledger commands, with `import` the journal file is an output file,
and will be modified, though only by appending (existing data will not be changed).
The input files are specified as arguments, so to import one or more

10
hledger/hledger.m4.md
View File

@ -667,11 +667,11 @@ These too will cause report start/end dates to be expanded, if needed,
to span a whole number of intervals.
Examples:
| | |
|-----------------------------------|-------------------------------------------------------------|
| `-p "bimonthly from 2008"` | periods will have boundaries on 2008/01/01, 2008/03/01, ... |
| `-p "every 2 weeks"` | starts on closest preceding Monday |
| `-p "every 5 month from 2009/03"` | periods will have boundaries on 2009/03/01, 2009/08/01, ... |
| | |
|------------------------------------|-------------------------------------------------------------|
| `-p "bimonthly from 2008"` | periods will have boundaries on 2008/01/01, 2008/03/01, ... |
| `-p "every 2 weeks"` | starts on closest preceding Monday |
| `-p "every 5 months from 2009/03"` | periods will have boundaries on 2009/03/01, 2009/08/01, ... |
### Intervals with custom start date