| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
[skip ci]
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Currently, collapsing is only done when both --depth and --collapse are
present. This is very unintuitive and I have even stumbled over this
myself while implenting the feature.
Change --depth to behave just like --collapse in all cases (except that
--depth has a parameter associated. --collapse defaults to 0 to retain
its old behavior).
|
|
|
|
| |
Use the value from --depth as the collapse_depth for --collapse.
|
| |
|
|
|
|
| |
[ci skip]
|
|
|
|
| |
[ci skip]
|
| |
|
|
|
|
| |
[ci skip]
|
|
|
|
|
|
| |
The following script makes it a no-brainer:
% NEXT_YEAR=2015; ag -l 'Copyright.*Wiegley' \
| xargs sed -i '' -e "s/\(Copyright.*\)-20[0-9]\{2\}/\1-${NEXT_YEAR}/"
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
For example, -A and -V used to override each other, whereas now:
-A report the average amount
-V report all amounts at current value
-AV report the current value of the average
-VA report the average of all current values
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
1. A bounded budget "from DATE to DATE" will now generate entries
throughout that entire range, if it is triggered.
2. An unbounded budget begins, as before, in the timeframe of the
reported posting which triggered it, but now continues until the
present date.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If you have a typed metadata key which contains an amount, you can use
--inject=KEY to inject a posting with that amount wherever a match
occurs. There are two main forms of usage:
2010-06-18 Sample
; Key:: $100
Expenses:Food $100.00
Assets:Checking
The command would be:
ledger reg --inject=Key
In the above, transactional form, a posting under the account "Key" will
be injected before the first posting reported for this transaction.
It's amount will be $100. This only happens once for the whole
transaction.
It is also possible to associate the key with a posting:
2010-06-18 Sample
Expenses:Food $100.00
; Key:: $100
Assets:Checking
Now the injected posting is generated whenever that particular post is
reported.
|
| |
|
| |
|
| |
|
|
|
|
| |
Fixes #188 / 53BCED29-F3B9-4E02-9A35-6C739ABB9662
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The --group-by option allows for most reports to be split up into
sections based on the varying value of EXPR. For example, to see
register subtotals by payee, use:
ledger reg --group-by=payee -s
This works for separated balances too:
ledger bal --group-by=payee
Another interesting possibility is seeing a register of all the accounts
affected by a related account:
ledger reg -r --group-by=payee
The option --group-title-format can be used to add a separator bar to
the group titles. The option --no-titles can be used to drop titles
altogether.
|
| |
|
|
|
|
|
|
|
|
| |
The purpose of this option is to add special "<Rounding>" postings, to
ensure that a regiter's running total is *always* the sum of its
postings. Within --rounding, these adjustment postings are missing,
which was the behavior in Ledger 2.x. It can be orders of magnitude
slower to turn it on for large reports with many commodities.
|
| |
|
|
|
|
| |
The switches the default back to the same as 2.x, which is --unsorted.
|
| |
|
|
|
|
|
|
| |
This is equivalent to the following:
--account='"TAG:" + tag(/TAG/)'
|
|
|
|
|
|
| |
When this option is on, then in balance report which show market values,
any gains or losses in value will be balanced into a pair of accounts
called Equity:Unrealized Gains and Equity:Unrealized Losses.
|
| |
|
| |
|
|
|
|
|
|
| |
It used to be "account_wise", since it only happens for non-account-wise
reports. Now it's called just "calc_running_total", so anyone can
request it.
|
| |
|
|
|
|
|
|
|
| |
This lets you do things like store a date as the value of a tag, then
run:
ledger --date='has_tag("Foo") ? to_date(tag("Foo")) : date' reg
|
| |
|
|
|
|
|
|
|
| |
This fits better with the --amount and --total options, which both
change the amount and total used for calculation. Same with --account:
it happens after filtering, but before calculation so that balance
reports look as you'd expect.
|
| |
|
|
|
|
|
| |
This sets how many years of forecasting Ledger will do before it
terminates the attempt.
|
|
|
|
| |
The journal_t now completely represents the data part of a session.
|
| |
|
| |
|
| |
|
| |
|