Initial chapter on time-keeping in ledger3.texi
This commit is contained in:
parent
eed1d8e53e
commit
70bbc81299
1 changed files with 32 additions and 2 deletions
|
|
@ -75,6 +75,7 @@ twinkling in their father's CRT.
|
||||||
* Reporting Commands::
|
* Reporting Commands::
|
||||||
* Command-line Syntax::
|
* Command-line Syntax::
|
||||||
* Budgeting and Forecasting::
|
* Budgeting and Forecasting::
|
||||||
|
* Time Keeping::
|
||||||
* Value Expressions::
|
* Value Expressions::
|
||||||
* Format Strings::
|
* Format Strings::
|
||||||
* Extending with Python::
|
* Extending with Python::
|
||||||
|
|
@ -6389,7 +6390,7 @@ weekly last august
|
||||||
@end smallexample
|
@end smallexample
|
||||||
|
|
||||||
|
|
||||||
@node Budgeting and Forecasting, Value Expressions, Command-line Syntax, Top
|
@node Budgeting and Forecasting, Time Keeping, Command-line Syntax, Top
|
||||||
@chapter Budgeting and Forecasting
|
@chapter Budgeting and Forecasting
|
||||||
|
|
||||||
@menu
|
@menu
|
||||||
|
|
@ -6485,8 +6486,37 @@ only, and not against the running total:
|
||||||
ledger --forecast "d<[2010]" bal ^assets ^liabilities
|
ledger --forecast "d<[2010]" bal ^assets ^liabilities
|
||||||
@end example
|
@end example
|
||||||
|
|
||||||
|
@node Time Keeping, Value Expressions, Budgeting and Forecasting, Top
|
||||||
|
@chapter Time Keeping
|
||||||
|
|
||||||
@node Value Expressions, Format Strings, Budgeting and Forecasting, Top
|
|
||||||
|
Ledger directly supports ``timelog'' entries, which have this form:
|
||||||
|
|
||||||
|
@smallexample
|
||||||
|
i 2013/03/28 22:13:00 ACCOUNT[ PAYEE]
|
||||||
|
o 2013/03/29 03:39:00
|
||||||
|
@end smallexample
|
||||||
|
|
||||||
|
This records a check-in to the given ACCOUNT, and a check-out. You can
|
||||||
|
be checked-in to multiple accounts at a time, if you wish, and they can
|
||||||
|
span multiple days (use @code{--day-break} to break them up in the
|
||||||
|
report). The number of seconds between is accumulated as time to that
|
||||||
|
ACCOUNT. If the checkout uses a capital ``O'', the transaction is marked
|
||||||
|
``cleared''. You can use an optional PAYEE for whatever meaning you like.
|
||||||
|
|
||||||
|
Now, there are a few ways to generate this information. You can use the
|
||||||
|
@file{timeclock.el} package, which is part of Emacs. Or you can write a
|
||||||
|
simple script in whichever language you prefer to emit similar
|
||||||
|
information. Or you can use Org-mode's time-clocking abilities and the
|
||||||
|
org2tc script developed by John Wiegly.
|
||||||
|
|
||||||
|
These timelog entries can appear in a separate file, or directly in your
|
||||||
|
main ledger file. The initial "i" and "o" count as Ledger "directives",
|
||||||
|
and are accepted anywhere that ordinary transactions are.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
@node Value Expressions, Format Strings, Time Keeping, Top
|
||||||
@chapter Value Expressions
|
@chapter Value Expressions
|
||||||
|
|
||||||
Ledger uses value expressions to make calculations for many different
|
Ledger uses value expressions to make calculations for many different
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue