import: doc: update builtin manuals
[ci skip]
This commit is contained in:
		
							parent
							
								
									376cfe352c
								
							
						
					
					
						commit
						e658c301e2
					
				| @ -1990,12 +1990,14 @@ just show the transactions to be imported | ||||
| .RS | ||||
| .RE | ||||
| .PP | ||||
| Input files are provided as arguments, or glob patterns. | ||||
| So eg to add new transactions from all CSV files to the main journal: | ||||
| hledger import *.csv | ||||
| The input files are specified as arguments \- no need to write \-f | ||||
| before each one. | ||||
| So eg to add new transactions from all CSV files to the main journal, | ||||
| it\[aq]s just: \f[C]hledger\ import\ *.csv\f[] | ||||
| .PP | ||||
| New transactions are detected like print \-\-new (using .latest.FILE | ||||
| state files). | ||||
| New transactions are detected in the same way as print \-\-new: by | ||||
| assuming transactions are always added to the input files in increasing | ||||
| date order, and by saving \f[C]\&.latest.FILE\f[] state files. | ||||
| .SS incomestatement | ||||
| .PP | ||||
| Show an income statement. | ||||
|  | ||||
| @ -1598,12 +1598,13 @@ the main journal file. | ||||
| 
 | ||||
|      just show the transactions to be imported | ||||
| 
 | ||||
|    Input files are provided as arguments, or glob patterns.  So eg to | ||||
| add new transactions from all CSV files to the main journal: hledger | ||||
| import *.csv | ||||
|    The input files are specified as arguments - no need to write -f | ||||
| before each one.  So eg to add new transactions from all CSV files to | ||||
| the main journal, it's just: 'hledger import *.csv' | ||||
| 
 | ||||
|    New transactions are detected like print -new (using .latest.FILE | ||||
| state files). | ||||
|    New transactions are detected in the same way as print -new: by | ||||
| assuming transactions are always added to the input files in increasing | ||||
| date order, and by saving '.latest.FILE' state files. | ||||
| 
 | ||||
|  | ||||
| File: hledger.1.info,  Node: incomestatement,  Next: prices,  Prev: import,  Up: COMMANDS | ||||
| @ -2285,57 +2286,57 @@ Node: help50477 | ||||
| Ref: #help50580 | ||||
| Node: import51654 | ||||
| Ref: #import51770 | ||||
| Node: incomestatement52165 | ||||
| Ref: #incomestatement52301 | ||||
| Node: prices54254 | ||||
| Ref: #prices54371 | ||||
| Node: print54414 | ||||
| Ref: #print54526 | ||||
| Node: print-unique59372 | ||||
| Ref: #print-unique59500 | ||||
| Node: register59568 | ||||
| Ref: #register59697 | ||||
| Node: Custom register output64198 | ||||
| Ref: #custom-register-output64329 | ||||
| Node: register-match65626 | ||||
| Ref: #register-match65762 | ||||
| Node: rewrite65945 | ||||
| Ref: #rewrite66064 | ||||
| Node: stats66133 | ||||
| Ref: #stats66238 | ||||
| Node: tags67119 | ||||
| Ref: #tags67219 | ||||
| Node: test67251 | ||||
| Ref: #test67337 | ||||
| Node: ADD-ON COMMANDS67705 | ||||
| Ref: #add-on-commands67817 | ||||
| Node: Official add-ons69104 | ||||
| Ref: #official-add-ons69246 | ||||
| Node: api69333 | ||||
| Ref: #api69424 | ||||
| Node: ui69476 | ||||
| Ref: #ui69577 | ||||
| Node: web69635 | ||||
| Ref: #web69726 | ||||
| Node: Third party add-ons69772 | ||||
| Ref: #third-party-add-ons69949 | ||||
| Node: diff70084 | ||||
| Ref: #diff70183 | ||||
| Node: iadd70282 | ||||
| Ref: #iadd70398 | ||||
| Node: interest70481 | ||||
| Ref: #interest70604 | ||||
| Node: irr70699 | ||||
| Ref: #irr70799 | ||||
| Node: Experimental add-ons70877 | ||||
| Ref: #experimental-add-ons71031 | ||||
| Node: autosync71322 | ||||
| Ref: #autosync71436 | ||||
| Node: budget71675 | ||||
| Ref: #budget71799 | ||||
| Node: chart71865 | ||||
| Ref: #chart71984 | ||||
| Node: check72055 | ||||
| Ref: #check72159 | ||||
| Node: incomestatement52313 | ||||
| Ref: #incomestatement52449 | ||||
| Node: prices54402 | ||||
| Ref: #prices54519 | ||||
| Node: print54562 | ||||
| Ref: #print54674 | ||||
| Node: print-unique59520 | ||||
| Ref: #print-unique59648 | ||||
| Node: register59716 | ||||
| Ref: #register59845 | ||||
| Node: Custom register output64346 | ||||
| Ref: #custom-register-output64477 | ||||
| Node: register-match65774 | ||||
| Ref: #register-match65910 | ||||
| Node: rewrite66093 | ||||
| Ref: #rewrite66212 | ||||
| Node: stats66281 | ||||
| Ref: #stats66386 | ||||
| Node: tags67267 | ||||
| Ref: #tags67367 | ||||
| Node: test67399 | ||||
| Ref: #test67485 | ||||
| Node: ADD-ON COMMANDS67853 | ||||
| Ref: #add-on-commands67965 | ||||
| Node: Official add-ons69252 | ||||
| Ref: #official-add-ons69394 | ||||
| Node: api69481 | ||||
| Ref: #api69572 | ||||
| Node: ui69624 | ||||
| Ref: #ui69725 | ||||
| Node: web69783 | ||||
| Ref: #web69874 | ||||
| Node: Third party add-ons69920 | ||||
| Ref: #third-party-add-ons70097 | ||||
| Node: diff70232 | ||||
| Ref: #diff70331 | ||||
| Node: iadd70430 | ||||
| Ref: #iadd70546 | ||||
| Node: interest70629 | ||||
| Ref: #interest70752 | ||||
| Node: irr70847 | ||||
| Ref: #irr70947 | ||||
| Node: Experimental add-ons71025 | ||||
| Ref: #experimental-add-ons71179 | ||||
| Node: autosync71470 | ||||
| Ref: #autosync71584 | ||||
| Node: budget71823 | ||||
| Ref: #budget71947 | ||||
| Node: chart72013 | ||||
| Ref: #chart72132 | ||||
| Node: check72203 | ||||
| Ref: #check72307 | ||||
|  | ||||
| End Tag Table | ||||
|  | ||||
| @ -1404,12 +1404,13 @@ COMMANDS | ||||
|        --dry-run | ||||
|               just show the transactions to be imported | ||||
| 
 | ||||
|        Input  files are provided as arguments, or glob patterns.  So eg to add | ||||
|        new transactions from all CSV files to the main journal: hledger import | ||||
|        *.csv | ||||
|        The input files are specified as arguments - no need to write -f before | ||||
|        each one.  So eg to add new transactions from all CSV files to the main | ||||
|        journal, it's just: hledger import *.csv | ||||
| 
 | ||||
|        New  transactions  are  detected  like  print --new (using .latest.FILE | ||||
|        state files). | ||||
|        New transactions are detected in the same way as print --new: by assum- | ||||
|        ing transactions are always added to the input files in increasing date | ||||
|        order, and by saving .latest.FILE state files. | ||||
| 
 | ||||
|    incomestatement | ||||
|        Show an income statement.  Alias: is. | ||||
| @ -1418,7 +1419,7 @@ COMMANDS | ||||
|               show balance change in each period (default) | ||||
| 
 | ||||
|        --cumulative | ||||
|               show balance change accumulated across periods  (in  multicolumn | ||||
|               show  balance  change accumulated across periods (in multicolumn | ||||
|               reports), instead of changes during periods | ||||
| 
 | ||||
|        -H --historical | ||||
| @ -1452,8 +1453,8 @@ COMMANDS | ||||
|        --sort-amount | ||||
|               sort by amount instead of account name | ||||
| 
 | ||||
|        This  command displays a simple income statement.  It currently assumes | ||||
|        that you have top-level accounts named income (or revenue) and  expense | ||||
|        This command displays a simple income statement.  It currently  assumes | ||||
|        that  you have top-level accounts named income (or revenue) and expense | ||||
|        (plural forms also allowed.) | ||||
| 
 | ||||
|               $ hledger incomestatement | ||||
| @ -1478,8 +1479,8 @@ COMMANDS | ||||
|                                  0 | ||||
| 
 | ||||
|        With a reporting interval, multiple columns will be shown, one for each | ||||
|        report period.  Normally incomestatement  shows  revenues/expenses  per | ||||
|        period,  though  as  with multicolumn balance reports you can alter the | ||||
|        report  period.   Normally  incomestatement shows revenues/expenses per | ||||
|        period, though as with multicolumn balance reports you  can  alter  the | ||||
|        report mode with --change/--cumulative/--historical. | ||||
| 
 | ||||
|    prices | ||||
| @ -1489,7 +1490,7 @@ COMMANDS | ||||
|        Show transactions from the journal.  Aliases: p, txns. | ||||
| 
 | ||||
|        -m STR --match=STR | ||||
|               show the transaction whose description is most similar  to  STR, | ||||
|               show  the  transaction whose description is most similar to STR, | ||||
|               and is most recent | ||||
| 
 | ||||
|        --new  show only newer-dated transactions added in each file since last | ||||
| @ -1502,7 +1503,7 @@ COMMANDS | ||||
|               select the output format.  Supported formats: txt, csv. | ||||
| 
 | ||||
|        -o FILE --output-file=FILE | ||||
|               write output to FILE.  A file  extension  matching  one  of  the | ||||
|               write  output  to  FILE.   A  file extension matching one of the | ||||
|               above formats selects that format. | ||||
| 
 | ||||
|               $ hledger print | ||||
| @ -1533,39 +1534,39 @@ COMMANDS | ||||
|        it does not preserve directives or inter-transaction comments | ||||
| 
 | ||||
|        Normally, the journal entry's explicit or implicit amount style is pre- | ||||
|        served.   Ie when an amount is omitted in the journal, it will be omit- | ||||
|        ted in the output.  You can use the  -x/--explicit  flag  to  make  all | ||||
|        served.  Ie when an amount is omitted in the journal, it will be  omit- | ||||
|        ted  in  the  output.   You  can use the -x/--explicit flag to make all | ||||
|        amounts explicit, which can be useful for troubleshooting or for making | ||||
|        your journal more readable and robust against data entry errors.  Note, | ||||
|        -x  will  cause postings with a multi-commodity amount (these can arise | ||||
|        when a multi-commodity transaction has  an  implicit  amount)  will  be | ||||
|        split  into  multiple single-commodity postings, for valid journal out- | ||||
|        -x will cause postings with a multi-commodity amount (these  can  arise | ||||
|        when  a  multi-commodity  transaction  has  an implicit amount) will be | ||||
|        split into multiple single-commodity postings, for valid  journal  out- | ||||
|        put. | ||||
| 
 | ||||
|        With -B/--cost, amounts with transaction prices are converted  to  cost | ||||
|        With  -B/--cost,  amounts with transaction prices are converted to cost | ||||
|        using that price. | ||||
| 
 | ||||
|        With  -m/--match and a STR argument, print will show at most one trans- | ||||
|        action: the one one whose description is most similar to  STR,  and  is | ||||
|        most  recent.  STR should contain at least two characters.  If there is | ||||
|        With -m/--match and a STR argument, print will show at most one  trans- | ||||
|        action:  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. | ||||
| 
 | ||||
|        With --new, for each FILE being read, hledger reads (and writes) a spe- | ||||
|        cial  state  file  (.latest.FILE in the same directory), containing the | ||||
|        latest transaction date(s) that were seen  last  time  FILE  was  read. | ||||
|        When  this  file  is found, only transactions with newer dates (and new | ||||
|        transactions on the latest date)  are  printed.   This  is  useful  for | ||||
|        ignoring  already-seen  entries  in import data, such as downloaded CSV | ||||
|        cial state file (.latest.FILE in the same  directory),  containing  the | ||||
|        latest  transaction  date(s)  that  were  seen last time FILE was read. | ||||
|        When this file is found, only transactions with newer  dates  (and  new | ||||
|        transactions  on  the  latest  date)  are  printed.  This is useful for | ||||
|        ignoring already-seen entries in import data, such  as  downloaded  CSV | ||||
|        files.  Eg: | ||||
| 
 | ||||
|               $ hledger -f bank1.csv print --new | ||||
|               # shows transactions added since last print --new on this file | ||||
| 
 | ||||
|        This assumes that transactions  added  to  FILE  always  have  same  or | ||||
|        increasing  dates,  and  that  transactions  on the same day do not get | ||||
|        This  assumes  that  transactions  added  to  FILE  always have same or | ||||
|        increasing dates, and that transactions on the  same  day  do  not  get | ||||
|        reordered.  See also the import command. | ||||
| 
 | ||||
|        The print command also supports  output  destination  and  CSV  output. | ||||
|        The  print  command  also  supports  output destination and CSV output. | ||||
|        Here's an example of print's CSV output: | ||||
| 
 | ||||
|               $ hledger print -Ocsv | ||||
| @ -1582,20 +1583,20 @@ COMMANDS | ||||
|               "5","2008/12/31","","*","","pay off","","liabilities:debts","1","$","","1","","" | ||||
|               "5","2008/12/31","","*","","pay off","","assets:bank:checking","-1","$","1","","","" | ||||
| 
 | ||||
|        o There  is  one  CSV record per posting, with the parent transaction's | ||||
|        o There is one CSV record per posting, with  the  parent  transaction's | ||||
|          fields repeated. | ||||
| 
 | ||||
|        o The "txnidx" (transaction index) field shows which postings belong to | ||||
|          the  same transaction.  (This number might change if transactions are | ||||
|          reordered within the file, files are parsed/included in  a  different | ||||
|          the same transaction.  (This number might change if transactions  are | ||||
|          reordered  within  the file, files are parsed/included in a different | ||||
|          order, etc.) | ||||
| 
 | ||||
|        o The  amount  is  separated into "commodity" (the symbol) and "amount" | ||||
|        o The amount is separated into "commodity" (the  symbol)  and  "amount" | ||||
|          (numeric quantity) fields. | ||||
| 
 | ||||
|        o The numeric amount is repeated in either the "credit" or "debit" col- | ||||
|          umn,  for convenience.  (Those names are not accurate in the account- | ||||
|          ing sense; it just puts negative amounts under  credit  and  zero  or | ||||
|          umn, for convenience.  (Those names are not accurate in the  account- | ||||
|          ing  sense;  it  just  puts negative amounts under credit and zero or | ||||
|          greater amounts under debit.) | ||||
| 
 | ||||
|    print-unique | ||||
| @ -1608,7 +1609,7 @@ COMMANDS | ||||
|               show running total from report start date (default) | ||||
| 
 | ||||
|        -H --historical | ||||
|               show  historical running total/balance (includes postings before | ||||
|               show historical running total/balance (includes postings  before | ||||
|               report start date) | ||||
| 
 | ||||
|        -A --average | ||||
| @ -1619,18 +1620,18 @@ COMMANDS | ||||
|               show postings' siblings instead | ||||
| 
 | ||||
|        -w N --width=N | ||||
|               set  output  width  (default:  terminal width or COLUMNS.  -wN,M | ||||
|               set output width (default: terminal  width  or  COLUMNS.   -wN,M | ||||
|               sets description width as well) | ||||
| 
 | ||||
|        -O FMT --output-format=FMT | ||||
|               select the output format.  Supported formats: txt, csv. | ||||
| 
 | ||||
|        -o FILE --output-file=FILE | ||||
|               write output to FILE.  A file  extension  matching  one  of  the | ||||
|               write  output  to  FILE.   A  file extension matching one of the | ||||
|               above formats selects that format. | ||||
| 
 | ||||
|        The register command displays postings, one per line, and their running | ||||
|        total.  This is typically used with  a  query  selecting  a  particular | ||||
|        total.   This  is  typically  used  with a query selecting a particular | ||||
|        account, to see that account's activity: | ||||
| 
 | ||||
|               $ hledger register checking | ||||
| @ -1639,8 +1640,8 @@ COMMANDS | ||||
|               2008/06/02 save                 assets:bank:checking           $-1            $1 | ||||
|               2008/12/31 pay off              assets:bank:checking           $-1             0 | ||||
| 
 | ||||
|        The  --historical/-H  flag  adds the balance from any undisplayed prior | ||||
|        postings to the running total.  This is useful when  you  want  to  see | ||||
|        The --historical/-H flag adds the balance from  any  undisplayed  prior | ||||
|        postings  to  the  running  total.  This is useful when you want to see | ||||
|        only recent activity, with a historically accurate running balance: | ||||
| 
 | ||||
|               $ hledger register checking -b 2008/6 --historical | ||||
| @ -1650,23 +1651,23 @@ COMMANDS | ||||
| 
 | ||||
|        The --depth option limits the amount of sub-account detail displayed. | ||||
| 
 | ||||
|        The  --average/-A flag shows the running average posting amount instead | ||||
|        The --average/-A flag shows the running average posting amount  instead | ||||
|        of the running total (so, the final number displayed is the average for | ||||
|        the  whole  report period).  This flag implies --empty (see below).  It | ||||
|        is affected by --historical.  It  works  best  when  showing  just  one | ||||
|        the whole report period).  This flag implies --empty (see  below).   It | ||||
|        is  affected  by  --historical.   It  works  best when showing just one | ||||
|        account and one commodity. | ||||
| 
 | ||||
|        The  --related/-r  flag shows the other postings in the transactions of | ||||
|        The --related/-r flag shows the other postings in the  transactions  of | ||||
|        the postings which would normally be shown. | ||||
| 
 | ||||
|        With a reporting interval, register shows  summary  postings,  one  per | ||||
|        With  a  reporting  interval,  register shows summary postings, one per | ||||
|        interval, aggregating the postings to each account: | ||||
| 
 | ||||
|               $ hledger register --monthly income | ||||
|               2008/01                 income:salary                          $-1           $-1 | ||||
|               2008/06                 income:gifts                           $-1           $-2 | ||||
| 
 | ||||
|        Periods  with no activity, and summary postings with a zero amount, are | ||||
|        Periods with no activity, and summary postings with a zero amount,  are | ||||
|        not shown by default; use the --empty/-E flag to see them: | ||||
| 
 | ||||
|               $ hledger register --monthly income -E | ||||
| @ -1683,7 +1684,7 @@ COMMANDS | ||||
|               2008/11                                                          0           $-2 | ||||
|               2008/12                                                          0           $-2 | ||||
| 
 | ||||
|        Often, you'll want to see just one  line  per  interval.   The  --depth | ||||
|        Often,  you'll  want  to  see  just one line per interval.  The --depth | ||||
|        option helps with this, causing subaccounts to be aggregated: | ||||
| 
 | ||||
|               $ hledger register --monthly assets --depth 1h | ||||
| @ -1691,19 +1692,19 @@ COMMANDS | ||||
|               2008/06                 assets                                 $-1             0 | ||||
|               2008/12                 assets                                 $-1           $-1 | ||||
| 
 | ||||
|        Note  when using report intervals, if you specify start/end dates these | ||||
|        will be adjusted outward if necessary to  contain  a  whole  number  of | ||||
|        intervals.   This  ensures  that  the first and last intervals are full | ||||
|        Note when using report intervals, if you specify start/end dates  these | ||||
|        will  be  adjusted  outward  if  necessary to contain a whole number of | ||||
|        intervals.  This ensures that the first and  last  intervals  are  full | ||||
|        length and comparable to the others in the report. | ||||
| 
 | ||||
|    Custom register output | ||||
|        register uses the full terminal width by default,  except  on  windows. | ||||
|        You  can override this by setting the COLUMNS environment variable (not | ||||
|        register  uses  the  full terminal width by default, except on windows. | ||||
|        You can override this by setting the COLUMNS environment variable  (not | ||||
|        a bash shell variable) or by using the --width/-w option. | ||||
| 
 | ||||
|        The description and account columns normally share  the  space  equally | ||||
|        (about  half  of  (width  - 40) each).  You can adjust this by adding a | ||||
|        description width  as  part  of  --width's  argument,  comma-separated: | ||||
|        The  description  and  account columns normally share the space equally | ||||
|        (about half of (width - 40) each).  You can adjust  this  by  adding  a | ||||
|        description  width  as  part  of  --width's  argument, comma-separated: | ||||
|        --width W,D .  Here's a diagram: | ||||
| 
 | ||||
|               <--------------------------------- width (W) ----------------------------------> | ||||
| @ -1719,12 +1720,12 @@ COMMANDS | ||||
|               $ hledger reg -w 100,40           # set overall width 100, description width 40 | ||||
|               $ hledger reg -w $COLUMNS,40      # use terminal width, and set description width | ||||
| 
 | ||||
|        The  register  command also supports the -o/--output-file and -O/--out- | ||||
|        The register command also supports the -o/--output-file  and  -O/--out- | ||||
|        put-format options for controlling output destination and CSV output. | ||||
| 
 | ||||
|    register-match | ||||
|        Print the one posting whose transaction description is closest to DESC, | ||||
|        in  the  style  of  the register command.  Helps ledger-autosync detect | ||||
|        in the style of the register  command.   Helps  ledger-autosync  detect | ||||
|        already-seen transactions when importing. | ||||
| 
 | ||||
|    rewrite | ||||
| @ -1734,7 +1735,7 @@ COMMANDS | ||||
|        Show some journal statistics. | ||||
| 
 | ||||
|        -o FILE --output-file=FILE | ||||
|               write output to FILE.  A file  extension  matching  one  of  the | ||||
|               write  output  to  FILE.   A  file extension matching one of the | ||||
|               above formats selects that format. | ||||
| 
 | ||||
|               $ hledger stats | ||||
| @ -1749,8 +1750,8 @@ COMMANDS | ||||
|               Accounts                 : 8 (depth 3) | ||||
|               Commodities              : 1 ($) | ||||
| 
 | ||||
|        The  stats  command displays summary information for the whole journal, | ||||
|        or a matched part of it.  With a reporting interval, it shows a  report | ||||
|        The stats command displays summary information for the  whole  journal, | ||||
|        or  a matched part of it.  With a reporting interval, it shows a report | ||||
|        for each report period. | ||||
| 
 | ||||
|        The stats command also supports -o/--output-file for controlling output | ||||
| @ -1765,34 +1766,34 @@ COMMANDS | ||||
|               $ hledger test | ||||
|               Cases: 74  Tried: 74  Errors: 0  Failures: 0 | ||||
| 
 | ||||
|        This command runs hledger's built-in unit tests and  displays  a  quick | ||||
|        This  command  runs  hledger's built-in unit tests and displays a quick | ||||
|        report.  With a regular expression argument, it selects only tests with | ||||
|        matching names.  It's mainly used in development, but it's also nice to | ||||
|        be able to check your hledger executable for smoke at any time. | ||||
| 
 | ||||
| ADD-ON COMMANDS | ||||
|        hledger  also  searches  for external add-on commands, and will include | ||||
|        hledger also searches for external add-on commands,  and  will  include | ||||
|        these in the commands list.  These are programs or scripts in your PATH | ||||
|        whose  name starts with hledger- and ends with a recognised file exten- | ||||
|        whose name starts with hledger- and ends with a recognised file  exten- | ||||
|        sion (currently: no extension, bat,com,exe, hs,lhs,pl,py,rb,rkt,sh). | ||||
| 
 | ||||
|        Add-ons can be invoked like any hledger command, but there  are  a  few | ||||
|        Add-ons  can  be  invoked like any hledger command, but there are a few | ||||
|        things to be aware of.  Eg if the hledger-web add-on is installed, | ||||
| 
 | ||||
|        o hledger -h web  shows  hledger's  help,  while  hledger web -h  shows | ||||
|          hledger-web's help. | ||||
| 
 | ||||
|        o Flags specific to the add-on must have a preceding --  to  hide  them | ||||
|          from  hledger.   So hledger web --serve --port 9000 will be rejected; | ||||
|        o Flags  specific  to  the add-on must have a preceding -- to hide them | ||||
|          from hledger.  So hledger web --serve --port 9000 will  be  rejected; | ||||
|          you must use hledger web -- --serve --port 9000. | ||||
| 
 | ||||
|        o You   can    always    run    add-ons    directly    if    preferred: | ||||
|        o You    can    always    run    add-ons    directly    if   preferred: | ||||
|          hledger-web --serve --port 9000. | ||||
| 
 | ||||
|        Add-ons  are  a relatively easy way to add local features or experiment | ||||
|        with new ideas.  They can be  written  in  any  language,  but  haskell | ||||
|        scripts  have  a  big  advantage:  they  can  use the same hledger (and | ||||
|        haskell) library functions that built-in commands do, for  command-line | ||||
|        Add-ons are a relatively easy way to add local features  or  experiment | ||||
|        with  new  ideas.   They  can  be  written in any language, but haskell | ||||
|        scripts have a big advantage:  they  can  use  the  same  hledger  (and | ||||
|        haskell)  library functions that built-in commands do, for command-line | ||||
|        options, journal parsing, reporting, etc. | ||||
| 
 | ||||
|        Here are some hledger add-ons available: | ||||
| @ -1810,7 +1811,7 @@ ADD-ON COMMANDS | ||||
|        hledger-web provides a simple web interface. | ||||
| 
 | ||||
|    Third party add-ons | ||||
|        These  are  maintained  separately, and usually updated shortly after a | ||||
|        These are maintained separately, and usually updated  shortly  after  a | ||||
|        hledger release. | ||||
| 
 | ||||
|    diff | ||||
| @ -1818,7 +1819,7 @@ ADD-ON COMMANDS | ||||
|        journal file and another. | ||||
| 
 | ||||
|    iadd | ||||
|        hledger-iadd  is  a  curses-style, more interactive replacement for the | ||||
|        hledger-iadd is a curses-style, more interactive  replacement  for  the | ||||
|        add command. | ||||
| 
 | ||||
|    interest | ||||
| @ -1826,19 +1827,19 @@ ADD-ON COMMANDS | ||||
|        ing to various schemes. | ||||
| 
 | ||||
|    irr | ||||
|        hledger-irr  calculates  the  internal  rate of return of an investment | ||||
|        hledger-irr calculates the internal rate of  return  of  an  investment | ||||
|        account. | ||||
| 
 | ||||
|    Experimental add-ons | ||||
|        These are available in source form in the hledger  repo's  bin/  direc- | ||||
|        These  are  available  in source form in the hledger repo's bin/ direc- | ||||
|        tory; installing them is pretty easy.  They may be less mature and doc- | ||||
|        umented than built-in commands.  Reading and tweaking these is  a  good | ||||
|        umented  than  built-in commands.  Reading and tweaking these is a good | ||||
|        way to start making your own! | ||||
| 
 | ||||
|    autosync | ||||
|        hledger-autosync is a symbolic link for easily running ledger-autosync, | ||||
|        if installed.  ledger-autosync does  deduplicating  conversion  of  OFX | ||||
|        data  and some CSV formats, and can also download the data if your bank | ||||
|        if  installed.   ledger-autosync  does  deduplicating conversion of OFX | ||||
|        data and some CSV formats, and can also download the data if your  bank | ||||
|        offers OFX Direct Connect. | ||||
| 
 | ||||
|    budget | ||||
| @ -1851,21 +1852,21 @@ ADD-ON COMMANDS | ||||
|        hledger-check.hs checks more powerful account balance assertions. | ||||
| 
 | ||||
| ENVIRONMENT | ||||
|        COLUMNS The screen width used by the register  command.   Default:  the | ||||
|        COLUMNS  The  screen  width used by the register command.  Default: the | ||||
|        full terminal width. | ||||
| 
 | ||||
|        LEDGER_FILE The journal file path when not specified with -f.  Default: | ||||
|        ~/.hledger.journal (on  windows,  perhaps  C:/Users/USER/.hledger.jour- | ||||
|        ~/.hledger.journal  (on  windows,  perhaps C:/Users/USER/.hledger.jour- | ||||
|        nal). | ||||
| 
 | ||||
| FILES | ||||
|        Reads  data from one or more files in hledger journal, timeclock, time- | ||||
|        dot,  or  CSV  format  specified   with   -f,   or   $LEDGER_FILE,   or | ||||
|        $HOME/.hledger.journal           (on          windows,          perhaps | ||||
|        Reads data from one or more files in hledger journal, timeclock,  time- | ||||
|        dot,   or   CSV   format   specified   with  -f,  or  $LEDGER_FILE,  or | ||||
|        $HOME/.hledger.journal          (on          windows,           perhaps | ||||
|        C:/Users/USER/.hledger.journal). | ||||
| 
 | ||||
| BUGS | ||||
|        The need to precede addon command options with  --  when  invoked  from | ||||
|        The  need  to  precede  addon command options with -- when invoked from | ||||
|        hledger is awkward. | ||||
| 
 | ||||
|        When input data contains non-ascii characters, a suitable system locale | ||||
| @ -1878,33 +1879,33 @@ BUGS | ||||
|        In a Cygwin/MSYS/Mintty window, the tab key is not supported in hledger | ||||
|        add. | ||||
| 
 | ||||
|        Not  all of Ledger's journal file syntax is supported.  See file format | ||||
|        Not all of Ledger's journal file syntax is supported.  See file  format | ||||
|        differences. | ||||
| 
 | ||||
|        On large data files, hledger  is  slower  and  uses  more  memory  than | ||||
|        On  large  data  files,  hledger  is  slower  and uses more memory than | ||||
|        Ledger. | ||||
| 
 | ||||
| TROUBLESHOOTING | ||||
|        Here  are  some  issues  you  might encounter when you run hledger (and | ||||
|        remember you can also seek help from the IRC channel, mail list or  bug | ||||
|        Here are some issues you might encounter  when  you  run  hledger  (and | ||||
|        remember  you can also seek help from the IRC channel, mail list or bug | ||||
|        tracker): | ||||
| 
 | ||||
|        Successfully installed, but "No command 'hledger' found" | ||||
|        stack and cabal install binaries into a special directory, which should | ||||
|        be added to your PATH environment variable.  Eg on  unix-like  systems, | ||||
|        be  added  to your PATH environment variable.  Eg on unix-like systems, | ||||
|        that is ~/.local/bin and ~/.cabal/bin respectively. | ||||
| 
 | ||||
|        I set a custom LEDGER_FILE, but hledger is still using the default file | ||||
|        LEDGER_FILE should be a real environment variable,  not  just  a  shell | ||||
|        variable.   The command env | grep LEDGER_FILE should show it.  You may | ||||
|        LEDGER_FILE  should  be  a  real environment variable, not just a shell | ||||
|        variable.  The command env | grep LEDGER_FILE should show it.  You  may | ||||
|        need to use export.  Here's an explanation. | ||||
| 
 | ||||
|        "Illegal byte sequence" or "Invalid or  incomplete  multibyte  or  wide | ||||
|        "Illegal  byte  sequence"  or  "Invalid or incomplete multibyte or wide | ||||
|        character" errors | ||||
|        In order to handle non-ascii letters and symbols (like ), hledger needs | ||||
|        an appropriate locale.  This is usually configured system-wide; you can | ||||
|        also configure it temporarily.  The locale may need to be one that sup- | ||||
|        ports UTF-8, if you built hledger with GHC < 7.2 (or  possibly  always, | ||||
|        ports  UTF-8,  if you built hledger with GHC < 7.2 (or possibly always, | ||||
|        I'm not sure yet). | ||||
| 
 | ||||
|        Here's  an  example  of  setting  the  locale  temporarily,  on  ubuntu | ||||
| @ -1923,7 +1924,7 @@ TROUBLESHOOTING | ||||
|               $ echo "export LANG=en_US.UTF-8" >>~/.bash_profile | ||||
|               $ bash --login | ||||
| 
 | ||||
|        If we preferred to use eg fr_FR.utf8, we might  have  to  install  that | ||||
|        If  we  preferred  to  use eg fr_FR.utf8, we might have to install that | ||||
|        first: | ||||
| 
 | ||||
|               $ apt-get install language-pack-fr | ||||
| @ -1944,7 +1945,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) | ||||
| 
 | ||||
| 
 | ||||
| @ -1958,7 +1959,7 @@ COPYRIGHT | ||||
| 
 | ||||
| 
 | ||||
| SEE ALSO | ||||
|        hledger(1),      hledger-ui(1),     hledger-web(1),     hledger-api(1), | ||||
|        hledger(1),     hledger-ui(1),     hledger-web(1),      hledger-api(1), | ||||
|        hledger_csv(5), hledger_journal(5), hledger_timeclock(5), hledger_time- | ||||
|        dot(5), ledger(1) | ||||
| 
 | ||||
|  | ||||
		Loading…
	
		Reference in New Issue
	
	Block a user