From 3cf21190c07cd9e42333b9974186b3dfbd8d3dee Mon Sep 17 00:00:00 2001 From: Simon Michael Date: Sat, 5 Jan 2019 07:31:13 +0000 Subject: [PATCH] update embedded manuals --- hledger-api/hledger-api.1 | 2 +- hledger-api/hledger-api.info | 8 +- hledger-api/hledger-api.txt | 2 +- hledger-lib/hledger_csv.5 | 2 +- hledger-lib/hledger_csv.info | 60 ++--- hledger-lib/hledger_csv.txt | 2 +- hledger-lib/hledger_journal.5 | 6 +- hledger-lib/hledger_journal.info | 208 +++++++++-------- hledger-lib/hledger_journal.txt | 348 ++++++++++++++--------------- hledger-lib/hledger_timeclock.5 | 2 +- hledger-lib/hledger_timeclock.info | 4 +- hledger-lib/hledger_timeclock.txt | 2 +- hledger-lib/hledger_timedot.5 | 2 +- hledger-lib/hledger_timedot.info | 8 +- hledger-lib/hledger_timedot.txt | 2 +- hledger-ui/hledger-ui.1 | 2 +- hledger-ui/hledger-ui.info | 32 +-- hledger-ui/hledger-ui.txt | 2 +- hledger-web/hledger-web.1 | 2 +- hledger-web/hledger-web.info | 8 +- hledger-web/hledger-web.txt | 2 +- hledger/hledger.1 | 2 +- hledger/hledger.info | 298 ++++++++++++------------ hledger/hledger.txt | 2 +- 24 files changed, 512 insertions(+), 496 deletions(-) diff --git a/hledger-api/hledger-api.1 b/hledger-api/hledger-api.1 index c75b24f7f..145d4f6fa 100644 --- a/hledger-api/hledger-api.1 +++ b/hledger-api/hledger-api.1 @@ -1,5 +1,5 @@ -.TH "hledger\-api" "1" "December 2018" "hledger\-api 1.12" "hledger User Manuals" +.TH "hledger\-api" "1" "January 2019" "hledger\-api 1.12.99" "hledger User Manuals" diff --git a/hledger-api/hledger-api.info b/hledger-api/hledger-api.info index 118e2ba3f..7f56014d7 100644 --- a/hledger-api/hledger-api.info +++ b/hledger-api/hledger-api.info @@ -3,8 +3,8 @@ This is hledger-api.info, produced by makeinfo version 6.5 from stdin.  File: hledger-api.info, Node: Top, Next: OPTIONS, Up: (dir) -hledger-api(1) hledger-api 1.12 -******************************* +hledger-api(1) hledger-api 1.12.99 +********************************** hledger-api is a simple web API server, intended to support client-side web apps operating on hledger data. It comes with a series of simple @@ -80,7 +80,7 @@ options as shown above.  Tag Table: Node: Top72 -Node: OPTIONS1660 -Ref: #options1745 +Node: OPTIONS1666 +Ref: #options1751  End Tag Table diff --git a/hledger-api/hledger-api.txt b/hledger-api/hledger-api.txt index fbe7a2746..0584ae141 100644 --- a/hledger-api/hledger-api.txt +++ b/hledger-api/hledger-api.txt @@ -117,4 +117,4 @@ SEE ALSO -hledger-api 1.12 December 2018 hledger-api(1) +hledger-api 1.12.99 January 2019 hledger-api(1) diff --git a/hledger-lib/hledger_csv.5 b/hledger-lib/hledger_csv.5 index b04c67ace..f9ccc0396 100644 --- a/hledger-lib/hledger_csv.5 +++ b/hledger-lib/hledger_csv.5 @@ -1,5 +1,5 @@ -.TH "hledger_csv" "5" "December 2018" "hledger 1.12" "hledger User Manuals" +.TH "hledger_csv" "5" "January 2019" "hledger 1.12.99" "hledger User Manuals" diff --git a/hledger-lib/hledger_csv.info b/hledger-lib/hledger_csv.info index d8ea27c17..bcc8d5a54 100644 --- a/hledger-lib/hledger_csv.info +++ b/hledger-lib/hledger_csv.info @@ -3,8 +3,8 @@ This is hledger_csv.info, produced by makeinfo version 6.5 from stdin.  File: hledger_csv.info, Node: Top, Next: CSV RULES, Up: (dir) -hledger_csv(5) hledger 1.12 -*************************** +hledger_csv(5) hledger 1.12.99 +****************************** hledger can read CSV (comma-separated value) files as if they were journal files, automatically converting each CSV record into a @@ -317,33 +317,33 @@ one rules file will be used for all the CSV files being read.  Tag Table: Node: Top72 -Node: CSV RULES2163 -Ref: #csv-rules2271 -Node: skip2533 -Ref: #skip2627 -Node: date-format2799 -Ref: #date-format2926 -Node: field list3432 -Ref: #field-list3569 -Node: field assignment4274 -Ref: #field-assignment4429 -Node: conditional block4933 -Ref: #conditional-block5087 -Node: include5983 -Ref: #include6113 -Node: newest-first6344 -Ref: #newest-first6458 -Node: CSV TIPS6869 -Ref: #csv-tips6963 -Node: CSV ordering7081 -Ref: #csv-ordering7199 -Node: CSV accounts7380 -Ref: #csv-accounts7518 -Node: CSV amounts7772 -Ref: #csv-amounts7918 -Node: CSV balance assertions8693 -Ref: #csv-balance-assertions8875 -Node: Reading multiple CSV files9080 -Ref: #reading-multiple-csv-files9250 +Node: CSV RULES2169 +Ref: #csv-rules2277 +Node: skip2539 +Ref: #skip2633 +Node: date-format2805 +Ref: #date-format2932 +Node: field list3438 +Ref: #field-list3575 +Node: field assignment4280 +Ref: #field-assignment4435 +Node: conditional block4939 +Ref: #conditional-block5093 +Node: include5989 +Ref: #include6119 +Node: newest-first6350 +Ref: #newest-first6464 +Node: CSV TIPS6875 +Ref: #csv-tips6969 +Node: CSV ordering7087 +Ref: #csv-ordering7205 +Node: CSV accounts7386 +Ref: #csv-accounts7524 +Node: CSV amounts7778 +Ref: #csv-amounts7924 +Node: CSV balance assertions8699 +Ref: #csv-balance-assertions8881 +Node: Reading multiple CSV files9086 +Ref: #reading-multiple-csv-files9256  End Tag Table diff --git a/hledger-lib/hledger_csv.txt b/hledger-lib/hledger_csv.txt index 80b1bf7b0..7f7c7dfbd 100644 --- a/hledger-lib/hledger_csv.txt +++ b/hledger-lib/hledger_csv.txt @@ -249,4 +249,4 @@ SEE ALSO -hledger 1.12 December 2018 hledger_csv(5) +hledger 1.12.99 January 2019 hledger_csv(5) diff --git a/hledger-lib/hledger_journal.5 b/hledger-lib/hledger_journal.5 index c0fa10672..1de9cf14f 100644 --- a/hledger-lib/hledger_journal.5 +++ b/hledger-lib/hledger_journal.5 @@ -1,6 +1,6 @@ .\"t -.TH "hledger_journal" "5" "December 2018" "hledger 1.12" "hledger User Manuals" +.TH "hledger_journal" "5" "January 2019" "hledger 1.12.99" "hledger User Manuals" @@ -598,6 +598,10 @@ One workaround is to isolate each commodity into its own subaccount: \ \ a:euro\ \ \ 0\ ==\ \ 1€ \f[] .fi +.SS Assertions and prices +.PP +Balance assertion (or assignment) amounts should not have a price, as +the meaning of that would be unclear. .SS Assertions and subaccounts .PP Balance assertions do not count the balance from subaccounts; they check diff --git a/hledger-lib/hledger_journal.info b/hledger-lib/hledger_journal.info index 7a4148fdd..4325ca423 100644 --- a/hledger-lib/hledger_journal.info +++ b/hledger-lib/hledger_journal.info @@ -4,8 +4,8 @@ stdin.  File: hledger_journal.info, Node: Top, Next: FILE FORMAT, Up: (dir) -hledger_journal(5) hledger 1.12 -******************************* +hledger_journal(5) hledger 1.12.99 +********************************** hledger's usual data source is a plain text file containing journal entries in hledger journal format. This file represents a standard @@ -473,6 +473,7 @@ or for reading Ledger files. * Assertions and included files:: * Assertions and multiple -f options:: * Assertions and commodities:: +* Assertions and prices:: * Assertions and subaccounts:: * Assertions and virtual postings:: @@ -517,7 +518,7 @@ Balance assertions don't work well across files specified with multiple -f options. Use include or concatenate the files instead.  -File: hledger_journal.info, Node: Assertions and commodities, Next: Assertions and subaccounts, Prev: Assertions and multiple -f options, Up: Balance Assertions +File: hledger_journal.info, Node: Assertions and commodities, Next: Assertions and prices, Prev: Assertions and multiple -f options, Up: Balance Assertions 1.9.4 Assertions and commodities -------------------------------- @@ -566,9 +567,18 @@ commodity into its own subaccount: a:euro 0 == 1€  -File: hledger_journal.info, Node: Assertions and subaccounts, Next: Assertions and virtual postings, Prev: Assertions and commodities, Up: Balance Assertions +File: hledger_journal.info, Node: Assertions and prices, Next: Assertions and subaccounts, Prev: Assertions and commodities, Up: Balance Assertions -1.9.5 Assertions and subaccounts +1.9.5 Assertions and prices +--------------------------- + +Balance assertion (or assignment) amounts should not have a price, as +the meaning of that would be unclear. + + +File: hledger_journal.info, Node: Assertions and subaccounts, Next: Assertions and virtual postings, Prev: Assertions and prices, Up: Balance Assertions + +1.9.6 Assertions and subaccounts -------------------------------- Balance assertions do not count the balance from subaccounts; they check @@ -591,7 +601,7 @@ $ hledger bal checking --flat  File: hledger_journal.info, Node: Assertions and virtual postings, Prev: Assertions and subaccounts, Up: Balance Assertions -1.9.6 Assertions and virtual postings +1.9.7 Assertions and virtual postings ------------------------------------- Balance assertions are checked against all postings, both real and @@ -1511,97 +1521,99 @@ Code  Tag Table: Node: Top76 -Node: FILE FORMAT2372 -Ref: #file-format2496 -Node: Transactions2783 -Ref: #transactions2904 -Node: Postings3588 -Ref: #postings3715 -Node: Dates4710 -Ref: #dates4825 -Node: Simple dates4890 -Ref: #simple-dates5016 -Node: Secondary dates5382 -Ref: #secondary-dates5536 -Node: Posting dates7099 -Ref: #posting-dates7228 -Node: Status8602 -Ref: #status8722 -Node: Description10430 -Ref: #description10568 -Node: Payee and note10887 -Ref: #payee-and-note11001 -Node: Account names11243 -Ref: #account-names11386 -Node: Amounts11873 -Ref: #amounts12009 -Node: Virtual Postings15026 -Ref: #virtual-postings15185 -Node: Balance Assertions16405 -Ref: #balance-assertions16580 -Node: Assertions and ordering17476 -Ref: #assertions-and-ordering17662 -Node: Assertions and included files18362 -Ref: #assertions-and-included-files18603 -Node: Assertions and multiple -f options18936 -Ref: #assertions-and-multiple--f-options19190 -Node: Assertions and commodities19322 -Ref: #assertions-and-commodities19557 -Node: Assertions and subaccounts20745 -Ref: #assertions-and-subaccounts20977 -Node: Assertions and virtual postings21498 -Ref: #assertions-and-virtual-postings21705 -Node: Balance Assignments21847 -Ref: #balance-assignments22028 -Node: Transaction prices23148 -Ref: #transaction-prices23317 -Node: Comments25585 -Ref: #comments25719 -Node: Tags26889 -Ref: #tags27007 -Node: Directives28409 -Ref: #directives28552 -Node: Comment blocks34159 -Ref: #comment-blocks34304 -Node: Including other files34480 -Ref: #including-other-files34660 -Node: Default year35068 -Ref: #default-year35237 -Node: Declaring commodities35660 -Ref: #declaring-commodities35843 -Node: Default commodity37070 -Ref: #default-commodity37246 -Node: Market prices37882 -Ref: #market-prices38047 -Node: Declaring accounts38888 -Ref: #declaring-accounts39064 -Node: Account types40021 -Ref: #account-types40170 -Node: Account comments41244 -Ref: #account-comments41429 -Node: Account display order41750 -Ref: #account-display-order41923 -Node: Rewriting accounts43045 -Ref: #rewriting-accounts43230 -Node: Basic aliases43964 -Ref: #basic-aliases44110 -Node: Regex aliases44814 -Ref: #regex-aliases44985 -Node: Multiple aliases45703 -Ref: #multiple-aliases45878 -Node: end aliases46376 -Ref: #end-aliases46523 -Node: Default parent account46624 -Ref: #default-parent-account46790 -Node: Periodic transactions47674 -Ref: #periodic-transactions47856 -Node: Forecasting with periodic transactions49559 -Ref: #forecasting-with-periodic-transactions49802 -Node: Budgeting with periodic transactions51489 -Ref: #budgeting-with-periodic-transactions51728 -Node: Transaction Modifiers52187 -Ref: #transaction-modifiers52350 -Node: EDITOR SUPPORT54331 -Ref: #editor-support54449 +Node: FILE FORMAT2378 +Ref: #file-format2502 +Node: Transactions2789 +Ref: #transactions2910 +Node: Postings3594 +Ref: #postings3721 +Node: Dates4716 +Ref: #dates4831 +Node: Simple dates4896 +Ref: #simple-dates5022 +Node: Secondary dates5388 +Ref: #secondary-dates5542 +Node: Posting dates7105 +Ref: #posting-dates7234 +Node: Status8608 +Ref: #status8728 +Node: Description10436 +Ref: #description10574 +Node: Payee and note10893 +Ref: #payee-and-note11007 +Node: Account names11249 +Ref: #account-names11392 +Node: Amounts11879 +Ref: #amounts12015 +Node: Virtual Postings15032 +Ref: #virtual-postings15191 +Node: Balance Assertions16411 +Ref: #balance-assertions16586 +Node: Assertions and ordering17508 +Ref: #assertions-and-ordering17694 +Node: Assertions and included files18394 +Ref: #assertions-and-included-files18635 +Node: Assertions and multiple -f options18968 +Ref: #assertions-and-multiple--f-options19222 +Node: Assertions and commodities19354 +Ref: #assertions-and-commodities19584 +Node: Assertions and prices20772 +Ref: #assertions-and-prices20984 +Node: Assertions and subaccounts21093 +Ref: #assertions-and-subaccounts21320 +Node: Assertions and virtual postings21841 +Ref: #assertions-and-virtual-postings22048 +Node: Balance Assignments22190 +Ref: #balance-assignments22371 +Node: Transaction prices23491 +Ref: #transaction-prices23660 +Node: Comments25928 +Ref: #comments26062 +Node: Tags27232 +Ref: #tags27350 +Node: Directives28752 +Ref: #directives28895 +Node: Comment blocks34502 +Ref: #comment-blocks34647 +Node: Including other files34823 +Ref: #including-other-files35003 +Node: Default year35411 +Ref: #default-year35580 +Node: Declaring commodities36003 +Ref: #declaring-commodities36186 +Node: Default commodity37413 +Ref: #default-commodity37589 +Node: Market prices38225 +Ref: #market-prices38390 +Node: Declaring accounts39231 +Ref: #declaring-accounts39407 +Node: Account types40364 +Ref: #account-types40513 +Node: Account comments41587 +Ref: #account-comments41772 +Node: Account display order42093 +Ref: #account-display-order42266 +Node: Rewriting accounts43388 +Ref: #rewriting-accounts43573 +Node: Basic aliases44307 +Ref: #basic-aliases44453 +Node: Regex aliases45157 +Ref: #regex-aliases45328 +Node: Multiple aliases46046 +Ref: #multiple-aliases46221 +Node: end aliases46719 +Ref: #end-aliases46866 +Node: Default parent account46967 +Ref: #default-parent-account47133 +Node: Periodic transactions48017 +Ref: #periodic-transactions48199 +Node: Forecasting with periodic transactions49902 +Ref: #forecasting-with-periodic-transactions50145 +Node: Budgeting with periodic transactions51832 +Ref: #budgeting-with-periodic-transactions52071 +Node: Transaction Modifiers52530 +Ref: #transaction-modifiers52693 +Node: EDITOR SUPPORT54674 +Ref: #editor-support54792  End Tag Table diff --git a/hledger-lib/hledger_journal.txt b/hledger-lib/hledger_journal.txt index 6fbf8e562..8dae3ce9a 100644 --- a/hledger-lib/hledger_journal.txt +++ b/hledger-lib/hledger_journal.txt @@ -446,8 +446,12 @@ FILE FORMAT a:usd 0 == $1 a:euro 0 == 1 + Assertions and prices + Balance assertion (or assignment) amounts should not have a price, as + the meaning of that would be unclear. + Assertions and subaccounts - Balance assertions do not count the balance from subaccounts; they + Balance assertions do not count the balance from subaccounts; they check the posted account's exclusive balance. For example: 1/1 @@ -455,7 +459,7 @@ FILE FORMAT checking 1 = 1 ; post to the parent account, its exclusive balance is now 1 equity - The balance report's flat mode shows these exclusive balances more + The balance report's flat mode shows these exclusive balances more clearly: $ hledger bal checking --flat @@ -469,10 +473,10 @@ FILE FORMAT tual. They are not affected by the --real/-R flag or real: query. Balance Assignments - Ledger-style balance assignments are also supported. These are like - balance assertions, but with no posting amount on the left side of the - equals sign; instead it is calculated automatically so as to satisfy - the assertion. This can be a convenience during data entry, eg when + Ledger-style balance assignments are also supported. These are like + balance assertions, but with no posting amount on the left side of the + equals sign; instead it is calculated automatically so as to satisfy + the assertion. This can be a convenience during data entry, eg when setting opening balances: ; starting a new journal, set asset account balances @@ -490,17 +494,17 @@ FILE FORMAT expenses:misc The calculated amount depends on the account's balance in the commodity - at that point (which depends on the previously-dated postings of the - commodity to that account since the last balance assertion or assign- + at that point (which depends on the previously-dated postings of the + commodity to that account since the last balance assertion or assign- ment). Note that using balance assignments makes your journal a little less explicit; to know the exact amount posted, you have to run hledger or do the calculations yourself, instead of just reading it. Transaction prices Within a transaction, you can note an amount's price in another commod- - ity. This can be used to document the cost (in a purchase) or selling - price (in a sale). For example, transaction prices are useful to - record purchases of a foreign currency. Note transaction prices are + ity. This can be used to document the cost (in a purchase) or selling + price (in a sale). For example, transaction prices are useful to + record purchases of a foreign currency. Note transaction prices are fixed at the time of the transaction, and do not change over time. See also market prices, which represent prevailing exchange rates on a cer- tain date. @@ -529,7 +533,7 @@ FILE FORMAT (Ledger users: Ledger uses a different syntax for fixed prices, {=UNIT- PRICE}, which hledger currently ignores). - Use the -B/--cost flag to convert amounts to their transaction price's + Use the -B/--cost flag to convert amounts to their transaction price's commodity, if any. (mnemonic: "B" is from "cost Basis", as in Ledger). Eg here is how -B affects the balance report for the example above: @@ -540,8 +544,8 @@ FILE FORMAT $-135 assets:dollars $135 assets:euros # <- the euros' cost - Note -B is sensitive to the order of postings when a transaction price - is inferred: the inferred price will be in the commodity of the last + Note -B is sensitive to the order of postings when a transaction price + is inferred: the inferred price will be in the commodity of the last amount. So if example 3's postings are reversed, while the transaction is equivalent, -B shows something different: @@ -555,14 +559,14 @@ FILE FORMAT Comments Lines in the journal beginning with a semicolon (;) or hash (#) or star - (*) are comments, and will be ignored. (Star comments cause org-mode - nodes to be ignored, allowing emacs users to fold and navigate their + (*) are comments, and will be ignored. (Star comments cause org-mode + nodes to be ignored, allowing emacs users to fold and navigate their journals with org-mode or orgstruct-mode.) - You can attach comments to a transaction by writing them after the - description and/or indented on the following lines (before the post- - ings). Similarly, you can attach comments to an individual posting by - writing them after the amount and/or indented on the following lines. + You can attach comments to a transaction by writing them after the + description and/or indented on the following lines (before the post- + ings). Similarly, you can attach comments to an individual posting by + writing them after the amount and/or indented on the following lines. Transaction and posting comments must begin with a semicolon (;). Some examples: @@ -586,24 +590,24 @@ FILE FORMAT ; another comment line for posting 2 ; a file comment (because not indented) - You can also comment larger regions of a file using comment and + You can also comment larger regions of a file using comment and end comment directives. Tags - Tags are a way to add extra labels or labelled data to postings and + Tags are a way to add extra labels or labelled data to postings and transactions, which you can then search or pivot on. - A simple tag is a word (which may contain hyphens) followed by a full + A simple tag is a word (which may contain hyphens) followed by a full colon, written inside a transaction or posting comment line: 2017/1/16 bought groceries ; sometag: - Tags can have a value, which is the text after the colon, up to the + Tags can have a value, which is the text after the colon, up to the next comma or end of line, with leading/trailing whitespace removed: expenses:food $10 ; a-posting-tag: the tag value - Note this means hledger's tag values can not contain commas or new- + Note this means hledger's tag values can not contain commas or new- lines. Ending at commas means you can write multiple short tags on one line, comma separated: @@ -617,55 +621,55 @@ FILE FORMAT o "tag2" is another tag, whose value is "some value ..." - Tags in a transaction comment affect the transaction and all of its - postings, while tags in a posting comment affect only that posting. - For example, the following transaction has three tags (A, TAG2, + Tags in a transaction comment affect the transaction and all of its + postings, while tags in a posting comment affect only that posting. + For example, the following transaction has three tags (A, TAG2, third-tag) and the posting has four (those plus posting-tag): 1/1 a transaction ; A:, TAG2: ; third-tag: a third transaction tag, <- with a value (a) $1 ; posting-tag: - Tags are like Ledger's metadata feature, except hledger's tag values + Tags are like Ledger's metadata feature, except hledger's tag values are simple strings. Directives - A directive is a line in the journal beginning with a special keyword, + A directive is a line in the journal beginning with a special keyword, that influences how the journal is processed. hledger's directives are based on a subset of Ledger's, but there are many differences (and also some differences between hledger versions). Directives' behaviour and interactions can get a little bit complex, so - here is a table summarising the directives and their effects, with + here is a table summarising the directives and their effects, with links to more detailed docs. - direc- end subdi- purpose can affect (as of + direc- end subdi- purpose can affect (as of tive directive rec- 2018/06) tives ------------------------------------------------------------------------------------------------- - account any document account names, all entries in all - text declare account types & dis- files, before or + account any document account names, all entries in all + text declare account types & dis- files, before or play order after alias end aliases rewrite account names following inline/included entries until end - of current file or + of current file or end directive - apply account end apply account prepend a common parent to following + apply account end apply account prepend a common parent to following account names inline/included entries until end - of current file or + of current file or end directive comment end comment ignore part of journal following inline/included entries until end - of current file or + of current file or end directive - commodity format declare a commodity and its number notation: + commodity format declare a commodity and its number notation: number notation & display following entries style in that commodity - in all files; dis- + in all files; dis- play style: amounts of that commodity in reports @@ -677,18 +681,14 @@ FILE FORMAT - - - - - D declare a commodity, number commodity: all com- + D declare a commodity, number commodity: all com- notation & display style for modityless entries - commodityless amounts in all files; num- - ber notation: fol- + commodityless amounts in all files; num- + ber notation: fol- lowing commodity- - less entries and + less entries and entries in that - commodity in all + commodity in all files; display style: amounts of that commodity in @@ -699,7 +699,7 @@ FILE FORMAT commodity commodity in reports, when -V is used - Y declare a year for yearless following + Y declare a year for yearless following dates inline/included entries until end of current file @@ -709,9 +709,9 @@ FILE FORMAT subdirec- optional indented directive line immediately following a par- tive ent directive - number how to interpret numbers when parsing journal entries (the - notation identity of the decimal separator character). (Currently - each commodity can have its own notation, even in the same + number how to interpret numbers when parsing journal entries (the + notation identity of the decimal separator character). (Currently + each commodity can have its own notation, even in the same file.) display how to display amounts of a commodity in reports (symbol side style and spacing, digit groups, decimal separator, decimal places) @@ -719,37 +719,37 @@ FILE FORMAT scope are affected by a directive As you can see, directives vary in which journal entries and files they - affect, and whether they are focussed on input (parsing) or output + affect, and whether they are focussed on input (parsing) or output (reports). Some directives have multiple effects. - If you have a journal made up of multiple files, or pass multiple -f - options on the command line, note that directives which affect input - typically last only until the end of their defining file. This pro- + If you have a journal made up of multiple files, or pass multiple -f + options on the command line, note that directives which affect input + typically last only until the end of their defining file. This pro- vides more simplicity and predictability, eg reports are not changed by - writing file options in a different order. It can be surprising at + writing file options in a different order. It can be surprising at times though. Comment blocks - A line containing just comment starts a commented region of the file, + A line containing just comment starts a commented region of the file, and a line containing just end comment (or the end of the current file) ends it. See also comments. Including other files - You can pull in the content of additional files by writing an include + You can pull in the content of additional files by writing an include directive, like this: include path/to/file.journal - If the path does not begin with a slash, it is relative to the current - file. The include file path may contain common glob patterns (e.g. + If the path does not begin with a slash, it is relative to the current + file. The include file path may contain common glob patterns (e.g. *). - The include directive can only be used in journal files. It can + The include directive can only be used in journal files. It can include journal, timeclock or timedot files, but not CSV files. Default year - You can set a default year to be used for subsequent dates which don't - specify a year. This is a line beginning with Y followed by the year. + You can set a default year to be used for subsequent dates which don't + specify a year. This is a line beginning with Y followed by the year. Eg: Y2009 ; set default year to 2009 @@ -769,8 +769,8 @@ FILE FORMAT assets Declaring commodities - The commodity directive declares commodities which may be used in the - journal (though currently we do not enforce this). It may be written + The commodity directive declares commodities which may be used in the + journal (though currently we do not enforce this). It may be written on a single line, like this: ; commodity EXAMPLEAMOUNT @@ -780,8 +780,8 @@ FILE FORMAT ; separating thousands with comma. commodity 1,000.0000 AAAA - or on multiple lines, using the "format" subdirective. In this case - the commodity symbol appears twice and should be the same in both + or on multiple lines, using the "format" subdirective. In this case + the commodity symbol appears twice and should be the same in both places: ; commodity SYMBOL @@ -793,19 +793,19 @@ FILE FORMAT commodity INR format INR 9,99,99,999.00 - Commodity directives have a second purpose: they define the standard + Commodity directives have a second purpose: they define the standard display format for amounts in the commodity. Normally the display for- - mat is inferred from journal entries, but this can be unpredictable; - declaring it with a commodity directive overrides this and removes - ambiguity. Towards this end, amounts in commodity directives must - always be written with a decimal point (a period or comma, followed by + mat is inferred from journal entries, but this can be unpredictable; + declaring it with a commodity directive overrides this and removes + ambiguity. Towards this end, amounts in commodity directives must + always be written with a decimal point (a period or comma, followed by 0 or more decimal digits). Default commodity - The D directive sets a default commodity (and display format), to be + The D directive sets a default commodity (and display format), to be used for amounts without a commodity symbol (ie, plain numbers). (Note - this differs from Ledger's default commodity directive.) The commodity - and display format will be applied to all subsequent commodity-less + this differs from Ledger's default commodity directive.) The commodity + and display format will be applied to all subsequent commodity-less amounts, or until the next D directive. # commodity-less amounts should be treated as dollars @@ -820,9 +820,9 @@ FILE FORMAT a decimal point. Market prices - The P directive declares a market price, which is an exchange rate + The P directive declares a market price, which is an exchange rate between two commodities on a certain date. (In Ledger, they are called - "historical prices".) These are often obtained from a stock exchange, + "historical prices".) These are often obtained from a stock exchange, cryptocurrency exchange, or the foreign exchange market. Here is the format: @@ -833,36 +833,36 @@ FILE FORMAT o COMMODITYA is the symbol of the commodity being priced - o COMMODITYBAMOUNT is an amount (symbol and quantity) in a second com- + o COMMODITYBAMOUNT is an amount (symbol and quantity) in a second com- modity, giving the price in commodity B of one unit of commodity A. - These two market price directives say that one euro was worth 1.35 US + These two market price directives say that one euro was worth 1.35 US dollars during 2009, and $1.40 from 2010 onward: P 2009/1/1 $1.35 P 2010/1/1 $1.40 - The -V/--value flag can be used to convert reported amounts to another + The -V/--value flag can be used to convert reported amounts to another commodity using these prices. Declaring accounts - account directives can be used to pre-declare some or all accounts. + account directives can be used to pre-declare some or all accounts. Though not required, they can provide several benefits: o They can document your intended chart of accounts, providing a refer- ence. - o They can store extra information about accounts (account numbers, + o They can store extra information about accounts (account numbers, notes, etc.) - o They can help hledger know your accounts' types (asset, liability, - equity, revenue, expense), useful for reports like balancesheet and + o They can help hledger know your accounts' types (asset, liability, + equity, revenue, expense), useful for reports like balancesheet and incomestatement. - o They control account display order in reports, allowing non-alpha- + o They control account display order in reports, allowing non-alpha- betic sorting (eg Revenues to appear above Expenses). - o They help with account name completion in the add command, + o They help with account name completion in the add command, hledger-iadd, hledger-web, ledger-mode etc. Here is the full syntax: @@ -875,15 +875,15 @@ FILE FORMAT account assets:bank:checking Account types - hledger recognises five types of account: asset, liability, equity, + hledger recognises five types of account: asset, liability, equity, revenue, expense. This is useful for certain accounting-aware reports, in particular balancesheet, incomestatement and cashflow. If you name your top-level accounts with some variation of assets, lia- - bilities/debts, equity, revenues/income, or expenses, their types are + bilities/debts, equity, revenues/income, or expenses, their types are detected automatically. - More generally, you can declare an account's type by adding one of the + More generally, you can declare an account's type by adding one of the letters ALERX to its account directive, separated from the account name by two or more spaces. Eg: @@ -893,8 +893,8 @@ FILE FORMAT account revenues R account expenses X - Note: if you ever override the types of those auto-detected english - account names mentioned above, you might need to help the reports a + Note: if you ever override the types of those auto-detected english + account names mentioned above, you might need to help the reports a bit: ; make "liabilities" not have the liability type, who knows why @@ -907,22 +907,22 @@ FILE FORMAT ) Account comments - An account directive can also have indented comments on following + An account directive can also have indented comments on following lines, eg: account assets:bank:checking ; acctno:12345 ; a comment - We also allow (and ignore) Ledger-style subdirectives, with no leading + We also allow (and ignore) Ledger-style subdirectives, with no leading semicolon, for compatibility. - Tags in account comments, like acctno above, currently have no effect. + Tags in account comments, like acctno above, currently have no effect. Account display order - Account directives also set the order in which accounts are displayed - in reports, the hledger-ui accounts screen, the hledger-web sidebar, - etc. Normally accounts are listed in alphabetical order, but if you + Account directives also set the order in which accounts are displayed + in reports, the hledger-ui accounts screen, the hledger-web sidebar, + etc. Normally accounts are listed in alphabetical order, but if you have eg these account directives in the journal: account assets @@ -931,7 +931,7 @@ FILE FORMAT account revenues account expenses - you'll see those accounts listed in declaration order, not alphabeti- + you'll see those accounts listed in declaration order, not alphabeti- cally: $ hledger accounts -1 @@ -943,16 +943,16 @@ FILE FORMAT Undeclared accounts, if any, are displayed last, in alphabetical order. - Note that sorting is done at each level of the account tree (within - each group of sibling accounts under the same parent). And currently, + Note that sorting is done at each level of the account tree (within + each group of sibling accounts under the same parent). And currently, this directive: account other:zoo - would influence the position of zoo among other's subaccounts, but not - the position of other among the top-level accounts. This means: - you - will sometimes declare parent accounts (eg account other above) that - you don't intend to post to, just to customize their display order - + would influence the position of zoo among other's subaccounts, but not + the position of other among the top-level accounts. This means: - you + will sometimes declare parent accounts (eg account other above) that + you don't intend to post to, just to customize their display order - sibling accounts stay together (you couldn't display x:y in between a:b and a:c). @@ -971,14 +971,14 @@ FILE FORMAT o customising reports Account aliases also rewrite account names in account directives. They - do not affect account names being entered via hledger add or + do not affect account names being entered via hledger add or hledger-web. See also Cookbook: Rewrite account names. Basic aliases - To set an account alias, use the alias directive in your journal file. - This affects all subsequent journal entries in the current file or its + To set an account alias, use the alias directive in your journal file. + This affects all subsequent journal entries in the current file or its included files. The spaces around the = are optional: alias OLD = NEW @@ -986,54 +986,54 @@ FILE FORMAT Or, you can use the --alias 'OLD=NEW' option on the command line. This affects all entries. It's useful for trying out aliases interactively. - OLD and NEW are case sensitive full account names. hledger will - replace any occurrence of the old account name with the new one. Sub- + OLD and NEW are case sensitive full account names. hledger will + replace any occurrence of the old account name with the new one. Sub- accounts are also affected. Eg: alias checking = assets:bank:wells fargo:checking # rewrites "checking" to "assets:bank:wells fargo:checking", or "checking:a" to "assets:bank:wells fargo:checking:a" Regex aliases - There is also a more powerful variant that uses a regular expression, + There is also a more powerful variant that uses a regular expression, indicated by the forward slashes: alias /REGEX/ = REPLACEMENT or --alias '/REGEX/=REPLACEMENT'. - REGEX is a case-insensitive regular expression. Anywhere it matches - inside an account name, the matched part will be replaced by REPLACE- - MENT. If REGEX contains parenthesised match groups, these can be ref- + REGEX is a case-insensitive regular expression. Anywhere it matches + inside an account name, the matched part will be replaced by REPLACE- + MENT. If REGEX contains parenthesised match groups, these can be ref- erenced by the usual numeric backreferences in REPLACEMENT. Eg: alias /^(.+):bank:([^:]+)(.*)/ = \1:\2 \3 # rewrites "assets:bank:wells fargo:checking" to "assets:wells fargo checking" - Also note that REPLACEMENT continues to the end of line (or on command - line, to end of option argument), so it can contain trailing white- + Also note that REPLACEMENT continues to the end of line (or on command + line, to end of option argument), so it can contain trailing white- space. Multiple aliases - You can define as many aliases as you like using directives or com- - mand-line options. Aliases are recursive - each alias sees the result - of applying previous ones. (This is different from Ledger, where + You can define as many aliases as you like using directives or com- + mand-line options. Aliases are recursive - each alias sees the result + of applying previous ones. (This is different from Ledger, where aliases are non-recursive by default). Aliases are applied in the fol- lowing order: - 1. alias directives, most recently seen first (recent directives take + 1. alias directives, most recently seen first (recent directives take precedence over earlier ones; directives not yet seen are ignored) 2. alias options, in the order they appear on the command line end aliases - You can clear (forget) all currently defined aliases with the + You can clear (forget) all currently defined aliases with the end aliases directive: end aliases Default parent account - You can specify a parent account which will be prepended to all - accounts within a section of the journal. Use the apply account and + You can specify a parent account which will be prepended to all + accounts within a section of the journal. Use the apply account and end apply account directives like so: apply account home @@ -1050,7 +1050,7 @@ FILE FORMAT home:food $10 home:cash $-10 - If end apply account is omitted, the effect lasts to the end of the + If end apply account is omitted, the effect lasts to the end of the file. Included files are also affected, eg: apply account business @@ -1059,18 +1059,18 @@ FILE FORMAT apply account personal include personal.journal - Prior to hledger 1.0, legacy account and end spellings were also sup- + Prior to hledger 1.0, legacy account and end spellings were also sup- ported. - A default parent account also affects account directives. It does not - affect account names being entered via hledger add or hledger-web. If - account aliases are present, they are applied after the default parent + A default parent account also affects account directives. It does not + affect account names being entered via hledger add or hledger-web. If + account aliases are present, they are applied after the default parent account. Periodic transactions - Periodic transaction rules describe transactions that recur. They + Periodic transaction rules describe transactions that recur. They allow you to generate future transactions for forecasting, without hav- - ing to write them out explicitly in the journal (with --forecast). + ing to write them out explicitly in the journal (with --forecast). Secondly, they also can be used to define budget goals (with --budget). A periodic transaction rule looks like a normal journal entry, with the @@ -1081,20 +1081,20 @@ FILE FORMAT expenses:rent $2000 assets:bank:checking - There is an additional constraint on the period expression: the start - date must fall on a natural boundary of the interval. Eg + There is an additional constraint on the period expression: the start + date must fall on a natural boundary of the interval. Eg monthly from 2018/1/1 is valid, but monthly from 2018/1/15 is not. - Partial or relative dates (M/D, D, tomorrow, last week) in the period - expression can work (useful or not). They will be relative to today's - date, unless a Y default year directive is in effect, in which case + Partial or relative dates (M/D, D, tomorrow, last week) in the period + expression can work (useful or not). They will be relative to today's + date, unless a Y default year directive is in effect, in which case they will be relative to Y/1/1. Period expressions must be terminated by two or more spaces if followed - by additional fields. For example, the periodic transaction given + by additional fields. For example, the periodic transaction given below includes a transaction description "paycheck", which is separated - from the period expression by a double space. If not for the second - space, hledger would attempt (and fail) to parse "paycheck" as a part + from the period expression by a double space. If not for the second + space, hledger would attempt (and fail) to parse "paycheck" as a part of the period expression. ; 2 or more spaces @@ -1105,65 +1105,65 @@ FILE FORMAT income:acme inc Forecasting with periodic transactions - With the --forecast flag, each periodic transaction rule generates + 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 named recur, whose value is + saved in the journal, but appear in all reports. They will look like + normal transactions, but with an extra tag named recur, whose value is the generating period expression. - Forecast transactions start on the first occurrence, and end on the - last occurrence, of their interval within the forecast period. The + Forecast transactions start on the first occurrence, and end on the + last occurrence, of their interval within the forecast period. The forecast period: o begins on the later of o the report start date if specified with -b/-p/date: - o the day after the latest normal (non-periodic) transaction in the + o the day after the latest normal (non-periodic) transaction in the journal, or today if there are no normal transactions. - o ends on the report end date if specified with -e/-p/date:, or 180 + o ends on the report end date if specified with -e/-p/date:, or 180 days from today. - where "today" means the current date at report time. The "later of" - rule ensures that forecast transactions do not overlap normal transac- + where "today" means the current date at report time. The "later of" + rule ensures that forecast transactions do not overlap normal transac- tions in time; they will begin only after normal transactions end. - Forecasting can be useful for estimating balances into the future, and - experimenting with different scenarios. Note the start date logic + Forecasting can be useful for estimating balances into the future, and + experimenting with different scenarios. Note the start date logic means that forecasted transactions are automatically replaced by normal transactions as you add those. Forecasting can also help with data entry: describe most of your trans- - actions with periodic rules, and every so often copy the output of + actions with periodic rules, and every so often copy the output of print --forecast to the journal. You can generate one-time transactions too: just write a period expres- - sion specifying a date with no report interval. (You could also write - a normal transaction with a future date, but remember this disables + sion specifying a date with no report interval. (You could also write + a normal transaction with a future date, but remember this disables forecast transactions on previous dates.) Budgeting with periodic transactions - With the --budget flag, currently supported by the balance command, - each periodic transaction rule declares recurring budget goals for the - specified accounts. Eg the first example above declares a goal of - spending $2000 on rent (and also, a goal of depositing $2000 into - checking) every month. Goals and actual performance can then be com- + With the --budget flag, currently supported by the balance command, + each periodic transaction rule declares recurring budget goals for the + specified accounts. Eg the first example above declares a goal of + spending $2000 on rent (and also, a goal of depositing $2000 into + checking) every month. Goals and actual performance can then be com- pared in budget reports. - For more details, see: balance: Budget report and Cookbook: Budgeting + For more details, see: balance: Budget report and Cookbook: Budgeting and Forecasting. Transaction Modifiers - Transaction modifier rules describe changes that should be applied - automatically to certain transactions. Currently, this means adding + Transaction modifier rules describe changes that should be applied + automatically to certain transactions. Currently, this means adding extra postings (also known as "automated postings"). Transaction modi- fiers are enabled by the --auto flag. - A transaction modifier rule looks quite like a normal transaction, - except the first line is an equals sign followed by a query that - matches certain postings (mnemonic: = suggests matching). And each + A transaction modifier rule looks quite like a normal transaction, + except the first line is an equals sign followed by a query that + matches certain postings (mnemonic: = suggests matching). And each "posting" is actually a posting-generating rule: = QUERY @@ -1174,17 +1174,17 @@ FILE FORMAT The posting rules look just like normal postings, except the amount can be: - o a normal amount with a commodity symbol, eg $2. This will be used + o a normal amount with a commodity symbol, eg $2. This will be used as-is. o a number, eg 2. The commodity symbol (if any) from the matched post- ing will be added to this. - o a numeric multiplier, eg *2 (a star followed by a number N). The + o a numeric multiplier, eg *2 (a star followed by a number N). The matched posting's amount (and total price, if any) will be multiplied by N. - o a multiplier with a commodity symbol, eg *$2 (a star, number N, and + o a multiplier with a commodity symbol, eg *$2 (a star, number N, and symbol S). The matched posting's amount will be multiplied by N, and its commodity symbol will be replaced with S. @@ -1220,16 +1220,16 @@ FILE FORMAT assets:checking $20 Postings added by transaction modifiers participate in transaction bal- - ancing, missing amount inference and balance assertions, like regular + ancing, missing amount inference and balance assertions, like regular postings. EDITOR SUPPORT Add-on modes exist for various text editors, to make working with jour- - nal files easier. They add colour, navigation aids and helpful com- - mands. For hledger users who edit the journal file directly (the + nal files easier. They add colour, navigation aids and helpful com- + mands. For hledger users who edit the journal file directly (the majority), using one of these modes is quite recommended. - These were written with Ledger in mind, but also work with hledger + These were written with Ledger in mind, but also work with hledger files: @@ -1248,7 +1248,7 @@ EDITOR SUPPORT REPORTING BUGS - Report bugs at http://bugs.hledger.org (or on the #hledger IRC channel + Report bugs at http://bugs.hledger.org (or on the #hledger IRC channel or hledger mail list) @@ -1262,7 +1262,7 @@ COPYRIGHT SEE ALSO - hledger(1), hledger-ui(1), hledger-web(1), hledger-api(1), + hledger(1), hledger-ui(1), hledger-web(1), hledger-api(1), hledger_csv(5), hledger_journal(5), hledger_timeclock(5), hledger_time- dot(5), ledger(1) @@ -1270,4 +1270,4 @@ SEE ALSO -hledger 1.12 December 2018 hledger_journal(5) +hledger 1.12.99 January 2019 hledger_journal(5) diff --git a/hledger-lib/hledger_timeclock.5 b/hledger-lib/hledger_timeclock.5 index 769f3862a..e00ccce44 100644 --- a/hledger-lib/hledger_timeclock.5 +++ b/hledger-lib/hledger_timeclock.5 @@ -1,5 +1,5 @@ -.TH "hledger_timeclock" "5" "December 2018" "hledger 1.12" "hledger User Manuals" +.TH "hledger_timeclock" "5" "January 2019" "hledger 1.12.99" "hledger User Manuals" diff --git a/hledger-lib/hledger_timeclock.info b/hledger-lib/hledger_timeclock.info index 17696bac5..c8ff34b8a 100644 --- a/hledger-lib/hledger_timeclock.info +++ b/hledger-lib/hledger_timeclock.info @@ -4,8 +4,8 @@ stdin.  File: hledger_timeclock.info, Node: Top, Up: (dir) -hledger_timeclock(5) hledger 1.12 -********************************* +hledger_timeclock(5) hledger 1.12.99 +************************************ hledger can read timeclock files. As with Ledger, these are (a subset of) timeclock.el's format, containing clock-in and clock-out entries as diff --git a/hledger-lib/hledger_timeclock.txt b/hledger-lib/hledger_timeclock.txt index 044727fc0..df0ca193f 100644 --- a/hledger-lib/hledger_timeclock.txt +++ b/hledger-lib/hledger_timeclock.txt @@ -77,4 +77,4 @@ SEE ALSO -hledger 1.12 December 2018 hledger_timeclock(5) +hledger 1.12.99 January 2019 hledger_timeclock(5) diff --git a/hledger-lib/hledger_timedot.5 b/hledger-lib/hledger_timedot.5 index 56ec37a6f..2c6e51d74 100644 --- a/hledger-lib/hledger_timedot.5 +++ b/hledger-lib/hledger_timedot.5 @@ -1,5 +1,5 @@ -.TH "hledger_timedot" "5" "December 2018" "hledger 1.12" "hledger User Manuals" +.TH "hledger_timedot" "5" "January 2019" "hledger 1.12.99" "hledger User Manuals" diff --git a/hledger-lib/hledger_timedot.info b/hledger-lib/hledger_timedot.info index 2bd7d15e8..cbdacdbd3 100644 --- a/hledger-lib/hledger_timedot.info +++ b/hledger-lib/hledger_timedot.info @@ -4,8 +4,8 @@ stdin.  File: hledger_timedot.info, Node: Top, Next: FILE FORMAT, Up: (dir) -hledger_timedot(5) hledger 1.12 -******************************* +hledger_timedot(5) hledger 1.12.99 +********************************** Timedot is a plain text format for logging dated, categorised quantities (of time, usually), supported by hledger. It is convenient for @@ -110,7 +110,7 @@ $ hledger -f t.timedot --alias /\\./=: bal date:2016/2/4  Tag Table: Node: Top76 -Node: FILE FORMAT807 -Ref: #file-format908 +Node: FILE FORMAT813 +Ref: #file-format914  End Tag Table diff --git a/hledger-lib/hledger_timedot.txt b/hledger-lib/hledger_timedot.txt index d669f6d08..492a55699 100644 --- a/hledger-lib/hledger_timedot.txt +++ b/hledger-lib/hledger_timedot.txt @@ -124,4 +124,4 @@ SEE ALSO -hledger 1.12 December 2018 hledger_timedot(5) +hledger 1.12.99 January 2019 hledger_timedot(5) diff --git a/hledger-ui/hledger-ui.1 b/hledger-ui/hledger-ui.1 index 3fb99beaa..31b18c08d 100644 --- a/hledger-ui/hledger-ui.1 +++ b/hledger-ui/hledger-ui.1 @@ -1,5 +1,5 @@ -.TH "hledger\-ui" "1" "December 2018" "hledger\-ui 1.12" "hledger User Manuals" +.TH "hledger\-ui" "1" "January 2019" "hledger\-ui 1.12.99" "hledger User Manuals" diff --git a/hledger-ui/hledger-ui.info b/hledger-ui/hledger-ui.info index 9647fccb2..b5ddfa286 100644 --- a/hledger-ui/hledger-ui.info +++ b/hledger-ui/hledger-ui.info @@ -3,8 +3,8 @@ This is hledger-ui.info, produced by makeinfo version 6.5 from stdin.  File: hledger-ui.info, Node: Top, Next: OPTIONS, Up: (dir) -hledger-ui(1) hledger-ui 1.12 -***************************** +hledger-ui(1) hledger-ui 1.12.99 +******************************** hledger-ui is hledger's curses-style interface, providing an efficient full-window text UI for viewing accounts and transactions, and some @@ -396,19 +396,19 @@ to cancel the reload attempt.)  Tag Table: Node: Top71 -Node: OPTIONS1084 -Ref: #options1181 -Node: KEYS4600 -Ref: #keys4695 -Node: SCREENS7951 -Ref: #screens8036 -Node: Accounts screen8126 -Ref: #accounts-screen8254 -Node: Register screen10470 -Ref: #register-screen10625 -Node: Transaction screen12622 -Ref: #transaction-screen12780 -Node: Error screen13650 -Ref: #error-screen13772 +Node: OPTIONS1090 +Ref: #options1187 +Node: KEYS4606 +Ref: #keys4701 +Node: SCREENS7957 +Ref: #screens8042 +Node: Accounts screen8132 +Ref: #accounts-screen8260 +Node: Register screen10476 +Ref: #register-screen10631 +Node: Transaction screen12628 +Ref: #transaction-screen12786 +Node: Error screen13656 +Ref: #error-screen13778  End Tag Table diff --git a/hledger-ui/hledger-ui.txt b/hledger-ui/hledger-ui.txt index 4729f5ae6..b7ad748b9 100644 --- a/hledger-ui/hledger-ui.txt +++ b/hledger-ui/hledger-ui.txt @@ -404,4 +404,4 @@ SEE ALSO -hledger-ui 1.12 December 2018 hledger-ui(1) +hledger-ui 1.12.99 January 2019 hledger-ui(1) diff --git a/hledger-web/hledger-web.1 b/hledger-web/hledger-web.1 index cf6a6e4b0..f07212d47 100644 --- a/hledger-web/hledger-web.1 +++ b/hledger-web/hledger-web.1 @@ -1,5 +1,5 @@ -.TH "hledger\-web" "1" "December 2018" "hledger\-web 1.12" "hledger User Manuals" +.TH "hledger\-web" "1" "January 2019" "hledger\-web 1.12.99" "hledger User Manuals" diff --git a/hledger-web/hledger-web.info b/hledger-web/hledger-web.info index aa50d6587..e3252efd4 100644 --- a/hledger-web/hledger-web.info +++ b/hledger-web/hledger-web.info @@ -3,8 +3,8 @@ This is hledger-web.info, produced by makeinfo version 6.5 from stdin.  File: hledger-web.info, Node: Top, Next: OPTIONS, Up: (dir) -hledger-web(1) hledger-web 1.12 -******************************* +hledger-web(1) hledger-web 1.12.99 +********************************** hledger-web is hledger's web interface. It starts a simple web application for browsing and adding transactions, and optionally opens @@ -212,7 +212,7 @@ this, insert a '--' argument before.)  Tag Table: Node: Top72 -Node: OPTIONS3154 -Ref: #options3239 +Node: OPTIONS3160 +Ref: #options3245  End Tag Table diff --git a/hledger-web/hledger-web.txt b/hledger-web/hledger-web.txt index 685358e1d..db841de8a 100644 --- a/hledger-web/hledger-web.txt +++ b/hledger-web/hledger-web.txt @@ -251,4 +251,4 @@ SEE ALSO -hledger-web 1.12 December 2018 hledger-web(1) +hledger-web 1.12.99 January 2019 hledger-web(1) diff --git a/hledger/hledger.1 b/hledger/hledger.1 index 24b4b1507..7d94e20c4 100644 --- a/hledger/hledger.1 +++ b/hledger/hledger.1 @@ -1,6 +1,6 @@ .\"t -.TH "hledger" "1" "December 2018" "hledger 1.12" "hledger User Manuals" +.TH "hledger" "1" "January 2019" "hledger 1.12.99" "hledger User Manuals" diff --git a/hledger/hledger.info b/hledger/hledger.info index 814cfcdbc..6621b5e2c 100644 --- a/hledger/hledger.info +++ b/hledger/hledger.info @@ -3,8 +3,8 @@ This is hledger.info, produced by makeinfo version 6.5 from stdin.  File: hledger.info, Node: Top, Next: EXAMPLES, Up: (dir) -hledger(1) hledger 1.12 -*********************** +hledger(1) hledger 1.12.99 +************************** This is hledger's command-line interface (there are also curses and web interfaces). Its basic function is to read a plain text file describing @@ -2554,152 +2554,152 @@ hledger-check.hs checks more powerful account balance assertions.  Tag Table: Node: Top68 -Node: EXAMPLES1884 -Ref: #examples1984 -Node: OPTIONS3630 -Ref: #options3732 -Node: General options4167 -Ref: #general-options4292 -Node: Command options6974 -Ref: #command-options7125 -Node: Command arguments7523 -Ref: #command-arguments7677 -Node: Argument files7798 -Ref: #argument-files7974 -Node: Special characters in arguments and queries8240 -Ref: #special-characters-in-arguments-and-queries8474 -Node: More escaping8924 -Ref: #more-escaping9086 -Node: Even more escaping9382 -Ref: #even-more-escaping9576 -Node: Less escaping10247 -Ref: #less-escaping10409 -Node: Command line tips10654 -Ref: #command-line-tips10840 -Node: Unicode characters11217 -Ref: #unicode-characters11373 -Node: Input files12098 -Ref: #input-files12234 -Node: Smart dates14204 -Ref: #smart-dates14345 -Node: Report start & end date15751 -Ref: #report-start-end-date15923 -Node: Report intervals16988 -Ref: #report-intervals17153 -Node: Period expressions17554 -Ref: #period-expressions17714 -Node: Depth limiting21671 -Ref: #depth-limiting21815 -Node: Pivoting22157 -Ref: #pivoting22275 -Node: Cost23951 -Ref: #cost24059 -Node: Market value24177 -Ref: #market-value24312 -Node: Combining -B and -V25678 -Ref: #combining--b-and--v25841 -Node: Output destination25988 -Ref: #output-destination26150 -Node: Output format26433 -Ref: #output-format26585 -Node: Regular expressions26970 -Ref: #regular-expressions27107 -Node: QUERIES28468 -Ref: #queries28570 -Node: COMMANDS32532 -Ref: #commands32644 -Node: accounts33644 -Ref: #accounts33742 -Node: activity34988 -Ref: #activity35098 -Node: add35458 -Ref: #add35557 -Node: balance38218 -Ref: #balance38329 -Node: Classic balance report41412 -Ref: #classic-balance-report41585 -Node: Customising the classic balance report42954 -Ref: #customising-the-classic-balance-report43182 -Node: Colour support45256 -Ref: #colour-support45423 -Node: Flat mode45596 -Ref: #flat-mode45744 -Node: Depth limited balance reports46157 -Ref: #depth-limited-balance-reports46357 -Node: Multicolumn balance report46813 -Ref: #multicolumn-balance-report47011 -Node: Budget report52191 -Ref: #budget-report52334 -Ref: #output-format-155368 -Node: balancesheet55446 -Ref: #balancesheet55582 -Node: balancesheetequity57893 -Ref: #balancesheetequity58042 -Node: cashflow58579 -Ref: #cashflow58707 -Node: check-dates60830 -Ref: #check-dates60957 -Node: check-dupes61074 -Ref: #check-dupes61198 -Node: close61335 -Ref: #close61443 -Node: files61773 -Ref: #files61874 -Node: help62015 -Ref: #help62115 -Node: import63189 -Ref: #import63303 -Node: incomestatement64033 -Ref: #incomestatement64167 -Node: prices66571 -Ref: #prices66686 -Node: print66958 -Ref: #print67068 -Node: print-unique71962 -Ref: #print-unique72088 -Node: register72156 -Ref: #register72283 -Node: Custom register output76784 -Ref: #custom-register-output76913 -Node: register-match78143 -Ref: #register-match78277 -Node: rewrite78460 -Ref: #rewrite78575 -Node: roi78644 -Ref: #roi78742 -Node: stats78858 -Ref: #stats78957 -Node: tags79827 -Ref: #tags79925 -Node: test80161 -Ref: #test80245 -Node: ADD-ON COMMANDS80953 -Ref: #add-on-commands81063 -Node: Official add-ons82350 -Ref: #official-add-ons82490 -Node: api82577 -Ref: #api82666 -Node: ui82718 -Ref: #ui82817 -Node: web82875 -Ref: #web82964 -Node: Third party add-ons83010 -Ref: #third-party-add-ons83185 -Node: diff83320 -Ref: #diff83417 -Node: iadd83516 -Ref: #iadd83630 -Node: interest83713 -Ref: #interest83834 -Node: irr83929 -Ref: #irr84027 -Node: Experimental add-ons84158 -Ref: #experimental-add-ons84310 -Node: autosync84590 -Ref: #autosync84701 -Node: chart84940 -Ref: #chart85059 -Node: check85130 -Ref: #check85232 +Node: EXAMPLES1890 +Ref: #examples1990 +Node: OPTIONS3636 +Ref: #options3738 +Node: General options4173 +Ref: #general-options4298 +Node: Command options6980 +Ref: #command-options7131 +Node: Command arguments7529 +Ref: #command-arguments7683 +Node: Argument files7804 +Ref: #argument-files7980 +Node: Special characters in arguments and queries8246 +Ref: #special-characters-in-arguments-and-queries8480 +Node: More escaping8930 +Ref: #more-escaping9092 +Node: Even more escaping9388 +Ref: #even-more-escaping9582 +Node: Less escaping10253 +Ref: #less-escaping10415 +Node: Command line tips10660 +Ref: #command-line-tips10846 +Node: Unicode characters11223 +Ref: #unicode-characters11379 +Node: Input files12104 +Ref: #input-files12240 +Node: Smart dates14210 +Ref: #smart-dates14351 +Node: Report start & end date15757 +Ref: #report-start-end-date15929 +Node: Report intervals16994 +Ref: #report-intervals17159 +Node: Period expressions17560 +Ref: #period-expressions17720 +Node: Depth limiting21677 +Ref: #depth-limiting21821 +Node: Pivoting22163 +Ref: #pivoting22281 +Node: Cost23957 +Ref: #cost24065 +Node: Market value24183 +Ref: #market-value24318 +Node: Combining -B and -V25684 +Ref: #combining--b-and--v25847 +Node: Output destination25994 +Ref: #output-destination26156 +Node: Output format26439 +Ref: #output-format26591 +Node: Regular expressions26976 +Ref: #regular-expressions27113 +Node: QUERIES28474 +Ref: #queries28576 +Node: COMMANDS32538 +Ref: #commands32650 +Node: accounts33650 +Ref: #accounts33748 +Node: activity34994 +Ref: #activity35104 +Node: add35464 +Ref: #add35563 +Node: balance38224 +Ref: #balance38335 +Node: Classic balance report41418 +Ref: #classic-balance-report41591 +Node: Customising the classic balance report42960 +Ref: #customising-the-classic-balance-report43188 +Node: Colour support45262 +Ref: #colour-support45429 +Node: Flat mode45602 +Ref: #flat-mode45750 +Node: Depth limited balance reports46163 +Ref: #depth-limited-balance-reports46363 +Node: Multicolumn balance report46819 +Ref: #multicolumn-balance-report47017 +Node: Budget report52197 +Ref: #budget-report52340 +Ref: #output-format-155374 +Node: balancesheet55452 +Ref: #balancesheet55588 +Node: balancesheetequity57899 +Ref: #balancesheetequity58048 +Node: cashflow58585 +Ref: #cashflow58713 +Node: check-dates60836 +Ref: #check-dates60963 +Node: check-dupes61080 +Ref: #check-dupes61204 +Node: close61341 +Ref: #close61449 +Node: files61779 +Ref: #files61880 +Node: help62021 +Ref: #help62121 +Node: import63195 +Ref: #import63309 +Node: incomestatement64039 +Ref: #incomestatement64173 +Node: prices66577 +Ref: #prices66692 +Node: print66964 +Ref: #print67074 +Node: print-unique71968 +Ref: #print-unique72094 +Node: register72162 +Ref: #register72289 +Node: Custom register output76790 +Ref: #custom-register-output76919 +Node: register-match78149 +Ref: #register-match78283 +Node: rewrite78466 +Ref: #rewrite78581 +Node: roi78650 +Ref: #roi78748 +Node: stats78864 +Ref: #stats78963 +Node: tags79833 +Ref: #tags79931 +Node: test80167 +Ref: #test80251 +Node: ADD-ON COMMANDS80959 +Ref: #add-on-commands81069 +Node: Official add-ons82356 +Ref: #official-add-ons82496 +Node: api82583 +Ref: #api82672 +Node: ui82724 +Ref: #ui82823 +Node: web82881 +Ref: #web82970 +Node: Third party add-ons83016 +Ref: #third-party-add-ons83191 +Node: diff83326 +Ref: #diff83423 +Node: iadd83522 +Ref: #iadd83636 +Node: interest83719 +Ref: #interest83840 +Node: irr83935 +Ref: #irr84033 +Node: Experimental add-ons84164 +Ref: #experimental-add-ons84316 +Node: autosync84596 +Ref: #autosync84707 +Node: chart84946 +Ref: #chart85065 +Node: check85136 +Ref: #check85238  End Tag Table diff --git a/hledger/hledger.txt b/hledger/hledger.txt index 1409f56a0..ebd41094f 100644 --- a/hledger/hledger.txt +++ b/hledger/hledger.txt @@ -2286,4 +2286,4 @@ SEE ALSO -hledger 1.12 December 2018 hledger(1) +hledger 1.12.99 January 2019 hledger(1)