Browse Source

Release 4.75

Carsten Dominik 17 years ago
parent
commit
faa09adf0e
7 changed files with 1058 additions and 565 deletions
  1. 427 339
      org
  2. 1 0
      org-install.el
  3. 415 95
      org.el
  4. BIN
      org.pdf
  5. 214 130
      org.texi
  6. BIN
      orgcard.pdf
  7. 1 1
      orgcard.tex

+ 427 - 339
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 4.74).
+   This manual is for Org-mode (version 4.75).
 
    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 4.74).
+This manual is for Org-mode (version 4.75).
 
    Copyright (C) 2004, 2005, 2006, 2007 Free Software Foundation
 
@@ -145,13 +145,18 @@ Timestamps
 
 * Time stamps::                 Assigning a time to a tree entry
 * Creating timestamps::         Commands which insert timestamps
-* Custom time format::          If you cannot work with the ISO format
-* Repeating items::             Deadlines that come back again and again
+* Deadlines and scheduling::    Planning your work
 * Progress logging::            Documenting when what work was done.
 
 Creating timestamps
 
 * The date/time prompt::        How org-mode helps you entering date and time
+* Custom time format::          Making dates look differently
+
+Deadlines and Scheduling
+
+* Inserting deadline/schedule::
+* Repeated tasks::
 
 Progress Logging
 
@@ -1927,10 +1932,12 @@ insert it into an org-mode file, and to follow the link.
      link, or one of the link type prefixes mentioned in the examples
      above.  All links stored during the current session are part of
      the history for this prompt, so you can access them with <up> and
-     <down>, or with completion(1).  The link will be inserted into the
-     buffer, along with a descriptive text.  If some text was selected
-     when this command is called, the selected text becomes the default
-     description.
+     <down>.  Completion, on the other hand, will help you to insert
+     valid link prefixes like `http:' or `ftp:', including the prefixes
+     defined through link abbreviations (*note Link abbreviations::).
+     The link will be inserted into the buffer(1), along with a
+     descriptive text.  If some text was selected when this command is
+     called, the selected text becomes the default description.
      Note that you don't have to use this command to insert a link.
      Links in Org-mode are plain text, and you can type or paste them
      straight into the buffer.  By using this command, the links are
@@ -2539,6 +2546,14 @@ agenda (*note Weekly/Daily agenda::).
      timestamps::).  Furthermore, these keys are also used by CUA-mode
      (*note Conflicts::).
 
+   You can change the range of allowed priorities by setting the
+variables `org-highest-priority', `org-lowest-priority', and
+`org-default-priority'.  For an individual buffer, you may set these
+values (highest, lowest, default) like this (please make sure that the
+highest priority is earlier in the alphabet than the lowest priority):
+
+     #+PRIORITIES: A C B
+
 
 File: org,  Node: Breaking down tasks,  Next: Checkboxes,  Prev: Priorities,  Up: TODO items
 
@@ -2636,8 +2651,7 @@ planning.
 
 * Time stamps::                 Assigning a time to a tree entry
 * Creating timestamps::         Commands which insert timestamps
-* Custom time format::          If you cannot work with the ISO format
-* Repeating items::             Deadlines that come back again and again
+* Deadlines and scheduling::    Planning your work
 * Progress logging::            Documenting when what work was done.
 
 
@@ -2649,7 +2663,7 @@ File: org,  Node: Time stamps,  Next: Creating timestamps,  Prev: Timestamps,  U
 A time stamp is a specification of a date (possibly with time) in a
 special format, either `<2003-09-16 Tue>' or `<2003-09-16 Tue
 09:39>'(1).  A time stamp can appear anywhere in the headline or body
-of an org-tree entry.  Its presence allows entries to be shown on
+of an org-tree entry.  Its presence causes entries to be shown on
 specific dates in the agenda (*note Weekly/Daily agenda::).  We
 distinguish:
 
@@ -2663,71 +2677,46 @@ PLAIN TIME STAMP
 
           * Meet Peter at the movies <2006-11-01 Wed 19:15>
 
-INACTIVE TIME STAMP
-     Just like a plain time stamp, but with square brackets instead of
-     angular ones.  These time stamps are inactive in the sense that
-     they do _not_ trigger an entry to show up in the agenda.
+TIME STAMP WITH REPEATER INTERVAL
+     A time stamp may contain a _repeater interval_, indicating that it
+     applies not only on the given date, but again and again after a
+     certain interval of N days (d), weeks (w), months(m), or years(y).
+     The following will show up in the agenda every Wednesday:
 
-          * Gillian comes late for the fifth time [2006-11-01 Wed]
+          * Pick up Sam at school <2007-05-16 Wed 12:30 +1w>
+
+DIARY-STYLE SEXP ENTRIES
+     For more complex date specifications, Org-mode supports using the
+     special sexp diary entries implemented in the Emacs calendar/diary
+     package.  For example
+
+          * The nerd meeting on every 2nd Thursday of the month
+            <%%(diary-float t 4 2)>
 
-TIME STAMP RANGE
-     Two time stamps connected by `--' denote a time range.  The
-     headline will be shown on the first and last day of the range, and
-     on any dates that are displayed and fall in the range.  Here is an
+TIME/DATE RANGE
+     Two time stamps connected by `--' denote a range.  The headline
+     will be shown on the first and last day of the range, and on any
+     dates that are displayed and fall in the range.  Here is an
      example:
 
           ** Meeting in Amsterdam
              <2004-08-23 Mon>--<2004-08-26 Thu>
 
-TIME STAMP WITH SCHEDULED KEYWORD
-     If a time stamp is preceded by the word `SCHEDULED:', it means you
-     are planning to start working on that task on the given date. So
-     this is not about recording an event, but about planning your
-     work.  The headline will be listed under the given date(2).  In
-     addition, a reminder that the scheduled date has passed will be
-     present in the compilation for _today_, until the entry is marked
-     DONE.  I.e., the task will automatically be forwarded until
-     completed.
-
-          *** TODO Call Trillian for a date on New Years Eve.
-              SCHEDULED: <2004-12-25 Sat>
-
-TIME STAMP WITH DEADLINE KEYWORD
-     If a time stamp is preceded by the word `DEADLINE:', the task
-     (most likely a TODO item) is supposed to be finished on that date,
-     and it will be listed then.  In addition, the compilation for
-     _today_ will carry a warning about the approaching or missed
-     deadline, starting `org-deadline-warning-days' before the due
-     date, and continuing until the entry is marked DONE.  An example:
-
-          *** TODO write article about the Earth for the Guide
-              The editor in charge is [[bbdb:Ford Prefect]]
-              DEADLINE: <2004-02-29 Sun>
+INACTIVE TIME STAMP
+     Just like a plain time stamp, but with square brackets instead of
+     angular ones.  These time stamps are inactive in the sense that
+     they do _not_ trigger an entry to show up in the agenda.
 
-TIME STAMP WITH CLOSED KEYWORD
-     When `org-log-done' is non-nil, Org-mode will automatically insert
-     a special time stamp each time a TODO entry is marked done (*note
-     Progress logging::).  This time stamp is enclosed in square
-     brackets instead of angular brackets.
+          * Gillian comes late for the fifth time [2006-11-01 Wed]
 
-TIME RANGE WITH CLOCK KEYWORD
-     When using the clock to time the work that is being done on
-     specific items, time ranges preceded by the CLOCK keyword are
-     inserted automatically into the file.  The time stamps are
-     enclosed in square brackets instead of angular brackets.  *Note
-     Clocking work time::.
 
    ---------- Footnotes ----------
 
    (1) This is the standard ISO date/time format.  If you cannot get
 used to these, see *Note Custom time format::
 
-   (2) It will still be listed on that date after it has been marked
-DONE.  If you don't like this, set the variable
-`org-agenda-skip-scheduled-if-done'.
-
 
-File: org,  Node: Creating timestamps,  Next: Custom time format,  Prev: Time stamps,  Up: Timestamps
+File: org,  Node: Creating timestamps,  Next: Deadlines and scheduling,  Prev: Time stamps,  Up: Timestamps
 
 6.2 Creating timestamps
 =======================
@@ -2763,22 +2752,6 @@ format.
      Access the agenda for the date given by the time stamp or -range at
      point (*note Weekly/Daily agenda::).  
 
-`C-c C-d'
-     Insert `DEADLINE' keyword along with a stamp.  The insertion will
-     happen in the line directly following the headline.  
-
-`C-c C-w'
-     Create a sparse tree with all deadlines that are either past-due,
-     or which will become due within `org-deadline-warning-days'.  With
-     `C-u' prefix, show all deadlines in the file.  With a numeric
-     prefix, check that many days.  For example, `C-1 C-c C-w' shows
-     all deadlines due tomorrow.  
-
-`C-c C-s'
-     Insert `SCHEDULED' keyword along with a stamp.  The insertion will
-     happen in the line directly following the headline.  Any CLOSED
-     timestamp will be removed.  
-
 `S-<left>'
 `S-<right>'
      Change date at cursor by one day.  These key bindings conflict with
@@ -2800,9 +2773,10 @@ format.
 * Menu:
 
 * The date/time prompt::        How org-mode helps you entering date and time
+* Custom time format::          Making dates look differently
 
 
-File: org,  Node: The date/time prompt,  Prev: Creating timestamps,  Up: Creating timestamps
+File: org,  Node: The date/time prompt,  Next: Custom time format,  Prev: Creating timestamps,  Up: Creating timestamps
 
 6.2.1 The date/time prompt
 --------------------------
@@ -2870,10 +2844,10 @@ the calendar fully from the minibuffer:
 `org-popup-calendar-for-date-prompt'.
 
 
-File: org,  Node: Custom time format,  Next: Repeating items,  Prev: Creating timestamps,  Up: Timestamps
+File: org,  Node: Custom time format,  Prev: The date/time prompt,  Up: Creating timestamps
 
-6.3 Custom time format
-======================
+6.2.2 Custom time format
+------------------------
 
 Org-mode uses the standard ISO notation for dates and times as it is
 defined in ISO 8601.  If you cannot get used to this and require another
@@ -2906,48 +2880,114 @@ consequences:
      the custom format is shorter, things do work as expected.
 
 
-File: org,  Node: Repeating items,  Next: Progress logging,  Prev: Custom time format,  Up: Timestamps
+File: org,  Node: Deadlines and scheduling,  Next: Progress logging,  Prev: Creating timestamps,  Up: Timestamps
 
-6.4 Repeating items
-===================
+6.3 Deadlines and Scheduling
+============================
 
-Org-mode integrates with the Emacs calendar and diary to display cyclic
-appointments, anniversaries and other special entries in the agenda
-(*note Weekly/Daily agenda::).  However, it can be useful to have
-certain deadlines and scheduling items to auto-repeat.  The advantage of
-a deadline or scheduled item is that the they produce warnings ahead of
-time and automatically forward themselves in the agenda until they are
-done.  The abstract difference is therefore between cyclic appointments
-and cyclic action items.  For appointments you should use the diary,
-for actions you can uses an org-mode deadline or scheduling time stamp
-together with a REPEAT cookie.  For example:
+A time stamp may be preceded by special keywords to facilitate planning
+of work:
 
-     * TODO Replace batteries in smoke detector REPEAT(+18m)
-       SCHEDULED: <2007-01-01 Mon>
+DEADLINE
+     The task (most likely a TODO item) is supposed to be finished on
+     that date, and it will be listed then.  In addition, the
+     compilation for _today_ will carry a warning about the approaching
+     or missed deadline, starting `org-deadline-warning-days' before
+     the due date, and continuing until the entry is marked DONE.  An
+     example:
 
-     * TODO Get dentist appointment REPEAT(+6m)
-       SCHEDULED: <2006-12-19 Tue>
+          *** TODO write article about the Earth for the Guide
+              The editor in charge is [[bbdb:Ford Prefect]]
+              DEADLINE: <2004-02-29 Sun>
 
-     * TODO Tax report to IRS REPEAT(+1y)
-       DEADLINE: <2007-04-01 Sun>
+SCHEDULED
+     You are planning to start working on that task on the given date.
+     The headline will be listed under the given date(1).  In addition,
+     a reminder that the scheduled date has passed will be present in
+     the compilation for _today_, until the entry is marked DONE.
+     I.e., the task will automatically be forwarded until completed.
 
-   Each time you try to mark one of these entries DONE using `C-c C-t',
-they will automatically switch back to the state TODO, and the
-deadline/scheduling will be shifted accordingly.  The time units
-recognized by org-mode are year (y), month (m), week (w), and day (d).
-Org-mode will also prompt you for a note and record the fact that you
-have closed this item in a note under the headline.
+          *** TODO Call Trillian for a date on New Years Eve.
+              SCHEDULED: <2004-12-25 Sat>
 
-   One unusual property of these repeating items is that only one
-instance of each exist at any given time.  So if you look back or ahead
-in the agenda, you will not find past and future instances, only the
-current one will show up.  Use a cyclic diary entry if you need all
-past and future instances to be visible in the agenda.
+* Menu:
+
+* Inserting deadline/schedule::
+* Repeated tasks::
+
+   ---------- Footnotes ----------
+
+   (1) It will still be listed on that date after it has been marked
+DONE.  If you don't like this, set the variable
+`org-agenda-skip-scheduled-if-done'.
+
+
+File: org,  Node: Inserting deadline/schedule,  Next: Repeated tasks,  Prev: Deadlines and scheduling,  Up: Deadlines and scheduling
+
+6.3.1 Inserting deadline/schedule
+---------------------------------
+
+The following commands allow to quickly insert a deadline or to schedule
+an item:
+
+`C-c C-d'
+     Insert `DEADLINE' keyword along with a stamp.  The insertion will
+     happen in the line directly following the headline.  
+
+`C-c C-w'
+     Create a sparse tree with all deadlines that are either past-due,
+     or which will become due within `org-deadline-warning-days'.  With
+     `C-u' prefix, show all deadlines in the file.  With a numeric
+     prefix, check that many days.  For example, `C-1 C-c C-w' shows
+     all deadlines due tomorrow.  
+
+`C-c C-s'
+     Insert `SCHEDULED' keyword along with a stamp.  The insertion will
+     happen in the line directly following the headline.  Any CLOSED
+     timestamp will be removed.
 
 
-File: org,  Node: Progress logging,  Prev: Repeating items,  Up: Timestamps
+File: org,  Node: Repeated tasks,  Prev: Inserting deadline/schedule,  Up: Deadlines and scheduling
 
-6.5 Progress Logging
+6.3.2 Repeated Tasks
+--------------------
+
+Some tasks need to be repeated again and again, and Org-mode therefore
+allows to use a repeater in a DEADLINE or SCHEDULED time stamp, for
+example:
+     ** TODO Pay the rent
+        DEADLINE: <2005-10-01 Sat +1m>
+
+   Deadlines and scheduled items produce entries in the agenda when they
+are over-due, so it is important to be able to mark such an entry as
+completed once you have done so.  When you mark a DEADLINE or a SCHEDULE
+with the todo keyword DONE, it will no longer produce entries in the
+agenda. The problem with this is, however, that then also the _next_
+instance of the repeated entry will not be active.  Org-mode deals with
+this in the following way: When you try to mark such an entry DONE
+(using `C-c C-t'), it will shift the base date of the repeating time
+stamp by the repeater interval, and immediately set the entry state
+back to TODO.  In the example above, setting the state to DONE would
+actually switch the date like this:
+
+     ** TODO Pay the rent
+        DEADLINE: <2005-11-01 Tue +1m>
+
+   You will also be prompted for a note that will be put under the
+DEADLINE line to keep a record that you actually acted on the previous
+instance of this deadline.
+
+   As a consequence of shifting the base date, this entry will no
+longer be visible in the agenda when checking past dates, but all
+future instances will be visible.
+
+   You may have both scheduling and deadline information for a specific
+task - just make sure that the repeater intervals on both are the same.
+
+
+File: org,  Node: Progress logging,  Prev: Deadlines and scheduling,  Up: Timestamps
+
+6.4 Progress Logging
 ====================
 
 Org-mode can automatically record a time stamp when you mark a TODO item
@@ -2965,7 +3005,7 @@ on an aspect of a project.
 
 File: org,  Node: Closing items,  Next: Tracking TODO state changes,  Prev: Progress logging,  Up: Progress logging
 
-6.5.1 Closing items
+6.4.1 Closing items
 -------------------
 
 If you want to keep track of _when_ a certain TODO item was finished,
@@ -2994,7 +3034,7 @@ the timestamp, use(2)
 
 File: org,  Node: Tracking TODO state changes,  Next: Clocking work time,  Prev: Closing items,  Up: Progress logging
 
-6.5.2 Tracking TODO state changes
+6.4.2 Tracking TODO state changes
 ---------------------------------
 
 When TODO keywords are used as workflow states (*note Workflow
@@ -3016,7 +3056,7 @@ these into a separate file that starts with:
 
 File: org,  Node: Clocking work time,  Prev: Tracking TODO state changes,  Up: Progress logging
 
-6.5.3 Clocking work time
+6.4.3 Clocking work time
 ------------------------
 
 Org-mode allows you to clock the time you spent on specific tasks in a
@@ -3533,6 +3573,22 @@ date works in the agenda buffer, as well as the commands `S', `M', and
 to other calendars, respectively.  `c' can be used to switch back and
 forth between calendar and agenda.
 
+   If you are using the diary only for sexp entries and holidays, it is
+faster to not use the above setting, but instead to copy or even move
+the entries into an Org-mode file. Org-mode evaluates diary-style sexp
+entries, and does it faster because there is no overhead for first
+creating the diary display.  Note that the sexp entries must start at
+the left margin, no white space is allowed before them.  For example,
+the following segment of an Org-mode file will be processed and entries
+will be made in the agenda:
+
+     * Birthdays and similar stuff
+     #+CATEGORY: Holiday
+     %%(org-calendar-holiday)   ; special function for holiday names
+     #+CATEGORY: Ann
+     %%(diary-anniversary 14  5 1956) Artur Dent %d is years old
+     %%(diary-anniversary  2 10 1869) Mahatma Gandhi would be %d years old
+
 
 File: org,  Node: Global TODO list,  Next: Matching headline tags,  Prev: Weekly/Daily agenda,  Up: Built-in agenda views
 
@@ -4681,13 +4737,25 @@ File: org,  Node: Export commands,  Next: Quoting HTML tags,  Prev: HTML export,
 `C-c C-e H'
      Export to a temporary buffer, do not create a file.  
 
+`C-c C-e H'
+     Export the active region to a temporary buffer.  With prefix arg,
+     do not produce file header and foot, but just the plain HTML
+     section for the region.  This is good for cut-and-paste operations.  
+
 `C-c C-e v h'
 
 `C-c C-e v b'
 
 `C-c C-e v H'
+
+`C-c C-e v R'
      Export only the visible part of the document.
 
+`M-x org-export-region-as-html'
+     Convert the region to HTML under the assumption that it was
+     org-mode syntax before.  This is a global command that can be
+     invoked in any buffer.
+
    In the exported version, the first 3 outline levels will become
 headlines, defining a general document structure.  Additional levels
 will be exported as itemized lists.  If you want that transition to
@@ -5491,6 +5559,11 @@ file is visited again in a new Emacs session.
      entries before it.  The corresponding variable is
      `org-archive-location'.
 
+`#+PRIORITIES: highest lowest default'
+     This line sets the limits and the default for the priorities.  All
+     three must be either letters A-Z or numbers 0-9.  The highest
+     priority must have a lower ASCII number that the lowest priority.
+
 `#+TBLFM:'
      This line contains the formulas for the table directly above the
      line.
@@ -6284,6 +6357,9 @@ if I have forgotten someone, please accept my apologies and let me know.
      patched CSS formatting into the HTML exporter, and inspired the
      agenda.
 
+   * David Emery provided a patch for custom CSS support in exported
+     HTML agendas.
+
    * Nic Ferrier contributed mailcap and XOXO support.
 
    * John Foerch figured out how to make incremental search show context
@@ -6300,6 +6376,11 @@ if I have forgotten someone, please accept my apologies and let me know.
    * Shidai Liu ("Leo") asked for embedded LaTeX and tested it.  He also
      provided frequent feedback and some patches.
 
+   * Jason F. McBrayer suggested agenda export to CSV format.
+
+   * Dmitri Minaev sent a patch to set priority limits on a per-file
+     basis.
+
    * Stefan Monnier provided a patch to keep the Emacs-Lisp compiler
      happy.
 
@@ -6442,13 +6523,11 @@ Index
 * checkboxes:                            Checkboxes.          (line   6)
 * children, subtree visibility state:    Visibility cycling.  (line  10)
 * clean outline view:                    Clean view.          (line   6)
-* CLOCK keyword:                         Time stamps.         (line  71)
-* CLOSED keyword:                        Time stamps.         (line  65)
 * column formula:                        Column formulas.     (line   6)
 * commands, in agenda buffer:            Agenda commands.     (line   6)
 * comment lines:                         Comment lines.       (line   6)
 * completion, of dictionary words:       Completion.          (line   6)
-* completion, of file names:             Handling links.      (line  41)
+* completion, of file names:             Handling links.      (line  43)
 * completion, of link abbreviations:     Completion.          (line   6)
 * completion, of links:                  Handling links.      (line  25)
 * completion, of option keywords <1>:    Completion.          (line   6)
@@ -6478,13 +6557,14 @@ Index
 * cycling, visibility:                   Visibility cycling.  (line   6)
 * daily agenda:                          Weekly/Daily agenda. (line   6)
 * date format, custom:                   Custom time format.  (line   6)
+* date range:                            Time stamps.         (line  40)
 * date stamps <1>:                       Time stamps.         (line   6)
 * date stamps:                           Timestamps.          (line   6)
 * date, reading in minibuffer:           The date/time prompt.
                                                               (line   6)
-* DEADLINE keyword:                      Time stamps.         (line  53)
+* DEADLINE keyword:                      Deadlines and scheduling.
+                                                              (line  10)
 * deadlines:                             Time stamps.         (line   6)
-* deadlines, repeating:                  Repeating items.     (line   6)
 * debugging, of table formulas:          Editing and debugging formulas.
                                                               (line  97)
 * demotion, of subtrees:                 Structure editing.   (line   6)
@@ -6504,7 +6584,7 @@ Index
 * elisp links:                           External links.      (line   6)
 * emphasized text:                       Export options.      (line  25)
 * enhancing text:                        Enhancing text.      (line   6)
-* evaluate time range:                   Creating timestamps. (line  64)
+* evaluate time range:                   Creating timestamps. (line  48)
 * even, STARTUP keyword:                 In-buffer settings.  (line  44)
 * exporting:                             Exporting.           (line   6)
 * exporting agenda views <1>:            Exporting Agenda Views.
@@ -6522,7 +6602,7 @@ Index
 * field references:                      References.          (line  15)
 * file links:                            External links.      (line   6)
 * file links, searching:                 Search options.      (line   6)
-* file name completion:                  Handling links.      (line  41)
+* file name completion:                  Handling links.      (line  43)
 * files for agenda:                      Agenda files.        (line   6)
 * files, adding to agenda list:          Agenda files.        (line  12)
 * files, selecting for publishing:       Selecting files.     (line   6)
@@ -6530,7 +6610,7 @@ Index
 * fixed-width sections:                  Export options.      (line  25)
 * folded, subtree visibility state:      Visibility cycling.  (line  10)
 * folding, sparse trees:                 Sparse trees.        (line   6)
-* following links:                       Handling links.      (line  56)
+* following links:                       Handling links.      (line  58)
 * format specifier:                      Formula syntax for Calc.
                                                               (line  14)
 * format, of links:                      Link format.         (line   6)
@@ -6551,7 +6631,7 @@ Index
 * GNUS links:                            External links.      (line   6)
 * hand-formatted lists:                  Enhancing text.      (line  11)
 * headline levels:                       Export options.      (line  25)
-* headline levels, for exporting <1>:    Export commands.     (line  22)
+* headline levels, for exporting <1>:    Export commands.     (line  34)
 * headline levels, for exporting:        ASCII export.        (line  18)
 * headline navigation:                   Motion.              (line   6)
 * headline tagging:                      Tags.                (line   6)
@@ -6570,7 +6650,7 @@ Index
 * iCalendar export:                      iCalendar export.    (line   6)
 * images, inline in HTML:                Images.              (line   6)
 * in-buffer settings:                    In-buffer settings.  (line   6)
-* inactive timestamp:                    Time stamps.         (line  24)
+* inactive timestamp:                    Time stamps.         (line  49)
 * index, of published pages:             Project page index.  (line   6)
 * Info links:                            External links.      (line   6)
 * inheritance, of tags:                  Tag inheritance.     (line   6)
@@ -6600,13 +6680,13 @@ Index
 * link completion:                       Handling links.      (line  25)
 * link format:                           Link format.         (line   6)
 * links, external:                       External links.      (line   6)
-* links, finding next/previous:          Handling links.      (line  89)
+* links, finding next/previous:          Handling links.      (line  91)
 * links, handling:                       Handling links.      (line   6)
 * links, in HTML export:                 Links.               (line   6)
 * links, internal:                       Internal links.      (line   6)
 * links, publishing:                     Publishing links.    (line   6)
 * links, radio targets:                  Radio targets.       (line   6)
-* links, returning to:                   Handling links.      (line  83)
+* links, returning to:                   Handling links.      (line  85)
 * Lisp forms, as table formulas:         Formula syntax for Lisp.
                                                               (line   6)
 * lists, hand-formatted:                 Enhancing text.      (line  11)
@@ -6619,7 +6699,7 @@ Index
 * lognotestate, STARTUP keyword:         In-buffer settings.  (line  33)
 * logrepeat, STARTUP keyword:            In-buffer settings.  (line  33)
 * maintainer:                            Feedback.            (line   6)
-* mark ring:                             Handling links.      (line  79)
+* mark ring:                             Handling links.      (line  81)
 * marking characters, tables:            Advanced features.   (line  40)
 * matching, of tags:                     Matching headline tags.
                                                               (line   6)
@@ -6698,9 +6778,9 @@ Index
 * remote editing, undo:                  Agenda commands.     (line 107)
 * richer text:                           Enhancing text.      (line   6)
 * RMAIL links:                           External links.      (line   6)
-* SCHEDULED keyword:                     Time stamps.         (line  40)
+* SCHEDULED keyword:                     Deadlines and scheduling.
+                                                              (line  22)
 * scheduling:                            Time stamps.         (line   6)
-* scheduling, repeating:                 Repeating items.     (line   6)
 * Scripts, for agenda processing:        Extracting Agenda Information for other programs.
                                                               (line   6)
 * search option in file links:           Search options.      (line   6)
@@ -6716,7 +6796,8 @@ Index
 * showstars, STARTUP keyword:            In-buffer settings.  (line  44)
 * sorting, of agenda items:              Sorting of agenda items.
                                                               (line   6)
-* sparse tree, for deadlines:            Creating timestamps. (line  39)
+* sparse tree, for deadlines:            Inserting deadline/schedule.
+                                                              (line  11)
 * sparse tree, for TODO:                 TODO basics.         (line  26)
 * sparse tree, tag based:                Tags.                (line   6)
 * sparse trees:                          Sparse trees.        (line   6)
@@ -6779,12 +6860,12 @@ Index
                                                               (line   6)
 * time-sorted view:                      Timeline.            (line   6)
 * timeline, single file:                 Timeline.            (line   6)
-* timerange:                             Time stamps.         (line  31)
+* timerange:                             Time stamps.         (line  40)
 * timestamp:                             Time stamps.         (line  14)
-* timestamp, inactive:                   Time stamps.         (line  24)
+* timestamp, inactive:                   Time stamps.         (line  49)
+* timestamp, with repeater interval:     Time stamps.         (line  24)
 * timestamps, creating:                  Creating timestamps. (line   6)
 * TODO items:                            TODO items.          (line   6)
-* TODO items, repeating:                 Repeating items.     (line   6)
 * TODO keyword matching:                 Global TODO list.    (line  17)
 * TODO keyword matching, with tags search: Tag searches.      (line  40)
 * todo keyword sets:                     Multiple sets in one file.
@@ -6876,8 +6957,8 @@ Key Index
 * C-a a L:                               Timeline.            (line  10)
 * C-c !:                                 Creating timestamps. (line  19)
 * C-c #:                                 Checkboxes.          (line  56)
-* C-c %:                                 Handling links.      (line  79)
-* C-c &:                                 Handling links.      (line  83)
+* C-c %:                                 Handling links.      (line  81)
+* C-c &:                                 Handling links.      (line  85)
 * C-c ':                                 Editing and debugging formulas.
                                                               (line  36)
 * C-c *:                                 Updating the table.  (line  13)
@@ -6937,7 +7018,8 @@ Key Index
                                                               (line  54)
 * C-c C-c:                               Plain lists.         (line  78)
 * C-c C-d <1>:                           Agenda commands.     (line 156)
-* C-c C-d:                               Creating timestamps. (line  35)
+* C-c C-d:                               Inserting deadline/schedule.
+                                                              (line   9)
 * C-c C-e:                               Exporting.           (line  19)
 * C-c C-e a:                             ASCII export.        (line   9)
 * C-c C-e b:                             Export commands.     (line   7)
@@ -6946,20 +7028,22 @@ Key Index
 * C-c C-e h:                             Export commands.     (line   6)
 * C-c C-e I:                             iCalendar export.    (line  16)
 * C-c C-e i:                             iCalendar export.    (line  14)
+* C-c C-e R:                             Export commands.     (line  13)
 * C-c C-e t:                             Export options.      (line  13)
 * C-c C-e v <1>:                         XOXO export.         (line  11)
 * C-c C-e v:                             Sparse trees.        (line  41)
 * C-c C-e v a:                           ASCII export.        (line  13)
-* C-c C-e v b:                           Export commands.     (line  13)
-* C-c C-e v H:                           Export commands.     (line  13)
-* C-c C-e v h:                           Export commands.     (line  13)
+* C-c C-e v b:                           Export commands.     (line  18)
+* C-c C-e v H:                           Export commands.     (line  18)
+* C-c C-e v h:                           Export commands.     (line  18)
+* C-c C-e v R:                           Export commands.     (line  18)
 * C-c C-e x:                             XOXO export.         (line  10)
 * C-c C-f:                               Motion.              (line  12)
 * C-c C-j:                               Motion.              (line  21)
 * C-c C-l:                               Handling links.      (line  25)
 * C-c C-n:                               Motion.              (line   8)
 * C-c C-o <1>:                           Creating timestamps. (line  31)
-* C-c C-o:                               Handling links.      (line  56)
+* C-c C-o:                               Handling links.      (line  58)
 * C-c C-p:                               Motion.              (line   9)
 * C-c C-q <1>:                           Editing and debugging formulas.
                                                               (line  50)
@@ -6969,12 +7053,14 @@ Key Index
                                                               (line  53)
 * C-c C-r:                               Visibility cycling.  (line  34)
 * C-c C-s <1>:                           Agenda commands.     (line 153)
-* C-c C-s:                               Creating timestamps. (line  46)
+* C-c C-s:                               Inserting deadline/schedule.
+                                                              (line  18)
 * C-c C-t <1>:                           Clocking work time.  (line  27)
 * C-c C-t:                               TODO basics.         (line  13)
 * C-c C-u:                               Motion.              (line  18)
 * C-c C-v:                               TODO basics.         (line  26)
-* C-c C-w:                               Creating timestamps. (line  39)
+* C-c C-w:                               Inserting deadline/schedule.
+                                                              (line  11)
 * 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)
@@ -6984,9 +7070,9 @@ Key Index
 * C-c C-x C-k:                           Structure editing.   (line  39)
 * C-c C-x C-l:                           Processing LaTeX fragments.
                                                               (line   9)
-* C-c C-x C-n:                           Handling links.      (line  89)
+* C-c C-x C-n:                           Handling links.      (line  91)
 * C-c C-x C-o:                           Clocking work time.  (line  14)
-* C-c C-x C-p:                           Handling links.      (line  89)
+* C-c C-x C-p:                           Handling links.      (line  91)
 * C-c C-x C-r:                           Clocking work time.  (line  43)
 * C-c C-x C-s:                           Moving subtrees.     (line  10)
 * C-c C-x C-t:                           Custom time format.  (line  12)
@@ -7002,7 +7088,7 @@ Key Index
                                                               (line 111)
 * C-c C-x M-w:                           Structure editing.   (line  43)
 * C-c C-y <1>:                           Clocking work time.  (line  22)
-* C-c C-y:                               Creating timestamps. (line  64)
+* C-c C-y:                               Creating timestamps. (line  48)
 * C-c l:                                 Handling links.      (line   9)
 * C-c { <1>:                             CDLaTeX mode.        (line  21)
 * C-c {:                                 Editing and debugging formulas.
@@ -7024,7 +7110,7 @@ Key Index
                                                               (line  14)
 * C-u C-c =:                             Field formulas.      (line  24)
 * C-u C-c C-c:                           Updating the table.  (line  19)
-* C-u C-c C-l:                           Handling links.      (line  41)
+* C-u C-c C-l:                           Handling links.      (line  43)
 * C-u C-c C-x C-a:                       ARCHIVE tag.         (line  31)
 * C-u C-c C-x C-s:                       Moving subtrees.     (line  12)
 * C-u C-c C-x C-u <1>:                   Dynamic blocks.      (line  22)
@@ -7098,11 +7184,11 @@ Key Index
 * mouse-1 <1>:                           Agenda commands.     (line  33)
 * mouse-1 <2>:                           The date/time prompt.
                                                               (line  36)
-* mouse-1:                               Handling links.      (line  70)
+* mouse-1:                               Handling links.      (line  72)
 * mouse-2 <1>:                           Agenda commands.     (line  33)
-* mouse-2:                               Handling links.      (line  70)
+* mouse-2:                               Handling links.      (line  72)
 * mouse-3 <1>:                           Agenda commands.     (line  28)
-* mouse-3:                               Handling links.      (line  75)
+* mouse-3:                               Handling links.      (line  77)
 * n:                                     Agenda commands.     (line  19)
 * O:                                     Agenda commands.     (line 180)
 * o:                                     Agenda commands.     (line  65)
@@ -7116,7 +7202,7 @@ Key Index
 * S-<down> <1>:                          Agenda commands.     (line 149)
 * S-<down> <2>:                          The date/time prompt.
                                                               (line  45)
-* S-<down> <3>:                          Creating timestamps. (line  56)
+* S-<down> <3>:                          Creating timestamps. (line  40)
 * S-<down> <4>:                          Priorities.          (line  23)
 * S-<down> <5>:                          Editing and debugging formulas.
                                                               (line  67)
@@ -7124,7 +7210,7 @@ Key Index
 * S-<left> <1>:                          Agenda commands.     (line 167)
 * S-<left> <2>:                          The date/time prompt.
                                                               (line  42)
-* S-<left> <3>:                          Creating timestamps. (line  51)
+* S-<left> <3>:                          Creating timestamps. (line  35)
 * S-<left> <4>:                          Multiple sets in one file.
                                                               (line  29)
 * S-<left> <5>:                          TODO basics.         (line  20)
@@ -7135,7 +7221,7 @@ Key Index
 * S-<right> <1>:                         Agenda commands.     (line 159)
 * S-<right> <2>:                         The date/time prompt.
                                                               (line  39)
-* S-<right> <3>:                         Creating timestamps. (line  51)
+* S-<right> <3>:                         Creating timestamps. (line  35)
 * S-<right> <4>:                         Multiple sets in one file.
                                                               (line  29)
 * S-<right> <5>:                         TODO basics.         (line  20)
@@ -7147,7 +7233,7 @@ Key Index
 * S-<up> <1>:                            Agenda commands.     (line 143)
 * S-<up> <2>:                            The date/time prompt.
                                                               (line  48)
-* S-<up> <3>:                            Creating timestamps. (line  56)
+* S-<up> <3>:                            Creating timestamps. (line  40)
 * S-<up> <4>:                            Priorities.          (line  23)
 * S-<up> <5>:                            Editing and debugging formulas.
                                                               (line  67)
@@ -7162,190 +7248,192 @@ Key Index
 
 Tag Table:
 Node: Top970
-Node: Introduction11580
-Node: Summary11995
-Node: Installation15004
-Node: Activation16382
-Node: Feedback17631
-Node: Document structure19707
-Node: Outlines20481
-Node: Headlines21141
-Ref: Headlines-Footnote-122149
-Node: Visibility cycling22248
-Ref: Visibility cycling-Footnote-124458
-Ref: Visibility cycling-Footnote-224516
-Ref: Visibility cycling-Footnote-324566
-Node: Motion24836
-Node: Structure editing25790
-Node: Archiving28616
-Node: ARCHIVE tag29174
-Node: Moving subtrees30967
-Node: Sparse trees32278
-Ref: Sparse trees-Footnote-134410
-Ref: Sparse trees-Footnote-234592
-Node: Plain lists34707
-Ref: Plain lists-Footnote-138476
-Ref: Plain lists-Footnote-238834
-Node: Tables39018
-Node: Built-in table editor39532
-Node: Narrow columns46771
-Ref: Narrow columns-Footnote-148704
-Node: orgtbl-mode48750
-Node: The spreadsheet49554
-Node: References50641
-Ref: References-Footnote-154770
-Node: Formula syntax for Calc55059
-Node: Formula syntax for Lisp57516
-Node: Field formulas58785
-Node: Column formulas60093
-Node: Editing and debugging formulas61692
-Node: Updating the table65845
-Node: Advanced features66880
-Node: Hyperlinks71405
-Node: Link format72178
-Node: Internal links73471
-Ref: Internal links-Footnote-175396
-Node: Radio targets75528
-Node: External links76219
-Node: Handling links78623
-Ref: Handling links-Footnote-183733
-Ref: Handling links-Footnote-283970
-Node: Link abbreviations84044
-Node: Search options85723
-Ref: Search options-Footnote-187503
-Node: Custom searches87584
-Node: Remember88632
-Node: Setting up remember89619
-Node: Remember templates90201
-Ref: Remember templates-Footnote-193493
-Node: Storing notes93591
-Node: TODO items95478
-Node: TODO basics96461
-Node: TODO extensions98158
-Node: Workflow states98977
-Ref: Workflow states-Footnote-1100152
-Node: TODO types100245
-Ref: TODO types-Footnote-1101828
-Node: Multiple sets in one file101910
-Node: Per file keywords103521
-Ref: Per file keywords-Footnote-1104810
-Node: Priorities105011
-Node: Breaking down tasks106257
-Ref: Breaking down tasks-Footnote-1106777
-Node: Checkboxes106873
-Node: Timestamps109628
-Node: Time stamps110162
-Ref: Time stamps-Footnote-1113656
-Ref: Time stamps-Footnote-2113772
-Node: Creating timestamps113927
-Node: The date/time prompt116585
-Ref: The date/time prompt-Footnote-1118546
-Node: Custom time format118652
-Node: Repeating items120210
-Node: Progress logging122020
-Node: Closing items122666
-Ref: Closing items-Footnote-1123600
-Ref: Closing items-Footnote-2123669
-Node: Tracking TODO state changes123742
-Node: Clocking work time124598
-Ref: Clocking work time-Footnote-1128244
-Ref: Clocking work time-Footnote-2128322
-Node: Tags128448
-Node: Tag inheritance129210
-Node: Setting tags130147
-Ref: Setting tags-Footnote-1134670
-Ref: Setting tags-Footnote-2134782
-Node: Tag searches134865
-Node: Agenda views137576
-Node: Agenda files139521
-Ref: Agenda files-Footnote-1140487
-Ref: Agenda files-Footnote-2140636
-Node: Agenda dispatcher140829
-Node: Built-in agenda views142520
-Node: Weekly/Daily agenda143098
-Node: Global TODO list145227
-Node: Matching headline tags147499
-Node: Timeline148570
-Node: Stuck projects149236
-Node: Presentation and sorting151087
-Node: Categories151878
-Node: Time-of-day specifications152542
-Node: Sorting of agenda items154513
-Node: Agenda commands155795
-Node: Custom agenda views162949
-Node: Storing searches163668
-Node: Block agenda165580
-Node: Setting Options166810
-Node: Exporting Agenda Views169549
-Ref: Exporting Agenda Views-Footnote-1173840
-Ref: Exporting Agenda Views-Footnote-2173897
-Node: Extracting Agenda Information for other programs174083
-Node: Embedded LaTeX178209
-Ref: Embedded LaTeX-Footnote-1179301
-Node: Math symbols179491
-Node: Subscripts and Superscripts180256
-Node: LaTeX fragments181100
-Ref: LaTeX fragments-Footnote-1183334
-Node: Processing LaTeX fragments183596
-Node: CDLaTeX mode184542
-Ref: CDLaTeX mode-Footnote-1187026
-Node: Exporting187174
-Node: ASCII export188488
-Node: HTML export189778
-Node: Export commands190397
-Node: Quoting HTML tags191208
-Node: Links191838
-Node: Images192535
-Ref: Images-Footnote-1193406
-Node: CSS support193467
-Ref: CSS support-Footnote-1194786
-Node: XOXO export194899
-Node: iCalendar export195338
-Node: Text interpretation196557
-Node: Comment lines197099
-Node: Initial text197494
-Node: Enhancing text199168
-Ref: Enhancing text-Footnote-1201030
-Node: Export options201120
-Node: Publishing203013
-Ref: Publishing-Footnote-1203809
-Node: Configuration204005
-Node: Project alist204723
-Node: Sources and destinations205789
-Node: Selecting files206519
-Node: Publishing action207267
-Node: Publishing options208500
-Node: Publishing links210652
-Node: Project page index212165
-Node: Sample configuration212943
-Node: Simple example213435
-Node: Complex example214108
-Node: Triggering publication216184
-Node: Miscellaneous216869
-Node: Completion217503
-Node: Customization218974
-Node: In-buffer settings219557
-Node: The very busy C-c C-c key224183
-Node: Clean view225827
-Node: TTY keys228404
-Node: Interaction230014
-Node: Cooperation230411
-Node: Conflicts233153
-Node: Bugs234716
-Node: Extensions and Hacking236212
-Node: Extensions236808
-Node: Tables in arbitrary syntax238755
-Node: Radio tables239832
-Node: A LaTeX example242335
-Ref: A LaTeX example-Footnote-1245981
-Ref: A LaTeX example-Footnote-2246129
-Node: Translator functions246564
-Ref: Translator functions-Footnote-1249673
-Node: Dynamic blocks249761
-Node: Special agenda views251733
-Ref: Special agenda views-Footnote-1254012
-Node: History and Acknowledgments254272
-Node: Index260132
-Node: Key Index291936
+Node: Introduction11627
+Node: Summary12042
+Node: Installation15051
+Node: Activation16429
+Node: Feedback17678
+Node: Document structure19754
+Node: Outlines20528
+Node: Headlines21188
+Ref: Headlines-Footnote-122196
+Node: Visibility cycling22295
+Ref: Visibility cycling-Footnote-124505
+Ref: Visibility cycling-Footnote-224563
+Ref: Visibility cycling-Footnote-324613
+Node: Motion24883
+Node: Structure editing25837
+Node: Archiving28663
+Node: ARCHIVE tag29221
+Node: Moving subtrees31014
+Node: Sparse trees32325
+Ref: Sparse trees-Footnote-134457
+Ref: Sparse trees-Footnote-234639
+Node: Plain lists34754
+Ref: Plain lists-Footnote-138523
+Ref: Plain lists-Footnote-238881
+Node: Tables39065
+Node: Built-in table editor39579
+Node: Narrow columns46818
+Ref: Narrow columns-Footnote-148751
+Node: orgtbl-mode48797
+Node: The spreadsheet49601
+Node: References50688
+Ref: References-Footnote-154817
+Node: Formula syntax for Calc55106
+Node: Formula syntax for Lisp57563
+Node: Field formulas58832
+Node: Column formulas60140
+Node: Editing and debugging formulas61739
+Node: Updating the table65892
+Node: Advanced features66927
+Node: Hyperlinks71452
+Node: Link format72225
+Node: Internal links73518
+Ref: Internal links-Footnote-175443
+Node: Radio targets75575
+Node: External links76266
+Node: Handling links78670
+Ref: Handling links-Footnote-183957
+Ref: Handling links-Footnote-284194
+Node: Link abbreviations84268
+Node: Search options85947
+Ref: Search options-Footnote-187727
+Node: Custom searches87808
+Node: Remember88856
+Node: Setting up remember89843
+Node: Remember templates90425
+Ref: Remember templates-Footnote-193717
+Node: Storing notes93815
+Node: TODO items95702
+Node: TODO basics96685
+Node: TODO extensions98382
+Node: Workflow states99201
+Ref: Workflow states-Footnote-1100376
+Node: TODO types100469
+Ref: TODO types-Footnote-1102052
+Node: Multiple sets in one file102134
+Node: Per file keywords103745
+Ref: Per file keywords-Footnote-1105034
+Node: Priorities105235
+Node: Breaking down tasks106845
+Ref: Breaking down tasks-Footnote-1107365
+Node: Checkboxes107461
+Node: Timestamps110216
+Node: Time stamps110657
+Ref: Time stamps-Footnote-1112962
+Node: Creating timestamps113078
+Node: The date/time prompt115152
+Ref: The date/time prompt-Footnote-1117140
+Node: Custom time format117246
+Node: Deadlines and scheduling118794
+Ref: Deadlines and scheduling-Footnote-1120144
+Node: Inserting deadline/schedule120299
+Node: Repeated tasks121237
+Node: Progress logging122876
+Node: Closing items123531
+Ref: Closing items-Footnote-1124465
+Ref: Closing items-Footnote-2124534
+Node: Tracking TODO state changes124607
+Node: Clocking work time125463
+Ref: Clocking work time-Footnote-1129109
+Ref: Clocking work time-Footnote-2129187
+Node: Tags129313
+Node: Tag inheritance130075
+Node: Setting tags131012
+Ref: Setting tags-Footnote-1135535
+Ref: Setting tags-Footnote-2135647
+Node: Tag searches135730
+Node: Agenda views138441
+Node: Agenda files140386
+Ref: Agenda files-Footnote-1141352
+Ref: Agenda files-Footnote-2141501
+Node: Agenda dispatcher141694
+Node: Built-in agenda views143385
+Node: Weekly/Daily agenda143963
+Node: Global TODO list146904
+Node: Matching headline tags149176
+Node: Timeline150247
+Node: Stuck projects150913
+Node: Presentation and sorting152764
+Node: Categories153555
+Node: Time-of-day specifications154219
+Node: Sorting of agenda items156190
+Node: Agenda commands157472
+Node: Custom agenda views164626
+Node: Storing searches165345
+Node: Block agenda167257
+Node: Setting Options168487
+Node: Exporting Agenda Views171226
+Ref: Exporting Agenda Views-Footnote-1175517
+Ref: Exporting Agenda Views-Footnote-2175574
+Node: Extracting Agenda Information for other programs175760
+Node: Embedded LaTeX179886
+Ref: Embedded LaTeX-Footnote-1180978
+Node: Math symbols181168
+Node: Subscripts and Superscripts181933
+Node: LaTeX fragments182777
+Ref: LaTeX fragments-Footnote-1185011
+Node: Processing LaTeX fragments185273
+Node: CDLaTeX mode186219
+Ref: CDLaTeX mode-Footnote-1188703
+Node: Exporting188851
+Node: ASCII export190165
+Node: HTML export191455
+Node: Export commands192074
+Node: Quoting HTML tags193318
+Node: Links193948
+Node: Images194645
+Ref: Images-Footnote-1195516
+Node: CSS support195577
+Ref: CSS support-Footnote-1196896
+Node: XOXO export197009
+Node: iCalendar export197448
+Node: Text interpretation198667
+Node: Comment lines199209
+Node: Initial text199604
+Node: Enhancing text201278
+Ref: Enhancing text-Footnote-1203140
+Node: Export options203230
+Node: Publishing205123
+Ref: Publishing-Footnote-1205919
+Node: Configuration206115
+Node: Project alist206833
+Node: Sources and destinations207899
+Node: Selecting files208629
+Node: Publishing action209377
+Node: Publishing options210610
+Node: Publishing links212762
+Node: Project page index214275
+Node: Sample configuration215053
+Node: Simple example215545
+Node: Complex example216218
+Node: Triggering publication218294
+Node: Miscellaneous218979
+Node: Completion219613
+Node: Customization221084
+Node: In-buffer settings221667
+Node: The very busy C-c C-c key226543
+Node: Clean view228187
+Node: TTY keys230764
+Node: Interaction232374
+Node: Cooperation232771
+Node: Conflicts235513
+Node: Bugs237076
+Node: Extensions and Hacking238572
+Node: Extensions239168
+Node: Tables in arbitrary syntax241115
+Node: Radio tables242192
+Node: A LaTeX example244695
+Ref: A LaTeX example-Footnote-1248341
+Ref: A LaTeX example-Footnote-2248489
+Node: Translator functions248924
+Ref: Translator functions-Footnote-1252033
+Node: Dynamic blocks252121
+Node: Special agenda views254093
+Ref: Special agenda views-Footnote-1256372
+Node: History and Acknowledgments256632
+Node: Index262726
+Node: Key Index294515
 
 End Tag Table

+ 1 - 0
org-install.el

@@ -22,6 +22,7 @@
 (autoload 'org-export-icalendar-combine-agenda-files "org"
   "Export all files in `org-agenda-files' to a single combined iCalendar file." t)
 (autoload 'org-batch-agenda "org")
+(autoload 'org-batch-agenda-csv "org")
 (autoload 'org-store-agenda-views "org" "Store agenda views to files" t)
 (autoload 'org-batch-store-agenda-views "org")
 

File diff suppressed because it is too large
+ 415 - 95
org.el


BIN
org.pdf


+ 214 - 130
org.texi

@@ -3,8 +3,8 @@
 @setfilename ../info/org
 @settitle Org Mode Manual
 
-@set VERSION 4.74
-@set DATE April 2007
+@set VERSION 4.75
+@set DATE May 2007
 
 @dircategory Emacs
 @direntry
@@ -176,13 +176,18 @@ Timestamps
 
 * Time stamps::                 Assigning a time to a tree entry
 * Creating timestamps::         Commands which insert timestamps
-* Custom time format::          If you cannot work with the ISO format
-* Repeating items::             Deadlines that come back again and again
+* Deadlines and scheduling::    Planning your work
 * Progress logging::            Documenting when what work was done.
 
 Creating timestamps
 
 * The date/time prompt::        How org-mode helps you entering date and time
+* Custom time format::          Making dates look differently
+
+Deadlines and Scheduling
+
+* Inserting deadline/schedule::  
+* Repeated tasks::              
 
 Progress Logging
 
@@ -2150,18 +2155,20 @@ Insert a link.  This prompts for a link to be inserted into the buffer.
 You can just type a link, using text for an internal link, or one of the
 link type prefixes mentioned in the examples above.  All links stored
 during the current session are part of the history for this prompt, so
-you can access them with @key{up} and @key{down}, or with
-completion@footnote{After insertion of a stored link, the link will be
-removed from the list of stored links.  To keep it in the list later
+you can access them with @key{up} and @key{down}.  Completion, on the
+other hand, will help you to insert valid link prefixes like
+@samp{http:} or @samp{ftp:}, including the prefixes defined through link
+abbreviations (@pxref{Link abbreviations}).  The link will be inserted
+into the buffer@footnote{After insertion of a stored link, the link will
+be removed from the list of stored links.  To keep it in the list later
 use, use a triple @kbd{C-u} prefix to @kbd{C-c C-l}, or configure the
-option @code{org-keep-stored-link-after-insertion}.}.  The link will be
-inserted into the buffer, along with a descriptive text.  If some text
-was selected when this command is called, the selected text becomes the
-default description.@* Note that you don't have to use this command to
-insert a link.  Links in Org-mode are plain text, and you can type or
-paste them straight into the buffer.  By using this command, the links
-are automatically enclosed in double brackets, and you will be asked for
-the optional descriptive text.
+option @code{org-keep-stored-link-after-insertion}.}, along with a
+descriptive text.  If some text was selected when this command is
+called, the selected text becomes the default description.@* Note that
+you don't have to use this command to insert a link.  Links in Org-mode
+are plain text, and you can type or paste them straight into the buffer.
+By using this command, the links are automatically enclosed in double
+brackets, and you will be asked for the optional descriptive text.
 @c
 @c  If the link is a @samp{file:} link and
 @c the linked file is located in the same directory as the current file or
@@ -2818,6 +2825,17 @@ are also used to modify time stamps (@pxref{Creating timestamps}).
 Furthermore, these keys are also used by CUA-mode (@pxref{Conflicts}).
 @end table
 
+You can change the range of allowed priorities by setting the variables
+@code{org-highest-priority}, @code{org-lowest-priority}, and
+@code{org-default-priority}.  For an individual buffer, you may set
+these values (highest, lowest, default) like this (please make sure that
+the highest priority is earlier in the alphabet than the lowest
+priority):
+
+@example
+#+PRIORITIES: A C B
+@end example
+
 @node Breaking down tasks, Checkboxes, Priorities, TODO items
 @section Breaking tasks down into subtasks
 @cindex tasks, breaking down
@@ -2915,8 +2933,7 @@ planning.
 @menu
 * Time stamps::                 Assigning a time to a tree entry
 * Creating timestamps::         Commands which insert timestamps
-* Custom time format::          If you cannot work with the ISO format
-* Repeating items::             Deadlines that come back again and again
+* Deadlines and scheduling::    Planning your work
 * Progress logging::            Documenting when what work was done.
 @end menu
 
@@ -2934,7 +2951,7 @@ special format, either @samp{<2003-09-16 Tue>} or @samp{<2003-09-16 Tue
 09:39>}@footnote{This is the standard ISO date/time format.  If you
 cannot get used to these, see @ref{Custom time format}}.  A time stamp
 can appear anywhere in the headline or body of an org-tree entry.  Its
-presence allows entries to be shown on specific dates in the agenda
+presence causes entries to be shown on specific dates in the agenda
 (@pxref{Weekly/Daily agenda}).  We distinguish:
 
 @table @var
@@ -2950,76 +2967,53 @@ associated with a plain time stamp will be shown exactly on that date.
 * Meet Peter at the movies <2006-11-01 Wed 19:15>
 @end example
 
-@item Inactive time stamp
-@cindex timestamp, inactive
-@cindex inactive timestamp
-Just like a plain time stamp, but with square brackets instead of
-angular ones.  These time stamps are inactive in the sense that they do
-@emph{not} trigger an entry to show up in the agenda.
+@item Time stamp with repeater interval
+@cindex timestamp, with repeater interval
+A time stamp may contain a @emph{repeater interval}, indicating that it
+applies not only on the given date, but again and again after a certain
+interval of N days (d), weeks (w), months(m), or years(y).  The
+following will show up in the agenda every Wednesday:
 
 @example
-* Gillian comes late for the fifth time [2006-11-01 Wed]
+* Pick up Sam at school <2007-05-16 Wed 12:30 +1w>
 @end example
 
-@item Time stamp range
-@cindex timerange
-Two time stamps connected by @samp{--} denote a time range.  The
-headline will be shown on the first and last day of the range, and on
-any dates that are displayed and fall in the range.  Here is an
-example:
+@item Diary-style sexp entries
+For more complex date specifications, Org-mode supports using the
+special sexp diary entries implemented in the Emacs calendar/diary
+package.  For example
 
 @example
-** Meeting in Amsterdam
-   <2004-08-23 Mon>--<2004-08-26 Thu>
+* The nerd meeting on every 2nd Thursday of the month
+  <%%(diary-float t 4 2)>
 @end example
 
-@item Time stamp with SCHEDULED keyword
-@cindex SCHEDULED keyword
-If a time stamp is preceded by the word @samp{SCHEDULED:}, it means you
-are planning to start working on that task on the given date. So this is
-not about recording an event, but about planning your work.  The
-headline will be listed under the given date@footnote{It will still be
-listed on that date after it has been marked DONE.  If you don't like
-this, set the variable @code{org-agenda-skip-scheduled-if-done}.}.  In
-addition, a reminder that the scheduled date has passed will be present
-in the compilation for @emph{today}, until the entry is marked DONE.
-I.e., the task will automatically be forwarded until completed.
+@item Time/Date range
+@cindex timerange
+@cindex date range
+Two time stamps connected by @samp{--} denote a range.  The headline
+will be shown on the first and last day of the range, and on any dates
+that are displayed and fall in the range.  Here is an example:
 
 @example
-*** TODO Call Trillian for a date on New Years Eve.
-    SCHEDULED: <2004-12-25 Sat>
+** Meeting in Amsterdam
+   <2004-08-23 Mon>--<2004-08-26 Thu>
 @end example
 
-@item Time stamp with DEADLINE keyword
-@cindex DEADLINE keyword
-If a time stamp is preceded by the word @samp{DEADLINE:}, the task
-(most likely a TODO item) is supposed to be finished on that date, and
-it will be listed then.  In addition, the compilation for @emph{today}
-will carry a warning about the approaching or missed deadline,
-starting @code{org-deadline-warning-days} before the due date, and
-continuing until the entry is marked DONE.  An example:
+@item Inactive time stamp
+@cindex timestamp, inactive
+@cindex inactive timestamp
+Just like a plain time stamp, but with square brackets instead of
+angular ones.  These time stamps are inactive in the sense that they do
+@emph{not} trigger an entry to show up in the agenda.
 
 @example
-*** TODO write article about the Earth for the Guide
-    The editor in charge is [[bbdb:Ford Prefect]]
-    DEADLINE: <2004-02-29 Sun>
+* Gillian comes late for the fifth time [2006-11-01 Wed]
 @end example
-@item Time stamp with CLOSED keyword
-@cindex CLOSED keyword
-When @code{org-log-done} is non-nil, Org-mode will automatically insert
-a special time stamp each time a TODO entry is marked done
-(@pxref{Progress logging}).  This time stamp is enclosed in square
-brackets instead of angular brackets.
-
-@item Time range with CLOCK keyword
-@cindex CLOCK keyword
-When using the clock to time the work that is being done on specific
-items, time ranges preceded by the CLOCK keyword are inserted
-automatically into the file.  The time stamps are enclosed in square
-brackets instead of angular brackets.  @xref{Clocking work time}.
+
 @end table
 
-@node Creating timestamps, Custom time format, Time stamps, Timestamps
+@node Creating timestamps, Deadlines and scheduling, Time stamps, Timestamps
 @section Creating timestamps
 @cindex creating timestamps
 @cindex timestamps, creating
@@ -3061,27 +3055,6 @@ instead.
 Access the agenda for the date given by the time stamp or -range at
 point (@pxref{Weekly/Daily agenda}).
 @c
-@kindex C-c C-d
-@item C-c C-d
-Insert @samp{DEADLINE} keyword along with a stamp.  The insertion will
-happen in the line directly following the headline.  
-@c FIXME Any CLOSED timestamp will be removed.????????
-@c
-@kindex C-c C-w
-@cindex sparse tree, for deadlines
-@item C-c C-w
-Create a sparse tree with all deadlines that are either past-due, or
-which will become due within @code{org-deadline-warning-days}.
-With @kbd{C-u} prefix, show all deadlines in the file.  With a numeric
-prefix, check that many days.  For example, @kbd{C-1 C-c C-w} shows
-all deadlines due tomorrow.
-@c
-@kindex C-c C-s
-@item C-c C-s
-Insert @samp{SCHEDULED} keyword along with a stamp.  The insertion will
-happen in the line directly following the headline.  Any CLOSED
-timestamp will be removed.
-@c
 @kindex S-@key{left}
 @kindex S-@key{right}
 @item S-@key{left}
@@ -3110,9 +3083,10 @@ into the following column).
 
 @menu
 * The date/time prompt::        How org-mode helps you entering date and time
+* Custom time format::          Making dates look differently
 @end menu
 
-@node The date/time prompt,  , Creating timestamps, Creating timestamps
+@node The date/time prompt, Custom time format, Creating timestamps, Creating timestamps
 @subsection The date/time prompt
 @cindex date, reading in minibuffer
 @cindex time, reading in minibuffer
@@ -3181,8 +3155,8 @@ One month back.
 Choose date in calendar (only if nothing was typed into minibuffer).
 @end table
 
-@node Custom time format, Repeating items, Creating timestamps, Timestamps
-@section Custom time format
+@node Custom time format,  , The date/time prompt, Creating timestamps
+@subsection Custom time format
 @cindex custom date/time format
 @cindex time format, custom
 @cindex date format, custom
@@ -3224,50 +3198,119 @@ using dates in tables, table alignment will be messed up.  If the custom
 format is shorter, things do work as expected.
 @end itemize
 
-@node Repeating items, Progress logging, Custom time format, Timestamps
-@section Repeating items
-@cindex TODO items, repeating
-@cindex deadlines, repeating
-@cindex scheduling, repeating
-
-Org-mode integrates with the Emacs calendar and diary to display cyclic
-appointments, anniversaries and other special entries in the agenda
-(@pxref{Weekly/Daily agenda}).  However, it can be useful to have
-certain deadlines and scheduling items to auto-repeat.  The advantage of
-a deadline or scheduled item is that the they produce warnings ahead of
-time and automatically forward themselves in the agenda until they are
-done.  The abstract difference is therefore between cyclic
-@i{appointments} and cyclic @i{action items}.  For appointments you
-should use the diary, for actions you can uses an org-mode deadline or
-scheduling time stamp together with a REPEAT cookie.  For example:
+
+@node Deadlines and scheduling, Progress logging, Creating timestamps, Timestamps
+@section Deadlines and Scheduling
+
+A time stamp may be preceded by special keywords to facilitate planning
+of work:
+
+@table @var
+@item DEADLINE
+@cindex DEADLINE keyword
+The task (most likely a TODO item) is supposed to be finished on that
+date, and it will be listed then.  In addition, the compilation for
+@emph{today} will carry a warning about the approaching or missed
+deadline, starting @code{org-deadline-warning-days} before the due date,
+and continuing until the entry is marked DONE.  An example:
 
 @example
-* TODO Replace batteries in smoke detector REPEAT(+18m)
-  SCHEDULED: <2007-01-01 Mon>
+*** TODO write article about the Earth for the Guide
+    The editor in charge is [[bbdb:Ford Prefect]]
+    DEADLINE: <2004-02-29 Sun>
+@end example
 
-* TODO Get dentist appointment REPEAT(+6m)
-  SCHEDULED: <2006-12-19 Tue>
+@item SCHEDULED
+@cindex SCHEDULED keyword
+You are planning to start working on that task on the given date. The
+headline will be listed under the given date@footnote{It will still be
+listed on that date after it has been marked DONE.  If you don't like
+this, set the variable @code{org-agenda-skip-scheduled-if-done}.}.  In
+addition, a reminder that the scheduled date has passed will be present
+in the compilation for @emph{today}, until the entry is marked DONE.
+I.e., the task will automatically be forwarded until completed.
 
-* TODO Tax report to IRS REPEAT(+1y)
-  DEADLINE: <2007-04-01 Sun>
+@example
+*** TODO Call Trillian for a date on New Years Eve.
+    SCHEDULED: <2004-12-25 Sat>
 @end example
+@end table
 
-Each time you try to mark one of these entries DONE using @kbd{C-c C-t},
-they will automatically switch back to the state TODO, and the
-deadline/scheduling will be shifted accordingly.  The time units
-recognized by org-mode are year (y), month (m), week (w), and day (d).
-Org-mode will also prompt you for a note and record the fact that you
-have closed this item in a note under the headline.
+@menu
+* Inserting deadline/schedule::  
+* Repeated tasks::              
+@end menu
 
-One unusual property of these repeating items is that only one instance
-of each exist at any given time.  So if you look back or ahead in the
-agenda, you will not find past and future instances, only the current
-one will show up.  Use a cyclic diary entry if you need all past and
-future instances to be visible in the agenda.
+@node Inserting deadline/schedule, Repeated tasks, Deadlines and scheduling, Deadlines and scheduling
+@subsection Inserting deadline/schedule
 
-@c FIXME: Document that a note is always being taken.
+The following commands allow to quickly insert a deadline or to schedule
+an item:
 
-@node Progress logging,  , Repeating items, Timestamps
+@table @kbd
+@c
+@kindex C-c C-d
+@item C-c C-d
+Insert @samp{DEADLINE} keyword along with a stamp.  The insertion will
+happen in the line directly following the headline.
+@c FIXME Any CLOSED timestamp will be removed.????????
+@c
+@kindex C-c C-w
+@cindex sparse tree, for deadlines
+@item C-c C-w
+Create a sparse tree with all deadlines that are either past-due, or
+which will become due within @code{org-deadline-warning-days}.
+With @kbd{C-u} prefix, show all deadlines in the file.  With a numeric
+prefix, check that many days.  For example, @kbd{C-1 C-c C-w} shows
+all deadlines due tomorrow.
+@c
+@kindex C-c C-s
+@item C-c C-s
+Insert @samp{SCHEDULED} keyword along with a stamp.  The insertion will
+happen in the line directly following the headline.  Any CLOSED
+timestamp will be removed.
+@end table
+
+@node Repeated tasks,  , Inserting deadline/schedule, Deadlines and scheduling
+@subsection Repeated Tasks
+
+Some tasks need to be repeated again and again, and Org-mode therefore
+allows to use a repeater in a DEADLINE or SCHEDULED time stamp, for
+example:
+@example
+** TODO Pay the rent
+   DEADLINE: <2005-10-01 Sat +1m>
+@end example
+
+Deadlines and scheduled items produce entries in the agenda when they
+are over-due, so it is important to be able to mark such an entry as
+completed once you have done so.  When you mark a DEADLINE or a SCHEDULE
+with the todo keyword DONE, it will no longer produce entries in the
+agenda. The problem with this is, however, that then also the
+@emph{next} instance of the repeated entry will not be active.  Org-mode
+deals with this in the following way: When you try to mark such an entry
+DONE (using @kbd{C-c C-t}), it will shift the base date of the repeating
+time stamp by the repeater interval, and immediately set the entry state
+back to TODO.  In the example above, setting the state to DONE would
+actually switch the date like this:
+
+@example
+** TODO Pay the rent
+   DEADLINE: <2005-11-01 Tue +1m>
+@end example
+
+You will also be prompted for a note that will be put under the DEADLINE
+line to keep a record that you actually acted on the previous instance
+of this deadline.
+
+As a consequence of shifting the base date, this entry will no longer be
+visible in the agenda when checking past dates, but all future instances
+will be visible.
+
+You may have both scheduling and deadline information for a specific
+task - just make sure that the repeater intervals on both are the same.
+
+@node Progress logging,  , Deadlines and scheduling, Timestamps
 @section Progress Logging
 @cindex progress logging
 @cindex logging, of progress
@@ -3335,6 +3378,7 @@ these into a separate file that starts with:
 #+STARTUP: lognotestate
 @end example
 
+
 @node Clocking work time,  , Tracking TODO state changes, Progress logging
 @subsection Clocking work time
 
@@ -3879,6 +3923,23 @@ Sunrise/Sunset times, show lunar phases and to convert to other
 calendars, respectively.  @kbd{c} can be used to switch back and forth
 between calendar and agenda.
 
+If you are using the diary only for sexp entries and holidays, it is
+faster to not use the above setting, but instead to copy or even move
+the entries into an Org-mode file. Org-mode evaluates diary-style sexp
+entries, and does it faster because there is no overhead for first
+creating the diary display.  Note that the sexp entries must start at
+the left margin, no white space is allowed before them.  For example,
+the following segment of an Org-mode file will be processed and entries
+will be made in the agenda:
+
+@example
+* Birthdays and similar stuff
+#+CATEGORY: Holiday
+%%(org-calendar-holiday)   ; special function for holiday names
+#+CATEGORY: Ann
+%%(diary-anniversary 14  5 1956) Artur Dent %d is years old
+%%(diary-anniversary  2 10 1869) Mahatma Gandhi would be %d years old
+@end example
 
 @node Global TODO list, Matching headline tags, Weekly/Daily agenda, Built-in agenda views
 @subsection The global TODO list
@@ -5151,13 +5212,24 @@ Export as HTML file and open it with a browser.
 @kindex C-c C-e H
 @item C-c C-e H
 Export to a temporary buffer, do not create a file.
+@kindex C-c C-e R
+@item C-c C-e H
+Export the active region to a temporary buffer.  With prefix arg, do not
+produce file header and foot, but just the plain HTML section for the
+region.  This is good for cut-and-paste operations.
 @kindex C-c C-e v h
 @kindex C-c C-e v b
 @kindex C-c C-e v H
+@kindex C-c C-e v R
 @item C-c C-e v h
 @item C-c C-e v b
 @item C-c C-e v H
+@item C-c C-e v R
 Export only the visible part of the document.
+@item M-x org-export-region-as-html
+Convert the region to HTML under the assumption that it was org-mode
+syntax before.  This is a global command that can be invoked in any
+buffer.
 @end table
 
 @cindex headline levels, for exporting
@@ -6048,6 +6120,10 @@ This line sets the archive location for the agenda file.  It applies for
 all subsequent lines until the next @samp{#+CATEGORY} line, or the end
 of the file.  The first such line also applies to any entries before it.
 The corresponding variable is @code{org-archive-location}.
+@item #+PRIORITIES: highest lowest default
+This line sets the limits and the default for the priorities.  All three
+must be either letters A-Z or numbers 0-9.  The highest priority must
+have a lower ASCII number that the lowest priority.
 @item #+TBLFM:
 This line contains the formulas for the table directly above the line.
 @item #+TITLE:, #+AUTHOR:, #+EMAIL:, #+LANGUAGE:, #+TEXT:, #+OPTIONS:
@@ -6893,6 +6969,9 @@ asked for a way to narrow wide table columns.
 @i{Christian Egli} converted the documentation into TeXInfo format,
 patched CSS formatting into the HTML exporter, and inspired the agenda.
 @item
+@i{David Emery} provided a patch for custom CSS support in exported
+HTML agendas.
+@item
 @i{Nic Ferrier} contributed mailcap and XOXO support.
 @item
 @i{John Foerch} figured out how to make incremental search show context
@@ -6908,6 +6987,11 @@ translated David O'Toole's tutorial into French.
 @i{Shidai Liu} ("Leo") asked for embedded LaTeX and tested it.  He also
 provided frequent feedback and some patches.
 @item
+@i{Jason F. McBrayer} suggested agenda export to CSV format.
+@item
+@i{Dmitri Minaev} sent a patch to set priority limits on a per-file
+basis.
+@item
 @i{Stefan Monnier} provided a patch to keep the Emacs-Lisp compiler
 happy.
 @item

BIN
orgcard.pdf


+ 1 - 1
orgcard.tex

@@ -1,5 +1,5 @@
 % Reference Card for Org Mode
-\def\orgversionnumber{4.74}
+\def\orgversionnumber{4.75}
 \def\versionyear{2007}          % latest update
 \def\year{2007}                 % latest copyright year
 %

Some files were not shown because too many files changed in this diff