sfos/ledger
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Fix @node pointer errors

Browse source 
Unfortunately, you cannot reliably use periods, commas, or colons within
a node name; these can confuse the Info reader.
This commit is contained in:
Jamie Nguyen 2014-04-27 19:15:15 +01:00
parent 04d147c9a7
commit 507fac7e50
1 changed files with 11 additions and 11 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
doc/ledger3.texi
View file

@ -2693,7 +2693,7 @@ doing it.
* Total posting costs:: * Total posting costs::
* Virtual posting costs:: * Virtual posting costs::
* Commodity prices:: * Commodity prices::
* Prices vs. costs:: * Prices versus costs::
* Fixated prices and costs:: * Fixated prices and costs::
* Lot dates:: * Lot dates::
* Lot notes:: * Lot notes::
@ -3296,7 +3296,7 @@ happening in the case of an exceptional transaction, surround the
Income:Gifts Received Income:Gifts Received
@end smallexample @end smallexample
@node Commodity prices, Prices vs. costs, Virtual posting costs, Transactions @node Commodity prices, Prices versus costs, Virtual posting costs, Transactions
@section Commodity prices @section Commodity prices
@findex --lot-prices @findex --lot-prices
@ -3424,8 +3424,8 @@ And in cases where the amounts do not divide into whole figures and
must be rounded, the capital gains figure could be off by a cent. Use must be rounded, the capital gains figure could be off by a cent. Use
with caution. with caution.
@node Prices vs. costs, Fixated prices and costs, Commodity prices, Transactions @node Prices versus costs, Fixated prices and costs, Commodity prices, Transactions
@section Prices vs. costs @section Prices versus costs
Because lot pricing provides enough information to infer the cost, the Because lot pricing provides enough information to infer the cost, the
following two transactions are equivalent: following two transactions are equivalent:
@ -3445,7 +3445,7 @@ example in the print report. Functionally, however, there is no
difference, and neither the register nor the balance report are difference, and neither the register nor the balance report are
sensitive to this difference. sensitive to this difference.
@node Fixated prices and costs, Lot dates, Prices vs. costs, Transactions @node Fixated prices and costs, Lot dates, Prices versus costs, Transactions
@section Fixated prices and costs @section Fixated prices and costs
If you buy a stock last year, and ask for its value today, Ledger will If you buy a stock last year, and ask for its value today, Ledger will
@ -3476,7 +3476,7 @@ fixated prices by way of the cost:
@end smallexample @end smallexample
This is the same as the previous transaction, with the same caveats This is the same as the previous transaction, with the same caveats
found in @ref{Prices vs. costs}. found in @ref{Prices versus costs}.
@node Lot dates, Lot notes, Fixated prices and costs, Transactions @node Lot dates, Lot notes, Fixated prices and costs, Transactions
@section Lot dates @section Lot dates
@ -8458,13 +8458,13 @@ make sense later.
@menu @menu
* Basic data traversal:: * Basic data traversal::
* Raw vs. Cooked:: * Raw versus Cooked::
* Queries:: * Queries::
* Embedded Python:: * Embedded Python::
* Amounts:: * Amounts::
@end menu @end menu
@node Basic data traversal, Raw vs. Cooked, Extending with Python, Extending with Python @node Basic data traversal, Raw versus Cooked, Extending with Python, Extending with Python
@section Basic data traversal @section Basic data traversal
Every interaction with Ledger happens in the context of a Session. Every interaction with Ledger happens in the context of a Session.
@ -8491,8 +8491,8 @@ for xact in ledger.read_journal("sample.dat").xacts:
print "Transferring %s to/from %s" % (post.amount, post.account) print "Transferring %s to/from %s" % (post.amount, post.account)
@end smallexample @end smallexample
@node Raw vs. Cooked, Queries, Basic data traversal, Extending with Python @node Raw versus Cooked, Queries, Basic data traversal, Extending with Python
@section Raw vs. Cooked @section Raw versus Cooked
Ledger data exists in one of two forms: raw and cooked. Raw objects are Ledger data exists in one of two forms: raw and cooked. Raw objects are
what you get from a traversal like the above, and represent exactly what what you get from a traversal like the above, and represent exactly what
@ -8556,7 +8556,7 @@ does it transaction-wise. It relies on the fact that an unsorted report
returns postings in the exact order they were parsed from the journal returns postings in the exact order they were parsed from the journal
file. file.
@node Queries, Embedded Python, Raw vs. Cooked, Extending with Python @node Queries, Embedded Python, Raw versus Cooked, Extending with Python
@section Queries @section Queries
The Journal.query() method accepts every argument you can specify on the The Journal.query() method accepts every argument you can specify on the