mirror of
https://github.com/simonmichael/hledger.git
synced 2024-09-18 17:57:11 +03:00
;doc: fix broken manual links in manuals source
[ci skip]
This commit is contained in:
parent
84cf3fe722
commit
ef04907484
@ -877,7 +877,7 @@ P 2009/1/1 € $1.35
|
||||
P 2010/1/1 € $1.40
|
||||
```
|
||||
|
||||
The [`-V/--value`](hledger.html#market-value) flag can be used to convert reported amounts
|
||||
The [`-V/--value`](hledger.html#v-market-value) flag can be used to convert reported amounts
|
||||
to another commodity using these prices.
|
||||
|
||||
### Declaring accounts
|
||||
@ -894,7 +894,8 @@ Though not required, they can provide several benefits:
|
||||
- They help with account name completion
|
||||
in the add command, hledger-iadd, hledger-web, ledger-mode etc.
|
||||
|
||||
The simplest form is just the word `account` followed by a hledger-style [account name](journal.html#account-names), eg:
|
||||
The simplest form is just the word `account` followed by a hledger-style
|
||||
[account name](journal.html#account-names), eg:
|
||||
```journal
|
||||
account assets:bank:checking
|
||||
```
|
||||
@ -1183,7 +1184,8 @@ read this whole section - or at least these tips:
|
||||
### Periodic rule syntax
|
||||
|
||||
A periodic transaction rule looks like a normal journal entry,
|
||||
with the date replaced by a tilde (`~`) followed by a [period expression](hledger.html#period-expressions)
|
||||
with the date replaced by a tilde (`~`) followed by a
|
||||
[period expression](hledger.html#period-expressions)
|
||||
(mnemonic: `~` looks like a recurring sine wave.):
|
||||
```journal
|
||||
~ monthly
|
||||
@ -1224,7 +1226,8 @@ So,
|
||||
With the `--forecast` flag, each periodic transaction rule generates
|
||||
future transactions recurring at the specified interval.
|
||||
These are not saved in the journal, but appear in all reports.
|
||||
They will look like normal transactions, but with an extra [tag](journal.html#tags):
|
||||
They will look like normal transactions, but with an extra
|
||||
[tag](journal.html#tags):
|
||||
|
||||
- `generated-transaction:~ PERIODICEXPR` - shows that this was generated by a periodic transaction rule, and the period
|
||||
|
||||
@ -1287,7 +1290,8 @@ Currently just one kind of change is possible - adding extra postings, which we
|
||||
These rules become active when you use the `--auto` flag.
|
||||
|
||||
A transaction modifier rule looks much like a normal transaction
|
||||
except the first line is an equals sign followed by a [query](hledger.html#queries) that matches certain postings
|
||||
except the first line is an equals sign followed by a
|
||||
[query](hledger.html#queries) that matches certain postings
|
||||
(mnemonic: `=` suggests matching).
|
||||
And each "posting" is actually a posting-generating rule:
|
||||
|
||||
|
@ -293,7 +293,7 @@ balance report, is not yet supported in multicolumn reports.
|
||||
With `--budget`, extra columns are displayed showing budget goals for each account and period, if any.
|
||||
Budget goals are defined by [periodic transactions](journal.html#periodic-transactions).
|
||||
This is very useful for comparing planned and actual income, expenses, time usage, etc.
|
||||
--budget is most often combined with a [report interval](manual.html#report-intervals).
|
||||
--budget is most often combined with a [report interval](hledger.html#report-intervals).
|
||||
|
||||
For example, you can take average monthly expenses in the common expense categories to construct a minimal monthly budget:
|
||||
```journal
|
||||
|
Loading…
Reference in New Issue
Block a user