hledger 1.50.1 → 1.50.2
raw patch · 13 files changed
+549/−583 lines, 13 filesdep ~hledger-libPVP ok
version bump matches the API change (PVP)
Dependency ranges changed: hledger-lib
API changes (from Hackage documentation)
Files
- CHANGES.md +22/−0
- Hledger/Cli/Commands/Print.txt +6/−8
- Hledger/Cli/Commands/Register.txt +1/−1
- embeddedfiles/hledger-ui.1 +2/−14
- embeddedfiles/hledger-ui.info +6/−16
- embeddedfiles/hledger-ui.txt +2/−12
- embeddedfiles/hledger-web.1 +2/−2
- embeddedfiles/hledger-web.info +1/−1
- embeddedfiles/hledger-web.txt +2/−2
- embeddedfiles/hledger.1 +39/−48
- embeddedfiles/hledger.info +408/−413
- embeddedfiles/hledger.txt +50/−58
- hledger.cabal +8/−8
CHANGES.md view
@@ -26,6 +26,28 @@ User-visible changes in the hledger command line tool and library. +# 1.50.2 2025-09-26++Fixes++- The CSV `encoding` rule is now respected when using the rules file as input file. This was a regression in 1.50.+ Also, the text decoding error message has been clarified; it now mentions a possible CSV encoding.+ [#2465]++- The doc for `--depth` has been clarified, and now mentions the use of quotes.+ (Quả Cầu, Simon Michael, [hledger_site#140])++- A typo was fixed in the --depth example in `register`'s doc.+ ([hledger_site#140], reported by Quả Cầu)++- Our package bounds now avoid hashtables 1.3.x, which fails to build with some gcc versions+ (see https://github.com/gregorycollins/hashtables/issues/97)).+ (hseg, [#2463])++[#2463]: https://github.com/simonmichael/hledger/issues/2463+[#2465]: https://github.com/simonmichael/hledger/issues/2465++ # 1.50.1 2025-09-16 Fixes
Hledger/Cli/Commands/Print.txt view
@@ -4,8 +4,12 @@ Flags: -x --explicit show all amounts explicitly- --show-costs show transaction prices even with conversion- postings+ --invert display all amounts with reversed sign+ --location add tags showing file paths and line numbers+ -m --match=DESC fuzzy search for one recent transaction with+ description closest to DESC+ --new show only newer-dated transactions added in each+ file since last run --round=TYPE how much rounding or padding should be done when displaying amounts ? none - show original decimal digits,@@ -16,15 +20,9 @@ (can unbalance transactions) all - also round cost amounts to precision (can unbalance transactions)- --invert display all amounts with reversed sign- --new show only newer-dated transactions added in each- file since last run- -m --match=DESC fuzzy search for one recent transaction with- description closest to DESC --base-url=URLPREFIX in html output, generate links to hledger-web, with this prefix. (Usually the base url shown by hledger-web; can also be relative.)- --location add tags showing file paths and line numbers -O --output-format=FMT select the output format. Supported formats: txt, beancount, csv, tsv, html, fods, json, sql. -o --output-file=FILE write output to FILE. A file extension matching
Hledger/Cli/Commands/Register.txt view
@@ -116,7 +116,7 @@ Often, you'll want to see just one line per interval. The --depth option helps with this, causing subaccounts to be aggregated: -$ hledger register --monthly assets --depth 1h+$ hledger register --monthly assets --depth 1 2008/01 assets $1 $1 2008/06 assets $-1 0 2008/12 assets $-1 $-1
embeddedfiles/hledger-ui.1 view
@@ -1,5 +1,5 @@ -.TH "HLEDGER\-UI" "1" "September 2025" "hledger-ui-1.50.1 " "hledger User Manuals"+.TH "HLEDGER\-UI" "1" "September 2025" "hledger-ui-1.50.2 " "hledger User Manuals" @@ -17,7 +17,7 @@ .PD \f[CR]hledger ui [OPTS] [QUERYARGS]\f[R] .SH DESCRIPTION-This manual is for hledger\[aq]s terminal interface, version 1.50.1.+This manual is for hledger\[aq]s terminal interface, version 1.50.2. See also the hledger manual for common concepts and file formats. .PP hledger is a robust, user\-friendly, cross\-platform set of programs for@@ -406,14 +406,6 @@ On this screen (and the register screen), the \f[CR]E\f[R] key will open your text editor with the cursor positioned at the current transaction if possible.-.PP-This screen has a limitation with showing file updates: it will not show-them until you exit and re\-enter it.-So eg to see the effect of using the \f[CR]E\f[R] key, currently you-must: \- press \f[CR]E\f[R], edit and save the file, then exit the-editor, returning to hledger\-ui \- press \f[CR]g\f[R] to reload the-file (or use \f[CR]\-w/\-\-watch\f[R] mode) \- press \f[CR]LEFT\f[R]-then \f[CR]RIGHT\f[R] to exit and re\-enter the transaction screen. .SS Error screen This screen will appear if there is a problem, such as a parse error, when you press g to reload.@@ -494,10 +486,6 @@ .PP \f[CR]\-\-watch\f[R] is not robust, especially with large files (see WATCH MODE above).-.PP-The Transaction screen does not update after file changes, even if you-press \f[CR]g\f[R], until you exit and re\-enter it.-(#2288) .PP If you press \f[CR]g\f[R] with large files, there could be a noticeable pause with the UI unresponsive.
embeddedfiles/hledger-ui.info view
@@ -18,7 +18,7 @@ or 'hledger ui [OPTS] [QUERYARGS]' - This manual is for hledger's terminal interface, version 1.50.1. See+ This manual is for hledger's terminal interface, version 1.50.2. See also the hledger manual for common concepts and file formats. hledger is a robust, user-friendly, cross-platform set of programs@@ -453,13 +453,6 @@ text editor with the cursor positioned at the current transaction if possible. - This screen has a limitation with showing file updates: it will not-show them until you exit and re-enter it. So eg to see the effect of-using the 'E' key, currently you must: - press 'E', edit and save the-file, then exit the editor, returning to hledger-ui - press 'g' to-reload the file (or use '-w/--watch' mode) - press 'LEFT' then 'RIGHT'-to exit and re-enter the transaction screen.- File: hledger-ui.info, Node: Error screen, Prev: Transaction screen, Up: SCREENS @@ -556,9 +549,6 @@ '--watch' is not robust, especially with large files (see WATCH MODE above). - The Transaction screen does not update after file changes, even if-you press 'g', until you exit and re-enter it. (#2288)- If you press 'g' with large files, there could be a noticeable pause with the UI unresponsive. @@ -576,11 +566,11 @@ Node: All accounts screen16229 Node: Register screen16592 Node: Transaction screen19035-Node: Error screen20610-Node: WATCH MODE20976-Node: --watch problems21874-Node: ENVIRONMENT23227-Node: BUGS23460+Node: Error screen20215+Node: WATCH MODE20581+Node: --watch problems21479+Node: ENVIRONMENT22832+Node: BUGS23065 End Tag Table
embeddedfiles/hledger-ui.txt view
@@ -11,7 +11,7 @@ hledger ui [OPTS] [QUERYARGS] DESCRIPTION- This manual is for hledger's terminal interface, version 1.50.1. See+ This manual is for hledger's terminal interface, version 1.50.2. See also the hledger manual for common concepts and file formats. hledger is a robust, user-friendly, cross-platform set of programs for@@ -366,13 +366,6 @@ editor with the cursor positioned at the current transaction if possi- ble. - This screen has a limitation with showing file updates: it will not- show them until you exit and re-enter it. So eg to see the effect of- using the E key, currently you must: - press E, edit and save the file,- then exit the editor, returning to hledger-ui - press g to reload the- file (or use -w/--watch mode) - press LEFT then RIGHT to exit and- re-enter the transaction screen.- Error screen This screen will appear if there is a problem, such as a parse error, when you press g to reload. Once you have fixed the problem, press g@@ -447,9 +440,6 @@ --watch is not robust, especially with large files (see WATCH MODE above). - The Transaction screen does not update after file changes, even if you- press g, until you exit and re-enter it. (#2288)- If you press g with large files, there could be a noticeable pause with the UI unresponsive. @@ -471,4 +461,4 @@ SEE ALSO hledger(1), hledger-ui(1), hledger-web(1), ledger(1) -hledger-ui-1.50.1 September 2025 HLEDGER-UI(1)+hledger-ui-1.50.2 September 2025 HLEDGER-UI(1)
embeddedfiles/hledger-web.1 view
@@ -1,5 +1,5 @@ -.TH "HLEDGER\-WEB" "1" "September 2025" "hledger-web-1.50.1 " "hledger User Manuals"+.TH "HLEDGER\-WEB" "1" "September 2025" "hledger-web-1.50.2 " "hledger User Manuals" @@ -17,7 +17,7 @@ .PD \f[CR]hledger web [OPTS] [QUERY]\f[R] .SH DESCRIPTION-This manual is for hledger\[aq]s web interface, version 1.50.1.+This manual is for hledger\[aq]s web interface, version 1.50.2. See also the hledger manual for common concepts and file formats. .PP hledger is a robust, user\-friendly, cross\-platform set of programs for
embeddedfiles/hledger-web.info view
@@ -18,7 +18,7 @@ or 'hledger web [OPTS] [QUERY]' - This manual is for hledger's web interface, version 1.50.1. See also+ This manual is for hledger's web interface, version 1.50.2. See also the hledger manual for common concepts and file formats. hledger is a robust, user-friendly, cross-platform set of programs
embeddedfiles/hledger-web.txt view
@@ -11,7 +11,7 @@ hledger web [OPTS] [QUERY] DESCRIPTION- This manual is for hledger's web interface, version 1.50.1. See also+ This manual is for hledger's web interface, version 1.50.2. See also the hledger manual for common concepts and file formats. hledger is a robust, user-friendly, cross-platform set of programs for@@ -480,4 +480,4 @@ SEE ALSO hledger(1), hledger-ui(1), hledger-web(1), ledger(1) -hledger-web-1.50.1 September 2025 HLEDGER-WEB(1)+hledger-web-1.50.2 September 2025 HLEDGER-WEB(1)
embeddedfiles/hledger.1 view
@@ -1,6 +1,6 @@ .\"t -.TH "HLEDGER" "1" "September 2025" "hledger-1.50.1 " "hledger User Manuals"+.TH "HLEDGER" "1" "September 2025" "hledger-1.50.2 " "hledger User Manuals" @@ -27,7 +27,7 @@ hledger is inspired by and largely compatible with ledger(1), and largely interconvertible with beancount(1). .PP-This manual is for hledger\[aq]s command line interface, version 1.50.1.+This manual is for hledger\[aq]s command line interface, version 1.50.2. It also describes the common options, file formats and concepts used by all hledger programs. It might accidentally teach you some bookkeeping/accounting as well!@@ -828,7 +828,7 @@ \f[I]# Options following a \[ga][COMMAND]\[ga] heading are used with that hledger command only.\f[R] \f[B][print]\f[R]-\-\-explicit \-\-show\-costs+\-\-explicit \-\-infer\-costs .EE .PP To use a config file, specify it with the \f[CR]\-\-conf\f[R] option.@@ -6693,46 +6693,37 @@ reports will show accounts only to the specified depth, hiding deeper subaccounts. Use this when you want a summary with less detail.-This flag has the same effect as a \f[CR]depth:\f[R] query argument:-\f[CR]depth:2\f[R], \f[CR]\-\-depth=2\f[R] or \f[CR]\-2\f[R] are-equivalent.+This flag has the same effect as a \f[CR]depth:\f[R] query argument.+So all of these are equivalent: \f[CR]depth:2\f[R],+\f[CR]\-\-depth=2\f[R], \f[CR]\-2\f[R]. .PP In place of a single number which limits the depth for all accounts, you-can also provide separate depth limits for different accounts using-regular expressions \f[I](since 1.41)\f[R].-.PP-For example, \f[CR]\-\-depth assets=2\f[R] (or, equivalently:+can also provide depth limits for specific accounts, by providing a+\f[CR]REGEX=DEPTH\f[R] argument instead of just a \f[CR]DEPTH\f[R]+\f[I](since 1.41)\f[R].+For example, \f[CR]\-\-depth assets=2\f[R] (or \f[CR]depth:assets=2\f[R]) will collapse accounts matching the regular-expression \f[CR]assets\f[R] to depth 2.+expression \[dq]assets\[dq] to depth 2. So \f[CR]assets:bank:savings\f[R] would be collapsed to-\f[CR]assets:bank\f[R], while \f[CR]liabilities:bank:credit card\f[R]+\f[CR]assets:bank\f[R], but \f[CR]liabilities:bank:credit card\f[R] would not be affected.-This can be combined with a flat depth to collapse other accounts not-matching the regular expression, so-\f[CR]\-\-depth assets=2 \-\-depth 1\f[R] would collapse-\f[CR]assets:bank:savings\f[R] to \f[CR]assets:bank\f[R] and-\f[CR]liabilities:bank:credit card\f[R] to \f[CR]liabilities\f[R]. .PP-You can supply multiple depth arguments and they will all be applied, so-\f[CR]\-\-depth assets=2 \-\-depth liabilities=3 \-\-depth 1\f[R] would-collapse:-.IP \[bu] 2-accounts matching \f[CR]assets\f[R] to depth 2,-.IP \[bu] 2-accounts matching \f[CR]liabilities\f[R] to depth 3,-.IP \[bu] 2-all other accounts to depth 1.+(If REGEX contains spaces or other special characters, enclose it in+quotes in the usual way.+Eg: \f[CR]\-\-depth \[aq]credit card=2\[aq]\f[R]) .PP+Specific depth options and a general depth option can be combined.+Eg \f[CR]\-\-depth assets=3 \-\-depth expenses=2 \-\-depth 1\f[R] would+collapse accounts containing \[dq]assets\[dq] to depth 3, accounts+containing \[dq]expenses\[dq] to depth 2, and all other accounts to+depth 1.+.PP If an account is matched by more than one regular expression depth-argument then the more specific one will be used.-For example, if-\f[CR]\-\-depth assets=1 \-\-depth assets:bank:savings=2\f[R] is-provided, then \f[CR]assets:bank:savings\f[R] will be collapsed to depth-2 rather than depth 1.-This is because \f[CR]assets:bank:savings\f[R] matches at level 3 in the-account name, while \f[CR]assets\f[R] matches at level 1.-The same would be true with the argument-\f[CR]\-\-depth assets=1 \-\-depth savings=2\f[R].+argument, the most specific (deepest) match will be used.+For example, with \f[CR]\-\-depth assets=1 \-\-depth savings=2\f[R],+\f[CR]assets:bank:savings\f[R] will be collapsed to depth 2, not depth 1+(because \[dq]savings\[dq] matches a deeper part of it than+\[dq]assets\[dq] does). .SH Queries Many hledger commands accept query arguments, which restrict their scope and let you report on a precise subset of your data.@@ -8264,7 +8255,6 @@ .SS Effect of valuation on reports Here is a reference for how valuation is supposed to affect each part of hledger\[aq]s reports.-(It\[aq]s wide, you may need to scroll sideways.) It may be useful when troubleshooting. If you find problems, please report them, ideally with a reproducible example.@@ -9708,8 +9698,12 @@ .EX Flags: \-x \-\-explicit show all amounts explicitly- \-\-show\-costs show transaction prices even with conversion- postings+ \-\-invert display all amounts with reversed sign+ \-\-location add tags showing file paths and line numbers+ \-m \-\-match=DESC fuzzy search for one recent transaction with+ description closest to DESC+ \-\-new show only newer\-dated transactions added in each+ file since last run \-\-round=TYPE how much rounding or padding should be done when displaying amounts ? none \- show original decimal digits,@@ -9720,15 +9714,9 @@ (can unbalance transactions) all \- also round cost amounts to precision (can unbalance transactions)- \-\-invert display all amounts with reversed sign- \-\-new show only newer\-dated transactions added in each- file since last run- \-m \-\-match=DESC fuzzy search for one recent transaction with- description closest to DESC \-\-base\-url=URLPREFIX in html output, generate links to hledger\-web, with this prefix. (Usually the base url shown by hledger\-web; can also be relative.)- \-\-location add tags showing file paths and line numbers \-O \-\-output\-format=FMT select the output format. Supported formats: txt, beancount, csv, tsv, html, fods, json, sql. \-o \-\-output\-file=FILE write output to FILE. A file extension matching@@ -10190,7 +10178,7 @@ be aggregated: .IP .EX-$ hledger register \-\-monthly assets \-\-depth 1h+$ hledger register \-\-monthly assets \-\-depth 1 2008/01 assets $1 $1 2008/06 assets $\-1 0 2008/12 assets $\-1 $\-1@@ -13213,13 +13201,16 @@ .PP Some known issues and limitations: .PP-A system locale with a suitable text encoding must be configured to work-with non\-ascii data.+hledger uses the system\[aq]s text encoding when reading non\-ascii+text.+If no system encoding is configured, or if the data\[aq]s encoding is+different, hledger will give an error. (See Text encoding, Troubleshooting.) .PP On Microsoft Windows, depending what kind of terminal window you use, non\-ascii characters, ANSI text formatting, and/or the add-command\[aq]s TAB key for completion, may not be supported.+command\[aq]s TAB key, may not be fully supported.+(For best results, try a powershell window.) .PP When processing large data files, hledger uses more memory than Ledger. .SS Troubleshooting
embeddedfiles/hledger.info view
@@ -24,7 +24,7 @@ and largely compatible with ledger(1), and largely interconvertible with beancount(1). - This manual is for hledger's command line interface, version 1.50.1.+ This manual is for hledger's command line interface, version 1.50.2. It also describes the common options, file formats and concepts used by all hledger programs. It might accidentally teach you some bookkeeping/accounting as well! You don't need to know everything in@@ -840,7 +840,7 @@ # Options following a `[COMMAND]` heading are used with that hledger command only. [print]---explicit --show-costs+--explicit --infer-costs To use a config file, specify it with the '--conf' option. Its options will be inserted near the start of your command line, so you can@@ -6528,36 +6528,30 @@ With the '--depth NUM' option (short form: '-NUM'), reports will show accounts only to the specified depth, hiding deeper subaccounts. Use this when you want a summary with less detail. This flag has the same-effect as a 'depth:' query argument: 'depth:2', '--depth=2' or '-2' are-equivalent.+effect as a 'depth:' query argument. So all of these are equivalent:+'depth:2', '--depth=2', '-2'. In place of a single number which limits the depth for all accounts,-you can also provide separate depth limits for different accounts using-regular expressions _(since 1.41)_.-- For example, '--depth assets=2' (or, equivalently: 'depth:assets=2')-will collapse accounts matching the regular expression 'assets' to depth-2. So 'assets:bank:savings' would be collapsed to 'assets:bank', while-'liabilities:bank:credit card' would not be affected. This can be-combined with a flat depth to collapse other accounts not matching the-regular expression, so '--depth assets=2 --depth 1' would collapse-'assets:bank:savings' to 'assets:bank' and 'liabilities:bank:credit-card' to 'liabilities'.+you can also provide depth limits for specific accounts, by providing a+'REGEX=DEPTH' argument instead of just a 'DEPTH' _(since 1.41)_. For+example, '--depth assets=2' (or 'depth:assets=2') will collapse accounts+matching the regular expression "assets" to depth 2. So+'assets:bank:savings' would be collapsed to 'assets:bank', but+'liabilities:bank:credit card' would not be affected. - You can supply multiple depth arguments and they will all be applied,-so '--depth assets=2 --depth liabilities=3 --depth 1' would collapse:+ (If REGEX contains spaces or other special characters, enclose it in+quotes in the usual way. Eg: '--depth 'credit card=2'') - * accounts matching 'assets' to depth 2,- * accounts matching 'liabilities' to depth 3,- * all other accounts to depth 1.+ Specific depth options and a general depth option can be combined.+Eg '--depth assets=3 --depth expenses=2 --depth 1' would collapse+accounts containing "assets" to depth 3, accounts containing "expenses"+to depth 2, and all other accounts to depth 1. If an account is matched by more than one regular expression depth-argument then the more specific one will be used. For example, if-'--depth assets=1 --depth assets:bank:savings=2' is provided, then-'assets:bank:savings' will be collapsed to depth 2 rather than depth 1.-This is because 'assets:bank:savings' matches at level 3 in the account-name, while 'assets' matches at level 1. The same would be true with-the argument '--depth assets=1 --depth savings=2'.+argument, the most specific (deepest) match will be used. For example,+with '--depth assets=1 --depth savings=2', 'assets:bank:savings' will be+collapsed to depth 2, not depth 1 (because "savings" matches a deeper+part of it than "assets" does). File: hledger.info, Node: Queries, Next: Pivoting, Prev: Depth, Up: Top@@ -8128,9 +8122,9 @@ ==================================== Here is a reference for how valuation is supposed to affect each part of-hledger's reports. (It's wide, you may need to scroll sideways.) It-may be useful when troubleshooting. If you find problems, please report-them, ideally with a reproducible example. Related: #329, #1083.+hledger's reports. It may be useful when troubleshooting. If you find+problems, please report them, ideally with a reproducible example.+Related: #329, #1083. First, a quick glossary: @@ -9459,8 +9453,12 @@ Flags: -x --explicit show all amounts explicitly- --show-costs show transaction prices even with conversion- postings+ --invert display all amounts with reversed sign+ --location add tags showing file paths and line numbers+ -m --match=DESC fuzzy search for one recent transaction with+ description closest to DESC+ --new show only newer-dated transactions added in each+ file since last run --round=TYPE how much rounding or padding should be done when displaying amounts ? none - show original decimal digits,@@ -9471,15 +9469,9 @@ (can unbalance transactions) all - also round cost amounts to precision (can unbalance transactions)- --invert display all amounts with reversed sign- --new show only newer-dated transactions added in each- file since last run- -m --match=DESC fuzzy search for one recent transaction with- description closest to DESC --base-url=URLPREFIX in html output, generate links to hledger-web, with this prefix. (Usually the base url shown by hledger-web; can also be relative.)- --location add tags showing file paths and line numbers -O --output-format=FMT select the output format. Supported formats: txt, beancount, csv, tsv, html, fods, json, sql. -o --output-file=FILE write output to FILE. A file extension matching@@ -9928,7 +9920,7 @@ Often, you'll want to see just one line per interval. The '--depth' option helps with this, causing subaccounts to be aggregated: -$ hledger register --monthly assets --depth 1h+$ hledger register --monthly assets --depth 1 2008/01 assets $1 $1 2008/06 assets $-1 0 2008/12 assets $-1 $-1@@ -12991,12 +12983,15 @@ Some known issues and limitations: - A system locale with a suitable text encoding must be configured to-work with non-ascii data. (See Text encoding, Troubleshooting.)+ hledger uses the system's text encoding when reading non-ascii text.+If no system encoding is configured, or if the data's encoding is+different, hledger will give an error. (See Text encoding,+Troubleshooting.) On Microsoft Windows, depending what kind of terminal window you use, non-ascii characters, ANSI text formatting, and/or the add command's TAB-key for completion, may not be supported.+key, may not be fully supported. (For best results, try a powershell+window.) When processing large data files, hledger uses more memory than Ledger.@@ -13068,378 +13063,378 @@ Node: hledger's regular expressions30424 Node: Argument files32065 Node: Config files32768-Node: Shell completions36036-Node: Output36525-Node: Output destination36716-Node: Output format37274-Node: Text output39060-Node: Box-drawing characters40039-Node: Colour40539-Node: Paging41125-Node: HTML output42644-Node: CSV / TSV output43062-Node: FODS output43316-Node: Beancount output44120-Node: Beancount account names45621-Node: Beancount commodity names46162-Node: Beancount virtual postings46809-Node: Beancount metadata47125-Node: Beancount costs47905-Node: Beancount operating currency48321-Node: SQL output48771-Node: JSON output49562-Node: Commodity styles50379-Node: Debug output51266-Node: Environment52098-Node: PART 2 DATA FORMATS52755-Node: Journal52898-Node: Journal cheatsheet55376-Node: Comments61627-Node: Transactions62571-Node: Dates63708-Node: Simple dates63860-Node: Posting dates64476-Node: Status65563-Node: Code67329-Node: Description67664-Node: Payee and note68351-Node: Transaction comments69442-Node: Postings69958-Node: Debits and credits71121-Node: The two space delimiter71731-Node: Account names72296-Node: Amounts74100-Node: Decimal marks75129-Node: Digit group marks76233-Node: Commodity76868-Node: Costs77985-Node: Balance assertions80237-Node: Assertions and ordering81485-Node: Assertions and multiple files82204-Node: Assertions and costs83372-Node: Assertions and commodities84019-Node: Assertions and subaccounts85678-Node: Assertions and status86338-Node: Assertions and virtual postings86758-Node: Assertions and auto postings87123-Node: Assertions and precision87998-Node: Assertions and hledger add88482-Node: Posting comments89230-Node: Transaction balancing89770-Node: Tags91978-Node: Querying with tags93272-Node: Displaying tags94071-Node: When to use tags ?94467-Node: Tag names95131-Node: Special tags95684-Node: Directives97249-Node: Directives and multiple files98706-Node: Directive effects99651-Node: account directive102807-Node: Account comments104257-Node: Account error checking104916-Node: Account display order106453-Node: Account types107651-Node: alias directive110926-Node: Basic aliases112137-Node: Regex aliases113012-Node: Combining aliases114059-Node: Aliases and multiple files115513-Node: end aliases directive116296-Node: Aliases can generate bad account names116664-Node: Aliases and account types117497-Node: commodity directive118389-Node: Commodity directive syntax119976-Node: Commodity error checking121625-Node: decimal-mark directive122100-Node: include directive122679-Node: P directive124897-Node: payee directive125931-Node: tag directive126553-Node: Periodic transactions127165-Node: Periodic rule syntax129319-Node: Periodic rules and relative dates130142-Node: Two spaces between period expression and description!130919-Node: Auto postings131880-Node: Auto postings and multiple files135166-Node: Auto postings and dates135571-Node: Auto postings and transaction balancing / inferred amounts / balance assertions136012-Node: Auto posting tags136858-Node: Auto postings on forecast transactions only137753-Node: Other syntax138223-Node: Balance assignments138995-Node: Balance assignments and costs140523-Node: Balance assignments and multiple files140945-Node: Bracketed posting dates141368-Node: D directive142066-Node: apply account directive143839-Node: Y directive144706-Node: Secondary dates145694-Node: Star comments147179-Node: Valuation expressions147871-Node: Virtual postings148170-Node: Other Ledger directives149794-Node: Other cost/lot notations150556-Node: CSV153397-Node: CSV rules cheatsheet155563-Node: source157662-Node: Data cleaning / generating commands159061-Node: archive160923-Node: encoding161851-Node: separator162894-Node: skip163547-Node: date-format164197-Node: timezone165142-Node: newest-first166268-Node: intra-day-reversed166981-Node: decimal-mark167583-Node: fields list168063-Node: Field assignment169871-Node: Field names171090-Node: date field172422-Node: date2 field172586-Node: status field172781-Node: code field172971-Node: description field173159-Node: comment field173376-Node: account field173933-Node: amount field174651-Node: currency field177490-Node: balance field177898-Node: if block178421-Node: Matchers179948-Node: Multiple matchers181938-Node: Match groups182746-Node: if table183639-Node: balance-type185702-Node: include186529-Node: Working with CSV187098-Node: Rapid feedback187650-Node: Valid CSV188233-Node: File Extension189109-Node: Reading CSV from standard input189844-Node: Reading multiple CSV files190230-Node: Reading files specified by rule190706-Node: Valid transactions192103-Node: Deduplicating importing192928-Node: Setting amounts194157-Node: Amount signs196684-Node: Setting currency/commodity197749-Node: Amount decimal places199125-Node: Referencing other fields200382-Node: How CSV rules are evaluated201490-Node: Well factored rules204207-Node: CSV rules examples204697-Node: Bank of Ireland204895-Node: Coinbase206492-Node: Amazon207675-Node: Paypal209517-Node: Timeclock217267-Node: Timedot221320-Node: Timedot examples224797-Node: PART 3 REPORTING CONCEPTS227074-Node: Time periods227238-Node: Report start & end date227511-Node: Smart dates228987-Node: Report intervals231110-Node: Date adjustments231684-Node: Start date adjustment231904-Node: End date adjustment232807-Node: Period headings233588-Node: Period expressions234521-Node: Period expressions with a report interval236426-Node: More complex report intervals236874-Node: Multiple weekday intervals238990-Node: Depth240001-Node: Queries241839-Node: Query types244511-Node: acct query244886-Node: amt query245197-Node: code query245894-Node: cur query246089-Node: desc query246695-Node: date query246878-Node: date2 query247274-Node: depth query247565-Node: note query247901-Node: payee query248167-Node: real query248448-Node: status query248653-Node: type query248893-Node: tag query249426-Node: Negative queries250055-Node: not query250237-Node: Space-separated queries250524-Node: Boolean queries251212-Node: expr query252530-Node: any query253210-Node: all query253663-Node: Queries and command options254245-Node: Queries and account aliases254693-Node: Queries and valuation255018-Node: Pivoting255380-Node: Generating data257656-Node: Forecasting259456-Node: --forecast260112-Node: Inspecting forecast transactions261213-Node: Forecast reports262546-Node: Forecast tags263655-Node: Forecast period in detail264275-Node: Forecast troubleshooting265363-Node: Budgeting266434-Node: Amount formatting266994-Node: Commodity display style267238-Node: Rounding269079-Node: Trailing decimal marks269684-Node: Amount parseability270617-Node: Cost reporting272226-Node: Recording costs273057-Node: Reporting at cost274784-Node: Equity conversion postings275549-Node: Inferring equity conversion postings278194-Node: Combining costs and equity conversion postings279336-Node: Requirements for detecting equity conversion postings280561-Node: Infer cost and equity by default ?282083-Node: Value reporting282520-Node: -V Value283456-Node: -X Value in specified commodity283783-Node: Valuation date284133-Node: Finding market price284966-Node: --infer-market-prices market prices from transactions286346-Node: Valuation commodity289390-Node: --value Flexible valuation290823-Node: Valuation examples292666-Node: Interaction of valuation and queries294810-Node: Effect of valuation on reports295527-Node: PART 4 COMMANDS303425-Node: Help commands306214-Node: commands306400-Node: demo306608-Node: help307701-Node: User interface commands309406-Node: repl309617-Node: Examples311881-Node: run312439-Node: Examples 2314854-Node: ui315878-Node: web316015-Node: Data entry commands316143-Node: add316404-Node: add and balance assertions318978-Node: add and balance assignments319702-Node: import320263-Node: Import dry run321342-Node: Overlap detection322290-Node: First import325176-Node: Importing balance assignments326371-Node: Import and commodity styles327426-Node: Import archiving327860-Node: Import special cases328685-Node: Deduplication328903-Node: Varying file name329394-Node: Multiple versions329778-Node: Basic report commands330885-Node: accounts331186-Node: codes333832-Node: commodities334854-Node: descriptions335611-Node: files336071-Node: notes336368-Node: payees336880-Node: prices337792-Node: stats338684-Node: tags340425-Node: Standard report commands341962-Node: print342267-Node: print explicitness345081-Node: print amount style346001-Node: print parseability347239-Node: print other features348158-Node: print output format349119-Node: aregister352404-Node: aregister and posting dates356968-Node: register357869-Node: Custom register output365110-Node: balancesheet366295-Node: balancesheetequity371260-Node: cashflow376595-Node: incomestatement381408-Node: Advanced report commands386257-Node: balance386465-Node: balance features391886-Node: Simple balance report393989-Node: Balance report line format395799-Node: Filtered balance report398159-Node: List or tree mode398678-Node: Depth limiting400191-Node: Dropping top-level accounts400958-Node: Showing declared accounts401468-Node: Sorting by amount402198-Node: Percentages403052-Node: Multi-period balance report403759-Node: Balance change end balance406511-Node: Balance report modes408148-Node: Calculation mode408827-Node: Accumulation mode409531-Node: Valuation mode410632-Node: Combining balance report modes411976-Node: Budget report414006-Node: Using the budget report416306-Node: Budget date surprises418582-Node: Selecting budget goals419946-Node: Budgeting vs forecasting420894-Node: Balance report layout422571-Node: Wide layout423776-Node: Tall layout426181-Node: Bare layout427487-Node: Tidy layout429551-Node: Balance report output431095-Node: Some useful balance reports431869-Node: roi433129-Node: Spaces and special characters in --inv and --pnl435376-Node: Semantics of --inv and --pnl436102-Node: IRR and TWR explained438189-Node: Chart commands441600-Node: activity441781-Node: Data generation commands442278-Node: close442484-Node: close --clopen445047-Node: close --close447221-Node: close --open447745-Node: close --assert447995-Node: close --assign448322-Node: close --retain449001-Node: close customisation449858-Node: close and balance assertions451502-Node: close examples453024-Node: Retain earnings453261-Node: Migrate balances to a new file453764-Node: More detailed close examples455126-Node: rewrite455348-Node: Re-write rules in a file457908-Node: Diff output format459209-Node: rewrite vs print --auto460479-Node: Maintenance commands461193-Node: check461412-Node: Basic checks462494-Node: Strict checks463515-Node: Other checks464452-Node: Custom checks466204-Node: diff466659-Node: setup467867-Node: test470734-Node: PART 5 COMMON TASKS471637-Node: Getting help471870-Node: Constructing command lines472779-Node: Starting a journal file473624-Node: Setting LEDGER_FILE475008-Node: Setting opening balances476266-Node: Recording transactions479588-Node: Reconciling480313-Node: Reporting482702-Node: Migrating to a new file486816-Node: BUGS487265-Node: Troubleshooting487978+Node: Shell completions36037+Node: Output36526+Node: Output destination36717+Node: Output format37275+Node: Text output39061+Node: Box-drawing characters40040+Node: Colour40540+Node: Paging41126+Node: HTML output42645+Node: CSV / TSV output43063+Node: FODS output43317+Node: Beancount output44121+Node: Beancount account names45622+Node: Beancount commodity names46163+Node: Beancount virtual postings46810+Node: Beancount metadata47126+Node: Beancount costs47906+Node: Beancount operating currency48322+Node: SQL output48772+Node: JSON output49563+Node: Commodity styles50380+Node: Debug output51267+Node: Environment52099+Node: PART 2 DATA FORMATS52756+Node: Journal52899+Node: Journal cheatsheet55377+Node: Comments61628+Node: Transactions62572+Node: Dates63709+Node: Simple dates63861+Node: Posting dates64477+Node: Status65564+Node: Code67330+Node: Description67665+Node: Payee and note68352+Node: Transaction comments69443+Node: Postings69959+Node: Debits and credits71122+Node: The two space delimiter71732+Node: Account names72297+Node: Amounts74101+Node: Decimal marks75130+Node: Digit group marks76234+Node: Commodity76869+Node: Costs77986+Node: Balance assertions80238+Node: Assertions and ordering81486+Node: Assertions and multiple files82205+Node: Assertions and costs83373+Node: Assertions and commodities84020+Node: Assertions and subaccounts85679+Node: Assertions and status86339+Node: Assertions and virtual postings86759+Node: Assertions and auto postings87124+Node: Assertions and precision87999+Node: Assertions and hledger add88483+Node: Posting comments89231+Node: Transaction balancing89771+Node: Tags91979+Node: Querying with tags93273+Node: Displaying tags94072+Node: When to use tags ?94468+Node: Tag names95132+Node: Special tags95685+Node: Directives97250+Node: Directives and multiple files98707+Node: Directive effects99652+Node: account directive102808+Node: Account comments104258+Node: Account error checking104917+Node: Account display order106454+Node: Account types107652+Node: alias directive110927+Node: Basic aliases112138+Node: Regex aliases113013+Node: Combining aliases114060+Node: Aliases and multiple files115514+Node: end aliases directive116297+Node: Aliases can generate bad account names116665+Node: Aliases and account types117498+Node: commodity directive118390+Node: Commodity directive syntax119977+Node: Commodity error checking121626+Node: decimal-mark directive122101+Node: include directive122680+Node: P directive124898+Node: payee directive125932+Node: tag directive126554+Node: Periodic transactions127166+Node: Periodic rule syntax129320+Node: Periodic rules and relative dates130143+Node: Two spaces between period expression and description!130920+Node: Auto postings131881+Node: Auto postings and multiple files135167+Node: Auto postings and dates135572+Node: Auto postings and transaction balancing / inferred amounts / balance assertions136013+Node: Auto posting tags136859+Node: Auto postings on forecast transactions only137754+Node: Other syntax138224+Node: Balance assignments138996+Node: Balance assignments and costs140524+Node: Balance assignments and multiple files140946+Node: Bracketed posting dates141369+Node: D directive142067+Node: apply account directive143840+Node: Y directive144707+Node: Secondary dates145695+Node: Star comments147180+Node: Valuation expressions147872+Node: Virtual postings148171+Node: Other Ledger directives149795+Node: Other cost/lot notations150557+Node: CSV153398+Node: CSV rules cheatsheet155564+Node: source157663+Node: Data cleaning / generating commands159062+Node: archive160924+Node: encoding161852+Node: separator162895+Node: skip163548+Node: date-format164198+Node: timezone165143+Node: newest-first166269+Node: intra-day-reversed166982+Node: decimal-mark167584+Node: fields list168064+Node: Field assignment169872+Node: Field names171091+Node: date field172423+Node: date2 field172587+Node: status field172782+Node: code field172972+Node: description field173160+Node: comment field173377+Node: account field173934+Node: amount field174652+Node: currency field177491+Node: balance field177899+Node: if block178422+Node: Matchers179949+Node: Multiple matchers181939+Node: Match groups182747+Node: if table183640+Node: balance-type185703+Node: include186530+Node: Working with CSV187099+Node: Rapid feedback187651+Node: Valid CSV188234+Node: File Extension189110+Node: Reading CSV from standard input189845+Node: Reading multiple CSV files190231+Node: Reading files specified by rule190707+Node: Valid transactions192104+Node: Deduplicating importing192929+Node: Setting amounts194158+Node: Amount signs196685+Node: Setting currency/commodity197750+Node: Amount decimal places199126+Node: Referencing other fields200383+Node: How CSV rules are evaluated201491+Node: Well factored rules204208+Node: CSV rules examples204698+Node: Bank of Ireland204896+Node: Coinbase206493+Node: Amazon207676+Node: Paypal209518+Node: Timeclock217268+Node: Timedot221321+Node: Timedot examples224798+Node: PART 3 REPORTING CONCEPTS227075+Node: Time periods227239+Node: Report start & end date227512+Node: Smart dates228988+Node: Report intervals231111+Node: Date adjustments231685+Node: Start date adjustment231905+Node: End date adjustment232808+Node: Period headings233589+Node: Period expressions234522+Node: Period expressions with a report interval236427+Node: More complex report intervals236875+Node: Multiple weekday intervals238991+Node: Depth240002+Node: Queries241582+Node: Query types244254+Node: acct query244629+Node: amt query244940+Node: code query245637+Node: cur query245832+Node: desc query246438+Node: date query246621+Node: date2 query247017+Node: depth query247308+Node: note query247644+Node: payee query247910+Node: real query248191+Node: status query248396+Node: type query248636+Node: tag query249169+Node: Negative queries249798+Node: not query249980+Node: Space-separated queries250267+Node: Boolean queries250955+Node: expr query252273+Node: any query252953+Node: all query253406+Node: Queries and command options253988+Node: Queries and account aliases254436+Node: Queries and valuation254761+Node: Pivoting255123+Node: Generating data257399+Node: Forecasting259199+Node: --forecast259855+Node: Inspecting forecast transactions260956+Node: Forecast reports262289+Node: Forecast tags263398+Node: Forecast period in detail264018+Node: Forecast troubleshooting265106+Node: Budgeting266177+Node: Amount formatting266737+Node: Commodity display style266981+Node: Rounding268822+Node: Trailing decimal marks269427+Node: Amount parseability270360+Node: Cost reporting271969+Node: Recording costs272800+Node: Reporting at cost274527+Node: Equity conversion postings275292+Node: Inferring equity conversion postings277937+Node: Combining costs and equity conversion postings279079+Node: Requirements for detecting equity conversion postings280304+Node: Infer cost and equity by default ?281826+Node: Value reporting282263+Node: -V Value283199+Node: -X Value in specified commodity283526+Node: Valuation date283876+Node: Finding market price284709+Node: --infer-market-prices market prices from transactions286089+Node: Valuation commodity289133+Node: --value Flexible valuation290566+Node: Valuation examples292409+Node: Interaction of valuation and queries294553+Node: Effect of valuation on reports295270+Node: PART 4 COMMANDS303120+Node: Help commands305909+Node: commands306095+Node: demo306303+Node: help307396+Node: User interface commands309101+Node: repl309312+Node: Examples311576+Node: run312134+Node: Examples 2314549+Node: ui315573+Node: web315710+Node: Data entry commands315838+Node: add316099+Node: add and balance assertions318673+Node: add and balance assignments319397+Node: import319958+Node: Import dry run321037+Node: Overlap detection321985+Node: First import324871+Node: Importing balance assignments326066+Node: Import and commodity styles327121+Node: Import archiving327555+Node: Import special cases328380+Node: Deduplication328598+Node: Varying file name329089+Node: Multiple versions329473+Node: Basic report commands330580+Node: accounts330881+Node: codes333527+Node: commodities334549+Node: descriptions335306+Node: files335766+Node: notes336063+Node: payees336575+Node: prices337487+Node: stats338379+Node: tags340120+Node: Standard report commands341657+Node: print341962+Node: print explicitness344666+Node: print amount style345586+Node: print parseability346824+Node: print other features347743+Node: print output format348704+Node: aregister351989+Node: aregister and posting dates356553+Node: register357454+Node: Custom register output364694+Node: balancesheet365879+Node: balancesheetequity370844+Node: cashflow376179+Node: incomestatement380992+Node: Advanced report commands385841+Node: balance386049+Node: balance features391470+Node: Simple balance report393573+Node: Balance report line format395383+Node: Filtered balance report397743+Node: List or tree mode398262+Node: Depth limiting399775+Node: Dropping top-level accounts400542+Node: Showing declared accounts401052+Node: Sorting by amount401782+Node: Percentages402636+Node: Multi-period balance report403343+Node: Balance change end balance406095+Node: Balance report modes407732+Node: Calculation mode408411+Node: Accumulation mode409115+Node: Valuation mode410216+Node: Combining balance report modes411560+Node: Budget report413590+Node: Using the budget report415890+Node: Budget date surprises418166+Node: Selecting budget goals419530+Node: Budgeting vs forecasting420478+Node: Balance report layout422155+Node: Wide layout423360+Node: Tall layout425765+Node: Bare layout427071+Node: Tidy layout429135+Node: Balance report output430679+Node: Some useful balance reports431453+Node: roi432713+Node: Spaces and special characters in --inv and --pnl434960+Node: Semantics of --inv and --pnl435686+Node: IRR and TWR explained437773+Node: Chart commands441184+Node: activity441365+Node: Data generation commands441862+Node: close442068+Node: close --clopen444631+Node: close --close446805+Node: close --open447329+Node: close --assert447579+Node: close --assign447906+Node: close --retain448585+Node: close customisation449442+Node: close and balance assertions451086+Node: close examples452608+Node: Retain earnings452845+Node: Migrate balances to a new file453348+Node: More detailed close examples454710+Node: rewrite454932+Node: Re-write rules in a file457492+Node: Diff output format458793+Node: rewrite vs print --auto460063+Node: Maintenance commands460777+Node: check460996+Node: Basic checks462078+Node: Strict checks463099+Node: Other checks464036+Node: Custom checks465788+Node: diff466243+Node: setup467451+Node: test470318+Node: PART 5 COMMON TASKS471221+Node: Getting help471454+Node: Constructing command lines472363+Node: Starting a journal file473208+Node: Setting LEDGER_FILE474592+Node: Setting opening balances475850+Node: Recording transactions479172+Node: Reconciling479897+Node: Reporting482286+Node: Migrating to a new file486400+Node: BUGS486849+Node: Troubleshooting487679 End Tag Table
embeddedfiles/hledger.txt view
@@ -16,7 +16,7 @@ and largely compatible with ledger(1), and largely interconvertible with beancount(1). - This manual is for hledger's command line interface, version 1.50.1.+ This manual is for hledger's command line interface, version 1.50.2. It also describes the common options, file formats and concepts used by all hledger programs. It might accidentally teach you some bookkeep- ing/accounting as well! You don't need to know everything in here to@@ -646,7 +646,7 @@ # Options following a `[COMMAND]` heading are used with that hledger command only. [print]- --explicit --show-costs+ --explicit --infer-costs To use a config file, specify it with the --conf option. Its options will be inserted near the start of your command line, so you can over-@@ -5225,38 +5225,30 @@ With the --depth NUM option (short form: -NUM), reports will show ac- counts only to the specified depth, hiding deeper subaccounts. Use this when you want a summary with less detail. This flag has the same- effect as a depth: query argument: depth:2, --depth=2 or -2 are equiva-- lent.-- In place of a single number which limits the depth for all accounts,- you can also provide separate depth limits for different accounts using- regular expressions (since 1.41).-- For example, --depth assets=2 (or, equivalently: depth:assets=2) will- collapse accounts matching the regular expression assets to depth 2.- So assets:bank:savings would be collapsed to assets:bank, while liabil-- ities:bank:credit card would not be affected. This can be combined- with a flat depth to collapse other accounts not matching the regular- expression, so --depth assets=2 --depth 1 would collapse as-- sets:bank:savings to assets:bank and liabilities:bank:credit card to- liabilities.-- You can supply multiple depth arguments and they will all be applied,- so --depth assets=2 --depth liabilities=3 --depth 1 would collapse:+ effect as a depth: query argument. So all of these are equivalent:+ depth:2, --depth=2, -2. - o accounts matching assets to depth 2,+ In place of a single number which limits the depth for all accounts,+ you can also provide depth limits for specific accounts, by providing a+ REGEX=DEPTH argument instead of just a DEPTH (since 1.41). For exam-+ ple, --depth assets=2 (or depth:assets=2) will collapse accounts match-+ ing the regular expression "assets" to depth 2. So assets:bank:savings+ would be collapsed to assets:bank, but liabilities:bank:credit card+ would not be affected. - o accounts matching liabilities to depth 3,+ (If REGEX contains spaces or other special characters, enclose it in+ quotes in the usual way. Eg: --depth 'credit card=2') - o all other accounts to depth 1.+ Specific depth options and a general depth option can be combined. Eg+ --depth assets=3 --depth expenses=2 --depth 1 would collapse accounts+ containing "assets" to depth 3, accounts containing "expenses" to depth+ 2, and all other accounts to depth 1. - If an account is matched by more than one regular expression depth ar-- gument then the more specific one will be used. For example, if- --depth assets=1 --depth assets:bank:savings=2 is provided, then as-- sets:bank:savings will be collapsed to depth 2 rather than depth 1.- This is because assets:bank:savings matches at level 3 in the account- name, while assets matches at level 1. The same would be true with the- argument --depth assets=1 --depth savings=2.+ If an account is matched by more than one regular expression depth ar-+ gument, the most specific (deepest) match will be used. For example,+ with --depth assets=1 --depth savings=2, assets:bank:savings will be+ collapsed to depth 2, not depth 1 (because "savings" matches a deeper+ part of it than "assets" does). Queries Many hledger commands accept query arguments, which restrict their@@ -6489,10 +6481,9 @@ Effect of valuation on reports Here is a reference for how valuation is supposed to affect each part- of hledger's reports. (It's wide, you may need to scroll sideways.)- It may be useful when troubleshooting. If you find problems, please- report them, ideally with a reproducible example. Related: #329,- #1083.+ of hledger's reports. It may be useful when troubleshooting. If you+ find problems, please report them, ideally with a reproducible example.+ Related: #329, #1083. First, a quick glossary: @@ -7590,8 +7581,12 @@ Flags: -x --explicit show all amounts explicitly- --show-costs show transaction prices even with conversion- postings+ --invert display all amounts with reversed sign+ --location add tags showing file paths and line numbers+ -m --match=DESC fuzzy search for one recent transaction with+ description closest to DESC+ --new show only newer-dated transactions added in each+ file since last run --round=TYPE how much rounding or padding should be done when displaying amounts ? none - show original decimal digits,@@ -7602,15 +7597,9 @@ (can unbalance transactions) all - also round cost amounts to precision (can unbalance transactions)- --invert display all amounts with reversed sign- --new show only newer-dated transactions added in each- file since last run- -m --match=DESC fuzzy search for one recent transaction with- description closest to DESC --base-url=URLPREFIX in html output, generate links to hledger-web, with this prefix. (Usually the base url shown by hledger-web; can also be relative.)- --location add tags showing file paths and line numbers -O --output-format=FMT select the output format. Supported formats: txt, beancount, csv, tsv, html, fods, json, sql. -o --output-file=FILE write output to FILE. A file extension matching@@ -8018,7 +8007,7 @@ Often, you'll want to see just one line per interval. The --depth op- tion helps with this, causing subaccounts to be aggregated: - $ hledger register --monthly assets --depth 1h+ $ hledger register --monthly assets --depth 1 2008/01 assets $1 $1 2008/06 assets $-1 0 2008/12 assets $-1 $-1@@ -10626,45 +10615,48 @@ Some known issues and limitations: - A system locale with a suitable text encoding must be configured to- work with non-ascii data. (See Text encoding, Troubleshooting.)+ hledger uses the system's text encoding when reading non-ascii text.+ If no system encoding is configured, or if the data's encoding is dif-+ ferent, hledger will give an error. (See Text encoding, Troubleshoot-+ ing.) On Microsoft Windows, depending what kind of terminal window you use, non-ascii characters, ANSI text formatting, and/or the add command's- TAB key for completion, may not be supported.+ TAB key, may not be fully supported. (For best results, try a power-+ shell window.) When processing large data files, hledger uses more memory than Ledger. Troubleshooting- Here are some common issues you might encounter when you run hledger,- and how to resolve them (and remember also you can usually get quick+ Here are some common issues you might encounter when you run hledger,+ and how to resolve them (and remember also you can usually get quick Support): PATH issues: I get an error like "No command 'hledger' found" Depending how you installed hledger, the executables may not be in your- shell's PATH. Eg on unix systems, stack installs hledger in ~/.lo-+ shell's PATH. Eg on unix systems, stack installs hledger in ~/.lo- cal/bin and cabal installs it in ~/.cabal/bin. You may need to add one- of these directories to your shell's PATH, and/or open a new terminal+ of these directories to your shell's PATH, and/or open a new terminal window. - LEDGER_FILE issues: I configured LEDGER_FILE but hledger is not using+ LEDGER_FILE issues: I configured LEDGER_FILE but hledger is not using it- o LEDGER_FILE should be a real environment variable, not just a shell+ o LEDGER_FILE should be a real environment variable, not just a shell variable. Eg on unix, the command env | grep LEDGER_FILE should show- it. You may need to use export (see https://stackover-+ it. You may need to use export (see https://stackover- flow.com/a/7411509). On Windows, $env:LEDGER_FILE should show it. - o You may need to force your shell to see the new configuration. A+ o You may need to force your shell to see the new configuration. A simple way is to close your terminal window and open a new one. Text decoding issues: I get errors like "Illegal byte sequence" or "In-- valid or incomplete multibyte or wide character" or "commitAndRelease-+ valid or incomplete multibyte or wide character" or "commitAndRelease- Buffer: invalid argument (invalid character)"- hledger usually needs its input to be decodable with the system lo-+ hledger usually needs its input to be decodable with the system lo- cale's text encoding. See Text encoding and Install: Text encoding. COMPATIBILITY ISSUES: hledger gives an error with my Ledger file- Not all of Ledger's journal file syntax or feature set is supported.+ Not all of Ledger's journal file syntax or feature set is supported. See hledger and Ledger for full details. @@ -10685,4 +10677,4 @@ SEE ALSO hledger(1), hledger-ui(1), hledger-web(1), ledger(1) -hledger-1.50.1 September 2025 HLEDGER(1)+hledger-1.50.2 September 2025 HLEDGER(1)
hledger.cabal view
@@ -5,7 +5,7 @@ -- see: https://github.com/sol/hpack name: hledger-version: 1.50.1+version: 1.50.2 synopsis: Command-line interface for the hledger accounting system description: The command-line interface for the hledger accounting system. Its basic function is to read a plain text file describing@@ -154,7 +154,7 @@ autogen-modules: Paths_hledger ghc-options: -Wall -Wno-incomplete-uni-patterns -Wno-missing-signatures -Wno-orphans -Wno-type-defaults -Wno-unused-do-bind -optP-Wno-nonportable-include-path- cpp-options: -DVERSION="1.50.1"+ cpp-options: -DVERSION="1.50.2" build-depends: Decimal >=0.5.1 , Diff >=0.2@@ -171,7 +171,7 @@ , githash >=0.1.6.2 , hashable >=1.2.4 , haskeline >=0.6- , hledger-lib >=1.50.1 && <1.51+ , hledger-lib >=1.50.2 && <1.51 , http-client , http-types , lucid@@ -211,7 +211,7 @@ hs-source-dirs: app ghc-options: -Wall -Wno-incomplete-uni-patterns -Wno-missing-signatures -Wno-orphans -Wno-type-defaults -Wno-unused-do-bind -optP-Wno-nonportable-include-path -with-rtsopts=-T- cpp-options: -DVERSION="1.50.1"+ cpp-options: -DVERSION="1.50.2" build-depends: Decimal >=0.5.1 , aeson >=1 && <2.3@@ -227,7 +227,7 @@ , githash >=0.1.6.2 , haskeline >=0.6 , hledger- , hledger-lib >=1.50.1 && <1.51+ , hledger-lib >=1.50.2 && <1.51 , http-client , http-types , math-functions >=0.3.3.0@@ -264,7 +264,7 @@ hs-source-dirs: test ghc-options: -Wall -Wno-incomplete-uni-patterns -Wno-missing-signatures -Wno-orphans -Wno-type-defaults -Wno-unused-do-bind -optP-Wno-nonportable-include-path- cpp-options: -DVERSION="1.50.1"+ cpp-options: -DVERSION="1.50.2" build-depends: Decimal >=0.5.1 , aeson >=1 && <2.3@@ -280,7 +280,7 @@ , githash >=0.1.6.2 , haskeline >=0.6 , hledger- , hledger-lib >=1.50.1 && <1.51+ , hledger-lib >=1.50.2 && <1.51 , http-client , http-types , math-functions >=0.3.3.0@@ -331,7 +331,7 @@ , githash >=0.1.6.2 , haskeline >=0.6 , hledger- , hledger-lib >=1.50.1 && <1.51+ , hledger-lib >=1.50.2 && <1.51 , html , http-client , http-types