From 18eb49c49439c7664e4179e28f4213954c5e7c8c Mon Sep 17 00:00:00 2001 From: Julian Gehring Date: Sat, 4 Jun 2011 23:07:41 +0200 Subject: [PATCH] add corrections to org manual --- doc/org.texi | 32 +++++++++++++++++--------------- 1 files changed, 17 insertions(+), 15 deletions(-) diff --git a/doc/org.texi b/doc/org.texi index eb97759..182219e 100644 --- a/doc/org.texi +++ b/doc/org.texi @@ -4025,7 +4025,7 @@ called ``habits''. A habit has the following properties: You have enabled the @code{habits} module by customizing the variable @code{org-modules}. @item -The habit is a TODO, with a TODO keyword representing an open state. +The habit is a TODO item, with a TODO keyword representing an open state. @item The property @code{STYLE} is set to the value @code{habit}. @item @@ -4941,7 +4941,7 @@ optional. The individual parts have the following meaning: @var{property} @r{The property that should be edited in this column.} @r{Special properties representing meta data are allowed here} @r{as well (@pxref{Special properties})} -@var{title} @r{The header text for the column. If omitted, the property} +@var{title} @r{The header text for the column. If omitted, the property} @r{name is used.} @{@var{summary-type}@} @r{The summary type. If specified, the column values for} @r{parent nodes are computed from the children.} @@ -6131,7 +6131,7 @@ not started at exactly the right moment. @kindex ; Calling @code{org-timer-set-timer} from an Org-mode buffer runs a countdown -timer. Use @key{;} from agenda buffers, @key{C-c C-x ;} everwhere else. +timer. Use @kbd{;} from agenda buffers, @kbd{C-c C-x ;} everwhere else. @code{org-timer-set-timer} prompts the user for a duration and displays a countdown timer in the modeline. @code{org-timer-default-timer} sets the @@ -6999,7 +6999,7 @@ Lift the restriction. @cindex agenda dispatcher @cindex dispatching agenda commands The views are created through a dispatcher, which should be bound to a -global key---for example @kbd{C-c a} (@pxref{Installation}). In the +global key---for example @kbd{C-c a} (@pxref{Activation}). In the following we will assume that @kbd{C-c a} is indeed how the dispatcher is accessed and list keyboard access to commands accordingly. After pressing @kbd{C-c a}, an additional letter is required to execute a @@ -8396,7 +8396,7 @@ version of some agenda views to carry around. Org-mode can export custom agenda views as plain text, HTML@footnote{You need to install Hrvoje Niksic's @file{htmlize.el}.}, Postscript, PDF@footnote{To create PDF output, the ghostscript @file{ps2pdf} utility must be installed on the system. Selecting -a PDF file with also create the postscript file.}, and iCalendar files. If +a PDF file will also create the postscript file.}, and iCalendar files. If you want to do this only occasionally, use the command @table @kbd @@ -8940,8 +8940,8 @@ If the syntax for the label format conflicts with the language syntax, use a @code{-l} switch to change the format, for example @samp{#+BEGIN_SRC pascal -n -r -l "((%s))"}. See also the variable @code{org-coderef-label-format}. -HTML export also allows examples to be published as text areas, @xref{Text -areas in HTML export}. +HTML export also allows examples to be published as text areas (@xref{Text +areas in HTML export}). Because the @code{#+BEGIN_...} and @code{#+END_...} patterns need to be added so often, shortcuts are provided using the Easy Templates facility @@ -9641,8 +9641,8 @@ language, but with additional support for tables. @table @kbd @orgcmd{C-c C-e h,org-export-as-html} @cindex property, EXPORT_FILE_NAME -Export as HTML file @file{myfile.html}. For an Org file @file{myfile.org}, -the ASCII file will be @file{myfile.html}. The file will be overwritten +Export as HTML file. For an Org file @file{myfile.org}, +the HTML file will be @file{myfile.html}. The file will be overwritten without warning. If there is an active region@footnote{This requires @code{transient-mark-mode} be turned on.}, only the region will be exported. If the selected region is a single tree@footnote{To select the @@ -10057,8 +10057,8 @@ sections. @table @kbd @orgcmd{C-c C-e l,org-export-as-latex} @cindex property EXPORT_FILE_NAME -Export as @LaTeX{} file @file{myfile.tex}. For an Org file -@file{myfile.org}, the ASCII file will be @file{myfile.tex}. The file will +Export as @LaTeX{} file. For an Org file +@file{myfile.org}, the @LaTeX{} file will be @file{myfile.tex}. The file will be overwritten without warning. If there is an active region@footnote{This requires @code{transient-mark-mode} be turned on.}, only the region will be exported. If the selected region is a single tree@footnote{To select the @@ -10710,7 +10710,8 @@ The Freemind exporter was written by Lennart Borgman. @table @kbd @orgcmd{C-c C-e m,org-export-as-freemind} -Export as Freemind mind map @file{myfile.mm}. +Export as Freemind mind map. For an Org file @file{myfile.org}, the Freemind +file will be @file{myfile.mm}. @end table @node XOXO export, iCalendar export, Freemind export, Exporting @@ -10723,7 +10724,8 @@ does not interpret any additional Org-mode features. @table @kbd @orgcmd{C-c C-e x,org-export-as-xoxo} -Export as XOXO file @file{myfile.html}. +Export as XOXO file. For an Org file @file{myfile.org}, the XOXO file will be +@file{myfile.html}. @orgkey{C-c C-e v x} Export only the visible part of the document. @end table @@ -12448,7 +12450,7 @@ interpreted language. The @code{:noweb} header argument controls expansion of ``noweb'' style (see @ref{Noweb reference syntax}) references in a code block. This header -argument can have one of three values: @code{yes} @code{no} or @code{tangle}. +argument can have one of three values: @code{yes}, @code{no}, or @code{tangle}. @itemize @bullet @item @code{yes} @@ -14880,7 +14882,7 @@ and to read captured notes from there. This operation copies all files currently listed in @code{org-mobile-files} to the directory @code{org-mobile-directory}. By default this list contains all agenda files (as listed in @code{org-agenda-files}), but additional files -can be included by customizing @code{org-mobiles-files}. File names will be +can be included by customizing @code{org-mobile-files}. File names will be staged with paths relative to @code{org-directory}, so all files should be inside this directory. The push operation also creates a special Org file @file{agendas.org} with all custom agenda view defined by the -- 1.7.4.1