diff --git a/hledger-ui/hledger-ui.info b/hledger-ui/hledger-ui.info
index a96a4181b..f078a9a1e 100644
--- a/hledger-ui/hledger-ui.info
+++ b/hledger-ui/hledger-ui.info
@@ -1,37 +1,36 @@
-This is hledger-ui/hledger-ui.info, produced by makeinfo version 4.8
-from stdin.
+This is hledger-ui.info, produced by makeinfo version 6.7 from stdin.
 
 
-File: hledger-ui.info,  Node: Top,  Up: (dir)
+File: hledger-ui.info,  Node: Top,  Next: OPTIONS,  Up: (dir)
 
 hledger-ui(1)
 *************
 
 hledger-ui is a terminal interface (TUI) for the hledger accounting
-tool. This manual is for hledger-ui 1.21.99.
+tool.  This manual is for hledger-ui 1.21.99.
 
-   `hledger-ui [OPTIONS] [QUERYARGS]'
-`hledger ui -- [OPTIONS] [QUERYARGS]'
+   'hledger-ui [OPTIONS] [QUERYARGS]'
+'hledger ui -- [OPTIONS] [QUERYARGS]'
 
    hledger is a reliable, cross-platform set of programs for tracking
 money, time, or any other commodity, using double-entry accounting and a
-simple, editable file format. hledger is inspired by and largely
+simple, editable file format.  hledger is inspired by and largely
 compatible with ledger(1).
 
    hledger-ui is hledger's terminal interface, providing an efficient
 full-window text UI for viewing accounts and transactions, and some
-limited data entry capability. It is easier than hledger's command-line
+limited data entry capability.  It is easier than hledger's command-line
 interface, and sometimes quicker and more convenient than the web
 interface.
 
    Like hledger, it reads data from one or more files in hledger
-journal, timeclock, timedot, or CSV format specified with `-f', or
-`$LEDGER_FILE', or `$HOME/.hledger.journal' (on windows, perhaps
-`C:/Users/USER/.hledger.journal'). For more about this see hledger(1),
+journal, timeclock, timedot, or CSV format specified with '-f', or
+'$LEDGER_FILE', or '$HOME/.hledger.journal' (on windows, perhaps
+'C:/Users/USER/.hledger.journal').  For more about this see hledger(1),
 hledger_journal(5) etc.
 
    Unlike hledger, hledger-ui hides all future-dated transactions by
-default. They can be revealed, along with any rule-generated periodic
+default.  They can be revealed, along with any rule-generated periodic
 transactions, by pressing the F key (or starting with -forecast) to
 enable "forecast mode".
 
@@ -50,143 +49,146 @@ File: hledger-ui.info,  Node: OPTIONS,  Next: KEYS,  Prev: Top,  Up: Top
 1 OPTIONS
 *********
 
-Note: if invoking hledger-ui as a hledger subcommand, write `--' before
+Note: if invoking hledger-ui as a hledger subcommand, write '--' before
 options as shown above.
 
    Any QUERYARGS are interpreted as a hledger search query which filters
 the data.
 
-`--watch'
+'--watch'
+
      watch for data and date changes and reload automatically
+'--theme=default|terminal|greenterm'
 
-`--theme=default|terminal|greenterm'
      use this custom display theme
+'--register=ACCTREGEX'
 
-`--register=ACCTREGEX'
      start in the (first) matched account's register screen
+'--change'
 
-`--change'
      show period balances (changes) at startup instead of historical
      balances
+'-l --flat'
 
-`-l --flat'
      show accounts as a flat list (default)
+'-t --tree'
 
-`-t --tree'
      show accounts as a tree
 
    hledger input options:
 
-`-f FILE --file=FILE'
-     use a different input file. For stdin, use - (default:
-     `$LEDGER_FILE' or `$HOME/.hledger.journal')
+'-f FILE --file=FILE'
+
+     use a different input file.  For stdin, use - (default:
+     '$LEDGER_FILE' or '$HOME/.hledger.journal')
+'--rules-file=RULESFILE'
 
-`--rules-file=RULESFILE'
      Conversion rules file to use when reading CSV (default: FILE.rules)
+'--separator=CHAR'
 
-`--separator=CHAR'
      Field separator to expect when reading CSV (default: ',')
+'--alias=OLD=NEW'
 
-`--alias=OLD=NEW'
      rename accounts named OLD to NEW
+'--anon'
 
-`--anon'
      anonymize accounts and payees
+'--pivot FIELDNAME'
 
-`--pivot FIELDNAME'
      use some other field or tag for the account name
+'-I --ignore-assertions'
 
-`-I --ignore-assertions'
      disable balance assertion checks (note: does not disable balance
      assignments)
+'-s --strict'
 
-`-s --strict'
      do extra error checking (check that all posted accounts are
      declared)
 
    hledger reporting options:
 
-`-b --begin=DATE'
+'-b --begin=DATE'
+
      include postings/txns on or after this date (will be adjusted to
      preceding subperiod start when using a report interval)
+'-e --end=DATE'
 
-`-e --end=DATE'
      include postings/txns before this date (will be adjusted to
      following subperiod end when using a report interval)
+'-D --daily'
 
-`-D --daily'
      multiperiod/multicolumn report by day
+'-W --weekly'
 
-`-W --weekly'
      multiperiod/multicolumn report by week
+'-M --monthly'
 
-`-M --monthly'
      multiperiod/multicolumn report by month
+'-Q --quarterly'
 
-`-Q --quarterly'
      multiperiod/multicolumn report by quarter
+'-Y --yearly'
 
-`-Y --yearly'
      multiperiod/multicolumn report by year
+'-p --period=PERIODEXP'
 
-`-p --period=PERIODEXP'
      set start date, end date, and/or reporting interval all at once
      using period expressions syntax
+'--date2'
 
-`--date2'
      match the secondary date instead (see command help for other
      effects)
+'-U --unmarked'
 
-`-U --unmarked'
      include only unmarked postings/txns (can combine with -P or -C)
+'-P --pending'
 
-`-P --pending'
      include only pending postings/txns
+'-C --cleared'
 
-`-C --cleared'
      include only cleared postings/txns
+'-R --real'
 
-`-R --real'
      include only non-virtual postings
+'-NUM --depth=NUM'
 
-`-NUM --depth=NUM'
      hide/aggregate accounts or postings more than NUM levels deep
+'-E --empty'
 
-`-E --empty'
      show items with zero amount, normally hidden (and vice-versa in
      hledger-ui/hledger-web)
+'-B --cost'
 
-`-B --cost'
      convert amounts to their cost/selling amount at transaction time
+'-V --market'
 
-`-V --market'
      convert amounts to their market value in default valuation
      commodities
+'-X --exchange=COMM'
 
-`-X --exchange=COMM'
      convert amounts to their market value in commodity COMM
+'--value'
 
-`--value'
      convert amounts to cost or market value, more flexibly than
      -B/-V/-X
+'--infer-market-prices'
 
-`--infer-market-prices'
      use transaction prices (recorded with @ or @@) as additional market
      prices, as if they were P directives
+'--auto'
 
-`--auto'
      apply automated posting rules to modify transactions.
+'--forecast'
 
-`--forecast'
      generate future transactions from periodic transaction rules, for
-     the next 6 months or till report end date. In hledger-ui, also
+     the next 6 months or till report end date.  In hledger-ui, also
      make ordinary future transactions visible.
+'--color=WHEN (or --colour=WHEN)'
 
-`--color=WHEN (or --colour=WHEN)'
      Should color-supporting commands use ANSI color codes in text
      output.  'auto' (default): whenever stdout seems to be a
      color-supporting terminal.  'always' or 'yes': always, useful eg
-     when piping output into 'less -R'.  'never' or 'no': never.  A
+     when piping output into 'less -R'. 'never' or 'no': never.  A
      NO_COLOR environment variable overrides this.
 
    When a reporting option appears more than once in the command line,
@@ -196,24 +198,25 @@ the last one takes precedence.
 
    hledger help options:
 
-`-h --help'
+'-h --help'
+
      show general or COMMAND help
+'--man'
 
-`--man'
      show general or COMMAND user manual with man
+'--info'
 
-`--info'
      show general or COMMAND user manual with info
+'--version'
 
-`--version'
      show general or ADDONCMD version
+'--debug[=N]'
 
-`--debug[=N]'
      show debug output (levels 1-9, default: 1)
 
    A @FILE argument will be expanded to the contents of FILE, which
-should contain one command line option/argument per line. (To prevent
-this, insert a `--' argument before.)
+should contain one command line option/argument per line.  (To prevent
+this, insert a '--' argument before.)
 
 
 File: hledger-ui.info,  Node: KEYS,  Next: SCREENS,  Prev: OPTIONS,  Up: Top
@@ -221,94 +224,94 @@ File: hledger-ui.info,  Node: KEYS,  Next: SCREENS,  Prev: OPTIONS,  Up: Top
 2 KEYS
 ******
 
-`?' shows a help dialog listing all keys. (Some of these also appear in
-the quick help at the bottom of each screen.) Press `?' again (or
-`ESCAPE', or `LEFT', or `q') to close it. The following keys work on
+'?' shows a help dialog listing all keys.  (Some of these also appear in
+the quick help at the bottom of each screen.)  Press '?' again (or
+'ESCAPE', or 'LEFT', or 'q') to close it.  The following keys work on
 most screens:
 
-   The cursor keys navigate: `right' (or `enter') goes deeper, `left'
-returns to the previous screen, `up'/`down'/`page up'/`page
-down'/`home'/`end' move up and down through lists. Emacs-style
-(`ctrl-p'/`ctrl-n'/`ctrl-f'/`ctrl-b') movement keys are also supported
+   The cursor keys navigate: 'right' (or 'enter') goes deeper, 'left'
+returns to the previous screen, 'up'/'down'/'page up'/'page
+down'/'home'/'end' move up and down through lists.  Emacs-style
+('ctrl-p'/'ctrl-n'/'ctrl-f'/'ctrl-b') movement keys are also supported
 (but not vi-style keys, since hledger-1.19, sorry!).  A tip: movement
 speed is limited by your keyboard repeat rate, to move faster you may
-want to adjust it. (If you're on a mac, the karabiner app is one way to
+want to adjust it.  (If you're on a mac, the karabiner app is one way to
 do that.)
 
    With shift pressed, the cursor keys adjust the report period,
 limiting the transactions to be shown (by default, all are shown).
-`shift-down/up' steps downward and upward through these standard report
-period durations: year, quarter, month, week, day. Then,
-`shift-left/right' moves to the previous/next period. `T' sets the
-report period to today. With the `--watch' option, when viewing a
+'shift-down/up' steps downward and upward through these standard report
+period durations: year, quarter, month, week, day.  Then,
+'shift-left/right' moves to the previous/next period.  'T' sets the
+report period to today.  With the '--watch' option, when viewing a
 "current" period (the current day, week, month, quarter, or year), the
-period will move automatically to track the current date. To set a
-non-standard period, you can use `/' and a `date:' query.
+period will move automatically to track the current date.  To set a
+non-standard period, you can use '/' and a 'date:' query.
 
-   `/' lets you set a general filter query limiting the data shown,
-using the same query terms as in hledger and hledger-web. While editing
-the query, you can use CTRL-a/e/d/k, BS, cursor keys; press `ENTER' to
-set it, or `ESCAPE'to cancel. There are also keys for quickly adjusting
+   '/' lets you set a general filter query limiting the data shown,
+using the same query terms as in hledger and hledger-web.  While editing
+the query, you can use CTRL-a/e/d/k, BS, cursor keys; press 'ENTER' to
+set it, or 'ESCAPE'to cancel.  There are also keys for quickly adjusting
 some common filters like account depth and transaction status (see
-below). `BACKSPACE' or `DELETE' removes all filters, showing all
+below).  'BACKSPACE' or 'DELETE' removes all filters, showing all
 transactions.
 
    As mentioned above, by default hledger-ui hides future transactions -
 both ordinary transactions recorded in the journal, and periodic
-transactions generated by rule. `F' toggles forecast mode, in which
+transactions generated by rule.  'F' toggles forecast mode, in which
 future/forecasted transactions are shown.
 
-   `ESCAPE' resets the UI state and jumps back to the top screen,
-restoring the app's initial state at startup. Or, it cancels minibuffer
+   'ESCAPE' resets the UI state and jumps back to the top screen,
+restoring the app's initial state at startup.  Or, it cancels minibuffer
 data entry or the help dialog.
 
-   `CTRL-l' redraws the screen and centers the selection if possible
+   'CTRL-l' redraws the screen and centers the selection if possible
 (selections near the top won't be centered, since we don't scroll above
 the top).
 
-   `g' reloads from the data file(s) and updates the current screen and
-any previous screens. (With large files, this could cause a noticeable
+   'g' reloads from the data file(s) and updates the current screen and
+any previous screens.  (With large files, this could cause a noticeable
 pause.)
 
-   `I' toggles balance assertion checking. Disabling balance assertions
+   'I' toggles balance assertion checking.  Disabling balance assertions
 temporarily can be useful for troubleshooting.
 
-   `a' runs command-line hledger's add command, and reloads the updated
-file. This allows some basic data entry.
+   'a' runs command-line hledger's add command, and reloads the updated
+file.  This allows some basic data entry.
 
-   `A' is like `a', but runs the hledger-iadd tool, which provides a
-terminal interface. This key will be available if `hledger-iadd' is
+   'A' is like 'a', but runs the hledger-iadd tool, which provides a
+terminal interface.  This key will be available if 'hledger-iadd' is
 installed in $path.
 
-   `E' runs $HLEDGER_UI_EDITOR, or $EDITOR, or a default (`emacsclient
--a "" -nw') on the journal file. With some editors (emacs, vi), the
+   'E' runs $HLEDGER_UI_EDITOR, or $EDITOR, or a default ('emacsclient
+-a "" -nw') on the journal file.  With some editors (emacs, vi), the
 cursor will be positioned at the current transaction when invoked from
 the register and transaction screens, and at the error location (if
 possible) when invoked from the error screen.
 
-   `B' toggles cost mode, showing amounts in their transaction price's
-commodity (like toggling the `-B/--cost' flag).
+   'B' toggles cost mode, showing amounts in their transaction price's
+commodity (like toggling the '-B/--cost' flag).
 
-   `V' toggles value mode, showing amounts' current market value in
-their default valuation commodity (like toggling the `-V/--market'
-flag). Note, "current market value" means the value on the report end
-date if specified, otherwise today. To see the value on another date,
-you can temporarily set that as the report end date. Eg: to see a
+   'V' toggles value mode, showing amounts' current market value in
+their default valuation commodity (like toggling the '-V/--market'
+flag).  Note, "current market value" means the value on the report end
+date if specified, otherwise today.  To see the value on another date,
+you can temporarily set that as the report end date.  Eg: to see a
 transaction as it was valued on july 30, go to the accounts or register
-screen, press `/', and add `date:-7/30' to the query.
+screen, press '/', and add 'date:-7/30' to the query.
 
    At most one of cost or value mode can be active at once.
 
    There's not yet any visual reminder when cost or value mode is
-active; for now pressing `b' `b' `v' should reliably reset to normal
+active; for now pressing 'b' 'b' 'v' should reliably reset to normal
 mode.
 
-   With `--watch' active, if you save an edit to the journal file while
-viewing the transaction screen in cost or value mode, the `B'/`V' keys
-will stop working. To work around, press `g' to force a manual reload,
+   With '--watch' active, if you save an edit to the journal file while
+viewing the transaction screen in cost or value mode, the 'B'/'V' keys
+will stop working.  To work around, press 'g' to force a manual reload,
 or exit the transaction screen.
 
-   `q' quits the application.
+   'q' quits the application.
 
    Additional screen-specific keys are described below.
 
@@ -331,47 +334,48 @@ File: hledger-ui.info,  Node: Accounts screen,  Next: Register screen,  Up: SCRE
 3.1 Accounts screen
 ===================
 
-This is normally the first screen displayed. It lists accounts and their
-balances, like hledger's balance command. By default, it shows all
-accounts and their latest ending balances (including the balances of
-subaccounts). If you specify a query on the command line, it shows just
+This is normally the first screen displayed.  It lists accounts and
+their balances, like hledger's balance command.  By default, it shows
+all accounts and their latest ending balances (including the balances of
+subaccounts).  If you specify a query on the command line, it shows just
 the matched accounts and the balances from matched transactions.
 
-   Account names are shown as a flat list by default; press `t' to
-toggle tree mode. In list mode, account balances are exclusive of
+   Account names are shown as a flat list by default; press 't' to
+toggle tree mode.  In list mode, account balances are exclusive of
 subaccounts, except where subaccounts are hidden by a depth limit (see
-below). In tree mode, all account balances are inclusive of subaccounts.
+below).  In tree mode, all account balances are inclusive of
+subaccounts.
 
-   To see less detail, press a number key, `1' to `9', to set a depth
-limit. Or use `-' to decrease and `+'/`=' to increase the depth limit.
-`0' shows even less detail, collapsing all accounts to a single total.
-To remove the depth limit, set it higher than the maximum account
-depth, or press `ESCAPE'.
+   To see less detail, press a number key, '1' to '9', to set a depth
+limit.  Or use '-' to decrease and '+'/'=' to increase the depth limit.
+'0' shows even less detail, collapsing all accounts to a single total.
+To remove the depth limit, set it higher than the maximum account depth,
+or press 'ESCAPE'.
 
-   `H' toggles between showing historical balances or period balances.
+   'H' toggles between showing historical balances or period balances.
 Historical balances (the default) are ending balances at the end of the
 report period, taking into account all transactions before that date
 (filtered by the filter query if any), including transactions before the
-start of the report period. In other words, historical balances are what
-you would see on a bank statement for that account (unless 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.
+start of the report period.  In other words, historical balances are
+what you would see on a bank statement for that account (unless
+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.
 
-   `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
+   '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.
+   'R' toggles real mode, in which virtual postings are ignored.
 
-   `Z' toggles nonzero mode, in which only accounts with nonzero
+   '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.
+   Press 'right' or 'enter' to view an account's transactions register.
 
 
 File: hledger-ui.info,  Node: Register screen,  Next: Transaction screen,  Prev: Accounts screen,  Up: SCREENS
@@ -380,46 +384,44 @@ File: hledger-ui.info,  Node: Register screen,  Next: Transaction screen,  Prev:
 ===================
 
 This screen shows the transactions affecting a particular account, like
-a check register. Each line represents one transaction and shows:
+a check register.  Each line represents one transaction and shows:
 
-   * 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.)
+   * 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.)
 
    * the overall change to the current account's balance; positive for
      an inflow to this account, negative for an outflow.
 
    * 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 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 see on a bank register for the
-     current account.
-
+     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 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 see on a bank register for the current account.
 
    Transactions affecting this account's subaccounts will be included in
 the register if the accounts screen is in tree mode, or if it's in list
 mode but this account has subaccounts which are not shown due to a depth
-limit. In other words, the register always shows the transactions
-contributing to the balance shown on the accounts screen. Tree mode/list
-mode can be toggled with `t' here also.
+limit.  In other words, the register always shows the transactions
+contributing to the balance shown on the accounts screen.  Tree
+mode/list mode can be toggled with 't' here also.
 
-   `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
+   '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.)
 
-   `R' toggles real mode, in which virtual postings are ignored.
+   'R' toggles real mode, in which virtual postings are ignored.
 
-   `Z' toggles nonzero mode, in which only transactions posting a
+   'Z' toggles nonzero mode, in which only transactions posting a
 nonzero change are shown (hledger-ui shows zero items by default, unlike
 command-line hledger).
 
-   Press `right' (or `enter') to view the selected transaction in
+   Press 'right' (or 'enter') to view the selected transaction in
 detail.
 
 
@@ -437,11 +439,11 @@ 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
+   '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
-transactions appear in multiple account registers). The #N number
+transactions appear in multiple account registers).  The #N number
 preceding them is the transaction's position within the complete
 unfiltered journal, which is a more stable id (at least until the next
 reload).
@@ -453,8 +455,8 @@ File: hledger-ui.info,  Node: Error screen,  Prev: Transaction screen,  Up: SCRE
 ================
 
 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
+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.)
 
 
@@ -463,28 +465,27 @@ File: hledger-ui.info,  Node: ENVIRONMENT,  Next: FILES,  Prev: SCREENS,  Up: To
 4 ENVIRONMENT
 *************
 
-*COLUMNS* The screen width to use. Default: the full terminal width.
+*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.journal').
+   *LEDGER_FILE* The journal file path when not specified with '-f'.
+Default: '~/.hledger.journal' (on windows, perhaps
+'C:/Users/USER/.hledger.journal').
 
-   A typical value is `~/DIR/YYYY.journal', where DIR is a
-version-controlled finance directory and YYYY is the current year. Or
-`~/DIR/current.journal', where current.journal is a symbolic link to
+   A typical value is '~/DIR/YYYY.journal', where DIR is a
+version-controlled finance directory and YYYY is the current year.  Or
+'~/DIR/current.journal', where current.journal is a symbolic link to
 YYYY.journal.
 
-   On Mac computers, you can set this and other environment variables
-in a more thorough way that also affects applications started from the
-GUI (say, an Emacs dock icon). Eg on MacOS Catalina I have a
-`~/.MacOSX/environment.plist' file containing
-
+   On Mac computers, you can set this and other environment variables in
+a more thorough way that also affects applications started from the GUI
+(say, an Emacs dock icon).  Eg on MacOS Catalina I have a
+'~/.MacOSX/environment.plist' file containing
 
 {
   "LEDGER_FILE" : "~/finance/current.journal"
 }
 
-   To see the effect you may need to `killall Dock', or reboot.
+   To see the effect you may need to 'killall Dock', or reboot.
 
 
 File: hledger-ui.info,  Node: FILES,  Next: BUGS,  Prev: ENVIRONMENT,  Up: Top
@@ -493,9 +494,9 @@ File: hledger-ui.info,  Node: FILES,  Next: BUGS,  Prev: ENVIRONMENT,  Up: Top
 *******
 
 Reads data from one or more files in hledger journal, timeclock,
-timedot, or CSV format specified with `-f', or `$LEDGER_FILE', or
-`$HOME/.hledger.journal' (on windows, perhaps
-`C:/Users/USER/.hledger.journal').
+timedot, or CSV format specified with '-f', or '$LEDGER_FILE', or
+'$HOME/.hledger.journal' (on windows, perhaps
+'C:/Users/USER/.hledger.journal').
 
 
 File: hledger-ui.info,  Node: BUGS,  Prev: FILES,  Up: Top
@@ -503,18 +504,18 @@ File: hledger-ui.info,  Node: BUGS,  Prev: FILES,  Up: Top
 6 BUGS
 ******
 
-The need to precede options with `--' when invoked from hledger is
+The need to precede options with '--' when invoked from hledger is
 awkward.
 
-   `-f-' doesn't work (hledger-ui can't read from stdin).
+   '-f-' doesn't work (hledger-ui can't read from stdin).
 
-   `-V' affects only the accounts screen.
+   '-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
+   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 visual indication that this is in progress.
 
-   `--watch' is not yet fully robust. It works well for normal usage,
+   '--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. Symptoms
 include: unresponsive UI, periodic resetting of the cursor position,
@@ -523,31 +524,30 @@ and possibly a small but persistent build-up of CPU usage until the
 program is restarted.
 
    Also, if you are viewing files mounted from another machine,
-`--watch' requires that both machine clocks are roughly in step.
-
+'--watch' requires that both machine clocks are roughly in step.
 
 
 Tag Table:
-Node: Top82
-Node: OPTIONS1478
-Ref: #options1575
-Node: KEYS5970
-Ref: #keys6065
-Node: SCREENS10361
-Ref: #screens10466
-Node: Accounts screen10556
-Ref: #accounts-screen10684
-Node: Register screen12888
-Ref: #register-screen13043
-Node: Transaction screen15038
-Ref: #transaction-screen15196
-Node: Error screen16063
-Ref: #error-screen16185
-Node: ENVIRONMENT16427
-Ref: #environment16541
-Node: FILES17346
-Ref: #files17445
-Node: BUGS17658
-Ref: #bugs17735
+Node: Top71
+Node: OPTIONS1488
+Ref: #options1585
+Node: KEYS5986
+Ref: #keys6081
+Node: SCREENS10400
+Ref: #screens10505
+Node: Accounts screen10595
+Ref: #accounts-screen10723
+Node: Register screen12938
+Ref: #register-screen13093
+Node: Transaction screen15090
+Ref: #transaction-screen15248
+Node: Error screen16118
+Ref: #error-screen16240
+Node: ENVIRONMENT16484
+Ref: #environment16598
+Node: FILES17405
+Ref: #files17504
+Node: BUGS17717
+Ref: #bugs17794
 
 End Tag Table
diff --git a/hledger-web/hledger-web.info b/hledger-web/hledger-web.info
index b7aaea0ee..9044e8bd3 100644
--- a/hledger-web/hledger-web.info
+++ b/hledger-web/hledger-web.info
@@ -1,8 +1,7 @@
-This is hledger-web/hledger-web.info, produced by makeinfo version 4.8
-from stdin.
+This is hledger-web.info, produced by makeinfo version 6.7 from stdin.
 
 
-File: hledger-web.info,  Node: Top,  Up: (dir)
+File: hledger-web.info,  Node: Top,  Next: OPTIONS,  Up: (dir)
 
 hledger-web(1)
 **************
@@ -10,31 +9,32 @@ hledger-web(1)
 hledger-web is a web interface (WUI) for the hledger accounting tool.
 This manual is for hledger-web 1.21.99.
 
-   `hledger-web [OPTIONS]'
-`hledger web -- [OPTIONS]'
+   'hledger-web [OPTIONS]'
+'hledger web -- [OPTIONS]'
 
    hledger is a reliable, cross-platform set of programs for tracking
 money, time, or any other commodity, using double-entry accounting and a
-simple, editable file format. hledger is inspired by and largely
+simple, editable file format.  hledger is inspired by and largely
 compatible with ledger(1).
 
-   hledger-web is hledger's web interface. It starts a simple web
+   hledger-web is hledger's web interface.  It starts a simple web
 application for browsing and adding transactions, and optionally opens
-it in a web browser window if possible. It provides a more user-friendly
-UI than the hledger CLI or hledger-ui interface, showing more at once
-(accounts, the current account register, balance charts) and allowing
-history-aware data entry, interactive searching, and bookmarking.
+it in a web browser window if possible.  It provides a more
+user-friendly UI than the hledger CLI or hledger-ui interface, showing
+more at once (accounts, the current account register, balance charts)
+and allowing history-aware data entry, interactive searching, and
+bookmarking.
 
    hledger-web also lets you share a ledger with multiple users, or even
-the public web. There is no access control, so if you need that you
-should put it behind a suitable web proxy. As a small protection against
-data loss when running an unprotected instance, it writes a numbered
-backup of the main journal file (only ?) on every edit.
+the public web.  There is no access control, so if you need that you
+should put it behind a suitable web proxy.  As a small protection
+against data loss when running an unprotected instance, it writes a
+numbered backup of the main journal file (only ?)  on every edit.
 
    Like hledger, it reads data from one or more files in hledger
-journal, timeclock, timedot, or CSV format specified with `-f', or
-`$LEDGER_FILE', or `$HOME/.hledger.journal' (on windows, perhaps
-`C:/Users/USER/.hledger.journal'). For more about this see hledger(1).
+journal, timeclock, timedot, or CSV format specified with '-f', or
+'$LEDGER_FILE', or '$HOME/.hledger.journal' (on windows, perhaps
+'C:/Users/USER/.hledger.journal').  For more about this see hledger(1).
 
 * Menu:
 
@@ -54,165 +54,168 @@ File: hledger-web.info,  Node: OPTIONS,  Next: PERMISSIONS,  Prev: Top,  Up: Top
 *********
 
 Command-line options and arguments may be used to set an initial filter
-on the data. These filter options are not shown in the web UI, but it
+on the data.  These filter options are not shown in the web UI, but it
 will be applied in addition to any search query entered there.
 
-   Note: if invoking hledger-web as a hledger subcommand, write `--'
+   Note: if invoking hledger-web as a hledger subcommand, write '--'
 before options, as shown in the synopsis above.
 
-`--serve'
-     serve and log requests, don't browse or auto-exit
+'--serve'
+
+     serve and log requests, don't browse or auto-exit
+'--serve-api'
 
-`--serve-api'
      like -serve, but serve only the JSON web API, without the
      server-side web UI
+'--host=IPADDR'
 
-`--host=IPADDR'
      listen on this IP address (default: 127.0.0.1)
+'--port=PORT'
 
-`--port=PORT'
      listen on this TCP port (default: 5000)
+'--socket=SOCKETFILE'
 
-`--socket=SOCKETFILE'
      use a unix domain socket file to listen for requests instead of a
-     TCP socket. Implies `--serve'. It can only be used if the operating
-     system can provide this type of socket.
+     TCP socket.  Implies '--serve'.  It can only be used if the
+     operating system can provide this type of socket.
+'--base-url=URL'
 
-`--base-url=URL'
      set the base url (default: http://IPADDR:PORT). You would change
      this when sharing over the network, or integrating within a larger
      website.
+'--file-url=URL'
 
-`--file-url=URL'
-     set the static files url (default: BASEURL/static). hledger-web
+     set the static files url (default: BASEURL/static).  hledger-web
      normally serves static files itself, but if you wanted to serve
-     them from another server for efficiency, you would set the url
-     with this.
+     them from another server for efficiency, you would set the url with
+     this.
+'--capabilities=CAP[,CAP..]'
 
-`--capabilities=CAP[,CAP..]'
      enable the view, add, and/or manage capabilities (default:
      view,add)
+'--capabilities-header=HTTPHEADER'
 
-`--capabilities-header=HTTPHEADER'
      read capabilities to enable from a HTTP header, like
      X-Sandstorm-Permissions (default: disabled)
+'--test'
 
-`--test'
-     run hledger-web's tests and exit. hspec test runner args may
+     run hledger-web's tests and exit.  hspec test runner args may
      follow a -, eg: hledger-web -test - -help
 
    hledger input options:
 
-`-f FILE --file=FILE'
-     use a different input file. For stdin, use - (default:
-     `$LEDGER_FILE' or `$HOME/.hledger.journal')
+'-f FILE --file=FILE'
+
+     use a different input file.  For stdin, use - (default:
+     '$LEDGER_FILE' or '$HOME/.hledger.journal')
+'--rules-file=RULESFILE'
 
-`--rules-file=RULESFILE'
      Conversion rules file to use when reading CSV (default: FILE.rules)
+'--separator=CHAR'
 
-`--separator=CHAR'
      Field separator to expect when reading CSV (default: ',')
+'--alias=OLD=NEW'
 
-`--alias=OLD=NEW'
      rename accounts named OLD to NEW
+'--anon'
 
-`--anon'
      anonymize accounts and payees
+'--pivot FIELDNAME'
 
-`--pivot FIELDNAME'
      use some other field or tag for the account name
+'-I --ignore-assertions'
 
-`-I --ignore-assertions'
      disable balance assertion checks (note: does not disable balance
      assignments)
+'-s --strict'
 
-`-s --strict'
      do extra error checking (check that all posted accounts are
      declared)
 
    hledger reporting options:
 
-`-b --begin=DATE'
+'-b --begin=DATE'
+
      include postings/txns on or after this date (will be adjusted to
      preceding subperiod start when using a report interval)
+'-e --end=DATE'
 
-`-e --end=DATE'
      include postings/txns before this date (will be adjusted to
      following subperiod end when using a report interval)
+'-D --daily'
 
-`-D --daily'
      multiperiod/multicolumn report by day
+'-W --weekly'
 
-`-W --weekly'
      multiperiod/multicolumn report by week
+'-M --monthly'
 
-`-M --monthly'
      multiperiod/multicolumn report by month
+'-Q --quarterly'
 
-`-Q --quarterly'
      multiperiod/multicolumn report by quarter
+'-Y --yearly'
 
-`-Y --yearly'
      multiperiod/multicolumn report by year
+'-p --period=PERIODEXP'
 
-`-p --period=PERIODEXP'
      set start date, end date, and/or reporting interval all at once
      using period expressions syntax
+'--date2'
 
-`--date2'
      match the secondary date instead (see command help for other
      effects)
+'-U --unmarked'
 
-`-U --unmarked'
      include only unmarked postings/txns (can combine with -P or -C)
+'-P --pending'
 
-`-P --pending'
      include only pending postings/txns
+'-C --cleared'
 
-`-C --cleared'
      include only cleared postings/txns
+'-R --real'
 
-`-R --real'
      include only non-virtual postings
+'-NUM --depth=NUM'
 
-`-NUM --depth=NUM'
      hide/aggregate accounts or postings more than NUM levels deep
+'-E --empty'
 
-`-E --empty'
      show items with zero amount, normally hidden (and vice-versa in
      hledger-ui/hledger-web)
+'-B --cost'
 
-`-B --cost'
      convert amounts to their cost/selling amount at transaction time
+'-V --market'
 
-`-V --market'
      convert amounts to their market value in default valuation
      commodities
+'-X --exchange=COMM'
 
-`-X --exchange=COMM'
      convert amounts to their market value in commodity COMM
+'--value'
 
-`--value'
      convert amounts to cost or market value, more flexibly than
      -B/-V/-X
+'--infer-market-prices'
 
-`--infer-market-prices'
      use transaction prices (recorded with @ or @@) as additional market
      prices, as if they were P directives
+'--auto'
 
-`--auto'
      apply automated posting rules to modify transactions.
+'--forecast'
 
-`--forecast'
      generate future transactions from periodic transaction rules, for
-     the next 6 months or till report end date. In hledger-ui, also
+     the next 6 months or till report end date.  In hledger-ui, also
      make ordinary future transactions visible.
+'--color=WHEN (or --colour=WHEN)'
 
-`--color=WHEN (or --colour=WHEN)'
      Should color-supporting commands use ANSI color codes in text
      output.  'auto' (default): whenever stdout seems to be a
      color-supporting terminal.  'always' or 'yes': always, useful eg
-     when piping output into 'less -R'.  'never' or 'no': never.  A
+     when piping output into 'less -R'. 'never' or 'no': never.  A
      NO_COLOR environment variable overrides this.
 
    When a reporting option appears more than once in the command line,
@@ -222,62 +225,62 @@ the last one takes precedence.
 
    hledger help options:
 
-`-h --help'
+'-h --help'
+
      show general or COMMAND help
+'--man'
 
-`--man'
      show general or COMMAND user manual with man
+'--info'
 
-`--info'
      show general or COMMAND user manual with info
+'--version'
 
-`--version'
      show general or ADDONCMD version
+'--debug[=N]'
 
-`--debug[=N]'
      show debug output (levels 1-9, default: 1)
 
    A @FILE argument will be expanded to the contents of FILE, which
-should contain one command line option/argument per line. (To prevent
-this, insert a `--' argument before.)
+should contain one command line option/argument per line.  (To prevent
+this, insert a '--' argument before.)
 
    By default, hledger-web starts the web app in "transient mode" and
-also opens it in your default web browser if possible. In this mode the
+also opens it in your default web browser if possible.  In this mode the
 web app will keep running for as long as you have it open in a browser
 window, and will exit after two minutes of inactivity (no requests and
-no browser windows viewing it). With `--serve', it just runs the web
-app without exiting, and logs requests to the console. With
-`--serve-api', only the JSON web api (see below) is served, with the
+no browser windows viewing it).  With '--serve', it just runs the web
+app without exiting, and logs requests to the console.  With
+'--serve-api', only the JSON web api (see below) is served, with the
 usual HTML server-side web UI disabled.
 
    By default the server listens on IP address 127.0.0.1, accessible
-only to local requests. You can use `--host' to change this, eg `--host
+only to local requests.  You can use '--host' to change this, eg '--host
 0.0.0.0' to listen on all configured addresses.
 
-   Similarly, use `--port' to set a TCP port other than 5000, eg if you
+   Similarly, use '--port' to set a TCP port other than 5000, eg if you
 are running multiple hledger-web instances.
 
-   Both of these options are ignored when `--socket' is used. In this
-case, it creates an `AF_UNIX' socket file at the supplied path and uses
-that for communication. This is an alternative way of running multiple
-hledger-web instances behind a reverse proxy that handles
-authentication for different users. The path can be derived in a
-predictable way, eg by using the username within the path. As an
-example, `nginx' as reverse proxy can use the variable `$remote_user'
-to derive a path from the username used in a HTTP basic authentication.
-The following `proxy_pass' directive allows access to all `hledger-web'
-instances that created a socket in `/tmp/hledger/':
-
+   Both of these options are ignored when '--socket' is used.  In this
+case, it creates an 'AF_UNIX' socket file at the supplied path and uses
+that for communication.  This is an alternative way of running multiple
+hledger-web instances behind a reverse proxy that handles authentication
+for different users.  The path can be derived in a predictable way, eg
+by using the username within the path.  As an example, 'nginx' as
+reverse proxy can use the variable '$remote_user' to derive a path from
+the username used in a HTTP basic authentication.  The following
+'proxy_pass' directive allows access to all 'hledger-web' instances that
+created a socket in '/tmp/hledger/':
 
   proxy_pass http://unix:/tmp/hledger/${remote_user}.socket;
 
-   You can use `--base-url' to change the protocol, hostname, port and
+   You can use '--base-url' to change the protocol, hostname, port and
 path that appear in hyperlinks, useful eg for integrating hledger-web
-within a larger website. The default is `http://HOST:PORT/' using the
-server's configured host address and TCP port (or `http://HOST' if PORT
+within a larger website.  The default is 'http://HOST:PORT/' using the
+server's configured host address and TCP port (or 'http://HOST' if PORT
 is 80).
 
-   With `--file-url' you can set a different base url for static files,
+   With '--file-url' you can set a different base url for static files,
 eg for better caching or cookie-less serving on high performance
 websites.
 
@@ -292,32 +295,28 @@ journal and to add new transactions, but not to change existing data.
 
    You can restrict who can reach it by
 
-   * setting the IP address it listens on (see `--host' above). By
+   * setting the IP address it listens on (see '--host' above).  By
      default it listens on 127.0.0.1, accessible to all users on the
      local machine.
-
    * putting it behind an authenticating proxy, using eg apache or nginx
-
    * custom firewall rules
 
    You can restrict what the users who reach it can do, by
 
-   * using the `--capabilities=CAP[,CAP..]' flag when you start it,
-     enabling one or more of the following capabilities. The default
-     value is `view,add':
-        * `view' - allows viewing the journal file and all included
+   * using the '--capabilities=CAP[,CAP..]' flag when you start it,
+     enabling one or more of the following capabilities.  The default
+     value is 'view,add':
+        * 'view' - allows viewing the journal file and all included
           files
-
-        * `add' - allows adding new transactions to the main journal
+        * 'add' - allows adding new transactions to the main journal
           file
-
-        * `manage' - allows editing, uploading or downloading the main
+        * 'manage' - allows editing, uploading or downloading the main
           or included files
 
-   * using the `--capabilities-header=HTTPHEADER' flag to specify a HTTP
-     header from which it will read capabilities to enable. hledger-web
+   * using the '--capabilities-header=HTTPHEADER' flag to specify a HTTP
+     header from which it will read capabilities to enable.  hledger-web
      on Sandstorm uses the X-Sandstorm-Permissions header to integrate
-     with Sandstorm's permissions. This is disabled by default.
+     with Sandstorm's permissions.  This is disabled by default.
 
 
 File: hledger-web.info,  Node: EDITING UPLOADING DOWNLOADING,  Next: RELOADING,  Prev: PERMISSIONS,  Up: Top
@@ -325,8 +324,8 @@ File: hledger-web.info,  Node: EDITING UPLOADING DOWNLOADING,  Next: RELOADING,
 3 EDITING, UPLOADING, DOWNLOADING
 *********************************
 
-If you enable the `manage' capability mentioned above, you'll see a new
-"spanner" button to the right of the search form. Clicking this will
+If you enable the 'manage' capability mentioned above, you'll see a new
+"spanner" button to the right of the search form.  Clicking this will
 let you edit, upload, or download the journal file or any files it
 includes.
 
@@ -335,13 +334,13 @@ visitor) can alter or wipe the data files.
 
    Normally whenever a file is changed in this way, hledger-web saves a
 numbered backup (assuming file permissions allow it, the disk is not
-full, etc.) hledger-web is not aware of version control systems,
+full, etc.)  hledger-web is not aware of version control systems,
 currently; if you use one, you'll have to arrange to commit the changes
 yourself (eg with a cron job or a file watcher like entr).
 
    Changes which would leave the journal file(s) unparseable or
 non-valid (eg with failing balance assertions) are prevented.
-(Probably. This needs re-testing.)
+(Probably.  This needs re-testing.)
 
 
 File: hledger-web.info,  Node: RELOADING,  Next: JSON API,  Prev: EDITING UPLOADING DOWNLOADING,  Up: Top
@@ -351,7 +350,7 @@ File: hledger-web.info,  Node: RELOADING,  Next: JSON API,  Prev: EDITING UPLOAD
 
 hledger-web detects changes made to the files by other means (eg if you
 edit it directly, outside of hledger-web), and it will show the new data
-when you reload the page or navigate to a new page. If a change makes a
+when you reload the page or navigate to a new page.  If a change makes a
 file unparseable, hledger-web will display an error message until the
 file has been fixed.
 
@@ -365,16 +364,14 @@ File: hledger-web.info,  Node: JSON API,  Next: ENVIRONMENT,  Prev: RELOADING,
 **********
 
 In addition to the web UI, hledger-web also serves a JSON API that can
-be used to get data or add new transactions. If you want the JSON API
-only, you can use the `--serve-api' flag. Eg:
-
+be used to get data or add new transactions.  If you want the JSON API
+only, you can use the '--serve-api' flag.  Eg:
 
 $ hledger-web -f examples/sample.journal --serve-api
 ...
 
    You can get JSON data from these routes:
 
-
 /version
 /accountnames
 /transactions
@@ -387,7 +384,6 @@ $ hledger-web -f examples/sample.journal --serve-api
 command).  (hledger-web's JSON does not include newlines, here we use
 python to prettify it):
 
-
 $ curl -s http://127.0.0.1:5000/accountnames | python -m json.tool
 [
     "assets",
@@ -407,7 +403,6 @@ $ curl -s http://127.0.0.1:5000/accountnames | python -m json.tool
 
    Or all transactions:
 
-
 $ curl -s http://127.0.0.1:5000/transactions | python -m json.tool
 [
     {
@@ -429,25 +424,24 @@ $ curl -s http://127.0.0.1:5000/transactions | python -m json.tool
 
    Most of the JSON corresponds to hledger's data types; for details of
 what the fields mean, see the Hledger.Data.Json haddock docs and click
-on the various data types, eg Transaction. And for a higher level
+on the various data types, eg Transaction.  And for a higher level
 understanding, see the journal manual.
 
    In some cases there is outer JSON corresponding to a "Report" type.
-To understand that, go to the Hledger.Web.Handler.MiscR haddock and
-look at the source for the appropriate handler to see what it returns.
-Eg for `/accounttransactions' it's getAccounttransactionsR, returning a
-"`accountTransactionsReport ...'". Looking up the haddock for that we
+To understand that, go to the Hledger.Web.Handler.MiscR haddock and look
+at the source for the appropriate handler to see what it returns.  Eg
+for '/accounttransactions' it's getAccounttransactionsR, returning a
+"'accountTransactionsReport ...'".  Looking up the haddock for that we
 can see that /accounttransactions returns an AccountTransactionsReport,
 which consists of a report title and a list of
 AccountTransactionsReportItem (etc).
 
    You can add a new transaction to the journal with a PUT request to
-`/add', if hledger-web was started with the `add' capability (enabled
-by default). The payload must be the full, exact JSON representation of
-a hledger transaction (partial data won't do). You can get sample JSON
-from hledger-web's `/transactions' or `/accounttransactions', or you
-can export it with hledger-lib, eg like so:
-
+'/add', if hledger-web was started with the 'add' capability (enabled by
+default).  The payload must be the full, exact JSON representation of a
+hledger transaction (partial data won't do).  You can get sample JSON
+from hledger-web's '/transactions' or '/accounttransactions', or you can
+export it with hledger-lib, eg like so:
 
 .../hledger$ stack ghci hledger-lib
 >>> writeJsonFile "txn.json" (head $ jtxns samplejournal)
@@ -456,7 +450,6 @@ can export it with hledger-lib, eg like so:
    Here's how it looks as of hledger-1.17 (remember, this JSON
 corresponds to hledger's Transaction and related data types):
 
-
 {
     "tcomment": "",
     "tpostings": [
@@ -543,10 +536,9 @@ corresponds to hledger's Transaction and related data types):
     "tstatus": "Unmarked"
 }
 
-   And here's how to test adding it with curl. This should add a new
+   And here's how to test adding it with curl.  This should add a new
 entry to your journal:
 
-
 $ curl http://127.0.0.1:5000/add -X PUT -H 'Content-Type: application/json' --data-binary @txn.json
 
 
@@ -555,26 +547,25 @@ File: hledger-web.info,  Node: ENVIRONMENT,  Next: FILES,  Prev: JSON API,  Up:
 6 ENVIRONMENT
 *************
 
-*LEDGER_FILE* The journal file path when not specified with `-f'.
-Default: `~/.hledger.journal' (on windows, perhaps
-`C:/Users/USER/.hledger.journal').
+*LEDGER_FILE* The journal file path when not specified with '-f'.
+Default: '~/.hledger.journal' (on windows, perhaps
+'C:/Users/USER/.hledger.journal').
 
-   A typical value is `~/DIR/YYYY.journal', where DIR is a
-version-controlled finance directory and YYYY is the current year. Or
-`~/DIR/current.journal', where current.journal is a symbolic link to
+   A typical value is '~/DIR/YYYY.journal', where DIR is a
+version-controlled finance directory and YYYY is the current year.  Or
+'~/DIR/current.journal', where current.journal is a symbolic link to
 YYYY.journal.
 
-   On Mac computers, you can set this and other environment variables
-in a more thorough way that also affects applications started from the
-GUI (say, an Emacs dock icon). Eg on MacOS Catalina I have a
-`~/.MacOSX/environment.plist' file containing
-
+   On Mac computers, you can set this and other environment variables in
+a more thorough way that also affects applications started from the GUI
+(say, an Emacs dock icon).  Eg on MacOS Catalina I have a
+'~/.MacOSX/environment.plist' file containing
 
 {
   "LEDGER_FILE" : "~/finance/current.journal"
 }
 
-   To see the effect you may need to `killall Dock', or reboot.
+   To see the effect you may need to 'killall Dock', or reboot.
 
 
 File: hledger-web.info,  Node: FILES,  Next: BUGS,  Prev: ENVIRONMENT,  Up: Top
@@ -583,9 +574,9 @@ File: hledger-web.info,  Node: FILES,  Next: BUGS,  Prev: ENVIRONMENT,  Up: Top
 *******
 
 Reads data from one or more files in hledger journal, timeclock,
-timedot, or CSV format specified with `-f', or `$LEDGER_FILE', or
-`$HOME/.hledger.journal' (on windows, perhaps
-`C:/Users/USER/.hledger.journal').
+timedot, or CSV format specified with '-f', or '$LEDGER_FILE', or
+'$HOME/.hledger.journal' (on windows, perhaps
+'C:/Users/USER/.hledger.journal').
 
 
 File: hledger-web.info,  Node: BUGS,  Prev: FILES,  Up: Top
@@ -593,10 +584,10 @@ File: hledger-web.info,  Node: BUGS,  Prev: FILES,  Up: Top
 8 BUGS
 ******
 
-The need to precede options with `--' when invoked from hledger is
+The need to precede options with '--' when invoked from hledger is
 awkward.
 
-   `-f-' doesn't work (hledger-web can't read from stdin).
+   '-f-' doesn't work (hledger-web can't read from stdin).
 
    Query arguments and some hledger options are ignored.
 
@@ -604,25 +595,24 @@ awkward.
 
    Does not work well on small screens.
 
-
 
 Tag Table:
-Node: Top84
-Node: OPTIONS1727
-Ref: #options1832
-Node: PERMISSIONS9245
-Ref: #permissions9384
-Node: EDITING UPLOADING DOWNLOADING10596
-Ref: #editing-uploading-downloading10777
-Node: RELOADING11608
-Ref: #reloading11742
-Node: JSON API12174
-Ref: #json-api12288
-Node: ENVIRONMENT17777
-Ref: #environment17893
-Node: FILES18625
-Ref: #files18725
-Node: BUGS18938
-Ref: #bugs19016
+Node: Top72
+Node: OPTIONS1738
+Ref: #options1843
+Node: PERMISSIONS9276
+Ref: #permissions9415
+Node: EDITING UPLOADING DOWNLOADING10627
+Ref: #editing-uploading-downloading10808
+Node: RELOADING11642
+Ref: #reloading11776
+Node: JSON API12209
+Ref: #json-api12323
+Node: ENVIRONMENT17813
+Ref: #environment17929
+Node: FILES18662
+Ref: #files18762
+Node: BUGS18975
+Ref: #bugs19053
 
 End Tag Table
diff --git a/hledger/hledger.1 b/hledger/hledger.1
index ef1e2ebf0..bb0cf1973 100644
--- a/hledger/hledger.1
+++ b/hledger/hledger.1
@@ -3621,9 +3621,10 @@ commands, including \f[C]check\f[R]:
 \f[B]parseable\f[R] - data files are well-formed and can be successfully
 parsed
 .IP \[bu] 2
-\f[B]autobalanced\f[R] - all transactions are balanced, inferring
-missing amounts where necessary, and possibly converting commodities
-using transaction prices or automatically-inferred transaction prices
+\f[B]balancedwithautoconversion\f[R] - all transactions are balanced,
+inferring missing amounts where necessary, and possibly converting
+commodities using transaction prices or automatically-inferred
+transaction prices
 .IP \[bu] 2
 \f[B]assertions\f[R] - all balance assertions in the journal are
 passing.
@@ -3640,6 +3641,9 @@ Or, they can be run by giving their names as arguments to
 declared
 .IP \[bu] 2
 \f[B]commodities\f[R] - all commodity symbols used have been declared
+.IP \[bu] 2
+\f[B]balancednoautoconversion\f[R] - transactions are balanced, possibly
+using explicit transaction prices but not inferred ones
 .SS Other checks
 .PP
 These checks can be run only by giving their names as arguments to
@@ -6743,7 +6747,7 @@ See also Rewrite account names.
 To set an account alias, use the \f[C]alias\f[R] directive in your
 journal file.
 This affects all subsequent journal entries in the current file or its
-included files.
+included files (but note: not sibling or parent files).
 The spaces around the = are optional:
 .IP
 .nf
@@ -7730,21 +7734,26 @@ below), a default account name will be chosen (like
 \[dq]expenses:unknown\[dq] or \[dq]income:unknown\[dq]).
 .SS amount
 .PP
-\f[C]amountN\f[R] sets posting N\[aq]s amount.
-If the CSV uses separate fields for inflows and outflows, you can use
-\f[C]amountN-in\f[R] and \f[C]amountN-out\f[R] instead.
+\f[C]amountN\f[R] sets the Nth posting\[aq]s amount.
 By assigning to \f[C]amount1\f[R], \f[C]amount2\f[R], ...
 etc.
-you can generate anywhere from 0 to 99 postings.
+you can generate up to 99 postings.
 .PP
-There is also an older, unnumbered form of these names, suitable for
-2-posting transactions, which sets both posting 1\[aq]s and (negated)
-posting 2\[aq]s amount: \f[C]amount\f[R], or \f[C]amount-in\f[R] and
-\f[C]amount-out\f[R].
-This is still supported because it keeps pre-hledger-1.17 csv rules
-files working, and because it can be more succinct, and because it
-converts posting 2\[aq]s amount to cost if there\[aq]s a transaction
-price, which can be useful.
+If the CSV uses separate fields for debits and credits (inflows and
+outflows), you can use \f[C]amountN-in\f[R] and \f[C]amountN-out\f[R]
+instead.
+Note hledger assumes both of these fields are unsigned, and will
+automatically negate the \[dq]-out\[dq] value.
+If the fields are signed, see \[dq]Setting amounts\[dq] below.
+.PP
+There is also an unnumbered form of these names: \f[C]amount\f[R], or
+\f[C]amount-in\f[R] and \f[C]amount-out\f[R].
+This is supported to keep pre-hledger-1.17 CSV rules files working (and
+for occasional convenience).
+It is suitable only for two-posting transactions; it sets both posting
+1\[aq]s and posting 2\[aq]s amount.
+Posting 2\[aq]s amount will be negated, and also converted to cost if
+there\[aq]s a transaction price.
 .PP
 If you have an existing rules file using the unnumbered form, you might
 want to use the numbered form in certain conditional blocks, without
@@ -8307,40 +8316,47 @@ Assign (via a fields list or a field assignment) to \f[C]amountN\f[R].
 This sets the Nth posting\[aq]s amount.
 N is usually 1 or 2 but can go up to 99.
 .IP "2." 3
-\f[B]If the CSV has separate Debit and Credit amount fields:\f[R]
+\f[B]If the CSV has separate amount fields for debit & credit (in &
+out):\f[R]
+.PD 0
+.P
+.PD
+.RS 4
+.IP "a." 3
+\f[B]If both fields are unsigned:\f[R]
 .PD 0
 .P
 .PD
 Assign to \f[C]amountN-in\f[R] and \f[C]amountN-out\f[R].
 This sets posting N\[aq]s amount to whichever of these has a non-zero
-value, guessing an appropriate sign.
-.RS 4
-.IP \[bu] 2
-\f[B]If hledger guesses the wrong sign:\f[R]
+value, and negates the \[dq]-out\[dq] value.
+.IP "b." 3
+\f[B]If either field is signed (can contain a minus sign):\f[R]
 .PD 0
 .P
 .PD
-Prepend a minus sign to flip it.
-Eg:
-.RS 2
+Use a conditional rule to flip the sign (of non-empty values).
+Since hledger always negates amountN-out, if it was already negative, we
+must undo that by negating once more (but only if the field is
+non-empty):
 .IP
 .nf
 \f[C]
-fields date, description, amount-in, amount-out
-amount-out -%amount-out
+fields date, description, amount1-in, amount1-out
+if %amount1-out [1-9]
+ amount1-out -%amount1-out
 \f[R]
 .fi
-.RE
-.IP \[bu] 2
-\f[B]If both fields contain a non-zero value:\f[R]
+.IP "c." 3
+\f[B]If both fields, or neither field, can contain a non-zero
+value:\f[R]
 .PD 0
 .P
 .PD
-The \f[C]amountN-in\f[R]/\f[C]amountN-out\f[R] rules require that each
-CSV record has a non-zero value in exactly one of the two fields, so
-that hledger knows which to choose.
-So these would all be rejected:
-.RS 2
+hledger normally expects exactly one of the fields to have a non-zero
+value.
+Eg, the \f[C]amountN-in\f[R]/\f[C]amountN-out\f[R] rules would reject
+value pairs like these:
 .IP
 .nf
 \f[C]
@@ -8350,9 +8366,10 @@ So these would all be rejected:
 \f[R]
 .fi
 .PP
-If your CSV has amount values like this, use conditional rules instead.
-For example, to make hledger to choose the value containing non-zero
-digits:
+So, use smarter conditional rules to set the amount from the appropriate
+field.
+Eg, these rules would make it use only the value containing non-zero
+digits, handling the above:
 .IP
 .nf
 \f[C]
@@ -8364,18 +8381,15 @@ if %out [1-9]
 \f[R]
 .fi
 .RE
-.RE
 .IP "3." 3
-\f[B]Using the old numberless syntax:\f[R]
+\f[B]If you are stuck with hledger <1.17, or you want posting 2\[aq]s
+amount converted to cost:\f[R]
 .PD 0
 .P
 .PD
 Assign to \f[C]amount\f[R] (or to \f[C]amount-in\f[R] and
 \f[C]amount-out\f[R]).
-This sets posting 1\[aq]s and posting 2\[aq]s amounts (and converts
-posting 2\[aq]s amount to cost).
-This is supported for backwards compatibility (and occasional
-convenience).
+(The old numberless syntax, which sets amount1 and amount2.)
 .IP "4." 3
 \f[B]If the CSV has the balance instead of the transaction amount:\f[R]
 .PD 0
diff --git a/hledger/hledger.info b/hledger/hledger.info
index 5e83daa2f..804fe7491 100644
--- a/hledger/hledger.info
+++ b/hledger/hledger.info
@@ -1,59 +1,57 @@
-This is hledger/hledger.info, produced by makeinfo version 4.8 from
-stdin.
+This is hledger.info, produced by makeinfo version 6.7 from stdin.
 
 
-File: hledger.info,  Node: Top,  Up: (dir)
+File: hledger.info,  Node: Top,  Next: OPTIONS,  Up: (dir)
 
 hledger(1)
 **********
 
 This is the command-line interface (CLI) for the hledger accounting
-tool. Here we also describe hledger's concepts and file formats. This
+tool.  Here we also describe hledger's concepts and file formats.  This
 manual is for hledger 1.21.99.
 
-   `hledger'
+   'hledger'
 
-   `hledger [-f FILE] COMMAND [OPTIONS] [ARGS]'
+   'hledger [-f FILE] COMMAND [OPTIONS] [ARGS]'
 
-   `hledger [-f FILE] ADDONCMD -- [OPTIONS] [ARGS]'
+   'hledger [-f FILE] ADDONCMD -- [OPTIONS] [ARGS]'
 
    hledger is a reliable, cross-platform set of programs for tracking
 money, time, or any other commodity, using double-entry accounting and a
-simple, editable file format. hledger is inspired by and largely
+simple, editable file format.  hledger is inspired by and largely
 compatible with ledger(1).
 
    The basic function of the hledger CLI is to read a plain text file
 describing financial transactions (in accounting terms, a general
 journal) and print useful reports on standard output, or export them as
 CSV. hledger can also read some other file formats such as CSV files,
-translating them to journal format. Additionally, hledger lists other
+translating them to journal format.  Additionally, hledger lists other
 hledger-* executables found in the user's $PATH and can invoke them as
 subcommands.
 
    hledger reads data from one or more files in hledger journal,
-timeclock, timedot, or CSV format specified with `-f', or
-`$LEDGER_FILE', or `$HOME/.hledger.journal' (on windows, perhaps
-`C:/Users/USER/.hledger.journal'). If using `$LEDGER_FILE', note this
-must be a real environment variable, not a shell variable. You can
-specify standard input with `-f-'.
+timeclock, timedot, or CSV format specified with '-f', or
+'$LEDGER_FILE', or '$HOME/.hledger.journal' (on windows, perhaps
+'C:/Users/USER/.hledger.journal').  If using '$LEDGER_FILE', note this
+must be a real environment variable, not a shell variable.  You can
+specify standard input with '-f-'.
 
    Transactions are dated movements of money between two (or more) named
 accounts, and are recorded with journal entries like this:
 
-
 2015/10/16 bought food
  expenses:food          $10
  assets:cash
 
    Most users use a text editor to edit the journal, usually with an
-editor mode such as ledger-mode for added convenience. hledger's
+editor mode such as ledger-mode for added convenience.  hledger's
 interactive add command is another way to record new transactions.
 hledger never changes existing transactions.
 
    To get started, you can either save some entries like the above in
-`~/.hledger.journal', or run `hledger add' and follow the prompts. Then
-try some commands like `hledger print' or `hledger balance'. Run
-`hledger' with no arguments for a list of commands.
+'~/.hledger.journal', or run 'hledger add' and follow the prompts.  Then
+try some commands like 'hledger print' or 'hledger balance'.  Run
+'hledger' with no arguments for a list of commands.
 
 * Menu:
 
@@ -98,137 +96,140 @@ File: hledger.info,  Node: General options,  Next: Command options,  Up: OPTIONS
 ===================
 
 To see general usage help, including general options which are supported
-by most hledger commands, run `hledger -h'.
+by most hledger commands, run 'hledger -h'.
 
    General help options:
 
-`-h --help'
+'-h --help'
+
      show general or COMMAND help
+'--man'
 
-`--man'
      show general or COMMAND user manual with man
+'--info'
 
-`--info'
      show general or COMMAND user manual with info
+'--version'
 
-`--version'
      show general or ADDONCMD version
+'--debug[=N]'
 
-`--debug[=N]'
      show debug output (levels 1-9, default: 1)
 
    General input options:
 
-`-f FILE --file=FILE'
-     use a different input file. For stdin, use - (default:
-     `$LEDGER_FILE' or `$HOME/.hledger.journal')
+'-f FILE --file=FILE'
+
+     use a different input file.  For stdin, use - (default:
+     '$LEDGER_FILE' or '$HOME/.hledger.journal')
+'--rules-file=RULESFILE'
 
-`--rules-file=RULESFILE'
      Conversion rules file to use when reading CSV (default: FILE.rules)
+'--separator=CHAR'
 
-`--separator=CHAR'
      Field separator to expect when reading CSV (default: ',')
+'--alias=OLD=NEW'
 
-`--alias=OLD=NEW'
      rename accounts named OLD to NEW
+'--anon'
 
-`--anon'
      anonymize accounts and payees
+'--pivot FIELDNAME'
 
-`--pivot FIELDNAME'
      use some other field or tag for the account name
+'-I --ignore-assertions'
 
-`-I --ignore-assertions'
      disable balance assertion checks (note: does not disable balance
      assignments)
+'-s --strict'
 
-`-s --strict'
      do extra error checking (check that all posted accounts are
      declared)
 
    General reporting options:
 
-`-b --begin=DATE'
+'-b --begin=DATE'
+
      include postings/txns on or after this date (will be adjusted to
      preceding subperiod start when using a report interval)
+'-e --end=DATE'
 
-`-e --end=DATE'
      include postings/txns before this date (will be adjusted to
      following subperiod end when using a report interval)
+'-D --daily'
 
-`-D --daily'
      multiperiod/multicolumn report by day
+'-W --weekly'
 
-`-W --weekly'
      multiperiod/multicolumn report by week
+'-M --monthly'
 
-`-M --monthly'
      multiperiod/multicolumn report by month
+'-Q --quarterly'
 
-`-Q --quarterly'
      multiperiod/multicolumn report by quarter
+'-Y --yearly'
 
-`-Y --yearly'
      multiperiod/multicolumn report by year
+'-p --period=PERIODEXP'
 
-`-p --period=PERIODEXP'
      set start date, end date, and/or reporting interval all at once
      using period expressions syntax
+'--date2'
 
-`--date2'
      match the secondary date instead (see command help for other
      effects)
+'-U --unmarked'
 
-`-U --unmarked'
      include only unmarked postings/txns (can combine with -P or -C)
+'-P --pending'
 
-`-P --pending'
      include only pending postings/txns
+'-C --cleared'
 
-`-C --cleared'
      include only cleared postings/txns
+'-R --real'
 
-`-R --real'
      include only non-virtual postings
+'-NUM --depth=NUM'
 
-`-NUM --depth=NUM'
      hide/aggregate accounts or postings more than NUM levels deep
+'-E --empty'
 
-`-E --empty'
      show items with zero amount, normally hidden (and vice-versa in
      hledger-ui/hledger-web)
+'-B --cost'
 
-`-B --cost'
      convert amounts to their cost/selling amount at transaction time
+'-V --market'
 
-`-V --market'
      convert amounts to their market value in default valuation
      commodities
+'-X --exchange=COMM'
 
-`-X --exchange=COMM'
      convert amounts to their market value in commodity COMM
+'--value'
 
-`--value'
      convert amounts to cost or market value, more flexibly than
      -B/-V/-X
+'--infer-market-prices'
 
-`--infer-market-prices'
      use transaction prices (recorded with @ or @@) as additional market
      prices, as if they were P directives
+'--auto'
 
-`--auto'
      apply automated posting rules to modify transactions.
+'--forecast'
 
-`--forecast'
      generate future transactions from periodic transaction rules, for
-     the next 6 months or till report end date. In hledger-ui, also
+     the next 6 months or till report end date.  In hledger-ui, also
      make ordinary future transactions visible.
+'--color=WHEN (or --colour=WHEN)'
 
-`--color=WHEN (or --colour=WHEN)'
      Should color-supporting commands use ANSI color codes in text
      output.  'auto' (default): whenever stdout seems to be a
      color-supporting terminal.  'always' or 'yes': always, useful eg
-     when piping output into 'less -R'.  'never' or 'no': never.  A
+     when piping output into 'less -R'. 'never' or 'no': never.  A
      NO_COLOR environment variable overrides this.
 
    When a reporting option appears more than once in the command line,
@@ -243,14 +244,14 @@ File: hledger.info,  Node: Command options,  Next: Command arguments,  Prev: Gen
 ===================
 
 To see options for a particular command, including command-specific
-options, run: `hledger COMMAND -h'.
+options, run: 'hledger COMMAND -h'.
 
    Command-specific options must be written after the command name, eg:
-`hledger print -x'.
+'hledger print -x'.
 
    Additionally, if the command is an add-on, you may need to put its
-options after a double-hyphen, eg: `hledger ui -- --watch'. Or, you can
-run the add-on executable directly: `hledger-ui --watch'.
+options after a double-hyphen, eg: 'hledger ui -- --watch'.  Or, you can
+run the add-on executable directly: 'hledger-ui --watch'.
 
 
 File: hledger.info,  Node: Command arguments,  Next: Special characters,  Prev: Command options,  Up: OPTIONS
@@ -262,36 +263,32 @@ Most hledger commands accept arguments after the command name, which are
 often a query, filtering the data in some way.
 
    You can save a set of command line options/arguments in a file, and
-then reuse them by writing `@FILENAME' as a command line argument. Eg:
-`hledger bal @foo.args'. (To prevent this, eg if you have an argument
-that begins with a literal `@', precede it with `--', eg: `hledger bal
+then reuse them by writing '@FILENAME' as a command line argument.  Eg:
+'hledger bal @foo.args'.  (To prevent this, eg if you have an argument
+that begins with a literal '@', precede it with '--', eg: 'hledger bal
 -- @ARG').
 
    Inside the argument file, each line should contain just one option or
-argument. Avoid the use of spaces, except inside quotes (or you'll see a
-confusing error). Between a flag and its argument, use = (or nothing).
-Bad:
-
+argument.  Avoid the use of spaces, except inside quotes (or you'll see
+a confusing error).  Between a flag and its argument, use = (or
+nothing).  Bad:
 
 assets depth:2
 -X USD
 
    Good:
 
-
 assets
 depth:2
 -X=USD
 
    For special characters (see below), use one less level of quoting
-than you would at the command prompt. Bad:
-
+than you would at the command prompt.  Bad:
 
 -X"$"
 
    Good:
 
-
 -X$
 
    See also: Save frequently used options.
@@ -316,17 +313,15 @@ File: hledger.info,  Node: Single escaping shell metacharacters,  Next: Double e
 --------------------------------------------
 
 In shell command lines, characters significant to your shell - such as
-spaces, `<', `>', `(', `)', `|', `$' and `\' - should be
-"shell-escaped" if you want hledger to see them.  This is done by
-enclosing them in single or double quotes, or by writing a backslash
-before them. Eg to match an account name containing a space:
-
+spaces, '<', '>', '(', ')', '|', '$' and '\' - should be "shell-escaped"
+if you want hledger to see them.  This is done by enclosing them in
+single or double quotes, or by writing a backslash before them.  Eg to
+match an account name containing a space:
 
 $ hledger register 'credit card'
 
    or:
 
-
 $ hledger register credit\ card
 
 
@@ -336,19 +331,17 @@ File: hledger.info,  Node: Double escaping regular expression metacharacters,  N
 ---------------------------------------------------------
 
 Characters significant in regular expressions (described below) - such
-as `.', `^', `$', `[', `]', `(', `)', `|', and `\' - may need to be
+as '.', '^', '$', '[', ']', '(', ')', '|', and '\' - may need to be
 "regex-escaped" if you don't want them to be interpreted by hledger's
-regular expression engine. This is done by writing backslashes before
+regular expression engine.  This is done by writing backslashes before
 them, but since backslash is typically also a shell metacharacter, both
-shell-escaping and regex-escaping will be needed. Eg to match a literal
-`$' sign while using the bash shell:
-
+shell-escaping and regex-escaping will be needed.  Eg to match a literal
+'$' sign while using the bash shell:
 
 $ hledger balance cur:'\$'
 
    or:
 
-
 $ hledger balance cur:\\$
 
 
@@ -360,28 +353,25 @@ File: hledger.info,  Node: Triple escaping for add-on commands,  Next: Less esca
 When you use hledger to run an external add-on command (described
 below), one level of shell-escaping is lost from any options or
 arguments intended for by the add-on command, so those need an extra
-level of shell-escaping. Eg to match a literal `$' sign while using the
-bash shell and running an add-on command (`ui'):
-
+level of shell-escaping.  Eg to match a literal '$' sign while using the
+bash shell and running an add-on command ('ui'):
 
 $ hledger ui cur:'\\$'
 
    or:
 
-
 $ hledger ui cur:\\\\$
 
    If you wondered why _four_ backslashes, perhaps this helps:
 
-unescaped:        `$'
-escaped:          `\$'
-double-escaped:   `\\$'
-triple-escaped:   `\\\\$'
+unescaped:        '$'
+escaped:          '\$'
+double-escaped:   '\\$'
+triple-escaped:   '\\\\$'
 
    Or, you can avoid the extra escaping by running the add-on executable
 directly:
 
-
 $ hledger-ui cur:\\$
 
 
@@ -392,14 +382,11 @@ File: hledger.info,  Node: Less escaping,  Prev: Triple escaping for add-on comm
 
 Options and arguments are sometimes used in places other than the shell
 command line, where shell-escaping is not needed, so there you should
-use one less level of escaping. Those places include:
+use one less level of escaping.  Those places include:
 
    * an @argumentfile
-
    * hledger-ui's filter field
-
    * hledger-web's search form
-
    * GHCI's prompt (used by developers).
 
 
@@ -417,13 +404,12 @@ hledger is expected to handle non-ascii characters correctly:
    * they should be displayed correctly by all hledger tools, and
      on-screen alignment should be preserved.
 
-
-   This requires a well-configured environment. Here are some tips:
+   This requires a well-configured environment.  Here are some tips:
 
    * A system locale must be configured, and it must be one that can
-     decode the characters being used. In bash, you can set a locale
-     like this: `export LANG=en_US.UTF-8'. There are some more details
-     in Troubleshooting. This step is essential - without it, hledger
+     decode the characters being used.  In bash, you can set a locale
+     like this: 'export LANG=en_US.UTF-8'.  There are some more details
+     in Troubleshooting.  This step is essential - without it, hledger
      will quit on encountering a non-ascii character (as with all
      GHC-compiled programs).
 
@@ -437,12 +423,11 @@ hledger is expected to handle non-ascii characters correctly:
      double width (for report alignment)
 
    * on Windows, for best results you should run hledger in the same
-     kind of environment in which it was built. Eg hledger built in the
+     kind of environment in which it was built.  Eg hledger built in the
      standard CMD.EXE environment (like the binaries on our download
      page) might show display problems when run in a cygwin or msys
      terminal, and vice versa.  (See eg #961).
 
-
 
 File: hledger.info,  Node: Regular expressions,  Prev: Unicode characters,  Up: OPTIONS
 
@@ -452,49 +437,41 @@ File: hledger.info,  Node: Regular expressions,  Prev: Unicode characters,  Up:
 hledger uses regular expressions in a number of places:
 
    * query terms, on the command line and in the hledger-web search
-     form: `REGEX', `desc:REGEX', `cur:REGEX', `tag:...=REGEX'
+     form: 'REGEX', 'desc:REGEX', 'cur:REGEX', 'tag:...=REGEX'
+   * CSV rules conditional blocks: 'if REGEX ...'
+   * account alias directives and options: 'alias /REGEX/ =
+     REPLACEMENT', '--alias /REGEX/=REPLACEMENT'
 
-   * CSV rules conditional blocks: `if REGEX ...'
-
-   * account alias directives and options: `alias /REGEX/ =
-     REPLACEMENT', `--alias /REGEX/=REPLACEMENT'
-
-   hledger's regular expressions come from the regex-tdfa library. If
+   hledger's regular expressions come from the regex-tdfa library.  If
 they're not doing what you expect, it's important to know exactly what
 they support:
 
   1. they are case insensitive
-
   2. they are infix matching (they do not need to match the entire thing
      being matched)
-
   3. they are POSIX ERE (extended regular expressions)
-
-  4. they also support GNU word boundaries (`\b', `\B', `\<', `\>')
-
-  5. they do not support backreferences; if you write `\1', it will
-     match the digit `1'. Except when doing text replacement, eg in
+  4. they also support GNU word boundaries ('\b', '\B', '\<', '\>')
+  5. they do not support backreferences; if you write '\1', it will
+     match the digit '1'.  Except when doing text replacement, eg in
      account aliases, where backreferences can be used in the
      replacement string to reference capturing groups in the search
      regexp.
-
-  6. they do not support mode modifiers (`(?s)'), character classes
-     (`\w', `\d'), or anything else not mentioned above.
+  6. they do not support mode modifiers ('(?s)'), character classes
+     ('\w', '\d'), or anything else not mentioned above.
 
    Some things to note:
 
-   * In the `alias' directive and `--alias' option, regular expressions
-     must be enclosed in forward slashes (`/REGEX/').  Elsewhere in
+   * In the 'alias' directive and '--alias' option, regular expressions
+     must be enclosed in forward slashes ('/REGEX/').  Elsewhere in
      hledger, these are not required.
 
-   * In queries, to match a regular expression metacharacter like `$' as
-     a literal character, prepend a backslash. Eg to search for amounts
-     with the dollar sign in hledger-web, write `cur:\$'.
-
-   * On the command line, some metacharacters like `$' have a special
-     meaning to the shell and so must be escaped at least once more. See
-     Special characters.
+   * In queries, to match a regular expression metacharacter like '$' as
+     a literal character, prepend a backslash.  Eg to search for amounts
+     with the dollar sign in hledger-web, write 'cur:\$'.
 
+   * On the command line, some metacharacters like '$' have a special
+     meaning to the shell and so must be escaped at least once more.
+     See Special characters.
 
 
 File: hledger.info,  Node: ENVIRONMENT,  Next: DATA FILES,  Prev: OPTIONS,  Up: Top
@@ -502,32 +479,31 @@ File: hledger.info,  Node: ENVIRONMENT,  Next: DATA FILES,  Prev: OPTIONS,  Up:
 2 ENVIRONMENT
 *************
 
-*LEDGER_FILE* The journal file path when not specified with `-f'.
-Default: `~/.hledger.journal' (on windows, perhaps
-`C:/Users/USER/.hledger.journal').
+*LEDGER_FILE* The journal file path when not specified with '-f'.
+Default: '~/.hledger.journal' (on windows, perhaps
+'C:/Users/USER/.hledger.journal').
 
-   A typical value is `~/DIR/YYYY.journal', where DIR is a
-version-controlled finance directory and YYYY is the current year. Or
-`~/DIR/current.journal', where current.journal is a symbolic link to
+   A typical value is '~/DIR/YYYY.journal', where DIR is a
+version-controlled finance directory and YYYY is the current year.  Or
+'~/DIR/current.journal', where current.journal is a symbolic link to
 YYYY.journal.
 
-   On Mac computers, you can set this and other environment variables
-in a more thorough way that also affects applications started from the
-GUI (say, an Emacs dock icon). Eg on MacOS Catalina I have a
-`~/.MacOSX/environment.plist' file containing
-
+   On Mac computers, you can set this and other environment variables in
+a more thorough way that also affects applications started from the GUI
+(say, an Emacs dock icon).  Eg on MacOS Catalina I have a
+'~/.MacOSX/environment.plist' file containing
 
 {
   "LEDGER_FILE" : "~/finance/current.journal"
 }
 
-   To see the effect you may need to `killall Dock', or reboot.
+   To see the effect you may need to 'killall Dock', or reboot.
 
-   *COLUMNS* The screen width used by the register command. Default:
+   *COLUMNS* The screen width used by the register command.  Default:
 the full terminal width.
 
    *NO_COLOR* If this variable exists with any value, hledger will not
-use ANSI color codes in terminal output. This overrides the
+use ANSI color codes in terminal output.  This overrides the
 -color/-colour option.
 
 
@@ -536,23 +512,20 @@ File: hledger.info,  Node: DATA FILES,  Next: TIME PERIODS,  Prev: ENVIRONMENT,
 3 DATA FILES
 ************
 
-hledger reads transactions from one or more data files. The default data
-file is `$HOME/.hledger.journal' (or on Windows, something like
-`C:/Users/USER/.hledger.journal').
-
-   You can override this with the `$LEDGER_FILE' environment variable:
+hledger reads transactions from one or more data files.  The default
+data file is '$HOME/.hledger.journal' (or on Windows, something like
+'C:/Users/USER/.hledger.journal').
 
+   You can override this with the '$LEDGER_FILE' environment variable:
 
 $ setenv LEDGER_FILE ~/finance/2016.journal
 $ hledger stats
 
-   or with one or more `-f/--file' options:
-
+   or with one or more '-f/--file' options:
 
 $ hledger -f /some/file -f another_file stats
 
-   The file name `-' means standard input:
-
+   The file name '-' means standard input:
 
 $ cat some.journal | hledger -f-
 
@@ -573,32 +546,31 @@ any of the supported file formats, which currently are:
 
 Reader:  Reads:                                   Used for file
                                                   extensions:
--------------------------------------------------------------------------- 
-`journal'hledger journal files and some Ledger    `.journal' `.j'
-         journals, for transactions               `.hledger' `.ledger'
-`timeclock'timeclock files, for precise time        `.timeclock'
-         logging                                  
-`timedot'timedot files, for approximate time      `.timedot'
-         logging                                  
-`csv'    comma/semicolon/tab/other-separated      `.csv' `.ssv' `.tsv'
-         values, for data import                  
+--------------------------------------------------------------------------
+'journal'hledger journal files and some Ledger    '.journal' '.j'
+         journals, for transactions               '.hledger' '.ledger'
+'timeclock'timeclock files, for precise time      '.timeclock'
+         logging
+'timedot'timedot files, for approximate time      '.timedot'
+         logging
+'csv'    comma/semicolon/tab/other-separated      '.csv' '.ssv' '.tsv'
+         values, for data import
 
    These formats are described in their own sections, below.
 
    hledger detects the format automatically based on the file extensions
-shown above. If it can't recognise the file extension, it assumes
-`journal' format. So for non-journal files, it's important to use a
+shown above.  If it can't recognise the file extension, it assumes
+'journal' format.  So for non-journal files, it's important to use a
 recognised file extension, so as to either read successfully or to show
 relevant error messages.
 
    You can also force a specific reader/format by prefixing the file
-path with the format and a colon. Eg, to read a .dat file as csv format:
-
+path with the format and a colon.  Eg, to read a .dat file as csv
+format:
 
 $ hledger -f csv:/some/csv-file.dat stats
 
-   Or to read stdin (`-') as timeclock format:
-
+   Or to read stdin ('-') as timeclock format:
 
 $ echo 'i 2009/13/1 08:00:00' | hledger print -ftimeclock:-
 
@@ -608,19 +580,17 @@ File: hledger.info,  Node: Multiple files,  Next: Strict mode,  Prev: Data forma
 3.2 Multiple files
 ==================
 
-You can specify multiple `-f' options, to read multiple files as one
-big journal. There are some limitations with this:
+You can specify multiple '-f' options, to read multiple files as one big
+journal.  There are some limitations with this:
 
    * most directives do not affect sibling files
-
    * balance assertions will not see any account balances from previous
      files
 
    If you need either of those things, you can
 
    * use a single parent file which includes the others
-
-   * or concatenate the files into one before reading, eg: `cat
+   * or concatenate the files into one before reading, eg: 'cat
      a.journal b.journal | hledger -f- CMD'.
 
 
@@ -629,22 +599,19 @@ File: hledger.info,  Node: Strict mode,  Prev: Multiple files,  Up: DATA FILES
 3.3 Strict mode
 ===============
 
-hledger checks input files for valid data. By default, the most
+hledger checks input files for valid data.  By default, the most
 important errors are detected, while still accepting easy journal files
 without a lot of declarations:
 
    * Are the input files parseable, with valid syntax ?
-
    * Are all transactions balanced ?
-
    * Do all balance assertions pass ?
 
-   With the `-s'/`--strict' flag, additional checks are performed:
+   With the '-s'/'--strict' flag, additional checks are performed:
 
-   * Are all accounts posted to, declared with an `account' directive ?
+   * Are all accounts posted to, declared with an 'account' directive ?
      (Account error checking)
-
-   * Are all commodities declared with a `commodity' directive ?
+   * Are all commodities declared with a 'commodity' directive ?
      (Commodity error checking)
 
    You can also use the check command to run these and some additional
@@ -669,35 +636,37 @@ File: hledger.info,  Node: Smart dates,  Next: Report start & end date,  Up: TIM
 4.1 Smart dates
 ===============
 
-hledger's user interfaces accept a flexible "smart date" syntax. Smart
+hledger's user interfaces accept a flexible "smart date" syntax.  Smart
 dates allow some english words, can be relative to today's date, and can
 have less-significant date parts omitted (defaulting to 1).
 
    Examples:
 
-`2004/10/1',              exact date, several separators allowed. Year
-`2004-01-01', `2004.9.1'  is 4+ digits, month is 1-12, day is 1-31
-`2004'                    start of year
-`2004/10'                 start of month
-`10/1'                    month and day in current year
-`21'                      day in current month
-`october, oct'            start of month in current year
-`yesterday, today,        -1, 0, 1 days from today
-tomorrow'                 
-`last/this/next           -1, 0, 1 periods from the current period
+'2004/10/1',              exact date, several separators allowed.  Year
+'2004-01-01',             is 4+ digits, month is 1-12, day is 1-31
+'2004.9.1'
+'2004'                    start of year
+'2004/10'                 start of month
+'10/1'                    month and day in current year
+'21'                      day in current month
+'october, oct'            start of month in current year
+'yesterday, today,        -1, 0, 1 days from today
+tomorrow'
+'last/this/next           -1, 0, 1 periods from the current period
 day/week/month/quarter/year'
-`20181201'                8 digit YYYYMMDD with valid year month and day
-`201812'                  6 digit YYYYMM with valid year and month
+'20181201'                8 digit YYYYMMDD with valid year month and
+                          day
+'201812'                  6 digit YYYYMM with valid year and month
 
    Counterexamples - malformed digit sequences might give surprising
 results:
 
-`201813'     6 digits with an invalid month is parsed as start of
+'201813'     6 digits with an invalid month is parsed as start of
              6-digit year
-`20181301'   8 digits with an invalid month is parsed as start of
+'20181301'   8 digits with an invalid month is parsed as start of
              8-digit year
-`20181232'   8 digits with an invalid day gives an error
-`201801012'  9+ digits beginning with a valid YYYYMMDD gives an error
+'20181232'   8 digits with an invalid day gives an error
+'201801012'  9+ digits beginning with a valid YYYYMMDD gives an error
 
 
 File: hledger.info,  Node: Report start & end date,  Next: Report intervals,  Prev: Smart dates,  Up: TIME PERIODS
@@ -706,46 +675,43 @@ File: hledger.info,  Node: Report start & end date,  Next: Report intervals,  Pr
 ===========================
 
 By default, most hledger reports will show the full span of time
-represented by the journal data. The report start date will be the
+represented by the journal data.  The report start date will be the
 earliest transaction or posting date, and the report end date will be
 the latest transaction, posting, or market price date.
 
    Often you will want to see a shorter time span, such as the current
-month. You can specify a start and/or end date using `-b/--begin',
-`-e/--end', `-p/--period' or a `date:' query (described below). All of
+month.  You can specify a start and/or end date using '-b/--begin',
+'-e/--end', '-p/--period' or a 'date:' query (described below).  All of
 these accept the smart date syntax.
 
    Some notes:
 
    * As in Ledger, end dates are exclusive, so you need to write the
      date _after_ the last day you want to include.
-
    * As noted in reporting options: among start/end dates specified with
-     _options_, the last (i.e. right-most) option takes precedence.
-
+     _options_, the last (i.e.  right-most) option takes precedence.
    * The effective report start and end dates are the intersection of
-     the start/end dates from options and that from `date:' queries.
-     That is, `date:2019-01 date:2019 -p'2000 to 2030'' yields January
+     the start/end dates from options and that from 'date:' queries.
+     That is, 'date:2019-01 date:2019 -p'2000 to 2030'' yields January
      2019, the smallest common time span.
-
    * A report interval (see below) will adjust start/end dates, when
      needed, so that they fall on subperiod boundaries.
 
    Examples:
 
-`-b           begin on St. Patrick's day 2016
-2016/3/17'    
-`-e 12/1'     end at the start of december 1st of the current year
+'-b           begin on St. Patrick's day 2016
+2016/3/17'
+'-e 12/1'     end at the start of december 1st of the current year
               (11/30 will be the last date included)
-`-b           all transactions on or after the 1st of the current month
-thismonth'    
-`-p           all transactions in the current month
-thismonth'    
-`date:2016/3/17..'the above written as queries instead (`..' can also be
-              replaced with `-')
-`date:..12/1' 
-`date:thismonth..'
-`date:thismonth'
+'-b           all transactions on or after the 1st of the current month
+thismonth'
+'-p           all transactions in the current month
+thismonth'
+'date:2016/3/17..'the above written as queries instead ('..' can also be
+              replaced with '-')
+'date:..12/1'
+'date:thismonth..'
+'date:thismonth'
 
 
 File: hledger.info,  Node: Report intervals,  Next: Period expressions,  Prev: Report start & end date,  Up: TIME PERIODS
@@ -760,26 +726,26 @@ separate row or column.
    The following "standard" report intervals can be enabled by using
 their corresponding flag:
 
-   `-D/--daily', `-W/--weekly', `-M/--monthly', `-Q/--quarterly',
-`-Y/--yearly'.
+   '-D/--daily', '-W/--weekly', '-M/--monthly', '-Q/--quarterly',
+'-Y/--yearly'.
 
-   These standard intervals always start on natural interval
-boundaries: eg `--weekly' starts on mondays, `--monthly' starts on the
-first of the month, `--yearly' always starts on January 1st, etc.
+   These standard intervals always start on natural interval boundaries:
+eg '--weekly' starts on mondays, '--monthly' starts on the first of the
+month, '--yearly' always starts on January 1st, etc.
 
-   Certain more complex intervals, and more flexible boundary dates,
-can be specified by `-p/--period'. These are described in period
+   Certain more complex intervals, and more flexible boundary dates, can
+be specified by '-p/--period'.  These are described in period
 expressions, below.
 
    Report intervals can only be specified by the flags above, and not by
 query arguments, currently.
 
    Report intervals have another effect: multi-period reports are always
-expanded to fill a whole number of subperiods. So if you use a report
-interval (other than `--daily'), and you have specified a start or end
-date, you may notice those dates being overridden (ie, the report
-starts earlier than your requested start date, or ends later than your
-requested end date). This is done to ensure "full" first and last
+expanded to fill a whole number of subperiods.  So if you use a report
+interval (other than '--daily'), and you have specified a start or end
+date, you may notice those dates being overridden (ie, the report starts
+earlier than your requested start date, or ends later than your
+requested end date).  This is done to ensure "full" first and last
 subperiods, so that all subperiods' numbers are comparable.
 
 
@@ -788,61 +754,65 @@ File: hledger.info,  Node: Period expressions,  Prev: Report intervals,  Up: TIM
 4.4 Period expressions
 ======================
 
-The `-p/--period' option accepts period expressions, a shorthand way of
+The '-p/--period' option accepts period expressions, a shorthand way of
 expressing a start date, end date, and/or report interval all at once.
 
    Here's a basic period expression specifying the first quarter of
 2009.  Note, hledger always treats start dates as inclusive and end
 dates as exclusive:
 
-   `-p "from 2009/1/1 to 2009/4/1"'
+   '-p "from 2009/1/1 to 2009/4/1"'
 
    Keywords like "from" and "to" are optional, and so are the spaces, as
-long as you don't run two dates together. "to" can also be written as
-".." or "-". These are equivalent to the above:
+long as you don't run two dates together.  "to" can also be written as
+".."  or "-".  These are equivalent to the above:
 
-`-p "2009/1/1 2009/4/1"'
-`-p2009/1/1to2009/4/1'
-`-p2009/1/1..2009/4/1'
+'-p "2009/1/1 2009/4/1"'
+'-p2009/1/1to2009/4/1'
+'-p2009/1/1..2009/4/1'
 
    Dates are smart dates, so if the current year is 2009, the above can
 also be written as:
 
-`-p "1/1 4/1"'
-`-p "january-apr"'
-`-p "this year to 4/1"'
+'-p "1/1 4/1"'
+'-p "january-apr"'
+'-p "this year to 4/1"'
 
    If you specify only one date, the missing start or end date will be
 the earliest or latest transaction in your journal:
 
-`-p "from 2009/1/1"'   everything after january 1, 2009
-`-p "from 2009/1"'     the same
-`-p "from 2009"'       the same
-`-p "to 2009"'         everything before january 1, 2009
+'-p "from 2009/1/1"'   everything after january 1, 2009
+'-p "from 2009/1"'     the same
+'-p "from 2009"'       the same
+'-p "to 2009"'         everything before january 1, 2009
 
    A single date with no "from" or "to" defines both the start and end
 date like so:
 
-`-p "2009"'       the year 2009; equivalent to “2009/1/1 to 2010/1/1”
-`-p "2009/1"'     the month of jan; equivalent to “2009/1/1 to 2009/2/1”
-`-p "2009/1/1"'   just that day; equivalent to “2009/1/1 to 2009/1/2”
+'-p "2009"'       the year 2009; equivalent to “2009/1/1 to
+                  2010/1/1”
+'-p "2009/1"'     the month of jan; equivalent to “2009/1/1 to
+                  2009/2/1”
+'-p "2009/1/1"'   just that day; equivalent to “2009/1/1 to
+                  2009/1/2”
 
    Or you can specify a single quarter like so:
 
-`-p "2009Q1"'   first quarter of 2009, equivalent to “2009/1/1 to 2009/4/1”
-`-p "q4"'       fourth quarter of the current year
+'-p "2009Q1"'   first quarter of 2009, equivalent to “2009/1/1 to
+                2009/4/1”
+'-p "q4"'       fourth quarter of the current year
 
-   The argument of `-p' can also begin with, or be, a report interval
-expression. The basic report intervals are `daily', `weekly',
-`monthly', `quarterly', or `yearly', which have the same effect as the
-`-D',`-W',`-M',`-Q', or `-Y' flags. Between report interval and
-start/end dates (if any), the word `in' is optional. Examples:
+   The argument of '-p' can also begin with, or be, a report interval
+expression.  The basic report intervals are 'daily', 'weekly',
+'monthly', 'quarterly', or 'yearly', which have the same effect as the
+'-D','-W','-M','-Q', or '-Y' flags.  Between report interval and
+start/end dates (if any), the word 'in' is optional.  Examples:
 
-`-p "weekly from 2009/1/1 to 2009/4/1"'
-`-p "monthly in 2008"'
-`-p "quarterly"'
+'-p "weekly from 2009/1/1 to 2009/4/1"'
+'-p "monthly in 2008"'
+'-p "quarterly"'
 
-   Note that `weekly', `monthly', `quarterly' and `yearly' intervals
+   Note that 'weekly', 'monthly', 'quarterly' and 'yearly' intervals
 will always start on the first day on week, month, quarter or year
 accordingly, and will end on the last day of same period, even if
 associated period expression specifies different explicit start and end
@@ -850,18 +820,19 @@ date.
 
    For example:
 
-`-p "weekly from 2009/1/1  starts on 2008/12/29, closest preceding Monday
-to 2009/4/1"'              
-`-p "monthly in            starts on 2018/11/01
-2008/11/25"'               
-`-p "quarterly from        starts on 2009/04/01, ends on 2009/06/30,
-2009-05-05 to 2009-06-01"' which are first and last days of Q2 2009
-`-p "yearly from           starts on 2009/01/01, first day of 2009
-2009-12-29"'               
+'-p "weekly from           starts on 2008/12/29, closest preceding
+2009/1/1 to 2009/4/1"'     Monday
+'-p "monthly in            starts on 2018/11/01
+2008/11/25"'
+'-p "quarterly from        starts on 2009/04/01, ends on 2009/06/30,
+2009-05-05 to              which are first and last days of Q2 2009
+2009-06-01"'
+'-p "yearly from           starts on 2009/01/01, first day of 2009
+2009-12-29"'
 
    The following more complex report intervals are also supported:
-`biweekly', `fortnightly', `bimonthly', `every
-day|week|month|quarter|year', `every N
+'biweekly', 'fortnightly', 'bimonthly', 'every
+day|week|month|quarter|year', 'every N
 days|weeks|months|quarters|years'.
 
    All of these will start on the first day of the requested period and
@@ -869,41 +840,42 @@ end on the last one, as described above.
 
    Examples:
 
-`-p "bimonthly from 2008"' periods will have boundaries on 2008/01/01,
-                           2008/03/01, ...
-`-p "every 2 weeks"'       starts on closest preceding Monday
-`-p "every 5 month from    periods will have boundaries on 2009/03/01,
+'-p "bimonthly from        periods will have boundaries on 2008/01/01,
+2008"'                     2008/03/01, ...
+'-p "every 2 weeks"'       starts on closest preceding Monday
+'-p "every 5 month from    periods will have boundaries on 2009/03/01,
 2009/03"'                  2009/08/01, ...
 
    If you want intervals that start on arbitrary day of your choosing
 and span a week, month or year, you need to use any of the following:
 
-   `every Nth day of week', `every WEEKDAYNAME' (eg
-`mon|tue|wed|thu|fri|sat|sun'), `every Nth day [of month]', `every Nth
-WEEKDAYNAME [of month]', `every MM/DD [of year]', `every Nth MMM [of
-year]', `every MMM Nth [of year]'.
+   'every Nth day of week', 'every WEEKDAYNAME' (eg
+'mon|tue|wed|thu|fri|sat|sun'), 'every Nth day [of month]', 'every Nth
+WEEKDAYNAME [of month]', 'every MM/DD [of year]', 'every Nth MMM [of
+year]', 'every MMM Nth [of year]'.
 
    Examples:
 
-`-p "every 2nd day of    periods will go from Tue to Tue
-week"'                   
-`-p "every Tue"'         same
-`-p "every 15th day"'    period boundaries will be on 15th of each month
-`-p "every 2nd Monday"'  period boundaries will be on second Monday of
-                         each month
-`-p "every 11/05"'       yearly periods with boundaries on 5th of Nov
-`-p "every 5th Nov"'     same
-`-p "every Nov 5th"'     same
+'-p "every 2nd day of    periods will go from Tue to Tue
+week"'
+'-p "every Tue"'         same
+'-p "every 15th day"'    period boundaries will be on 15th of each
+                         month
+'-p "every 2nd           period boundaries will be on second Monday of
+Monday"'                 each month
+'-p "every 11/05"'       yearly periods with boundaries on 5th of Nov
+'-p "every 5th Nov"'     same
+'-p "every Nov 5th"'     same
 
    Show historical balances at end of 15th each month (N is exclusive
 end date):
 
-   `hledger balance -H -p "every 16th day"'
+   'hledger balance -H -p "every 16th day"'
 
    Group postings from start of wednesday to end of next tuesday (N is
 start date and exclusive end date):
 
-   `hledger register checking -p "every 3rd day of week"'
+   'hledger register checking -p "every 3rd day of week"'
 
 
 File: hledger.info,  Node: DEPTH,  Next: QUERIES,  Prev: TIME PERIODS,  Up: Top
@@ -911,11 +883,11 @@ File: hledger.info,  Node: DEPTH,  Next: QUERIES,  Prev: TIME PERIODS,  Up: Top
 5 DEPTH
 *******
 
-With the `--depth N' option (short form: `-N'), commands like account,
+With the '--depth N' option (short form: '-N'), commands like account,
 balance and register will show only the uppermost accounts in the
 account tree, down to level N. Use this when you want a summary with
-less detail. This flag has the same effect as a `depth:' query argument
-(so `-2', `--depth=2' or `depth:2' are equivalent).
+less detail.  This flag has the same effect as a 'depth:' query argument
+(so '-2', '--depth=2' or 'depth:2' are equivalent).
 
 
 File: hledger.info,  Node: QUERIES,  Next: COSTING,  Prev: DEPTH,  Up: Top
@@ -924,110 +896,108 @@ File: hledger.info,  Node: QUERIES,  Next: COSTING,  Prev: DEPTH,  Up: Top
 *********
 
 One of hledger's strengths is being able to quickly report on precise
-subsets of your data. Most commands accept an optional query expression,
-written as arguments after the command name, to filter the data by date,
-account name or other criteria. The syntax is similar to a web search:
-one or more space-separated search terms, quotes to enclose whitespace,
-prefixes to match specific fields, a not: prefix to negate the match.
+subsets of your data.  Most commands accept an optional query
+expression, written as arguments after the command name, to filter the
+data by date, account name or other criteria.  The syntax is similar to
+a web search: one or more space-separated search terms, quotes to
+enclose whitespace, prefixes to match specific fields, a not: prefix to
+negate the match.
 
    We do not yet support arbitrary boolean combinations of search terms;
 instead most commands show transactions/postings/accounts which match
 (or negatively match):
 
    * any of the description terms AND
-
    * any of the account terms AND
-
    * any of the status terms AND
-
    * all the other terms.
 
    The print command instead shows transactions which:
 
    * match any of the description terms AND
-
    * have any postings matching any of the positive account terms AND
-
    * have no postings matching any of the negative account terms AND
-
    * match all the other terms.
 
-   The following kinds of search terms can be used. Remember these can
-also be prefixed with *`not:'*, eg to exclude a particular subaccount.
+   The following kinds of search terms can be used.  Remember these can
+also be prefixed with *'not:'*, eg to exclude a particular subaccount.
 
-*`REGEX', `acct:REGEX'*
-     match account names by this regular expression. (With no prefix,
-     `acct:' is assumed.)  same as above
+*'REGEX', 'acct:REGEX'*
+
+     match account names by this regular expression.  (With no prefix,
+     'acct:' is assumed.)  same as above
+
+*'amt:N, amt:<N, amt:<=N, amt:>N, amt:>=N'*
 
-*`amt:N, amt:<N, amt:<=N, amt:>N, amt:>=N'*
      match postings with a single-commodity amount that is equal to,
      less than, or greater than N. (Multi-commodity amounts are not
-     tested, and will always match.) The comparison has two modes: if N
+     tested, and will always match.)  The comparison has two modes: if N
      is preceded by a + or - sign (or is 0), the two signed numbers are
-     compared. Otherwise, the absolute magnitudes are compared,
+     compared.  Otherwise, the absolute magnitudes are compared,
      ignoring sign.
+*'code:REGEX'*
 
-*`code:REGEX'*
      match by transaction code (eg check number)
+*'cur:REGEX'*
 
-*`cur:REGEX'*
      match postings or transactions including any amounts whose
      currency/commodity symbol is fully matched by REGEX. (For a partial
-     match, use `.*REGEX.*'). Note, to match characters which are
-     regex-significant, like the dollar sign (`$'), you need to prepend
-     `\'. And when using the command line you need to add one more level
-     of quoting to hide it from the shell, so eg do: `hledger print
-     cur:'\$'' or `hledger print cur:\\$'.
+     match, use '.*REGEX.*').  Note, to match characters which are
+     regex-significant, like the dollar sign ('$'), you need to prepend
+     '\'.  And when using the command line you need to add one more
+     level of quoting to hide it from the shell, so eg do: 'hledger
+     print cur:'\$'' or 'hledger print cur:\\$'.
+*'desc:REGEX'*
 
-*`desc:REGEX'*
      match transaction descriptions.
+*'date:PERIODEXPR'*
 
-*`date:PERIODEXPR'*
-     match dates within the specified period. PERIODEXPR is a period
-     expression (with no report interval). Examples: `date:2016',
-     `date:thismonth', `date:2000/2/1-2/15', `date:lastweek-'.  If the
-     `--date2' command line flag is present, this matches secondary
-     dates instead. (Report intervals will adjust start/end dates to
+     match dates within the specified period.  PERIODEXPR is a period
+     expression (with no report interval).  Examples: 'date:2016',
+     'date:thismonth', 'date:2000/2/1-2/15', 'date:lastweek-'.  If the
+     '--date2' command line flag is present, this matches secondary
+     dates instead.  (Report intervals will adjust start/end dates to
      preceding/following subperiod boundaries.)
+*'date2:PERIODEXPR'*
 
-*`date2:PERIODEXPR'*
      match secondary dates within the specified period.
+*'depth:N'*
 
-*`depth:N'*
      match (or display, depending on command) accounts at or above this
      depth
+*'note:REGEX'*
 
-*`note:REGEX'*
-     match transaction notes (part of description right of `|', or whole
-     description when there's no `|')
+     match transaction notes (part of description right of '|', or whole
+     description when there's no '|')
+*'payee:REGEX'*
 
-*`payee:REGEX'*
      match transaction payee/payer names (part of description left of
-     `|', or whole description when there's no `|')
+     '|', or whole description when there's no '|')
+*'real:, real:0'*
 
-*`real:, real:0'*
      match real or virtual postings respectively
+*'status:, status:!, status:*'*
 
-*`status:, status:!, status:*'*
      match unmarked, pending, or cleared transactions respectively
+*'tag:REGEX[=REGEX]'*
 
-*`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 tags of
-     their parent transaction.
+     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.
 
    The following special search term is used automatically in
 hledger-web, only:
 
-*`inacct:ACCTNAME'*
+*'inacct:ACCTNAME'*
+
      tells hledger-web to show the transaction register for this
-     account. Can be filtered further with `acct' etc.
+     account.  Can be filtered further with 'acct' etc.
 
    Some of these can also be expressed as command-line options (eg
-`depth:2' is equivalent to `--depth 2'). Generally you can mix options
+'depth:2' 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).
+(perhaps excluding the '-p/--period' option).
 
 
 File: hledger.info,  Node: COSTING,  Next: VALUATION,  Prev: QUERIES,  Up: Top
@@ -1035,8 +1005,8 @@ File: hledger.info,  Node: COSTING,  Next: VALUATION,  Prev: QUERIES,  Up: Top
 7 COSTING
 *********
 
-The `-B/--cost' flag converts amounts to their cost or sale amount at
-transaction time, if they have a transaction price specified. If this
+The '-B/--cost' flag converts amounts to their cost or sale amount at
+transaction time, if they have a transaction price specified.  If this
 flag is supplied, hledger will perform cost conversion first, and will
 apply any market price valuations (if requested) afterwards.
 
@@ -1049,9 +1019,9 @@ File: hledger.info,  Node: VALUATION,  Next: PIVOTING,  Prev: COSTING,  Up: Top
 Instead of reporting amounts in their original commodity, hledger can
 convert them to cost/sale amount (using the conversion rate recorded in
 the transaction), and/or to market value (using some market price on a
-certain date). This is controlled by the `--value=TYPE[,COMMODITY]'
-option, which will be described below. We also provide the simpler `-V'
-and `-X COMMODITY' options, and often one of these is all you need:
+certain date).  This is controlled by the '--value=TYPE[,COMMODITY]'
+option, which will be described below.  We also provide the simpler '-V'
+and '-X COMMODITY' options, and often one of these is all you need:
 
 * Menu:
 
@@ -1072,9 +1042,9 @@ File: hledger.info,  Node: -V Value,  Next: -X Value in specified commodity,  Up
 8.1 -V: Value
 =============
 
-The `-V/--market' flag converts amounts to market value in their
-default _valuation commodity_, using the market prices in effect on the
-_valuation date(s)_, if any. More on these in a minute.
+The '-V/--market' flag converts amounts to market value in their default
+_valuation commodity_, using the market prices in effect on the
+_valuation date(s)_, if any.  More on these in a minute.
 
 
 File: hledger.info,  Node: -X Value in specified commodity,  Next: Valuation date,  Prev: -V Value,  Up: VALUATION
@@ -1082,7 +1052,7 @@ File: hledger.info,  Node: -X Value in specified commodity,  Next: Valuation dat
 8.2 -X: Value in specified commodity
 ====================================
 
-The `-X/--exchange=COMM' option is like `-V', except you tell it which
+The '-X/--exchange=COMM' option is like '-V', except you tell it which
 currency you want to convert to, and it tries to convert everything to
 that.
 
@@ -1100,8 +1070,8 @@ prices will be used.
 specified, that will be used as the valuation date; otherwise the
 valuation date is the journal's end date.
 
-   For multiperiod reports, each column/period is valued on the last
-day of the period, by default.
+   For multiperiod reports, each column/period is valued on the last day
+of the period, by default.
 
 
 File: hledger.info,  Node: Market prices,  Next: --infer-market-price market prices from transactions,  Prev: Valuation date,  Up: VALUATION
@@ -1115,7 +1085,7 @@ this order of preference :
 
   1. A _declared market price_ or _inferred market price_: A's latest
      market price in B on or before the valuation date as declared by a
-     P directive, or (with the `--infer-market-price' flag) inferred
+     P directive, or (with the '--infer-market-price' flag) inferred
      from transaction prices.
 
   2. A _reverse market price_: the inverse of a declared or inferred
@@ -1129,11 +1099,10 @@ this order of preference :
      including both forward and reverse prices (1 and 2 above), leading
      from A to B.
 
-
    There is a limit to the length of these price chains; if hledger
 reaches that length without finding a complete chain or exhausting all
 possibilities, it will give up (with a "gave up" message visible in
-`--debug=2' output). That limit is currently 1000.
+'--debug=2' output).  That limit is currently 1000.
 
    Amounts for which no suitable market price can be found, are not
 converted.
@@ -1145,33 +1114,32 @@ File: hledger.info,  Node: --infer-market-price market prices from transactions,
 ========================================================
 
 Normally, market value in hledger is fully controlled by, and requires,
-P directives in your journal. Since adding and updating those can be a
+P directives in your journal.  Since adding and updating those can be a
 chore, and since transactions usually take place at close to market
 value, why not use the recorded transaction prices as additional market
-prices (as Ledger does) ? We could produce value reports without needing
-P directives at all.
+prices (as Ledger does) ?  We could produce value reports without
+needing P directives at all.
 
-   Adding the `--infer-market-price' flag to `-V', `-X' or `--value'
-enables this. So for example, `hledger bs -V --infer-market-price' will
-get market prices both from P directives and from transactions. (And if
+   Adding the '--infer-market-price' flag to '-V', '-X' or '--value'
+enables this.  So for example, 'hledger bs -V --infer-market-price' will
+get market prices both from P directives and from transactions.  (And if
 both occur on the same day, the P directive takes precedence).
 
    There is a downside: value reports can sometimes be affected in
-confusing/undesired ways by your journal entries. If this happens to
+confusing/undesired ways by your journal entries.  If this happens to
 you, read all of this Valuation section carefully, and try adding
-`--debug' or `--debug=2' to troubleshoot.
+'--debug' or '--debug=2' to troubleshoot.
 
-   `--infer-market-price' can infer market prices from:
+   '--infer-market-price' can infer market prices from:
 
-   * multicommodity transactions with explicit prices (`@'/`@@')
+   * multicommodity transactions with explicit prices ('@'/'@@')
 
-   * multicommodity transactions with implicit prices (no `@', two
-     commodities, unbalanced). (With these, the order of postings
-     matters.  `hledger print -x' can be useful for troubleshooting.)
-
-   * but not, currently, from "more correct" multicommodity
-     transactions (no `@', multiple commodities, balanced).
+   * multicommodity transactions with implicit prices (no '@', two
+     commodities, unbalanced).  (With these, the order of postings
+     matters.  'hledger print -x' can be useful for troubleshooting.)
 
+   * but not, currently, from "more correct" multicommodity transactions
+     (no '@', multiple commodities, balanced).
 
 
 File: hledger.info,  Node: Valuation commodity,  Next: Simple valuation examples,  Prev: --infer-market-price market prices from transactions,  Up: VALUATION
@@ -1179,13 +1147,13 @@ File: hledger.info,  Node: Valuation commodity,  Next: Simple valuation examples
 8.6 Valuation commodity
 =======================
 
-*When you specify a valuation commodity (`-X COMM' or `--value
+*When you specify a valuation commodity ('-X COMM' or '--value
 TYPE,COMM'):*
 hledger will convert all amounts to COMM, wherever it can find a
 suitable market price (including by reversing or chaining prices).
 
-   *When you leave the valuation commodity unspecified (`-V' or
-`--value TYPE'):*
+   *When you leave the valuation commodity unspecified ('-V' or '--value
+TYPE'):*
 For each commodity A, hledger picks a default valuation commodity as
 follows, in this order of preference:
 
@@ -1193,24 +1161,22 @@ follows, in this order of preference:
      on or before valuation date.
 
   2. The price commodity from the latest P-declared market price for A
-     on any date. (Allows conversion to proceed when there are inferred
+     on any date.  (Allows conversion to proceed when there are inferred
      prices before the valuation date.)
 
   3. If there are no P directives at all (any commodity or date) and the
-     `--infer-market-price' flag is used: the price commodity from the
+     '--infer-market-price' flag is used: the price commodity from the
      latest transaction-inferred price for A on or before valuation
      date.
 
-
    This means:
 
-   * If you have P directives, they determine which commodities `-V'
+   * If you have P directives, they determine which commodities '-V'
      will convert, and to what.
 
-   * If you have no P directives, and use the `--infer-market-price'
+   * If you have no P directives, and use the '--infer-market-price'
      flag, transaction prices determine it.
 
-
    Amounts for which no valuation commodity can be found are not
 converted.
 
@@ -1220,8 +1186,7 @@ File: hledger.info,  Node: Simple valuation examples,  Next: --value Flexible va
 8.7 Simple valuation examples
 =============================
 
-Here are some quick examples of `-V':
-
+Here are some quick examples of '-V':
 
 ; one euro is worth this many dollars from nov 1
 P 2016/11/01 € $1.10
@@ -1236,19 +1201,16 @@ P 2016/12/21 € $1.03
 
    How many euros do I have ?
 
-
 $ hledger -f t.j bal -N euros
                 €100  assets:euros
 
    What are they worth at end of nov 3 ?
 
-
 $ hledger -f t.j bal -N euros -V -e 2016/11/4
              $110.00  assets:euros
 
-   What are they worth after 2016/12/21 ? (no report end date specified,
-defaults to today)
-
+   What are they worth after 2016/12/21 ?  (no report end date
+specified, defaults to today)
 
 $ hledger -f t.j bal -N euros -V
              $103.00  assets:euros
@@ -1259,8 +1221,7 @@ File: hledger.info,  Node: --value Flexible valuation,  Next: More valuation exa
 8.8 -value: Flexible valuation
 ==============================
 
-`-V' and `-X' are special cases of the more general `--value' option:
-
+'-V' and '-X' are special cases of the more general '--value' option:
 
  --value=TYPE[,COMM]  TYPE is then, end, now or YYYY-MM-DD.
                       COMM is an optional commodity symbol.
@@ -1272,27 +1233,28 @@ File: hledger.info,  Node: --value Flexible valuation,  Next: More valuation exa
 
    The TYPE part selects cost or value and valuation date:
 
-`--value=then'
+'--value=then'
+
      Convert amounts to their value in the default valuation commodity,
      using market prices on each posting's date.
+'--value=end'
 
-`--value=end'
      Convert amounts to their value in the default valuation commodity,
      using market prices on the last day of the report period (or if
      unspecified, the journal's end date); or in multiperiod reports,
      market prices on the last day of each subperiod.
+'--value=now'
 
-`--value=now'
      Convert amounts to their value in the default valuation commodity
      using current market prices (as of when report is generated).
+'--value=YYYY-MM-DD'
 
-`--value=YYYY-MM-DD'
      Convert amounts to their value in the default valuation commodity
      using market prices on this date.
 
-   To select a different valuation commodity, add the optional `,COMM'
-part: a comma, then the target commodity's symbol. Eg:
-*`--value=now,EUR'*. hledger will do its best to convert amounts to
+   To select a different valuation commodity, add the optional ',COMM'
+part: a comma, then the target commodity's symbol.  Eg:
+*'--value=now,EUR'*.  hledger will do its best to convert amounts to
 this commodity, deducing market prices as described above.
 
 
@@ -1301,9 +1263,8 @@ File: hledger.info,  Node: More valuation examples,  Next: Effect of valuation o
 8.9 More valuation examples
 ===========================
 
-Here are some examples showing the effect of `--value', as seen with
-`print':
-
+Here are some examples showing the effect of '--value', as seen with
+'print':
 
 P 2000-01-01 A  1 B
 P 2000-02-01 A  2 B
@@ -1321,7 +1282,6 @@ P 2000-04-01 A  4 B
 
    Show the cost of each posting:
 
-
 $ hledger -f- print --cost
 2000-01-01
     (a)             5 B
@@ -1334,7 +1294,6 @@ $ hledger -f- print --cost
 
    Show the value as of the last day of the report period (2000-02-29):
 
-
 $ hledger -f- print --value=end date:2000/01-2000/03
 2000-01-01
     (a)             2 B
@@ -1345,7 +1304,6 @@ $ hledger -f- print --value=end date:2000/01-2000/03
    With no report period specified, that shows the value as of the last
 day of the journal (2000-03-01):
 
-
 $ hledger -f- print --value=end
 2000-01-01
     (a)             3 B
@@ -1359,7 +1317,6 @@ $ hledger -f- print --value=end
    Show the current value (the 2000-04-01 price is still in effect
 today):
 
-
 $ hledger -f- print --value=now
 2000-01-01
     (a)             4 B
@@ -1372,7 +1329,6 @@ $ hledger -f- print --value=now
 
    Show the value on 2000/01/15:
 
-
 $ hledger -f- print --value=2000-01-15
 2000-01-01
     (a)             1 B
@@ -1384,8 +1340,7 @@ $ hledger -f- print --value=2000-01-15
     (a)             1 B
 
    You may need to explicitly set a commodity's display style, when
-reverse prices are used. Eg this output might be surprising:
-
+reverse prices are used.  Eg this output might be surprising:
 
 P 2000-01-01 A 2B
 
@@ -1393,7 +1348,6 @@ P 2000-01-01 A 2B
   a  1B
   b
 
-
 $ hledger print -x -X A
 2000-01-01
     a               0
@@ -1401,11 +1355,10 @@ $ hledger print -x -X A
 
    Explanation: because there's no amount or commodity directive
 specifying a display style for A, 0.5A gets the default style, which
-shows no decimal digits. Because the displayed amount looks like zero,
-the commodity symbol and minus sign are not displayed either. Adding a
+shows no decimal digits.  Because the displayed amount looks like zero,
+the commodity symbol and minus sign are not displayed either.  Adding a
 commodity directive sets a more useful display style for A:
 
-
 P 2000-01-01 A 2B
 commodity 0.00A
 
@@ -1413,7 +1366,6 @@ commodity 0.00A
   a  1B
   b
 
-
 $ hledger print -X A
 2000-01-01
     a           0.50A
@@ -1426,49 +1378,51 @@ File: hledger.info,  Node: Effect of valuation on reports,  Prev: More valuation
 ===================================
 
 Here is a reference for how valuation is supposed to affect each part of
-hledger's reports (and a glossary). (It's wide, you'll have 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 (and a glossary).  (It's wide, you'll have to scroll
+sideways.)  It may be useful when troubleshooting.  If you find
+problems, please report them, ideally with a reproducible example.
+Related: #329, #1083.
 
-Report     `-B',        `-V', `-X'   `--value=then'     `--value=end'`--value=DATE',
-type       `--cost'                                                  `--value=now'
------------------------------------------------------------------------------- 
-*print*                                                              
+Report     '-B',        '-V', '-X'   '--value=then'     '--value=end''--value=DATE',
+type       '--cost'                                                  '--value=now'
+------------------------------------------------------------------------------
+*print*
 posting    cost         value at     value at posting   value at     value
 amounts                 report end   date               report or    at
-                        or today                        journal end  DATE/today
+                        or today                        journal      DATE/today
+                                                        end
 balance    unchanged    unchanged    unchanged          unchanged    unchanged
-assertions/assignments                                                          
-
-*register*                                                           
+assertions/assignments
+*register*
 starting   cost         value at     valued at day      value at     value
 balance                 day before   each historical    day before   at
 (-H)                    report or    posting was made   report or    DATE/today
-                        journal                         journal      
-                        start                           start        
+                        journal                         journal
+                        start                           start
 posting    cost         value at     value at posting   value at     value
 amounts                 report end   date               report or    at
-                        or today                        journal end  DATE/today
+                        or today                        journal      DATE/today
+                                                        end
 summary    summarised   value at     sum of postings    value at     value
-posting    cost         period ends  in interval,       period ends  at
-amounts                              valued at                       DATE/today
-with                                 interval start                  
-report                                                               
-interval                                                             
+posting    cost         period       in interval,       period       at
+amounts                 ends         valued at          ends         DATE/today
+with                                 interval start
+report
+interval
 running    sum/average  sum/average  sum/average of     sum/average  sum/average
-total/averageof           of           displayed values   of           of
+total/averageof         of           displayed values   of           of
            displayed    displayed                       displayed    displayed
            values       values                          values       values
-
-*balance                                                             
-(bs, bse,                                                            
-cf, is)*                                                             
+*balance
+(bs,
+bse, cf,
+is)*
 balance    sums of      value at     value at posting   value at     value
 changes    costs        report end   date               report or    at
-                        or today of                     journal end  DATE/today
-                        sums of                         of sums of   of sums
-                        postings                        postings     of
+                        or today                        journal      DATE/today
+                        of sums of                      end of       of
+                        postings                        sums of      sums
+                                                        postings     of
                                                                      postings
 budget     like         like         like balance       like         like
 amounts    balance      balance      changes            balances     balance
@@ -1476,84 +1430,87 @@ amounts    balance      balance      changes            balances     balance
 grand      sum of       sum of       sum of displayed   sum of       sum of
 total      displayed    displayed    valued             displayed    displayed
            values       values                          values       values
-
-*balance                                                             
-(bs, bse,                                                            
-cf, is)                                                              
-with                                                                 
-report                                                               
-interval*                                                            
-starting   sums of      value at     sums of values of  value at     sums of
-balances   costs of     report       postings before    report       postings
-(-H)       postings     start of     report start at    start of     before
-           before       sums of all  respective         sums of all  report
-           report start postings     posting dates      postings     start
-                        before                          before       
-                        report start                    report start 
-balance    sums of      same as      sums of values of  balance      value
-changes    costs of     -value=end   postings in        change in    at
-(bal, is,  postings in               period at          each         DATE/today
-bs         period                    respective         period,      of sums
--change,                             posting dates      valued at    of
-cf                                                      period ends  postings
--change)                                                             
-end        sums of      same as      sums of values of  period end   value
-balances   costs of     -value=end   postings from      balances,    at
+*balance
+(bs,
+bse, cf,
+is) with
+report
+interval*
+starting   sums of      value at     sums of values     value at     sums
+balances   costs of     report       of postings        report       of
+(-H)       postings     start of     before report      start of     postings
+           before       sums of      start at           sums of      before
+           report       all          respective         all          report
+           start        postings     posting dates      postings     start
+                        before                          before
+                        report                          report
+                        start                           start
+balance    sums of      same as      sums of values     balance      value
+changes    costs of     -value=end   of postings in     change in    at
+(bal,      postings                  period at          each         DATE/today
+is, bs     in period                 respective         period,      of
+-change,                             posting dates      valued at    sums
+cf                                                      period       of
+-change)                                                ends         postings
+end        sums of      same as      sums of values     period end   value
+balances   costs of     -value=end   of postings from   balances,    at
 (bal -H,   postings                  before period      valued at    DATE/today
-is -H,     from before               start to period    period ends  of sums
-bs, cf)    report                    end at respective               of
+is -H,     from                      start to period    period       of
+bs, cf)    before                    end at             ends         sums
+           report                    respective                      of
            start to                  posting dates                   postings
-           period end                                                
+           period end
 budget     like         like         like balance       like         like
 amounts    balance      balance      changes/end        balances     balance
 (-budget)  changes/end  changes/end  balances                        changes/end
            balances     balances                                     balances
-row        sums,        sums,        sums, averages of  sums,        sums,
-totals,    averages of  averages of  displayed values   averages of  averages
-row        displayed    displayed                       displayed    of
-averages   values       values                          values       displayed
-(-T, -A)                                                             values
-column     sums of      sums of      sums of displayed  sums of      sums of
-totals     displayed    displayed    values             displayed    displayed
-           values       values                          values       values
+row        sums,        sums,        sums, averages     sums,        sums,
+totals,    averages     averages     of displayed       averages     averages
+row        of           of           values             of           of
+averages   displayed    displayed                       displayed    displayed
+(-T, -A)   values       values                          values       values
+column     sums of      sums of      sums of            sums of      sums
+totals     displayed    displayed    displayed values   displayed    of
+           values       values                          values       displayed
+                                                                     values
 grand      sum,         sum,         sum, average of    sum,         sum,
 total,     average of   average of   column totals      average of   average
 grand      column       column                          column       of
 average    totals       totals                          totals       column
                                                                      totals
 
-
-   `--cumulative' is omitted to save space, it works like `-H' but with
+   '--cumulative' is omitted to save space, it works like '-H' but with
 a zero starting balance.
 
    *Glossary:*
 
 _cost_
-     calculated using price(s) recorded in the transaction(s).
 
+     calculated using price(s) recorded in the transaction(s).
 _value_
+
      market value using available market price declarations, or the
      unchanged amount if no conversion rate can be found.
-
 _report start_
+
      the first day of the report period specified with -b or -p or
      date:, otherwise today.
-
 _report or journal start_
+
      the first day of the report period specified with -b or -p or
      date:, otherwise the earliest transaction date in the journal,
      otherwise today.
-
 _report end_
+
      the last day of the report period specified with -e or -p or date:,
      otherwise today.
-
 _report or journal end_
+
      the last day of the report period specified with -e or -p or date:,
      otherwise the latest transaction date in the journal, otherwise
      today.
-
 _report interval_
+
      a flag (-D/-W/-M/-Q/-Y) or period expression that activates the
      report's multi-period mode (whether showing one or many
      subperiods).
@@ -1565,28 +1522,26 @@ File: hledger.info,  Node: PIVOTING,  Next: OUTPUT,  Prev: VALUATION,  Up: Top
 **********
 
 Normally hledger sums amounts, and organizes them in a hierarchy, based
-on account name. The `--pivot FIELD' option causes it to sum and
-organize hierarchy based on the value of some other field instead. FIELD
-can be: `code', `description', `payee', `note', or the full name (case
-insensitive) of any tag. As with account names, values containing
-`colon:separated:parts' will be displayed hierarchically in reports.
+on account name.  The '--pivot FIELD' option causes it to sum and
+organize hierarchy based on the value of some other field instead.
+FIELD can be: 'code', 'description', 'payee', 'note', or the full name
+(case insensitive) of any tag.  As with account names, values containing
+'colon:separated:parts' will be displayed hierarchically in reports.
 
-   `--pivot' is a general option affecting all reports; you can think
-of hledger transforming the journal before any other processing,
-replacing every posting's account name with the value of the specified
-field on that posting, inheriting it from the transaction or using a
-blank value if it's not present.
+   '--pivot' is a general option affecting all reports; you can think of
+hledger transforming the journal before any other processing, replacing
+every posting's account name with the value of the specified field on
+that posting, inheriting it from the transaction or using a blank value
+if it's not present.
 
    An example:
 
-
 2016/02/16 Member Fee Payment
     assets:bank account                    2 EUR
     income:member fees                    -2 EUR  ; member: John Doe
 
    Normal balance report showing account names:
 
-
 $ hledger balance
                2 EUR  assets:bank account
               -2 EUR  income:member fees
@@ -1595,7 +1550,6 @@ $ hledger balance
 
    Pivoted balance report, using member: tag values instead:
 
-
 $ hledger balance --pivot member
                2 EUR
               -2 EUR  John Doe
@@ -1605,7 +1559,6 @@ $ hledger balance --pivot member
    One way to show only amounts with a member: value (using a query,
 described below):
 
-
 $ hledger balance --pivot member tag:member=.
               -2 EUR  John Doe
 --------------------
@@ -1614,7 +1567,6 @@ $ hledger balance --pivot member tag:member=.
    Another way (the acct: query matches against the pivoted "account
 name"):
 
-
 $ hledger balance --pivot member acct:.
               -2 EUR  John Doe
 --------------------
@@ -1637,24 +1589,22 @@ File: hledger.info,  Node: Output destination,  Next: Output format,  Up: OUTPUT
 10.1 Output destination
 =======================
 
-hledger commands send their output to the terminal by default. You can
+hledger commands send their output to the terminal by default.  You can
 of course redirect this, eg into a file, using standard shell syntax:
 
-
 $ hledger print > foo.txt
 
    Some commands (print, register, stats, the balance commands) also
-provide the `-o/--output-file' option, which does the same thing
-without needing the shell. Eg:
-
+provide the '-o/--output-file' option, which does the same thing without
+needing the shell.  Eg:
 
 $ hledger print -o foo.txt
 $ hledger print -o -        # write to stdout (the default)
 
    hledger can optionally produce debug output (if enabled with
-`--debug=N'); this goes to stderr, and is not affected by
-`-o/--output-file'. If you need to capture it, use shell redirects, eg:
-`hledger bal --debug=3 >file 2>&1'.
+'--debug=N'); this goes to stderr, and is not affected by
+'-o/--output-file'.  If you need to capture it, use shell redirects, eg:
+'hledger bal --debug=3 >file 2>&1'.
 
 
 File: hledger.info,  Node: Output format,  Prev: Output destination,  Up: OUTPUT
@@ -1663,42 +1613,38 @@ File: hledger.info,  Node: Output format,  Prev: Output destination,  Up: OUTPUT
 ==================
 
 Some commands (print, register, the balance commands) offer a choice of
-output format. In addition to the usual plain text format (`txt'),
-there are CSV (`csv'), HTML (`html'), JSON (`json') and SQL (`sql').
-This is controlled by the `-O/--output-format' option:
-
+output format.  In addition to the usual plain text format ('txt'),
+there are CSV ('csv'), HTML ('html'), JSON ('json') and SQL ('sql').
+This is controlled by the '-O/--output-format' option:
 
 $ hledger print -O csv
 
-   or, by a file extension specified with `-o/--output-file':
-
+   or, by a file extension specified with '-o/--output-file':
 
 $ hledger balancesheet -o foo.html   # write HTML to foo.html
 
-   The `-O' option can be used to override the file extension if needed:
-
+   The '-O' option can be used to override the file extension if needed:
 
 $ hledger balancesheet -o foo.txt -O html   # write HTML to foo.txt
 
    Some notes about JSON output:
 
    * This feature is marked experimental, and not yet much used; you
-     should expect our JSON to evolve. Real-world feedback is welcome.
+     should expect our JSON to evolve.  Real-world feedback is welcome.
 
    * Our JSON is rather large and verbose, as it is quite a faithful
-     representation of hledger's internal data types. To understand the
+     representation of hledger's internal data types.  To understand the
      JSON, read the Haskell type definitions, which are mostly in
      https://github.com/simonmichael/hledger/blob/master/hledger-lib/Hledger/Data/Types.hs.
 
-
    * hledger represents quantities as Decimal values storing up to 255
-     significant digits, eg for repeating decimals. Such numbers can
+     significant digits, eg for repeating decimals.  Such numbers can
      arise in practice (from automatically-calculated transaction
-     prices), and would break most JSON consumers. So in JSON, we show
-     quantities as simple Numbers with at most 10 decimal places. We
+     prices), and would break most JSON consumers.  So in JSON, we show
+     quantities as simple Numbers with at most 10 decimal places.  We
      don't limit the number of integer digits, but that part is under
-     your control. We hope this approach will not cause problems in
-     practice; if you find otherwise, please let us know. (Cf #1195)
+     your control.  We hope this approach will not cause problems in
+     practice; if you find otherwise, please let us know.  (Cf #1195)
 
    Notes about SQL output:
 
@@ -1707,14 +1653,13 @@ $ hledger balancesheet -o foo.txt -O html   # write HTML to foo.txt
 
    * SQL output is expected to work with sqlite, MySQL and PostgreSQL
 
-   * SQL output is structured with the expectations that statements
-     will be executed in the empty database. If you already have tables
+   * SQL output is structured with the expectations that statements will
+     be executed in the empty database.  If you already have tables
      created via SQL output of hledger, you would probably want to
-     either clear tables of existing data (via `delete' or `truncate'
+     either clear tables of existing data (via 'delete' or 'truncate'
      SQL statements) or drop tables completely as otherwise your
      postings will be duped.
 
-
 
 File: hledger.info,  Node: COMMANDS,  Next: JOURNAL FORMAT,  Prev: OUTPUT,  Up: Top
 
@@ -1722,10 +1667,10 @@ File: hledger.info,  Node: COMMANDS,  Next: JOURNAL FORMAT,  Prev: OUTPUT,  Up:
 ***********
 
 hledger provides a number of commands for producing reports and managing
-your data. Run `hledger' with no arguments to list the commands
-available, and `hledger CMD' to run a command. CMD can be the full
+your data.  Run 'hledger' with no arguments to list the commands
+available, and 'hledger CMD' to run a command.  CMD can be the full
 command name, or its standard abbreviation shown in the commands list,
-or any unambiguous prefix of the name. Eg: `hledger bal'.
+or any unambiguous prefix of the name.  Eg: 'hledger bal'.
 
    Here are the built-in commands, with the most often-used in bold:
 
@@ -1735,91 +1680,62 @@ or any unambiguous prefix of the name. Eg: `hledger bal'.
 journal file.
 
    * *add* - add transactions using guided prompts
-
    * *import* - add any new transactions from other files (eg csv)
 
    *Data management:*
 
    * check - check for various kinds of issue in the data
-
    * close (equity) - generate balance-resetting transactions
-
    * diff - compare account transactions in two journal files
-
    * rewrite - generate extra postings, similar to print -auto
 
    *Financial statements:*
 
    * *aregister (areg)* - show transactions in a particular account
-
    * *balancesheet (bs)* - show assets, liabilities and net worth
-
    * balancesheetequity (bse) - show assets, liabilities and equity
-
    * cashflow (cf) - show changes in liquid assets
-
    * *incomestatement (is)* - show revenues and expenses
-
    * roi - show return on investments
 
    *Miscellaneous reports:*
 
    * accounts - show account names
-
    * activity - show postings-per-interval bar charts
-
    * *balance (bal)* - show balance changes/end balances/budgets in any
      accounts
-
    * codes - show transaction codes
-
    * commodities - show commodity/currency symbols
-
    * descriptions - show unique transaction descriptions
-
    * files - show input file paths
-
    * help - show hledger user manuals in several formats
-
    * notes - show unique note segments of transaction descriptions
-
    * payees - show unique payee segments of transaction descriptions
-
    * prices - show market price records
-
    * *print* - show transactions (journal entries)
-
    * print-unique - show only transactions with unique descriptions
-
    * *register (reg)* - show postings in one or more accounts & running
      total
-
    * register-match - show a recent posting that best matches a
      description
-
    * stats - show journal statistics
-
    * tags - show tag names
-
    * test - run self tests
 
    *Add-on commands:*
 
-   Programs or scripts named `hledger-SOMETHING' in your PATH are
-add-on commands; these appear in the commands list with a `+' mark.
-Two of these are maintained and released with hledger:
+   Programs or scripts named 'hledger-SOMETHING' in your PATH are add-on
+commands; these appear in the commands list with a '+' mark.  Two of
+these are maintained and released with hledger:
 
    * *ui* - an efficient terminal interface (TUI) for hledger
-
    * *web* - a simple web interface (WUI) for hledger
 
    And these add-ons are maintained separately:
 
    * iadd - a more interactive alternative for the add command
-
    * interest - generates interest transactions according to various
      schemes
-
    * stockquotes - downloads market prices for your commodities from
      AlphaVantage _(experimental)_
 
@@ -1869,17 +1785,16 @@ accounts
 Show account names.
 
    This command lists account names, either declared with account
-directives (-declared), posted to (-used), or both (the default). With
+directives (-declared), posted to (-used), or both (the default).  With
 query arguments, only matched account names and account names referenced
-by matched postings are shown. 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
-components. Account names can be depth-clipped with `depth:N' or
-`--depth N' or `-N'.
+by matched postings are shown.  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
+components.  Account names can be depth-clipped with 'depth:N' or
+'--depth N' or '-N'.
 
    Examples:
 
-
 $ hledger accounts
 assets:bank:checking
 assets:bank:saving
@@ -1901,15 +1816,14 @@ 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
-default). With query arguments, it counts only matched transactions.
+default).  With query arguments, it counts only matched transactions.
 
    Examples:
 
-
 $ hledger activity --quarterly
 2008-01-01 **
 2008-04-01 *******
-2008-07-01
+2008-07-01 
 2008-10-01 **
 
 
@@ -1919,19 +1833,19 @@ File: hledger.info,  Node: add,  Next: aregister,  Prev: activity,  Up: COMMANDS
 ========
 
 add
-Prompt for transactions and add them to the journal. Any arguments will
+Prompt for transactions and add them to the journal.  Any arguments will
 be used as default inputs for the first N prompts.
 
    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
+'add' command, which prompts interactively on the console for new
 transactions, 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
+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 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 `.'
+   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 control-d or control-c to exit.
 
    Features:
@@ -1939,31 +1853,22 @@ or press control-d or control-c to exit.
    * add tries to provide useful defaults, using the most similar (by
      description) recent transaction (filtered by the query, if any) as
      a template.
-
    * You can also set the initial defaults with command line arguments.
-
    * Readline-style edit keys can be used during data entry.
-
    * The tab key will auto-complete whenever possible - accounts,
-     descriptions, dates (`yesterday', `today', `tomorrow').  If the
+     descriptions, dates ('yesterday', 'today', 'tomorrow').  If the
      input area is empty, it will insert the default value.
-
-   * If the journal defines a default commodity, it will be added to
-     any bare numbers entered.
-
+   * If the journal defines a default commodity, it will be added to any
+     bare numbers entered.
    * A parenthesised transaction code may be entered following a date.
-
    * Comments and tags may be entered following a description or amount.
-
-   * If you make a mistake, enter `<' at any prompt to go one step
+   * If you make a mistake, enter '<' at any prompt to go one step
      backward.
-
    * Input prompts are displayed in a different colour when the terminal
      supports it.
 
    Example (see the tutorial for a detailed explanation):
 
-
 $ hledger add
 Adding transactions to journal file /src/hledger/examples/sample.journal
 Any command line arguments will be used as defaults.
@@ -1973,18 +1878,18 @@ An optional ; COMMENT may follow descriptions or amounts.
 If you make a mistake, enter < at any prompt to go one step backward.
 To end a transaction, enter . when prompted.
 To quit, enter . at a date prompt or press control-d or control-c.
-Date [2015/05/22]:
+Date [2015/05/22]: 
 Description: supermarket
 Account 1: expenses:food
 Amount  1: $10
 Account 2: assets:checking
-Amount  2 [$-10.0]:
+Amount  2 [$-10.0]: 
 Account 3 (or . or enter to finish this transaction): .
 2015/05/22 supermarket
     expenses:food             $10
     assets:checking        $-10.0
 
-Save this transaction to the journal ? [y]:
+Save this transaction to the journal ? [y]: 
 Saved.
 Starting the next transaction (. or ctrl-D/ctrl-C to quit)
 Date [2015/05/22]: <CTRL-D> $
@@ -1999,57 +1904,56 @@ File: hledger.info,  Node: aregister,  Next: balance,  Prev: add,  Up: COMMANDS
 ==============
 
 aregister, areg
-Show the transactions and running historical balance in an account, with
-each line item representing one transaction.
 
-   `aregister' shows the transactions affecting a particular account
-and its subaccounts, with each line item representing a whole
-transaction - as in bank statements, hledger-ui, hledger-web and other
-accounting apps.
+   Show the transactions and running historical balance in an account,
+with each line item representing one transaction.
 
-   Note this is unlike the `register' command, which shows individual
+   'aregister' shows the transactions affecting a particular account and
+its subaccounts, with each line item representing a whole transaction -
+as in bank statements, hledger-ui, hledger-web and other accounting
+apps.
+
+   Note this is unlike the 'register' command, which shows individual
 postings and does not always show a single account or a historical
 balance.
 
    A reminder, "historical" balances include any balance from
 transactions before the report start date, so (if opening balances are
-recorded correctly) `aregister' will show the real-world balances of an
+recorded correctly) 'aregister' will show the real-world balances of an
 account, as you would see in a bank statement.
 
-   As a quick rule of thumb, use `aregister' for reconciling real-world
-asset/liability accounts and `register' for reviewing detailed
+   As a quick rule of thumb, use 'aregister' for reconciling real-world
+asset/liability accounts and 'register' for reviewing detailed
 revenues/expenses.
 
-   `aregister' shows the register for just one account (and its
-subaccounts). This account must be specified as the first argument. You
-can write either the full account name, or a case-insensitive regular
-expression which will select the alphabetically first matched account.
-(Eg if you have `assets:aaa:checking' and `assets:bbb:checking'
-accounts, `hledger areg checking' would select `assets:aaa:checking'.)
+   'aregister' shows the register for just one account (and its
+subaccounts).  This account must be specified as the first argument.
+You can write either the full account name, or a case-insensitive
+regular expression which will select the alphabetically first matched
+account.  (Eg if you have 'assets:aaa:checking' and
+'assets:bbb:checking' accounts, 'hledger areg checking' would select
+'assets:aaa:checking'.)
 
    Any additional arguments form a query which will filter the
 transactions shown.
 
-   Each `aregister' line item shows:
+   Each 'aregister' line item shows:
 
    * the transaction's date (or the relevant posting's date if
      different, see below)
-
    * the names of all the other account(s) involved in this transaction
      (probably abbreviated)
-
    * the total change to this account's balance from this transaction
-
    * the account's historical running balance after this transaction.
 
    Transactions making a net change of zero are not shown by default;
-add the `-E/--empty' flag to show them.
+add the '-E/--empty' flag to show them.
 
-   `aregister' ignores a depth limit, so its final total will always
+   'aregister' ignores a depth limit, so its final total will always
 match a balance report with similar arguments.
 
    This command also supports the output destination and output format
-options The output formats supported are `txt', `csv', and `json'.
+options The output formats supported are 'txt', 'csv', and 'json'.
 
 * Menu:
 
@@ -2063,26 +1967,24 @@ File: hledger.info,  Node: aregister and custom posting dates,  Up: aregister
 
 Transactions whose date is outside the report period can still be shown,
 if they have a posting to this account dated inside the report period.
-(And in this case it's the posting date that is shown.) This ensures
-that `aregister' can show an accurate historical running balance,
-matching the one shown by `register -H' with the same arguments.
+(And in this case it's the posting date that is shown.)  This ensures
+that 'aregister' can show an accurate historical running balance,
+matching the one shown by 'register -H' with the same arguments.
 
-   To filter strictly by transaction date instead, add the
-`--txn-dates' flag. If you use this flag and some of your postings have
-custom dates, it's probably best to assume the running balance is wrong.
+   To filter strictly by transaction date instead, add the '--txn-dates'
+flag.  If you use this flag and some of your postings have custom dates,
+it's probably best to assume the running balance is wrong.
 
    Examples:
 
    Show all transactions and historical running balance in the first
 account whose name contains "checking":
 
-
 $ hledger areg checking
 
    Show transactions and historical running balance in all asset
 accounts during july:
 
-
 $ hledger areg assets date:jul
 
 
@@ -2094,15 +1996,15 @@ File: hledger.info,  Node: balance,  Next: balancesheet,  Prev: aregister,  Up:
 balance, bal
 Show accounts and their balances.
 
-   `balance' is one of hledger's oldest and most versatile commands,
-for listing account balances, balance changes, values, value changes and
-more, during one time period or many. Generally it shows a table, with
+   'balance' is one of hledger's oldest and most versatile commands, for
+listing account balances, balance changes, values, value changes and
+more, during one time period or many.  Generally it shows a table, with
 rows representing accounts, and columns representing periods.
 
-   Note there are some higher-level variants of the `balance' command
-with convenient defaults, which can be simpler to use: `balancesheet',
-`balancesheetequity', `cashflow' and `incomestatement'. When you need
-more control, then use `balance'.
+   Note there are some higher-level variants of the 'balance' command
+with convenient defaults, which can be simpler to use: 'balancesheet',
+'balancesheetequity', 'cashflow' and 'incomestatement'.  When you need
+more control, then use 'balance'.
 
 * Menu:
 
@@ -2126,69 +2028,54 @@ File: hledger.info,  Node: balance features,  Next: Simple balance report,  Up:
 11.5.1 balance features
 -----------------------
 
-Here's a quick overview of the `balance' command's features, followed
-by more detailed descriptions and examples. Many of these work with the
+Here's a quick overview of the 'balance' command's features, followed by
+more detailed descriptions and examples.  Many of these work with the
 higher-level commands as well.
 
-   `balance' can show..
-
-   * accounts as a list (`-l') or a tree (`-t')
-
-   * optionally depth-limited (`-[1-9]')
+   'balance' can show..
 
+   * accounts as a list ('-l') or a tree ('-t')
+   * optionally depth-limited ('-[1-9]')
    * sorted by declaration order and name, or by amount
 
    ..and their..
 
    * balance changes (the default)
-
-   * or actual and planned balance changes (`--budget')
-
-   * or value of balance changes (`-V')
-
-   * or change of balance values (`--valuechange')
+   * or actual and planned balance changes ('--budget')
+   * or value of balance changes ('-V')
+   * or change of balance values ('--valuechange')
 
    ..in..
 
    * one time period (the whole journal period by default)
-
-   * or multiple periods (`-D', `-W', `-M', `-Q', `-Y', `-p INTERVAL')
+   * or multiple periods ('-D', '-W', '-M', '-Q', '-Y', '-p INTERVAL')
 
    ..either..
 
    * per period (the default)
-
-   * or accumulated since report start date (`--cumulative')
-
-   * or accumulated since account creation (`--historical/-H')
+   * or accumulated since report start date ('--cumulative')
+   * or accumulated since account creation ('--historical/-H')
 
    ..possibly converted to..
 
-   * cost (`--value=cost[,COMM]'/`--cost'/`-B')
-
-   * or market value, as of transaction dates (`--value=then[,COMM]')
-
-   * or at period ends (`--value=end[,COMM]')
-
-   * or now (`--value=now')
-
-   * or at some other date (`--value=YYYY-MM-DD')
+   * cost ('--value=cost[,COMM]'/'--cost'/'-B')
+   * or market value, as of transaction dates ('--value=then[,COMM]')
+   * or at period ends ('--value=end[,COMM]')
+   * or now ('--value=now')
+   * or at some other date ('--value=YYYY-MM-DD')
 
    ..with..
 
-   * totals (`-T'), averages (`-A'), percentages (`-%'), inverted sign
-     (`--invert')
-
-   * rows and columns swapped (`--transpose')
-
-   * another field used as account name (`--pivot')
-
+   * totals ('-T'), averages ('-A'), percentages ('-%'), inverted sign
+     ('--invert')
+   * rows and columns swapped ('--transpose')
+   * another field used as account name ('--pivot')
    * custom-formatted line items (single-period reports only)
-     (`--format')
+     ('--format')
 
    This command supports the output destination and output format
-options, with output formats `txt', `csv', `json', and (multi-period
-reports only:) `html'. In `txt' output in a colour-supporting terminal,
+options, with output formats 'txt', 'csv', 'json', and (multi-period
+reports only:) 'html'.  In 'txt' output in a colour-supporting terminal,
 negative amounts are shown in red.
 
 
@@ -2197,17 +2084,16 @@ File: hledger.info,  Node: Simple balance report,  Next: Filtered balance report
 11.5.2 Simple balance report
 ----------------------------
 
-With no arguments, `balance' shows a list of all accounts and their
+With no arguments, 'balance' shows a list of all accounts and their
 change of balance - ie, the sum of posting amounts, both inflows and
-outflows - during the entire period of the journal. For real-world
+outflows - during the entire period of the journal.  For real-world
 accounts, this should also match their end balance at the end of the
 journal period (more on this below).
 
    Accounts are sorted by declaration order if any, and then
-alphabetically by account name. For instance, using
+alphabetically by account name.  For instance, using
 examples/sample.journal:
 
-
 $ hledger bal
                   $1  assets:bank:saving
                  $-2  assets:cash
@@ -2217,12 +2103,11 @@ $ hledger bal
                  $-1  income:salary
                   $1  liabilities:debts
 --------------------
-                   0
+                   0  
 
    Accounts with a zero balance (and no non-zero subaccounts, in tree
-mode - see below) are hidden by default. Use `-E/--empty' to show them
-(revealing `assets:bank:checking' here):
-
+mode - see below) are hidden by default.  Use '-E/--empty' to show them
+(revealing 'assets:bank:checking' here):
 
 $ hledger -f examples/sample.journal  bal  -E
                    0  assets:bank:checking
@@ -2234,10 +2119,10 @@ $ hledger -f examples/sample.journal  bal  -E
                  $-1  income:salary
                   $1  liabilities:debts
 --------------------
-                   0
+                   0  
 
    The total of the amounts displayed is shown as the last line, unless
-`-N'/`--no-total' is used.
+'-N'/'--no-total' is used.
 
 
 File: hledger.info,  Node: Filtered balance report,  Next: List or tree mode,  Prev: Simple balance report,  Up: balance
@@ -2246,14 +2131,13 @@ File: hledger.info,  Node: Filtered balance report,  Next: List or tree mode,  P
 ------------------------------
 
 You can show fewer accounts, a different time period, totals from
-cleared transactions only, etc. by using query arguments or options to
-limit the postings being matched. Eg:
-
+cleared transactions only, etc.  by using query arguments or options to
+limit the postings being matched.  Eg:
 
 $ hledger bal --cleared assets date:200806
                  $-2  assets:cash
 --------------------
-                 $-2
+                 $-2  
 
 
 File: hledger.info,  Node: List or tree mode,  Next: Depth limiting,  Prev: Filtered balance report,  Up: balance
@@ -2261,13 +2145,12 @@ File: hledger.info,  Node: List or tree mode,  Next: Depth limiting,  Prev: Filt
 11.5.4 List or tree mode
 ------------------------
 
-By default, or with `-l/--flat', accounts are shown as a flat list with
+By default, or with '-l/--flat', accounts are shown as a flat list with
 their full names visible, as in the examples above.
 
-   With `-t/--tree', the account hierarchy is shown, with subaccounts'
+   With '-t/--tree', the account hierarchy is shown, with subaccounts'
 "leaf" names indented below their parent:
 
-
 $ hledger balance
                  $-1  assets
                   $1    bank:saving
@@ -2285,33 +2168,31 @@ $ hledger balance
    Notes:
 
    * "Boring" accounts are combined with their subaccount for more
-     compact output, unless `--no-elide' is used. Boring accounts have
-     no balance of their own and just one subaccount (eg `assets:bank'
-     and `liabilities' above).
+     compact output, unless '--no-elide' is used.  Boring accounts have
+     no balance of their own and just one subaccount (eg 'assets:bank'
+     and 'liabilities' above).
 
    * All balances shown are "inclusive", ie including the balances from
-     all subaccounts. Note this means some repetition in the output,
+     all subaccounts.  Note this means some repetition in the output,
      which requires explanation when sharing reports with
-     non-plaintextaccounting-users. A tree mode report's final total is
+     non-plaintextaccounting-users.  A tree mode report's final total is
      the sum of the top-level balances shown, not of all the balances
      shown.
 
    * Each group of sibling accounts (ie, under a common parent) is
      sorted separately.
 
-
 
 File: hledger.info,  Node: Depth limiting,  Next: Multi-period balance report,  Prev: List or tree mode,  Up: balance
 
 11.5.5 Depth limiting
 ---------------------
 
-With a `depth:N' query, or `--depth N' option, or just `-N', balance
+With a 'depth:N' query, or '--depth N' option, or just '-N', balance
 reports will show accounts only to the specified depth, hiding the
-deeper subaccounts. Account balances at the depth limit always include
-the balances from any hidden subaccounts (even in list mode). This can
-be useful for getting an overview. Eg, limiting to depth 1:
-
+deeper subaccounts.  Account balances at the depth limit always include
+the balances from any hidden subaccounts (even in list mode).  This can
+be useful for getting an overview.  Eg, limiting to depth 1:
 
 $ hledger balance -N -1
                  $-1  assets
@@ -2319,15 +2200,14 @@ $ hledger balance -N -1
                  $-2  income
                   $1  liabilities
 
-   You can also hide top-level account name parts, using `--drop N'.
+   You can also hide top-level account name parts, using '--drop N'.
 This can be useful for hiding repetitive top-level account names:
 
-
 $ hledger bal expenses --drop 1
                   $1  food
                   $1  supplies
 --------------------
-                  $2
+                  $2  
 
 
 File: hledger.info,  Node: Multi-period balance report,  Next: Sorting by amount,  Prev: Depth limiting,  Up: balance
@@ -2335,66 +2215,53 @@ File: hledger.info,  Node: Multi-period balance report,  Next: Sorting by amount
 11.5.6 Multi-period balance report
 ----------------------------------
 
-With a report interval (set by the `-D/--daily', `-W/--weekly',
-`-M/--monthly', `-Q/--quarterly', `-Y/--yearly', or `-p/--period'
-flag), `balance' shows a tabular report, with columns representing
-successive time periods (and a title):
-
+With a report interval (set by the '-D/--daily', '-W/--weekly',
+'-M/--monthly', '-Q/--quarterly', '-Y/--yearly', or '-p/--period' flag),
+'balance' shows a tabular report, with columns representing successive
+time periods (and a title):
 
 $ hledger balance --quarterly income expenses -E
 Balance changes in 2008:
 
-                   ||  2008q1  2008q2  2008q3  2008q4
+                   ||  2008q1  2008q2  2008q3  2008q4 
 ===================++=================================
- expenses:food     ||       0      $1       0       0
- expenses:supplies ||       0      $1       0       0
- income:gifts      ||       0     $-1       0       0
- income:salary     ||     $-1       0       0       0
+ expenses:food     ||       0      $1       0       0 
+ expenses:supplies ||       0      $1       0       0 
+ income:gifts      ||       0     $-1       0       0 
+ income:salary     ||     $-1       0       0       0 
 -------------------++---------------------------------
-                   ||     $-1      $1       0       0
+                   ||     $-1      $1       0       0 
 
    Notes:
 
    * The report's start/end dates will be expanded, if necessary, to
      fully encompass the displayed subperiods (so that the first and
      last subperiods have the same duration as the others).
-
    * Leading and trailing periods (columns) containing all zeroes are
-     not shown, unless `-E/--empty' is used.
-
+     not shown, unless '-E/--empty' is used.
    * Accounts (rows) containing all zeroes are not shown, unless
-     `-E/--empty' is used.
-
+     '-E/--empty' is used.
    * Amounts with many commodities are shown in abbreviated form, unless
-     `--no-elide' is used. _(experimental)_
-
-   * Average and/or total columns can be added with the `-A/--average'
-     and `-T/--row-total' flags.
-
-   * The `--transpose' flag can be used to exchange rows and columns.
-
-   * The `--pivot FIELD' option causes a different transaction field to
-     be used as "account name". See PIVOTING.
+     '--no-elide' is used.  _(experimental)_
+   * Average and/or total columns can be added with the '-A/--average'
+     and '-T/--row-total' flags.
+   * The '--transpose' flag can be used to exchange rows and columns.
+   * The '--pivot FIELD' option causes a different transaction field to
+     be used as "account name".  See PIVOTING.
 
    Multi-period reports with many periods can be too wide for easy
-viewing in the terminal. Here are some ways to handle that:
-
-   * Hide the totals row with `-N/--no-total'
-
-   * Convert to a single currency with `-V'
+viewing in the terminal.  Here are some ways to handle that:
 
+   * Hide the totals row with '-N/--no-total'
+   * Convert to a single currency with '-V'
    * Maximize the terminal window
-
    * Reduce the terminal's font size
-
-   * View with a pager like less, eg: `hledger bal -D --color=yes |
-     less -RS'
-
-   * Output as CSV and use a CSV viewer like visidata (`hledger bal -D
-     -O csv | vd -f csv'), Emacs' csv-mode (`M-x csv-mode, C-c C-a'),
-     or a spreadsheet (`hledger bal -D -o a.csv && open a.csv')
-
-   * Output as HTML and view with a browser: `hledger bal -D -o a.html
+   * View with a pager like less, eg: 'hledger bal -D --color=yes | less
+     -RS'
+   * Output as CSV and use a CSV viewer like visidata ('hledger bal -D
+     -O csv | vd -f csv'), Emacs' csv-mode ('M-x csv-mode, C-c C-a'), or
+     a spreadsheet ('hledger bal -D -o a.csv && open a.csv')
+   * Output as HTML and view with a browser: 'hledger bal -D -o a.html
      && open a.html'
 
 
@@ -2403,14 +2270,14 @@ File: hledger.info,  Node: Sorting by amount,  Next: Percentages,  Prev: Multi-p
 11.5.7 Sorting by amount
 ------------------------
 
-With `-S/--sort-amount', accounts with the largest (most positive)
-balances are shown first. Eg: `hledger bal expenses -MAS' shows your
+With '-S/--sort-amount', accounts with the largest (most positive)
+balances are shown first.  Eg: 'hledger bal expenses -MAS' shows your
 biggest averaged monthly expenses first.
 
    Revenues and liability balances are typically negative, however, so
-`-S' shows these in reverse order. To work around this, you can add
-`--invert' to flip the signs. (Or, use one of the higher-level reports,
-which flip the sign automatically. Eg: `hledger incomestatement -MAS').
+'-S' shows these in reverse order.  To work around this, you can add
+'--invert' to flip the signs.  (Or, use one of the higher-level reports,
+which flip the sign automatically.  Eg: 'hledger incomestatement -MAS').
 
 
 File: hledger.info,  Node: Percentages,  Next: Balance change end balance,  Prev: Sorting by amount,  Up: balance
@@ -2418,33 +2285,30 @@ File: hledger.info,  Node: Percentages,  Next: Balance change end balance,  Prev
 11.5.8 Percentages
 ------------------
 
-With `-%/--percent', balance reports show each account's value
-expressed as a percentage of the (column) total:
-
+With '-%/--percent', balance reports show each account's value expressed
+as a percentage of the (column) total:
 
 $ hledger bal expenses -Q -%
 Balance changes in 2008:
 
-                   || 2008Q1   2008Q2  2008Q3  2008Q4
+                   || 2008Q1   2008Q2  2008Q3  2008Q4 
 ===================++=================================
- expenses:food     ||      0   50.0 %       0       0
- expenses:supplies ||      0   50.0 %       0       0
+ expenses:food     ||      0   50.0 %       0       0 
+ expenses:supplies ||      0   50.0 %       0       0 
 -------------------++---------------------------------
-                   ||      0  100.0 %       0       0
+                   ||      0  100.0 %       0       0 
 
    Note it is not useful to calculate percentages if the amounts in a
-column have mixed signs. In this case, make a separate report for each
+column have mixed signs.  In this case, make a separate report for each
 sign, eg:
 
-
 $ hledger bal -% amt:`>0`
 $ hledger bal -% amt:`<0`
 
    Similarly, if the amounts in a column have mixed commodities, convert
-them to one commodity with `-B', `-V', `-X' or `--value', or make a
+them to one commodity with '-B', '-V', '-X' or '--value', or make a
 separate report for each commodity:
 
-
 $ hledger bal -% cur:\\$
 $ hledger bal -% cur:€
 
@@ -2455,25 +2319,25 @@ File: hledger.info,  Node: Balance change end balance,  Next: Balance report typ
 ----------------------------------
 
 It's important to be clear on the meaning of the numbers shown in
-balance reports. Here is some terminology we use:
+balance reports.  Here is some terminology we use:
 
    A *_balance change_* is the net amount added to, or removed from, an
 account during some period.
 
-   An *_end balance_* is the amount accumulated in an account as of
-some date (and some time, but hledger doesn't store that; assume end of
-day in your timezone). It is the sum of previous balance changes.
+   An *_end balance_* is the amount accumulated in an account as of some
+date (and some time, but hledger doesn't store that; assume end of day
+in your timezone).  It is the sum of previous balance changes.
 
    We call it a *_historical end balance_* if it includes all balance
-changes since the account was created. For a real world account, this
-means it will match the "historical record", eg the balances reported
-in your bank statements or bank web UI. (If they are correct!)
+changes since the account was created.  For a real world account, this
+means it will match the "historical record", eg the balances reported in
+your bank statements or bank web UI. (If they are correct!)
 
    In general, balance changes are what you want to see when reviewing
 revenues and expenses, and historical end balances are what you want to
 see when reviewing or reconciling asset, liability and equity accounts.
 
-   `balance' shows balance changes by default. To see accurate
+   'balance' shows balance changes by default.  To see accurate
 historical end balances:
 
   1. Initialise account starting balances with an "opening balances"
@@ -2482,10 +2346,9 @@ historical end balances:
 
   2. Include all of of the account's prior postings in the report, by
      not specifying a report start date, or by using the
-     `-H/--historical' flag. (`-H' causes report start date to be
+     '-H/--historical' flag.  ('-H' causes report start date to be
      ignored when summing postings.)
 
-
 
 File: hledger.info,  Node: Balance report types,  Next: Useful balance reports,  Prev: Balance change end balance,  Up: balance
 
@@ -2494,101 +2357,91 @@ File: hledger.info,  Node: Balance report types,  Next: Useful balance reports,
 
 For more flexible reporting, there are three important option groups:
 
-   `hledger balance [CALCULATIONTYPE] [ACCUMULATIONTYPE]
-[VALUATIONTYPE] ...'
+   'hledger balance [CALCULATIONTYPE] [ACCUMULATIONTYPE] [VALUATIONTYPE]
+...'
 
    The first two are the most important: calculation type selects the
 basic calculation to perform for each table cell, while accumulation
 type says which postings should be included in each cell's calculation.
 Typically one or both of these are selected by default, so you don't
-need to write them explicitly. A valuation type can be added if you
+need to write them explicitly.  A valuation type can be added if you
 want to convert the basic report to value or cost.
 
    *Calculation type:*
-The basic calculation to perform for each table cell. It is one of:
+The basic calculation to perform for each table cell.  It is one of:
 
-   * `--sum' : sum the posting amounts (*default*)
-
-   * `--budget' : like -sum but also show a goal amount
-
-   * `--valuechange' : show the change in period-end historical balance
+   * '--sum' : sum the posting amounts (*default*)
+   * '--budget' : like -sum but also show a goal amount
+   * '--valuechange' : show the change in period-end historical balance
      values
 
    *Accumulation type:*
-Which postings should be included in each cell's calculation. It is one
+Which postings should be included in each cell's calculation.  It is one
 of:
 
-   * `--change' : postings from column start to column end, ie within
-     the cell's period. Typically used to see revenues/expenses.
+   * '--change' : postings from column start to column end, ie within
+     the cell's period.  Typically used to see revenues/expenses.
      (*default for balance, incomestatement*)
 
-   * `--cumulative' : postings from report start to column end, eg to
-     show changes accumulated since the report's start date. Rarely
+   * '--cumulative' : postings from report start to column end, eg to
+     show changes accumulated since the report's start date.  Rarely
      used.
 
-   * `--historical/-H' : postings from journal start to column end, ie
+   * '--historical/-H' : postings from journal start to column end, ie
      all postings from account creation to the end of the cell's period.
      Typically used to see historical end balances of
-     assets/liabilities/equity. (*default for balancesheet,
+     assets/liabilities/equity.  (*default for balancesheet,
      balancesheetequity, cashflow*)
 
-
    *Valuation type:*
 Which kind of valuation, valuation date(s) and optionally a target
-valuation commodity to use. It is one of:
+valuation commodity to use.  It is one of:
 
    * no valuation, show amounts in their original commodities
      (*default*)
-
-   * `--value=cost[,COMM]' : no valuation, show amounts converted to
+   * '--value=cost[,COMM]' : no valuation, show amounts converted to
      cost
+   * '--value=then[,COMM]' : show value at transaction dates
+   * '--value=end[,COMM]' : show value at period end date(s) (*default
+     with '--valuechange'*)
+   * '--value=now[,COMM]' : show value at today's date
+   * '--value=YYYY-MM-DD[,COMM]' : show value at another date
 
-   * `--value=then[,COMM]' : show value at transaction dates
-
-   * `--value=end[,COMM]' : show value at period end date(s) (*default
-     with `--valuechange'*)
-
-   * `--value=now[,COMM]' : show value at today's date
-
-   * `--value=YYYY-MM-DD[,COMM]' : show value at another date
-
-   or one of their aliases: `--cost/-B', `--market/-V' or
-`--exchange/-X'.
+   or one of their aliases: '--cost/-B', '--market/-V' or
+'--exchange/-X'.
 
    Most combinations of these options should produce reasonable reports,
-but if you find any that seem wrong or misleading, let us know. The
+but if you find any that seem wrong or misleading, let us know.  The
 following restrictions are applied:
 
-   * `--valuechange' implies `--value=end'
-
-   * `--valuechange' makes `--change' the default when used with the
-     `balancesheet'/`balancesheetequity' commands
-
-   * `--cumulative' or `--historical' disables `--row-total/-T'
+   * '--valuechange' implies '--value=end'
+   * '--valuechange' makes '--change' the default when used with the
+     'balancesheet'/'balancesheetequity' commands
+   * '--cumulative' or '--historical' disables '--row-total/-T'
 
    For reference, here is what the combinations of accumulation and
 valuation show:
 
-Valuation:no valuation      `--value= then'   `--value= end'   `--value=
->Accumulation:                                                     YYYY-MM-DD
+Valuation:no valuation      '--value= then'   '--value= end'   '--value=
+>Accumulation:                                                 YYYY-MM-DD
 v                                                              /now'
------------------------------------------------------------------------------- 
-`--change'change in period  sum of            period-end       DATE-value of
-                            posting-date      value of change  change in
-                            market values in  in period        period
-                            period                             
-`--cumulative'change from       sum of            period-end       DATE-value of
-          report start to   posting-date      value of change  change from
-          period end        market values     from report      report start
-                            from report       start to period  to period end
-                            start to period   end              
-                            end                                
-`--historicalchange from       sum of            period-end       DATE-value of
-/-H'      journal start to  posting-date      value of change  change from
-          period end        market values     from journal     journal start
-          (historical end   from journal      start to period  to period end
-          balance)          start to period   end              
-                            end                                
+------------------------------------------------------------------------------
+'--change'change in         sum of            period-end       DATE-value
+          period            posting-date      value of         of change in
+                            market values     change in        period
+                            in period         period
+'--cumulative'change from   sum of            period-end       DATE-value
+          report start to   posting-date      value of         of change
+          period end        market values     change from      from report
+                            from report       report start     start to
+                            start to period   to period end    period end
+                            end
+'--historicalchange from    sum of            period-end       DATE-value
+/-H'      journal start     posting-date      value of         of change
+          to period end     market values     change from      from journal
+          (historical end   from journal      journal start    start to
+          balance)          start to period   to period end    period end
+                            end
 
 
 File: hledger.info,  Node: Useful balance reports,  Next: Budget report,  Prev: Balance report types,  Up: balance
@@ -2596,57 +2449,54 @@ File: hledger.info,  Node: Useful balance reports,  Next: Budget report,  Prev:
 11.5.11 Useful balance reports
 ------------------------------
 
-Some frequently used `balance' options/reports are:
+Some frequently used 'balance' options/reports are:
 
-   * `bal -M revenues expenses'
-     Show revenues/expenses in each month. Also available as the
-     `incomestatement' command.
+   * 'bal -M revenues expenses'
+     Show revenues/expenses in each month.  Also available as the
+     'incomestatement' command.
 
-   * `bal -M -H assets liabilities'
-     Show historical asset/liability balances at each month end. Also
-     available as the `balancesheet' command.
+   * 'bal -M -H assets liabilities'
+     Show historical asset/liability balances at each month end.  Also
+     available as the 'balancesheet' command.
 
-   * `bal -M -H assets liabilities equity'
+   * 'bal -M -H assets liabilities equity'
      Show historical asset/liability/equity balances at each month end.
-     Also available as the `balancesheetequity' command.
-
-   * `bal -M assets not:receivable'
-     Show changes to liquid assets in each month. Also available as the
-     `cashflow' command.
+     Also available as the 'balancesheetequity' command.
 
+   * 'bal -M assets not:receivable'
+     Show changes to liquid assets in each month.  Also available as the
+     'cashflow' command.
 
    Also:
 
-   * `bal -M expenses -2 -SA'
+   * 'bal -M expenses -2 -SA'
      Show monthly expenses summarised to depth 2 and sorted by average
      amount.
 
-   * `bal -M --budget expenses'
+   * 'bal -M --budget expenses'
      Show monthly expenses and budget goals.
 
-   * `bal -M --valuechange investments'
+   * 'bal -M --valuechange investments'
      Show monthly change in market value of investment assets.
 
-   * `bal investments --valuechange -D date:lastweek amt:'>1000' -STA
+   * 'bal investments --valuechange -D date:lastweek amt:'>1000' -STA
      [--invert]'
      Show top gainers [or losers] last week
 
-
 
 File: hledger.info,  Node: Budget report,  Next: Customising single-period balance reports,  Prev: Useful balance reports,  Up: balance
 
 11.5.12 Budget report
 ---------------------
 
-The `--budget' report type activates extra columns showing any budget
-goals for each account and period. The budget goals are defined by
-periodic transactions. This is very useful for comparing planned and
+The '--budget' report type activates extra columns showing any budget
+goals for each account and period.  The budget goals are defined by
+periodic transactions.  This is very useful for comparing planned and
 actual income, expenses, time usage, etc.
 
    For example, you can take average monthly expenses in the common
 expense categories to construct a minimal monthly budget:
 
-
 ;; Budget
 ~ monthly
   income  $2000
@@ -2673,85 +2523,81 @@ expense categories to construct a minimal monthly budget:
 
    You can now see a monthly budget report:
 
-
 $ hledger balance -M --budget
 Budget performance in 2017/11/01-2017/12/31:
 
-                      ||                      Nov                       Dec
+                      ||                      Nov                       Dec 
 ======================++====================================================
- assets               || $-2445 [  99% of $-2480]  $-2665 [ 107% of $-2480]
- assets:bank          || $-2445 [  99% of $-2480]  $-2665 [ 107% of $-2480]
- assets:bank:checking || $-2445 [  99% of $-2480]  $-2665 [ 107% of $-2480]
- expenses             ||   $495 [ 103% of   $480]    $565 [ 118% of   $480]
- expenses:bus         ||    $49 [  98% of    $50]     $53 [ 106% of    $50]
- expenses:food        ||   $396 [  99% of   $400]    $412 [ 103% of   $400]
- expenses:movies      ||    $30 [ 100% of    $30]       0 [   0% of    $30]
- income               ||  $1950 [  98% of  $2000]   $2100 [ 105% of  $2000]
+ assets               || $-2445 [  99% of $-2480]  $-2665 [ 107% of $-2480] 
+ assets:bank          || $-2445 [  99% of $-2480]  $-2665 [ 107% of $-2480] 
+ assets:bank:checking || $-2445 [  99% of $-2480]  $-2665 [ 107% of $-2480] 
+ expenses             ||   $495 [ 103% of   $480]    $565 [ 118% of   $480] 
+ expenses:bus         ||    $49 [  98% of    $50]     $53 [ 106% of    $50] 
+ expenses:food        ||   $396 [  99% of   $400]    $412 [ 103% of   $400] 
+ expenses:movies      ||    $30 [ 100% of    $30]       0 [   0% of    $30] 
+ income               ||  $1950 [  98% of  $2000]   $2100 [ 105% of  $2000] 
 ----------------------++----------------------------------------------------
-                      ||      0 [              0]       0 [              0]
+                      ||      0 [              0]       0 [              0] 
 
    This is different from a normal balance report in several ways:
 
-   * Only accounts with budget goals during the report period are
-     shown, by default.
+   * Only accounts with budget goals during the report period are shown,
+     by default.
 
    * In each column, in square brackets after the actual amount, budget
-     goal amounts are shown, and the actual/goal percentage. (Note:
+     goal amounts are shown, and the actual/goal percentage.  (Note:
      budget goals should be in the same commodity as the actual amount.)
 
-   * All parent accounts are always shown, even in list mode. Eg assets,
-     assets:bank, and expenses above.
+   * All parent accounts are always shown, even in list mode.  Eg
+     assets, assets:bank, and expenses above.
 
    * Amounts always include all subaccounts, budgeted or unbudgeted,
      even in list mode.
 
-
-   This means that the numbers displayed will not always add up! Eg
-above, the `expenses' actual amount includes the gifts and supplies
-transactions, but the `expenses:gifts' and `expenses:supplies' accounts
+   This means that the numbers displayed will not always add up!  Eg
+above, the 'expenses' actual amount includes the gifts and supplies
+transactions, but the 'expenses:gifts' and 'expenses:supplies' accounts
 are not shown, as they have no budget amounts declared.
 
-   This can be confusing. When you need to make things clearer, use the
-`-E/--empty' flag, which will reveal all accounts including unbudgeted
-ones, giving the full picture. Eg:
-
+   This can be confusing.  When you need to make things clearer, use the
+'-E/--empty' flag, which will reveal all accounts including unbudgeted
+ones, giving the full picture.  Eg:
 
 $ hledger balance -M --budget --empty
 Budget performance in 2017/11/01-2017/12/31:
 
-                      ||                      Nov                       Dec
+                      ||                      Nov                       Dec 
 ======================++====================================================
- assets               || $-2445 [  99% of $-2480]  $-2665 [ 107% of $-2480]
- assets:bank          || $-2445 [  99% of $-2480]  $-2665 [ 107% of $-2480]
- assets:bank:checking || $-2445 [  99% of $-2480]  $-2665 [ 107% of $-2480]
- expenses             ||   $495 [ 103% of   $480]    $565 [ 118% of   $480]
- expenses:bus         ||    $49 [  98% of    $50]     $53 [ 106% of    $50]
- expenses:food        ||   $396 [  99% of   $400]    $412 [ 103% of   $400]
- expenses:gifts       ||      0                      $100
- expenses:movies      ||    $30 [ 100% of    $30]       0 [   0% of    $30]
- expenses:supplies    ||    $20                         0
- income               ||  $1950 [  98% of  $2000]   $2100 [ 105% of  $2000]
+ assets               || $-2445 [  99% of $-2480]  $-2665 [ 107% of $-2480] 
+ assets:bank          || $-2445 [  99% of $-2480]  $-2665 [ 107% of $-2480] 
+ assets:bank:checking || $-2445 [  99% of $-2480]  $-2665 [ 107% of $-2480] 
+ expenses             ||   $495 [ 103% of   $480]    $565 [ 118% of   $480] 
+ expenses:bus         ||    $49 [  98% of    $50]     $53 [ 106% of    $50] 
+ expenses:food        ||   $396 [  99% of   $400]    $412 [ 103% of   $400] 
+ expenses:gifts       ||      0                      $100                   
+ expenses:movies      ||    $30 [ 100% of    $30]       0 [   0% of    $30] 
+ expenses:supplies    ||    $20                         0                   
+ income               ||  $1950 [  98% of  $2000]   $2100 [ 105% of  $2000] 
 ----------------------++----------------------------------------------------
-                      ||      0 [              0]       0 [              0]
-
-   You can roll over unspent budgets to next period with `--cumulative':
+                      ||      0 [              0]       0 [              0] 
 
+   You can roll over unspent budgets to next period with '--cumulative':
 
 $ hledger balance -M --budget --cumulative
 Budget performance in 2017/11/01-2017/12/31:
 
-                      ||                      Nov                       Dec
+                      ||                      Nov                       Dec 
 ======================++====================================================
- assets               || $-2445 [  99% of $-2480]  $-5110 [ 103% of $-4960]
- assets:bank          || $-2445 [  99% of $-2480]  $-5110 [ 103% of $-4960]
- assets:bank:checking || $-2445 [  99% of $-2480]  $-5110 [ 103% of $-4960]
- expenses             ||   $495 [ 103% of   $480]   $1060 [ 110% of   $960]
- expenses:bus         ||    $49 [  98% of    $50]    $102 [ 102% of   $100]
- expenses:food        ||   $396 [  99% of   $400]    $808 [ 101% of   $800]
- expenses:movies      ||    $30 [ 100% of    $30]     $30 [  50% of    $60]
- income               ||  $1950 [  98% of  $2000]   $4050 [ 101% of  $4000]
+ assets               || $-2445 [  99% of $-2480]  $-5110 [ 103% of $-4960] 
+ assets:bank          || $-2445 [  99% of $-2480]  $-5110 [ 103% of $-4960] 
+ assets:bank:checking || $-2445 [  99% of $-2480]  $-5110 [ 103% of $-4960] 
+ expenses             ||   $495 [ 103% of   $480]   $1060 [ 110% of   $960] 
+ expenses:bus         ||    $49 [  98% of    $50]    $102 [ 102% of   $100] 
+ expenses:food        ||   $396 [  99% of   $400]    $808 [ 101% of   $800] 
+ expenses:movies      ||    $30 [ 100% of    $30]     $30 [  50% of    $60] 
+ income               ||  $1950 [  98% of  $2000]   $4050 [ 101% of  $4000] 
 ----------------------++----------------------------------------------------
-                      ||      0 [              0]       0 [              0]
+                      ||      0 [              0]       0 [              0] 
 
    For more examples and notes, see Budgeting.
 
@@ -2768,13 +2614,12 @@ File: hledger.info,  Node: Budget report start date,  Next: Nested budgets,  Up:
 
 This might be a bug, but for now: when making budget reports, it's a
 good idea to explicitly set the report's start date to the first day of
-a reporting period, because a periodic rule like `~ monthly' generates
+a reporting period, because a periodic rule like '~ monthly' generates
 its transactions on the 1st of each month, and if your journal has no
 regular transactions on the 1st, the default report start date could
-exclude that budget goal, which can be a little surprising. Eg here the
+exclude that budget goal, which can be a little surprising.  Eg here the
 default report period is just the day of 2020-01-15:
 
-
 ~ monthly in 2020
   (expenses:food)  $500
 
@@ -2782,30 +2627,28 @@ default report period is just the day of 2020-01-15:
   expenses:food    $400
   assets:checking
 
-
 $ hledger bal expenses --budget
 Budget performance in 2020-01-15:
 
-              || 2020-01-15
+              || 2020-01-15 
 ==============++============
- <unbudgeted> ||       $400
+ <unbudgeted> ||       $400 
 --------------++------------
-              ||       $400
+              ||       $400 
 
    To avoid this, specify the budget report's period, or at least the
-start date, with `-b'/`-e'/`-p'/`date:', to ensure it includes the
-budget goal transactions (periodic transactions) that you want. Eg,
-adding `-b 2020/1/1' to the above:
-
+start date, with '-b'/'-e'/'-p'/'date:', to ensure it includes the
+budget goal transactions (periodic transactions) that you want.  Eg,
+adding '-b 2020/1/1' to the above:
 
 $ hledger bal expenses --budget -b 2020/1/1
 Budget performance in 2020-01-01..2020-01-15:
 
-               || 2020-01-01..2020-01-15
+               || 2020-01-01..2020-01-15 
 ===============++========================
- expenses:food ||     $400 [80% of $500]
+ expenses:food ||     $400 [80% of $500] 
 ---------------++------------------------
-               ||     $400 [80% of $500]
+               ||     $400 [80% of $500] 
 
 
 File: hledger.info,  Node: Nested budgets,  Prev: Budget report start date,  Up: Budget report
@@ -2813,7 +2656,7 @@ File: hledger.info,  Node: Nested budgets,  Prev: Budget report start date,  Up:
 11.5.12.2 Nested budgets
 ........................
 
-You can add budgets to any account in your account hierarchy. If you
+You can add budgets to any account in your account hierarchy.  If you
 have budgets on both parent account and some of its children, then
 budget(s) of the child account(s) would be added to the budget of their
 parent, much like account balances behave.
@@ -2823,7 +2666,6 @@ account, all its parents would have budget as well.
 
    To illustrate this, consider the following budget:
 
-
 ~ monthly from 2019/01
     expenses:personal             $1,000.00
     expenses:personal:electronics    $100.00
@@ -2831,16 +2673,15 @@ account, all its parents would have budget as well.
 
    With this, monthly budget for electronics is defined to be $100 and
 budget for personal expenses is an additional $1000, which implicitly
-means that budget for both `expenses:personal' and `expenses' is $1100.
+means that budget for both 'expenses:personal' and 'expenses' is $1100.
 
-   Transactions in `expenses:personal:electronics' will be counted both
-towards its $100 budget and $1100 of `expenses:personal' , and
-transactions in any other subaccount of `expenses:personal' would be
-counted towards only towards the budget of `expenses:personal'.
+   Transactions in 'expenses:personal:electronics' will be counted both
+towards its $100 budget and $1100 of 'expenses:personal' , and
+transactions in any other subaccount of 'expenses:personal' would be
+counted towards only towards the budget of 'expenses:personal'.
 
    For example, let's consider these transactions:
 
-
 ~ monthly from 2019/01
     expenses:personal             $1,000.00
     expenses:personal:electronics    $100.00
@@ -2863,41 +2704,39 @@ counted towards only towards the budget of `expenses:personal'.
     liabilities
 
    As you can see, we have transactions in
-`expenses:personal:electronics:upgrades' and `expenses:personal:train
+'expenses:personal:electronics:upgrades' and 'expenses:personal:train
 tickets', and since both of these accounts are without explicitly
 defined budget, these transactions would be counted towards budgets of
-`expenses:personal:electronics' and `expenses:personal' accordingly:
-
+'expenses:personal:electronics' and 'expenses:personal' accordingly:
 
 $ hledger balance --budget -M
 Budget performance in 2019/01:
 
-                               ||                           Jan
+                               ||                           Jan 
 ===============================++===============================
- expenses                      ||  $283.00 [  26% of  $1100.00]
- expenses:personal             ||  $283.00 [  26% of  $1100.00]
- expenses:personal:electronics ||  $100.00 [ 100% of   $100.00]
- liabilities                   || $-283.00 [  26% of $-1100.00]
+ expenses                      ||  $283.00 [  26% of  $1100.00] 
+ expenses:personal             ||  $283.00 [  26% of  $1100.00] 
+ expenses:personal:electronics ||  $100.00 [ 100% of   $100.00] 
+ liabilities                   || $-283.00 [  26% of $-1100.00] 
 -------------------------------++-------------------------------
-                               ||        0 [                 0]
+                               ||        0 [                 0] 
 
-   And with `--empty', we can get a better picture of budget allocation
+   And with '--empty', we can get a better picture of budget allocation
 and consumption:
 
-
 $ hledger balance --budget -M --empty
 Budget performance in 2019/01:
 
-                                        ||                           Jan
+                                        ||                           Jan 
 ========================================++===============================
- expenses                               ||  $283.00 [  26% of  $1100.00]
- expenses:personal                      ||  $283.00 [  26% of  $1100.00]
- expenses:personal:electronics          ||  $100.00 [ 100% of   $100.00]
- expenses:personal:electronics:upgrades ||   $10.00
- expenses:personal:train tickets        ||  $153.00
- liabilities                            || $-283.00 [  26% of $-1100.00]
+ expenses                               ||  $283.00 [  26% of  $1100.00] 
+ expenses:personal                      ||  $283.00 [  26% of  $1100.00] 
+ expenses:personal:electronics          ||  $100.00 [ 100% of   $100.00] 
+ expenses:personal:electronics:upgrades ||   $10.00                      
+ expenses:personal:train tickets        ||  $153.00                      
+ liabilities                            || $-283.00 [  26% of $-1100.00] 
 ----------------------------------------++-------------------------------
-                                        ||        0 [                 0]
+                                        ||        0 [                 0] 
 
 
 File: hledger.info,  Node: Customising single-period balance reports,  Prev: Budget report,  Up: balance
@@ -2906,9 +2745,8 @@ File: hledger.info,  Node: Customising single-period balance reports,  Prev: Bud
 -------------------------------------------------
 
 For single-period balance reports displayed in the terminal (only), you
-can use `--format FMT' to customise the format and content of each
-line. Eg:
-
+can use '--format FMT' to customise the format and content of each line.
+Eg:
 
 $ hledger balance --format "%20(account) %12(total)"
               assets          $-1
@@ -2925,10 +2763,10 @@ $ hledger balance --format "%20(account) %12(total)"
                                 0
 
    The FMT format string (plus a newline) specifies the formatting
-applied to each account/balance pair. It may contain any suitable text,
+applied to each account/balance pair.  It may contain any suitable text,
 with data fields interpolated like so:
 
-   `%[MIN][.MAX](FIELDNAME)'
+   '%[MIN][.MAX](FIELDNAME)'
 
    * MIN pads with spaces to at least this width (optional)
 
@@ -2936,39 +2774,31 @@ with data fields interpolated like so:
 
    * FIELDNAME must be enclosed in parentheses, and can be one of:
 
-        * `depth_spacer' - a number of spaces equal to the account's
+        * 'depth_spacer' - a number of spaces equal to the account's
           depth, or if MIN is specified, MIN * depth spaces.
-
-        * `account' - the account's name
-
-        * `total' - the account's balance/posted total, right justified
-
+        * 'account' - the account's name
+        * 'total' - the account's balance/posted total, right justified
 
    Also, FMT can begin with an optional prefix to control how
 multi-commodity amounts are rendered:
 
-   * `%_' - render on multiple lines, bottom-aligned (the default)
+   * '%_' - render on multiple lines, bottom-aligned (the default)
+   * '%^' - render on multiple lines, top-aligned
+   * '%,' - render on one line, comma-separated
 
-   * `%^' - render on multiple lines, top-aligned
-
-   * `%,' - render on one line, comma-separated
-
-   There are some quirks. Eg in one-line mode, `%(depth_spacer)' has no
-effect, instead `%(account)' has indentation built in.  Experimentation
+   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.
 
    Some example formats:
 
-   * `%(total)' - the account's total
-
-   * `%-20.20(account)' - the account's name, left justified, padded to
+   * '%(total)' - the account's total
+   * '%-20.20(account)' - the account's name, left justified, padded to
      20 characters and clipped at 20 characters
-
-   * `%,%-50(account)  %25(total)' - account name padded to 50
+   * '%,%-50(account) %25(total)' - account name padded to 50
      characters, total padded to 20 characters, with multiple
      commodities rendered on one line
-
-   * `%20(total)  %2(depth_spacer)%-(account)' - the default format for
+   * '%20(total) %2(depth_spacer)%-(account)' - the default format for
      the single-column balance report
 
 
@@ -2979,18 +2809,17 @@ File: hledger.info,  Node: balancesheet,  Next: balancesheetequity,  Prev: balan
 
 balancesheet, bs
 This command displays a balance sheet, showing historical ending
-balances of asset and liability accounts. (To see equity as well, use
-the balancesheetequity command.) Amounts are shown with normal positive
+balances of asset and liability accounts.  (To see equity as well, use
+the balancesheetequity command.)  Amounts are shown with normal positive
 sign, as in conventional financial statements.
 
    The asset and liability accounts shown are those accounts declared
-with the `Asset' or `Cash' or `Liability' type, or otherwise all
-accounts under a top-level `asset' or `liability' account (case
+with the 'Asset' or 'Cash' or 'Liability' type, or otherwise all
+accounts under a top-level 'asset' or 'liability' account (case
 insensitive, plurals allowed).
 
    Example:
 
-
 $ hledger balancesheet
 Balance Sheet
 
@@ -3010,15 +2839,15 @@ Total:
 --------------------
                    0
 
-   This command is a higher-level variant of the `balance' command, and
+   This command is a higher-level variant of the 'balance' command, and
 supports many of that command's features, such as multi-period reports.
-It is similar to `hledger balance -H assets liabilities', but with
+It is similar to 'hledger balance -H assets liabilities', but with
 smarter account detection, and liabilities displayed with their sign
 flipped.
 
    This command also supports the output destination and output format
-options The output formats supported are `txt', `csv', `html', and
-(experimental) `json'.
+options The output formats supported are 'txt', 'csv', 'html', and
+(experimental) 'json'.
 
 
 File: hledger.info,  Node: balancesheetequity,  Next: cashflow,  Prev: balancesheet,  Up: COMMANDS
@@ -3028,17 +2857,16 @@ File: hledger.info,  Node: balancesheetequity,  Next: cashflow,  Prev: balancesh
 
 balancesheetequity, bse
 This command displays a balance sheet, showing historical ending
-balances of asset, liability and equity accounts. Amounts are shown with
-normal positive sign, as in conventional financial statements.
+balances of asset, liability and equity accounts.  Amounts are shown
+with normal positive sign, as in conventional financial statements.
 
    The asset, liability and equity accounts shown are those accounts
-declared with the `Asset', `Cash', `Liability' or `Equity' type, or
-otherwise all accounts under a top-level `asset', `liability' or
-`equity' account (case insensitive, plurals allowed).
+declared with the 'Asset', 'Cash', 'Liability' or 'Equity' type, or
+otherwise all accounts under a top-level 'asset', 'liability' or
+'equity' account (case insensitive, plurals allowed).
 
    Example:
 
-
 $ hledger balancesheetequity
 Balance Sheet With Equity
 
@@ -3063,15 +2891,15 @@ Total:
 --------------------
                    0
 
-   This command is a higher-level variant of the `balance' command, and
+   This command is a higher-level variant of the 'balance' command, and
 supports many of that command's features, such as multi-period reports.
-It is similar to `hledger balance -H assets liabilities equity', but
+It is similar to 'hledger balance -H assets liabilities equity', but
 with smarter account detection, and liabilities/equity displayed with
 their sign flipped.
 
    This command also supports the output destination and output format
-options The output formats supported are `txt', `csv', `html', and
-(experimental) `json'.
+options The output formats supported are 'txt', 'csv', 'html', and
+(experimental) 'json'.
 
 
 File: hledger.info,  Node: cashflow,  Next: check,  Prev: balancesheetequity,  Up: COMMANDS
@@ -3081,17 +2909,16 @@ File: hledger.info,  Node: cashflow,  Next: check,  Prev: balancesheetequity,  U
 
 cashflow, cf
 This command displays a cashflow statement, showing the inflows and
-outflows affecting "cash" (ie, liquid) assets. Amounts are shown with
+outflows affecting "cash" (ie, liquid) assets.  Amounts are shown with
 normal positive sign, as in conventional financial statements.
 
-   The "cash" accounts shown are those accounts declared with the
-`Cash' type, or otherwise all accounts under a top-level `asset'
-account (case insensitive, plural allowed) which do not have `fixed',
-`investment', `receivable' or `A/R' in their name.
+   The "cash" accounts shown are those accounts declared with the 'Cash'
+type, or otherwise all accounts under a top-level 'asset' account (case
+insensitive, plural allowed) which do not have 'fixed', 'investment',
+'receivable' or 'A/R' in their name.
 
    Example:
 
-
 $ hledger cashflow
 Cashflow Statement
 
@@ -3106,14 +2933,14 @@ Total:
 --------------------
                  $-1
 
-   This command is a higher-level variant of the `balance' command, and
+   This command is a higher-level variant of the 'balance' command, and
 supports many of that command's features, such as multi-period reports.
-It is similar to `hledger balance assets not:fixed not:investment
+It is similar to 'hledger balance assets not:fixed not:investment
 not:receivable', but with smarter account detection.
 
    This command also supports the output destination and output format
-options The output formats supported are `txt', `csv', `html', and
-(experimental) `json'.
+options The output formats supported are 'txt', 'csv', 'html', and
+(experimental) 'json'.
 
 
 File: hledger.info,  Node: check,  Next: close,  Prev: cashflow,  Up: COMMANDS
@@ -3125,14 +2952,13 @@ check
 Check for various kinds of errors in your data.
 
    hledger provides a number of built-in error checks to help prevent
-problems in your data. Some of these are run automatically; or, you can
-use this `check' command to run them on demand, with no output and a
-zero exit code if all is well. Specify their names (or a prefix) as
+problems in your data.  Some of these are run automatically; or, you can
+use this 'check' command to run them on demand, with no output and a
+zero exit code if all is well.  Specify their names (or a prefix) as
 argument(s).
 
    Some examples:
 
-
 hledger check      # basic checks
 hledger check -s   # basic + strict checks
 hledger check ordereddates payees  # basic + two other checks
@@ -3153,18 +2979,18 @@ File: hledger.info,  Node: Basic checks,  Next: Strict checks,  Up: check
 -------------------
 
 These checks are always run automatically, by (almost) all hledger
-commands, including `check':
+commands, including 'check':
 
    * *parseable* - data files are well-formed and can be successfully
      parsed
 
-   * *autobalanced* - all transactions are balanced, inferring missing
-     amounts where necessary, and possibly converting commodities using
-     transaction prices or automatically-inferred transaction prices
+   * *balancedwithautoconversion* - all transactions are balanced,
+     inferring missing amounts where necessary, and possibly converting
+     commodities using transaction prices or automatically-inferred
+     transaction prices
 
    * *assertions* - all balance assertions in the journal are passing.
-     (This check can be disabled with `-I'/`--ignore-assertions'.)
-
+     (This check can be disabled with '-I'/'--ignore-assertions'.)
 
 
 File: hledger.info,  Node: Strict checks,  Next: Other checks,  Prev: Basic checks,  Up: check
@@ -3172,15 +2998,17 @@ File: hledger.info,  Node: Strict checks,  Next: Other checks,  Prev: Basic chec
 11.9.2 Strict checks
 --------------------
 
-These additional checks are run when the `-s'/`--strict' (strict mode)
-flag is used. Or, they can be run by giving their names as arguments to
-`check':
+These additional checks are run when the '-s'/'--strict' (strict mode)
+flag is used.  Or, they can be run by giving their names as arguments to
+'check':
 
    * *accounts* - all account names used by transactions have been
      declared
 
    * *commodities* - all commodity symbols used have been declared
 
+   * *balancednoautoconversion* - transactions are balanced, possibly
+     using explicit transaction prices but not inferred ones
 
 
 File: hledger.info,  Node: Other checks,  Next: Custom checks,  Prev: Strict checks,  Up: check
@@ -3189,7 +3017,7 @@ File: hledger.info,  Node: Other checks,  Next: Custom checks,  Prev: Strict che
 -------------------
 
 These checks can be run only by giving their names as arguments to
-`check'. They are more specialised and not desirable for everyone,
+'check'.  They are more specialised and not desirable for everyone,
 therefore optional:
 
    * *ordereddates* - transactions are ordered by date within each file
@@ -3198,7 +3026,6 @@ therefore optional:
 
    * *uniqueleafnames* - all account leaf names are unique
 
-
 
 File: hledger.info,  Node: Custom checks,  Prev: Other checks,  Up: check
 
@@ -3214,7 +3041,6 @@ https://github.com/simonmichael/hledger/tree/master/bin:
    * *hledger-check-fancyassertions* - more complex balance assertions
      are passing
 
-
    You could make similar scripts to perform your own custom checks.
 See: Cookbook -> Scripting.
 
@@ -3231,27 +3057,27 @@ These can be added to your journal file(s), eg to bring asset/liability
 balances forward into a new journal file, or to close out
 revenues/expenses to retained earnings at the end of a period.
 
-   You can print just one of these transactions by using the `--close'
-or `--open' flag. You can customise their descriptions with the
-`--close-desc' and `--open-desc' options.
+   You can print just one of these transactions by using the '--close'
+or '--open' flag.  You can customise their descriptions with the
+'--close-desc' and '--open-desc' options.
 
    One amountless posting to "equity:opening/closing balances" is added
-to balance the transactions, by default. You can customise this account
-name with `--close-acct' and `--open-acct'; if you specify only one of
+to balance the transactions, by default.  You can customise this account
+name with '--close-acct' and '--open-acct'; if you specify only one of
 these, it will be used for both.
 
-   With `--x/--explicit', the equity posting's amount will be shown.
+   With '--x/--explicit', the equity posting's amount will be shown.
 And if it involves multiple commodities, a posting for each commodity
 will be shown, as with the print command.
 
-   With `--interleaved', the equity postings are shown next to the
+   With '--interleaved', the equity postings are shown next to the
 postings they balance, which makes troubleshooting easier.
 
    By default, transaction prices in the journal are ignored when
-generating the closing/opening transactions. With `--show-costs', this
-cost information is preserved (`balance -B' reports will be unchanged
-after the transition). Separate postings are generated for each cost in
-each commodity. Note this can generate very large journal entries, if
+generating the closing/opening transactions.  With '--show-costs', this
+cost information is preserved ('balance -B' reports will be unchanged
+after the transition).  Separate postings are generated for each cost in
+each commodity.  Note this can generate very large journal entries, if
 you have many foreign currency or investment transactions.
 
 * Menu:
@@ -3267,39 +3093,38 @@ File: hledger.info,  Node: close usage,  Up: close
 If you split your journal files by time (eg yearly), you will typically
 run this command at the end of the year, and save the closing
 transaction as last entry of the old file, and the opening transaction
-as the first entry of the new file. This makes the files self contained,
-so that correct balances are reported no matter which of them are
-loaded. Ie, if you load just one file, the balances are initialised
+as the first entry of the new file.  This makes the files self
+contained, so that correct balances are reported no matter which of them
+are loaded.  Ie, if you load just one file, the balances are initialised
 correctly; or if you load several files, the redundant closing/opening
-transactions cancel each other out. (They will show up in print or
+transactions cancel each other out.  (They will show up in print or
 register reports; you can exclude them with a query like
-`not:desc:'(opening|closing) balances''.)
+'not:desc:'(opening|closing) balances''.)
 
    If you're running a business, you might also use this command to
 "close the books" at the end of an accounting period, transferring
-income statement account balances to retained earnings. (You may want
+income statement account balances to retained earnings.  (You may want
 to change the equity account name to something like "equity:retained
 earnings".)
 
    By default, the closing transaction is dated yesterday, the balances
 are calculated as of end of yesterday, and the opening transaction is
-dated today. To close on some other date, use: `hledger close -e
-OPENINGDATE'. Eg, to close/open on the 2018/2019 boundary, use `-e
-2019'. You can also use -p or `date:PERIOD' (any starting date is
+dated today.  To close on some other date, use: 'hledger close -e
+OPENINGDATE'.  Eg, to close/open on the 2018/2019 boundary, use '-e
+2019'.  You can also use -p or 'date:PERIOD' (any starting date is
 ignored).
 
    Both transactions will include balance assertions for the
-closed/reopened accounts. You probably shouldn't use status or realness
-filters (like -C or -R or `status:') with this command, or the
-generated balance assertions will depend on these flags. Likewise, if
-you run this command with -auto, the balance assertions will probably
-always require -auto.
+closed/reopened accounts.  You probably shouldn't use status or realness
+filters (like -C or -R or 'status:') with this command, or the generated
+balance assertions will depend on these flags.  Likewise, if you run
+this command with -auto, the balance assertions will probably always
+require -auto.
 
    Examples:
 
    Carrying asset/liability balances into a new file for 2019:
 
-
 $ hledger close -f 2018.journal -e 2019 assets liabilities --open
     # (copy/paste the output to the start of your 2019 journal file)
 $ hledger close -f 2018.journal -e 2019 assets liabilities --close
@@ -3307,7 +3132,6 @@ $ hledger close -f 2018.journal -e 2019 assets liabilities --close
 
    Now:
 
-
 $ hledger bs -f 2019.journal                   # one file - balances are correct
 $ hledger bs -f 2018.journal -f 2019.journal   # two files - balances still correct
 $ hledger bs -f 2018.journal not:desc:closing  # to see year-end balances, must exclude closing txn
@@ -3315,14 +3139,12 @@ $ hledger bs -f 2018.journal not:desc:closing  # to see year-end balances, must
    Transactions spanning the closing date can complicate matters,
 breaking balance assertions:
 
-
 2018/12/30 a purchase made in 2018, clearing the following year
     expenses:food          5
     assets:bank:checking  -5  ; [2019/1/2]
 
    Here's one way to resolve that:
 
-
 ; in 2018.journal:
 2018/12/30 a purchase made in 2018, clearing the following year
     expenses:food          5
@@ -3343,19 +3165,18 @@ codes
 List the codes seen in transactions, in the order parsed.
 
    This command prints the value of each transaction's code field, in
-the order transactions were parsed. The transaction code is an optional
+the order transactions were parsed.  The transaction code is an optional
 value written in parentheses between the date and description, often
 used to store a cheque number, order number or similar.
 
    Transactions aren't required to have a code, and missing or empty
-codes will not be shown by default. With the `-E'/`--empty' flag, they
+codes will not be shown by default.  With the '-E'/'--empty' flag, they
 will be printed as blank lines.
 
    You can add a query to select a subset of transactions.
 
    Examples:
 
-
 1/1 (123)
  (a)  1
 
@@ -3368,13 +3189,11 @@ will be printed as blank lines.
 1/1 (126)
  (a)  1
 
-
 $ hledger codes
 123
 124
 126
 
-
 $ hledger codes -E
 123
 124
@@ -3401,12 +3220,11 @@ descriptions
 List the unique descriptions that appear in transactions.
 
    This command lists the unique descriptions that appear in
-transactions, in alphabetic order. You can add a query to select a
+transactions, in alphabetic order.  You can add a query to select a
 subset of transactions.
 
    Example:
 
-
 $ hledger descriptions
 Store Name
 Gas Station | Petrol
@@ -3419,26 +3237,25 @@ File: hledger.info,  Node: diff,  Next: files,  Prev: descriptions,  Up: COMMAND
 ==========
 
 diff
-Compares a particular account's transactions in two input files. It
+Compares a particular account's transactions in two input files.  It
 shows any transactions to this account which are in one file but not in
 the other.
 
    More precisely, for each posting affecting this account in either
-file, it looks for a corresponding posting in the other file which
-posts the same amount to the same account (ignoring date, description,
-etc.) Since postings not transactions are compared, this also works
-when multiple bank transactions have been combined into a single
-journal entry.
+file, it looks for a corresponding posting in the other file which posts
+the same amount to the same account (ignoring date, description, etc.)
+Since postings not transactions are compared, this also works when
+multiple bank transactions have been combined into a single journal
+entry.
 
    This is useful eg if you have downloaded an account's transactions
-from your bank (eg as CSV data). When hledger and your bank disagree
+from your bank (eg as CSV data).  When hledger and your bank disagree
 about the account balance, you can compare the bank data with your
 journal to find out the cause.
 
    Examples:
 
-
-$ hledger diff -f $LEDGER_FILE -f bank.csv assets:bank:giro
+$ hledger diff -f $LEDGER_FILE -f bank.csv assets:bank:giro 
 These transactions are in the first file only:
 
 2014/01/01 Opening Balances
@@ -3455,8 +3272,8 @@ File: hledger.info,  Node: files,  Next: help,  Prev: diff,  Up: COMMANDS
 ===========
 
 files
-List all files included in the journal. With a REGEX argument, only file
-names matching the regular expression (case sensitive) are shown.
+List all files included in the journal.  With a REGEX argument, only
+file names matching the regular expression (case sensitive) are shown.
 
 
 File: hledger.info,  Node: help,  Next: import,  Prev: files,  Up: COMMANDS
@@ -3466,8 +3283,8 @@ File: hledger.info,  Node: help,  Next: import,  Prev: files,  Up: COMMANDS
 
 help
 Show the hledger user manual in one of several formats, optionally
-positioned at a given TOPIC (if possible). TOPIC is any heading, or
-heading prefix, in the manual. Some examples: commands, print, 'auto
+positioned at a given TOPIC (if possible).  TOPIC is any heading, or
+heading prefix, in the manual.  Some examples: commands, print, 'auto
 postings', periodic.
 
    This command shows the user manual built in to this hledger version.
@@ -3475,9 +3292,9 @@ It can be useful if the correct version of the hledger manual, or the
 usual viewing tools, are not installed on your system.
 
    By default it uses the best viewer it can find in $PATH, in this
-order: `info', `man', $PAGER (unless a topic is specified), `less', or
-stdout. When run non-interactively, it always uses stdout. Or you can
-select a particular viewer with the `-i' (info), `-m' (man), or `-p'
+order: 'info', 'man', $PAGER (unless a topic is specified), 'less', or
+stdout.  When run non-interactively, it always uses stdout.  Or you can
+select a particular viewer with the '-i' (info), '-m' (man), or '-p'
 (pager) flags.
 
 
@@ -3488,15 +3305,15 @@ File: hledger.info,  Node: import,  Next: incomestatement,  Prev: help,  Up: COM
 
 import
 Read new transactions added to each FILE since last run, and add them to
-the main journal file. Or with -dry-run, just print the transactions
-that would be added. Or with -catchup, just mark all of the FILEs'
+the main journal file.  Or with -dry-run, just print the transactions
+that would be added.  Or with -catchup, just mark all of the FILEs'
 transactions as imported, without actually importing any.
 
-   Unlike other hledger commands, with `import' the journal file is an
+   Unlike other hledger commands, with 'import' the journal file is an
 output file, and will be modified, though only by appending (existing
-data will not be changed). The input files are specified as arguments,
+data will not be changed).  The input files are specified as arguments,
 so to import one or more CSV files to your main journal, you will run
-`hledger import bank.csv' or perhaps `hledger import *.csv'.
+'hledger import bank.csv' or perhaps 'hledger import *.csv'.
 
    Note you can import from any file format, though CSV files are the
 most common import source, and these docs focus on that case.
@@ -3514,45 +3331,43 @@ File: hledger.info,  Node: Deduplication,  Next: Import testing,  Up: import
 11.17.1 Deduplication
 ---------------------
 
-As a convenience `import' does _deduplication_ while reading
-transactions. This does not mean "ignore transactions that look the
-same", but rather "ignore transactions that have been seen before". This
-is intended for when you are periodically importing foreign data which
-may contain already-imported transactions. So eg, if every day you
-download bank CSV files containing redundant data, you can safely run
-`hledger import bank.csv' and only new transactions will be imported.
-(`import' is idempotent.)
+As a convenience 'import' does _deduplication_ while reading
+transactions.  This does not mean "ignore transactions that look the
+same", but rather "ignore transactions that have been seen before".
+This is intended for when you are periodically importing foreign data
+which may contain already-imported transactions.  So eg, if every day
+you download bank CSV files containing redundant data, you can safely
+run 'hledger import bank.csv' and only new transactions will be
+imported.  ('import' is idempotent.)
 
    Since the items being read (CSV records, eg) often do not come with
 unique identifiers, hledger detects new transactions by date, assuming
 that:
 
   1. new items always have the newest dates
-
   2. item dates do not change across reads
-
   3. and items with the same date remain in the same relative order
      across reads.
 
    These are often true of CSV files representing transactions, or true
-enough so that it works pretty well in practice. 1 is important, but
+enough so that it works pretty well in practice.  1 is important, but
 violations of 2 and 3 amongst the old transactions won't matter (and if
 you import often, the new transactions will be few, so less likely to be
 the ones affected).
 
    hledger remembers the latest date processed in each input file by
-saving a hidden ".latest" state file in the same directory. Eg when
-reading `finance/bank.csv', it will look for and update the
-`finance/.latest.bank.csv' state file. The format is simple: one or
+saving a hidden ".latest" state file in the same directory.  Eg when
+reading 'finance/bank.csv', it will look for and update the
+'finance/.latest.bank.csv' state file.  The format is simple: one or
 more lines containing the same ISO-format date (YYYY-MM-DD), meaning "I
 have processed transactions up to this date, and this many of them on
-that date." Normally you won't see or manipulate these state files
-yourself. But if needed, you can delete them to reset the state (making
+that date."  Normally you won't see or manipulate these state files
+yourself.  But if needed, you can delete them to reset the state (making
 all transactions "new"), or you can construct them to "catch up" to a
 certain date.
 
    Note deduplication (and updating of state files) can also be done by
-`print --new', but this is less often used.
+'print --new', but this is less often used.
 
 
 File: hledger.info,  Node: Import testing,  Next: Importing balance assignments,  Prev: Deduplication,  Up: import
@@ -3560,18 +3375,16 @@ File: hledger.info,  Node: Import testing,  Next: Importing balance assignments,
 11.17.2 Import testing
 ----------------------
 
-With `--dry-run', the transactions that will be imported are printed to
+With '--dry-run', the transactions that will be imported are printed to
 the terminal, without updating your journal or state files.  The output
-is valid journal format, like the print command, so you can re-parse
-it. Eg, to see any importable transactions which CSV rules have not
+is valid journal format, like the print command, so you can re-parse it.
+Eg, to see any importable transactions which CSV rules have not
 categorised:
 
-
 $ hledger import --dry bank.csv | hledger -f- -I print unknown
 
    or (live updating):
 
-
 $ ls bank.csv* | entr bash -c 'echo ====; hledger import --dry bank.csv | hledger -f- -I print unknown'
 
 
@@ -3581,13 +3394,12 @@ File: hledger.info,  Node: Importing balance assignments,  Next: Commodity displ
 -------------------------------------
 
 Entries added by import will have their posting amounts made explicit
-(like `hledger print -x'). This means that any balance assignments in
+(like 'hledger print -x').  This means that any balance assignments in
 imported files must be evaluated; but, imported files don't get to see
-the main file's account balances. As a result, importing entries with
+the main file's account balances.  As a result, importing entries with
 balance assignments (eg from an institution that provides only balances
 and not posting amounts) will probably generate incorrect posting
-amounts. To avoid this problem, use print instead of import:
-
+amounts.  To avoid this problem, use print instead of import:
 
 $ hledger print IMPORTFILE [--new] >> $LEDGER_FILE
 
@@ -3610,18 +3422,18 @@ File: hledger.info,  Node: incomestatement,  Next: notes,  Prev: import,  Up: CO
 =====================
 
 incomestatement, is
-This command displays an income statement, showing revenues and expenses
-during one or more periods. Amounts are shown with normal positive sign,
-as in conventional financial statements.
+
+   This command displays an income statement, showing revenues and
+expenses during one or more periods.  Amounts are shown with normal
+positive sign, as in conventional financial statements.
 
    The revenue and expense accounts shown are those accounts declared
-with the `Revenue' or `Expense' type, or otherwise all accounts under a
-top-level `revenue' or `income' or `expense' account (case insensitive,
+with the 'Revenue' or 'Expense' type, or otherwise all accounts under a
+top-level 'revenue' or 'income' or 'expense' account (case insensitive,
 plurals allowed).
 
    Example:
 
-
 $ hledger incomestatement
 Income Statement
 
@@ -3643,15 +3455,15 @@ Total:
 --------------------
                    0
 
-   This command is a higher-level variant of the `balance' command, and
+   This command is a higher-level variant of the 'balance' command, and
 supports many of that command's features, such as multi-period reports.
-It is similar to `hledger balance '(revenues|income)' expenses', but
-with smarter account detection, and revenues/income displayed with
-their sign flipped.
+It is similar to 'hledger balance '(revenues|income)' expenses', but
+with smarter account detection, and revenues/income displayed with their
+sign flipped.
 
    This command also supports the output destination and output format
-options The output formats supported are `txt', `csv', `html', and
-(experimental) `json'.
+options The output formats supported are 'txt', 'csv', 'html', and
+(experimental) 'json'.
 
 
 File: hledger.info,  Node: notes,  Next: payees,  Prev: incomestatement,  Up: COMMANDS
@@ -3663,13 +3475,12 @@ notes
 List the unique notes that appear in transactions.
 
    This command lists the unique notes that appear in transactions, in
-alphabetic order. You can add a query to select a subset of
-transactions. The note is the part of the transaction description after
+alphabetic order.  You can add a query to select a subset of
+transactions.  The note is the part of the transaction description after
 a | character (or if there is no |, the whole description).
 
    Example:
 
-
 $ hledger notes
 Petrol
 Snacks
@@ -3690,12 +3501,11 @@ with payee directives (-declared), used in transaction descriptions
    The payee/payer is the part of the transaction description before a |
 character (or if there is no |, the whole description).
 
-   You can add query arguments to select a subset of transactions. This
+   You can add query arguments to select a subset of transactions.  This
 implies -used.
 
    Example:
 
-
 $ hledger payees
 Store Name
 Gas Station
@@ -3708,11 +3518,11 @@ File: hledger.info,  Node: prices,  Next: print,  Prev: payees,  Up: COMMANDS
 ============
 
 prices
-Print market price directives from the journal. With -costs, also print
-synthetic market prices based on transaction prices. With
+Print market price directives from the journal.  With -costs, also print
+synthetic market prices based on transaction prices.  With
 -inverted-costs, also print inverse prices based on transaction prices.
-Prices (and postings providing prices) can be filtered by a query. Price
-amounts are always displayed with their full precision.
+Prices (and postings providing prices) can be filtered by a query.
+Price amounts are always displayed with their full precision.
 
 
 File: hledger.info,  Node: print,  Next: print-unique,  Prev: prices,  Up: COMMANDS
@@ -3724,10 +3534,10 @@ print
 Show transaction journal entries, sorted by date.
 
    The print command displays full journal entries (transactions) from
-the journal file, sorted by date (or with `--date2', by secondary date).
+the journal file, sorted by date (or with '--date2', by secondary date).
 
    Amounts are shown mostly normalised to commodity display style, eg
-the placement of commodity symbols will be consistent. All of their
+the placement of commodity symbols will be consistent.  All of their
 decimal places are shown, as in the original journal entry (with one
 alteration: in some cases trailing zeroes are added.)
 
@@ -3741,7 +3551,6 @@ directives and file-level comments.
 
    Eg:
 
-
 $ hledger print
 2008/01/01 income
     assets:bank:checking            $1
@@ -3765,10 +3574,9 @@ $ hledger print
     assets:bank:checking           $-1
 
    print's output is usually a valid hledger journal, and you can
-process it again with a second hledger command. This can be useful for
+process it again with a second hledger command.  This can be useful for
 certain kinds of search, eg:
 
-
 # Show running total of food expenses paid from cash.
 # -f- reads from stdin. -I/--ignore-assertions is sometimes needed.
 $ hledger print assets:cash | hledger -f- -I reg expenses:food
@@ -3778,42 +3586,40 @@ unparseable:
 
    * Valuation affects posting amounts but not balance assertion or
      balance assignment amounts, potentially causing those to fail.
-
    * Auto postings can generate postings with too many missing amounts.
 
    Normally, the journal entry's explicit or implicit amount style is
-preserved. For example, when an amount is omitted in the journal, it
-will not appear in the output. Similarly, when a transaction price is
-implied but not written, it will not appear in the output. You can use
-the `-x'/`--explicit' flag to make all amounts and transaction prices
+preserved.  For example, when an amount is omitted in the journal, it
+will not appear in the output.  Similarly, when a transaction price is
+implied but not written, it will not appear in the output.  You can use
+the '-x'/'--explicit' flag to make all amounts and transaction prices
 explicit, which can be useful for troubleshooting or for making your
-journal more readable and robust against data entry errors.  `-x' is
-also implied by using any of `-B',`-V',`-X',`--value'.
+journal more readable and robust against data entry errors.  '-x' is
+also implied by using any of '-B','-V','-X','--value'.
 
-   Note, `-x'/`--explicit' will cause postings with a multi-commodity
+   Note, '-x'/'--explicit' will cause postings with a multi-commodity
 amount (these can arise when a multi-commodity transaction has an
 implicit amount) to be split into multiple single-commodity postings,
 keeping the output parseable.
 
-   With `-B'/`--cost', amounts with transaction prices are converted to
-cost using that price. This can be used for troubleshooting.
+   With '-B'/'--cost', amounts with transaction prices are converted to
+cost using that price.  This can be used for troubleshooting.
 
-   With `-m'/`--match' and a STR argument, print will show at most one
+   With '-m'/'--match' and a STR argument, print will show at most one
 transaction: the one one whose description is most similar to STR, and
-is most recent. STR should contain at least two characters. If there is
-no similar-enough match, no transaction will be shown.
+is most recent.  STR should contain at least two characters.  If there
+is no similar-enough match, no transaction will be shown.
 
-   With `--new', hledger prints only transactions it has not seen on a
-previous run. This uses the same deduplication system as the `import'
-command. (See import's docs for details.)
+   With '--new', hledger prints only transactions it has not seen on a
+previous run.  This uses the same deduplication system as the 'import'
+command.  (See import's docs for details.)
 
    This command also supports the output destination and output format
-options The output formats supported are `txt', `csv', and
-(experimental) `json' and `sql'.
+options The output formats supported are 'txt', 'csv', and
+(experimental) 'json' and 'sql'.
 
    Here's an example of print's CSV output:
 
-
 $ hledger print -Ocsv
 "txnidx","date","date2","status","code","description","comment","account","amount","commodity","credit","debit","posting-status","posting-comment"
 "1","2008/01/01","","","","income","","assets:bank:checking","1","$","","1","",""
@@ -3830,17 +3636,14 @@ $ hledger print -Ocsv
 
    * There is one CSV record per posting, with the parent transaction's
      fields repeated.
-
    * The "txnidx" (transaction index) field shows which postings belong
-     to the same transaction. (This number might change if transactions
+     to the same transaction.  (This number might change if transactions
      are reordered within the file, files are parsed/included in a
      different order, etc.)
-
    * The amount is separated into "commodity" (the symbol) and "amount"
      (numeric quantity) fields.
-
    * The numeric amount is repeated in either the "credit" or "debit"
-     column, for convenience. (Those names are not accurate in the
+     column, for convenience.  (Those names are not accurate in the
      accounting sense; it just puts negative amounts under credit and
      zero or greater amounts under debit.)
 
@@ -3855,7 +3658,6 @@ Print transactions which do not reuse an already-seen description.
 
    Example:
 
-
 $ cat unique.journal
 1/1 test
  (acct:one)  1
@@ -3877,7 +3679,7 @@ Show postings and their running total.
 
    The register command displays matched postings, across all accounts,
 in date order, with their running total or running historical balance.
-(See also the `aregister' command, which shows matched transactions in a
+(See also the 'aregister' command, which shows matched transactions in a
 specific account.)
 
    register normally shows line per posting, but note that
@@ -3887,7 +3689,6 @@ commodity).
    It is typically used with a query selecting a particular account, to
 see that account's activity:
 
-
 $ hledger register checking
 2008/01/01 income               assets:bank:checking            $1           $1
 2008/06/01 gift                 assets:bank:checking            $1           $2
@@ -3896,47 +3697,43 @@ $ hledger register checking
 
    With -date2, it shows and sorts by secondary date instead.
 
-   The `--historical'/`-H' flag adds the balance from any undisplayed
-prior postings to the running total. This is useful when you want to
+   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
 2008/06/01 gift                 assets:bank:checking            $1           $2
 2008/06/02 save                 assets:bank:checking           $-1           $1
 2008/12/31 pay off              assets:bank:checking           $-1            0
 
-   The `--depth' option limits the amount of sub-account detail
+   The '--depth' option limits the amount of sub-account detail
 displayed.
 
-   The `--average'/`-A' flag shows the running average posting amount
+   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
+average for 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
+   The '--related'/'-r' flag shows the _other_ postings in the
 transactions of the postings which would normally be shown.
 
-   The `--invert' flag negates all amounts. For example, it can be used
+   The '--invert' flag negates all amounts.  For example, it can be used
 on an income account where amounts are normally displayed as negative
-numbers. It's also useful to show postings on the checking account
+numbers.  It's also useful to show postings on the checking account
 together with the related account:
 
-
 $ hledger register --related --invert assets:checking
 
    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 not shown by default; use the `--empty'/`-E' flag to see them:
-
+are not shown by default; use the '--empty'/'-E' flag to see them:
 
 $ hledger register --monthly income -E
 2008/01                 income:salary                          $-1          $-1
@@ -3952,10 +3749,9 @@ $ hledger register --monthly income -E
 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
 2008/01                 assets                                  $1           $1
 2008/06                 assets                                 $-1            0
@@ -3963,7 +3759,7 @@ $ hledger register --monthly assets --depth 1h
 
    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
+intervals.  This ensures that the first and last intervals are full
 length and comparable to the others in the report.
 
 * Menu:
@@ -3976,15 +3772,14 @@ File: hledger.info,  Node: Custom register output,  Up: register
 11.24.1 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 a
-bash shell variable) or by using the `--width'/`-w' option.
+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
+(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 (won't display correctly in -help):
-
+'--width W,D' .  Here's a diagram (won't display correctly in -help):
 
 <--------------------------------- width (W) ---------------------------------->
 date (10)  description (D)       account (W-41-D)     amount (12)   balance (12)
@@ -3992,7 +3787,6 @@ DDDDDDDDDD dddddddddddddddddddd  aaaaaaaaaaaaaaaaaaa  AAAAAAAAAAAA  AAAAAAAAAAAA
 
    and some examples:
 
-
 $ hledger reg                     # use terminal width (or 80 on windows)
 $ hledger reg -w 100              # use width 100
 $ COLUMNS=100 hledger reg         # set with one-time environment variable
@@ -4001,8 +3795,8 @@ $ hledger reg -w 100,40           # set overall width 100, description width 40
 $ hledger reg -w $COLUMNS,40      # use terminal width, & description width 40
 
    This command also supports the output destination and output format
-options The output formats supported are `txt', `csv', and
-(experimental) `json'.
+options The output formats supported are 'txt', 'csv', and
+(experimental) 'json'.
 
 
 File: hledger.info,  Node: register-match,  Next: rewrite,  Prev: register,  Up: COMMANDS
@@ -4012,9 +3806,9 @@ File: hledger.info,  Node: register-match,  Next: rewrite,  Prev: register,  Up:
 
 register-match
 Print the one posting whose transaction description is closest to DESC,
-in the style of the register command. If there are multiple equally good
-matches, it shows the most recent. Query options (options, not
-arguments) can be used to restrict the search space. Helps
+in the style of the register command.  If there are multiple equally
+good matches, it shows the most recent.  Query options (options, not
+arguments) can be used to restrict the search space.  Helps
 ledger-autosync detect already-seen transactions when importing.
 
 
@@ -4028,7 +3822,7 @@ Print all transactions, rewriting the postings of matched transactions.
 For now the only rewrite available is adding new postings, like print
 -auto.
 
-   This is a start at a generic rewriter of transaction entries. It
+   This is a start at a generic rewriter of transaction entries.  It
 reads the default journal and prints the transactions, like print, but
 adds one or more specified postings to any transactions matching QUERY.
 The posting amounts can be fixed, or a multiplier of the existing
@@ -4036,14 +3830,12 @@ transaction's first posting amount.
 
    Examples:
 
-
 $ hledger-rewrite.hs ^income --add-posting '(liabilities:tax)  *.33  ; income tax' --add-posting '(reserve:gifts)  $100'
 $ hledger-rewrite.hs expenses:gifts --add-posting '(reserve:gifts)  *-1"'
 $ hledger-rewrite.hs -f rewrites.hledger
 
    rewrites.hledger may consist of entries like:
 
-
 = ^income amt:<0 date:2017
   (liabilities:tax)  *0.33  ; tax on income
   (reserve:grocery)  *0.25  ; reserve 25% for grocery
@@ -4054,18 +3846,17 @@ two spaces between account and amount.
 
    More:
 
-
 $ hledger rewrite -- [QUERY]        --add-posting "ACCT  AMTEXPR" ...
 $ hledger rewrite -- ^income        --add-posting '(liabilities:tax)  *.33'
 $ hledger rewrite -- expenses:gifts --add-posting '(budget:gifts)  *-1"'
 $ hledger rewrite -- ^income        --add-posting '(budget:foreign currency)  *0.25 JPY; diversify'
 
-   Argument for `--add-posting' option is a usual posting of
-transaction with an exception for amount specification. More precisely,
-you can use `'*'' (star symbol) before the amount to indicate that that
-this is a factor for an amount of original matched posting. If the
-amount includes a commodity name, the new posting amount will be in the
-new commodity; otherwise, it will be in the matched posting amount's
+   Argument for '--add-posting' option is a usual posting of transaction
+with an exception for amount specification.  More precisely, you can use
+''*'' (star symbol) before the amount to indicate that that this is a
+factor for an amount of original matched posting.  If the amount
+includes a commodity name, the new posting amount will be in the new
+commodity; otherwise, it will be in the matched posting amount's
 commodity.
 
 * Menu:
@@ -4081,15 +3872,13 @@ File: hledger.info,  Node: Re-write rules in a file,  Next: Diff output format,
 --------------------------------
 
 During the run this tool will execute so called "Automated Transactions"
-found in any journal it process. I.e instead of specifying this
+found in any journal it process.  I.e instead of specifying this
 operations in command line you can put them in a journal file.
 
-
 $ rewrite-rules.journal
 
    Make contents look like this:
 
-
 = ^income
     (liabilities:tax)  *.33
 
@@ -4097,23 +3886,21 @@ $ rewrite-rules.journal
     budget:gifts  *-1
     assets:budget  *1
 
-   Note that `'='' (equality symbol) that is used instead of date in
-transactions you usually write. It indicates the query by which you want
-to match the posting to add new ones.
-
+   Note that ''='' (equality symbol) that is used instead of date in
+transactions you usually write.  It indicates the query by which you
+want to match the posting to add new ones.
 
 $ hledger rewrite -- -f input.journal -f rewrite-rules.journal > rewritten-tidy-output.journal
 
    This is something similar to the commands pipeline:
 
-
 $ hledger rewrite -- -f input.journal '^income' --add-posting '(liabilities:tax)  *.33' \
   | hledger rewrite -- -f - expenses:gifts      --add-posting 'budget:gifts  *-1'       \
                                                 --add-posting 'assets:budget  *1'       \
   > rewritten-tidy-output.journal
 
    It is important to understand that relative order of such entries in
-journal is important. You can re-use result of previously added
+journal is important.  You can re-use result of previously added
 postings.
 
 
@@ -4125,12 +3912,10 @@ File: hledger.info,  Node: Diff output format,  Next: rewrite vs print --auto,
 To use this tool for batch modification of your journal files you may
 find useful output in form of unified diff.
 
-
 $ hledger rewrite -- --diff -f examples/sample.journal '^income' --add-posting '(liabilities:tax)  *.33'
 
    Output might look like:
 
-
 --- /tmp/examples/sample.journal
 +++ /tmp/examples/sample.journal
 @@ -18,3 +18,4 @@
@@ -4146,14 +3931,14 @@ $ hledger rewrite -- --diff -f examples/sample.journal '^income' --add-posting '
      income:gifts
 +    (liabilities:tax)                0
 
-   If you'll pass this through `patch' tool you'll get transactions
-containing the posting that matches your query be updated. Note that
+   If you'll pass this through 'patch' tool you'll get transactions
+containing the posting that matches your query be updated.  Note that
 multiple files might be update according to list of input files
-specified via `--file' options and `include' directives inside of these
+specified via '--file' options and 'include' directives inside of these
 files.
 
-   Be careful. Whole transaction being re-formatted in a style of output
-from `hledger print'.
+   Be careful.  Whole transaction being re-formatted in a style of
+output from 'hledger print'.
 
    See also:
 
@@ -4169,16 +3954,16 @@ This command predates print -auto, and currently does much the same
 thing, but with these differences:
 
    * with multiple files, rewrite lets rules in any file affect all
-     other files. print -auto uses standard directive scoping; rules
+     other files.  print -auto uses standard directive scoping; rules
      affect only child files.
 
    * rewrite's query limits which transactions can be rewritten; all are
-     printed. print -auto's query limits which transactions are printed.
+     printed.  print -auto's query limits which transactions are
+     printed.
 
    * rewrite applies rules specified on command line or in the journal.
      print -auto applies rules specified in the journal.
 
-
 
 File: hledger.info,  Node: roi,  Next: stats,  Prev: rewrite,  Up: COMMANDS
 
@@ -4190,28 +3975,27 @@ Shows the time-weighted (TWR) and money-weighted (IRR) rate of return on
 your investments.
 
    At a minimum, you need to supply a query (which could be just an
-account name) to select your investment(s) with `--inv', and another
-query to identify your profit and loss transactions with `--pnl'.
+account name) to select your investment(s) with '--inv', and another
+query to identify your profit and loss transactions with '--pnl'.
 
    If you do not record changes in the value of your investment
 manually, or do not require computation of time-weighted return (TWR),
-`--pnl' could be an empty query (`--pnl ""' or `--pnl STR' where `STR'
+'--pnl' could be an empty query ('--pnl ""' or '--pnl STR' where 'STR'
 does not match any of your accounts).
 
    This command will compute and display the internalized rate of return
 (IRR) and time-weighted rate of return (TWR) for your investments for
-the time period requested. Both rates of return are annualized before
+the time period requested.  Both rates of return are annualized before
 display, regardless of the length of reporting interval.
 
    Price directives will be taken into account if you supply appropriate
-`--cost' or `--value' flags (see VALUATION).
+'--cost' or '--value' flags (see VALUATION).
 
    Note, in some cases this report can fail, for these reasons:
 
    * Error (NotBracketed): No solution for Internal Rate of Return
-     (IRR).  Possible causes: IRR is huge (>1000000%), balance of
+     (IRR). Possible causes: IRR is huge (>1000000%), balance of
      investment becomes negative at some point in time.
-
    * Error (SearchFailed): Failed to find solution for Internal Rate of
      Return (IRR). Either search does not converge to a solution, or
      converges too slowly.
@@ -4223,7 +4007,6 @@ display, regardless of the length of reporting interval.
 
    * Cookbook -> Return on Investment
 
-
 * Menu:
 
 * Semantics of --inv and --pnl::
@@ -4232,49 +4015,44 @@ display, regardless of the length of reporting interval.
 
 File: hledger.info,  Node: Semantics of --inv and --pnl,  Next: IRR and TWR explained,  Up: roi
 
-11.27.1 Semantics of `--inv' and `--pnl'
+11.27.1 Semantics of '--inv' and '--pnl'
 ----------------------------------------
 
-Query supplied to `--inv' has to match all transactions that are
-related to your investment. Transactions not matching `--inv' will be
-ignored.
+Query supplied to '--inv' has to match all transactions that are related
+to your investment.  Transactions not matching '--inv' will be ignored.
 
-   In these transactions, ROI will conside postings that match `--inv'
-to be "investment postings" and other postings (not matching `--inv')
+   In these transactions, ROI will conside postings that match '--inv'
+to be "investment postings" and other postings (not matching '--inv')
 will be sorted into two categories: "cash flow" and "profit and loss",
 as ROI needs to know which part of the investment value is your
 contributions and which is due to the return on investment.
 
    * "Cash flow" is depositing or withdrawing money, buying or selling
      assets, or otherwise converting between your investment commodity
-     and any other commodity. Example:
-
+     and any other commodity.  Example:
 
      2019-01-01 Investing in Snake Oil
        assets:cash          -$100
        investment:snake oil
-
+     
      2020-01-01 Selling my Snake Oil
        assets:cash           $10
        investment:snake oil  = 0
 
    * "Profit and loss" is change in the value of your investment:
 
-
      2019-06-01 Snake Oil falls in value
        investment:snake oil  = $57
        equity:unrealized profit or loss
 
-
    All non-investment postings are assumed to be "cash flow", unless
-they match `--pnl' query. Changes in value of your investment due to
+they match '--pnl' query.  Changes in value of your investment due to
 "profit and loss" postings will be considered as part of your investment
 return.
 
-   Example: if you use `--inv snake --pnl equity:unrealized', then
+   Example: if you use '--inv snake --pnl equity:unrealized', then
 postings in the example below would be classifed as:
 
-
 2019-01-01 Snake Oil #1
   assets:cash          -$100   ; cash flow posting
   investment:snake oil         ; investment posting
@@ -4294,31 +4072,31 @@ File: hledger.info,  Node: IRR and TWR explained,  Prev: Semantics of --inv and
 11.27.2 IRR and TWR explained
 -----------------------------
 
-"ROI" stands for "return on investment". Traditionally this was computed
-as a difference between current value of investment and its initial
-value, expressed in percentage of the initial value.
+"ROI" stands for "return on investment".  Traditionally this was
+computed as a difference between current value of investment and its
+initial value, expressed in percentage of the initial value.
 
    However, this approach is only practical in simple cases, where
 investments receives no in-flows or out-flows of money, and where rate
-of growth is fixed over time. For more complex scenarios you need
+of growth is fixed over time.  For more complex scenarios you need
 different ways to compute rate of return, and this command implements
 two of them: IRR and TWR.
 
    Internal rate of return, or "IRR" (also called "money-weighted rate
 of return") takes into account effects of in-flows and out-flows.
 Naively, if you are withdrawing from your investment, your future gains
-would be smaller (in absolute numbers), and will be a smaller
-percentage of your initial investment, and if you are adding to your
-investment, you will receive bigger absolute gains (but probably at the
-same rate of return).  IRR is a way to compute rate of return for each
-period between in-flow or out-flow of money, and then combine them in a
-way that gives you a compound annual rate of return that investment is
-expected to generate.
+would be smaller (in absolute numbers), and will be a smaller percentage
+of your initial investment, and if you are adding to your investment,
+you will receive bigger absolute gains (but probably at the same rate of
+return).  IRR is a way to compute rate of return for each period between
+in-flow or out-flow of money, and then combine them in a way that gives
+you a compound annual rate of return that investment is expected to
+generate.
 
    As mentioned before, in-flows and out-flows would be any cash that
 you personally put in or withdraw, and for the "roi" command, these are
-the postings that match the query in the`--inv' argument and NOT match
-the query in the`--pnl' argument.
+the postings that match the query in the'--inv' argument and NOT match
+the query in the'--pnl' argument.
 
    If you manually record changes in the value of your investment as
 transactions that balance them against "profit and loss" (or "unrealized
@@ -4329,21 +4107,21 @@ close to the days when in- or out-flows occur.
 
    In technical terms, IRR uses the same approach as computation of net
 present value, and tries to find a discount rate that makes net present
-value of all the cash flows of your investment to add up to zero. This
+value of all the cash flows of your investment to add up to zero.  This
 could be hard to wrap your head around, especially if you haven't done
-discounted cash flow analysis before. Implementation of IRR in hledger
-should produce results that match the `XIRR' formula in Excel.
+discounted cash flow analysis before.  Implementation of IRR in hledger
+should produce results that match the 'XIRR' formula in Excel.
 
-   Second way to compute rate of return that `roi' command implements
-is called "time-weighted rate of return" or "TWR". Like IRR, it will
-also break the history of your investment into periods between in-flows,
+   Second way to compute rate of return that 'roi' command implements is
+called "time-weighted rate of return" or "TWR". Like IRR, it will also
+break the history of your investment into periods between in-flows,
 out-flows and value changes, to compute rate of return per each period
-and then a compound rate of return. However, internal workings of TWR
+and then a compound rate of return.  However, internal workings of TWR
 are quite different.
 
    TWR represents your investment as an imaginary "unit fund" where
 in-flows/ out-flows lead to buying or selling "units" of your investment
-and changes in its value change the value of "investment unit". Change
+and changes in its value change the value of "investment unit".  Change
 in "unit price" over the reporting period gives you rate of return of
 your investment.
 
@@ -4360,16 +4138,15 @@ File: hledger.info,  Node: stats,  Next: tags,  Prev: roi,  Up: COMMANDS
 stats
 Show some journal statistics.
 
-   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 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.
 
    Example:
 
-
 $ hledger stats
 Main journal file        : /src/hledger/examples/sample.journal
-Included journal files   :
+Included journal files   : 
 Transactions span        : 2008-01-01 to 2009-01-01 (366 days)
 Last transaction         : 2008-12-31 (2333 days ago)
 Transactions             : 5 (0.0 per day)
@@ -4390,10 +4167,10 @@ File: hledger.info,  Node: tags,  Next: test,  Prev: stats,  Up: COMMANDS
 ==========
 
 tags
-List the unique tag names used in the journal. With a TAGREGEX argument,
-only tag names matching the regular expression (case insensitive) are
-shown. With QUERY arguments, only transactions matching the query are
-considered.
+List the unique tag names used in the journal.  With a TAGREGEX
+argument, only tag names matching the regular expression (case
+insensitive) are shown.  With QUERY arguments, only transactions
+matching the query are considered.
 
    With the -values flag, the tags' unique values are listed instead.
 
@@ -4413,23 +4190,22 @@ test
 Run built-in unit tests.
 
    This command runs the unit tests built in to hledger and hledger-lib,
-printing the results on stdout. If any test fails, the exit code will be
-non-zero.
+printing the results on stdout.  If any test fails, the exit code will
+be non-zero.
 
    This is mainly used by hledger developers, but you can also use it to
-sanity-check the installed hledger executable on your platform. All
+sanity-check the installed hledger executable on your platform.  All
 tests are expected to pass - if you ever see a failure, please report as
 a bug!
 
    This command also accepts tasty test runner options, written after a
-- (double hyphen). Eg to run only the tests in Hledger.Data.Amount, with
-ANSI colour codes disabled:
-
+- (double hyphen).  Eg to run only the tests in Hledger.Data.Amount,
+with ANSI colour codes disabled:
 
 $ hledger test -- -pData.Amount --color=never
 
    For help on these, see https://github.com/feuerbach/tasty#options
-(`-- --help' currently doesn't show them).
+('-- --help' currently doesn't show them).
 
 
 File: hledger.info,  Node: About add-on commands,  Prev: test,  Up: COMMANDS
@@ -4439,40 +4215,35 @@ File: hledger.info,  Node: About add-on commands,  Prev: test,  Up: COMMANDS
 
 Add-on commands are programs or scripts in your PATH
 
-   * whose name starts with `hledger-'
-
+   * whose name starts with 'hledger-'
    * whose name ends with a recognised file extension:
-     `.bat',`.com',`.exe', `.hs',`.lhs',`.pl',`.py',`.rb',`.rkt',`.sh'
+     '.bat','.com','.exe', '.hs','.lhs','.pl','.py','.rb','.rkt','.sh'
      or none
-
    * and (on unix, mac) which are executable by the current user.
 
    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 library functions
-that built-in commands use for command-line options, parsing and
-reporting. Some experimental/example add-on scripts can be found in the
-hledger repo's bin/ directory.
+with new ideas.  They can be written in any language, but haskell
+scripts have a big advantage: they can use the same hledger library
+functions that built-in commands use for command-line options, parsing
+and reporting.  Some experimental/example add-on scripts can be found in
+the hledger repo's bin/ directory.
 
    Note in a hledger command line, add-on command flags must have a
-double dash (`--') preceding them. Eg you must write:
-
+double dash ('--') preceding them.  Eg you must write:
 
 $ hledger web -- --serve
 
    and not:
 
-
 $ hledger web --serve
 
-   (because the `--serve' flag belongs to `hledger-web', not `hledger').
+   (because the '--serve' flag belongs to 'hledger-web', not 'hledger').
 
-   The `-h/--help' and `--version' flags don't require `--'.
+   The '-h/--help' and '--version' flags don't require '--'.
 
    If you have any trouble with this, remember you can always run the
 add-on program directly, eg:
 
-
 $ hledger-web --serve
 
 
@@ -4484,30 +4255,30 @@ File: hledger.info,  Node: JOURNAL FORMAT,  Next: CSV FORMAT,  Prev: COMMANDS,
 hledger's default file format, representing a General Journal.
 
    hledger's usual data source is a plain text file containing journal
-entries in hledger journal format. This file represents a standard
-accounting general journal. I use file names ending in `.journal', but
-that's not required. The journal file contains a number of transaction
+entries in hledger journal format.  This file represents a standard
+accounting general journal.  I use file names ending in '.journal', but
+that's not required.  The journal file contains a number of transaction
 entries, each describing a transfer of money (or any commodity) between
 two or more named accounts, in a simple format readable by both hledger
 and humans.
 
    hledger's journal format is a compatible subset, mostly, of ledger's
 journal format, so hledger can work with compatible ledger journal files
-as well. It's safe, and encouraged, to run both hledger and ledger on
+as well.  It's safe, and encouraged, to run both hledger and ledger on
 the same journal file, eg to validate the results you're getting.
 
    You can use hledger without learning any more about this file; just
 use the add or web or import commands to create and update it.
 
    Many users, though, edit the journal file with a text editor, and
-track changes with a version control system such as git. Editor addons
+track changes with a version control system such as git.  Editor addons
 such as ledger-mode or hledger-mode for Emacs, vim-ledger for Vim, and
 hledger-vscode for Visual Studio Code, make this easier, adding colour,
-formatting, tab completion, and useful commands. See Editor
+formatting, tab completion, and useful commands.  See Editor
 configuration at hledger.org for the full list.
 
    Here's a description of each part of the file format (and hledger's
-data model). These are mostly in the order you'll use them, but in some
+data model).  These are mostly in the order you'll use them, but in some
 cases related concepts have been grouped together for easy reference, or
 linked before they are introduced, so feel free to skip over anything
 that looks unnecessary right now.
@@ -4548,30 +4319,25 @@ File: hledger.info,  Node: Transactions,  Next: Dates,  Up: JOURNAL FORMAT
 12.1 Transactions
 =================
 
-Transactions are the main unit of information in a journal file. They
+Transactions are the main unit of information in a journal file.  They
 represent events, typically a movement of some quantity of commodities
 between two or more named accounts.
 
    Each transaction is recorded as a journal entry, beginning with a
-simple date in column 0. This can be followed by any of the following
+simple date in column 0.  This can be followed by any of the following
 optional fields, separated by spaces:
 
-   * a status character (empty, `!', or `*')
-
+   * a status character (empty, '!', or '*')
    * a code (any short number or text, enclosed in parentheses)
-
    * a description (any remaining text until end of line or a semicolon)
-
    * a comment (any remaining text following a semicolon until end of
      line, and any following indented lines beginning with a semicolon)
-
    * 0 or more indented _posting_ lines, describing what was transferred
-     and the accounts involved (indented comment lines are also
-     allowed, but not blank lines or non-indented lines).
+     and the accounts involved (indented comment lines are also allowed,
+     but not blank lines or non-indented lines).
 
    Here's a simple journal file containing one transaction:
 
-
 2008/01/01 income
   assets:bank:checking   $1
   income:salary         $-1
@@ -4594,12 +4360,12 @@ File: hledger.info,  Node: Simple dates,  Next: Secondary dates,  Up: Dates
 12.2.1 Simple dates
 -------------------
 
-Dates in the journal file use _simple dates_ format: `YYYY-MM-DD' or
-`YYYY/MM/DD' or `YYYY.MM.DD', with leading zeros optional. The year may
+Dates in the journal file use _simple dates_ format: 'YYYY-MM-DD' or
+'YYYY/MM/DD' or 'YYYY.MM.DD', with leading zeros optional.  The year may
 be omitted, in which case it will be inferred from the context: the
-current transaction, the default year set with a default year
-directive, or the current date when the command is run. Some examples:
-`2010-01-31', `2010/01/31', `2010.1.31', `1/31'.
+current transaction, the default year set with a default year directive,
+or the current date when the command is run.  Some examples:
+'2010-01-31', '2010/01/31', '2010.1.31', '1/31'.
 
    (The UI also accepts simple dates, as well as the more flexible smart
 dates documented in the hledger manual.)
@@ -4611,35 +4377,32 @@ File: hledger.info,  Node: Secondary dates,  Next: Posting dates,  Prev: Simple
 ----------------------
 
 Real-life transactions sometimes involve more than one date - eg the
-date you write a cheque, and the date it clears in your bank. When you
+date you write a cheque, and the date it clears in your bank.  When you
 want to model this, for more accurate daily balances, you can specify
 individual posting dates.
 
    Or, you can use the older _secondary date_ feature (Ledger calls it
-auxiliary date or effective date). Note: we support this for
+auxiliary date or effective date).  Note: we support this for
 compatibility, but I usually recommend avoiding this feature; posting
 dates are almost always clearer and simpler.
 
    A secondary date is written after the primary date, following an
-equals sign. If the year is omitted, the primary date's year is
-assumed. When running reports, the primary (left) date is used by
-default, but with the `--date2' flag (or `--aux-date' or `--effective'),
+equals sign.  If the year is omitted, the primary date's year is
+assumed.  When running reports, the primary (left) date is used by
+default, but with the '--date2' flag (or '--aux-date' or '--effective'),
 the secondary (right) date will be used instead.
 
    The meaning of secondary dates is up to you, but it's best to follow
-a consistent rule. Eg "primary = the bank's clearing date, secondary =
+a consistent rule.  Eg "primary = the bank's clearing date, secondary =
 date the transaction was initiated, if different", as shown here:
 
-
 2010/2/23=2/19 movie ticket
   expenses:cinema                   $10
   assets:checking
 
-
 $ hledger register checking
 2010-02-23 movie ticket         assets:checking                $-10         $-10
 
-
 $ hledger register checking --date2
 2010-02-19 movie ticket         assets:checking                $-10         $-10
 
@@ -4651,34 +4414,31 @@ File: hledger.info,  Node: Posting dates,  Prev: Secondary dates,  Up: Dates
 
 You can give individual postings a different date from their parent
 transaction, by adding a posting comment containing a tag (see below)
-like `date:DATE'. This is probably the best way to control posting
-dates precisely. Eg in this example the expense should appear in May
+like 'date:DATE'.  This is probably the best way to control posting
+dates precisely.  Eg in this example the expense should appear in May
 reports, and the deduction from checking should be reported on 6/1 for
 easy bank reconciliation:
 
-
 2015/5/30
     expenses:food     $10  ; food purchased on saturday 5/30
     assets:checking        ; bank cleared it on monday, date:6/1
 
-
 $ hledger -f t.j register food
 2015-05-30                      expenses:food                  $10           $10
 
-
 $ hledger -f t.j register checking
 2015-06-01                      assets:checking               $-10          $-10
 
    DATE should be a simple date; if the year is not specified it will
-use the year of the transaction's date. You can set the secondary date
-similarly, with `date2:DATE2'. The `date:' or `date2:' tags must have a
-valid simple date value if they are present, eg a `date:' tag with no
+use the year of the transaction's date.  You can set the secondary date
+similarly, with 'date2:DATE2'.  The 'date:' or 'date2:' tags must have a
+valid simple date value if they are present, eg a 'date:' tag with no
 value is not allowed.
 
    Ledger's earlier, more compact bracketed date syntax is also
-supported: `[DATE]', `[DATE=DATE2]' or `[=DATE2]'. hledger will attempt
-to parse any square-bracketed sequence of the `0123456789/-.='
-characters in this way. With this syntax, DATE infers its year from the
+supported: '[DATE]', '[DATE=DATE2]' or '[=DATE2]'.  hledger will attempt
+to parse any square-bracketed sequence of the '0123456789/-.='
+characters in this way.  With this syntax, DATE infers its year from the
 transaction and DATE2 infers its year from DATE.
 
 
@@ -4693,42 +4453,43 @@ description or posting account name, separated from it by a space,
 indicating one of three statuses:
 
 mark  status
------------------ 
+ 
+-----------------
       unmarked
-`!'   pending
-`*'   cleared
+'!'   pending
+'*'   cleared
 
-   When reporting, you can filter by status with the `-U/--unmarked',
-`-P/--pending', and `-C/--cleared' flags; or the `status:', `status:!',
-and `status:*' queries; or the U, P, C keys in hledger-ui.
+   When reporting, you can filter by status with the '-U/--unmarked',
+'-P/--pending', and '-C/--cleared' flags; or the 'status:', 'status:!',
+and 'status:*' queries; or the U, P, C keys in hledger-ui.
 
    Note, in Ledger and in older versions of hledger, the "unmarked"
-state is called "uncleared". As of hledger 1.3 we have renamed it to
+state is called "uncleared".  As of hledger 1.3 we have renamed it to
 unmarked for clarity.
 
    To replicate Ledger and old hledger's behaviour of also matching
 pending, combine -U and -P.
 
    Status marks are optional, but can be helpful eg for reconciling with
-real-world accounts. Some editor modes provide highlighting and
-shortcuts for working with status. Eg in Emacs ledger-mode, you can
+real-world accounts.  Some editor modes provide highlighting and
+shortcuts for working with status.  Eg in Emacs ledger-mode, you can
 toggle transaction status with C-c C-e, or posting status with C-c C-c.
 
    What "uncleared", "pending", and "cleared" actually mean is up to
 you.  Here's one suggestion:
 
 status     meaning
--------------------------------------------------------------------------- 
+--------------------------------------------------------------------------
 uncleared  recorded but not yet reconciled; needs review
 pending    tentatively reconciled (if needed, eg during a big
            reconciliation)
 cleared    complete, reconciled as far as possible, and considered
            correct
 
-   With this scheme, you would use `-PC' to see the current balance at
-your bank, `-U' to see things which will probably hit your bank soon
-(like uncashed checks), and no flags to see the most up-to-date state
-of your finances.
+   With this scheme, you would use '-PC' to see the current balance at
+your bank, '-U' to see things which will probably hit your bank soon
+(like uncashed checks), and no flags to see the most up-to-date state of
+your finances.
 
 
 File: hledger.info,  Node: Description,  Next: Comments,  Prev: Status,  Up: JOURNAL FORMAT
@@ -4737,9 +4498,9 @@ File: hledger.info,  Node: Description,  Next: Comments,  Prev: Status,  Up: JOU
 ================
 
 A transaction's description is the rest of the line following the date
-and status mark (or until a comment begins). Sometimes called the
+and status mark (or until a comment begins).  Sometimes called the
 "narration" in traditional bookkeeping, it can be used for whatever you
-wish, or left blank. Transaction descriptions can be queried, unlike
+wish, or left blank.  Transaction descriptions can be queried, unlike
 comments.
 
 * Menu:
@@ -4752,11 +4513,11 @@ File: hledger.info,  Node: Payee and note,  Up: Description
 12.4.1 Payee and note
 ---------------------
 
-You can optionally include a `|' (pipe) character in descriptions to
+You can optionally include a '|' (pipe) character in descriptions to
 subdivide the description into separate fields for payee/payer name on
-the left (up to the first `|') and an additional note field on the
-right (after the first `|'). This may be worthwhile if you need to do
-more precise querying and pivoting by payee or by note.
+the left (up to the first '|') and an additional note field on the right
+(after the first '|').  This may be worthwhile if you need to do more
+precise querying and pivoting by payee or by note.
 
 
 File: hledger.info,  Node: Comments,  Next: Tags,  Prev: Description,  Up: JOURNAL FORMAT
@@ -4764,20 +4525,19 @@ File: hledger.info,  Node: Comments,  Next: Tags,  Prev: Description,  Up: JOURN
 12.5 Comments
 =============
 
-Lines in the journal beginning with a semicolon (`;') or hash (`#') or
-star (`*') are comments, and will be ignored. (Star comments cause
+Lines in the journal beginning with a semicolon (';') or hash ('#') or
+star ('*') are comments, and will be ignored.  (Star comments cause
 org-mode nodes to be ignored, allowing emacs users to fold and navigate
 their journals with org-mode or orgstruct-mode.)
 
    You can attach comments to a transaction by writing them after the
 description and/or indented on the following lines (before the
-postings). Similarly, you can attach comments to an individual posting
+postings).  Similarly, you can attach comments to an individual posting
 by writing them after the amount and/or indented on the following lines.
-Transaction and posting comments must begin with a semicolon (`;').
+Transaction and posting comments must begin with a semicolon (';').
 
    Some examples:
 
-
 # a file comment
 ; another file comment
 * also a file comment, useful in org/orgstruct mode
@@ -4796,8 +4556,8 @@ end comment
     ; another comment line for posting 2
 ; a file comment (because not indented)
 
-   You can also comment larger regions of a file using `comment' and
-`end comment' directives.
+   You can also comment larger regions of a file using 'comment' and
+'end comment' directives.
 
 
 File: hledger.info,  Node: Tags,  Next: Postings,  Prev: Comments,  Up: JOURNAL FORMAT
@@ -4811,35 +4571,29 @@ transactions, which you can then search or pivot on.
    A simple tag is a word (which may contain hyphens) followed by a full
 colon, written inside a transaction or posting comment line:
 
-
 2017/1/16 bought groceries  ; sometag:
 
    Tags can have a value, which is the text after the colon, up to the
 next comma or end of line, with leading/trailing whitespace removed:
 
-
     expenses:food    $10 ; a-posting-tag: the tag value
 
    Note this means hledger's tag values can not contain commas or
 newlines.  Ending at commas means you can write multiple short tags on
 one line, comma separated:
 
-
     assets:checking  ; a comment containing tag1:, tag2: some value ...
 
    Here,
 
-   * "`a comment containing'" is just comment text, not a tag
-
-   * "`tag1'" is a tag with no value
-
-   * "`tag2'" is another tag, whose value is "`some value ...'"
+   * "'a comment containing'" is just comment text, not a tag
+   * "'tag1'" is a tag with no value
+   * "'tag2'" is another tag, whose value is "'some value ...'"
 
    Tags in a transaction comment affect the transaction and all of its
-postings, while tags in a posting comment affect only that posting. For
-example, the following transaction has three tags (`A', `TAG2',
-`third-tag') and the posting has four (those plus `posting-tag'):
-
+postings, while tags in a posting comment affect only that posting.  For
+example, the following transaction has three tags ('A', 'TAG2',
+'third-tag') and the posting has four (those plus 'posting-tag'):
 
 1/1 a transaction  ; A:, TAG2:
     ; third-tag: a third transaction tag, <- with a value
@@ -4855,27 +4609,25 @@ File: hledger.info,  Node: Postings,  Next: Account names,  Prev: Tags,  Up: JOU
 =============
 
 A posting is an addition of some amount to, or removal of some amount
-from, an account. Each posting line begins with at least one space or
+from, an account.  Each posting line begins with at least one space or
 tab (2 or 4 spaces is common), followed by:
 
-   * (optional) a status character (empty, `!', or `*'), followed by a
+   * (optional) a status character (empty, '!', or '*'), followed by a
      space
-
-   * (required) an account name (any text, optionally containing
-     *single spaces*, until end of line or a double space)
-
+   * (required) an account name (any text, optionally containing *single
+     spaces*, until end of line or a double space)
    * (optional) *two or more spaces* or tabs followed by an amount.
 
    Positive amounts are being added to the account, negative amounts are
 being removed.
 
-   The amounts within a transaction must always sum up to zero. As a
+   The amounts within a transaction must always sum up to zero.  As a
 convenience, one amount may be left blank; it will be inferred so as to
 balance the transaction.
 
    Be sure to note the unusual two-space delimiter between account name
-and amount. This makes it easy to write account names containing
-spaces. But if you accidentally leave only one space (or tab) before
+and amount.  This makes it easy to write account names containing
+spaces.  But if you accidentally leave only one space (or tab) before
 the amount, the amount will be considered part of the account name.
 
 * Menu:
@@ -4893,19 +4645,17 @@ posting_ or _unbalanced posting_, which means it is exempt from the
 usual rule that a transaction's postings must balance add up to zero.
 
    This is not part of double entry accounting, so you might choose to
-avoid this feature. Or you can use it sparingly for certain special
-cases where it can be convenient. Eg, you could set opening balances
+avoid this feature.  Or you can use it sparingly for certain special
+cases where it can be convenient.  Eg, you could set opening balances
 without using a balancing equity account:
 
-
 1/1 opening balances
   (assets:checking)   $1000
   (assets:savings)    $2000
 
-   A posting with a bracketed account name is called a _balanced
-virtual posting_. The balanced virtual postings in a transaction must
-add up to zero (separately from other postings). Eg:
-
+   A posting with a bracketed account name is called a _balanced virtual
+posting_.  The balanced virtual postings in a transaction must add up to
+zero (separately from other postings).  Eg:
 
 1/1 buy food with cash, update budget envelope subaccounts, & something else
   assets:cash                    $-10 ; <- these balance
@@ -4916,8 +4666,8 @@ add up to zero (separately from other postings). Eg:
   (something:else)                 $5       ; <- not required to balance
 
    Ordinary non-parenthesised, non-bracketed postings are called _real
-postings_. You can exclude virtual postings from reports with the
-`-R/--real' flag or `real:1' query.
+postings_.  You can exclude virtual postings from reports with the
+'-R/--real' flag or 'real:1' query.
 
 
 File: hledger.info,  Node: Account names,  Next: Amounts,  Prev: Postings,  Up: JOURNAL FORMAT
@@ -4926,12 +4676,13 @@ File: hledger.info,  Node: Account names,  Next: Amounts,  Prev: Postings,  Up:
 ==================
 
 Account names typically have several parts separated by a full colon,
-from which hledger derives a hierarchical chart of accounts. They can be
-anything you like, but in finance there are traditionally five top-level
-accounts: `assets', `liabilities', `revenue', `expenses', and `equity'.
+from which hledger derives a hierarchical chart of accounts.  They can
+be anything you like, but in finance there are traditionally five
+top-level accounts: 'assets', 'liabilities', 'revenue', 'expenses', and
+'equity'.
 
-   Account names may contain single spaces, eg: `assets:accounts
-receivable'. Because of this, they must always be followed by *two or
+   Account names may contain single spaces, eg: 'assets:accounts
+receivable'.  Because of this, they must always be followed by *two or
 more spaces* (or newline).
 
    Account names can be aliased.
@@ -4942,12 +4693,12 @@ File: hledger.info,  Node: Amounts,  Next: Transaction prices,  Prev: Account na
 12.9 Amounts
 ============
 
-After the account name, there is usually an amount. (Important: between
+After the account name, there is usually an amount.  (Important: between
 account name and amount, there must be *two or more spaces*.)
 
    hledger's amount format is flexible, supporting several international
-formats. Here are some examples. Amounts have a number (the "quantity"):
-
+formats.  Here are some examples.  Amounts have a number (the
+"quantity"):
 
 1
 
@@ -4955,7 +4706,6 @@ formats. Here are some examples. Amounts have a number (the "quantity"):
 below), to the left or right of the quantity, with or without a
 separating space:
 
-
 $1
 4000 AAPL
 3 "green apples"
@@ -4964,20 +4714,17 @@ $1
 is the default), The sign can be written before or after a left-side
 commodity symbol:
 
-
 -$1
 $-1
 
    One or more spaces between the sign and the number are acceptable
 when parsing (but they won't be displayed in output):
 
-
 + $1
 $-      1
 
    Scientific E notation is allowed:
 
-
 1E-6
 EUR 1E3
 
@@ -4997,14 +4744,12 @@ File: hledger.info,  Node: Decimal marks digit group marks,  Next: Commodity,  U
 
 A decimal mark can be written as a period or a comma:
 
-
 1.23
 1,23456780000009
 
    In the integer part of the quantity (left of the decimal mark),
-groups of digits can optionally be separated by a "digit group mark" -
-a space, comma, or period (different from the decimal mark):
-
+groups of digits can optionally be separated by a "digit group mark" - a
+space, comma, or period (different from the decimal mark):
 
      $1,000,000.00
   EUR 2.000.000,00
@@ -5012,17 +4757,16 @@ INR 9,99,99,999.00
       1 000 000.9455
 
    Note, a number containing a single digit group mark and no decimal
-mark is ambiguous. Are these digit group marks or decimal marks ?
-
+mark is ambiguous.  Are these digit group marks or decimal marks ?
 
 1,000
 1.000
 
    If you don't tell it otherwise, hledger will assume both of the above
-are decimal marks, parsing both numbers as 1. To prevent confusion and
-undetected typos, we recommend adding `commodity' directives at the top
+are decimal marks, parsing both numbers as 1.  To prevent confusion and
+undetected typos, we recommend adding 'commodity' directives at the top
 of your journal file to explicitly declare the decimal mark (and
-optionally a digit group mark) for each commodity. Read on for more
+optionally a digit group mark) for each commodity.  Read on for more
 about this.
 
 
@@ -5036,20 +4780,20 @@ number, and a "commodity", which is a currency symbol, stock ticker, or
 any word or phrase describing something you are tracking.
 
    If the commodity name contains non-letters (spaces, numbers, or
-punctuation), you must always write it inside double quotes (`"green
-apples"', `"ABC123"').
+punctuation), you must always write it inside double quotes ('"green
+apples"', '"ABC123"').
 
    If you write just a bare number, that too will have a commodity, with
-name `""'; we call that the "no-symbol commodity".
+name '""'; we call that the "no-symbol commodity".
 
    Actually, hledger combines these single-commodity amounts into more
 powerful multi-commodity amounts, which are what it works with most of
-the time. A multi-commodity amount could be, eg: `1 USD, 2 EUR, 3.456
-TSLA'. In practice, you will only see multi-commodity amounts in
+the time.  A multi-commodity amount could be, eg: '1 USD, 2 EUR, 3.456
+TSLA'.  In practice, you will only see multi-commodity amounts in
 hledger's output; you can't write them directly in the journal file.
 
    (If you are writing scripts or working with hledger's internals,
-these are the `Amount' and `MixedAmount' types.)
+these are the 'Amount' and 'MixedAmount' types.)
 
 
 File: hledger.info,  Node: Commodity directives,  Next: Commodity display style,  Prev: Commodity,  Up: Amounts
@@ -5057,12 +4801,11 @@ File: hledger.info,  Node: Commodity directives,  Next: Commodity display style,
 12.9.3 Commodity directives
 ---------------------------
 
-You can add `commodity' directives to the journal, preferably at the
+You can add 'commodity' directives to the journal, preferably at the
 top, to declare your commodities and help with number parsing (see
-above) and display (see below). These are optional, but recommended.
+above) and display (see below).  These are optional, but recommended.
 They are described in more detail in JOURNAL FORMAT -> Declaring
-commodities. Here's a quick example:
-
+commodities.  Here's a quick example:
 
 # number format and display style for $, EUR, INR and the no-symbol commodity:
 commodity $1,000.00
@@ -5077,13 +4820,13 @@ File: hledger.info,  Node: Commodity display style,  Next: Rounding,  Prev: Comm
 ------------------------------
 
 For the amounts in each commodity, hledger chooses a consistent display
-style to use in most reports. (Exceptions: price amounts, and all
-amounts displayed by the `print' command, are displayed with all of
+style to use in most reports.  (Exceptions: price amounts, and all
+amounts displayed by the 'print' command, are displayed with all of
 their decimal digits visible.)
 
    A commodity's display style is inferred as follows.
 
-   First, if a default commodity is declared with `D', this commodity
+   First, if a default commodity is declared with 'D', this commodity
 and its style is applied to any no-symbol amounts in the journal.
 
    Then each commodity's style is inferred from one of the following, in
@@ -5091,39 +4834,34 @@ order of preference:
 
    * The commodity directive for that commodity (including the no-symbol
      commodity), if any.
-
    * The amounts in that commodity seen in the journal's transactions.
      (Posting amounts only; prices and periodic or auto rules are
      ignored, currently.)
-
-   * The built-in fallback style, which looks like this: `$1000.00'.
+   * The built-in fallback style, which looks like this: '$1000.00'.
      (Symbol on the left, period decimal mark, two decimal places.)
 
    A style is inferred from journal amounts as follows:
 
    * Use the general style (decimal mark, symbol placement) of the first
      amount
-
    * Use the first-seen digit group style (digit group mark, digit group
      sizes), if any
-
    * Use the maximum number of decimal places of all.
 
    Transaction price amounts don't affect the commodity display style
 directly, but occasionally they can do so indirectly (eg when a
-posting's amount is inferred using a transaction price). If you find
+posting's amount is inferred using a transaction price).  If you find
 this causing problems, use a commodity directive to fix the display
 style.
 
    To summarise: each commodity's amounts will be normalised to (a) the
-style declared by a `commodity' directive, or (b) the style of the
-first posting amount in the journal, with the first-seen digit group
-style and the maximum-seen number of decimal places. So if your reports
-are showing amounts in a way you don't like, eg with too many decimal
-places, use a commodity directive. Some examples:
+style declared by a 'commodity' directive, or (b) the style of the first
+posting amount in the journal, with the first-seen digit group style and
+the maximum-seen number of decimal places.  So if your reports are
+showing amounts in a way you don't like, eg with too many decimal
+places, use a commodity directive.  Some examples:
 
-
-# declare euro, dollar, bitcoin and no-symbol commodities and set their
+# declare euro, dollar, bitcoin and no-symbol commodities and set their 
 # input number formats and output display styles:
 commodity EUR 1.000,
 commodity $1000.00
@@ -5138,10 +4876,10 @@ File: hledger.info,  Node: Rounding,  Prev: Commodity display style,  Up: Amount
 
 Amounts are stored internally as decimal numbers with up to 255 decimal
 places, and displayed with the number of decimal places specified by the
-commodity display style. Note, hledger uses banker's rounding: it rounds
-to the nearest even number, eg 0.5 displayed with zero decimal places is
-"0"). (Guaranteed since hledger 1.17.1; in older versions this could
-vary if hledger was built with Decimal < 0.5.1.)
+commodity display style.  Note, hledger uses banker's rounding: it
+rounds to the nearest even number, eg 0.5 displayed with zero decimal
+places is "0").  (Guaranteed since hledger 1.17.1; in older versions
+this could vary if hledger was built with Decimal < 0.5.1.)
 
 
 File: hledger.info,  Node: Transaction prices,  Next: Lot prices lot dates,  Prev: Amounts,  Up: JOURNAL FORMAT
@@ -5150,24 +4888,22 @@ File: hledger.info,  Node: Transaction prices,  Next: Lot prices lot dates,  Pre
 ========================
 
 Within a transaction, you can note an amount's price in another
-commodity. This can be used to document the cost (in a purchase) or
-selling price (in a sale). For example, transaction prices are useful to
-record purchases of a foreign currency. Note transaction prices are
-fixed at the time of the transaction, and do not change over time. See
+commodity.  This can be used to document the cost (in a purchase) or
+selling price (in a sale).  For example, transaction prices are useful
+to record purchases of a foreign currency.  Note transaction prices are
+fixed at the time of the transaction, and do not change over time.  See
 also market prices, which represent prevailing exchange rates on a
 certain date.
 
    There are several ways to record a transaction price:
 
-  1. Write the price per unit, as `@ UNITPRICE' after the amount:
-
+  1. Write the price per unit, as '@ UNITPRICE' after the amount:
 
      2009/1/1
        assets:euros     €100 @ $1.35  ; one hundred euros purchased at $1.35 each
        assets:dollars                 ; balancing amount is -$135.00
 
-  2. Write the total price, as `@@ TOTALPRICE' after the amount:
-
+  2. Write the total price, as '@@ TOTALPRICE' after the amount:
 
      2009/1/1
        assets:euros     €100 @@ $135  ; one hundred euros purchased at $135 for the lot
@@ -5176,25 +4912,22 @@ certain date.
   3. Specify amounts for all postings, using exactly two commodities,
      and let hledger infer the price that balances the transaction:
 
-
      2009/1/1
        assets:euros     €100          ; one hundred euros purchased
        assets:dollars  $-135          ; for $135
 
-  4. Like 1, but the `@' is parenthesised, i.e. `(@)'; this is for
+  4. Like 1, but the '@' is parenthesised, i.e.  '(@)'; this is for
      compatibility with Ledger journals (Virtual posting costs), and is
      equivalent to 1 in hledger.
 
-  5. Like 2, but as in 4 the `@@' is parenthesised, i.e.  `(@@)'; in
+  5. Like 2, but as in 4 the '@@' is parenthesised, i.e.  '(@@)'; in
      hledger, this is equivalent to 2.
 
-
-   Use the `-B/--cost' flag to convert amounts to their transaction
-price's commodity, if any. (mnemonic: "B" is from "cost Basis", as in
-Ledger). Eg here is how -B affects the balance report for the example
+   Use the '-B/--cost' flag to convert amounts to their transaction
+price's commodity, if any.  (mnemonic: "B" is from "cost Basis", as in
+Ledger).  Eg here is how -B affects the balance report for the example
 above:
 
-
 $ hledger bal -N --flat
                $-135  assets:dollars
                 €100  assets:euros
@@ -5204,15 +4937,13 @@ $ hledger bal -N --flat -B
 
    Note -B is sensitive to the order of postings when a transaction
 price is inferred: the inferred price will be in the commodity of the
-last amount. So if example 3's postings are reversed, while the
+last amount.  So if example 3's postings are reversed, while the
 transaction is equivalent, -B shows something different:
 
-
 2009/1/1
   assets:dollars  $-135              ; 135 dollars sold
   assets:euros     €100              ; for 100 euros
 
-
 $ hledger bal -N --flat -B
                €-100  assets:dollars  # <- the dollars' selling price
                 €100  assets:euros
@@ -5224,13 +4955,13 @@ File: hledger.info,  Node: Lot prices lot dates,  Next: Balance assertions,  Pre
 ===========================
 
 Ledger allows another kind of price, lot price (four variants:
-`{UNITPRICE}', `{{TOTALPRICE}}', `{=FIXEDUNITPRICE}',
-`{{=FIXEDTOTALPRICE}}'), and/or a lot date (`[DATE]') to be specified.
+'{UNITPRICE}', '{{TOTALPRICE}}', '{=FIXEDUNITPRICE}',
+'{{=FIXEDTOTALPRICE}}'), and/or a lot date ('[DATE]') to be specified.
 These are normally used to select a lot when selling investments.
 hledger will parse these, for compatibility with Ledger journals, but
-currently ignores them. A transaction price, lot price and/or lot date
-may appear in any order, after the posting amount and before the
-balance assertion if any.
+currently ignores them.  A transaction price, lot price and/or lot date
+may appear in any order, after the posting amount and before the balance
+assertion if any.
 
 
 File: hledger.info,  Node: Balance assertions,  Next: Balance assignments,  Prev: Lot prices lot dates,  Up: JOURNAL FORMAT
@@ -5238,12 +4969,11 @@ File: hledger.info,  Node: Balance assertions,  Next: Balance assignments,  Prev
 12.12 Balance assertions
 ========================
 
-hledger supports Ledger-style balance assertions in journal files. These
-look like, for example, `= EXPECTEDBALANCE' following a posting's
-amount. Eg here we assert the expected dollar balance in accounts a and
+hledger supports Ledger-style balance assertions in journal files.
+These look like, for example, '= EXPECTEDBALANCE' following a posting's
+amount.  Eg here we assert the expected dollar balance in accounts a and
 b after each posting:
 
-
 2013/1/1
   a   $1  =$1
   b       =$-1
@@ -5253,12 +4983,12 @@ b after each posting:
   b  $-1  =$-2
 
    After reading a journal file, hledger will check all balance
-assertions and report an error if any of them fail. Balance assertions
+assertions and report an error if any of them fail.  Balance assertions
 can protect you from, eg, inadvertently disrupting reconciled balances
-while cleaning up old entries. You can disable them temporarily with the
-`-I/--ignore-assertions' flag, which can be useful for troubleshooting
-or for reading Ledger files. (Note: this flag currently does not
-disable balance assignments, below).
+while cleaning up old entries.  You can disable them temporarily with
+the '-I/--ignore-assertions' flag, which can be useful for
+troubleshooting or for reading Ledger files.  (Note: this flag currently
+does not disable balance assignments, below).
 
 * Menu:
 
@@ -5278,17 +5008,17 @@ File: hledger.info,  Node: Assertions and ordering,  Next: Assertions and includ
 -------------------------------
 
 hledger sorts an account's postings and assertions first by date and
-then (for postings on the same day) by parse order. Note this is
+then (for postings on the same day) by parse order.  Note this is
 different from Ledger, which sorts assertions only by parse order.
 (Also, Ledger assertions do not see the accumulated effect of repeated
 postings to the same account within a transaction.)
 
    So, hledger balance assertions keep working if you reorder
-differently-dated transactions within the journal. But if you reorder
+differently-dated transactions within the journal.  But if you reorder
 same-dated transactions or postings, assertions might break and require
-updating. This order dependence does bring an advantage: precise control
-over the order of postings and assertions within a day, so you can
-assert intra-day balances.
+updating.  This order dependence does bring an advantage: precise
+control over the order of postings and assertions within a day, so you
+can assert intra-day balances.
 
 
 File: hledger.info,  Node: Assertions and included files,  Next: Assertions and multiple -f options,  Prev: Assertions and ordering,  Up: Balance assertions
@@ -5296,8 +5026,8 @@ File: hledger.info,  Node: Assertions and included files,  Next: Assertions and
 12.12.2 Assertions and included files
 -------------------------------------
 
-With included files, things are a little more complicated. Including
-preserves the ordering of postings and assertions. If you have multiple
+With included files, things are a little more complicated.  Including
+preserves the ordering of postings and assertions.  If you have multiple
 postings to an account on the same day, split across different files,
 and you also want to assert the account's balance on the same day,
 you'll have to put the assertion in the right file.
@@ -5309,7 +5039,7 @@ File: hledger.info,  Node: Assertions and multiple -f options,  Next: Assertions
 ------------------------------------------
 
 Balance assertions don't work well across files specified with multiple
--f options. Use include or concatenate the files instead.
+-f options.  Use include or concatenate the files instead.
 
 
 File: hledger.info,  Node: Assertions and commodities,  Next: Assertions and prices,  Prev: Assertions and multiple -f options,  Up: Balance assertions
@@ -5319,18 +5049,17 @@ File: hledger.info,  Node: Assertions and commodities,  Next: Assertions and pri
 
 The asserted balance must be a simple single-commodity amount, and in
 fact the assertion checks only this commodity's balance within the
-(possibly multi-commodity) account balance. This is how assertions work
-in Ledger also. We could call this a "partial" balance assertion.
+(possibly multi-commodity) account balance.  This is how assertions work
+in Ledger also.  We could call this a "partial" balance assertion.
 
    To assert the balance of more than one commodity in an account, you
 can write multiple postings, each asserting one commodity's balance.
 
    You can make a stronger "total" balance assertion by writing a double
-equals sign (`== EXPECTEDBALANCE'). This asserts that there are no
+equals sign ('== EXPECTEDBALANCE').  This asserts that there are no
 other unasserted commodities in the account (or, that their balance is
 0).
 
-
 2013/1/1
   a   $1
   a    1€
@@ -5347,10 +5076,9 @@ other unasserted commodities in the account (or, that their balance is
   a    0 ==  $1
 
    It's not yet possible to make a complete assertion about a balance
-that has multiple commodities. One workaround is to isolate each
+that has multiple commodities.  One workaround is to isolate each
 commodity into its own subaccount:
 
-
 2013/1/1
   a:usd   $1
   a:euro   1€
@@ -5370,14 +5098,13 @@ File: hledger.info,  Node: Assertions and prices,  Next: Assertions and subaccou
 Balance assertions ignore transaction prices, and should normally be
 written without one:
 
-
 2019/1/1
   (a)     $1 @ €1 = $1
 
    We do allow prices to be written there, however, and print shows
 them, even though they don't affect whether the assertion passes or
-fails.  This is for backward compatibility (hledger's close command
-used to generate balance assertions with prices), and because balance
+fails.  This is for backward compatibility (hledger's close command used
+to generate balance assertions with prices), and because balance
 _assignments_ do use them (see below).
 
 
@@ -5386,12 +5113,11 @@ File: hledger.info,  Node: Assertions and subaccounts,  Next: Assertions and vir
 12.12.6 Assertions and subaccounts
 ----------------------------------
 
-The balance assertions above (`=' and `==') do not count the balance
-from subaccounts; they check the account's exclusive balance only. You
-can assert the balance including subaccounts by writing `=*' or `==*',
+The balance assertions above ('=' and '==') do not count the balance
+from subaccounts; they check the account's exclusive balance only.  You
+can assert the balance including subaccounts by writing '=*' or '==*',
 eg:
 
-
 2019/1/1
   equity:opening balances
   checking:a       5
@@ -5405,7 +5131,8 @@ File: hledger.info,  Node: Assertions and virtual postings,  Next: Assertions an
 ---------------------------------------
 
 Balance assertions are checked against all postings, both real and
-virtual. They are not affected by the `--real/-R' flag or `real:' query.
+virtual.  They are not affected by the '--real/-R' flag or 'real:'
+query.
 
 
 File: hledger.info,  Node: Assertions and precision,  Prev: Assertions and virtual postings,  Up: Balance assertions
@@ -5414,8 +5141,8 @@ File: hledger.info,  Node: Assertions and precision,  Prev: Assertions and virtu
 --------------------------------
 
 Balance assertions compare the exactly calculated amounts, which are not
-always what is shown by reports. Eg a commodity directive may limit the
-display precision, but this will not affect balance assertions. Balance
+always what is shown by reports.  Eg a commodity directive may limit the
+display precision, but this will not affect balance assertions.  Balance
 assertion failure messages show exact amounts.
 
 
@@ -5424,13 +5151,12 @@ File: hledger.info,  Node: Balance assignments,  Next: Directives,  Prev: Balanc
 12.13 Balance assignments
 =========================
 
-Ledger-style balance assignments are also supported. These are like
+Ledger-style balance assignments are also supported.  These are like
 balance assertions, but with no posting amount on the left side of the
 equals sign; instead it is calculated automatically so as to satisfy the
-assertion. This can be a convenience during data entry, eg when setting
+assertion.  This can be a convenience during data entry, eg when setting
 opening balances:
 
-
 ; starting a new journal, set asset account balances
 2016/1/1 opening balances
   assets:checking            = $409.32
@@ -5440,7 +5166,6 @@ opening balances:
 
    or when adjusting a balance to reality:
 
-
 ; no cash left; update balance, record any untracked spending as a generic expense
 2016/1/15
   assets:cash    = $0
@@ -5449,7 +5174,7 @@ opening balances:
    The calculated amount depends on the account's balance in the
 commodity at that point (which depends on the previously-dated postings
 of the commodity to that account since the last balance assertion or
-assignment). Note that using balance assignments makes your journal a
+assignment).  Note that using balance assignments makes your journal a
 little less explicit; to know the exact amount posted, you have to run
 hledger or do the calculations yourself, instead of just reading it.
 
@@ -5466,11 +5191,9 @@ File: hledger.info,  Node: Balance assignments and prices,  Up: Balance assignme
 A transaction price in a balance assignment will cause the calculated
 amount to have that price attached:
 
-
 2019/1/1
   (a)             = $1 @ €2
 
-
 $ hledger print --explicit
 2019-01-01
     (a)         $1 @ €2 = $1 @ €2
@@ -5482,34 +5205,34 @@ File: hledger.info,  Node: Directives,  Next: Directives and multiple files,  Pr
 ================
 
 A directive is a line in the journal beginning with a special keyword,
-that influences how the journal is processed. hledger's directives are
+that influences how the journal is processed.  hledger's directives are
 based on a subset of Ledger's, but there are many differences (and also
 some differences between hledger versions).
 
    Directives' behaviour and interactions can get a little bit complex,
 so here is a table summarising the directives and their effects, with
-links to more detailed docs. Note part of this table is hidden when
+links to more detailed docs.  Note part of this table is hidden when
 viewed in a web browser - scroll it sideways to see more.
 
-directiveend       subdirectivespurpose                       can affect (as of
+directiveend       subdirectivespurpose                  can affect (as of
          directive                                       2018/06)
------------------------------------------------------------------------------ 
-`account'          any     document account names,       all entries in all
-                   text    declare account types &       files, before or
-                           display order                 after
-`alias'  `end              rewrite account names         following entries
+-----------------------------------------------------------------------------
+'account'          any     document account names,       all entries in
+                   text    declare account types &       all files, before
+                           display order                 or after
+'alias'  'end              rewrite account names         following entries
          aliases'                                        until end of
                                                          current file or
                                                          end directive
-`apply   `end              prepend a common parent to    following entries
+'apply   'end              prepend a common parent to    following entries
 account' apply             account names                 until end of
          account'                                        current file or
                                                          end directive
-`comment'`end              ignore part of journal        following entries
+'comment''end              ignore part of journal        following entries
          comment'                                        until end of
                                                          current file or
                                                          end directive
-`commodity'          `format'declare a commodity and its   number notation:
+'commodity'        'format'declare a commodity and its   number notation:
                            number notation & display     following entries
                            style                         in that commodity
                                                          in all files ;
@@ -5517,10 +5240,11 @@ account' apply             account names                 until end of
                                                          amounts of that
                                                          commodity in
                                                          reports
-`D'                        declare a commodity to be     default commodity:
-                           used for commodityless        following
-                           amounts, and its number       commodityless
-                           notation & display style      entries until end
+'D'                        declare a commodity to be     default
+                           used for commodityless        commodity:
+                           amounts, and its number       following
+                           notation & display style      commodityless
+                                                         entries until end
                                                          of current file;
                                                          number notation:
                                                          following entries
@@ -5531,39 +5255,39 @@ account' apply             account names                 until end of
                                                          amounts of that
                                                          commodity in
                                                          reports
-`include'                  include entries/directives    what the included
+'include'                  include entries/directives    what the included
                            from another file             directives affect
-[`payee']                  declare a payee name          following entries
+['payee']                  declare a payee name          following entries
                                                          until end of
                                                          current file
-`P'                        declare a market price for a  amounts of that
-                           commodity                     commodity in
+'P'                        declare a market price for    amounts of that
+                           a commodity                   commodity in
                                                          reports, when -V
                                                          is used
-`Y'                        declare a year for yearless   following entries
+'Y'                        declare a year for yearless   following entries
                            dates                         until end of
                                                          current file
-`='                        declare an auto posting       all entries in
+'='                        declare an auto posting       all entries in
                            rule, adding postings to      parent/current/child
                            other transactions            files (but not
-                                                         sibling files, see
-                                                         #1212)
+                                                         sibling files,
+                                                         see #1212)
 
    And some definitions:
 
 subdirectiveoptional indented directive line immediately following a parent
        directive
 number how to interpret numbers when parsing journal entries (the
-notationidentity of the decimal separator character). (Currently each
+notationidentity of the decimal separator character).  (Currently each
        commodity can have its own notation, even in the same file.)
-displayhow to display amounts of a commodity in reports (symbol side and
-style  spacing, digit groups, decimal separator, decimal places)
-directivewhich entries and (when there are multiple files) which files are
-scope  affected by a directive
+displayhow to display amounts of a commodity in reports (symbol side
+style  and spacing, digit groups, decimal separator, decimal places)
+directivewhich entries and (when there are multiple files) which files
+scope  are affected by a directive
 
    As you can see, directives vary in which journal entries and files
 they affect, and whether they are focussed on input (parsing) or output
-(reports). Some directives have multiple effects.
+(reports).  Some directives have multiple effects.
 
 
 File: hledger.info,  Node: Directives and multiple files,  Next: Comment blocks,  Prev: Directives,  Up: JOURNAL FORMAT
@@ -5571,18 +5295,18 @@ File: hledger.info,  Node: Directives and multiple files,  Next: Comment blocks,
 12.15 Directives and multiple files
 ===================================
 
-If you use multiple `-f'/`--file' options, or the `include' directive,
-hledger will process multiple input files. But note that directives
+If you use multiple '-f'/'--file' options, or the 'include' directive,
+hledger will process multiple input files.  But note that directives
 which affect input (see above) typically last only until the end of the
 file in which they occur.
 
    This may seem inconvenient, but it's intentional; it makes reports
-stable and deterministic, independent of the order of input. Otherwise
+stable and deterministic, independent of the order of input.  Otherwise
 you could see different numbers if you happened to write -f options in a
 different order, or if you moved includes around while cleaning up your
 files.
 
-   It can be surprising though; for example, it means that `alias'
+   It can be surprising though; for example, it means that 'alias'
 directives do not affect parent or sibling files (see below).
 
 
@@ -5591,9 +5315,9 @@ File: hledger.info,  Node: Comment blocks,  Next: Including other files,  Prev:
 12.16 Comment blocks
 ====================
 
-A line containing just `comment' starts a commented region of the file,
-and a line containing just `end comment' (or the end of the current
-file) ends it. See also comments.
+A line containing just 'comment' starts a commented region of the file,
+and a line containing just 'end comment' (or the end of the current
+file) ends it.  See also comments.
 
 
 File: hledger.info,  Node: Including other files,  Next: Default year,  Prev: Comment blocks,  Up: JOURNAL FORMAT
@@ -5604,7 +5328,6 @@ File: hledger.info,  Node: Including other files,  Next: Default year,  Prev: Co
 You can pull in the content of additional files by writing an include
 directive, like this:
 
-
 include FILEPATH
 
    Only journal files can include, and only journal, timeclock or
@@ -5613,19 +5336,19 @@ timedot files can be included (not CSV files, currently).
    If the file path does not begin with a slash, it is relative to the
 current file's folder.
 
-   A tilde means home directory, eg: `include ~/main.journal'.
+   A tilde means home directory, eg: 'include ~/main.journal'.
 
    The path may contain glob patterns to match multiple files, eg:
-`include *.journal'.
+'include *.journal'.
 
-   There is limited support for recursive wildcards: `**/' (the slash
-is required) matches 0 or more subdirectories. It's not super convenient
+   There is limited support for recursive wildcards: '**/' (the slash is
+required) matches 0 or more subdirectories.  It's not super convenient
 since you have to avoid include cycles and including directories, but
-this can be done, eg: `include */**/*.journal'.
+this can be done, eg: 'include */**/*.journal'.
 
    The path may also be prefixed to force a specific file format,
 overriding the file extension (as described in hledger.1 -> Input
-files): `include timedot:~/notes/2020*.md'.
+files): 'include timedot:~/notes/2020*.md'.
 
 
 File: hledger.info,  Node: Default year,  Next: Declaring payees,  Prev: Including other files,  Up: JOURNAL FORMAT
@@ -5634,10 +5357,9 @@ File: hledger.info,  Node: Default year,  Next: Declaring payees,  Prev: Includi
 ==================
 
 You can set a default year to be used for subsequent dates which don't
-specify a year. This is a line beginning with `Y' followed by the year.
+specify a year.  This is a line beginning with 'Y' followed by the year.
 Eg:
 
-
 Y2009  ; set default year to 2009
 
 12/15  ; equivalent to 2009/12/15
@@ -5660,11 +5382,10 @@ File: hledger.info,  Node: Declaring payees,  Next: Declaring commodities,  Prev
 12.19 Declaring payees
 ======================
 
-The `payee' directive can be used to declare a limited set of payees
-which may appear in transaction descriptions. The "payees" check will
+The 'payee' directive can be used to declare a limited set of payees
+which may appear in transaction descriptions.  The "payees" check will
 report an error if any transaction refers to a payee that has not been
-declared. Eg:
-
+declared.  Eg:
 
 payee Whole Foods
 
@@ -5674,24 +5395,23 @@ File: hledger.info,  Node: Declaring commodities,  Next: Default commodity,  Pre
 12.20 Declaring commodities
 ===========================
 
-You can use `commodity' directives to declare your commodities. In fact
-the `commodity' directive performs several functions at once:
+You can use 'commodity' directives to declare your commodities.  In fact
+the 'commodity' directive performs several functions at once:
 
-  1. It declares commodities which may be used in the journal. This can
-     optionally be enforced, providing useful error checking. (Cf
+  1. It declares commodities which may be used in the journal.  This can
+     optionally be enforced, providing useful error checking.  (Cf
      Commodity error checking)
 
   2. It declares which decimal mark character (period or comma), to
      expect when parsing input - useful to disambiguate international
-     number formats in your data. Without this, hledger will parse both
-     `1,000' and `1.000' as 1. (Cf Amounts)
+     number formats in your data.  Without this, hledger will parse both
+     '1,000' and '1.000' as 1.  (Cf Amounts)
 
   3. It declares how to render the commodity's amounts when displaying
      output - the decimal mark, any digit group marks, the number of
-     decimal places, symbol placement and so on. (Cf Commodity display
+     decimal places, symbol placement and so on.  (Cf Commodity display
      style)
 
-
    You will run into one of the problems solved by commodity directives
 sooner or later, so we recommend using them, for robust and predictable
 parsing and display.
@@ -5699,20 +5419,18 @@ parsing and display.
    Generally you should put them at the top of your journal file (since
 for function 2, they affect only following amounts, cf #793).
 
-   A commodity directive is just the word `commodity' followed by a
+   A commodity directive is just the word 'commodity' followed by a
 sample amount, like this:
 
-
 ;commodity SAMPLEAMOUNT
 
 commodity $1000.00
 commodity 1,000.0000 AAAA  ; optional same-line comment
 
-   It may also be written on multiple lines, and use the `format'
-subdirective, as in Ledger. Note in this case the commodity symbol
+   It may also be written on multiple lines, and use the 'format'
+subdirective, as in Ledger.  Note in this case the commodity symbol
 appears twice; it must be the same in both places:
 
-
 ;commodity SYMBOL
 ;  format SAMPLEAMOUNT
 
@@ -5731,7 +5449,6 @@ comma - followed by 0 or more decimal digits.
 
    A few more examples:
 
-
 # number formats for $, EUR, INR and the no-symbol commodity:
 commodity $1,000.00
 commodity EUR 1.000,00
@@ -5739,7 +5456,7 @@ commodity INR 9,99,99,999.0
 commodity 1 000 000.
 
    Note hledger normally uses banker's rounding, so 0.5 displayed with
-zero decimal digits is "0". (More at Commodity display style.)
+zero decimal digits is "0".  (More at Commodity display style.)
 
 * Menu:
 
@@ -5751,10 +5468,10 @@ File: hledger.info,  Node: Commodity error checking,  Up: Declaring commodities
 12.20.1 Commodity error checking
 --------------------------------
 
-In strict mode, enabled with the `-s'/`--strict' flag, hledger will
-report an error if a commodity symbol is used that has not been
-declared by a `commodity' directive. This works similarly to account
-error checking, see the notes there for more details.
+In strict mode, enabled with the '-s'/'--strict' flag, hledger will
+report an error if a commodity symbol is used that has not been declared
+by a 'commodity' directive.  This works similarly to account error
+checking, see the notes there for more details.
 
 
 File: hledger.info,  Node: Default commodity,  Next: Declaring market prices,  Prev: Declaring commodities,  Up: JOURNAL FORMAT
@@ -5762,21 +5479,20 @@ File: hledger.info,  Node: Default commodity,  Next: Declaring market prices,  P
 12.21 Default commodity
 =======================
 
-The `D' directive sets a default commodity, to be used for any
+The 'D' directive sets a default commodity, to be used for any
 subsequent commodityless amounts (ie, plain numbers) seen while parsing
-the journal. This effect lasts until the next `D' directive, or the end
+the journal.  This effect lasts until the next 'D' directive, or the end
 of the journal.
 
-   For compatibility/historical reasons, `D' also acts like a
-`commodity' directive (setting the commodity's decimal mark for parsing
+   For compatibility/historical reasons, 'D' also acts like a
+'commodity' directive (setting the commodity's decimal mark for parsing
 and display style for output).
 
-   As with `commodity', the amount must include a decimal mark (either
-period or comma). If both `commodity' and `D' directives are used for
-the same commodity, the `commodity' style takes precedence.
-
-   The syntax is `D AMOUNT'. Eg:
+   As with 'commodity', the amount must include a decimal mark (either
+period or comma).  If both 'commodity' and 'D' directives are used for
+the same commodity, the 'commodity' style takes precedence.
 
+   The syntax is 'D AMOUNT'.  Eg:
 
 ; commodity-less amounts should be treated as dollars
 ; (and displayed with the dollar sign on the left, thousands separators and two decimal places)
@@ -5792,33 +5508,29 @@ File: hledger.info,  Node: Declaring market prices,  Next: Declaring accounts,
 12.22 Declaring market prices
 =============================
 
-The `P' directive declares a market price, which is an exchange rate
-between two commodities on a certain date. (In Ledger, they are called
-"historical prices".) These are often obtained from a stock exchange,
+The 'P' directive declares a market price, which is an exchange rate
+between two commodities on a certain date.  (In Ledger, they are called
+"historical prices".)  These are often obtained from a stock exchange,
 cryptocurrency exchange, or the foreign exchange market.
 
    Here is the format:
 
-
 P DATE COMMODITYA COMMODITYBAMOUNT
 
    * DATE is a simple date
-
    * COMMODITYA is the symbol of the commodity being priced
-
    * COMMODITYBAMOUNT is an amount (symbol and quantity) in a second
-     commodity, giving the price in commodity B of one unit of
-     commodity A.
+     commodity, giving the price in commodity B of one unit of commodity
+     A.
 
    These two market price directives say that one euro was worth 1.35 US
 dollars during 2009, and $1.40 from 2010 onward:
 
-
 P 2009/1/1 € $1.35
 P 2010/1/1 € $1.40
 
-   The `-V', `-X' and `--value' flags use these market prices to show
-amount values in another commodity. See Valuation.
+   The '-V', '-X' and '--value' flags use these market prices to show
+amount values in another commodity.  See Valuation.
 
 
 File: hledger.info,  Node: Declaring accounts,  Next: Rewriting accounts,  Prev: Declaring market prices,  Up: JOURNAL FORMAT
@@ -5826,33 +5538,27 @@ File: hledger.info,  Node: Declaring accounts,  Next: Rewriting accounts,  Prev:
 12.23 Declaring accounts
 ========================
 
-`account' directives can be used to declare accounts (ie, the places
-that amounts are transferred from and to). Though not required, these
+'account' directives can be used to declare accounts (ie, the places
+that amounts are transferred from and to).  Though not required, these
 declarations can provide several benefits:
 
    * They can document your intended chart of accounts, providing a
      reference.
-
    * They can help hledger know your accounts' types (asset, liability,
      equity, revenue, expense), useful for reports like balancesheet and
      incomestatement.
-
    * They control account display order in reports, allowing
      non-alphabetic sorting (eg Revenues to appear above Expenses).
-
    * They can store extra information about accounts (account numbers,
      notes, etc.)
-
    * They help with account name completion in the add command,
      hledger-iadd, hledger-web, ledger-mode etc.
-
    * In strict mode, they restrict which accounts may be posted to by
      transactions, which helps detect typos.
 
-   The simplest form is just the word `account' followed by a
+   The simplest form is just the word 'account' followed by a
 hledger-style account name, eg this account directive declares the
-`assets:bank:checking' account:
-
+'assets:bank:checking' account:
 
 account assets:bank:checking
 
@@ -5871,27 +5577,24 @@ File: hledger.info,  Node: Account error checking,  Next: Account comments,  Up:
 ------------------------------
 
 By default, accounts come into existence when a transaction references
-them by name. This is convenient, but it means hledger can't warn you
-when you mis-spell an account name in the journal. Usually you'll find
+them by name.  This is convenient, but it means hledger can't warn you
+when you mis-spell an account name in the journal.  Usually you'll find
 the error later, as an extra account in balance reports, or an incorrect
 balance when reconciling.
 
-   In strict mode, enabled with the `-s'/`--strict' flag, hledger will
+   In strict mode, enabled with the '-s'/'--strict' flag, hledger will
 report an error if any transaction uses an account name that has not
-been declared by an account directive. Some notes:
+been declared by an account directive.  Some notes:
 
    * The declaration is case-sensitive; transactions must use the
      correct account name capitalisation.
-
    * The account directive's scope is "whole file and below" (see
-     directives). This means it affects all of the current file, and any
-     files it includes, but not parent or sibling files. The position of
-     account directives within the file does not matter, though it's
-     usual to put them at the top.
-
-   * Accounts can only be declared in `journal' files (but will affect
+     directives).  This means it affects all of the current file, and
+     any files it includes, but not parent or sibling files.  The
+     position of account directives within the file does not matter,
+     though it's usual to put them at the top.
+   * Accounts can only be declared in 'journal' files (but will affect
      included files in other formats).
-
    * It's currently not possible to declare "all possible subaccounts"
      with a wildcard; every account posted to must be declared.
 
@@ -5905,12 +5608,10 @@ Comments, beginning with a semicolon, can be added:
 
    * on the same line, *after two or more spaces* (because ; is allowed
      in account names)
-
    * on the next lines, indented
 
    An example of both:
 
-
 account assets:bank:checking  ; same-line comment, note 2+ spaces before ;
   ; next-line comment
   ; another with tag, acctno:12345 (not used yet)
@@ -5926,13 +5627,11 @@ File: hledger.info,  Node: Account subdirectives,  Next: Account types,  Prev: A
 We also allow (and ignore) Ledger-style indented subdirectives, just for
 compatibility.:
 
-
 account assets:bank:checking
   format blah blah  ; <- subdirective, ignored
 
    Here is the full syntax of account directives:
 
-
 account ACCTNAME  [ACCTTYPE] [;COMMENT]
   [;COMMENTS]
   [LEDGER-STYLE SUBDIRECTIVES, IGNORED]
@@ -5946,16 +5645,16 @@ File: hledger.info,  Node: Account types,  Next: Account display order,  Prev: A
 hledger recognises five main types of account, corresponding to the
 account classes in the accounting equation:
 
-   `Asset', `Liability', `Equity', `Revenue', `Expense'.
+   'Asset', 'Liability', 'Equity', 'Revenue', 'Expense'.
 
    These account types are important for controlling which accounts
 appear in the balancesheet, balancesheetequity, incomestatement reports
 (and probably for other things in future).
 
-   Additionally, we recognise the `Cash' type, which is also an
-`Asset', and which causes accounts to appear in the cashflow report.
-("Cash" here means liquid assets, eg bank balances but typically not
-investments or receivables.)
+   Additionally, we recognise the 'Cash' type, which is also an 'Asset',
+and which causes accounts to appear in the cashflow report.  ("Cash"
+here means liquid assets, eg bank balances but typically not investments
+or receivables.)
 
 * Menu:
 
@@ -5971,14 +5670,13 @@ File: hledger.info,  Node: Declaring account types,  Next: Auto-detected account
 .................................
 
 Generally, to make these reports work you should declare your top-level
-accounts and their types, using account directives with `type:' tags.
+accounts and their types, using account directives with 'type:' tags.
 
-   The tag's value should be one of: `Asset', `Liability', `Equity',
-`Revenue', `Expense', `Cash', `A', `L', `E', `R', `X', `C' (all case
+   The tag's value should be one of: 'Asset', 'Liability', 'Equity',
+'Revenue', 'Expense', 'Cash', 'A', 'L', 'E', 'R', 'X', 'C' (all case
 insensitive).  The type is inherited by all subaccounts except where
 they override it.  Here's a complete example:
 
-
 account assets       ; type: Asset
 account assets:bank  ; type: Cash
 account assets:cash  ; type: Cash
@@ -5997,19 +5695,19 @@ If you happen to use common english top-level account names, you may not
 need to declare account types, as they will be detected automatically
 using the following rules:
 
-If name matches this regular expression:   account type
-                                           is:
---------------------------------------------------------- 
-`^assets?(:|$)'                            `Asset'
-`^(debts?|liabilit(y|ies))(:|$)'           `Liability'
-`^equity(:|$)'                             `Equity'
-`^(income|revenue)s?(:|$)'                 `Revenue'
-`^expenses?(:|$)'                          `Expense'
+If name matches this regular expression:   account
+                                           type is:
+---------------------------------------------------------
+'^assets?(:|$)'                            'Asset'
+'^(debts?|liabilit(y|ies))(:|$)'           'Liability'
+'^equity(:|$)'                             'Equity'
+'^(income|revenue)s?(:|$)'                 'Revenue'
+'^expenses?(:|$)'                          'Expense'
 
-If account type is `Asset' and name does not contain this   account type
-regular expression:                                         is:
--------------------------------------------------------------------------- 
-`(investment|receivable|:A/R|:fixed)'                       `Cash'
+If account type is 'Asset' and name does not contain this   account
+regular expression:                                         type is:
+--------------------------------------------------------------------------
+'(investment|receivable|:A/R|:fixed)'                       'Cash'
 
    Even so, explicit declarations may be a good idea, for clarity and
 predictability.
@@ -6023,10 +5721,9 @@ File: hledger.info,  Node: Interference from auto-detected account types,  Next:
 If you assign any account type, it's a good idea to assign all of them,
 to prevent any confusion from mixing declared and auto-detected types.
 Although it's unlikely to happen in real life, here's an example: with
-the following journal, `balancesheetequity' shows "liabilities" in both
-Liabilities and Equity sections. Declaring another account as
-`type:Liability' would fix it:
-
+the following journal, 'balancesheetequity' shows "liabilities" in both
+Liabilities and Equity sections.  Declaring another account as
+'type:Liability' would fix it:
 
 account liabilities  ; type:Equity
 
@@ -6045,7 +5742,6 @@ In some hledger journals you might instead see this old syntax (the
 letters ALERX, separated from the account name by two or more spaces);
 this is deprecated and may be removed soon:
 
-
 account assets       A
 account liabilities  L
 account equity       E
@@ -6060,10 +5756,9 @@ File: hledger.info,  Node: Account display order,  Prev: Account types,  Up: Dec
 
 Account directives also set the order in which accounts are displayed,
 eg in reports, the hledger-ui accounts screen, and the hledger-web
-sidebar. By default accounts are listed in alphabetical order. But if
+sidebar.  By default accounts are listed in alphabetical order.  But if
 you have these account directives in the journal:
 
-
 account assets
 account liabilities
 account equity
@@ -6073,7 +5768,6 @@ account expenses
    you'll see those accounts displayed in declaration order, not
 alphabetically:
 
-
 $ hledger accounts -1
 assets
 liabilities
@@ -6085,22 +5779,20 @@ expenses
 order.
 
    Note that sorting is done at each level of the account tree (within
-each group of sibling accounts under the same parent). And currently,
+each group of sibling accounts under the same parent).  And currently,
 this directive:
 
-
 account other:zoo
 
-   would influence the position of `zoo' among `other''s subaccounts,
-but not the position of `other' among the top-level accounts. This
+   would influence the position of 'zoo' among 'other''s subaccounts,
+but not the position of 'other' among the top-level accounts.  This
 means:
 
-   * you will sometimes declare parent accounts (eg `account other'
+   * you will sometimes declare parent accounts (eg 'account other'
      above) that you don't intend to post to, just to customize their
      display order
-
-   * sibling accounts stay together (you couldn't display `x:y' in
-     between `a:b' and `a:c').
+   * sibling accounts stay together (you couldn't display 'x:y' in
+     between 'a:b' and 'a:c').
 
 
 File: hledger.info,  Node: Rewriting accounts,  Next: Default parent account,  Prev: Declaring accounts,  Up: JOURNAL FORMAT
@@ -6109,16 +5801,13 @@ File: hledger.info,  Node: Rewriting accounts,  Next: Default parent account,  P
 ========================
 
 You can define account alias rules which rewrite your account names, or
-parts of them, before generating reports. This can be useful for:
+parts of them, before generating reports.  This can be useful for:
 
    * expanding shorthand account names to their full form, allowing
      easier data entry and a less verbose journal
-
    * adapting old journals to your current chart of accounts
-
    * experimenting with new account organisations, like a new hierarchy
      or combining two accounts into one
-
    * customising reports
 
    Account aliases also rewrite account names in account directives.
@@ -6141,21 +5830,20 @@ File: hledger.info,  Node: Basic aliases,  Next: Regex aliases,  Up: Rewriting a
 12.24.1 Basic aliases
 ---------------------
 
-To set an account alias, use the `alias' directive in your journal
-file. This affects all subsequent journal entries in the current file or
-its included files. The spaces around the = are optional:
-
+To set an account alias, use the 'alias' directive in your journal file.
+This affects all subsequent journal entries in the current file or its
+included files (but note: not sibling or parent files).  The spaces
+around the = are optional:
 
 alias OLD = NEW
 
-   Or, you can use the `--alias 'OLD=NEW'' option on the command line.
-This affects all entries. It's useful for trying out aliases
+   Or, you can use the '--alias 'OLD=NEW'' option on the command line.
+This affects all entries.  It's useful for trying out aliases
 interactively.
 
-   OLD and NEW are case sensitive full account names. hledger will
+   OLD and NEW are case sensitive full account names.  hledger will
 replace any occurrence of the old account name with the new one.
-Subaccounts are also affected. Eg:
-
+Subaccounts are also affected.  Eg:
 
 alias checking = assets:bank:wells fargo:checking
 ; rewrites "checking" to "assets:bank:wells fargo:checking", or "checking:a" to "assets:bank:wells fargo:checking:a"
@@ -6169,17 +5857,15 @@ File: hledger.info,  Node: Regex aliases,  Next: Combining aliases,  Prev: Basic
 There is also a more powerful variant that uses a regular expression,
 indicated by the forward slashes:
 
-
 alias /REGEX/ = REPLACEMENT
 
-   or `--alias '/REGEX/=REPLACEMENT''.
+   or '--alias '/REGEX/=REPLACEMENT''.
 
-   REGEX is a case-insensitive regular expression. Anywhere it matches
+   REGEX is a case-insensitive regular expression.  Anywhere it matches
 inside an account name, the matched part will be replaced by
 REPLACEMENT. If REGEX contains parenthesised match groups, these can be
 referenced by the usual numeric backreferences in REPLACEMENT. Eg:
 
-
 alias /^(.+):bank:([^:]+):(.*)/ = \1:\2 \3
 ; rewrites "assets:bank:wells fargo:checking" to  "assets:wells fargo checking"
 
@@ -6197,34 +5883,31 @@ You can define as many aliases as you like, using journal directives
 and/or command line options.
 
    Recursive aliases - where an account name is rewritten by one alias,
-then by another alias, and so on - are allowed. Each alias sees the
+then by another alias, and so on - are allowed.  Each alias sees the
 effect of previously applied aliases.
 
    In such cases it can be important to understand which aliases will be
-applied and in which order. For (each account name in) each journal
+applied and in which order.  For (each account name in) each journal
 entry, we apply:
 
-  1. `alias' directives preceding the journal entry, most recently
+  1. 'alias' directives preceding the journal entry, most recently
      parsed first (ie, reading upward from the journal entry, bottom to
      top)
-
-  2. `--alias' options, in the order they appeared on the command line
+  2. '--alias' options, in the order they appeared on the command line
      (left to right).
 
    In other words, for (an account name in) a given journal entry:
 
    * the nearest alias declaration before/above the entry is applied
      first
-
    * the next alias before/above that will be be applied next, and so on
-
    * aliases defined after/below the entry do not affect it.
 
    This gives nearby aliases precedence over distant ones, and helps
 provide semantic stability - aliases will keep working the same way
 independent of which files are being read and in which order.
 
-   In case of trouble, adding `--debug=6' to the command line will show
+   In case of trouble, adding '--debug=6' to the command line will show
 which aliases are being applied when.
 
 
@@ -6233,16 +5916,14 @@ File: hledger.info,  Node: Aliases and multiple files,  Next: end aliases,  Prev
 12.24.4 Aliases and multiple files
 ----------------------------------
 
-As explained at Directives and multiple files, `alias' directives do
-not affect parent or sibling files. Eg in this command,
-
+As explained at Directives and multiple files, 'alias' directives do not
+affect parent or sibling files.  Eg in this command,
 
 hledger -f a.aliases -f b.journal
 
    account aliases defined in a.aliases will not affect b.journal.
 Including the aliases doesn't work either:
 
-
 include a.aliases
 
 2020-01-01  ; not affected by a.aliases
@@ -6252,7 +5933,6 @@ include a.aliases
    This means that account aliases should usually be declared at the
 start of your top-most file, like this:
 
-
 alias foo=Foo
 alias bar=Bar
 
@@ -6265,13 +5945,12 @@ include c.journal  ; also affected
 
 File: hledger.info,  Node: end aliases,  Prev: Aliases and multiple files,  Up: Rewriting accounts
 
-12.24.5 `end aliases'
+12.24.5 'end aliases'
 ---------------------
 
-You can clear (forget) all currently defined aliases with the `end
+You can clear (forget) all currently defined aliases with the 'end
 aliases' directive:
 
-
 end aliases
 
 
@@ -6281,10 +5960,9 @@ File: hledger.info,  Node: Default parent account,  Next: Periodic transactions,
 ============================
 
 You can specify a parent account which will be prepended to all accounts
-within a section of the journal. Use the `apply account' and `end apply
+within a section of the journal.  Use the 'apply account' and 'end apply
 account' directives like so:
 
-
 apply account home
 
 2010/1/1
@@ -6295,14 +5973,12 @@ end apply account
 
    which is equivalent to:
 
-
 2010/01/01
     home:food           $10
     home:cash          $-10
 
-   If `end apply account' is omitted, the effect lasts to the end of
-the file. Included files are also affected, eg:
-
+   If 'end apply account' is omitted, the effect lasts to the end of the
+file.  Included files are also affected, eg:
 
 apply account business
 include biz.journal
@@ -6310,13 +5986,13 @@ end apply account
 apply account personal
 include personal.journal
 
-   Prior to hledger 1.0, legacy `account' and `end' spellings were also
+   Prior to hledger 1.0, legacy 'account' and 'end' spellings were also
 supported.
 
-   A default parent account also affects account directives. It does not
-affect account names being entered via hledger add or hledger-web. If
-account aliases are present, they are applied after the default parent
-account.
+   A default parent account also affects account directives.  It does
+not affect account names being entered via hledger add or hledger-web.
+If account aliases are present, they are applied after the default
+parent account.
 
 
 File: hledger.info,  Node: Periodic transactions,  Next: Auto postings,  Prev: Default parent account,  Up: JOURNAL FORMAT
@@ -6324,7 +6000,7 @@ File: hledger.info,  Node: Periodic transactions,  Next: Auto postings,  Prev: D
 12.26 Periodic transactions
 ===========================
 
-Periodic transaction rules describe transactions that recur. They allow
+Periodic transaction rules describe transactions that recur.  They allow
 hledger to generate temporary future transactions to help with
 forecasting, so you don't have to write out each one in the journal, and
 it's easy to try out different forecasts.
@@ -6334,30 +6010,24 @@ read this whole section - or at least these tips:
 
   1. Two spaces accidentally added or omitted will cause you trouble -
      read about this below.
-
-  2. For troubleshooting, show the generated transactions with `hledger
-     print --forecast tag:generated' or `hledger register --forecast
+  2. For troubleshooting, show the generated transactions with 'hledger
+     print --forecast tag:generated' or 'hledger register --forecast
      tag:generated'.
-
   3. Forecasted transactions will begin only after the last
      non-forecasted transaction's date.
-
   4. Forecasted transactions will end 6 months from today, by default.
      See below for the exact start/end rules.
-
-  5. period expressions can be tricky. Their documentation needs
+  5. period expressions can be tricky.  Their documentation needs
      improvement, but is worth studying.
-
   6. Some period expressions with a repeating interval must begin on a
-     natural boundary of that interval. Eg in `weekly from DATE', DATE
-     must be a monday. `~ weekly from 2019/10/1' (a tuesday) will give
+     natural boundary of that interval.  Eg in 'weekly from DATE', DATE
+     must be a monday.  '~ weekly from 2019/10/1' (a tuesday) will give
      an error.
-
   7. Other period expressions with an interval are automatically
-     expanded to cover a whole number of that interval. (This is done
+     expanded to cover a whole number of that interval.  (This is done
      to improve reports, but it also affects periodic transactions.
-     Yes, it's a bit inconsistent with the above.) Eg: `~ every 10th
-     day of month from 2020/01', which is equivalent to `~ every 10th
+     Yes, it's a bit inconsistent with the above.)  Eg: '~ every 10th
+     day of month from 2020/01', which is equivalent to '~ every 10th
      day of month from 2020/01/01', will be adjusted to start on
      2019/12/10.
 
@@ -6378,20 +6048,19 @@ File: hledger.info,  Node: Periodic rule syntax,  Next: Two spaces between perio
 ----------------------------
 
 A periodic transaction rule looks like a normal journal entry, with the
-date replaced by a tilde (`~') followed by a period expression
-(mnemonic: `~' looks like a recurring sine wave.):
-
+date replaced by a tilde ('~') followed by a period expression
+(mnemonic: '~' looks like a recurring sine wave.):
 
 ~ monthly
     expenses:rent          $2000
     assets:bank:checking
 
    There is an additional constraint on the period expression: the start
-date must fall on a natural boundary of the interval. Eg `monthly from
-2018/1/1' is valid, but `monthly from 2018/1/15' is not.
+date must fall on a natural boundary of the interval.  Eg 'monthly from
+2018/1/1' is valid, but 'monthly from 2018/1/15' is not.
 
    Partial or relative dates (M/D, D, tomorrow, last week) in the period
-expression can work (useful or not). They will be relative to today's
+expression can work (useful or not).  They will be relative to today's
 date, unless a Y default year directive is in effect, in which case they
 will be relative to Y/1/1.
 
@@ -6402,11 +6071,10 @@ File: hledger.info,  Node: Two spaces between period expression and description!
 -------------------------------------------------------------
 
 If the period expression is followed by a transaction description, these
-must be separated by *two or more spaces*. This helps hledger know
+must be separated by *two or more spaces*.  This helps hledger know
 where the period expression ends, so that descriptions can not
 accidentally alter their meaning, as in this example:
 
-
 ; 2 or more spaces needed here, so the period is not understood as "every 2 months in 2020"
 ;               ||
 ;               vv
@@ -6418,7 +6086,6 @@ accidentally alter their meaning, as in this example:
 
    * Do write two spaces between your period expression and your
      transaction description, if any.
-
    * Don't accidentally write two spaces in the middle of your period
      expression.
 
@@ -6428,26 +6095,25 @@ File: hledger.info,  Node: Forecasting with periodic transactions,  Next: Budget
 12.26.3 Forecasting with periodic transactions
 ----------------------------------------------
 
-The `--forecast' flag activates any periodic transaction rules in the
-journal. They will generate temporary recurring transactions, which are
+The '--forecast' flag activates any periodic transaction rules in the
+journal.  They will generate temporary recurring transactions, which are
 not saved in the journal, but will appear in all reports (eg print).
 This can be useful for estimating balances into the future, or
-experimenting with different scenarios. Or, it can be used as a data
+experimenting with different scenarios.  Or, it can be used as a data
 entry aid: describe recurring transactions, and every so often copy the
-output of `print --forecast' into the journal.
+output of 'print --forecast' into the journal.
 
    These transactions will have an extra tag indicating which periodic
-rule generated them: `generated-transaction:~ PERIODICEXPR'. And a
+rule generated them: 'generated-transaction:~ PERIODICEXPR'.  And a
 similar, hidden tag (beginning with an underscore) which, because it's
 never displayed by print, can be used to match transactions generated
-"just now": `_generated-transaction:~ PERIODICEXPR'.
+"just now": '_generated-transaction:~ PERIODICEXPR'.
 
-   Periodic transactions are generated within some forecast period. By
+   Periodic transactions are generated within some forecast period.  By
 default, this
 
    * begins on the later of
         * the report start date if specified with -b/-p/date:
-
         * the day after the latest normal (non-periodic) transaction in
           the journal, or today if there are no normal transactions.
 
@@ -6455,19 +6121,19 @@ default, this
      months (180 days) from today.
 
    This means that periodic transactions will begin only after the
-latest recorded transaction. And a recorded transaction dated in the
-future can prevent generation of periodic transactions. (You can avoid
+latest recorded transaction.  And a recorded transaction dated in the
+future can prevent generation of periodic transactions.  (You can avoid
 that by writing the future transaction as a one-time periodic rule
-instead - put tilde before the date, eg `~ YYYY-MM-DD ...').
+instead - put tilde before the date, eg '~ YYYY-MM-DD ...').
 
    Or, you can set your own arbitrary "forecast period", which can
 overlap recorded transactions, and need not be in the future, by
-providing an option argument, like `--forecast=PERIODEXPR'. Note the
-equals sign is required, a space won't work. PERIODEXPR is a period
-expression, which can specify the start date, end date, or both, like
-in a `date:' query. (See also hledger.1 -> Report start & end date).
-Some examples: `--forecast=202001-202004', `--forecast=jan-',
-`--forecast=2020'.
+providing an option argument, like '--forecast=PERIODEXPR'.  Note the
+equals sign is required, a space won't work.  PERIODEXPR is a period
+expression, which can specify the start date, end date, or both, like in
+a 'date:' query.  (See also hledger.1 -> Report start & end date).  Some
+examples: '--forecast=202001-202004', '--forecast=jan-',
+'--forecast=2020'.
 
 
 File: hledger.info,  Node: Budgeting with periodic transactions,  Prev: Forecasting with periodic transactions,  Up: Periodic transactions
@@ -6475,12 +6141,12 @@ File: hledger.info,  Node: Budgeting with periodic transactions,  Prev: Forecast
 12.26.4 Budgeting with periodic transactions
 --------------------------------------------
 
-With the `--budget' flag, currently supported by the balance command,
+With the '--budget' flag, currently supported by the balance command,
 each periodic transaction rule declares recurring budget goals for the
-specified accounts. Eg the first example above declares a goal of
+specified accounts.  Eg the first example above declares a goal of
 spending $2000 on rent (and also, a goal of depositing $2000 into
-checking) every month. Goals and actual performance can then be compared
-in budget reports.
+checking) every month.  Goals and actual performance can then be
+compared in budget reports.
 
    See also: Budgeting and Forecasting.
 
@@ -6492,46 +6158,40 @@ File: hledger.info,  Node: Auto postings,  Prev: Periodic transactions,  Up: JOU
 
 "Automated postings" or "auto postings" are extra postings which get
 added automatically to transactions which match certain queries, defined
-by "auto posting rules", when you use the `--auto' flag.
+by "auto posting rules", when you use the '--auto' flag.
 
    An auto posting rule looks a bit like a transaction:
 
-
 = QUERY
     ACCOUNT  AMOUNT
     ...
     ACCOUNT  [AMOUNT]
 
-   except the first line is an equals sign (mnemonic: `=' suggests
+   except the first line is an equals sign (mnemonic: '=' suggests
 matching), followed by a query (which matches existing postings), and
 each "posting" line describes a posting to be generated, and the posting
 amounts can be:
 
-   * a normal amount with a commodity symbol, eg `$2'. This will be used
-     as-is.
-
-   * a number, eg `2'. The commodity symbol (if any) from the matched
+   * a normal amount with a commodity symbol, eg '$2'.  This will be
+     used as-is.
+   * a number, eg '2'.  The commodity symbol (if any) from the matched
      posting will be added to this.
-
-   * a numeric multiplier, eg `*2' (a star followed by a number N). The
+   * a numeric multiplier, eg '*2' (a star followed by a number N). The
      matched posting's amount (and total price, if any) will be
      multiplied by N.
-
-   * a multiplier with a commodity symbol, eg `*$2' (a star, number N,
+   * a multiplier with a commodity symbol, eg '*$2' (a star, number N,
      and symbol S). The matched posting's amount will be multiplied by
      N, and its commodity symbol will be replaced with S.
 
    Any query term containing spaces must be enclosed in single or double
-quotes, as on the command line. Eg, note the quotes around the second
+quotes, as on the command line.  Eg, note the quotes around the second
 query term below:
 
-
 = expenses:groceries 'expenses:dining out'
     (budget:funds:dining out)                 *-1
 
    Some examples:
 
-
 ; every time I buy food, schedule a dollar donation
 = expenses:food
     (liabilities:charity)   $-1
@@ -6549,7 +6209,6 @@ query term below:
   expenses:gifts   $20
   assets:checking
 
-
 $ hledger print --auto
 2017-12-01
     expenses:food              $10
@@ -6576,8 +6235,8 @@ File: hledger.info,  Node: Auto postings and multiple files,  Next: Auto posting
 ----------------------------------------
 
 An auto posting rule can affect any transaction in the current file, or
-in any parent file or child file. Note, currently it will not affect
-sibling files (when multiple `-f'/`--file' are used - see #1212).
+in any parent file or child file.  Note, currently it will not affect
+sibling files (when multiple '-f'/'--file' are used - see #1212).
 
 
 File: hledger.info,  Node: Auto postings and dates,  Next: Auto postings and transaction balancing / inferred amounts / balance assertions,  Prev: Auto postings and multiple files,  Up: Auto postings
@@ -6595,17 +6254,14 @@ File: hledger.info,  Node: Auto postings and transaction balancing / inferred am
 12.27.3 Auto postings and transaction balancing / inferred amounts /
 --------------------------------------------------------------------
 
-balance assertions
-
-   Currently, auto postings are added:
+balance assertions Currently, auto postings are added:
 
    * after missing amounts are inferred, and transactions are checked
      for balancedness,
-
    * but before balance assertions are checked.
 
    Note this means that journal entries must be balanced both before and
-after auto postings are added. This changed in hledger 1.12+; see #893
+after auto postings are added.  This changed in hledger 1.12+; see #893
 for background.
 
 
@@ -6616,20 +6272,18 @@ File: hledger.info,  Node: Auto posting tags,  Prev: Auto postings and transacti
 
 Automated postings will have some extra tags:
 
-   * `generated-posting:= QUERY' - shows this was generated by an auto
+   * 'generated-posting:= QUERY' - shows this was generated by an auto
      posting rule, and the query
-
-   * `_generated-posting:= QUERY' - a hidden tag, which does not appear
-     in hledger's output. This can be used to match postings generated
+   * '_generated-posting:= QUERY' - a hidden tag, which does not appear
+     in hledger's output.  This can be used to match postings generated
      "just now", rather than generated in the past and saved to the
      journal.
 
    Also, any transaction that has been changed by auto posting rules
 will have these tags added:
 
-   * `modified:' - this transaction was modified
-
-   * `_modified:' - a hidden tag not appearing in the comment; this
+   * 'modified:' - this transaction was modified
+   * '_modified:' - a hidden tag not appearing in the comment; this
      transaction was modified "just now".
 
 
@@ -6647,44 +6301,44 @@ transaction.
 
    (To learn about _writing_ CSV, see CSV output.)
 
-   We describe each CSV file's format with a corresponding _rules
-file_. By default this is named like the CSV file with a `.rules'
-extension added. Eg when reading `FILE.csv', hledger also looks for
-`FILE.csv.rules' in the same directory as `FILE.csv'. You can specify a
-different rules file with the `--rules-file' option. If a rules file is
-not found, hledger will create a sample rules file, which you'll need
-to adjust.
+   We describe each CSV file's format with a corresponding _rules file_.
+By default this is named like the CSV file with a '.rules' extension
+added.  Eg when reading 'FILE.csv', hledger also looks for
+'FILE.csv.rules' in the same directory as 'FILE.csv'.  You can specify a
+different rules file with the '--rules-file' option.  If a rules file is
+not found, hledger will create a sample rules file, which you'll need to
+adjust.
 
    This file contains rules describing the CSV data (header line, fields
 layout, date format etc.), and how to construct hledger journal entries
-(transactions) from it. Often there will also be a list of conditional
-rules for categorising transactions based on their descriptions. Here's
+(transactions) from it.  Often there will also be a list of conditional
+rules for categorising transactions based on their descriptions.  Here's
 an overview of the CSV rules; these are described more fully below,
 after the examples:
 
-*`skip'*                        skip one or more header lines or matched
-                                CSV records
-*`fields'*                      name CSV fields, assign them to hledger
+*'skip'*                        skip one or more header lines or
+                                matched CSV records
+*'fields'*                      name CSV fields, assign them to hledger
                                 fields
 *field assignment*              assign a value to one hledger field,
                                 with interpolation
-*`separator'*                   a custom field separator
-*`if' block*                    apply some rules to CSV records matched
+*'separator'*                   a custom field separator
+*'if' block*                    apply some rules to CSV records matched
                                 by patterns
-*`if' table*                    apply some rules to CSV records matched
+*'if' table*                    apply some rules to CSV records matched
                                 by patterns, alternate syntax
-*`end'*                         skip the remaining CSV records
-*`date-format'*                 how to parse dates in CSV records
-*`decimal-mark'*                the decimal mark used in CSV amounts, if
-                                ambiguous
-*`newest-first'*                disambiguate record order when there's
+*'end'*                         skip the remaining CSV records
+*'date-format'*                 how to parse dates in CSV records
+*'decimal-mark'*                the decimal mark used in CSV amounts,
+                                if ambiguous
+*'newest-first'*                disambiguate record order when there's
                                 only one date
-*`include'*                     inline another CSV rules file
-*`balance-type'*                choose which type of balance assignments
-                                to use
+*'include'*                     inline another CSV rules file
+*'balance-type'*                choose which type of balance
+                                assignments to use
 
-   Note, for best error messages when reading CSV files, use a `.csv',
-`.tsv' or `.ssv' file extension or file prefix - see File Extension
+   Note, for best error messages when reading CSV files, use a '.csv',
+'.tsv' or '.ssv' file extension or file prefix - see File Extension
 below.
 
    There's an introductory Convert CSV files tutorial on hledger.org.
@@ -6701,7 +6355,7 @@ File: hledger.info,  Node: Examples,  Next: CSV rules,  Up: CSV FORMAT
 13.1 Examples
 =============
 
-Here are some sample hledger CSV rules files. See also the full
+Here are some sample hledger CSV rules files.  See also the full
 collection at:
 https://github.com/simonmichael/hledger/tree/master/examples/csv
 
@@ -6720,19 +6374,16 @@ File: hledger.info,  Node: Basic,  Next: Bank of Ireland,  Up: Examples
 
 At minimum, the rules file must identify the date and amount fields, and
 often it also specifies the date format and how many header lines there
-are. Here's a simple CSV file and a rules file for it:
-
+are.  Here's a simple CSV file and a rules file for it:
 
 Date, Description, Id, Amount
 12/11/2019, Foo, 123, 10.23
 
-
 # basic.csv.rules
 skip         1
 fields       date, description, _, amount
 date-format  %d/%m/%Y
 
-
 $ hledger print -f basic.csv
 2019-11-12 Foo
     expenses:unknown           10.23
@@ -6750,12 +6401,10 @@ Here's a CSV with two amount fields (Debit and Credit), and a balance
 field, which we can use to add balance assertions, which is not
 necessary but provides extra error checking:
 
-
 Date,Details,Debit,Credit,Balance
 07/12/2012,LODGMENT       529898,,10.0,131.21
 07/12/2012,PAYMENT,5,,126
 
-
 # bankofireland-checking.csv.rules
 
 # skip the header line
@@ -6782,7 +6431,6 @@ currency  EUR
 # set the base account for all txns
 account1  assets:bank:boi:checking
 
-
 $ hledger -f bankofireland-checking.csv print
 2012-12-07 LODGMENT       529898
     assets:bank:boi:checking         EUR10.0 = EUR131.2
@@ -6803,15 +6451,13 @@ File: hledger.info,  Node: Amazon,  Next: Paypal,  Prev: Bank of Ireland,  Up: E
 -------------
 
 Here we convert amazon.com order history, and use an if block to
-generate a third posting if there's a fee. (In practice you'd probably
+generate a third posting if there's a fee.  (In practice you'd probably
 get this data from your bank instead, but it's an example.)
 
-
 "Date","Type","To/From","Name","Status","Amount","Fees","Transaction ID"
 "Jul 29, 2012","Payment","To","Foo.","Completed","$20.00","$0.00","16000000000000DGLNJPI1P9B8DKPVHL"
 "Jul 30, 2012","Payment","To","Adapteva, Inc.","Completed","$25.00","$1.00","17LA58JSKRD4HDGLNJPI1P9B8DKPVHL"
 
-
 # amazon-orders.csv.rules
 
 # skip one header line
@@ -6846,7 +6492,6 @@ if %fees [1-9]
  account3    expenses:fees
  amount3     %fees
 
-
 $ hledger -f amazon-orders.csv print
 2012-07-29 (16000000000000DGLNJPI1P9B8DKPVHL) To Foo.  ; status:Completed
     assets:amazon
@@ -6866,7 +6511,6 @@ File: hledger.info,  Node: Paypal,  Prev: Amazon,  Up: Examples
 Here's a real-world rules file for (customised) Paypal CSV, with some
 Paypal-specific rules, and a second rules file included:
 
-
 "Date","Time","TimeZone","Name","Type","Status","Currency","Gross","Fee","Net","From Email Address","To Email Address","Transaction ID","Item Title","Item ID","Reference Txn ID","Receipt ID","Balance","Note"
 "10/01/2019","03:46:20","PDT","Calm Radio","Subscription Payment","Completed","USD","-6.99","0.00","-6.99","simon@joyful.com","memberships@calmradio.com","60P57143A8206782E","MONTHLY - $1 for the first 2 Months: Me - Order 99309. Item total: $1.00 USD first 2 months, then $6.99 / Month","","I-R8YLY094FJYR","","-6.99",""
 "10/01/2019","03:46:20","PDT","","Bank Deposit to PP Account ","Pending","USD","6.99","0.00","6.99","","simon@joyful.com","0TU1544T080463733","","","60P57143A8206782E","","0.00",""
@@ -6876,7 +6520,6 @@ Paypal-specific rules, and a second rules file included:
 "10/19/2019","03:02:12","PDT","","Bank Deposit to PP Account ","Pending","USD","2.00","0.00","2.00","","simon@joyful.com","3XJ107139A851061F","","","K9U43044RY432050M","","0.00",""
 "10/22/2019","05:07:06","PDT","Noble Benefactor","Subscription Payment","Completed","USD","10.00","-0.59","9.41","noble@bene.fac.tor","simon@joyful.com","6L8L1662YP1334033","Joyful Systems","","I-KC9VBGY2GWDB","","9.41",""
 
-
 # paypal-custom.csv.rules
 
 # Tips:
@@ -6959,7 +6602,6 @@ Bank Deposit to PP Account
 if Currency Conversion
  account2 equity:currency conversion
 
-
 # common.rules
 
 if
@@ -6983,7 +6625,6 @@ if Google
  account2 expenses:online:apps
  description google | music
 
-
 $ hledger -f paypal-custom.csv  print
 2019-10-01 (60P57143A8206782E) Calm Radio MONTHLY - $1 for the first 2 Months: Me - Order 99309. Item total: $1.00 USD first 2 months, then $6.99 / Month  ; itemid:, fromemail:simon@joyful.com, toemail:memberships@calmradio.com, time:03:46:20, type:Subscription Payment, status:Completed
     assets:online:paypal          $-6.99 = $-6.99
@@ -7022,7 +6663,7 @@ File: hledger.info,  Node: CSV rules,  Next: Tips,  Prev: Examples,  Up: CSV FOR
 ==============
 
 The following kinds of rule can appear in the rules file, in any order.
-Blank lines and lines beginning with `#' or `;' are ignored.
+Blank lines and lines beginning with '#' or ';' are ignored.
 
 * Menu:
 
@@ -7042,16 +6683,15 @@ Blank lines and lines beginning with `#' or `;' are ignored.
 
 File: hledger.info,  Node: skip,  Next: fields,  Up: CSV rules
 
-13.2.1 `skip'
+13.2.1 'skip'
 -------------
 
-
 skip N
 
-The word "skip" followed by a number (or no number, meaning 1) tells
+   The word "skip" followed by a number (or no number, meaning 1) tells
 hledger to ignore this many non-empty lines preceding the CSV data.
-(Empty/blank lines are skipped automatically.) You'll need this whenever
-your CSV data contains header lines.
+(Empty/blank lines are skipped automatically.)  You'll need this
+whenever your CSV data contains header lines.
 
    It also has a second purpose: it can be used inside if blocks to
 ignore certain CSV records (described below).
@@ -7059,38 +6699,35 @@ ignore certain CSV records (described below).
 
 File: hledger.info,  Node: fields,  Next: field assignment,  Prev: skip,  Up: CSV rules
 
-13.2.2 `fields'
+13.2.2 'fields'
 ---------------
 
-
 fields FIELDNAME1, FIELDNAME2, ...
 
-A fields list (the word "fields" followed by comma-separated field
-names) is the quick way to assign CSV field values to hledger fields. It
-does two things:
+   A fields list (the word "fields" followed by comma-separated field
+names) is the quick way to assign CSV field values to hledger fields.
+It does two things:
 
-  1. it names the CSV fields. This is optional, but can be convenient
+  1. it names the CSV fields.  This is optional, but can be convenient
      later for interpolating them.
 
   2. when you use a standard hledger field name, it assigns the CSV
      value to that part of the hledger transaction.
 
-
    Here's an example that says "use the 1st, 2nd and 4th fields as the
 transaction's date, description and amount; name the last two fields for
 later reference; and ignore the others":
 
-
 fields date, description, , amount, , , somefield, anotherfield
 
-   Field names may not contain whitespace. Fields you don't care about
-can be left unnamed. Currently there must be least two items (there
+   Field names may not contain whitespace.  Fields you don't care about
+can be left unnamed.  Currently there must be least two items (there
 must be at least one comma).
 
    Note, always use comma in the fields list, even if your CSV uses
 another separator character.
 
-   Here are the standard hledger field/pseudo-field names. For more
+   Here are the standard hledger field/pseudo-field names.  For more
 about the transaction parts they refer to, see the manual for hledger's
 journal format.
 
@@ -7105,7 +6742,7 @@ File: hledger.info,  Node: Transaction field names,  Next: Posting field names,
 13.2.2.1 Transaction field names
 ................................
 
-`date', `date2', `status', `code', `description', `comment' can be used
+'date', 'date2', 'status', 'code', 'description', 'comment' can be used
 to form the transaction's first line.
 
 
@@ -7114,48 +6751,52 @@ File: hledger.info,  Node: Posting field names,  Prev: Transaction field names,
 13.2.2.2 Posting field names
 ............................
 
-account `accountN', where N is 1 to 99, causes a posting to be
+account 'accountN', where N is 1 to 99, causes a posting to be
 generated, with that account name.
 
-   Most often there are two postings, so you'll want to set `account1'
-and `account2'. Typically `account1' is associated with the CSV file,
-and is set once with a top-level assignment, while `account2' is set
+   Most often there are two postings, so you'll want to set 'account1'
+and 'account2'.  Typically 'account1' is associated with the CSV file,
+and is set once with a top-level assignment, while 'account2' is set
 based on each transaction's description, and in conditional blocks.
 
    If a posting's account name is left unset but its amount is set (see
 below), a default account name will be chosen (like "expenses:unknown"
-or "income:unknown").  amount `amountN' sets posting N's amount. If the
-CSV uses separate fields for inflows and outflows, you can use
-`amountN-in' and `amountN-out' instead. By assigning to `amount1',
-`amount2', ... etc. you can generate anywhere from 0 to 99 postings.
+or "income:unknown").  amount 'amountN' sets the Nth posting's amount.
+By assigning to 'amount1', 'amount2', ...  etc.  you can generate up to
+99 postings.
 
-   There is also an older, unnumbered form of these names, suitable for
-2-posting transactions, which sets both posting 1's and (negated)
-posting 2's amount: `amount', or `amount-in' and `amount-out'. This is
-still supported because it keeps pre-hledger-1.17 csv rules files
-working, and because it can be more succinct, and because it converts
-posting 2's amount to cost if there's a transaction price, which can be
-useful.
+   If the CSV uses separate fields for debits and credits (inflows and
+outflows), you can use 'amountN-in' and 'amountN-out' instead.  Note
+hledger assumes both of these fields are unsigned, and will
+automatically negate the "-out" value.  If the fields are signed, see
+"Setting amounts" below.
+
+   There is also an unnumbered form of these names: 'amount', or
+'amount-in' and 'amount-out'.  This is supported to keep
+pre-hledger-1.17 CSV rules files working (and for occasional
+convenience).  It is suitable only for two-posting transactions; it sets
+both posting 1's and posting 2's amount.  Posting 2's amount will be
+negated, and also converted to cost if there's a transaction price.
 
    If you have an existing rules file using the unnumbered form, you
 might want to use the numbered form in certain conditional blocks,
-without having to update and retest all the old rules. To facilitate
-this, posting 1 ignores `amount'/`amount-in'/`amount-out' if any of
-`amount1'/`amount1-in'/`amount1-out' are assigned, and posting 2
-ignores them if any of `amount2'/`amount2-in'/`amount2-out' are
-assigned, avoiding conflicts.  currency If the CSV has the currency
-symbol in a separate field (ie, not part of the amount field), you can
-use `currencyN' to prepend it to posting N's amount. Or, `currency'
-with no number affects all postings.  balance `balanceN' sets a balance
+without having to update and retest all the old rules.  To facilitate
+this, posting 1 ignores 'amount'/'amount-in'/'amount-out' if any of
+'amount1'/'amount1-in'/'amount1-out' are assigned, and posting 2 ignores
+them if any of 'amount2'/'amount2-in'/'amount2-out' are assigned,
+avoiding conflicts.  currency If the CSV has the currency symbol in a
+separate field (ie, not part of the amount field), you can use
+'currencyN' to prepend it to posting N's amount.  Or, 'currency' with no
+number affects all postings.  balance 'balanceN' sets a balance
 assertion amount (or if the posting amount is left empty, a balance
 assignment) on posting N.
 
-   Also, for compatibility with hledger <1.17: `balance' with no number
-is equivalent to `balance1'.
+   Also, for compatibility with hledger <1.17: 'balance' with no number
+is equivalent to 'balance1'.
 
    You can adjust the type of assertion/assignment with the
-`balance-type' rule (see below).  comment Finally, `commentN' sets a
-comment on the Nth posting. Comments can also contain tags, as usual.
+'balance-type' rule (see below).  comment Finally, 'commentN' sets a
+comment on the Nth posting.  Comments can also contain tags, as usual.
 
    See TIPS below for more about setting amounts and currency.
 
@@ -7165,16 +6806,14 @@ File: hledger.info,  Node: field assignment,  Next: separator,  Prev: fields,  U
 13.2.3 field assignment
 -----------------------
 
-
 HLEDGERFIELDNAME FIELDVALUE
 
-Instead of or in addition to a fields list, you can use a "field
+   Instead of or in addition to a fields list, you can use a "field
 assignment" rule to set the value of a single hledger field, by writing
 its name (any of the standard hledger field names above) followed by a
-text value. The value may contain interpolated CSV fields, referenced by
-their 1-based position in the CSV record (`%N'), or by the name they
-were given in the fields list (`%CSVFIELDNAME'). Some examples:
-
+text value.  The value may contain interpolated CSV fields, referenced
+by their 1-based position in the CSV record ('%N'), or by the name they
+were given in the fields list ('%CSVFIELDNAME').  Some examples:
 
 # set the amount to the 4th CSV field, with " USD" appended
 amount %4 USD
@@ -7182,45 +6821,41 @@ amount %4 USD
 # combine three fields to make a comment, containing note: and date: tags
 comment note: %somefield - %anotherfield, date: %1
 
-   Interpolation strips outer whitespace (so a CSV value like `" 1 "'
-becomes `1' when interpolated) (#1051). See TIPS below for more about
+   Interpolation strips outer whitespace (so a CSV value like '" 1 "'
+becomes '1' when interpolated) (#1051).  See TIPS below for more about
 referencing other fields.
 
 
 File: hledger.info,  Node: separator,  Next: if block,  Prev: field assignment,  Up: CSV rules
 
-13.2.4 `separator'
+13.2.4 'separator'
 ------------------
 
-You can use the `separator' rule to read other kinds of
-character-separated data. The argument is any single separator
-character, or the words `tab' or `space' (case insensitive).  Eg, for
+You can use the 'separator' rule to read other kinds of
+character-separated data.  The argument is any single separator
+character, or the words 'tab' or 'space' (case insensitive).  Eg, for
 comma-separated values (CSV):
 
-
 separator ,
 
    or for semicolon-separated values (SSV):
 
-
 separator ;
 
    or for tab-separated values (TSV):
 
-
 separator TAB
 
-   If the input file has a `.csv', `.ssv' or `.tsv' file extension (or
-a `csv:', `ssv:', `tsv:' prefix), the appropriate separator will be
+   If the input file has a '.csv', '.ssv' or '.tsv' file extension (or a
+'csv:', 'ssv:', 'tsv:' prefix), the appropriate separator will be
 inferred automatically, and you won't need this rule.
 
 
 File: hledger.info,  Node: if block,  Next: if table,  Prev: separator,  Up: CSV rules
 
-13.2.5 `if' block
+13.2.5 'if' block
 -----------------
 
-
 if MATCHER
  RULE
 
@@ -7231,9 +6866,10 @@ MATCHER
  RULE
  RULE
 
-Conditional blocks ("if blocks") are a block of rules that are applied
-only to CSV records which match certain patterns. They are often used
-for customising account names based on transaction descriptions.
+   Conditional blocks ("if blocks") are a block of rules that are
+applied only to CSV records which match certain patterns.  They are
+often used for customising account names based on transaction
+descriptions.
 
 * Menu:
 
@@ -7250,21 +6886,20 @@ File: hledger.info,  Node: Matching the whole record,  Next: Matching individual
 
 Each MATCHER can be a record matcher, which looks like this:
 
-
 REGEX
 
    REGEX is a case-insensitive regular expression that tries to match
-anywhere within the CSV record. It is a POSIX ERE (extended regular
-expression) that also supports GNU word boundaries (`\b', `\B', `\<',
-`\>'), and nothing else. If you have trouble, be sure to check our doc:
+anywhere within the CSV record.  It is a POSIX ERE (extended regular
+expression) that also supports GNU word boundaries ('\b', '\B', '\<',
+'\>'), and nothing else.  If you have trouble, be sure to check our doc:
 https://hledger.org/hledger.html#regular-expressions
 
    Important note: the record that is matched is not the original
 record, but a synthetic one, with any enclosing double quotes (but not
 enclosing whitespace) removed, and always comma-separated (which means
-that a field containing a comma will appear like two fields). Eg, if the
-original record is `2020-01-01; "Acme, Inc.";  1,000', the REGEX will
-actually see `2020-01-01,Acme, Inc.,  1,000').
+that a field containing a comma will appear like two fields).  Eg, if
+the original record is '2020-01-01; "Acme, Inc."; 1,000', the REGEX will
+actually see '2020-01-01,Acme, Inc., 1,000').
 
 
 File: hledger.info,  Node: Matching individual fields,  Next: Combining matchers,  Prev: Matching the whole record,  Up: if block
@@ -7274,12 +6909,11 @@ File: hledger.info,  Node: Matching individual fields,  Next: Combining matchers
 
 Or, MATCHER can be a field matcher, like this:
 
-
 %CSVFIELD REGEX
 
-   which matches just the content of a particular CSV field. CSVFIELD
+   which matches just the content of a particular CSV field.  CSVFIELD
 is a percent sign followed by the field's name or column number, like
-`%date' or `%1'.
+'%date' or '%1'.
 
 
 File: hledger.info,  Node: Combining matchers,  Next: Rules applied on successful match,  Prev: Matching individual fields,  Up: if block
@@ -7290,10 +6924,9 @@ File: hledger.info,  Node: Combining matchers,  Next: Rules applied on successfu
 A single matcher can be written on the same line as the "if"; or
 multiple matchers can be written on the following lines, non-indented.
 Multiple matchers are OR'd (any one of them can match), unless one
-begins with an `&' symbol, in which case it is AND'ed with the previous
+begins with an '&' symbol, in which case it is AND'ed with the previous
 matcher.
 
-
 if
 MATCHER
 & MATCHER
@@ -7306,23 +6939,19 @@ File: hledger.info,  Node: Rules applied on successful match,  Prev: Combining m
 ..........................................
 
 After the patterns there should be one or more rules to apply, all
-indented by at least one space. Three kinds of rule are allowed in
+indented by at least one space.  Three kinds of rule are allowed in
 conditional blocks:
 
    * field assignments (to set a hledger field)
-
    * skip (to skip the matched CSV record)
-
    * end (to skip all remaining CSV records).
 
    Examples:
 
-
 # if the CSV record contains "groceries", set account2 to "expenses:groceries"
 if groceries
  account2 expenses:groceries
 
-
 # if the CSV record contains any of these patterns, set account2 and comment as shown
 if
 monthly service fee
@@ -7334,28 +6963,26 @@ banking thru software
 
 File: hledger.info,  Node: if table,  Next: end,  Prev: if block,  Up: CSV rules
 
-13.2.6 `if' table
+13.2.6 'if' table
 -----------------
 
-
 if,CSVFIELDNAME1,CSVFIELDNAME2,...,CSVFIELDNAMEn
 MATCHER1,VALUE11,VALUE12,...,VALUE1n
 MATCHER2,VALUE21,VALUE22,...,VALUE2n
 MATCHER3,VALUE31,VALUE32,...,VALUE3n
 <empty line>
 
-Conditional tables ("if tables") are a different syntax to specify field
-assignments that will be applied only to CSV records which match certain
-patterns.
+   Conditional tables ("if tables") are a different syntax to specify
+field assignments that will be applied only to CSV records which match
+certain patterns.
 
    MATCHER could be either field or record matcher, as described above.
 When MATCHER matches, values from that row would be assigned to the CSV
-fields named on the `if' line, in the same order.
+fields named on the 'if' line, in the same order.
 
-   Therefore `if' table is exactly equivalent to a sequence of of `if'
+   Therefore 'if' table is exactly equivalent to a sequence of of 'if'
 blocks:
 
-
 if MATCHER1
   CSVFIELDNAME1 VALUE11
   CSVFIELDNAME2 VALUE12
@@ -7378,18 +7005,17 @@ if MATCHER3
 empty) values for all the listed fields.
 
    Rules would be checked and applied in the order they are listed in
-the table and, like with `if' blocks, later rules (in the same or
-another table) or `if' blocks could override the effect of any rule.
+the table and, like with 'if' blocks, later rules (in the same or
+another table) or 'if' blocks could override the effect of any rule.
 
    Instead of ',' you can use a variety of other non-alphanumeric
-characters as a separator. First character after `if' is taken to be
-the separator for the rest of the table. It is the responsibility of
+characters as a separator.  First character after 'if' is taken to be
+the separator for the rest of the table.  It is the responsibility of
 the user to ensure that separator does not occur inside MATCHERs and
 values - there is no way to escape separator.
 
    Example:
 
-
 if,account2,comment
 atm transaction fee,expenses:business:banking,deductible? check it
 %description groceries,expenses:groceries,
@@ -7398,13 +7024,12 @@ atm transaction fee,expenses:business:banking,deductible? check it
 
 File: hledger.info,  Node: end,  Next: date-format,  Prev: if table,  Up: CSV rules
 
-13.2.7 `end'
+13.2.7 'end'
 ------------
 
 This rule can be used inside if blocks (only), to make hledger stop
 reading this CSV file and move on to the next input file, or to command
-execution. Eg:
-
+execution.  Eg:
 
 # ignore everything following the first empty record
 if ,,,,
@@ -7413,32 +7038,27 @@ if ,,,,
 
 File: hledger.info,  Node: date-format,  Next: decimal-mark,  Prev: end,  Up: CSV rules
 
-13.2.8 `date-format'
+13.2.8 'date-format'
 --------------------
 
-
 date-format DATEFMT
 
-This is a helper for the `date' (and `date2') fields. If your CSV dates
-are not formatted like `YYYY-MM-DD', `YYYY/MM/DD' or `YYYY.MM.DD',
+   This is a helper for the 'date' (and 'date2') fields.  If your CSV
+dates are not formatted like 'YYYY-MM-DD', 'YYYY/MM/DD' or 'YYYY.MM.DD',
 you'll need to add a date-format rule describing them with a strptime
 date parsing pattern, which must parse the CSV date value completely.
 Some examples:
 
-
 # MM/DD/YY
 date-format %m/%d/%y
 
-
 # D/M/YYYY
 # The - makes leading zeros optional.
 date-format %-d/%-m/%Y
 
-
 # YYYY-Mmm-DD
 date-format %Y-%h-%d
 
-
 # M/D/YYYY HH:MM AM some other junk
 # Note the time and junk must be fully parsed, though only the date is used.
 date-format %-m/%-d/%Y %l:%M %p some other junk
@@ -7449,19 +7069,17 @@ https://hackage.haskell.org/package/time/docs/Data-Time-Format.html#v:formatTime
 
 File: hledger.info,  Node: decimal-mark,  Next: newest-first,  Prev: date-format,  Up: CSV rules
 
-13.2.9 `decimal-mark'
+13.2.9 'decimal-mark'
 ---------------------
 
-
 decimal-mark .
 
-or:
-
+   or:
 
 decimal-mark ,
 
    hledger automatically accepts either period or comma as a decimal
-mark when parsing numbers (cf Amounts). However if any numbers in the
+mark when parsing numbers (cf Amounts).  However if any numbers in the
 CSV contain digit group marks, such as thousand-separating commas, you
 should declare the decimal mark explicitly with this rule, to avoid
 misparsed numbers.
@@ -7469,24 +7087,21 @@ misparsed numbers.
 
 File: hledger.info,  Node: newest-first,  Next: include,  Prev: decimal-mark,  Up: CSV rules
 
-13.2.10 `newest-first'
+13.2.10 'newest-first'
 ----------------------
 
-hledger always sorts the generated transactions by date. Transactions on
-the same date should appear in the same order as their CSV records, as
-hledger can usually auto-detect whether the CSV's normal order is oldest
-first or newest first. But if all of the following are true:
+hledger always sorts the generated transactions by date.  Transactions
+on the same date should appear in the same order as their CSV records,
+as hledger can usually auto-detect whether the CSV's normal order is
+oldest first or newest first.  But if all of the following are true:
 
    * the CSV might sometimes contain just one day of data (all records
      having the same date)
-
-   * the CSV records are normally in reverse chronological order
-     (newest at the top)
-
+   * the CSV records are normally in reverse chronological order (newest
+     at the top)
    * and you care about preserving the order of same-day transactions
 
-   then, you should add the `newest-first' rule as a hint. Eg:
-
+   then, you should add the 'newest-first' rule as a hint.  Eg:
 
 # tell hledger explicitly that the CSV is normally newest first
 newest-first
@@ -7494,18 +7109,16 @@ newest-first
 
 File: hledger.info,  Node: include,  Next: balance-type,  Prev: newest-first,  Up: CSV rules
 
-13.2.11 `include'
+13.2.11 'include'
 -----------------
 
-
 include RULESFILE
 
-This includes the contents of another CSV rules file at this point.
-`RULESFILE' is an absolute file path or a path relative to the current
-file's directory. This can be useful for sharing common rules between
+   This includes the contents of another CSV rules file at this point.
+'RULESFILE' is an absolute file path or a path relative to the current
+file's directory.  This can be useful for sharing common rules between
 several rules files, eg:
 
-
 # someaccount.csv.rules
 
 ## someaccount-specific rules
@@ -7519,23 +7132,21 @@ include categorisation.rules
 
 File: hledger.info,  Node: balance-type,  Prev: include,  Up: CSV rules
 
-13.2.12 `balance-type'
+13.2.12 'balance-type'
 ----------------------
 
 Balance assertions generated by assigning to balanceN are of the simple
-`=' type by default, which is a single-commodity, subaccount-excluding
-assertion. You may find the subaccount-including variants more useful,
-eg if you have created some virtual subaccounts of checking to help
-with budgeting. You can select a different type of assertion with the
-`balance-type' rule:
-
+'=' type by default, which is a single-commodity, subaccount-excluding
+assertion.  You may find the subaccount-including variants more useful,
+eg if you have created some virtual subaccounts of checking to help with
+budgeting.  You can select a different type of assertion with the
+'balance-type' rule:
 
 # balance assertions will consider all commodities and all subaccounts
 balance-type ==*
 
    Here are the balance assertion types for quick reference:
 
-
 =    single commodity, exclude subaccounts
 =*   single commodity, include subaccounts
 ==   multi commodity,  exclude subaccounts
@@ -7569,16 +7180,15 @@ File: hledger.info,  Node: Rapid feedback,  Next: Valid CSV,  Up: Tips
 ---------------------
 
 It's a good idea to get rapid feedback while creating/troubleshooting
-CSV rules. Here's a good way, using entr from
+CSV rules.  Here's a good way, using entr from
 http://eradman.com/entrproject :
 
-
 $ ls foo.csv* | entr bash -c 'echo ----; hledger -f foo.csv print desc:SOMEDESC'
 
-   A desc: query (eg) is used to select just one, or a few,
-transactions of interest. "bash -c" is used to run multiple commands,
-so we can echo a separator each time the command re-runs, making it
-easier to read the output.
+   A desc: query (eg) is used to select just one, or a few, transactions
+of interest.  "bash -c" is used to run multiple commands, so we can echo
+a separator each time the command re-runs, making it easier to read the
+output.
 
 
 File: hledger.info,  Node: Valid CSV,  Next: File Extension,  Prev: Rapid feedback,  Up: Tips
@@ -7586,11 +7196,10 @@ File: hledger.info,  Node: Valid CSV,  Next: File Extension,  Prev: Rapid feedba
 13.3.2 Valid CSV
 ----------------
 
-hledger accepts CSV conforming to RFC 4180. When CSV values are enclosed
-in quotes, note:
+hledger accepts CSV conforming to RFC 4180.  When CSV values are
+enclosed in quotes, note:
 
    * they must be double quotes (not single quotes)
-
    * spaces outside the quotes are not allowed
 
 
@@ -7600,16 +7209,14 @@ File: hledger.info,  Node: File Extension,  Next: Reading multiple CSV files,  P
 ---------------------
 
 To help hledger identify the format and show the right error messages,
-CSV/SSV/TSV files should normally be named with a `.csv', `.ssv' or
-`.tsv' filename extension. Or, the file path should be prefixed with
-`csv:', `ssv:' or `tsv:'. Eg:
-
+CSV/SSV/TSV files should normally be named with a '.csv', '.ssv' or
+'.tsv' filename extension.  Or, the file path should be prefixed with
+'csv:', 'ssv:' or 'tsv:'.  Eg:
 
 $ hledger -f foo.ssv print
 
    or:
 
-
 $ cat foo | hledger -f ssv:- foo
 
    You can override the file extension with a separator rule if needed.
@@ -7621,9 +7228,9 @@ File: hledger.info,  Node: Reading multiple CSV files,  Next: Valid transactions
 13.3.4 Reading multiple CSV files
 ---------------------------------
 
-If you use multiple `-f' options to read multiple CSV files at once,
+If you use multiple '-f' options to read multiple CSV files at once,
 hledger will look for a correspondingly-named rules file for each CSV
-file. But if you use the `--rules-file' option, that rules file will be
+file.  But if you use the '--rules-file' option, that rules file will be
 used for all the CSV files.
 
 
@@ -7640,10 +7247,9 @@ the problem entry.
 
    There is one exception: balance assertions, if you have generated
 them, will not be checked, since normally these will work only when the
-CSV data is part of the main journal. If you do need to check balance
+CSV data is part of the main journal.  If you do need to check balance
 assertions generated from CSV right away, pipe into another hledger:
 
-
 $ hledger -f file.csv print | hledger -f- print
 
 
@@ -7657,25 +7263,23 @@ transactions, the new file may overlap with the old one, containing some
 of the same records.
 
    The import command will (a) detect the new transactions, and (b)
-append just those transactions to your main journal. It is idempotent,
+append just those transactions to your main journal.  It is idempotent,
 so you don't have to remember how many times you ran it or with which
-version of the CSV. (It keeps state in a hidden `.latest.FILE.csv'
-file.)  This is the easiest way to import CSV data. Eg:
-
+version of the CSV. (It keeps state in a hidden '.latest.FILE.csv'
+file.)  This is the easiest way to import CSV data.  Eg:
 
 # download the latest CSV files, then run this command.
 # Note, no -f flags needed here.
 $ hledger import *.csv [--dry]
 
-   This method works for most CSV files. (Where records have a stable
+   This method works for most CSV files.  (Where records have a stable
 chronological order, and new records appear only at the new end.)
 
    A number of other tools and workflows, hledger-specific and
-otherwise, exist for converting, deduplicating, classifying and
-managing CSV data.  See:
+otherwise, exist for converting, deduplicating, classifying and managing
+CSV data.  See:
 
    * https://hledger.org -> sidebar -> real world setups
-
    * https://plaintextaccounting.org -> data import/conversion
 
 
@@ -7689,67 +7293,66 @@ Some tips on using the amount-setting rules discussed above.
    Here are the ways to set a posting's amount:
 
   1. *If the CSV has a single amount field:*
-     Assign (via a fields list or a field assignment) to `amountN'. This
-     sets the Nth posting's amount. N is usually 1 or 2 but can go up
-     to 99.
+     Assign (via a fields list or a field assignment) to 'amountN'.
+     This sets the Nth posting's amount.  N is usually 1 or 2 but can go
+     up to 99.
 
-  2. *If the CSV has separate Debit and Credit amount fields:*
-     Assign to `amountN-in' and `amountN-out'. This sets posting N's
-     amount to whichever of these has a non-zero value, guessing an
-     appropriate sign.
+  2. *If the CSV has separate amount fields for debit & credit (in &
+     out):*
 
-        * *If hledger guesses the wrong sign:*
-          Prepend a minus sign to flip it. Eg:
+       a. *If both fields are unsigned:*
+          Assign to 'amountN-in' and 'amountN-out'.  This sets posting
+          N's amount to whichever of these has a non-zero value, and
+          negates the "-out" value.
 
+       b. *If either field is signed (can contain a minus sign):*
+          Use a conditional rule to flip the sign (of non-empty values).
+          Since hledger always negates amountN-out, if it was already
+          negative, we must undo that by negating once more (but only if
+          the field is non-empty):
 
-          fields date, description, amount-in, amount-out
-          amount-out -%amount-out
+     fields date, description, amount1-in, amount1-out
+     if %amount1-out [1-9]
+      amount1-out -%amount1-out
 
-        * *If both fields contain a non-zero value:*
-          The `amountN-in'/`amountN-out' rules require that each CSV
-          record has a non-zero value in exactly one of the two fields,
-          so that hledger knows which to choose. So these would all be
-          rejected:
+       c. *If both fields, or neither field, can contain a non-zero
+          value:*
+          hledger normally expects exactly one of the fields to have a
+          non-zero value.  Eg, the 'amountN-in'/'amountN-out' rules
+          would reject value pairs like these:
 
+     "",  ""
+     "0", "0"
+     "1", "none"
 
-          "",  ""
-          "0", "0"
-          "1", "none"
+     So, use smarter conditional rules to set the amount from the
+     appropriate field.  Eg, these rules would make it use only the
+     value containing non-zero digits, handling the above:
 
-          If your CSV has amount values like this, use conditional
-          rules instead.  For example, to make hledger to choose the
-          value containing non-zero digits:
+     fields date, description, in, out
+     if %in [1-9]
+      amount1 %in
+     if %out [1-9]
+      amount1 %out
 
-
-          fields date, description, in, out
-          if %in [1-9]
-           amount1 %in
-          if %out [1-9]
-           amount1 %out
-
-
-  3. *Using the old numberless syntax:*
-     Assign to `amount' (or to `amount-in' and `amount-out').  This
-     sets posting 1's and posting 2's amounts (and converts posting 2's
-     amount to cost). This is supported for backwards compatibility (and
-     occasional convenience).
+  3. *If you are stuck with hledger <1.17, or you want posting 2's
+     amount converted to cost:*
+     Assign to 'amount' (or to 'amount-in' and 'amount-out').  (The old
+     numberless syntax, which sets amount1 and amount2.)
 
   4. *If the CSV has the balance instead of the transaction amount:*
-     Assign to `balanceN', which sets posting N's amount indirectly via
-     a balance assignment. (Old syntax: `balance', equivalent to
-     `balance1'.)
+     Assign to 'balanceN', which sets posting N's amount indirectly via
+     a balance assignment.  (Old syntax: 'balance', equivalent to
+     'balance1'.)
 
         * *If hledger guesses the wrong default account name:*
           When setting the amount via balance assertion, hledger may
-          guess the wrong default account name. So, set the account
+          guess the wrong default account name.  So, set the account
           name explicitly, eg:
 
-
           fields date, description, balance1
           account1 assets:checking
 
-
-
 
 File: hledger.info,  Node: Amount signs,  Next: Setting currency/commodity,  Prev: Setting amounts,  Up: Tips
 
@@ -7760,22 +7363,21 @@ There is some special handling for amount signs, to simplify parsing and
 sign-flipping:
 
    * *If an amount value begins with a plus sign:*
-     that will be removed: `+AMT' becomes `AMT'
+     that will be removed: '+AMT' becomes 'AMT'
 
    * *If an amount value is parenthesised:*
-     it will be de-parenthesised and sign-flipped: `(AMT)' becomes
-     `-AMT'
+     it will be de-parenthesised and sign-flipped: '(AMT)' becomes
+     '-AMT'
 
    * *If an amount value has two minus signs (or two sets of
      parentheses, or a minus sign and parentheses):*
-     they cancel out and will be removed: `--AMT' or `-(AMT)' becomes
-     `AMT'
+     they cancel out and will be removed: '--AMT' or '-(AMT)' becomes
+     'AMT'
 
    * *If an amount value contains just a sign (or just a set of
      parentheses):*
-     that is removed, making it an empty value. `"+"' or `"-"' or
-     `"()"' becomes `""'.
-
+     that is removed, making it an empty value.  '"+"' or '"-"' or
+     '"()"' becomes '""'.
 
 
 File: hledger.info,  Node: Setting currency/commodity,  Next: Amount decimal places,  Prev: Amount signs,  Up: Tips
@@ -7786,51 +7388,43 @@ File: hledger.info,  Node: Setting currency/commodity,  Next: Amount decimal pla
 If the currency/commodity symbol is included in the CSV's amount
 field(s):
 
-
 2020-01-01,foo,$123.00
 
    you don't have to do anything special for the commodity symbol, it
-will be assigned as part of the amount. Eg:
-
+will be assigned as part of the amount.  Eg:
 
 fields date,description,amount
 
-
 2020-01-01 foo
     expenses:unknown         $123.00
     income:unknown          $-123.00
 
    If the currency is provided as a separate CSV field:
 
-
 2020-01-01,foo,USD,123.00
 
-   You can assign that to the `currency' pseudo-field, which has the
+   You can assign that to the 'currency' pseudo-field, which has the
 special effect of prepending itself to every amount in the transaction
 (on the left, with no separating space):
 
-
 fields date,description,currency,amount
 
-
 2020-01-01 foo
     expenses:unknown       USD123.00
     income:unknown        USD-123.00
 
    Or, you can use a field assignment to construct the amount yourself,
-with more control. Eg to put the symbol on the right, and separated by a
-space:
-
+with more control.  Eg to put the symbol on the right, and separated by
+a space:
 
 fields date,description,cur,amt
 amount %amt %cur
 
-
 2020-01-01 foo
     expenses:unknown        123.00 USD
     income:unknown         -123.00 USD
 
-   Note we used a temporary field name (`cur') that is not `currency' -
+   Note we used a temporary field name ('cur') that is not 'currency' -
 that would trigger the prepending effect, which we don't want here.
 
 
@@ -7840,7 +7434,7 @@ File: hledger.info,  Node: Amount decimal places,  Next: Referencing other field
 -----------------------------
 
 Like amounts in a journal file, the amounts generated by CSV rules like
-`amount1' influence commodity display styles, such as the number of
+'amount1' influence commodity display styles, such as the number of
 decimal places displayed in reports.
 
    The original amounts as written in the CSV file do not affect display
@@ -7853,11 +7447,10 @@ File: hledger.info,  Node: Referencing other fields,  Next: How CSV rules are ev
 --------------------------------
 
 In field assignments, you can interpolate only CSV fields, not hledger
-fields. In the example below, there's both a CSV field and a hledger
+fields.  In the example below, there's both a CSV field and a hledger
 field named amount1, but %amount1 always means the CSV field, not the
 hledger field:
 
-
 # Name the third CSV field "amount1"
 fields date,description,amount1
 
@@ -7870,16 +7463,14 @@ comment %amount1
    Here, since there's no CSV amount1 field, %amount1 will produce a
 literal "amount1":
 
-
 fields date,description,csvamount
 amount1 %csvamount USD
 # Can't interpolate amount1 here
 comment %amount1
 
    When there are multiple field assignments to the same hledger field,
-only the last one takes effect. Here, comment's value will be be B, or C
-if "something" is matched, but never A:
-
+only the last one takes effect.  Here, comment's value will be be B, or
+C if "something" is matched, but never A:
 
 comment A
 comment B
@@ -7893,43 +7484,37 @@ File: hledger.info,  Node: How CSV rules are evaluated,  Prev: Referencing other
 -----------------------------------
 
 Here's how to think of CSV rules being evaluated (if you really need
-to). First,
+to).  First,
 
-   * `include' - all includes are inlined, from top to bottom, depth
-     first. (At each include point the file is inlined and scanned for
+   * 'include' - all includes are inlined, from top to bottom, depth
+     first.  (At each include point the file is inlined and scanned for
      further includes, recursively, before proceeding.)
 
-   Then "global" rules are evaluated, top to bottom. If a rule is
+   Then "global" rules are evaluated, top to bottom.  If a rule is
 repeated, the last one wins:
 
-   * `skip' (at top level)
-
-   * `date-format'
-
-   * `newest-first'
-
-   * `fields' - names the CSV fields, optionally sets up initial
+   * 'skip' (at top level)
+   * 'date-format'
+   * 'newest-first'
+   * 'fields' - names the CSV fields, optionally sets up initial
      assignments to hledger fields
 
    Then for each CSV record in turn:
 
-   * test all `if' blocks. If any of them contain a `end' rule, skip
-     all remaining CSV records. Otherwise if any of them contain a
-     `skip' rule, skip that many CSV records. If there are multiple
-     matched `skip' rules, the first one wins.
-
-   * collect all field assignments at top level and in matched `if'
-     blocks. When there are multiple assignments for a field, keep only
+   * test all 'if' blocks.  If any of them contain a 'end' rule, skip
+     all remaining CSV records.  Otherwise if any of them contain a
+     'skip' rule, skip that many CSV records.  If there are multiple
+     matched 'skip' rules, the first one wins.
+   * collect all field assignments at top level and in matched 'if'
+     blocks.  When there are multiple assignments for a field, keep only
      the last one.
-
    * compute a value for each hledger field - either the one that was
      assigned to it (and interpolate the %CSVFIELDNAME references), or a
      default
-
    * generate a synthetic hledger transaction from these values.
 
    This is all part of the CSV reader, one of several readers hledger
-can use to parse input files. When all files have been read
+can use to parse input files.  When all files have been read
 successfully, the transactions are passed as input to whichever hledger
 command the user specified.
 
@@ -7941,24 +7526,22 @@ File: hledger.info,  Node: TIMECLOCK FORMAT,  Next: TIMEDOT FORMAT,  Prev: CSV F
 
 The time logging format of timeclock.el, as read by hledger.
 
-   hledger can read time logs in timeclock format. As with Ledger, these
-are (a subset of) timeclock.el's format, containing clock-in and
-clock-out entries as in the example below. The date is a simple date.
+   hledger can read time logs in timeclock format.  As with Ledger,
+these are (a subset of) timeclock.el's format, containing clock-in and
+clock-out entries as in the example below.  The date is a simple date.
 The time format is HH:MM[:SS][+-ZZZZ]. Seconds and timezone are
-optional. The timezone, if present, must be four digits and is ignored
+optional.  The timezone, if present, must be four digits and is ignored
 (currently the time is always interpreted as a local time).
 
-
 i 2015/03/30 09:00:00 some:account name  optional description after two spaces
 o 2015/03/30 09:20:00
 i 2015/03/31 22:21:45 another account
 o 2015/04/01 02:00:34
 
    hledger treats each clock-in/clock-out pair as a transaction posting
-some number of hours to an account. Or if the session spans more than
-one day, it is split into several transactions, one for each day. For
-the above time log, `hledger print' generates these journal entries:
-
+some number of hours to an account.  Or if the session spans more than
+one day, it is split into several transactions, one for each day.  For
+the above time log, 'hledger print' generates these journal entries:
 
 $ hledger -f t.timeclock print
 2015-03-30 * optional description after two spaces
@@ -7972,7 +7555,6 @@ $ hledger -f t.timeclock print
 
    Here is a sample.timeclock to download and some queries to try:
 
-
 $ hledger -f sample.timeclock balance                               # current time balances
 $ hledger -f sample.timeclock register -p 2009/3                    # sessions in march 2009
 $ hledger -f sample.timeclock register -p weekly --depth 1 --empty  # time summary by week
@@ -7982,15 +7564,14 @@ $ hledger -f sample.timeclock register -p weekly --depth 1 --empty  # time summa
    * use emacs and the built-in timeclock.el, or the extended
      timeclock-x.el and perhaps the extras in ledgerutils.el
 
-   * at the command line, use these bash aliases: `shell     alias
-     ti="echo i `date '+%Y-%m-%d %H:%M:%S'` \$* >>$TIMELOG"     alias
-     to="echo o `date '+%Y-%m-%d %H:%M:%S'` >>$TIMELOG"'
+   * at the command line, use these bash aliases: 'shell alias ti="echo
+     i `date '+%Y-%m-%d %H:%M:%S'` \$* >>$TIMELOG" alias to="echo o
+     `date '+%Y-%m-%d %H:%M:%S'` >>$TIMELOG"'
 
-   * or use the old `ti' and `to' scripts in the ledger 2.x repository.
+   * or use the old 'ti' and 'to' scripts in the ledger 2.x repository.
      These rely on a "timeclock" executable which I think is just the
      ledger 2 executable renamed.
 
-
 
 File: hledger.info,  Node: TIMEDOT FORMAT,  Next: COMMON TASKS,  Prev: TIMECLOCK FORMAT,  Up: Top
 
@@ -8000,61 +7581,58 @@ File: hledger.info,  Node: TIMEDOT FORMAT,  Next: COMMON TASKS,  Prev: TIMECLOCK
 hledger's human-friendly time logging format.
 
    Timedot is a plain text format for logging dated, categorised
-quantities (of time, usually), supported by hledger. It is convenient
+quantities (of time, usually), supported by hledger.  It is convenient
 for approximate and retroactive time logging, eg when the real-time
 clock-in/out required with a timeclock file is too precise or too
-interruptive. It can be formatted like a bar chart, making clear at a
+interruptive.  It can be formatted like a bar chart, making clear at a
 glance where time was spent.
 
    Though called "timedot", this format is read by hledger as
 commodityless quantities, so it could be used to represent dated
-quantities other than time. In the docs below we'll assume it's time.
+quantities other than time.  In the docs below we'll assume it's time.
 
-   A timedot file contains a series of day entries. A day entry begins
+   A timedot file contains a series of day entries.  A day entry begins
 with a non-indented hledger-style simple date (Y-M-D, Y/M/D, Y.M.D..)
 Any additional text on the same line is used as a transaction
 description for this day.
 
    This is followed by optionally-indented timelog items for that day,
-one per line. Each timelog item is a note, usually a
+one per line.  Each timelog item is a note, usually a
 hledger:style:account:name representing a time category, followed by two
-or more spaces, and a quantity. Each timelog item generates a hledger
+or more spaces, and a quantity.  Each timelog item generates a hledger
 transaction.
 
    Quantities can be written as:
 
-   * dots: a sequence of dots (.) representing quarter hours. Spaces may
-     optionally be used for grouping. Eg: .... ..
+   * dots: a sequence of dots (.)  representing quarter hours.  Spaces
+     may optionally be used for grouping.  Eg: ....  ..
 
-   * an integral or decimal number, representing hours. Eg: 1.5
+   * an integral or decimal number, representing hours.  Eg: 1.5
 
    * an integral or decimal number immediately followed by a unit symbol
-     `s', `m', `h', `d', `w', `mo', or `y', representing seconds,
-     minutes, hours, days weeks, months or years respectively. Eg: 90m.
+     's', 'm', 'h', 'd', 'w', 'mo', or 'y', representing seconds,
+     minutes, hours, days weeks, months or years respectively.  Eg: 90m.
      The following equivalencies are assumed, currently: 1m = 60s, 1h =
      60m, 1d = 24h, 1w = 7d, 1mo = 30d, 1y=365d.
 
-
    There is some flexibility allowing notes and todo lists to be kept
 right in the time log, if needed:
 
-   * Blank lines and lines beginning with `#' or `;' are ignored.
+   * Blank lines and lines beginning with '#' or ';' are ignored.
 
    * Lines not ending with a double-space and quantity are parsed as
      items taking no time, which will not appear in balance reports by
      default.  (Add -E to see them.)
 
-   * Org mode headlines (lines beginning with one or more `*' followed
+   * Org mode headlines (lines beginning with one or more '*' followed
      by a space) can be used as date lines or timelog items (the stars
-     are ignored). Also all org headlines before the first date line
+     are ignored).  Also all org headlines before the first date line
      are ignored.  This means org users can manage their timelog as an
      org outline (eg using org-mode/orgstruct-mode in Emacs), for
      organisation, faster navigation, controlling visibility etc.
 
-
    Examples:
 
-
 # on this day, 6h was spent on client work, 1.5h on haskell FOSS work, etc.
 2016/2/1
 inc:client1   .... .... .... .... .... ....
@@ -8065,19 +7643,16 @@ biz:research  .
 inc:client1   .... ....
 biz:research  .
 
-
 2016/2/3
 inc:client1   4
 fos:hledger   3
 biz:research  1
 
-
 * Time log
 ** 2020-01-01
 *** adm:time  .
 *** adm:finance  .
 
-
 * 2020 Work Diary
 ** Q1
 *** 2020-02-29
@@ -8096,7 +7671,6 @@ adm:planning: trip
 
    Reporting:
 
-
 $ hledger -f t.timedot print date:2016/2/2
 2016-02-02 *
     (inc:client1)          2.00
@@ -8104,31 +7678,28 @@ $ hledger -f t.timedot print date:2016/2/2
 2016-02-02 *
     (biz:research)          0.25
 
-
 $ hledger -f t.timedot bal --daily --tree
 Balance changes in 2016-02-01-2016-02-03:
 
-            ||  2016-02-01d  2016-02-02d  2016-02-03d
+            ||  2016-02-01d  2016-02-02d  2016-02-03d 
 ============++========================================
- biz        ||         0.25         0.25         1.00
-   research ||         0.25         0.25         1.00
- fos        ||         1.50            0         3.00
-   haskell  ||         1.50            0            0
-   hledger  ||            0            0         3.00
- inc        ||         6.00         2.00         4.00
-   client1  ||         6.00         2.00         4.00
+ biz        ||         0.25         0.25         1.00 
+   research ||         0.25         0.25         1.00 
+ fos        ||         1.50            0         3.00 
+   haskell  ||         1.50            0            0 
+   hledger  ||            0            0         3.00 
+ inc        ||         6.00         2.00         4.00 
+   client1  ||         6.00         2.00         4.00 
 ------------++----------------------------------------
-            ||         7.75         2.25         8.00
-
-   I prefer to use period for separating account components. We can make
-this work with an account alias:
+            ||         7.75         2.25         8.00 
 
+   I prefer to use period for separating account components.  We can
+make this work with an account alias:
 
 2016/2/4
 fos.hledger.timedot  4
 fos.ledger           ..
 
-
 $ hledger -f t.timedot --alias /\\./=: bal date:2016/2/4 --tree
                 4.50  fos
                 4.00    hledger:timedot
@@ -8166,7 +7737,6 @@ File: hledger.info,  Node: Getting help,  Next: Constructing command lines,  Up:
 16.1 Getting help
 =================
 
-
 $ hledger                 # show available commands
 $ hledger --help          # show common options
 $ hledger CMD --help      # show common and command options, and command help
@@ -8175,7 +7745,7 @@ $ hledger help hledger    # show hledger manual as info/man/text (auto-chosen)
 $ hledger help journal --man  # show the journal manual as a man page
 $ hledger help --help     # show more detailed help for the help command
 
-Find more docs, chat, mail list, reddit, issue tracker:
+   Find more docs, chat, mail list, reddit, issue tracker:
 https://hledger.org#help-feedback
 
 
@@ -8184,23 +7754,19 @@ File: hledger.info,  Node: Constructing command lines,  Next: Starting a journal
 16.2 Constructing command lines
 ===============================
 
-hledger has an extensive and powerful command line interface. We strive
+hledger has an extensive and powerful command line interface.  We strive
 to keep it simple and ergonomic, but you may run into one of the
-confusing real world details described in OPTIONS, below. If that
+confusing real world details described in OPTIONS, below.  If that
 happens, here are some tips that may help:
 
    * command-specific options must go after the command (it's fine to
-     put all options there) (`hledger CMD OPTS ARGS')
-
+     put all options there) ('hledger CMD OPTS ARGS')
    * running add-on executables directly simplifies command line parsing
-     (`hledger-ui OPTS ARGS')
-
+     ('hledger-ui OPTS ARGS')
    * enclose "problematic" args in single quotes
-
    * if needed, also add a backslash to hide regular expression
      metacharacters from the shell
-
-   * to see how a misbehaving command is being parsed, add `--debug=2'.
+   * to see how a misbehaving command is being parsed, add '--debug=2'.
 
 
 File: hledger.info,  Node: Starting a journal file,  Next: Setting opening balances,  Prev: Constructing command lines,  Up: COMMON TASKS
@@ -8209,19 +7775,17 @@ File: hledger.info,  Node: Starting a journal file,  Next: Setting opening balan
 ============================
 
 hledger looks for your accounting data in a journal file,
-`$HOME/.hledger.journal' by default:
-
+'$HOME/.hledger.journal' by default:
 
 $ hledger stats
 The hledger journal file "/Users/simon/.hledger.journal" was not found.
 Please create it first, eg with "hledger add" or a text editor.
 Or, specify an existing journal file with -f or LEDGER_FILE.
 
-   You can override this by setting the `LEDGER_FILE' environment
-variable. It's a good practice to keep this important file under version
-control, and to start a new file each year. So you could do something
-like this:
-
+   You can override this by setting the 'LEDGER_FILE' environment
+variable.  It's a good practice to keep this important file under
+version control, and to start a new file each year.  So you could do
+something like this:
 
 $ mkdir ~/finance
 $ cd ~/finance
@@ -8232,7 +7796,7 @@ $ echo "export LEDGER_FILE=$HOME/finance/2020.journal" >> ~/.bashrc
 $ source ~/.bashrc
 $ hledger stats
 Main file                : /Users/simon/finance/2020.journal
-Included files           :
+Included files           : 
 Transactions span        :  to  (0 days)
 Last transaction         : none
 Transactions             : 0 (0.0 per day)
@@ -8250,22 +7814,21 @@ File: hledger.info,  Node: Setting opening balances,  Next: Recording transactio
 =============================
 
 Pick a starting date for which you can look up the balances of some
-real-world assets (bank accounts, wallet..) and liabilities (credit
+real-world assets (bank accounts, wallet..)  and liabilities (credit
 cards..).
 
    To avoid a lot of data entry, you may want to start with just one or
 two accounts, like your checking account or cash wallet; and pick a
-recent starting date, like today or the start of the week. You can
+recent starting date, like today or the start of the week.  You can
 always come back later and add more accounts and older transactions, eg
 going back to january 1st.
 
    Add an opening balances transaction to the journal, declaring the
-balances on this date. Here are two ways to do it:
+balances on this date.  Here are two ways to do it:
 
    * The first way: open the journal in any text editor and save an
      entry like this:
 
-
      2020-01-01 * opening balances
          assets:bank:checking                $1000   = $1000
          assets:bank:savings                 $2000   = $2000
@@ -8276,7 +7839,7 @@ balances on this date. Here are two ways to do it:
      These are start-of-day balances, ie whatever was in the account at
      the end of the previous day.
 
-     The * after the date is an optional status flag. Here it means
+     The * after the date is an optional status flag.  Here it means
      "cleared & confirmed".
 
      The currency symbols are optional, but usually a good idea as
@@ -8285,10 +7848,9 @@ balances on this date. Here are two ways to do it:
      The = amounts are optional balance assertions, providing extra
      error checking.
 
-   * The second way: run `hledger add' and follow the prompts to record
+   * The second way: run 'hledger add' and follow the prompts to record
      a similar transaction:
 
-
      $ hledger add
      Adding transactions to journal file /Users/simon/finance/2020.journal
      Any command line arguments will be used as defaults.
@@ -8309,7 +7871,7 @@ balances on this date. Here are two ways to do it:
      Account 4: liabilities:creditcard
      Amount  4 [$-3100]: $-50
      Account 5: equity:opening/closing balances
-     Amount  5 [$-3050]:
+     Amount  5 [$-3050]: 
      Account 6 (or . or enter to finish this transaction): .
      2020-01-01 * opening balances
          assets:bank:checking                      $1000
@@ -8317,16 +7879,14 @@ balances on this date. Here are two ways to do it:
          assets:cash                                $100
          liabilities:creditcard                     $-50
          equity:opening/closing balances          $-3050
-
-     Save this transaction to the journal ? [y]:
+     
+     Save this transaction to the journal ? [y]: 
      Saved.
      Starting the next transaction (. or ctrl-D/ctrl-C to quit)
      Date [2020-01-01]: .
 
-
    If you're using version control, this could be a good time to commit
-the journal. Eg:
-
+the journal.  Eg:
 
 $ git commit -m 'initial balances' 2020.journal
 
@@ -8344,7 +7904,6 @@ convert CSV data downloaded from your bank.
    Here are some simple transactions, see the hledger_journal(5) manual
 and hledger.org for more ideas:
 
-
 2020/1/10 * gift received
   assets:cash   $20
   income:gifts
@@ -8367,52 +7926,49 @@ Periodically you should reconcile - compare your hledger-reported
 balances against external sources of truth, like bank statements or your
 bank's website - to be sure that your ledger accurately represents the
 real-world balances (and, that the real-world institutions have not made
-a mistake!). This gets easy and fast with (1) practice and (2)
-frequency. If you do it daily, it can take 2-10 minutes. If you let it
+a mistake!).  This gets easy and fast with (1) practice and (2)
+frequency.  If you do it daily, it can take 2-10 minutes.  If you let it
 pile up, expect it to take longer as you hunt down errors and
 discrepancies.
 
    A typical workflow:
 
-  1. Reconcile cash. Count what's in your wallet. Compare with what
-     hledger reports (`hledger bal cash'). If they are different, try to
-     remember the missing transaction, or look for the error in the
-     already-recorded transactions. A register report can be helpful
-     (`hledger reg cash'). If you can't find the error, add an
-     adjustment transaction. Eg if you have $105 after the above, and
+  1. Reconcile cash.  Count what's in your wallet.  Compare with what
+     hledger reports ('hledger bal cash').  If they are different, try
+     to remember the missing transaction, or look for the error in the
+     already-recorded transactions.  A register report can be helpful
+     ('hledger reg cash').  If you can't find the error, add an
+     adjustment transaction.  Eg if you have $105 after the above, and
      can't explain the missing $2, it could be:
 
-
      2020-01-16 * adjust cash
          assets:cash    $-2 = $105
          expenses:misc
 
-  2. Reconcile checking. Log in to your bank's website. Compare today's
-     (cleared) balance with hledger's cleared balance (`hledger bal
-     checking -C'). If they are different, track down the error or
-     record the missing transaction(s) or add an adjustment
-     transaction, similar to the above. Unlike the cash case, you can
-     usually compare the transaction history and running balance from
-     your bank with the one reported by `hledger reg checking -C'. This
-     will be easier if you generally record transaction dates quite
-     similar to your bank's clearing dates.
+  2. Reconcile checking.  Log in to your bank's website.  Compare
+     today's (cleared) balance with hledger's cleared balance ('hledger
+     bal checking -C').  If they are different, track down the error or
+     record the missing transaction(s) or add an adjustment transaction,
+     similar to the above.  Unlike the cash case, you can usually
+     compare the transaction history and running balance from your bank
+     with the one reported by 'hledger reg checking -C'.  This will be
+     easier if you generally record transaction dates quite similar to
+     your bank's clearing dates.
 
   3. Repeat for other asset/liability accounts.
 
-
    Tip: instead of the register command, use hledger-ui to see a
-live-updating register while you edit the journal: `hledger-ui --watch
+live-updating register while you edit the journal: 'hledger-ui --watch
 --register checking -C'
 
    After reconciling, it could be a good time to mark the reconciled
 transactions' status as "cleared and confirmed", if you want to track
-that, by adding the `*' marker. Eg in the paycheck transaction above,
-insert `*' between `2020-01-15' and `paycheck'
+that, by adding the '*' marker.  Eg in the paycheck transaction above,
+insert '*' between '2020-01-15' and 'paycheck'
 
    If you're using version control, this can be another good time to
 commit:
 
-
 $ git commit -m 'txns' 2020.journal
 
 
@@ -8425,7 +7981,6 @@ Here are some basic reports.
 
    Show all transactions:
 
-
 $ hledger print
 2020-01-01 * opening balances
     assets:bank:checking                      $1000
@@ -8452,7 +8007,6 @@ $ hledger print
 
    Show account names, and their hierarchy:
 
-
 $ hledger accounts --tree
 assets
   bank
@@ -8472,7 +8026,6 @@ liabilities
 
    Show all account totals:
 
-
 $ hledger balance
                $4105  assets
                $4000    bank
@@ -8493,7 +8046,6 @@ $ hledger balance
    Show only asset and liability balances, as a flat list, limited to
 depth 2:
 
-
 $ hledger bal assets liabilities --flat -2
                $4000  assets:bank
                 $105  assets:cash
@@ -8504,59 +8056,56 @@ $ hledger bal assets liabilities --flat -2
    Show the same thing without negative numbers, formatted as a simple
 balance sheet:
 
-
 $ hledger bs --flat -2
 Balance Sheet 2020-01-16
 
-                        || 2020-01-16
+                        || 2020-01-16 
 ========================++============
- Assets                 ||
+ Assets                 ||            
 ------------------------++------------
- assets:bank            ||      $4000
- assets:cash            ||       $105
+ assets:bank            ||      $4000 
+ assets:cash            ||       $105 
 ------------------------++------------
-                        ||      $4105
+                        ||      $4105 
 ========================++============
- Liabilities            ||
+ Liabilities            ||            
 ------------------------++------------
- liabilities:creditcard ||        $50
+ liabilities:creditcard ||        $50 
 ------------------------++------------
-                        ||        $50
+                        ||        $50 
 ========================++============
- Net:                   ||      $4055
+ Net:                   ||      $4055 
 
-   The final total is your "net worth" on the end date. (Or use `bse'
+   The final total is your "net worth" on the end date.  (Or use 'bse'
 for a full balance sheet with equity.)
 
    Show income and expense totals, formatted as an income statement:
 
-
-hledger is
+hledger is 
 Income Statement 2020-01-01-2020-01-16
 
-               || 2020-01-01-2020-01-16
+               || 2020-01-01-2020-01-16 
 ===============++=======================
- Revenues      ||
+ Revenues      ||                       
 ---------------++-----------------------
- income:gifts  ||                   $20
- income:salary ||                 $1000
+ income:gifts  ||                   $20 
+ income:salary ||                 $1000 
 ---------------++-----------------------
-               ||                 $1020
+               ||                 $1020 
 ===============++=======================
- Expenses      ||
+ Expenses      ||                       
 ---------------++-----------------------
- expenses:food ||                   $13
- expenses:misc ||                    $2
+ expenses:food ||                   $13 
+ expenses:misc ||                    $2 
 ---------------++-----------------------
-               ||                   $15
+               ||                   $15 
 ===============++=======================
- Net:          ||                 $1005
+ Net:          ||                 $1005 
 
    The final total is your net income during this period.
 
    Show transactions affecting your wallet, with running total:
 
-
 $ hledger register cash
 2020-01-01 opening balances     assets:cash                   $100          $100
 2020-01-10 gift received        assets:cash                    $20          $120
@@ -8565,7 +8114,6 @@ $ hledger register cash
 
    Show weekly posting counts as a bar chart:
 
-
 $ hledger activity -W
 2019-12-30 *****
 2020-01-06 ****
@@ -8579,10 +8127,10 @@ File: hledger.info,  Node: Migrating to a new file,  Prev: Reporting,  Up: COMMO
 
 At the end of the year, you may want to continue your journal in a new
 file, so that old transactions don't slow down or clutter your reports,
-and to help ensure the integrity of your accounting history. See the
+and to help ensure the integrity of your accounting history.  See the
 close command.
 
-   If using version control, don't forget to `git add' the new file.
+   If using version control, don't forget to 'git add' the new file.
 
 
 File: hledger.info,  Node: LIMITATIONS,  Next: TROUBLESHOOTING,  Prev: COMMON TASKS,  Up: Top
@@ -8590,11 +8138,11 @@ File: hledger.info,  Node: LIMITATIONS,  Next: TROUBLESHOOTING,  Prev: COMMON TA
 17 LIMITATIONS
 **************
 
-The need to precede add-on command options with `--' when invoked from
+The need to precede add-on command options with '--' when invoked from
 hledger is awkward.
 
    When input data contains non-ascii characters, a suitable system
-locale must be configured (or there will be an unhelpful error). Eg on
+locale must be configured (or there will be an unhelpful error).  Eg on
 POSIX, set LANG to something other than C.
 
    In a Microsoft Windows CMD window, non-ascii characters and colours
@@ -8606,8 +8154,8 @@ running a hledger built in CMD in MSYS/CYGWIN, or vice-versa.
    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
-differences.
+   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
 Ledger.
@@ -8624,29 +8172,28 @@ 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
-need to use `export'. Here's an explanation.
+'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.
 
    *Getting errors like "Illegal byte sequence" or "Invalid or
 incomplete multibyte or wide character" or "commitAndReleaseBuffer:
 invalid argument (invalid character)"*
-Programs compiled with GHC (hledger, haskell build tools, etc.) need to
+Programs compiled with GHC (hledger, haskell build tools, etc.)  need to
 have a UTF-8-aware locale configured in the environment, otherwise they
 will fail with these kinds of errors when they encounter non-ascii
 characters.
 
    To fix it, set the LANG environment variable to some locale which
-supports UTF-8. The locale you choose must be installed on your system.
+supports UTF-8.  The locale you choose must be installed on your system.
 
    Here's an example of setting LANG temporarily, on Ubuntu GNU/Linux:
 
-
 $ file my.journal
 my.journal: UTF-8 Unicode text         # the file is UTF8-encoded
 $ echo $LANG
@@ -8657,11 +8204,10 @@ en_US.utf8                             # here's a UTF8-aware one we can use
 POSIX
 $ LANG=en_US.utf8 hledger -f my.journal print   # ensure it is used for this command
 
-   If available, `C.UTF-8' will also work. If your preferred locale
-isn't listed by `locale -a', you might need to install it. Eg on
+   If available, 'C.UTF-8' will also work.  If your preferred locale
+isn't listed by 'locale -a', you might need to install it.  Eg on
 Ubuntu/Debian:
 
-
 $ apt-get install language-pack-fr
 $ locale -a
 C
@@ -8676,468 +8222,465 @@ $ LANG=fr_FR.utf8 hledger -f my.journal print
 
    Here's how you could set it permanently, if you use a bash shell:
 
-
 $ echo "export LANG=en_US.utf8" >>~/.bash_profile
 $ bash --login
 
-   Exact spelling and capitalisation may be important. Note the
-difference on MacOS (`UTF-8', not `utf8'). Some platforms (eg ubuntu)
+   Exact spelling and capitalisation may be important.  Note the
+difference on MacOS ('UTF-8', not 'utf8').  Some platforms (eg ubuntu)
 allow variant spellings, but others (eg macos) require it to be exact:
 
-
 $ locale -a | grep -iE en_us.*utf
 en_US.UTF-8
 $ LANG=en_US.UTF-8 hledger -f my.journal print
 
-
 
 Tag Table:
-Node: Top76
-Node: OPTIONS2449
-Ref: #options2550
-Node: General options2692
-Ref: #general-options2817
-Node: Command options6548
-Ref: #command-options6699
-Node: Command arguments7098
-Ref: #command-arguments7256
-Node: Special characters8134
-Ref: #special-characters8297
-Node: Single escaping shell metacharacters8460
-Ref: #single-escaping-shell-metacharacters8701
-Node: Double escaping regular expression metacharacters9103
-Ref: #double-escaping-regular-expression-metacharacters9414
-Node: Triple escaping for add-on commands9940
-Ref: #triple-escaping-for-add-on-commands10200
-Node: Less escaping10846
-Ref: #less-escaping11000
-Node: Unicode characters11326
-Ref: #unicode-characters11491
-Node: Regular expressions12900
-Ref: #regular-expressions13040
-Node: ENVIRONMENT14781
-Ref: #environment14897
-Node: DATA FILES15879
-Ref: #data-files15998
-Node: Data formats16539
-Ref: #data-formats16657
-Node: Multiple files18139
-Ref: #multiple-files18281
-Node: Strict mode18751
-Ref: #strict-mode18866
-Node: TIME PERIODS19517
-Ref: #time-periods19634
-Node: Smart dates19732
-Ref: #smart-dates19858
-Node: Report start & end date21162
-Ref: #report-start-end-date21337
-Node: Report intervals23007
-Ref: #report-intervals23175
-Node: Period expressions24449
-Ref: #period-expressions24589
-Node: DEPTH28968
-Ref: #depth29068
-Node: QUERIES29399
-Ref: #queries29498
-Node: COSTING33547
-Ref: #costing33650
-Node: VALUATION33923
-Ref: #valuation34031
-Node: -V Value34754
-Ref: #v-value34878
-Node: -X Value in specified commodity35072
-Ref: #x-value-in-specified-commodity35265
-Node: Valuation date35414
-Ref: #valuation-date35576
-Node: Market prices36013
-Ref: #market-prices36194
-Node: --infer-market-price market prices from transactions37376
-Ref: #infer-market-price-market-prices-from-transactions37640
-Node: Valuation commodity38989
-Ref: #valuation-commodity39199
-Node: Simple valuation examples40424
-Ref: #simple-valuation-examples40620
-Node: --value Flexible valuation41282
-Ref: #value-flexible-valuation41484
-Node: More valuation examples43126
-Ref: #more-valuation-examples43327
-Node: Effect of valuation on reports45333
-Ref: #effect-of-valuation-on-reports45515
-Node: PIVOTING53412
-Ref: #pivoting53517
-Node: OUTPUT55196
-Ref: #output55298
-Node: Output destination55349
-Ref: #output-destination55482
-Node: Output format56138
-Ref: #output-format56261
-Node: COMMANDS58424
-Ref: #commands58536
-Node: accounts61926
-Ref: #accounts62026
-Node: activity62718
-Ref: #activity62830
-Node: add63212
-Ref: #add63315
-Node: aregister66110
-Ref: #aregister66224
-Node: aregister and custom posting dates68419
-Ref: #aregister-and-custom-posting-dates68585
-Node: balance69406
-Ref: #balance69525
-Node: balance features70438
-Ref: #balance-features70578
-Node: Simple balance report72248
-Ref: #simple-balance-report72430
-Node: Filtered balance report73878
-Ref: #filtered-balance-report74065
-Node: List or tree mode74362
-Ref: #list-or-tree-mode74530
-Node: Depth limiting75847
-Ref: #depth-limiting76013
-Node: Multi-period balance report76771
-Ref: #multi-period-balance-report76963
-Node: Sorting by amount79219
-Ref: #sorting-by-amount79388
-Node: Percentages79850
-Ref: #percentages80006
-Node: Balance change end balance80938
-Ref: #balance-change-end-balance81129
-Node: Balance report types82553
-Ref: #balance-report-types82743
-Node: Useful balance reports86907
-Ref: #useful-balance-reports87088
-Node: Budget report88172
-Ref: #budget-report88356
-Node: Budget report start date93525
-Ref: #budget-report-start-date93694
-Node: Nested budgets95021
-Ref: #nested-budgets95170
-Node: Customising single-period balance reports98557
-Ref: #customising-single-period-balance-reports98766
-Node: balancesheet100923
-Ref: #balancesheet101061
-Node: balancesheetequity102359
-Ref: #balancesheetequity102510
-Node: cashflow103890
-Ref: #cashflow104014
-Node: check105160
-Ref: #check105265
-Node: Basic checks105898
-Ref: #basic-checks106016
-Node: Strict checks106549
-Ref: #strict-checks106690
-Node: Other checks106994
-Ref: #other-checks107134
-Node: Custom checks107491
-Ref: #custom-checks107611
-Node: close108029
-Ref: #close108133
-Node: close usage109650
-Ref: #close-usage109745
-Node: codes112553
-Ref: #codes112663
-Node: commodities113376
-Ref: #commodities113505
-Node: descriptions113587
-Ref: #descriptions113717
-Node: diff114021
-Ref: #diff114129
-Node: files115174
-Ref: #files115276
-Node: help115422
-Ref: #help115524
-Node: import116247
-Ref: #import116363
-Node: Deduplication117225
-Ref: #deduplication117350
-Node: Import testing119238
-Ref: #import-testing119403
-Node: Importing balance assignments119893
-Ref: #importing-balance-assignments120099
-Node: Commodity display styles120746
-Ref: #commodity-display-styles120919
-Node: incomestatement121048
-Ref: #incomestatement121183
-Node: notes122484
-Ref: #notes122599
-Node: payees122966
-Ref: #payees123074
-Node: prices123600
-Ref: #prices123708
-Node: print124047
-Ref: #print124159
-Node: print-unique129469
-Ref: #print-unique129597
-Node: register129883
-Ref: #register130012
-Node: Custom register output134456
-Ref: #custom-register-output134587
-Node: register-match135924
-Ref: #register-match136060
-Node: rewrite136408
-Ref: #rewrite136525
-Node: Re-write rules in a file138431
-Ref: #re-write-rules-in-a-file138594
-Node: Diff output format139744
-Ref: #diff-output-format139927
-Node: rewrite vs print --auto141019
-Ref: #rewrite-vs.-print---auto141179
-Node: roi141729
-Ref: #roi141829
-Node: Semantics of --inv and --pnl143464
-Ref: #semantics-of---inv-and---pnl143646
-Node: IRR and TWR explained145492
-Ref: #irr-and-twr-explained145652
-Node: stats148714
-Ref: #stats148815
-Node: tags149602
-Ref: #tags149702
-Node: test150219
-Ref: #test150335
-Node: About add-on commands151080
-Ref: #about-add-on-commands151217
-Node: JOURNAL FORMAT152350
-Ref: #journal-format152478
-Node: Transactions154658
-Ref: #transactions154773
-Node: Dates155790
-Ref: #dates155906
-Node: Simple dates155971
-Ref: #simple-dates156091
-Node: Secondary dates156598
-Ref: #secondary-dates156746
-Node: Posting dates158080
-Ref: #posting-dates158203
-Node: Status159572
-Ref: #status159689
-Node: Description161394
-Ref: #description161524
-Node: Payee and note161842
-Ref: #payee-and-note161950
-Node: Comments162284
-Ref: #comments162406
-Node: Tags163599
-Ref: #tags-1163710
-Node: Postings165108
-Ref: #postings165232
-Node: Virtual postings166256
-Ref: #virtual-postings166367
-Node: Account names167669
-Ref: #account-names167806
-Node: Amounts168292
-Ref: #amounts168427
-Node: Decimal marks digit group marks169385
-Ref: #decimal-marks-digit-group-marks169560
-Node: Commodity170432
-Ref: #commodity170590
-Node: Commodity directives171540
-Ref: #commodity-directives171712
-Node: Commodity display style172198
-Ref: #commodity-display-style172375
-Node: Rounding174483
-Ref: #rounding174601
-Node: Transaction prices175011
-Ref: #transaction-prices175177
-Node: Lot prices lot dates177607
-Ref: #lot-prices-lot-dates177790
-Node: Balance assertions178277
-Ref: #balance-assertions178455
-Node: Assertions and ordering179485
-Ref: #assertions-and-ordering179667
-Node: Assertions and included files180364
-Ref: #assertions-and-included-files180601
-Node: Assertions and multiple -f options180932
-Ref: #assertions-and-multiple--f-options181182
-Node: Assertions and commodities181313
-Ref: #assertions-and-commodities181539
-Node: Assertions and prices182694
-Ref: #assertions-and-prices182902
-Node: Assertions and subaccounts183343
-Ref: #assertions-and-subaccounts183566
-Node: Assertions and virtual postings183890
-Ref: #assertions-and-virtual-postings184126
-Node: Assertions and precision184267
-Ref: #assertions-and-precision184454
-Node: Balance assignments184719
-Ref: #balance-assignments184889
-Node: Balance assignments and prices186052
-Ref: #balance-assignments-and-prices186218
-Node: Directives186444
-Ref: #directives186607
-Node: Directives and multiple files192012
-Ref: #directives-and-multiple-files192208
-Node: Comment blocks192870
-Ref: #comment-blocks193047
-Node: Including other files193222
-Ref: #including-other-files193396
-Node: Default year194320
-Ref: #default-year194478
-Node: Declaring payees194885
-Ref: #declaring-payees195051
-Node: Declaring commodities195296
-Ref: #declaring-commodities195477
-Node: Commodity error checking197853
-Ref: #commodity-error-checking198003
-Node: Default commodity198259
-Ref: #default-commodity198439
-Node: Declaring market prices199313
-Ref: #declaring-market-prices199502
-Node: Declaring accounts200360
-Ref: #declaring-accounts200540
-Node: Account error checking201747
-Ref: #account-error-checking201913
-Node: Account comments203090
-Ref: #account-comments203274
-Node: Account subdirectives203700
-Ref: #account-subdirectives203885
-Node: Account types204200
-Ref: #account-types204374
-Node: Declaring account types205109
-Ref: #declaring-account-types205288
-Node: Auto-detected account types205939
-Ref: #auto-detected-account-types206180
-Node: Interference from auto-detected account types207146
-Ref: #interference-from-auto-detected-account-types207423
-Node: Old account type syntax207906
-Ref: #old-account-type-syntax208103
-Node: Account display order208404
-Ref: #account-display-order208564
-Node: Rewriting accounts209715
-Ref: #rewriting-accounts209894
-Node: Basic aliases210653
-Ref: #basic-aliases210789
-Node: Regex aliases211491
-Ref: #regex-aliases211653
-Node: Combining aliases212373
-Ref: #combining-aliases212556
-Node: Aliases and multiple files213833
-Ref: #aliases-and-multiple-files214032
-Node: end aliases214613
-Ref: #end-aliases214760
-Node: Default parent account214862
-Ref: #default-parent-account215052
-Node: Periodic transactions215936
-Ref: #periodic-transactions216119
-Node: Periodic rule syntax218036
-Ref: #periodic-rule-syntax218236
-Node: Two spaces between period expression and description!218939
-Ref: #two-spaces-between-period-expression-and-description219252
-Node: Forecasting with periodic transactions219937
-Ref: #forecasting-with-periodic-transactions220236
-Node: Budgeting with periodic transactions222282
-Ref: #budgeting-with-periodic-transactions222515
-Node: Auto postings222922
-Ref: #auto-postings223058
-Node: Auto postings and multiple files225241
-Ref: #auto-postings-and-multiple-files225439
-Node: Auto postings and dates225647
-Ref: #auto-postings-and-dates225915
-Node: Auto postings and transaction balancing / inferred amounts / balance assertions226090
-Ref: #auto-postings-and-transaction-balancing-inferred-amounts-balance-assertions226436
-Node: Auto posting tags226781
-Ref: #auto-posting-tags226990
-Node: CSV FORMAT227627
-Ref: #csv-format227755
-Node: Examples230336
-Ref: #examples230439
-Node: Basic230646
-Ref: #basic230748
-Node: Bank of Ireland231292
-Ref: #bank-of-ireland231429
-Node: Amazon232894
-Ref: #amazon233014
-Node: Paypal234735
-Ref: #paypal234831
-Node: CSV rules242479
-Ref: #csv-rules242597
-Node: skip242909
-Ref: #skip243004
-Node: fields243376
-Ref: #fields243500
-Node: Transaction field names244661
-Ref: #transaction-field-names244823
-Node: Posting field names244934
-Ref: #posting-field-names245088
-Node: field assignment247449
-Ref: #field-assignment247594
-Node: separator248408
-Ref: #separator248545
-Node: if block249087
-Ref: #if-block249214
-Node: Matching the whole record249612
-Ref: #matching-the-whole-record249789
-Node: Matching individual fields250592
-Ref: #matching-individual-fields250798
-Node: Combining matchers251022
-Ref: #combining-matchers251220
-Node: Rules applied on successful match251534
-Ref: #rules-applied-on-successful-match251727
-Node: if table252384
-Ref: #if-table252505
-Node: end254241
-Ref: #end254355
-Node: date-format254579
-Ref: #date-format254713
-Node: decimal-mark255463
-Ref: #decimal-mark255608
-Node: newest-first255945
-Ref: #newest-first256088
-Node: include256771
-Ref: #include256904
-Node: balance-type257346
-Ref: #balance-type257468
-Node: Tips258168
-Ref: #tips258259
-Node: Rapid feedback258558
-Ref: #rapid-feedback258677
-Node: Valid CSV259136
-Ref: #valid-csv259268
-Node: File Extension259460
-Ref: #file-extension259614
-Node: Reading multiple CSV files260043
-Ref: #reading-multiple-csv-files260230
-Node: Valid transactions260470
-Ref: #valid-transactions260650
-Node: Deduplicating importing261278
-Ref: #deduplicating-importing261459
-Node: Setting amounts262491
-Ref: #setting-amounts262648
-Node: Amount signs264867
-Ref: #amount-signs265021
-Node: Setting currency/commodity265708
-Ref: #setting-currencycommodity265896
-Node: Amount decimal places267076
-Ref: #amount-decimal-places267268
-Node: Referencing other fields267580
-Ref: #referencing-other-fields267779
-Node: How CSV rules are evaluated268677
-Ref: #how-csv-rules-are-evaluated268852
-Node: TIMECLOCK FORMAT270301
-Ref: #timeclock-format270441
-Node: TIMEDOT FORMAT272509
-Ref: #timedot-format272647
-Node: COMMON TASKS276910
-Ref: #common-tasks277039
-Node: Getting help277446
-Ref: #getting-help277580
-Node: Constructing command lines278131
-Ref: #constructing-command-lines278325
-Node: Starting a journal file279024
-Ref: #starting-a-journal-file279224
-Node: Setting opening balances280411
-Ref: #setting-opening-balances280609
-Node: Recording transactions283742
-Ref: #recording-transactions283924
-Node: Reconciling284481
-Ref: #reconciling284626
-Node: Reporting286871
-Ref: #reporting287013
-Node: Migrating to a new file290933
-Ref: #migrating-to-a-new-file291083
-Node: LIMITATIONS291381
-Ref: #limitations291509
-Node: TROUBLESHOOTING292250
-Ref: #troubleshooting292365
+Node: Top68
+Node: OPTIONS2465
+Ref: #options2566
+Node: General options2708
+Ref: #general-options2833
+Node: Command options6568
+Ref: #command-options6719
+Node: Command arguments7119
+Ref: #command-arguments7277
+Node: Special characters8157
+Ref: #special-characters8320
+Node: Single escaping shell metacharacters8483
+Ref: #single-escaping-shell-metacharacters8724
+Node: Double escaping regular expression metacharacters9125
+Ref: #double-escaping-regular-expression-metacharacters9436
+Node: Triple escaping for add-on commands9962
+Ref: #triple-escaping-for-add-on-commands10222
+Node: Less escaping10866
+Ref: #less-escaping11020
+Node: Unicode characters11344
+Ref: #unicode-characters11509
+Node: Regular expressions12921
+Ref: #regular-expressions13061
+Node: ENVIRONMENT14797
+Ref: #environment14913
+Node: DATA FILES15898
+Ref: #data-files16017
+Node: Data formats16556
+Ref: #data-formats16674
+Node: Multiple files18068
+Ref: #multiple-files18210
+Node: Strict mode18679
+Ref: #strict-mode18794
+Node: TIME PERIODS19443
+Ref: #time-periods19560
+Node: Smart dates19658
+Ref: #smart-dates19784
+Node: Report start & end date21110
+Ref: #report-start-end-date21285
+Node: Report intervals22943
+Ref: #report-intervals23111
+Node: Period expressions24388
+Ref: #period-expressions24528
+Node: DEPTH28971
+Ref: #depth29071
+Node: QUERIES29403
+Ref: #queries29502
+Node: COSTING33562
+Ref: #costing33665
+Node: VALUATION33939
+Ref: #valuation34047
+Node: -V Value34772
+Ref: #v-value34896
+Node: -X Value in specified commodity35091
+Ref: #x-value-in-specified-commodity35284
+Node: Valuation date35433
+Ref: #valuation-date35595
+Node: Market prices36032
+Ref: #market-prices36213
+Node: --infer-market-price market prices from transactions37395
+Ref: #infer-market-price-market-prices-from-transactions37659
+Node: Valuation commodity39013
+Ref: #valuation-commodity39223
+Node: Simple valuation examples40447
+Ref: #simple-valuation-examples40643
+Node: --value Flexible valuation41302
+Ref: #value-flexible-valuation41504
+Node: More valuation examples43148
+Ref: #more-valuation-examples43349
+Node: Effect of valuation on reports45348
+Ref: #effect-of-valuation-on-reports45530
+Node: PIVOTING52931
+Ref: #pivoting53036
+Node: OUTPUT54712
+Ref: #output54814
+Node: Output destination54865
+Ref: #output-destination54998
+Node: Output format55655
+Ref: #output-format55778
+Node: COMMANDS57945
+Ref: #commands58057
+Node: accounts61422
+Ref: #accounts61522
+Node: activity62218
+Ref: #activity62330
+Node: add62713
+Ref: #add62816
+Node: aregister65609
+Ref: #aregister65723
+Node: aregister and custom posting dates67921
+Ref: #aregister-and-custom-posting-dates68087
+Node: balance68908
+Ref: #balance69027
+Node: balance features69942
+Ref: #balance-features70082
+Node: Simple balance report71739
+Ref: #simple-balance-report71921
+Node: Filtered balance report73374
+Ref: #filtered-balance-report73561
+Node: List or tree mode73861
+Ref: #list-or-tree-mode74029
+Node: Depth limiting75347
+Ref: #depth-limiting75513
+Node: Multi-period balance report76274
+Ref: #multi-period-balance-report76466
+Node: Sorting by amount78718
+Ref: #sorting-by-amount78887
+Node: Percentages79353
+Ref: #percentages79509
+Node: Balance change end balance80443
+Ref: #balance-change-end-balance80634
+Node: Balance report types82062
+Ref: #balance-report-types82252
+Node: Useful balance reports86325
+Ref: #useful-balance-reports86506
+Node: Budget report87591
+Ref: #budget-report87775
+Node: Budget report start date93014
+Ref: #budget-report-start-date93183
+Node: Nested budgets94515
+Ref: #nested-budgets94664
+Node: Customising single-period balance reports98104
+Ref: #customising-single-period-balance-reports98313
+Node: balancesheet100461
+Ref: #balancesheet100599
+Node: balancesheetequity101898
+Ref: #balancesheetequity102049
+Node: cashflow103429
+Ref: #cashflow103553
+Node: check104699
+Ref: #check104804
+Node: Basic checks105438
+Ref: #basic-checks105556
+Node: Strict checks106107
+Ref: #strict-checks106248
+Node: Other checks106684
+Ref: #other-checks106824
+Node: Custom checks107181
+Ref: #custom-checks107301
+Node: close107718
+Ref: #close107822
+Node: close usage109344
+Ref: #close-usage109439
+Node: codes112252
+Ref: #codes112362
+Node: commodities113074
+Ref: #commodities113203
+Node: descriptions113285
+Ref: #descriptions113415
+Node: diff113719
+Ref: #diff113827
+Node: files114874
+Ref: #files114976
+Node: help115123
+Ref: #help115225
+Node: import115952
+Ref: #import116068
+Node: Deduplication116933
+Ref: #deduplication117058
+Node: Import testing118952
+Ref: #import-testing119117
+Node: Importing balance assignments119605
+Ref: #importing-balance-assignments119811
+Node: Commodity display styles120460
+Ref: #commodity-display-styles120633
+Node: incomestatement120762
+Ref: #incomestatement120897
+Node: notes122202
+Ref: #notes122317
+Node: payees122685
+Ref: #payees122793
+Node: prices123319
+Ref: #prices123427
+Node: print123768
+Ref: #print123880
+Node: print-unique129195
+Ref: #print-unique129323
+Node: register129608
+Ref: #register129737
+Node: Custom register output134183
+Ref: #custom-register-output134314
+Node: register-match135651
+Ref: #register-match135787
+Node: rewrite136138
+Ref: #rewrite136255
+Node: Re-write rules in a file138161
+Ref: #re-write-rules-in-a-file138324
+Node: Diff output format139473
+Ref: #diff-output-format139656
+Node: rewrite vs print --auto140748
+Ref: #rewrite-vs.-print---auto140908
+Node: roi141464
+Ref: #roi141564
+Node: Semantics of --inv and --pnl143197
+Ref: #semantics-of---inv-and---pnl143379
+Node: IRR and TWR explained145229
+Ref: #irr-and-twr-explained145389
+Node: stats148457
+Ref: #stats148558
+Node: tags149346
+Ref: #tags149446
+Node: test149965
+Ref: #test150081
+Node: About add-on commands150828
+Ref: #about-add-on-commands150965
+Node: JOURNAL FORMAT152096
+Ref: #journal-format152224
+Node: Transactions154411
+Ref: #transactions154526
+Node: Dates155540
+Ref: #dates155656
+Node: Simple dates155721
+Ref: #simple-dates155841
+Node: Secondary dates156350
+Ref: #secondary-dates156498
+Node: Posting dates157834
+Ref: #posting-dates157957
+Node: Status159329
+Ref: #status159446
+Node: Description161154
+Ref: #description161284
+Node: Payee and note161604
+Ref: #payee-and-note161712
+Node: Comments162047
+Ref: #comments162169
+Node: Tags163363
+Ref: #tags-1163474
+Node: Postings164867
+Ref: #postings164991
+Node: Virtual postings166017
+Ref: #virtual-postings166128
+Node: Account names167433
+Ref: #account-names167570
+Node: Amounts168058
+Ref: #amounts168193
+Node: Decimal marks digit group marks169149
+Ref: #decimal-marks-digit-group-marks169324
+Node: Commodity170196
+Ref: #commodity170354
+Node: Commodity directives171306
+Ref: #commodity-directives171478
+Node: Commodity display style171965
+Ref: #commodity-display-style172142
+Node: Rounding174250
+Ref: #rounding174368
+Node: Transaction prices174780
+Ref: #transaction-prices174946
+Node: Lot prices lot dates177377
+Ref: #lot-prices-lot-dates177560
+Node: Balance assertions178048
+Ref: #balance-assertions178226
+Node: Assertions and ordering179259
+Ref: #assertions-and-ordering179441
+Node: Assertions and included files180141
+Ref: #assertions-and-included-files180378
+Node: Assertions and multiple -f options180711
+Ref: #assertions-and-multiple--f-options180961
+Node: Assertions and commodities181093
+Ref: #assertions-and-commodities181319
+Node: Assertions and prices182476
+Ref: #assertions-and-prices182684
+Node: Assertions and subaccounts183124
+Ref: #assertions-and-subaccounts183347
+Node: Assertions and virtual postings183671
+Ref: #assertions-and-virtual-postings183907
+Node: Assertions and precision184049
+Ref: #assertions-and-precision184236
+Node: Balance assignments184503
+Ref: #balance-assignments184673
+Node: Balance assignments and prices185837
+Ref: #balance-assignments-and-prices186003
+Node: Directives186227
+Ref: #directives186390
+Node: Directives and multiple files191848
+Ref: #directives-and-multiple-files192044
+Node: Comment blocks192708
+Ref: #comment-blocks192885
+Node: Including other files193061
+Ref: #including-other-files193235
+Node: Default year194159
+Ref: #default-year194317
+Node: Declaring payees194724
+Ref: #declaring-payees194890
+Node: Declaring commodities195136
+Ref: #declaring-commodities195317
+Node: Commodity error checking197697
+Ref: #commodity-error-checking197847
+Node: Default commodity198104
+Ref: #default-commodity198284
+Node: Declaring market prices199160
+Ref: #declaring-market-prices199349
+Node: Declaring accounts200206
+Ref: #declaring-accounts200386
+Node: Account error checking201588
+Ref: #account-error-checking201754
+Node: Account comments202933
+Ref: #account-comments203117
+Node: Account subdirectives203541
+Ref: #account-subdirectives203726
+Node: Account types204039
+Ref: #account-types204213
+Node: Declaring account types204949
+Ref: #declaring-account-types205128
+Node: Auto-detected account types205778
+Ref: #auto-detected-account-types206019
+Node: Interference from auto-detected account types206983
+Ref: #interference-from-auto-detected-account-types207260
+Node: Old account type syntax207743
+Ref: #old-account-type-syntax207940
+Node: Account display order208240
+Ref: #account-display-order208400
+Node: Rewriting accounts209551
+Ref: #rewriting-accounts209730
+Node: Basic aliases210487
+Ref: #basic-aliases210623
+Node: Regex aliases211367
+Ref: #regex-aliases211529
+Node: Combining aliases212248
+Ref: #combining-aliases212431
+Node: Aliases and multiple files213707
+Ref: #aliases-and-multiple-files213906
+Node: end aliases214485
+Ref: #end-aliases214632
+Node: Default parent account214733
+Ref: #default-parent-account214923
+Node: Periodic transactions215807
+Ref: #periodic-transactions215990
+Node: Periodic rule syntax217907
+Ref: #periodic-rule-syntax218107
+Node: Two spaces between period expression and description!218811
+Ref: #two-spaces-between-period-expression-and-description219124
+Node: Forecasting with periodic transactions219808
+Ref: #forecasting-with-periodic-transactions220107
+Node: Budgeting with periodic transactions222162
+Ref: #budgeting-with-periodic-transactions222395
+Node: Auto postings222804
+Ref: #auto-postings222940
+Node: Auto postings and multiple files225119
+Ref: #auto-postings-and-multiple-files225317
+Node: Auto postings and dates225526
+Ref: #auto-postings-and-dates225794
+Node: Auto postings and transaction balancing / inferred amounts / balance assertions225969
+Ref: #auto-postings-and-transaction-balancing-inferred-amounts-balance-assertions226314
+Node: Auto posting tags226656
+Ref: #auto-posting-tags226865
+Node: CSV FORMAT227501
+Ref: #csv-format227629
+Node: Examples230215
+Ref: #examples230318
+Node: Basic230526
+Ref: #basic230628
+Node: Bank of Ireland231170
+Ref: #bank-of-ireland231307
+Node: Amazon232769
+Ref: #amazon232889
+Node: Paypal234608
+Ref: #paypal234704
+Node: CSV rules242348
+Ref: #csv-rules242466
+Node: skip242778
+Ref: #skip242873
+Node: fields243248
+Ref: #fields243372
+Node: Transaction field names244537
+Ref: #transaction-field-names244699
+Node: Posting field names244810
+Ref: #posting-field-names244964
+Node: field assignment247478
+Ref: #field-assignment247623
+Node: separator248441
+Ref: #separator248578
+Node: if block249118
+Ref: #if-block249245
+Node: Matching the whole record249646
+Ref: #matching-the-whole-record249823
+Node: Matching individual fields250626
+Ref: #matching-individual-fields250832
+Node: Combining matchers251056
+Ref: #combining-matchers251254
+Node: Rules applied on successful match251567
+Ref: #rules-applied-on-successful-match251760
+Node: if table252414
+Ref: #if-table252535
+Node: end254273
+Ref: #end254387
+Node: date-format254611
+Ref: #date-format254745
+Node: decimal-mark255494
+Ref: #decimal-mark255639
+Node: newest-first255978
+Ref: #newest-first256121
+Node: include256804
+Ref: #include256937
+Node: balance-type257381
+Ref: #balance-type257503
+Node: Tips258203
+Ref: #tips258294
+Node: Rapid feedback258593
+Ref: #rapid-feedback258712
+Node: Valid CSV259172
+Ref: #valid-csv259304
+Node: File Extension259496
+Ref: #file-extension259650
+Node: Reading multiple CSV files260079
+Ref: #reading-multiple-csv-files260266
+Node: Valid transactions260507
+Ref: #valid-transactions260687
+Node: Deduplicating importing261315
+Ref: #deduplicating-importing261496
+Node: Setting amounts262529
+Ref: #setting-amounts262686
+Node: Amount signs265127
+Ref: #amount-signs265281
+Node: Setting currency/commodity265968
+Ref: #setting-currencycommodity266156
+Node: Amount decimal places267330
+Ref: #amount-decimal-places267522
+Node: Referencing other fields267834
+Ref: #referencing-other-fields268033
+Node: How CSV rules are evaluated268930
+Ref: #how-csv-rules-are-evaluated269105
+Node: TIMECLOCK FORMAT270556
+Ref: #timeclock-format270696
+Node: TIMEDOT FORMAT272757
+Ref: #timedot-format272895
+Node: COMMON TASKS277171
+Ref: #common-tasks277300
+Node: Getting help277707
+Ref: #getting-help277841
+Node: Constructing command lines278394
+Ref: #constructing-command-lines278588
+Node: Starting a journal file279285
+Ref: #starting-a-journal-file279485
+Node: Setting opening balances280673
+Ref: #setting-opening-balances280871
+Node: Recording transactions284012
+Ref: #recording-transactions284194
+Node: Reconciling284750
+Ref: #reconciling284895
+Node: Reporting287152
+Ref: #reporting287294
+Node: Migrating to a new file291293
+Ref: #migrating-to-a-new-file291443
+Node: LIMITATIONS291742
+Ref: #limitations291870
+Node: TROUBLESHOOTING292613
+Ref: #troubleshooting292728
 
 End Tag Table
diff --git a/hledger/hledger.txt b/hledger/hledger.txt
index 86b2b376e..fdb766bd4 100644
--- a/hledger/hledger.txt
+++ b/hledger/hledger.txt
@@ -2598,22 +2598,25 @@ COMMANDS
 
        o parseable - data files are well-formed and can be successfully parsed
 
-       o autobalanced -  all  transactions  are  balanced,  inferring  missing
-         amounts  where  necessary,  and possibly converting commodities using
-         transaction prices or automatically-inferred transaction prices
+       o balancedwithautoconversion - all transactions are balanced, inferring
+         missing  amounts where necessary, and possibly converting commodities
+         using transaction prices or automatically-inferred transaction prices
 
-       o assertions - all balance  assertions  in  the  journal  are  passing.
+       o assertions  -  all  balance  assertions  in  the journal are passing.
          (This check can be disabled with -I/--ignore-assertions.)
 
    Strict checks
        These additional checks are run when the -s/--strict (strict mode) flag
-       is used.  Or, they can be run by giving their  names  as  arguments  to
+       is  used.   Or,  they  can be run by giving their names as arguments to
        check:
 
        o accounts - all account names used by transactions have been declared
 
        o commodities - all commodity symbols used have been declared
 
+       o balancednoautoconversion - transactions are balanced, possibly  using
+         explicit transaction prices but not inferred ones
+
    Other checks
        These  checks  can  be  run  only by giving their names as arguments to
        check.  They are more  specialised  and  not  desirable  for  everyone,
@@ -4892,56 +4895,57 @@ JOURNAL FORMAT
    Basic aliases
        To set an account alias, use the alias directive in your journal  file.
        This  affects all subsequent journal entries in the current file or its
-       included files.  The spaces around the = are optional:
+       included files (but note: not sibling or  parent  files).   The  spaces
+       around the = are optional:
 
               alias OLD = NEW
 
        Or, you can use the --alias 'OLD=NEW' option on the command line.  This
        affects all entries.  It's useful for trying out aliases interactively.
 
-       OLD and NEW are  case  sensitive  full  account  names.   hledger  will
-       replace  any occurrence of the old account name with the new one.  Sub-
+       OLD  and  NEW  are  case  sensitive  full  account names.  hledger will
+       replace any occurrence of the old account name with the new one.   Sub-
        accounts are also affected.  Eg:
 
               alias checking = assets:bank:wells fargo:checking
               ; rewrites "checking" to "assets:bank:wells fargo:checking", or "checking:a" to "assets:bank:wells fargo:checking:a"
 
    Regex aliases
-       There is also a more powerful variant that uses a  regular  expression,
+       There  is  also a more powerful variant that uses a regular expression,
        indicated by the forward slashes:
 
               alias /REGEX/ = REPLACEMENT
 
        or --alias '/REGEX/=REPLACEMENT'.
 
-       REGEX  is  a  case-insensitive regular expression.  Anywhere it matches
-       inside an account name, the matched part will be replaced  by  REPLACE-
-       MENT.   If REGEX contains parenthesised match groups, these can be ref-
+       REGEX is a case-insensitive regular expression.   Anywhere  it  matches
+       inside  an  account name, the matched part will be replaced by REPLACE-
+       MENT.  If REGEX contains parenthesised match groups, these can be  ref-
        erenced by the usual numeric backreferences in REPLACEMENT.  Eg:
 
               alias /^(.+):bank:([^:]+):(.*)/ = \1:\2 \3
               ; rewrites "assets:bank:wells fargo:checking" to  "assets:wells fargo checking"
 
-       Also note that REPLACEMENT continues to the end of line (or on  command
-       line,  to  end  of  option argument), so it can contain trailing white-
+       Also  note that REPLACEMENT continues to the end of line (or on command
+       line, to end of option argument), so it  can  contain  trailing  white-
        space.
 
    Combining aliases
-       You can define as many aliases as you like,  using  journal  directives
+       You  can  define  as many aliases as you like, using journal directives
        and/or command line options.
 
-       Recursive  aliases  -  where an account name is rewritten by one alias,
-       then by another alias, and so on - are allowed.  Each  alias  sees  the
+       Recursive aliases - where an account name is rewritten  by  one  alias,
+       then  by  another  alias, and so on - are allowed.  Each alias sees the
        effect of previously applied aliases.
 
-       In  such  cases it can be important to understand which aliases will be
-       applied and in which order.  For (each account name  in)  each  journal
+       In such cases it can be important to understand which aliases  will  be
+       applied  and  in  which order.  For (each account name in) each journal
        entry, we apply:
 
-       1. alias  directives  preceding the journal entry, most recently parsed
+       1. alias directives preceding the journal entry, most  recently  parsed
           first (ie, reading upward from the journal entry, bottom to top)
 
-       2. --alias options, in the order they  appeared  on  the  command  line
+       2. --alias  options,  in  the  order  they appeared on the command line
           (left to right).
 
        In other words, for (an account name in) a given journal entry:
@@ -4952,15 +4956,15 @@ JOURNAL FORMAT
 
        o aliases defined after/below the entry do not affect it.
 
-       This gives nearby aliases precedence over distant ones, and helps  pro-
-       vide  semantic stability - aliases will keep working the same way inde-
+       This  gives nearby aliases precedence over distant ones, and helps pro-
+       vide semantic stability - aliases will keep working the same way  inde-
        pendent of which files are being read and in which order.
 
-       In case of trouble, adding --debug=6 to  the  command  line  will  show
+       In  case  of  trouble,  adding  --debug=6 to the command line will show
        which aliases are being applied when.
 
    Aliases and multiple files
-       As  explained at Directives and multiple files, alias directives do not
+       As explained at Directives and multiple files, alias directives do  not
        affect parent or sibling files.  Eg in this command,
 
               hledger -f a.aliases -f b.journal
@@ -4987,14 +4991,14 @@ JOURNAL FORMAT
               include c.journal  ; also affected
 
    end aliases
-       You can clear (forget) all  currently  defined  aliases  with  the  end
+       You  can  clear  (forget)  all  currently  defined aliases with the end
        aliases directive:
 
               end aliases
 
    Default parent account
-       You  can  specify  a  parent  account  which  will  be prepended to all
-       accounts within a section of the journal.  Use the  apply  account  and
+       You can specify a  parent  account  which  will  be  prepended  to  all
+       accounts  within  a  section of the journal.  Use the apply account and
        end apply account directives like so:
 
               apply account home
@@ -5011,7 +5015,7 @@ JOURNAL FORMAT
                   home:food           $10
                   home:cash          $-10
 
-       If  end  apply  account  is omitted, the effect lasts to the end of the
+       If end apply account is omitted, the effect lasts to  the  end  of  the
        file.  Included files are also affected, eg:
 
               apply account business
@@ -5020,49 +5024,49 @@ JOURNAL FORMAT
               apply account personal
               include personal.journal
 
-       Prior to hledger 1.0, legacy account and end spellings were  also  sup-
+       Prior  to  hledger 1.0, legacy account and end spellings were also sup-
        ported.
 
-       A  default parent account also affects account directives.  It does not
-       affect account names being entered via hledger add or hledger-web.   If
-       account  aliases are present, they are applied after the default parent
+       A default parent account also affects account directives.  It does  not
+       affect  account names being entered via hledger add or hledger-web.  If
+       account aliases are present, they are applied after the default  parent
        account.
 
    Periodic transactions
-       Periodic transaction rules  describe  transactions  that  recur.   They
-       allow  hledger  to  generate temporary future transactions to help with
-       forecasting, so you don't have to write out each one  in  the  journal,
+       Periodic  transaction  rules  describe  transactions  that recur.  They
+       allow hledger to generate temporary future transactions  to  help  with
+       forecasting,  so  you  don't have to write out each one in the journal,
        and it's easy to try out different forecasts.
 
-       Periodic  transactions  can be a little tricky, so before you use them,
+       Periodic transactions can be a little tricky, so before you  use  them,
        read this whole section - or at least these tips:
 
-       1. Two spaces accidentally added or omitted will cause  you  trouble  -
+       1. Two  spaces  accidentally  added or omitted will cause you trouble -
           read about this below.
 
-       2. For  troubleshooting,  show  the generated transactions with hledger
-          print  --forecast  tag:generated  or  hledger  register   --forecast
+       2. For troubleshooting, show the generated  transactions  with  hledger
+          print   --forecast  tag:generated  or  hledger  register  --forecast
           tag:generated.
 
-       3. Forecasted  transactions  will  begin  only after the last non-fore-
+       3. Forecasted transactions will begin only  after  the  last  non-fore-
           casted transaction's date.
 
-       4. Forecasted transactions will end 6 months from  today,  by  default.
+       4. Forecasted  transactions  will  end 6 months from today, by default.
           See below for the exact start/end rules.
 
-       5. period   expressions  can  be  tricky.   Their  documentation  needs
+       5. period  expressions  can  be  tricky.   Their  documentation   needs
           improvement, but is worth studying.
 
-       6. Some period expressions with a repeating interval must  begin  on  a
-          natural  boundary  of  that  interval.  Eg in weekly from DATE, DATE
-          must be a monday.  ~ weekly from 2019/10/1 (a tuesday) will give  an
+       6. Some  period  expressions  with a repeating interval must begin on a
+          natural boundary of that interval.  Eg in  weekly  from  DATE,  DATE
+          must  be a monday.  ~ weekly from 2019/10/1 (a tuesday) will give an
           error.
 
        7. Other period expressions with an interval are automatically expanded
-          to cover a whole number of that interval.  (This is done to  improve
+          to  cover a whole number of that interval.  (This is done to improve
           reports, but it also affects periodic transactions.  Yes, it's a bit
-          inconsistent with the above.) Eg: ~ every 10th  day  of  month  from
-          2020/01,  which  is  equivalent  to  ~  every 10th day of month from
+          inconsistent  with  the  above.)  Eg: ~ every 10th day of month from
+          2020/01, which is equivalent to ~  every  10th  day  of  month  from
           2020/01/01, will be adjusted to start on 2019/12/10.
 
        Periodic transaction rules also have a second meaning: they are used to
@@ -5077,17 +5081,17 @@ JOURNAL FORMAT
                   expenses:rent          $2000
                   assets:bank:checking
 
-       There  is  an additional constraint on the period expression: the start
-       date must fall on a natural boundary of the interval.  Eg monthly  from
+       There is an additional constraint on the period expression:  the  start
+       date  must fall on a natural boundary of the interval.  Eg monthly from
        2018/1/1 is valid, but monthly from 2018/1/15 is not.
 
-       Partial  or  relative dates (M/D, D, tomorrow, last week) in the period
-       expression can work (useful or not).  They will be relative to  today's
-       date,  unless  a  Y  default year directive is in effect, in which case
+       Partial or relative dates (M/D, D, tomorrow, last week) in  the  period
+       expression  can work (useful or not).  They will be relative to today's
+       date, unless a Y default year directive is in  effect,  in  which  case
        they will be relative to Y/1/1.
 
    Two spaces between period expression and description!
-       If the period expression is  followed  by  a  transaction  description,
+       If  the  period  expression  is  followed by a transaction description,
        these must be separated by two or more spaces.  This helps hledger know
        where the period expression ends, so that descriptions can not acciden-
        tally alter their meaning, as in this example:
@@ -5101,67 +5105,67 @@ JOURNAL FORMAT
 
        So,
 
-       o Do  write two spaces between your period expression and your transac-
+       o Do write two spaces between your period expression and your  transac-
          tion description, if any.
 
-       o Don't accidentally write two spaces in  the  middle  of  your  period
+       o Don't  accidentally  write  two  spaces  in the middle of your period
          expression.
 
    Forecasting with periodic transactions
-       The  --forecast  flag  activates  any periodic transaction rules in the
-       journal.  They will generate temporary  recurring  transactions,  which
-       are  not  saved  in  the  journal,  but  will appear in all reports (eg
+       The --forecast flag activates any periodic  transaction  rules  in  the
+       journal.   They  will  generate temporary recurring transactions, which
+       are not saved in the journal,  but  will  appear  in  all  reports  (eg
        print).  This can be useful for estimating balances into the future, or
-       experimenting  with  different scenarios.  Or, it can be used as a data
+       experimenting with different scenarios.  Or, it can be used as  a  data
        entry aid: describe recurring transactions, and every so often copy the
        output of print --forecast into the journal.
 
-       These  transactions  will  have  an extra tag indicating which periodic
+       These transactions will have an extra  tag  indicating  which  periodic
        rule generated them: generated-transaction:~ PERIODICEXPR.  And a simi-
-       lar,  hidden  tag  (beginning  with  an underscore) which, because it's
-       never displayed by print, can be used to match  transactions  generated
+       lar, hidden tag (beginning with  an  underscore)  which,  because  it's
+       never  displayed  by print, can be used to match transactions generated
        "just now": _generated-transaction:~ PERIODICEXPR.
 
-       Periodic  transactions  are  generated within some forecast period.  By
+       Periodic transactions are generated within some  forecast  period.   By
        default, this
 
        o begins on the later of
 
          o the report start date if specified with -b/-p/date:
 
-         o the day after the latest normal (non-periodic) transaction  in  the
+         o the  day  after the latest normal (non-periodic) transaction in the
            journal, or today if there are no normal transactions.
 
-       o ends  on  the  report  end  date  if specified with -e/-p/date:, or 6
+       o ends on the report end date  if  specified  with  -e/-p/date:,  or  6
          months (180 days) from today.
 
-       This means that periodic transactions will begin only after the  latest
-       recorded  transaction.   And a recorded transaction dated in the future
-       can prevent generation of periodic transactions.  (You can  avoid  that
+       This  means that periodic transactions will begin only after the latest
+       recorded transaction.  And a recorded transaction dated in  the  future
+       can  prevent  generation of periodic transactions.  (You can avoid that
        by writing the future transaction as a one-time periodic rule instead -
        put tilde before the date, eg ~ YYYY-MM-DD ...).
 
        Or, you can set your own arbitrary "forecast period", which can overlap
-       recorded  transactions,  and need not be in the future, by providing an
-       option argument, like --forecast=PERIODEXPR.  Note the equals  sign  is
+       recorded transactions, and need not be in the future, by  providing  an
+       option  argument,  like --forecast=PERIODEXPR.  Note the equals sign is
        required, a space won't work.  PERIODEXPR is a period expression, which
-       can specify the start date, end date, or both, like in a  date:  query.
-       (See  also  hledger.1  ->  Report  start  &  end date).  Some examples:
+       can  specify  the start date, end date, or both, like in a date: query.
+       (See also hledger.1 ->  Report  start  &  end  date).   Some  examples:
        --forecast=202001-202004, --forecast=jan-, --forecast=2020.
 
    Budgeting with periodic transactions
-       With the --budget flag, currently supported  by  the  balance  command,
-       each  periodic transaction rule declares recurring budget goals for the
-       specified accounts.  Eg the first example  above  declares  a  goal  of
-       spending  $2000  on  rent  (and  also,  a goal of depositing $2000 into
-       checking) every month.  Goals and actual performance can then  be  com-
+       With  the  --budget  flag,  currently supported by the balance command,
+       each periodic transaction rule declares recurring budget goals for  the
+       specified  accounts.   Eg  the  first  example above declares a goal of
+       spending $2000 on rent (and also,  a  goal  of  depositing  $2000  into
+       checking)  every  month.  Goals and actual performance can then be com-
        pared in budget reports.
 
        See also: Budgeting and Forecasting.
 
 
    Auto postings
-       "Automated  postings"  or  "auto postings" are extra postings which get
+       "Automated postings" or "auto postings" are extra  postings  which  get
        added  automatically  to  transactions  which  match  certain  queries,
        defined by "auto posting rules", when you use the --auto flag.
 
@@ -5172,27 +5176,27 @@ JOURNAL FORMAT
                   ...
                   ACCOUNT  [AMOUNT]
 
-       except  the  first  line is an equals sign (mnemonic: = suggests match-
-       ing), followed by a query (which matches existing postings),  and  each
-       "posting"  line  describes  a  posting to be generated, and the posting
+       except the first line is an equals sign (mnemonic:  =  suggests  match-
+       ing),  followed  by a query (which matches existing postings), and each
+       "posting" line describes a posting to be  generated,  and  the  posting
        amounts can be:
 
-       o a normal amount with a commodity symbol, eg $2.  This  will  be  used
+       o a  normal  amount  with a commodity symbol, eg $2.  This will be used
          as-is.
 
        o a number, eg 2.  The commodity symbol (if any) from the matched post-
          ing will be added to this.
 
-       o a numeric multiplier, eg *2 (a star followed by  a  number  N).   The
+       o a  numeric  multiplier,  eg  *2 (a star followed by a number N).  The
          matched posting's amount (and total price, if any) will be multiplied
          by N.
 
-       o a multiplier with a commodity symbol, eg *$2 (a star, number  N,  and
+       o a  multiplier  with a commodity symbol, eg *$2 (a star, number N, and
          symbol S).  The matched posting's amount will be multiplied by N, and
          its commodity symbol will be replaced with S.
 
-       Any query term containing spaces must be enclosed in single  or  double
-       quotes,  as on the command line.  Eg, note the quotes around the second
+       Any  query  term containing spaces must be enclosed in single or double
+       quotes, as on the command line.  Eg, note the quotes around the  second
        query term below:
 
               = expenses:groceries 'expenses:dining out'
@@ -5231,24 +5235,24 @@ JOURNAL FORMAT
 
    Auto postings and multiple files
        An auto posting rule can affect any transaction in the current file, or
-       in  any  parent file or child file.  Note, currently it will not affect
+       in any parent file or child file.  Note, currently it will  not  affect
        sibling files (when multiple -f/--file are used - see #1212).
 
    Auto postings and dates
-       A posting date (or secondary date) in the matched posting,  or  (taking
-       precedence)  a  posting date in the auto posting rule itself, will also
+       A  posting  date (or secondary date) in the matched posting, or (taking
+       precedence) a posting date in the auto posting rule itself,  will  also
        be used in the generated posting.
 
    Auto postings and transaction balancing / inferred amounts / balance asser-
        tions
        Currently, auto postings are added:
 
-       o after  missing amounts are inferred, and transactions are checked for
+       o after missing amounts are inferred, and transactions are checked  for
          balancedness,
 
        o but before balance assertions are checked.
 
-       Note this means that journal entries must be balanced both  before  and
+       Note  this  means that journal entries must be balanced both before and
        after auto postings are added.  This changed in hledger 1.12+; see #893
        for background.
 
@@ -5258,11 +5262,11 @@ JOURNAL FORMAT
        o generated-posting:= QUERY - shows this was generated by an auto post-
          ing rule, and the query
 
-       o _generated-posting:=  QUERY  - a hidden tag, which does not appear in
+       o _generated-posting:= QUERY - a hidden tag, which does not  appear  in
          hledger's output.  This can be used to match postings generated "just
          now", rather than generated in the past and saved to the journal.
 
-       Also,  any transaction that has been changed by auto posting rules will
+       Also, any transaction that has been changed by auto posting rules  will
        have these tags added:
 
        o modified: - this transaction was modified
@@ -5273,61 +5277,61 @@ JOURNAL FORMAT
 CSV FORMAT
        How hledger reads CSV data, and the CSV rules file format.
 
-       hledger  can read CSV files (Character Separated Value - usually comma,
-       semicolon, or tab) containing dated records as  if  they  were  journal
+       hledger can read CSV files (Character Separated Value - usually  comma,
+       semicolon,  or  tab)  containing  dated records as if they were journal
        files, automatically converting each CSV record into a transaction.
 
        (To learn about writing CSV, see CSV output.)
 
        We describe each CSV file's format with a corresponding rules file.  By
-       default this is named like the CSV file with a .rules extension  added.
-       Eg  when reading FILE.csv, hledger also looks for FILE.csv.rules in the
-       same directory as FILE.csv.  You can specify  a  different  rules  file
-       with  the  --rules-file  option.  If a rules file is not found, hledger
+       default  this is named like the CSV file with a .rules extension added.
+       Eg when reading FILE.csv, hledger also looks for FILE.csv.rules in  the
+       same  directory  as  FILE.csv.   You can specify a different rules file
+       with the --rules-file option.  If a rules file is  not  found,  hledger
        will create a sample rules file, which you'll need to adjust.
 
-       This file contains rules describing the CSV data (header  line,  fields
+       This  file  contains rules describing the CSV data (header line, fields
        layout, date format etc.), and how to construct hledger journal entries
        (transactions) from it.  Often there will also be a list of conditional
        rules  for  categorising  transactions  based  on  their  descriptions.
-       Here's an overview of the CSV rules; these  are  described  more  fully
+       Here's  an  overview  of  the CSV rules; these are described more fully
        below, after the examples:
 
 
        skip                             skip one or more header lines or matched
                                         CSV records
-       fields                           name CSV fields, assign them to  hledger
+       fields                           name  CSV fields, assign them to hledger
                                         fields
-       field assignment                 assign  a  value  to  one hledger field,
+       field assignment                 assign a value  to  one  hledger  field,
                                         with interpolation
        separator                        a custom field separator
-       if block                         apply some rules to CSV records  matched
+       if block                         apply  some rules to CSV records matched
                                         by patterns
-       if table                         apply  some rules to CSV records matched
+       if table                         apply some rules to CSV records  matched
                                         by patterns, alternate syntax
        end                              skip the remaining CSV records
        date-format                      how to parse dates in CSV records
        decimal-mark                     the decimal mark used in CSV amounts, if
                                         ambiguous
-       newest-first                     disambiguate  record  order when there's
+       newest-first                     disambiguate record order  when  there's
                                         only one date
        include                          inline another CSV rules file
        balance-type                     choose which type of balance assignments
                                         to use
 
-       Note,  for best error messages when reading CSV files, use a .csv, .tsv
+       Note, for best error messages when reading CSV files, use a .csv,  .tsv
        or .ssv file extension or file prefix - see File Extension below.
 
        There's an introductory Convert CSV files tutorial on hledger.org.
 
    Examples
-       Here are some sample hledger CSV rules files.  See also the  full  col-
+       Here  are  some sample hledger CSV rules files.  See also the full col-
        lection at:
        https://github.com/simonmichael/hledger/tree/master/examples/csv
 
    Basic
-       At  minimum,  the  rules file must identify the date and amount fields,
-       and often it also specifies the date format and how many  header  lines
+       At minimum, the rules file must identify the date  and  amount  fields,
+       and  often  it also specifies the date format and how many header lines
        there are.  Here's a simple CSV file and a rules file for it:
 
               Date, Description, Id, Amount
@@ -5346,8 +5350,8 @@ CSV FORMAT
        Default account names are chosen, since we didn't set them.
 
    Bank of Ireland
-       Here's  a  CSV with two amount fields (Debit and Credit), and a balance
-       field, which we can use to add balance assertions, which is not  neces-
+       Here's a CSV with two amount fields (Debit and Credit), and  a  balance
+       field,  which we can use to add balance assertions, which is not neces-
        sary but provides extra error checking:
 
               Date,Details,Debit,Credit,Balance
@@ -5389,13 +5393,13 @@ CSV FORMAT
                   assets:bank:boi:checking         EUR-5.0 = EUR126.0
                   expenses:unknown                  EUR5.0
 
-       The  balance assertions don't raise an error above, because we're read-
-       ing directly from CSV, but they will be checked if  these  entries  are
+       The balance assertions don't raise an error above, because we're  read-
+       ing  directly  from  CSV, but they will be checked if these entries are
        imported into a journal file.
 
    Amazon
        Here we convert amazon.com order history, and use an if block to gener-
-       ate a third posting if there's a fee.  (In practice you'd probably  get
+       ate  a third posting if there's a fee.  (In practice you'd probably get
        this data from your bank instead, but it's an example.)
 
               "Date","Type","To/From","Name","Status","Amount","Fees","Transaction ID"
@@ -5447,7 +5451,7 @@ CSV FORMAT
                   expenses:fees           $1.00
 
    Paypal
-       Here's  a  real-world rules file for (customised) Paypal CSV, with some
+       Here's a real-world rules file for (customised) Paypal CSV,  with  some
        Paypal-specific rules, and a second rules file included:
 
               "Date","Time","TimeZone","Name","Type","Status","Currency","Gross","Fee","Net","From Email Address","To Email Address","Transaction ID","Item Title","Item ID","Reference Txn ID","Receipt ID","Balance","Note"
@@ -5602,9 +5606,9 @@ CSV FORMAT
    skip
               skip N
 
-       The  word  "skip"  followed by a number (or no number, meaning 1) tells
-       hledger to ignore this many non-empty lines  preceding  the  CSV  data.
-       (Empty/blank  lines  are skipped automatically.) You'll need this when-
+       The word "skip" followed by a number (or no number,  meaning  1)  tells
+       hledger  to  ignore  this  many non-empty lines preceding the CSV data.
+       (Empty/blank lines are skipped automatically.) You'll need  this  when-
        ever your CSV data contains header lines.
 
        It also has a second purpose: it can be used inside if blocks to ignore
@@ -5613,27 +5617,27 @@ CSV FORMAT
    fields
               fields FIELDNAME1, FIELDNAME2, ...
 
-       A  fields  list  (the  word  "fields" followed by comma-separated field
-       names) is the quick way to assign CSV field values to  hledger  fields.
+       A fields list (the word  "fields"  followed  by  comma-separated  field
+       names)  is  the quick way to assign CSV field values to hledger fields.
        It does two things:
 
-       1. it  names  the  CSV fields.  This is optional, but can be convenient
+       1. it names the CSV fields.  This is optional, but  can  be  convenient
           later for interpolating them.
 
        2. when you use a standard hledger field name, it assigns the CSV value
           to that part of the hledger transaction.
 
-       Here's  an  example  that  says "use the 1st, 2nd and 4th fields as the
-       transaction's date, description and amount; name the  last  two  fields
+       Here's an example that says "use the 1st, 2nd and  4th  fields  as  the
+       transaction's  date,  description  and amount; name the last two fields
        for later reference; and ignore the others":
 
               fields date, description, , amount, , , somefield, anotherfield
 
-       Field  names  may  not contain whitespace.  Fields you don't care about
-       can be left unnamed.  Currently there must be least  two  items  (there
+       Field names may not contain whitespace.  Fields you  don't  care  about
+       can  be  left  unnamed.  Currently there must be least two items (there
        must be at least one comma).
 
-       Note,  always  use  comma  in  the  fields  list, even if your CSV uses
+       Note, always use comma in the  fields  list,  even  if  your  CSV  uses
        another separator character.
 
        Here are the standard hledger field/pseudo-field names.  For more about
@@ -5646,30 +5650,34 @@ CSV FORMAT
 
    Posting field names
    account
-       accountN,  where  N  is 1 to 99, causes a posting to be generated, with
+       accountN, where N is 1 to 99, causes a posting to  be  generated,  with
        that account name.
 
-       Most often there are two postings, so you'll want to set  account1  and
-       account2.   Typically  account1 is associated with the CSV file, and is
-       set once with a top-level assignment, while account2 is  set  based  on
+       Most  often  there are two postings, so you'll want to set account1 and
+       account2.  Typically account1 is associated with the CSV file,  and  is
+       set  once  with  a top-level assignment, while account2 is set based on
        each transaction's description, and in conditional blocks.
 
-       If  a  posting's  account name is left unset but its amount is set (see
-       below), a default account name will be chosen (like  "expenses:unknown"
+       If a posting's account name is left unset but its amount  is  set  (see
+       below),  a default account name will be chosen (like "expenses:unknown"
        or "income:unknown").
 
    amount
-       amountN  sets  posting N's amount.  If the CSV uses separate fields for
-       inflows and outflows, you can use amountN-in and  amountN-out  instead.
-       By  assigning to amount1, amount2, ...  etc.  you can generate anywhere
-       from 0 to 99 postings.
+       amountN sets the  Nth  posting's  amount.   By  assigning  to  amount1,
+       amount2, ...  etc.  you can generate up to 99 postings.
 
-       There is also an older, unnumbered form of these  names,  suitable  for
-       2-posting transactions, which sets both posting 1's and (negated) post-
-       ing 2's amount: amount, or amount-in and  amount-out.   This  is  still
-       supported  because  it  keeps pre-hledger-1.17 csv rules files working,
-       and because it can be more succinct, and because  it  converts  posting
-       2's amount to cost if there's a transaction price, which can be useful.
+       If  the  CSV  uses  separate fields for debits and credits (inflows and
+       outflows), you  can  use  amountN-in  and  amountN-out  instead.   Note
+       hledger  assumes  both of these fields are unsigned, and will automati-
+       cally negate the "-out" value.  If the fields are signed, see  "Setting
+       amounts" below.
+
+       There  is  also an unnumbered form of these names: amount, or amount-in
+       and amount-out.  This is supported to keep pre-hledger-1.17  CSV  rules
+       files  working  (and  for occasional convenience).  It is suitable only
+       for two-posting transactions; it sets both posting 1's and posting  2's
+       amount.  Posting 2's amount will be negated, and also converted to cost
+       if there's a transaction price.
 
        If you have an existing rules file using the unnumbered form, you might
        want  to  use  the numbered form in certain conditional blocks, without
@@ -6068,55 +6076,61 @@ CSV FORMAT
        Assign (via a fields list or a field assignment) to amountN.  This sets
        the Nth posting's amount.  N is usually 1 or 2 but can go up to 99.
 
-       2. If the CSV has separate Debit and Credit amount fields:
-       Assign  to amountN-in and amountN-out.  This sets posting N's amount to
-       whichever of these has a non-zero value, guessing an appropriate  sign.
+       2. If the CSV has separate amount fields for debit & credit (in & out):
 
-           o If hledger guesses the wrong sign:
-           Prepend a minus sign to flip it.  Eg:
+           a. If both fields are unsigned:
+           Assign to amountN-in and amountN-out.  This sets posting N's amount
+           to  whichever of these has a non-zero value, and negates the "-out"
+           value.
 
-                    fields date, description, amount-in, amount-out
-                    amount-out -%amount-out
+           b. If either field is signed (can contain a minus sign):
+           Use a conditional rule to flip  the  sign  (of  non-empty  values).
+           Since  hledger  always negates amountN-out, if it was already nega-
+           tive, we must undo that by negating once  more  (but  only  if  the
+           field is non-empty):
 
-           o If both fields contain a non-zero value:
-           The amountN-in/amountN-out rules require that each CSV record has a
-           non-zero value in exactly one of the two fields,  so  that  hledger
-           knows which to choose.  So these would all be rejected:
+                  fields date, description, amount1-in, amount1-out
+                  if %amount1-out [1-9]
+                   amount1-out -%amount1-out
 
-                    "",  ""
-                    "0", "0"
-                    "1", "none"
+           c. If both fields, or neither field, can contain a non-zero value:
+           hledger  normally  expects exactly one of the fields to have a non-
+           zero value.  Eg,  the  amountN-in/amountN-out  rules  would  reject
+           value pairs like these:
 
-             If  your  CSV  has amount values like this, use conditional rules
-             instead.  For example, to make hledger to choose the  value  con-
-             taining non-zero digits:
+                  "",  ""
+                  "0", "0"
+                  "1", "none"
 
-                    fields date, description, in, out
-                    if %in [1-9]
-                     amount1 %in
-                    if %out [1-9]
-                     amount1 %out
+           So, use smarter conditional rules to set the amount from the appro-
+           priate field.  Eg, these rules would make it  use  only  the  value
+           containing non-zero digits, handling the above:
 
-       3. Using the old numberless syntax:
-       Assign  to  amount (or to amount-in and amount-out).  This sets posting
-       1's and posting 2's amounts (and converts posting 2's amount to  cost).
-       This  is  supported  for backwards compatibility (and occasional conve-
-       nience).
+                  fields date, description, in, out
+                  if %in [1-9]
+                   amount1 %in
+                  if %out [1-9]
+                   amount1 %out
+
+       3. If  you are stuck with hledger <1.17, or you want posting 2's amount
+          converted to cost:
+       Assign to amount (or to amount-in and amount-out).  (The old numberless
+       syntax, which sets amount1 and amount2.)
 
        4. If the CSV has the balance instead of the transaction amount:
        Assign to balanceN, which sets posting N's amount indirectly via a bal-
        ance assignment.  (Old syntax: balance, equivalent to balance1.)
 
            o If hledger guesses the wrong default account name:
-           When  setting  the  amount via balance assertion, hledger may guess
-           the wrong default account name.  So, set the account  name  explic-
+           When setting the amount via balance assertion,  hledger  may  guess
+           the  wrong  default account name.  So, set the account name explic-
            itly, eg:
 
                     fields date, description, balance1
                     account1 assets:checking
 
    Amount signs
-       There  is  some  special handling for amount signs, to simplify parsing
+       There is some special handling for amount signs,  to  simplify  parsing
        and sign-flipping:
 
        o If an amount value begins with a plus sign:
@@ -6125,17 +6139,17 @@ CSV FORMAT
        o If an amount value is parenthesised:
        it will be de-parenthesised and sign-flipped: (AMT) becomes -AMT
 
-       o If an amount value has two minus signs (or two sets  of  parentheses,
+       o If  an  amount value has two minus signs (or two sets of parentheses,
          or a minus sign and parentheses):
        they cancel out and will be removed: --AMT or -(AMT) becomes AMT
 
-       o If  an  amount value contains just a sign (or just a set of parenthe-
+       o If an amount value contains just a sign (or just a set  of  parenthe-
          ses):
-       that is removed, making it an empty value.  "+" or "-" or "()"  becomes
+       that  is removed, making it an empty value.  "+" or "-" or "()" becomes
        "".
 
    Setting currency/commodity
-       If  the  currency/commodity  symbol  is  included  in  the CSV's amount
+       If the currency/commodity  symbol  is  included  in  the  CSV's  amount
        field(s):
 
               2020-01-01,foo,$123.00
@@ -6154,7 +6168,7 @@ CSV FORMAT
               2020-01-01,foo,USD,123.00
 
        You can assign that to the currency pseudo-field, which has the special
-       effect of prepending itself to every amount in the transaction (on  the
+       effect  of prepending itself to every amount in the transaction (on the
        left, with no separating space):
 
               fields date,description,currency,amount
@@ -6163,7 +6177,7 @@ CSV FORMAT
                   expenses:unknown       USD123.00
                   income:unknown        USD-123.00
 
-       Or,  you  can  use a field assignment to construct the amount yourself,
+       Or, you can use a field assignment to construct  the  amount  yourself,
        with more control.  Eg to put the symbol on the right, and separated by
        a space:
 
@@ -6174,7 +6188,7 @@ CSV FORMAT
                   expenses:unknown        123.00 USD
                   income:unknown         -123.00 USD
 
-       Note  we  used a temporary field name (cur) that is not currency - that
+       Note we used a temporary field name (cur) that is not currency  -  that
        would trigger the prepending effect, which we don't want here.
 
    Amount decimal places
@@ -6182,13 +6196,13 @@ CSV FORMAT
        amount1 influence commodity display styles, such as the number of deci-
        mal places displayed in reports.
 
-       The original amounts as written in the CSV file do not  affect  display
+       The  original  amounts as written in the CSV file do not affect display
        style (because we don't yet reliably know their commodity).
 
    Referencing other fields
-       In  field assignments, you can interpolate only CSV fields, not hledger
-       fields.  In the example below, there's both a CSV field and  a  hledger
-       field  named  amount1, but %amount1 always means the CSV field, not the
+       In field assignments, you can interpolate only CSV fields, not  hledger
+       fields.   In  the example below, there's both a CSV field and a hledger
+       field named amount1, but %amount1 always means the CSV field,  not  the
        hledger field:
 
               # Name the third CSV field "amount1"
@@ -6200,7 +6214,7 @@ CSV FORMAT
               # Set comment to the CSV amount1 (not the amount1 assigned above)
               comment %amount1
 
-       Here, since there's no CSV amount1 field, %amount1 will produce a  lit-
+       Here,  since there's no CSV amount1 field, %amount1 will produce a lit-
        eral "amount1":
 
               fields date,description,csvamount
@@ -6208,7 +6222,7 @@ CSV FORMAT
               # Can't interpolate amount1 here
               comment %amount1
 
-       When  there  are  multiple field assignments to the same hledger field,
+       When there are multiple field assignments to the  same  hledger  field,
        only the last one takes effect.  Here, comment's value will be be B, or
        C if "something" is matched, but never A:
 
@@ -6218,14 +6232,14 @@ CSV FORMAT
                comment C
 
    How CSV rules are evaluated
-       Here's  how  to  think of CSV rules being evaluated (if you really need
+       Here's how to think of CSV rules being evaluated (if  you  really  need
        to).  First,
 
-       o include - all includes are inlined, from top to bottom, depth  first.
-         (At  each  include  point the file is inlined and scanned for further
+       o include  - all includes are inlined, from top to bottom, depth first.
+         (At each include point the file is inlined and  scanned  for  further
          includes, recursively, before proceeding.)
 
-       Then "global" rules are  evaluated,  top  to  bottom.   If  a  rule  is
+       Then  "global"  rules  are  evaluated,  top  to  bottom.   If a rule is
        repeated, the last one wins:
 
        o skip (at top level)
@@ -6239,33 +6253,33 @@ CSV FORMAT
 
        Then for each CSV record in turn:
 
-       o test all if blocks.  If any of them contain  a  end  rule,  skip  all
+       o test  all  if  blocks.   If  any of them contain a end rule, skip all
          remaining CSV records.  Otherwise if any of them contain a skip rule,
-         skip that many CSV records.   If  there  are  multiple  matched  skip
+         skip  that  many  CSV  records.   If  there are multiple matched skip
          rules, the first one wins.
 
-       o collect  all field assignments at top level and in matched if blocks.
-         When there are multiple assignments for a field, keep only  the  last
+       o collect all field assignments at top level and in matched if  blocks.
+         When  there  are multiple assignments for a field, keep only the last
          one.
 
-       o compute  a  value  for  each  hledger field - either the one that was
-         assigned to it (and interpolate the %CSVFIELDNAME references),  or  a
+       o compute a value for each hledger field -  either  the  one  that  was
+         assigned  to  it (and interpolate the %CSVFIELDNAME references), or a
          default
 
        o generate a synthetic hledger transaction from these values.
 
-       This  is all part of the CSV reader, one of several readers hledger can
-       use to parse input files.  When all files have been read  successfully,
-       the  transactions  are passed as input to whichever hledger command the
+       This is all part of the CSV reader, one of several readers hledger  can
+       use  to parse input files.  When all files have been read successfully,
+       the transactions are passed as input to whichever hledger  command  the
        user specified.
 
 TIMECLOCK FORMAT
        The time logging format of timeclock.el, as read by hledger.
 
-       hledger can read time logs in timeclock format.  As with Ledger,  these
+       hledger  can read time logs in timeclock format.  As with Ledger, these
        are (a subset of) timeclock.el's format, containing clock-in and clock-
-       out entries as in the example below.  The date is a simple  date.   The
-       time  format is HH:MM[:SS][+-ZZZZ].  Seconds and timezone are optional.
+       out  entries  as in the example below.  The date is a simple date.  The
+       time format is HH:MM[:SS][+-ZZZZ].  Seconds and timezone are  optional.
        The timezone, if present, must be four digits and is ignored (currently
        the time is always interpreted as a local time).
 
@@ -6274,9 +6288,9 @@ TIMECLOCK FORMAT
               i 2015/03/31 22:21:45 another account
               o 2015/04/01 02:00:34
 
-       hledger  treats  each  clock-in/clock-out pair as a transaction posting
-       some number of hours to an account.  Or if the session spans more  than
-       one  day, it is split into several transactions, one for each day.  For
+       hledger treats each clock-in/clock-out pair as  a  transaction  posting
+       some  number of hours to an account.  Or if the session spans more than
+       one day, it is split into several transactions, one for each day.   For
        the above time log, hledger print generates these journal entries:
 
               $ hledger -f t.timeclock print
@@ -6297,69 +6311,69 @@ TIMECLOCK FORMAT
 
        To generate time logs, ie to clock in and clock out, you could:
 
-       o use emacs and the built-in timeclock.el, or the  extended  timeclock-
+       o use  emacs  and the built-in timeclock.el, or the extended timeclock-
          x.el and perhaps the extras in ledgerutils.el
 
        o at the command line, use these bash aliases: shell     alias ti="echo
-         i `date '+%Y-%m-%d %H:%M:%S'` \$* >>$TIMELOG"      alias  to="echo  o
+         i  `date  '+%Y-%m-%d  %H:%M:%S'` \$* >>$TIMELOG"     alias to="echo o
          `date '+%Y-%m-%d %H:%M:%S'` >>$TIMELOG"
 
        o or use the old ti and to scripts in the ledger 2.x repository.  These
-         rely on a "timeclock" executable which I think is just the  ledger  2
+         rely  on  a "timeclock" executable which I think is just the ledger 2
          executable renamed.
 
 TIMEDOT FORMAT
        hledger's human-friendly time logging format.
 
-       Timedot  is  a plain text format for logging dated, categorised quanti-
-       ties (of time, usually), supported by hledger.  It  is  convenient  for
-       approximate  and retroactive time logging, eg when the real-time clock-
-       in/out required with a timeclock file is too precise or  too  interrup-
-       tive.   It  can be formatted like a bar chart, making clear at a glance
+       Timedot is a plain text format for logging dated,  categorised  quanti-
+       ties  (of  time,  usually), supported by hledger.  It is convenient for
+       approximate and retroactive time logging, eg when the real-time  clock-
+       in/out  required  with a timeclock file is too precise or too interrup-
+       tive.  It can be formatted like a bar chart, making clear at  a  glance
        where time was spent.
 
-       Though called "timedot", this format is read by hledger  as  commodity-
-       less  quantities,  so  it  could  be used to represent dated quantities
+       Though  called  "timedot", this format is read by hledger as commodity-
+       less quantities, so it could be  used  to  represent  dated  quantities
        other than time.  In the docs below we'll assume it's time.
 
-       A timedot file contains a series of day entries.  A  day  entry  begins
-       with  a  non-indented hledger-style simple date (Y-M-D, Y/M/D, Y.M.D..)
-       Any additional text on the same line is used as a transaction  descrip-
+       A  timedot  file  contains a series of day entries.  A day entry begins
+       with a non-indented hledger-style simple date (Y-M-D,  Y/M/D,  Y.M.D..)
+       Any  additional text on the same line is used as a transaction descrip-
        tion for this day.
 
        This is followed by optionally-indented timelog items for that day, one
-       per   line.    Each   timelog   item   is    a    note,    usually    a
-       hledger:style:account:name  representing  a  time category, followed by
-       two or more spaces, and a quantity.   Each  timelog  item  generates  a
+       per    line.     Each    timelog    item   is   a   note,   usually   a
+       hledger:style:account:name representing a time  category,  followed  by
+       two  or  more  spaces,  and  a quantity.  Each timelog item generates a
        hledger transaction.
 
        Quantities can be written as:
 
-       o dots:  a sequence of dots (.) representing quarter hours.  Spaces may
+       o dots: a sequence of dots (.) representing quarter hours.  Spaces  may
          optionally be used for grouping.  Eg: ....  ..
 
        o an integral or decimal number, representing hours.  Eg: 1.5
 
-       o an integral or decimal number immediately followed by a  unit  symbol
-         s,  m,  h, d, w, mo, or y, representing seconds, minutes, hours, days
+       o an  integral  or decimal number immediately followed by a unit symbol
+         s, m, h, d, w, mo, or y, representing seconds, minutes,  hours,  days
          weeks, months or years respectively.  Eg: 90m.  The following equiva-
-         lencies  are  assumed,  currently: 1m = 60s, 1h = 60m, 1d = 24h, 1w =
+         lencies are assumed, currently: 1m = 60s, 1h = 60m, 1d =  24h,  1w  =
          7d, 1mo = 30d, 1y=365d.
 
-       There is some flexibility allowing notes and  todo  lists  to  be  kept
+       There  is  some  flexibility  allowing  notes and todo lists to be kept
        right in the time log, if needed:
 
        o Blank lines and lines beginning with # or ; are ignored.
 
        o Lines not ending with a double-space and quantity are parsed as items
-         taking no time, which will not appear in balance reports by  default.
+         taking  no time, which will not appear in balance reports by default.
          (Add -E to see them.)
 
-       o Org  mode headlines (lines beginning with one or more * followed by a
-         space) can be used as date lines or  timelog  items  (the  stars  are
-         ignored).   Also  all  org  headlines  before the first date line are
-         ignored.  This means org users can manage their  timelog  as  an  org
-         outline  (eg  using  org-mode/orgstruct-mode in Emacs), for organisa-
+       o Org mode headlines (lines beginning with one or more * followed by  a
+         space)  can  be  used  as  date lines or timelog items (the stars are
+         ignored).  Also all org headlines before  the  first  date  line  are
+         ignored.   This  means  org  users can manage their timelog as an org
+         outline (eg using org-mode/orgstruct-mode in  Emacs),  for  organisa-
          tion, faster navigation, controlling visibility etc.
 
        Examples:
@@ -6424,7 +6438,7 @@ TIMEDOT FORMAT
               ------------++----------------------------------------
                           ||         7.75         2.25         8.00
 
-       I prefer to use period for separating account components.  We can  make
+       I  prefer to use period for separating account components.  We can make
        this work with an account alias:
 
               2016/2/4
@@ -6441,9 +6455,9 @@ TIMEDOT FORMAT
        Here is a sample.timedot.
 
 COMMON TASKS
-       Here  are  some  quick  examples  of  how  to  do some basic tasks with
-       hledger.  For more  details,  see  the  reference  section  below,  the
-       hledger_journal(5)    manual,   or   the   more   extensive   docs   at
+       Here are some quick examples  of  how  to  do  some  basic  tasks  with
+       hledger.   For  more  details,  see  the  reference  section below, the
+       hledger_journal(5)   manual,   or   the   more   extensive   docs    at
        https://hledger.org.
 
    Getting help
@@ -6459,26 +6473,26 @@ COMMON TASKS
        https://hledger.org#help-feedback
 
    Constructing command lines
-       hledger  has  an  extensive  and  powerful  command line interface.  We
+       hledger has an extensive  and  powerful  command  line  interface.   We
        strive to keep it simple and ergonomic, but you may run into one of the
        confusing real world details described in OPTIONS, below.  If that hap-
        pens, here are some tips that may help:
 
-       o command-specific options must go after the command (it's fine to  put
+       o command-specific  options must go after the command (it's fine to put
          all options there) (hledger CMD OPTS ARGS)
 
-       o running  add-on  executables directly simplifies command line parsing
+       o running add-on executables directly simplifies command  line  parsing
          (hledger-ui OPTS ARGS)
 
        o enclose "problematic" args in single quotes
 
-       o if needed, also add a backslash to hide regular expression  metachar-
+       o if  needed, also add a backslash to hide regular expression metachar-
          acters from the shell
 
        o to see how a misbehaving command is being parsed, add --debug=2.
 
    Starting a journal file
-       hledger   looks   for   your   accounting   data  in  a  journal  file,
+       hledger  looks  for  your  accounting   data   in   a   journal   file,
        $HOME/.hledger.journal by default:
 
               $ hledger stats
@@ -6486,9 +6500,9 @@ COMMON TASKS
               Please create it first, eg with "hledger add" or a text editor.
               Or, specify an existing journal file with -f or LEDGER_FILE.
 
-       You can override this by setting the LEDGER_FILE environment  variable.
+       You  can override this by setting the LEDGER_FILE environment variable.
        It's a good practice to keep this important file under version control,
-       and to start a new file each year.  So  you  could  do  something  like
+       and  to  start  a  new  file each year.  So you could do something like
        this:
 
               $ mkdir ~/finance
@@ -6512,20 +6526,20 @@ COMMON TASKS
               Market prices            : 0 ()
 
    Setting opening balances
-       Pick  a  starting  date  for which you can look up the balances of some
-       real-world assets (bank accounts,  wallet..)  and  liabilities  (credit
+       Pick a starting date for which you can look up  the  balances  of  some
+       real-world  assets  (bank  accounts,  wallet..) and liabilities (credit
        cards..).
 
-       To  avoid  a  lot of data entry, you may want to start with just one or
-       two accounts, like your checking account or cash  wallet;  and  pick  a
-       recent  starting  date,  like  today or the start of the week.  You can
+       To avoid a lot of data entry, you may want to start with  just  one  or
+       two  accounts,  like  your  checking account or cash wallet; and pick a
+       recent starting date, like today or the start of  the  week.   You  can
        always come back later and add more accounts and older transactions, eg
        going back to january 1st.
 
-       Add  an opening balances transaction to the journal, declaring the bal-
+       Add an opening balances transaction to the journal, declaring the  bal-
        ances on this date.  Here are two ways to do it:
 
-       o The first way: open the journal in any text editor and save an  entry
+       o The  first way: open the journal in any text editor and save an entry
          like this:
 
                 2020-01-01 * opening balances
@@ -6535,19 +6549,19 @@ COMMON TASKS
                     liabilities:creditcard               $-50   = $-50
                     equity:opening/closing balances
 
-         These  are  start-of-day  balances, ie whatever was in the account at
+         These are start-of-day balances, ie whatever was in  the  account  at
          the end of the previous day.
 
-         The * after the date is an  optional  status  flag.   Here  it  means
+         The  *  after  the  date  is  an optional status flag.  Here it means
          "cleared & confirmed".
 
-         The  currency symbols are optional, but usually a good idea as you'll
+         The currency symbols are optional, but usually a good idea as  you'll
          be dealing with multiple currencies sooner or later.
 
-         The = amounts are optional balance assertions, providing extra  error
+         The  = amounts are optional balance assertions, providing extra error
          checking.
 
-       o The  second  way:  run hledger add and follow the prompts to record a
+       o The second way: run hledger add and follow the prompts  to  record  a
          similar transaction:
 
                 $ hledger add
@@ -6584,18 +6598,18 @@ COMMON TASKS
                 Starting the next transaction (. or ctrl-D/ctrl-C to quit)
                 Date [2020-01-01]: .
 
-       If you're using version control, this could be a good  time  to  commit
+       If  you're  using  version control, this could be a good time to commit
        the journal.  Eg:
 
               $ git commit -m 'initial balances' 2020.journal
 
    Recording transactions
-       As  you spend or receive money, you can record these transactions using
-       one of the methods above (text editor, hledger add)  or  by  using  the
-       hledger-iadd  or hledger-web add-ons, or by using the import command to
+       As you spend or receive money, you can record these transactions  using
+       one  of  the  methods  above (text editor, hledger add) or by using the
+       hledger-iadd or hledger-web add-ons, or by using the import command  to
        convert CSV data downloaded from your bank.
 
-       Here are some simple transactions, see  the  hledger_journal(5)  manual
+       Here  are  some  simple transactions, see the hledger_journal(5) manual
        and hledger.org for more ideas:
 
               2020/1/10 * gift received
@@ -6611,22 +6625,22 @@ COMMON TASKS
                 assets:bank:checking    $1000
 
    Reconciling
-       Periodically  you should reconcile - compare your hledger-reported bal-
-       ances against external sources of truth, like bank statements  or  your
-       bank's  website - to be sure that your ledger accurately represents the
-       real-world balances (and, that the  real-world  institutions  have  not
-       made  a  mistake!).   This gets easy and fast with (1) practice and (2)
-       frequency.  If you do it daily, it can take 2-10 minutes.  If  you  let
-       it  pile  up, expect it to take longer as you hunt down errors and dis-
+       Periodically you should reconcile - compare your hledger-reported  bal-
+       ances  against  external sources of truth, like bank statements or your
+       bank's website - to be sure that your ledger accurately represents  the
+       real-world  balances  (and,  that  the real-world institutions have not
+       made a mistake!).  This gets easy and fast with (1)  practice  and  (2)
+       frequency.   If  you do it daily, it can take 2-10 minutes.  If you let
+       it pile up, expect it to take longer as you hunt down errors  and  dis-
        crepancies.
 
        A typical workflow:
 
-       1. Reconcile cash.  Count what's in your  wallet.   Compare  with  what
-          hledger  reports  (hledger bal cash).  If they are different, try to
-          remember the missing transaction, or  look  for  the  error  in  the
-          already-recorded  transactions.   A  register  report can be helpful
-          (hledger reg cash).  If you can't find the error, add an  adjustment
+       1. Reconcile  cash.   Count  what's  in your wallet.  Compare with what
+          hledger reports (hledger bal cash).  If they are different,  try  to
+          remember  the  missing  transaction,  or  look  for the error in the
+          already-recorded transactions.  A register  report  can  be  helpful
+          (hledger  reg cash).  If you can't find the error, add an adjustment
           transaction.  Eg if you have $105 after the above, and can't explain
           the missing $2, it could be:
 
@@ -6636,26 +6650,26 @@ COMMON TASKS
 
        2. Reconcile checking.  Log in to your bank's website.  Compare today's
           (cleared) balance with hledger's cleared balance (hledger bal check-
-          ing -C).  If they are different, track down the error or record  the
-          missing  transaction(s) or add an adjustment transaction, similar to
+          ing  -C).  If they are different, track down the error or record the
+          missing transaction(s) or add an adjustment transaction, similar  to
           the above.  Unlike the cash case, you can usually compare the trans-
-          action  history  and  running  balance  from  your bank with the one
-          reported by hledger reg checking -C.  This will  be  easier  if  you
-          generally  record  transaction  dates  quite  similar to your bank's
+          action history and running balance  from  your  bank  with  the  one
+          reported  by  hledger  reg  checking -C.  This will be easier if you
+          generally record transaction dates  quite  similar  to  your  bank's
           clearing dates.
 
        3. Repeat for other asset/liability accounts.
 
-       Tip: instead of the register command, use hledger-ui  to  see  a  live-
+       Tip:  instead  of  the  register command, use hledger-ui to see a live-
        updating register while you edit the journal: hledger-ui --watch --reg-
        ister checking -C
 
-       After reconciling, it could be a  good  time  to  mark  the  reconciled
-       transactions'  status  as "cleared and confirmed", if you want to track
-       that, by adding the * marker.  Eg in the  paycheck  transaction  above,
+       After  reconciling,  it  could  be  a  good time to mark the reconciled
+       transactions' status as "cleared and confirmed", if you want  to  track
+       that,  by  adding  the * marker.  Eg in the paycheck transaction above,
        insert * between 2020-01-15 and paycheck
 
-       If  you're using version control, this can be another good time to com-
+       If you're using version control, this can be another good time to  com-
        mit:
 
               $ git commit -m 'txns' 2020.journal
@@ -6727,7 +6741,7 @@ COMMON TASKS
               --------------------
                                  0
 
-       Show only asset and liability balances, as  a  flat  list,  limited  to
+       Show  only  asset  and  liability  balances, as a flat list, limited to
        depth 2:
 
               $ hledger bal assets liabilities --flat -2
@@ -6737,7 +6751,7 @@ COMMON TASKS
               --------------------
                              $4055
 
-       Show  the  same  thing  without negative numbers, formatted as a simple
+       Show the same thing without negative numbers,  formatted  as  a  simple
        balance sheet:
 
               $ hledger bs --flat -2
@@ -6804,15 +6818,15 @@ COMMON TASKS
               2020-01-13 ****
 
    Migrating to a new file
-       At  the end of the year, you may want to continue your journal in a new
+       At the end of the year, you may want to continue your journal in a  new
        file, so that old transactions don't slow down or clutter your reports,
-       and  to  help ensure the integrity of your accounting history.  See the
+       and to help ensure the integrity of your accounting history.   See  the
        close command.
 
        If using version control, don't forget to git add the new file.
 
 LIMITATIONS
-       The need to precede add-on command options with --  when  invoked  from
+       The  need  to  precede add-on command options with -- when invoked from
        hledger is awkward.
 
        When input data contains non-ascii characters, a suitable system locale
@@ -6828,36 +6842,36 @@ LIMITATIONS
        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.
 
-       Getting  errors  like "Illegal byte sequence" or "Invalid or incomplete
-       multibyte or wide character" or "commitAndReleaseBuffer: invalid  argu-
+       Getting errors like "Illegal byte sequence" or "Invalid  or  incomplete
+       multibyte  or wide character" or "commitAndReleaseBuffer: invalid argu-
        ment (invalid character)"
        Programs compiled with GHC (hledger, haskell build tools, etc.) need to
        have a UTF-8-aware locale configured in the environment, otherwise they
-       will  fail  with  these  kinds  of errors when they encounter non-ascii
+       will fail with these kinds of  errors  when  they  encounter  non-ascii
        characters.
 
-       To fix it, set the LANG environment variable to some locale which  sup-
+       To  fix it, set the LANG environment variable to some locale which sup-
        ports UTF-8.  The locale you choose must be installed on your system.
 
        Here's an example of setting LANG temporarily, on Ubuntu GNU/Linux:
@@ -6872,8 +6886,8 @@ TROUBLESHOOTING
               POSIX
               $ LANG=en_US.utf8 hledger -f my.journal print   # ensure it is used for this command
 
-       If  available,  C.UTF-8 will also work.  If your preferred locale isn't
-       listed  by  locale  -a,  you  might  need  to  install   it.    Eg   on
+       If available, C.UTF-8 will also work.  If your preferred  locale  isn't
+       listed   by   locale   -a,  you  might  need  to  install  it.   Eg  on
        Ubuntu/Debian:
 
               $ apt-get install language-pack-fr
@@ -6893,8 +6907,8 @@ TROUBLESHOOTING
               $ echo "export LANG=en_US.utf8" >>~/.bash_profile
               $ bash --login
 
-       Exact  spelling  and capitalisation may be important.  Note the differ-
-       ence on MacOS (UTF-8, not utf8).   Some  platforms  (eg  ubuntu)  allow
+       Exact spelling and capitalisation may be important.  Note  the  differ-
+       ence  on  MacOS  (UTF-8,  not  utf8).  Some platforms (eg ubuntu) allow
        variant spellings, but others (eg macos) require it to be exact:
 
               $ locale -a | grep -iE en_us.*utf
@@ -6904,7 +6918,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)
 
 
