Previous: Feedback, Up: Introduction [Contents][Index]
Org mainly uses three types of keywords: TODO keywords, tags and property names. In this manual we use the following conventions:
TODOWAITINGTODO keywords are written with all capitals, even if they are user-defined.
bossARCHIVEUser-defined tags are written in lowercase; built-in tags with special meaning are written with all capitals.
ReleasePRIORITYUser-defined properties are capitalized; built-in properties with special meaning are written with all capitals.
Moreover, Org uses option keywords (like #+TITLE to set the title)
and environment keywords (like #+BEGIN_EXPORT html to start
a HTML environment). They are written in uppercase in the manual to
enhance its readability, but you can use lowercase in your Org file.
The manual suggests a few global key bindings, in particular C-c a for
org-agenda and C-c c for org-capture. These are only
suggestions, but the rest of the manual assumes that these key bindings are in
place in order to list commands by key access.
Also, the manual lists both the keys and the corresponding commands for
accessing a functionality. Org mode often uses the same key for different
functions, depending on context. The command that is bound to such keys has
a generic name, like org-metaright. In the manual we will, wherever
possible, give the function that is internally called by the generic command.
For example, in the chapter on document structure, M-RIGHT will
be listed to call org-do-demote, while in the chapter on tables, it
will be listed to call org-table-move-column-right. If you prefer,
you can compile the manual without the command names by unsetting the flag
cmdnames in org.texi.
Previous: Feedback, Up: Introduction [Contents][Index]