doc.org 1011 KB

Definitions

This page lists all hooks, commands and options of Org 7.8.11.

Hooks
are options containing functions to be run before or after a
function. For example, =org-mode-hook= can contain a list of functions to be called after org-mode is turned on.
Commands
are interactive functions that the user can run with =M-x
command RET=. Most commands have an associated keybinding, indicated here. Users can bind command to his preferred keybinding.
Options
are variables that the user can set through the customize
interface. Calling =M-x customize-variable RET= then completing over availables options will open the custom interface, which makes it easy to set an option.

These are the main "internals" that the uesr may want to know about, and we list them here for further reference. E.g. You can safely create links to =http://orgmode.org/worg/doc.html#org-agenda= to refer to the documentation of the org-agenda command.

On top of these symbols, there are other non-interactive functions and /variables/. You can get more documentation about them with C-h f org- TAB and C-h v org- TAB respectively.

Hooks

:PROPERTIES: :CUSTOM_ID: hooks :END:

org-after-demote-entry-hook nil

Hook run after an entry has been demoted.

The cursor will be at the beginning of the entry. When a subtree is being demoted, the hook will be called for each node.

org-after-promote-entry-hook nil

Hook run after an entry has been promoted.

The cursor will be at the beginning of the entry. When a subtree is being promoted, the hook will be called for each node.

org-after-refile-insert-hook nil

Hook run after `org-refile' has inserted its stuff at the new location.

Note that this is still *before* the stuff will be removed from the *old* location.

org-after-save-iCalendar-file-hook nil

Hook run after an iCalendar file has been saved.

The iCalendar buffer is still current when this hook is run. A good way to use this is to tell a desktop calendar application to re-read the iCalendar file.

org-after-sorting-entries-or-items-hook nil

Hook that is run after a bunch of entries or items have been sorted.

When children are sorted, the cursor is in the parent line when this hook gets called. When a region or a plain list is sorted, the cursor will be in the first entry of the sorted region/list.

org-after-tags-change-hook nil

Hook that is run after the tags in a line have changed.

org-after-todo-state-change-hook nil

Hook which is run after the state of a TODO item was changed.

The new state (a string with a TODO keyword, or nil) is available in the Lisp variable `org-state'.

org-after-todo-statistics-hook nil

Hook that is called after a TODO statistics cookie has been updated.

org-agenda-after-show-hook nil

Each function is called with two arguments: the number of not-done entries and the number of done entries. For example, the following function, when added to this hook, will switch an entry to DONE when all children are done, and back to TODO when new entries are set to a TODO status. Note that this hook is only called when there is a statistics cookie in the headline! (defun org-summary-todo (n-done n-not-done) "Switch entry to DONE when all subentries are done, to TODO otherwise." (let (org-log-done org-log-states) ; turn off logging (org-todo (if (= n-not-done 0) "DONE" "TODO"))))

Normal hook run after an item has been shown from the agenda.

Point is in the buffer where the item originated.

org-agenda-before-write-hook (quote (org-agenda-add-entry-t...

Hook run in temporary buffer before writing it to an export file.

A useful function is `org-agenda-add-entry-text'.

org-agenda-bulk-custom-functions nil

Alist of characters and custom functions for bulk actions.

For example, this value makes those two functions available: '((?R set-category) (?C bulk-cut)) With selected entries in an agenda buffer, `B R' will call the custom function `set-category' on the selected entries. Note that functions in this alist don't need to be quoted.

org-agenda-cleanup-fancy-diary-hook nil

Hook run when the fancy diary buffer is cleaned up.

org-agenda-entry-text-cleanup-hook nil

Hook that is run after basic cleanup of entry text to be shown in agenda.

This cleanup is done in a temporary buffer, so the function may inspect and change the entire buffer. Some default stuff like drawers and scheduling/deadline dates will already have been removed when this is called, as will any matches for regular expressions listed in `org-agenda-entry-text-exclude-regexps'.

org-agenda-mode-hook nil

Hook for `org-agenda-mode', run after the mode is turned on.

org-babel-after-execute-hook nil

Hook for functions to be called after `org-babel-execute-src-block'

org-babel-post-tangle-hook nil

Hook run in code files tangled by `org-babel-tangle'.

org-babel-pre-tangle-hook (quote (save-buffer))

Hook run at the beginning of `org-babel-tangle'.

org-babel-tangle-body-hook nil

Hook run over the contents of each code block body.

org-before-save-iCalendar-file-hook nil

Hook run before  an iCalendar file has been saved.

This can be used to modify the result of the export.

org-blocker-hook nil

Hook for functions that are allowed to block a state change.

Each function gets as its single argument a property list, see `org-trigger-hook' for more information about this list. If any of the functions in this hook returns nil, the state change is blocked.

org-capture-after-finalize-hook nil

Hook that is run right after a capture process is finalized.

Suitable for window cleanup

org-capture-before-finalize-hook nil

Hook that is run right before a capture process is finalized.

The capture buffer is still current when this hook runs and it is widened to the entire buffer.

org-capture-mode-hook nil

Hook for the minor `org-capture-mode'.

org-capture-prepare-finalize-hook nil

Hook that is run before the finalization starts.

The capture buffer is current and still narrowed.

org-checkbox-statistics-hook nil

Hook that is run whenever Org thinks checkbox statistics should be updated.

This hook runs even if checkbox rule in `org-list-automatic-rules' does not apply, so it can be used to implement alternative ways of collecting statistics information.

org-clock-before-select-task-hook nil

Hook called in task selection just before prompting the user.

org-clock-cancel-hook nil

Hook run when cancelling the current clock.

org-clock-goto-hook nil

Hook run when selecting the currently clocked-in entry.

org-clock-in-hook nil

Hook run when starting the clock.

org-clock-in-prepare-hook nil

Hook run when preparing the clock.

This hook is run before anything happens to the task that you want to clock in. For example, you can use this hook to add an effort property.

org-clock-out-hook nil

Hook run when stopping the current clock.

org-create-file-search-functions nil

List of functions to construct the right search string for a file link.

These functions are called in turn with point at the location to which the link should point. A function in the hook should first test if it would like to handle this file type, for example by checking the `major-mode' or the file extension. If it decides not to handle this file, it should just return nil to give other functions a chance. If it does handle the file, it must return the search string to be used when following the link. The search string will be part of the file link, given after a double colon, and `org-open-at-point' will automatically search for it. If special measures must be taken to make the search successful, another function should be added to the companion hook `org-execute-file-search-functions', which see. A function in this hook may also use `setq' to set the variable `description' to provide a suggestion for the descriptive text to be used for this link when it gets inserted into an Org-mode buffer with \[org-insert-link].

List of functions to be prepended to ORG-OPEN-LINK-FUNCTIONS when ORG-CTAGS is active.

org-ctrl-c-ctrl-c-final-hook nil

Hook for functions attaching themselves to `C-c C-c'.

This can be used to add additional functionality to the C-c C-c key which executes context-dependent commands. This hook is run after any other test, while `org-ctrl-c-ctrl-c-hook' is run before the first test. Each function will be called with no arguments. The function must check if the context is appropriate for it to act. If yes, it should do its thing and then return a non-nil value. If the context is wrong, just do nothing and return nil.

org-ctrl-c-ctrl-c-hook nil

Hook for functions attaching themselves to `C-c C-c'.

This can be used to add additional functionality to the C-c C-c key which executes context-dependent commands. This hook is run before any other test, while `org-ctrl-c-ctrl-c-final-hook' is run after the last test. Each function will be called with no arguments. The function must check if the context is appropriate for it to act. If yes, it should do its thing and then return a non-nil value. If the context is wrong, just do nothing and return nil.

org-cycle-hook (quote (org-cycle-hide-archive...

Hook that is run after `org-cycle' has changed the buffer visibility.

The function(s) in this hook must accept a single argument which indicates the new state that was set by the most recent `org-cycle' command. The argument is a symbol. After a global state change, it can have the values `overview', `content', or `all'. After a local state change, it can have the values `folded', `children', or `subtree'.

org-execute-file-search-functions nil

List of functions to execute a file search triggered by a link.

Functions added to this hook must accept a single argument, the search string that was part of the file link, the part after the double colon. The function must first check if it would like to handle this search, for example by checking the `major-mode' or the file extension. If it decides not to handle this search, it should just return nil to give other functions a chance. If it does handle the search, it must return a non-nil value to keep other functions from trying. Each function can access the current prefix argument through the variable `current-prefix-argument'. Note that a single prefix is used to force opening a link in Emacs, so it may be good to only use a numeric or double prefix to guide the search function. In case this is needed, a function in this hook can also restore the window configuration before `org-open-at-point' was called using: (set-window-configuration org-window-config-before-follow-link)

org-export-ascii-final-hook nil

Hook run at the end of ASCII export, in the new buffer.

org-export-blocks-postblock-hook nil

Run after blocks have been processed with `org-export-blocks-preprocess'.

org-export-define-heading-targets-headline-hook nil

Hook that is run when a headline was matched during target search.

This is part of the preprocessing for export.

org-export-docbook-final-hook nil

Hook run at the end of DocBook export, in the new buffer.

org-export-first-hook nil

Hook called as the first thing in each exporter.

Point will be still in the original buffer. Good for general initialization

org-export-html-after-blockquotes-hook nil

Hook run during HTML export, after blockquote, verse, center are done.

org-export-html-final-hook nil

Hook run at the end of HTML export, in the new buffer.

org-export-latex-after-blockquotes-hook nil

Hook run during LaTeX export, after blockquote, verse, center are done.

org-export-latex-after-initial-vars-hook nil

Hook run before LaTeX export.

The exact moment is after the initial variables like org-export-latex-class have been determined from the environment.

org-export-latex-after-save-hook nil

Hook run in the finalized LaTeX buffer, after it has been saved.

org-export-latex-final-hook nil

Hook run in the finalized LaTeX buffer.

org-export-preprocess-after-blockquote-hook nil

Hook for preprocessing an export buffer.

This is run after blockquote/quote/verse/center have been marked with cookies.

org-export-preprocess-after-headline-targets-hook nil

Hook for preprocessing export buffer.

This is run just after the headline targets have been defined and the target-alist has been set up.

org-export-preprocess-after-include-files-hook nil

Hook for preprocessing an export buffer.

This is run after the contents of included files have been inserted.

org-export-preprocess-after-radio-targets-hook nil

Hook for preprocessing an export buffer.

This is run after radio target processing.

org-export-preprocess-after-tree-selection-hook nil

Hook for preprocessing an export buffer.

This is run after selection of trees to be exported has happened. This selection includes tags-based selection, as well as removal of commented and archived trees.

org-export-preprocess-before-backend-specifics-hook nil

Hook run before backend-specific functions are called during preprocessing.

Hook for preprocessing an export buffer.

This hook is run before links are normalized.

org-export-preprocess-before-selecting-backend-code-hook nil

Hook for preprocessing an export buffer.

This is run just before backend-specific blocks get selected.

org-export-preprocess-final-hook nil

Hook for preprocessing an export buffer.

This is run as the last thing in the preprocessing buffer, just before returning the buffer string to the backend.

org-export-preprocess-hook nil

Hook for preprocessing an export buffer.

Pretty much the first thing when exporting is running this hook. Point will be in a temporary buffer that contains a copy of the original buffer, or of the section that is being exported. All the other hooks in the org-export-preprocess... category also work in that temporary buffer, already modified by various stages of the processing.

org-export-taskjuggler-final-hook nil

Hook run at the end of TaskJuggler export, in the new buffer.

org-export-xoxo-final-hook nil

Hook run after XOXO export, in the new buffer.

org-feed-after-adding-hook nil

Hook that is run after new items have been added to a file.

Depending on `org-feed-save-after-adding', the buffer will already have been saved.

org-feed-before-adding-hook nil

Hook that is run before adding new feed items to a file.

You might want to commit the file in its current state to version control, for example.

org-finalize-agenda-hook nil

Hook run just before displaying an agenda buffer.

Hook that is run after a link has been followed.

org-font-lock-hook nil

Functions to be called for special font lock stuff.

org-font-lock-set-keywords-hook nil

Functions that can manipulate `org-font-lock-extra-keywords'.

This is called after `org-font-lock-extra-keywords' is defined, but before it is installed to be used by font lock. This can be useful if something needs to be inserted at a specific position in the font-lock sequence.

org-insert-heading-hook nil

Hook being run after inserting a new heading.

org-load-hook nil

Hook that is run after org.el has been loaded.

org-log-buffer-setup-hook nil

Hook that is run after an Org log buffer is created.

org-metadown-hook nil

Hook for functions attaching themselves to `M-down'.

See `org-ctrl-c-ctrl-c-hook' for more information.

org-metaleft-hook nil

Hook for functions attaching themselves to `M-left'.

See `org-ctrl-c-ctrl-c-hook' for more information.

org-metareturn-hook nil

Hook for functions attaching themselves to `M-RET'.

See `org-ctrl-c-ctrl-c-hook' for more information.

org-metaright-hook nil

Hook for functions attaching themselves to `M-right'.

See `org-ctrl-c-ctrl-c-hook' for more information.

org-metaup-hook nil

Hook for functions attaching themselves to `M-up'.

See `org-ctrl-c-ctrl-c-hook' for more information.

org-mobile-before-process-capture-hook nil

Hook that is run after content was moved to `org-mobile-inbox-for-pull'.

The inbox file is visited by the current buffer, and the buffer is narrowed to the newly captured data.

org-mobile-post-pull-hook nil

Hook run after running `org-mobile-pull'.

If Emacs does not have direct write access to the WebDAV directory used by the mobile device, this hook should be used to copy the emptied capture file `mobileorg.org' back to the WebDAV directory, for example using `rsync' or `scp'.

org-mobile-post-push-hook nil

Hook run after running `org-mobile-push'.

If Emacs does not have direct write access to the WebDAV directory used by the mobile device, this hook should be used to copy all files from the local staging directory `org-mobile-directory' to the WebDAV directory, for example using `rsync' or `scp'.

org-mobile-pre-pull-hook nil

Hook run before executing `org-mobile-pull'.

If Emacs does not have direct write access to the WebDAV directory used by the mobile device, this hook should be used to copy the capture file `mobileorg.org' from the WebDAV location to the local staging directory `org-mobile-directory'.

org-mobile-pre-push-hook nil

Hook run before running `org-mobile-push'.

This could be used to clean up `org-mobile-directory', for example to remove files that used to be included in the agenda but no longer are. The presence of such files would not really be a problem, but after time they may accumulate.

org-mode-hook nil

Mode hook for Org-mode, run after the mode was turned on.

org-occur-hook (quote (org-first-headline-rec...

Hook that is run after `org-occur' has constructed a sparse tree.

This can be used to recenter the window to show as much of the structure as possible.

org-open-at-point-functions nil

Hook that is run when following a link at point.

Functions in this hook must return t if they identify and follow a link at point. If they don't find anything interesting at point, they must return nil.

Hook for functions finding a plain text link.

These functions must take a single argument, the link content. They will be called for links that look like [[link text][description]] when LINK TEXT does not have a protocol like "http:" and does not look like a filename (e.g. "./blue.png"). These functions will be called *before* Org attempts to resolve the link by doing text searches in the current buffer - so if you want a link "[[target]]" to still find "<>", your function should handle this as a special case. When the function does handle the link, it must return a non-nil value. If it decides that it is not responsible for this link, it must return nil to indicate that that Org-mode can continue with other options like exact and fuzzy text search.

org-pre-cycle-hook nil

Hook that is run before visibility cycling is happening.

The function(s) in this hook must accept a single argument which indicates the new state that will be set right after running this hook. The argument is a symbol. Before a global state change, it can have the values `overview', `content', or `all'. Before a local state change, it can have the values `folded', `children', or `subtree'.

org-property-allowed-value-functions nil

Hook for functions supplying allowed values for a specific property.

The functions must take a single argument, the name of the property, and return a flat list of allowed values. If ":ETC" is one of the values, this means that these values are intended as defaults for completion, but that other values should be allowed too. The functions must return nil if they are not responsible for this property.

org-property-changed-functions nil

Hook called when the value of a property has changed.

Each hook function should accept two arguments, the name of the property and the new value.

org-publish-after-export-hook nil

Hook run after export on the exported buffer.

Any changes made by this hook will be saved.

org-publish-before-export-hook nil

Hook run before export on the Org file.

The hook may modify the file in arbitrary ways before publishing happens. The original version of the buffer will be restored after publishing.

org-read-date-minibuffer-setup-hook nil

Hook to be used to set up keys for the date/time interface.

Add key definitions to `minibuffer-local-map', which will be a temporary copy.

org-remember-before-finalize-hook nil

Hook that is run right before a remember process is finalized.

The remember buffer is still current when this hook runs.

org-remember-mode-hook nil

Hook for the minor `org-remember-mode'.

org-reveal-start-hook nil

Hook run before revealing a location.

org-shiftdown-final-hook nil

Hook for functions attaching themselves to `S-down'.

This one runs after all other options except shift-select have been excluded. See `org-ctrl-c-ctrl-c-hook' for more information.

org-shiftdown-hook nil

Hook for functions attaching themselves to `S-down'.

See `org-ctrl-c-ctrl-c-hook' for more information.

org-shiftleft-final-hook nil

Hook for functions attaching themselves to `S-left'.

This one runs after all other options except shift-select have been excluded. See `org-ctrl-c-ctrl-c-hook' for more information.

org-shiftleft-hook nil

Hook for functions attaching themselves to `S-left'.

See `org-ctrl-c-ctrl-c-hook' for more information.

org-shiftmetadown-hook nil

Hook for functions attaching themselves to `M-S-down'.

See `org-ctrl-c-ctrl-c-hook' for more information.

org-shiftmetaleft-hook nil

Hook for functions attaching themselves to `M-S-left'.

See `org-ctrl-c-ctrl-c-hook' for more information.

org-shiftmetaright-hook nil

Hook for functions attaching themselves to `M-S-right'.

See `org-ctrl-c-ctrl-c-hook' for more information.

org-shiftmetaup-hook nil

Hook for functions attaching themselves to `M-S-up'.

See `org-ctrl-c-ctrl-c-hook' for more information.

org-shiftright-final-hook nil

Hook for functions attaching themselves to `S-right'.

This one runs after all other options except shift-select have been excluded. See `org-ctrl-c-ctrl-c-hook' for more information.

org-shiftright-hook nil

Hook for functions attaching themselves to `S-right'.

See `org-ctrl-c-ctrl-c-hook' for more information.

org-shiftup-final-hook nil

Hook for functions attaching themselves to `S-up'.

This one runs after all other options except shift-select have been excluded. See `org-ctrl-c-ctrl-c-hook' for more information.

org-shiftup-hook nil

Hook for functions attaching themselves to `S-up'.

See `org-ctrl-c-ctrl-c-hook' for more information.

org-speed-command-hook (quote (org-speed-command-defa...

Hook for activating speed commands at strategic locations.

Hook functions are called in sequence until a valid handler is found. Each hook takes a single argument, a user-pressed command key which is also a `self-insert-command' from the global map. Within the hook, examine the cursor position and the command key and return nil or a valid handler as appropriate. Handler could be one of an interactive command, a function, or a form. Set `org-use-speed-commands' to non-nil value to enable this hook. The default setting is `org-speed-command-default-hook'.

org-src-mode-hook nil

Hook  run after Org switched a source code snippet to its Emacs mode.

This hook will run - when editing a source code snippet with "C-c '". - When formatting a source code snippet for export with htmlize. You may want to use this hook for example to turn off `outline-minor-mode' or similar things which you want to have when editing a source code file, but which mess up the display of a snippet in Org exported files.

List of functions that are called to create and store a link.

Each function will be called in turn until one returns a non-nil value. Each function should check if it is responsible for creating this link (for example by looking at the major mode). If not, it must exit and return nil. If yes, it should return a non-nil value after a calling `org-store-link-props' with a list of properties and values. Special properties are: :type The link prefix, like "http". This must be given. :link The link, like "http://www.astro.uva.nl/~dominik". This is obligatory as well. :description Optional default description for the second pair of brackets in an Org-mode link. The user can still change this when inserting this link into an Org-mode buffer. In addition to these, any additional properties can be specified and then used in remember templates.

org-tab-after-check-for-cycling-hook nil

Hook for functions to attach themselves to TAB.

See `org-ctrl-c-ctrl-c-hook' for more information. This hook runs after it has been established that not table field motion and not visibility should be done because of current context. This is probably the place where a package like yasnippets can hook in.

org-tab-after-check-for-table-hook nil

Hook for functions to attach themselves to TAB.

See `org-ctrl-c-ctrl-c-hook' for more information. This hook runs after it has been established that the cursor is not in a table, but before checking if the cursor is in a headline or if global cycling should be done. If any function in this hook returns t, not other actions like visibility cycling will be done.

org-tab-before-tab-emulation-hook nil

Hook for functions to attach themselves to TAB.

See `org-ctrl-c-ctrl-c-hook' for more information. This hook runs after every other options for TAB have been exhausted, but before indentation and insertion takes place.

org-tab-first-hook nil

Hook for functions to attach themselves to TAB.

See `org-ctrl-c-ctrl-c-hook' for more information. This hook runs as the first action when TAB is pressed, even before `org-cycle' messes around with the `outline-regexp' to cater for inline tasks and plain list item folding. If any function in this hook returns t, any other actions that would have been caused by TAB (such as table field motion or visibility cycling) will not occur.

org-timer-cancel-hook nil

Hook run before countdown timer is canceled.

org-timer-continue-hook nil

Hook run after relative timer is continued.

org-timer-done-hook nil

Hook run after countdown timer reaches zero.

org-timer-pause-hook nil

Hook run before relative timer is paused.

org-timer-set-hook nil

Hook run after countdown timer is set.

org-timer-start-hook nil

Hook run after relative timer is started.

org-timer-stop-hook nil

Hook run before relative timer is stopped.

org-todo-get-default-hook nil

Hook for functions that get a default item for todo.

Each function takes arguments (NEW-MARK OLD-MARK) and returns either nil or a string to be used for the todo mark.

org-todo-setup-filter-hook nil

Hook for functions that pre-filter todo specs.

Each function takes a todo spec and returns either nil or the spec transformed into canonical form.

org-todo-statistics-hook nil

Hook that is run whenever Org thinks TODO statistics should be updated.

This hook runs even if there is no statistics cookie present, in which case `org-after-todo-statistics-hook' would not run.

org-trigger-hook nil

Hook for functions that are triggered by a state change.

Each function gets as its single argument a property list with at least the following elements: (:type type-of-change :position pos-at-entry-start :from old-state :to new-state) Depending on the type, more properties may be present. This mechanism is currently implemented for: TODO state changes ------------------ :type todo-state-change :from previous state (keyword as a string), or nil, or a symbol 'todo' or 'done', to indicate the general type of state. :to new state, like in :from

orgtbl-after-send-table-hook nil

Hook for functions attaching to `C-c C-c', if the table is sent.

This can be used to add additional functionality after the table is sent to the receiver position, otherwise, if table is not sent, the functions are not run.

Commands

:PROPERTIES: :CUSTOM_ID: commands :END:

org-add-note

:PROPERTIES: :CUSTOM_ID: org-add-note :END:

org-add-planning-info (what &optional time &rest remove)

Add a note to the current entry.
This is done in the same way as adding a state change note.

:PROPERTIES: :CUSTOM_ID: org-add-planning-info :END:

org-advertized-archive-subtree (&optional find-done)

Insert new timestamp with keyword in the line directly after the headline.
WHAT indicates what kind of time stamp to add.  TIME indicates the time to use.
If non is given, the user is prompted for a date.
REMOVE indicates what kind of entries to remove.  An old WHAT entry will also
be removed.

:PROPERTIES: :CUSTOM_ID: org-advertized-archive-subtree :END:

org-agenda (&optional arg keys restriction)

Move the current subtree to the archive.
The archive can be a certain top-level heading in the current file, or in
a different file.  The tree will be moved to that location, the subtree
heading be marked DONE, and the current time will be added.

When called with prefix argument FIND-DONE, find whole trees without any
open TODO items and archive them (after getting confirmation from the user).
If the cursor is not at a headline when this command is called, try all level
1 trees.  If the cursor is on a headline, only try the direct children of
this heading.

:PROPERTIES: :CUSTOM_ID: org-agenda :END:

org-agenda-action

Dispatch agenda commands to collect entries to the agenda buffer.
Prompts for a command to execute.  Any prefix arg will be passed
on to the selected command.  The default selections are:

a     Call `org-agenda-list' to display the agenda for current day or week.
t     Call `org-todo-list' to display the global todo list.
T     Call `org-todo-list' to display the global todo list, select only
      entries with a specific TODO keyword (the user gets a prompt).
m     Call `org-tags-view' to display headlines with tags matching
      a condition  (the user is prompted for the condition).
M     Like `m', but select only TODO entries, no ordinary headlines.
L     Create a timeline for the current buffer.
e     Export views to associated files.
s     Search entries for keywords.
/     Multi occur across all agenda files and also files listed
      in `org-agenda-text-search-extra-files'.
<     Restrict agenda commands to buffer, subtree, or region.
      Press several times to get the desired effect.
>     Remove a previous restriction.
#     List "stuck" projects.
!     Configure what "stuck" means.
C     Configure custom agenda commands.

More commands can be added by configuring the variable
`org-agenda-custom-commands'.  In particular, specific tags and TODO keyword
searches can be pre-defined in this way.

If the current buffer is in Org-mode and visiting a file, you can also
first press `<' once to indicate that the agenda should be temporarily
(until the next use of C-c a) restricted to the current file.
Pressing `<' twice means to restrict to the current subtree or region
(if active).

:PROPERTIES: :CUSTOM_ID: org-agenda-action :END:

org-agenda-add-note (&optional arg)

Select entry for agenda action, or execute an agenda action.
This command prompts for another letter.  Valid inputs are:

m     Mark the entry at point for an agenda action
s     Schedule the marked entry to the date at the cursor
d     Set the deadline of the marked entry to the date at the cursor
r     Call `org-remember' with cursor date as the default date
c     Call `org-capture' with cursor date as the default date
SPC   Show marked entry in other window
TAB   Visit marked entry in other window

The cursor may be at a date in the calendar, or in the Org agenda.

:PROPERTIES: :CUSTOM_ID: org-agenda-add-note :END:

org-agenda-append-agenda

Add a time-stamped note to the entry at point.

:PROPERTIES: :CUSTOM_ID: org-agenda-append-agenda :END:

org-agenda-archive

Append another agenda view to the current one.
This function allows interactive building of block agendas.
Agenda views are separated by `org-agenda-block-separator'.

:PROPERTIES: :CUSTOM_ID: org-agenda-archive :END:

org-agenda-archive-default

Archive the entry or subtree belonging to the current agenda entry.

:PROPERTIES: :CUSTOM_ID: org-agenda-archive-default :END:

org-agenda-archive-default-with-confirmation

Archive the entry or subtree belonging to the current agenda entry.

:PROPERTIES: :CUSTOM_ID: org-agenda-archive-default-with-confirmation :END:

org-agenda-archive-to-archive-sibling

Archive the entry or subtree belonging to the current agenda entry.

:PROPERTIES: :CUSTOM_ID: org-agenda-archive-to-archive-sibling :END:

org-agenda-archive-with (cmd &optional confirm)

Move the entry to the archive sibling.

:PROPERTIES: :CUSTOM_ID: org-agenda-archive-with :END:

org-agenda-archives-mode (&optional with-files)

Move the entry to the archive sibling.

:PROPERTIES: :CUSTOM_ID: org-agenda-archives-mode :END:

org-agenda-bulk-action (&optional arg)

Toggle inclusion of items in trees marked with :ARCHIVE:.
When called with a prefix argument, include all archive files as well.

:PROPERTIES: :CUSTOM_ID: org-agenda-bulk-action :END:

org-agenda-bulk-mark (&optional arg)

Execute an remote-editing action on all marked entries.
The prefix arg is passed through to the command if possible.

:PROPERTIES: :CUSTOM_ID: org-agenda-bulk-mark :END:

org-agenda-bulk-mark-all

Mark the entry at point for future bulk action.

:PROPERTIES: :CUSTOM_ID: org-agenda-bulk-mark-all :END:

org-agenda-bulk-mark-regexp (regexp)

Mark all entries for future agenda bulk action.

:PROPERTIES: :CUSTOM_ID: org-agenda-bulk-mark-regexp :END:

org-agenda-bulk-remove-overlays (&optional beg end)

Mark entries matching REGEXP for future agenda bulk action.

:PROPERTIES: :CUSTOM_ID: org-agenda-bulk-remove-overlays :END:

org-agenda-bulk-toggle

Remove the mark overlays between BEG and END in the agenda buffer.
BEG and END default to the buffer limits.

This only removes the overlays, it does not remove the markers
from the list in `org-agenda-bulk-marked-entries'.

:PROPERTIES: :CUSTOM_ID: org-agenda-bulk-toggle :END:

org-agenda-bulk-unmark (&optional arg)

Toggle marking the entry at point for bulk action.

:PROPERTIES: :CUSTOM_ID: org-agenda-bulk-unmark :END:

org-agenda-bulk-unmark-all

Unmark the entry at point for future bulk action.

:PROPERTIES: :CUSTOM_ID: org-agenda-bulk-unmark-all :END:

org-agenda-clock-cancel (&optional arg)

Remove all marks in the agenda buffer.
This will remove the markers and the overlays.

:PROPERTIES: :CUSTOM_ID: org-agenda-clock-cancel :END:

org-agenda-clock-goto

Cancel the currently running clock.

:PROPERTIES: :CUSTOM_ID: org-agenda-clock-goto :END:

org-agenda-clock-in (&optional arg)

Jump to the currently clocked in task within the agenda.
If the currently clocked in task is not listed in the agenda
buffer, display it in another window.

:PROPERTIES: :CUSTOM_ID: org-agenda-clock-in :END:

org-agenda-clock-out

Start the clock on the currently selected item.

:PROPERTIES: :CUSTOM_ID: org-agenda-clock-out :END:

org-agenda-clockreport-mode (&optional with-filter)

Stop the currently running clock.

:PROPERTIES: :CUSTOM_ID: org-agenda-clockreport-mode :END:

org-agenda-columns

Toggle clocktable mode in an agenda buffer.
With prefix arg WITH-FILTER, make the clocktable respect the current
agenda filter.

:PROPERTIES: :CUSTOM_ID: org-agenda-columns :END:

org-agenda-convert-date

Turn on or update column view in the agenda.

:PROPERTIES: :CUSTOM_ID: org-agenda-convert-date :END:

org-agenda-cycle-show (&optional n)

:PROPERTIES: :CUSTOM_ID: org-agenda-cycle-show :END:

org-agenda-date-earlier (arg &optional what)

Show the current entry in another window, with default settings.
Default settings are taken from `org-show-hierarchy-above' and siblings.
When use repeatedly in immediate succession, the remote entry will cycle
through visibility

children -> subtree -> folded

When called with a numeric prefix arg, that arg will be passed through to
`org-agenda-show-1'.  For the interpretation of that argument, see the
docstring of `org-agenda-show-1'.

:PROPERTIES: :CUSTOM_ID: org-agenda-date-earlier :END:

org-agenda-date-earlier-hours (arg)

Change the date of this item to ARG day(s) earlier.

:PROPERTIES: :CUSTOM_ID: org-agenda-date-earlier-hours :END:

org-agenda-date-earlier-minutes (arg)

Change the time of this item, in hour steps.

:PROPERTIES: :CUSTOM_ID: org-agenda-date-earlier-minutes :END:

org-agenda-date-later (arg &optional what)

Change the time of this item, in units of `org-time-stamp-rounding-minutes'.

:PROPERTIES: :CUSTOM_ID: org-agenda-date-later :END:

org-agenda-date-later-hours (arg)

Change the date of this item to ARG day(s) later.

:PROPERTIES: :CUSTOM_ID: org-agenda-date-later-hours :END:

org-agenda-date-later-minutes (arg)

Change the time of this item, in hour steps.

:PROPERTIES: :CUSTOM_ID: org-agenda-date-later-minutes :END:

org-agenda-date-prompt (arg)

Change the time of this item, in units of `org-time-stamp-rounding-minutes'.

:PROPERTIES: :CUSTOM_ID: org-agenda-date-prompt :END:

org-agenda-day-view (&optional day-of-year)

Change the date of this item.  Date is prompted for, with default today.
The prefix ARG is passed to the `org-time-stamp' command and can therefore
be used to request time specification in the time stamp.

:PROPERTIES: :CUSTOM_ID: org-agenda-day-view :END:

org-agenda-deadline (arg &optional time)

Switch to daily view for agenda.
With argument DAY-OF-YEAR, switch to that day of the year.

:PROPERTIES: :CUSTOM_ID: org-agenda-deadline :END:

org-agenda-diary-entry

Schedule the item at point.
ARG is passed through to `org-deadline'.

:PROPERTIES: :CUSTOM_ID: org-agenda-diary-entry :END:

org-agenda-do-date-earlier (arg)

Make a diary entry, like the `i' command from the calendar.
All the standard commands work: block, weekly etc.
When `org-agenda-diary-file' points to a file,
`org-agenda-diary-entry-in-org-file' is called instead to create
entries in that Org-mode file.

:PROPERTIES: :CUSTOM_ID: org-agenda-do-date-earlier :END:

org-agenda-do-date-later (arg)

:PROPERTIES: :CUSTOM_ID: org-agenda-do-date-later :END:

org-agenda-earlier (arg)

:PROPERTIES: :CUSTOM_ID: org-agenda-earlier :END:

org-agenda-entry-text-mode (&optional arg)

Go backward in time by the current span.
With prefix ARG, go backward that many times the current span.

:PROPERTIES: :CUSTOM_ID: org-agenda-entry-text-mode :END:

org-agenda-entry-text-show

Toggle entry text mode in an agenda buffer.

:PROPERTIES: :CUSTOM_ID: org-agenda-entry-text-show :END:

org-agenda-execute (arg)

Add entry context for all agenda lines.

:PROPERTIES: :CUSTOM_ID: org-agenda-execute :END:

org-agenda-exit

Execute another agenda command, keeping same window.
So this is just a shortcut for `C-c a', available
in the agenda.

:PROPERTIES: :CUSTOM_ID: org-agenda-exit :END:

org-agenda-file-to-front (&optional to-end)

Exit agenda by removing the window or the buffer.
Also kill all Org-mode buffers which have been loaded by `org-agenda'.
Org-mode buffers visited directly by the user will not be touched.

:PROPERTIES: :CUSTOM_ID: org-agenda-file-to-front :END:

  • Access: C-c [, <menu-bar> <Org> <File List for Agenda> <Add/Move Current File to Front of List>
  • In file: org.el
  • Search modifications

org-agenda-filter-by-category (strip)

Move/add the current file to the top of the agenda file list.
If the file is not present in the list, it is added to the front.  If it is
present, it is moved there.  With optional argument TO-END, add/move to the
end of the list.

:PROPERTIES: :CUSTOM_ID: org-agenda-filter-by-category :END:

org-agenda-filter-by-tag (strip &optional char narrow)

Keep only those lines in the agenda buffer that have a specific category.
The category is that of the current line.

:PROPERTIES: :CUSTOM_ID: org-agenda-filter-by-tag :END:

org-agenda-filter-by-tag-refine (strip &optional char)

Keep only those lines in the agenda buffer that have a specific tag.
The tag is selected with its fast selection letter, as configured.
With prefix argument STRIP, remove all lines that do have the tag.
A lisp caller can specify CHAR.  NARROW means that the new tag should be
used to narrow the search - the interactive user can also press `-' or `+'
to switch to narrowing.

:PROPERTIES: :CUSTOM_ID: org-agenda-filter-by-tag-refine :END:

org-agenda-filter-by-top-category (strip)

Refine the current filter.  See `org-agenda-filter-by-tag'.

:PROPERTIES: :CUSTOM_ID: org-agenda-filter-by-top-category :END:

org-agenda-follow-mode

Keep only those lines in the agenda buffer that have a specific category.
The category is that of the current line.

:PROPERTIES: :CUSTOM_ID: org-agenda-follow-mode :END:

org-agenda-fontify-priorities

Toggle follow mode in an agenda buffer.

:PROPERTIES: :CUSTOM_ID: org-agenda-fontify-priorities :END:

org-agenda-goto (&optional highlight)

Make highest priority lines bold, and lowest italic.

:PROPERTIES: :CUSTOM_ID: org-agenda-goto :END:

org-agenda-goto-calendar

Go to the Org-mode file which contains the item at point.

:PROPERTIES: :CUSTOM_ID: org-agenda-goto-calendar :END:

org-agenda-goto-date (date)

Open the Emacs calendar with the date at the cursor.

:PROPERTIES: :CUSTOM_ID: org-agenda-goto-date :END:

org-agenda-goto-mouse (ev)

Jump to DATE in agenda.

:PROPERTIES: :CUSTOM_ID: org-agenda-goto-mouse :END:

org-agenda-goto-today

Go to the Org-mode file which contains the item at the mouse click.

:PROPERTIES: :CUSTOM_ID: org-agenda-goto-today :END:

org-agenda-holidays

Go to today.

:PROPERTIES: :CUSTOM_ID: org-agenda-holidays :END:

org-agenda-kill

Display the holidays for the 3 months around the cursor date.

:PROPERTIES: :CUSTOM_ID: org-agenda-kill :END:

org-agenda-kill-all-agenda-buffers

Kill the entry or subtree belonging to the current agenda entry.

:PROPERTIES: :CUSTOM_ID: org-agenda-kill-all-agenda-buffers :END:

org-agenda-later (arg)

Kill all buffers in `org-agena-mode'.
This is used when toggling sticky agendas.  You can also explicitly invoke it
with `C-c a C-k'.

:PROPERTIES: :CUSTOM_ID: org-agenda-later :END:

org-agenda-list (&optional arg start-day span)

Go forward in time by thee current span.
With prefix ARG, go forward that many times the current span.

:PROPERTIES: :CUSTOM_ID: org-agenda-list :END:

org-agenda-list-stuck-projects (&rest ignore)

Produce a daily/weekly view from all files in variable `org-agenda-files'.
The view will be for the current day or week, but from the overview buffer
you will be able to go to other days/weeks.

With a numeric prefix argument in an interactive call, the agenda will
span ARG days.  Lisp programs should instead specify SPAN to change
the number of days.  SPAN defaults to `org-agenda-span'.

START-DAY defaults to TODAY, or to the most recent match for the weekday
given in `org-agenda-start-on-weekday'.

:PROPERTIES: :CUSTOM_ID: org-agenda-list-stuck-projects :END:

org-agenda-log-mode (&optional special)

Create agenda view for projects that are stuck.
Stuck projects are project that have no next actions.  For the definitions
of what a project is and how to check if it stuck, customize the variable
`org-stuck-projects'.

:PROPERTIES: :CUSTOM_ID: org-agenda-log-mode :END:

org-agenda-manipulate-query-add

Toggle log mode in an agenda buffer.
With argument SPECIAL, show all possible log items, not only the ones
configured in `org-agenda-log-mode-items'.
With a double `C-u' prefix arg, show *only* log items, nothing else.

:PROPERTIES: :CUSTOM_ID: org-agenda-manipulate-query-add :END:

org-agenda-manipulate-query-add-re

Manipulate the query by adding a search term with positive selection.
Positive selection means the term must be matched for selection of an entry.

:PROPERTIES: :CUSTOM_ID: org-agenda-manipulate-query-add-re :END:

org-agenda-manipulate-query-subtract

Manipulate the query by adding a search regexp with positive selection.
Positive selection means the regexp must match for selection of an entry.

:PROPERTIES: :CUSTOM_ID: org-agenda-manipulate-query-subtract :END:

org-agenda-manipulate-query-subtract-re

Manipulate the query by adding a search term with negative selection.
Negative selection means term must not be matched for selection of an entry.

:PROPERTIES: :CUSTOM_ID: org-agenda-manipulate-query-subtract-re :END:

org-agenda-menu (event)

Manipulate the query by adding a search regexp with negative selection.
Negative selection means regexp must not match for selection of an entry.

:PROPERTIES: :CUSTOM_ID: org-agenda-menu :END:

org-agenda-mode

Agenda menu

:PROPERTIES: :CUSTOM_ID: org-agenda-mode :END:

org-agenda-month-view (&optional month)

Mode for time-sorted view on action items in Org-mode files.

The following commands are available:

key             binding
---             -------

C-c		Prefix Command
TAB		org-agenda-goto
C-k		org-agenda-kill
RET		org-agenda-switch-to
C-n		org-agenda-next-line
C-p		org-agenda-previous-line
C-x		Prefix Command
C-_		org-agenda-undo
SPC		org-agenda-show-and-scroll-up
!		org-agenda-toggle-deadlines
$		org-agenda-archive
%		org-agenda-bulk-mark-regexp
*		org-agenda-bulk-mark-all
+		org-agenda-priority-up
,		org-agenda-priority
-		org-agenda-priority-down
.		org-agenda-goto-today
/		org-agenda-filter-by-tag
0 .. 9		digit-argument
:		org-agenda-set-tags
;		org-timer-set-timer
<		org-agenda-filter-by-category
>		org-agenda-date-prompt
?		org-agenda-show-the-flagging-note
A		org-agenda-append-agenda
B		org-agenda-bulk-action
C		org-agenda-convert-date
D		org-agenda-toggle-diary
E		org-agenda-entry-text-mode
F		org-agenda-follow-mode
G		org-agenda-toggle-time-grid
H		org-agenda-holidays
I		org-agenda-clock-in
J		org-agenda-clock-goto
K		org-habit-toggle-habits
L		org-agenda-recenter
M		org-agenda-phases-of-moon
O		org-agenda-clock-out
P		org-agenda-show-priority
Q		org-agenda-Quit
R		org-agenda-clockreport-mode
S		org-agenda-sunrise-sunset
T		org-agenda-show-tags
U		org-agenda-bulk-unmark-all
X		org-agenda-clock-cancel
[		org-agenda-manipulate-query-add
\		org-agenda-filter-by-tag-refine
]		org-agenda-manipulate-query-subtract
^		org-agenda-filter-by-top-category
a		org-agenda-archive-default-with-confirmation
b		org-agenda-earlier
c		org-agenda-goto-calendar
d		org-agenda-day-view
e		org-agenda-set-effort
f		org-agenda-later
g		org-agenda-redo
h		org-agenda-holidays
i		org-agenda-diary-entry
j		org-agenda-goto-date
k		org-agenda-action
l		org-agenda-log-mode
m		org-agenda-bulk-mark
n		org-agenda-next-line
o		delete-other-windows
p		org-agenda-previous-line
q		org-agenda-quit
r		org-agenda-redo
s		org-save-all-org-buffers
t		org-agenda-todo
u		org-agenda-bulk-unmark
v		org-agenda-view-mode-dispatch
w		org-agenda-week-view
x		org-agenda-exit
y		org-agenda-year-view
z		org-agenda-add-note
{		org-agenda-manipulate-query-add-re
}		org-agenda-manipulate-query-subtract-re
DEL		org-agenda-show-scroll-down
C-/		org-agenda-undo
	org-agenda-todo-previousset
	org-agenda-todo-nextset
	org-agenda-priority-down
	org-agenda-do-date-earlier
	org-agenda-do-date-later
		org-agenda-priority-up
	org-agenda-show-scroll-down
		org-agenda-next-line
	org-agenda-goto-mouse
	org-agenda-show-mouse
		org-agenda-goto
		org-agenda-undo
		org-agenda-previous-line

C-c C-a		org-attach
C-c C-d		org-agenda-deadline
C-c C-n		org-agenda-next-date-line
C-c C-o		org-agenda-open-link
C-c C-p		org-agenda-previous-date-line
C-c C-q		org-agenda-set-tags
C-c C-s		org-agenda-schedule
C-c C-t		org-agenda-todo
C-c C-w		org-agenda-refile
C-c C-x		Prefix Command
C-c C-z		org-agenda-add-note
C-c $		org-agenda-archive
C-c ,		org-agenda-priority

C-x C-s		org-save-all-org-buffers
C-x C-w		org-agenda-write
C-x u		org-agenda-undo

C-c C-x C-a	org-agenda-archive-default
C-c C-x C-c	org-agenda-columns
C-c C-x C-e	org-clock-modify-effort-estimate
C-c C-x TAB	org-agenda-clock-in
C-c C-x C-j	org-clock-goto
C-c C-x C-k	org-agenda-action
C-c C-x RET	Prefix Command
C-c C-x C-o	org-agenda-clock-out
C-c C-x C-s	org-agenda-archive
C-c C-x C-x	org-agenda-clock-cancel
C-c C-x !	org-reload
C-c C-x >	org-agenda-remove-restriction-lock
C-c C-x A	org-agenda-archive-to-archive-sibling
C-c C-x a	org-agenda-toggle-archive-tag
C-c C-x b	org-agenda-tree-to-indirect-buffer
C-c C-x e	org-agenda-set-effort
C-c C-x p	org-agenda-set-property
C-c C-x 	org-agenda-priority-down
C-c C-x 	org-agenda-do-date-earlier
C-c C-x 			org-agenda-do-date-later
C-c C-x 			org-agenda-priority-up

C-c C-x RET g	org-mobile-pull
C-c C-x RET p	org-mobile-push

:PROPERTIES: :CUSTOM_ID: org-agenda-month-view :END:

org-agenda-next-date-line (&optional arg)

Switch to monthly view for agenda.
With argument MONTH, switch to that month.

:PROPERTIES: :CUSTOM_ID: org-agenda-next-date-line :END:

org-agenda-next-line

Jump to the next line indicating a date in agenda buffer.

:PROPERTIES: :CUSTOM_ID: org-agenda-next-line :END:

Move cursor to the next line, and show if follow mode is active.

:PROPERTIES: :CUSTOM_ID: org-agenda-open-link :END:

org-agenda-phases-of-moon

Follow the link in the current line, if any.
This looks for a link in the displayed line in the agenda.  It also looks
at the text of the entry itself.

:PROPERTIES: :CUSTOM_ID: org-agenda-phases-of-moon :END:

org-agenda-previous-date-line (&optional arg)

Display the phases of the moon for the 3 months around the cursor date.

:PROPERTIES: :CUSTOM_ID: org-agenda-previous-date-line :END:

org-agenda-previous-line

Jump to the previous line indicating a date in agenda buffer.

:PROPERTIES: :CUSTOM_ID: org-agenda-previous-line :END:

org-agenda-priority (&optional force-direction)

Move cursor to the previous line, and show if follow-mode is active.

:PROPERTIES: :CUSTOM_ID: org-agenda-priority :END:

org-agenda-priority-down

Set the priority of line at point, also in Org-mode file.
This changes the line at point, all other lines in the agenda referring to
the same tree node, and the headline of the tree node in the Org-mode file.

:PROPERTIES: :CUSTOM_ID: org-agenda-priority-down :END:

org-agenda-priority-up

Decrease the priority of line at point, also in Org-mode file.

:PROPERTIES: :CUSTOM_ID: org-agenda-priority-up :END:

org-agenda-quit

Increase the priority of line at point, also in Org-mode file.

:PROPERTIES: :CUSTOM_ID: org-agenda-quit :END:

org-agenda-Quit (&optional arg)

Exit agenda by killing agenda buffer or burying it when
`org-agenda-sticky' is non-NIL

:PROPERTIES: :CUSTOM_ID: org-agenda-Quit :END:

org-agenda-recenter (arg)

Exit agenda by removing the window or the buffer

:PROPERTIES: :CUSTOM_ID: org-agenda-recenter :END:

org-agenda-redo

Display the Org-mode file which contains the item at point and recenter.

:PROPERTIES: :CUSTOM_ID: org-agenda-redo :END:

org-agenda-refile (&optional goto rfloc no-update)

Rebuild Agenda.
When this is the global TODO list, a prefix argument will be interpreted.

:PROPERTIES: :CUSTOM_ID: org-agenda-refile :END:

org-agenda-remove-restriction-lock (&optional noupdate)

Refile the item at point.

:PROPERTIES: :CUSTOM_ID: org-agenda-remove-restriction-lock :END:

org-agenda-reset-view

Remove the agenda restriction lock.

:PROPERTIES: :CUSTOM_ID: org-agenda-reset-view :END:

org-agenda-schedule (arg &optional time)

Switch to default view for agenda.

:PROPERTIES: :CUSTOM_ID: org-agenda-schedule :END:

org-agenda-set-effort

Schedule the item at point.
ARG is passed through to `org-schedule'.

:PROPERTIES: :CUSTOM_ID: org-agenda-set-effort :END:

org-agenda-set-property

Set the effort property for the current headline.

:PROPERTIES: :CUSTOM_ID: org-agenda-set-property :END:

org-agenda-set-restriction-lock (&optional type)

Set a property for the current headline.

:PROPERTIES: :CUSTOM_ID: org-agenda-set-restriction-lock :END:

org-agenda-set-tags (&optional tag onoff)

Set restriction lock for agenda, to current subtree or file.
Restriction will be the file if TYPE is `file', or if type is the
universal prefix '(4), or if the cursor is before the first headline
in the file.  Otherwise, restriction will be to the current subtree.

:PROPERTIES: :CUSTOM_ID: org-agenda-set-tags :END:

org-agenda-show (&optional full-entry)

Set tags for the current headline.

:PROPERTIES: :CUSTOM_ID: org-agenda-show :END:

org-agenda-show-1 (&optional more)

Display the Org-mode file which contains the item at point.
With prefix argument FULL-ENTRY, make the entire entry visible
if it was hidden in the outline.

:PROPERTIES: :CUSTOM_ID: org-agenda-show-1 :END:

org-agenda-show-and-scroll-up (&optional arg)

Display the Org-mode file which contains the item at point.
The prefix arg selects the amount of information to display:

0   hide the subtree
1   just show the entry according to defaults.
2   show the children view
3   show the subtree view
4   show the entire subtree and any LOGBOOK drawers
5   show the entire subtree and any drawers
With prefix argument FULL-ENTRY, make the entire entry visible
if it was hidden in the outline.

:PROPERTIES: :CUSTOM_ID: org-agenda-show-and-scroll-up :END:

org-agenda-show-clocking-issues

Display the Org-mode file which contains the item at point.
When called repeatedly, scroll the window that is displaying the buffer.
With a C-u prefix, use `org-show-entry' instead of
`show-subtree' to display the item, so that drawers and logbooks stay
folded.

:PROPERTIES: :CUSTOM_ID: org-agenda-show-clocking-issues :END:

org-agenda-show-mouse (ev)

Add overlays, showing issues with clocking.
See also the user option `org-agenda-clock-consistency-checks'.

:PROPERTIES: :CUSTOM_ID: org-agenda-show-mouse :END:

org-agenda-show-priority

Display the Org-mode file which contains the item at the mouse click.

:PROPERTIES: :CUSTOM_ID: org-agenda-show-priority :END:

org-agenda-show-scroll-down

Show the priority of the current item.
This priority is composed of the main priority given with the [#A] cookies,
and by additional input from the age of a schedules or deadline entry.

:PROPERTIES: :CUSTOM_ID: org-agenda-show-scroll-down :END:

org-agenda-show-tags

Scroll down the window showing the agenda.

:PROPERTIES: :CUSTOM_ID: org-agenda-show-tags :END:

org-agenda-show-the-flagging-note

Show the tags applicable to the current item.

:PROPERTIES: :CUSTOM_ID: org-agenda-show-the-flagging-note :END:

org-agenda-sunrise-sunset (arg)

Display the flagging note in the other window.
When called a second time in direct sequence, offer to remove the FLAGGING
tag and (if present) the flagging note.

:PROPERTIES: :CUSTOM_ID: org-agenda-sunrise-sunset :END:

org-agenda-switch-to (&optional delete-other-windows)

Display sunrise and sunset for the cursor date.
Latitude and longitude can be specified with the variables
`calendar-latitude' and `calendar-longitude'.  When called with prefix
argument, latitude and longitude will be prompted for.

:PROPERTIES: :CUSTOM_ID: org-agenda-switch-to :END:

org-agenda-to-appt (&optional refresh filter &rest args)

Go to the Org-mode file which contains the item at point.

:PROPERTIES: :CUSTOM_ID: org-agenda-to-appt :END:

org-agenda-todo (&optional arg)

Activate appointments found in `org-agenda-files'.
With a C-u prefix, refresh the list of
appointments.

If FILTER is t, interactively prompt the user for a regular
expression, and filter out entries that don't match it.

If FILTER is a string, use this string as a regular expression
for filtering entries out.

If FILTER is a function, filter out entries against which
calling the function returns nil.  This function takes one
argument: an entry from `org-agenda-get-day-entries'.

FILTER can also be an alist with the car of each cell being
either 'headline or 'category.  For example:

  '((headline "IMPORTANT")
    (category "Work"))

will only add headlines containing IMPORTANT or headlines
belonging to the "Work" category.

ARGS are symbols indicating what kind of entries to consider.
By default `org-agenda-to-appt' will use :deadline, :scheduled
and :timestamp entries.  See the docstring of `org-diary' for
details and examples.

:PROPERTIES: :CUSTOM_ID: org-agenda-todo :END:

org-agenda-todo-nextset

Cycle TODO state of line at point, also in Org-mode file.
This changes the line at point, all other lines in the agenda referring to
the same tree node, and the headline of the tree node in the Org-mode file.

:PROPERTIES: :CUSTOM_ID: org-agenda-todo-nextset :END:

org-agenda-todo-previousset

Switch TODO entry to next sequence.

:PROPERTIES: :CUSTOM_ID: org-agenda-todo-previousset :END:

org-agenda-todo-yesterday (&optional arg)

Switch TODO entry to previous sequence.

:PROPERTIES: :CUSTOM_ID: org-agenda-todo-yesterday :END:

org-agenda-toggle-archive-tag

Like `org-agenda-todo' but the time of change will be 23:59 of yesterday

:PROPERTIES: :CUSTOM_ID: org-agenda-toggle-archive-tag :END:

org-agenda-toggle-deadlines

Toggle the archive tag for the current entry.

:PROPERTIES: :CUSTOM_ID: org-agenda-toggle-deadlines :END:

org-agenda-toggle-diary

Toggle inclusion of entries with a deadline in an agenda buffer.

:PROPERTIES: :CUSTOM_ID: org-agenda-toggle-diary :END:

org-agenda-toggle-time-grid

Toggle diary inclusion in an agenda buffer.

:PROPERTIES: :CUSTOM_ID: org-agenda-toggle-time-grid :END:

org-agenda-tree-to-indirect-buffer

Toggle time grid in an agenda buffer.

:PROPERTIES: :CUSTOM_ID: org-agenda-tree-to-indirect-buffer :END:

org-agenda-undo

Show the subtree corresponding to the current entry in an indirect buffer.
This calls the command `org-tree-to-indirect-buffer' from the original
Org-mode buffer.
With numerical prefix arg ARG, go up to this level and then take that tree.
With a C-u prefix, make a separate frame for this tree (i.e. don't
use the dedicated frame).

:PROPERTIES: :CUSTOM_ID: org-agenda-undo :END:

org-agenda-view-mode-dispatch

Undo a remote editing step in the agenda.
This undoes changes both in the agenda buffer and in the remote buffer
that have been changed along.

:PROPERTIES: :CUSTOM_ID: org-agenda-view-mode-dispatch :END:

org-agenda-week-view (&optional iso-week)

Call one of the view mode commands.

:PROPERTIES: :CUSTOM_ID: org-agenda-week-view :END:

org-agenda-write (file &optional open nosettings)

Switch to daily view for agenda.
With argument ISO-WEEK, switch to the corresponding ISO week.
If ISO-WEEK has more then 2 digits, only the last two encode the
week.  Any digits before this encode a year.  So 200712 means
week 12 of year 2007.  Years in the range 1938-2037 can also be
written as 2-digit years.

:PROPERTIES: :CUSTOM_ID: org-agenda-write :END:

org-agenda-year-view (&optional year)

Write the current buffer (an agenda view) as a file.
Depending on the extension of the file name, plain text (.txt),
HTML (.html or .htm) or Postscript (.ps) is produced.
If the extension is .ics, run icalendar export over all files used
to construct the agenda and limit the export to entries listed in the
agenda now.
With prefix argument OPEN, open the new file immediately.
If NOSETTINGS is given, do not scope the settings of
`org-agenda-exporter-settings' into the export commands.  This is used when
the settings have already been scoped and we do not wish to overrule other,
higher priority settings.

:PROPERTIES: :CUSTOM_ID: org-agenda-year-view :END:

org-align-all-tags

Switch to yearly view for agenda.
With argument YEAR, switch to that year.
If MONTH has more then 2 digits, only the last two encode the
month.  Any digits before this encode a year.  So 200712 means
December year 2007.  Years in the range 1938-2037 can also be
written as 2-digit years.

:PROPERTIES: :CUSTOM_ID: org-align-all-tags :END:

org-archive-set-tag

Align the tags i all headings.

:PROPERTIES: :CUSTOM_ID: org-archive-set-tag :END:

org-archive-subtree (&optional find-done)

Set the ARCHIVE tag.

:PROPERTIES: :CUSTOM_ID: org-archive-subtree :END:

org-archive-subtree-default

Move the current subtree to the archive.
The archive can be a certain top-level heading in the current file, or in
a different file.  The tree will be moved to that location, the subtree
heading be marked DONE, and the current time will be added.

When called with prefix argument FIND-DONE, find whole trees without any
open TODO items and archive them (after getting confirmation from the user).
If the cursor is not at a headline when this command is called, try all level
1 trees.  If the cursor is on a headline, only try the direct children of
this heading.

:PROPERTIES: :CUSTOM_ID: org-archive-subtree-default :END:

org-archive-subtree-default-with-confirmation

Archive the current subtree with the default command.
This command is set with the variable `org-archive-default-command'.

:PROPERTIES: :CUSTOM_ID: org-archive-subtree-default-with-confirmation :END:

org-archive-to-archive-sibling

Archive the current subtree with the default command.
This command is set with the variable `org-archive-default-command'.

:PROPERTIES: :CUSTOM_ID: org-archive-to-archive-sibling :END:

org-at-date-range-p (&optional inactive-ok)

Archive the current heading by moving it under the archive sibling.
The archive sibling is a sibling of the heading with the heading name
`org-archive-sibling-heading' and an `org-archive-tag' tag.  If this
sibling does not exist, it will be created at the end of the subtree.

:PROPERTIES: :CUSTOM_ID: org-at-date-range-p :END:

org-at-timestamp-p (&optional inactive-ok)

Is the cursor inside a date range?

:PROPERTIES: :CUSTOM_ID: org-at-timestamp-p :END:

org-attach

Determine if the cursor is in or at a timestamp.

:PROPERTIES: :CUSTOM_ID: org-attach :END:

org-attach-attach (file &optional visit-dir method)

The dispatcher for attachment commands.
Shows a list of commands and prompts for another key to execute a command.

:PROPERTIES: :CUSTOM_ID: org-attach-attach :END:

org-attach-attach-cp

Move/copy/link FILE into the attachment directory of the current task.
If VISIT-DIR is non-nil, visit the directory with dired.
METHOD may be `cp', `mv', `ln', or `lns' default taken from
`org-attach-method'.

:PROPERTIES: :CUSTOM_ID: org-attach-attach-cp :END:

org-attach-attach-ln

Attach a file by copying it.

:PROPERTIES: :CUSTOM_ID: org-attach-attach-ln :END:

org-attach-attach-lns

Attach a file by creating a hard link to it.
Beware that this does not work on systems that do not support hard links.
On some systems, this apparently does copy the file instead.

:PROPERTIES: :CUSTOM_ID: org-attach-attach-lns :END:

org-attach-attach-mv

Attach a file by creating a symbolic link to it.

Beware that this does not work on systems that do not support symbolic links.
On some systems, this apparently does copy the file instead.

:PROPERTIES: :CUSTOM_ID: org-attach-attach-mv :END:

org-attach-delete-all (&optional force)

Attach a file by moving (renaming) it.

:PROPERTIES: :CUSTOM_ID: org-attach-delete-all :END:

org-attach-delete-one (&optional file)

Delete all attachments from the current task.
This actually deletes the entire attachment directory.
A safer way is to open the directory in dired and delete from there.

:PROPERTIES: :CUSTOM_ID: org-attach-delete-one :END:

org-attach-new (file)

Delete a single attachment.

:PROPERTIES: :CUSTOM_ID: org-attach-new :END:

org-attach-open (&optional in-emacs)

Create a new attachment FILE for the current task.
The attachment is created as an Emacs buffer.

:PROPERTIES: :CUSTOM_ID: org-attach-open :END:

org-attach-open-in-emacs

Open an attachment of the current task.
If there are more than one attachment, you will be prompted for the file name.
This command will open the file using the settings in `org-file-apps'
and in the system-specific variants of this variable.
If IN-EMACS is non-nil, force opening in Emacs.

:PROPERTIES: :CUSTOM_ID: org-attach-open-in-emacs :END:

org-attach-reveal (&optional if-exists)

Open attachment, force opening in Emacs.
See `org-attach-open'.

:PROPERTIES: :CUSTOM_ID: org-attach-reveal :END:

org-attach-reveal-in-emacs

Show the attachment directory of the current task in dired.

:PROPERTIES: :CUSTOM_ID: org-attach-reveal-in-emacs :END:

org-attach-set-directory

Show the attachment directory of the current task.
This will attempt to use an external program to show the directory.

:PROPERTIES: :CUSTOM_ID: org-attach-set-directory :END:

org-attach-set-inherit

Set the ATTACH_DIR property of the current entry.
The property defines the directory that is used for attachments
of the entry.

:PROPERTIES: :CUSTOM_ID: org-attach-set-inherit :END:

org-attach-sync

Set the ATTACH_DIR_INHERIT property of the current entry.
The property defines the directory that is used for attachments
of the entry and any children that do not explicitly define (by setting
the ATTACH_DIR property) their own attachment directory.

:PROPERTIES: :CUSTOM_ID: org-attach-sync :END:

org-babel-check-src-block

Synchronize the current tasks with its attachments.
This can be used after files have been added externally.

:PROPERTIES: :CUSTOM_ID: org-babel-check-src-block :END:

org-babel-demarcate-block (&optional arg)

Check for misspelled header arguments in the current code block.

:PROPERTIES: :CUSTOM_ID: org-babel-demarcate-block :END:

org-babel-describe-bindings

Wrap or split the code in the region or on the point.
When called from inside of a code block the current block is
split.  When called from outside of a code block a new code block
is created.  In both cases if the region is demarcated and if the
region is not active then the point is demarcated.

:PROPERTIES: :CUSTOM_ID: org-babel-describe-bindings :END:

org-babel-detangle (&optional source-code-file)

Describe all keybindings behind `org-babel-key-prefix'.

:PROPERTIES: :CUSTOM_ID: org-babel-detangle :END:

org-babel-do-key-sequence-in-edit-buffer (key)

Propagate changes in source file back original to Org-mode file.
This requires that code blocks were tangled with link comments
which enable the original code blocks to be found.

:PROPERTIES: :CUSTOM_ID: org-babel-do-key-sequence-in-edit-buffer :END:

org-babel-examplize-region (beg end &optional results-switches)

Read key sequence and execute the command in edit buffer.
Enter a key sequence to be executed in the language major-mode
edit buffer.  For example, TAB will alter the contents of the
Org-mode code block according to the effect of TAB in the
language major-mode buffer.  For languages that support
interactive sessions, this can be used to send code from the Org
buffer to the session for evaluation using the native major-mode
evaluation mechanisms.

:PROPERTIES: :CUSTOM_ID: org-babel-examplize-region :END:

org-babel-execute-buffer (&optional arg)

Comment out region using the inline '==' or ': ' org example quote.

:PROPERTIES: :CUSTOM_ID: org-babel-execute-buffer :END:

org-babel-execute-maybe

Execute source code blocks in a buffer.
Call `org-babel-execute-src-block' on every source block in
the current buffer.

:PROPERTIES: :CUSTOM_ID: org-babel-execute-maybe :END:

org-babel-execute-src-block (&optional arg info params)

:PROPERTIES: :CUSTOM_ID: org-babel-execute-src-block :END:

org-babel-execute-src-block-maybe

Execute the current source code block.
Insert the results of execution into the buffer.  Source code
execution and the collection and formatting of results can be
controlled through a variety of header arguments.

With prefix argument ARG, force re-execution even if an existing
result cached in the buffer would otherwise have been returned.

Optionally supply a value for INFO in the form returned by
`org-babel-get-src-block-info'.

Optionally supply a value for PARAMS which will be merged with
the header arguments specified at the front of the source code
block.

:PROPERTIES: :CUSTOM_ID: org-babel-execute-src-block-maybe :END:

org-babel-execute-subtree (&optional arg)

Conditionally execute a source block.
Detect if this is context for a Babel src-block and if so
then run `org-babel-execute-src-block'.

:PROPERTIES: :CUSTOM_ID: org-babel-execute-subtree :END:

org-babel-exp-non-block-elements (start end)

Execute source code blocks in a subtree.
Call `org-babel-execute-src-block' on every source block in
the current subtree.

:PROPERTIES: :CUSTOM_ID: org-babel-exp-non-block-elements :END:

org-babel-exp-src-block (body &rest headers)

Process inline source and call lines between START and END for export.

:PROPERTIES: :CUSTOM_ID: org-babel-exp-src-block :END:

org-babel-expand-src-block (&optional arg info params)

Process source block for export.
Depending on the 'export' headers argument in replace the source
code block with...

both ---- display the code and the results

code ---- the default, display the code inside the block but do
          not process

results - just like none only the block is run on export ensuring
          that it's results are present in the org-mode buffer

none ----- do not display either code or results upon export

:PROPERTIES: :CUSTOM_ID: org-babel-expand-src-block :END:

org-babel-expand-src-block-maybe

Expand the current source code block.
Expand according to the source code block's header
arguments and pop open the results in a preview buffer.

:PROPERTIES: :CUSTOM_ID: org-babel-expand-src-block-maybe :END:

org-babel-goto-named-result (name)

Conditionally expand a source block.
Detect if this is context for a org-babel src-block and if so
then run `org-babel-expand-src-block'.

:PROPERTIES: :CUSTOM_ID: org-babel-goto-named-result :END:

org-babel-goto-named-src-block (name)

Go to a named result.

:PROPERTIES: :CUSTOM_ID: org-babel-goto-named-src-block :END:

org-babel-goto-src-block-head

Go to a named source-code block.

:PROPERTIES: :CUSTOM_ID: org-babel-goto-src-block-head :END:

org-babel-hash-at-point (&optional point)

Go to the beginning of the current code block.

:PROPERTIES: :CUSTOM_ID: org-babel-hash-at-point :END:

org-babel-haskell-export-to-lhs (&optional arg)

Return the value of the hash at POINT.
The hash is also added as the last element of the kill ring.
This can be called with C-c C-c.

:PROPERTIES: :CUSTOM_ID: org-babel-haskell-export-to-lhs :END:

org-babel-hide-result-toggle (&optional force)

Export to a .lhs file with all haskell code blocks escaped.
When called with a prefix argument the resulting
.lhs file will be exported to a .tex file.  This function will
create two new files, base-name.lhs and base-name.tex where
base-name is the name of the current org-mode file.

Note that all standard Babel literate programming
constructs (header arguments, no-web syntax etc...) are ignored.

:PROPERTIES: :CUSTOM_ID: org-babel-hide-result-toggle :END:

org-babel-hide-result-toggle-maybe

Toggle the visibility of the current result.

:PROPERTIES: :CUSTOM_ID: org-babel-hide-result-toggle-maybe :END:

org-babel-initiate-session (&optional arg info)

Toggle visibility of result at point.

:PROPERTIES: :CUSTOM_ID: org-babel-initiate-session :END:

org-babel-insert-header-arg

Initiate session for current code block.
If called with a prefix argument then resolve any variable
references in the header arguments and assign these variables in
the session. Copy the body of the code block to the kill ring.

:PROPERTIES: :CUSTOM_ID: org-babel-insert-header-arg :END:

org-babel-load-file (file)

Insert a header argument selecting from lists of common args and values.

:PROPERTIES: :CUSTOM_ID: org-babel-load-file :END:

org-babel-load-in-session (&optional arg info)

Load Emacs Lisp source code blocks in the Org-mode FILE.
This function exports the source code using
`org-babel-tangle' and then loads the resulting file using
`load-file'.

:PROPERTIES: :CUSTOM_ID: org-babel-load-in-session :END:

org-babel-load-in-session-maybe

Load the body of the current source-code block.
Evaluate the header arguments for the source block before
entering the session.  After loading the body this pops open the
session.

:PROPERTIES: :CUSTOM_ID: org-babel-load-in-session-maybe :END:

org-babel-lob-execute-maybe

Conditionally load a source block in a session.
Detect if this is context for a org-babel src-block and if so
then run `org-babel-load-in-session'.

:PROPERTIES: :CUSTOM_ID: org-babel-lob-execute-maybe :END:

org-babel-lob-ingest (&optional file)

Execute a Library of Babel source block, if appropriate.
Detect if this is context for a Library Of Babel source block and
if so then run the appropriate source block from the Library.

:PROPERTIES: :CUSTOM_ID: org-babel-lob-ingest :END:

org-babel-mark-block

Add all named source-blocks defined in FILE to
`org-babel-library-of-babel'.

:PROPERTIES: :CUSTOM_ID: org-babel-mark-block :END:

org-babel-next-src-block (&optional arg)

Mark current src block

:PROPERTIES: :CUSTOM_ID: org-babel-next-src-block :END:

org-babel-open-src-block-result (&optional re-run)

Jump to the next source block.
With optional prefix argument ARG, jump forward ARG many source blocks.

:PROPERTIES: :CUSTOM_ID: org-babel-open-src-block-result :END:

org-babel-pop-to-session (&optional arg info)

If `point' is on a src block then open the results of the
source code block, otherwise return nil.  With optional prefix
argument RE-RUN the source-code block is evaluated even if
results already exist.

:PROPERTIES: :CUSTOM_ID: org-babel-pop-to-session :END:

org-babel-pop-to-session-maybe

Switch to the session of the current code block.
Uses `org-babel-initiate-session' to start the session. If called
with a prefix argument then this is passed on to
`org-babel-initiate-session'.

:PROPERTIES: :CUSTOM_ID: org-babel-pop-to-session-maybe :END:

org-babel-previous-src-block (&optional arg)

Conditionally pop to a session.
Detect if this is context for a org-babel src-block and if so
then run `org-babel-pop-to-session'.

:PROPERTIES: :CUSTOM_ID: org-babel-previous-src-block :END:

org-babel-remove-result (&optional info)

Jump to the previous source block.
With optional prefix argument ARG, jump backward ARG many source blocks.

:PROPERTIES: :CUSTOM_ID: org-babel-remove-result :END:

org-babel-result-hide-all

Remove the result of the current source block.

:PROPERTIES: :CUSTOM_ID: org-babel-result-hide-all :END:

org-babel-sha1-hash (&optional info)

Fold all results in the current buffer.

:PROPERTIES: :CUSTOM_ID: org-babel-sha1-hash :END:

org-babel-shell-command-on-region (start end command &optional output-buffer replace error-buffer display-error-buffer)

Generate an sha1 hash based on the value of info.

:PROPERTIES: :CUSTOM_ID: org-babel-shell-command-on-region :END:

org-babel-switch-to-session (&optional arg info)

Execute COMMAND in an inferior shell with region as input.

Fixes bugs in the emacs 23.1.1 version of `shell-command-on-region'

Normally display output (if any) in temp buffer `*Shell Command Output*';
Prefix arg means replace the region with it.  Return the exit code of
COMMAND.

To specify a coding system for converting non-ASCII characters in
the input and output to the shell command, use
C-x RET c before this command.  By
default, the input (from the current buffer) is encoded in the
same coding system that will be used to save the file,
`buffer-file-coding-system'.  If the output is going to replace
the region, then it is decoded from that same coding system.

The noninteractive arguments are START, END, COMMAND,
OUTPUT-BUFFER, REPLACE, ERROR-BUFFER, and DISPLAY-ERROR-BUFFER.
Noninteractive callers can specify coding systems by binding
`coding-system-for-read' and `coding-system-for-write'.

If the command generates output, the output may be displayed
in the echo area or in a buffer.
If the output is short enough to display in the echo area
(determined by the variable `max-mini-window-height' if
`resize-mini-windows' is non-nil), it is shown there.  Otherwise
it is displayed in the buffer `*Shell Command Output*'.  The output
is available in that buffer in both cases.

If there is output and an error, a message about the error
appears at the end of the output.

If there is no output, or if output is inserted in the current buffer,
then `*Shell Command Output*' is deleted.

If the optional fourth argument OUTPUT-BUFFER is non-nil,
that says to put the output in some other buffer.
If OUTPUT-BUFFER is a buffer or buffer name, put the output there.
If OUTPUT-BUFFER is not a buffer and not nil,
insert output in the current buffer.
In either case, the output is inserted after point (leaving mark after it).

If REPLACE, the optional fifth argument, is non-nil, that means insert
the output in place of text from START to END, putting point and mark
around it.

If optional sixth argument ERROR-BUFFER is non-nil, it is a buffer
or buffer name to which to direct the command's standard error output.
If it is nil, error output is mingled with regular output.
If DISPLAY-ERROR-BUFFER is non-nil, display the error buffer if there
were any errors.  (This is always t, interactively.)
In an interactive call, the variable `shell-command-default-error-buffer'
specifies the value of ERROR-BUFFER.

:PROPERTIES: :CUSTOM_ID: org-babel-switch-to-session :END:

org-babel-switch-to-session-with-code (&optional arg info)

Switch to the session of the current code block.
Uses `org-babel-initiate-session' to start the session. If called
with a prefix argument then this is passed on to
`org-babel-initiate-session'.

:PROPERTIES: :CUSTOM_ID: org-babel-switch-to-session-with-code :END:

org-babel-tangle (&optional only-this-block target-file lang)

Switch to code buffer and display session.

:PROPERTIES: :CUSTOM_ID: org-babel-tangle :END:

org-babel-tangle-clean

Write code blocks to source-specific files.
Extract the bodies of all source code blocks from the current
file into their own source-specific files.  Optional argument
TARGET-FILE can be used to specify a default export file for all
source blocks.  Optional argument LANG can be used to limit the
exported source code blocks by language.

:PROPERTIES: :CUSTOM_ID: org-babel-tangle-clean :END:

org-babel-tangle-file (file &optional target-file lang)

Remove comments inserted by `org-babel-tangle'.
Call this function inside of a source-code file generated by
`org-babel-tangle' to remove all comments inserted automatically
by `org-babel-tangle'.  Warning, this comment removes any lines
containing constructs which resemble org-mode file links or noweb
references.

:PROPERTIES: :CUSTOM_ID: org-babel-tangle-file :END:

org-babel-tangle-jump-to-org

Extract the bodies of source code blocks in FILE.
Source code blocks are extracted with `org-babel-tangle'.
Optional argument TARGET-FILE can be used to specify a default
export file for all source blocks.  Optional argument LANG can be
used to limit the exported source code blocks by language.

:PROPERTIES: :CUSTOM_ID: org-babel-tangle-jump-to-org :END:

org-babel-view-src-block-info

Jump from a tangled code file to the related Org-mode file.

:PROPERTIES: :CUSTOM_ID: org-babel-view-src-block-info :END:

org-backward-same-level (arg &optional invisible-ok)

Display information on the current source block.
This includes header arguments, language and name, and is largely
a window into the `org-babel-get-src-block-info' function.

:PROPERTIES: :CUSTOM_ID: org-backward-same-level :END:

org-backward-sentence (&optional arg)

Move backward to the arg'th subheading at same level as this one.
Stop at the first and last subheadings of a superior heading.

:PROPERTIES: :CUSTOM_ID: org-backward-sentence :END:

org-beamer-mode (&optional arg)

Go to beginning of sentence, or beginning of table field.
This will call `backward-sentence' or `org-table-beginning-of-field',
depending on context.

:PROPERTIES: :CUSTOM_ID: org-beamer-mode :END:

org-beamer-select-environment

Special support for editing Org-mode files made to export to beamer.

:PROPERTIES: :CUSTOM_ID: org-beamer-select-environment :END:

org-beginning-of-item

Select the environment to be used by beamer for this entry.
While this uses (for convenience) a tag selection interface, the result
of this command will be that the BEAMER_env *property* of the entry is set.

In addition to this, the command will also set a tag as a visual aid, but
the tag does not have any semantic meaning.

:PROPERTIES: :CUSTOM_ID: org-beginning-of-item :END:

org-beginning-of-item-list

Go to the beginning of the current item.
Throw an error when not in a list.

:PROPERTIES: :CUSTOM_ID: org-beginning-of-item-list :END:

org-beginning-of-line (&optional arg)

Go to the beginning item of the current list or sublist.
Throw an error when not in a list.

:PROPERTIES: :CUSTOM_ID: org-beginning-of-line :END:

org-bibtex (&optional filename)

Go to the beginning of the current line.  If that is invisible, continue
to a visible line beginning.  This makes the function of C-a more intuitive.
If this is a headline, and `org-special-ctrl-a/e' is set, ignore tags on the
first attempt, and only move to after the tags when the cursor is already
beyond the end of the headline.

:PROPERTIES: :CUSTOM_ID: org-bibtex :END:

org-bibtex-check (&optional optional)

Export each headline in the current file to a bibtex entry.
Headlines are exported using `org-bibtex-export-headline'.

:PROPERTIES: :CUSTOM_ID: org-bibtex-check :END:

org-bibtex-check-all (&optional optional)

Check the current headline for required fields.
With prefix argument OPTIONAL also prompt for optional fields.

:PROPERTIES: :CUSTOM_ID: org-bibtex-check-all :END:

org-bibtex-create (&optional arg nonew)

Check all headlines in the current file.
With prefix argument OPTIONAL also prompt for optional fields.

:PROPERTIES: :CUSTOM_ID: org-bibtex-create :END:

org-bibtex-create-in-current-entry (&optional arg)

Create a new entry at the given level.
With a prefix arg, query for optional fields as well.
If nonew is t, add data to the headline of the entry at point.

:PROPERTIES: :CUSTOM_ID: org-bibtex-create-in-current-entry :END:

org-bibtex-export-to-kill-ring

Add bibliographical data to the current entry.
With a prefix arg, query for optional fields.

:PROPERTIES: :CUSTOM_ID: org-bibtex-export-to-kill-ring :END:

org-bibtex-read

Export current headline to kill ring as bibtex entry.

:PROPERTIES: :CUSTOM_ID: org-bibtex-read :END:

org-bibtex-search (string)

Read a bibtex entry and save to `org-bibtex-entries'.
This uses `bibtex-parse-entry'.

:PROPERTIES: :CUSTOM_ID: org-bibtex-search :END:

org-bibtex-write

Search for bibliographical entries in agenda files.
This function relies `org-search-view' to locate results.

:PROPERTIES: :CUSTOM_ID: org-bibtex-write :END:

org-bibtex-yank

Insert a heading built from the first element of `org-bibtex-entries'.

:PROPERTIES: :CUSTOM_ID: org-bibtex-yank :END:

org-calendar-goto-agenda

If kill ring holds a bibtex entry yank it as an Org-mode headline.

:PROPERTIES: :CUSTOM_ID: org-calendar-goto-agenda :END:

org-calendar-select

Compute the Org-mode agenda for the calendar date displayed at the cursor.
This is a command that has to be installed in `calendar-mode-map'.

:PROPERTIES: :CUSTOM_ID: org-calendar-select :END:

org-calendar-select-mouse (ev)

Return to `org-read-date' with the date currently selected.
This is used by `org-read-date' in a temporary keymap for the calendar buffer.

:PROPERTIES: :CUSTOM_ID: org-calendar-select-mouse :END:

org-capture (&optional goto keys)

Return to `org-read-date' with the date currently selected.
This is used by `org-read-date' in a temporary keymap for the calendar buffer.

:PROPERTIES: :CUSTOM_ID: org-capture :END:

org-capture-finalize (&optional stay-with-capture)

Capture something.

This will let you select a template from `org-capture-templates', and then
file the newly captured information.  The text is immediately inserted
at the target location, and an indirect buffer is shown where you can
edit it.  Pressing C-c C-c brings you back to the previous state
of Emacs, so that you can continue your work.

When called interactively with a C-u prefix argument GOTO, don't capture
anything, just go to the file/headline where the selected template
stores its notes.  With a double prefix argument C-u C-u, go to the last note
stored.

When called with a `C-0' (zero) prefix, insert a template at point.

Lisp programs can set KEYS to a string associated with a template in
`org-capture-templates'.  In this case, interactive selection will be
bypassed.

:PROPERTIES: :CUSTOM_ID: org-capture-finalize :END:

org-capture-goto-last-stored

Finalize the capture process.
With prefix argument STAY-WITH-CAPTURE, jump to the location of the
captured item after finalizing.

:PROPERTIES: :CUSTOM_ID: org-capture-goto-last-stored :END:

org-capture-goto-target (&optional template-key)

Go to the location where the last capture note was stored.

:PROPERTIES: :CUSTOM_ID: org-capture-goto-target :END:

org-capture-import-remember-templates

Go to the target location of a capture template.
The user is queried for the template.

:PROPERTIES: :CUSTOM_ID: org-capture-import-remember-templates :END:

org-capture-kill

Set org-capture-templates to be similar to `org-remember-templates'.

:PROPERTIES: :CUSTOM_ID: org-capture-kill :END:

org-capture-mode (&optional arg)

Abort the current capture process.

:PROPERTIES: :CUSTOM_ID: org-capture-mode :END:

org-capture-refile

Minor mode for special key bindings in a capture buffer.

:PROPERTIES: :CUSTOM_ID: org-capture-refile :END:

org-cdlatex-math-modify (&optional arg)

Finalize the current capture and then refile the entry.
Refiling is done from the base buffer, because the indirect buffer is then
already gone.  Any prefix argument will be passed to the refile command.

:PROPERTIES: :CUSTOM_ID: org-cdlatex-math-modify :END:

org-cdlatex-mode (&optional arg)

Execute `cdlatex-math-modify' in LaTeX fragments.
Revert to the normal definition outside of these fragments.

:PROPERTIES: :CUSTOM_ID: org-cdlatex-mode :END:

org-cdlatex-underscore-caret (&optional arg)

Toggle the minor `org-cdlatex-mode'.
This mode supports entering LaTeX environment and math in LaTeX fragments
in Org-mode.
key             binding
---             -------

C-c		Prefix Command
'		org-cdlatex-math-modify
^ .. _		org-cdlatex-underscore-caret
`		cdlatex-math-symbol

C-c {		cdlatex-environment

:PROPERTIES: :CUSTOM_ID: org-cdlatex-underscore-caret :END:

org-change-tag-in-region (beg end tag off)

Execute `cdlatex-sub-superscript' in LaTeX fragments.
Revert to the normal definition outside of these fragments.

:PROPERTIES: :CUSTOM_ID: org-change-tag-in-region :END:

org-check-after-date (date)

Add or remove TAG for each entry in the region.
This works in the agenda, and also in an org-mode buffer.

:PROPERTIES: :CUSTOM_ID: org-check-after-date :END:

org-check-before-date (date)

Check if there are deadlines or scheduled entries after DATE.

:PROPERTIES: :CUSTOM_ID: org-check-before-date :END:

org-check-dates-range (start-date end-date)

Check if there are deadlines or scheduled entries before DATE.

:PROPERTIES: :CUSTOM_ID: org-check-dates-range :END:

org-check-deadlines (ndays)

Check for deadlines/scheduled entries between START-DATE and END-DATE.

:PROPERTIES: :CUSTOM_ID: org-check-deadlines :END:

org-clock-cancel

Check if there are any deadlines due or past due.
A deadline is considered due if it happens within `org-deadline-warning-days'
days from today's date.  If the deadline appears in an entry marked DONE,
it is not shown.  The prefix arg NDAYS can be used to test that many
days.  If the prefix is a raw C-u prefix, all deadlines are shown.

:PROPERTIES: :CUSTOM_ID: org-clock-cancel :END:

org-clock-display (&optional total-only)

Cancel the running clock by removing the start timestamp.

:PROPERTIES: :CUSTOM_ID: org-clock-display :END:

org-clock-goto (&optional select)

Show subtree times in the entire buffer.
If TOTAL-ONLY is non-nil, only show the total time for the entire file
in the echo area.

Use M-x org-clock-remove-overlays to remove the subtree times.

:PROPERTIES: :CUSTOM_ID: org-clock-goto :END:

org-clock-in (&optional select start-time)

Go to the currently clocked-in entry, or to the most recently clocked one.
With prefix arg SELECT, offer recently clocked tasks for selection.

:PROPERTIES: :CUSTOM_ID: org-clock-in :END:

org-clock-in-last (&optional arg)

Start the clock on the current item.
If necessary, clock-out of the currently active clock.
With a prefix argument SELECT (C-u), offer a list of recently clocked tasks to
clock into.  When SELECT is C-u C-u, clock into the current task and mark
it as the default task, a special task that will always be offered in
the clocking selection, associated with the letter `d'.
When SELECT is C-u C-u C-u, clock in by using the last clock-out time as the start time
(see `org-clock-continuously' to make this the default behavior.)

:PROPERTIES: :CUSTOM_ID: org-clock-in-last :END:

org-clock-jump-to-current-clock (&optional effective-clock)

Clock in the last closed clocked item.
When already clocking in, send an warning.
With a universal prefix argument, select the task you want to
clock in from the last clocked in tasks.
With two universal prefix arguments, start clocking using the
last clock-out time, if any.

:PROPERTIES: :CUSTOM_ID: org-clock-jump-to-current-clock :END:

org-clock-mark-default-task

:PROPERTIES: :CUSTOM_ID: org-clock-mark-default-task :END:

org-clock-menu

Mark current task as default task.

:PROPERTIES: :CUSTOM_ID: org-clock-menu :END:

org-clock-modify-effort-estimate (&optional value)

:PROPERTIES: :CUSTOM_ID: org-clock-modify-effort-estimate :END:

org-clock-out (&optional fail-quietly at-time)

Add to or set the effort estimate of the item currently being clocked.
VALUE can be a number of minutes, or a string with format hh:mm or mm.
When the string starts with a + or a - sign, the current value of the effort
property will be changed by that amount.
This will update the "Effort" property of currently clocked item, and
the mode line.

:PROPERTIES: :CUSTOM_ID: org-clock-out :END:

org-clock-remove-overlays (&optional beg end noremove)

Stop the currently running clock.
Throw an error if there is no running clock and FAIL-QUIETLY is nil.

:PROPERTIES: :CUSTOM_ID: org-clock-remove-overlays :END:

org-clock-report (&optional arg)

Remove the occur highlights from the buffer.
BEG and END are ignored.  If NOREMOVE is nil, remove this function
from the `before-change-functions' in the current buffer.

:PROPERTIES: :CUSTOM_ID: org-clock-report :END:

org-clock-select-task (&optional prompt)

Create a table containing a report about clocked time.
If the cursor is inside an existing clocktable block, then the table
will be updated.  If not, a new clocktable will be inserted.  The scope
of the new clock will be subtree when called from within a subtree, and
file elsewhere.

When called with a prefix argument, move to the first clock table in the
buffer and update it.

:PROPERTIES: :CUSTOM_ID: org-clock-select-task :END:

org-clock-sum (&optional tstart tend headline-filter)

Select a task that recently was associated with clocking.

:PROPERTIES: :CUSTOM_ID: org-clock-sum :END:

org-clock-timestamps-down

Sum the times for each subtree.
Puts the resulting times in minutes as a text property on each headline.
TSTART and TEND can mark a time range to be considered.  HEADLINE-FILTER is a
zero-arg function that, if specified, is called for each headline in the time
range with point at the headline.  Headlines for which HEADLINE-FILTER returns
nil are excluded from the clock summation.

:PROPERTIES: :CUSTOM_ID: org-clock-timestamps-down :END:

org-clock-timestamps-up

Increase CLOCK timestamps at cursor.

:PROPERTIES: :CUSTOM_ID: org-clock-timestamps-up :END:

org-clock-update-time-maybe

Increase CLOCK timestamps at cursor.

:PROPERTIES: :CUSTOM_ID: org-clock-update-time-maybe :END:

org-clone-subtree-with-time-shift (n &optional shift)

If this is a CLOCK line, update it and return t.
Otherwise, return nil.

:PROPERTIES: :CUSTOM_ID: org-clone-subtree-with-time-shift :END:

org-closed-in-range

Clone the task (subtree) at point N times.
The clones will be inserted as siblings.

In interactive use, the user will be prompted for the number of
clones to be produced, and for a time SHIFT, which may be a
repeater as used in time stamps, for example `+3d'.

When a valid repeater is given and the entry contains any time
stamps, the clones will become a sequence in time, with time
stamps in the subtree shifted for each clone produced.  If SHIFT
is nil or the empty string, time stamps will be left alone.  The
ID property of the original subtree is removed.

If the original subtree did contain time stamps with a repeater,
the following will happen:
- the repeater will be removed in each clone
- an additional clone will be produced, with the current, unshifted
  date(s) in the entry.
- the original entry will be placed *after* all the clones, with
  repeater intact.
- the start days in the repeater in the original entry will be shifted
  to past the last clone.
In this way you can spell out a number of instances of a repeating task,
and still retain the repeater to cover future instances of the task.

:PROPERTIES: :CUSTOM_ID: org-closed-in-range :END:

org-columns

Sparse tree of items closed in a certain time range.
Still experimental, may disappear in the future.

:PROPERTIES: :CUSTOM_ID: org-columns :END:

org-columns-backward-char

Turn on column view on an org-mode file.

:PROPERTIES: :CUSTOM_ID: org-columns-backward-char :END:

org-columns-compute (property)

:PROPERTIES: :CUSTOM_ID: org-columns-compute :END:

org-columns-content

Sum the values of property PROPERTY hierarchically, for the entire buffer.

:PROPERTIES: :CUSTOM_ID: org-columns-content :END:

org-columns-delete

Switch to contents view while in columns view.

:PROPERTIES: :CUSTOM_ID: org-columns-delete :END:

org-columns-display-here (&optional props dateline)

Delete the column at point from columns view.

:PROPERTIES: :CUSTOM_ID: org-columns-display-here :END:

org-columns-display-here-title

Overlay the current line with column display.

:PROPERTIES: :CUSTOM_ID: org-columns-display-here-title :END:

org-columns-edit-allowed

Overlay the newline before the current line with the table title.

:PROPERTIES: :CUSTOM_ID: org-columns-edit-allowed :END:

org-columns-edit-attributes

Edit the list of allowed values for the current property.

:PROPERTIES: :CUSTOM_ID: org-columns-edit-attributes :END:

org-columns-edit-value (&optional key)

Edit the attributes of the current column.

:PROPERTIES: :CUSTOM_ID: org-columns-edit-value :END:

org-columns-forward-char

Edit the value of the property at point in column view.
Where possible, use the standard interface for changing this line.

:PROPERTIES: :CUSTOM_ID: org-columns-forward-char :END:

org-columns-menu (event)

:PROPERTIES: :CUSTOM_ID: org-columns-menu :END:

org-columns-move-left

Org Column Menu

:PROPERTIES: :CUSTOM_ID: org-columns-move-left :END:

org-columns-move-right

Swap this column with the one to the left.

:PROPERTIES: :CUSTOM_ID: org-columns-move-right :END:

org-columns-narrow (arg)

Swap this column with the one to the right.

:PROPERTIES: :CUSTOM_ID: org-columns-narrow :END:

org-columns-new (&optional prop title width op fmt fun &rest rest)

Make the column narrower by ARG characters.

:PROPERTIES: :CUSTOM_ID: org-columns-new :END:

org-columns-next-allowed-value (&optional previous nth)

Insert a new column, to the left of the current column.

:PROPERTIES: :CUSTOM_ID: org-columns-next-allowed-value :END:

Switch to the next allowed value for this column.
When PREVIOUS is set, go to the previous value.  When NTH is
an integer, select that value.

:PROPERTIES: :CUSTOM_ID: org-columns-open-link :END:

org-columns-previous-allowed-value

:PROPERTIES: :CUSTOM_ID: org-columns-previous-allowed-value :END:

org-columns-quit

Switch to the previous allowed value for this column.

:PROPERTIES: :CUSTOM_ID: org-columns-quit :END:

org-columns-redo

Remove the column overlays and in this way exit column editing.

:PROPERTIES: :CUSTOM_ID: org-columns-redo :END:

org-columns-remove-overlays

Construct the column display again.

:PROPERTIES: :CUSTOM_ID: org-columns-remove-overlays :END:

org-columns-set-tags-or-toggle (&optional arg)

Remove all currently active column overlays.

:PROPERTIES: :CUSTOM_ID: org-columns-set-tags-or-toggle :END:

org-columns-show-value

Toggle checkbox at point, or set tags for current headline.

:PROPERTIES: :CUSTOM_ID: org-columns-show-value :END:

org-columns-todo (&optional arg)

Show the full value of the property.

:PROPERTIES: :CUSTOM_ID: org-columns-todo :END:

org-columns-widen (arg)

Change the TODO state during column view.

:PROPERTIES: :CUSTOM_ID: org-columns-widen :END:

org-compute-property-at-point

Make the column wider by ARG characters.

:PROPERTIES: :CUSTOM_ID: org-compute-property-at-point :END:

org-content (&optional arg)

Compute the property at point.
This looks for an enclosing column format, extracts the operator and
then applies it to the property in the column format's scope.

:PROPERTIES: :CUSTOM_ID: org-content :END:

org-convert-to-odd-levels

Show all headlines in the buffer, like a table of contents.
With numerical argument N, show content up to level N.

:PROPERTIES: :CUSTOM_ID: org-convert-to-odd-levels :END:

org-convert-to-oddeven-levels

Convert an org-mode file with all levels allowed to one with odd levels.
This will leave level 1 alone, convert level 2 to level 3, level 3 to
level 5 etc.

:PROPERTIES: :CUSTOM_ID: org-convert-to-oddeven-levels :END:

org-copy-special

Convert an org-mode file with only odd levels to one with odd/even levels.
This promotes level 3 to level 2, level 5 to level 3 etc.  If the
file contains a section with an even level, conversion would
destroy the structure of the file.  An error is signaled in this
case.

:PROPERTIES: :CUSTOM_ID: org-copy-special :END:

  • Access: <menu-bar> <Org> <Edit Structure> <Copy Subtree>, <menu-bar> <Tbl> <Rectangle> <Copy Rectangle>, C-c C-x M-w
  • In file: org.el
  • Search modifications

org-copy-subtree (&optional n cut force-store-markers)

Copy region in table or copy current subtree.
Calls `org-table-copy' or `org-copy-subtree', depending on context.
See the individual commands for more information.

:PROPERTIES: :CUSTOM_ID: org-copy-subtree :END:

org-copy-visible (beg end)

Cut the current subtree into the clipboard.
With prefix arg N, cut this many sequential subtrees.
This is a short-hand for marking the subtree and then copying it.
If CUT is non-nil, actually cut the subtree.
If FORCE-STORE-MARKERS is non-nil, store the relative locations
of some markers in the region, even if CUT is non-nil.  This is
useful if the caller implements cut-and-paste as copy-then-paste-then-cut.

:PROPERTIES: :CUSTOM_ID: org-copy-visible :END:

org-create-customize-menu

Copy the visible parts of the region.

:PROPERTIES: :CUSTOM_ID: org-create-customize-menu :END:

org-create-math-formula (latex-frag &optional mathml-file)

Create a full customization menu for Org-mode, insert it into the menu.

:PROPERTIES: :CUSTOM_ID: org-create-math-formula :END:

org-ctags-all-tags-in-current-tags-table

Convert LATEX-FRAG to MathML and store it in MATHML-FILE.
Use `org-latex-to-mathml-convert-command'.  If the conversion is
sucessful, return the portion between " "
elements otherwise return nil.  When MATHML-FILE is specified,
write the results in to that file.  When invoked as an
interactive command, prompt for LATEX-FRAG, with initial value
set to the current active region and echo the results for user
inspection.

:PROPERTIES: :CUSTOM_ID: org-ctags-all-tags-in-current-tags-table :END:

org-ctags-append-topic (name &optional narrowp)

Read all tags defined in the active TAGS file, into a list of strings.
Return the list.

:PROPERTIES: :CUSTOM_ID: org-ctags-append-topic :END:

org-ctags-create-tags (&optional directory-name)

This function is intended to be used in ORG-OPEN-LINK-FUNCTIONS.
Append a new toplevel heading to the end of the current buffer. The
heading contains NAME surrounded by <>, thus making
the heading a destination for the tag `NAME'.

:PROPERTIES: :CUSTOM_ID: org-ctags-create-tags :END:

org-ctags-find-tag (name)

(Re)create tags file in the directory of the active buffer.
The file will contain tag definitions for all the files in the
directory and its subdirectories which are recognized by ctags.
This will include files ending in `.org' as well as most other
source files (.C, .H, .EL, .LISP, etc).  All the resulting tags
end up in one file, called TAGS, located in the directory.  This
function may take several seconds to finish if the directory or
its subdirectories contain large numbers of taggable files.

:PROPERTIES: :CUSTOM_ID: org-ctags-find-tag :END:

org-ctags-find-tag-interactive

This function is intended to be used in ORG-OPEN-LINK-FUNCTIONS.
Look for a tag called `NAME' in the current TAGS table.  If it is found,
visit the file and location where the tag is found.

:PROPERTIES: :CUSTOM_ID: org-ctags-find-tag-interactive :END:

org-ctags-get-filename-for-tag (tag)

Prompt for the name of a tag, with autocompletion, then visit the named tag.
Uses `ido-mode' if available.
If the user enters a string that does not match an existing tag, create
a new topic.

:PROPERTIES: :CUSTOM_ID: org-ctags-get-filename-for-tag :END:

org-ctags-open-file (name &optional title)

TAG is a string.  Search the active TAGS file for a matching tag.
If the tag is found, return a list containing the filename, line number, and
buffer position where the tag is found.

:PROPERTIES: :CUSTOM_ID: org-ctags-open-file :END:

org-ctags-visit-buffer-or-file (name &optional create)

Visit or create a file called `NAME.org', and insert a new topic.
The new topic will be titled NAME (or TITLE if supplied).

:PROPERTIES: :CUSTOM_ID: org-ctags-visit-buffer-or-file :END:

org-ctrl-c-ctrl-c (&optional arg)

This function is intended to be used in ORG-OPEN-LINK-FUNCTIONS.
Visit buffer named `NAME.org'.  If there is no such buffer, visit the file
with the same name if it exists.  If the file does not exist, then behavior
depends on the value of CREATE.

If CREATE is nil (default), then return nil.  Do not create a new file.
If CREATE is t, create the new file and visit it.
If CREATE is the symbol `ask', then ask the user if they wish to create
the new file.

:PROPERTIES: :CUSTOM_ID: org-ctrl-c-ctrl-c :END:

org-ctrl-c-minus

Set tags in headline, or update according to changed information at point.

This command does many different things, depending on context:

- If a function in `org-ctrl-c-ctrl-c-hook' recognizes this location,
  this is what we do.

- If the cursor is on a statistics cookie, update it.

- If the cursor is in a headline, prompt for tags and insert them
  into the current line, aligned to `org-tags-column'.  When called
  with prefix arg, realign all tags in the current buffer.

- If the cursor is in one of the special #+KEYWORD lines, this
  triggers scanning the buffer for these lines and updating the
  information.

- If the cursor is inside a table, realign the table.  This command
  works even if the automatic table editor has been turned off.

- If the cursor is on a #+TBLFM line, re-apply the formulas to
  the entire table.

- If the cursor is at a footnote reference or definition, jump to
  the corresponding definition or references, respectively.

- If the cursor is a the beginning of a dynamic block, update it.

- If the current buffer is a capture buffer, close note and file it.

- If the cursor is on a <<>>, update radio targets and
  corresponding links in this buffer.

- If the cursor is on a numbered item in a plain list, renumber the
  ordered list.

- If the cursor is on a checkbox, toggle it.

- If the cursor is on a code block, evaluate it.  The variable
  `org-confirm-babel-evaluate' can be used to control prompting
  before code block evaluation, by default every code block
  evaluation requires confirmation.  Code block evaluation can be
  inhibited by setting `org-babel-no-eval-on-ctrl-c-ctrl-c'.

:PROPERTIES: :CUSTOM_ID: org-ctrl-c-minus :END:

org-ctrl-c-ret

Insert separator line in table or modify bullet status of line.
Also turns a plain line or a region of lines into list items.
Calls `org-table-insert-hline', `org-toggle-item', or
`org-cycle-list-bullet', depending on context.

:PROPERTIES: :CUSTOM_ID: org-ctrl-c-ret :END:

org-ctrl-c-star

Call `org-table-hline-and-move' or `org-insert-heading' dep. on context.

:PROPERTIES: :CUSTOM_ID: org-ctrl-c-star :END:

org-customize

Compute table, or change heading status of lines.
Calls `org-table-recalculate' or `org-toggle-heading',
depending on context.

:PROPERTIES: :CUSTOM_ID: org-customize :END:

org-cut-special

Call the customize function with org as argument.

:PROPERTIES: :CUSTOM_ID: org-cut-special :END:

  • Access: C-c C-x C-w, <menu-bar> <Org> <Edit Structure> <Cut Subtree>, <menu-bar> <Tbl> <Rectangle> <Cut Rectangle>
  • In file: org.el
  • Search modifications

org-cut-subtree (&optional n)

Cut region in table or cut current subtree.
Calls `org-table-copy' or `org-cut-subtree', depending on context.
See the individual commands for more information.

:PROPERTIES: :CUSTOM_ID: org-cut-subtree :END:

org-cycle (&optional arg)

Cut the current subtree into the clipboard.
With prefix arg N, cut this many sequential subtrees.
This is a short-hand for marking the subtree and then cutting it.

:PROPERTIES: :CUSTOM_ID: org-cycle :END:

  • Access: <tab>, TAB, <menu-bar> <Tbl> <Next Field>, <menu-bar> <Org> <Show/Hide> <Cycle Visibility>
  • In file: org.el
  • Search modifications

org-cycle-agenda-files

TAB-action and visibility cycling for Org-mode.

This is the command invoked in Org-mode by the TAB key.  Its main purpose
is outline visibility cycling, but it also invokes other actions
in special contexts.

- When this function is called with a prefix argument, rotate the entire
  buffer through 3 states (global cycling)
  1. OVERVIEW: Show only top-level headlines.
  2. CONTENTS: Show all headlines of all levels, but no body text.
  3. SHOW ALL: Show everything.
  When called with two `C-u C-u' prefixes, switch to the startup visibility,
  determined by the variable `org-startup-folded', and by any VISIBILITY
  properties in the buffer.
  When called with three `C-u C-u C-u' prefixed, show the entire buffer,
  including any drawers.

- When inside a table, re-align the table and move to the next field.

- When point is at the beginning of a headline, rotate the subtree started
  by this line through 3 different states (local cycling)
  1. FOLDED:   Only the main headline is shown.
  2. CHILDREN: The main headline and the direct children are shown.
               From this state, you can move to one of the children
               and zoom in further.
  3. SUBTREE:  Show the entire subtree, including body text.
  If there is no subtree, switch directly from CHILDREN to FOLDED.

- When point is at the beginning of an empty headline and the variable
  `org-cycle-level-after-item/entry-creation' is set, cycle the level
  of the headline by demoting and promoting it to likely levels.  This
  speeds up creation document structure by pressing TAB once or several
  times right after creating a new headline.

- When there is a numeric prefix, go up to a heading with level ARG, do
  a `show-subtree' and return to the previous cursor position.  If ARG
  is negative, go up that many levels.

- When point is not at the beginning of a headline, execute the global
  binding for TAB, which is re-indenting the line.  See the option
  `org-cycle-emulate-tab' for details.

- Special case: if point is at the beginning of the buffer and there is
  no headline in line 1, this function will act as if called with prefix arg
  (C-u TAB, same as S-TAB) also when called without prefix arg.
  But only if also the variable `org-cycle-global-at-bob' is t.

:PROPERTIES: :CUSTOM_ID: org-cycle-agenda-files :END:

org-cycle-global

Cycle through the files in `org-agenda-files'.
If the current buffer visits an agenda file, find the next one in the list.
If the current buffer does not, find the first agenda file.

:PROPERTIES: :CUSTOM_ID: org-cycle-global :END:

org-cycle-level

:PROPERTIES: :CUSTOM_ID: org-cycle-level :END:

org-cycle-list-bullet (&optional which)

Cycle the level of an empty headline through possible states.
This goes first to child, then to parent, level, then up the hierarchy.
After top level, it switches back to sibling level.

:PROPERTIES: :CUSTOM_ID: org-cycle-list-bullet :END:

org-cycle-local

Cycle through the different itemize/enumerate bullets.
This cycle the entire list level through the sequence:

   `-'  ->  `+'  ->  `*'  ->  `1.'  ->  `1)'

If WHICH is a valid string, use that as the new bullet.  If WHICH
is an integer, 0 means `-', 1 means `+' etc.  If WHICH is
`previous', cycle backwards.

:PROPERTIES: :CUSTOM_ID: org-cycle-local :END:

org-date-from-calendar

:PROPERTIES: :CUSTOM_ID: org-date-from-calendar :END:

org-datetree-cleanup

Insert time stamp corresponding to cursor date in *Calendar* buffer.
If there is already a time stamp at the cursor position, update it.

:PROPERTIES: :CUSTOM_ID: org-datetree-cleanup :END:

org-dblock-update (&optional arg)

Make sure all entries in the current tree are under the correct date.
It may be useful to restrict the buffer to the applicable portion
before running this command, even though the command tries to be smart.

:PROPERTIES: :CUSTOM_ID: org-dblock-update :END:

org-dblock-write:amazon (params)

User command for updating dynamic blocks.
Update the dynamic block at point.  With prefix ARG, update all dynamic
blocks in the buffer.

:PROPERTIES: :CUSTOM_ID: org-dblock-write:amazon :END:

org-deadline (&optional remove time)

Dynamic block for inserting the cover of a book.

:PROPERTIES: :CUSTOM_ID: org-deadline :END:

org-decrypt-entries

Insert the "DEADLINE:" string with a timestamp to make a deadline.
With argument REMOVE, remove any deadline from the item.
With argument TIME, set the deadline at the corresponding date.  TIME
can either be an Org date like "2011-07-24" or a delta like "+2d".

:PROPERTIES: :CUSTOM_ID: org-decrypt-entries :END:

org-decrypt-entry

Decrypt all entries in the current buffer.

:PROPERTIES: :CUSTOM_ID: org-decrypt-entry :END:

org-delete-backward-char (N)

Decrypt the content of the current headline.

:PROPERTIES: :CUSTOM_ID: org-delete-backward-char :END:

org-delete-char (N)

Like `delete-backward-char', insert whitespace at field end in tables.
When deleting backwards, in tables this function will insert whitespace in
front of the next "|" separator, to keep the table aligned.  The table will
still be marked for re-alignment if the field did fill the entire column,
because, in this case the deletion might narrow the column.

:PROPERTIES: :CUSTOM_ID: org-delete-char :END:

org-delete-property (property)

Like `delete-char', but insert whitespace at field end in tables.
When deleting characters, in tables this function will insert whitespace in
front of the next "|" separator, to keep the table aligned.  The table will
still be marked for re-alignment if the field did fill the entire column,
because, in this case the deletion might narrow the column.

:PROPERTIES: :CUSTOM_ID: org-delete-property :END:

org-delete-property-globally (property)

In the current entry, delete PROPERTY.

:PROPERTIES: :CUSTOM_ID: org-delete-property-globally :END:

org-demote-subtree

Remove PROPERTY globally, from all entries.

:PROPERTIES: :CUSTOM_ID: org-demote-subtree :END:

org-display-inline-images (&optional include-linked refresh beg end)

Demote the entire subtree.  See `org-demote'.
See also `org-promote'.

:PROPERTIES: :CUSTOM_ID: org-display-inline-images :END:

org-display-outline-path (&optional file current)

Display inline images.
Normally only links without a description part are inlined, because this
is how it will work for export.  When INCLUDE-LINKED is set, also links
with a description part will be inlined.  This can be nice for a quick
look at those images, but it does not reflect what exported files will look
like.
When REFRESH is set, refresh existing images between BEG and END.
This will create new image displays only if necessary.
BEG and END default to the buffer boundaries.

:PROPERTIES: :CUSTOM_ID: org-display-outline-path :END:

org-do-demote

Display the current outline path in the echo area.

:PROPERTIES: :CUSTOM_ID: org-do-demote :END:

org-do-promote

Demote the current heading lower down the tree.
If the region is active in `transient-mark-mode', demote all headings
in the region.

:PROPERTIES: :CUSTOM_ID: org-do-promote :END:

org-edit-agenda-file-list

Promote the current heading higher up the tree.
If the region is active in `transient-mark-mode', promote all headings
in the region.

:PROPERTIES: :CUSTOM_ID: org-edit-agenda-file-list :END:

org-edit-fixed-width-region

Edit the list of agenda files.
Depending on setup, this either uses customize to edit the variable
`org-agenda-files', or it visits the file that is holding the list.  In the
latter case, the buffer is set up in a way that saving it automatically kills
the buffer and restores the previous window configuration.

:PROPERTIES: :CUSTOM_ID: org-edit-fixed-width-region :END:

org-edit-special (&optional arg)

Edit the fixed-width ascii drawing at point.
This must be a region where each line starts with a colon followed by
a space character.
An new buffer is created and the fixed-width region is copied into it,
and the buffer is switched into `artist-mode' for editing.  When done,
exit with M-x org-edit-src-exit.  The edited text will then replace
the fragment in the Org-mode buffer.

:PROPERTIES: :CUSTOM_ID: org-edit-special :END:

  • Access: C-c ', <menu-bar> <Org> <Editing> <Edit Source Example>, <menu-bar> <Tbl> <Calculate> <Edit Formulas>
  • In file: org.el
  • Search modifications

org-edit-src-code (&optional context code edit-buffer-name)

Call a special editor for the stuff at point.
When at a table, call the formula editor with `org-table-edit-formulas'.
When at the first line of an src example, call `org-edit-src-code'.
When in an #+include line, visit the include file.  Otherwise call
`ffap' to visit the file at point.

:PROPERTIES: :CUSTOM_ID: org-edit-src-code :END:

org-edit-src-continue (e)

Edit the source CODE example at point.
The example is copied to a separate buffer, and that buffer is
switched to the correct language mode.  When done, exit with
M-x org-edit-src-exit.  This will remove the original code in the
Org buffer, and replace it with the edited version.  An optional
argument CONTEXT is used by M-x org-edit-src-save when calling
this function.  See `org-src-window-setup' to configure the
display of windows containing the Org buffer and the code
buffer.

:PROPERTIES: :CUSTOM_ID: org-edit-src-continue :END:

org-edit-src-exit (&optional context)

Continue editing source blocks.

:PROPERTIES: :CUSTOM_ID: org-edit-src-exit :END:

org-edit-src-save

Exit special edit and protect problematic lines.

:PROPERTIES: :CUSTOM_ID: org-edit-src-save :END:

org-emphasize (&optional char)

Save parent buffer with current state source-code buffer.

:PROPERTIES: :CUSTOM_ID: org-emphasize :END:

org-encrypt-entries

Insert or change an emphasis, i.e. a font like bold or italic.
If there is an active region, change that region to a new emphasis.
If there is no region, just insert the marker characters and position
the cursor between them.
CHAR should be either the marker character, or the first character of the
HTML tag associated with that emphasis.  If CHAR is a space, the means
to remove the emphasis of the selected region.
If char is not given (for example in an interactive call) it
will be prompted for.

:PROPERTIES: :CUSTOM_ID: org-encrypt-entries :END:

org-encrypt-entry

Encrypt all top-level entries in the current buffer.

:PROPERTIES: :CUSTOM_ID: org-encrypt-entry :END:

org-end-of-item

Encrypt the content of the current headline.

:PROPERTIES: :CUSTOM_ID: org-end-of-item :END:

org-end-of-item-list

Go to the end of the current item.
Throw an error when not in a list.

:PROPERTIES: :CUSTOM_ID: org-end-of-item-list :END:

org-end-of-line (&optional arg)

Go to the end of the current list or sublist.
Throw an error when not in a list.

:PROPERTIES: :CUSTOM_ID: org-end-of-line :END:

org-entities-create-table

Go to the end of the line.
If this is a headline, and `org-special-ctrl-a/e' is set, ignore tags on the
first attempt, and only move to after the tags when the cursor is already
beyond the end of the headline.

:PROPERTIES: :CUSTOM_ID: org-entities-create-table :END:

org-entities-help

Create an Org mode table with all entities.

:PROPERTIES: :CUSTOM_ID: org-entities-help :END:

org-evaluate-time-range (&optional to-buffer)

Create a Help buffer with all available entities.

:PROPERTIES: :CUSTOM_ID: org-evaluate-time-range :END:

org-export (&optional arg)

Evaluate a time range by computing the difference between start and end.
Normally the result is just printed in the echo area, but with prefix arg
TO-BUFFER, the result is inserted just after the date stamp into the buffer.
If the time range is actually in a table, the result is inserted into the
next column.
For time difference computation, a year is assumed to be exactly 365
days in order to avoid rounding problems.

:PROPERTIES: :CUSTOM_ID: org-export :END:

org-export-as-ascii (arg &optional hidden ext-plist to-buffer body-only pub-dir)

Export dispatcher for Org-mode.
When `org-export-run-in-background' is non-nil, try to run the command
in the background.  This will be done only for commands that write
to a file.  For details see the docstring of `org-export-run-in-background'.

The prefix argument ARG will be passed to the exporter.  However, if
ARG is a double universal prefix C-u C-u, that means to inverse the
value of `org-export-run-in-background'.

If `org-export-initial-scope' is set to 'subtree, try to export
the current subtree, otherwise try to export the whole buffer.
Pressing `1' will switch between these two options.

:PROPERTIES: :CUSTOM_ID: org-export-as-ascii :END:

org-export-as-ascii-to-buffer (arg)

Export the outline as a pretty ASCII file.
If there is an active region, export only the region.
The prefix ARG specifies how many levels of the outline should become
underlined headlines, default is 3.    Lower levels will become bulleted
lists.  When HIDDEN is non-nil, don't display the ASCII buffer.
EXT-PLIST is a property list with external parameters overriding
org-mode's default settings, but still inferior to file-local
settings.  When TO-BUFFER is non-nil, create a buffer with that
name and export to that buffer.  If TO-BUFFER is the symbol
`string', don't leave any buffer behind but just return the
resulting ASCII as a string.  When BODY-ONLY is set, don't produce
the file header and footer.  When PUB-DIR is set, use this as the
publishing directory.

:PROPERTIES: :CUSTOM_ID: org-export-as-ascii-to-buffer :END:

org-export-as-docbook (&optional hidden ext-plist to-buffer body-only pub-dir)

Call `org-export-as-ascii` with output to a temporary buffer.
No file is created.  The prefix ARG is passed through to `org-export-as-ascii'.

:PROPERTIES: :CUSTOM_ID: org-export-as-docbook :END:

org-export-as-docbook-pdf (&optional hidden ext-plist to-buffer body-only pub-dir)

Export the current buffer as a DocBook file.
If there is an active region, export only the region.  When
HIDDEN is obsolete and does nothing.  EXT-PLIST is a
property list with external parameters overriding org-mode's
default settings, but still inferior to file-local settings.
When TO-BUFFER is non-nil, create a buffer with that name and
export to that buffer.  If TO-BUFFER is the symbol `string',
don't leave any buffer behind but just return the resulting HTML
as a string.  When BODY-ONLY is set, don't produce the file
header and footer, simply return the content of the document (all
top-level sections).  When PUB-DIR is set, use this as the
publishing directory.

:PROPERTIES: :CUSTOM_ID: org-export-as-docbook-pdf :END:

org-export-as-docbook-pdf-and-open

Export as DocBook XML file, and generate PDF file.

:PROPERTIES: :CUSTOM_ID: org-export-as-docbook-pdf-and-open :END:

org-export-as-docbook-to-buffer

Export as DocBook XML file, generate PDF file, and open it.

:PROPERTIES: :CUSTOM_ID: org-export-as-docbook-to-buffer :END:

org-export-as-freemind (&optional hidden ext-plist to-buffer body-only pub-dir)

Call `org-export-as-docbook' with output to a temporary buffer.
No file is created.

:PROPERTIES: :CUSTOM_ID: org-export-as-freemind :END:

org-export-as-html (arg &optional hidden ext-plist to-buffer body-only pub-dir)

Export the current buffer as a Freemind file.
If there is an active region, export only the region.  HIDDEN is
obsolete and does nothing.  EXT-PLIST is a property list with
external parameters overriding org-mode's default settings, but
still inferior to file-local settings.  When TO-BUFFER is
non-nil, create a buffer with that name and export to that
buffer.  If TO-BUFFER is the symbol `string', don't leave any
buffer behind but just return the resulting HTML as a string.
When BODY-ONLY is set, don't produce the file header and footer,
simply return the content of the document (all top level
sections).  When PUB-DIR is set, use this as the publishing
directory.

See `org-freemind-from-org-mode' for more information.

:PROPERTIES: :CUSTOM_ID: org-export-as-html :END:

org-export-as-html-and-open (arg)

Export the outline as a pretty HTML file.
If there is an active region, export only the region.  The prefix
ARG specifies how many levels of the outline should become
headlines.  The default is 3.  Lower levels will become bulleted
lists.  HIDDEN is obsolete and does nothing.
EXT-PLIST is a property list with external parameters overriding
org-mode's default settings, but still inferior to file-local
settings.  When TO-BUFFER is non-nil, create a buffer with that
name and export to that buffer.  If TO-BUFFER is the symbol
`string', don't leave any buffer behind but just return the
resulting HTML as a string.  When BODY-ONLY is set, don't produce
the file header and footer, simply return the content of
..., without even the body tags themselves.  When
PUB-DIR is set, use this as the publishing directory.

:PROPERTIES: :CUSTOM_ID: org-export-as-html-and-open :END:

org-export-as-html-to-buffer (arg)

Export the outline as HTML and immediately open it with a browser.
If there is an active region, export only the region.
The prefix ARG specifies how many levels of the outline should become
headlines.  The default is 3.  Lower levels will become bulleted lists.

:PROPERTIES: :CUSTOM_ID: org-export-as-html-to-buffer :END:

org-export-as-latex (arg &optional hidden ext-plist to-buffer body-only pub-dir)

Call `org-export-as-html` with output to a temporary buffer.
No file is created.  The prefix ARG is passed through to `org-export-as-html'.

:PROPERTIES: :CUSTOM_ID: org-export-as-latex :END:

org-export-as-latex-to-buffer (arg)

Export current buffer to a LaTeX file.
If there is an active region, export only the region.  The prefix
ARG specifies how many levels of the outline should become
headlines.  The default is 3.  Lower levels will be exported
depending on `org-export-latex-low-levels'.  The default is to
convert them as description lists.
HIDDEN is obsolete and does nothing.
EXT-PLIST is a property list with
external parameters overriding org-mode's default settings, but
still inferior to file-local settings.  When TO-BUFFER is
non-nil, create a buffer with that name and export to that
buffer.  If TO-BUFFER is the symbol `string', don't leave any
buffer behind but just return the resulting LaTeX as a string.
When BODY-ONLY is set, don't produce the file header and footer,
simply return the content of \begin{document}...\end{document},
without even the \begin{document} and \end{document} commands.
when PUB-DIR is set, use this as the publishing directory.

:PROPERTIES: :CUSTOM_ID: org-export-as-latex-to-buffer :END:

org-export-as-latin1 (&rest args)

Call `org-export-as-latex` with output to a temporary buffer.
No file is created.  The prefix ARG is passed through to `org-export-as-latex'.

:PROPERTIES: :CUSTOM_ID: org-export-as-latin1 :END:

org-export-as-latin1-to-buffer (&rest args)

Like `org-export-as-ascii', use latin1 encoding for special symbols.

:PROPERTIES: :CUSTOM_ID: org-export-as-latin1-to-buffer :END:

org-export-as-odf (latex-frag &optional odf-file)

Like `org-export-as-ascii-to-buffer', use latin1 encoding for symbols.

:PROPERTIES: :CUSTOM_ID: org-export-as-odf :END:

org-export-as-odf-and-open

Export LATEX-FRAG as OpenDocument formula file ODF-FILE.
Use `org-create-math-formula' to convert LATEX-FRAG first to
MathML.  When invoked as an interactive command, use
`org-latex-regexps' to infer LATEX-FRAG from currently active
region.  If no LaTeX fragments are found, prompt for it.  Push
MathML source to kill ring, if `org-export-copy-to-kill-ring' is
non-nil.

:PROPERTIES: :CUSTOM_ID: org-export-as-odf-and-open :END:

org-export-as-odt (arg &optional hidden ext-plist to-buffer body-only pub-dir)

Export LaTeX fragment as OpenDocument formula and immediately open it.
Use `org-export-as-odf' to read LaTeX fragment and OpenDocument
formula file.

:PROPERTIES: :CUSTOM_ID: org-export-as-odt :END:

org-export-as-odt-and-open (arg)

Export the outline as a OpenDocumentText file.
If there is an active region, export only the region.  The prefix
ARG specifies how many levels of the outline should become
headlines.  The default is 3.  Lower levels will become bulleted
lists.  HIDDEN is obsolete and does nothing.
EXT-PLIST is a property list with external parameters overriding
org-mode's default settings, but still inferior to file-local
settings.  When TO-BUFFER is non-nil, create a buffer with that
name and export to that buffer.  If TO-BUFFER is the symbol
`string', don't leave any buffer behind but just return the
resulting XML as a string.  When BODY-ONLY is set, don't produce
the file header and footer, simply return the content of
..., without even the body tags themselves.  When
PUB-DIR is set, use this as the publishing directory.

:PROPERTIES: :CUSTOM_ID: org-export-as-odt-and-open :END:

org-export-as-org (arg &optional hidden ext-plist to-buffer body-only pub-dir)

Export the outline as ODT and immediately open it with a browser.
If there is an active region, export only the region.
The prefix ARG specifies how many levels of the outline should become
headlines.  The default is 3.  Lower levels will become bulleted lists.

:PROPERTIES: :CUSTOM_ID: org-export-as-org :END:

org-export-as-pdf (arg &optional hidden ext-plist to-buffer body-only pub-dir)

Make a copy with not-exporting stuff removed.
The purpose of this function is to provide a way to export the source
Org file of a webpage in Org format, but with sensitive and/or irrelevant
stuff removed.  This command will remove the following:

- archived trees (if the variable `org-export-with-archived-trees' is nil)
- comment blocks and trees starting with the COMMENT keyword
- only trees that are consistent with `org-export-select-tags'
  and `org-export-exclude-tags'.

The only arguments that will be used are EXT-PLIST and PUB-DIR,
all the others will be ignored (but are present so that the general
mechanism to call publishing functions will work).

EXT-PLIST is a property list with external parameters overriding
org-mode's default settings, but still inferior to file-local
settings.  When PUB-DIR is set, use this as the publishing
directory.

:PROPERTIES: :CUSTOM_ID: org-export-as-pdf :END:

org-export-as-pdf-and-open (arg)

Export as LaTeX, then process through to PDF.

:PROPERTIES: :CUSTOM_ID: org-export-as-pdf-and-open :END:

org-export-as-taskjuggler

Export as LaTeX, then process through to PDF, and open.

:PROPERTIES: :CUSTOM_ID: org-export-as-taskjuggler :END:

org-export-as-taskjuggler-and-open

Export parts of the current buffer as a TaskJuggler file.
The exporter looks for a tree with tag, property or todo that
matches `org-export-taskjuggler-project-tag' and takes this as
the tasks for this project. The first node of this tree defines
the project properties such as project name and project period.
If there is a tree with tag, property or todo that matches
`org-export-taskjuggler-resource-tag' this three is taken as
resources for the project. If no resources are specified, a
default resource is created and allocated to the project. Also
the taskjuggler project will be created with default reports as
defined in `org-export-taskjuggler-default-reports'.

:PROPERTIES: :CUSTOM_ID: org-export-as-taskjuggler-and-open :END:

org-export-as-utf8 (&rest args)

Export the current buffer as a TaskJuggler file and open it
with the TaskJuggler GUI.

:PROPERTIES: :CUSTOM_ID: org-export-as-utf8 :END:

org-export-as-utf8-to-buffer (&rest args)

Like `org-export-as-ascii', use encoding for special symbols.

:PROPERTIES: :CUSTOM_ID: org-export-as-utf8-to-buffer :END:

org-export-as-xoxo (&optional buffer)

Like `org-export-as-ascii-to-buffer', use utf8 encoding for symbols.

:PROPERTIES: :CUSTOM_ID: org-export-as-xoxo :END:

org-export-blocks-preprocess

Export the org buffer as XOXO.
The XOXO buffer is named *xoxo-*

:PROPERTIES: :CUSTOM_ID: org-export-blocks-preprocess :END:

org-export-htmlize-generate-css

Export all blocks according to the `org-export-blocks' block export alist.
Does not export block types specified in specified in BLOCKS
which defaults to the value of `org-export-blocks-witheld'.

:PROPERTIES: :CUSTOM_ID: org-export-htmlize-generate-css :END:

org-export-icalendar-all-agenda-files

Create the CSS for all font definitions in the current Emacs session.
Use this to create face definitions in your CSS style file that can then
be used by code snippets transformed by htmlize.
This command just produces a buffer that contains class definitions for all
faces used in the current Emacs session.  You can copy and paste the ones you
need into your CSS file.

If you then set `org-export-htmlize-output-type' to `css', calls to
the function `org-export-htmlize-region-for-paste' will produce code
that uses these same face definitions.

:PROPERTIES: :CUSTOM_ID: org-export-icalendar-all-agenda-files :END:

org-export-icalendar-combine-agenda-files

Export all files in the variable `org-agenda-files' to iCalendar .ics files.
Each iCalendar file will be located in the same directory as the Org-mode
file, but with extension `.ics'.

:PROPERTIES: :CUSTOM_ID: org-export-icalendar-combine-agenda-files :END:

org-export-icalendar-this-file

Export all files in `org-agenda-files' to a single combined iCalendar file.
The file is stored under the name `org-combined-agenda-icalendar-file'.

:PROPERTIES: :CUSTOM_ID: org-export-icalendar-this-file :END:

org-export-odt-convert (&optional in-file out-fmt prefix-arg)

Export current file as an iCalendar file.
The iCalendar file will be located in the same directory as the Org-mode
file, but with extension `.ics'.

:PROPERTIES: :CUSTOM_ID: org-export-odt-convert :END:

org-export-preprocess-string (string &rest parameters)

Convert IN-FILE to format OUT-FMT using a command line converter.
IN-FILE is the file to be converted.  If unspecified, it defaults
to variable `buffer-file-name'.  OUT-FMT is the desired output
format.  Use `org-export-odt-convert-process' as the converter.
If PREFIX-ARG is non-nil then the newly converted file is opened
using `org-open-file'.

:PROPERTIES: :CUSTOM_ID: org-export-preprocess-string :END:

org-export-region-as-ascii (beg end &optional body-only buffer)

Cleanup STRING so that the true exported has a more consistent source.
This function takes STRING, which should be a buffer-string of an org-file
to export.  It then creates a temporary buffer where it does its job.
The result is then again returned as a string, and the exporter works
on this string to produce the exported version.

:PROPERTIES: :CUSTOM_ID: org-export-region-as-ascii :END:

org-export-region-as-docbook (beg end &optional body-only buffer)

Convert region from BEG to END in org-mode buffer to plain ASCII.
If prefix arg BODY-ONLY is set, omit file header, footer, and table of
contents, and only produce the region of converted text, useful for
cut-and-paste operations.
If BUFFER is a buffer or a string, use/create that buffer as a target
of the converted ASCII.  If BUFFER is the symbol `string', return the
produced ASCII as a string and leave not buffer behind.  For example,
a Lisp program could call this function in the following way:

  (setq ascii (org-export-region-as-ascii beg end t 'string))

When called interactively, the output buffer is selected, and shown
in a window.  A non-interactive call will only return the buffer.

:PROPERTIES: :CUSTOM_ID: org-export-region-as-docbook :END:

org-export-region-as-html (beg end &optional body-only buffer)

Convert region from BEG to END in `org-mode' buffer to DocBook.
If prefix arg BODY-ONLY is set, omit file header and footer and
only produce the region of converted text, useful for
cut-and-paste operations.  If BUFFER is a buffer or a string,
use/create that buffer as a target of the converted DocBook.  If
BUFFER is the symbol `string', return the produced DocBook as a
string and leave not buffer behind.  For example, a Lisp program
could call this function in the following way:

  (setq docbook (org-export-region-as-docbook beg end t 'string))

When called interactively, the output buffer is selected, and shown
in a window.  A non-interactive call will only return the buffer.

:PROPERTIES: :CUSTOM_ID: org-export-region-as-html :END:

org-export-region-as-latex (beg end &optional body-only buffer)

Convert region from BEG to END in org-mode buffer to HTML.
If prefix arg BODY-ONLY is set, omit file header, footer, and table of
contents, and only produce the region of converted text, useful for
cut-and-paste operations.
If BUFFER is a buffer or a string, use/create that buffer as a target
of the converted HTML.  If BUFFER is the symbol `string', return the
produced HTML as a string and leave not buffer behind.  For example,
a Lisp program could call this function in the following way:

  (setq html (org-export-region-as-html beg end t 'string))

When called interactively, the output buffer is selected, and shown
in a window.  A non-interactive call will only return the buffer.

:PROPERTIES: :CUSTOM_ID: org-export-region-as-latex :END:

org-export-res/src-name-cleanup

Convert region from BEG to END in `org-mode' buffer to LaTeX.
If prefix arg BODY-ONLY is set, omit file header, footer, and table of
contents, and only produce the region of converted text, useful for
cut-and-paste operations.
If BUFFER is a buffer or a string, use/create that buffer as a target
of the converted LaTeX.  If BUFFER is the symbol `string', return the
produced LaTeX as a string and leave no buffer behind.  For example,
a Lisp program could call this function in the following way:

  (setq latex (org-export-region-as-latex beg end t 'string))

When called interactively, the output buffer is selected, and shown
in a window.  A non-interactive call will only return the buffer.

:PROPERTIES: :CUSTOM_ID: org-export-res/src-name-cleanup :END:

org-export-visible (type arg)

Clean up #+results and #+name lines for export.
This function should only be called after all block processing
has taken place.

:PROPERTIES: :CUSTOM_ID: org-export-visible :END:

org-feed-goto-inbox (feed)

Create a copy of the visible part of the current buffer, and export it.
The copy is created in a temporary buffer and removed after use.
TYPE is the final key (as a string) that also selects the export command in
the C-c C-e export dispatcher.
As a special case, if the you type SPC at the prompt, the temporary
org-mode file will not be removed but presented to you so that you can
continue to use it.  The prefix arg ARG is passed through to the exporting
command.

:PROPERTIES: :CUSTOM_ID: org-feed-goto-inbox :END:

org-feed-show-raw-feed (feed)

Go to the inbox that captures the feed named FEED.

:PROPERTIES: :CUSTOM_ID: org-feed-show-raw-feed :END:

org-feed-update (feed &optional retrieve-only)

Show the raw feed buffer of a feed.

:PROPERTIES: :CUSTOM_ID: org-feed-update :END:

org-feed-update-all

Get inbox items from FEED.
FEED can be a string with an association in `org-feed-alist', or
it can be a list structured like an entry in `org-feed-alist'.

:PROPERTIES: :CUSTOM_ID: org-feed-update-all :END:

org-find-entry-with-id (ident)

Get inbox items from all feeds in `org-feed-alist'.

:PROPERTIES: :CUSTOM_ID: org-find-entry-with-id :END:

org-find-file-at-mouse (ev)

Locate the entry that contains the ID property with exact value IDENT.
IDENT can be a string, a symbol or a number, this function will search for
the string representation of it.
Return the position where this entry starts, or nil if there is no such entry.

:PROPERTIES: :CUSTOM_ID: org-find-file-at-mouse :END:

org-first-sibling-p

Open file link or URL at mouse.

:PROPERTIES: :CUSTOM_ID: org-first-sibling-p :END:

org-footnote-action (&optional special)

Is this heading the first child of its parents?

:PROPERTIES: :CUSTOM_ID: org-footnote-action :END:

org-footnote-create-definition (label)

Do the right thing for footnotes.

When at a footnote reference, jump to the definition.

When at a definition, jump to the references if they exist, offer
to create them otherwise.

When neither at definition or reference, create a new footnote,
interactively.

With prefix arg SPECIAL, offer additional commands in a menu.

:PROPERTIES: :CUSTOM_ID: org-footnote-create-definition :END:

org-footnote-goto-definition (label)

Start the definition of a footnote with label LABEL.

:PROPERTIES: :CUSTOM_ID: org-footnote-goto-definition :END:

org-footnote-goto-previous-reference (label)

Move point to the definition of the footnote LABEL.
Return a non-nil value when a definition has been found.

:PROPERTIES: :CUSTOM_ID: org-footnote-goto-previous-reference :END:

org-footnote-new

Find the first closest (to point) reference of footnote with label LABEL.

:PROPERTIES: :CUSTOM_ID: org-footnote-new :END:

org-footnote-renumber-fn:N

Insert a new footnote.
This command prompts for a label.  If this is a label referencing an
existing label, only insert the label.  If the footnote label is empty
or new, let the user edit the definition of the footnote.

:PROPERTIES: :CUSTOM_ID: org-footnote-renumber-fn:N :END:

org-force-cycle-archived

Renumber the simple footnotes like fn:17 into a sequence in the document.

:PROPERTIES: :CUSTOM_ID: org-force-cycle-archived :END:

org-force-self-insert (N)

Cycle subtree even if it is archived.

:PROPERTIES: :CUSTOM_ID: org-force-self-insert :END:

org-forward-same-level (arg &optional invisible-ok)

Needed to enforce self-insert under remapping.

:PROPERTIES: :CUSTOM_ID: org-forward-same-level :END:

org-forward-sentence (&optional arg)

Move forward to the arg'th subheading at same level as this one.
Stop at the first and last subheadings of a superior heading.
Normally this only looks at visible headings, but when INVISIBLE-OK is non-nil
it wil also look at invisible ones.

:PROPERTIES: :CUSTOM_ID: org-forward-sentence :END:

org-freemind-from-org-mode (org-file mm-file)

Go to end of sentence, or end of table field.
This will call `forward-sentence' or `org-table-end-of-field',
depending on context.

:PROPERTIES: :CUSTOM_ID: org-freemind-from-org-mode :END:

org-freemind-from-org-mode-node (node-line mm-file)

Convert the `org-mode' file ORG-FILE to the FreeMind file MM-FILE.
All the nodes will be opened or closed in Freemind just as you
have them in `org-mode'.

Note that exporting to Freemind also gives you an alternative way
to export from `org-mode' to html.  You can create a dynamic html
version of the your org file, by first exporting to Freemind and
then exporting from Freemind to html.  The 'As
XHTML (JavaScript)' version in Freemind works very well (and you
can use a CSS stylesheet to style it).

:PROPERTIES: :CUSTOM_ID: org-freemind-from-org-mode-node :END:

org-freemind-from-org-sparse-tree (org-buffer mm-file)

Convert node at line NODE-LINE to the FreeMind file MM-FILE.
See `org-freemind-from-org-mode' for more information.

:PROPERTIES: :CUSTOM_ID: org-freemind-from-org-sparse-tree :END:

org-freemind-show (mm-file)

Convert visible part of buffer ORG-BUFFER to FreeMind file MM-FILE.

:PROPERTIES: :CUSTOM_ID: org-freemind-show :END:

org-freemind-to-org-mode (mm-file org-file)

Show file MM-FILE in Freemind.

:PROPERTIES: :CUSTOM_ID: org-freemind-to-org-mode :END:

org-get-tags-at (&optional pos local)

Convert FreeMind file MM-FILE to `org-mode' file ORG-FILE.

:PROPERTIES: :CUSTOM_ID: org-get-tags-at :END:

org-global-cycle (&optional arg)

Get a list of all headline tags applicable at POS.
POS defaults to point.  If tags are inherited, the list contains
the targets in the same sequence as the headlines appear, i.e.
the tags of the current headline come last.
When LOCAL is non-nil, only return tags from the current headline,
ignore inherited ones.

:PROPERTIES: :CUSTOM_ID: org-global-cycle :END:

org-go-to-remember-target (&optional template-key)

Cycle the global visibility.  For details see `org-cycle'.
With C-u prefix arg, switch to startup visibility.
With a numeric prefix, show all headlines up to that level.

:PROPERTIES: :CUSTOM_ID: org-go-to-remember-target :END:

org-goto (&optional alternative-interface)

Go to the target location of a remember template.
The user is queried for the template.

:PROPERTIES: :CUSTOM_ID: org-goto :END:

org-goto-calendar (&optional arg)

Look up a different location in the current file, keeping current visibility.

When you want look-up or go to a different location in a
document, the fastest way is often to fold the entire buffer and
then dive into the tree.  This method has the disadvantage, that
the previous location will be folded, which may not be what you
want.

This command works around this by showing a copy of the current
buffer in an indirect buffer, in overview mode.  You can dive
into the tree in that copy, use org-occur and incremental search
to find a location.  When pressing RET or `Q', the command
returns to the original buffer in which the visibility is still
unchanged.  After RET it will also jump to the location selected
in the indirect buffer and expose the headline hierarchy above.

With a prefix argument, use the alternative interface: e.g. if
`org-goto-interface' is 'outline use 'outline-path-completion.

:PROPERTIES: :CUSTOM_ID: org-goto-calendar :END:

org-goto-left

Go to the Emacs calendar at the current date.
If there is a time stamp in the current line, go to that date.
A prefix ARG can be used to force the current date.

:PROPERTIES: :CUSTOM_ID: org-goto-left :END:

org-goto-local-auto-isearch

Finish `org-goto' by going to the new location.

:PROPERTIES: :CUSTOM_ID: org-goto-local-auto-isearch :END:

org-goto-quit

Start isearch.

:PROPERTIES: :CUSTOM_ID: org-goto-quit :END:

org-goto-ret (&optional arg)

Finish `org-goto' without cursor motion.

:PROPERTIES: :CUSTOM_ID: org-goto-ret :END:

org-goto-right

Finish `org-goto' by going to the new location.

:PROPERTIES: :CUSTOM_ID: org-goto-right :END:

org-habit-toggle-habits

Finish `org-goto' by going to the new location.

:PROPERTIES: :CUSTOM_ID: org-habit-toggle-habits :END:

org-hide-block-all

Toggle display of habits in an agenda buffer.

:PROPERTIES: :CUSTOM_ID: org-hide-block-all :END:

org-hide-block-toggle (&optional force)

Fold all blocks in the current buffer.

:PROPERTIES: :CUSTOM_ID: org-hide-block-toggle :END:

org-hide-block-toggle-maybe

Toggle the visibility of the current block.

:PROPERTIES: :CUSTOM_ID: org-hide-block-toggle-maybe :END:

org-id-copy

Toggle visibility of block at point.

:PROPERTIES: :CUSTOM_ID: org-id-copy :END:

org-id-get-create (&optional force)

Copy the ID of the entry at point to the kill ring.
Create an ID if necessary.

:PROPERTIES: :CUSTOM_ID: org-id-get-create :END:

org-id-goto (id)

Create an ID for the current entry and return it.
If the entry already has an ID, just return it.
With optional argument FORCE, force the creation of a new ID.

:PROPERTIES: :CUSTOM_ID: org-id-goto :END:

Switch to the buffer containing the entry with id ID.
Move the cursor to that entry in that buffer.

:PROPERTIES: :CUSTOM_ID: org-id-store-link :END:

org-id-update-id-locations (&optional files silent)

Store a link to the current entry, using its ID.

:PROPERTIES: :CUSTOM_ID: org-id-update-id-locations :END:

org-ido-switchb (&optional arg)

Scan relevant files for IDs.
Store the relation between files and corresponding IDs.
This will scan all agenda files, all associated archives, and all
files currently mentioned in `org-id-locations'.
When FILES is given, scan these files instead.
When CHECK is given, prepare detailed information about duplicate IDs.

:PROPERTIES: :CUSTOM_ID: org-ido-switchb :END:

org-indent-block

Switch between Org buffers.
With one prefix argument, restrict available buffers to files.
With two prefix arguments, restrict available buffers to agenda files.

Defaults to `iswitchb' for buffer name completion.
Set `org-completion-use-ido' to make it use ido instead.

:PROPERTIES: :CUSTOM_ID: org-indent-block :END:

org-indent-drawer

Indent the block at point.

:PROPERTIES: :CUSTOM_ID: org-indent-drawer :END:

org-indent-indent-buffer

Indent the drawer at point.

:PROPERTIES: :CUSTOM_ID: org-indent-indent-buffer :END:

org-indent-item

Add indentation properties to the accessible part of the buffer.

:PROPERTIES: :CUSTOM_ID: org-indent-item :END:

org-indent-item-tree

Indent a local list item, but not its children.
If a region is active, all items inside will be moved.

:PROPERTIES: :CUSTOM_ID: org-indent-item-tree :END:

org-indent-line

Indent a local list item including its children.
If a region is active, all items inside will be moved.

:PROPERTIES: :CUSTOM_ID: org-indent-line :END:

org-indent-mode (&optional arg)

Indent line depending on context.

:PROPERTIES: :CUSTOM_ID: org-indent-mode :END:

org-indent-region (start end)

When active, indent text according to outline structure.

Internally this works by adding `line-prefix' and `wrap-prefix'
properties, after each buffer modification, on the modified zone.

The process is synchronous.  Though, initial indentation of
buffer, which can take a few seconds on large buffers, is done
during idle time.

:PROPERTIES: :CUSTOM_ID: org-indent-region :END:

org-info (&optional node)

Indent region.

:PROPERTIES: :CUSTOM_ID: org-info :END:

org-inlinetask-demote

Read documentation for Org-mode in the info system.
With optional NODE, go directly to that node.

:PROPERTIES: :CUSTOM_ID: org-inlinetask-demote :END:

org-inlinetask-insert-task (&optional no-state)

Demote the inline task at point.
If the task has an end part, also demote it.

:PROPERTIES: :CUSTOM_ID: org-inlinetask-insert-task :END:

org-inlinetask-promote

Insert an inline task.
If prefix arg NO-STATE is set, ignore `org-inlinetask-default-state'.

:PROPERTIES: :CUSTOM_ID: org-inlinetask-promote :END:

org-insert-beamer-options-template (&optional kind)

Promote the inline task at point.
If the task has an end part, promote it.  Also, prevents level from
going below `org-inlinetask-min-level'.

:PROPERTIES: :CUSTOM_ID: org-insert-beamer-options-template :END:

org-insert-columns-dblock

Insert a settings template, to make sure users do this right.

:PROPERTIES: :CUSTOM_ID: org-insert-columns-dblock :END:

org-insert-drawer (&optional arg drawer)

Create a dynamic block capturing a column view table.

:PROPERTIES: :CUSTOM_ID: org-insert-drawer :END:

org-insert-export-options-template

Insert a drawer at point.

Optional argument DRAWER, when non-nil, is a string representing
drawer's name.  Otherwise, the user is prompted for a name.

If a region is active, insert the drawer around that region
instead.

Point is left between drawer's boundaries.

:PROPERTIES: :CUSTOM_ID: org-insert-export-options-template :END:

org-insert-heading (&optional force-heading invisible-ok)

Insert into the buffer a template with information for exporting.

:PROPERTIES: :CUSTOM_ID: org-insert-heading :END:

org-insert-heading-after-current

Insert a new heading or item with same depth at point.
If point is in a plain list and FORCE-HEADING is nil, create a new list item.
If point is at the beginning of a headline, insert a sibling before the
current headline.  If point is not at the beginning, split the line,
create the new headline with the text in the current line after point
(but see also the variable `org-M-RET-may-split-line').

When INVISIBLE-OK is set, stop at invisible headlines when going back.
This is important for non-interactive uses of the command.

:PROPERTIES: :CUSTOM_ID: org-insert-heading-after-current :END:

org-insert-heading-respect-content

Insert a new heading with same level as current, after current subtree.

:PROPERTIES: :CUSTOM_ID: org-insert-heading-respect-content :END:

:PROPERTIES: :CUSTOM_ID: org-insert-link :END:

Insert a link.  At the prompt, enter the link.

Completion can be used to insert any of the link protocol prefixes like
http or ftp in use.

The history can be used to select a link previously stored with
`org-store-link'.  When the empty string is entered (i.e. if you just
press RET at the prompt), the link defaults to the most recently
stored link.  As SPC triggers completion in the minibuffer, you need to
use M-SPC or C-q SPC to force the insertion of a space character.

You will also be prompted for a description, and if one is given, it will
be displayed in the buffer instead of the link.

If there is already a link at point, this command will allow you to edit link
and description parts.

With a C-u prefix, prompts for a file to link to.  The file name can
be selected using completion.  The path to the file will be relative to the
current directory if the file is in the current directory or a subdirectory.
Otherwise, the link will be the absolute path as completed in the minibuffer
(i.e. normally ~/path/to/file).  You can configure this behavior using the
option `org-link-file-path-type'.

With two C-u prefixes, enforce an absolute path even if the file is in
the current directory or below.

With three C-u prefixes, negate the meaning of
`org-keep-stored-link-after-insertion'.

If `org-make-link-description-function' is non-nil, this function will be
called with the link target, and the result will be the default
link description.

If the LINK-LOCATION parameter is non-nil, this value will be
used as the link location instead of reading one interactively.

If the DEFAULT-DESCRIPTION parameter is non-nil, this value will
be used as the default description.

:PROPERTIES: :CUSTOM_ID: org-insert-link-global :END:

org-insert-subheading (arg)

Insert a link like Org-mode does.
This command can be called in any mode to insert a link in Org-mode syntax.

:PROPERTIES: :CUSTOM_ID: org-insert-subheading :END:

org-insert-todo-heading (arg &optional force-heading)

Insert a new subheading and demote it.
Works for outline headings and for plain lists alike.

:PROPERTIES: :CUSTOM_ID: org-insert-todo-heading :END:

org-insert-todo-heading-respect-content (&optional force-state)

Insert a new heading with the same level and TODO state as current heading.
If the heading has no TODO state, or if the state is DONE, use the first
state (TODO by default).  Also with prefix arg, force first state.

:PROPERTIES: :CUSTOM_ID: org-insert-todo-heading-respect-content :END:

org-insert-todo-subheading (arg)

:PROPERTIES: :CUSTOM_ID: org-insert-todo-subheading :END:

org-iswitchb (&optional arg)

Insert a new subheading with TODO keyword or checkbox and demote it.
Works for outline headings and for plain lists alike.

:PROPERTIES: :CUSTOM_ID: org-iswitchb :END:

org-kill-line (&optional arg)

Switch between Org buffers.
With one prefix argument, restrict available buffers to files.
With two prefix arguments, restrict available buffers to agenda files.

Defaults to `iswitchb' for buffer name completion.
Set `org-completion-use-ido' to make it use ido instead.

:PROPERTIES: :CUSTOM_ID: org-kill-line :END:

org-kill-note-or-show-branches

Kill line, to tags or end of line.

:PROPERTIES: :CUSTOM_ID: org-kill-note-or-show-branches :END:

org-list-insert-radio-list

If this is a Note buffer, abort storing the note.  Else call `show-branches'.

:PROPERTIES: :CUSTOM_ID: org-list-insert-radio-list :END:

org-list-make-subtree

Insert a radio list template appropriate for this major mode.

:PROPERTIES: :CUSTOM_ID: org-list-make-subtree :END:

org-list-repair

Convert the plain list at point into a subtree.

:PROPERTIES: :CUSTOM_ID: org-list-repair :END:

org-list-send-list (&optional maybe)

Fix indentation, bullets and checkboxes is the list at point.

:PROPERTIES: :CUSTOM_ID: org-list-send-list :END:

org-list-to-generic (list params)

Send a transformed version of this list to the receiver position.
With argument MAYBE, fail quietly if no transformation is defined
for this list.

:PROPERTIES: :CUSTOM_ID: org-list-to-generic :END:

Convert a LIST parsed through `org-list-parse-list' to other formats.
Valid parameters PARAMS are:

:ustart	    String to start an unordered list
:uend	    String to end an unordered list

:ostart	    String to start an ordered list
:oend	    String to end an ordered list

:dstart	    String to start a descriptive list
:dend	    String to end a descriptive list
:dtstart    String to start a descriptive term
:dtend	    String to end a descriptive term
:ddstart    String to start a description
:ddend	    String to end a description

:splice	    When set to t, return only list body lines, don't wrap
	    them into :[u/o]start and :[u/o]end.  Default is nil.

:istart	    String to start a list item.
:icount     String to start an item with a counter.
:iend	    String to end a list item
:isep	    String to separate items
:lsep	    String to separate sublists
:csep	    String to separate text from a sub-list

:cboff      String to insert for an unchecked check-box
:cbon       String to insert for a checked check-box
:cbtrans    String to insert for a check-box in transitional state

:nobr       Non-nil means remove line breaks in lists items.

Alternatively, each parameter can also be a form returning
a string.  These sexp can use keywords `counter' and `depth',
representing respectively counter associated to the current
item, and depth of the current sub-list, starting at 0.
Obviously, `counter' is only available for parameters applying to
items.

:PROPERTIES: :CUSTOM_ID: org-mac-message-get-links :END:

org-mac-message-insert-flagged (org-buffer org-heading)

Create links to the messages currently selected or flagged in Mail.app.
This will use AppleScript to get the message-id and the subject of the
messages in Mail.app and make a link out of it.
When SELECT-OR-FLAG is "s", get the selected messages (this is also
the default).  When SELECT-OR-FLAG is "f", get the flagged messages.
The Org-syntax text will be pushed to the kill ring, and also returned.

:PROPERTIES: :CUSTOM_ID: org-mac-message-insert-flagged :END:

Asks for an org buffer and a heading within it, and replace message links.
If heading exists, delete all message:// links within heading's first
level.  If heading doesn't exist, create it at point-max.  Insert
list of message:// links to flagged mail after heading.

:PROPERTIES: :CUSTOM_ID: org-mac-message-insert-link :END:

org-mac-message-insert-selected

Insert a link to the messages currently selected in Mail.app.
This will use AppleScript to get the message-id and the subject of the
active mail in Mail.app and make a link out of it.

:PROPERTIES: :CUSTOM_ID: org-mac-message-insert-selected :END:

org-make-org-heading-search-string (&optional string heading)

Insert a link to the messages currently selected in Mail.app.
This will use AppleScript to get the message-id and the subject of the
active mail in Mail.app and make a link out of it.

:PROPERTIES: :CUSTOM_ID: org-make-org-heading-search-string :END:

org-mark-entry-for-agenda-action

Make search string for STRING or current headline.

:PROPERTIES: :CUSTOM_ID: org-mark-entry-for-agenda-action :END:

org-mark-list

Mark the current entry as target of an agenda action.
Agenda actions are actions executed from the agenda with the key `k',
which make use of the date at the cursor.

:PROPERTIES: :CUSTOM_ID: org-mark-list :END:

org-mark-ring-goto (&optional n)

Mark the current list.
If this is a sublist, only mark the sublist.

:PROPERTIES: :CUSTOM_ID: org-mark-ring-goto :END:

org-mark-ring-push (&optional pos buffer)

Jump to the previous position in the mark ring.
With prefix arg N, jump back that many stored positions.  When
called several times in succession, walk through the entire ring.
Org-mode commands jumping to a different position in the current file,
or to another Org-mode file, automatically push the old position
onto the ring.

:PROPERTIES: :CUSTOM_ID: org-mark-ring-push :END:

org-mark-subtree

Put the current position or POS into the mark ring and rotate it.

:PROPERTIES: :CUSTOM_ID: org-mark-subtree :END:

org-match-sparse-tree (&optional todo-only match)

Mark the current subtree.
This puts point at the start of the current subtree, and mark at the end.

If point is in an inline task, mark that task instead.

:PROPERTIES: :CUSTOM_ID: org-match-sparse-tree :END:

org-meta-return (&optional arg)

Create a sparse tree according to tags string MATCH.
MATCH can contain positive and negative selection of tags, like
"+WORK+URGENT-WITHBOSS".
If optional argument TODO-ONLY is non-nil, only select lines that are
also TODO lines.

:PROPERTIES: :CUSTOM_ID: org-meta-return :END:

org-metadown (&optional arg)

Insert a new heading or wrap a region in a table.
Calls `org-insert-heading' or `org-table-wrap-region', depending on context.
See the individual commands for more information.

:PROPERTIES: :CUSTOM_ID: org-metadown :END:

org-metaleft (&optional arg)

Move subtree down or move table row down.
Calls `org-move-subtree-down' or `org-table-move-row' or
`org-move-item-down', depending on context.  See the individual
commands for more information.

:PROPERTIES: :CUSTOM_ID: org-metaleft :END:

  • Access: <M-left>, <menu-bar> <Org> <Edit Structure> <Promote Heading>, <menu-bar> <Tbl> <Column> <Move Column Left>
  • In file: org.el
  • Search modifications

org-metaright (&optional arg)

Promote heading or move table column to left.
Calls `org-do-promote' or `org-table-move-column', depending on context.
With no specific context, calls the Emacs default `backward-word'.
See the individual commands for more information.

:PROPERTIES: :CUSTOM_ID: org-metaright :END:

  • Access: <M-right>, <menu-bar> <Org> <Edit Structure> <Demote Heading>, <menu-bar> <Tbl> <Column> <Move Column Right>
  • In file: org.el
  • Search modifications

org-metaup (&optional arg)

Demote a subtree, a list item or move table column to right.
In front of a drawer or a block keyword, indent it correctly.
With no specific context, calls the Emacs default `forward-word'.
See the individual commands for more information.

:PROPERTIES: :CUSTOM_ID: org-metaup :END:

org-mobile-apply (&optional beg end)

Move subtree up or move table row up.
Calls `org-move-subtree-up' or `org-table-move-row' or
`org-move-item-up', depending on context.  See the individual commands
for more information.

:PROPERTIES: :CUSTOM_ID: org-mobile-apply :END:

org-mobile-create-sumo-agenda

Apply all change requests in the current buffer.
If BEG and END are given, only do this in that region.

:PROPERTIES: :CUSTOM_ID: org-mobile-create-sumo-agenda :END:

org-mobile-move-capture

Create a file that contains all custom agenda views.

:PROPERTIES: :CUSTOM_ID: org-mobile-move-capture :END:

org-mobile-pull

Move the contents of the capture file to the inbox file.
Return a marker to the location where the new content has been added.
If nothing new has been added, return nil.

:PROPERTIES: :CUSTOM_ID: org-mobile-pull :END:

org-mobile-push

Pull the contents of `org-mobile-capture-file' and integrate them.
Apply all flagged actions, flag entries to be flagged and then call an
agenda view showing the flagged items.

:PROPERTIES: :CUSTOM_ID: org-mobile-push :END:

org-mode

Push the current state of Org affairs to the WebDAV directory.
This will create the index file, copy all agenda files there, and also
create all custom agenda views, for upload to the mobile phone.

:PROPERTIES: :CUSTOM_ID: org-mode :END:

org-mode-restart

Outline-based notes management and organizer, alias
"Carsten's outline-mode for keeping track of everything."

Org-mode develops organizational tasks around a NOTES file which
contains information about projects as plain text.  Org-mode is
implemented on top of outline-mode, which is ideal to keep the content
of large files well structured.  It supports ToDo items, deadlines and
time stamps, which magically appear in the diary listing of the Emacs
calendar.  Tables are easily created with a built-in table editor.
Plain text URL-like links connect to websites, emails (VM), Usenet
messages (Gnus), BBDB entries, and any files related to the project.
For printing and sharing of notes, an Org-mode file (or a part of it)
can be exported as a structured ASCII or HTML file.

The following commands are available:

key             binding
---             -------

C-a		org-beginning-of-line
C-c		Prefix Command
C-e		org-end-of-line
TAB		org-cycle
C-j		org-return-indent
C-k		org-kill-line
RET		org-return
C-y		org-yank
ESC		Prefix Command
|		org-force-self-insert
C-#		org-table-rotate-recalc-marks
C-'		org-cycle-agenda-files
C-,		org-cycle-agenda-files
	org-shiftcontroldown
	org-shiftcontrolleft
	org-insert-todo-heading-respect-content
	org-shiftcontrolright
	org-shiftcontrolup
	org-insert-heading-respect-content
		org-force-cycle-archived
	org-shiftmetadown
	org-shiftmetaleft
	org-insert-todo-heading
	org-shiftmetaright
	org-shiftmetaup
	org-metadown
	org-metaleft
	org-meta-return
	org-metaright
		org-metaup
	org-shiftdown
			org-shifttab
	org-shiftleft
	org-mouse-yank-link
	org-table-copy-down
	org-shiftright
		org-shifttab
		org-shiftup
	org-shifttab
	org-mouse-down-mouse
	org-mouse-yank-link
	org-mouse-show-context-menu
		Prefix Command
		org-cycle

M-TAB		pcomplete
M-RET		org-insert-heading
M-J		org-insert-todo-subheading
M-a		org-backward-sentence
M-e		org-forward-sentence
M-j		org-insert-subheading

C-c C-@		org-mark-list
C-c C-a		org-attach
C-c C-b		org-backward-same-level
C-c C-c		org-ctrl-c-ctrl-c
C-c C-d		org-deadline
C-c C-e		org-export
C-c C-f		org-forward-same-level
C-c C-j		org-goto
C-c C-k		org-kill-note-or-show-branches
C-c C-l		org-insert-link
C-c RET		org-ctrl-c-ret
C-c C-o		org-open-at-point
C-c C-q		org-set-tags-command
C-c C-r		org-reveal
C-c C-s		org-schedule
C-c C-t		org-todo
C-c C-v		Prefix Command
C-c C-w		org-refile
C-c C-x		Prefix Command
C-c C-y		org-evaluate-time-range
C-c C-z		org-add-note
C-c SPC		org-table-blank-field
C-c !		org-time-stamp-inactive
C-c #		org-update-statistics-cookies
C-c $		org-archive-subtree
C-c %		org-mark-ring-push
C-c &		org-mark-ring-goto
C-c '		org-edit-special
C-c *		org-ctrl-c-star
C-c +		org-table-sum
C-c ,		org-priority
C-c -		org-ctrl-c-minus
C-c .		org-time-stamp
C-c /		org-sparse-tree
C-c :		org-toggle-fixed-width-section
C-c ;		org-toggle-comment
C-c <		org-date-from-calendar
C-c =		org-table-eval-formula
C-c >		org-goto-calendar
C-c ?		org-table-field-info
C-c @		org-mark-subtree
C-c [		org-agenda-file-to-front
C-c \		org-match-sparse-tree
C-c ]		org-remove-file
C-c ^		org-sort
C-c `		org-table-edit-field
C-c {		org-table-toggle-formula-debugger
C-c |		org-table-create-or-convert-from-region
C-c }		org-table-toggle-coordinate-overlays
C-c ~		org-table-create-with-table.el
C-c C-*		org-list-make-subtree

 	org-delete-backward-char
 		org-delete-char
 
				org-backward-same-level
 	org-demote-subtree
 
				org-forward-same-level
 
				org-ctrl-c-ret
 	org-mark-subtree
 	org-promote-subtree
 	org-self-insert-command
 		org-kill-note-or-show-branches
 		org-show-subtree

C-c C-a		show-all
  (that binding is currently shadowed by another mode)
C-c C-b		outline-backward-same-level
  (that binding is currently shadowed by another mode)
C-c C-c		hide-entry
  (that binding is currently shadowed by another mode)
C-c C-d		hide-subtree
  (that binding is currently shadowed by another mode)
C-c C-e		show-entry
  (that binding is currently shadowed by another mode)
C-c C-f		outline-forward-same-level
  (that binding is currently shadowed by another mode)
C-c TAB		show-children
C-c C-k		show-branches
  (that binding is currently shadowed by another mode)
C-c C-l		hide-leaves
  (that binding is currently shadowed by another mode)
C-c RET		outline-insert-heading
  (that binding is currently shadowed by another mode)
C-c C-n		outline-next-visible-heading
C-c C-o		hide-other
  (that binding is currently shadowed by another mode)
C-c C-p		outline-previous-visible-heading
C-c C-q		hide-sublevels
  (that binding is currently shadowed by another mode)
C-c C-s		show-subtree
  (that binding is currently shadowed by another mode)
C-c C-t		hide-body
  (that binding is currently shadowed by another mode)
C-c C-u		outline-up-heading
C-c C-v		outline-move-subtree-down
  (that binding is currently shadowed by another mode)
C-c C-^		outline-move-subtree-up
C-c @		outline-mark-subtree
  (that binding is currently shadowed by another mode)
C-c C-<		outline-promote
C-c C->		outline-demote

M-TAB		ispell-complete-word
  (that binding is currently shadowed by another mode)

C-c C-v C-a	org-babel-sha1-hash
C-c C-v C-b	org-babel-execute-buffer
C-c C-v C-c	org-babel-check-src-block
C-c C-v C-d	org-babel-demarcate-block
C-c C-v C-e	org-babel-execute-maybe
C-c C-v C-f	org-babel-tangle-file
C-c C-v TAB	org-babel-view-src-block-info
C-c C-v C-j	org-babel-insert-header-arg
C-c C-v C-l	org-babel-load-in-session
C-c C-v C-n	org-babel-next-src-block
C-c C-v C-o	org-babel-open-src-block-result
C-c C-v C-p	org-babel-previous-src-block
C-c C-v C-r	org-babel-goto-named-result
C-c C-v C-s	org-babel-execute-subtree
C-c C-v C-t	org-babel-tangle
C-c C-v C-u	org-babel-goto-src-block-head
C-c C-v C-v	org-babel-expand-src-block
C-c C-v C-x	org-babel-do-key-sequence-in-edit-buffer
C-c C-v C-z	org-babel-switch-to-session
C-c C-v ESC	Prefix Command
C-c C-v I	org-babel-view-src-block-info
C-c C-v a	org-babel-sha1-hash
C-c C-v b	org-babel-execute-buffer
C-c C-v c	org-babel-check-src-block
C-c C-v d	org-babel-demarcate-block
C-c C-v e	org-babel-execute-maybe
C-c C-v f	org-babel-tangle-file
C-c C-v g	org-babel-goto-named-src-block
C-c C-v h	org-babel-describe-bindings
C-c C-v i	org-babel-lob-ingest
C-c C-v j	org-babel-insert-header-arg
C-c C-v l	org-babel-load-in-session
C-c C-v n	org-babel-next-src-block
C-c C-v o	org-babel-open-src-block-result
C-c C-v p	org-babel-previous-src-block
C-c C-v r	org-babel-goto-named-result
C-c C-v s	org-babel-execute-subtree
C-c C-v t	org-babel-tangle
C-c C-v u	org-babel-goto-src-block-head
C-c C-v v	org-babel-expand-src-block
C-c C-v x	org-babel-do-key-sequence-in-edit-buffer
C-c C-v z	org-babel-switch-to-session-with-code

C-c C-x C-a	org-archive-subtree-default
C-c C-x C-b	org-toggle-checkbox
C-c C-x C-c	org-columns
C-c C-x C-d	org-clock-display
C-c C-x C-f	org-emphasize
C-c C-x TAB	org-clock-in
C-c C-x C-j	org-clock-goto
C-c C-x C-k	org-mark-entry-for-agenda-action
C-c C-x C-l	org-preview-latex-fragment
C-c C-x RET	Prefix Command
C-c C-x C-n	org-next-link
C-c C-x C-o	org-clock-out
C-c C-x C-p	org-previous-link
C-c C-x C-q	org-clock-cancel
C-c C-x C-r	org-clock-report
C-c C-x C-s	org-advertized-archive-subtree
C-c C-x C-t	org-toggle-time-stamp-overlays
C-c C-x C-u	org-dblock-update
C-c C-x C-v	org-toggle-inline-images
C-c C-x C-w	org-cut-special
C-c C-x C-x	org-clock-in-last
C-c C-x C-y	org-paste-special
C-c C-x ESC	Prefix Command
C-c C-x !	org-reload
C-c C-x ,	org-timer-pause-or-continue
C-c C-x -	org-timer-item
C-c C-x .	org-timer
C-c C-x 0	org-timer-start
C-c C-x :	org-timer-cancel-timer
C-c C-x ;	org-timer-set-timer
C-c C-x <	org-agenda-set-restriction-lock
C-c C-x >	org-agenda-remove-restriction-lock
C-c C-x A	org-archive-to-archive-sibling
C-c C-x G	org-feed-goto-inbox
C-c C-x [	org-reftex-citation
C-c C-x \	org-toggle-pretty-entities
C-c C-x _	org-timer-stop
C-c C-x a	org-toggle-archive-tag
C-c C-x b	org-tree-to-indirect-buffer
C-c C-x c	org-clone-subtree-with-time-shift
C-c C-x d	org-insert-drawer
C-c C-x e	org-set-effort
C-c C-x f	org-footnote-action
C-c C-x g	org-feed-update-all
C-c C-x i	org-insert-columns-dblock
C-c C-x o	org-toggle-ordered-property
C-c C-x p	org-set-property
C-c C-x v	org-copy-visible

C-c C-v C-M-h	org-babel-mark-block

C-c C-x M-w	org-copy-special

C-c C-x RET g	org-mobile-pull
C-c C-x RET p	org-mobile-push


In addition to any hooks its parent mode `outline-mode' might have run,
this mode runs the hook `org-mode-hook', as the final step
during initialization.

:PROPERTIES: :CUSTOM_ID: org-mode-restart :END:

org-mouse-down-mouse (event)

Restart Org-mode, to scan again for special lines.
Also updates the keyword regular expressions.

:PROPERTIES: :CUSTOM_ID: org-mouse-down-mouse :END:

org-mouse-end-headline

:PROPERTIES: :CUSTOM_ID: org-mouse-end-headline :END:

org-mouse-insert-checkbox

Go to the end of current headline (ignoring tags).

:PROPERTIES: :CUSTOM_ID: org-mouse-insert-checkbox :END:

org-mouse-insert-heading

:PROPERTIES: :CUSTOM_ID: org-mouse-insert-heading :END:

org-mouse-move-tree (event)

Insert a new heading, as `org-insert-heading'.

If the point is at the :beginning (`org-mouse-line-position') of the line,
insert the new heading before the current line.  Otherwise, insert it
after the current heading.

:PROPERTIES: :CUSTOM_ID: org-mouse-move-tree :END:

org-mouse-move-tree-start (event)

:PROPERTIES: :CUSTOM_ID: org-mouse-move-tree-start :END:

org-mouse-remove-match-and-spaces

:PROPERTIES: :CUSTOM_ID: org-mouse-remove-match-and-spaces :END:

org-mouse-show-context-menu (event prefix)

Remove the match, make just one space around the point.

:PROPERTIES: :CUSTOM_ID: org-mouse-show-context-menu :END:

org-mouse-show-headlines

Invoke the context menu.

If the value of `org-mouse-context-menu-function' is a function, then
this function is called.  Otherwise, the current major mode menu is used.

:PROPERTIES: :CUSTOM_ID: org-mouse-show-headlines :END:

org-mouse-show-overview

Change the visibility of the current org buffer to only show headlines.

:PROPERTIES: :CUSTOM_ID: org-mouse-show-overview :END:

org-mouse-timestamp-today (&optional shift units)

Change visibility of current org buffer to first-level headlines only.

:PROPERTIES: :CUSTOM_ID: org-mouse-timestamp-today :END:

org-mouse-transform-to-outline

Change the timestamp into SHIFT UNITS in the future.

For the acceptable UNITS, see `org-timestamp-change'.

:PROPERTIES: :CUSTOM_ID: org-mouse-transform-to-outline :END:

:PROPERTIES: :CUSTOM_ID: org-mouse-yank-link :END:

org-move-item-down

:PROPERTIES: :CUSTOM_ID: org-move-item-down :END:

org-move-item-up

Move the item at point down, i.e. swap with following item.
Sub-items (items with larger indentation) are considered part of
the item, so this really moves item trees.

:PROPERTIES: :CUSTOM_ID: org-move-item-up :END:

org-move-subtree-down (&optional arg)

Move the item at point up, i.e. swap with previous item.
Sub-items (items with larger indentation) are considered part of
the item, so this really moves item trees.

:PROPERTIES: :CUSTOM_ID: org-move-subtree-down :END:

org-move-subtree-up (&optional arg)

Move the current subtree down past ARG headlines of the same level.

:PROPERTIES: :CUSTOM_ID: org-move-subtree-up :END:

org-narrow-to-block

Move the current subtree up past ARG headlines of the same level.

:PROPERTIES: :CUSTOM_ID: org-narrow-to-block :END:

org-narrow-to-subtree

Narrow buffer to the current block.

:PROPERTIES: :CUSTOM_ID: org-narrow-to-subtree :END:

org-next-item

Narrow buffer to the current subtree.

:PROPERTIES: :CUSTOM_ID: org-next-item :END:

Move to the beginning of the next item.
Throw an error when not in a list.  Also throw an error when at
last item, unless `org-list-use-circular-motion' is non-nil.

:PROPERTIES: :CUSTOM_ID: org-next-link :END:

org-occur (regexp &optional keep-previous callback)

Move forward to the next link.
If the link is in hidden text, expose it.

:PROPERTIES: :CUSTOM_ID: org-occur :END:

org-occur-in-agenda-files (regexp &optional nlines)

Make a compact tree which shows all matches of REGEXP.
The tree will show the lines where the regexp matches, and all higher
headlines above the match.  It will also show the heading after the match,
to make sure editing the matching entry is easy.
If KEEP-PREVIOUS is non-nil, highlighting and exposing done by a previous
call to `org-occur' will be kept, to allow stacking of calls to this
command.
If CALLBACK is non-nil, it is a function which is called to confirm
that the match should indeed be shown.

:PROPERTIES: :CUSTOM_ID: org-occur-in-agenda-files :END:

Call `multi-occur' with buffers for all agenda files.

:PROPERTIES: :CUSTOM_ID: org-occur-link-in-agenda-files :END:

org-open-at-mouse (ev)

Create a link and search for it in the agendas.
The link is not stored in `org-stored-links', it is just created
for the search purpose.

:PROPERTIES: :CUSTOM_ID: org-open-at-mouse :END:

org-open-at-point (&optional arg reference-buffer)

Open file link or URL at mouse.
See the docstring of `org-open-file' for details.

:PROPERTIES: :CUSTOM_ID: org-open-at-point :END:

org-open-at-point-global

Open link at or after point.
If there is no link at point, this function will search forward up to
the end of the current line.
Normally, files will be opened by an appropriate application.  If the
optional prefix argument ARG is non-nil, Emacs will visit the file.
With a double prefix argument, try to open outside of Emacs, in the
application the system uses for this file type.

This function is advised.

Around-advice `org-mouse-open-at-point'.

:PROPERTIES: :CUSTOM_ID: org-open-at-point-global :END:

Follow a link like Org-mode does.
This command can be called in any mode to follow a link that has
Org-mode syntax.

:PROPERTIES: :CUSTOM_ID: org-open-link-from-string :END:

org-org-menu (event)

Open a link in the string S, as if it was in Org-mode.

:PROPERTIES: :CUSTOM_ID: org-org-menu :END:

org-outdent-item

Org menu

:PROPERTIES: :CUSTOM_ID: org-outdent-item :END:

org-outdent-item-tree

Outdent a local list item, but not its children.
If a region is active, all items inside will be moved.

:PROPERTIES: :CUSTOM_ID: org-outdent-item-tree :END:

org-overview

Outdent a local list item including its children.
If a region is active, all items inside will be moved.

:PROPERTIES: :CUSTOM_ID: org-overview :END:

org-paste-special (arg)

Switch to overview mode, showing only top-level headlines.
Really, this shows all headlines with level equal or greater than the level
of the first headline in the buffer.  This is important, because if the
first headline is not level one, then (hide-sublevels 1) gives confusing
results.

:PROPERTIES: :CUSTOM_ID: org-paste-special :END:

  • Access: C-c C-x C-y, <menu-bar> <Org> <Edit Structure> <Paste Subtree>, <menu-bar> <Tbl> <Rectangle> <Paste Rectangle>
  • In file: org.el
  • Search modifications

org-paste-subtree (&optional level tree for-yank)

Paste rectangular region into table, or past subtree relative to level.
Calls `org-table-paste-rectangle' or `org-paste-subtree', depending on context.
See the individual commands for more information.

:PROPERTIES: :CUSTOM_ID: org-paste-subtree :END:

org-plot/collect-options (&optional params)

Paste the clipboard as a subtree, with modification of headline level.
The entire subtree is promoted or demoted in order to match a new headline
level.

If the cursor is at the beginning of a headline, the same level as
that headline is used to paste the tree

If not, the new level is derived from the *visible* headings
before and after the insertion point, and taken to be the inferior headline
level of the two.  So if the previous visible heading is level 3 and the
next is level 4 (or vice versa), level 4 will be used for insertion.
This makes sure that the subtree remains an independent subtree and does
not swallow low level entries.

You can also force a different level, either by using a numeric prefix
argument, or by inserting the heading marker by hand.  For example, if the
cursor is after "*****", then the tree will be shifted to level 5.

If optional TREE is given, use this text instead of the kill ring.

When FOR-YANK is set, this is called by `org-yank'.  In this case, do not
move back over whitespace before inserting, and move point to the end of
the inserted text when done.

:PROPERTIES: :CUSTOM_ID: org-plot/collect-options :END:

org-plot/gnuplot (&optional params)

Collect options from an org-plot '#+Plot:' line.
Accepts an optional property list PARAMS, to which the options
will be added.  Returns the resulting property list.

:PROPERTIES: :CUSTOM_ID: org-plot/gnuplot :END:

org-plot/gnuplot-to-grid-data (table data-file params)

Plot table using gnuplot.  Gnuplot options can be specified with PARAMS.
If not given options will be taken from the +PLOT
line directly before or after the table.

:PROPERTIES: :CUSTOM_ID: org-plot/gnuplot-to-grid-data :END:

org-plot/goto-nearest-table

Export the data in TABLE to DATA-FILE for gnuplot.
This means in a format appropriate for grid plotting by gnuplot.
PARAMS specifies which columns of TABLE should be plotted as independent
and dependant variables.

:PROPERTIES: :CUSTOM_ID: org-plot/goto-nearest-table :END:

org-prepare-agenda-buffers (files)

Move the point forward to the beginning of nearest table.
Return value is the point at the beginning of the table.

:PROPERTIES: :CUSTOM_ID: org-prepare-agenda-buffers :END:

org-preview-latex-fragment (&optional subtree)

Create buffers for all agenda files, protect archived trees and comments.

:PROPERTIES: :CUSTOM_ID: org-preview-latex-fragment :END:

org-previous-item

Preview the LaTeX fragment at point, or all locally or globally.
If the cursor is in a LaTeX fragment, create the image and overlay
it over the source code.  If there is no fragment at point, display
all fragments in the current text, from one headline to the next.  With
prefix SUBTREE, display all fragments in the current subtree.  With a
double prefix arg C-u C-u, or when the cursor is before the first headline,
display all fragments in the buffer.
The images can be removed again with C-c C-c.

:PROPERTIES: :CUSTOM_ID: org-previous-item :END:

Move to the beginning of the previous item.
Throw an error when not in a list.  Also throw an error when at
first item, unless `org-list-use-circular-motion' is non-nil.

:PROPERTIES: :CUSTOM_ID: org-previous-link :END:

org-priority (&optional action)

Move backward to the previous link.
If the link is in hidden text, expose it.

:PROPERTIES: :CUSTOM_ID: org-priority :END:

org-priority-down

Change the priority of an item by ARG.
ACTION can be `set', `up', `down', or a character.

:PROPERTIES: :CUSTOM_ID: org-priority-down :END:

org-priority-up

Decrease the priority of the current item.

:PROPERTIES: :CUSTOM_ID: org-priority-up :END:

org-promote-subtree

Increase the priority of the current item.

:PROPERTIES: :CUSTOM_ID: org-promote-subtree :END:

org-property-action

Promote the entire subtree.
See also `org-promote'.

:PROPERTIES: :CUSTOM_ID: org-property-action :END:

org-property-next-allowed-value (&optional previous)

Do an action on properties.

:PROPERTIES: :CUSTOM_ID: org-property-next-allowed-value :END:

org-property-previous-allowed-value (&optional previous)

Switch to the next allowed value for this property.

:PROPERTIES: :CUSTOM_ID: org-property-previous-allowed-value :END:

org-protocol-create (&optional project-plist)

Switch to the next allowed value for this property.

:PROPERTIES: :CUSTOM_ID: org-protocol-create :END:

org-protocol-create-for-org

Create a new org-protocol project interactively.
An org-protocol project is an entry in `org-protocol-project-alist'
which is used by `org-protocol-open-source'.
Optionally use project-plist to initialize the defaults for this project. If
project-plist is the CDR of an element in `org-publish-project-alist', reuse
:base-directory, :html-extension and :base-extension.

:PROPERTIES: :CUSTOM_ID: org-protocol-create-for-org :END:

org-publish (project &optional force)

Create a org-protocol project for the current file's Org-mode project.
This works, if the file visited is part of a publishing project in
`org-publish-project-alist'.  This function calls `org-protocol-create' to do
most of the work.

:PROPERTIES: :CUSTOM_ID: org-publish :END:

org-publish-all (&optional force)

Publish PROJECT.

:PROPERTIES: :CUSTOM_ID: org-publish-all :END:

org-publish-current-file (&optional force)

Publish all projects.
With prefix argument, remove all files in the timestamp
directory and force publishing all files.

:PROPERTIES: :CUSTOM_ID: org-publish-current-file :END:

org-publish-current-project (&optional force)

Publish the current file.
With prefix argument, force publish the file.

:PROPERTIES: :CUSTOM_ID: org-publish-current-project :END:

org-publish-project (project &optional force)

Publish the project associated with the current file.
With a prefix argument, force publishing of all files in
the project.

:PROPERTIES: :CUSTOM_ID: org-publish-project :END:

org-refile (&optional goto default-buffer rfloc)

Publish PROJECT.

:PROPERTIES: :CUSTOM_ID: org-refile :END:

org-refile-goto-last-stored

Move the entry or entries at point to another heading.
The list of target headings is compiled using the information in
`org-refile-targets', which see.

At the target location, the entry is filed as a subitem of the target
heading.  Depending on `org-reverse-note-order', the new subitem will
either be the first or the last subitem.

If there is an active region, all entries in that region will be moved.
However, the region must fulfill the requirement that the first heading
is the first one sets the top-level of the moved text - at most siblings
below it are allowed.

With prefix arg GOTO, the command will only visit the target location
and not actually move anything.

With a double prefix arg C-u C-u, go to the location where the last refiling operation has put the subtree.
With a prefix argument of `2', refile to the running clock.

RFLOC can be a refile location obtained in a different way.

See also `org-refile-use-outline-path' and `org-completion-use-ido'.

If you are using target caching (see `org-refile-use-cache'),
you have to clear the target cache in order to find new targets.
This can be done with a 0 prefix (`C-0 C-c C-w') or a triple
prefix argument (`C-u C-u C-u C-c C-w').

:PROPERTIES: :CUSTOM_ID: org-refile-goto-last-stored :END:

org-reftex-citation

Go to the location where the last refile was stored.

:PROPERTIES: :CUSTOM_ID: org-reftex-citation :END:

org-reload (&optional uncompiled)

Use reftex-citation to insert a citation into the buffer.
This looks for a line like

#+BIBLIOGRAPHY: foo plain option:-d

and derives from it that foo.bib is the bibliography file relevant
for this document.  It then installs the necessary environment for RefTeX
to work in this buffer and calls `reftex-citation'  to insert a citation
into the buffer.

Export of such citations to both LaTeX and HTML is handled by the contributed
package org-exp-bibtex by Taru Karttunen.

:PROPERTIES: :CUSTOM_ID: org-reload :END:

org-remember (&optional goto org-force-remember-template-char)

Reload all org lisp files.
With prefix arg UNCOMPILED, load the uncompiled versions.

:PROPERTIES: :CUSTOM_ID: org-remember :END:

org-remember-finalize

Call `remember'.  If this is already a remember buffer, re-apply template.
If there is an active region, make sure remember uses it as initial content
of the remember buffer.

When called interactively with a C-u prefix argument GOTO, don't remember
anything, just go to the file/headline where the selected template usually
stores its notes.  With a double prefix argument C-u C-u, go to the last
note stored by remember.

Lisp programs can set ORG-FORCE-REMEMBER-TEMPLATE-CHAR to a character
associated with a template in `org-remember-templates'.

:PROPERTIES: :CUSTOM_ID: org-remember-finalize :END:

org-remember-goto-last-stored

Finalize the remember process.

:PROPERTIES: :CUSTOM_ID: org-remember-goto-last-stored :END:

org-remember-kill

Go to the location where the last remember note was stored.

:PROPERTIES: :CUSTOM_ID: org-remember-kill :END:

org-remember-mode (&optional arg)

Abort the current remember process.

:PROPERTIES: :CUSTOM_ID: org-remember-mode :END:

org-remove-file (&optional file)

Minor mode for special key bindings in a remember buffer.

:PROPERTIES: :CUSTOM_ID: org-remove-file :END:

org-remove-formatting-on-newlines-in-region (beg end)

Remove current file from the list of files in variable `org-agenda-files'.
These are the files which are being checked for agenda entries.
Optional argument FILE means use this file instead of the current.

:PROPERTIES: :CUSTOM_ID: org-remove-formatting-on-newlines-in-region :END:

org-remove-inline-images

Remove formatting on newline characters

:PROPERTIES: :CUSTOM_ID: org-remove-inline-images :END:

org-remove-occur-highlights (&optional beg end noremove)

Remove inline display of images.

:PROPERTIES: :CUSTOM_ID: org-remove-occur-highlights :END:

org-replace-region-by-ascii (beg end)

Remove the occur highlights from the buffer.
BEG and END are ignored.  If NOREMOVE is nil, remove this function
from the `before-change-functions' in the current buffer.

:PROPERTIES: :CUSTOM_ID: org-replace-region-by-ascii :END:

org-replace-region-by-docbook (beg end)

Assume the current region has org-mode syntax, and convert it to plain ASCII.
This can be used in any buffer.  For example, you could write an
itemized list in org-mode syntax in a Mail buffer and then use this
command to convert it.

:PROPERTIES: :CUSTOM_ID: org-replace-region-by-docbook :END:

org-replace-region-by-html (beg end)

Replace the region from BEG to END with its DocBook export.
It assumes the region has `org-mode' syntax, and then convert it to
DocBook.  This can be used in any buffer.  For example, you could
write an itemized list in `org-mode' syntax in an DocBook buffer and
then use this command to convert it.

:PROPERTIES: :CUSTOM_ID: org-replace-region-by-html :END:

org-replace-region-by-latex (beg end)

Assume the current region has org-mode syntax, and convert it to HTML.
This can be used in any buffer.  For example, you could write an
itemized list in org-mode syntax in an HTML buffer and then use this
command to convert it.

:PROPERTIES: :CUSTOM_ID: org-replace-region-by-latex :END:

org-require-autoloaded-modules

Replace the region from BEG to END with its LaTeX export.
It assumes the region has `org-mode' syntax, and then convert it to
LaTeX.  This can be used in any buffer.  For example, you could
write an itemized list in `org-mode' syntax in an LaTeX buffer and
then use this command to convert it.

:PROPERTIES: :CUSTOM_ID: org-require-autoloaded-modules :END:

org-reset-checkbox-state-subtree

:PROPERTIES: :CUSTOM_ID: org-reset-checkbox-state-subtree :END:

org-resolve-clocks (&optional only-dangling-p prompt-fn last-valid)

Reset all checkboxes in an entry subtree.

:PROPERTIES: :CUSTOM_ID: org-resolve-clocks :END:

org-return (&optional indent)

Resolve all currently open org-mode clocks.
If `only-dangling-p' is non-nil, only ask to resolve dangling
(i.e., not currently open and valid) clocks.

:PROPERTIES: :CUSTOM_ID: org-return :END:

org-return-indent

Goto next table row or insert a newline.
Calls `org-table-next-row' or `newline', depending on context.
See the individual commands for more information.

:PROPERTIES: :CUSTOM_ID: org-return-indent :END:

org-reveal (&optional siblings)

Goto next table row or insert a newline and indent.
Calls `org-table-next-row' or `newline-and-indent', depending on
context.  See the individual commands for more information.

:PROPERTIES: :CUSTOM_ID: org-reveal :END:

org-revert-all-org-buffers

Show current entry, hierarchy above it, and the following headline.
This can be used to show a consistent set of context around locations
exposed with `org-show-hierarchy-above' or `org-show-following-heading'
not t for the search context.

With optional argument SIBLINGS, on each level of the hierarchy all
siblings are shown.  This repairs the tree structure to what it would
look like when opened with hierarchical calls to `org-cycle'.
With double optional argument C-u C-u, go to the parent and show the
entire tree.

:PROPERTIES: :CUSTOM_ID: org-revert-all-org-buffers :END:

org-save-all-org-buffers

Revert all Org-mode buffers.
Prompt for confirmation when there are unsaved changes.
Be sure you know what you are doing before letting this function
overwrite your changes.

This function is useful in a setup where one tracks org files
with a version control system, to revert on one machine after pulling
changes from another.  I believe the procedure must be like this:

1. M-x org-save-all-org-buffers
2. Pull changes from the other machine, resolve conflicts
3. M-x org-revert-all-org-buffers

:PROPERTIES: :CUSTOM_ID: org-save-all-org-buffers :END:

org-schedule (&optional remove time)

Save all Org-mode buffers without user confirmation.

:PROPERTIES: :CUSTOM_ID: org-schedule :END:

org-search-view (&optional todo-only string edit-at)

Insert the SCHEDULED: string with a timestamp to schedule a TODO item.
With argument REMOVE, remove any scheduling date from the item.
With argument TIME, scheduled at the corresponding date.  TIME can
either be an Org date like "2011-07-24" or a delta like "+2d".

:PROPERTIES: :CUSTOM_ID: org-search-view :END:

org-self-insert-command (N)

Show all entries that contain a phrase or words or regular expressions.

With optional prefix argument TODO-ONLY, only consider entries that are
TODO entries.  The argument STRING can be used to pass a default search
string into this function.  If EDIT-AT is non-nil, it means that the
user should get a chance to edit this string, with cursor at position
EDIT-AT.

The search string can be viewed either as a phrase that should be found as
is, or it can be broken into a number of snippets, each of which must match
in a Boolean way to select an entry.  The default depends on the variable
`org-agenda-search-view-always-boolean'.
Even if this is turned off (the default) you can always switch to
Boolean search dynamically by preceding the first word with  "+" or "-".

The default is a direct search of the whole phrase, where each space in
the search string can expand to an arbitrary amount of whitespace,
including newlines.

If using a Boolean search, the search string is split on whitespace and
each snippet is searched separately, with logical AND to select an entry.
Words prefixed with a minus must *not* occur in the entry.  Words without
a prefix or prefixed with a plus must occur in the entry.  Matching is
case-insensitive.  Words are enclosed by word delimiters (i.e. they must
match whole words, not parts of a word) if
`org-agenda-search-view-force-full-words' is set (default is nil).

Boolean search snippets enclosed by curly braces are interpreted as
regular expressions that must or (when preceded with "-") must not
match in the entry.  Snippets enclosed into double quotes will be taken
as a whole, to include whitespace.

- If the search string starts with an asterisk, search only in headlines.
- If (possibly after the leading star) the search string starts with an
  exclamation mark, this also means to look at TODO entries only, an effect
  that can also be achieved with a prefix argument.
- If (possibly after star and exclamation mark) the search string starts
  with a colon, this will mean that the (non-regexp) snippets of the
  Boolean search must match as full words.

This command searches the agenda files, and in addition the files listed
in `org-agenda-text-search-extra-files'.

:PROPERTIES: :CUSTOM_ID: org-self-insert-command :END:

org-set-autofill-regexps

Like `self-insert-command', use overwrite-mode for whitespace in tables.
If the cursor is in a table looking at whitespace, the whitespace is
overwritten, and the table is not marked as requiring realignment.

:PROPERTIES: :CUSTOM_ID: org-set-autofill-regexps :END:

org-set-effort (&optional value)

:PROPERTIES: :CUSTOM_ID: org-set-effort :END:

org-set-property (property value)

Set the effort property of the current entry.
With numerical prefix arg, use the nth allowed value, 0 stands for the 10th
allowed value.

:PROPERTIES: :CUSTOM_ID: org-set-property :END:

org-set-tags (&optional arg just-align)

In the current entry, set PROPERTY to VALUE.
When called interactively, this will prompt for a property name, offering
completion on existing and default properties.  And then it will prompt
for a value, offering completion either on allowed values (via an inherited
xxx_ALL property) or on existing values in other instances of this property
in the current file.

:PROPERTIES: :CUSTOM_ID: org-set-tags :END:

org-set-tags-command (&optional arg just-align)

Set the tags for the current headline.
With prefix ARG, realign all tags in headings in the current buffer.

:PROPERTIES: :CUSTOM_ID: org-set-tags-command :END:

org-set-tags-to (data)

Call the set-tags command for the current entry.

:PROPERTIES: :CUSTOM_ID: org-set-tags-to :END:

org-set-visibility-according-to-property (&optional no-cleanup)

Set the tags of the current entry to DATA, replacing the current tags.
DATA may be a tags string like :aa:bb:cc:, or a list of tags.
If DATA is nil or the empty string, any tags will be removed.

:PROPERTIES: :CUSTOM_ID: org-set-visibility-according-to-property :END:

org-shiftcontroldown

Switch subtree visibilities according to :VISIBILITY: property.

:PROPERTIES: :CUSTOM_ID: org-shiftcontroldown :END:

org-shiftcontrolleft

Change timestamps synchronously down in CLOCK log lines.

:PROPERTIES: :CUSTOM_ID: org-shiftcontrolleft :END:

org-shiftcontrolright

Switch to previous TODO set.

:PROPERTIES: :CUSTOM_ID: org-shiftcontrolright :END:

  • Access: <C-S-right>, <menu-bar> <Org> <TODO Lists> <Select keyword> <Next keyword set>, <menu-bar> <Org> <TODO Lists> <Select keyword> <Previous keyword set>
  • In file: org.el
  • Search modifications

org-shiftcontrolup

Switch to next TODO set.

:PROPERTIES: :CUSTOM_ID: org-shiftcontrolup :END:

org-shiftdown (&optional arg)

Change timestamps synchronously up in CLOCK log lines.

:PROPERTIES: :CUSTOM_ID: org-shiftdown :END:

  • Access: <S-down>, <menu-bar> <Org> <TODO Lists> <Priority Down>, <menu-bar> <Org> <Dates and Scheduling> <Change Date> <1 ... Earlier>
  • In file: org.el
  • Search modifications

org-shiftleft (&optional arg)

Decrease item in timestamp or decrease priority of current headline.
Calls `org-timestamp-down' or `org-priority-down', or `org-next-item'
depending on context.  See the individual commands for more information.

:PROPERTIES: :CUSTOM_ID: org-shiftleft :END:

  • Access: <S-left>, <menu-bar> <Org> <TODO Lists> <Select keyword> <Previous keyword>, <menu-bar> <Org> <Dates and Scheduling> <Change Date> <1 Day Earlier>
  • In file: org.el
  • Search modifications

org-shiftmetadown (&optional arg)

Cycle the thing at point or in the current line, depending on context.
Depending on context, this does one of the following:

- switch a timestamp at point one day into the past
- on a headline, switch to the previous TODO keyword.
- on an item, switch entire list to the previous bullet type
- on a property line, switch to the previous allowed value
- on a clocktable definition line, move time block into the past

:PROPERTIES: :CUSTOM_ID: org-shiftmetadown :END:

  • Access: <M-S-down>, <menu-bar> <Org> <Edit Structure> <Move Subtree Down>, <menu-bar> <Tbl> <Row> <Insert Row>
  • In file: org.el
  • Search modifications

org-shiftmetaleft

Move subtree down or insert table row.
Calls `org-move-subtree-down' or `org-table-insert-row' or
`org-move-item-down', depending on context.  See the individual
commands for more information.

:PROPERTIES: :CUSTOM_ID: org-shiftmetaleft :END:

  • Access: <M-S-left>, <menu-bar> <Org> <Edit Structure> <Promote Subtree>, <menu-bar> <Tbl> <Column> <Delete Column>
  • In file: org.el
  • Search modifications

org-shiftmetaright

Promote subtree or delete table column.
Calls `org-promote-subtree', `org-outdent-item-tree', or
`org-table-delete-column', depending on context.  See the
individual commands for more information.

:PROPERTIES: :CUSTOM_ID: org-shiftmetaright :END:

  • Access: <M-S-right>, <menu-bar> <Org> <Edit Structure> <Demote Subtree>, <menu-bar> <Tbl> <Column> <Insert Column>
  • In file: org.el
  • Search modifications

org-shiftmetaup (&optional arg)

Demote subtree or insert table column.
Calls `org-demote-subtree', `org-indent-item-tree', or
`org-table-insert-column', depending on context.  See the
individual commands for more information.

:PROPERTIES: :CUSTOM_ID: org-shiftmetaup :END:

  • Access: <M-S-up>, <menu-bar> <Org> <Edit Structure> <Move Subtree Up>, <menu-bar> <Tbl> <Row> <Delete Row>
  • In file: org.el
  • Search modifications

org-shiftright (&optional arg)

Move subtree up or kill table row.
Calls `org-move-subtree-up' or `org-table-kill-row' or
`org-move-item-up' depending on context.  See the individual commands
for more information.

:PROPERTIES: :CUSTOM_ID: org-shiftright :END:

  • Access: <S-right>, <menu-bar> <Org> <TODO Lists> <Select keyword> <Next keyword>, <menu-bar> <Org> <Dates and Scheduling> <Change Date> <1 Day Later>
  • In file: org.el
  • Search modifications

org-shifttab (&optional arg)

Cycle the thing at point or in the current line, depending on context.
Depending on context, this does one of the following:

- switch a timestamp at point one day into the future
- on a headline, switch to the next TODO keyword.
- on an item, switch entire list to the next bullet type
- on a property line, switch to the next allowed value
- on a clocktable definition line, move time block into the future

:PROPERTIES: :CUSTOM_ID: org-shifttab :END:

  • Access: <backtab>, <S-tab>, <S-iso-lefttab>, <menu-bar> <Tbl> <Previous Field>, <menu-bar> <Org> <Show/Hide> <Cycle Global Visibility>
  • In file: org.el
  • Search modifications

org-shiftup (&optional arg)

Global visibility cycling or move to previous table field.
Calls `org-cycle' with argument t, or `org-table-previous-field', depending
on context.
See the individual commands for more information.

:PROPERTIES: :CUSTOM_ID: org-shiftup :END:

  • Access: <S-up>, <menu-bar> <Org> <TODO Lists> <Priority Up>, <menu-bar> <Org> <Dates and Scheduling> <Change Date> <1 ... Later>
  • In file: org.el
  • Search modifications

org-show-block-all

Increase item in timestamp or increase priority of current headline.
Calls `org-timestamp-up' or `org-priority-up', or `org-previous-item',
depending on context.  See the individual commands for more information.

:PROPERTIES: :CUSTOM_ID: org-show-block-all :END:

org-show-entry

Unfold all blocks in the current buffer.

:PROPERTIES: :CUSTOM_ID: org-show-entry :END:

org-show-subtree

Show the body directly following this heading.
Show the heading too, if it is currently invisible.

:PROPERTIES: :CUSTOM_ID: org-show-subtree :END:

org-show-todo-tree (arg)

Show everything after this heading at deeper levels.

:PROPERTIES: :CUSTOM_ID: org-show-todo-tree :END:

  • Access: <menu-bar> <Org> <TODO Lists> <Show TODO Tree>, <menu-bar> <Org> <Special views current file> <TODO Tree>
  • In file: org.el
  • Search modifications

org-smart-reschedule (quality)

Make a compact tree which shows all headlines marked with TODO.
The tree will show the lines where the regexp matches, and all higher
headlines above the match.
With a C-u prefix, prompt for a regexp to match.
With a numeric prefix N, construct a sparse tree for the Nth element
of `org-todo-keywords-1'.

:PROPERTIES: :CUSTOM_ID: org-smart-reschedule :END:

org-sort (with-case)

:PROPERTIES: :CUSTOM_ID: org-sort :END:

org-sort-entries (&optional with-case sorting-type getkey-func compare-func property)

Call `org-sort-entries', `org-table-sort-lines' or `org-sort-list'.
Optional argument WITH-CASE means sort case-sensitively.

:PROPERTIES: :CUSTOM_ID: org-sort-entries :END:

org-sort-list (&optional with-case sorting-type getkey-func compare-func)

Sort entries on a certain level of an outline tree.
If there is an active region, the entries in the region are sorted.
Else, if the cursor is before the first entry, sort the top-level items.
Else, the children of the entry at point are sorted.

Sorting can be alphabetically, numerically, by date/time as given by
a time stamp, by a property or by priority.

The command prompts for the sorting type unless it has been given to the
function through the SORTING-TYPE argument, which needs to be a character,
(?n ?N ?a ?A ?t ?T ?s ?S ?d ?D ?p ?P ?r ?R ?f ?F).  Here is the
precise meaning of each character:

n   Numerically, by converting the beginning of the entry/item to a number.
a   Alphabetically, ignoring the TODO keyword and the priority, if any.
t   By date/time, either the first active time stamp in the entry, or, if
    none exist, by the first inactive one.
s   By the scheduled date/time.
d   By deadline date/time.
c   By creation time, which is assumed to be the first inactive time stamp
    at the beginning of a line.
p   By priority according to the cookie.
r   By the value of a property.

Capital letters will reverse the sort order.

If the SORTING-TYPE is ?f or ?F, then GETKEY-FUNC specifies a function to be
called with point at the beginning of the record.  It must return either
a string or a number that should serve as the sorting key for that record.

Comparing entries ignores case by default.  However, with an optional argument
WITH-CASE, the sorting considers case as well.

:PROPERTIES: :CUSTOM_ID: org-sort-list :END:

org-sparse-tree (&optional arg)

Sort list items.
The cursor may be at any item of the list that should be sorted.
Sublists are not sorted.  Checkboxes, if any, are ignored.

Sorting can be alphabetically, numerically, by date/time as given
by a time stamp, by a property or by priority.

Comparing entries ignores case by default.  However, with an
optional argument WITH-CASE, the sorting considers case as well.

The command prompts for the sorting type unless it has been given
to the function through the SORTING-TYPE argument, which needs to
be a character, (?n ?N ?a ?A ?t ?T ?f ?F).  Here is the precise
meaning of each character:

n   Numerically, by converting the beginning of the item to a number.
a   Alphabetically.  Only the first line of item is checked.
t   By date/time, either the first active time stamp in the entry, if
    any, or by the first inactive one.  In a timer list, sort the timers.

Capital letters will reverse the sort order.

If the SORTING-TYPE is ?f or ?F, then GETKEY-FUNC specifies
a function to be called with point at the beginning of the
record.  It must return either a string or a number that should
serve as the sorting key for that record.  It will then use
COMPARE-FUNC to compare entries.

:PROPERTIES: :CUSTOM_ID: org-sparse-tree :END:

org-speed-command-help

Create a sparse tree, prompt for the details.
This command can create sparse trees.  You first need to select the type
of match used to create the tree:

t      Show all TODO entries.
T      Show entries with a specific TODO keyword.
m      Show entries selected by a tags/property match.
p      Enter a property name and its value (both with completion on existing
       names/values) and show entries with that property.
r      Show entries matching a regular expression (`/' can be used as well)
d      Show deadlines due within `org-deadline-warning-days'.
b      Show deadlines and scheduled items before a date.
a      Show deadlines and scheduled items after a date.

:PROPERTIES: :CUSTOM_ID: org-speed-command-help :END:

org-speed-move-safe (cmd)

Show the available speed commands.

:PROPERTIES: :CUSTOM_ID: org-speed-move-safe :END:

org-speedbar-set-agenda-restriction

Execute CMD, but make sure that the cursor always ends up in a headline.
If not, return to the original position and throw an error.

:PROPERTIES: :CUSTOM_ID: org-speedbar-set-agenda-restriction :END:

org-src-associate-babel-session (info)

Restrict future agenda commands to the location at point in speedbar.
To get rid of the restriction, use C-c C-x >.

:PROPERTIES: :CUSTOM_ID: org-src-associate-babel-session :END:

org-src-do-key-sequence-at-code-block (&optional key)

Associate edit buffer with comint session.

:PROPERTIES: :CUSTOM_ID: org-src-do-key-sequence-at-code-block :END:

org-src-fontify-block

Execute key sequence at code block in the source Org buffer.
The command bound to KEY in the Org-babel key map is executed
remotely with point temporarily at the start of the code block in
the Org buffer.

This command is not bound to a key by default, to avoid conflicts
with language major mode bindings.  To bind it to C-c @ in all
language major modes, you could use

  (add-hook 'org-src-mode-hook
            (lambda () (define-key org-src-mode-map "\C-c@"
                    'org-src-do-key-sequence-at-code-block)))

In that case, for example, C-c @ t issued in code edit buffers
would tangle the current Org code block, C-c @ e would execute
the block and C-c @ h would display the other available
Org-babel commands.

:PROPERTIES: :CUSTOM_ID: org-src-fontify-block :END:

org-src-fontify-buffer

Fontify code block at point.

:PROPERTIES: :CUSTOM_ID: org-src-fontify-buffer :END:

org-src-mode (&optional arg)

Fontify all code blocks in the current buffer.

:PROPERTIES: :CUSTOM_ID: org-src-mode :END:

org-src-tangle (arg)

Minor mode for language major mode buffers generated by org.
This minor mode is turned on in two situations:
- when editing a source code snippet with "C-c '".
- When formatting a source code snippet for export with htmlize.
There is a mode hook, and keybindings for `org-edit-src-exit' and
`org-edit-src-save'

:PROPERTIES: :CUSTOM_ID: org-src-tangle :END:

org-store-agenda-views (&rest parameters)

Tangle the parent buffer.

:PROPERTIES: :CUSTOM_ID: org-store-agenda-views :END:

:PROPERTIES: :CUSTOM_ID: org-store-link :END:

org-strip-protective-commas (beg end)

Store an org-link to the current location.
This link is added to `org-stored-links' and can later be inserted
into an org-buffer with C-c C-l.

For some link types, a prefix arg is interpreted:
For links to usenet articles, arg negates `org-gnus-prefer-web-links'.
For file links, arg negates `org-context-in-file-links'.

:PROPERTIES: :CUSTOM_ID: org-strip-protective-commas :END:

org-submit-bug-report

Strip protective commas between BEG and END in the current buffer.

:PROPERTIES: :CUSTOM_ID: org-submit-bug-report :END:

org-switchb (&optional arg)

Submit a bug report on Org-mode via mail.

Don't hesitate to report any problems or inaccurate documentation.

If you don't have setup sending mail from (X)Emacs, please copy the
output buffer into your mail program, as it gives us important
information about your Org-mode version and configuration.

:PROPERTIES: :CUSTOM_ID: org-switchb :END:

org-table-align

Switch between Org buffers.
With one prefix argument, restrict available buffers to files.
With two prefix arguments, restrict available buffers to agenda files.

Defaults to `iswitchb' for buffer name completion.
Set `org-completion-use-ido' to make it use ido instead.

:PROPERTIES: :CUSTOM_ID: org-table-align :END:

org-table-beginning-of-field (&optional n)

Align the table at point by aligning all vertical bars.

:PROPERTIES: :CUSTOM_ID: org-table-beginning-of-field :END:

org-table-blank-field

Move to the end of the current table field.
If already at or after the end, move to the end of the next table field.
With numeric argument N, move N-1 fields forward first.

:PROPERTIES: :CUSTOM_ID: org-table-blank-field :END:

org-table-convert

Blank the current table field or active region.

:PROPERTIES: :CUSTOM_ID: org-table-convert :END:

org-table-convert-region (beg0 end0 &optional separator)

Convert from `org-mode' table to table.el and back.
Obviously, this only works within limits.  When an Org-mode table is
converted to table.el, all horizontal separator lines get lost, because
table.el uses these as cell boundaries and has no notion of horizontal lines.
A table.el table can be converted to an Org-mode table only if it does not
do row or column spanning.  Multiline cells will become multiple cells.
Beware, Org-mode does not test if the table can be successfully converted - it
blindly applies a recipe that works for simple tables.

:PROPERTIES: :CUSTOM_ID: org-table-convert-region :END:

org-table-copy-down (n)

Convert region to a table.
The region goes from BEG0 to END0, but these borders will be moved
slightly, to make sure a beginning of line in the first line is included.

SEPARATOR specifies the field separator in the lines.  It can have the
following values:

'(4)     Use the comma as a field separator
'(16)    Use a TAB as field separator
integer  When a number, use that many spaces as field separator
nil      When nil, the command tries to be smart and figure out the
         separator in the following way:
         - when each line contains a TAB, assume TAB-separated material
         - when each line contains a comma, assume CSV material
         - else, assume one or more SPACE characters as separator.

:PROPERTIES: :CUSTOM_ID: org-table-copy-down :END:

org-table-copy-region (beg end &optional cut)

Copy a field down in the current column.
If the field at the cursor is empty, copy into it the content of
the nearest non-empty field above.  With argument N, use the Nth
non-empty field.  If the current field is not empty, it is copied
down to the next row, and the cursor is moved with it.
Therefore, repeating this command causes the column to be filled
row-by-row.
If the variable `org-table-copy-increment' is non-nil and the
field is an integer or a timestamp, it will be incremented while
copying.  In the case of a timestamp, increment by one day.

:PROPERTIES: :CUSTOM_ID: org-table-copy-region :END:

org-table-create (&optional size)

Copy rectangular region in table to clipboard.
A special clipboard is used which can only be accessed
with `org-table-paste-rectangle'.

:PROPERTIES: :CUSTOM_ID: org-table-create :END:

org-table-create-or-convert-from-region (arg)

Query for a size and insert a table skeleton.
SIZE is a string Columns x Rows like for example "3x2".

:PROPERTIES: :CUSTOM_ID: org-table-create-or-convert-from-region :END:

org-table-create-with-table.el

Convert region to table, or create an empty table.
If there is an active region, convert it to a table, using the function
`org-table-convert-region'.  See the documentation of that function
to learn how the prefix argument is interpreted to determine the field
separator.
If there is no such region, create an empty table with `org-table-create'.

:PROPERTIES: :CUSTOM_ID: org-table-create-with-table.el :END:

org-table-current-column

Use the table.el package to insert a new table.
If there is already a table at point, convert between Org-mode tables
and table.el tables.

:PROPERTIES: :CUSTOM_ID: org-table-current-column :END:

org-table-current-dline

Find out which column we are in.

:PROPERTIES: :CUSTOM_ID: org-table-current-dline :END:

org-table-cut-region (beg end)

Find out what table data line we are in.
Only data lines count for this.

:PROPERTIES: :CUSTOM_ID: org-table-cut-region :END:

org-table-delete-column

Copy region in table to the clipboard and blank all relevant fields.
If there is no active region, use just the field at point.

:PROPERTIES: :CUSTOM_ID: org-table-delete-column :END:

org-table-edit-field (arg)

Delete a column from the table.

:PROPERTIES: :CUSTOM_ID: org-table-edit-field :END:

org-table-edit-formulas

Edit table field in a different window.
This is mainly useful for fields that contain hidden parts.
When called with a C-u prefix, just make the full field visible so that
it can be edited in place.

:PROPERTIES: :CUSTOM_ID: org-table-edit-formulas :END:

org-table-end-of-field (&optional n)

Edit the formulas of the current table in a separate buffer.

:PROPERTIES: :CUSTOM_ID: org-table-end-of-field :END:

org-table-eval-formula (&optional arg equation suppress-align suppress-const suppress-store suppress-analysis)

Move to the beginning of the current table field.
If already at or before the beginning, move to the beginning of the
previous field.
With numeric argument N, move N-1 fields backward first.

:PROPERTIES: :CUSTOM_ID: org-table-eval-formula :END:

org-table-export (&optional file format)

Replace the table field value at the cursor by the result of a calculation.

This function makes use of Dave Gillespie's Calc package, in my view the
most exciting program ever written for GNU Emacs.  So you need to have Calc
installed in order to use this function.

In a table, this command replaces the value in the current field with the
result of a formula.  It also installs the formula as the "current" column
formula, by storing it in a special line below the table.  When called
with a `C-u' prefix, the current field must be a named field, and the
formula is installed as valid in only this specific field.

When called with two `C-u' prefixes, insert the active equation
for the field back into the current field, so that it can be
edited there.  This is useful in order to use M-x org-table-show-reference
to check the referenced fields.

When called, the command first prompts for a formula, which is read in
the minibuffer.  Previously entered formulas are available through the
history list, and the last used formula is offered as a default.
These stored formulas are adapted correctly when moving, inserting, or
deleting columns with the corresponding commands.

The formula can be any algebraic expression understood by the Calc package.
For details, see the Org-mode manual.

This function can also be called from Lisp programs and offers
additional arguments: EQUATION can be the formula to apply.  If this
argument is given, the user will not be prompted.  SUPPRESS-ALIGN is
used to speed-up recursive calls by by-passing unnecessary aligns.
SUPPRESS-CONST suppresses the interpretation of constants in the
formula, assuming that this has been done already outside the function.
SUPPRESS-STORE means the formula should not be stored, either because
it is already stored, or because it is a modified equation that should
not overwrite the stored one.

:PROPERTIES: :CUSTOM_ID: org-table-export :END:

org-table-fedit-abort

Export table to a file, with configurable format.
Such a file can be imported into usual spreadsheet programs.

FILE can be the output file name.  If not given, it will be taken
from a TABLE_EXPORT_FILE property in the current entry or higher
up in the hierarchy, or the user will be prompted for a file
name.  FORMAT can be an export format, of the same kind as it
used when `orgtbl-mode' sends a table in a different format.

The command suggests a format depending on TABLE_EXPORT_FORMAT,
whether it is set locally or up in the hierarchy, then on the
extension of the given file name, and finally on the variable
`org-table-export-default-format'.

:PROPERTIES: :CUSTOM_ID: org-table-fedit-abort :END:

org-table-fedit-finish (&optional arg)

Abort editing formulas, without installing the changes.

:PROPERTIES: :CUSTOM_ID: org-table-fedit-finish :END:

org-table-fedit-line-down

Parse the buffer for formula definitions and install them.
With prefix ARG, apply the new formulas to the table.

:PROPERTIES: :CUSTOM_ID: org-table-fedit-line-down :END:

org-table-fedit-line-up

Move cursor one line down in the window showing the table.

:PROPERTIES: :CUSTOM_ID: org-table-fedit-line-up :END:

org-table-fedit-lisp-indent

Move cursor one line up in the window showing the table.

:PROPERTIES: :CUSTOM_ID: org-table-fedit-lisp-indent :END:

org-table-fedit-menu (event)

Pretty-print and re-indent Lisp expressions in the Formula Editor.

:PROPERTIES: :CUSTOM_ID: org-table-fedit-menu :END:

org-table-fedit-ref-down

Org Edit Formulas Menu

:PROPERTIES: :CUSTOM_ID: org-table-fedit-ref-down :END:

org-table-fedit-ref-left

Shift the reference at point one row/hline down.

:PROPERTIES: :CUSTOM_ID: org-table-fedit-ref-left :END:

org-table-fedit-ref-right

Shift the reference at point one field to the left.

:PROPERTIES: :CUSTOM_ID: org-table-fedit-ref-right :END:

org-table-fedit-ref-up

Shift the reference at point one field to the right.

:PROPERTIES: :CUSTOM_ID: org-table-fedit-ref-up :END:

org-table-fedit-scroll (N)

Shift the reference at point one row/hline up.

:PROPERTIES: :CUSTOM_ID: org-table-fedit-scroll :END:

org-table-fedit-scroll-down (N)

:PROPERTIES: :CUSTOM_ID: org-table-fedit-scroll-down :END:

org-table-fedit-toggle-coordinates

:PROPERTIES: :CUSTOM_ID: org-table-fedit-toggle-coordinates :END:

org-table-fedit-toggle-ref-type

Toggle the display of coordinates in the referenced table.

:PROPERTIES: :CUSTOM_ID: org-table-fedit-toggle-ref-type :END:

org-table-field-info (arg)

Convert all references in the buffer from B3 to @3$2 and back.

:PROPERTIES: :CUSTOM_ID: org-table-field-info :END:

org-table-follow-field-mode (&optional arg)

Show info about the current field, and highlight any reference at point.

:PROPERTIES: :CUSTOM_ID: org-table-follow-field-mode :END:

org-table-get-stored-formulas (&optional noerror)

Minor mode to make the table field editor window follow the cursor.
When this mode is active, the field editor window will always show the
current field.  The mode exits automatically when the cursor leaves the
table (but see `org-table-exit-follow-field-mode-when-leaving-table').

:PROPERTIES: :CUSTOM_ID: org-table-get-stored-formulas :END:

org-table-goto-column (n &optional on-delim force)

Return an alist with the stored formulas directly after current table.

:PROPERTIES: :CUSTOM_ID: org-table-goto-column :END:

org-table-hline-and-move (&optional same-column)

Move the cursor to the Nth column in the current table line.
With optional argument ON-DELIM, stop with point before the left delimiter
of the field.
If there are less than N fields, just go to after the last delimiter.
However, when FORCE is non-nil, create new columns if necessary.

:PROPERTIES: :CUSTOM_ID: org-table-hline-and-move :END:

org-table-import (file arg)

Insert a hline and move to the row below that line.

:PROPERTIES: :CUSTOM_ID: org-table-import :END:

org-table-insert-column

Import FILE as a table.
The file is assumed to be tab-separated.  Such files can be produced by most
spreadsheet and database applications.  If no tabs (at least one per line)
are found, lines will be split on whitespace into fields.

:PROPERTIES: :CUSTOM_ID: org-table-insert-column :END:

org-table-insert-hline (&optional above)

Insert a new column into the table.

:PROPERTIES: :CUSTOM_ID: org-table-insert-hline :END:

org-table-insert-row (&optional arg)

Insert a horizontal-line below the current line into the table.
With prefix ABOVE, insert above the current line.

:PROPERTIES: :CUSTOM_ID: org-table-insert-row :END:

org-table-iterate (&optional arg)

Insert a new row above the current line into the table.
With prefix ARG, insert below the current line.

:PROPERTIES: :CUSTOM_ID: org-table-iterate :END:

org-table-iterate-buffer-tables

Recalculate the table until it does not change anymore.
The maximum number of iterations is 10, but you can choose a different value
with the prefix ARG.

:PROPERTIES: :CUSTOM_ID: org-table-iterate-buffer-tables :END:

org-table-kill-row

Iterate all tables in the buffer, to converge inter-table dependencies.

:PROPERTIES: :CUSTOM_ID: org-table-kill-row :END:

org-table-maybe-recalculate-line

Delete the current row or horizontal line from the table.

:PROPERTIES: :CUSTOM_ID: org-table-maybe-recalculate-line :END:

org-table-move-column (&optional left)

Recompute the current line if marked for it, and if we haven't just done it.

:PROPERTIES: :CUSTOM_ID: org-table-move-column :END:

org-table-move-column-left

Move the current column to the right.  With arg LEFT, move to the left.

:PROPERTIES: :CUSTOM_ID: org-table-move-column-left :END:

org-table-move-column-right

Move column to the left.

:PROPERTIES: :CUSTOM_ID: org-table-move-column-right :END:

org-table-move-row (&optional up)

Move column to the right.

:PROPERTIES: :CUSTOM_ID: org-table-move-row :END:

org-table-move-row-down

Move the current table line down.  With arg UP, move it up.

:PROPERTIES: :CUSTOM_ID: org-table-move-row-down :END:

org-table-move-row-up

Move table row down.

:PROPERTIES: :CUSTOM_ID: org-table-move-row-up :END:

org-table-next-field

Move table row up.

:PROPERTIES: :CUSTOM_ID: org-table-next-field :END:

org-table-next-row

Go to the next field in the current table, creating new lines as needed.
Before doing so, re-align the table if necessary.

:PROPERTIES: :CUSTOM_ID: org-table-next-row :END:

org-table-overlay-coordinates

Go to the next row (same column) in the current table.
Before doing so, re-align the table if necessary.

:PROPERTIES: :CUSTOM_ID: org-table-overlay-coordinates :END:

org-table-paste-rectangle

Add overlays to the table at point, to show row/column coordinates.

:PROPERTIES: :CUSTOM_ID: org-table-paste-rectangle :END:

org-table-previous-field

Paste a rectangular region into a table.
The upper right corner ends up in the current field.  All involved fields
will be overwritten.  If the rectangle does not fit into the present table,
the table is enlarged as needed.  The process ignores horizontal separator
lines.

:PROPERTIES: :CUSTOM_ID: org-table-previous-field :END:

org-table-recalculate (&optional all noalign)

Go to the previous field in the table.
Before doing so, re-align the table if necessary.

:PROPERTIES: :CUSTOM_ID: org-table-recalculate :END:

org-table-recalculate-buffer-tables

Recalculate the current table line by applying all stored formulas.
With prefix arg ALL, do this for all lines in the table.
With the prefix argument ALL is `(16)' (a double M-x universal-prefix M-x universal-prefix prefix), or if
it is the symbol `iterate', recompute the table until it no longer changes.
If NOALIGN is not nil, do not re-align the table after the computations
are done.  This is typically used internally to save time, if it is
known that the table will be realigned a little later anyway.

:PROPERTIES: :CUSTOM_ID: org-table-recalculate-buffer-tables :END:

org-table-rotate-recalc-marks (&optional newchar)

Recalculate all tables in the current buffer.

:PROPERTIES: :CUSTOM_ID: org-table-rotate-recalc-marks :END:

org-table-show-reference (&optional local)

Rotate the recalculation mark in the first column.
If in any row, the first field is not consistent with a mark,
insert a new column for the markers.
When there is an active region, change all the lines in the region,
after prompting for the marking character.
After each change, a message will be displayed indicating the meaning
of the new mark.

:PROPERTIES: :CUSTOM_ID: org-table-show-reference :END:

org-table-sort-lines (with-case &optional sorting-type)

Show the location/value of the $ expression at point.

:PROPERTIES: :CUSTOM_ID: org-table-sort-lines :END:

org-table-sum (&optional beg end nlast)

Sort table lines according to the column at point.

The position of point indicates the column to be used for
sorting, and the range of lines is the range between the nearest
horizontal separator lines, or the entire table of no such lines
exist.  If point is before the first column, you will be prompted
for the sorting column.  If there is an active region, the mark
specifies the first line and the sorting column, while point
should be in the last line to be included into the sorting.

The command then prompts for the sorting type which can be
alphabetically, numerically, or by time (as given in a time stamp
in the field).  Sorting in reverse order is also possible.

With prefix argument WITH-CASE, alphabetic sorting will be case-sensitive.

If SORTING-TYPE is specified when this function is called from a Lisp
program, no prompting will take place.  SORTING-TYPE must be a character,
any of (?a ?A ?n ?N ?t ?T) where the capital letter indicate that sorting
should be done in reverse order.

:PROPERTIES: :CUSTOM_ID: org-table-sum :END:

org-table-toggle-coordinate-overlays

Sum numbers in region of current table column.
The result will be displayed in the echo area, and will be available
as kill to be inserted with .

If there is an active region, it is interpreted as a rectangle and all
numbers in that rectangle will be summed.  If there is no active
region and point is located in a table column, sum all numbers in that
column.

If at least one number looks like a time HH:MM or HH:MM:SS, all other
numbers are assumed to be times as well (in decimal hours) and the
numbers are added as such.

If NLAST is a number, only the NLAST fields will actually be summed.

:PROPERTIES: :CUSTOM_ID: org-table-toggle-coordinate-overlays :END:

org-table-toggle-formula-debugger

Toggle the display of Row/Column numbers in tables.

:PROPERTIES: :CUSTOM_ID: org-table-toggle-formula-debugger :END:

org-table-transpose-table-at-point

Toggle the formula debugger in tables.

:PROPERTIES: :CUSTOM_ID: org-table-transpose-table-at-point :END:

org-table-wrap-region (arg)

Transpose orgmode table at point and eliminate hlines.
So a table like

| 1 | 2 | 4 | 5 |
|---+---+---+---|
| a | b | c | d |
| e | f | g | h |

will be transposed as

| 1 | a | e |
| 2 | b | f |
| 4 | c | g |
| 5 | d | h |

Note that horizontal lines disappeared.

:PROPERTIES: :CUSTOM_ID: org-table-wrap-region :END:

org-tags-sparse-tree (&optional todo-only match)

Wrap several fields in a column like a paragraph.
This is useful if you'd like to spread the contents of a field over several
lines, in order to keep the table compact.

If there is an active region, and both point and mark are in the same column,
the text in the column is wrapped to minimum width for the given number of
lines.  Generally, this makes the table more compact.  A prefix ARG may be
used to change the number of desired lines.  For example, `C-2 M-x org-table-wrap'
formats the selected text to two lines.  If the region was longer than two
lines, the remaining lines remain empty.  A negative prefix argument reduces
the current number of lines by that amount.  The wrapped text is pasted back
into the table.  If you formatted it to more lines than it was before, fields
further down in the table get overwritten - so you might need to make space in
the table first.

If there is no region, the current field is split at the cursor position and
the text fragment to the right of the cursor is prepended to the field one
line down.

If there is no region, but you specify a prefix ARG, the current field gets
blank, and the content is appended to the field above.

:PROPERTIES: :CUSTOM_ID: org-tags-sparse-tree :END:

org-tags-view (&optional todo-only match)

Create a sparse tree according to tags string MATCH.
MATCH can contain positive and negative selection of tags, like
"+WORK+URGENT-WITHBOSS".
If optional argument TODO-ONLY is non-nil, only select lines that are
also TODO lines.

:PROPERTIES: :CUSTOM_ID: org-tags-view :END:

org-tbl-menu (event)

Show all headlines for all `org-agenda-files' matching a TAGS criterion.
The prefix arg TODO-ONLY limits the search to TODO entries.

:PROPERTIES: :CUSTOM_ID: org-tbl-menu :END:

org-time-stamp (arg &optional inactive)

Tbl menu

:PROPERTIES: :CUSTOM_ID: org-time-stamp :END:

org-time-stamp-inactive (&optional arg)

Prompt for a date/time and insert a time stamp.
If the user specifies a time like HH:MM or if this command is
called with at least one prefix argument, the time stamp contains
the date and the time.  Otherwise, only the date is be included.

All parts of a date not specified by the user is filled in from
the current date/time.  So if you just press return without
typing anything, the time stamp will represent the current
date/time.

If there is already a timestamp at the cursor, it will be
modified.

With two universal prefix arguments, insert an active timestamp
with the current time without prompting the user.

:PROPERTIES: :CUSTOM_ID: org-time-stamp-inactive :END:

org-timeline (&optional dotodo)

Insert an inactive time stamp.
An inactive time stamp is enclosed in square brackets instead of angle
brackets.  It is inactive in the sense that it does not trigger agenda entries,
does not link to the calendar and cannot be changed with the S-cursor keys.
So these are more for recording a certain time/date.

:PROPERTIES: :CUSTOM_ID: org-timeline :END:

org-timer (&optional restart no-insert-p)

Show a time-sorted view of the entries in the current org file.
Only entries with a time stamp of today or later will be listed.  With
C-u prefix, all unfinished TODO items will also be shown,
under the current date.
If the buffer contains an active region, only check the region for
dates.

:PROPERTIES: :CUSTOM_ID: org-timer :END:

org-timer-cancel-timer

Insert a H:MM:SS string from the timer into the buffer.
The first time this command is used, the timer is started.  When used with
a C-u prefix, force restarting the timer.
When used with a double prefix argument C-u, change all the timer string
in the region by a fixed amount.  This can be used to recalibrate a timer
that was not started at the correct moment.

If NO-INSERT-P is non-nil, return the string instead of inserting
it in the buffer.

:PROPERTIES: :CUSTOM_ID: org-timer-cancel-timer :END:

org-timer-change-times-in-region (beg end delta)

Cancel the current timer.

:PROPERTIES: :CUSTOM_ID: org-timer-change-times-in-region :END:

org-timer-item (&optional arg)

Change all h:mm:ss time in region by a DELTA.

:PROPERTIES: :CUSTOM_ID: org-timer-item :END:

org-timer-pause-or-continue (&optional stop)

Insert a description-type item with the current timer value.

:PROPERTIES: :CUSTOM_ID: org-timer-pause-or-continue :END:

  • Access: C-c C-x ,, <menu-bar> <Org> <Dates and Scheduling> <Pause/Continue Timer>, <menu-bar> <Org> <Dates and Scheduling> <Stop Timer>
  • In file: org-timer.el
  • Search modifications

org-timer-reset-timers [Arg list not available until function definition is loaded.]

Pause or continue the relative timer.
With prefix arg STOP, stop it entirely.

:PROPERTIES: :CUSTOM_ID: org-timer-reset-timers :END:

org-timer-set-timer (&optional opt)

Documentation will be available after `org-timer.el' is loaded.

:PROPERTIES: :CUSTOM_ID: org-timer-set-timer :END:

org-timer-show-remaining-time

Prompt for a duration and set a timer.

If `org-timer-default-timer' is not zero, suggest this value as
the default duration for the timer.  If a timer is already set,
prompt the user if she wants to replace it.

Called with a numeric prefix argument, use this numeric value as
the duration of the timer.

Called with a `C-u' prefix arguments, use `org-timer-default-timer'
without prompting the user for a duration.

With two `C-u' prefix arguments, use `org-timer-default-timer'
without prompting the user for a duration and automatically
replace any running timer.

:PROPERTIES: :CUSTOM_ID: org-timer-show-remaining-time :END:

org-timer-start (&optional offset)

Display the remaining time before the timer ends.

:PROPERTIES: :CUSTOM_ID: org-timer-start :END:

org-timer-stop

Set the starting time for the relative timer to now.
When called with prefix argument OFFSET, prompt the user for an offset time,
with the default taken from a timer stamp at point, if any.
If OFFSET is a string or an integer, it is directly taken to be the offset
without user interaction.
When called with a double prefix arg, all timer strings in the active
region will be shifted by a specific amount.  You will be prompted for
the amount, with the default to make the first timer string in
the region 0:00:00.

:PROPERTIES: :CUSTOM_ID: org-timer-stop :END:

org-timestamp-down (&optional arg)

Stop the relative timer.

:PROPERTIES: :CUSTOM_ID: org-timestamp-down :END:

org-timestamp-down-day (&optional arg)

Decrease the date item at the cursor by one.
If the cursor is on the year, change the year.  If it is on the month,
the day or the time, change that.
With prefix ARG, change by that many units.

:PROPERTIES: :CUSTOM_ID: org-timestamp-down-day :END:

org-timestamp-up (&optional arg)

Decrease the date in the time stamp by one day.
With prefix ARG, change that many days.

:PROPERTIES: :CUSTOM_ID: org-timestamp-up :END:

org-timestamp-up-day (&optional arg)

Increase the date item at the cursor by one.
If the cursor is on the year, change the year.  If it is on the month,
the day or the time, change that.
With prefix ARG, change by that many units.

:PROPERTIES: :CUSTOM_ID: org-timestamp-up-day :END:

org-todo (&optional arg)

Increase the date in the time stamp by one day.
With prefix ARG, change that many days.

:PROPERTIES: :CUSTOM_ID: org-todo :END:

org-todo-list (arg)

Change the TODO state of an item.
The state of an item is given by a keyword at the start of the heading,
like
     *** TODO Write paper
     *** DONE Call mom

The different keywords are specified in the variable `org-todo-keywords'.
By default the available states are "TODO" and "DONE".
So for this example: when the item starts with TODO, it is changed to DONE.
When it starts with DONE, the DONE is removed.  And when neither TODO nor
DONE are present, add TODO at the beginning of the heading.

With C-u prefix arg, use completion to determine the new state.
With numeric prefix arg, switch to that state.
With a double C-u prefix, switch to the next set of TODO keywords (nextset).
With a triple C-u prefix, circumvent any state blocking.
With a numeric prefix arg of 0, inhibit note taking for the change.

For calling through lisp, arg is also interpreted in the following way:
'none             -> empty state
""(empty string)  -> switch to empty state
'done             -> switch to DONE
'nextset          -> switch to the next set of keywords
'previousset      -> switch to the previous set of keywords
"WAITING"         -> switch to the specified keyword, but only if it
                     really is a member of `org-todo-keywords'.

:PROPERTIES: :CUSTOM_ID: org-todo-list :END:

org-todo-yesterday (&optional arg)

Show all (not done) TODO entries from all agenda file in a single list.
The prefix arg can be used to select a specific TODO keyword and limit
the list to these.  When using C-u, you will be prompted
for a keyword.  A numeric prefix directly selects the Nth keyword in
`org-todo-keywords-1'.

:PROPERTIES: :CUSTOM_ID: org-todo-yesterday :END:

org-toggle-archive-tag (&optional find-done)

Like `org-todo' but the time of change will be 23:59 of yesterday.

:PROPERTIES: :CUSTOM_ID: org-toggle-archive-tag :END:

org-toggle-checkbox (&optional toggle-presence)

Toggle the archive tag for the current headline.
With prefix ARG, check all children of current headline and offer tagging
the children that do not contain any open TODO items.

:PROPERTIES: :CUSTOM_ID: org-toggle-checkbox :END:

org-toggle-comment

Toggle the checkbox in the current line.
With prefix arg TOGGLE-PRESENCE, add or remove checkboxes.  With
double prefix, set checkbox to [-].

When there is an active region, toggle status or presence of the
first checkbox there, and make every item inside have the same
status or presence, respectively.

If the cursor is in a headline, apply this to all checkbox items
in the text below the heading, taking as reference the first item
in subtree, ignoring drawers.

:PROPERTIES: :CUSTOM_ID: org-toggle-comment :END:

org-toggle-fixed-width-section (arg)

Change the COMMENT state of an entry.

:PROPERTIES: :CUSTOM_ID: org-toggle-fixed-width-section :END:

org-toggle-heading (&optional nstars)

Toggle the fixed-width export.
If there is no active region, the QUOTE keyword at the current headline is
inserted or removed.  When present, it causes the text between this headline
and the next to be exported as fixed-width text, and unmodified.
If there is an active region, this command adds or removes a colon as the
first character of this line.  If the first character of a line is a colon,
this line is also exported in fixed-width font.

:PROPERTIES: :CUSTOM_ID: org-toggle-heading :END:

org-toggle-inline-images (&optional include-linked)

Convert headings to normal text, or items or text to headings.
If there is no active region, only the current line is considered.

With a C-u prefix, convert the whole list at
point into heading.

In a region:

- If the first non blank line is an headline, remove the stars
  from all headlines in the region.

- If it is a normal line turn each and every normal line (i.e. not an
  heading or an item) in the region into a heading.

- If it is a plain list item, turn all plain list items into headings.

When converting a line into a heading, the number of stars is chosen
such that the lines become children of the current entry.  However,
when a prefix argument is given, its value determines the number of
stars to add.

:PROPERTIES: :CUSTOM_ID: org-toggle-inline-images :END:

org-toggle-item (arg)

Toggle the display of inline images.
INCLUDE-LINKED is passed to `org-display-inline-images'.

:PROPERTIES: :CUSTOM_ID: org-toggle-item :END:

Convert headings or normal lines to items, items to normal lines.
If there is no active region, only the current line is considered.

If the first non blank line in the region is an headline, convert
all headlines to items, shifting text accordingly.

If it is an item, convert all items to normal lines.

If it is normal text, change region into an item.  With a prefix
argument ARG, change each line in region into an item.

:PROPERTIES: :CUSTOM_ID: org-toggle-link-display :END:

  • Access: <menu-bar> <Org> <Hyperlinks> <Descriptive Links>, <menu-bar> <Org> <Hyperlinks> <Literal Links>
  • In file: org.el
  • Search modifications

org-toggle-ordered-property

Toggle the literal or descriptive display of links.

:PROPERTIES: :CUSTOM_ID: org-toggle-ordered-property :END:

  • Access: C-c C-x o, <menu-bar> <Org> <TODO Lists> <Do Children sequentially>, <menu-bar> <Org> <TODO Lists> <Do Children parallel>
  • In file: org.el
  • Search modifications

org-toggle-pretty-entities

Toggle the ORDERED property of the current entry.
For better visibility, you can track the value of this property with a tag.
See variable `org-track-ordered-property-with-tag'.

:PROPERTIES: :CUSTOM_ID: org-toggle-pretty-entities :END:

org-toggle-sticky-agenda (&optional arg)

Toggle the composition display of entities as UTF8 characters.

:PROPERTIES: :CUSTOM_ID: org-toggle-sticky-agenda :END:

org-toggle-time-stamp-overlays

Toggle `org-agenda-sticky'.

:PROPERTIES: :CUSTOM_ID: org-toggle-time-stamp-overlays :END:

org-toggle-timestamp-type

Toggle the use of custom time stamp formats.

:PROPERTIES: :CUSTOM_ID: org-toggle-timestamp-type :END:

org-tree-to-indirect-buffer (&optional arg)

Toggle the type ( or [inactive]) of a time stamp.

:PROPERTIES: :CUSTOM_ID: org-tree-to-indirect-buffer :END:

org-update-all-dblocks

Create indirect buffer and narrow it to current subtree.
With numerical prefix ARG, go up to this level and then take that tree.
If ARG is negative, go up that many levels.
If `org-indirect-buffer-display' is not `new-frame', the command removes the
indirect buffer previously made with this command, to avoid proliferation of
indirect buffers.  However, when you call the command with a C-u prefix, or
when `org-indirect-buffer-display' is `new-frame', the last buffer
is kept so that you can work with several indirect buffers at the same time.
If `org-indirect-buffer-display' is `dedicated-frame', the C-u prefix also
requests that a new frame be made for the new buffer, so that the dedicated
frame is not changed.

:PROPERTIES: :CUSTOM_ID: org-update-all-dblocks :END:

org-update-checkbox-count (&optional all)

Update all dynamic blocks in the buffer.
This function can be used in a hook.

:PROPERTIES: :CUSTOM_ID: org-update-checkbox-count :END:

org-update-dblock

Update the checkbox statistics in the current section.
This will find all statistic cookies like [57%] and [6/12] and
update them with the current numbers.

With optional prefix argument ALL, do this for the whole buffer.

:PROPERTIES: :CUSTOM_ID: org-update-dblock :END:

org-update-radio-target-regexp

Update the dynamic block at point.
This means to empty the block, parse for parameters and then call
the correct writing function.

:PROPERTIES: :CUSTOM_ID: org-update-radio-target-regexp :END:

org-update-statistics-cookies (all)

Find all radio targets in this file and update the regular expression.

:PROPERTIES: :CUSTOM_ID: org-update-statistics-cookies :END:

org-version (&optional here full message)

Update the statistics cookie, either from TODO or from checkboxes.
This should be called with the cursor in a line with a statistics cookie.

:PROPERTIES: :CUSTOM_ID: org-version :END:

org-w3m-copy-for-org-mode

Show the org-mode version in the echo area.
With prefix arg HERE, insert it at point.

:PROPERTIES: :CUSTOM_ID: org-w3m-copy-for-org-mode :END:

org-yank (&optional arg)

Copy current buffer content or active region with `org-mode' style links.
This will encode `link-title' and `link-location' with
`org-make-link-string', and insert the transformed test into the kill ring,
so that it can be yanked into an Org-mode buffer with links working correctly.

:PROPERTIES: :CUSTOM_ID: org-yank :END:

orgstruct++-mode (&optional arg)

Yank.  If the kill is a subtree, treat it specially.
This command will look at the current kill and check if is a single
subtree, or a series of subtrees[1].  If it passes the test, and if the
cursor is at the beginning of a line or after the stars of a currently
empty headline, then the yank is handled specially.  How exactly depends
on the value of the following variables, both set by default.

org-yank-folded-subtrees
    When set, the subtree(s) will be folded after insertion, but only
    if doing so would now swallow text after the yanked text.

org-yank-adjusted-subtrees
    When set, the subtree will be promoted or demoted in order to
    fit into the local outline tree structure, which means that the level
    will be adjusted so that it becomes the smaller one of the two
    *visible* surrounding headings.

Any prefix to this command will cause `yank' to be called directly with
no special treatment.  In particular, a simple C-u prefix will just
plainly yank the text as it is.

[1] The test checks if the first non-white line is a heading
    and if there are no other headings with fewer stars.

:PROPERTIES: :CUSTOM_ID: orgstruct++-mode :END:

orgstruct-error

Toggle `orgstruct-mode', the enhanced version of it.
In addition to setting orgstruct-mode, this also exports all
indentation and autofilling variables from org-mode into the
buffer.  It will also recognize item context in multiline items.

:PROPERTIES: :CUSTOM_ID: orgstruct-error :END:

orgstruct-mode (&optional arg)

Error when there is no default binding for a structure key.

:PROPERTIES: :CUSTOM_ID: orgstruct-mode :END:

orgtbl-create-or-convert-from-region (arg)

Toggle the minor mode `orgstruct-mode'.
This mode is for using Org-mode structure commands in other
modes.  The following keys behave as if Org-mode were active, if
the cursor is on a headline, or on a plain list item (both as
defined by Org-mode).

M-up        Move entry/item up
M-down	    Move entry/item down
M-left	    Promote
M-right	    Demote
M-S-up	    Move entry/item up
M-S-down    Move entry/item down
M-S-left    Promote subtree
M-S-right   Demote subtree
M-q	    Fill paragraph and items like in Org-mode
C-c ^	    Sort entries
C-c -	    Cycle list bullet
TAB         Cycle item visibility
M-RET       Insert new heading/item
S-M-RET     Insert new TODO heading / Checkbox item
C-c C-c     Set tags / toggle checkbox

:PROPERTIES: :CUSTOM_ID: orgtbl-create-or-convert-from-region :END:

orgtbl-ctrl-c-ctrl-c (arg)

Create table or convert region to table, if no conflicting binding.
This installs the table binding `C-c |', but only if there is no
conflicting binding to this key outside orgtbl-mode.

:PROPERTIES: :CUSTOM_ID: orgtbl-ctrl-c-ctrl-c :END:

orgtbl-error

If the cursor is inside a table, realign the table.
If it is a table to be sent away to a receiver, do it.
With prefix arg, also recompute table.

:PROPERTIES: :CUSTOM_ID: orgtbl-error :END:

orgtbl-insert-radio-table

Error when there is no default binding for a table key.

:PROPERTIES: :CUSTOM_ID: orgtbl-insert-radio-table :END:

orgtbl-mode (&optional arg)

Insert a radio table template appropriate for this major mode.

:PROPERTIES: :CUSTOM_ID: orgtbl-mode :END:

orgtbl-ret

The `org-mode' table editor as a minor mode for use in other modes.

:PROPERTIES: :CUSTOM_ID: orgtbl-ret :END:

orgtbl-self-insert-command (N)

Justification and field motion for `orgtbl-mode'.

:PROPERTIES: :CUSTOM_ID: orgtbl-self-insert-command :END:

orgtbl-send-table (&optional maybe)

Like `self-insert-command', use overwrite-mode for whitespace in tables.
If the cursor is in a table looking at whitespace, the whitespace is
overwritten, and the table is not marked as requiring realignment.

:PROPERTIES: :CUSTOM_ID: orgtbl-send-table :END:

orgtbl-tab (arg)

Send a transformed version of this table to the receiver position.
With argument MAYBE, fail quietly if no transformation is defined for
this table.

:PROPERTIES: :CUSTOM_ID: orgtbl-tab :END:

orgtbl-to-generic (table params)

Justification and field motion for `orgtbl-mode'.

:PROPERTIES: :CUSTOM_ID: orgtbl-to-generic :END:

orgtbl-toggle-comment

Convert the orgtbl-mode TABLE to some other format.
This generic routine can be used for many standard cases.
TABLE is a list, each entry either the symbol `hline' for a horizontal
separator line, or a list of fields for that line.
PARAMS is a property list of parameters that can influence the conversion.
For the generic converter, some parameters are obligatory: you need to
specify either :lfmt, or all of (:lstart :lend :sep).

Valid parameters are

:splice     When set to t, return only table body lines, don't wrap
            them into :tstart and :tend.  Default is nil.  When :splice
            is non-nil, this also means that the exporter should not look
            for and interpret header and footer sections.

:hline      String to be inserted on horizontal separation lines.
            May be nil to ignore hlines.

:sep        Separator between two fields
:remove-nil-lines Do not include lines that evaluate to nil.


Each in the following group may be either a string or a function
of no arguments returning a string:
:tstart     String to start the table.  Ignored when :splice is t.
:tend       String to end the table.  Ignored when :splice is t.
:lstart     String to start a new table line.
:llstart    String to start the last table line, defaults to :lstart.
:lend       String to end a table line
:llend      String to end the last table line, defaults to :lend.

Each in the following group may be a string, a function of one
argument (the field or line) returning a string, or a plist
mapping columns to either of the above:
:lfmt       Format for entire line, with enough %s to capture all fields.
            If this is present, :lstart, :lend, and :sep are ignored.
:llfmt      Format for the entire last line, defaults to :lfmt.
:fmt        A format to be used to wrap the field, should contain
            %s for the original field value.  For example, to wrap
            everything in dollars, you could use :fmt "$%s$".
            This may also be a property list with column numbers and
            formats. For example :fmt (2 "$%s$" 4 "%s%%")

:hlstart :hllstart :hlend :hllend :hlsep :hlfmt :hllfmt :hfmt
            Same as above, specific for the header lines in the table.
            All lines before the first hline are treated as header.
            If any of these is not present, the data line value is used.

This may be either a string or a function of two arguments:
:efmt       Use this format to print numbers with exponentials.
            The format should have %s twice for inserting mantissa
            and exponent, for example "%s\\times10^{%s}".  This
            may also be a property list with column numbers and
            formats.  :fmt will still be applied after :efmt.

In addition to this, the parameters :skip and :skipcols are always handled
directly by `orgtbl-send-table'.  See manual.

:PROPERTIES: :CUSTOM_ID: orgtbl-toggle-comment :END:

Options

Comment or uncomment the orgtbl at point.

:PROPERTIES: :CUSTOM_ID: options :END:

:PROPERTIES: :CUSTOM_ID: org-activate-links :END:

Types of links that should be activated in Org-mode files.
This is a list of symbols, each leading to the activation of a certain link
type.  In principle, it does not hurt to turn on most link types - there may
be a small gain when turning off unused link types.  The types are:

bracket   The recommended [[link][description]] or [[link]] links with hiding.
angle     Links in angular brackets that may contain whitespace like
          .
plain     Plain links in normal text, no whitespace, like http://google.com.
radio     Text that is matched by a radio target, see manual for details.
tag       Tag settings in a headline (link to tag search).
date      Time stamps (link to calendar).
footnote  Footnote labels.

Changing this variable requires a restart of Emacs to become effective.

org-adapt-indentation t

:PROPERTIES: :CUSTOM_ID: org-adapt-indentation :END:

Non-nil means adapt indentation to outline node level.

When this variable is set, Org assumes that you write outlines by
indenting text in each node to align with the headline (after the stars).
The following issues are influenced by this variable:

- When this is set and the *entire* text in an entry is indented, the
  indentation is increased by one space in a demotion command, and
  decreased by one in a promotion command.  If any line in the entry
  body starts with text at column 0, indentation is not changed at all.

- Property drawers and planning information is inserted indented when
  this variable s set.  When nil, they will not be indented.

- TAB indents a line relative to context.  The lines below a headline
  will be indented when this variable is set.

Note that this is all about true indentation, by adding and removing
space characters.  See also `org-indent.el' which does level-dependent
indentation in a virtual way, i.e. at display time in Emacs.

org-agenda-add-entry-text-descriptive-links t

:PROPERTIES: :CUSTOM_ID: org-agenda-add-entry-text-descriptive-links :END:

Non-nil means export org-links as descriptive links in agenda added text.
This variable applies to the text added to the agenda when
`org-agenda-add-entry-text-maxlines' is larger than 0.
When this variable nil, the URL will (also) be shown.

org-agenda-add-entry-text-maxlines 0

:PROPERTIES: :CUSTOM_ID: org-agenda-add-entry-text-maxlines :END:

Maximum number of entry text lines to be added to agenda.
This is only relevant when `org-agenda-add-entry-text' is part of
`org-agenda-before-write-hook', which it is by default.
When this is 0, nothing will happen.  When it is greater than 0, it
specifies the maximum number of lines that will be added for each entry
that is listed in the agenda view.

Note that this variable is not used during display, only when exporting
the agenda.  For agenda display, see the variables `org-agenda-entry-text-mode'
and `org-agenda-entry-text-maxlines'.

org-agenda-auto-exclude-function nil

:PROPERTIES: :CUSTOM_ID: org-agenda-auto-exclude-function :END:

A function called with a tag to decide if it is filtered on '/ RET'.
The sole argument to the function, which is called once for each
possible tag, is a string giving the name of the tag.  The
function should return either nil if the tag should be included
as normal, or "-" to exclude the tag.
Note that for the purpose of tag filtering, only the lower-case version of
all tags will be considered, so that this function will only ever see
the lower-case version of all tags.

org-agenda-block-separator 61

:PROPERTIES: :CUSTOM_ID: org-agenda-block-separator :END:

The separator between blocks in the agenda.
If this is a string, it will be used as the separator, with a newline added.
If it is a character, it will be repeated to fill the window width.
If nil the separator is disabled.  In `org-agenda-custom-commands' this
addresses the separator between the current and the previous block.

org-agenda-bulk-mark-char ">"

:PROPERTIES: :CUSTOM_ID: org-agenda-bulk-mark-char :END:

A single-character string to be used as the bulk mark.

org-agenda-category-icon-alist nil

:PROPERTIES: :CUSTOM_ID: org-agenda-category-icon-alist :END:

Alist of category icon to be displayed in agenda views.

Each entry should have the following format:

  (CATEGORY-REGEXP FILE-OR-DATA TYPE DATA-P PROPS)

Where CATEGORY-REGEXP is a regexp matching the categories where
the icon should be displayed.
FILE-OR-DATA either a file path or a string containing image data.

The other fields can be omitted safely if not needed:
TYPE indicates the image type.
DATA-P is a boolean indicating whether the FILE-OR-DATA string is
image data.
PROPS are additional image attributes to assign to the image,
like, e.g. `:ascent center'.

   ("Org" "/path/to/icon.png" nil nil :ascent center)

If you want to set the display properties yourself, just put a
list as second element:

  (CATEGORY-REGEXP (MY PROPERTY LIST))

For example, to display a 16px horizontal space for Emacs
category, you can use:

  ("Emacs" '(space . (:width (16))))

org-agenda-clock-consistency-checks (quote (:max-duration "10:00" ...

:PROPERTIES: :CUSTOM_ID: org-agenda-clock-consistency-checks :END:

This is a property list, with the following keys:

:max-duration    Mark clocking chunks that are longer than this time.
                 This is a time string like "HH:MM", or the number
                 of minutes as an integer.

:min-duration    Mark clocking chunks that are shorter that this.
                 This is a time string like "HH:MM", or the number
                 of minutes as an integer.

:max-gap         Mark gaps between clocking chunks that are longer than
                 this duration.  A number of minutes, or a string
                 like "HH:MM".

:gap-ok-around   List of times during the day which are usually not working
                 times.  When a gap is detected, but the gap contains any
                 of these times, the gap is *not* reported.  For example,
                 if this is ("4:00" "13:00") then gaps that contain
                 4:00 in the morning (i.e. the night) and 13:00
                 (i.e. a typical lunch time) do not cause a warning.
                 You should have at least one time during the night in this
                 list, or otherwise the first task each morning will trigger
                 a warning because it follows a long gap.

Furthermore, the following properties can be used to define faces for
issue display.

:default-face         the default face, if the specific face is undefined
:overlap-face         face for overlapping clocks
:gap-face             face for gaps between clocks
:no-end-time-face     face for incomplete clocks
:long-face            face for clock intervals that are too long
:short-face           face for clock intervals that are too short

:PROPERTIES: :CUSTOM_ID: org-agenda-clockreport-parameter-plist :END:

Property list with parameters for the clocktable in clockreport mode.
This is the display mode that shows a clock table in the daily/weekly
agenda, the properties for this dynamic block can be set here.
The usual clocktable parameters are allowed here, but you cannot set
the properties :name, :tstart, :tend, :block, and :scope - these will
be overwritten to make sure the content accurately reflects the
current display in the agenda.

org-agenda-cmp-user-defined nil

:PROPERTIES: :CUSTOM_ID: org-agenda-cmp-user-defined :END:

A function to define the comparison `user-defined'.
This function must receive two arguments, agenda entry a and b.
If a>b, return +1.  If a

org-agenda-columns-add-appointments-to-effort-sum nil

:PROPERTIES: :CUSTOM_ID: org-agenda-columns-add-appointments-to-effort-sum :END:

Non-nil means the duration of an appointment will add to day effort.
The property to which appointment durations will be added is the one given
in the option `org-effort-property'.  If an appointment does not have
an end time, `org-agenda-default-appointment-duration' will be used.  If that
is not set, an appointment without end time will not contribute to the time
estimate.

org-agenda-columns-compute-summary-properties t

:PROPERTIES: :CUSTOM_ID: org-agenda-columns-compute-summary-properties :END:

Non-nil means recompute all summary properties before column view.
When column view in the agenda is listing properties that have a summary
operator, it can go to all relevant buffers and recompute the summaries
there.  This can mean overhead for the agenda column view, but is necessary
to have thing up to date.
As a special case, a CLOCKSUM property also makes sure that the clock
computations are current.

org-agenda-columns-show-summaries t

:PROPERTIES: :CUSTOM_ID: org-agenda-columns-show-summaries :END:

Non-nil means show summaries for columns displayed in the agenda view.

org-agenda-compact-blocks nil

:PROPERTIES: :CUSTOM_ID: org-agenda-compact-blocks :END:

Non-nil means make the block agenda more compact.
This is done globally by leaving out lines like the agenda span
name and week number or the separator lines.

org-agenda-confirm-kill 1

:PROPERTIES: :CUSTOM_ID: org-agenda-confirm-kill :END:

When set, remote killing from the agenda buffer needs confirmation.
When t, a confirmation is always needed.  When a number N, confirmation is
only needed when the text to be killed contains more than N non-white lines.

org-agenda-current-time-string "now - - - - - - - - - - - - -...

:PROPERTIES: :CUSTOM_ID: org-agenda-current-time-string :END:

The string for the current time marker in the agenda.

org-agenda-custom-commands (quote (("n" "Agenda and all T...

:PROPERTIES: :CUSTOM_ID: org-agenda-custom-commands :END:

Custom commands for the agenda.
These commands will be offered on the splash screen displayed by the
agenda dispatcher \[org-agenda].  Each entry is a list like this:

   (key desc type match settings files)

key      The key (one or more characters as a string) to be associated
         with the command.
desc     A description of the command, when omitted or nil, a default
         description is built using MATCH.
type     The command type, any of the following symbols:
          agenda      The daily/weekly agenda.
          todo        Entries with a specific TODO keyword, in all agenda files.
          search      Entries containing search words entry or headline.
          tags        Tags/Property/TODO match in all agenda files.
          tags-todo   Tags/P/T match in all agenda files, TODO entries only.
          todo-tree   Sparse tree of specific TODO keyword in *current* file.
          tags-tree   Sparse tree with all tags matches in *current* file.
          occur-tree  Occur sparse tree for *current* file.
          ...         A user-defined function.
match    What to search for:
          - a single keyword for TODO keyword searches
          - a tags match expression for tags searches
          - a word search expression for text searches.
          - a regular expression for occur searches
          For all other commands, this should be the empty string.
settings  A list of option settings, similar to that in a let form, so like
          this: ((opt1 val1) (opt2 val2) ...).   The values will be
          evaluated at the moment of execution, so quote them when needed.
files     A list of files file to write the produced agenda buffer to
          with the command `org-store-agenda-views'.
          If a file name ends in ".html", an HTML version of the buffer
          is written out.  If it ends in ".ps", a postscript version is
          produced.  Otherwise, only the plain text is written to the file.

You can also define a set of commands, to create a composite agenda buffer.
In this case, an entry looks like this:

  (key desc (cmd1 cmd2 ...) general-settings-for-whole-set files)

where

desc   A description string to be displayed in the dispatcher menu.
cmd    An agenda command, similar to the above.  However, tree commands
       are not allowed, but instead you can get agenda and global todo list.
       So valid commands for a set are:
       (agenda "" settings)
       (alltodo "" settings)
       (stuck "" settings)
       (todo "match" settings files)
       (search "match" settings files)
       (tags "match" settings files)
       (tags-todo "match" settings files)

Each command can carry a list of options, and another set of options can be
given for the whole set of commands.  Individual command options take
precedence over the general options.

When using several characters as key to a command, the first characters
are prefix commands.  For the dispatcher to display useful information, you
should provide a description for the prefix, like

 (setq org-agenda-custom-commands
   '(("h" . "HOME + Name tag searches") ; describe prefix "h"
     ("hl" tags "+HOME+Lisa")
     ("hp" tags "+HOME+Peter")
     ("hk" tags "+HOME+Kim")))

org-agenda-day-face-function nil

:PROPERTIES: :CUSTOM_ID: org-agenda-day-face-function :END:

Function called to determine what face should be used to display a day.
The only argument passed to that function is the day. It should
returns a face, or nil if does not want to specify a face and let
the normal rules apply.

org-agenda-deadline-faces (quote ((1.0 . org-warning) (0...

:PROPERTIES: :CUSTOM_ID: org-agenda-deadline-faces :END:

Faces for showing deadlines in the agenda.
This is a list of cons cells.  The cdr of each cell is a face to be used,
and it can also just be like '(:foreground "yellow").
Each car is a fraction of the head-warning time that must have passed for
this the face in the cdr to be used for display.  The numbers must be
given in descending order.  The head-warning time is normally taken
from `org-deadline-warning-days', but can also be specified in the deadline
timestamp itself, like this:

   DEADLINE: <2007-08-13 Mon -8d>

You may use d for days, w for weeks, m for months and y for years.  Months
and years will only be treated in an approximate fashion (30.4 days for a
month and 365.24 days for a year).

org-agenda-deadline-leaders (quote ("Deadline: " "In %3d ...

:PROPERTIES: :CUSTOM_ID: org-agenda-deadline-leaders :END:

Text preceding deadline items in the agenda view.
This is a list with two strings.  The first applies when the item has its
deadline on the current day.  The second applies when it is in the past or
in the future, it may contain %d to capture how many days away the deadline
is (was).

org-agenda-default-appointment-duration nil

:PROPERTIES: :CUSTOM_ID: org-agenda-default-appointment-duration :END:

Default duration for appointments that only have a starting time.
When nil, no duration is specified in such cases.
When non-nil, this must be the number of minutes, e.g. 60 for one hour.

org-agenda-diary-file (quote diary-file)

:PROPERTIES: :CUSTOM_ID: org-agenda-diary-file :END:

File to which to add new entries with the `i' key in agenda and calendar.
When this is the symbol `diary-file', the functionality in the Emacs
calendar will be used to add entries to the `diary-file'.  But when this
points to a file, `org-agenda-diary-entry' will be used instead.

org-agenda-diary-sexp-prefix nil

:PROPERTIES: :CUSTOM_ID: org-agenda-diary-sexp-prefix :END:

A regexp that matches part of a diary sexp entry
which should be treated as scheduling/deadline information in
`org-agenda'.

For example, you can use this to extract the `diary-remind-message' from
`diary-remind' entries.

org-agenda-dim-blocked-tasks t

:PROPERTIES: :CUSTOM_ID: org-agenda-dim-blocked-tasks :END:

Non-nil means dim blocked tasks in the agenda display.
This causes some overhead during agenda construction, but if you
have turned on `org-enforce-todo-dependencies',
`org-enforce-todo-checkbox-dependencies', or any other blocking
mechanism, this will create useful feedback in the agenda.

Instead of t, this variable can also have the value `invisible'.
Then blocked tasks will be invisible and only become visible when
they become unblocked.  An exemption to this behavior is when a task is
blocked because of unchecked checkboxes below it.  Since checkboxes do
not show up in the agenda views, making this task invisible you remove any
trace from agenda views that there is something to do.  Therefore, a task
that is blocked because of checkboxes will never be made invisible, it
will only be dimmed.

org-agenda-entry-text-exclude-regexps nil

:PROPERTIES: :CUSTOM_ID: org-agenda-entry-text-exclude-regexps :END:

List of regular expressions to clean up entry text.
The complete matches of all regular expressions in this list will be
removed from entry text before it is shown in the agenda.

org-agenda-entry-text-maxlines 5

:PROPERTIES: :CUSTOM_ID: org-agenda-entry-text-maxlines :END:

Number of text lines to be added when `E' is pressed in the agenda.

Note that this variable only used during agenda display.  Add add entry text
when exporting the agenda, configure the variable
`org-agenda-add-entry-ext-maxlines'.

org-agenda-export-html-style ""

:PROPERTIES: :CUSTOM_ID: org-agenda-export-html-style :END:

The style specification for exported HTML Agenda files.
If this variable contains a string, it will replace the default 

or, if you want to keep the style in a file,

   

As the value of this option simply gets inserted into the HTML  header,
you can "misuse" it to also add other text to the header.  However,
 is required, if not present the variable will be ignored.

org-agenda-exporter-settings nil

:PROPERTIES: :CUSTOM_ID: org-agenda-exporter-settings :END:

Alist of variable/value pairs that should be active during agenda export.
This is a good place to set options for ps-print and for htmlize.
Note that the way this is implemented, the values will be evaluated
before assigned to the variables.  So make sure to quote values you do
*not* want evaluated, for example

   (setq org-agenda-exporter-settings
         '((ps-print-color-p 'black-white)))

org-agenda-file-regexp "\\`[^.].*\\.org\\'"

:PROPERTIES: :CUSTOM_ID: org-agenda-file-regexp :END:

Regular expression to match files for `org-agenda-files'.
If any element in the list in that variable contains a directory instead
of a normal file, all files in that directory that are matched by this
regular expression will be included.

org-agenda-files nil

:PROPERTIES: :CUSTOM_ID: org-agenda-files :END:

The files to be used for agenda display.
Entries may be added to this list with \[org-agenda-file-to-front] and removed with
\[org-remove-file].  You can also use customize to edit the list.

If an entry is a directory, all files in that directory that are matched by
`org-agenda-file-regexp' will be part of the file list.

If the value of the variable is not a list but a single file name, then
the list of agenda files is actually stored and maintained in that file, one
agenda file per line.  In this file paths can be given relative to
`org-directory'.  Tilde expansion and environment variable substitution
are also made.

org-agenda-filter-effort-default-operator "<"

:PROPERTIES: :CUSTOM_ID: org-agenda-filter-effort-default-operator :END:

The default operator for effort estimate filtering.
If you select an effort estimate limit without first pressing an operator,
this one will be used.

org-agenda-follow-indirect nil

:PROPERTIES: :CUSTOM_ID: org-agenda-follow-indirect :END:

Non-nil means `org-agenda-follow-mode' displays only the
current item's tree, in an indirect buffer.

org-agenda-format-date (quote org-agenda-format-date-...

:PROPERTIES: :CUSTOM_ID: org-agenda-format-date :END:

Format string for displaying dates in the agenda.
Used by the daily/weekly agenda and by the timeline.  This should be
a format string understood by `format-time-string', or a function returning
the formatted date as a string.  The function must take a single argument,
a calendar-style date list like (month day year).

org-agenda-hide-tags-regexp nil

:PROPERTIES: :CUSTOM_ID: org-agenda-hide-tags-regexp :END:

Regular expression used to filter away specific tags in agenda views.
This means that these tags will be present, but not be shown in the agenda
line.  Secondary filtering will still work on the hidden tags.
Nil means don't hide any tags.

org-agenda-inactive-leader "["

:PROPERTIES: :CUSTOM_ID: org-agenda-inactive-leader :END:

Text preceding item pulled into the agenda by inactive time stamps.
These entries are added to the agenda when pressing "[".

org-agenda-include-deadlines t

:PROPERTIES: :CUSTOM_ID: org-agenda-include-deadlines :END:

If non-nil, include entries within their deadline warning period.
Custom commands can set this variable in the options section.

org-agenda-include-diary nil

:PROPERTIES: :CUSTOM_ID: org-agenda-include-diary :END:

If non-nil, include in the agenda entries from the Emacs Calendar's diary.
Custom commands can set this variable in the options section.

org-agenda-insert-diary-extract-time nil

:PROPERTIES: :CUSTOM_ID: org-agenda-insert-diary-extract-time :END:

Non-nil means extract any time specification from the diary entry.

org-agenda-insert-diary-strategy (quote date-tree)

:PROPERTIES: :CUSTOM_ID: org-agenda-insert-diary-strategy :END:

Where in `org-agenda-diary-file' should new entries be added?
Valid values:

date-tree    in the date tree, as child of the date
top-level    as top-level entries at the end of the file.

org-agenda-jump-prefer-future (quote org-read-date-prefer-fu...

:PROPERTIES: :CUSTOM_ID: org-agenda-jump-prefer-future :END:

Should the agenda jump command prefer the future for incomplete dates?
The default is to do the same as configured in `org-read-date-prefer-future'.
But you can also set a deviating value here.
This may t or nil, or the symbol `org-read-date-prefer-future'.

org-agenda-log-mode-add-notes t

:PROPERTIES: :CUSTOM_ID: org-agenda-log-mode-add-notes :END:

Non-nil means add first line of notes to log entries in agenda views.
If a log item like a state change or a clock entry is associated with
notes, the first line of these notes will be added to the entry in the
agenda display.

org-agenda-log-mode-items (quote (closed clock))

:PROPERTIES: :CUSTOM_ID: org-agenda-log-mode-items :END:

List of items that should be shown in agenda log mode.
This list may contain the following symbols:

  closed    Show entries that have been closed on that day.
  clock     Show entries that have received clocked time on that day.
  state     Show all logged state changes.
Note that instead of changing this variable, you can also press `C-u l' in
the agenda to display all available LOG items temporarily.

org-agenda-menu-show-matcher t

:PROPERTIES: :CUSTOM_ID: org-agenda-menu-show-matcher :END:

Non-nil means show the match string in the agenda dispatcher menu.
When nil, the matcher string is not shown, but is put into the help-echo
property so than moving the mouse over the command shows it.
Setting it to nil is good if matcher strings are very long and/or if
you want to use two-column display (see `org-agenda-menu-two-column').

org-agenda-menu-two-column nil

:PROPERTIES: :CUSTOM_ID: org-agenda-menu-two-column :END:

Non-nil means, use two columns to show custom commands in the dispatcher.
If you use this, you probably want to set `org-agenda-menu-show-matcher'
to nil.

:PROPERTIES: :CUSTOM_ID: org-agenda-mouse-1-follows-link :END:

Non-nil means mouse-1 on a link will follow the link in the agenda.
A longer mouse click will still set point.  Does not work on XEmacs.
Needs to be set before org.el is loaded.

org-agenda-move-date-from-past-immediately-to-today t

:PROPERTIES: :CUSTOM_ID: org-agenda-move-date-from-past-immediately-to-today :END:

Non-nil means jump to today when moving a past date forward in time.
When using S-right in the agenda to move a a date forward, and the date
stamp currently points to the past, the first key press will move it
to today.  WHen nil, just move one day forward even if the date stays
in the past.

org-agenda-ndays nil

:PROPERTIES: :CUSTOM_ID: org-agenda-ndays :END:

Number of days to include in overview display.
Should be 1 or 7.
Obsolete, see `org-agenda-span'.

org-agenda-persistent-filter nil

:PROPERTIES: :CUSTOM_ID: org-agenda-persistent-filter :END:

When set, keep filters from one agenda view to the next.

org-agenda-persistent-marks nil

:PROPERTIES: :CUSTOM_ID: org-agenda-persistent-marks :END:

Non-nil means marked items will stay marked after a bulk action.
You can interactively and temporarily toggle by typing `p' when you
are prompted for a bulk action.

org-agenda-prefix-format (quote ((agenda . " %i %-12:c%...

:PROPERTIES: :CUSTOM_ID: org-agenda-prefix-format :END:

Format specifications for the prefix of items in the agenda views.
An alist with five entries, each for the different agenda types.  The
keys of the sublists are `agenda', `timeline', `todo', `search' and `tags'.
The values are format strings.

This format works similar to a printf format, with the following meaning:

  %c   the category of the item, "Diary" for entries from the diary,
       or as given by the CATEGORY keyword or derived from the file name
  %e   the effort required by the item
  %i   the icon category of the item, see `org-agenda-category-icon-alist'
  %T   the last tag of the item (ignore inherited tags, which come first)
  %t   the HH:MM time-of-day specification if one applies to the entry
  %s   Scheduling/Deadline information, a short string
  %(expression) Eval EXPRESSION and replace the control string
                by the result

All specifiers work basically like the standard `%s' of printf, but may
contain two additional characters:  a question mark just after the `%'
and a whitespace/punctuation character just before the final letter.

If the first character after `%' is a question mark, the entire field
will only be included if the corresponding value applies to the current
entry.  This is useful for fields which should have fixed width when
present, but zero width when absent.  For example, "%?-12t" will
result in a 12 character time field if a time of the day is specified,
but will completely disappear in entries which do not contain a time.

If there is punctuation or whitespace character just before the final
format letter, this character will be appended to the field value if
the value is not empty.  For example, the format "%-12:c" leads to
"Diary: " if the category is "Diary".  If the category were be
empty, no additional colon would be inserted.

The default value for the agenda sublist is "  %-12:c%?-12t% s",
which means:

- Indent the line with two space characters
- Give the category a 12 chars wide field, padded with whitespace on
  the right (because of `-').  Append a colon if there is a category
  (because of `:').
- If there is a time-of-day, put it into a 12 chars wide field.  If no
  time, don't put in an empty field, just skip it (because of '?').
- Finally, put the scheduling information.

See also the variables `org-agenda-remove-times-when-in-prefix' and
`org-agenda-remove-tags'.

Custom commands can set this variable in the options section.

org-agenda-query-register 111

:PROPERTIES: :CUSTOM_ID: org-agenda-query-register :END:

The register holding the current query string.
The purpose of this is that if you construct a query string interactively,
you can then use it to define a custom command.

org-agenda-remove-tags nil

:PROPERTIES: :CUSTOM_ID: org-agenda-remove-tags :END:

Non-nil means remove the tags from the headline copy in the agenda.
When this is the symbol `prefix', only remove tags when
`org-agenda-prefix-format' contains a `%T' specifier.

org-agenda-remove-timeranges-from-blocks nil

:PROPERTIES: :CUSTOM_ID: org-agenda-remove-timeranges-from-blocks :END:

Non-nil means remove time ranges specifications in agenda
items that span on several days.

org-agenda-remove-times-when-in-prefix t

:PROPERTIES: :CUSTOM_ID: org-agenda-remove-times-when-in-prefix :END:

Non-nil means remove duplicate time specifications in agenda items.
When the format `org-agenda-prefix-format' contains a `%t' specifier, a
time-of-day specification in a headline or diary entry is extracted and
placed into the prefix.  If this option is non-nil, the original specification
(a timestamp or -range, or just a plain time(range) specification like
11:30-4pm) will be removed for agenda display.  This makes the agenda less
cluttered.
The option can be t or nil.  It may also be the symbol `beg', indicating
that the time should only be removed when it is located at the beginning of
the headline/diary entry.

org-agenda-repeating-timestamp-show-all t

:PROPERTIES: :CUSTOM_ID: org-agenda-repeating-timestamp-show-all :END:

Non-nil means show all occurrences of a repeating stamp in the agenda.
When set to a list of strings, only show occurrences of repeating
stamps for these TODO keywords.  When nil, only one occurrence is
shown, either today or the nearest into the future.

org-agenda-restore-windows-after-quit nil

:PROPERTIES: :CUSTOM_ID: org-agenda-restore-windows-after-quit :END:

Non-nil means restore window configuration upon exiting agenda.
Before the window configuration is changed for displaying the agenda,
the current status is recorded.  When the agenda is exited with
`q' or `x' and this option is set, the old state is restored.  If
`org-agenda-window-setup' is `other-frame', the value of this
option will be ignored.

org-agenda-scheduled-leaders (quote ("Scheduled: " "Sched.%...

:PROPERTIES: :CUSTOM_ID: org-agenda-scheduled-leaders :END:

Text preceding scheduled items in the agenda view.
This is a list with two strings.  The first applies when the item is
scheduled on the current day.  The second applies when it has been scheduled
previously, it may contain a %d indicating that this is the nth time that
this item is scheduled, due to automatic rescheduling of unfinished items
for the following day.  So this number is one larger than the number of days
that passed since this item was scheduled first.

org-agenda-search-headline-for-time t

:PROPERTIES: :CUSTOM_ID: org-agenda-search-headline-for-time :END:

Non-nil means search headline for a time-of-day.
If the headline contains a time-of-day in one format or another, it will
be used to sort the entry into the time sequence of items for a day.
Some people have time stamps in the headline that refer to the creation
time or so, and then this produces an unwanted side effect.  If this is
the case for your, use this variable to turn off searching the headline
for a time.

org-agenda-search-view-always-boolean nil

:PROPERTIES: :CUSTOM_ID: org-agenda-search-view-always-boolean :END:

Non-nil means the search string is interpreted as individual parts.

The search string for search view can either be interpreted as a phrase,
or as a list of snippets that define a boolean search for a number of
strings.

When this is non-nil, the string will be split on whitespace, and each
snippet will be searched individually, and all must match in order to
select an entry.  A snippet is then a single string of non-white
characters, or a string in double quotes, or a regexp in {} braces.
If a snippet is preceded by "-", the snippet must *not* match.
"+" is syntactic sugar for positive selection.  Each snippet may
be found as a full word or a partial word, but see the variable
`org-agenda-search-view-force-full-words'.

When this is nil, search will look for the entire search phrase as one,
with each space character matching any amount of whitespace, including
line breaks.

Even when this is nil, you can still switch to Boolean search dynamically
by preceding the first snippet with "+" or "-".  If the first snippet
is a regexp marked with braces like "{abc}", this will also switch to
boolean search.

org-agenda-search-view-force-full-words nil

:PROPERTIES: :CUSTOM_ID: org-agenda-search-view-force-full-words :END:

Non-nil means, search words must be matches as complete words.
When nil, they may also match part of a word.

org-agenda-show-all-dates t

:PROPERTIES: :CUSTOM_ID: org-agenda-show-all-dates :END:

Non-nil means `org-agenda' shows every day in the selected range.
When nil, only the days which actually have entries are shown.

org-agenda-show-current-time-in-grid t

:PROPERTIES: :CUSTOM_ID: org-agenda-show-current-time-in-grid :END:

Non-nil means show the current time in the time grid.

org-agenda-show-inherited-tags t

:PROPERTIES: :CUSTOM_ID: org-agenda-show-inherited-tags :END:

Non-nil means show inherited tags in each agenda line.

org-agenda-show-outline-path t

:PROPERTIES: :CUSTOM_ID: org-agenda-show-outline-path :END:

Non-nil means show outline path in echo area after line motion.

org-agenda-skip-additional-timestamps-same-entry nil

:PROPERTIES: :CUSTOM_ID: org-agenda-skip-additional-timestamps-same-entry :END:

When nil, multiple same-day timestamps in entry make multiple agenda lines.
When non-nil, after the search for timestamps has matched once in an
entry, the rest of the entry will not be searched.

org-agenda-skip-archived-trees t

:PROPERTIES: :CUSTOM_ID: org-agenda-skip-archived-trees :END:

Non-nil means the agenda will skip any items located in archived trees.
An archived tree is a tree marked with the tag ARCHIVE.  The use of this
variable is no longer recommended, you should leave it at the value t.
Instead, use the key `v' to cycle the archives-mode in the agenda.

org-agenda-skip-comment-trees t

:PROPERTIES: :CUSTOM_ID: org-agenda-skip-comment-trees :END:

Non-nil means skip trees that start with the COMMENT keyword.
When nil, these trees are also scanned by agenda commands.

org-agenda-skip-deadline-if-done nil

:PROPERTIES: :CUSTOM_ID: org-agenda-skip-deadline-if-done :END:

Non-nil means don't show deadlines when the corresponding item is done.
When nil, the deadline is still shown and should give you a happy feeling.
This is relevant for the daily/weekly agenda.  And it applied only to the
actually date of the deadline.  Warnings about approaching and past-due
deadlines are always turned off when the item is DONE.

org-agenda-skip-deadline-prewarning-if-scheduled nil

:PROPERTIES: :CUSTOM_ID: org-agenda-skip-deadline-prewarning-if-scheduled :END:

Non-nil means skip deadline prewarning when entry is also scheduled.
This will apply on all days where a prewarning for the deadline would
be shown, but not at the day when the entry is actually due.  On that day,
the deadline will be shown anyway.
This variable may be set to nil, t, or a number which will then give
the number of days before the actual deadline when the prewarnings
should resume.
This can be used in a workflow where the first showing of the deadline will
trigger you to schedule it, and then you don't want to be reminded of it
because you will take care of it on the day when scheduled.

org-agenda-skip-function-global nil

:PROPERTIES: :CUSTOM_ID: org-agenda-skip-function-global :END:

Function to be called at each match during agenda construction.
If this function returns nil, the current match should not be skipped.
If the function decided to skip an agenda match, is must return the
buffer position from which the search should be continued.
This may also be a Lisp form, which will be evaluated.

This variable will be applied to every agenda match, including
tags/property searches and TODO lists.  So try to make the test function
do its checking as efficiently as possible.  To implement a skipping
condition just for specific agenda commands, use the variable
`org-agenda-skip-function' which can be set in the options section
of custom agenda commands.

org-agenda-skip-scheduled-if-deadline-is-shown nil

:PROPERTIES: :CUSTOM_ID: org-agenda-skip-scheduled-if-deadline-is-shown :END:

Non-nil means skip scheduling line if same entry shows because of deadline.
In the agenda of today, an entry can show up multiple times because
it is both scheduled and has a nearby deadline, and maybe a plain time
stamp as well.
When this variable is t, then only the deadline is shown and the fact that
the entry is scheduled today or was scheduled previously is not shown.
When this variable is nil, the entry will be shown several times.  When
the variable is the symbol `not-today', then skip scheduled previously,
but not scheduled today.

org-agenda-skip-scheduled-if-done nil

:PROPERTIES: :CUSTOM_ID: org-agenda-skip-scheduled-if-done :END:

Non-nil means don't show scheduled items in agenda when they are done.
This is relevant for the daily/weekly agenda, not for the TODO list.  And
it applies only to the actual date of the scheduling.  Warnings about
an item with a past scheduling dates are always turned off when the item
is DONE.

org-agenda-skip-timestamp-if-deadline-is-shown nil

:PROPERTIES: :CUSTOM_ID: org-agenda-skip-timestamp-if-deadline-is-shown :END:

Non-nil means skip timestamp line if same entry shows because of deadline.
In the agenda of today, an entry can show up multiple times
because it has both a plain timestamp and has a nearby deadline.
When this variable is t, then only the deadline is shown and the
fact that the entry has a timestamp for or including today is not
shown.  When this variable is nil, the entry will be shown
several times.

org-agenda-skip-timestamp-if-done nil

:PROPERTIES: :CUSTOM_ID: org-agenda-skip-timestamp-if-done :END:

Non-nil means don't select item by timestamp or -range if it is DONE.

org-agenda-skip-unavailable-files nil

:PROPERTIES: :CUSTOM_ID: org-agenda-skip-unavailable-files :END:

Non-nil means to just skip non-reachable files in `org-agenda-files'.
A nil value means to remove them, after a query, from the list.

org-agenda-sorting-strategy (quote ((agenda habit-down tim...

:PROPERTIES: :CUSTOM_ID: org-agenda-sorting-strategy :END:

Sorting structure for the agenda items of a single day.
This is a list of symbols which will be used in sequence to determine
if an entry should be listed before another entry.  The following
symbols are recognized:

time-up            Put entries with time-of-day indications first, early first
time-down          Put entries with time-of-day indications first, late first
category-keep      Keep the default order of categories, corresponding to the
		   sequence in `org-agenda-files'.
category-up        Sort alphabetically by category, A-Z.
category-down      Sort alphabetically by category, Z-A.
tag-up             Sort alphabetically by last tag, A-Z.
tag-down           Sort alphabetically by last tag, Z-A.
priority-up        Sort numerically by priority, high priority last.
priority-down      Sort numerically by priority, high priority first.
todo-state-up      Sort by todo state, tasks that are done last.
todo-state-down    Sort by todo state, tasks that are done first.
effort-up          Sort numerically by estimated effort, high effort last.
effort-down        Sort numerically by estimated effort, high effort first.
user-defined-up    Sort according to `org-agenda-cmp-user-defined', high last.
user-defined-down  Sort according to `org-agenda-cmp-user-defined', high first.
habit-up           Put entries that are habits first
habit-down         Put entries that are habits last
alpha-up           Sort headlines alphabetically
alpha-down         Sort headlines alphabetically, reversed

The different possibilities will be tried in sequence, and testing stops
if one comparison returns a "not-equal".  For example, the default
    '(time-up category-keep priority-down)
means: Pull out all entries having a specified time of day and sort them,
in order to make a time schedule for the current day the first thing in the
agenda listing for the day.  Of the entries without a time indication, keep
the grouped in categories, don't sort the categories, but keep them in
the sequence given in `org-agenda-files'.  Within each category sort by
priority.

Leaving out `category-keep' would mean that items will be sorted across
categories by priority.

Instead of a single list, this can also be a set of list for specific
contents, with a context symbol in the car of the list, any of
`agenda', `todo', `tags', `search' for the corresponding agenda views.

Custom commands can bind this variable in the options section.

org-agenda-span (quote week)

:PROPERTIES: :CUSTOM_ID: org-agenda-span :END:

Number of days to include in overview display.
Can be day, week, month, year, or any number of days.
Custom commands can set this variable in the options section.

org-agenda-start-on-weekday 1

:PROPERTIES: :CUSTOM_ID: org-agenda-start-on-weekday :END:

Non-nil means start the overview always on the specified weekday.
0 denotes Sunday, 1 denotes Monday etc.
When nil, always start on the current day.
Custom commands can set this variable in the options section.

org-agenda-start-with-clockreport-mode nil

:PROPERTIES: :CUSTOM_ID: org-agenda-start-with-clockreport-mode :END:

The initial value of clockreport-mode in a newly created agenda window.

org-agenda-start-with-entry-text-mode nil

:PROPERTIES: :CUSTOM_ID: org-agenda-start-with-entry-text-mode :END:

The initial value of entry-text-mode in a newly created agenda window.

org-agenda-start-with-follow-mode nil

:PROPERTIES: :CUSTOM_ID: org-agenda-start-with-follow-mode :END:

The initial value of follow mode in a newly created agenda window.

org-agenda-start-with-log-mode nil

:PROPERTIES: :CUSTOM_ID: org-agenda-start-with-log-mode :END:

The initial value of log-mode in a newly created agenda window.

org-agenda-sticky nil

:PROPERTIES: :CUSTOM_ID: org-agenda-sticky :END:

Non-nil means agenda q key will bury agenda buffers.
Agenda commands will then show existing buffer instead of generating new ones.
When nil, `q' will kill the single agenda buffer.

org-agenda-tags-column (if (featurep (quote xemacs)) ...

:PROPERTIES: :CUSTOM_ID: org-agenda-tags-column :END:

Shift tags in agenda items to this column.
If this number is positive, it specifies the column.  If it is negative,
it means that the tags should be flushright to that column.  For example,
-80 works well for a normal 80 character screen.

org-agenda-tags-todo-honor-ignore-options nil

:PROPERTIES: :CUSTOM_ID: org-agenda-tags-todo-honor-ignore-options :END:

Non-nil means honor todo-list ...ignore options also in tags-todo search.
The variables
   `org-agenda-todo-ignore-with-date',
   `org-agenda-todo-ignore-timestamp',
   `org-agenda-todo-ignore-scheduled',
   `org-agenda-todo-ignore-deadlines'
make the global TODO list skip entries that have time stamps of certain
kinds.  If this option is set, the same options will also apply for the
tags-todo search, which is the general tags/property matcher
restricted to unfinished TODO entries only.

org-agenda-text-search-extra-files nil

:PROPERTIES: :CUSTOM_ID: org-agenda-text-search-extra-files :END:

List of extra files to be searched by text search commands.
These files will be search in addition to the agenda files by the
commands `org-search-view' (`C-c a s') and `org-occur-in-agenda-files'.
Note that these files will only be searched for text search commands,
not for the other agenda views like todo lists, tag searches or the weekly
agenda.  This variable is intended to list notes and possibly archive files
that should also be searched by these two commands.
In fact, if the first element in the list is the symbol `agenda-archives',
than all archive files of all agenda files will be added to the search
scope.

org-agenda-time-grid (quote ((daily today require-t...

:PROPERTIES: :CUSTOM_ID: org-agenda-time-grid :END:

The settings for time grid for agenda display.
This is a list of three items.  The first item is again a list.  It contains
symbols specifying conditions when the grid should be displayed:

 daily         if the agenda shows a single day
 weekly        if the agenda shows an entire week
 today         show grid on current date, independent of daily/weekly display
 require-timed show grid only if at least one item has a time specification

The second item is a string which will be placed behind the grid time.

The third item is a list of integers, indicating the times that should have
a grid line.

org-agenda-time-leading-zero nil

:PROPERTIES: :CUSTOM_ID: org-agenda-time-leading-zero :END:

Non-nil means use leading zero for military times in agenda.
For example, 9:30am would become 09:30 rather than  9:30.

org-agenda-timegrid-use-ampm nil

:PROPERTIES: :CUSTOM_ID: org-agenda-timegrid-use-ampm :END:

When set, show AM/PM style timestamps on the timegrid.

org-agenda-timerange-leaders (quote ("" "(%d/%d): "))

:PROPERTIES: :CUSTOM_ID: org-agenda-timerange-leaders :END:

Text preceding timerange entries in the agenda view.
This is a list with two strings.  The first applies when the range
is entirely on one day.  The second applies if the range spans several days.
The strings may have two "%d" format specifiers which will be filled
with the sequence number of the days, and the total number of days in the
range, respectively.

org-agenda-todo-ignore-deadlines nil

:PROPERTIES: :CUSTOM_ID: org-agenda-todo-ignore-deadlines :END:

Non-nil means ignore some deadlined TODO items when making TODO list.
There are different motivations for using different values, please think
carefully when configuring this variable.

This applies when creating the global todo list.
Valid values are:

near    Don't show near deadline entries.  A deadline is near when it is
        closer than `org-deadline-warning-days' days.  The idea behind this
        is that such items will appear in the agenda anyway.

far     Don't show TODO entries where a deadline has been defined, but
        the deadline is not near.  This is useful if you don't want to
        use the todo list to figure out what to do now.

past    Don't show entries with a deadline timestamp for today or in the past.

future  Don't show entries with a deadline timestamp in the future, not even
        when they become `near' ones.  Use it with caution.

all     Ignore all TODO entries that do have a deadline.

t       Same as `near', for backward compatibility.

This variable can also have an integer as a value. See
`org-agenda-todo-ignore-timestamp' for more details.

See also `org-agenda-todo-ignore-with-date'.
See also the variable `org-agenda-tags-todo-honor-ignore-options' if you want
to make his option also apply to the tags-todo list.

org-agenda-todo-ignore-scheduled nil

:PROPERTIES: :CUSTOM_ID: org-agenda-todo-ignore-scheduled :END:

Non-nil means, ignore some scheduled TODO items when making TODO list.
This applies when creating the global todo list.
Valid values are:

past     Don't show entries scheduled today or in the past.

future   Don't show entries scheduled in the future.
         The idea behind this is that by scheduling it, you don't want to
         think about it until the scheduled date.

all      Don't show any scheduled entries in the global todo list.
         The idea behind this is that by scheduling it, you have already
         "taken care" of this item.

t        Same as `all', for backward compatibility.

This variable can also have an integer as a value. See
`org-agenda-todo-ignore-timestamp' for more details.

See also `org-agenda-todo-ignore-with-date'.
See also the variable `org-agenda-tags-todo-honor-ignore-options' if you want
to make his option also apply to the tags-todo list.

org-agenda-todo-ignore-timestamp nil

:PROPERTIES: :CUSTOM_ID: org-agenda-todo-ignore-timestamp :END:

Non-nil means don't show entries with a timestamp.
This applies when creating the global todo list.
Valid values are:

past     Don't show entries for today or in the past.

future   Don't show entries with a timestamp in the future.
         The idea behind this is that if it has a future
         timestamp, you don't want to think about it until the
         date.

all      Don't show any entries with a timestamp in the global todo list.
         The idea behind this is that by setting a timestamp, you
         have already "taken care" of this item.

This variable can also have an integer as a value. If positive (N),
todos with a timestamp N or more days in the future will be ignored. If
negative (-N), todos with a timestamp N or more days in the past will be
ignored. If 0, todos with a timestamp either today or in the future will
be ignored. For example, a value of -1 will exclude todos with a
timestamp in the past (yesterday or earlier), while a value of 7 will
exclude todos with a timestamp a week or more in the future.

See also `org-agenda-todo-ignore-with-date'.
See also the variable `org-agenda-tags-todo-honor-ignore-options' if you want
to make his option also apply to the tags-todo list.

org-agenda-todo-ignore-with-date nil

:PROPERTIES: :CUSTOM_ID: org-agenda-todo-ignore-with-date :END:

Non-nil means don't show entries with a date in the global todo list.
You can use this if you prefer to mark mere appointments with a TODO keyword,
but don't want them to show up in the TODO list.
When this is set, it also covers deadlines and scheduled items, the settings
of `org-agenda-todo-ignore-scheduled' and `org-agenda-todo-ignore-deadlines'
will be ignored.
See also the variable `org-agenda-tags-todo-honor-ignore-options'.

org-agenda-todo-keyword-format "%-1s"

:PROPERTIES: :CUSTOM_ID: org-agenda-todo-keyword-format :END:

Format for the TODO keyword in agenda lines.
Set this to something like "%-12s" if you want all TODO keywords
to occupy a fixed space in the agenda display.

org-agenda-todo-list-sublevels t

:PROPERTIES: :CUSTOM_ID: org-agenda-todo-list-sublevels :END:

Non-nil means check also the sublevels of a TODO entry for TODO entries.
When nil, the sublevels of a TODO entry are not checked, resulting in
potentially much shorter TODO lists.

org-agenda-use-time-grid t

:PROPERTIES: :CUSTOM_ID: org-agenda-use-time-grid :END:

Non-nil means show a time grid in the agenda schedule.
A time grid is a set of lines for specific times (like every two hours between
8:00 and 20:00).  The items scheduled for a day at specific times are
sorted in between these lines.
For details about when the grid will be shown, and what it will look like, see
the variable `org-agenda-time-grid'.

org-agenda-weekend-days (quote (6 0))

:PROPERTIES: :CUSTOM_ID: org-agenda-weekend-days :END:

Which days are weekend?
These days get the special face `org-agenda-date-weekend' in the agenda
and timeline buffers.

org-agenda-window-frame-fractions (quote (0.5 . 0.75))

:PROPERTIES: :CUSTOM_ID: org-agenda-window-frame-fractions :END:

The min and max height of the agenda window as a fraction of frame height.
The value of the variable is a cons cell with two numbers between 0 and 1.
It only matters if `org-agenda-window-setup' is `reorganize-frame'.

org-agenda-window-setup (quote reorganize-frame)

:PROPERTIES: :CUSTOM_ID: org-agenda-window-setup :END:

How the agenda buffer should be displayed.
Possible values for this option are:

current-window    Show agenda in the current window, keeping all other windows.
other-window      Use `switch-to-buffer-other-window' to display agenda.
reorganize-frame  Show only two windows on the current frame, the current
                  window and the agenda.
other-frame       Use `switch-to-buffer-other-frame' to display agenda.
                  Also, when exiting the agenda, kill that frame.
See also the variable `org-agenda-restore-windows-after-quit'.

org-agenda-with-colors t

:PROPERTIES: :CUSTOM_ID: org-agenda-with-colors :END:

Non-nil means use colors in agenda views.

org-allow-promoting-top-level-subtree nil

:PROPERTIES: :CUSTOM_ID: org-allow-promoting-top-level-subtree :END:

When non-nil, allow promoting a top level subtree.
The leading star of the top level headline will be replaced
by a #.

org-alphabetical-lists nil

:PROPERTIES: :CUSTOM_ID: org-alphabetical-lists :END:

Non-nil means single character alphabetical bullets are allowed.
Both uppercase and lowercase are handled.  Lists with more than
26 items will fallback to standard numbering.  Alphabetical
counters like "[@c]" will be recognized.

org-archive-default-command (quote org-archive-subtree)

:PROPERTIES: :CUSTOM_ID: org-archive-default-command :END:

The default archiving command.

org-archive-location "%s_archive::"

:PROPERTIES: :CUSTOM_ID: org-archive-location :END:

The location where subtrees should be archived.

The value of this variable is a string, consisting of two parts,
separated by a double-colon.  The first part is a filename and
the second part is a headline.

When the filename is omitted, archiving happens in the same file.
%s in the filename will be replaced by the current file
name (without the directory part).  Archiving to a different file
is useful to keep archived entries from contributing to the
Org-mode Agenda.

The archived entries will be filed as subtrees of the specified
headline.  When the headline is omitted, the subtrees are simply
filed away at the end of the file, as top-level entries.  Also in
the heading you can use %s to represent the file name, this can be
useful when using the same archive for a number of different files.

Here are a few examples:
"%s_archive::"
	If the current file is Projects.org, archive in file
	Projects.org_archive, as top-level trees.  This is the default.

"::* Archived Tasks"
	Archive in the current file, under the top-level headline
	"* Archived Tasks".

"~/org/archive.org::"
	Archive in file ~/org/archive.org (absolute path), as top-level trees.

"~/org/archive.org::* From %s"
	Archive in file ~/org/archive.org (absolute path), under headlines
        "From FILENAME" where file name is the current file name.

"~/org/datetree.org::datetree/* Finished Tasks"
        The "datetree/" string is special, signifying to archive
        items to the datetree.  Items are placed in either the CLOSED
        date of the item, or the current date if there is no CLOSED date.
        The heading will be a subentry to the current date.  There doesn't
        need to be a heading, but there always needs to be a slash after
        datetree.  For example, to store archived items directly in the
        datetree, use "~/org/datetree.org::datetree/".

"basement::** Finished Tasks"
	Archive in file ./basement (relative path), as level 3 trees
	below the level 2 heading "** Finished Tasks".

You may set this option on a per-file basis by adding to the buffer a
line like

#+ARCHIVE: basement::** Finished Tasks

You may also define it locally for a subtree by setting an ARCHIVE property
in the entry.  If such a property is found in an entry, or anywhere up
the hierarchy, it will be used.

org-archive-mark-done nil

:PROPERTIES: :CUSTOM_ID: org-archive-mark-done :END:

Non-nil means mark entries as DONE when they are moved to the archive file.
This can be a string to set the keyword to use.  When t, Org-mode will
use the first keyword in its list that means done.

org-archive-reversed-order nil

:PROPERTIES: :CUSTOM_ID: org-archive-reversed-order :END:

Non-nil means make the tree first child under the archive heading, not last.

org-archive-save-context-info (quote (time file olpath categ...

:PROPERTIES: :CUSTOM_ID: org-archive-save-context-info :END:

Parts of context info that should be stored as properties when archiving.
When a subtree is moved to an archive file, it loses information given by
context, like inherited tags, the category, and possibly also the TODO
state (depending on the variable `org-archive-mark-done').
This variable can be a list of any of the following symbols:

time       The time of archiving.
file       The file where the entry originates.
ltags      The local tags, in the headline of the subtree.
itags      The tags the subtree inherits from further up the hierarchy.
todo       The pre-archive TODO state.
category   The category, taken from file name or #+CATEGORY lines.
olpath     The outline path to the item.  These are all headlines above
           the current item, separated by /, like a file path.

For each symbol present in the list, a property will be created in
the archived entry, with a prefix "ARCHIVE_", to remember this
information.

org-archive-sibling-heading "Archive"

:PROPERTIES: :CUSTOM_ID: org-archive-sibling-heading :END:

Name of the local archive sibling that is used to archive entries locally.
Locally means: in the tree, under a sibling.
See `org-archive-to-archive-sibling' for more information.

org-archive-stamp-time t

:PROPERTIES: :CUSTOM_ID: org-archive-stamp-time :END:

Non-nil means add a time stamp to entries moved to an archive file.
This variable is obsolete and has no effect anymore, instead add or remove
`time' from the variable `org-archive-save-context-info'.

org-archive-subtree-add-inherited-tags (quote infile)

:PROPERTIES: :CUSTOM_ID: org-archive-subtree-add-inherited-tags :END:

Non-nil means append inherited tags when archiving a subtree.

org-archive-tag "ARCHIVE"

:PROPERTIES: :CUSTOM_ID: org-archive-tag :END:

The tag that marks a subtree as archived.
An archived subtree does not open during visibility cycling, and does
not contribute to the agenda listings.
After changing this, font-lock must be restarted in the relevant buffers to
get the proper fontification.

org-attach-allow-inheritance t

:PROPERTIES: :CUSTOM_ID: org-attach-allow-inheritance :END:

Non-nil means allow attachment directories be inherited.

org-attach-auto-tag "ATTACH"

:PROPERTIES: :CUSTOM_ID: org-attach-auto-tag :END:

Tag that will be triggered automatically when an entry has an attachment.

org-attach-directory "data/"

:PROPERTIES: :CUSTOM_ID: org-attach-directory :END:

The directory where attachments are stored.
If this is a relative path, it will be interpreted relative to the directory
where the Org file lives.

org-attach-expert nil

:PROPERTIES: :CUSTOM_ID: org-attach-expert :END:

Non-nil means do not show the splash buffer with the attach dispatcher.

org-attach-file-list-property "Attachments"

:PROPERTIES: :CUSTOM_ID: org-attach-file-list-property :END:

The property used to keep a list of attachment belonging to this entry.
This is not really needed, so you may set this to nil if you don't want it.
Also, for entries where children inherit the directory, the list of
attachments is not kept in this property.

org-attach-method (quote cp)

:PROPERTIES: :CUSTOM_ID: org-attach-method :END:

The preferred method to attach a file.
Allowed values are:

mv    rename the file to move it into the attachment directory
cp    copy the file
ln    create a hard link.  Note that this is not supported
      on all systems, and then the result is not defined.
lns   create a symbol link.  Note that this is not supported
      on all systems, and then the result is not defined.

:PROPERTIES: :CUSTOM_ID: org-attach-store-link-p :END:

Non-nil means store a link to a file when attaching it.

org-auto-align-tags t

:PROPERTIES: :CUSTOM_ID: org-auto-align-tags :END:

Non-nil keeps tags aligned when modifying headlines.
Some operations (i.e. demoting) change the length of a headline and
therefore shift the tags around.  With this option turned on, after
each such operation the tags are again aligned to `org-tags-column'.

org-babel-exp-call-line-template ""

:PROPERTIES: :CUSTOM_ID: org-babel-exp-call-line-template :END:

Template used to export call lines.
This template may be customized to include the call line name
with any export markup.  The template is filled out using
`org-fill-template', and the following %keys may be used.

 line --- call line

An example value would be "\n: call: %line" to export the call line
wrapped in a verbatim environment.

Note: the results are inserted separately after the contents of
this template.

org-babel-exp-code-template "#+BEGIN_SRC %lang%flags\n%bod...

:PROPERTIES: :CUSTOM_ID: org-babel-exp-code-template :END:

Template used to export the body of code blocks.
This template may be customized to include additional information
such as the code block name, or the values of particular header
arguments.  The template is filled out using `org-fill-template',
and the following %keys may be used.

 lang ------ the language of the code block
 name ------ the name of the code block
 body ------ the body of the code block
 flags ----- the flags passed to the code block

In addition to the keys mentioned above, every header argument
defined for the code block may be used as a key and will be
replaced with its value.

org-babel-load-languages (quote ((emacs-lisp . t)))

:PROPERTIES: :CUSTOM_ID: org-babel-load-languages :END:

Languages which can be evaluated in Org-mode buffers.
This list can be used to load support for any of the languages
below, note that each language will depend on a different set of
system executables and/or Emacs modes.  When a language is
"loaded", then code blocks in that language can be evaluated
with `org-babel-execute-src-block' bound by default to C-c
C-c (note the `org-babel-no-eval-on-ctrl-c-ctrl-c' variable can
be set to remove code block evaluation from the C-c C-c
keybinding.  By default only Emacs Lisp (which has no
requirements) is loaded.

org-babel-lob-files (quote nil)

:PROPERTIES: :CUSTOM_ID: org-babel-lob-files :END:

Files used to populate the `org-babel-library-of-babel'.
To add files to this list use the `org-babel-lob-ingest' command.

org-babel-no-eval-on-ctrl-c-ctrl-c nil

:PROPERTIES: :CUSTOM_ID: org-babel-no-eval-on-ctrl-c-ctrl-c :END:

Remove code block evaluation from the C-c C-c key binding.

org-babel-noweb-wrap-end ">>"

:PROPERTIES: :CUSTOM_ID: org-babel-noweb-wrap-end :END:

String used to end a noweb reference in a code block.
See also `org-babel-noweb-wrap-start'.

org-babel-noweb-wrap-start "<<"

:PROPERTIES: :CUSTOM_ID: org-babel-noweb-wrap-start :END:

String used to begin a noweb reference in a code block.
See also `org-babel-noweb-wrap-end'.

org-babel-picolisp-cmd "pil"

:PROPERTIES: :CUSTOM_ID: org-babel-picolisp-cmd :END:

Name of command used to evaluate picolisp blocks.

org-babel-process-comment-text (function org-babel-trim)

:PROPERTIES: :CUSTOM_ID: org-babel-process-comment-text :END:

Function called to process raw Org-mode text collected to be
inserted as comments in tangled source-code files.  The function
should take a single string argument and return a string
result.  The default value is `org-babel-trim'.

org-babel-R-command "R --slave --no-save"

:PROPERTIES: :CUSTOM_ID: org-babel-R-command :END:

Name of command to use for executing R code.

org-babel-results-keyword "RESULTS"

:PROPERTIES: :CUSTOM_ID: org-babel-results-keyword :END:

Keyword used to name results generated by code blocks.
Should be either RESULTS or NAME however any capitalization may
be used.

org-babel-sh-var-quote-fmt "$(cat <<'BABEL_TABLE'\n%s\nBA...

:PROPERTIES: :CUSTOM_ID: org-babel-sh-var-quote-fmt :END:

Format string used to escape variables when passed to shell scripts.

:PROPERTIES: :CUSTOM_ID: org-babel-tangle-comment-format-beg :END:

Format of inserted comments in tangled code files.
The following format strings can be used to insert special
information into the output using `org-fill-template'.
%start-line --- the line number at the start of the code block
%file --------- the file from which the code block was tangled
%link --------- Org-mode style link to the code block
%source-name -- name of the code block

Whether or not comments are inserted during tangling is
controlled by the :comments header argument.

org-babel-tangle-comment-format-end "%source-name ends here"

:PROPERTIES: :CUSTOM_ID: org-babel-tangle-comment-format-end :END:

Format of inserted comments in tangled code files.
The following format strings can be used to insert special
information into the output using `org-fill-template'.
%start-line --- the line number at the start of the code block
%file --------- the file from which the code block was tangled
%link --------- Org-mode style link to the code block
%source-name -- name of the code block

Whether or not comments are inserted during tangling is
controlled by the :comments header argument.

org-babel-tangle-lang-exts (quote (("emacs-lisp" . "el"))...

:PROPERTIES: :CUSTOM_ID: org-babel-tangle-lang-exts :END:

Alist mapping languages to their file extensions.
The key is the language name, the value is the string that should
be inserted as the extension commonly used to identify files
written in this language.  If no entry is found in this list,
then the name of the language is used.

org-bbdb-anniversary-field (quote anniversary)

:PROPERTIES: :CUSTOM_ID: org-bbdb-anniversary-field :END:

The BBDB field which contains anniversaries.
The anniversaries are stored in the following format

YYYY-MM-DD Class-or-Format-String

where class is one of the customized classes for anniversaries;
birthday and wedding are predefined.  Format-String can take three
substitutions 1) the name of the record containing this
anniversary, 2) the number of years, and 3) an ordinal suffix for
the year.

Multiple anniversaries can be separated by \n.

org-bbdb-anniversary-format-alist (quote (("birthday" lambda (na...

:PROPERTIES: :CUSTOM_ID: org-bbdb-anniversary-format-alist :END:

How different types of anniversaries should be formatted.
An alist of elements (STRING . FORMAT) where STRING is the name of an
anniversary class and format is either:
1) A format string with the following substitutions (in order):
    - the name of the record containing this anniversary
    - the number of years
    - an ordinal suffix (st, nd, rd, th) for the year

2) A function to be called with three arguments: NAME YEARS SUFFIX
   (string int string) returning a string for the diary or nil.

3) An Emacs Lisp form that should evaluate to a string (or nil) in the
   scope of variables NAME, YEARS and SUFFIX (among others).

org-bbdb-default-anniversary-format "birthday"

:PROPERTIES: :CUSTOM_ID: org-bbdb-default-anniversary-format :END:

Default anniversary class.

org-bbdb-extract-date-fun (quote org-bbdb-anniv-extract-...

:PROPERTIES: :CUSTOM_ID: org-bbdb-extract-date-fun :END:

How to retrieve `month date year' from the anniversary field.

Customize if you have already filled your BBDB with dates
different from YYYY-MM-DD.  The function must return a list (month
date year).

org-beamer-column-view-format "%45ITEM %10BEAMER_env(Env) %1...

:PROPERTIES: :CUSTOM_ID: org-beamer-column-view-format :END:

Default column view format that should be used to fill the template.

org-beamer-environments-extra nil

:PROPERTIES: :CUSTOM_ID: org-beamer-environments-extra :END:

Environments triggered by tags in Beamer export.
Each entry has 4 elements:

name    Name of the environment
key     Selection key for `org-beamer-select-environment'
open    The opening template for the environment, with the following escapes
        %a   the action/overlay specification
        %A   the default action/overlay specification
        %o   the options argument of the template
        %h   the headline text
        %H   if there is headline text, that text in {} braces
        %U   if there is headline text, that text in [] brackets
        %x   the content of the BEAMER_extra property
close   The closing string of the environment.

org-beamer-fragile-re "\\\\\\(verb\\|lstinline\\)\\|...

:PROPERTIES: :CUSTOM_ID: org-beamer-fragile-re :END:

If this regexp matches in a frame, the frame is marked as fragile.

org-beamer-frame-default-options ""

:PROPERTIES: :CUSTOM_ID: org-beamer-frame-default-options :END:

Default options string to use for frames, should contains the [brackets].
And example for this is "[allowframebreaks]".

org-beamer-frame-level 1

:PROPERTIES: :CUSTOM_ID: org-beamer-frame-level :END:

The level that should be interpreted as a frame.
The levels above this one will be translated into a sectioning structure.
Setting this to 2 will allow sections, 3 will allow subsections as well.
You can set this to 4 as well, if you at the same time set
`org-beamer-use-parts' to make the top levels `part'.

org-beamer-inherited-properties nil

:PROPERTIES: :CUSTOM_ID: org-beamer-inherited-properties :END:

Properties that should be inherited during beamer export.

org-beamer-outline-frame-options nil

:PROPERTIES: :CUSTOM_ID: org-beamer-outline-frame-options :END:

Outline frame options appended after \begin{frame}.
You might want to put e.g. [allowframebreaks=0.9] here.  Remember to
include square brackets.

org-beamer-outline-frame-title "Outline"

:PROPERTIES: :CUSTOM_ID: org-beamer-outline-frame-title :END:

Default title of a frame containing an outline.

org-beamer-themes "\\usetheme{default}\\usecolor...

:PROPERTIES: :CUSTOM_ID: org-beamer-themes :END:

Default string to be used for extra heading stuff in beamer presentations.
When a beamer template is filled, this will be the default for
BEAMER_HEADER_EXTRA, which will be inserted just before \begin{document}.

org-beamer-use-parts nil

:PROPERTIES: :CUSTOM_ID: org-beamer-use-parts :END:


org-bibtex-autogen-keys nil

:PROPERTIES: :CUSTOM_ID: org-bibtex-autogen-keys :END:

Set to a truth value to use `bibtex-generate-autokey' to generate keys.

org-bibtex-export-arbitrary-fields nil

:PROPERTIES: :CUSTOM_ID: org-bibtex-export-arbitrary-fields :END:

When converting to bibtex allow fields not defined in `org-bibtex-fields'.
This only has effect if `org-bibtex-prefix' is defined, so as to
ensure that other org-properties, such as CATEGORY or LOGGING are
not placed in the exported bibtex entry.

org-bibtex-key-property "CUSTOM_ID"

:PROPERTIES: :CUSTOM_ID: org-bibtex-key-property :END:

Property that holds the bibtex key.
By default, this is CUSTOM_ID, which enables easy linking to
bibtex headlines from within an org file. This can be set to ID
to enable global links, but only with great caution, as global
IDs must be unique.

org-bibtex-no-export-tags nil

:PROPERTIES: :CUSTOM_ID: org-bibtex-no-export-tags :END:

List of tag(s) that should not be converted to keywords.
This variable is relevant only if `org-bibtex-export-tags-as-keywords` is t.

org-bibtex-prefix nil

:PROPERTIES: :CUSTOM_ID: org-bibtex-prefix :END:

Optional prefix for all bibtex property names.
For example setting to 'BIB_' would allow interoperability with fireforg.

org-bibtex-tags nil

:PROPERTIES: :CUSTOM_ID: org-bibtex-tags :END:

List of tag(s) that should be added to new bib entries.

org-bibtex-tags-are-keywords nil

:PROPERTIES: :CUSTOM_ID: org-bibtex-tags-are-keywords :END:

Convert the value of the keywords field to tags and vice versa.
If set to t, comma-separated entries in a bibtex entry's keywords
field will be converted to org tags. Note: spaces will be escaped
with underscores, and characters that are not permitted in org
tags will be removed.

If t, local tags in an org entry will be exported as a
comma-separated string of keywords when exported to bibtex. Tags
defined in `org-bibtex-tags' or `org-bibtex-no-export-tags' will
not be exported.

org-bibtex-treat-headline-as-title t

:PROPERTIES: :CUSTOM_ID: org-bibtex-treat-headline-as-title :END:

Treat headline text as title if title property is absent.
If an entry is missing a title property, use the headline text as
the property. If this value is t, `org-bibtex-check' will ignore
a missing title field.

org-bibtex-type-property-name "btype"

:PROPERTIES: :CUSTOM_ID: org-bibtex-type-property-name :END:

Property in which to store bibtex entry type (e.g., article).

org-blank-before-new-entry (quote ((heading . auto) (plai...

:PROPERTIES: :CUSTOM_ID: org-blank-before-new-entry :END:

Should `org-insert-heading' leave a blank line before new heading/item?
The value is an alist, with `heading' and `plain-list-item' as CAR,
and a boolean flag as CDR.  The cdr may also be the symbol `auto', in
which case Org will look at the surrounding headings/items and try to
make an intelligent decision whether to insert a blank line or not.

For plain lists, if the variable `org-empty-line-terminates-plain-lists' is
set, the setting here is ignored and no empty line is inserted, to avoid
breaking the list structure.

org-calc-default-modes (quote (calc-internal-prec 12 ...

:PROPERTIES: :CUSTOM_ID: org-calc-default-modes :END:

List with Calc mode settings for use in `calc-eval' for table formulas.
The list must contain alternating symbols (Calc modes variables and values).
Don't remove any of the default settings, just change the values.  Org-mode
relies on the variables to be present in the list.

org-calendar-agenda-action-key [107]

:PROPERTIES: :CUSTOM_ID: org-calendar-agenda-action-key :END:

The key to be installed in `calendar-mode-map' for agenda-action.
The command `org-agenda-action' will be bound to this key.  The
default is the character `k' because we use the same key in the agenda.

org-calendar-follow-timestamp-change t

:PROPERTIES: :CUSTOM_ID: org-calendar-follow-timestamp-change :END:

Non-nil means make the calendar window follow timestamp changes.
When a timestamp is modified and the calendar window is visible, it will be
moved to the new date.

org-calendar-insert-diary-entry-key [105]

:PROPERTIES: :CUSTOM_ID: org-calendar-insert-diary-entry-key :END:

The key to be installed in `calendar-mode-map' for adding diary entries.
This option is irrelevant until `org-agenda-diary-file' has been configured
to point to an Org-mode file.  When that is the case, the command
`org-agenda-diary-entry' will be bound to the key given here, by default
`i'.  In the calendar, `i' normally adds entries to `diary-file'.  So
if you want to continue doing this, you need to change this to a different
key.

org-calendar-to-agenda-key [99]

:PROPERTIES: :CUSTOM_ID: org-calendar-to-agenda-key :END:

The key to be installed in `calendar-mode-map' for switching to the agenda.
The command `org-calendar-goto-agenda' will be bound to this key.  The
default is the character `c' because then `c' can be used to switch back and
forth between agenda and calendar.

org-capture-bookmark t

:PROPERTIES: :CUSTOM_ID: org-capture-bookmark :END:

When non-nil, add a bookmark pointing at the last stored
position when capturing.

org-capture-templates nil

:PROPERTIES: :CUSTOM_ID: org-capture-templates :END:

Templates for the creation of new entries.

Each entry is a list with the following items:

keys         The keys that will select the template, as a string, characters
             only, for example "a" for a template to be selected with a
             single key, or "bt" for selection with two keys.  When using
             several keys, keys using the same prefix key must be together
             in the list and preceded by a 2-element entry explaining the
             prefix key, for example

                     ("b" "Templates for marking stuff to buy")

             The "C" key is used by default for quick access to the
             customization of the template variable.  But if you want to use
             that key for a template, you can.

description  A short string describing the template, will be shown during
             selection.

type         The type of entry.  Valid types are:
               entry       an Org-mode node, with a headline. Will be
                           filed as the child of the target entry or as
                           a top-level entry.
               item        a plain list item, will be placed in the
                           first plain list at the target
                           location.
               checkitem   a checkbox item.  This differs from the
                           plain list item only is so far as it uses a
                           different default template.
               table-line  a new line in the first table at target location.
               plain       text to be inserted as it is.

target       Specification of where the captured item should be placed.
             In Org-mode files, targets usually define a node.  Entries will
             become children of this node, other types will be added to the
             table or list in the body of this node.

             Most target specifications contain a file name.  If that file
             name is the empty string, it defaults to `org-default-notes-file'.
             A file can also be given as a variable, function, or Emacs Lisp
             form.

             Valid values are:

             (file "path/to/file")
                 Text will be placed at the beginning or end of that file

             (id "id of existing org entry")
                 File as child of this entry, or in the body of the entry

             (file+headline "path/to/file" "node headline")
                 Fast configuration if the target heading is unique in the file

             (file+olp "path/to/file" "Level 1 heading" "Level 2" ...)
                 For non-unique headings, the full path is safer

             (file+regexp  "path/to/file" "regexp to find location")
                 File to the entry matching regexp

             (file+datetree "path/to/file")
                 Will create a heading in a date tree for today's date

             (file+datetree+prompt "path/to/file")
                 Will create a heading in a date tree, prompts for date

             (file+function "path/to/file" function-finding-location)
                 A function to find the right location in the file

             (clock)
                File to the entry that is currently being clocked

             (function function-finding-location)
                Most general way, write your own function to find both
                file and location

template     The template for creating the capture item.  If you leave this
             empty, an appropriate default template will be used.  See below
             for more details.  Instead of a string, this may also be one of

                 (file "/path/to/template-file")
                 (function function-returning-the-template)

             in order to get a template from a file, or dynamically
             from a function.

The rest of the entry is a property list of additional options.  Recognized
properties are:

 :prepend            Normally newly captured information will be appended at
                     the target location (last child, last table line,
                     last list item...).  Setting this property will
                     change that.

 :immediate-finish   When set, do not offer to edit the information, just
                     file it away immediately.  This makes sense if the
                     template only needs information that can be added
                     automatically.

 :empty-lines        Set this to the number of lines the should be inserted
                     before and after the new item.  Default 0, only common
                     other value is 1.

 :empty-lines-before Set this to the number of lines the should be inserted
                     before the new item. Overrides :empty-lines for the
                     number lines inserted before.

 :empty-lines-after  Set this to the number of lines the should be inserted
                     after the new item. Overrides :empty-lines for the
                     number of lines inserted after.

 :clock-in           Start the clock in this item.

 :clock-keep         Keep the clock running when filing the captured entry.

 :clock-resume       Start the interrupted clock when finishing the capture.
                     Note that :clock-keep has precedence over :clock-resume.
                     When setting both to `t', the current clock will run and
                     the previous one will not be resumed.

 :unnarrowed         Do not narrow the target buffer, simply show the
                     full buffer.  Default is to narrow it so that you
                     only see the new stuff.

 :table-line-pos     Specification of the location in the table where the
                     new line should be inserted.  It should be a string like
                     "II-3", meaning that the new line should become the
                     third line before the second horizontal separator line.

 :kill-buffer        If the target file was not yet visited by a buffer when
                     capture was invoked, kill the buffer again after capture
                     is finalized.

The template defines the text to be inserted.  Often this is an
org-mode entry (so the first line should start with a star) that
will be filed as a child of the target headline.  It can also be
freely formatted text.  Furthermore, the following %-escapes will
be replaced with content and expanded in this order:

  %[pathname] insert the contents of the file given by `pathname'.
  %(sexp)     evaluate elisp `(sexp)' and replace with the result.
  %<...>      the result of format-time-string on the ... format specification.
  %t          time stamp, date only.
  %T          time stamp with date and time.
  %u, %U      like the above, but inactive time stamps.
  %a          annotation, normally the link created with `org-store-link'.
  %i          initial content, copied from the active region.  If %i is
              indented, the entire inserted text will be indented as well.
  %A          like %a, but prompt for the description part.
  %c          current kill ring head.
  %x          content of the X clipboard.
  %k          title of currently clocked task.
  %K          link to currently clocked task.
  %n          user name (taken from `user-full-name').
  %f          file visited by current buffer when org-capture was called.
  %F          full path of the file or directory visited by current buffer.
  %:keyword   specific information for certain link types, see below.
  %^g         prompt for tags, with completion on tags in target file.
  %^G         prompt for tags, with completion on all tags in all agenda files.
  %^t         like %t, but prompt for date.  Similarly %^T, %^u, %^U.
              You may define a prompt like %^{Please specify birthday.
  %^C         interactive selection of which kill or clip to use.
  %^L         like %^C, but insert as link.
  %^{prop}p   prompt the user for a value for property `prop'.
  %^{prompt}  prompt the user for a string and replace this sequence with it.
              A default value and a completion table ca be specified like this:
              %^{prompt|default|completion2|completion3|...}.
  %?          After completing the template, position cursor here.
  %\n         Insert the text entered at the nth %^{prompt}, where `n' is
              a number, starting from 1.

Apart from these general escapes, you can access information specific to the
link type that is created.  For example, calling `org-capture' in emails
or gnus will record the author and the subject of the message, which you
can access with "%:from" and "%:subject", respectively.  Here is a
complete list of what is recorded for each link type.

Link type               |  Available information
------------------------+------------------------------------------------------
bbdb                    |  %:type %:name %:company
vm, wl, mh, mew, rmail  |  %:type %:subject %:message-id
                        |  %:from %:fromname %:fromaddress
                        |  %:to   %:toname   %:toaddress
                        |  %:fromto (either "to NAME" or "from NAME")
                        |  %:date
                        |  %:date-timestamp (as active timestamp)
                        |  %:date-timestamp-inactive (as inactive timestamp)
gnus                    |  %:group, for messages also all email fields
w3, w3m                 |  %:type %:url
info                    |  %:type %:file %:node
calendar                |  %:type %:date

org-catch-invisible-edits nil

:PROPERTIES: :CUSTOM_ID: org-catch-invisible-edits :END:

Check if in invisible region before inserting or deleting a character.
Valid values are:

nil              Do not check, so just do invisible edits.
error            Throw an error and do nothing.
show             Make point visible, and do the requested edit.
show-and-error   Make point visible, then throw an error and abort the edit.
smart            Make point visible, and do insertion/deletion if it is
                 adjacent to visible text and the change feels predictable.
                 Never delete a previously invisible character or add in the
                 middle or right after an invisible region.  Basically, this
                 allows insertion and backward-delete right before ellipses.
                 FIXME: maybe in this case we should not even show?

org-clock-auto-clock-resolution (quote when-no-clock-is-runnin...

:PROPERTIES: :CUSTOM_ID: org-clock-auto-clock-resolution :END:

When to automatically resolve open clocks found in Org buffers.

org-clock-clocked-in-display (quote mode-line)

:PROPERTIES: :CUSTOM_ID: org-clock-clocked-in-display :END:

When clocked in for a task, org-mode can display the current
task and accumulated time in the mode line and/or frame title.
Allowed values are:

both         displays in both mode line and frame title
mode-line    displays only in mode line (default)
frame-title  displays only in frame title
nil          current clock is not displayed

org-clock-clocktable-default-properties ~(quote (:maxlevel 2

:PROPERTIES: :CUSTOM_ID: org-clock-clocktable-default-properties :END:

Default properties for new clocktables.
These will be inserted into the BEGIN line, to make it easy for users to
play with them.

org-clock-clocktable-formatter (quote org-clocktable-write-de...

:PROPERTIES: :CUSTOM_ID: org-clock-clocktable-formatter :END:

Function to turn clocking data into a table.
For more information, see `org-clocktable-write-default'.

org-clock-clocktable-language-setup (quote (("en" "File" "L" "Time...

:PROPERTIES: :CUSTOM_ID: org-clock-clocktable-language-setup :END:

Terms used in clocktable, translated to different languages.

org-clock-continuously nil

:PROPERTIES: :CUSTOM_ID: org-clock-continuously :END:

Non-nil means to start clocking from the last clock-out time, if any.

org-clock-file-time-cell-format "*%s*"

:PROPERTIES: :CUSTOM_ID: org-clock-file-time-cell-format :END:

Format string for the file time cells.

org-clock-frame-title-format (quote (t org-mode-line-string...

:PROPERTIES: :CUSTOM_ID: org-clock-frame-title-format :END:

The value for `frame-title-format' when clocking in.

When `org-clock-clocked-in-display' is set to 'frame-title
or 'both, clocking in will replace `frame-title-format' with
this value.  Clocking out will restore `frame-title-format'.

`org-frame-title-string' is a format string using the same
specifications than `frame-title-format', which see.

org-clock-goto-may-find-recent-task t

:PROPERTIES: :CUSTOM_ID: org-clock-goto-may-find-recent-task :END:

Non-nil means `org-clock-goto' can go to recent task if no active clock.

org-clock-heading-function nil

:PROPERTIES: :CUSTOM_ID: org-clock-heading-function :END:

When non-nil, should be a function to create `org-clock-heading'.
This is the string shown in the mode line when a clock is running.
The function is called with point at the beginning of the headline.

org-clock-history-length 5

:PROPERTIES: :CUSTOM_ID: org-clock-history-length :END:

Number of clock tasks to remember in history.

org-clock-idle-time nil

:PROPERTIES: :CUSTOM_ID: org-clock-idle-time :END:

When non-nil, resolve open clocks if the user is idle more than X minutes.

org-clock-in-resume nil

:PROPERTIES: :CUSTOM_ID: org-clock-in-resume :END:

If non-nil, resume clock when clocking into task with open clock.
When clocking into a task with a clock entry which has not been closed,
the clock can be resumed from that point.

org-clock-in-switch-to-state nil

:PROPERTIES: :CUSTOM_ID: org-clock-in-switch-to-state :END:

Set task to a special todo state while clocking it.
The value should be the state to which the entry should be
switched.  If the value is a function, it must take one
parameter (the current TODO state of the item) and return the
state to switch it to.

org-clock-into-drawer org-log-into-drawer

:PROPERTIES: :CUSTOM_ID: org-clock-into-drawer :END:

Should clocking info be wrapped into a drawer?
When t, clocking info will always be inserted into a :LOGBOOK: drawer.
If necessary, the drawer will be created.
When nil, the drawer will not be created, but used when present.
When an integer and the number of clocking entries in an item
reaches or exceeds this number, a drawer will be created.
When a string, it names the drawer to be used.

The default for this variable is the value of `org-log-into-drawer',
which see.

org-clock-modeline-total (quote auto)

:PROPERTIES: :CUSTOM_ID: org-clock-modeline-total :END:

Default setting for the time included for the mode line clock.
This can be overruled locally using the CLOCK_MODELINE_TOTAL property.
Allowed values are:

current  Only the time in the current instance of the clock
today    All time clocked into this task today
repeat   All time clocked into this task since last repeat
all      All time ever recorded for this task
auto     Automatically, either `all', or `repeat' for repeating tasks

org-clock-out-remove-zero-time-clocks nil

:PROPERTIES: :CUSTOM_ID: org-clock-out-remove-zero-time-clocks :END:

Non-nil means remove the clock line when the resulting time is zero.

org-clock-out-switch-to-state nil

:PROPERTIES: :CUSTOM_ID: org-clock-out-switch-to-state :END:

Set task to a special todo state after clocking out.
The value should be the state to which the entry should be
switched.  If the value is a function, it must take one
parameter (the current TODO state of the item) and return the
state to switch it to.

org-clock-out-when-done t

:PROPERTIES: :CUSTOM_ID: org-clock-out-when-done :END:

When non-nil, clock will be stopped when the clocked entry is marked DONE.
DONE here means any DONE-like state.
A nil value means clock will keep running until stopped explicitly with
`C-c C-x C-o', or until the clock is started in a different item.
Instead of t, this can also be a list of TODO states that should trigger
clocking out.

org-clock-persist nil

:PROPERTIES: :CUSTOM_ID: org-clock-persist :END:

When non-nil, save the running clock when Emacs is closed.
The clock is resumed when Emacs restarts.
When this is t, both the running clock, and the entire clock
history are saved.  When this is the symbol `clock', only the
running clock is saved.

When Emacs restarts with saved clock information, the file containing the
running clock as well as all files mentioned in the clock history will
be visited.
All this depends on running `org-clock-persistence-insinuate' in .emacs

org-clock-persist-file (convert-standard-filename "~/...

:PROPERTIES: :CUSTOM_ID: org-clock-persist-file :END:

File to save clock data to.

org-clock-persist-query-resume t

:PROPERTIES: :CUSTOM_ID: org-clock-persist-query-resume :END:

When non-nil, ask before resuming any stored clock during load.

org-clock-persist-query-save nil

:PROPERTIES: :CUSTOM_ID: org-clock-persist-query-save :END:

When non-nil, ask before saving the current clock on exit.

org-clock-report-include-clocking-task nil

:PROPERTIES: :CUSTOM_ID: org-clock-report-include-clocking-task :END:

When non-nil, include the current clocking task time in clock reports.

org-clock-resolve-expert nil

:PROPERTIES: :CUSTOM_ID: org-clock-resolve-expert :END:

Non-nil means do not show the splash buffer with the clock resolver.

org-clock-sound nil

:PROPERTIES: :CUSTOM_ID: org-clock-sound :END:

Sound that will used for notifications.
Possible values:

nil        no sound played.
t          standard Emacs beep
file name  play this sound file.  If not possible, fall back to beep

org-clock-string "CLOCK:"

:PROPERTIES: :CUSTOM_ID: org-clock-string :END:

String used as prefix for timestamps clocking work hours on an item.

org-clock-string-limit 0

:PROPERTIES: :CUSTOM_ID: org-clock-string-limit :END:

Maximum length of clock strings in the mode line.  0 means no limit.

org-clock-task-overrun-text nil

:PROPERTIES: :CUSTOM_ID: org-clock-task-overrun-text :END:

Extra mode line text to indicate that the clock is overrun.
The can be nil to indicate that instead of adding text, the clock time
should get a different face (`org-mode-line-clock-overrun').
When this is a string, it is prepended to the clock string as an indication,
also using the face `org-mode-line-clock-overrun'.

org-clock-total-time-cell-format "*%s*"

:PROPERTIES: :CUSTOM_ID: org-clock-total-time-cell-format :END:

Format string for the total time cells.

org-clocktable-defaults ~(list maxlevel 2

:PROPERTIES: :CUSTOM_ID: org-clocktable-defaults :END:

Default properties for clock tables.

org-clone-delete-id nil

:PROPERTIES: :CUSTOM_ID: org-clone-delete-id :END:

Remove ID property of clones of a subtree.
When non-nil, clones of a subtree don't inherit the ID property.
Otherwise they inherit the ID property with a new unique
identifier.

org-closed-string "CLOSED:"

:PROPERTIES: :CUSTOM_ID: org-closed-string :END:

String used as the prefix for timestamps logging closing a TODO entry.

org-coderef-label-format "(ref:%s)"

:PROPERTIES: :CUSTOM_ID: org-coderef-label-format :END:

The default coderef format.
This format string will be used to search for coderef labels in literal
examples (EXAMPLE and SRC blocks).  The format can be overwritten in
an individual literal example with the -l option, like

#+BEGIN_SRC pascal +n -r -l "((%s))"
...
#+END_SRC

If you want to use this for HTML export, make sure that the format does
not introduce special font-locking, and avoid the HTML special
characters `<', `>', and `&'.  The reason for this restriction is that
the labels are searched for only after htmlize has done its job.

org-columns-default-format "%25ITEM %TODO %3PRIORITY %TAG...

:PROPERTIES: :CUSTOM_ID: org-columns-default-format :END:

The default column format, if no other format has been defined.
This variable can be set on the per-file basis by inserting a line

#+COLUMNS: %25ITEM .....

org-columns-ellipses ".."

:PROPERTIES: :CUSTOM_ID: org-columns-ellipses :END:

The ellipses to be used when a field in column view is truncated.
When this is the empty string, as many characters as possible are shown,
but then there will be no visual indication that the field has been truncated.
When this is a string of length N, the last N characters of a truncated
field are replaced by this string.  If the column is narrower than the
ellipses string, only part of the ellipses string will be shown.

org-columns-modify-value-for-display-function nil

:PROPERTIES: :CUSTOM_ID: org-columns-modify-value-for-display-function :END:

Function that modifies values for display in column view.
For example, it can be used to cut out a certain part from a time stamp.
The function must take 2 arguments:

column-title    The title of the column (*not* the property name)
value           The value that should be modified.

The function should return the value that should be displayed,
or nil if the normal value should be used.

org-columns-skip-archived-trees t

:PROPERTIES: :CUSTOM_ID: org-columns-skip-archived-trees :END:

Non-nil means ignore archived trees when creating column view.

org-combined-agenda-icalendar-file "~/org.ics"

:PROPERTIES: :CUSTOM_ID: org-combined-agenda-icalendar-file :END:

The file name for the iCalendar file covering all agenda files.
This file is created with the command \[org-export-icalendar-all-agenda-files].
The file name should be absolute, the file will be overwritten without warning.

org-comment-string "COMMENT"

:PROPERTIES: :CUSTOM_ID: org-comment-string :END:

Entries starting with this keyword will never be exported.
An entry can be toggled between COMMENT and normal with
\[org-toggle-comment].
Changes become only effective after restarting Emacs.

org-complete-tags-always-offer-all-agenda-tags nil

:PROPERTIES: :CUSTOM_ID: org-complete-tags-always-offer-all-agenda-tags :END:

If non-nil, always offer completion for all tags of all agenda files.
Instead of customizing this variable directly, you might want to
set it locally for capture buffers, because there no list of
tags in that file can be created dynamically (there are none).

  (add-hook 'org-capture-mode-hook
            (lambda ()
              (set (make-local-variable
                    'org-complete-tags-always-offer-all-agenda-tags)
                   t)))

org-completion-fallback-command (quote hippie-expand)

:PROPERTIES: :CUSTOM_ID: org-completion-fallback-command :END:

The expansion command called by \[pcomplete] in normal context.
Normal means, no org-mode-specific context.

org-completion-use-ido nil

:PROPERTIES: :CUSTOM_ID: org-completion-use-ido :END:

Non-nil means use ido completion wherever possible.
Note that `ido-mode' must be active for this variable to be relevant.
If you decide to turn this variable on, you might well want to turn off
`org-outline-path-complete-in-steps'.
See also `org-completion-use-iswitchb'.

org-completion-use-iswitchb nil

:PROPERTIES: :CUSTOM_ID: org-completion-use-iswitchb :END:

Non-nil means use iswitchb completion wherever possible.
Note that `iswitchb-mode' must be active for this variable to be relevant.
If you decide to turn this variable on, you might well want to turn off
`org-outline-path-complete-in-steps'.
Note that this variable has only an effect if `org-completion-use-ido' is nil.

org-confirm-babel-evaluate t

:PROPERTIES: :CUSTOM_ID: org-confirm-babel-evaluate :END:

Confirm before evaluation.
Require confirmation before interactively evaluating code
blocks in Org-mode buffers.  The default value of this variable
is t, meaning confirmation is required for any code block
evaluation.  This variable can be set to nil to inhibit any
future confirmation requests.  This variable can also be set to a
function which takes two arguments the language of the code block
and the body of the code block.  Such a function should then
return a non-nil value if the user should be prompted for
execution or nil if no prompt is required.

Warning: Disabling confirmation may result in accidental
evaluation of potentially harmful code.  It may be advisable
remove code block execution from C-c C-c as further protection
against accidental code block evaluation.  The
`org-babel-no-eval-on-ctrl-c-ctrl-c' variable can be used to
remove code block execution from the C-c C-c keybinding.

:PROPERTIES: :CUSTOM_ID: org-confirm-elisp-link-function :END:

Non-nil means ask for confirmation before executing Emacs Lisp links.
Elisp links can be dangerous: just think about a link

     [[elisp:(shell-command "rm -rf ~/*")][Google Search]]

This link would show up in your Org-mode document as "Google Search",
but really it would remove your entire home directory.
Therefore we advise against setting this variable to nil.
Just change it to `y-or-n-p' if you want to confirm with a
single keystroke rather than having to type "yes".

:PROPERTIES: :CUSTOM_ID: org-confirm-elisp-link-not-regexp :END:

A regexp to skip confirmation for Elisp links.

:PROPERTIES: :CUSTOM_ID: org-confirm-shell-link-function :END:

Non-nil means ask for confirmation before executing shell links.
Shell links can be dangerous: just think about a link

     [[shell:rm -rf ~/*][Google Search]]

This link would show up in your Org-mode document as "Google Search",
but really it would remove your entire home directory.
Therefore we advise against setting this variable to nil.
Just change it to `y-or-n-p' if you want to confirm with a
single keystroke rather than having to type "yes".

:PROPERTIES: :CUSTOM_ID: org-confirm-shell-link-not-regexp :END:

A regexp to skip confirmation for shell links.

:PROPERTIES: :CUSTOM_ID: org-context-in-file-links :END:

Non-nil means file links from `org-store-link' contain context.
A search string will be added to the file name with :: as separator and
used to find the context when the link is activated by the command
`org-open-at-point'.  When this option is t, the entire active region
will be placed in the search string of the file link.  If set to a
positive integer, only the first n lines of context will be stored.

Using a prefix arg to the command \[org-store-link] (`org-store-link')
negates this setting for the duration of the command.

org-crypt-disable-auto-save (quote ask)

:PROPERTIES: :CUSTOM_ID: org-crypt-disable-auto-save :END:

What org-decrypt should do if `auto-save-mode' is enabled.

t        : Disable auto-save-mode for the current buffer
           prior to decrypting an entry.

nil      : Leave auto-save-mode enabled.
           This may cause data to be written to disk unencrypted!

'ask     : Ask user whether or not to disable auto-save-mode
           for the current buffer.

'encrypt : Leave auto-save-mode enabled for the current buffer,
           but automatically re-encrypt all decrypted entries
           *before* auto-saving.
           NOTE: This only works for entries which have a tag
           that matches `org-crypt-tag-matcher'.

org-crypt-key ""

:PROPERTIES: :CUSTOM_ID: org-crypt-key :END:

The default key to use when encrypting the contents of a heading.

This setting can also be overridden in the CRYPTKEY property.

org-crypt-tag-matcher "crypt"

:PROPERTIES: :CUSTOM_ID: org-crypt-tag-matcher :END:

The tag matcher used to find headings whose contents should be encrypted.

See the "Match syntax" section of the org manual for more details.

org-ctags-new-topic-template "* <<%t>>\n\n\n\n\n\n"

:PROPERTIES: :CUSTOM_ID: org-ctags-new-topic-template :END:

Text to insert when creating a new org file via opening a hyperlink.
The following patterns are replaced in the string:
    `%t' - replaced with the capitalized title of the hyperlink

org-ctags-path-to-ctags (case system-type (windows-nt ...

:PROPERTIES: :CUSTOM_ID: org-ctags-path-to-ctags :END:

Full path to the ctags executable file.

org-ctrl-k-protect-subtree nil

:PROPERTIES: :CUSTOM_ID: org-ctrl-k-protect-subtree :END:

Non-nil means, do not delete a hidden subtree with C-k.
When set to the symbol `error', simply throw an error when C-k is
used to kill (part-of) a headline that has hidden text behind it.
Any other non-nil value will result in a query to the user, if it is
OK to kill that hidden subtree.  When nil, kill without remorse.

org-cycle-emulate-tab t

:PROPERTIES: :CUSTOM_ID: org-cycle-emulate-tab :END:

Where should `org-cycle' emulate TAB.
nil         Never
white       Only in completely white lines
whitestart  Only at the beginning of lines, before the first non-white char
t           Everywhere except in headlines
exc-hl-bol  Everywhere except at the start of a headline
If TAB is used in a place where it does not emulate TAB, the current subtree
visibility is cycled.

org-cycle-global-at-bob nil

:PROPERTIES: :CUSTOM_ID: org-cycle-global-at-bob :END:

Cycle globally if cursor is at beginning of buffer and not at a headline.
This makes it possible to do global cycling without having to use S-TAB or
\[universal-argument] TAB.  For this special case to work, the first line of the buffer
must not be a headline - it may be empty or some other text.  When used in
this way, `org-cycle-hook' is disables temporarily, to make sure the
cursor stays at the beginning of the buffer.
When this option is nil, don't do anything special at the beginning
of the buffer.

org-cycle-include-plain-lists t

:PROPERTIES: :CUSTOM_ID: org-cycle-include-plain-lists :END:

When t, make TAB cycle visibility on plain list items.
Cycling plain lists works only when the cursor is on a plain list
item.  When the cursor is on an outline heading, plain lists are
treated as text.  This is the most stable way of handling this,
which is why it is the default.

When this is the symbol `integrate', then during cycling, plain
list items will *temporarily* be interpreted as outline headlines
with a level given by 1000+i where i is the indentation of the
bullet.  This setting can lead to strange effects when switching
visibility to `children', because the first "child" in a
subtree decides what children should be listed.  If that first
"child" is a plain list item with an implied large level
number, all true children and grand children of the outline
heading will be exposed in a children' view.

org-cycle-level-after-item/entry-creation t

:PROPERTIES: :CUSTOM_ID: org-cycle-level-after-item/entry-creation :END:

Non-nil means cycle entry level or item indentation in new empty entries.

When the cursor is at the end of an empty headline, i.e with only stars
and maybe a TODO keyword, TAB will then switch the entry to become a child,
and then all possible ancestor states, before returning to the original state.
This makes data entry extremely fast:  M-RET to create a new headline,
on TAB to make it a child, two or more tabs to make it a (grand-)uncle.

When the cursor is at the end of an empty plain list item, one TAB will
make it a subitem, two or more tabs will back up to make this an item
higher up in the item hierarchy.

org-cycle-level-faces t

:PROPERTIES: :CUSTOM_ID: org-cycle-level-faces :END:

Non-nil means level styles cycle after level `org-n-level-faces'.
Then so level org-n-level-faces+1 is styled like level 1.
If nil, then all levels >=org-n-level-faces are styled like
level org-n-level-faces

org-cycle-max-level nil

:PROPERTIES: :CUSTOM_ID: org-cycle-max-level :END:

Maximum level which should still be subject to visibility cycling.
Levels higher than this will, for cycling, be treated as text, not a headline.
When `org-odd-levels-only' is set, a value of N in this variable actually
means 2N-1 stars as the limiting headline.
When nil, cycle all levels.
Note that the limiting level of cycling is also influenced by
`org-inlinetask-min-level'.  When `org-cycle-max-level' is not set but
`org-inlinetask-min-level' is, cycling will be limited to levels one less
than its value.

org-cycle-open-archived-trees nil

:PROPERTIES: :CUSTOM_ID: org-cycle-open-archived-trees :END:

Non-nil means `org-cycle' will open archived trees.
An archived tree is a tree marked with the tag ARCHIVE.
When nil, archived trees will stay folded.  You can still open them with
normal outline commands like `show-all', but not with the cycling commands.

org-cycle-separator-lines 2

:PROPERTIES: :CUSTOM_ID: org-cycle-separator-lines :END:

Number of empty lines needed to keep an empty line between collapsed trees.
If you leave an empty line between the end of a subtree and the following
headline, this empty line is hidden when the subtree is folded.
Org-mode will leave (exactly) one empty line visible if the number of
empty lines is equal or larger to the number given in this variable.
So the default 2 means at least 2 empty lines after the end of a subtree
are needed to produce free space between a collapsed subtree and the
following headline.

If the number is negative, and the number of empty lines is at least -N,
all empty lines are shown.

Special case: when 0, never leave empty lines in collapsed view.

org-cycle-skip-children-state-if-no-children t

:PROPERTIES: :CUSTOM_ID: org-cycle-skip-children-state-if-no-children :END:

Non-nil means skip CHILDREN state in entries that don't have any.

org-deadline-string "DEADLINE:"

:PROPERTIES: :CUSTOM_ID: org-deadline-string :END:

String to mark deadline entries.
A deadline is this string, followed by a time stamp.  Should be a word,
terminated by a colon.  You can insert a schedule keyword and
a timestamp with \[org-deadline].
Changes become only effective after restarting Emacs.

org-deadline-warning-days 14

:PROPERTIES: :CUSTOM_ID: org-deadline-warning-days :END:

No. of days before expiration during which a deadline becomes active.
This variable governs the display in sparse trees and in the agenda.
When 0 or negative, it means use this number (the absolute value of it)
even if a deadline has a different individual lead time specified.

Custom commands can set this variable in the options section.

org-default-notes-file (convert-standard-filename "~/...

:PROPERTIES: :CUSTOM_ID: org-default-notes-file :END:

Default target for storing notes.
Used as a fall back file for org-remember.el and org-capture.el, for
templates that do not specify a target file.

org-default-priority 66

:PROPERTIES: :CUSTOM_ID: org-default-priority :END:

The default priority of TODO items.
This is the priority an item gets if no explicit priority is given.
When starting to cycle on an empty priority the first step in the cycle
depends on `org-priority-start-cycle-with-default'.  The resulting first
step priority must not exceed the range from `org-highest-priority' to
`org-lowest-priority' which means that `org-default-priority' has to be
in this range exclusive or inclusive the range boundaries.  Else the
first step refuses to set the default and the second will fall back
to (depending on the command used) the highest or lowest priority.

org-description-max-indent 20

:PROPERTIES: :CUSTOM_ID: org-description-max-indent :END:

Maximum indentation for the second line of a description list.
When the indentation would be larger than this, it will become
5 characters instead.

:PROPERTIES: :CUSTOM_ID: org-descriptive-links :END:

Non-nil means Org will display descriptive links.
E.g. [[http://orgmode.org][Org website]] will be displayed as
"Org Website", hiding the link itself and just displaying its
description.  When set to `nil', Org will display the full links
literally.

You can interactively set the value of this variable by calling
`org-toggle-link-display' or from the menu Org>Hyperlinks menu.

org-directory "~/org"

:PROPERTIES: :CUSTOM_ID: org-directory :END:

Directory with org files.
This is just a default location to look for Org files.  There is no need
at all to put your files into this directory.  It is only used in the
following situations:

1. When a remember template specifies a target file that is not an
   absolute path.  The path will then be interpreted relative to
   `org-directory'
2. When a remember note is filed away in an interactive way (when exiting the
   note buffer with `C-1 C-c C-c'.  The user is prompted for an org file,
   with `org-directory' as the default path.

org-display-custom-times nil

:PROPERTIES: :CUSTOM_ID: org-display-custom-times :END:

Non-nil means overlay custom formats over all time stamps.
The formats are defined through the variable `org-time-stamp-custom-formats'.
To turn this on on a per-file basis, insert anywhere in the file:
   #+STARTUP: customtime

:PROPERTIES: :CUSTOM_ID: org-display-internal-link-with-indirect-buffer :END:

Non-nil means use indirect buffer to display infile links.
Activating internal links (from one location in a file to another location
in the same file) normally just jumps to the location.  When the link is
activated with a \[universal-argument] prefix (or with mouse-3), the link is displayed in
another window.  When this option is set, the other window actually displays
an indirect buffer clone of the current buffer, to avoid any visibility
changes to the current buffer.

org-disputed-keys (quote (([(shift up)] . [(meta...

:PROPERTIES: :CUSTOM_ID: org-disputed-keys :END:

Keys for which Org-mode and other modes compete.
This is an alist, cars are the default keys, second element specifies
the alternative to use when `org-replace-disputed-keys' is t.

Keys can be specified in any syntax supported by `define-key'.
The value of this option takes effect only at Org-mode's startup,
therefore you'll have to restart Emacs to apply it after changing.

org-ditaa-jar-option "-jar"

:PROPERTIES: :CUSTOM_ID: org-ditaa-jar-option :END:

Option for the ditaa jar file.
Do not leave leading or trailing spaces in this string.

org-ditaa-jar-path (expand-file-name "ditaa.jar" ...

:PROPERTIES: :CUSTOM_ID: org-ditaa-jar-path :END:

Path to the ditaa jar executable.

org-doi-server-url "http://dx.doi.org/"

:PROPERTIES: :CUSTOM_ID: org-doi-server-url :END:

The URL of the DOI server.

org-drawers (quote ("PROPERTIES" "CLOCK" "...

:PROPERTIES: :CUSTOM_ID: org-drawers :END:

Names of drawers.  Drawers are not opened by cycling on the headline above.
Drawers only open with a TAB on the drawer line itself.  A drawer looks like
this:
   :DRAWERNAME:
   .....
   :END:
The drawer "PROPERTIES" is special for capturing properties through
the property API.

Drawers can be defined on the per-file basis with a line like:

#+DRAWERS: HIDDEN STATE PROPERTIES

org-edit-fixed-width-region-mode (quote artist-mode)

:PROPERTIES: :CUSTOM_ID: org-edit-fixed-width-region-mode :END:

The mode that should be used to edit fixed-width regions.
These are the regions where each line starts with a colon.

org-edit-src-content-indentation 2

:PROPERTIES: :CUSTOM_ID: org-edit-src-content-indentation :END:

Indentation for the content of a source code block.
This should be the number of spaces added to the indentation of the #+begin
line in order to compute the indentation of the block content after
editing it with \[org-edit-src-code].  Has no effect if
`org-src-preserve-indentation' is non-nil.

org-edit-src-persistent-message t

:PROPERTIES: :CUSTOM_ID: org-edit-src-persistent-message :END:

Non-nil means show persistent exit help message while editing src examples.
The message is shown in the header-line, which will be created in the
first line of the window showing the editing buffer.

org-edit-src-region-extra nil

:PROPERTIES: :CUSTOM_ID: org-edit-src-region-extra :END:

Additional regexps to identify regions for editing with `org-edit-src-code'.
For examples see the function `org-edit-src-find-region-and-lang'.
The regular expression identifying the begin marker should end with a newline,
and the regexp marking the end line should start with a newline, to make sure
there are kept outside the narrowed region.

org-edit-timestamp-down-means-later nil

:PROPERTIES: :CUSTOM_ID: org-edit-timestamp-down-means-later :END:

Non-nil means S-down will increase the time in a time stamp.
When nil, S-up will increase.

org-effort-durations (\` (("h" . 60) ("d" \, (* 60 ...

:PROPERTIES: :CUSTOM_ID: org-effort-durations :END:

Conversion factor to minutes for an effort modifier.

Each entry has the form (MODIFIER . MINUTES).

In an effort string, a number followed by MODIFIER is multiplied
by the specified number of MINUTES to obtain an effort in
minutes.

For example, if the value of this variable is (("hours" . 60)), then an
effort string "2hours" is equivalent to 120 minutes.

org-effort-property "Effort"

:PROPERTIES: :CUSTOM_ID: org-effort-property :END:

The property that is being used to keep track of effort estimates.
Effort estimates given in this property need to have the format H:MM.

org-ellipsis nil

:PROPERTIES: :CUSTOM_ID: org-ellipsis :END:

The ellipsis to use in the Org-mode outline.
When nil, just use the standard three dots.  When a string, use that instead,
When a face, use the standard 3 dots, but with the specified face.
The change affects only Org-mode (which will then use its own display table).
Changing this requires executing `M-x org-mode' in a buffer to become
effective.

:PROPERTIES: :CUSTOM_ID: org-email-link-description-format :END:

Format of the description part of a link to an email or usenet message.
The following %-escapes will be replaced by corresponding information:

%F   full "From" field
%f   name, taken from "From" field, address if no name
%T   full "To" field
%t   first name in "To" field, address if no name
%c   correspondent.  Usually "from NAME", but if you sent it yourself, it
     will be "to NAME".  See also the variable `org-from-is-user-regexp'.
%s   subject
%d   date
%m   message-id.

You may use normal field width specification between the % and the letter.
This is for example useful to limit the length of the subject.

Examples: "%f on: %.30s", "Email from %f", "Email %c"

org-emphasis-alist (\` (("*" bold "<b>" "</b>") (...

:PROPERTIES: :CUSTOM_ID: org-emphasis-alist :END:

Special syntax for emphasized text.
Text starting and ending with a special character will be emphasized, for
example *bold*, _underlined_ and /italic/.  This variable sets the marker
characters, the face to be used by font-lock for highlighting in Org-mode
Emacs buffers, and the HTML tags to be used for this.
For LaTeX export, see the variable `org-export-latex-emphasis-alist'.
For DocBook export, see the variable `org-export-docbook-emphasis-alist'.
Use customize to modify this, or restart Emacs after changing it.

org-emphasis-regexp-components (quote (" ('\"{" "- .,:!?;'\...

:PROPERTIES: :CUSTOM_ID: org-emphasis-regexp-components :END:

Components used to build the regular expression for emphasis.
This is a list with five entries.  Terminology:  In an emphasis string
like " *strong word* ", we call the initial space PREMATCH, the final
space POSTMATCH, the stars MARKERS, "s" and "d" are BORDER characters
and "trong wor" is the body.  The different components in this variable
specify what is allowed/forbidden in each part:

pre          Chars allowed as prematch.  Beginning of line will be allowed too.
post         Chars allowed as postmatch.  End of line will be allowed too.
border       The chars *forbidden* as border characters.
body-regexp  A regexp like "." to match a body character.  Don't use
             non-shy groups here, and don't allow newline here.
newline      The maximum number of newlines allowed in an emphasis exp.

Use customize to modify this, or restart Emacs after changing it.

org-empty-line-terminates-plain-lists nil

:PROPERTIES: :CUSTOM_ID: org-empty-line-terminates-plain-lists :END:

Non-nil means an empty line ends all plain list levels.
Otherwise, two of them will be necessary.

org-enable-fixed-width-editor t

:PROPERTIES: :CUSTOM_ID: org-enable-fixed-width-editor :END:

Non-nil means lines starting with ":" are treated as fixed-width.
This currently only means they are never auto-wrapped.
When nil, such lines will be treated like ordinary lines.
See also the QUOTE keyword.

org-enable-priority-commands t

:PROPERTIES: :CUSTOM_ID: org-enable-priority-commands :END:

Non-nil means priority commands are active.
When nil, these commands will be disabled, so that you never accidentally
set a priority.

org-enable-table-editor (quote optimized)

:PROPERTIES: :CUSTOM_ID: org-enable-table-editor :END:

Non-nil means lines starting with "|" are handled by the table editor.
When nil, such lines will be treated like ordinary lines.

When equal to the symbol `optimized', the table editor will be optimized to
do the following:
- Automatic overwrite mode in front of whitespace in table fields.
  This makes the structure of the table stay in tact as long as the edited
  field does not exceed the column width.
- Minimize the number of realigns.  Normally, the table is aligned each time
  TAB or RET are pressed to move to another field.  With optimization this
  happens only if changes to a field might have changed the column width.
Optimization requires replacing the functions `self-insert-command',
`delete-char', and `backward-delete-char' in Org-mode buffers, with a
slight (in fact: unnoticeable) speed impact for normal typing.  Org-mode is
very good at guessing when a re-align will be necessary, but you can always
force one with \[org-ctrl-c-ctrl-c].

If you would like to use the optimized version in Org-mode, but the
un-optimized version in OrgTbl-mode, see the variable `orgtbl-optimized'.

This variable can be used to turn on and off the table editor during a session,
but in order to toggle optimization, a restart is required.

See also the variable `org-table-auto-blank-field'.

org-enforce-todo-checkbox-dependencies nil

:PROPERTIES: :CUSTOM_ID: org-enforce-todo-checkbox-dependencies :END:

Non-nil means unchecked boxes will block switching the parent to DONE.
When this is nil, checkboxes have no influence on switching TODO states.
When non-nil, you first need to check off all check boxes before the TODO
entry can be switched to DONE.
This variable needs to be set before org.el is loaded, and you need to
restart Emacs after a change to make the change effective.  The only way
to change is while Emacs is running is through the customize interface.

org-enforce-todo-dependencies nil

:PROPERTIES: :CUSTOM_ID: org-enforce-todo-dependencies :END:

Non-nil means undone TODO entries will block switching the parent to DONE.
Also, if a parent has an :ORDERED: property, switching an entry to DONE will
be blocked if any prior sibling is not yet done.
Finally, if the parent is blocked because of ordered siblings of its own,
the child will also be blocked.

org-entities-ascii-explanatory nil

:PROPERTIES: :CUSTOM_ID: org-entities-ascii-explanatory :END:

Non-nil means replace special entities in ASCII.
For example, this will replace "\nsup" with "[not a superset of]"
in backends where the corresponding character is not available.

org-entities-user nil

:PROPERTIES: :CUSTOM_ID: org-entities-user :END:

User-defined entities used in Org-mode to produce special characters.
Each entry in this list is a list of strings.  It associates the name
of the entity that can be inserted into an Org file as \name with the
appropriate replacements for the different export backends.  The order
of the fields is the following

name                 As a string, without the leading backslash
LaTeX replacement    In ready LaTeX, no further processing will take place
LaTeX mathp          A Boolean, either t or nil.  t if this entity needs
                     to be in math mode.
HTML replacement     In ready HTML, no further processing will take place.
                     Usually this will be an &...; entity.
ASCII replacement    Plain ASCII, no extensions.  Symbols that cannot be
                     represented will be left as they are, but see the.
                     variable `org-entities-ascii-explanatory'.
Latin1 replacement   Use the special characters available in latin1.
utf-8 replacement    Use the special characters available in utf-8.

If you define new entities here that require specific LaTeX packages to be
loaded, add these packages to `org-export-latex-packages-alist'.

org-export-allow-BIND (quote confirm)

:PROPERTIES: :CUSTOM_ID: org-export-allow-BIND :END:

Non-nil means allow #+BIND to define local variable values for export.
This is a potential security risk, which is why the user must confirm the
use of these lines.

org-export-ascii-bullets (quote (42 43 45))

:PROPERTIES: :CUSTOM_ID: org-export-ascii-bullets :END:

Bullet characters for headlines converted to lists in ASCII export.
The first character is used for the first lest level generated in this
way, and so on.  If there are more levels than characters given here,
the list will be repeated.
Note that plain lists will keep the same bullets as the have in the
Org-mode file.

:PROPERTIES: :CUSTOM_ID: org-export-ascii-links-to-notes :END:

Non-nil means convert links to notes before the next headline.
When nil, the link will be exported in place.  If the line becomes long
in this way, it will be wrapped.

org-export-ascii-table-keep-all-vertical-lines nil

:PROPERTIES: :CUSTOM_ID: org-export-ascii-table-keep-all-vertical-lines :END:

Non-nil means keep all vertical lines in ASCII tables.
When nil, vertical lines will be removed except for those needed
for column grouping.

org-export-ascii-table-widen-columns t

:PROPERTIES: :CUSTOM_ID: org-export-ascii-table-widen-columns :END:

Non-nil means widen narrowed columns for export.
When nil, narrowed columns will look in ASCII export just like in org-mode,
i.e. with "=>" as ellipsis.

org-export-ascii-underline (quote (61 45 126 67108896 46 ...

:PROPERTIES: :CUSTOM_ID: org-export-ascii-underline :END:

Characters for underlining headings in ASCII export.
In the given sequence, these characters will be used for level 1, 2, ...

org-export-author-info t

:PROPERTIES: :CUSTOM_ID: org-export-author-info :END:

Non-nil means insert author name and email into the exported file.

This option can also be set with the +OPTIONS line,
e.g. "author:nil".

org-export-babel-evaluate t

:PROPERTIES: :CUSTOM_ID: org-export-babel-evaluate :END:

Switch controlling code evaluation during export.
When set to nil no code will be evaluated as part of the export
process.

org-export-blocks (quote ((export-comment org-ex...

:PROPERTIES: :CUSTOM_ID: org-export-blocks :END:

Use this alist to associate block types with block exporting functions.
The type of a block is determined by the text immediately
following the '#+BEGIN_' portion of the block header.  Each block
export function should accept three arguments.

org-export-blocks-witheld (quote (hidden))

:PROPERTIES: :CUSTOM_ID: org-export-blocks-witheld :END:

List of block types (see `org-export-blocks') which should not be exported.

org-export-copy-to-kill-ring t

:PROPERTIES: :CUSTOM_ID: org-export-copy-to-kill-ring :END:

Non-nil means exported stuff will also be pushed onto the kill ring.

org-export-creator-info t

:PROPERTIES: :CUSTOM_ID: org-export-creator-info :END:

Non-nil means the postamble should contain a creator sentence.
This sentence is "HTML generated by org-mode XX in emacs XXX".

org-export-date-timestamp-format "%Y-%m-%d"

:PROPERTIES: :CUSTOM_ID: org-export-date-timestamp-format :END:

Time string format for Org timestamps in the #+DATE option.

org-export-default-language "en"

:PROPERTIES: :CUSTOM_ID: org-export-default-language :END:

The default language for export and clocktable translations, as a string.
This should have an association in `org-export-language-setup'
and in `org-clock-clocktable-language-setup'.

org-export-docbook-article-header "<article xmlns=\"http://docbo...

:PROPERTIES: :CUSTOM_ID: org-export-docbook-article-header :END:

Article header of DocBook XML files.

org-export-docbook-coding-system nil

:PROPERTIES: :CUSTOM_ID: org-export-docbook-coding-system :END:

Coding system for DocBook XML files.

org-export-docbook-default-image-attributes (\` (("align" . "\"center\"") ...

:PROPERTIES: :CUSTOM_ID: org-export-docbook-default-image-attributes :END:

Alist of default DocBook image attributes.
These attributes will be inserted into element  by
default, but users can override them using `#+ATTR_DocBook:'.

org-export-docbook-doctype nil

:PROPERTIES: :CUSTOM_ID: org-export-docbook-doctype :END:

DOCTYPE declaration string for DocBook XML files.
This can be used to include entities that are needed to handle
special characters in Org files.

For example, if the Org file to be exported contains XHTML
entities, you can set this variable to:

"
%xhtml1-symbol;
]>
"

If you want to process DocBook documents without an Internet
connection, it is suggested that you download the required entity
file(s) and use system identifier(s) (external files) in the
DOCTYPE declaration.

org-export-docbook-emphasis-alist (\` (("*" "<emphasis role=\"bo...

:PROPERTIES: :CUSTOM_ID: org-export-docbook-emphasis-alist :END:

A list of DocBook expressions to convert emphasis fontifiers.
Each element of the list is a list of three elements.
The first element is the character used as a marker for fontification.
The second element is a format string to wrap fontified text with.
The third element decides whether to protect converted text from other
conversions.

org-export-docbook-extension ".xml"

:PROPERTIES: :CUSTOM_ID: org-export-docbook-extension :END:

Extension of DocBook XML files.

org-export-docbook-footnote-id-prefix "fn-"

:PROPERTIES: :CUSTOM_ID: org-export-docbook-footnote-id-prefix :END:

The prefix of footnote IDs used during exporting.
Like `org-export-docbook-section-id-prefix', this variable can help
avoid same set of footnote IDs being used multiple times.

org-export-docbook-footnote-separator "<superscript>, </superscript>...

:PROPERTIES: :CUSTOM_ID: org-export-docbook-footnote-separator :END:

Text used to separate footnotes.

org-export-docbook-header "<?xml version=\"1.0\" encodin...

:PROPERTIES: :CUSTOM_ID: org-export-docbook-header :END:

Header of DocBook XML files.

org-export-docbook-inline-image-extensions (quote ("jpeg" "jpg" "png" "gi...

:PROPERTIES: :CUSTOM_ID: org-export-docbook-inline-image-extensions :END:

Extensions of image files that can be inlined into DocBook.

org-export-docbook-keywords-markup "<literal>%s</literal>"

:PROPERTIES: :CUSTOM_ID: org-export-docbook-keywords-markup :END:

A printf format string to be applied to keywords by DocBook exporter.

org-export-docbook-section-id-prefix "sec-"

:PROPERTIES: :CUSTOM_ID: org-export-docbook-section-id-prefix :END:

Prefix of section IDs used during exporting.
This can be set before exporting to avoid same set of section IDs
being used again and again, which can be a problem when multiple
people work on the same document.

org-export-docbook-timestamp-markup "<emphasis>%s</emphasis>"

:PROPERTIES: :CUSTOM_ID: org-export-docbook-timestamp-markup :END:

A printf format string to be applied to time stamps by DocBook exporter.

org-export-docbook-xsl-fo-proc-command nil

:PROPERTIES: :CUSTOM_ID: org-export-docbook-xsl-fo-proc-command :END:

Format of XSL-FO processor command used by DocBook exporter.
This command is used to process a Formatting Object (FO) file to
generate the PDF file.

The value of this variable should be a format control string that
includes two arguments: `%i' and `%o'.  During exporting time,
`%i' is replaced by the input FO file name, and `%o' is replaced
by the output PDF file name.

For example, if you use FOP as the XSL-FO processor, you can set
the variable to

  "fop %i %o"

org-export-docbook-xslt-proc-command nil

:PROPERTIES: :CUSTOM_ID: org-export-docbook-xslt-proc-command :END:

Format of XSLT processor command used by DocBook exporter.
This command is used to process a DocBook XML file to generate
the Formatting Object (FO) file.

The value of this variable should be a format control string that
includes three arguments: `%i', `%o', and `%s'.  During exporting
time, `%i' is replaced by the input DocBook XML file name, `%o'
is replaced by the output FO file name, and `%s' is replaced by
`org-export-docbook-xslt-stylesheet' (or the #+XSLT option if it
is specified in the Org file).

For example, if you use Saxon as the XSLT processor, you may want
to set the variable to

  "java com.icl.saxon.StyleSheet -o %o %i %s"

If you use Xalan, you can set it to

  "java org.apache.xalan.xslt.Process -out %o -in %i -xsl %s"

For xsltproc, the following string should work:

  "xsltproc --output %o %s %i"

You can include additional stylesheet parameters in this command.
Just make sure that they meet the syntax requirement of each
processor.

org-export-docbook-xslt-stylesheet nil

:PROPERTIES: :CUSTOM_ID: org-export-docbook-xslt-stylesheet :END:

File name of the XSLT stylesheet used by DocBook exporter.
This XSLT stylesheet is used by
`org-export-docbook-xslt-proc-command' to generate the Formatting
Object (FO) files.  You can use either `fo/docbook.xsl' that
comes with DocBook, or any customization layer you may have.

org-export-email-info nil

:PROPERTIES: :CUSTOM_ID: org-export-email-info :END:

Non-nil means insert author name and email into the exported file.

This option can also be set with the +OPTIONS line,
e.g. "email:t".

org-export-exclude-tags (quote ("noexport"))

:PROPERTIES: :CUSTOM_ID: org-export-exclude-tags :END:

Tags that exclude a tree from export.
All trees carrying any of these tags will be excluded from export.
This is without condition, so even subtrees inside that carry one of the
`org-export-select-tags' will be removed.

org-export-headline-levels 3

:PROPERTIES: :CUSTOM_ID: org-export-headline-levels :END:

The last level which is still exported as a headline.
Inferior levels will produce itemize lists when exported.
Note that a numeric prefix argument to an exporter function overrides
this setting.

This option can also be set with the +OPTIONS line, e.g. "H:2".

org-export-highlight-first-table-line t

:PROPERTIES: :CUSTOM_ID: org-export-highlight-first-table-line :END:

Non-nil means highlight the first table line.
In HTML export, this means use  instead of .
In tables created with table.el, this applies to the first table line.
In Org-mode tables, all lines before the first horizontal separator
line will be formatted with  tags.

org-export-html-coding-system nil

:PROPERTIES: :CUSTOM_ID: org-export-html-coding-system :END:

Coding system for HTML export, defaults to `buffer-file-coding-system'.

org-export-html-date-format-string "%Y-%m-%dT%R%z"

:PROPERTIES: :CUSTOM_ID: org-export-html-date-format-string :END:

Format string to format the date and time.

The default is an extended format of the ISO 8601 specification.

org-export-html-divs (quote ("preamble" "content" "...

:PROPERTIES: :CUSTOM_ID: org-export-html-divs :END:

The name of the main divs for HTML export.
This is a list of three strings, the first one for the preamble
DIV, the second one for the content DIV and the third one for the
postamble DIV.

org-export-html-expand t

:PROPERTIES: :CUSTOM_ID: org-export-html-expand :END:

Non-nil means for HTML export, treat @<...> as HTML tag.
When nil, these tags will be exported as plain text and therefore
not be interpreted by a browser.

This option can also be set with the +OPTIONS line, e.g. "@:nil".

org-export-html-extension "html"

:PROPERTIES: :CUSTOM_ID: org-export-html-extension :END:

The extension for exported HTML files.

org-export-html-footnote-format "<sup>%s</sup>"

:PROPERTIES: :CUSTOM_ID: org-export-html-footnote-format :END:

The format for the footnote reference.
%s will be replaced by the footnote reference itself.

org-export-html-footnote-separator "<sup>, </sup>"

:PROPERTIES: :CUSTOM_ID: org-export-html-footnote-separator :END:

Text used to separate footnotes.

org-export-html-footnotes-section "<div id=\"footnotes\">\n<h2 c...

:PROPERTIES: :CUSTOM_ID: org-export-html-footnotes-section :END:

Format for the footnotes section.
Should contain a two instances of %s.  The first will be replaced with the
language-specific word for "Footnotes", the second one will be replaced
by the footnotes themselves.

org-export-html-headline-anchor-format "<a name=\"%s\" id=\"%s\"></a>...

:PROPERTIES: :CUSTOM_ID: org-export-html-headline-anchor-format :END:

Format for anchors in HTML headlines.
It requires to %s: both will be replaced by the anchor referring
to the headline (e.g. "sec-2").  When set to `nil', don't insert
HTML anchors in headlines.

org-export-html-home/up-format "<div id=\"org-div-home-and-up...

:PROPERTIES: :CUSTOM_ID: org-export-html-home/up-format :END:

Snippet used to insert the HOME and UP links.
This is a format string, the first %s will receive the UP link,
the second the HOME link.  If both `org-export-html-link-up' and
`org-export-html-link-home' are empty, the entire snippet will be
ignored.

org-export-html-inline-image-extensions (quote ("png" "jpeg" "jpg" "gi...

:PROPERTIES: :CUSTOM_ID: org-export-html-inline-image-extensions :END:

Extensions of image files that can be inlined into HTML.

org-export-html-inline-images (quote maybe)

:PROPERTIES: :CUSTOM_ID: org-export-html-inline-images :END:

Non-nil means inline images into exported HTML pages.
This is done using an  tag.  When nil, an anchor with href is used to
link to the image.  If this option is `maybe', then images in links with
an empty description will be inlined, while images with a description will
be linked only.

:PROPERTIES: :CUSTOM_ID: org-export-html-link-home :END:

Where should the "HOME" link of exported HTML pages lead?

:PROPERTIES: :CUSTOM_ID: org-export-html-link-org-files-as-html :END:

Non-nil means make file links to `file.org' point to `file.html'.
When org-mode is exporting an org-mode file to HTML, links to
non-html files are directly put into a href tag in HTML.
However, links to other Org-mode files (recognized by the
extension `.org.) should become links to the corresponding html
file, assuming that the linked org-mode file will also be
converted to HTML.
When nil, the links still point to the plain `.org' file.

:PROPERTIES: :CUSTOM_ID: org-export-html-link-up :END:

Where should the "UP" link of exported HTML pages lead?

org-export-html-mathjax-options (quote ((path "http://orgmode....

:PROPERTIES: :CUSTOM_ID: org-export-html-mathjax-options :END:

Options for MathJax setup.

path        The path where to find MathJax
scale       Scaling for the HTML-CSS backend, usually between 100 and 133
align       How to align display math: left, center, or right
indent      If align is not center, how far from the left/right side?
mathml      Should a MathML player be used if available?
            This is faster and reduces bandwidth use, but currently
            sometimes has lower spacing quality.  Therefore, the default is
            nil.  When browsers get better, this switch can be flipped.

You can also customize this for each buffer, using something like

#+MATHJAX: scale:"133" align:"right" mathml:t path:"/MathJax/"

org-export-html-mathjax-template "<script type=\"text/javascrip...

:PROPERTIES: :CUSTOM_ID: org-export-html-mathjax-template :END:

The MathJax setup for XHTML files.

org-export-html-postamble (quote auto)

:PROPERTIES: :CUSTOM_ID: org-export-html-postamble :END:

Non-nil means insert a postamble in HTML export.

When `t', insert a string as defined by the format string in
`org-export-html-postamble-format'.  When set to a string, this
string overrides `org-export-html-postamble-format'.  When set to
'auto, discard `org-export-html-postamble-format' and honor
`org-export-author/email/creator-info' variables.  When set to a
function, apply this function and insert the returned string.
The function takes no argument, but you can use `opt-plist' to
access the current export options.

Setting :html-postamble in publishing projects will take
precedence over this variable.

org-export-html-postamble-format (quote (("en" "<p class=\"auth...

:PROPERTIES: :CUSTOM_ID: org-export-html-postamble-format :END:

Alist of languages and format strings for the HTML postamble.

The first element of each list is the language code, as used for
the #+LANGUAGE keyword.

The second element of each list is a format string to format the
postamble itself.  This format string can contain these elements:

%a stands for the author's name.
%e stands for the author's email.
%d stands for the date.
%c will be replaced by information about Org/Emacs versions.
%v will be replaced by `org-export-html-validation-link'.

If you need to use a "%" character, you need to escape it
like that: "%%".

org-export-html-preamble t

:PROPERTIES: :CUSTOM_ID: org-export-html-preamble :END:

Non-nil means insert a preamble in HTML export.

When `t', insert a string as defined by one of the formatting
strings in `org-export-html-preamble-format'.  When set to a
string, this string overrides `org-export-html-preamble-format'.
When set to a function, apply this function and insert the
returned string.  The function takes no argument, but you can
use `opt-plist' to access the current export options.

Setting :html-preamble in publishing projects will take
precedence over this variable.

org-export-html-preamble-format (quote (("en" "")))

:PROPERTIES: :CUSTOM_ID: org-export-html-preamble-format :END:

Alist of languages and format strings for the HTML preamble.

The first element of each list is the language code, as used for
the #+LANGUAGE keyword.

The second element of each list is a format string to format the
preamble itself.  This format string can contain these elements:

%t stands for the title.
%a stands for the author's name.
%e stands for the author's email.
%d stands for the date.

If you need to use a "%" character, you need to escape it
like that: "%%".

org-export-html-protect-char-alist (quote (("&" . "&amp;") ("<" ....

:PROPERTIES: :CUSTOM_ID: org-export-html-protect-char-alist :END:

Alist of characters to be converted by `org-html-protect'.

org-export-html-style ""

:PROPERTIES: :CUSTOM_ID: org-export-html-style :END:

Org-wide style definitions for exported HTML files.

This variable needs to contain the full HTML structure to provide a style,
including the surrounding HTML tags.  If you set the value of this variable,
you should consider to include definitions for the following classes:
 title, todo, done, timestamp, timestamp-kwd, tag, target.

For example, a valid value would be:

   

If you'd like to refer to an external style file, use something like

   

As the value of this option simply gets inserted into the HTML  header,
you can "misuse" it to add arbitrary text to the header.
See also the variable `org-export-html-style-extra'.

org-export-html-style-extra ""

:PROPERTIES: :CUSTOM_ID: org-export-html-style-extra :END:

Additional style information for HTML export.
The value of this variable is inserted into the HTML buffer right after
the value of `org-export-html-style'.  Use this variable for per-file
settings of style information, and do not forget to surround the style
settings with  tags.

org-export-html-style-include-default t

:PROPERTIES: :CUSTOM_ID: org-export-html-style-include-default :END:

Non-nil means include the default style in exported HTML files.
The actual style is defined in `org-export-html-style-default' and should
not be modified.  Use the variables `org-export-html-style' to add
your own style information.

org-export-html-style-include-scripts t

:PROPERTIES: :CUSTOM_ID: org-export-html-style-include-scripts :END:

Non-nil means include the JavaScript snippets in exported HTML files.
The actual script is defined in `org-export-html-scripts' and should
not be modified.

org-export-html-table-align-individual-fields t

:PROPERTIES: :CUSTOM_ID: org-export-html-table-align-individual-fields :END:

Non-nil means attach style attributes for alignment to each table field.
When nil, alignment will only be specified in the column tags, but this
is ignored by some browsers (like Firefox, Safari).  Opera does it right
though.

org-export-html-table-tag "<table border=\"2\" cellspaci...

:PROPERTIES: :CUSTOM_ID: org-export-html-table-tag :END:

The HTML tag that is used to start a table.
This must be a  tag, but you may change the options like
borders and spacing.

org-export-html-table-use-header-tags-for-first-column nil

:PROPERTIES: :CUSTOM_ID: org-export-html-table-use-header-tags-for-first-column :END:

Non-nil means format column one in tables with header tags.
When nil, also column one will use data tags.

org-export-html-tag-class-prefix ""

:PROPERTIES: :CUSTOM_ID: org-export-html-tag-class-prefix :END:

Prefix to class names for TODO keywords.
Each tag gets a class given by the tag itself, with this prefix.
The default prefix is empty because it is nice to just use the keyword
as a class name.  But if you get into conflicts with other, existing
CSS classes, then this prefix can be very useful.

org-export-html-todo-kwd-class-prefix ""

:PROPERTIES: :CUSTOM_ID: org-export-html-todo-kwd-class-prefix :END:

Prefix to class names for TODO keywords.
Each TODO keyword gets a class given by the keyword itself, with this prefix.
The default prefix is empty because it is nice to just use the keyword
as a class name.  But if you get into conflicts with other, existing
CSS classes, then this prefix can be very useful.

org-export-html-toplevel-hlevel 2

:PROPERTIES: :CUSTOM_ID: org-export-html-toplevel-hlevel :END:

The  level for level 1 headings in HTML export.
This is also important for the classes that will be wrapped around headlines
and outline structure.  If this variable is 1, the top-level headlines will
be 

, and the corresponding classes will be outline-1, section-number-1, and outline-text-1. If this is 2, all of these will get a 2 instead. The default for this variable is 2, because we use

for formatting the document title.

org-export-html-use-infojs (quote when-configured)

:PROPERTIES: :CUSTOM_ID: org-export-html-use-infojs :END:

Should Sebastian Rose's Java Script org-info.js be linked into HTML files?
This option can be nil or t to never or always use the script.  It can
also be the symbol `when-configured', meaning that the script will be
linked into the export file if and only if there is a "#+INFOJS_OPT:"
line in the buffer.  See also the variable `org-infojs-options'.

:PROPERTIES: :CUSTOM_ID: org-export-html-validation-link :END:

Link to HTML validation service.

org-export-html-xml-declaration (quote (("html" . "<?xml versi...

:PROPERTIES: :CUSTOM_ID: org-export-html-xml-declaration :END:

The extension for exported HTML files.
%s will be replaced with the charset of the exported file.
This may be a string, or an alist with export extensions
and corresponding declarations.

org-export-htmlize-css-font-prefix "org-"

:PROPERTIES: :CUSTOM_ID: org-export-htmlize-css-font-prefix :END:

The prefix for CSS class names for htmlize font specifications.

org-export-htmlize-output-type (quote inline-css)

:PROPERTIES: :CUSTOM_ID: org-export-htmlize-output-type :END:

Output type to be used by htmlize when formatting code snippets.
Choices are `css', to export the CSS selectors only, or `inline-css', to
export the CSS attribute values inline in the HTML.  We use as default
`inline-css', in order to make the resulting HTML self-containing.

However, this will fail when using Emacs in batch mode for export, because
then no rich font definitions are in place.  It will also not be good if
people with different Emacs setup contribute HTML files to a website,
because the fonts will represent the individual setups.  In these cases,
it is much better to let Org/Htmlize assign classes only, and to use
a style file to define the look of these classes.
To get a start for your css file, start Emacs session and make sure that
all the faces you are interested in are defined, for example by loading files
in all modes you want.  Then, use the command
\[org-export-htmlize-generate-css] to extract class definitions.

org-export-htmlized-org-css-url nil

:PROPERTIES: :CUSTOM_ID: org-export-htmlized-org-css-url :END:

URL pointing to a CSS file defining text colors for htmlized Emacs buffers.
Normally when creating an htmlized version of an Org buffer, htmlize will
create CSS to define the font colors.  However, this does not work when
converting in batch mode, and it also can look bad if different people
with different fontification setup work on the same website.
When this variable is non-nil, creating an htmlized version of an Org buffer
using `org-export-as-org' will remove the internal CSS section and replace it
with a link to this URL.

org-export-initial-scope (quote buffer)

:PROPERTIES: :CUSTOM_ID: org-export-initial-scope :END:

The initial scope when exporting with `org-export'.
This variable can be either set to 'buffer or 'subtree.

org-export-interblocks (quote nil)

:PROPERTIES: :CUSTOM_ID: org-export-interblocks :END:

Use this a-list to associate block types with block exporting functions.
The type of a block is determined by the text immediately
following the '#+BEGIN_' portion of the block header.  Each block
export function should accept three arguments.

org-export-kill-product-buffer-when-displayed nil

:PROPERTIES: :CUSTOM_ID: org-export-kill-product-buffer-when-displayed :END:

Non-nil means kill the product buffer if it is displayed immediately.
This applied to the commands `org-export-as-html-and-open' and
`org-export-as-pdf-and-open'.

org-export-language-setup (quote (("en" "Author" "Date" ...

:PROPERTIES: :CUSTOM_ID: org-export-language-setup :END:

Terms used in export text, translated to different languages.
Use the variable `org-export-default-language' to set the language,
or use the +OPTION lines for a per-file setting.

org-export-latex-classes (quote (("article" "\\document...

:PROPERTIES: :CUSTOM_ID: org-export-latex-classes :END:

Alist of LaTeX classes and associated header and structure.
If #+LaTeX_CLASS is set in the buffer, use its value and the
associated information.  Here is the structure of each cell:

  (class-name
    header-string
    (numbered-section . unnumbered-section)
    ...)

The header string
-----------------

The HEADER-STRING is the header that will be inserted into the LaTeX file.
It should contain the \documentclass macro, and anything else that is needed
for this setup.  To this header, the following commands will be added:

- Calls to \usepackage for all packages mentioned in the variables
  `org-export-latex-default-packages-alist' and
  `org-export-latex-packages-alist'.  Thus, your header definitions should
  avoid to also request these packages.

- Lines specified via "#+LaTeX_HEADER:"

If you need more control about the sequence in which the header is built
up, or if you want to exclude one of these building blocks for a particular
class, you can use the following macro-like placeholders.

 [DEFAULT-PACKAGES]      \usepackage statements for default packages
 [NO-DEFAULT-PACKAGES]   do not include any of the default packages
 [PACKAGES]              \usepackage statements for packages
 [NO-PACKAGES]           do not include the packages
 [EXTRA]                 the stuff from #+LaTeX_HEADER
 [NO-EXTRA]              do not include #+LaTeX_HEADER stuff
 [BEAMER-HEADER-EXTRA]   the beamer extra headers

So a header like

  \documentclass{article}
  [NO-DEFAULT-PACKAGES]
  [EXTRA]
  \providecommand{\alert}[1]{\textbf{#1}}
  [PACKAGES]

will omit the default packages, and will include the #+LaTeX_HEADER lines,
then have a call to \providecommand, and then place \usepackage commands
based on the content of `org-export-latex-packages-alist'.

If your header or `org-export-latex-default-packages-alist' inserts
"\usepackage[AUTO]{inputenc}", AUTO will automatically be replaced with
a coding system derived from `buffer-file-coding-system'.  See also the
variable `org-export-latex-inputenc-alist' for a way to influence this
mechanism.

The sectioning structure
------------------------

The sectioning structure of the class is given by the elements following
the header string.  For each sectioning level, a number of strings is
specified.  A %s formatter is mandatory in each section string and will
be replaced by the title of the section.

Instead of a cons cell (numbered . unnumbered), you can also provide a list
of 2 or 4 elements,

  (numbered-open numbered-close)

or

  (numbered-open numbered-close unnumbered-open unnumbered-close)

providing opening and closing strings for a LaTeX environment that should
represent the document section.  The opening clause should have a %s
to represent the section title.

Instead of a list of sectioning commands, you can also specify a
function name.  That function will be called with two parameters,
the (reduced) level of the headline, and the headline text.  The function
must return a cons cell with the (possibly modified) headline text, and the
sectioning list in the cdr.

org-export-latex-coding-system nil

:PROPERTIES: :CUSTOM_ID: org-export-latex-coding-system :END:

Coding system for the exported LaTeX file.

org-export-latex-date-format "\\today"

:PROPERTIES: :CUSTOM_ID: org-export-latex-date-format :END:

Format string for \date{...}.

org-export-latex-default-class "article"

:PROPERTIES: :CUSTOM_ID: org-export-latex-default-class :END:

The default LaTeX class.

org-export-latex-default-packages-alist (quote (("AUTO" "inputenc" t) ...

:PROPERTIES: :CUSTOM_ID: org-export-latex-default-packages-alist :END:

Alist of default packages to be inserted in the header.
Change this only if one of the packages here causes an incompatibility
with another package you are using.
The packages in this list are needed by one part or another of Org-mode
to function properly.

- inputenc, fontenc:  for basic font and character selection
- textcomp, marvosymb, wasysym, latexsym, amssym: for various symbols used
  for interpreting the entities in `org-entities'.  You can skip some of these
  packages if you don't use any of the symbols in it.
- graphicx: for including images
- float, wrapfig: for figure placement
- longtable: for long tables
- hyperref: for cross references

Therefore you should not modify this variable unless you know what you
are doing.  The one reason to change it anyway is that you might be loading
some other package that conflicts with one of the default packages.
Each cell is of the format ( "options" "package" snippet-flag).
If SNIPPET-FLAG is t, the package also needs to be included when
compiling LaTeX snippets into images for inclusion into HTML.

org-export-latex-emphasis-alist (quote (("*" "\\textbf{%s}" ni...

:PROPERTIES: :CUSTOM_ID: org-export-latex-emphasis-alist :END:

Alist of LaTeX expressions to convert emphasis fontifiers.
Each element of the list is a list of three elements.
The first element is the character used as a marker for fontification.
The second element is a format string to wrap fontified text with.
If it is "\verb", Org will automatically select a delimiter
character that is not in the string.  "\protectedtexttt" will use \texttt
to typeset and try to protect special characters.
The third element decides whether to protect converted text from other
conversions.

org-export-latex-footnote-separator "\\textsuperscript{,}\\,"

:PROPERTIES: :CUSTOM_ID: org-export-latex-footnote-separator :END:

Text used to separate footnotes.

org-export-latex-href-format "\\href{%s}{%s}"

:PROPERTIES: :CUSTOM_ID: org-export-latex-href-format :END:

A printf format string to be applied to href links.
The format must contain either two %s instances or just one.
If it contains two %s instances, the first will be filled with
the link, the second with the link description.  If it contains
only one, the %s will be filled with the link.

org-export-latex-hyperref-format "\\hyperref[%s]{%s}"

:PROPERTIES: :CUSTOM_ID: org-export-latex-hyperref-format :END:

A printf format string to be applied to hyperref links.
The format must contain one or two %s instances.  The first one
will be filled with the link, the second with its description.

org-export-latex-hyperref-options-format "\\hypersetup{\n pdfkeywords=...

:PROPERTIES: :CUSTOM_ID: org-export-latex-hyperref-options-format :END:

A format string for hyperref options.
When non-nil, it must contain three %s format specifications
which will respectively be replaced by the document's keywords,
its description and the Org's version number, as a string.  Set
this option to the empty string if you don't want to include
hyperref options altogether.

org-export-latex-image-default-option "width=.9\\linewidth"

:PROPERTIES: :CUSTOM_ID: org-export-latex-image-default-option :END:

Default option for images.

org-export-latex-import-inbuffer-stuff nil

:PROPERTIES: :CUSTOM_ID: org-export-latex-import-inbuffer-stuff :END:

Non-nil means define TeX macros for Org's inbuffer definitions.
For example orgTITLE for #+TITLE.

org-export-latex-inline-image-extensions (quote ("pdf" "jpeg" "jpg" "pn...

:PROPERTIES: :CUSTOM_ID: org-export-latex-inline-image-extensions :END:

Extensions of image files that can be inlined into LaTeX.
Note that the image extension *actually* allowed depend on the way the
LaTeX file is processed.  When used with pdflatex, pdf, jpg and png images
are OK.  When processing through dvi to Postscript, only ps and eps are
allowed.  The default we use here encompasses both.

org-export-latex-inputenc-alist nil

:PROPERTIES: :CUSTOM_ID: org-export-latex-inputenc-alist :END:

Alist of inputenc coding system names, and what should really be used.
For example, adding an entry

      ("utf8" . "utf8x")

will cause \usepackage[utf8x]{inputenc} to be used for buffers that
are written as utf8 files.

:PROPERTIES: :CUSTOM_ID: org-export-latex-link-with-unknown-path-format :END:

Format string for links with unknown path type.

org-export-latex-list-parameters ~(quote (:cbon "$\\boxtimes$"

:PROPERTIES: :CUSTOM_ID: org-export-latex-list-parameters :END:

Parameters for the LaTeX list exporter.
These parameters will be passed on to `org-list-to-latex', which in turn
will pass them (combined with the LaTeX default list parameters) to
`org-list-to-generic'.

org-export-latex-listings nil

:PROPERTIES: :CUSTOM_ID: org-export-latex-listings :END:

Non-nil means export source code using the listings package.
This package will fontify source code, possibly even with color.
If you want to use this, you also need to make LaTeX use the
listings package, and if you want to have color, the color
package.  Just add these to `org-export-latex-packages-alist',
for example using customize, or with something like

  (require 'org-latex)
  (add-to-list 'org-export-latex-packages-alist '("" "listings"))
  (add-to-list 'org-export-latex-packages-alist '("" "color"))

Alternatively,

  (setq org-export-latex-listings 'minted)

causes source code to be exported using the minted package as
opposed to listings.  If you want to use minted, you need to add
the minted package to `org-export-latex-packages-alist', for
example using customize, or with

  (require 'org-latex)
  (add-to-list 'org-export-latex-packages-alist '("" "minted"))

In addition, it is necessary to install
pygments (http://pygments.org), and to configure the variable
`org-latex-to-pdf-process' so that the -shell-escape option is
passed to pdflatex.

org-export-latex-listings-langs (quote ((emacs-lisp "Lisp") (l...

:PROPERTIES: :CUSTOM_ID: org-export-latex-listings-langs :END:

Alist mapping languages to their listing language counterpart.
The key is a symbol, the major mode symbol without the "-mode".
The value is the string that should be inserted as the language parameter
for the listings package.  If the mode name and the listings name are
the same, the language does not need an entry in this list - but it does not
hurt if it is present.

org-export-latex-listings-options nil

:PROPERTIES: :CUSTOM_ID: org-export-latex-listings-options :END:

Association list of options for the latex listings package.

These options are supplied as a comma-separated list to the
\lstset command. Each element of the association list should be
a list containing two strings: the name of the option, and the
value. For example,

  (setq org-export-latex-listings-options
    '(("basicstyle" "\small")
      ("keywordstyle" "\color{black}\bfseries\underbar")))

will typeset the code in a small size font with underlined, bold
black keywords.

Note that the same options will be applied to blocks of all
languages.

org-export-latex-listings-w-names t

:PROPERTIES: :CUSTOM_ID: org-export-latex-listings-w-names :END:

Non-nil means export names of named code blocks.
Code blocks exported with the listings package (controlled by the
`org-export-latex-listings' variable) can be named in the style
of noweb.

org-export-latex-low-levels (quote itemize)

:PROPERTIES: :CUSTOM_ID: org-export-latex-low-levels :END:

How to convert sections below the current level of sectioning.
This is specified by the `org-export-headline-levels' option or the
value of "H:" in Org's #+OPTION line.

This can be either nil (skip the sections), `description', `itemize',
or `enumerate' (convert the sections as the corresponding list type), or
a string to be used instead of \section{%s}.  In this latter case,
the %s stands here for the inserted headline and is mandatory.

It may also be a list of three string to define a user-defined environment
that should be used.  The first string should be the like
"\begin{itemize}", the second should be like "\item %s %s" with up
to two occurrences of %s for the title and a label, respectively.  The third
string should be like "\end{itemize".

org-export-latex-minted-langs (quote ((emacs-lisp "common-li...

:PROPERTIES: :CUSTOM_ID: org-export-latex-minted-langs :END:

Alist mapping languages to their minted language counterpart.
The key is a symbol, the major mode symbol without the "-mode".
The value is the string that should be inserted as the language parameter
for the minted package.  If the mode name and the listings name are
the same, the language does not need an entry in this list - but it does not
hurt if it is present.

Note that minted uses all lower case for language identifiers,
and that the full list of language identifiers can be obtained
with:
pygmentize -L lexers

org-export-latex-minted-options nil

:PROPERTIES: :CUSTOM_ID: org-export-latex-minted-options :END:

Association list of options for the latex minted package.

These options are supplied within square brackets in
\begin{minted} environments. Each element of the alist should be
a list containing two strings: the name of the option, and the
value. For example,

  (setq org-export-latex-minted-options
    '(("bgcolor" "bg") ("frame" "lines")))

will result in src blocks being exported with

\begin{minted}[bgcolor=bg,frame=lines]{}

as the start of the minted environment. Note that the same
options will be applied to blocks of all languages.

org-export-latex-packages-alist nil

:PROPERTIES: :CUSTOM_ID: org-export-latex-packages-alist :END:

Alist of packages to be inserted in every LaTeX header.
These will be inserted after `org-export-latex-default-packages-alist'.
Each cell is of the format ( "options" "package" snippet-flag ).
SNIPPET-FLAG, when