mirror of
https://github.com/simonmichael/hledger.git
synced 2024-11-08 07:09:28 +03:00
doc: update builtin manuals
This commit is contained in:
parent
22e751983b
commit
40699af34a
@ -146,8 +146,8 @@ show, and match with \-b/\-e/\-p/date:, secondary dates instead
|
||||
.RS
|
||||
.RE
|
||||
.TP
|
||||
.B \f[C]\-C\ \-\-cleared\f[]
|
||||
include only cleared postings/txns
|
||||
.B \f[C]\-U\ \-\-unmarked\f[]
|
||||
include only unmarked postings/txns (can combine with \-P or \-C)
|
||||
.RS
|
||||
.RE
|
||||
.TP
|
||||
@ -156,8 +156,8 @@ include only pending postings/txns
|
||||
.RS
|
||||
.RE
|
||||
.TP
|
||||
.B \f[C]\-U\ \-\-unmarked\f[]
|
||||
include only unmarked postings/txns
|
||||
.B \f[C]\-C\ \-\-cleared\f[]
|
||||
include only cleared postings/txns
|
||||
.RS
|
||||
.RE
|
||||
.TP
|
||||
@ -322,11 +322,13 @@ Period balances ignore transactions before the report start date, so
|
||||
they show the change in balance during the report period.
|
||||
They are more useful eg when viewing a time log.
|
||||
.PP
|
||||
\f[C]C\f[] toggles cleared mode, which shows balances for postings with
|
||||
cleared status only.
|
||||
Similarly, \f[C]P\f[] toggles pending mode, which shows balances for
|
||||
pending postings only, and \f[C]U\f[] toggles uncleared mode, which
|
||||
shows balances for unmarked postings only.
|
||||
\f[C]U\f[] toggles filtering by unmarked status, including or excluding
|
||||
unmarked postings in the balances.
|
||||
Similarly, \f[C]P\f[] toggles pending postings, and \f[C]C\f[] toggles
|
||||
cleared postings.
|
||||
(By default, balances include all postings; if you activate one or two
|
||||
status filters, only those postings are included; and if you activate
|
||||
all three, the filter is removed.)
|
||||
.PP
|
||||
\f[C]R\f[] toggles real mode, in which virtual postings are ignored.
|
||||
.PP
|
||||
@ -368,11 +370,13 @@ In other words, the register always shows the transactions responsible
|
||||
for the period balance shown on the accounts screen.
|
||||
As on the accounts screen, this can be toggled with \f[C]F\f[].
|
||||
.PP
|
||||
\f[C]C\f[] toggles cleared mode, which shows transactions with cleared
|
||||
status only.
|
||||
Similarly, \f[C]P\f[] toggles pending mode, which shows only pending
|
||||
transactions, and \f[C]U\f[] toggles uncleared mode, which shows only
|
||||
\f[C]U\f[] toggles filtering by unmarked status, showing or hiding
|
||||
unmarked transactions.
|
||||
Similarly, \f[C]P\f[] toggles pending transactions, and \f[C]C\f[]
|
||||
toggles cleared transactions.
|
||||
(By default, transactions with all statuses are shown; if you activate
|
||||
one or two status filters, only those transactions are shown; and if you
|
||||
activate all three, the filter is removed.)q
|
||||
.PP
|
||||
\f[C]R\f[] toggles real mode, in which virtual postings are ignored.
|
||||
.PP
|
||||
|
@ -104,15 +104,15 @@ the data.
|
||||
'--date2'
|
||||
|
||||
show, and match with -b/-e/-p/date:, secondary dates instead
|
||||
'-C --cleared'
|
||||
'-U --unmarked'
|
||||
|
||||
include only cleared postings/txns
|
||||
include only unmarked postings/txns (can combine with -P or -C)
|
||||
'-P --pending'
|
||||
|
||||
include only pending postings/txns
|
||||
'-U --unmarked'
|
||||
'-C --cleared'
|
||||
|
||||
include only unmarked postings/txns
|
||||
include only cleared postings/txns
|
||||
'-R --real'
|
||||
|
||||
include only non-virtual postings
|
||||
@ -260,10 +260,12 @@ disturbed by a filter query). Period balances ignore transactions
|
||||
before the report start date, so they show the change in balance during
|
||||
the report period. They are more useful eg when viewing a time log.
|
||||
|
||||
'C' toggles cleared mode, which shows balances for postings with
|
||||
cleared status only. Similarly, 'P' toggles pending mode, which shows
|
||||
balances for pending postings only, and 'U' toggles uncleared mode,
|
||||
which shows balances for unmarked postings only.
|
||||
'U' toggles filtering by unmarked status, including or excluding
|
||||
unmarked postings in the balances. Similarly, 'P' toggles pending
|
||||
postings, and 'C' toggles cleared postings. (By default, balances
|
||||
include all postings; if you activate one or two status filters, only
|
||||
those postings are included; and if you activate all three, the filter
|
||||
is removed.)
|
||||
|
||||
'R' toggles real mode, in which virtual postings are ignored.
|
||||
|
||||
@ -305,10 +307,12 @@ subaccounts. In other words, the register always shows the transactions
|
||||
responsible for the period balance shown on the accounts screen. As on
|
||||
the accounts screen, this can be toggled with 'F'.
|
||||
|
||||
'C' toggles cleared mode, which shows transactions with cleared
|
||||
status only. Similarly, 'P' toggles pending mode, which shows only
|
||||
pending transactions, and 'U' toggles uncleared mode, which shows only
|
||||
unmarked transactions.
|
||||
'U' toggles filtering by unmarked status, showing or hiding unmarked
|
||||
transactions. Similarly, 'P' toggles pending transactions, and 'C'
|
||||
toggles cleared transactions. (By default, transactions with all
|
||||
statuses are shown; if you activate one or two status filters, only
|
||||
those transactions are shown; and if you activate all three, the filter
|
||||
is removed.)q
|
||||
|
||||
'R' toggles real mode, in which virtual postings are ignored.
|
||||
|
||||
@ -359,17 +363,17 @@ Tag Table:
|
||||
Node: Top73
|
||||
Node: OPTIONS831
|
||||
Ref: #options930
|
||||
Node: KEYS3643
|
||||
Ref: #keys3740
|
||||
Node: SCREENS6329
|
||||
Ref: #screens6416
|
||||
Node: Accounts screen6506
|
||||
Ref: #accounts-screen6636
|
||||
Node: Register screen8766
|
||||
Ref: #register-screen8923
|
||||
Node: Transaction screen10866
|
||||
Ref: #transaction-screen11026
|
||||
Node: Error screen11896
|
||||
Ref: #error-screen12020
|
||||
Node: KEYS3671
|
||||
Ref: #keys3768
|
||||
Node: SCREENS6357
|
||||
Ref: #screens6444
|
||||
Node: Accounts screen6534
|
||||
Ref: #accounts-screen6664
|
||||
Node: Register screen8894
|
||||
Ref: #register-screen9051
|
||||
Node: Transaction screen11125
|
||||
Ref: #transaction-screen11285
|
||||
Node: Error screen12155
|
||||
Ref: #error-screen12279
|
||||
|
||||
End Tag Table
|
||||
|
@ -101,14 +101,14 @@ OPTIONS
|
||||
--date2
|
||||
show, and match with -b/-e/-p/date:, secondary dates instead
|
||||
|
||||
-C --cleared
|
||||
include only cleared postings/txns
|
||||
-U --unmarked
|
||||
include only unmarked postings/txns (can combine with -P or -C)
|
||||
|
||||
-P --pending
|
||||
include only pending postings/txns
|
||||
|
||||
-U --unmarked
|
||||
include only unmarked postings/txns
|
||||
-C --cleared
|
||||
include only cleared postings/txns
|
||||
|
||||
-R --real
|
||||
include only non-virtual postings
|
||||
@ -226,15 +226,16 @@ SCREENS
|
||||
before the report start date, so they show the change in balance during
|
||||
the report period. They are more useful eg when viewing a time log.
|
||||
|
||||
C toggles cleared mode, which shows balances for postings with cleared
|
||||
status only. Similarly, P toggles pending mode, which shows balances
|
||||
for pending postings only, and U toggles uncleared mode, which shows
|
||||
balances for unmarked postings only.
|
||||
U toggles filtering by unmarked status, including or excluding unmarked
|
||||
postings in the balances. Similarly, P toggles pending postings, and C
|
||||
toggles cleared postings. (By default, balances include all postings;
|
||||
if you activate one or two status filters, only those postings are
|
||||
included; and if you activate all three, the filter is removed.)
|
||||
|
||||
R toggles real mode, in which virtual postings are ignored.
|
||||
|
||||
Z toggles nonzero mode, in which only accounts with nonzero balances
|
||||
are shown (hledger-ui shows zero items by default, unlike command-line
|
||||
Z toggles nonzero mode, in which only accounts with nonzero balances
|
||||
are shown (hledger-ui shows zero items by default, unlike command-line
|
||||
hledger).
|
||||
|
||||
Press right or enter to view an account's transactions register.
|
||||
@ -243,63 +244,65 @@ SCREENS
|
||||
This screen shows the transactions affecting a particular account, like
|
||||
a check register. Each line represents one transaction and shows:
|
||||
|
||||
o the other account(s) involved, in abbreviated form. (If there are
|
||||
both real and virtual postings, it shows only the accounts affected
|
||||
o the other account(s) involved, in abbreviated form. (If there are
|
||||
both real and virtual postings, it shows only the accounts affected
|
||||
by real postings.)
|
||||
|
||||
o the overall change to the current account's balance; positive for an
|
||||
o the overall change to the current account's balance; positive for an
|
||||
inflow to this account, negative for an outflow.
|
||||
|
||||
o the running historical total or period total for the current account,
|
||||
after the transaction. This can be toggled with H. Similar to the
|
||||
accounts screen, the historical total is affected by transactions
|
||||
(filtered by the filter query) before the report start date, while
|
||||
after the transaction. This can be toggled with H. Similar to the
|
||||
accounts screen, the historical total is affected by transactions
|
||||
(filtered by the filter query) before the report start date, while
|
||||
the period total is not. If the historical total is not disturbed by
|
||||
a filter query, it will be the running historical balance you would
|
||||
a filter query, it will be the running historical balance you would
|
||||
see on a bank register for the current account.
|
||||
|
||||
If the accounts screen was in tree mode, the register screen will
|
||||
If the accounts screen was in tree mode, the register screen will
|
||||
include transactions from both the current account and its subaccounts.
|
||||
If the accounts screen was in flat mode, and a non-depth-clipped
|
||||
account was selected, the register screen will exclude transactions
|
||||
If the accounts screen was in flat mode, and a non-depth-clipped
|
||||
account was selected, the register screen will exclude transactions
|
||||
from subaccounts. In other words, the register always shows the trans-
|
||||
actions responsible for the period balance shown on the accounts
|
||||
actions responsible for the period balance shown on the accounts
|
||||
screen. As on the accounts screen, this can be toggled with F.
|
||||
|
||||
C toggles cleared mode, which shows transactions with cleared status
|
||||
only. Similarly, P toggles pending mode, which shows only pending
|
||||
transactions, and U toggles uncleared mode, which shows only unmarked
|
||||
transactions.
|
||||
U toggles filtering by unmarked status, showing or hiding unmarked
|
||||
transactions. Similarly, P toggles pending transactions, and C toggles
|
||||
cleared transactions. (By default, transactions with all statuses are
|
||||
shown; if you activate one or two status filters, only those transac-
|
||||
tions are shown; and if you activate all three, the filter is
|
||||
removed.)q
|
||||
|
||||
R toggles real mode, in which virtual postings are ignored.
|
||||
|
||||
Z toggles nonzero mode, in which only transactions posting a nonzero
|
||||
change are shown (hledger-ui shows zero items by default, unlike com-
|
||||
Z toggles nonzero mode, in which only transactions posting a nonzero
|
||||
change are shown (hledger-ui shows zero items by default, unlike com-
|
||||
mand-line hledger).
|
||||
|
||||
Press right (or enter) to view the selected transaction in detail.
|
||||
|
||||
Transaction screen
|
||||
This screen shows a single transaction, as a general journal entry,
|
||||
similar to hledger's print command and journal format (hledger_jour-
|
||||
This screen shows a single transaction, as a general journal entry,
|
||||
similar to hledger's print command and journal format (hledger_jour-
|
||||
nal(5)).
|
||||
|
||||
The transaction's date(s) and any cleared flag, transaction code,
|
||||
description, comments, along with all of its account postings are
|
||||
shown. Simple transactions have two postings, but there can be more
|
||||
The transaction's date(s) and any cleared flag, transaction code,
|
||||
description, comments, along with all of its account postings are
|
||||
shown. Simple transactions have two postings, but there can be more
|
||||
(or in certain cases, fewer).
|
||||
|
||||
up and down will step through all transactions listed in the previous
|
||||
account register screen. In the title bar, the numbers in parentheses
|
||||
show your position within that account register. They will vary
|
||||
up and down will step through all transactions listed in the previous
|
||||
account register screen. In the title bar, the numbers in parentheses
|
||||
show your position within that account register. They will vary
|
||||
depending on which account register you came from (remember most trans-
|
||||
actions appear in multiple account registers). The #N number preceding
|
||||
them is the transaction's position within the complete unfiltered jour-
|
||||
nal, which is a more stable id (at least until the next reload).
|
||||
|
||||
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
|
||||
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
|
||||
again to reload and resume normal operation. (Or, you can press escape
|
||||
to cancel the reload attempt.)
|
||||
|
||||
@ -307,17 +310,17 @@ ENVIRONMENT
|
||||
COLUMNS The screen width to use. Default: the full terminal width.
|
||||
|
||||
LEDGER_FILE The journal file path when not specified with -f. Default:
|
||||
~/.hledger.journal (on windows, perhaps C:/Users/USER/.hledger.jour-
|
||||
~/.hledger.journal (on windows, perhaps C:/Users/USER/.hledger.jour-
|
||||
nal).
|
||||
|
||||
FILES
|
||||
Reads data from one or more files in hledger journal, timeclock, time-
|
||||
dot, or CSV format specified with -f, or $LEDGER_FILE, or
|
||||
$HOME/.hledger.journal (on windows, perhaps
|
||||
Reads data from one or more files in hledger journal, timeclock, time-
|
||||
dot, or CSV format specified with -f, or $LEDGER_FILE, or
|
||||
$HOME/.hledger.journal (on windows, perhaps
|
||||
C:/Users/USER/.hledger.journal).
|
||||
|
||||
BUGS
|
||||
The need to precede options with -- when invoked from hledger is awk-
|
||||
The need to precede options with -- when invoked from hledger is awk-
|
||||
ward.
|
||||
|
||||
-f- doesn't work (hledger-ui can't read from stdin).
|
||||
@ -325,13 +328,13 @@ BUGS
|
||||
-V affects only the accounts screen.
|
||||
|
||||
When you press g, the current and all previous screens are regenerated,
|
||||
which may cause a noticeable pause with large files. Also there is no
|
||||
which may cause a noticeable pause with large files. Also there is no
|
||||
visual indication that this is in progress.
|
||||
|
||||
--watch is not yet fully robust. It works well for normal usage, but
|
||||
many file changes in a short time (eg saving the file thousands of
|
||||
times with an editor macro) can cause problems at least on OSX. Symp-
|
||||
toms include: unresponsive UI, periodic resetting of the cursor posi-
|
||||
--watch is not yet fully robust. It works well for normal usage, but
|
||||
many file changes in a short time (eg saving the file thousands of
|
||||
times with an editor macro) can cause problems at least on OSX. Symp-
|
||||
toms include: unresponsive UI, periodic resetting of the cursor posi-
|
||||
tion, momentary display of parse errors, high CPU usage eventually sub-
|
||||
siding, and possibly a small but persistent build-up of CPU usage until
|
||||
the program is restarted.
|
||||
@ -339,7 +342,7 @@ BUGS
|
||||
|
||||
|
||||
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)
|
||||
|
||||
|
||||
@ -353,7 +356,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)
|
||||
|
||||
|
@ -202,8 +202,8 @@ show, and match with \-b/\-e/\-p/date:, secondary dates instead
|
||||
.RS
|
||||
.RE
|
||||
.TP
|
||||
.B \f[C]\-C\ \-\-cleared\f[]
|
||||
include only cleared postings/txns
|
||||
.B \f[C]\-U\ \-\-unmarked\f[]
|
||||
include only unmarked postings/txns (can combine with \-P or \-C)
|
||||
.RS
|
||||
.RE
|
||||
.TP
|
||||
@ -212,8 +212,8 @@ include only pending postings/txns
|
||||
.RS
|
||||
.RE
|
||||
.TP
|
||||
.B \f[C]\-U\ \-\-unmarked\f[]
|
||||
include only unmarked postings/txns
|
||||
.B \f[C]\-C\ \-\-cleared\f[]
|
||||
include only cleared postings/txns
|
||||
.RS
|
||||
.RE
|
||||
.TP
|
||||
|
@ -149,15 +149,15 @@ options as shown above.
|
||||
'--date2'
|
||||
|
||||
show, and match with -b/-e/-p/date:, secondary dates instead
|
||||
'-C --cleared'
|
||||
'-U --unmarked'
|
||||
|
||||
include only cleared postings/txns
|
||||
include only unmarked postings/txns (can combine with -P or -C)
|
||||
'-P --pending'
|
||||
|
||||
include only pending postings/txns
|
||||
'-U --unmarked'
|
||||
'-C --cleared'
|
||||
|
||||
include only unmarked postings/txns
|
||||
include only cleared postings/txns
|
||||
'-R --real'
|
||||
|
||||
include only non-virtual postings
|
||||
|
@ -146,14 +146,14 @@ OPTIONS
|
||||
--date2
|
||||
show, and match with -b/-e/-p/date:, secondary dates instead
|
||||
|
||||
-C --cleared
|
||||
include only cleared postings/txns
|
||||
-U --unmarked
|
||||
include only unmarked postings/txns (can combine with -P or -C)
|
||||
|
||||
-P --pending
|
||||
include only pending postings/txns
|
||||
|
||||
-U --unmarked
|
||||
include only unmarked postings/txns
|
||||
-C --cleared
|
||||
include only cleared postings/txns
|
||||
|
||||
-R --real
|
||||
include only non-virtual postings
|
||||
|
@ -273,8 +273,8 @@ show, and match with \-b/\-e/\-p/date:, secondary dates instead
|
||||
.RS
|
||||
.RE
|
||||
.TP
|
||||
.B \f[C]\-C\ \-\-cleared\f[]
|
||||
include only cleared postings/txns
|
||||
.B \f[C]\-U\ \-\-unmarked\f[]
|
||||
include only unmarked postings/txns (can combine with \-P or \-C)
|
||||
.RS
|
||||
.RE
|
||||
.TP
|
||||
@ -283,8 +283,8 @@ include only pending postings/txns
|
||||
.RS
|
||||
.RE
|
||||
.TP
|
||||
.B \f[C]\-U\ \-\-unmarked\f[]
|
||||
include only unmarked postings/txns
|
||||
.B \f[C]\-C\ \-\-cleared\f[]
|
||||
include only cleared postings/txns
|
||||
.RS
|
||||
.RE
|
||||
.TP
|
||||
@ -1052,8 +1052,8 @@ match real or virtual postings respectively
|
||||
.RS
|
||||
.RE
|
||||
.TP
|
||||
.B \f[B]\f[C]status:*,\ status:!,\ status:\f[]\f[]
|
||||
match cleared, pending, or uncleared/pending transactions respectively
|
||||
.B \f[B]\f[C]status:,\ status:!,\ status:*\f[]\f[]
|
||||
match unmarked, pending, or cleared transactions respectively
|
||||
.RS
|
||||
.RE
|
||||
.TP
|
||||
|
@ -214,15 +214,15 @@ different, like git.)
|
||||
'--date2'
|
||||
|
||||
show, and match with -b/-e/-p/date:, secondary dates instead
|
||||
'-C --cleared'
|
||||
'-U --unmarked'
|
||||
|
||||
include only cleared postings/txns
|
||||
include only unmarked postings/txns (can combine with -P or -C)
|
||||
'-P --pending'
|
||||
|
||||
include only pending postings/txns
|
||||
'-U --unmarked'
|
||||
'-C --cleared'
|
||||
|
||||
include only unmarked postings/txns
|
||||
include only cleared postings/txns
|
||||
'-R --real'
|
||||
|
||||
include only non-virtual postings
|
||||
@ -744,10 +744,9 @@ match (or negatively match)
|
||||
*'real:, real:0'*
|
||||
|
||||
match real or virtual postings respectively
|
||||
*'status:*, status:!, status:'*
|
||||
*'status:, status:!, status:*'*
|
||||
|
||||
match cleared, pending, or uncleared/pending transactions
|
||||
respectively
|
||||
match unmarked, pending, or cleared transactions respectively
|
||||
*'tag:REGEX[=REGEX]'*
|
||||
|
||||
match by tag name, and optionally also by tag value. Note a tag:
|
||||
@ -2120,123 +2119,123 @@ Node: OPTIONS3640
|
||||
Ref: #options3744
|
||||
Node: General options4025
|
||||
Ref: #general-options4152
|
||||
Node: Command options6662
|
||||
Ref: #command-options6815
|
||||
Node: Command arguments7213
|
||||
Ref: #command-arguments7373
|
||||
Node: Special characters7494
|
||||
Ref: #special-characters7652
|
||||
Node: Input files8820
|
||||
Ref: #input-files8958
|
||||
Node: Smart dates10921
|
||||
Ref: #smart-dates11064
|
||||
Node: Report start & end date12043
|
||||
Ref: #report-start-end-date12215
|
||||
Node: Report intervals13281
|
||||
Ref: #report-intervals13446
|
||||
Node: Period expressions13847
|
||||
Ref: #period-expressions14007
|
||||
Node: Depth limiting16347
|
||||
Ref: #depth-limiting16493
|
||||
Node: Pivoting16694
|
||||
Ref: #pivoting16814
|
||||
Node: Cost18585
|
||||
Ref: #cost18695
|
||||
Node: Market value18813
|
||||
Ref: #market-value18950
|
||||
Node: Regular expressions20250
|
||||
Ref: #regular-expressions20388
|
||||
Node: QUERIES21749
|
||||
Ref: #queries21853
|
||||
Node: COMMANDS25532
|
||||
Ref: #commands25646
|
||||
Node: accounts26319
|
||||
Ref: #accounts26419
|
||||
Node: activity27401
|
||||
Ref: #activity27513
|
||||
Node: add27872
|
||||
Ref: #add27973
|
||||
Node: balance30631
|
||||
Ref: #balance30744
|
||||
Node: Flat mode33759
|
||||
Ref: #flat-mode33886
|
||||
Node: Depth limited balance reports34306
|
||||
Ref: #depth-limited-balance-reports34509
|
||||
Node: Multicolumn balance reports34929
|
||||
Ref: #multicolumn-balance-reports35140
|
||||
Node: Custom balance output39788
|
||||
Ref: #custom-balance-output39972
|
||||
Node: Colour support42065
|
||||
Ref: #colour-support42226
|
||||
Node: Output destination42399
|
||||
Ref: #output-destination42557
|
||||
Node: CSV output42827
|
||||
Ref: #csv-output42946
|
||||
Node: balancesheet43343
|
||||
Ref: #balancesheet43471
|
||||
Node: cashflow45378
|
||||
Ref: #cashflow45495
|
||||
Node: help47363
|
||||
Ref: #help47475
|
||||
Node: incomestatement48313
|
||||
Ref: #incomestatement48443
|
||||
Node: info50335
|
||||
Ref: #info50442
|
||||
Node: man50806
|
||||
Ref: #man50903
|
||||
Node: print51308
|
||||
Ref: #print51413
|
||||
Node: register55169
|
||||
Ref: #register55282
|
||||
Node: Custom register output59778
|
||||
Ref: #custom-register-output59909
|
||||
Node: stats61206
|
||||
Ref: #stats61312
|
||||
Node: test62193
|
||||
Ref: #test62280
|
||||
Node: ADD-ON COMMANDS62648
|
||||
Ref: #add-on-commands62760
|
||||
Node: Official add-ons64047
|
||||
Ref: #official-add-ons64189
|
||||
Node: api64276
|
||||
Ref: #api64367
|
||||
Node: ui64419
|
||||
Ref: #ui64520
|
||||
Node: web64578
|
||||
Ref: #web64669
|
||||
Node: Third party add-ons64715
|
||||
Ref: #third-party-add-ons64892
|
||||
Node: diff65027
|
||||
Ref: #diff65126
|
||||
Node: iadd65225
|
||||
Ref: #iadd65341
|
||||
Node: interest65424
|
||||
Ref: #interest65547
|
||||
Node: irr65642
|
||||
Ref: #irr65742
|
||||
Node: Experimental add-ons65820
|
||||
Ref: #experimental-add-ons65974
|
||||
Node: autosync66367
|
||||
Ref: #autosync66481
|
||||
Node: budget66720
|
||||
Ref: #budget66844
|
||||
Node: chart66910
|
||||
Ref: #chart67029
|
||||
Node: check67100
|
||||
Ref: #check67224
|
||||
Node: check-dates67291
|
||||
Ref: #check-dates67433
|
||||
Node: check-dupes67506
|
||||
Ref: #check-dupes67649
|
||||
Node: equity67726
|
||||
Ref: #equity67854
|
||||
Node: prices67973
|
||||
Ref: #prices68102
|
||||
Node: print-unique68157
|
||||
Ref: #print-unique68306
|
||||
Node: register-match68399
|
||||
Ref: #register-match68555
|
||||
Node: rewrite68653
|
||||
Ref: #rewrite68774
|
||||
Node: Command options6690
|
||||
Ref: #command-options6843
|
||||
Node: Command arguments7241
|
||||
Ref: #command-arguments7401
|
||||
Node: Special characters7522
|
||||
Ref: #special-characters7680
|
||||
Node: Input files8848
|
||||
Ref: #input-files8986
|
||||
Node: Smart dates10949
|
||||
Ref: #smart-dates11092
|
||||
Node: Report start & end date12071
|
||||
Ref: #report-start-end-date12243
|
||||
Node: Report intervals13309
|
||||
Ref: #report-intervals13474
|
||||
Node: Period expressions13875
|
||||
Ref: #period-expressions14035
|
||||
Node: Depth limiting16375
|
||||
Ref: #depth-limiting16521
|
||||
Node: Pivoting16722
|
||||
Ref: #pivoting16842
|
||||
Node: Cost18613
|
||||
Ref: #cost18723
|
||||
Node: Market value18841
|
||||
Ref: #market-value18978
|
||||
Node: Regular expressions20278
|
||||
Ref: #regular-expressions20416
|
||||
Node: QUERIES21777
|
||||
Ref: #queries21881
|
||||
Node: COMMANDS25546
|
||||
Ref: #commands25660
|
||||
Node: accounts26333
|
||||
Ref: #accounts26433
|
||||
Node: activity27415
|
||||
Ref: #activity27527
|
||||
Node: add27886
|
||||
Ref: #add27987
|
||||
Node: balance30645
|
||||
Ref: #balance30758
|
||||
Node: Flat mode33773
|
||||
Ref: #flat-mode33900
|
||||
Node: Depth limited balance reports34320
|
||||
Ref: #depth-limited-balance-reports34523
|
||||
Node: Multicolumn balance reports34943
|
||||
Ref: #multicolumn-balance-reports35154
|
||||
Node: Custom balance output39802
|
||||
Ref: #custom-balance-output39986
|
||||
Node: Colour support42079
|
||||
Ref: #colour-support42240
|
||||
Node: Output destination42413
|
||||
Ref: #output-destination42571
|
||||
Node: CSV output42841
|
||||
Ref: #csv-output42960
|
||||
Node: balancesheet43357
|
||||
Ref: #balancesheet43485
|
||||
Node: cashflow45392
|
||||
Ref: #cashflow45509
|
||||
Node: help47377
|
||||
Ref: #help47489
|
||||
Node: incomestatement48327
|
||||
Ref: #incomestatement48457
|
||||
Node: info50349
|
||||
Ref: #info50456
|
||||
Node: man50820
|
||||
Ref: #man50917
|
||||
Node: print51322
|
||||
Ref: #print51427
|
||||
Node: register55183
|
||||
Ref: #register55296
|
||||
Node: Custom register output59792
|
||||
Ref: #custom-register-output59923
|
||||
Node: stats61220
|
||||
Ref: #stats61326
|
||||
Node: test62207
|
||||
Ref: #test62294
|
||||
Node: ADD-ON COMMANDS62662
|
||||
Ref: #add-on-commands62774
|
||||
Node: Official add-ons64061
|
||||
Ref: #official-add-ons64203
|
||||
Node: api64290
|
||||
Ref: #api64381
|
||||
Node: ui64433
|
||||
Ref: #ui64534
|
||||
Node: web64592
|
||||
Ref: #web64683
|
||||
Node: Third party add-ons64729
|
||||
Ref: #third-party-add-ons64906
|
||||
Node: diff65041
|
||||
Ref: #diff65140
|
||||
Node: iadd65239
|
||||
Ref: #iadd65355
|
||||
Node: interest65438
|
||||
Ref: #interest65561
|
||||
Node: irr65656
|
||||
Ref: #irr65756
|
||||
Node: Experimental add-ons65834
|
||||
Ref: #experimental-add-ons65988
|
||||
Node: autosync66381
|
||||
Ref: #autosync66495
|
||||
Node: budget66734
|
||||
Ref: #budget66858
|
||||
Node: chart66924
|
||||
Ref: #chart67043
|
||||
Node: check67114
|
||||
Ref: #check67238
|
||||
Node: check-dates67305
|
||||
Ref: #check-dates67447
|
||||
Node: check-dupes67520
|
||||
Ref: #check-dupes67663
|
||||
Node: equity67740
|
||||
Ref: #equity67868
|
||||
Node: prices67987
|
||||
Ref: #prices68116
|
||||
Node: print-unique68171
|
||||
Ref: #print-unique68320
|
||||
Node: register-match68413
|
||||
Ref: #register-match68569
|
||||
Node: rewrite68667
|
||||
Ref: #rewrite68788
|
||||
|
||||
End Tag Table
|
||||
|
@ -182,14 +182,14 @@ OPTIONS
|
||||
--date2
|
||||
show, and match with -b/-e/-p/date:, secondary dates instead
|
||||
|
||||
-C --cleared
|
||||
include only cleared postings/txns
|
||||
-U --unmarked
|
||||
include only unmarked postings/txns (can combine with -P or -C)
|
||||
|
||||
-P --pending
|
||||
include only pending postings/txns
|
||||
|
||||
-U --unmarked
|
||||
include only unmarked postings/txns
|
||||
-C --cleared
|
||||
include only cleared postings/txns
|
||||
|
||||
-R --real
|
||||
include only non-virtual postings
|
||||
@ -684,14 +684,13 @@ QUERIES
|
||||
real:, real:0
|
||||
match real or virtual postings respectively
|
||||
|
||||
status:*, status:!, status:
|
||||
match cleared, pending, or uncleared/pending transactions
|
||||
respectively
|
||||
status:, status:!, status:*
|
||||
match unmarked, pending, or cleared transactions respectively
|
||||
|
||||
tag:REGEX[=REGEX]
|
||||
match by tag name, and optionally also by tag value. Note a
|
||||
tag: query is considered to match a transaction if it matches
|
||||
any of the postings. Also remember that postings inherit the
|
||||
match by tag name, and optionally also by tag value. Note a
|
||||
tag: query is considered to match a transaction if it matches
|
||||
any of the postings. Also remember that postings inherit the
|
||||
tags of their parent transaction.
|
||||
|
||||
not: before any of the above negates the match.
|
||||
@ -699,24 +698,24 @@ QUERIES
|
||||
inacct:ACCTNAME
|
||||
a special term used automatically when you click an account name
|
||||
in hledger-web, specifying the account register we are currently
|
||||
in (selects the transactions of that account and how to show
|
||||
them, can be filtered further with acct etc). Not supported
|
||||
in (selects the transactions of that account and how to show
|
||||
them, can be filtered further with acct etc). Not supported
|
||||
elsewhere in hledger.
|
||||
|
||||
Some of these can also be expressed as command-line options (eg depth:2
|
||||
is equivalent to --depth 2). Generally you can mix options and query
|
||||
arguments, and the resulting query will be their intersection (perhaps
|
||||
is equivalent to --depth 2). Generally you can mix options and query
|
||||
arguments, and the resulting query will be their intersection (perhaps
|
||||
excluding the -p/--period option).
|
||||
|
||||
COMMANDS
|
||||
hledger provides a number of subcommands; hledger with no arguments
|
||||
hledger provides a number of subcommands; hledger with no arguments
|
||||
shows a list.
|
||||
|
||||
If you install additional hledger-* packages, or if you put programs or
|
||||
scripts named hledger-NAME in your PATH, these will also be listed as
|
||||
scripts named hledger-NAME in your PATH, these will also be listed as
|
||||
subcommands.
|
||||
|
||||
Run a subcommand by writing its name as first argument (eg
|
||||
Run a subcommand by writing its name as first argument (eg
|
||||
hledger incomestatement). You can also write any unambiguous prefix of
|
||||
a command name (hledger inc), or one of the standard short aliases dis-
|
||||
played in the command list (hledger is).
|
||||
@ -731,14 +730,14 @@ COMMANDS
|
||||
--drop=N
|
||||
in flat mode: omit N leading account name parts
|
||||
|
||||
This command lists all account names that are in use (ie, all the
|
||||
accounts which have at least one transaction posting to them). With
|
||||
This command lists all account names that are in use (ie, all the
|
||||
accounts which have at least one transaction posting to them). With
|
||||
query arguments, only matched account names are shown.
|
||||
|
||||
It shows a flat list by default. With --tree, it uses indentation to
|
||||
It shows a flat list by default. With --tree, it uses indentation to
|
||||
show the account hierarchy.
|
||||
|
||||
In flat mode you can add --drop N to omit the first few account name
|
||||
In flat mode you can add --drop N to omit the first few account name
|
||||
components.
|
||||
|
||||
Examples:
|
||||
@ -781,8 +780,8 @@ COMMANDS
|
||||
activity
|
||||
Show an ascii barchart of posting counts per interval.
|
||||
|
||||
The activity command displays an ascii histogram showing transaction
|
||||
counts by day, week, month or other reporting interval (by day is the
|
||||
The activity command displays an ascii histogram showing transaction
|
||||
counts by day, week, month or other reporting interval (by day is the
|
||||
default). With query arguments, it counts only matched transactions.
|
||||
|
||||
$ hledger activity --quarterly
|
||||
@ -795,24 +794,24 @@ COMMANDS
|
||||
Prompt for transactions and add them to the journal.
|
||||
|
||||
--no-new-accounts
|
||||
don't allow creating new accounts; helps prevent typos when
|
||||
don't allow creating new accounts; helps prevent typos when
|
||||
entering account names
|
||||
|
||||
Many hledger users edit their journals directly with a text editor, or
|
||||
generate them from CSV. For more interactive data entry, there is the
|
||||
add command, which prompts interactively on the console for new trans-
|
||||
actions, and appends them to the journal file (if there are multiple
|
||||
Many hledger users edit their journals directly with a text editor, or
|
||||
generate them from CSV. For more interactive data entry, there is the
|
||||
add command, which prompts interactively on the console for new trans-
|
||||
actions, and appends them to the journal file (if there are multiple
|
||||
-f FILE options, the first file is used.) Existing transactions are not
|
||||
changed. This is the only hledger command that writes to the journal
|
||||
changed. This is the only hledger command that writes to the journal
|
||||
file.
|
||||
|
||||
To use it, just run hledger add and follow the prompts. You can add as
|
||||
many transactions as you like; when you are finished, enter . or press
|
||||
many transactions as you like; when you are finished, enter . or press
|
||||
control-d or control-c to exit.
|
||||
|
||||
Features:
|
||||
|
||||
o add tries to provide useful defaults, using the most similar recent
|
||||
o add tries to provide useful defaults, using the most similar recent
|
||||
transaction (by description) as a template.
|
||||
|
||||
o You can also set the initial defaults with command line arguments.
|
||||
@ -820,20 +819,20 @@ COMMANDS
|
||||
o Readline-style edit keys can be used during data entry.
|
||||
|
||||
o The tab key will auto-complete whenever possible - accounts, descrip-
|
||||
tions, dates (yesterday, today, tomorrow). If the input area is
|
||||
tions, dates (yesterday, today, tomorrow). If the input area is
|
||||
empty, it will insert the default value.
|
||||
|
||||
o If the journal defines a default commodity, it will be added to any
|
||||
o If the journal defines a default commodity, it will be added to any
|
||||
bare numbers entered.
|
||||
|
||||
o A parenthesised transaction code may be entered following a date.
|
||||
|
||||
o Comments and tags may be entered following a description or amount.
|
||||
|
||||
o If you make a mistake, enter < at any prompt to restart the transac-
|
||||
o If you make a mistake, enter < at any prompt to restart the transac-
|
||||
tion.
|
||||
|
||||
o Input prompts are displayed in a different colour when the terminal
|
||||
o Input prompts are displayed in a different colour when the terminal
|
||||
supports it.
|
||||
|
||||
Example (see the tutorial for a detailed explanation):
|
||||
@ -870,7 +869,7 @@ COMMANDS
|
||||
show balance change in each period (default)
|
||||
|
||||
--cumulative
|
||||
show balance change accumulated across periods (in multicolumn
|
||||
show balance change accumulated across periods (in multicolumn
|
||||
reports)
|
||||
|
||||
-H --historical
|
||||
@ -905,13 +904,13 @@ COMMANDS
|
||||
select the output format. Supported formats: txt, csv.
|
||||
|
||||
-o FILE --output-file=FILE
|
||||
write output to FILE. A file extension matching one of the
|
||||
write output to FILE. A file extension matching one of the
|
||||
above formats selects that format.
|
||||
|
||||
--pretty-tables
|
||||
Use unicode to display prettier tables.
|
||||
|
||||
The balance command displays accounts and balances. It is hledger's
|
||||
The balance command displays accounts and balances. It is hledger's
|
||||
most featureful and versatile command.
|
||||
|
||||
$ hledger balance
|
||||
@ -928,25 +927,25 @@ COMMANDS
|
||||
--------------------
|
||||
0
|
||||
|
||||
More precisely, the balance command shows the change to each account's
|
||||
More precisely, the balance command shows the change to each account's
|
||||
balance caused by all (matched) postings. In the common case where you
|
||||
do not filter by date and your journal sets the correct opening bal-
|
||||
do not filter by date and your journal sets the correct opening bal-
|
||||
ances, this is the same as the account's ending balance.
|
||||
|
||||
By default, accounts are displayed hierarchically, with subaccounts
|
||||
By default, accounts are displayed hierarchically, with subaccounts
|
||||
indented below their parent. "Boring" accounts, which contain a single
|
||||
interesting subaccount and no balance of their own, are elided into the
|
||||
following line for more compact output. (Use --no-elide to prevent
|
||||
this. Eliding of boring accounts is not yet supported in multicolumn
|
||||
following line for more compact output. (Use --no-elide to prevent
|
||||
this. Eliding of boring accounts is not yet supported in multicolumn
|
||||
reports.)
|
||||
|
||||
Each account's balance is the "inclusive" balance - it includes the
|
||||
Each account's balance is the "inclusive" balance - it includes the
|
||||
balances of any subaccounts.
|
||||
|
||||
Accounts which have zero balance (and no non-zero subaccounts) are
|
||||
Accounts which have zero balance (and no non-zero subaccounts) are
|
||||
omitted. Use -E/--empty to show them.
|
||||
|
||||
A final total is displayed by default; use -N/--no-total to suppress
|
||||
A final total is displayed by default; use -N/--no-total to suppress
|
||||
it:
|
||||
|
||||
$ hledger balance -p 2008/6 expenses --no-total
|
||||
@ -956,9 +955,9 @@ COMMANDS
|
||||
|
||||
Flat mode
|
||||
To see a flat list of full account names instead of the default hierar-
|
||||
chical display, use --flat. In this mode, accounts (unless
|
||||
chical display, use --flat. In this mode, accounts (unless
|
||||
depth-clipped) show their "exclusive" balance, excluding any subaccount
|
||||
balances. In this mode, you can also use --drop N to omit the first
|
||||
balances. In this mode, you can also use --drop N to omit the first
|
||||
few account name components.
|
||||
|
||||
$ hledger balance -p 2008/6 expenses -N --flat --drop 1
|
||||
@ -966,9 +965,9 @@ COMMANDS
|
||||
$1 supplies
|
||||
|
||||
Depth limited balance reports
|
||||
With --depth N, balance shows accounts only to the specified depth.
|
||||
This is very useful to show a complex charts of accounts in less
|
||||
detail. In flat mode, balances from accounts below the depth limit
|
||||
With --depth N, balance shows accounts only to the specified depth.
|
||||
This is very useful to show a complex charts of accounts in less
|
||||
detail. In flat mode, balances from accounts below the depth limit
|
||||
will be shown as part of a parent account at the depth limit.
|
||||
|
||||
$ hledger balance -N --depth 1
|
||||
@ -978,12 +977,12 @@ COMMANDS
|
||||
$1 liabilities
|
||||
|
||||
Multicolumn balance reports
|
||||
With a reporting interval, multiple balance columns will be shown, one
|
||||
for each report period. There are three types of multi-column balance
|
||||
With a reporting interval, multiple balance columns will be shown, one
|
||||
for each report period. There are three types of multi-column balance
|
||||
report, showing different information:
|
||||
|
||||
1. By default: each column shows the sum of postings in that period, ie
|
||||
the account's change of balance in that period. This is useful eg
|
||||
the account's change of balance in that period. This is useful eg
|
||||
for a monthly income statement:
|
||||
|
||||
$ hledger balance --quarterly income expenses -E
|
||||
@ -998,8 +997,8 @@ COMMANDS
|
||||
-------------------++---------------------------------
|
||||
|| $-1 $1 0 0
|
||||
|
||||
2. With --cumulative: each column shows the ending balance for that
|
||||
period, accumulating the changes across periods, starting from 0 at
|
||||
2. With --cumulative: each column shows the ending balance for that
|
||||
period, accumulating the changes across periods, starting from 0 at
|
||||
the report start date:
|
||||
|
||||
$ hledger balance --quarterly income expenses -E --cumulative
|
||||
@ -1015,8 +1014,8 @@ COMMANDS
|
||||
|| $-1 0 0 0
|
||||
|
||||
3. With --historical/-H: each column shows the actual historical ending
|
||||
balance for that period, accumulating the changes across periods,
|
||||
starting from the actual balance at the report start date. This is
|
||||
balance for that period, accumulating the changes across periods,
|
||||
starting from the actual balance at the report start date. This is
|
||||
useful eg for a multi-period balance sheet, and when you are showing
|
||||
only the data after a certain start date:
|
||||
|
||||
@ -1032,26 +1031,26 @@ COMMANDS
|
||||
----------------------++-------------------------------------
|
||||
|| 0 0 0
|
||||
|
||||
Multi-column balance reports display accounts in flat mode by default;
|
||||
Multi-column balance reports display accounts in flat mode by default;
|
||||
to see the hierarchy, use --tree.
|
||||
|
||||
With a reporting interval (like --quarterly above), the report
|
||||
start/end dates will be adjusted if necessary so that they encompass
|
||||
With a reporting interval (like --quarterly above), the report
|
||||
start/end dates will be adjusted if necessary so that they encompass
|
||||
the displayed report periods. This is so that the first and last peri-
|
||||
ods will be "full" and comparable to the others.
|
||||
|
||||
The -E/--empty flag does two things in multicolumn balance reports:
|
||||
first, the report will show all columns within the specified report
|
||||
period (without -E, leading and trailing columns with all zeroes are
|
||||
not shown). Second, all accounts which existed at the report start
|
||||
date will be considered, not just the ones with activity during the
|
||||
The -E/--empty flag does two things in multicolumn balance reports:
|
||||
first, the report will show all columns within the specified report
|
||||
period (without -E, leading and trailing columns with all zeroes are
|
||||
not shown). Second, all accounts which existed at the report start
|
||||
date will be considered, not just the ones with activity during the
|
||||
report period (use -E to include low-activity accounts which would oth-
|
||||
erwise would be omitted).
|
||||
|
||||
The -T/--row-total flag adds an additional column showing the total for
|
||||
each row.
|
||||
|
||||
The -A/--average flag adds a column showing the average value in each
|
||||
The -A/--average flag adds a column showing the average value in each
|
||||
row.
|
||||
|
||||
Here's an example of all three:
|
||||
@ -1073,7 +1072,7 @@ COMMANDS
|
||||
# Average is rounded to the dollar here since all journal amounts are
|
||||
|
||||
Custom balance output
|
||||
In simple (non-multi-column) balance reports, you can customise the
|
||||
In simple (non-multi-column) balance reports, you can customise the
|
||||
output with --format FMT:
|
||||
|
||||
$ hledger balance --format "%20(account) %12(total)"
|
||||
@ -1091,7 +1090,7 @@ COMMANDS
|
||||
0
|
||||
|
||||
The FMT format string (plus a newline) specifies the formatting applied
|
||||
to each account/balance pair. It may contain any suitable text, with
|
||||
to each account/balance pair. It may contain any suitable text, with
|
||||
data fields interpolated like so:
|
||||
|
||||
%[MIN][.MAX](FIELDNAME)
|
||||
@ -1102,14 +1101,14 @@ COMMANDS
|
||||
|
||||
o FIELDNAME must be enclosed in parentheses, and can be one of:
|
||||
|
||||
o depth_spacer - a number of spaces equal to the account's depth, or
|
||||
o depth_spacer - a number of spaces equal to the account's depth, or
|
||||
if MIN is specified, MIN * depth spaces.
|
||||
|
||||
o account - the account's name
|
||||
|
||||
o total - the account's balance/posted total, right justified
|
||||
|
||||
Also, FMT can begin with an optional prefix to control how multi-com-
|
||||
Also, FMT can begin with an optional prefix to control how multi-com-
|
||||
modity amounts are rendered:
|
||||
|
||||
o %_ - render on multiple lines, bottom-aligned (the default)
|
||||
@ -1118,7 +1117,7 @@ COMMANDS
|
||||
|
||||
o %, - render on one line, comma-separated
|
||||
|
||||
There are some quirks. Eg in one-line mode, %(depth_spacer) has no
|
||||
There are some quirks. Eg in one-line mode, %(depth_spacer) has no
|
||||
effect, instead %(account) has indentation built in.
|
||||
Experimentation may be needed to get pleasing results.
|
||||
|
||||
@ -1126,14 +1125,14 @@ COMMANDS
|
||||
|
||||
o %(total) - the account's total
|
||||
|
||||
o %-20.20(account) - the account's name, left justified, padded to 20
|
||||
o %-20.20(account) - the account's name, left justified, padded to 20
|
||||
characters and clipped at 20 characters
|
||||
|
||||
o %,%-50(account) %25(total) - account name padded to 50 characters,
|
||||
total padded to 20 characters, with multiple commodities rendered on
|
||||
o %,%-50(account) %25(total) - account name padded to 50 characters,
|
||||
total padded to 20 characters, with multiple commodities rendered on
|
||||
one line
|
||||
|
||||
o %20(total) %2(depth_spacer)%-(account) - the default format for the
|
||||
o %20(total) %2(depth_spacer)%-(account) - the default format for the
|
||||
single-column balance report
|
||||
|
||||
Colour support
|
||||
@ -1144,8 +1143,8 @@ COMMANDS
|
||||
o the output is not being redirected or piped anywhere
|
||||
|
||||
Output destination
|
||||
The balance, print, register and stats commands can write their output
|
||||
to a destination other than the console. This is controlled by the
|
||||
The balance, print, register and stats commands can write their output
|
||||
to a destination other than the console. This is controlled by the
|
||||
-o/--output-file option.
|
||||
|
||||
$ hledger balance -o - # write to stdout (the default)
|
||||
@ -1153,8 +1152,8 @@ COMMANDS
|
||||
|
||||
CSV output
|
||||
The balance, print and register commands can write their output as CSV.
|
||||
This is useful for exporting data to other applications, eg to make
|
||||
charts in a spreadsheet. This is controlled by the -O/--output-format
|
||||
This is useful for exporting data to other applications, eg to make
|
||||
charts in a spreadsheet. This is controlled by the -O/--output-format
|
||||
option, or by specifying a .csv file extension with -o/--output-file.
|
||||
|
||||
$ hledger balance -O csv # write CSV to stdout
|
||||
@ -1168,7 +1167,7 @@ COMMANDS
|
||||
balances
|
||||
|
||||
--cumulative
|
||||
show balance change accumulated across periods (in multicolumn
|
||||
show balance change accumulated across periods (in multicolumn
|
||||
reports), instead of historical ending balances
|
||||
|
||||
-H --historical
|
||||
@ -1199,8 +1198,8 @@ COMMANDS
|
||||
--format=LINEFORMAT
|
||||
in single-column balance reports: use this custom line format
|
||||
|
||||
This command displays a simple balance sheet. It currently assumes
|
||||
that you have top-level accounts named asset and liability (plural
|
||||
This command displays a simple balance sheet. It currently assumes
|
||||
that you have top-level accounts named asset and liability (plural
|
||||
forms also allowed.)
|
||||
|
||||
$ hledger balancesheet
|
||||
@ -1223,9 +1222,9 @@ COMMANDS
|
||||
0
|
||||
|
||||
With a reporting interval, multiple columns will be shown, one for each
|
||||
report period. As with multicolumn balance reports, you can alter the
|
||||
report mode with --change/--cumulative/--historical. Normally bal-
|
||||
ancesheet shows historical ending balances, which is what you need for
|
||||
report period. As with multicolumn balance reports, you can alter the
|
||||
report mode with --change/--cumulative/--historical. Normally bal-
|
||||
ancesheet shows historical ending balances, which is what you need for
|
||||
a balance sheet; note this means it ignores report begin dates.
|
||||
|
||||
cashflow
|
||||
@ -1235,7 +1234,7 @@ COMMANDS
|
||||
show balance change in each period (default)
|
||||
|
||||
--cumulative
|
||||
show balance change accumulated across periods (in multicolumn
|
||||
show balance change accumulated across periods (in multicolumn
|
||||
reports), instead of changes during periods
|
||||
|
||||
-H --historical
|
||||
@ -1266,9 +1265,9 @@ COMMANDS
|
||||
--format=LINEFORMAT
|
||||
in single-column balance reports: use this custom line format
|
||||
|
||||
This command displays a simple cashflow statement It shows the change
|
||||
in all "cash" (ie, liquid assets) accounts for the period. It cur-
|
||||
rently assumes that cash accounts are under a top-level account named
|
||||
This command displays a simple cashflow statement It shows the change
|
||||
in all "cash" (ie, liquid assets) accounts for the period. It cur-
|
||||
rently assumes that cash accounts are under a top-level account named
|
||||
asset and do not contain receivable or A/R (plural forms also allowed.)
|
||||
|
||||
$ hledger cashflow
|
||||
@ -1286,18 +1285,18 @@ COMMANDS
|
||||
$-1
|
||||
|
||||
With a reporting interval, multiple columns will be shown, one for each
|
||||
report period. Normally cashflow shows changes in assets per period,
|
||||
though as with multicolumn balance reports you can alter the report
|
||||
report period. Normally cashflow shows changes in assets per period,
|
||||
though as with multicolumn balance reports you can alter the report
|
||||
mode with --change/--cumulative/--historical.
|
||||
|
||||
help
|
||||
Show any of the hledger manuals.
|
||||
|
||||
The help command displays any of the main hledger man pages. (Unlike
|
||||
hledger --help, which displays only the hledger man page.) Run it with
|
||||
no arguments to list available topics (their names are shortened for
|
||||
easier typing), and run hledger help TOPIC to select one. The output
|
||||
is similar to a man page, but fixed width. It may be long, so you may
|
||||
The help command displays any of the main hledger man pages. (Unlike
|
||||
hledger --help, which displays only the hledger man page.) Run it with
|
||||
no arguments to list available topics (their names are shortened for
|
||||
easier typing), and run hledger help TOPIC to select one. The output
|
||||
is similar to a man page, but fixed width. It may be long, so you may
|
||||
wish to pipe it into a pager. See also info and man.
|
||||
|
||||
$ hledger help
|
||||
@ -1325,7 +1324,7 @@ COMMANDS
|
||||
show balance change in each period (default)
|
||||
|
||||
--cumulative
|
||||
show balance change accumulated across periods (in multicolumn
|
||||
show balance change accumulated across periods (in multicolumn
|
||||
reports), instead of changes during periods
|
||||
|
||||
-H --historical
|
||||
@ -1356,8 +1355,8 @@ COMMANDS
|
||||
--format=LINEFORMAT
|
||||
in single-column balance reports: use this custom line format
|
||||
|
||||
This command displays a simple income statement. It currently assumes
|
||||
that you have top-level accounts named income (or revenue) and expense
|
||||
This command displays a simple income statement. It currently assumes
|
||||
that you have top-level accounts named income (or revenue) and expense
|
||||
(plural forms also allowed.)
|
||||
|
||||
$ hledger incomestatement
|
||||
@ -1382,30 +1381,30 @@ COMMANDS
|
||||
0
|
||||
|
||||
With a reporting interval, multiple columns will be shown, one for each
|
||||
report period. Normally incomestatement shows revenues/expenses per
|
||||
period, though as with multicolumn balance reports you can alter the
|
||||
report period. Normally incomestatement shows revenues/expenses per
|
||||
period, though as with multicolumn balance reports you can alter the
|
||||
report mode with --change/--cumulative/--historical.
|
||||
|
||||
info
|
||||
Show any of the hledger manuals using info.
|
||||
|
||||
The info command displays any of the hledger reference manuals using
|
||||
the info hypertextual documentation viewer. This can be a very effi-
|
||||
cient way to browse large manuals. It requires the "info" program to
|
||||
The info command displays any of the hledger reference manuals using
|
||||
the info hypertextual documentation viewer. This can be a very effi-
|
||||
cient way to browse large manuals. It requires the "info" program to
|
||||
be available in your PATH.
|
||||
|
||||
As with help, run it with no arguments to list available topics (manu-
|
||||
As with help, run it with no arguments to list available topics (manu-
|
||||
als).
|
||||
|
||||
man
|
||||
Show any of the hledger manuals using man.
|
||||
|
||||
The man command displays any of the hledger reference manuals using
|
||||
man, the standard documentation viewer on unix systems. This will fit
|
||||
the text to your terminal width, and probably invoke a pager automati-
|
||||
The man command displays any of the hledger reference manuals using
|
||||
man, the standard documentation viewer on unix systems. This will fit
|
||||
the text to your terminal width, and probably invoke a pager automati-
|
||||
cally. It requires the "man" program to be available in your PATH.
|
||||
|
||||
As with help, run it with no arguments to list available topics (manu-
|
||||
As with help, run it with no arguments to list available topics (manu-
|
||||
als).
|
||||
|
||||
print
|
||||
@ -1415,14 +1414,14 @@ COMMANDS
|
||||
show all amounts explicitly
|
||||
|
||||
-m STR --match=STR
|
||||
show the transaction whose description is most similar to STR,
|
||||
show the transaction whose description is most similar to STR,
|
||||
and is most recent
|
||||
|
||||
-O FMT --output-format=FMT
|
||||
select the output format. Supported formats: txt, csv.
|
||||
|
||||
-o FILE --output-file=FILE
|
||||
write output to FILE. A file extension matching one of the
|
||||
write output to FILE. A file extension matching one of the
|
||||
above formats selects that format.
|
||||
|
||||
$ hledger print
|
||||
@ -1450,23 +1449,23 @@ COMMANDS
|
||||
The print command displays full journal entries (transactions) from the
|
||||
journal file, tidily formatted.
|
||||
|
||||
As of hledger 1.2, print's output is always a valid hledger journal.
|
||||
However it may not preserve all original content, eg it does not print
|
||||
As of hledger 1.2, print's output is always a valid hledger journal.
|
||||
However it may not preserve all original content, eg it does not print
|
||||
directives or inter-transaction comments.
|
||||
|
||||
Normally, transactions' implicit/explicit amount style is preserved:
|
||||
when an amount is omitted in the journal, it will be omitted in the
|
||||
output. You can use the -x/--explicit flag to make all amounts
|
||||
explicit, which can be useful for troubleshooting or for making your
|
||||
journal more readable and robust against data entry errors. Note, in
|
||||
this mode postings with a multi-commodity amount (possible with an
|
||||
implicit amount in a multi-commodity transaction) will be split into
|
||||
Normally, transactions' implicit/explicit amount style is preserved:
|
||||
when an amount is omitted in the journal, it will be omitted in the
|
||||
output. You can use the -x/--explicit flag to make all amounts
|
||||
explicit, which can be useful for troubleshooting or for making your
|
||||
journal more readable and robust against data entry errors. Note, in
|
||||
this mode postings with a multi-commodity amount (possible with an
|
||||
implicit amount in a multi-commodity transaction) will be split into
|
||||
multiple single-commodity postings, for valid journal output.
|
||||
|
||||
With -B/--cost, amounts with transaction prices are converted to cost
|
||||
With -B/--cost, amounts with transaction prices are converted to cost
|
||||
(using the transaction price).
|
||||
|
||||
The print command also supports output destination and CSV output.
|
||||
The print command also supports output destination and CSV output.
|
||||
Here's an example of print's CSV output:
|
||||
|
||||
$ hledger print -Ocsv
|
||||
@ -1483,20 +1482,20 @@ COMMANDS
|
||||
"5","2008/12/31","","*","","pay off","","liabilities:debts","1","$","","1","",""
|
||||
"5","2008/12/31","","*","","pay off","","assets:bank:checking","-1","$","1","","",""
|
||||
|
||||
o There is one CSV record per posting, with the parent transaction's
|
||||
o There is one CSV record per posting, with the parent transaction's
|
||||
fields repeated.
|
||||
|
||||
o The "txnidx" (transaction index) field shows which postings belong to
|
||||
the same transaction. (This number might change if transactions are
|
||||
reordered within the file, files are parsed/included in a different
|
||||
the same transaction. (This number might change if transactions are
|
||||
reordered within the file, files are parsed/included in a different
|
||||
order, etc.)
|
||||
|
||||
o The amount is separated into "commodity" (the symbol) and "amount"
|
||||
o The amount is separated into "commodity" (the symbol) and "amount"
|
||||
(numeric quantity) fields.
|
||||
|
||||
o The numeric amount is repeated in either the "credit" or "debit" col-
|
||||
umn, for convenience. (Those names are not accurate in the account-
|
||||
ing sense; it just puts negative amounts under credit and zero or
|
||||
umn, for convenience. (Those names are not accurate in the account-
|
||||
ing sense; it just puts negative amounts under credit and zero or
|
||||
greater amounts under debit.)
|
||||
|
||||
register
|
||||
@ -1506,7 +1505,7 @@ COMMANDS
|
||||
show running total from report start date (default)
|
||||
|
||||
-H --historical
|
||||
show historical running total/balance (includes postings before
|
||||
show historical running total/balance (includes postings before
|
||||
report start date)
|
||||
|
||||
-A --average
|
||||
@ -1517,18 +1516,18 @@ COMMANDS
|
||||
show postings' siblings instead
|
||||
|
||||
-w N --width=N
|
||||
set output width (default: terminal width or COLUMNS. -wN,M
|
||||
set output width (default: terminal width or COLUMNS. -wN,M
|
||||
sets description width as well)
|
||||
|
||||
-O FMT --output-format=FMT
|
||||
select the output format. Supported formats: txt, csv.
|
||||
|
||||
-o FILE --output-file=FILE
|
||||
write output to FILE. A file extension matching one of the
|
||||
write output to FILE. A file extension matching one of the
|
||||
above formats selects that format.
|
||||
|
||||
The register command displays postings, one per line, and their running
|
||||
total. This is typically used with a query selecting a particular
|
||||
total. This is typically used with a query selecting a particular
|
||||
account, to see that account's activity:
|
||||
|
||||
$ hledger register checking
|
||||
@ -1537,8 +1536,8 @@ COMMANDS
|
||||
2008/06/02 save assets:bank:checking $-1 $1
|
||||
2008/12/31 pay off assets:bank:checking $-1 0
|
||||
|
||||
The --historical/-H flag adds the balance from any undisplayed prior
|
||||
postings to the running total. This is useful when you want to see
|
||||
The --historical/-H flag adds the balance from any undisplayed prior
|
||||
postings to the running total. This is useful when you want to see
|
||||
only recent activity, with a historically accurate running balance:
|
||||
|
||||
$ hledger register checking -b 2008/6 --historical
|
||||
@ -1548,23 +1547,23 @@ COMMANDS
|
||||
|
||||
The --depth option limits the amount of sub-account detail displayed.
|
||||
|
||||
The --average/-A flag shows the running average posting amount instead
|
||||
The --average/-A flag shows the running average posting amount instead
|
||||
of the running total (so, the final number displayed is the average for
|
||||
the whole report period). This flag implies --empty (see below). It
|
||||
is affected by --historical. It works best when showing just one
|
||||
the whole report period). This flag implies --empty (see below). It
|
||||
is affected by --historical. It works best when showing just one
|
||||
account and one commodity.
|
||||
|
||||
The --related/-r flag shows the other postings in the transactions of
|
||||
The --related/-r flag shows the other postings in the transactions of
|
||||
the postings which would normally be shown.
|
||||
|
||||
With a reporting interval, register shows summary postings, one per
|
||||
With a reporting interval, register shows summary postings, one per
|
||||
interval, aggregating the postings to each account:
|
||||
|
||||
$ hledger register --monthly income
|
||||
2008/01 income:salary $-1 $-1
|
||||
2008/06 income:gifts $-1 $-2
|
||||
|
||||
Periods with no activity, and summary postings with a zero amount, are
|
||||
Periods with no activity, and summary postings with a zero amount, are
|
||||
not shown by default; use the --empty/-E flag to see them:
|
||||
|
||||
$ hledger register --monthly income -E
|
||||
@ -1581,7 +1580,7 @@ COMMANDS
|
||||
2008/11 0 $-2
|
||||
2008/12 0 $-2
|
||||
|
||||
Often, you'll want to see just one line per interval. The --depth
|
||||
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
|
||||
@ -1589,19 +1588,19 @@ COMMANDS
|
||||
2008/06 assets $-1 0
|
||||
2008/12 assets $-1 $-1
|
||||
|
||||
Note when using report intervals, if you specify start/end dates these
|
||||
will be adjusted outward if necessary to contain a whole number of
|
||||
intervals. This ensures that the first and last intervals are full
|
||||
Note when using report intervals, if you specify start/end dates these
|
||||
will be adjusted outward if necessary to contain a whole number of
|
||||
intervals. This ensures that the first and last intervals are full
|
||||
length and comparable to the others in the report.
|
||||
|
||||
Custom register output
|
||||
register uses the full terminal width by default, except on windows.
|
||||
You can override this by setting the COLUMNS environment variable (not
|
||||
register uses the full terminal width by default, except on windows.
|
||||
You can override this by setting the COLUMNS environment variable (not
|
||||
a bash shell variable) or by using the --width/-w option.
|
||||
|
||||
The description and account columns normally share the space equally
|
||||
(about half of (width - 40) each). You can adjust this by adding a
|
||||
description width as part of --width's argument, comma-separated:
|
||||
The description and account columns normally share the space equally
|
||||
(about half of (width - 40) each). You can adjust this by adding a
|
||||
description width as part of --width's argument, comma-separated:
|
||||
--width W,D . Here's a diagram:
|
||||
|
||||
<--------------------------------- width (W) ---------------------------------->
|
||||
@ -1617,14 +1616,14 @@ COMMANDS
|
||||
$ hledger reg -w 100,40 # set overall width 100, description width 40
|
||||
$ hledger reg -w $COLUMNS,40 # use terminal width, and set description width
|
||||
|
||||
The register command also supports the -o/--output-file and -O/--out-
|
||||
The register command also supports the -o/--output-file and -O/--out-
|
||||
put-format options for controlling output destination and CSV output.
|
||||
|
||||
stats
|
||||
Show some journal statistics.
|
||||
|
||||
-o FILE --output-file=FILE
|
||||
write output to FILE. A file extension matching one of the
|
||||
write output to FILE. A file extension matching one of the
|
||||
above formats selects that format.
|
||||
|
||||
$ hledger stats
|
||||
@ -1639,8 +1638,8 @@ COMMANDS
|
||||
Accounts : 8 (depth 3)
|
||||
Commodities : 1 ($)
|
||||
|
||||
The stats command displays summary information for the whole journal,
|
||||
or a matched part of it. With a reporting interval, it shows a report
|
||||
The stats command displays summary information for the whole journal,
|
||||
or a matched part of it. With a reporting interval, it shows a report
|
||||
for each report period.
|
||||
|
||||
The stats command also supports -o/--output-file for controlling output
|
||||
@ -1652,34 +1651,34 @@ COMMANDS
|
||||
$ hledger test
|
||||
Cases: 74 Tried: 74 Errors: 0 Failures: 0
|
||||
|
||||
This command runs hledger's built-in unit tests and displays a quick
|
||||
This command runs hledger's built-in unit tests and displays a quick
|
||||
report. With a regular expression argument, it selects only tests with
|
||||
matching names. It's mainly used in development, but it's also nice to
|
||||
be able to check your hledger executable for smoke at any time.
|
||||
|
||||
ADD-ON COMMANDS
|
||||
hledger also searches for external add-on commands, and will include
|
||||
hledger also searches for external add-on commands, and will include
|
||||
these in the commands list. These are programs or scripts in your PATH
|
||||
whose name starts with hledger- and ends with a recognised file exten-
|
||||
whose name starts with hledger- and ends with a recognised file exten-
|
||||
sion (currently: no extension, bat,com,exe, hs,lhs,pl,py,rb,rkt,sh).
|
||||
|
||||
Add-ons can be invoked like any hledger command, but there are a few
|
||||
Add-ons can be invoked like any hledger command, but there are a few
|
||||
things to be aware of. Eg if the hledger-web add-on is installed,
|
||||
|
||||
o hledger -h web shows hledger's help, while hledger web -h shows
|
||||
hledger-web's help.
|
||||
|
||||
o Flags specific to the add-on must have a preceding -- to hide them
|
||||
from hledger. So hledger web --serve --port 9000 will be rejected;
|
||||
o Flags specific to the add-on must have a preceding -- to hide them
|
||||
from hledger. So hledger web --serve --port 9000 will be rejected;
|
||||
you must use hledger web -- --serve --port 9000.
|
||||
|
||||
o You can always run add-ons directly if preferred:
|
||||
o You can always run add-ons directly if preferred:
|
||||
hledger-web --serve --port 9000.
|
||||
|
||||
Add-ons are a relatively easy way to add local features or experiment
|
||||
with new ideas. They can be written in any language, but haskell
|
||||
scripts have a big advantage: they can use the same hledger (and
|
||||
haskell) library functions that built-in commands do, for command-line
|
||||
Add-ons are a relatively easy way to add local features or experiment
|
||||
with new ideas. They can be written in any language, but haskell
|
||||
scripts have a big advantage: they can use the same hledger (and
|
||||
haskell) library functions that built-in commands do, for command-line
|
||||
options, journal parsing, reporting, etc.
|
||||
|
||||
Here are some hledger add-ons available:
|
||||
@ -1697,7 +1696,7 @@ ADD-ON COMMANDS
|
||||
hledger-web provides a simple web interface.
|
||||
|
||||
Third party add-ons
|
||||
These are maintained separately, and usually updated shortly after a
|
||||
These are maintained separately, and usually updated shortly after a
|
||||
hledger release.
|
||||
|
||||
diff
|
||||
@ -1705,7 +1704,7 @@ ADD-ON COMMANDS
|
||||
journal file and another.
|
||||
|
||||
iadd
|
||||
hledger-iadd is a curses-style, more interactive replacement for the
|
||||
hledger-iadd is a curses-style, more interactive replacement for the
|
||||
add command.
|
||||
|
||||
interest
|
||||
@ -1713,19 +1712,19 @@ ADD-ON COMMANDS
|
||||
ing to various schemes.
|
||||
|
||||
irr
|
||||
hledger-irr calculates the internal rate of return of an investment
|
||||
hledger-irr calculates the internal rate of return of an investment
|
||||
account.
|
||||
|
||||
Experimental add-ons
|
||||
These are available in source form in the hledger repo's bin/ direc-
|
||||
These are available in source form in the hledger repo's bin/ direc-
|
||||
tory; installing them is pretty easy. They may be less mature and doc-
|
||||
umented than built-in commands. Reading and tweaking these is a good
|
||||
umented than built-in commands. Reading and tweaking these is a good
|
||||
way to start making your own!
|
||||
|
||||
autosync
|
||||
hledger-autosync is a symbolic link for easily running ledger-autosync,
|
||||
if installed. ledger-autosync does deduplicating conversion of OFX
|
||||
data and some CSV formats, and can also download the data if your bank
|
||||
if installed. ledger-autosync does deduplicating conversion of OFX
|
||||
data and some CSV formats, and can also download the data if your bank
|
||||
offers OFX Direct Connect.
|
||||
|
||||
budget
|
||||
@ -1741,18 +1740,18 @@ ADD-ON COMMANDS
|
||||
hledger-check-dates.hs checks that journal entries are ordered by date.
|
||||
|
||||
check-dupes
|
||||
hledger-check-dupes.hs checks for account names sharing the same leaf
|
||||
hledger-check-dupes.hs checks for account names sharing the same leaf
|
||||
name.
|
||||
|
||||
equity
|
||||
hledger-equity.hs prints balance-resetting transactions, useful for
|
||||
hledger-equity.hs prints balance-resetting transactions, useful for
|
||||
bringing account balances across file boundaries.
|
||||
|
||||
prices
|
||||
hledger-prices.hs prints all prices from the journal.
|
||||
|
||||
print-unique
|
||||
hledger-print-unique.hs prints transactions which do not reuse an
|
||||
hledger-print-unique.hs prints transactions which do not reuse an
|
||||
already-seen description.
|
||||
|
||||
register-match
|
||||
@ -1764,21 +1763,21 @@ ADD-ON COMMANDS
|
||||
tions.
|
||||
|
||||
ENVIRONMENT
|
||||
COLUMNS The screen width used by the register command. Default: the
|
||||
COLUMNS The screen width used by the register command. Default: the
|
||||
full terminal width.
|
||||
|
||||
LEDGER_FILE The journal file path when not specified with -f. Default:
|
||||
~/.hledger.journal (on windows, perhaps C:/Users/USER/.hledger.jour-
|
||||
~/.hledger.journal (on windows, perhaps C:/Users/USER/.hledger.jour-
|
||||
nal).
|
||||
|
||||
FILES
|
||||
Reads data from one or more files in hledger journal, timeclock, time-
|
||||
dot, or CSV format specified with -f, or $LEDGER_FILE, or
|
||||
$HOME/.hledger.journal (on windows, perhaps
|
||||
Reads data from one or more files in hledger journal, timeclock, time-
|
||||
dot, or CSV format specified with -f, or $LEDGER_FILE, or
|
||||
$HOME/.hledger.journal (on windows, perhaps
|
||||
C:/Users/USER/.hledger.journal).
|
||||
|
||||
BUGS
|
||||
The need to precede addon command options with -- when invoked from
|
||||
The need to precede addon command options with -- when invoked from
|
||||
hledger is awkward.
|
||||
|
||||
When input data contains non-ascii characters, a suitable system locale
|
||||
@ -1791,33 +1790,33 @@ BUGS
|
||||
In a Cygwin/MSYS/Mintty window, the tab key is not supported in hledger
|
||||
add.
|
||||
|
||||
Not all of Ledger's journal file syntax is supported. See file format
|
||||
Not all of Ledger's journal file syntax is supported. See file format
|
||||
differences.
|
||||
|
||||
On large data files, hledger is slower and uses more memory than
|
||||
On large data files, hledger is slower and uses more memory than
|
||||
Ledger.
|
||||
|
||||
TROUBLESHOOTING
|
||||
Here are some issues you might encounter when you run hledger (and
|
||||
remember you can also seek help from the IRC channel, mail list or bug
|
||||
Here are some issues you might encounter when you run hledger (and
|
||||
remember you can also seek help from the IRC channel, mail list or bug
|
||||
tracker):
|
||||
|
||||
Successfully installed, but "No command 'hledger' found"
|
||||
stack and cabal install binaries into a special directory, which should
|
||||
be added to your PATH environment variable. Eg on unix-like systems,
|
||||
be added to your PATH environment variable. Eg on unix-like systems,
|
||||
that is ~/.local/bin and ~/.cabal/bin respectively.
|
||||
|
||||
I set a custom LEDGER_FILE, but hledger is still using the default file
|
||||
LEDGER_FILE should be a real environment variable, not just a shell
|
||||
variable. The command env | grep LEDGER_FILE should show it. You may
|
||||
LEDGER_FILE should be a real environment variable, not just a shell
|
||||
variable. The command env | grep LEDGER_FILE should show it. You may
|
||||
need to use export. Here's an explanation.
|
||||
|
||||
"Illegal byte sequence" or "Invalid or incomplete multibyte or wide
|
||||
"Illegal byte sequence" or "Invalid or incomplete multibyte or wide
|
||||
character" errors
|
||||
In order to handle non-ascii letters and symbols (like ), hledger needs
|
||||
an appropriate locale. This is usually configured system-wide; you can
|
||||
also configure it temporarily. The locale may need to be one that sup-
|
||||
ports UTF-8, if you built hledger with GHC < 7.2 (or possibly always,
|
||||
ports UTF-8, if you built hledger with GHC < 7.2 (or possibly always,
|
||||
I'm not sure yet).
|
||||
|
||||
Here's an example of setting the locale temporarily, on ubuntu
|
||||
@ -1836,7 +1835,7 @@ TROUBLESHOOTING
|
||||
$ echo "export LANG=en_US.UTF-8" >>~/.bash_profile
|
||||
$ bash --login
|
||||
|
||||
If we preferred to use eg fr_FR.utf8, we might have to install that
|
||||
If we preferred to use eg fr_FR.utf8, we might have to install that
|
||||
first:
|
||||
|
||||
$ apt-get install language-pack-fr
|
||||
@ -1857,7 +1856,7 @@ TROUBLESHOOTING
|
||||
|
||||
|
||||
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)
|
||||
|
||||
|
||||
@ -1871,7 +1870,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)
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user