Removed references to 'cache' option

This commit is contained in:
Craig Earls 2011-11-11 23:05:01 -07:00 committed by John Wiegley
parent 70e86719ea
commit bd00b04bfc

View file

@ -5,7 +5,7 @@
@dircategory User Applications
@copying
Copyright (c) 2003-2010, John Wiegley. All rights reserved.
Copyright (c) 2003-2011, John Wiegley. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
@ -45,7 +45,7 @@ OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
@titlepage
@title Ledger: Command-Line Accounting
@subtitle For Version 3.0 of Ledger
@subtitle Draft Manual Time-stamp: <2011-11-11 22:27 (cpearls)>
@subtitle Draft Manual Time-stamp: <2011-11-11 22:56 (cpearls)>
@author John Wiegley
@end titlepage
@ -285,6 +285,7 @@ to @xref{Keeping a Journal}.
* Balance Report::
* Register Report::
* Cleared Report::
* Using the Windows command line::
@end menu
@node Balance Report, Register Report, Run Some Reports, Run Some Reports
@ -417,7 +418,7 @@ $ ledger -f drewr3.dat register payee "Organic"
Assets:Checking $ -225.00 0
@end smallexample
@node Cleared Report, , Register Report, Run Some Reports
@node Cleared Report, Using the Windows command line, Register Report, Run Some Reports
@subsection Cleared Report
A very useful report is to show what your obligations are versus what
@ -450,6 +451,12 @@ $ ledger -f drewr3.dat cleared
@end smallexample
@noindent The first column shows the outstanding balance, the second column show the ``cleared'' balance.
@node Using the Windows command line, , Cleared Report, Run Some Reports
@subsection Using the Windows Command Line
Using ledger under the windows command shell has one significant
limitation. CMD.exe is limited to standard ASCII characters and as such
cannot display any currency symbols other than dollar signs ($).
@node Command Line Quick Reference, , Run Some Reports, Ledger Tutorial
@section Command Line Quick Reference
@ -488,7 +495,6 @@ $ ledger -f drewr3.dat cleared
@item @code{-f FILE} @tab @code{--file FILE} @tab read @file{FILE} as a ledger file
@item @code{-o FILE} @tab @code{--output FILE} @tab redirects output to @file{FILE}
@item @code{-i FILE} @tab @code{--init-file FILE} @tab specify options file
@item @tab @code{--cache FILE} @tab specify binary cache file
@item @code{-a NAME} @tab @code{--account NAME} @tab specify default account name for QIF file postings
@end multitable
@ -2584,7 +2590,6 @@ option on it's own line. Here's an example init file:
@smallexample
--price-db ~/finance/.pricedb
--cache /tmp/ledger-cache
; ~/.ledgerrc ends here
@end smallexample
@ -2592,14 +2597,6 @@ option on it's own line. Here's an example init file:
Option settings on the command-line or in the environment always take
precedence over settings in the init file.
@option{--cache FILE} identifies FILE as the default binary cache
file. That is, if the ledger files to be read are specified using the
environment variable @env{LEDGER_FILE}, then whenever a command is
finished a binary copy will be written to the specified cache, to
speed up the loading time of subsequent queries. This filename can
also be given using the environment variable @env{LEDGER_CACHE}, or by
putting the option into your init file. The @option{--no-cache}
option causes Ledger to always ignore the binary cache.
@option{--account NAME} (@option{-a NAME}) specifies the default
account which QIF file postings are assumed to relate to.
@ -2945,7 +2942,6 @@ Note that you may also permanently specify option values by placing
option settings in the file @file{~/.ledgerrc}, for example:
@smallexample
--cache /tmp/.mycache
--pager /bin/cat
@end smallexample