From e9994aad8e343c17a32e03cb1de139cdd4c100fb Mon Sep 17 00:00:00 2001 From: Julian Gehring Date: Sat, 4 Jun 2011 23:09:32 +0200 Subject: [PATCH] add suggestions to org manual --- doc/org.texi | 30 +++++++++++++++--------------- 1 files changed, 15 insertions(+), 15 deletions(-) diff --git a/doc/org.texi b/doc/org.texi index eb97759..d6fd5d9 100644 --- a/doc/org.texi +++ b/doc/org.texi @@ -1949,7 +1949,7 @@ C-u} forces TAB, and a numeric argument N indicates that at least N consecutive spaces, or alternatively a TAB will be the separator. @* If there is no active region, this command creates an empty Org -table. But it's easier just to start typing, like +table. But it is easier just to start typing, like @kbd{|Name|Phone|Age @key{RET} |- @key{TAB}}. @tsubheading{Re-aligning and field motion} @@ -3570,7 +3570,7 @@ entire buffer, but shows all TODO items (with not-DONE state) and the headings hierarchy above them. With a prefix argument (or by using @kbd{C-c / T}), search for a specific TODO. You will be prompted for the keyword, and you can also give a list of keywords like @code{KWD1|KWD2|...} to list -entries that match any one of these keywords. With numeric prefix argument +entries that match any one of these keywords. With a numeric prefix argument N, show the tree for the Nth keyword in the variable @code{org-todo-keywords}. With two prefix arguments, find all TODO states, both un-done and done. @@ -3741,8 +3741,8 @@ key after each keyword, in parentheses. For example: @end lisp @vindex org-fast-tag-selection-include-todo -If you then press @code{C-c C-t} followed by the selection key, the entry -will be switched to this state. @key{SPC} can be used to remove any TODO +If you then press @kbd{C-c C-t} followed by the selection key, the entry +will be switched to this state. @kbd{SPC} can be used to remove any TODO keyword from an entry.@footnote{Check also the variable @code{org-fast-tag-selection-include-todo}, it allows you to change the TODO state through the tags interface (@pxref{Setting tags}), in case you like to @@ -4039,8 +4039,8 @@ syntax @samp{.+2d/3d}, which says that you want to do the task at least every three days, but at most every two days. @item You must also have state logging for the @code{DONE} state enabled, in order -for historical data to be represented in the consistency graph. If it's not -enabled it's not an error, but the consistency graphs will be largely +for historical data to be represented in the consistency graph. If it is not +enabled it is not an error, but the consistency graphs will be largely meaningless. @end enumerate @@ -4098,7 +4098,7 @@ habits are displayed in the agenda. @table @code @item org-habit-graph-column The buffer column at which the consistency graph should be drawn. This will -overwrite any text in that column, so it's a good idea to keep your habits' +overwrite any text in that column, so it is a good idea to keep your habits' titles brief and to the point. @item org-habit-preceding-days The amount of history, in days before today, to appear in consistency graphs. @@ -4437,7 +4437,7 @@ When the cursor is in a headline, this does the same as @kbd{C-c C-q}. @end table @vindex org-tag-alist -Org will support tag insertion based on a @emph{list of tags}. By +Org supports tag insertion based on a @emph{list of tags}. By default this list is constructed dynamically, containing all tags currently used in the buffer. You may also globally specify a hard list of tags with the variable @code{org-tag-alist}. Finally you can set @@ -6015,7 +6015,7 @@ If you restart Emacs and clock into any task, Org will notice that you have a dangling clock which was never clocked out from your last session. Using that clock's starting time as the beginning of the unaccounted-for period, Org will ask how you want to resolve that time. The logic and behavior is -identical to dealing with away time due to idleness; it's just happening due +identical to dealing with away time due to idleness; it is just happening due to a recovery event rather than a set amount of idle time. You can also check all the files visited by your Org agenda for dangling @@ -6052,7 +6052,7 @@ together with clock sums (if you want to clock your time). For a specific buffer you can use @example -#+PROPERTY: Effort_ALL 0 0:10 0:30 1:00 2:00 3:00 4:00 5:00 6:00 7:00 8:00 +#+PROPERTY: Effort_ALL 0 0:10 0:30 1:00 2:00 3:00 4:00 5:00 6:00 7:00 #+COLUMNS: %40ITEM(Task) %17Effort(Estimated Effort)@{:@} %CLOCKSUM @end example @@ -6497,8 +6497,8 @@ similar way.}: @vindex org-from-is-user-regexp @smallexample -Link type | Available keywords --------------------+---------------------------------------------- +Link type | Available keywords +------------------------+---------------------------------------------- bbdb | %:name %:company irc | %:server %:port %:nick vm, wl, mh, mew, rmail | %:type %:subject %:message-id @@ -8701,7 +8701,7 @@ If you still want to have some text before the first headline, use the #+OPTIONS: skip:t #+TEXT: This text will go before the *first* headline. #+TEXT: [TABLE-OF-CONTENTS] -#+TEXT: This goes between the table of contents and the first headline +#+TEXT: This goes between the table of contents and the *first* headline. @end example @node Lists, Paragraphs, Initial text, Structural markup elements @@ -10607,7 +10607,7 @@ Export as TaskJuggler file and then open the file with TaskJugglerUI. @vindex org-export-taskjuggler-project-tag Create your tasks as you usually do with Org-mode. Assign efforts to each -task using properties (it's easiest to do this in the column view). You +task using properties (it is easiest to do this in the column view). You should end up with something similar to the example by Peter Jones in @url{http://www.contextualdevelopment.com/static/artifacts/articles/2008/project-planning/project-planning.org}. Now mark the top node of your tasks with a tag named @@ -14037,7 +14037,7 @@ Since Orgtbl mode can be used as a minor mode in arbitrary buffers, a frequent feature request has been to make it work with native tables in specific languages, for example @LaTeX{}. However, this is extremely hard to do in a general way, would lead to a customization nightmare, -and would take away much of the simplicity of the Orgtbl-mode table +and would take away much of the simplicity of the Orgtbl mode table editor. This appendix describes a different approach. We keep the Orgtbl mode -- 1.7.4.1