To see options for a particular command, including command-specificĬommand-specific options must be written after the command name, eg:Īdditionally, if the command is an addon, you may need to Some reporting options can also be written as query When a reporting option appears more than once in the command line, the Rules to generate future transactions, to 6 months from now or : convert amounts to their market value on the report end date (using : convert amounts to their cost at transaction time (using the : show items with zero amount, normally hidden
: hide/aggregate accounts or postings more than NUM levels deep : include only unmarked postings/txns (can combine with -P or -C)
: match the secondary date instead (see command help for other : set start date, end date, and/or reporting interval all at once : multiperiod/multicolumn report by quarter : multiperiod/multicolumn report by month : include postings/txns on or after this date : use some other field or tag for the account name : Conversion rules file to use when reading CSV (default: les) : show debug output (levels 1-9, default: 1) : show general usage (or after COMMAND, command usage) To see general usage help, including general options which are supportedīy most hledger commands, run hledger -h. $ hledger activity -W # show transaction counts per week as a bar chart $ hledger print desc:shop # show transactions with shop in the description $ hledger reg 'assets:some bank:checking' # show postings to/from this checking account $ hledger reg income # show postings to/from income accounts $ hledger register # show account postings, with running total $ hledger balance -depth 1 # only top-level accounts $ hledger balance -help # show detailed help for balance command $ hledger balance # all accounts with aggregated balances $ hledger add # add more transactions to the journal file More commands: $ hledger # show available commands Two simple transactions in hledger journal format: 0 gift received Hledger with no arguments for a list of commands. Try some commands like hledger print or hledger balance. ~/.hledger.journal, or run hledger add and follow the prompts. To get started, you can either save some entries like the above in hledger's interactiveĪdd command is another way to record new transactions. Mode such as ledger-mode for added convenience. Most users use a text editor to edit the journal, usually with an editor Transactions are dated movements of money between two (or more) namedĪccounts, and are recorded with journal entries like this: 6 bought foodįor more about this format, see hledger_journal(5). Must be a real environment variable, not a shell variable.
$HOME/.hledger.journal (on windows, perhapsĬ:/Users/USER/.hledger.journal). Timedot, or CSV format specified with -f, or $LEDGER_FILE, or Hledger reads data from one or more files in hledger journal, timeclock, Additionally, hledger lists other hledger-*Įxecutables found in the user's $PATH and can invoke them as hledgerĬan also read some other file formats such as CSV files, translating Print useful reports on standard output, or export them as CSV. Its basic function is to read a plain text file describingįinancial transactions (in accounting terms, a general journal) and This is hledger's command-line interface (there are also curses and web Tested on unix, mac, windows, hledger aims to be a reliable, practical hledger is inspired by and largely compatible with Other commodity, using double-entry accounting and a simple, editableįile format. Hledger is a cross-platform program for tracking money, time, or any Hledger - a command-line accounting tool SYNOPSIS -p "every 2nd day of week" - periods will go from Tue to Tue -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 2 weeks" - starts on closest preceeding Monday -p "every 5 month from 2009/03" - periods will have boundaries on 1, 1. -p "bimonthly from 2008" - periods will have boundaries on 1, 1.-p "weekly from to " - starts on 9, closest preceeding Monday -p "monthly in 5" - starts on 1 -p "quarterly from to " - starts on 1, ends on 0, which are first and last days of Q2 2009 -p "yearly from " - starts on 1, first day of 2009.-p "weekly from to "``-p "monthly in 2008"``-p "quarterly".
0 kommentar(er)
