orgguide.texi 97 KB

  1. \input texinfo
  2. @c %**start of header
  3. @setfilename ../../info/orgguide
  4. @settitle The compact Org-mode Guide
  5. @include
  6. @c Use proper quote and backtick for code sections in PDF output
  7. @c Cf. Texinfo manual 14.2
  8. @set txicodequoteundirected
  9. @set txicodequotebacktick
  10. @c Version and Contact Info
  11. @set MAINTAINERSITE @uref{,maintainers webpage}
  12. @set AUTHOR Carsten Dominik
  13. @set MAINTAINER Carsten Dominik
  14. @set MAINTAINEREMAIL @email{carsten at orgmode dot org}
  15. @set MAINTAINERCONTACT @uref{mailto:carsten at orgmode dot org,contact the maintainer}
  16. @c %**end of header
  17. @finalout
  18. @c Macro definitions
  19. @iftex
  20. @c @hyphenation{time-stamp time-stamps time-stamp-ing time-stamp-ed}
  21. @end iftex
  22. @c Subheadings inside a table.
  23. @macro tsubheading{text}
  24. @ifinfo
  25. @subsubheading \text\
  26. @end ifinfo
  27. @ifnotinfo
  28. @item @b{\text\}
  29. @end ifnotinfo
  30. @end macro
  31. @macro seealso{text}
  32. @noindent
  33. @b{Further reading}@*@noindent \text\
  34. @end macro
  35. @copying
  36. Copyright @copyright{} 2010--2016 Free Software Foundation
  37. @quotation
  38. Permission is granted to copy, distribute and/or modify this document
  39. under the terms of the GNU Free Documentation License, Version 1.3 or
  40. any later version published by the Free Software Foundation; with no
  41. Invariant Sections, with the Front-Cover Texts being ``A GNU Manual,''
  42. and with the Back-Cover Texts as in (a) below. A copy of the license
  43. is included in the section entitled ``GNU Free Documentation License''
  44. in the full Org manual, which is distributed together with the compact
  45. guide.
  46. (a) The FSF's Back-Cover Text is: ``You have the freedom to copy and
  47. modify this GNU manual.''
  48. @end quotation
  49. @end copying
  50. @dircategory Emacs
  51. @direntry
  52. * Org Mode Guide: (orgguide). Abbreviated Org-mode Manual
  53. @end direntry
  54. @titlepage
  55. @title The compact Org-mode Guide
  56. @subtitle Release @value{VERSION}
  57. @author by Carsten Dominik
  58. @c The following two commands start the copyright page.
  59. @page
  60. @vskip 0pt plus 1filll
  61. @insertcopying
  62. @end titlepage
  63. @c Output the table of contents at the beginning.
  64. @shortcontents
  65. @ifnottex
  66. @node Top, Introduction, (dir), (dir)
  67. @top Org Mode Guide
  68. @insertcopying
  69. @end ifnottex
  70. @menu
  71. * Introduction:: Getting started
  72. * Document Structure:: A tree works like your brain
  73. * Tables:: Pure magic for quick formatting
  74. * Hyperlinks:: Notes in context
  75. * TODO Items:: Every tree branch can be a TODO item
  76. * Tags:: Tagging headlines and matching sets of tags
  77. * Properties:: Properties
  78. * Dates and Times:: Making items useful for planning
  79. * Capture - Refile - Archive:: The ins and outs for projects
  80. * Agenda Views:: Collecting information into views
  81. * Markup:: Prepare text for rich export
  82. * Exporting:: Sharing and publishing of notes
  83. * Publishing:: Create a web site of linked Org files
  84. * Working With Source Code:: Source code snippets embedded in Org
  85. * Miscellaneous:: All the rest which did not fit elsewhere
  86. * GNU Free Documentation License:: This manual license.
  87. @detailmenu
  88. --- The Detailed Node Listing ---
  89. Introduction
  90. * Preface:: Welcome
  91. * Installation:: How to install a downloaded version of Org
  92. * Activation:: How to activate Org for certain buffers
  93. * Feedback:: Bug reports, ideas, patches etc.
  94. Document Structure
  95. * Outlines:: Org is based on Outline mode
  96. * Headlines:: How to typeset Org tree headlines
  97. * Visibility cycling:: Show and hide, much simplified
  98. * Motion:: Jumping to other headlines
  99. * Structure editing:: Changing sequence and level of headlines
  100. * Sparse trees:: Matches embedded in context
  101. * Plain lists:: Additional structure within an entry
  102. * Footnotes:: How footnotes are defined in Org's syntax
  103. Hyperlinks
  104. * Link format:: How links in Org are formatted
  105. * Internal links:: Links to other places in the current file
  106. * External links:: URL-like links to the world
  107. * Handling links:: Creating, inserting and following
  108. * Targeted links:: Point at a location in a file
  109. TODO Items
  110. * Using TODO states:: Setting and switching states
  111. * Multi-state workflows:: More than just on/off
  112. * Progress logging:: Dates and notes for progress
  113. * Priorities:: Some things are more important than others
  114. * Breaking down tasks:: Splitting a task into manageable pieces
  115. * Checkboxes:: Tick-off lists
  116. Progress logging
  117. * Closing items:: When was this entry marked DONE?
  118. * Tracking TODO state changes:: When did the status change?
  119. Tags
  120. * Tag inheritance:: Tags use the tree structure of the outline
  121. * Setting tags:: How to assign tags to a headline
  122. * Tag groups:: Use one tag to search for several tags
  123. * Tag searches:: Searching for combinations of tags
  124. Dates and Times
  125. * Timestamps:: Assigning a time to a tree entry
  126. * Creating timestamps:: Commands which insert timestamps
  127. * Deadlines and scheduling:: Planning your work
  128. * Clocking work time:: Tracking how long you spend on a task
  129. Capture - Refile - Archive
  130. * Capture:: Capturing new stuff
  131. * Refile and copy:: Moving a tree from one place to another
  132. * Archiving:: What to do with finished projects
  133. Capture
  134. * Setting up a capture location:: Where notes will be stored
  135. * Using capture:: Commands to invoke and terminate capture
  136. * Capture templates:: Define the outline of different note types
  137. Agenda Views
  138. * Agenda files:: Files being searched for agenda information
  139. * Agenda dispatcher:: Keyboard access to agenda views
  140. * Built-in agenda views:: What is available out of the box?
  141. * Agenda commands:: Remote editing of Org trees
  142. * Custom agenda views:: Defining special searches and views
  143. The built-in agenda views
  144. * Weekly/daily agenda:: The calendar page with current tasks
  145. * Global TODO list:: All unfinished action items
  146. * Matching tags and properties:: Structured information with fine-tuned search
  147. * Timeline:: Time-sorted view for single file
  148. * Search view:: Find entries by searching for text
  149. Markup for rich export
  150. * Structural markup elements:: The basic structure as seen by the exporter
  151. * Images and tables:: Images, tables and caption mechanism
  152. * Literal examples:: Source code examples with special formatting
  153. * Include files:: Include additional files into a document
  154. * Embedded @LaTeX{}:: @LaTeX{} can be freely used inside Org documents
  155. Structural markup elements
  156. * Document title:: Where the title is taken from
  157. * Headings and sections:: The document structure as seen by the exporter
  158. * Table of contents:: The if and where of the table of contents
  159. * Paragraphs:: Paragraphs
  160. * Emphasis and monospace:: Bold, italic, etc.
  161. * Comment lines:: What will *not* be exported
  162. Exporting
  163. * Export options:: Per-file export settings
  164. * The export dispatcher:: How to access exporter commands
  165. * ASCII/Latin-1/UTF-8 export:: Exporting to flat files with encoding
  166. * HTML export:: Exporting to HTML
  167. * @LaTeX{} and PDF export:: Exporting to @LaTeX{}, and processing to PDF
  168. * iCalendar export:: Exporting to iCalendar
  169. Miscellaneous
  170. * Completion:: M-TAB knows what you need
  171. * Clean view:: Getting rid of leading stars in the outline
  172. * MobileOrg:: Org-mode on the iPhone
  173. @end detailmenu
  174. @end menu
  175. @node Introduction, Document Structure, Top, Top
  176. @chapter Introduction
  177. @menu
  178. * Preface:: Welcome
  179. * Installation:: How to install a downloaded version of Org
  180. * Activation:: How to activate Org for certain buffers
  181. * Feedback:: Bug reports, ideas, patches etc.
  182. @end menu
  183. @node Preface, Installation, Introduction, Introduction
  184. @section Preface
  185. Org is a mode for keeping notes, maintaining TODO lists, and doing project
  186. planning with a fast and effective plain-text system. It is also an
  187. authoring and publishing system, and it supports working with source code for
  188. literal programming and reproducible research.
  189. @i{This document is a much compressed derivative of the
  190. @uref{, comprehensive Org-mode manual}.
  191. It contains all basic features and commands, along with important hints for
  192. customization. It is intended for beginners who would shy back from a 200
  193. page manual because of sheer size.}
  194. @node Installation, Activation, Preface, Introduction
  195. @section Installation
  196. @b{Important:} @i{If you are using a version of Org that is part of the Emacs
  197. distribution or an XEmacs package, please skip this section and go directly
  198. to @ref{Activation}.}
  199. If you have downloaded Org from the Web, either as a distribution @file{.zip}
  200. or @file{.tar} file, or as a Git archive, it is best to run it directly from
  201. the distribution directory. You need to add the @file{lisp} subdirectories
  202. to the Emacs load path. To do this, add the following line to @file{.emacs}:
  203. @smallexample
  204. (setq load-path (cons "~/path/to/orgdir/lisp" load-path))
  205. (setq load-path (cons "~/path/to/orgdir/contrib/lisp" load-path))
  206. @end smallexample
  207. @noindent
  208. If you have been using git or a tar ball to get Org, you need to
  209. run the following command to generate autoload information.
  210. command:
  211. @smallexample
  212. make autoloads
  213. @end smallexample
  214. @node Activation, Feedback, Installation, Introduction
  215. @section Activation
  216. Add the following lines to your @file{.emacs} file. The last four lines
  217. define @emph{global} keys for some commands --- please choose suitable keys
  218. yourself.
  219. @smalllisp
  220. ;; The following lines are always needed. Choose your own keys.
  221. (global-set-key "\C-cl" 'org-store-link)
  222. (global-set-key "\C-ca" 'org-agenda)
  223. (global-set-key "\C-cc" 'org-capture)
  224. (global-set-key "\C-cb" 'org-iswitchb)
  225. @end smalllisp
  226. Files with extension @samp{.org} will be put into Org mode automatically.
  227. @node Feedback, , Activation, Introduction
  228. @section Feedback
  229. If you find problems with Org, or if you have questions, remarks, or ideas
  230. about it, please mail to the Org mailing list @email{}.
  231. For information on how to submit bug reports, see the main manual.
  232. @node Document Structure, Tables, Introduction, Top
  233. @chapter Document Structure
  234. Org is based on Outline mode and provides flexible commands to
  235. edit the structure of the document.
  236. @menu
  237. * Outlines:: Org is based on Outline mode
  238. * Headlines:: How to typeset Org tree headlines
  239. * Visibility cycling:: Show and hide, much simplified
  240. * Motion:: Jumping to other headlines
  241. * Structure editing:: Changing sequence and level of headlines
  242. * Sparse trees:: Matches embedded in context
  243. * Plain lists:: Additional structure within an entry
  244. * Footnotes:: How footnotes are defined in Org's syntax
  245. @end menu
  246. @node Outlines, Headlines, Document Structure, Document Structure
  247. @section Outlines
  248. Org is implemented on top of Outline mode. Outlines allow a
  249. document to be organized in a hierarchical structure, which (at least
  250. for me) is the best representation of notes and thoughts. An overview
  251. of this structure is achieved by folding (hiding) large parts of the
  252. document to show only the general document structure and the parts
  253. currently being worked on. Org greatly simplifies the use of
  254. outlines by compressing the entire show/hide functionality into a single
  255. command, @command{org-cycle}, which is bound to the @key{TAB} key.
  256. @node Headlines, Visibility cycling, Outlines, Document Structure
  257. @section Headlines
  258. Headlines define the structure of an outline tree. The headlines in
  259. Org start with one or more stars, on the left margin@footnote{See
  260. the variable @code{org-special-ctrl-a/e} to configure special behavior
  261. of @kbd{C-a} and @kbd{C-e} in headlines.}. For example:
  262. @smallexample
  263. * Top level headline
  264. ** Second level
  265. *** 3rd level
  266. some text
  267. *** 3rd level
  268. more text
  269. * Another top level headline
  270. @end smallexample
  271. @noindent Note that a headline named after @code{org-footnote-section},
  272. which defaults to @samp{Footnotes}, is considered as special. A subtree with
  273. this headline will be silently ignored by exporting functions.
  274. Some people find the many stars too noisy and would prefer an
  275. outline that has whitespace followed by a single star as headline
  276. starters. @ref{Clean view}, describes a setup to realize this.
  277. @node Visibility cycling, Motion, Headlines, Document Structure
  278. @section Visibility cycling
  279. Outlines make it possible to hide parts of the text in the buffer.
  280. Org uses just two commands, bound to @key{TAB} and
  281. @kbd{S-@key{TAB}} to change the visibility in the buffer.
  282. @table @kbd
  283. @item @key{TAB}
  284. @emph{Subtree cycling}: Rotate current subtree among the states
  285. @smallexample
  286. ,-> FOLDED -> CHILDREN -> SUBTREE --.
  287. '-----------------------------------'
  288. @end smallexample
  289. When called with a prefix argument (@kbd{C-u @key{TAB}}) or with the shift
  290. key, global cycling is invoked.
  291. @item S-@key{TAB} @r{and} C-u @key{TAB}
  292. @emph{Global cycling}: Rotate the entire buffer among the states
  293. @smallexample
  294. ,-> OVERVIEW -> CONTENTS -> SHOW ALL --.
  295. '--------------------------------------'
  296. @end smallexample
  297. @item C-u C-u C-u @key{TAB}
  298. Show all, including drawers.
  299. @end table
  300. When Emacs first visits an Org file, the global state is set to
  301. OVERVIEW, i.e.@: only the top level headlines are visible. This can be
  302. configured through the variable @code{org-startup-folded}, or on a
  303. per-file basis by adding a startup keyword @code{overview}, @code{content},
  304. @code{showall}, like this:
  305. @smallexample
  306. #+STARTUP: content
  307. @end smallexample
  308. @node Motion, Structure editing, Visibility cycling, Document Structure
  309. @section Motion
  310. The following commands jump to other headlines in the buffer.
  311. @table @kbd
  312. @item C-c C-n
  313. Next heading.
  314. @item C-c C-p
  315. Previous heading.
  316. @item C-c C-f
  317. Next heading same level.
  318. @item C-c C-b
  319. Previous heading same level.
  320. @item C-c C-u
  321. Backward to higher level heading.
  322. @end table
  323. @node Structure editing, Sparse trees, Motion, Document Structure
  324. @section Structure editing
  325. @table @kbd
  326. @item M-@key{RET}
  327. Insert new heading with same level as current. If the cursor is in a plain
  328. list item, a new item is created (@pxref{Plain lists}). When this command is
  329. used in the middle of a line, the line is split and the rest of the line
  330. becomes the new headline@footnote{If you do not want the line to be split,
  331. customize the variable @code{org-M-RET-may-split-line}.}.
  332. @item M-S-@key{RET}
  333. Insert new TODO entry with same level as current heading.
  334. @item @key{TAB} @r{in new, empty entry}
  335. In a new entry with no text yet, @key{TAB} will cycle through reasonable
  336. levels.
  337. @item M-@key{left}@r{/}@key{right}
  338. Promote/demote current heading by one level.
  339. @item M-S-@key{left}@r{/}@key{right}
  340. Promote/demote the current subtree by one level.
  341. @item M-S-@key{up}@r{/}@key{down}
  342. Move subtree up/down (swap with previous/next subtree of same
  343. level).
  344. @item C-c C-w
  345. Refile entry or region to a different location. @xref{Refile and copy}.
  346. @item C-x n s/w
  347. Narrow buffer to current subtree / widen it again
  348. @end table
  349. When there is an active region (Transient Mark mode), promotion and
  350. demotion work on all headlines in the region.
  351. @node Sparse trees, Plain lists, Structure editing, Document Structure
  352. @section Sparse trees
  353. An important feature of Org mode is the ability to construct @emph{sparse
  354. trees} for selected information in an outline tree, so that the entire
  355. document is folded as much as possible, but the selected information is made
  356. visible along with the headline structure above it@footnote{See also the
  357. variable @code{org-show-context-detail} to decide how much context is shown
  358. around each match.}. Just try it out and you will see immediately how it
  359. works.
  360. Org mode contains several commands creating such trees, all these
  361. commands can be accessed through a dispatcher:
  362. @table @kbd
  363. @item C-c /
  364. This prompts for an extra key to select a sparse-tree creating command.
  365. @item C-c / r
  366. Occur. Prompts for a regexp and shows a sparse tree with all matches. Each
  367. match is also highlighted; the highlights disappear by pressing @kbd{C-c C-c}.
  368. @end table
  369. The other sparse tree commands select headings based on TODO keywords,
  370. tags, or properties and will be discussed later in this manual.
  371. @node Plain lists, Footnotes, Sparse trees, Document Structure
  372. @section Plain lists
  373. Within an entry of the outline tree, hand-formatted lists can provide
  374. additional structure. They also provide a way to create lists of
  375. checkboxes (@pxref{Checkboxes}). Org supports editing such lists,
  376. and the HTML exporter (@pxref{Exporting}) parses and formats them.
  377. Org knows ordered lists, unordered lists, and description lists.
  378. @itemize @bullet
  379. @item
  380. @emph{Unordered} list items start with @samp{-}, @samp{+}, or
  381. @samp{*} as bullets.
  382. @item
  383. @emph{Ordered} list items start with @samp{1.} or @samp{1)}.
  384. @item
  385. @emph{Description} list use @samp{ :: } to separate the @emph{term} from the
  386. description.
  387. @end itemize
  388. Items belonging to the same list must have the same indentation on the first
  389. line. An item ends before the next line that is indented like its
  390. bullet/number, or less. A list ends when all items are closed, or before two
  391. blank lines. An example:
  392. @smallexample
  393. @group
  394. ** Lord of the Rings
  395. My favorite scenes are (in this order)
  396. 1. The attack of the Rohirrim
  397. 2. Eowyn's fight with the witch king
  398. + this was already my favorite scene in the book
  399. + I really like Miranda Otto.
  400. Important actors in this film are:
  401. - @b{Elijah Wood} :: He plays Frodo
  402. - @b{Sean Astin} :: He plays Sam, Frodo's friend.
  403. @end group
  404. @end smallexample
  405. The following commands act on items when the cursor is in the first line of
  406. an item (the line with the bullet or number).
  407. @table @kbd
  408. @item @key{TAB}
  409. Items can be folded just like headline levels.
  410. @item M-@key{RET}
  411. Insert new item at current level. With a prefix argument, force a new
  412. heading (@pxref{Structure editing}).
  413. @item M-S-@key{RET}
  414. Insert a new item with a checkbox (@pxref{Checkboxes}).
  415. @item M-S-@key{up}@r{/}@key{down}
  416. Move the item including subitems up/down (swap with previous/next item
  417. of same indentation). If the list is ordered, renumbering is
  418. automatic.
  419. @item M-@key{left}@r{/}M-@key{right}
  420. Decrease/increase the indentation of an item, leaving children alone.
  421. @item M-S-@key{left}@r{/}@key{right}
  422. Decrease/increase the indentation of the item, including subitems.
  423. @item C-c C-c
  424. If there is a checkbox (@pxref{Checkboxes}) in the item line, toggle the
  425. state of the checkbox. Also verify bullets and indentation consistency in
  426. the whole list.
  427. @item C-c -
  428. Cycle the entire list level through the different itemize/enumerate bullets
  429. (@samp{-}, @samp{+}, @samp{*}, @samp{1.}, @samp{1)}).
  430. @end table
  431. @node Footnotes, , Plain lists, Document Structure
  432. @section Footnotes
  433. A footnote is defined in a paragraph that is started by a footnote marker in
  434. square brackets in column 0, no indentation allowed. The footnote reference
  435. is simply the marker in square brackets, inside text. For example:
  436. @smallexample
  437. The Org homepage[fn:1] now looks a lot better than it used to.
  438. ...
  439. [fn:1] The link is:
  440. @end smallexample
  441. @noindent
  442. The following commands handle footnotes:
  443. @table @kbd
  444. @item C-c C-x f
  445. The footnote action command. When the cursor is on a footnote reference,
  446. jump to the definition. When it is at a definition, jump to the (first)
  447. reference. Otherwise, create a new footnote. When this command is called
  448. with a prefix argument, a menu of additional options including renumbering is
  449. offered.
  450. @item C-c C-c
  451. Jump between definition and reference.
  452. @end table
  453. @seealso{
  454. @uref{,
  455. Chapter 2 of the manual}@*
  456. @uref{,
  457. Sacha Chua's tutorial}}
  458. @node Tables, Hyperlinks, Document Structure, Top
  459. @chapter Tables
  460. Org comes with a fast and intuitive table editor. Spreadsheet-like
  461. calculations are supported in connection with the Emacs @file{calc}
  462. package
  463. @ifinfo
  464. (@pxref{Top,Calc,,Calc,Gnu Emacs Calculator Manual}).
  465. @end ifinfo
  466. @ifnotinfo
  467. (see the Emacs Calculator manual for more information about the Emacs
  468. calculator).
  469. @end ifnotinfo
  470. Org makes it easy to format tables in plain ASCII. Any line with
  471. @samp{|} as the first non-whitespace character is considered part of a
  472. table. @samp{|} is also the column separator. A table might look like
  473. this:
  474. @smallexample
  475. | Name | Phone | Age |
  476. |-------+-------+-----|
  477. | Peter | 1234 | 17 |
  478. | Anna | 4321 | 25 |
  479. @end smallexample
  480. A table is re-aligned automatically each time you press @key{TAB} or
  481. @key{RET} or @kbd{C-c C-c} inside the table. @key{TAB} also moves to
  482. the next field (@key{RET} to the next row) and creates new table rows
  483. at the end of the table or before horizontal lines. The indentation
  484. of the table is set by the first line. Any line starting with
  485. @samp{|-} is considered as a horizontal separator line and will be
  486. expanded on the next re-align to span the whole table width. So, to
  487. create the above table, you would only type
  488. @smallexample
  489. |Name|Phone|Age|
  490. |-
  491. @end smallexample
  492. @noindent
  493. and then press @key{TAB} to align the table and start filling in
  494. fields. Even faster would be to type @code{|Name|Phone|Age} followed by
  495. @kbd{C-c @key{RET}}.
  496. When typing text into a field, Org treats @key{DEL},
  497. @key{Backspace}, and all character keys in a special way, so that
  498. inserting and deleting avoids shifting other fields. Also, when
  499. typing @emph{immediately after the cursor was moved into a new field
  500. with @kbd{@key{TAB}}, @kbd{S-@key{TAB}} or @kbd{@key{RET}}}, the
  501. field is automatically made blank.
  502. @table @kbd
  503. @tsubheading{Creation and conversion}
  504. @item C-c |
  505. Convert the active region to table. If every line contains at least one TAB
  506. character, the function assumes that the material is tab separated. If every
  507. line contains a comma, comma-separated values (CSV) are assumed. If not,
  508. lines are split at whitespace into fields.
  509. @*
  510. If there is no active region, this command creates an empty Org
  511. table. But it's easier just to start typing, like
  512. @kbd{|Name|Phone|Age C-c @key{RET}}.
  513. @tsubheading{Re-aligning and field motion}
  514. @item C-c C-c
  515. Re-align the table without moving the cursor.
  516. @c
  517. @item @key{TAB}
  518. Re-align the table, move to the next field. Creates a new row if
  519. necessary.
  520. @c
  521. @item S-@key{TAB}
  522. Re-align, move to previous field.
  523. @c
  524. @item @key{RET}
  525. Re-align the table and move down to next row. Creates a new row if
  526. necessary.
  527. @tsubheading{Column and row editing}
  528. @item M-@key{left}
  529. @itemx M-@key{right}
  530. Move the current column left/right.
  531. @c
  532. @item M-S-@key{left}
  533. Kill the current column.
  534. @c
  535. @item M-S-@key{right}
  536. Insert a new column to the left of the cursor position.
  537. @c
  538. @item M-@key{up}
  539. @itemx M-@key{down}
  540. Move the current row up/down.
  541. @c
  542. @item M-S-@key{up}
  543. Kill the current row or horizontal line.
  544. @c
  545. @item M-S-@key{down}
  546. Insert a new row above the current row. With a prefix argument, the line is
  547. created below the current one.
  548. @c
  549. @item C-c -
  550. Insert a horizontal line below current row. With a prefix argument, the line
  551. is created above the current line.
  552. @c
  553. @item C-c @key{RET}
  554. Insert a horizontal line below current row, and move the cursor into the row
  555. below that line.
  556. @c
  557. @item C-c ^
  558. Sort the table lines in the region. The position of point indicates the
  559. column to be used for sorting, and the range of lines is the range
  560. between the nearest horizontal separator lines, or the entire table.
  561. @end table
  562. @seealso{
  563. @uref{, Chapter 3 of the
  564. manual}@*
  565. @uref{, Bastien's
  566. table tutorial}@*
  567. @uref{,
  568. Bastien's spreadsheet tutorial}@*
  569. @uref{, Eric's plotting tutorial}}
  570. @node Hyperlinks, TODO Items, Tables, Top
  571. @chapter Hyperlinks
  572. Like HTML, Org provides links inside a file, external links to
  573. other files, Usenet articles, emails, and much more.
  574. @menu
  575. * Link format:: How links in Org are formatted
  576. * Internal links:: Links to other places in the current file
  577. * External links:: URL-like links to the world
  578. * Handling links:: Creating, inserting and following
  579. * Targeted links:: Point at a location in a file
  580. @end menu
  581. @node Link format, Internal links, Hyperlinks, Hyperlinks
  582. @section Link format
  583. Org will recognize plain URL-like links and activate them as
  584. clickable links. The general link format, however, looks like this:
  585. @smallexample
  586. [[link][description]] @r{or alternatively} [[link]]
  587. @end smallexample
  588. @noindent
  589. Once a link in the buffer is complete (all brackets present), Org will change
  590. the display so that @samp{description} is displayed instead of
  591. @samp{[[link][description]]} and @samp{link} is displayed instead of
  592. @samp{[[link]]}. To edit the invisible @samp{link} part, use @kbd{C-c
  593. C-l} with the cursor on the link.
  594. @node Internal links, External links, Link format, Hyperlinks
  595. @section Internal links
  596. If the link does not look like a URL, it is considered to be internal in the
  597. current file. The most important case is a link like
  598. @samp{[[#my-custom-id]]} which will link to the entry with the
  599. @code{CUSTOM_ID} property @samp{my-custom-id}.
  600. Links such as @samp{[[My Target]]} or @samp{[[My Target][Find my target]]}
  601. lead to a text search in the current file for the corresponding target which
  602. looks like @samp{<<My Target>>}.
  603. Internal links will be used to reference their destination, through links or
  604. numbers, when possible.
  605. @node External links, Handling links, Internal links, Hyperlinks
  606. @section External links
  607. Org supports links to files, websites, Usenet and email messages,
  608. BBDB database entries and links to both IRC conversations and their
  609. logs. External links are URL-like locators. They start with a short
  610. identifying string followed by a colon. There can be no space after
  611. the colon. Here are some examples:
  612. @smallexample
  613. @r{on the web}
  614. file:/home/dominik/images/jupiter.jpg @r{file, absolute path}
  615. /home/dominik/images/jupiter.jpg @r{same as above}
  616. file:papers/last.pdf @r{file, relative path}
  617. @r{another Org file}
  618. docview:papers/last.pdf::NNN @r{open file in doc-view mode at page NNN}
  619. id:B7423F4D-2E8A-471B-8810-C40F074717E9 @r{Link to heading by ID}
  620. news:comp.emacs @r{Usenet link}
  621. @r{Mail link}
  622. vm:folder @r{VM folder link}
  623. vm:folder#id @r{VM message link}
  624. wl:folder#id @r{WANDERLUST message link}
  625. mhe:folder#id @r{MH-E message link}
  626. rmail:folder#id @r{RMAIL message link}
  627. gnus:group#id @r{Gnus article link}
  628. bbdb:R.*Stallman @r{BBDB link (with regexp)}
  629. irc:/ @r{IRC link}
  630. info:org:External%20links @r{Info node link (with encoded space)}
  631. @end smallexample
  632. A link should be enclosed in double brackets and may contain a
  633. descriptive text to be displayed instead of the URL (@pxref{Link
  634. format}), for example:
  635. @smallexample
  636. [[][GNU Emacs]]
  637. @end smallexample
  638. @noindent
  639. If the description is a file name or URL that points to an image, HTML export
  640. (@pxref{HTML export}) will inline the image as a clickable button. If there
  641. is no description at all and the link points to an image, that image will be
  642. inlined into the exported HTML file.
  643. @node Handling links, Targeted links, External links, Hyperlinks
  644. @section Handling links
  645. Org provides methods to create a link in the correct syntax, to
  646. insert it into an Org file, and to follow the link.
  647. @table @kbd
  648. @item C-c l
  649. Store a link to the current location. This is a @emph{global} command (you
  650. must create the key binding yourself) which can be used in any buffer to
  651. create a link. The link will be stored for later insertion into an Org
  652. buffer (see below).
  653. @c
  654. @item C-c C-l
  655. Insert a link. This prompts for a link to be inserted into the buffer. You
  656. can just type a link, or use history keys @key{up} and @key{down} to access
  657. stored links. You will be prompted for the description part of the link.
  658. When called with a @kbd{C-u} prefix argument, file name completion is used to
  659. link to a file.
  660. @c
  661. @item C-c C-l @r{(with cursor on existing link)}
  662. When the cursor is on an existing link, @kbd{C-c C-l} allows you to edit the
  663. link and description parts of the link.
  664. @c
  665. @item C-c C-o @r{or} mouse-1 @r{or} mouse-2
  666. Open link at point.
  667. @item C-c &
  668. Jump back to a recorded position. A position is recorded by the
  669. commands following internal links, and by @kbd{C-c %}. Using this
  670. command several times in direct succession moves through a ring of
  671. previously recorded positions.
  672. @c
  673. @end table
  674. @node Targeted links, , Handling links, Hyperlinks
  675. @section Targeted links
  676. File links can contain additional information to make Emacs jump to a
  677. particular location in the file when following a link. This can be a
  678. line number or a search option after a double colon.
  679. Here is the syntax of the different ways to attach a search to a file
  680. link, together with an explanation:
  681. @smallexample
  682. [[file:~/code/main.c::255]] @r{Find line 255}
  683. [[file:~/ Target]] @r{Find @samp{<<My Target>>}}
  684. [[file:~/]] @r{Find entry with custom id}
  685. @end smallexample
  686. @seealso{
  687. @uref{, Chapter 4 of the
  688. manual}}
  689. @node TODO Items, Tags, Hyperlinks, Top
  690. @chapter TODO Items
  691. Org mode does not require TODO lists to live in separate documents. Instead,
  692. TODO items are part of a notes file, because TODO items usually
  693. come up while taking notes! With Org mode, simply mark any entry in a tree
  694. as being a TODO item. In this way, information is not duplicated, and TODO
  695. items remain in the context from which they emerged.
  696. Org mode providing methods to give you an overview of all the things that you
  697. have to do, collected from many files.
  698. @menu
  699. * Using TODO states:: Setting and switching states
  700. * Multi-state workflows:: More than just on/off
  701. * Progress logging:: Dates and notes for progress
  702. * Priorities:: Some things are more important than others
  703. * Breaking down tasks:: Splitting a task into manageable pieces
  704. * Checkboxes:: Tick-off lists
  705. @end menu
  706. @node Using TODO states, Multi-state workflows, TODO Items, TODO Items
  707. @section Using TODO states
  708. Any headline becomes a TODO item when it starts with the word
  709. @samp{TODO}, for example:
  710. @smallexample
  711. *** TODO Write letter to Sam Fortune
  712. @end smallexample
  713. @noindent
  714. The most important commands to work with TODO entries are:
  715. @table @kbd
  716. @item C-c C-t
  717. Rotate the TODO state of the current item among
  718. @smallexample
  719. (unmarked) -> TODO -> DONE -> (unmarked)
  720. @end smallexample
  721. The same rotation can also be done ``remotely'' from the timeline and
  722. agenda buffers with the @kbd{t} command key (@pxref{Agenda commands}).
  723. @item S-@key{right}@r{/}@key{left}
  724. Select the following/preceding TODO state, similar to cycling.
  725. @item C-c / t
  726. View TODO items in a @emph{sparse tree} (@pxref{Sparse trees}). Folds the
  727. buffer, but shows all TODO items and the headings hierarchy above
  728. them.
  729. @item C-c a t
  730. Show the global TODO list. Collects the TODO items from all agenda files
  731. (@pxref{Agenda Views}) into a single buffer. @xref{Global TODO list}, for
  732. more information.
  733. @item S-M-@key{RET}
  734. Insert a new TODO entry below the current one.
  735. @end table
  736. @noindent
  737. Changing a TODO state can also trigger tag changes. See the docstring of the
  738. option @code{org-todo-state-tags-triggers} for details.
  739. @node Multi-state workflows, Progress logging, Using TODO states, TODO Items
  740. @section Multi-state workflows
  741. You can use TODO keywords to indicate @emph{sequential} working progress
  742. states:
  743. @smalllisp
  744. (setq org-todo-keywords
  745. '((sequence "TODO" "FEEDBACK" "VERIFY" "|" "DONE" "DELEGATED")))
  746. @end smalllisp
  747. The vertical bar separates the TODO keywords (states that @emph{need action})
  748. from the DONE states (which need @emph{no further action}). If you don't
  749. provide the separator bar, the last state is used as the DONE state. With
  750. this setup, the command @kbd{C-c C-t} will cycle an entry from TODO to
  751. FEEDBACK, then to VERIFY, and finally to DONE and DELEGATED. Sometimes you
  752. may want to use different sets of TODO keywords in parallel. For example,
  753. you may want to have the basic @code{TODO}/@code{DONE}, but also a workflow
  754. for bug fixing. Your setup would then look like this:
  755. @smalllisp
  756. (setq org-todo-keywords
  757. '((sequence "TODO(t)" "|" "DONE(d)")
  758. (sequence "REPORT(r)" "BUG(b)" "KNOWNCAUSE(k)" "|" "FIXED(f)")))
  759. @end smalllisp
  760. The keywords should all be different, this helps Org mode to keep track of
  761. which subsequence should be used for a given entry. The example also shows
  762. how to define keys for fast access of a particular state, by adding a letter
  763. in parenthesis after each keyword---you will be prompted for the key after
  764. @kbd{C-c C-t}.
  765. To define TODO keywords that are valid only in a single file, use the
  766. following text anywhere in the file.
  767. @smallexample
  768. #+TODO: TODO(t) | DONE(d)
  769. #+TODO: REPORT(r) BUG(b) KNOWNCAUSE(k) | FIXED(f)
  770. #+TODO: | CANCELED(c)
  771. @end smallexample
  772. After changing one of these lines, use @kbd{C-c C-c} with the cursor still in
  773. the line to make the changes known to Org mode.
  774. @node Progress logging, Priorities, Multi-state workflows, TODO Items
  775. @section Progress logging
  776. Org mode can automatically record a timestamp and possibly a note when
  777. you mark a TODO item as DONE, or even each time you change the state of
  778. a TODO item. This system is highly configurable; settings can be on a
  779. per-keyword basis and can be localized to a file or even a subtree. For
  780. information on how to clock working time for a task, see @ref{Clocking
  781. work time}.
  782. @menu
  783. * Closing items:: When was this entry marked DONE?
  784. * Tracking TODO state changes:: When did the status change?
  785. @end menu
  786. @node Closing items, Tracking TODO state changes, Progress logging, Progress logging
  787. @unnumberedsubsec Closing items
  788. The most basic logging is to keep track of @emph{when} a certain TODO
  789. item was finished. This is achieved with@footnote{The corresponding
  790. in-buffer setting is: @code{#+STARTUP: logdone}}.
  791. @smalllisp
  792. (setq org-log-done 'time)
  793. @end smalllisp
  794. @noindent
  795. Then each time you turn an entry from a TODO (not-done) state into any of the
  796. DONE states, a line @samp{CLOSED: [timestamp]} will be inserted just after
  797. the headline. If you want to record a note along with the timestamp,
  798. use@footnote{The corresponding in-buffer setting is: @code{#+STARTUP:
  799. lognotedone}}
  800. @smalllisp
  801. (setq org-log-done 'note)
  802. @end smalllisp
  803. @noindent
  804. You will then be prompted for a note, and that note will be stored below
  805. the entry with a @samp{Closing Note} heading.
  806. @node Tracking TODO state changes, , Closing items, Progress logging
  807. @unnumberedsubsec Tracking TODO state changes
  808. You might want to keep track of TODO state changes. You can either record
  809. just a timestamp, or a time-stamped note for a change. These records will be
  810. inserted after the headline as an itemized list. When taking a lot of notes,
  811. you might want to get the notes out of the way into a drawer. Customize the
  812. variable @code{org-log-into-drawer} to get this behavior.
  813. For state logging, Org mode expects configuration on a per-keyword basis.
  814. This is achieved by adding special markers @samp{!} (for a timestamp) and
  815. @samp{@@} (for a note) in parentheses after each keyword. For example:
  816. @smallexample
  817. #+TODO: TODO(t) WAIT(w@@/!) | DONE(d!) CANCELED(c@@)
  818. @end smallexample
  819. @noindent
  820. will define TODO keywords and fast access keys, and also request that a time
  821. is recorded when the entry is set to DONE, and that a note is recorded when
  822. switching to WAIT or CANCELED. The same syntax works also when setting
  823. @code{org-todo-keywords}.
  824. @node Priorities, Breaking down tasks, Progress logging, TODO Items
  825. @section Priorities
  826. If you use Org mode extensively, you may end up with enough TODO items that
  827. it starts to make sense to prioritize them. Prioritizing can be done by
  828. placing a @emph{priority cookie} into the headline of a TODO item, like this
  829. @smallexample
  830. *** TODO [#A] Write letter to Sam Fortune
  831. @end smallexample
  832. @noindent
  833. Org mode supports three priorities: @samp{A}, @samp{B}, and @samp{C}.
  834. @samp{A} is the highest, @samp{B} the default if none is given. Priorities
  835. make a difference only in the agenda.
  836. @table @kbd
  837. @item @kbd{C-c ,}
  838. Set the priority of the current headline. Press @samp{A}, @samp{B} or
  839. @samp{C} to select a priority, or @key{SPC} to remove the cookie.
  840. @c
  841. @item S-@key{up}/@key{dwn}
  842. Increase/decrease priority of current headline
  843. @end table
  844. @node Breaking down tasks, Checkboxes, Priorities, TODO Items
  845. @section Breaking tasks down into subtasks
  846. It is often advisable to break down large tasks into smaller, manageable
  847. subtasks. You can do this by creating an outline tree below a TODO item,
  848. with detailed subtasks on the tree. To keep the overview over the fraction
  849. of subtasks that are already completed, insert either @samp{[/]} or
  850. @samp{[%]} anywhere in the headline. These cookies will be updated each time
  851. the TODO status of a child changes, or when pressing @kbd{C-c C-c} on the
  852. cookie. For example:
  853. @smallexample
  854. * Organize Party [33%]
  855. ** TODO Call people [1/2]
  856. *** TODO Peter
  857. *** DONE Sarah
  858. ** TODO Buy food
  859. ** DONE Talk to neighbor
  860. @end smallexample
  861. @node Checkboxes, , Breaking down tasks, TODO Items
  862. @section Checkboxes
  863. Every item in a plain list (@pxref{Plain lists}) can be made into a checkbox
  864. by starting it with the string @samp{[ ]}. Checkboxes are not included in
  865. the global TODO list, so they are often great to split a task into a number
  866. of simple steps.
  867. Here is an example of a checkbox list.
  868. @smallexample
  869. * TODO Organize party [1/3]
  870. - [-] call people [1/2]
  871. - [ ] Peter
  872. - [X] Sarah
  873. - [X] order food
  874. @end smallexample
  875. Checkboxes work hierarchically, so if a checkbox item has children that
  876. are checkboxes, toggling one of the children checkboxes will make the
  877. parent checkbox reflect if none, some, or all of the children are
  878. checked.
  879. @noindent
  880. The following commands work with checkboxes:
  881. @table @kbd
  882. @item C-c C-c
  883. Toggle checkbox status or (with prefix arg) checkbox presence at point.
  884. @item M-S-@key{RET}
  885. Insert a new item with a checkbox.
  886. This works only if the cursor is already in a plain list item
  887. (@pxref{Plain lists}).
  888. @end table
  889. @seealso{
  890. @uref{, Chapter 5 of the manual}@*
  891. @uref{, David
  892. O'Toole's introductory tutorial}@*
  893. @uref{,
  894. Charles Cave's GTD setup}}
  895. @node Tags, Properties, TODO Items, Top
  896. @chapter Tags
  897. An excellent way to implement labels and contexts for cross-correlating
  898. information is to assign @i{tags} to headlines. Org mode has extensive
  899. support for tags.
  900. Every headline can contain a list of tags; they occur at the end of the
  901. headline. Tags are normal words containing letters, numbers, @samp{_}, and
  902. @samp{@@}. Tags must be preceded and followed by a single colon, e.g.,
  903. @samp{:work:}. Several tags can be specified, as in @samp{:work:urgent:}.
  904. Tags will by default be in bold face with the same color as the headline.
  905. @menu
  906. * Tag inheritance:: Tags use the tree structure of the outline
  907. * Setting tags:: How to assign tags to a headline
  908. * Tag groups:: Use one tag to search for several tags
  909. * Tag searches:: Searching for combinations of tags
  910. @end menu
  911. @node Tag inheritance, Setting tags, Tags, Tags
  912. @section Tag inheritance
  913. @i{Tags} make use of the hierarchical structure of outline trees. If a
  914. heading has a certain tag, all subheadings will inherit the tag as
  915. well. For example, in the list
  916. @smallexample
  917. * Meeting with the French group :work:
  918. ** Summary by Frank :boss:notes:
  919. *** TODO Prepare slides for him :action:
  920. @end smallexample
  921. @noindent
  922. the final heading will have the tags @samp{:work:}, @samp{:boss:},
  923. @samp{:notes:}, and @samp{:action:} even though the final heading is not
  924. explicitly marked with those tags. You can also set tags that all entries in
  925. a file should inherit just as if these tags were defined in a hypothetical
  926. level zero that surrounds the entire file. Use a line like this@footnote{As
  927. with all these in-buffer settings, pressing @kbd{C-c C-c} activates any
  928. changes in the line.}:
  929. @smallexample
  930. #+FILETAGS: :Peter:Boss:Secret:
  931. @end smallexample
  932. @node Setting tags, Tag groups, Tag inheritance, Tags
  933. @section Setting tags
  934. Tags can simply be typed into the buffer at the end of a headline.
  935. After a colon, @kbd{M-@key{TAB}} offers completion on tags. There is
  936. also a special command for inserting tags:
  937. @table @kbd
  938. @item C-c C-q
  939. Enter new tags for the current headline. Org mode will either offer
  940. completion or a special single-key interface for setting tags, see
  941. below. After pressing @key{RET}, the tags will be inserted and aligned
  942. to @code{org-tags-column}. When called with a @kbd{C-u} prefix, all
  943. tags in the current buffer will be aligned to that column, just to make
  944. things look nice.
  945. @item C-c C-c
  946. When the cursor is in a headline, this does the same as @kbd{C-c C-q}.
  947. @end table
  948. Org will support tag insertion based on a @emph{list of tags}. By
  949. default this list is constructed dynamically, containing all tags
  950. currently used in the buffer. You may also globally specify a hard list
  951. of tags with the variable @code{org-tag-alist}. Finally you can set
  952. the default tags for a given file with lines like
  953. @smallexample
  954. #+TAGS: @@work @@home @@tennisclub
  955. #+TAGS: laptop car pc sailboat
  956. @end smallexample
  957. By default Org mode uses the standard minibuffer completion facilities for
  958. entering tags. However, it also implements another, quicker, tag selection
  959. method called @emph{fast tag selection}. This allows you to select and
  960. deselect tags with just a single key press. For this to work well you should
  961. assign unique letters to most of your commonly used tags. You can do this
  962. globally by configuring the variable @code{org-tag-alist} in your
  963. @file{.emacs} file. For example, you may find the need to tag many items in
  964. different files with @samp{:@@home:}. In this case you can set something
  965. like:
  966. @smalllisp
  967. (setq org-tag-alist '(("@@work" . ?w) ("@@home" . ?h) ("laptop" . ?l)))
  968. @end smalllisp
  969. @noindent
  970. If the tag is only relevant to the file you are working on, then you
  971. can instead set the TAGS option line as:
  972. @smallexample
  973. #+TAGS: @@work(w) @@home(h) @@tennisclub(t) laptop(l) pc(p)
  974. @end smallexample
  975. @node Tag groups, Tag searches, Setting tags, Tags
  976. @section Tag groups
  977. @cindex group tags
  978. @cindex tags, groups
  979. In a set of mutually exclusive tags, the first tag can be defined as a
  980. @emph{group tag}. When you search for a group tag, it will return matches
  981. for all members in the group. In an agenda view, filtering by a group tag
  982. will display headlines tagged with at least one of the members of the
  983. group. This makes tag searches and filters even more flexible.
  984. You can set group tags by inserting a colon between the group tag and other
  985. tags, like this:
  986. @example
  987. #+TAGS: @{ @@read : @@read_book @@read_ebook @}
  988. @end example
  989. In this example, @samp{@@read} is a @emph{group tag} for a set of three
  990. tags: @samp{@@read}, @samp{@@read_book} and @samp{@@read_ebook}.
  991. You can also use the @code{:grouptags} keyword directly when setting
  992. @var{org-tag-alist}, see the documentation of that variable.
  993. @kindex C-c C-x q
  994. @vindex org-group-tags
  995. If you want to ignore group tags temporarily, toggle group tags support
  996. with @command{org-toggle-tags-groups}, bound to @kbd{C-c C-x q}. If you
  997. want to disable tag groups completely, set @var{org-group-tags} to nil.
  998. @node Tag searches, , Tag groups, Tags
  999. @section Tag searches
  1000. Once a system of tags has been set up, it can be used to collect related
  1001. information into special lists.
  1002. @table @kbd
  1003. @item C-c \
  1004. @itemx C-c / m
  1005. Create a sparse tree with all headlines matching a tags search. With a
  1006. @kbd{C-u} prefix argument, ignore headlines that are not a TODO line.
  1007. @item C-c a m
  1008. Create a global list of tag matches from all agenda files.
  1009. @xref{Matching tags and properties}.
  1010. @item C-c a M
  1011. Create a global list of tag matches from all agenda files, but check
  1012. only TODO items and force checking subitems (see variable
  1013. @code{org-tags-match-list-sublevels}).
  1014. @end table
  1015. These commands all prompt for a match string which allows basic Boolean logic
  1016. like @samp{+boss+urgent-project1}, to find entries with tags @samp{boss} and
  1017. @samp{urgent}, but not @samp{project1}, or @samp{Kathy|Sally} to find entries
  1018. which are tagged, like @samp{Kathy} or @samp{Sally}. The full syntax of the
  1019. search string is rich and allows also matching against TODO keywords, entry
  1020. levels and properties. For a complete description with many examples, see
  1021. @ref{Matching tags and properties}.
  1022. @seealso{
  1023. @uref{, Chapter 6 of the manual}@*
  1024. @uref{,
  1025. Sacha Chua's article about tagging in Org-mode}}
  1026. @node Properties, Dates and Times, Tags, Top
  1027. @chapter Properties
  1028. Properties are key-value pairs associated with an entry. They live in a
  1029. special drawer with the name @code{PROPERTIES}. Each
  1030. property is specified on a single line, with the key (surrounded by colons)
  1031. first, and the value after it:
  1032. @smallexample
  1033. * CD collection
  1034. ** Classic
  1035. *** Goldberg Variations
  1036. :PROPERTIES:
  1037. :Title: Goldberg Variations
  1038. :Composer: J.S. Bach
  1039. :Publisher: Deutsche Grammophon
  1040. :NDisks: 1
  1041. :END:
  1042. @end smallexample
  1043. You may define the allowed values for a particular property @samp{:Xyz:}
  1044. by setting a property @samp{:Xyz_ALL:}. This special property is
  1045. @emph{inherited}, so if you set it in a level 1 entry, it will apply to
  1046. the entire tree. When allowed values are defined, setting the
  1047. corresponding property becomes easier and is less prone to typing
  1048. errors. For the example with the CD collection, we can predefine
  1049. publishers and the number of disks in a box like this:
  1050. @smallexample
  1051. * CD collection
  1052. :PROPERTIES:
  1053. :NDisks_ALL: 1 2 3 4
  1054. :Publisher_ALL: "Deutsche Grammophon" Philips EMI
  1055. :END:
  1056. @end smallexample
  1057. or globally using @code{org-global-properties}, or file-wide like this:
  1058. @smallexample
  1059. #+PROPERTY: NDisks_ALL 1 2 3 4
  1060. @end smallexample
  1061. @table @kbd
  1062. @item C-c C-x p
  1063. Set a property. This prompts for a property name and a value.
  1064. @item C-c C-c d
  1065. Remove a property from the current entry.
  1066. @end table
  1067. To create sparse trees and special lists with selection based on properties,
  1068. the same commands are used as for tag searches (@pxref{Tag searches}). The
  1069. syntax for the search string is described in @ref{Matching tags and
  1070. properties}.
  1071. @table @kbd
  1072. @end table
  1073. @seealso{
  1074. @uref{,
  1075. Chapter 7 of the manual}@*
  1076. @uref{,Bastien
  1077. Guerry's column view tutorial}}
  1078. @node Dates and Times, Capture - Refile - Archive, Properties, Top
  1079. @chapter Dates and Times
  1080. To assist project planning, TODO items can be labeled with a date and/or
  1081. a time. The specially formatted string carrying the date and time
  1082. information is called a @emph{timestamp} in Org mode.
  1083. @menu
  1084. * Timestamps:: Assigning a time to a tree entry
  1085. * Creating timestamps:: Commands which insert timestamps
  1086. * Deadlines and scheduling:: Planning your work
  1087. * Clocking work time:: Tracking how long you spend on a task
  1088. @end menu
  1089. @node Timestamps, Creating timestamps, Dates and Times, Dates and Times
  1090. @section Timestamps
  1091. A timestamp is a specification of a date (possibly with a time or a range of
  1092. times) in a special format, either @samp{<2003-09-16 Tue>} or
  1093. @samp{<2003-09-16 Tue 09:39>} or @samp{<2003-09-16 Tue 12:00-12:30>}. A
  1094. timestamp can appear anywhere in the headline or body of an Org tree entry.
  1095. Its presence causes entries to be shown on specific dates in the agenda
  1096. (@pxref{Weekly/daily agenda}). We distinguish:
  1097. @noindent
  1098. @b{Plain timestamp; Event; Appointment}@*
  1099. A simple timestamp just assigns a date/time to an item. This is just
  1100. like writing down an appointment or event in a paper agenda.
  1101. @smallexample
  1102. * Meet Peter at the movies
  1103. <2006-11-01 Wed 19:15>
  1104. * Discussion on climate change
  1105. <2006-11-02 Thu 20:00-22:00>
  1106. @end smallexample
  1107. @noindent
  1108. @b{Timestamp with repeater interval}@*
  1109. A timestamp may contain a @emph{repeater interval}, indicating that it
  1110. applies not only on the given date, but again and again after a certain
  1111. interval of N days (d), weeks (w), months (m), or years (y). The
  1112. following will show up in the agenda every Wednesday:
  1113. @smallexample
  1114. * Pick up Sam at school
  1115. <2007-05-16 Wed 12:30 +1w>
  1116. @end smallexample
  1117. @noindent
  1118. @b{Diary-style sexp entries}@*
  1119. For more complex date specifications, Org mode supports using the
  1120. special sexp diary entries implemented in the Emacs calendar/diary
  1121. package. For example
  1122. @smallexample
  1123. * The nerd meeting on every 2nd Thursday of the month
  1124. <%%(diary-float t 4 2)>
  1125. @end smallexample
  1126. @noindent
  1127. @b{Time/Date range}@*
  1128. Two timestamps connected by @samp{--} denote a range.
  1129. @smallexample
  1130. ** Meeting in Amsterdam
  1131. <2004-08-23 Mon>--<2004-08-26 Thu>
  1132. @end smallexample
  1133. @noindent
  1134. @b{Inactive timestamp}@*
  1135. Just like a plain timestamp, but with square brackets instead of
  1136. angular ones. These timestamps are inactive in the sense that they do
  1137. @emph{not} trigger an entry to show up in the agenda.
  1138. @smallexample
  1139. * Gillian comes late for the fifth time
  1140. [2006-11-01 Wed]
  1141. @end smallexample
  1142. @node Creating timestamps, Deadlines and scheduling, Timestamps, Dates and Times
  1143. @section Creating timestamps
  1144. For Org mode to recognize timestamps, they need to be in the specific
  1145. format. All commands listed below produce timestamps in the correct
  1146. format.
  1147. @table @kbd
  1148. @item C-c .
  1149. Prompt for a date and insert a corresponding timestamp. When the cursor is
  1150. at an existing timestamp in the buffer, the command is used to modify this
  1151. timestamp instead of inserting a new one. When this command is used twice in
  1152. succession, a time range is inserted. With a prefix, also add the current
  1153. time.
  1154. @c
  1155. @item C-c !
  1156. Like @kbd{C-c .}, but insert an inactive timestamp that will not cause
  1157. an agenda entry.
  1158. @c
  1159. @item S-@key{left}@r{/}@key{right}
  1160. Change date at cursor by one day.
  1161. @c
  1162. @item S-@key{up}@r{/}@key{down}
  1163. Change the item under the cursor in a timestamp. The cursor can be on a
  1164. year, month, day, hour or minute. When the timestamp contains a time range
  1165. like @samp{15:30-16:30}, modifying the first time will also shift the second,
  1166. shifting the time block with constant length. To change the length, modify
  1167. the second time.
  1168. @end table
  1169. When Org mode prompts for a date/time, it will accept any string containing
  1170. some date and/or time information, and intelligently interpret the string,
  1171. deriving defaults for unspecified information from the current date and time.
  1172. You can also select a date in the pop-up calendar. See the manual for more
  1173. information on how exactly the date/time prompt works.
  1174. @node Deadlines and scheduling, Clocking work time, Creating timestamps, Dates and Times
  1175. @section Deadlines and scheduling
  1176. A timestamp may be preceded by special keywords to facilitate planning:
  1177. @noindent
  1178. @b{DEADLINE}@*
  1179. Meaning: the task (most likely a TODO item, though not necessarily) is supposed
  1180. to be finished on that date.
  1181. @table @kbd
  1182. @item C-c C-d
  1183. Insert @samp{DEADLINE} keyword along with a stamp, in the line following the
  1184. headline.
  1185. @end table
  1186. On the deadline date, the task will be listed in the agenda. In
  1187. addition, the agenda for @emph{today} will carry a warning about the
  1188. approaching or missed deadline, starting
  1189. @code{org-deadline-warning-days} before the due date, and continuing
  1190. until the entry is marked DONE. An example:
  1191. @smallexample
  1192. *** TODO write article about the Earth for the Guide
  1193. The editor in charge is [[bbdb:Ford Prefect]]
  1194. DEADLINE: <2004-02-29 Sun>
  1195. @end smallexample
  1196. @noindent
  1197. @b{SCHEDULED}@*
  1198. Meaning: you are @i{planning to start working} on that task on the given
  1199. date@footnote{This is quite different from what is normally understood by
  1200. @i{scheduling a meeting}, which is done in Org-mode by just inserting a time
  1201. stamp without keyword.}.
  1202. @table @kbd
  1203. @item C-c C-s
  1204. Insert @samp{SCHEDULED} keyword along with a stamp, in the line following the
  1205. headline.
  1206. @end table
  1207. The headline will be listed under the given date@footnote{It will still
  1208. be listed on that date after it has been marked DONE. If you don't like
  1209. this, set the variable @code{org-agenda-skip-scheduled-if-done}.}. In
  1210. addition, a reminder that the scheduled date has passed will be present
  1211. in the compilation for @emph{today}, until the entry is marked DONE.
  1212. I.e.@: the task will automatically be forwarded until completed.
  1213. @smallexample
  1214. *** TODO Call Trillian for a date on New Years Eve.
  1215. SCHEDULED: <2004-12-25 Sat>
  1216. @end smallexample
  1217. Some tasks need to be repeated again and again. Org mode helps to
  1218. organize such tasks using a so-called repeater in a DEADLINE, SCHEDULED,
  1219. or plain timestamp. In the following example
  1220. @smallexample
  1221. ** TODO Pay the rent
  1222. DEADLINE: <2005-10-01 Sat +1m>
  1223. @end smallexample
  1224. @noindent
  1225. the @code{+1m} is a repeater; the intended interpretation is that the task
  1226. has a deadline on <2005-10-01> and repeats itself every (one) month starting
  1227. from that time.
  1228. @node Clocking work time, , Deadlines and scheduling, Dates and Times
  1229. @section Clocking work time
  1230. Org mode allows you to clock the time you spend on specific tasks in a
  1231. project.
  1232. @table @kbd
  1233. @item C-c C-x C-i
  1234. Start the clock on the current item (clock-in). This inserts the CLOCK
  1235. keyword together with a timestamp. When called with a @kbd{C-u} prefix
  1236. argument, select the task from a list of recently clocked tasks.
  1237. @c
  1238. @item C-c C-x C-o
  1239. Stop the clock (clock-out). This inserts another timestamp at the same
  1240. location where the clock was last started. It also directly computes
  1241. the resulting time in inserts it after the time range as @samp{=>
  1242. HH:MM}.
  1243. @item C-c C-x C-e
  1244. Update the effort estimate for the current clock task.
  1245. @item C-c C-x C-q
  1246. Cancel the current clock. This is useful if a clock was started by
  1247. mistake, or if you ended up working on something else.
  1248. @item C-c C-x C-j
  1249. Jump to the entry that contains the currently running clock. With a
  1250. @kbd{C-u} prefix arg, select the target task from a list of recently clocked
  1251. tasks.
  1252. @item C-c C-x C-r
  1253. Insert a dynamic block containing a clock
  1254. report as an Org-mode table into the current file. When the cursor is
  1255. at an existing clock table, just update it.
  1256. @smallexample
  1257. #+BEGIN: clocktable :maxlevel 2 :emphasize nil :scope file
  1258. #+END: clocktable
  1259. @end smallexample
  1260. @noindent
  1261. For details about how to customize this view, see @uref{,the manual}.
  1262. @item C-c C-c
  1263. Update dynamic block at point. The cursor needs to be in the
  1264. @code{#+BEGIN} line of the dynamic block.
  1265. @end table
  1266. The @kbd{l} key may be used in the timeline (@pxref{Timeline}) and in
  1267. the agenda (@pxref{Weekly/daily agenda}) to show which tasks have been
  1268. worked on or closed during a day.
  1269. @seealso{
  1270. @uref{,
  1271. Chapter 8 of the manual}@*
  1272. @uref{, Charles
  1273. Cave's Date and Time tutorial}@*
  1274. @uref{, Bernt Hansen's clocking workflow}}
  1275. @node Capture - Refile - Archive, Agenda Views, Dates and Times, Top
  1276. @chapter Capture - Refile - Archive
  1277. An important part of any organization system is the ability to quickly
  1278. capture new ideas and tasks, and to associate reference material with them.
  1279. Org defines a capture process to create tasks. Once in the system, tasks and
  1280. projects need to be moved around. Moving completed project trees to an
  1281. archive file keeps the system compact and fast.
  1282. @menu
  1283. * Capture:: Capturing new stuff
  1284. * Refile and copy:: Moving a tree from one place to another
  1285. * Archiving:: What to do with finished projects
  1286. @end menu
  1287. @node Capture, Refile and copy, Capture - Refile - Archive, Capture - Refile - Archive
  1288. @section Capture
  1289. Org's lets you store quick notes with little interruption of your work flow.
  1290. You can define templates for new entries and associate them with different
  1291. targets for storing notes.
  1292. @menu
  1293. * Setting up a capture location:: Where notes will be stored
  1294. * Using capture:: Commands to invoke and terminate capture
  1295. * Capture templates:: Define the outline of different note types
  1296. @end menu
  1297. @node Setting up a capture location, Using capture, Capture, Capture
  1298. @unnumberedsubsec Setting up a capture location
  1299. The following customization sets a default target@footnote{Using capture
  1300. templates, you get finer control over capture locations, see
  1301. @ref{Capture templates}.} file for notes, and defines a global
  1302. key for capturing new stuff.
  1303. @example
  1304. (setq org-default-notes-file (concat org-directory "/"))
  1305. (define-key global-map "\C-cc" 'org-capture)
  1306. @end example
  1307. @node Using capture, Capture templates, Setting up a capture location, Capture
  1308. @unnumberedsubsec Using capture
  1309. @table @kbd
  1310. @item C-c c
  1311. Start a capture process, placing you into a narrowed indirect buffer to edit.
  1312. @item C-c C-c
  1313. Once you are done entering information into the capture buffer,
  1314. @kbd{C-c C-c} will return you to the window configuration before the capture
  1315. process, so that you can resume your work without further distraction.
  1316. @item C-c C-w
  1317. Finalize by moving the entry to a refile location (see section 9.2).
  1318. @item C-c C-k
  1319. Abort the capture process and return to the previous state.
  1320. @end table
  1321. @node Capture templates, , Using capture, Capture
  1322. @unnumberedsubsec Capture templates
  1323. You can use templates to generate different types of capture notes, and to
  1324. store them in different places. For example, if you would like
  1325. to store new tasks under a heading @samp{Tasks} in file @file{}, and
  1326. journal entries in a date tree in @file{} you could
  1327. use:
  1328. @smallexample
  1329. (setq org-capture-templates
  1330. '(("t" "Todo" entry (file+headline "~/org/" "Tasks")
  1331. "* TODO %?\n %i\n %a")
  1332. ("j" "Journal" entry (file+datetree "~/org/")
  1333. "* %?\nEntered on %U\n %i\n %a")))
  1334. @end smallexample
  1335. @noindent
  1336. In these entries, the first string is the key to reach the
  1337. template, the second is a short description. Then follows the type of the
  1338. entry and a definition of the target location for storing the note. Finally,
  1339. the template itself, a string with %-escapes to fill in information based on
  1340. time and context.
  1341. When you call @kbd{M-x org-capture}, Org will prompt for a key to select the
  1342. template (if you have more than one template) and then prepare the buffer like
  1343. @smallexample
  1344. * TODO
  1345. [[file:@var{link to where you were when initiating capture}]]
  1346. @end smallexample
  1347. @noindent
  1348. During expansion of the template, special @kbd{%}-escapes@footnote{If you
  1349. need one of these sequences literally, escape the @kbd{%} with a backslash.}
  1350. allow dynamic insertion of content. Here is a small selection of the
  1351. possibilities, consult the manual for more.
  1352. @smallexample
  1353. %a @r{annotation, normally the link created with @code{org-store-link}}
  1354. %i @r{initial content, the region when capture is called with C-u.}
  1355. %t, %T @r{timestamp, date only, or date and time}
  1356. %u, %U @r{like above, but inactive timestamps}
  1357. @end smallexample
  1358. @node Refile and copy, Archiving, Capture, Capture - Refile - Archive
  1359. @section Refile and copy
  1360. When reviewing the captured data, you may want to refile or copy some of the
  1361. entries into a different list, for example into a project. Cutting, finding
  1362. the right location, and then pasting the note is cumbersome. To simplify
  1363. this process, use the following commands:
  1364. @table @kbd
  1365. @item C-c M-x
  1366. Copy the entry or region at point. This command behaves like
  1367. @code{org-refile}, except that the original note will not be deleted.
  1368. @item C-c C-w
  1369. Refile the entry or region at point. This command offers possible locations
  1370. for refiling the entry and lets you select one with completion. The item (or
  1371. all items in the region) is filed below the target heading as a subitem.@*
  1372. By default, all level 1 headlines in the current buffer are considered to be
  1373. targets, but you can have more complex definitions across a number of files.
  1374. See the variable @code{org-refile-targets} for details.
  1375. @item C-u C-c C-w
  1376. Use the refile interface to jump to a heading.
  1377. @item C-u C-u C-c C-w
  1378. Jump to the location where @code{org-refile} last moved a tree to.
  1379. @end table
  1380. @node Archiving, , Refile and copy, Capture - Refile - Archive
  1381. @section Archiving
  1382. When a project represented by a (sub)tree is finished, you may want
  1383. to move the tree out of the way and to stop it from contributing to the
  1384. agenda. Archiving is important to keep your working files compact and global
  1385. searches like the construction of agenda views fast.
  1386. The most common archiving action is to move a project tree to another file,
  1387. the archive file.
  1388. @table @kbd
  1389. @item C-c C-x C-a
  1390. Archive the current entry using @code{org-archive-default-command}.
  1391. @item C-c C-x C-s@ @r{or short} @ C-c $
  1392. Archive the subtree starting at the cursor position to the location
  1393. given by @code{org-archive-location}.
  1394. @end table
  1395. The default archive location is a file in the same directory as the
  1396. current file, with the name derived by appending @file{_archive} to the
  1397. current file name. For information and examples on how to change this,
  1398. see the documentation string of the variable
  1399. @code{org-archive-location}. There is also an in-buffer option for
  1400. setting this variable, for example
  1401. @smallexample
  1402. #+ARCHIVE: %s_done::
  1403. @end smallexample
  1404. @seealso{
  1405. @uref{,
  1406. Chapter 9 of the manual}@*
  1407. @uref{,
  1408. Sebastian Rose's tutorial for capturing from a web browser}}@uref{}@*
  1409. @node Agenda Views, Markup, Capture - Refile - Archive, Top
  1410. @chapter Agenda Views
  1411. Due to the way Org works, TODO items, time-stamped items, and tagged
  1412. headlines can be scattered throughout a file or even a number of files. To
  1413. get an overview of open action items, or of events that are important for a
  1414. particular date, this information must be collected, sorted and displayed in
  1415. an organized way. There are several different views, see below.
  1416. The extracted information is displayed in a special @emph{agenda buffer}.
  1417. This buffer is read-only, but provides commands to visit the corresponding
  1418. locations in the original Org files, and even to edit these files remotely.
  1419. Remote editing from the agenda buffer means, for example, that you can
  1420. change the dates of deadlines and appointments from the agenda buffer.
  1421. The commands available in the Agenda buffer are listed in @ref{Agenda
  1422. commands}.
  1423. @menu
  1424. * Agenda files:: Files being searched for agenda information
  1425. * Agenda dispatcher:: Keyboard access to agenda views
  1426. * Built-in agenda views:: What is available out of the box?
  1427. * Agenda commands:: Remote editing of Org trees
  1428. * Custom agenda views:: Defining special searches and views
  1429. @end menu
  1430. @node Agenda files, Agenda dispatcher, Agenda Views, Agenda Views
  1431. @section Agenda files
  1432. The information to be shown is normally collected from all @emph{agenda
  1433. files}, the files listed in the variable
  1434. @code{org-agenda-files}.
  1435. @table @kbd
  1436. @item C-c [
  1437. Add current file to the list of agenda files. The file is added to
  1438. the front of the list. If it was already in the list, it is moved to
  1439. the front. With a prefix argument, file is added/moved to the end.
  1440. @item C-c ]
  1441. Remove current file from the list of agenda files.
  1442. @item C-,
  1443. Cycle through agenda file list, visiting one file after the other.
  1444. @end table
  1445. @node Agenda dispatcher, Built-in agenda views, Agenda files, Agenda Views
  1446. @section The agenda dispatcher
  1447. The views are created through a dispatcher, which should be bound to a
  1448. global key---for example @kbd{C-c a} (@pxref{Installation}). After
  1449. pressing @kbd{C-c a}, an additional letter is required to execute a
  1450. command:
  1451. @table @kbd
  1452. @item a
  1453. The calendar-like agenda (@pxref{Weekly/daily agenda}).
  1454. @item t @r{/} T
  1455. A list of all TODO items (@pxref{Global TODO list}).
  1456. @item m @r{/} M
  1457. A list of headlines matching a TAGS expression (@pxref{Matching
  1458. tags and properties}).
  1459. @item L
  1460. The timeline view for the current buffer (@pxref{Timeline}).
  1461. @item s
  1462. A list of entries selected by a boolean expression of keywords
  1463. and/or regular expressions that must or must not occur in the entry.
  1464. @end table
  1465. @node Built-in agenda views, Agenda commands, Agenda dispatcher, Agenda Views
  1466. @section The built-in agenda views
  1467. @menu
  1468. * Weekly/daily agenda:: The calendar page with current tasks
  1469. * Global TODO list:: All unfinished action items
  1470. * Matching tags and properties:: Structured information with fine-tuned search
  1471. * Timeline:: Time-sorted view for single file
  1472. * Search view:: Find entries by searching for text
  1473. @end menu
  1474. @node Weekly/daily agenda, Global TODO list, Built-in agenda views, Built-in agenda views
  1475. @subsection The weekly/daily agenda
  1476. The purpose of the weekly/daily @emph{agenda} is to act like a page of a
  1477. paper agenda, showing all the tasks for the current week or day.
  1478. @table @kbd
  1479. @item C-c a a
  1480. Compile an agenda for the current week from a list of Org files. The agenda
  1481. shows the entries for each day.
  1482. @end table
  1483. Emacs contains the calendar and diary by Edward M. Reingold. Org-mode
  1484. understands the syntax of the diary and allows you to use diary sexp entries
  1485. directly in Org files:
  1486. @smallexample
  1487. * Birthdays and similar stuff
  1488. #+CATEGORY: Holiday
  1489. %%(org-calendar-holiday) ; special function for holiday names
  1490. #+CATEGORY: Ann
  1491. %%(diary-anniversary 5 14 1956)@footnote{Note that the order of the arguments (month, day, year) depends on the setting of @code{calendar-date-style}.} Arthur Dent is %d years old
  1492. %%(diary-anniversary 10 2 1869) Mahatma Gandhi would be %d years old
  1493. @end smallexample
  1494. Org can interact with Emacs appointments notification facility. To add all
  1495. the appointments of your agenda files, use the command
  1496. @code{org-agenda-to-appt}. See the docstring for details.
  1497. @node Global TODO list, Matching tags and properties, Weekly/daily agenda, Built-in agenda views
  1498. @subsection The global TODO list
  1499. The global TODO list contains all unfinished TODO items formatted and
  1500. collected into a single place. Remote editing of TODO items lets you
  1501. can change the state of a TODO entry with a single key press. The commands
  1502. available in the TODO list are described in @ref{Agenda commands}.
  1503. @table @kbd
  1504. @item C-c a t
  1505. Show the global TODO list. This collects the TODO items from all
  1506. agenda files (@pxref{Agenda Views}) into a single buffer.
  1507. @item C-c a T
  1508. Like the above, but allows selection of a specific TODO keyword.
  1509. @end table
  1510. @node Matching tags and properties, Timeline, Global TODO list, Built-in agenda views
  1511. @subsection Matching tags and properties
  1512. If headlines in the agenda files are marked with @emph{tags} (@pxref{Tags}),
  1513. or have properties (@pxref{Properties}), you can select headlines
  1514. based on this metadata and collect them into an agenda buffer. The match
  1515. syntax described here also applies when creating sparse trees with @kbd{C-c /
  1516. m}. The commands available in the tags list are described in @ref{Agenda
  1517. commands}.
  1518. @table @kbd
  1519. @item C-c a m
  1520. Produce a list of all headlines that match a given set of tags. The
  1521. command prompts for a selection criterion, which is a boolean logic
  1522. expression with tags, like @samp{+work+urgent-withboss} or
  1523. @samp{work|home} (@pxref{Tags}). If you often need a specific search,
  1524. define a custom command for it (@pxref{Agenda dispatcher}).
  1525. @item C-c a M
  1526. Like @kbd{C-c a m}, but only select headlines that are also TODO items.
  1527. @end table
  1528. @subsubheading Match syntax
  1529. A search string can use Boolean operators @samp{&} for AND and @samp{|} for
  1530. OR. @samp{&} binds more strongly than @samp{|}. Parentheses are currently
  1531. not implemented. Each element in the search is either a tag, a regular
  1532. expression matching tags, or an expression like @code{PROPERTY OPERATOR
  1533. VALUE} with a comparison operator, accessing a property value. Each element
  1534. may be preceded by @samp{-}, to select against it, and @samp{+} is syntactic
  1535. sugar for positive selection. The AND operator @samp{&} is optional when
  1536. @samp{+} or @samp{-} is present. Here are some examples, using only tags.
  1537. @table @samp
  1538. @item +work-boss
  1539. Select headlines tagged @samp{:work:}, but discard those also tagged
  1540. @samp{:boss:}.
  1541. @item work|laptop
  1542. Selects lines tagged @samp{:work:} or @samp{:laptop:}.
  1543. @item work|laptop+night
  1544. Like before, but require the @samp{:laptop:} lines to be tagged also
  1545. @samp{:night:}.
  1546. @end table
  1547. You may also test for properties at the same
  1548. time as matching tags, see the manual for more information.
  1549. @node Timeline, Search view, Matching tags and properties, Built-in agenda views
  1550. @subsection Timeline for a single file
  1551. The timeline summarizes all time-stamped items from a single Org mode
  1552. file in a @emph{time-sorted view}. The main purpose of this command is
  1553. to give an overview over events in a project.
  1554. @table @kbd
  1555. @item C-c a L
  1556. Show a time-sorted view of the Org file, with all time-stamped items.
  1557. When called with a @kbd{C-u} prefix, all unfinished TODO entries
  1558. (scheduled or not) are also listed under the current date.
  1559. @end table
  1560. @node Search view, , Timeline, Built-in agenda views
  1561. @subsection Search view
  1562. This agenda view is a general text search facility for Org mode entries.
  1563. It is particularly useful to find notes.
  1564. @table @kbd
  1565. @item C-c a s
  1566. This is a special search that lets you select entries by matching a substring
  1567. or specific words using a boolean logic.
  1568. @end table
  1569. For example, the search string @samp{computer equipment} will find entries
  1570. that contain @samp{computer equipment} as a substring.
  1571. Search view can also search for specific keywords in the entry, using Boolean
  1572. logic. The search string @samp{+computer +wifi -ethernet -@{8\.11[bg]@}}
  1573. will search for note entries that contain the keywords @code{computer}
  1574. and @code{wifi}, but not the keyword @code{ethernet}, and which are also
  1575. not matched by the regular expression @code{8\.11[bg]}, meaning to
  1576. exclude both 8.11b and 8.11g.
  1577. Note that in addition to the agenda files, this command will also search
  1578. the files listed in @code{org-agenda-text-search-extra-files}.
  1579. @node Agenda commands, Custom agenda views, Built-in agenda views, Agenda Views
  1580. @section Commands in the agenda buffer
  1581. Entries in the agenda buffer are linked back to the Org file or diary
  1582. file where they originate. Commands are provided to show and jump to the
  1583. original entry location, and to edit the Org files ``remotely'' from
  1584. the agenda buffer. This is just a selection of the many commands, explore
  1585. the @code{Agenda} menu and the manual for a complete list.
  1586. @table @kbd
  1587. @tsubheading{Motion}
  1588. @item n
  1589. Next line (same as @key{up} and @kbd{C-p}).
  1590. @item p
  1591. Previous line (same as @key{down} and @kbd{C-n}).
  1592. @tsubheading{View/Go to Org file}
  1593. @item mouse-3
  1594. @itemx @key{SPC}
  1595. Display the original location of the item in another window.
  1596. With prefix arg, make sure that the entire entry is made visible in the
  1597. outline, not only the heading.
  1598. @c
  1599. @itemx @key{TAB}
  1600. Go to the original location of the item in another window. Under Emacs
  1601. 22, @kbd{mouse-1} will also work for this.
  1602. @c
  1603. @itemx @key{RET}
  1604. Go to the original location of the item and delete other windows.
  1605. @c
  1606. @tsubheading{Change display}
  1607. @item o
  1608. Delete other windows.
  1609. @c
  1610. @item d @r{/} w
  1611. Switch to day/week view.
  1612. @c
  1613. @item f @r{and} b
  1614. Go forward/backward in time to display the following
  1615. @code{org-agenda-current-span} days. For example, if the display covers a
  1616. week, switch to the following/previous week.
  1617. @c
  1618. @item .
  1619. Go to today.
  1620. @c
  1621. @item j
  1622. Prompt for a date and go there.
  1623. @c
  1624. @item v l @ @r{or short} @ l
  1625. Toggle Logbook mode. In Logbook mode, entries that were marked DONE while
  1626. logging was on (variable @code{org-log-done}) are shown in the agenda, as are
  1627. entries that have been clocked on that day. When called with a @kbd{C-u}
  1628. prefix, show all possible logbook entries, including state changes.
  1629. @c
  1630. @item r @r{or} g
  1631. Recreate the agenda buffer, to reflect the changes.
  1632. @item s
  1633. Save all Org buffers in the current Emacs session, and also the locations of
  1634. IDs.
  1635. @tsubheading{Secondary filtering and query editing}
  1636. @item /
  1637. Filter the current agenda view with respect to a tag. You are prompted for a
  1638. letter to select a tag. Press @samp{-} first to select against the tag.
  1639. @item \
  1640. Narrow the current agenda filter by an additional condition.
  1641. @tsubheading{Remote editing (see the manual for many more commands)}
  1642. @item 0--9
  1643. Digit argument.
  1644. @c
  1645. @item t
  1646. Change the TODO state of the item, in the agenda and in the
  1647. org file.
  1648. @c
  1649. @item C-k
  1650. Delete the current agenda item along with the entire subtree belonging
  1651. to it in the original Org file.
  1652. @c
  1653. @item C-c C-w
  1654. Refile the entry at point.
  1655. @c
  1656. @item C-c C-x C-a @ @r{or short} @ a
  1657. Archive the subtree corresponding to the entry at point using the default
  1658. archiving command set in @code{org-archive-default-command}.
  1659. @c
  1660. @item C-c C-x C-s @ @r{or short} @ $
  1661. Archive the subtree corresponding to the current headline.
  1662. @c
  1663. @item C-c C-s
  1664. Schedule this item, with prefix arg remove the scheduling timestamp
  1665. @c
  1666. @item C-c C-d
  1667. Set a deadline for this item, with prefix arg remove the deadline.
  1668. @c
  1669. @item S-@key{right} @r{and} S-@key{left}
  1670. Change the timestamp associated with the current line by one day.
  1671. @c
  1672. @item I
  1673. Start the clock on the current item.
  1674. @c
  1675. @item O / X
  1676. Stop/cancel the previously started clock.
  1677. @item J
  1678. Jump to the running clock in another window.
  1679. @end table
  1680. @node Custom agenda views, , Agenda commands, Agenda Views
  1681. @section Custom agenda views
  1682. The main application of custom searches is the definition of keyboard
  1683. shortcuts for frequently used searches, either creating an agenda
  1684. buffer, or a sparse tree (the latter covering of course only the current
  1685. buffer).
  1686. Custom commands are configured in the variable
  1687. @code{org-agenda-custom-commands}. You can customize this variable, for
  1688. example by pressing @kbd{C-c a C}. You can also directly set it with
  1689. Emacs Lisp in @file{.emacs}. The following example contains all valid
  1690. search types:
  1691. @smalllisp
  1692. @group
  1693. (setq org-agenda-custom-commands
  1694. '(("w" todo "WAITING")
  1695. ("u" tags "+boss-urgent")
  1696. ("v" tags-todo "+boss-urgent")))
  1697. @end group
  1698. @end smalllisp
  1699. @noindent
  1700. The initial string in each entry defines the keys you have to press after the
  1701. dispatcher command @kbd{C-c a} in order to access the command. Usually this
  1702. will be just a single character. The second parameter is the search type,
  1703. followed by the string or regular expression to be used for the matching.
  1704. The example above will therefore define:
  1705. @table @kbd
  1706. @item C-c a w
  1707. as a global search for TODO entries with @samp{WAITING} as the TODO
  1708. keyword
  1709. @item C-c a u
  1710. as a global tags search for headlines marked @samp{:boss:} but not
  1711. @samp{:urgent:}
  1712. @item C-c a v
  1713. as the same search as @kbd{C-c a u}, but limiting the search to
  1714. headlines that are also TODO items
  1715. @end table
  1716. @seealso{
  1717. @uref{, Chapter 10 of
  1718. the manual}@*
  1719. @uref{,
  1720. Mat Lundin's tutorial about custom agenda commands}@*
  1721. @uref{,
  1722. John Wiegley's setup}}
  1723. @node Markup, Exporting, Agenda Views, Top
  1724. @chapter Markup for rich export
  1725. When exporting Org-mode documents, the exporter tries to reflect the
  1726. structure of the document as accurately as possible in the backend. Since
  1727. export targets like HTML, @LaTeX{}, or DocBook allow much richer formatting,
  1728. Org mode has rules on how to prepare text for rich export. This section
  1729. summarizes the markup rules used in an Org-mode buffer.
  1730. @menu
  1731. * Structural markup elements:: The basic structure as seen by the exporter
  1732. * Images and tables:: Images, tables and caption mechanism
  1733. * Literal examples:: Source code examples with special formatting
  1734. * Include files:: Include additional files into a document
  1735. * Embedded @LaTeX{}:: @LaTeX{} can be freely used inside Org documents
  1736. @end menu
  1737. @node Structural markup elements, Images and tables, Markup, Markup
  1738. @section Structural markup elements
  1739. @menu
  1740. * Document title:: Where the title is taken from
  1741. * Headings and sections:: The document structure as seen by the exporter
  1742. * Table of contents:: The if and where of the table of contents
  1743. * Paragraphs:: Paragraphs
  1744. * Emphasis and monospace:: Bold, italic, etc.
  1745. * Comment lines:: What will *not* be exported
  1746. @end menu
  1747. @node Document title, Headings and sections, Structural markup elements, Structural markup elements
  1748. @subheading Document title
  1749. @noindent
  1750. The title of the exported document is taken from the special line
  1751. @smallexample
  1752. #+TITLE: This is the title of the document
  1753. @end smallexample
  1754. @node Headings and sections, Table of contents, Document title, Structural markup elements
  1755. @subheading Headings and sections
  1756. The outline structure of the document as described in @ref{Document
  1757. Structure}, forms the basis for defining sections of the exported document.
  1758. However, since the outline structure is also used for (for example) lists of
  1759. tasks, only the first three outline levels will be used as headings. Deeper
  1760. levels will become itemized lists. You can change the location of this
  1761. switch globally by setting the variable @code{org-export-headline-levels}, or on a
  1762. per-file basis with a line
  1763. @smallexample
  1764. #+OPTIONS: H:4
  1765. @end smallexample
  1766. @node Table of contents, Paragraphs, Headings and sections, Structural markup elements
  1767. @subheading Table of contents
  1768. The table of contents is normally inserted directly before the first headline
  1769. of the file.
  1770. @smallexample
  1771. #+OPTIONS: toc:2 (only to two levels in TOC)
  1772. #+OPTIONS: toc:nil (no TOC at all)
  1773. @end smallexample
  1774. @node Paragraphs, Emphasis and monospace, Table of contents, Structural markup elements
  1775. @subheading Paragraphs, line breaks, and quoting
  1776. Paragraphs are separated by at least one empty line. If you need to enforce
  1777. a line break within a paragraph, use @samp{\\} at the end of a line.
  1778. To keep the line breaks in a region, but otherwise use normal formatting, you
  1779. can use this construct, which can also be used to format poetry.
  1780. @smallexample
  1781. #+BEGIN_VERSE
  1782. Great clouds overhead
  1783. Tiny black birds rise and fall
  1784. Snow covers Emacs
  1785. -- AlexSchroeder
  1786. #+END_VERSE
  1787. @end smallexample
  1788. When quoting a passage from another document, it is customary to format this
  1789. as a paragraph that is indented on both the left and the right margin. You
  1790. can include quotations in Org-mode documents like this:
  1791. @smallexample
  1792. #+BEGIN_QUOTE
  1793. Everything should be made as simple as possible,
  1794. but not any simpler -- Albert Einstein
  1795. #+END_QUOTE
  1796. @end smallexample
  1797. If you would like to center some text, do it like this:
  1798. @smallexample
  1799. #+BEGIN_CENTER
  1800. Everything should be made as simple as possible, \\
  1801. but not any simpler
  1802. #+END_CENTER
  1803. @end smallexample
  1804. @node Emphasis and monospace, Comment lines, Paragraphs, Structural markup elements
  1805. @subheading Emphasis and monospace
  1806. You can make words @b{*bold*}, @i{/italic/}, _underlined_, @code{=code=}
  1807. and @code{~verbatim~}, and, if you must, @samp{+strike-through+}. Text
  1808. in the code and verbatim string is not processed for Org-mode specific
  1809. syntax, it is exported verbatim. To insert a horizontal rules, use a line
  1810. consisting of only dashes, and at least 5 of them.
  1811. @node Comment lines, , Emphasis and monospace, Structural markup elements
  1812. @subheading Comment lines
  1813. Lines starting with zero or more whitespace characters followed by @samp{#}
  1814. and a whitespace are treated as comments and, as such, are not exported.
  1815. Likewise, regions surrounded by @samp{#+BEGIN_COMMENT}
  1816. ... @samp{#+END_COMMENT} are not exported.
  1817. Finally, a @samp{COMMENT} keyword at the beginning of an entry, but after any
  1818. other keyword or priority cookie, comments out the entire subtree. The
  1819. command below helps changing the comment status of a headline.
  1820. @table @kbd
  1821. @item C-c ;
  1822. Toggle the COMMENT keyword at the beginning of an entry.
  1823. @end table
  1824. @node Images and tables, Literal examples, Structural markup elements, Markup
  1825. @section Images and Tables
  1826. For Org mode tables, the lines before the first horizontal separator line
  1827. will become table header lines. You can use the following lines somewhere
  1828. before the table to assign a caption and a label for cross references, and in
  1829. the text you can refer to the object with @code{[[tab:basic-data]]}:
  1830. @smallexample
  1831. #+CAPTION: This is the caption for the next table (or link)
  1832. #+NAME: tbl:basic-data
  1833. | ... | ...|
  1834. |-----|----|
  1835. @end smallexample
  1836. Some backends allow you to directly include images into the exported
  1837. document. Org does this, if a link to an image files does not have
  1838. a description part, for example @code{[[./img/a.jpg]]}. If you wish to
  1839. define a caption for the image and maybe a label for internal cross
  1840. references, you sure that the link is on a line by itself precede it with:
  1841. @smallexample
  1842. #+CAPTION: This is the caption for the next figure link (or table)
  1843. #+NAME: fig:SED-HR4049
  1844. [[./img/a.jpg]]
  1845. @end smallexample
  1846. The same caption mechanism applies to other structures than images and tables
  1847. (e.g., @LaTeX{} equations, source code blocks), provided the chosen export
  1848. back-end supports them.
  1849. @node Literal examples, Include files, Images and tables, Markup
  1850. @section Literal examples
  1851. You can include literal examples that should not be subjected to
  1852. markup. Such examples will be typeset in monospace, so this is well suited
  1853. for source code and similar examples.
  1854. @smallexample
  1856. Some example from a text file.
  1857. #+END_EXAMPLE
  1858. @end smallexample
  1859. For simplicity when using small examples, you can also start the example
  1860. lines with a colon followed by a space. There may also be additional
  1861. whitespace before the colon:
  1862. @smallexample
  1863. Here is an example
  1864. : Some example from a text file.
  1865. @end smallexample
  1866. For source code from a programming language, or any other text
  1867. that can be marked up by font-lock in Emacs, you can ask for it to
  1868. look like the fontified Emacs buffer
  1869. @smallexample
  1870. #+BEGIN_SRC emacs-lisp
  1871. (defun org-xor (a b)
  1872. "Exclusive or."
  1873. (if a (not b) b))
  1874. #+END_SRC
  1875. @end smallexample
  1876. To edit the example in a special buffer supporting this language, use
  1877. @kbd{C-c '} to both enter and leave the editing buffer.
  1878. @node Include files, Embedded @LaTeX{}, Literal examples, Markup
  1879. @section Include files
  1880. During export, you can include the content of another file. For example, to
  1881. include your @file{.emacs} file, you could use:
  1882. @smallexample
  1883. #+INCLUDE: "~/.emacs" src emacs-lisp
  1884. @end smallexample
  1885. @noindent
  1886. The optional second and third parameter are the markup (i.e., @samp{example}
  1887. or @samp{src}), and, if the markup is @samp{src}, the language for formatting
  1888. the contents. The markup is optional, if it is not given, the text will be
  1889. assumed to be in Org mode format and will be processed normally. File-links
  1890. will be interpreted as well:
  1891. @smallexample
  1892. #+INCLUDE: "./" :only-contents t
  1893. @end smallexample
  1894. @noindent
  1895. @kbd{C-c '} will visit the included file.
  1896. @node Embedded @LaTeX{}, , Include files, Markup
  1897. @section Embedded @LaTeX{}
  1898. For scientific notes which need to be able to contain mathematical symbols
  1899. and the occasional formula, Org-mode supports embedding @LaTeX{} code into
  1900. its files. You can directly use TeX-like syntax for special symbols, enter
  1901. formulas and entire @LaTeX{} environments.
  1902. @smallexample
  1903. Angles are written as Greek letters \alpha, \beta and \gamma. The mass if
  1904. the sun is M_sun = 1.989 x 10^30 kg. The radius of the sun is R_@{sun@} =
  1905. 6.96 x 10^8 m. If $a^2=b$ and $b=2$, then the solution must be either
  1906. $a=+\sqrt@{2@}$ or $a=-\sqrt@{2@}$.
  1907. \begin@{equation@}
  1908. x=\sqrt@{b@}
  1909. \end@{equation@}
  1910. @end smallexample
  1911. @noindent
  1912. With
  1913. @uref{,special
  1914. setup}, @LaTeX{} snippets will be included as images when exporting to HTML.
  1915. @seealso{
  1916. @uref{, Chapter 11 of the manual}}
  1917. @node Exporting, Publishing, Markup, Top
  1918. @chapter Exporting
  1919. Org-mode documents can be exported into a variety of other formats: ASCII
  1920. export for inclusion into emails, HTML to publish on the web, @LaTeX{}/PDF
  1921. for beautiful printed documents and DocBook to enter the world of many other
  1922. formats using DocBook tools. There is also export to iCalendar format so
  1923. that planning information can be incorporated into desktop calendars.
  1924. @menu
  1925. * Export options:: Per-file export settings
  1926. * The export dispatcher:: How to access exporter commands
  1927. * ASCII/Latin-1/UTF-8 export:: Exporting to flat files with encoding
  1928. * HTML export:: Exporting to HTML
  1929. * @LaTeX{} and PDF export:: Exporting to @LaTeX{}, and processing to PDF
  1930. * iCalendar export:: Exporting to iCalendar
  1931. @end menu
  1932. @node Export options, The export dispatcher, Exporting, Exporting
  1933. @section Export options
  1934. The exporter recognizes special lines in the buffer which provide additional
  1935. information. These lines may be put anywhere in the file. The whole set of
  1936. lines can be inserted into the buffer with @kbd{C-c C-e #}.
  1937. @table @kbd
  1938. @item C-c C-e #
  1939. Insert template with export options, see example below.
  1940. @end table
  1941. @smallexample
  1942. #+TITLE: the title to be shown
  1943. #+AUTHOR: the author (default taken from @code{user-full-name})
  1944. #+DATE: a date, fixed, or an Org timestamp
  1945. #+EMAIL: his/her email address (default from @code{user-mail-address})
  1946. #+LANGUAGE: language, e.g.@: @samp{en} (@code{org-export-default-language})
  1947. #+OPTIONS: H:2 num:t toc:t \n:nil ::t |:t ^:t f:t tex:t ...
  1948. @end smallexample
  1949. @node The export dispatcher, ASCII/Latin-1/UTF-8 export, Export options, Exporting
  1950. @section The export dispatcher
  1951. All export commands can be reached using the export dispatcher, which is
  1952. a prefix key that prompts for an additional key specifying the command.
  1953. Normally the entire file is exported, but if a region is active, it will be
  1954. exported instead.
  1955. @table @kbd
  1956. @item C-c C-e
  1957. Dispatcher for export and publishing commands.
  1958. @end table
  1959. @node ASCII/Latin-1/UTF-8 export, HTML export, The export dispatcher, Exporting
  1960. @section ASCII/Latin-1/UTF-8 export
  1961. ASCII export produces a simple and very readable version of an Org-mode
  1962. file, containing only plain ASCII. Latin-1 and UTF-8 export augment the file
  1963. with special characters and symbols available in these encodings.
  1964. @table @kbd
  1965. @item C-c C-e t a @ @ @r{and} @ @ C-c C-e t A
  1966. Export as ASCII file or temporary buffer.
  1967. @item C-c C-e t n @ @ @r{and} @ @ C-c C-e t N
  1968. Like the above commands, but use Latin-1 encoding.
  1969. @item C-c C-e t u @ @ @r{and} @ @ C-c C-e t U
  1970. Like the above commands, but use UTF-8 encoding.
  1971. @end table
  1972. @node HTML export, @LaTeX{} and PDF export, ASCII/Latin-1/UTF-8 export, Exporting
  1973. @section HTML export
  1974. @table @kbd
  1975. @item C-c C-e h h
  1976. Export as HTML file @file{myfile.html}.
  1977. @item C-c C-e h o
  1978. Export as HTML file and immediately open it with a browser.
  1979. @end table
  1980. To insert HTML that should be copied verbatim to
  1981. the exported file use either
  1982. @smallexample
  1983. #+HTML: Literal HTML code for export
  1984. @end smallexample
  1985. @noindent
  1986. or
  1987. @smallexample
  1988. #+BEGIN_HTML
  1989. All lines between these markers are exported literally
  1990. #+END_HTML
  1991. @end smallexample
  1992. @node @LaTeX{} and PDF export, iCalendar export, HTML export, Exporting
  1993. @section @LaTeX{} and PDF export
  1994. @table @kbd
  1995. @item C-c C-e l l
  1996. Export as @LaTeX{} file @file{myfile.tex}.
  1997. @item C-c C-e l p
  1998. Export as @LaTeX{} and then process to PDF.
  1999. @item C-c C-e l o
  2000. Export as @LaTeX{} and then process to PDF, then open the resulting PDF file.
  2001. @end table
  2002. By default, the @LaTeX{} output uses the class @code{article}. You can
  2003. change this by adding an option like @code{#+LATEX_CLASS: myclass} in your
  2004. file. The class must be listed in @code{org-latex-classes}.
  2005. Embedded @LaTeX{} as described in @ref{Embedded @LaTeX{}}, will be correctly
  2006. inserted into the @LaTeX{} file. Similarly to the HTML exporter, you can use
  2007. @code{#+LATEX:} and @code{#+BEGIN_LATEX ... #+END_LATEX} construct to add
  2008. verbatim @LaTeX{} code.
  2009. @node iCalendar export, , @LaTeX{} and PDF export, Exporting
  2010. @section iCalendar export
  2011. @table @kbd
  2012. @item C-c C-e c f
  2013. Create iCalendar entries for the current file in a @file{.ics} file.
  2014. @item C-c C-e c c
  2015. Create a single large iCalendar file from all files in
  2016. @code{org-agenda-files} and write it to the file given by
  2017. @code{org-icalendar-combined-agenda-file}.
  2018. @end table
  2019. @seealso{
  2020. @uref{, Chapter 12 of the manual}@*
  2021. @uref{,
  2022. Sebastian Rose's image handling tutorial}@*
  2023. @uref{, Thomas
  2024. Dye's LaTeX export tutorial}
  2025. @uref{, Eric
  2026. Fraga's BEAMER presentation tutorial}}
  2027. @node Publishing, Working With Source Code, Exporting, Top
  2028. @chapter Publishing
  2029. Org includes a publishing management system that allows you to configure
  2030. automatic HTML conversion of @emph{projects} composed of interlinked org
  2031. files. You can also configure Org to automatically upload your exported HTML
  2032. pages and related attachments, such as images and source code files, to a web
  2033. server. For detailed instructions about setup, see the manual.
  2034. Here is an example:
  2035. @smalllisp
  2036. (setq org-publish-project-alist
  2037. '(("org"
  2038. :base-directory "~/org/"
  2039. :publishing-directory "~/public_html"
  2040. :section-numbers nil
  2041. :table-of-contents nil
  2042. :style "<link rel=\"stylesheet\"
  2043. href=\"../other/mystyle.css\"
  2044. type=\"text/css\"/>")))
  2045. @end smalllisp
  2046. @table @kbd
  2047. @item C-c C-e P x
  2048. Prompt for a specific project and publish all files that belong to it.
  2049. @item C-c C-e P p
  2050. Publish the project containing the current file.
  2051. @item C-c C-e P f
  2052. Publish only the current file.
  2053. @item C-c C-e P a
  2054. Publish every project.
  2055. @end table
  2056. Org uses timestamps to track when a file has changed. The above functions
  2057. normally only publish changed files. You can override this and force
  2058. publishing of all files by giving a prefix argument to any of the commands
  2059. above.
  2060. @seealso{
  2061. @uref{, Chapter 13 of the
  2062. manual}@*
  2063. @uref{,
  2064. Sebastian Rose's publishing tutorial}@*
  2065. @uref{, Ian Barton's
  2066. Jekyll/blogging setup}}
  2067. @node Working With Source Code, Miscellaneous, Publishing, Top
  2068. @chapter Working with source code
  2069. Org-mode provides a number of features for working with source code,
  2070. including editing of code blocks in their native major-mode, evaluation of
  2071. code blocks, tangling of code blocks, and exporting code blocks and their
  2072. results in several formats.
  2073. @subheading Structure of Code Blocks
  2074. The structure of code blocks is as follows:
  2075. @example
  2076. #+NAME: <name>
  2077. #+BEGIN_SRC <language> <switches> <header arguments>
  2078. <body>
  2079. #+END_SRC
  2080. @end example
  2081. Where @code{<name>} is a string used to name the code block,
  2082. @code{<language>} specifies the language of the code block
  2083. (e.g.@: @code{emacs-lisp}, @code{shell}, @code{R}, @code{python}, etc...),
  2084. @code{<switches>} can be used to control export of the code block,
  2085. @code{<header arguments>} can be used to control many aspects of code block
  2086. behavior as demonstrated below, and @code{<body>} contains the actual source
  2087. code.
  2088. @subheading Editing source code
  2089. Use @kbd{C-c '} to edit the current code block. This brings up a language
  2090. major-mode edit buffer containing the body of the code block. Saving this
  2091. buffer will write the new contents back to the Org buffer. Use @kbd{C-c '}
  2092. again to exit the edit buffer.
  2093. @subheading Evaluating code blocks
  2094. Use @kbd{C-c C-c} to evaluate the current code block and insert its results
  2095. in the Org-mode buffer. By default, evaluation is only turned on for
  2096. @code{emacs-lisp} code blocks, however support exists for evaluating blocks
  2097. in many languages. For a complete list of supported languages see the
  2098. manual. The following shows a code block and its results.
  2099. @example
  2100. #+BEGIN_SRC emacs-lisp
  2101. (+ 1 2 3 4)
  2102. #+END_SRC
  2103. #+RESULTS:
  2104. : 10
  2105. @end example
  2106. @subheading Extracting source code
  2107. Use @kbd{C-c C-v t} to create pure source code files by extracting code from
  2108. source blocks in the current buffer. This is referred to as ``tangling''---a
  2109. term adopted from the literate programming community. During ``tangling'' of
  2110. code blocks their bodies are expanded using @code{org-babel-expand-src-block}
  2111. which can expand both variable and ``noweb'' style references. In order to
  2112. tangle a code block it must have a @code{:tangle} header argument, see the
  2113. manual for details.
  2114. @subheading Library of Babel
  2115. Use @kbd{C-c C-v l} to load the code blocks from an Org-mode files into the
  2116. ``Library of Babel'', these blocks can then be evaluated from any Org-mode
  2117. buffer. A collection of generally useful code blocks is distributed with
  2118. Org-mode in @code{contrib/}.
  2119. @subheading Header Arguments
  2120. Many aspects of the evaluation and export of code blocks are controlled
  2121. through header arguments. These can be specified globally, at the file
  2122. level, at the outline subtree level, and at the individual code block level.
  2123. The following describes some of the header arguments.
  2124. @table @code
  2125. @item :var
  2126. The @code{:var} header argument is used to pass arguments to code blocks.
  2127. The values passed to arguments can be literal values, values from org-mode
  2128. tables and literal example blocks, or the results of other named code blocks.
  2129. @item :results
  2130. The @code{:results} header argument controls the @emph{collection},
  2131. @emph{type}, and @emph{handling} of code block results. Values of
  2132. @code{output} or @code{value} (the default) specify how results are collected
  2133. from a code block's evaluation. Values of @code{vector}, @code{scalar}
  2134. @code{file} @code{raw} @code{html} @code{latex} and @code{code} specify the
  2135. type of the results of the code block which dictates how they will be
  2136. incorporated into the Org-mode buffer. Values of @code{silent},
  2137. @code{replace}, @code{prepend}, and @code{append} specify handling of code
  2138. block results, specifically if and how the results should be inserted into
  2139. the Org-mode buffer.
  2140. @item :session
  2141. A header argument of @code{:session} will cause the code block to be
  2142. evaluated in a persistent interactive inferior process in Emacs. This allows
  2143. for persisting state between code block evaluations, and for manual
  2144. inspection of the results of evaluation.
  2145. @item :exports
  2146. Any combination of the @emph{code} or the @emph{results} of a block can be
  2147. retained on export, this is specified by setting the @code{:results} header
  2148. argument to @code{code} @code{results} @code{none} or @code{both}.
  2149. @item :tangle
  2150. A header argument of @code{:tangle yes} will cause a code block's contents to
  2151. be tangled to a file named after the filename of the Org-mode buffer. An
  2152. alternate file name can be specified with @code{:tangle filename}.
  2153. @item :cache
  2154. A header argument of @code{:cache yes} will cause associate a hash of the
  2155. expanded code block with the results, ensuring that code blocks are only
  2156. re-run when their inputs have changed.
  2157. @item :noweb
  2158. A header argument of @code{:noweb yes} will expand ``noweb'' style references
  2159. on evaluation and tangling.
  2160. @item :file
  2161. Code blocks which output results to files (e.g.@: graphs, diagrams and figures)
  2162. can accept a @code{:file filename} header argument in which case the results
  2163. are saved to the named file, and a link to the file is inserted into the
  2164. Org-mode buffer.
  2165. @end table
  2166. @seealso{
  2167. @uref{,
  2168. Chapter 11.3 of the manual}@*
  2169. @uref{,
  2170. The Babel site on Worg}}
  2171. @node Miscellaneous, GNU Free Documentation License, Working With Source Code, Top
  2172. @chapter Miscellaneous
  2173. @menu
  2174. * Completion:: M-TAB knows what you need
  2175. * Clean view:: Getting rid of leading stars in the outline
  2176. * MobileOrg:: Org-mode on the iPhone
  2177. @end menu
  2178. @node Completion, Clean view, Miscellaneous, Miscellaneous
  2179. @section Completion
  2180. Org supports in-buffer completion with @kbd{M-@key{TAB}}. This type of
  2181. completion does not make use of the minibuffer. You simply type a few
  2182. letters into the buffer and use the key to complete text right there. For
  2183. example, this command will complete @TeX{} symbols after @samp{\}, TODO
  2184. keywords at the beginning of a headline, and tags after @samp{:} in a
  2185. headline.
  2186. @node Clean view, MobileOrg, Completion, Miscellaneous
  2187. @section A cleaner outline view
  2188. Some people find it noisy and distracting that the Org headlines start with a
  2189. potentially large number of stars, and that text below the headlines is not
  2190. indented. While this is no problem when writing a @emph{book-like} document
  2191. where the outline headings are really section headings, in a more
  2192. @emph{list-oriented} outline, indented structure is a lot cleaner:
  2193. @smallexample
  2194. @group
  2195. * Top level headline | * Top level headline
  2196. ** Second level | * Second level
  2197. *** 3rd level | * 3rd level
  2198. some text | some text
  2199. *** 3rd level | * 3rd level
  2200. more text | more text
  2201. * Another top level headline | * Another top level headline
  2202. @end group
  2203. @end smallexample
  2204. @noindent
  2205. If you are using at least Emacs and version 6.29 of Org, this kind
  2206. of view can be achieved dynamically at display time using
  2207. @code{org-indent-mode}, which will prepend intangible space to each line.
  2208. You can turn on @code{org-indent-mode} for all files by customizing the
  2209. variable @code{org-startup-indented}, or you can turn it on for individual
  2210. files using
  2211. @smallexample
  2212. #+STARTUP: indent
  2213. @end smallexample
  2214. If you want a similar effect in earlier version of Emacs and/or Org, or if
  2215. you want the indentation to be hard space characters so that the plain text
  2216. file looks as similar as possible to the Emacs display, Org supports you by
  2217. helping to indent (with @key{TAB}) text below each headline, by hiding
  2218. leading stars, and by only using levels 1, 3, etc to get two characters
  2219. indentation for each level. To get this support in a file, use
  2220. @smallexample
  2221. #+STARTUP: hidestars odd
  2222. @end smallexample
  2223. @node MobileOrg, , Clean view, Miscellaneous
  2224. @section MobileOrg
  2225. @i{MobileOrg} is the name of the mobile companion app for Org mode, currently
  2226. available for iOS and for Android. @i{MobileOrg} offers offline viewing and
  2227. capture support for an Org mode system rooted on a ``real'' computer. It
  2228. does also allow you to record changes to existing entries.
  2229. The @uref{, iOS implementation} for the
  2230. @i{iPhone/iPod Touch/iPad} series of devices, was developed by Richard
  2231. Moreland. Android users should check out
  2232. @uref{, MobileOrg Android}
  2233. by Matt Jones. The two implementations are not identical but offer similar
  2234. features.
  2235. @seealso{
  2236. @uref{, Chapter 15
  2237. of the manual}@*
  2238. @uref{, Appendix B of the
  2239. manual}@*
  2240. @uref{,Key reference card}}
  2241. @node GNU Free Documentation License, , Miscellaneous, Top
  2242. @appendix GNU Free Documentation License
  2243. @include doclicense.texi
  2244. @bye
  2245. @c Local variables:
  2246. @c fill-column: 77
  2247. @c End:
  2248. @c LocalWords: webdavhost pre