Kaynağa Gözat

Release 5.02

Carsten Dominik 17 yıl önce
ebeveyn
işleme
1b2e32f488
8 değiştirilmiş dosya ile 1944 ekleme ve 1221 silme
  1. 541 371
      org
  2. 605 195
      org.el
  3. BIN
      org.pdf
  4. 260 120
      org.texi
  5. BIN
      orgcard.pdf
  6. 39 19
      orgcard.tex
  7. BIN
      orgcard_letter.pdf
  8. 499 516
      orgcard_letter.ps

+ 541 - 371
org

@@ -5,7 +5,7 @@ START-INFO-DIR-ENTRY
 * Org Mode: (org).      Outline-based notes management and organizer
 END-INFO-DIR-ENTRY
 
-   This manual is for Org-mode (version 5.01).
+   This manual is for Org-mode (version 5.02).
 
    Copyright (C) 2004, 2005, 2006, 2007 Free Software Foundation
 
@@ -27,7 +27,7 @@ File: org,  Node: Top,  Next: Introduction,  Prev: (dir),  Up: (dir)
 Org Mode Manual
 ***************
 
-This manual is for Org-mode (version 5.01).
+This manual is for Org-mode (version 5.02).
 
    Copyright (C) 2004, 2005, 2006, 2007 Free Software Foundation
 
@@ -51,7 +51,7 @@ This manual is for Org-mode (version 5.01).
 * Hyperlinks::                  Notes in context
 * TODO items::                  Every tree branch can be a TODO item
 * Tags::                        Tagging headlines and matching sets of tags
-* Properties::
+* Properties and columns::
 * Timestamps::                  Assign date and time to items
 * Agenda views::                Collecting information into views
 * Embedded LaTeX::              LaTeX fragments and formulas
@@ -82,7 +82,8 @@ Document Structure
 * Archiving::                   Move done task trees to a different place
 * Sparse trees::                Matches embedded in context
 * Plain lists::                 Additional structure within an entry
-* Drawers::
+* Drawers::                     Tucking stuff away
+* orgstruct-mode::              Structure editing outside Org-mode
 
 Archiving
 
@@ -150,7 +151,7 @@ Tags
 * Setting tags::                How to assign tags to a headline
 * Tag searches::                Searching for combinations of tags
 
-Properties
+Properties and Columns
 
 * Property syntax::             How properties are spelled out
 * Special properties::          Access to other Org-mode features
@@ -163,6 +164,11 @@ Column View
 * Defining columns::            The COLUMNS format property
 * Using column view::           How to create and use column view
 
+Defining Columns
+
+* Scope of column definitions::
+* Column attributes::
+
 Timestamps
 
 * Time stamps::                 Assigning a time to a tree entry
@@ -349,7 +355,7 @@ selected by tags etc are created dynamically when you need them.
    Org-mode keeps simple things simple.  When first fired up, it should
 feel like a straightforward, easy to use outliner.  Complexity is not
 imposed, but a large amount of functionality is available when you need
-it.  Org-mode can be used on different levels and in different ways, for
+it.  Org-mode is a toolbox and can be used in different ways, for
 example as:
 
      * outline extension with visibility cycling and structure editing
@@ -358,13 +364,16 @@ example as:
      * TODO list editor
      * full agenda and planner with deadlines and work scheduling
      * environment to implement David Allen's GTD system
+     * a basic database application
      * simple hypertext system, with HTML export
      * publishing tool to create a set of interlinked webpages
 
    Org-mode's automatic, context sensitive table editor with spreadsheet
 capabilities can be integrated into any major mode by activating the
 minor Orgtbl-mode.  Using a translation step, it can be used to maintain
-tables in arbitrary file types, for example in LaTeX.
+tables in arbitrary file types, for example in LaTeX.  The structure
+editing and list creation capabilities can be used outside Org-mode with
+the minor Orgstruct-mode.
 
    There is a website for Org-mode which provides links to the newest
 version of Org-mode, as well as additional information, frequently asked
@@ -512,7 +521,8 @@ edit the structure of the document.
 * Archiving::                   Move done task trees to a different place
 * Sparse trees::                Matches embedded in context
 * Plain lists::                 Additional structure within an entry
-* Drawers::
+* Drawers::                     Tucking stuff away
+* orgstruct-mode::              Structure editing outside Org-mode
 
 
 File: org,  Node: Outlines,  Next: Headlines,  Prev: Document structure,  Up: Document structure
@@ -996,15 +1006,15 @@ XEmacs, you should use Kyle E. Jones' `filladapt.el'.  To turn this on,
 put into `.emacs': `(require 'filladapt)'
 
 
-File: org,  Node: Drawers,  Prev: Plain lists,  Up: Document structure
+File: org,  Node: Drawers,  Next: orgstruct-mode,  Prev: Plain lists,  Up: Document structure
 
 2.9 Drawers
 ===========
 
 Sometimes you want to keep information associated with an entry, but you
-normally don't want to see it, except when explicitly asking for it.
-For this, Org-mode has _drawers_.  Drawers need to be configured with
-the variable `org-drawers', and look like this:
+normally don't want to see it.  For this, Org-mode has _drawers_.
+Drawers need to be configured with the variable `org-drawers', and look
+like this:
 
      ** This is a headline
         Still outside the drawer
@@ -1017,7 +1027,29 @@ the variable `org-drawers', and look like this:
 hide and show the entry, but keep the drawer collapsed to a single line.
 In order to look inside the drawer, you need to move the cursor to the
 drawer line and press <TAB> there.  Org-mode uses a drawer for storing
-properties (*note Properties::).
+properties (*note Properties and columns::).
+
+
+File: org,  Node: orgstruct-mode,  Prev: Drawers,  Up: Document structure
+
+2.10 The Orgstruct minor mode
+=============================
+
+If you like the intuitive way the Org-mode structure editing and list
+formatting works, you might want to use these commands in other modes
+like text-mode or mail-mode as well.  The minor mode Orgstruct-mode
+makes this possible.  You can always toggle the mode with `M-x
+orgstruct-mode'.  To turn it on by default, for example in mail mode,
+use
+
+     (add-hook 'mail-mode-hook 'turn-on-orgstruct)
+
+   When this mode is active and the cursor is on a line that looks to
+Org-mode like a headline of the first line of a list item, most
+structure editing commands will work, even if the same keys normally
+have different functionality in the major mode you are using.  If the
+cursor is not in one of those special lines, Orgstruct-mode lurks
+silently in the shadow.
 
 
 File: org,  Node: Tables,  Next: Hyperlinks,  Prev: Document structure,  Up: Top
@@ -1441,15 +1473,16 @@ line like
 
      #+CONSTANTS: c=299792458. pi=3.14 eps=2.4e-6
 
-Also properties (*note Properties::) can be used as constants in table
-formulas: For a property `:XYZ:' use the name `$PROP_XYZ', and the
-property will be searched in the current outline entry and in the
-hierarchy above it.  If you have the `constants.el' package, it will
-also be used to resolve constants, including natural constants like
-`$h' for Planck's constant, and units like `$km' for kilometers(1).
-Column names and parameters can be specified in special table lines.
-These are described below, see *Note Advanced features::.  All names
-must start with a letter, and further consist of letters and numbers.
+Also properties (*note Properties and columns::) can be used as
+constants in table formulas: For a property `:XYZ:' use the name
+`$PROP_XYZ', and the property will be searched in the current outline
+entry and in the hierarchy above it.  If you have the `constants.el'
+package, it will also be used to resolve constants, including natural
+constants like `$h' for Planck's constant, and units like `$km' for
+kilometers(1).  Column names and parameters can be specified in special
+table lines.  These are described below, see *Note Advanced features::.
+All names must start with a letter, and further consist of letters and
+numbers.
 
    ---------- Footnotes ----------
 
@@ -2743,7 +2776,7 @@ The following commands work with checkboxes:
      with `C-c C-c'.
 
 
-File: org,  Node: Tags,  Next: Properties,  Prev: TODO items,  Up: Top
+File: org,  Node: Tags,  Next: Properties and columns,  Prev: TODO items,  Up: Top
 
 6 Tags
 ******
@@ -2982,10 +3015,10 @@ instead of any TAG an expression like `LEVEL=3'.  For example, a search
 BOSS and are _not_ marked with the todo keyword DONE.
 
 
-File: org,  Node: Properties,  Next: Timestamps,  Prev: Tags,  Up: Top
+File: org,  Node: Properties and columns,  Next: Timestamps,  Prev: Tags,  Up: Top
 
-7 Properties
-************
+7 Properties and Columns
+************************
 
 Properties are a set of key-value pairs associated with an entry.  There
 are two main applications for properties in Org-mode.  First, properties
@@ -2995,6 +3028,8 @@ tags like `:release_1:', `:release_2:', it can be more efficient to use
 a property `RELEASE' with a value `1.0' or `2.0'.  Second, you can use
 properties to implement (very basic) database capabilities in an
 Org-mode buffer, for example to create a list of Music CD's you own.
+You can edit and view properties conveniently in column view (*note
+Column view::).
 
 * Menu:
 
@@ -3005,7 +3040,7 @@ Org-mode buffer, for example to create a list of Music CD's you own.
 * Property API::                Properties for Lisp programmers
 
 
-File: org,  Node: Property syntax,  Next: Special properties,  Prev: Properties,  Up: Properties
+File: org,  Node: Property syntax,  Next: Special properties,  Prev: Properties and columns,  Up: Properties and columns
 
 7.1 Property Syntax
 ===================
@@ -3022,23 +3057,65 @@ and the value after it.  Here is an example:
          :Title:     Goldberg Variations
          :Composer:  J.S. Bach
          :Artist:    Glen Gould
+         :Publisher: Deutsche Grammphon
+         :NDisks:    1
          :END:
 
-The following commands help to insert properties:
+   You may define the allowed values for a particular property `XYZ' by
+setting a property `XYZ_ALL'.  This special property is _inherited_, so
+if you set it in a level 1 entry, it will apply to the entire tree.
+When allowed values are defined, setting the corresponding property
+becomes easier and is less prone to typing errors.  For the example
+with the CD collection, we can predefine publishers and the number of
+disks in a box like this:
+
+     * CD collection
+       :PROPERTIES:
+       :NDisks_ALL:  1 2 3 4
+       :Publisher_ALL: "Deutsche Grammophon" Phillips EMI
+       :END:
+
+The following commands help to work with properties:
 
 `M-<TAB>'
      After an initial colon in a line, complete property keys.  All
      keys used in the current file will be offered as possible
      completions.
 
+`M-x org-insert-property-drawer'
+     Insert a property drawer into the current entry.  The drawer will
+     be inserted early in the entry, but after the lines with planning
+     information like deadlines.  
+
+`C-c C-c'
+     With the cursor in a property drawer, this executes property
+     commands.
+
+`C-c C-c s'
+     Set a property in the current entry.  Both the property and the
+     value can be inserted using completion.  
+
+`S-<left>/<right>'
+     Switch property at point to the next/previous allowed value.
+
+`C-c C-c d'
+     Remove a property from the current entry.
+
+`C-c C-c D'
+     Globally remove a property, from all entries in the current file.
+
 
-File: org,  Node: Special properties,  Next: Property searches,  Prev: Property syntax,  Up: Properties
+File: org,  Node: Special properties,  Next: Property searches,  Prev: Property syntax,  Up: Properties and columns
 
 7.2 Special Properties
 ======================
 
-Several properties are special, because they can be used to access other
-features of Org-mode like the TODO status:
+Special properties provide alternative access method to Org-mode
+features discussed in the previous chapters, like the TODO state or the
+priority of an entry.  This interface exists so that you can include
+these states into columns view (*note Column view::).  The following
+property names are special and should not be used as keys in the
+properties drawer:
 
      TODO         The TODO keyword of the entry.
      TAGS         The tags defined directly in the headline.
@@ -3048,7 +3125,7 @@ features of Org-mode like the TODO status:
      SCHEDULED    The scheduling time stamp, without the angular brackets.
 
 
-File: org,  Node: Property searches,  Next: Column view,  Prev: Special properties,  Up: Properties
+File: org,  Node: Property searches,  Next: Column view,  Prev: Special properties,  Up: Properties and columns
 
 7.3 Property searches
 =====================
@@ -3065,25 +3142,24 @@ and a `:with:' property that is matched by the regular expression
 `Sarah\|Denny'.
 
 
-File: org,  Node: Column view,  Next: Property API,  Prev: Property searches,  Up: Properties
+File: org,  Node: Column view,  Next: Property API,  Prev: Property searches,  Up: Properties and columns
 
 7.4 Column View
 ===============
 
-If different items in a document have similar properties, it can be nice
-to view and edit those properties in a table-like format, in _column
-view_.  Org-mode implements columns by overlaying a tabular structure
-over the headline of an item.  So the column view does not use a
-special buffer, it happens in exactly the same buffer where the outline
-is, and only temporarily changes the look of this buffer - not the
-content.  This has the advantage that you can still change the
-visibility of the outline tree.  For example, you get a compact table by
-switching to CONTENTS view, but you can still open, read, and edit the
-entry below each headline.  Or, you can switch to column view after
-executing a sparse tree command and in this way get a table only for the
-selected items.  Column view also works in agenda buffers (*note Agenda
-views::) where queries have collected selected items, possibly from a
-number of files.
+A great way to view and edit properties in aan outline tree is _column
+view_.  In column view, each outline item is turned into a table row.
+Columns in this table provide access to properties of the entries.
+Org-mode implements columns by overlaying a tabular structure over the
+headline of each item.  While the headlines have been turned into a
+table row, you can still change the visibility of the outline tree.
+For example, you get a compact table by switching to CONTENTS view
+(`S-<TAB> S-<TAB>', or simple `c' while column view is active), but you
+can still open, read, and edit the entry below each headline.  Or, you
+can switch to column view after executing a sparse tree command and in
+this way get a table only for the selected items.  Column view also
+works in agenda buffers (*note Agenda views::) where queries have
+collected selected items, possibly from a number of files.
 
 * Menu:
 
@@ -3096,60 +3172,84 @@ File: org,  Node: Defining columns,  Next: Using column view,  Prev: Column view
 7.4.1 Defining Columns
 ----------------------
 
-Setting up a column view first requires defining the columns.  A column
-definition is a property itself and looks like this:
+Setting up a column view first requires defining the columns.  This is
+done by defining a column format line.
 
-     :COLUMNS: %25ITEM %TAGS %PRIORITY %TODO
+* Menu:
 
-   This definition means that column 1 should be the first 25
-characters of the item itself, i.e. of the headline.  You probably
-always should start the column definition with the ITEM specifier -
-just select a useful width for it.  The other specifiers create columns
-for the local tags, for the priority and for the TODO state.  When no
-width is given after the `%' character, the column will be exactly as
-wide as it need to be in order to fully display all values.
+* Scope of column definitions::  Where defined, where valid?
+* Column attributes::           Appearance and content of a column
 
-   If a `COLUMNS' property is present in an entry, it defines columns
-for the entry itself, and for the entire subtree below it.  Since the
-column definition is part of the hierarchical structure of the
-document, you can define columns on level 1 that are general enough for
-all sublevels, and more specific columns further down, when you edit a
-deeper part of the tree.  Here is an example:
+
+File: org,  Node: Scope of column definitions,  Next: Column attributes,  Prev: Defining columns,  Up: Defining columns
 
-     * People
-       :PROPERTIES:
-       :COLUMNS: %25ITEM %Name
-       :END:
-     ** Family
-        :PROPERTIES:
-        :COLUMNS: %25ITEM %Name %3Age
-        :END:
-     *** Sam
-         Info about Sam, including a property list with Name and Age.
-     *** Sarah
-         Info about Sarah, including a property list with Name and Age.
-     ** Office
-        :PROPERTIES:
-        :COLUMNS: %25ITEM %Name %Function %Salary
-        :END:
-     *** Boss
-         Info about the Boss, including a property list with Name,
-         Function and Salary (if only we knew....).
+7.4.1.1 Scope of column definitions
+...................................
+
+To define a column format for an entire file, use a line like
 
-   Now we have defined three different sets of columns.  If you switch
-to column view in the _Family_ section, you will get a different table
-than if you do it in the _Office_ section.  However, if you switch to
-column view with the cursor on the _People_ section, the table will
-cover all entries, but contain only the _Name_ column.
+     #+COLUMNS: %25ITEM %TAGS %PRIORITY %TODO
 
-   If no COLUMNS property applies to a given location, Org-mode uses a
-default format specified in the variable `org-default-columns-format'.
-This format in particular also applies when column view is invoked with
-the cursor before the first headline.  You can set the default format
-on a per-file basis with a line (don't forget to press `C-c C-c' to
-activate any changes to this line).
+   To specify a format that only applies to a specific tree, add a
+COLUMNS property to the top node of that tree, for example
+     ** Top node for columns view
+        :PROPERTIES:
+        :COLUMNS: %25ITEM %TAGS %PRIORITY %TODO
+        :END:
 
-     #+COLUMNS: %25ITEM ....."
+   If a `COLUMNS' property is present in an entry, it defines columns
+for the entry itself, and for the entire subtree below it.  Since the
+column definition is part of the hierarchical structure of the document,
+you can define columns on level 1 that are general enough for all
+sublevels, and more specific columns further down, when you edit a
+deeper part of the tree.
+
+
+File: org,  Node: Column attributes,  Prev: Scope of column definitions,  Up: Defining columns
+
+7.4.1.2 Column attributes
+.........................
+
+A column definition sets the attributes of a column.  The general
+definition looks like this:
+
+      %[width]property[(title)][{summary-type}]
+
+Except for the percent sign and the property name, all items are
+optional.  The individual parts have the following meaning:
+
+     width           An integer specifying the width of the column in characters.
+                     If omitted, the width will be determined automatically.
+     property        The property that should be edited in this column.
+     (title)         The header text for the column. If omitted, the
+                     property name is used.
+     {summary-type}  The summary type.  If specified, the column values for
+                     parent nodes are computed from the children.
+                     Supported summary types are:
+                     {+}  Sum numbers in this column.
+                     {:}  Sum times, HH:MM:SS, plain numbers are hours.
+                     {X}  Checkbox status, [X] if all children are [X].
+
+Here is an example for a complete columns definition, along with allowed
+values.
+
+     :COLUMNS:  %20ITEM %9Approved(Approved?){X} %Owner %11Status %10Time_Spent{:}
+     :Owner_ALL:    Tammy Mark Karl Lisa Don
+     :Status_ALL:   "In progress" "Not started yet" "Finished" ""
+     :Approved_ALL: "[ ]" "[X]"
+
+   The first column, `%25ITEM', means the first 25 characters of the
+item itself, i.e. of the headline.  You probably always should start the
+column definition with the ITEM specifier.  The other specifiers create
+columns `Owner' with a list of names as allowed values, for `Status'
+with four different possible values, and for a checkbox field
+`Approved'.  When no width is given after the `%' character, the column
+will be exactly as wide as it needs to be in order to fully display all
+values.  The `Approved' column does have a modified title (`Approved?',
+with a question mark).  Summaries will be created for the `Time_Spent'
+column by adding time duration expressions like HH:MM, and for the
+`Approved' column, by providing an `[X]' status if all children have
+been checked.
 
 
 File: org,  Node: Using column view,  Prev: Defining columns,  Up: Column view
@@ -3157,15 +3257,35 @@ File: org,  Node: Using column view,  Prev: Defining columns,  Up: Column view
 7.4.2 Using Column View
 -----------------------
 
+Turning column view on and off
+..............................
+
 `C-c C-x C-c'
      Create the column view for the local environment.  This command
      searches the hierarchy, up from point, for a `COLUMNS' property
      that defines a format.  When one is found, the column view table
-     is established for the entire subtree.
+     is established for the entire tree, starting from the entry that
+     contains the `COLUMNS' property.  If none is found, the format is
+     taken from the `#+COLUMNS' line or from the variable
+     `org-columns-default-format', and column view is established for
+     the current entry and its subtree.  
+
+`q'
+     Exit column view.
+
+Editing values
+..............
 
 `<left> <right> <up> <down>'
      Move through the column view from field to field.  
 
+`S-<left>/<right>'
+     Switch to the next/previous allowed value of the field.  For this,
+     you have to have specified allowed values for a property.  
+
+`n / p'
+     Same as `S-<left>/<right>' 
+
 `e'
      Edit the property at point.  For the special properties, this will
      invoke the same interface that you normally use to change that
@@ -3176,11 +3296,26 @@ File: org,  Node: Using column view,  Prev: Defining columns,  Up: Column view
      View the full value of this property.  This is useful if the width
      of the column is smaller than that of the value.  
 
-`q'
-     Exit column view.
+`a'
+     Edit the list of allowed values for this property.  If the list is
+     found in the hierarchy, the modified values is stored there.  If
+     no list is found, the new value is stored in the first entry that
+     is part of the current column view.
+
+Modifying the table structure
+.............................
+
+`< / >'
+     Make the column narrower/wider by one character.  
+
+`S-M-<right>'
+     Insert a new column, to the right of the current column.  
+
+`S-M-<left>'
+     Delete the current column.
 
 
-File: org,  Node: Property API,  Prev: Column view,  Up: Properties
+File: org,  Node: Property API,  Prev: Column view,  Up: Properties and columns
 
 7.5 The Property API
 ====================
@@ -3191,7 +3326,7 @@ features based on them.  For more information see *Note Using the
 property API::.
 
 
-File: org,  Node: Timestamps,  Next: Agenda views,  Prev: Properties,  Up: Top
+File: org,  Node: Timestamps,  Next: Agenda views,  Prev: Properties and columns,  Up: Top
 
 8 Timestamps
 ************
@@ -4218,7 +4353,10 @@ Change display
      Delete other windows.  
 
 `d w m y'
-     Switch to day/week/month/year view.  
+     Switch to day/week/month/year view.  When switching to day or week
+     view, this setting becomes the default for subseqent agenda
+     commands.  Since month and year views are slow to create, the do
+     not become the default.  
 
 `D'
      Toggle the inclusion of diary entries.  See *Note Weekly/Daily
@@ -5429,9 +5567,9 @@ tool.
 
    ---------- Footnotes ----------
 
-   (1) `org-publish.el' is not yet part of Emacs, so if you are using
-`org.el' as it comes with Emacs, you need to download this file
-separately.  Also make sure org.el is at least version 4.27.
+   (1) `org-publish.el' is not distributed with Emacs 21, if you are
+still using Emacs 21, you need you need to download this file
+separately.
 
 
 File: org,  Node: Configuration,  Next: Sample configuration,  Prev: Publishing,  Up: Publishing
@@ -5580,7 +5718,7 @@ respective variable for details.
 
    When a property is given a value in org-publish-project-alist, its
 setting overrides the value of the corresponding user variable (if any)
-during publishing.  options set within a file (*note Export options::),
+during publishing.  Options set within a file (*note Export options::),
 however, override everything.
 
 
@@ -5886,8 +6024,8 @@ file is visited again in a new Emacs session.
           logging          record a timestamp when an item is marked DONE
           nologging        don't record when items are marked DONE
           lognotedone      record timestamp and a note when DONE
-          lognotestate     record timestamp, note when TODO state changes
-          logrepeat        record a not when re-instating a repeating item
+          lognotestate     record timestamp and a note when TODO state changes
+          logrepeat        record a note when re-instating a repeating item
           nologrepeat      do not record when re-instating repeating item
           lognoteclock-out record timestamp and a note when clocking out
      Here are the options for hiding leading stars in outline headings.
@@ -5961,6 +6099,9 @@ means in different contexts.
    - If the cursor is on a `<<<target>>>', update radio targets and
      corresponding links in this buffer.
 
+   - If the cursor is in a property line or at the start or end of a
+     property drawer, offer property commands.
+
    - If the cursor is in a plain list item with a checkbox, toggle the
      status of the checkbox.
 
@@ -6888,12 +7029,12 @@ Index
 * agenda:                                Weekly/Daily agenda. (line   6)
 * agenda dispatcher:                     Agenda dispatcher.   (line   6)
 * agenda files:                          Agenda files.        (line   6)
-* agenda files, removing buffers:        Agenda commands.     (line 236)
+* agenda files, removing buffers:        Agenda commands.     (line 239)
 * agenda views:                          Agenda views.        (line   6)
 * agenda views, custom:                  Custom agenda views. (line   6)
 * agenda views, exporting <1>:           Exporting Agenda Views.
                                                               (line   6)
-* agenda views, exporting:               Agenda commands.     (line 225)
+* agenda views, exporting:               Agenda commands.     (line 228)
 * agenda views, user-defined:            Special agenda views.
                                                               (line   6)
 * agenda, pipe:                          Extracting Agenda Information for other programs.
@@ -6902,8 +7043,9 @@ Index
 * align, STARTUP keyword:                In-buffer settings.  (line  63)
 * allout.el:                             Conflicts.           (line   6)
 * angular brackets, around links:        External links.      (line  43)
-* API, for properties:                   Using the property API.
+* API, for properties <1>:               Using the property API.
                                                               (line   6)
+* API, for properties:                   Property API.        (line   6)
 * archive locations:                     Moving subtrees.     (line  21)
 * archiving:                             Archiving.           (line   6)
 * ASCII export:                          ASCII export.        (line   6)
@@ -6924,7 +7066,7 @@ Index
 * calculations, in tables <1>:           The spreadsheet.     (line   6)
 * calculations, in tables:               Built-in table editor.
                                                               (line 141)
-* calendar commands, from agenda:        Agenda commands.     (line 188)
+* calendar commands, from agenda:        Agenda commands.     (line 191)
 * calendar integration:                  Weekly/Daily agenda. (line  24)
 * calendar, for selecting date:          The date/time prompt.
                                                               (line  26)
@@ -6936,6 +7078,7 @@ Index
 * children, subtree visibility state:    Visibility cycling.  (line  10)
 * clean outline view:                    Clean view.          (line   6)
 * column formula:                        Column formulas.     (line   6)
+* column view, for properties:           Defining columns.    (line   6)
 * commands, in agenda buffer:            Agenda commands.     (line   6)
 * comment lines:                         Comment lines.       (line   6)
 * completion, of dictionary words:       Completion.          (line   6)
@@ -6981,7 +7124,7 @@ Index
 * debugging, of table formulas:          Editing and debugging formulas.
                                                               (line  97)
 * demotion, of subtrees:                 Structure editing.   (line   6)
-* diary entries, creating from agenda:   Agenda commands.     (line 193)
+* diary entries, creating from agenda:   Agenda commands.     (line 196)
 * diary integration:                     Weekly/Daily agenda. (line  24)
 * dictionary word completion:            Completion.          (line   6)
 * directories, for publishing:           Sources and destinations.
@@ -6990,6 +7133,7 @@ Index
 * display changing, in agenda:           Agenda commands.     (line  65)
 * document structure:                    Document structure.  (line   6)
 * DONE, final TODO keyword:              Per file keywords.   (line  26)
+* drawer, for properties:                Property syntax.     (line   6)
 * drawers:                               Drawers.             (line   6)
 * dynamic blocks:                        Dynamic blocks.      (line   6)
 * editing tables:                        Tables.              (line   6)
@@ -7003,14 +7147,14 @@ Index
 * exporting:                             Exporting.           (line   6)
 * exporting agenda views <1>:            Exporting Agenda Views.
                                                               (line  12)
-* exporting agenda views:                Agenda commands.     (line 225)
+* exporting agenda views:                Agenda commands.     (line 228)
 * exporting, not:                        Comment lines.       (line   6)
 * extended TODO keywords:                TODO extensions.     (line   6)
 * extension, third-party:                Extensions.          (line   6)
 * external archiving:                    Moving subtrees.     (line   6)
 * external links:                        External links.      (line   6)
 * external links, in HTML export:        Links.               (line   6)
-* FAQ:                                   Summary.             (line  53)
+* FAQ:                                   Summary.             (line  56)
 * feedback:                              Feedback.            (line   6)
 * field formula:                         Field formulas.      (line   6)
 * field references:                      References.          (line  15)
@@ -7128,6 +7272,7 @@ Index
 * matching, tags:                        Tags.                (line   6)
 * math symbols:                          Math symbols.        (line   6)
 * MH-E links:                            External links.      (line   6)
+* minor mode for structure editing:      orgstruct-mode.      (line   6)
 * minor mode for tables:                 orgtbl-mode.         (line   6)
 * mode, for calc:                        Formula syntax for Calc.
                                                               (line  14)
@@ -7155,6 +7300,7 @@ Index
 * org-publish-project-alist:             Project alist.       (line   6)
 * org-publish.el:                        Extensions.          (line   8)
 * org2rem.el:                            Extensions.          (line  36)
+* orgstruct-mode:                        orgstruct-mode.      (line   6)
 * orgtbl-mode <1>:                       Tables in arbitrary syntax.
                                                               (line   6)
 * orgtbl-mode:                           orgtbl-mode.         (line   6)
@@ -7177,7 +7323,15 @@ Index
 * progress logging:                      Progress logging.    (line   6)
 * projects, for publishing:              Project alist.       (line   6)
 * promotion, of subtrees:                Structure editing.   (line   6)
-* properties:                            Properties.          (line   6)
+* properties:                            Properties and columns.
+                                                              (line   6)
+* properties, API <1>:                   Using the property API.
+                                                              (line   6)
+* properties, API:                       Property API.        (line   6)
+* properties, column view:               Defining columns.    (line   6)
+* properties, searching:                 Property searches.   (line   6)
+* properties, special:                   Special properties.  (line   6)
+* property syntax:                       Property syntax.     (line   6)
 * publishing:                            Publishing.          (line   6)
 * quoted HTML tags:                      Export options.      (line  25)
 * radio tables:                          Radio tables.        (line   6)
@@ -7197,8 +7351,8 @@ Index
 * regular expressions, with tags search: Tag searches.        (line  63)
 * remember.el <1>:                       Cooperation.         (line  33)
 * remember.el:                           Remember.            (line   6)
-* remote editing, from agenda:           Agenda commands.     (line 103)
-* remote editing, undo:                  Agenda commands.     (line 104)
+* remote editing, from agenda:           Agenda commands.     (line 106)
+* remote editing, undo:                  Agenda commands.     (line 107)
 * richer text:                           Enhancing text.      (line   6)
 * RMAIL links:                           External links.      (line   6)
 * SCHEDULED keyword:                     Deadlines and scheduling.
@@ -7309,7 +7463,7 @@ Index
 * tty keybindings:                       TTY keys.            (line   6)
 * types as TODO keywords:                TODO types.          (line   6)
 * underlined text:                       Enhancing text.      (line  15)
-* undoing remote-editing events:         Agenda commands.     (line 104)
+* undoing remote-editing events:         Agenda commands.     (line 107)
 * updating, table:                       Updating the table.  (line   6)
 * URL links:                             External links.      (line   6)
 * USENET links:                          External links.      (line   6)
@@ -7317,6 +7471,7 @@ Index
 * vectors, in table calculations:        Formula syntax for Calc.
                                                               (line  11)
 * visibility cycling:                    Visibility cycling.  (line   6)
+* visibility cycling, drawers:           Drawers.             (line   6)
 * visible text, printing:                Sparse trees.        (line  41)
 * VM links:                              External links.      (line   6)
 * WANDERLUST links:                      External links.      (line   6)
@@ -7335,23 +7490,24 @@ Key Index
 [index]
 * Menu:
 
-* $:                                     Agenda commands.     (line 118)
+* $:                                     Agenda commands.     (line 121)
 * ':                                     CDLaTeX mode.        (line  43)
-* +:                                     Agenda commands.     (line 140)
-* ,:                                     Agenda commands.     (line 132)
-* -:                                     Agenda commands.     (line 146)
-* .:                                     Agenda commands.     (line  95)
-* ::                                     Agenda commands.     (line 126)
-* <:                                     The date/time prompt.
+* +:                                     Agenda commands.     (line 143)
+* ,:                                     Agenda commands.     (line 135)
+* -:                                     Agenda commands.     (line 149)
+* .:                                     Agenda commands.     (line  98)
+* ::                                     Agenda commands.     (line 129)
+* < <1>:                                 The date/time prompt.
                                                               (line  32)
-* <left>:                                Agenda commands.     (line  92)
+* <:                                     Using column view.   (line  54)
+* <left>:                                Agenda commands.     (line  95)
 * <RET> <1>:                             Agenda commands.     (line  39)
 * <RET> <2>:                             The date/time prompt.
                                                               (line  57)
 * <RET> <3>:                             Setting tags.        (line  76)
 * <RET>:                                 Built-in table editor.
                                                               (line  62)
-* <right>:                               Agenda commands.     (line  87)
+* <right>:                               Agenda commands.     (line  90)
 * <SPC> <1>:                             Agenda commands.     (line  28)
 * <SPC>:                                 Setting tags.        (line  73)
 * <TAB> <1>:                             CDLaTeX mode.        (line  23)
@@ -7363,20 +7519,22 @@ Key Index
                                                               (line  55)
 * <TAB> <6>:                             Plain lists.         (line  41)
 * <TAB>:                                 Visibility cycling.  (line  10)
-* > <1>:                                 Agenda commands.     (line 168)
-* >:                                     The date/time prompt.
+* > <1>:                                 Agenda commands.     (line 171)
+* > <2>:                                 The date/time prompt.
                                                               (line  33)
+* >:                                     Using column view.   (line  54)
 * ^:                                     CDLaTeX mode.        (line  33)
 * _:                                     CDLaTeX mode.        (line  33)
 * `:                                     CDLaTeX mode.        (line  39)
-* a:                                     Agenda commands.     (line 129)
+* a <1>:                                 Agenda commands.     (line 132)
+* a:                                     Using column view.   (line  43)
 * b:                                     Agenda commands.     (line  49)
-* C:                                     Agenda commands.     (line 208)
-* c:                                     Agenda commands.     (line 188)
+* C:                                     Agenda commands.     (line 211)
+* c:                                     Agenda commands.     (line 191)
 * C-#:                                   Advanced features.   (line   9)
 * C-':                                   Agenda files.        (line  18)
 * C-,:                                   Agenda files.        (line  18)
-* C-_:                                   Agenda commands.     (line 104)
+* C-_:                                   Agenda commands.     (line 107)
 * C-a a L:                               Timeline.            (line  10)
 * C-c ! <1>:                             Footnotes.           (line  14)
 * C-c !:                                 Creating timestamps. (line  19)
@@ -7435,14 +7593,15 @@ Key Index
                                                               (line   6)
 * C-c C-c <3>:                           Processing LaTeX fragments.
                                                               (line  15)
-* C-c C-c <4>:                           Setting tags.        (line  10)
-* C-c C-c <5>:                           Checkboxes.          (line  37)
-* C-c C-c <6>:                           Editing and debugging formulas.
+* C-c C-c <4>:                           Property syntax.     (line  46)
+* C-c C-c <5>:                           Setting tags.        (line  10)
+* C-c C-c <6>:                           Checkboxes.          (line  37)
+* C-c C-c <7>:                           Editing and debugging formulas.
                                                               (line  46)
-* C-c C-c <7>:                           Built-in table editor.
+* C-c C-c <8>:                           Built-in table editor.
                                                               (line  54)
 * C-c C-c:                               Plain lists.         (line  81)
-* C-c C-d <1>:                           Agenda commands.     (line 153)
+* C-c C-d <1>:                           Agenda commands.     (line 156)
 * C-c C-d:                               Inserting deadline/schedule.
                                                               (line   9)
 * C-c C-e:                               Exporting.           (line  19)
@@ -7477,7 +7636,7 @@ Key Index
 * C-c C-r <1>:                           Editing and debugging formulas.
                                                               (line  53)
 * C-c C-r:                               Visibility cycling.  (line  34)
-* C-c C-s <1>:                           Agenda commands.     (line 150)
+* C-c C-s <1>:                           Agenda commands.     (line 153)
 * C-c C-s:                               Inserting deadline/schedule.
                                                               (line  18)
 * C-c C-t <1>:                           Clocking work time.  (line  27)
@@ -7489,8 +7648,8 @@ Key Index
 * C-c C-x b:                             Visibility cycling.  (line  41)
 * C-c C-x C-a:                           ARCHIVE tag.         (line  28)
 * C-c C-x C-b:                           Checkboxes.          (line  38)
-* C-c C-x C-c <1>:                       Agenda commands.     (line 215)
-* C-c C-x C-c:                           Using column view.   (line   6)
+* C-c C-x C-c <1>:                       Agenda commands.     (line 218)
+* C-c C-x C-c:                           Using column view.   (line   9)
 * C-c C-x C-d:                           Clocking work time.  (line  35)
 * C-c C-x C-i:                           Clocking work time.  (line  12)
 * C-c C-x C-k:                           Structure editing.   (line  39)
@@ -7524,7 +7683,7 @@ Key Index
 * C-c }:                                 Editing and debugging formulas.
                                                               (line  28)
 * C-c ~:                                 Cooperation.         (line  48)
-* C-k:                                   Agenda commands.     (line 112)
+* C-k:                                   Agenda commands.     (line 115)
 * C-S-<left>:                            Multiple sets in one file.
                                                               (line  25)
 * C-S-<right>:                           Multiple sets in one file.
@@ -7548,18 +7707,18 @@ Key Index
                                                               (line  46)
 * C-x C-w <1>:                           Exporting Agenda Views.
                                                               (line  11)
-* C-x C-w:                               Agenda commands.     (line 224)
-* D:                                     Agenda commands.     (line  69)
+* C-x C-w:                               Agenda commands.     (line 227)
+* D:                                     Agenda commands.     (line  72)
 * d:                                     Agenda commands.     (line  66)
-* e:                                     Using column view.   (line  13)
+* e:                                     Using column view.   (line  33)
 * f:                                     Agenda commands.     (line  42)
-* g:                                     Agenda commands.     (line  73)
-* H:                                     Agenda commands.     (line 212)
-* i:                                     Agenda commands.     (line 193)
-* I:                                     Agenda commands.     (line 173)
+* g:                                     Agenda commands.     (line  76)
+* H:                                     Agenda commands.     (line 215)
+* i:                                     Agenda commands.     (line 196)
+* I:                                     Agenda commands.     (line 176)
 * l:                                     Agenda commands.     (line  55)
 * L:                                     Agenda commands.     (line  30)
-* M:                                     Agenda commands.     (line 199)
+* M:                                     Agenda commands.     (line 202)
 * m:                                     Agenda commands.     (line  66)
 * M-<down> <1>:                          Editing and debugging formulas.
                                                               (line  76)
@@ -7574,7 +7733,7 @@ Key Index
                                                               (line  72)
 * M-<right>:                             Structure editing.   (line  24)
 * M-<TAB> <1>:                           Completion.          (line  10)
-* M-<TAB> <2>:                           Property syntax.     (line  22)
+* M-<TAB> <2>:                           Property syntax.     (line  38)
 * M-<TAB> <3>:                           Setting tags.        (line   6)
 * M-<TAB> <4>:                           Per file keywords.   (line  23)
 * M-<TAB>:                               Editing and debugging formulas.
@@ -7618,18 +7777,20 @@ Key Index
 * mouse-2:                               Handling links.      (line  72)
 * mouse-3 <1>:                           Agenda commands.     (line  28)
 * mouse-3:                               Handling links.      (line  77)
-* n:                                     Agenda commands.     (line  19)
-* O:                                     Agenda commands.     (line 177)
+* n <1>:                                 Agenda commands.     (line  19)
+* n:                                     Using column view.   (line  30)
+* O:                                     Agenda commands.     (line 180)
 * o:                                     Agenda commands.     (line  65)
-* P:                                     Agenda commands.     (line 137)
-* p:                                     Agenda commands.     (line  20)
-* q <1>:                                 Agenda commands.     (line 235)
-* q:                                     Using column view.   (line  23)
-* r <1>:                                 Agenda commands.     (line  77)
+* P:                                     Agenda commands.     (line 140)
+* p <1>:                                 Agenda commands.     (line  20)
+* p:                                     Using column view.   (line  30)
+* q <1>:                                 Agenda commands.     (line 238)
+* q:                                     Using column view.   (line  17)
+* r <1>:                                 Agenda commands.     (line  80)
 * r:                                     Global TODO list.    (line  22)
-* S:                                     Agenda commands.     (line 203)
-* s:                                     Agenda commands.     (line  84)
-* S-<down> <1>:                          Agenda commands.     (line 146)
+* S:                                     Agenda commands.     (line 206)
+* s:                                     Agenda commands.     (line  87)
+* S-<down> <1>:                          Agenda commands.     (line 149)
 * S-<down> <2>:                          The date/time prompt.
                                                               (line  45)
 * S-<down> <3>:                          Creating timestamps. (line  40)
@@ -7637,30 +7798,34 @@ Key Index
 * S-<down> <5>:                          Editing and debugging formulas.
                                                               (line  67)
 * S-<down>:                              Plain lists.         (line  62)
-* S-<left> <1>:                          Agenda commands.     (line 164)
+* S-<left> <1>:                          Agenda commands.     (line 167)
 * S-<left> <2>:                          The date/time prompt.
                                                               (line  42)
 * S-<left> <3>:                          Creating timestamps. (line  35)
-* S-<left> <4>:                          Multiple sets in one file.
+* S-<left> <4>:                          Using column view.   (line  26)
+* S-<left> <5>:                          Property syntax.     (line  54)
+* S-<left> <6>:                          Multiple sets in one file.
                                                               (line  29)
-* S-<left> <5>:                          TODO basics.         (line  20)
+* S-<left> <7>:                          TODO basics.         (line  20)
 * S-<left>:                              Editing and debugging formulas.
                                                               (line  67)
 * S-<RET>:                               Built-in table editor.
                                                               (line 144)
-* S-<right> <1>:                         Agenda commands.     (line 156)
+* S-<right> <1>:                         Agenda commands.     (line 159)
 * S-<right> <2>:                         The date/time prompt.
                                                               (line  39)
 * S-<right> <3>:                         Creating timestamps. (line  35)
-* S-<right> <4>:                         Multiple sets in one file.
+* S-<right> <4>:                         Using column view.   (line  26)
+* S-<right> <5>:                         Property syntax.     (line  54)
+* S-<right> <6>:                         Multiple sets in one file.
                                                               (line  29)
-* S-<right> <5>:                         TODO basics.         (line  20)
+* S-<right> <7>:                         TODO basics.         (line  20)
 * S-<right>:                             Editing and debugging formulas.
                                                               (line  67)
 * S-<TAB> <1>:                           Built-in table editor.
                                                               (line  59)
 * S-<TAB>:                               Visibility cycling.  (line  22)
-* S-<up> <1>:                            Agenda commands.     (line 140)
+* S-<up> <1>:                            Agenda commands.     (line 143)
 * S-<up> <2>:                            The date/time prompt.
                                                               (line  48)
 * S-<up> <3>:                            Creating timestamps. (line  40)
@@ -7668,217 +7833,222 @@ Key Index
 * S-<up> <5>:                            Editing and debugging formulas.
                                                               (line  67)
 * S-<up>:                                Plain lists.         (line  62)
+* S-M-<left>:                            Using column view.   (line  58)
 * S-M-<RET>:                             TODO basics.         (line  44)
-* T:                                     Agenda commands.     (line 121)
-* t:                                     Agenda commands.     (line 108)
-* v:                                     Using column view.   (line  19)
+* S-M-<right>:                           Using column view.   (line  55)
+* T:                                     Agenda commands.     (line 124)
+* t:                                     Agenda commands.     (line 111)
+* v:                                     Using column view.   (line  39)
 * w:                                     Agenda commands.     (line  66)
-* x:                                     Agenda commands.     (line 236)
-* X:                                     Agenda commands.     (line 180)
+* x:                                     Agenda commands.     (line 239)
+* X:                                     Agenda commands.     (line 183)
 * y:                                     Agenda commands.     (line  66)
 
 
 
 Tag Table:
 Node: Top970
-Node: Introduction12310
-Node: Summary12725
-Node: Installation15734
-Node: Activation17112
-Node: Feedback18361
-Node: Document structure20437
-Node: Outlines21223
-Node: Headlines21883
-Ref: Headlines-Footnote-122891
-Node: Visibility cycling22990
-Ref: Visibility cycling-Footnote-125200
-Ref: Visibility cycling-Footnote-225258
-Ref: Visibility cycling-Footnote-325308
-Node: Motion25578
-Node: Structure editing26532
-Node: Archiving29358
-Node: ARCHIVE tag29916
-Node: Moving subtrees31709
-Node: Sparse trees33020
-Ref: Sparse trees-Footnote-135152
-Ref: Sparse trees-Footnote-235334
-Node: Plain lists35449
-Ref: Plain lists-Footnote-139646
-Ref: Plain lists-Footnote-240004
-Node: Drawers40185
-Node: Tables41026
-Node: Built-in table editor41607
-Node: Narrow columns48846
-Ref: Narrow columns-Footnote-150781
-Node: Column groups50827
-Node: orgtbl-mode52360
-Node: The spreadsheet53163
-Node: References54250
-Ref: References-Footnote-158701
-Node: Formula syntax for Calc58990
-Node: Formula syntax for Lisp61447
-Node: Field formulas63165
-Node: Column formulas64473
-Node: Editing and debugging formulas66072
-Node: Updating the table70225
-Node: Advanced features71260
-Node: Hyperlinks75785
-Node: Link format76558
-Node: Internal links77851
-Ref: Internal links-Footnote-179776
-Node: Radio targets79911
-Node: External links80602
-Node: Handling links83006
-Ref: Handling links-Footnote-188293
-Ref: Handling links-Footnote-288530
-Node: Link abbreviations88604
-Node: Search options90283
-Ref: Search options-Footnote-192063
-Node: Custom searches92144
-Node: Remember93192
-Node: Setting up remember94179
-Node: Remember templates94761
-Ref: Remember templates-Footnote-198207
-Node: Storing notes98305
-Node: TODO items100192
-Node: TODO basics101169
-Node: TODO extensions102933
-Node: Workflow states103752
-Ref: Workflow states-Footnote-1104927
-Node: TODO types105020
-Ref: TODO types-Footnote-1106603
-Node: Multiple sets in one file106685
-Node: Per file keywords108296
-Ref: Per file keywords-Footnote-1109585
-Node: Priorities109786
-Node: Breaking down tasks111396
-Ref: Breaking down tasks-Footnote-1111916
-Node: Checkboxes112012
-Node: Tags114767
-Node: Tag inheritance115527
-Node: Setting tags116464
-Ref: Setting tags-Footnote-1120987
-Ref: Setting tags-Footnote-2121099
-Node: Tag searches121182
-Node: Properties123899
-Node: Property syntax124884
-Node: Special properties125705
-Node: Property searches126366
-Node: Column view127009
-Node: Defining columns128199
-Node: Using column view130710
-Node: Property API131627
-Node: Timestamps131969
-Node: Time stamps132418
-Ref: Time stamps-Footnote-1134846
-Node: Creating timestamps134962
-Node: The date/time prompt137036
-Ref: The date/time prompt-Footnote-1139024
-Node: Custom time format139130
-Node: Deadlines and scheduling140822
-Ref: Deadlines and scheduling-Footnote-1142172
-Node: Inserting deadline/schedule142327
-Node: Repeated tasks143265
-Node: Progress logging144904
-Node: Closing items145559
-Ref: Closing items-Footnote-1146493
-Ref: Closing items-Footnote-2146562
-Node: Tracking TODO state changes146635
-Node: Clocking work time147491
-Ref: Clocking work time-Footnote-1151137
-Ref: Clocking work time-Footnote-2151215
-Node: Agenda views151341
-Node: Agenda files153292
-Ref: Agenda files-Footnote-1154258
-Ref: Agenda files-Footnote-2154407
-Node: Agenda dispatcher154600
-Node: Built-in agenda views156297
-Node: Weekly/Daily agenda156877
-Node: Global TODO list159819
-Node: Matching tags and properties162097
-Node: Timeline163186
-Node: Stuck projects163858
-Node: Presentation and sorting165709
-Node: Categories166500
-Node: Time-of-day specifications167164
-Node: Sorting of agenda items169135
-Node: Agenda commands170417
-Node: Custom agenda views177503
-Node: Storing searches178222
-Node: Block agenda180134
-Node: Setting Options181364
-Node: Exporting Agenda Views184103
-Ref: Exporting Agenda Views-Footnote-1188387
-Ref: Exporting Agenda Views-Footnote-2188444
-Node: Extracting Agenda Information for other programs188630
-Node: Embedded LaTeX192756
-Ref: Embedded LaTeX-Footnote-1193850
-Node: Math symbols194040
-Node: Subscripts and Superscripts194807
-Node: LaTeX fragments195653
-Ref: LaTeX fragments-Footnote-1197889
-Node: Processing LaTeX fragments198151
-Node: CDLaTeX mode199099
-Ref: CDLaTeX mode-Footnote-1201585
-Node: Exporting201733
-Node: ASCII export203047
-Node: HTML export204337
-Node: Export commands204956
-Node: Quoting HTML tags206200
-Node: Links206830
-Node: Images207527
-Ref: Images-Footnote-1208398
-Node: CSS support208459
-Ref: CSS support-Footnote-1209778
-Node: XOXO export209891
-Node: iCalendar export210330
-Node: Text interpretation211549
-Node: Comment lines212140
-Node: Initial text212535
-Node: Footnotes214204
-Node: Enhancing text215019
-Ref: Enhancing text-Footnote-1216878
-Node: Export options216968
-Node: Publishing218913
-Ref: Publishing-Footnote-1219709
-Node: Configuration219905
-Node: Project alist220623
-Node: Sources and destinations221689
-Node: Selecting files222419
-Node: Publishing action223167
-Node: Publishing options224400
-Node: Publishing links226552
-Node: Project page index228065
-Node: Sample configuration228843
-Node: Simple example229335
-Node: Complex example230008
-Node: Triggering publication232084
-Node: Miscellaneous232769
-Node: Completion233403
-Node: Customization235073
-Node: In-buffer settings235656
-Node: The very busy C-c C-c key240989
-Node: Clean view242633
-Node: TTY keys245210
-Node: Interaction246820
-Node: Cooperation247217
-Node: Conflicts250093
-Node: Bugs252096
-Node: Extensions and Hacking253592
-Node: Extensions254263
-Node: Tables in arbitrary syntax256210
-Node: Radio tables257287
-Node: A LaTeX example259790
-Ref: A LaTeX example-Footnote-1263436
-Ref: A LaTeX example-Footnote-2263584
-Node: Translator functions264019
-Ref: Translator functions-Footnote-1267128
-Node: Dynamic blocks267216
-Node: Special agenda views269188
-Ref: Special agenda views-Footnote-1271498
-Node: Using the property API271758
-Node: History and Acknowledgments273239
-Node: Index279623
-Node: Key Index312363
+Node: Introduction12513
+Node: Summary12928
+Node: Installation16080
+Node: Activation17458
+Node: Feedback18707
+Node: Document structure20783
+Node: Outlines21675
+Node: Headlines22335
+Ref: Headlines-Footnote-123343
+Node: Visibility cycling23442
+Ref: Visibility cycling-Footnote-125652
+Ref: Visibility cycling-Footnote-225710
+Ref: Visibility cycling-Footnote-325760
+Node: Motion26030
+Node: Structure editing26984
+Node: Archiving29810
+Node: ARCHIVE tag30368
+Node: Moving subtrees32161
+Node: Sparse trees33472
+Ref: Sparse trees-Footnote-135604
+Ref: Sparse trees-Footnote-235786
+Node: Plain lists35901
+Ref: Plain lists-Footnote-140098
+Ref: Plain lists-Footnote-240456
+Node: Drawers40637
+Node: orgstruct-mode41475
+Node: Tables42375
+Node: Built-in table editor42956
+Node: Narrow columns50195
+Ref: Narrow columns-Footnote-152130
+Node: Column groups52176
+Node: orgtbl-mode53709
+Node: The spreadsheet54512
+Node: References55599
+Ref: References-Footnote-160063
+Node: Formula syntax for Calc60352
+Node: Formula syntax for Lisp62809
+Node: Field formulas64527
+Node: Column formulas65835
+Node: Editing and debugging formulas67434
+Node: Updating the table71587
+Node: Advanced features72622
+Node: Hyperlinks77147
+Node: Link format77920
+Node: Internal links79213
+Ref: Internal links-Footnote-181138
+Node: Radio targets81273
+Node: External links81964
+Node: Handling links84368
+Ref: Handling links-Footnote-189655
+Ref: Handling links-Footnote-289892
+Node: Link abbreviations89966
+Node: Search options91645
+Ref: Search options-Footnote-193425
+Node: Custom searches93506
+Node: Remember94554
+Node: Setting up remember95541
+Node: Remember templates96123
+Ref: Remember templates-Footnote-199569
+Node: Storing notes99667
+Node: TODO items101554
+Node: TODO basics102531
+Node: TODO extensions104295
+Node: Workflow states105114
+Ref: Workflow states-Footnote-1106289
+Node: TODO types106382
+Ref: TODO types-Footnote-1107965
+Node: Multiple sets in one file108047
+Node: Per file keywords109658
+Ref: Per file keywords-Footnote-1110947
+Node: Priorities111148
+Node: Breaking down tasks112758
+Ref: Breaking down tasks-Footnote-1113278
+Node: Checkboxes113374
+Node: Tags116129
+Node: Tag inheritance116901
+Node: Setting tags117838
+Ref: Setting tags-Footnote-1122361
+Ref: Setting tags-Footnote-2122473
+Node: Tag searches122556
+Node: Properties and columns125273
+Node: Property syntax126378
+Node: Special properties128538
+Node: Property searches129454
+Node: Column view130109
+Node: Defining columns131277
+Node: Scope of column definitions131675
+Node: Column attributes132597
+Node: Using column view134845
+Node: Property API136832
+Node: Timestamps137186
+Node: Time stamps137647
+Ref: Time stamps-Footnote-1140075
+Node: Creating timestamps140191
+Node: The date/time prompt142265
+Ref: The date/time prompt-Footnote-1144253
+Node: Custom time format144359
+Node: Deadlines and scheduling146051
+Ref: Deadlines and scheduling-Footnote-1147401
+Node: Inserting deadline/schedule147556
+Node: Repeated tasks148494
+Node: Progress logging150133
+Node: Closing items150788
+Ref: Closing items-Footnote-1151722
+Ref: Closing items-Footnote-2151791
+Node: Tracking TODO state changes151864
+Node: Clocking work time152720
+Ref: Clocking work time-Footnote-1156366
+Ref: Clocking work time-Footnote-2156444
+Node: Agenda views156570
+Node: Agenda files158521
+Ref: Agenda files-Footnote-1159487
+Ref: Agenda files-Footnote-2159636
+Node: Agenda dispatcher159829
+Node: Built-in agenda views161526
+Node: Weekly/Daily agenda162106
+Node: Global TODO list165048
+Node: Matching tags and properties167326
+Node: Timeline168415
+Node: Stuck projects169087
+Node: Presentation and sorting170938
+Node: Categories171729
+Node: Time-of-day specifications172393
+Node: Sorting of agenda items174364
+Node: Agenda commands175646
+Node: Custom agenda views182927
+Node: Storing searches183646
+Node: Block agenda185558
+Node: Setting Options186788
+Node: Exporting Agenda Views189527
+Ref: Exporting Agenda Views-Footnote-1193811
+Ref: Exporting Agenda Views-Footnote-2193868
+Node: Extracting Agenda Information for other programs194054
+Node: Embedded LaTeX198180
+Ref: Embedded LaTeX-Footnote-1199274
+Node: Math symbols199464
+Node: Subscripts and Superscripts200231
+Node: LaTeX fragments201077
+Ref: LaTeX fragments-Footnote-1203313
+Node: Processing LaTeX fragments203575
+Node: CDLaTeX mode204523
+Ref: CDLaTeX mode-Footnote-1207009
+Node: Exporting207157
+Node: ASCII export208471
+Node: HTML export209761
+Node: Export commands210380
+Node: Quoting HTML tags211624
+Node: Links212254
+Node: Images212951
+Ref: Images-Footnote-1213822
+Node: CSS support213883
+Ref: CSS support-Footnote-1215202
+Node: XOXO export215315
+Node: iCalendar export215754
+Node: Text interpretation216973
+Node: Comment lines217564
+Node: Initial text217959
+Node: Footnotes219628
+Node: Enhancing text220443
+Ref: Enhancing text-Footnote-1222302
+Node: Export options222392
+Node: Publishing224337
+Ref: Publishing-Footnote-1225133
+Node: Configuration225277
+Node: Project alist225995
+Node: Sources and destinations227061
+Node: Selecting files227791
+Node: Publishing action228539
+Node: Publishing options229772
+Node: Publishing links231924
+Node: Project page index233437
+Node: Sample configuration234215
+Node: Simple example234707
+Node: Complex example235380
+Node: Triggering publication237456
+Node: Miscellaneous238141
+Node: Completion238775
+Node: Customization240445
+Node: In-buffer settings241028
+Node: The very busy C-c C-c key246367
+Node: Clean view248128
+Node: TTY keys250705
+Node: Interaction252315
+Node: Cooperation252712
+Node: Conflicts255588
+Node: Bugs257591
+Node: Extensions and Hacking259087
+Node: Extensions259758
+Node: Tables in arbitrary syntax261705
+Node: Radio tables262782
+Node: A LaTeX example265285
+Ref: A LaTeX example-Footnote-1268931
+Ref: A LaTeX example-Footnote-2269079
+Node: Translator functions269514
+Ref: Translator functions-Footnote-1272623
+Node: Dynamic blocks272711
+Node: Special agenda views274683
+Ref: Special agenda views-Footnote-1276993
+Node: Using the property API277253
+Node: History and Acknowledgments278734
+Node: Index285118
+Node: Key Index318864
 
 End Tag Table

Dosya farkı çok büyük olduğundan ihmal edildi
+ 605 - 195
org.el


BIN
org.pdf


+ 260 - 120
org.texi

@@ -3,7 +3,7 @@
 @setfilename ../info/org
 @settitle Org Mode Manual
 
-@set VERSION 5.01
+@set VERSION 5.02
 @set DATE July 2007
 
 @dircategory Emacs
@@ -81,7 +81,7 @@ Software Foundation raise funds for GNU development.''
 * Hyperlinks::                  Notes in context
 * TODO items::                  Every tree branch can be a TODO item
 * Tags::                        Tagging headlines and matching sets of tags
-* Properties::                  
+* Properties and columns::      
 * Timestamps::                  Assign date and time to items
 * Agenda views::                Collecting information into views
 * Embedded LaTeX::              LaTeX fragments and formulas
@@ -113,7 +113,8 @@ Document Structure
 * Archiving::                   Move done task trees to a different place
 * Sparse trees::                Matches embedded in context
 * Plain lists::                 Additional structure within an entry
-* Drawers::                     
+* Drawers::                     Tucking stuff away
+* orgstruct-mode::              Structure editing outside Org-mode
 
 Archiving
 
@@ -181,7 +182,7 @@ Tags
 * Setting tags::                How to assign tags to a headline
 * Tag searches::                Searching for combinations of tags
 
-Properties
+Properties and Columns
 
 * Property syntax::             How properties are spelled out
 * Special properties::          Access to other Org-mode features
@@ -194,6 +195,11 @@ Column View
 * Defining columns::            The COLUMNS format property
 * Using column view::           How to create and use column view
 
+Defining Columns
+
+* Scope of column definitions:: 
+* Column attributes::           
+
 Timestamps
 
 * Time stamps::                 Assigning a time to a tree entry
@@ -379,7 +385,7 @@ tags etc are created dynamically when you need them.
 Org-mode keeps simple things simple.  When first fired up, it should
 feel like a straightforward, easy to use outliner.  Complexity is not
 imposed, but a large amount of functionality is available when you need
-it.  Org-mode can be used on different levels and in different ways, for
+it.  Org-mode is a toolbox and can be used in different ways, for
 example as:
 
 @example
@@ -389,6 +395,7 @@ example as:
 @r{@bullet{} TODO list editor}
 @r{@bullet{} full agenda and planner with deadlines and work scheduling}
 @r{@bullet{} environment to implement David Allen's GTD system}
+@r{@bullet{} a basic database application}
 @r{@bullet{} simple hypertext system, with HTML export}
 @r{@bullet{} publishing tool to create a set of interlinked webpages}
 @end example
@@ -396,7 +403,9 @@ example as:
 Org-mode's automatic, context sensitive table editor with spreadsheet
 capabilities can be integrated into any major mode by activating the
 minor Orgtbl-mode.  Using a translation step, it can be used to maintain
-tables in arbitrary file types, for example in LaTeX.
+tables in arbitrary file types, for example in LaTeX.  The structure
+editing and list creation capabilities can be used outside Org-mode with
+the minor Orgstruct-mode.
 
 @cindex FAQ
 There is a website for Org-mode which provides links to the newest
@@ -468,9 +477,10 @@ make install-info
 
 @iftex
 @b{Important:} @i{If you use copy-and-paste to copy lisp code from the
-PDF documentation to your .emacs file, the single quote character comes
-out incorrectly and the code will not work.  You need to fix the single
-quotes by hand, or copy from Info documentation.}
+PDF documentation as viewed by Acrobat reader to your .emacs file, the
+single quote character comes out incorrectly and the code will not work.
+You need to fix the single quotes by hand, or copy from Info
+documentation.}
 @end iftex
 
 Add the following lines to your @file{.emacs} file.  The last two lines
@@ -580,7 +590,8 @@ edit the structure of the document.
 * Archiving::                   Move done task trees to a different place
 * Sparse trees::                Matches embedded in context
 * Plain lists::                 Additional structure within an entry
-* Drawers::                     
+* Drawers::                     Tucking stuff away
+* orgstruct-mode::              Structure editing outside Org-mode
 @end menu
 
 @node Outlines, Headlines, Document structure, Document structure
@@ -1121,14 +1132,15 @@ bullets (@samp{-}, @samp{+}, @samp{*}, @samp{1.}, @samp{1)}).
 With prefix arg, select the nth bullet from this list.
 @end table
 
-@node Drawers,  , Plain lists, Document structure
+@node Drawers, orgstruct-mode, Plain lists, Document structure
 @section Drawers
 @cindex drawers
+@cindex visibility cycling, drawers
 
 Sometimes you want to keep information associated with an entry, but you
-normally don't want to see it, except when explicitly asking for it.
-For this, Org-mode has @emph{drawers}.  Drawers need to be configured
-with the variable @code{org-drawers}, and look like this:
+normally don't want to see it.  For this, Org-mode has @emph{drawers}.
+Drawers need to be configured with the variable @code{org-drawers}, and
+look like this:
 
 @example
 ** This is a headline
@@ -1143,7 +1155,30 @@ Visibility cycling (@pxref{Visibility cycling}) on the headline will
 hide and show the entry, but keep the drawer collapsed to a single line.
 In order to look inside the drawer, you need to move the cursor to the
 drawer line and press @key{TAB} there.  Org-mode uses a drawer for
-storing properties (@pxref{Properties}).
+storing properties (@pxref{Properties and columns}).
+
+@node orgstruct-mode,  , Drawers, Document structure
+@section The Orgstruct minor mode
+@cindex orgstruct-mode
+@cindex minor mode for structure editing
+
+If you like the intuitive way the Org-mode structure editing and list
+formatting works, you might want to use these commands in other modes
+like text-mode or mail-mode as well.  The minor mode Orgstruct-mode
+makes this possible.  You can always toggle the mode with @kbd{M-x
+orgstruct-mode}.  To turn it on by default, for example in mail mode,
+use
+
+@lisp
+(add-hook 'mail-mode-hook 'turn-on-orgstruct)
+@end lisp
+
+When this mode is active and the cursor is on a line that looks to
+Org-mode like a headline of the first line of a list item, most
+structure editing commands will work, even if the same keys normally
+have different functionality in the major mode you are using.  If the
+cursor is not in one of those special lines, Orgstruct-mode lurks
+silently in the shadow.
 
 @node Tables, Hyperlinks, Document structure, Top
 @chapter Tables
@@ -1611,15 +1646,15 @@ line like
 @end example
 
 @noindent
-Also properties (@pxref{Properties}) can be used as constants in table
-formulas: For a property @samp{:XYZ:} use the name @samp{$PROP_XYZ}, and
-the property will be searched in the current outline entry and in the
-hierarchy above it.  If you have the @file{constants.el} package, it
-will also be used to resolve constants, including natural constants like
-@samp{$h} for Planck's constant, and units like @samp{$km} for
-kilometers@footnote{@file{Constant.el} can supply the values of
-constants in two different unit systems, @code{SI} and @code{cgs}.
-Which one is used depends on the value of the variable
+Also properties (@pxref{Properties and columns}) can be used as
+constants in table formulas: For a property @samp{:XYZ:} use the name
+@samp{$PROP_XYZ}, and the property will be searched in the current
+outline entry and in the hierarchy above it.  If you have the
+@file{constants.el} package, it will also be used to resolve constants,
+including natural constants like @samp{$h} for Planck's constant, and
+units like @samp{$km} for kilometers@footnote{@file{Constant.el} can
+supply the values of constants in two different unit systems, @code{SI}
+and @code{cgs}.  Which one is used depends on the value of the variable
 @code{constants-unit-system}.  You can use the @code{#+STARTUP} options
 @code{constSI} and @code{constcgs} to set this value for the current
 buffer.}.  Column names and parameters can be specified in special table
@@ -3030,7 +3065,7 @@ back into synch.  Or simply toggle any checkbox twice with @kbd{C-c C-c}.
 @end table
 
 
-@node Tags, Properties, TODO items, Top
+@node Tags, Properties and columns, TODO items, Top
 @chapter Tags
 @cindex tags
 @cindex headline tagging
@@ -3286,8 +3321,8 @@ instead of any TAG an expression like @samp{LEVEL=3}.  For example, a
 search @samp{+LEVEL=3+BOSS/-DONE} lists all level three headlines that
 have the tag BOSS and are @emph{not} marked with the todo keyword DONE.
 
-@node Properties, Timestamps, Tags, Top
-@chapter Properties
+@node Properties and columns, Timestamps, Tags, Top
+@chapter Properties and Columns
 @cindex properties
 
 Properties are a set of key-value pairs associated with an entry.  There
@@ -3298,7 +3333,8 @@ tags like @code{:release_1:}, @code{:release_2:}, it can be more
 efficient to use a property @code{RELEASE} with a value @code{1.0} or
 @code{2.0}.  Second, you can use properties to implement (very basic)
 database capabilities in an Org-mode buffer, for example to create a
-list of Music CD's you own.
+list of Music CD's you own.  You can edit and view properties
+conveniently in column view (@pxref{Column view}).
 
 @menu
 * Property syntax::             How properties are spelled out
@@ -3308,8 +3344,10 @@ list of Music CD's you own.
 * Property API::                Properties for Lisp programmers
 @end menu
 
-@node Property syntax, Special properties, Properties, Properties
+@node Property syntax, Special properties, Properties and columns, Properties and columns
 @section Property Syntax
+@cindex property syntax
+@cindex drawer, for properties
 
 Properties are key-value pairs.  They need to be inserted into a special
 drawer (@pxref{Drawers}) with the name @code{PROPERTIES}.  Each property
@@ -3324,26 +3362,65 @@ first, and the value after it.  Here is an example:
     :Title:     Goldberg Variations
     :Composer:  J.S. Bach
     :Artist:    Glen Gould 
-    :END:
+    :Publisher: Deutsche Grammphon
+    :NDisks:    1
+    :END:       
+@end example
+
+You may define the allowed values for a particular property @samp{XYZ}
+by setting a property @samp{XYZ_ALL}.  This special property is
+@emph{inherited}, so if you set it in a level 1 entry, it will apply to
+the entire tree.  When allowed values are defined, setting the
+corresponding property becomes easier and is less prone to typing
+errors.  For the example with the CD collection, we can predefine
+publishers and the number of disks in a box like this:
+
+@example
+* CD collection
+  :PROPERTIES:
+  :NDisks_ALL:  1 2 3 4
+  :Publisher_ALL: "Deutsche Grammophon" Phillips EMI
+  :END:
 @end example
 
 @noindent
-The following commands help to insert properties:
+The following commands help to work with properties:
 
 @table @kbd
 @kindex M-@key{TAB}
 @item M-@key{TAB}
 After an initial colon in a line, complete property keys.  All keys used
 in the current file will be offered as possible completions.
+@item M-x org-insert-property-drawer
+Insert a property drawer into the current entry.  The drawer will be
+inserted early in the entry, but after the lines with planning
+information like deadlines.
+@kindex C-c C-c
+@item C-c C-c
+With the cursor in a property drawer, this executes property commands.
+@item C-c C-c s
+Set a property in the current entry.  Both the property and the value
+can be inserted using completion.
+@kindex S-@key{right}
+@kindex S-@key{left}
+@item S-@key{left}/@key{right}
+Switch property at point to the next/previous allowed value.
+@item C-c C-c d
+Remove a property from the current entry.
+@item C-c C-c D
+Globally remove a property, from all entries in the current file.
 @end table
 
-
-
-@node Special properties, Property searches, Property syntax, Properties
+@node Special properties, Property searches, Property syntax, Properties and columns
 @section Special Properties
+@cindex properties, special
 
-Several properties are special, because they can be used to access other
-features of Org-mode like the TODO status:
+Special properties provide alternative access method to Org-mode
+features discussed in the previous chapters, like the TODO state or the
+priority of an entry.  This interface exists so that you can include
+these states into columns view (@pxref{Column view}).  The following
+property names are special and should not be used as keys in the
+properties drawer:
 
 @example
 TODO         @r{The TODO keyword of the entry.}
@@ -3354,8 +3431,9 @@ DEADLINE     @r{The deadline time string, without the angular brackets.}
 SCHEDULED    @r{The scheduling time stamp, without the angular brackets.}
 @end example
 
-@node Property searches, Column view, Special properties, Properties
+@node Property searches, Column view, Special properties, Properties and columns
 @section Property searches
+@cindex properties, searching
 
 To create sparse trees and special lists with selection based on
 properties, the same commands are used as for tag searches (@pxref{Tag
@@ -3371,23 +3449,23 @@ also have a priority value @samp{A}, a @samp{:coffee:} property with the
 value @samp{unlimited}, and a @samp{:with:} property that is matched by
 the regular expression @samp{Sarah\|Denny}.
 
-@node Column view, Property API, Property searches, Properties
+@node Column view, Property API, Property searches, Properties and columns
 @section Column View
 
-If different items in a document have similar properties, it can be nice
-to view and edit those properties in a table-like format, in
-@emph{column view}.  Org-mode implements columns by overlaying a tabular
-structure over the headline of an item.  So the column view does not use
-a special buffer, it happens in exactly the same buffer where the
-outline is, and only temporarily changes the look of this buffer - not
-the content.  This has the advantage that you can still change the
-visibility of the outline tree.  For example, you get a compact table by
-switching to CONTENTS view, but you can still open, read, and edit the
-entry below each headline.  Or, you can switch to column view after
-executing a sparse tree command and in this way get a table only for the
-selected items.  Column view also works in agenda buffers (@pxref{Agenda
-views}) where queries have collected selected items, possibly from a
-number of files.
+A great way to view and edit properties in aan outline tree is
+@emph{column view}.  In column view, each outline item is turned into a
+table row.  Columns in this table provide access to properties of the
+entries.  Org-mode implements columns by overlaying a tabular structure
+over the headline of each item.  While the headlines have been turned
+into a table row, you can still change the visibility of the outline
+tree.  For example, you get a compact table by switching to CONTENTS
+view (@kbd{S-@key{TAB} S-@key{TAB}}, or simple @kbd{c} while column view
+is active), but you can still open, read, and
+edit the entry below each headline.  Or, you can switch to column view
+after executing a sparse tree command and in this way get a table only
+for the selected items.  Column view also works in agenda buffers
+(@pxref{Agenda views}) where queries have collected selected items,
+possibly from a number of files.
 
 @menu
 * Defining columns::            The COLUMNS format property
@@ -3396,81 +3474,122 @@ number of files.
 
 @node Defining columns, Using column view, Column view, Column view
 @subsection Defining Columns
+@cindex column view, for properties
+@cindex properties, column view
 
-Setting up a column view first requires defining the columns.  A column
-definition is a property itself and looks like this:
+Setting up a column view first requires defining the columns.  This is
+done by defining a column format line.
 
-@example
-:COLUMNS: %25ITEM %TAGS %PRIORITY %TODO
-@end example
+@menu
+* Scope of column definitions::  Where defined, where valid?
+* Column attributes::           Appearance and content of a column
+@end menu
 
-This definition means that column 1 should be the first 25 characters of
-the item itself, i.e. of the headline.  You probably always should start
-the column definition with the ITEM specifier - just select a useful
-width for it.  The other specifiers create columns for the local tags,
-for the priority and for the TODO state.  When no width is given after
-the @samp{%} character, the column will be exactly as wide as it need to
-be in order to fully display all values.
+@node Scope of column definitions, Column attributes, Defining columns, Defining columns
+@subsubsection Scope of column definitions
 
-If a @code{COLUMNS} property is present in an entry, it defines
-columns for the entry itself, and for the entire subtree below it.
-Since the column definition is part of the hierarchical structure of the
-document, you can define columns on level 1 that are general enough for
-all sublevels, and more specific columns further down, when you edit a deeper
-part of the tree.  Here is an example:
+To define a column format for an entire file, use a line like
 
 @example
-* People
-  :PROPERTIES:
-  :COLUMNS: %25ITEM %Name
-  :END:
-** Family
-   :PROPERTIES:
-   :COLUMNS: %25ITEM %Name %3Age
-   :END:
-*** Sam
-    Info about Sam, including a property list with Name and Age.
-*** Sarah
-    Info about Sarah, including a property list with Name and Age.
-** Office
+#+COLUMNS: %25ITEM %TAGS %PRIORITY %TODO
+@end example
+
+To specify a format that only applies to a specific tree, add a COLUMNS
+property to the top node of that tree, for example
+@example
+** Top node for columns view
    :PROPERTIES:
-   :COLUMNS: %25ITEM %Name %Function %Salary
+   :COLUMNS: %25ITEM %TAGS %PRIORITY %TODO
    :END:
-*** Boss
-    Info about the Boss, including a property list with Name,
-    Function and Salary (if only we knew....).
 @end example
 
-Now we have defined three different sets of columns.  If you switch to
-column view in the @emph{Family} section, you will get a different table
-than if you do it in the @emph{Office} section.  However, if you switch
-to column view with the cursor on the @emph{People} section, the table
-will cover all entries, but contain only the @emph{Name} column.
+If a @code{COLUMNS} property is present in an entry, it defines columns
+for the entry itself, and for the entire subtree below it.  Since the
+column definition is part of the hierarchical structure of the document,
+you can define columns on level 1 that are general enough for all
+sublevels, and more specific columns further down, when you edit a
+deeper part of the tree.
+
+@node Column attributes,  , Scope of column definitions, Defining columns
+@subsubsection Column attributes
+A column definition sets the attributes of a column.  The general
+definition looks like this:
+
+@example
+ %[width]property[(title)][@{summary-type@}]
+@end example
 
-If no COLUMNS property applies to a given location, Org-mode uses a
-default format specified in the variable
-@code{org-default-columns-format}.  This format in particular also
-applies when column view is invoked with the cursor before the first
-headline.  You can set the default format on a per-file basis with a
-line (don't forget to press @kbd{C-c C-c} to activate any changes to
-this line).
+@noindent
+Except for the percent sign and the property name, all items are
+optional.  The individual parts have the following meaning:
 
 @example
-#+COLUMNS: %25ITEM ....."
+width           @r{An integer specifying the width of the column in characters.}
+                @r{If omitted, the width will be determined automatically.}
+property        @r{The property that should be edited in this column.}
+(title)         @r{The header text for the column. If omitted, the}
+                @r{property name is used.}
+@{summary-type@}  @r{The summary type.  If specified, the column values for}
+                @r{parent nodes are computed from the children.}
+                @r{Supported summary types are:}
+                @{+@}  @r{Sum numbers in this column.}
+                @{:@}  @r{Sum times, HH:MM:SS, plain numbers are hours.}
+                @{X@}  @r{Checkbox status, [X] if all children are [X].}
 @end example
 
+@noindent
+Here is an example for a complete columns definition, along with allowed
+values.
+
+@example
+:COLUMNS:  %20ITEM %9Approved(Approved?)@{X@} %Owner %11Status %10Time_Spent@{:@}
+:Owner_ALL:    Tammy Mark Karl Lisa Don
+:Status_ALL:   "In progress" "Not started yet" "Finished" ""
+:Approved_ALL: "[ ]" "[X]"
+@end example
+
+The first column, @samp{%25ITEM}, means the first 25 characters of the
+item itself, i.e. of the headline.  You probably always should start the
+column definition with the ITEM specifier.  The other specifiers create
+columns @samp{Owner} with a list of names as allowed values, for
+@samp{Status} with four different possible values, and for a checkbox
+field @samp{Approved}.  When no width is given after the @samp{%}
+character, the column will be exactly as wide as it needs to be in order
+to fully display all values.  The @samp{Approved} column does have a
+modified title (@samp{Approved?}, with a question mark).  Summaries will
+be created for the @samp{Time_Spent} column by adding time duration
+expressions like HH:MM, and for the @samp{Approved} column, by providing
+an @samp{[X]} status if all children have been checked.
+
 @node Using column view,  , Defining columns, Column view
 @subsection Using Column View
 
 @table @kbd
+@tsubheading{Turning column view on and off}
 @kindex C-c C-x C-c
 @item C-c C-x C-c
 Create the column view for the local environment.  This command searches
 the hierarchy, up from point, for a @code{COLUMNS} property that defines
 a format.  When one is found, the column view table is established for
-the entire subtree.
+the entire tree, starting from the entry that contains the @code{COLUMNS}
+property.  If none is found, the format is taken from the @code{#+COLUMNS}
+line or from the variable @code{org-columns-default-format}, and column
+view is established for the current entry and its subtree.
+@kindex q
+@item q
+Exit column view.
+@tsubheading{Editing values}
 @item @key{left} @key{right} @key{up} @key{down}
 Move through the column view from field to field.
+@kindex S-@key{left}
+@kindex S-@key{right}
+@item  S-@key{left}/@key{right}
+Switch to the next/previous allowed value of the field.  For this, you
+have to have specified allowed values for a property.
+@kindex n
+@kindex p
+@itemx  n / p
+Same as @kbd{S-@key{left}/@key{right}}
 @kindex e
 @item e
 Edit the property at point.  For the special properties, this will
@@ -3481,20 +3600,36 @@ or fast selection interface will pop up.
 @item v
 View the full value of this property.  This is useful if the width of
 the column is smaller than that of the value.
-@kindex q
-@item q
-Exit column view.
+@kindex a
+@item a
+Edit the list of allowed values for this property.  If the list is found
+in the hierarchy, the modified values is stored there.  If no list is
+found, the new value is stored in the first entry that is part of the
+current column view.
+@tsubheading{Modifying the table structure}
+@kindex <
+@kindex >
+@item < / >
+Make the column narrower/wider by one character.
+@kindex S-M-@key{right}
+@item S-M-@key{right}
+Insert a new column, to the right of the current column.
+@kindex S-M-@key{left}
+@item S-M-@key{left}
+Delete the current column.
 @end table
 
-@node Property API,  , Column view, Properties
+@node Property API,  , Column view, Properties and columns
 @section The Property API
+@cindex properties, API
+@cindex API, for properties
 
 There is a full API for accessing and changing properties.  This API can
 be used by Emacs Lisp programs to work with properties and to implement
 features based on them.  For more information see @ref{Using the
 property API}.
 
-@node Timestamps, Agenda views, Properties, Top
+@node Timestamps, Agenda views, Properties and columns, Top
 @chapter Timestamps
 @cindex time stamps
 @cindex date stamps
@@ -4604,7 +4739,9 @@ Delete other windows.
 @kindex m
 @kindex y
 @item d w m y
-Switch to day/week/month/year view.
+Switch to day/week/month/year view.  When switching to day or week view,
+this setting becomes the default for subseqent agenda commands.  Since
+month and year views are slow to create, the do not become the default.
 @c
 @kindex D
 @item D
@@ -5947,16 +6084,15 @@ skip:   @r{turn on/off skipping the text before the first heading}
 @chapter Publishing
 @cindex publishing
 
-Org-mode includes@footnote{@file{org-publish.el} is not yet part of
-Emacs, so if you are using @file{org.el} as it comes with Emacs, you
-need to download this file separately.  Also make sure org.el is at
-least version 4.27.} a publishing management system
-that allows you to configure automatic HTML conversion of
-@emph{projects} composed of interlinked org files.  This system is
-called @emph{org-publish}.  You can also configure org-publish to
-automatically upload your exported HTML pages and related attachments,
-such as images and source code files, to a web server.  Org-publish turns
-org-mode into a web-site authoring tool.
+Org-mode includes@footnote{@file{org-publish.el} is not distributed with
+Emacs 21, if you are still using Emacs 21, you need you need to download
+this file separately.} a publishing management system that allows you to
+configure automatic HTML conversion of @emph{projects} composed of
+interlinked org files.  This system is called @emph{org-publish}.  You
+can also configure org-publish to automatically upload your exported
+HTML pages and related attachments, such as images and source code
+files, to a web server.  Org-publish turns org-mode into a web-site
+authoring tool.
 
 Org-publish has been contributed to Org-mode by David O'Toole.
 
@@ -6118,7 +6254,7 @@ respective variable for details.
 
 When a property is given a value in org-publish-project-alist, its
 setting overrides the value of the corresponding user variable (if any)
-during publishing.  options set within a file (@pxref{Export
+during publishing.  Options set within a file (@pxref{Export
 options}), however, override everything.
 
 @node Publishing links, Project page index, Publishing options, Configuration
@@ -6445,8 +6581,8 @@ Logging TODO state changes and clock intervals (variable
 logging          @r{record a timestamp when an item is marked DONE}
 nologging        @r{don't record when items are marked DONE}
 lognotedone      @r{record timestamp and a note when DONE}
-lognotestate     @r{record timestamp, note when TODO state changes}
-logrepeat        @r{record a not when re-instating a repeating item}
+lognotestate     @r{record timestamp and a note when TODO state changes}
+logrepeat        @r{record a note when re-instating a repeating item}
 nologrepeat      @r{do not record when re-instating repeating item}
 lognoteclock-out @r{record timestamp and a note when clocking out}
 @end example
@@ -6531,6 +6667,9 @@ default location.
 If the cursor is on a @code{<<<target>>>}, update radio targets and
 corresponding links in this buffer.
 @item
+If the cursor is in a property line or at the start or end of a property
+drawer, offer property commands.
+@item
 If the cursor is in a plain list item with a checkbox, toggle the status
 of the checkbox.
 @item
@@ -7289,6 +7428,7 @@ MATCH is being ignored."
 @node Using the property API,  , Special agenda views, Extensions and Hacking
 @section Using the property API
 @cindex API, for properties
+@cindex properties, API
 
 Here is a description of the functions that can be used to work with
 properties.

BIN
orgcard.pdf


+ 39 - 19
orgcard.tex

@@ -1,5 +1,5 @@
 % Reference Card for Org Mode
-\def\orgversionnumber{5.01}
+\def\orgversionnumber{5.02}
 \def\versionyear{2007}          % latest update
 \def\year{2007}                 % latest copyright year
 
@@ -544,6 +544,24 @@ after  ``{\tt :}'', and dictionary words elsewhere.
 \key{create sparse tree with matching tags}{C-c \\}
 \key{globally (agenda) match tags at cursor}{C-c C-o}
 
+\section{Properties and Column View}
+
+\key{special commands in property lines}{C-c C-c}
+\key{next/previous allowed value}{S-left/right}
+\key{turn on column view}{C-c C-x C-c}
+
+\key{quit column view}{q}
+\key{next/previous allowed value}{S-left/right}
+\key{next/previous allowed value}{n / p}
+\key{edit value}{e}
+\key{edit allowed values list}{a}
+\key{show value}{v}
+\key{make column wider/narrower}{> / <}
+\key{move column left/right}{M-left/right}
+\key{add new column}{M-S-right}
+\key{Delete current column}{M-S-left}
+
+
 \section{Timestamps}
 
 \key{prompt for date and insert timestamp}{C-c .}
@@ -566,6 +584,8 @@ after  ``{\tt :}'', and dictionary words elsewhere.
 %\key{... forward/backward one month}{M-S-LEFT/RIGT}
 \key{Toggle custom format display for dates/times}{C-c C-x C-t}
 
+\newcolumn
+
 {\bf Clocking time}
 
 \key{start clock on current item}{C-c C-x C-i}
@@ -575,12 +595,6 @@ after  ``{\tt :}'', and dictionary words elsewhere.
 \key{remove displayed times}{C-c C-c}
 \key{insert/update table with clock report}{C-c C-x C-r}
 
-\section{LaTeX and cdlatex-mode}
-
-\key{preview LaTeX fragment}{C-c C-x C-l}
-\key{Expand abbreviation (cdlatex-mode)}{TAB}
-\key{Insert/modify math symbol (cdlatex-mode)}{` / '}
-
 \section{Agenda Views}
 
 \key{add/move current file to front of agenda}{C-c [}
@@ -648,6 +662,7 @@ To set categories, add lines like$^2$:
 \key{change timestamp to today}{>}
 \key{insert new entry into diary}{i}
 
+\newcolumn
 \key{start the clock on current item (clock-in)}{I}
 \key{stop the clock (clock-out)}{O}
 \key{cancel current clock}{X}
@@ -656,7 +671,6 @@ To set categories, add lines like$^2$:
 
 \key{Open link in current line}{C-c C-o}
 
-\newcolumn
 {\bf Calendar commands}
 
 \key{find agenda cursor date in calendar}{c}
@@ -678,6 +692,12 @@ Include Emacs diary entries into Org-mode agenda with:
 (setq org-agenda-include-diary t)
 \endexample
 
+\section{LaTeX and cdlatex-mode}
+
+\key{preview LaTeX fragment}{C-c C-x C-l}
+\key{Expand abbreviation (cdlatex-mode)}{TAB}
+\key{Insert/modify math symbol (cdlatex-mode)}{` / '}
+
 \section{Exporting and Publishing}
 
 Exporting creates files with extensions {\it .txt\/} and {\it .html\/}
@@ -690,17 +710,17 @@ some other place.
 \key{insert template of export options}{C-c C-x t}
 \key{toggle fixed width for entry or region}{C-c :}
 
-{\bf HTML formatting}
-
-\key{make words {\bf bold}}{*bold*}
-\key{make words {\it italic}}{/italic/}
-\key{make words \underbar{underlined}}{_underlined_}
-\key{sub- and superscripts}{x\^{}3, J_dust}
-\key{\TeX{}-like macros}{\\alpha, \\to}
-\key{typeset lines in fixed width font}{start with :}
-\key{tables are exported as HTML tables}{start with |}
-\key{links become HTML links}{http:... etc}
-\key{include html tags}{@<b>...@</b>}
+%{\bf HTML formatting}
+
+%\key{make words {\bf bold}}{*bold*}
+%\key{make words {\it italic}}{/italic/}
+%\key{make words \underbar{underlined}}{_underlined_}
+%\key{sub- and superscripts}{x\^{}3, J_dust}
+%\key{\TeX{}-like macros}{\\alpha, \\to}
+%\key{typeset lines in fixed width font}{start with :}
+%\key{tables are exported as HTML tables}{start with |}
+%\key{links become HTML links}{http:... etc}
+%\key{include html tags}{@<b>...@</b>}
 
 %{\bf Export options}
 %

BIN
orgcard_letter.pdf


Dosya farkı çok büyük olduğundan ihmal edildi
+ 499 - 516
orgcard_letter.ps


Bu fark içinde çok fazla dosya değişikliği olduğu için bazı dosyalar gösterilmiyor