mirror of
https://github.com/simonmichael/hledger.git
synced 2024-12-27 12:24:43 +03:00
;doc: cli: fix all links to Journal > Tags / Commands > tags
This commit is contained in:
parent
4eeafdc4d3
commit
89b699e78e
@ -1,5 +1,7 @@
|
|||||||
tags\
|
tags\
|
||||||
List the tags used in the journal, or their values.
|
List the [tags](#tags) used in the journal, or their values.
|
||||||
|
|
||||||
|
<!-- same section name as Journal > Tags, if reordering these update all #tags[-1] links -->
|
||||||
|
|
||||||
_FLAGS
|
_FLAGS
|
||||||
|
|
||||||
|
@ -1098,7 +1098,7 @@ field on the right (after the first `|`). This may be worthwhile if you need to
|
|||||||
Text following `;`, after a transaction description,
|
Text following `;`, after a transaction description,
|
||||||
and/or on indented lines immediately below it, form comments for that transaction.
|
and/or on indented lines immediately below it, form comments for that transaction.
|
||||||
They are reproduced by `print` but otherwise ignored,
|
They are reproduced by `print` but otherwise ignored,
|
||||||
except they may contain [tags](#tags-1), which are not ignored.
|
except they may contain [tags](#tags), which are not ignored.
|
||||||
|
|
||||||
```journal
|
```journal
|
||||||
2012-01-01 something ; a transaction comment
|
2012-01-01 something ; a transaction comment
|
||||||
@ -1624,7 +1624,7 @@ Balance assertion failure messages show exact amounts.
|
|||||||
Text following `;`, at the end of a posting line,
|
Text following `;`, at the end of a posting line,
|
||||||
and/or on indented lines immediately below it, form comments for that posting.
|
and/or on indented lines immediately below it, form comments for that posting.
|
||||||
They are reproduced by `print` but otherwise ignored,
|
They are reproduced by `print` but otherwise ignored,
|
||||||
except they may contain [tags](#tags-1), which are not ignored.
|
except they may contain [tags](#tags), which are not ignored.
|
||||||
|
|
||||||
```journal
|
```journal
|
||||||
2012-01-01
|
2012-01-01
|
||||||
@ -1636,6 +1636,8 @@ except they may contain [tags](#tags-1), which are not ignored.
|
|||||||
|
|
||||||
## Tags
|
## Tags
|
||||||
|
|
||||||
|
<!-- same section name as Commands > tags, if reordering these update all #tags[-1] links -->
|
||||||
|
|
||||||
Tags are a way to add extra labels or labelled data to transactions, postings, or accounts,
|
Tags are a way to add extra labels or labelled data to transactions, postings, or accounts,
|
||||||
which you can then [search](#queries) or [pivot](#pivoting) on.
|
which you can then [search](#queries) or [pivot](#pivoting) on.
|
||||||
|
|
||||||
@ -1811,7 +1813,7 @@ account (assets:bank:checking)
|
|||||||
|
|
||||||
Text following **two or more spaces** and `;` at the end of an account directive line,
|
Text following **two or more spaces** and `;` at the end of an account directive line,
|
||||||
and/or following `;` on indented lines immediately below it, form comments for that account.
|
and/or following `;` on indented lines immediately below it, form comments for that account.
|
||||||
They are ignored except they may contain [tags](#tags-1), which are not ignored.
|
They are ignored except they may contain [tags](#tags), which are not ignored.
|
||||||
|
|
||||||
The two-space requirement for same-line account comments is because `;` is allowed in account names.
|
The two-space requirement for same-line account comments is because `;` is allowed in account names.
|
||||||
|
|
||||||
@ -1889,7 +1891,7 @@ This enables easy reports like [balancesheet] and [incomestatement], and filteri
|
|||||||
|
|
||||||
As a convenience, hledger will detect these account types automatically if you are using common english-language top-level account names (described below).
|
As a convenience, hledger will detect these account types automatically if you are using common english-language top-level account names (described below).
|
||||||
But generally we recommend you declare types explicitly,
|
But generally we recommend you declare types explicitly,
|
||||||
by adding a `type:` [tag](#tags-1) to your top-level account directives.
|
by adding a `type:` [tag](#tags) to your top-level account directives.
|
||||||
Subaccounts will inherit the type of their parent.
|
Subaccounts will inherit the type of their parent.
|
||||||
The tag's value should be one of the [five main account types]:
|
The tag's value should be one of the [five main account types]:
|
||||||
|
|
||||||
@ -2527,7 +2529,7 @@ amount applied to a given transaction, as it will be unable to infer amounts.
|
|||||||
|
|
||||||
#### Auto posting tags
|
#### Auto posting tags
|
||||||
|
|
||||||
Automated postings will have some extra [tags](#tags-1):
|
Automated postings will have some extra [tags](#tags):
|
||||||
|
|
||||||
- `generated-posting:= QUERY` - shows this was generated by an auto posting rule, and the query
|
- `generated-posting:= QUERY` - shows this was generated by an auto posting rule, and the query
|
||||||
- `_generated-posting:= QUERY` - a hidden tag, which does not appear in hledger's output.
|
- `_generated-posting:= QUERY` - a hidden tag, which does not appear in hledger's output.
|
||||||
@ -5733,7 +5735,7 @@ These data entry commands are the only ones which can modify your journal file.
|
|||||||
- **[print](#print)** - show transactions (journal entries)
|
- **[print](#print)** - show transactions (journal entries)
|
||||||
- **[register](#register) (reg)** - show postings in one or more accounts & running total
|
- **[register](#register) (reg)** - show postings in one or more accounts & running total
|
||||||
- [stats](#stats) - show journal statistics
|
- [stats](#stats) - show journal statistics
|
||||||
- [tags](#tags) - show tag names
|
- [tags](#tags-1) - show tag names
|
||||||
- [test](#test) - run self tests
|
- [test](#test) - run self tests
|
||||||
|
|
||||||
<a name="addons"></a>
|
<a name="addons"></a>
|
||||||
|
Loading…
Reference in New Issue
Block a user