Commit | Line | Data |
---|---|---|
4009494e GM |
1 | \input texinfo |
2 | @c %**start of header | |
db78a8cb | 3 | @setfilename ../../info/org |
a7808fba | 4 | @settitle The Org Manual |
4009494e | 5 | |
55033558 CD |
6 | @set VERSION 6.21b |
7 | @set DATE February 2009 | |
4009494e | 8 | |
4009494e | 9 | @c Version and Contact Info |
dbc28aaa | 10 | @set MAINTAINERSITE @uref{http://orgmode.org,maintainers webpage} |
4009494e GM |
11 | @set AUTHOR Carsten Dominik |
12 | @set MAINTAINER Carsten Dominik | |
dbc28aaa CD |
13 | @set MAINTAINEREMAIL @email{carsten at orgmode dot org} |
14 | @set MAINTAINERCONTACT @uref{mailto:carsten at orgmode dot org,contact the maintainer} | |
4009494e GM |
15 | @c %**end of header |
16 | @finalout | |
17 | ||
18 | @c Macro definitions | |
19 | ||
20 | @c Subheadings inside a table. | |
21 | @macro tsubheading{text} | |
22 | @ifinfo | |
23 | @subsubheading \text\ | |
24 | @end ifinfo | |
25 | @ifnotinfo | |
26 | @item @b{\text\} | |
27 | @end ifnotinfo | |
28 | @end macro | |
29 | ||
30 | @copying | |
a7808fba | 31 | This manual is for Org (version @value{VERSION}). |
4009494e | 32 | |
6ed161e1 | 33 | Copyright @copyright{} 2004, 2005, 2006, 2007, 2008, 2009 Free Software Foundation |
4009494e GM |
34 | |
35 | @quotation | |
36 | Permission is granted to copy, distribute and/or modify this document | |
d60b1ba1 | 37 | under the terms of the GNU Free Documentation License, Version 1.3 or |
4009494e GM |
38 | any later version published by the Free Software Foundation; with no |
39 | Invariant Sections, with the Front-Cover texts being ``A GNU Manual,'' | |
47271179 GM |
40 | and with the Back-Cover Texts as in (a) below. A copy of the license |
41 | is included in the section entitled ``GNU Free Documentation License.'' | |
4009494e | 42 | |
6f093307 GM |
43 | (a) The FSF's Back-Cover Text is: ``You have the freedom to copy and |
44 | modify this GNU manual. Buying copies from the FSF supports it in | |
45 | developing GNU and promoting software freedom.'' | |
5b14aca9 GM |
46 | |
47 | This document is part of a collection distributed under the GNU Free | |
48 | Documentation License. If you want to distribute this document | |
49 | separately from the collection, you can do so by adding a copy of the | |
50 | license to the document, as described in section 6 of the license. | |
4009494e GM |
51 | @end quotation |
52 | @end copying | |
53 | ||
5dc584b5 KB |
54 | @dircategory Emacs |
55 | @direntry | |
56 | * Org Mode: (org). Outline-based notes management and organizer | |
57 | @end direntry | |
58 | ||
4009494e | 59 | @titlepage |
a7808fba | 60 | @title The Org Manual |
4009494e GM |
61 | |
62 | @subtitle Release @value{VERSION} | |
63 | @author by Carsten Dominik | |
64 | ||
65 | @c The following two commands start the copyright page. | |
66 | @page | |
67 | @vskip 0pt plus 1filll | |
68 | @insertcopying | |
69 | @end titlepage | |
70 | ||
71 | @c Output the table of contents at the beginning. | |
72 | @contents | |
73 | ||
74 | @ifnottex | |
75 | @node Top, Introduction, (dir), (dir) | |
76 | @top Org Mode Manual | |
77 | ||
78 | @insertcopying | |
79 | @end ifnottex | |
80 | ||
81 | @menu | |
82 | * Introduction:: Getting started | |
a7808fba | 83 | * Document Structure:: A tree works like your brain |
4009494e GM |
84 | * Tables:: Pure magic for quick formatting |
85 | * Hyperlinks:: Notes in context | |
a7808fba | 86 | * TODO Items:: Every tree branch can be a TODO item |
4009494e | 87 | * Tags:: Tagging headlines and matching sets of tags |
a7808fba CD |
88 | * Properties and Columns:: Storing information about an entry |
89 | * Dates and Times:: Making items useful for planning | |
864c9740 | 90 | * Capture:: Creating tasks and attaching files |
a7808fba | 91 | * Agenda Views:: Collecting information into views |
4009494e GM |
92 | * Embedded LaTeX:: LaTeX fragments and formulas |
93 | * Exporting:: Sharing and publishing of notes | |
a7808fba | 94 | * Publishing:: Create a web site of linked Org files |
4009494e | 95 | * Miscellaneous:: All the rest which did not fit elsewhere |
44ce9197 | 96 | * Extensions:: Add-ons for Org mode |
a50253cc | 97 | * Hacking:: How to hack your way around |
a7808fba CD |
98 | * History and Acknowledgments:: How Org came into being |
99 | * Main Index:: An index of Org's concepts and features | |
4009494e GM |
100 | * Key Index:: Key bindings and where they are described |
101 | ||
102 | @detailmenu | |
103 | --- The Detailed Node Listing --- | |
104 | ||
105 | Introduction | |
106 | ||
a7808fba CD |
107 | * Summary:: Brief summary of what Org does |
108 | * Installation:: How to install a downloaded version of Org | |
109 | * Activation:: How to activate Org for certain buffers | |
4009494e | 110 | * Feedback:: Bug reports, ideas, patches etc. |
dbc28aaa | 111 | * Conventions:: Type-setting conventions in the manual |
4009494e GM |
112 | |
113 | Document Structure | |
114 | ||
a7808fba CD |
115 | * Outlines:: Org is based on Outline mode |
116 | * Headlines:: How to typeset Org tree headlines | |
4009494e GM |
117 | * Visibility cycling:: Show and hide, much simplified |
118 | * Motion:: Jumping to other headlines | |
119 | * Structure editing:: Changing sequence and level of headlines | |
120 | * Archiving:: Move done task trees to a different place | |
121 | * Sparse trees:: Matches embedded in context | |
122 | * Plain lists:: Additional structure within an entry | |
123 | * Drawers:: Tucking stuff away | |
55e0839d | 124 | * Footnotes:: How footnotes are defined in Org's syntax |
a7808fba | 125 | * Orgstruct mode:: Structure editing outside Org |
4009494e GM |
126 | |
127 | Archiving | |
128 | ||
129 | * ARCHIVE tag:: Marking a tree as inactive | |
130 | * Moving subtrees:: Moving a tree to an archive file | |
131 | ||
132 | Tables | |
133 | ||
134 | * Built-in table editor:: Simple tables | |
28a16a1b | 135 | * Narrow columns:: Stop wasting space in tables |
4009494e | 136 | * Column groups:: Grouping to trigger vertical lines |
a7808fba CD |
137 | * Orgtbl mode:: The table editor as minor mode |
138 | * The spreadsheet:: The table editor has spreadsheet capabilities | |
864c9740 | 139 | * Org Plot:: Plotting from org tables |
4009494e GM |
140 | |
141 | The spreadsheet | |
142 | ||
143 | * References:: How to refer to another field or range | |
144 | * Formula syntax for Calc:: Using Calc to compute stuff | |
145 | * Formula syntax for Lisp:: Writing formulas in Emacs Lisp | |
146 | * Field formulas:: Formulas valid for a single field | |
147 | * Column formulas:: Formulas valid for an entire column | |
148 | * Editing and debugging formulas:: Fixing formulas | |
149 | * Updating the table:: Recomputing all dependent fields | |
150 | * Advanced features:: Field names, parameters and automatic recalc | |
151 | ||
152 | Hyperlinks | |
153 | ||
a7808fba | 154 | * Link format:: How links in Org are formatted |
4009494e GM |
155 | * Internal links:: Links to other places in the current file |
156 | * External links:: URL-like links to the world | |
157 | * Handling links:: Creating, inserting and following | |
a7808fba | 158 | * Using links outside Org:: Linking from my C source code? |
4009494e GM |
159 | * Link abbreviations:: Shortcuts for writing complex links |
160 | * Search options:: Linking to a specific location | |
161 | * Custom searches:: When the default search is not enough | |
4009494e GM |
162 | |
163 | Internal links | |
164 | ||
a7808fba | 165 | * Radio targets:: Make targets trigger links in plain text |
4009494e | 166 | |
a7808fba | 167 | TODO Items |
4009494e GM |
168 | |
169 | * TODO basics:: Marking and displaying TODO entries | |
170 | * TODO extensions:: Workflow and assignments | |
dbc28aaa | 171 | * Progress logging:: Dates and notes for progress |
4009494e GM |
172 | * Priorities:: Some things are more important than others |
173 | * Breaking down tasks:: Splitting a task into manageable pieces | |
174 | * Checkboxes:: Tick-off lists | |
175 | ||
176 | Extended use of TODO keywords | |
177 | ||
178 | * Workflow states:: From TODO to DONE in steps | |
dbc28aaa | 179 | * TODO types:: I do this, Fred does the rest |
4009494e | 180 | * Multiple sets in one file:: Mixing it all, and still finding your way |
dbc28aaa CD |
181 | * Fast access to TODO states:: Single letter selection of a state |
182 | * Per-file keywords:: Different files, different requirements | |
183 | * Faces for TODO keywords:: Highlighting states | |
ec712abb | 184 | * TODO dependencies:: When one task needs to wait for others |
dbc28aaa | 185 | |
a7808fba | 186 | Progress logging |
dbc28aaa CD |
187 | |
188 | * Closing items:: When was this entry marked DONE? | |
189 | * Tracking TODO state changes:: When did the status change? | |
4009494e GM |
190 | |
191 | Tags | |
192 | ||
193 | * Tag inheritance:: Tags use the tree structure of the outline | |
194 | * Setting tags:: How to assign tags to a headline | |
195 | * Tag searches:: Searching for combinations of tags | |
196 | ||
197 | Properties and Columns | |
198 | ||
199 | * Property syntax:: How properties are spelled out | |
a7808fba | 200 | * Special properties:: Access to other Org mode features |
4009494e | 201 | * Property searches:: Matching property values |
dbc28aaa | 202 | * Property inheritance:: Passing values down the tree |
4009494e GM |
203 | * Column view:: Tabular viewing and editing |
204 | * Property API:: Properties for Lisp programmers | |
205 | ||
a7808fba | 206 | Column view |
4009494e GM |
207 | |
208 | * Defining columns:: The COLUMNS format property | |
209 | * Using column view:: How to create and use column view | |
a7808fba | 210 | * Capturing column view:: A dynamic block for column view |
4009494e | 211 | |
a7808fba | 212 | Defining columns |
4009494e GM |
213 | |
214 | * Scope of column definitions:: Where defined, where valid? | |
215 | * Column attributes:: Appearance and content of a column | |
216 | ||
dbc28aaa | 217 | Dates and Times |
4009494e | 218 | |
a7808fba | 219 | * Timestamps:: Assigning a time to a tree entry |
4009494e GM |
220 | * Creating timestamps:: Commands which insert timestamps |
221 | * Deadlines and scheduling:: Planning your work | |
a7808fba CD |
222 | * Clocking work time:: Tracking how long you spend on a task |
223 | * Effort estimates:: Planning work effort in advance | |
96c8522a | 224 | * Relative timer:: Notes with a running timer |
4009494e GM |
225 | |
226 | Creating timestamps | |
227 | ||
a7808fba CD |
228 | * The date/time prompt:: How Org mode helps you entering date and time |
229 | * Custom time format:: Making dates look different | |
4009494e | 230 | |
a7808fba | 231 | Deadlines and scheduling |
4009494e GM |
232 | |
233 | * Inserting deadline/schedule:: Planning items | |
234 | * Repeated tasks:: Items that show up again and again | |
235 | ||
864c9740 CD |
236 | Capture |
237 | ||
238 | * Remember:: Capture new tasks/ideas with little interruption | |
239 | * Attachments:: Add files to tasks. | |
240 | ||
dbc28aaa | 241 | Remember |
4009494e | 242 | |
a7808fba | 243 | * Setting up Remember:: Some code for .emacs to get things going |
dbc28aaa CD |
244 | * Remember templates:: Define the outline of different note types |
245 | * Storing notes:: Directly get the note to where it belongs | |
246 | * Refiling notes:: Moving a note or task to a project | |
4009494e GM |
247 | |
248 | Agenda Views | |
249 | ||
250 | * Agenda files:: Files being searched for agenda information | |
251 | * Agenda dispatcher:: Keyboard access to agenda views | |
252 | * Built-in agenda views:: What is available out of the box? | |
253 | * Presentation and sorting:: How agenda items are prepared for display | |
a7808fba | 254 | * Agenda commands:: Remote editing of Org trees |
4009494e | 255 | * Custom agenda views:: Defining special searches and views |
a7808fba | 256 | * Agenda column view:: Using column view for collected entries |
4009494e GM |
257 | |
258 | The built-in agenda views | |
259 | ||
a7808fba | 260 | * Weekly/daily agenda:: The calendar page with current tasks |
4009494e GM |
261 | * Global TODO list:: All unfinished action items |
262 | * Matching tags and properties:: Structured information with fine-tuned search | |
263 | * Timeline:: Time-sorted view for single file | |
28a16a1b | 264 | * Keyword search:: Finding entries by keyword |
4009494e GM |
265 | * Stuck projects:: Find projects you need to review |
266 | ||
267 | Presentation and sorting | |
268 | ||
269 | * Categories:: Not all tasks are equal | |
270 | * Time-of-day specifications:: How the agenda knows the time | |
271 | * Sorting of agenda items:: The order of things | |
272 | ||
273 | Custom agenda views | |
274 | ||
275 | * Storing searches:: Type once, use often | |
276 | * Block agenda:: All the stuff you need in a single buffer | |
277 | * Setting Options:: Changing the rules | |
a7808fba CD |
278 | * Exporting Agenda Views:: Writing agendas to files |
279 | * Using the agenda elsewhere:: Using agenda information in other programs | |
4009494e GM |
280 | |
281 | Embedded LaTeX | |
282 | ||
283 | * Math symbols:: TeX macros for symbols and Greek letters | |
a7808fba | 284 | * Subscripts and superscripts:: Simple syntax for raising/lowering text |
4009494e GM |
285 | * LaTeX fragments:: Complex formulas made easy |
286 | * Processing LaTeX fragments:: Previewing LaTeX processing | |
287 | * CDLaTeX mode:: Speed up entering of formulas | |
288 | ||
289 | Exporting | |
290 | ||
b349f79f | 291 | * Markup rules:: Which structures are recognized? |
864c9740 | 292 | * Selective export:: Using tags to select and exclude trees |
b349f79f CD |
293 | * Export options:: Per-file export settings |
294 | * The export dispatcher:: How to access exporter commands | |
4009494e GM |
295 | * ASCII export:: Exporting to plain ASCII |
296 | * HTML export:: Exporting to HTML | |
71d35b24 | 297 | * LaTeX and PDF export:: Exporting to LaTeX, and processing to PDF |
4009494e GM |
298 | * XOXO export:: Exporting to XOXO |
299 | * iCalendar export:: Exporting in iCalendar format | |
b349f79f CD |
300 | |
301 | Markup rules | |
302 | ||
303 | * Document title:: How the document title is determined | |
304 | * Headings and sections:: The main structure of the exported document | |
305 | * Table of contents:: If, where, how to create a table of contents | |
306 | * Initial text:: Text before the first headline | |
307 | * Lists:: Plain lists are exported | |
308 | * Paragraphs:: What determines beginning and ending | |
309 | * Literal examples:: Source code and other examples | |
310 | * Include files:: Include the contents of a file during export | |
311 | * Tables exported:: Tables are exported richly | |
67df9cfb | 312 | * Inlined images:: How to inline images during export |
867d4bb3 | 313 | * Footnote markup:: |
b349f79f CD |
314 | * Emphasis and monospace:: To bold or not to bold |
315 | * TeX macros and LaTeX fragments:: Create special, rich export. | |
316 | * Horizontal rules:: A line across the page | |
317 | * Comment lines:: Some lines will not be exported | |
4009494e GM |
318 | |
319 | HTML export | |
320 | ||
b349f79f | 321 | * HTML Export commands:: How to invoke HTML export |
a7808fba | 322 | * Quoting HTML tags:: Using direct HTML in Org mode |
4009494e | 323 | * Links:: Transformation of links for HTML |
55e0839d CD |
324 | * Images in HTML export:: How to insert figures into HTML output |
325 | * Text areas in HTML export:: An alternative way to show an example | |
a7808fba CD |
326 | * CSS support:: Changing the appearance of the output |
327 | * Javascript support:: Info and Folding in a web browser | |
4009494e | 328 | |
71d35b24 | 329 | LaTeX and PDF export |
4009494e | 330 | |
a50253cc | 331 | * LaTeX/PDF export commands:: Which key invokes which commands |
4009494e | 332 | * Quoting LaTeX code:: Incorporating literal LaTeX code |
a7808fba | 333 | * Sectioning structure:: Changing sectioning in LaTeX output |
67df9cfb CD |
334 | * Tables in LaTeX export:: Options for exporting tables to LaTeX |
335 | * Images in LaTeX export:: How to insert figures into LaTeX output | |
4009494e | 336 | |
4009494e GM |
337 | Publishing |
338 | ||
339 | * Configuration:: Defining projects | |
340 | * Sample configuration:: Example projects | |
341 | * Triggering publication:: Publication commands | |
342 | ||
343 | Configuration | |
344 | ||
345 | * Project alist:: The central configuration variable | |
346 | * Sources and destinations:: From here to there | |
347 | * Selecting files:: What files are part of the project? | |
348 | * Publishing action:: Setting the function doing the publishing | |
349 | * Publishing options:: Tweaking HTML export | |
350 | * Publishing links:: Which links keep working after publishing? | |
351 | * Project page index:: Publishing a list of project files | |
352 | ||
353 | Sample configuration | |
354 | ||
355 | * Simple example:: One-component publishing | |
356 | * Complex example:: A multi-component publishing example | |
357 | ||
358 | Miscellaneous | |
359 | ||
360 | * Completion:: M-TAB knows what you need | |
a7808fba | 361 | * Customization:: Adapting Org to your taste |
4009494e GM |
362 | * In-buffer settings:: Overview of the #+KEYWORDS |
363 | * The very busy C-c C-c key:: When in doubt, press C-c C-c | |
364 | * Clean view:: Getting rid of leading stars in the outline | |
a7808fba | 365 | * TTY keys:: Using Org on a tty |
4009494e GM |
366 | * Interaction:: Other Emacs packages |
367 | * Bugs:: Things which do not work perfectly | |
368 | ||
369 | Interaction with other packages | |
370 | ||
a7808fba | 371 | * Cooperation:: Packages Org cooperates with |
4009494e GM |
372 | * Conflicts:: Packages that lead to conflicts |
373 | ||
b349f79f CD |
374 | Extensions |
375 | ||
376 | * Extensions in the contrib directory:: These come with the Org distro | |
377 | * Other extensions:: These you have to find on the web. | |
378 | ||
379 | Hacking | |
4009494e | 380 | |
4009494e GM |
381 | * Adding hyperlink types:: New custom link types |
382 | * Tables in arbitrary syntax:: Orgtbl for LaTeX and other programs | |
383 | * Dynamic blocks:: Automatically filled blocks | |
384 | * Special agenda views:: Customized views | |
385 | * Using the property API:: Writing programs that use entry properties | |
b349f79f | 386 | * Using the mapping API:: Mapping over all or selected entries |
4009494e | 387 | |
a7808fba | 388 | Tables and lists in arbitrary syntax |
4009494e GM |
389 | |
390 | * Radio tables:: Sending and receiving | |
391 | * A LaTeX example:: Step by step, almost a tutorial | |
392 | * Translator functions:: Copy and modify | |
a7808fba | 393 | * Radio lists:: Doing the same for lists |
4009494e GM |
394 | |
395 | @end detailmenu | |
396 | @end menu | |
397 | ||
a7808fba | 398 | @node Introduction, Document Structure, Top, Top |
4009494e GM |
399 | @chapter Introduction |
400 | @cindex introduction | |
401 | ||
402 | @menu | |
a7808fba CD |
403 | * Summary:: Brief summary of what Org does |
404 | * Installation:: How to install a downloaded version of Org | |
405 | * Activation:: How to activate Org for certain buffers | |
4009494e | 406 | * Feedback:: Bug reports, ideas, patches etc. |
dbc28aaa | 407 | * Conventions:: Type-setting conventions in the manual |
4009494e GM |
408 | @end menu |
409 | ||
410 | @node Summary, Installation, Introduction, Introduction | |
411 | @section Summary | |
412 | @cindex summary | |
413 | ||
a7808fba | 414 | Org is a mode for keeping notes, maintaining TODO lists, and doing |
4009494e GM |
415 | project planning with a fast and effective plain-text system. |
416 | ||
a7808fba CD |
417 | Org develops organizational tasks around NOTES files that contain |
418 | lists or information about projects as plain text. Org is | |
419 | implemented on top of Outline mode, which makes it possible to keep the | |
4009494e GM |
420 | content of large files well structured. Visibility cycling and |
421 | structure editing help to work with the tree. Tables are easily created | |
a7808fba | 422 | with a built-in table editor. Org supports TODO items, deadlines, |
4009494e GM |
423 | time stamps, and scheduling. It dynamically compiles entries into an |
424 | agenda that utilizes and smoothly integrates much of the Emacs calendar | |
425 | and diary. Plain text URL-like links connect to websites, emails, | |
426 | Usenet messages, BBDB entries, and any files related to the projects. | |
a7808fba | 427 | For printing and sharing of notes, an Org file can be exported as a |
dbc28aaa | 428 | structured ASCII file, as HTML, or (TODO and agenda items only) as an |
4009494e | 429 | iCalendar file. It can also serve as a publishing tool for a set of |
a7808fba | 430 | linked web pages. |
4009494e | 431 | |
a7808fba | 432 | An important design aspect that distinguishes Org from for example |
4009494e GM |
433 | Planner/Muse is that it encourages to store every piece of information |
434 | only once. In Planner, you have project pages, day pages and possibly | |
a7808fba | 435 | other files, duplicating some information such as tasks. In Org, |
4009494e GM |
436 | you only have notes files. In your notes you mark entries as tasks, |
437 | label them with tags and timestamps. All necessary lists like a | |
438 | schedule for the day, the agenda for a meeting, tasks lists selected by | |
439 | tags etc are created dynamically when you need them. | |
440 | ||
a7808fba | 441 | Org keeps simple things simple. When first fired up, it should |
4009494e GM |
442 | feel like a straightforward, easy to use outliner. Complexity is not |
443 | imposed, but a large amount of functionality is available when you need | |
a7808fba | 444 | it. Org is a toolbox and can be used in different ways, for |
4009494e GM |
445 | example as: |
446 | ||
447 | @example | |
448 | @r{@bullet{} outline extension with visibility cycling and structure editing} | |
449 | @r{@bullet{} ASCII system and table editor for taking structured notes} | |
450 | @r{@bullet{} ASCII table editor with spreadsheet-like capabilities} | |
451 | @r{@bullet{} TODO list editor} | |
452 | @r{@bullet{} full agenda and planner with deadlines and work scheduling} | |
453 | @r{@bullet{} environment to implement David Allen's GTD system} | |
454 | @r{@bullet{} a basic database application} | |
dbc28aaa | 455 | @r{@bullet{} simple hypertext system, with HTML and LaTeX export} |
4009494e GM |
456 | @r{@bullet{} publishing tool to create a set of interlinked webpages} |
457 | @end example | |
458 | ||
a7808fba | 459 | Org's automatic, context sensitive table editor with spreadsheet |
4009494e | 460 | capabilities can be integrated into any major mode by activating the |
a7808fba | 461 | minor Orgtbl mode. Using a translation step, it can be used to maintain |
4009494e | 462 | tables in arbitrary file types, for example in La@TeX{}. The structure |
a7808fba CD |
463 | editing and list creation capabilities can be used outside Org with |
464 | the minor Orgstruct mode. | |
4009494e GM |
465 | |
466 | @cindex FAQ | |
a7808fba CD |
467 | There is a website for Org which provides links to the newest |
468 | version of Org, as well as additional information, frequently asked | |
4009494e | 469 | questions (FAQ), links to tutorials etc. This page is located at |
dbc28aaa | 470 | @uref{http://orgmode.org}. |
4009494e GM |
471 | |
472 | @page | |
473 | ||
474 | ||
475 | @node Installation, Activation, Summary, Introduction | |
476 | @section Installation | |
477 | @cindex installation | |
478 | @cindex XEmacs | |
479 | ||
a7808fba | 480 | @b{Important:} @i{If Org is part of the Emacs distribution or an |
4009494e GM |
481 | XEmacs package, please skip this section and go directly to |
482 | @ref{Activation}.} | |
483 | ||
a7808fba CD |
484 | If you have downloaded Org from the Web, either as a distribution @file{.zip} |
485 | or @file{.tar} file, or as a GIT archive, you must take the following steps | |
486 | to install it: Go into the unpacked Org distribution directory and edit the | |
487 | top section of the file @file{Makefile}. You must set the name of the Emacs | |
488 | binary (likely either @file{emacs} or @file{xemacs}), and the paths to the | |
489 | directories where local Lisp and Info files are kept. If you don't have | |
490 | access to the system-wide directories, you can simply run Org directly from | |
491 | the distribution directory by adding the @file{lisp} subdirectory to the | |
492 | Emacs load path. To do this, add the following line to @file{.emacs}: | |
4009494e GM |
493 | |
494 | @example | |
a7808fba CD |
495 | (setq load-path (cons "~/path/to/orgdir/lisp" load-path)) |
496 | @end example | |
497 | ||
498 | @noindent | |
499 | If you plan to use code from the @file{contrib} subdirectory, do a similar | |
500 | step for this directory: | |
501 | ||
502 | @example | |
503 | (setq load-path (cons "~/path/to/orgdir/contrib/lisp" load-path)) | |
4009494e GM |
504 | @end example |
505 | ||
506 | @b{XEmacs users now need to install the file @file{noutline.el} from | |
a7808fba | 507 | the @file{xemacs} sub-directory of the Org distribution. Use the |
4009494e GM |
508 | command:} |
509 | ||
510 | @example | |
511 | @b{make install-noutline} | |
512 | @end example | |
513 | ||
a7808fba | 514 | @noindent Now byte-compile the Lisp files with the shell command: |
4009494e GM |
515 | |
516 | @example | |
517 | make | |
4009494e GM |
518 | @end example |
519 | ||
a7808fba CD |
520 | @noindent If you are running Org from the distribution directory, this is |
521 | all. If you want to install into the system directories, use | |
4009494e GM |
522 | |
523 | @example | |
a7808fba | 524 | make install |
4009494e GM |
525 | make install-info |
526 | @end example | |
527 | ||
528 | @noindent Then add to @file{.emacs}: | |
529 | ||
530 | @lisp | |
a7808fba | 531 | ;; This line only if Org is not part of the X/Emacs distribution. |
4009494e GM |
532 | (require 'org-install) |
533 | @end lisp | |
534 | ||
55e0839d | 535 | Do not forget to activate Org as described in the following section. |
a7808fba | 536 | |
4009494e GM |
537 | @node Activation, Feedback, Installation, Introduction |
538 | @section Activation | |
539 | @cindex activation | |
540 | @cindex autoload | |
a7808fba CD |
541 | @cindex global key bindings |
542 | @cindex key bindings, global | |
4009494e GM |
543 | |
544 | @iftex | |
545 | @b{Important:} @i{If you use copy-and-paste to copy lisp code from the | |
44ce9197 | 546 | PDF documentation as viewed by some PDF viewers to your .emacs file, the |
4009494e GM |
547 | single quote character comes out incorrectly and the code will not work. |
548 | You need to fix the single quotes by hand, or copy from Info | |
549 | documentation.} | |
550 | @end iftex | |
551 | ||
71d35b24 | 552 | Add the following lines to your @file{.emacs} file. The last three lines |
a7808fba CD |
553 | define @emph{global} keys for the commands @command{org-store-link}, |
554 | @command{org-agenda}, and @command{org-iswitchb} - please choose suitable | |
555 | keys yourself. | |
4009494e GM |
556 | |
557 | @lisp | |
558 | ;; The following lines are always needed. Choose your own keys. | |
559 | (add-to-list 'auto-mode-alist '("\\.org\\'" . org-mode)) | |
560 | (global-set-key "\C-cl" 'org-store-link) | |
561 | (global-set-key "\C-ca" 'org-agenda) | |
a7808fba | 562 | (global-set-key "\C-cb" 'org-iswitchb) |
4009494e GM |
563 | @end lisp |
564 | ||
a7808fba | 565 | Furthermore, you must activate @code{font-lock-mode} in Org |
4009494e GM |
566 | buffers, because significant functionality depends on font-locking being |
567 | active. You can do this with either one of the following two lines | |
568 | (XEmacs user must use the second option): | |
569 | @lisp | |
570 | (global-font-lock-mode 1) ; for all buffers | |
a7808fba | 571 | (add-hook 'org-mode-hook 'turn-on-font-lock) ; Org buffers only |
4009494e GM |
572 | @end lisp |
573 | ||
a7808fba | 574 | @cindex Org mode, turning on |
4009494e | 575 | With this setup, all files with extension @samp{.org} will be put |
a7808fba | 576 | into Org mode. As an alternative, make the first line of a file look |
4009494e GM |
577 | like this: |
578 | ||
579 | @example | |
580 | MY PROJECTS -*- mode: org; -*- | |
581 | @end example | |
582 | ||
a7808fba | 583 | @noindent which will select Org mode for this buffer no matter what |
4009494e GM |
584 | the file's name is. See also the variable |
585 | @code{org-insert-mode-line-in-empty-file}. | |
586 | ||
b4ba5e86 | 587 | Many commands in Org work on the region if the region is active. To make use |
b6cb4cd5 CD |
588 | of this, you need to have @code{transient-mark-mode} (@code{zmacs-regions} in |
589 | XEmacs) turned on. In Emacs 23 this is the default, in Emacs 22 you need to | |
590 | do this yourself with | |
591 | ||
592 | @lisp | |
593 | (transient-mark-mode 1) | |
594 | @end lisp | |
595 | ||
dbc28aaa | 596 | @node Feedback, Conventions, Activation, Introduction |
4009494e GM |
597 | @section Feedback |
598 | @cindex feedback | |
599 | @cindex bug reports | |
600 | @cindex maintainer | |
601 | @cindex author | |
602 | ||
b349f79f CD |
603 | If you find problems with Org, or if you have questions, remarks, or ideas |
604 | about it, please mail to the Org mailing list @code{emacs-orgmode@@gnu.org}. | |
605 | If you are not a member of the mailing list, your mail will be reviewed by a | |
606 | moderator and then passed through to the list. | |
4009494e GM |
607 | |
608 | For bug reports, please provide as much information as possible, | |
609 | including the version information of Emacs (@kbd{C-h v emacs-version | |
a7808fba CD |
610 | @key{RET}}) and Org (@kbd{C-h v org-version @key{RET}}), as well as |
611 | the Org related setup in @file{.emacs}. If an error occurs, a | |
4009494e GM |
612 | backtrace can be very useful (see below on how to create one). Often a |
613 | small example file helps, along with clear information about: | |
614 | ||
615 | @enumerate | |
616 | @item What exactly did you do? | |
617 | @item What did you expect to happen? | |
618 | @item What happened instead? | |
619 | @end enumerate | |
620 | @noindent Thank you for helping to improve this mode. | |
621 | ||
622 | @subsubheading How to create a useful backtrace | |
623 | ||
624 | @cindex backtrace of an error | |
a7808fba | 625 | If working with Org produces an error with a message you don't |
4009494e GM |
626 | understand, you may have hit a bug. The best way to report this is by |
627 | providing, in addition to what was mentioned above, a @emph{Backtrace}. | |
628 | This is information from the built-in debugger about where and how the | |
629 | error occurred. Here is how to produce a useful backtrace: | |
630 | ||
631 | @enumerate | |
632 | @item | |
633 | Start a fresh Emacs or XEmacs, and make sure that it will load the | |
634 | original Lisp code in @file{org.el} instead of the compiled version in | |
635 | @file{org.elc}. The backtrace contains much more information if it is | |
636 | produced with uncompiled code. To do this, either rename @file{org.elc} | |
637 | to something else before starting Emacs, or ask Emacs explicitly to load | |
638 | @file{org.el} by using the command line | |
639 | @example | |
640 | emacs -l /path/to/org.el | |
641 | @end example | |
642 | @item | |
643 | Go to the @code{Options} menu and select @code{Enter Debugger on Error} | |
644 | (XEmacs has this option in the @code{Troubleshooting} sub-menu). | |
645 | @item | |
646 | Do whatever you have to do to hit the error. Don't forget to | |
647 | document the steps you take. | |
648 | @item | |
649 | When you hit the error, a @file{*Backtrace*} buffer will appear on the | |
650 | screen. Save this buffer to a file (for example using @kbd{C-x C-w}) and | |
651 | attach it to your bug report. | |
652 | @end enumerate | |
653 | ||
dbc28aaa CD |
654 | @node Conventions, , Feedback, Introduction |
655 | @section Typesetting conventions used in this manual | |
656 | ||
a7808fba | 657 | Org uses three types of keywords: TODO keywords, tags, and property |
dbc28aaa CD |
658 | names. In this manual we use the following conventions: |
659 | ||
660 | @table @code | |
661 | @item TODO | |
662 | @itemx WAITING | |
663 | TODO keywords are written with all capitals, even if they are | |
664 | user-defined. | |
665 | @item boss | |
666 | @itemx ARCHIVE | |
667 | User-defined tags are written in lowercase; built-in tags with special | |
668 | meaning are written with all capitals. | |
669 | @item Release | |
670 | @itemx PRIORITY | |
671 | User-defined properties are capitalized; built-in properties with | |
672 | special meaning are written with all capitals. | |
673 | @end table | |
674 | ||
a7808fba | 675 | @node Document Structure, Tables, Introduction, Top |
4009494e GM |
676 | @chapter Document Structure |
677 | @cindex document structure | |
678 | @cindex structure of document | |
679 | ||
a7808fba | 680 | Org is based on outline mode and provides flexible commands to |
4009494e GM |
681 | edit the structure of the document. |
682 | ||
683 | @menu | |
a7808fba CD |
684 | * Outlines:: Org is based on Outline mode |
685 | * Headlines:: How to typeset Org tree headlines | |
4009494e GM |
686 | * Visibility cycling:: Show and hide, much simplified |
687 | * Motion:: Jumping to other headlines | |
688 | * Structure editing:: Changing sequence and level of headlines | |
689 | * Archiving:: Move done task trees to a different place | |
690 | * Sparse trees:: Matches embedded in context | |
691 | * Plain lists:: Additional structure within an entry | |
692 | * Drawers:: Tucking stuff away | |
55e0839d | 693 | * Footnotes:: How footnotes are defined in Org's syntax |
a7808fba | 694 | * Orgstruct mode:: Structure editing outside Org |
4009494e GM |
695 | @end menu |
696 | ||
a7808fba | 697 | @node Outlines, Headlines, Document Structure, Document Structure |
4009494e GM |
698 | @section Outlines |
699 | @cindex outlines | |
a7808fba | 700 | @cindex Outline mode |
4009494e | 701 | |
a7808fba | 702 | Org is implemented on top of Outline mode. Outlines allow a |
4009494e GM |
703 | document to be organized in a hierarchical structure, which (at least |
704 | for me) is the best representation of notes and thoughts. An overview | |
705 | of this structure is achieved by folding (hiding) large parts of the | |
706 | document to show only the general document structure and the parts | |
a7808fba | 707 | currently being worked on. Org greatly simplifies the use of |
4009494e GM |
708 | outlines by compressing the entire show/hide functionality into a single |
709 | command @command{org-cycle}, which is bound to the @key{TAB} key. | |
710 | ||
a7808fba | 711 | @node Headlines, Visibility cycling, Outlines, Document Structure |
4009494e GM |
712 | @section Headlines |
713 | @cindex headlines | |
714 | @cindex outline tree | |
715 | ||
716 | Headlines define the structure of an outline tree. The headlines in | |
a7808fba | 717 | Org start with one or more stars, on the left margin@footnote{See |
4009494e GM |
718 | the variable @code{org-special-ctrl-a/e} to configure special behavior |
719 | of @kbd{C-a} and @kbd{C-e} in headlines.}. For example: | |
720 | ||
721 | @example | |
722 | * Top level headline | |
723 | ** Second level | |
724 | *** 3rd level | |
725 | some text | |
726 | *** 3rd level | |
727 | more text | |
728 | ||
729 | * Another top level headline | |
730 | @end example | |
731 | ||
732 | @noindent Some people find the many stars too noisy and would prefer an | |
733 | outline that has whitespace followed by a single star as headline | |
734 | starters. @ref{Clean view} describes a setup to realize this. | |
735 | ||
736 | An empty line after the end of a subtree is considered part of it and | |
737 | will be hidden when the subtree is folded. However, if you leave at | |
738 | least two empty lines, one empty line will remain visible after folding | |
739 | the subtree, in order to structure the collapsed view. See the | |
740 | variable @code{org-cycle-separator-lines} to modify this behavior. | |
741 | ||
a7808fba | 742 | @node Visibility cycling, Motion, Headlines, Document Structure |
4009494e GM |
743 | @section Visibility cycling |
744 | @cindex cycling, visibility | |
745 | @cindex visibility cycling | |
746 | @cindex trees, visibility | |
747 | @cindex show hidden text | |
748 | @cindex hide text | |
749 | ||
750 | Outlines make it possible to hide parts of the text in the buffer. | |
a7808fba | 751 | Org uses just two commands, bound to @key{TAB} and |
4009494e GM |
752 | @kbd{S-@key{TAB}} to change the visibility in the buffer. |
753 | ||
754 | @cindex subtree visibility states | |
755 | @cindex subtree cycling | |
756 | @cindex folded, subtree visibility state | |
757 | @cindex children, subtree visibility state | |
758 | @cindex subtree, subtree visibility state | |
759 | @table @kbd | |
760 | @kindex @key{TAB} | |
761 | @item @key{TAB} | |
762 | @emph{Subtree cycling}: Rotate current subtree among the states | |
763 | ||
764 | @example | |
765 | ,-> FOLDED -> CHILDREN -> SUBTREE --. | |
766 | '-----------------------------------' | |
767 | @end example | |
768 | ||
769 | The cursor must be on a headline for this to work@footnote{see, however, | |
770 | the option @code{org-cycle-emulate-tab}.}. When the cursor is at the | |
771 | beginning of the buffer and the first line is not a headline, then | |
772 | @key{TAB} actually runs global cycling (see below)@footnote{see the | |
773 | option @code{org-cycle-global-at-bob}.}. Also when called with a prefix | |
774 | argument (@kbd{C-u @key{TAB}}), global cycling is invoked. | |
775 | ||
776 | @cindex global visibility states | |
777 | @cindex global cycling | |
778 | @cindex overview, global visibility state | |
779 | @cindex contents, global visibility state | |
780 | @cindex show all, global visibility state | |
781 | @kindex S-@key{TAB} | |
782 | @item S-@key{TAB} | |
783 | @itemx C-u @key{TAB} | |
784 | @emph{Global cycling}: Rotate the entire buffer among the states | |
785 | ||
786 | @example | |
787 | ,-> OVERVIEW -> CONTENTS -> SHOW ALL --. | |
788 | '--------------------------------------' | |
789 | @end example | |
790 | ||
a7808fba CD |
791 | When @kbd{S-@key{TAB}} is called with a numeric prefix argument N, the |
792 | CONTENTS view up to headlines of level N will be shown. Note that inside | |
793 | tables, @kbd{S-@key{TAB}} jumps to the previous field. | |
4009494e GM |
794 | |
795 | @cindex show all, command | |
864c9740 CD |
796 | @kindex C-u C-u C-u @key{TAB} |
797 | @item C-u C-u C-u @key{TAB} | |
798 | Show all, including drawers. | |
4009494e GM |
799 | @kindex C-c C-r |
800 | @item C-c C-r | |
a7808fba CD |
801 | Reveal context around point, showing the current entry, the following heading |
802 | and the hierarchy above. Useful for working near a location that has been | |
803 | exposed by a sparse tree command (@pxref{Sparse trees}) or an agenda command | |
804 | (@pxref{Agenda commands}). With a prefix argument show, on each | |
4009494e GM |
805 | level, all sibling headings. |
806 | @kindex C-c C-x b | |
807 | @item C-c C-x b | |
808 | Show the current subtree in an indirect buffer@footnote{The indirect | |
809 | buffer | |
810 | @ifinfo | |
811 | (@pxref{Indirect Buffers,,,emacs,GNU Emacs Manual}) | |
812 | @end ifinfo | |
813 | @ifnotinfo | |
814 | (see the Emacs manual for more information about indirect buffers) | |
815 | @end ifnotinfo | |
816 | will contain the entire buffer, but will be narrowed to the current | |
817 | tree. Editing the indirect buffer will also change the original buffer, | |
a7808fba CD |
818 | but without affecting visibility in that buffer.}. With a numeric |
819 | prefix argument N, go up to level N and then take that tree. If N is | |
820 | negative then go up that many levels. With a @kbd{C-u} prefix, do not remove | |
4009494e GM |
821 | the previously used indirect buffer. |
822 | @end table | |
823 | ||
a7808fba | 824 | When Emacs first visits an Org file, the global state is set to |
4009494e GM |
825 | OVERVIEW, i.e. only the top level headlines are visible. This can be |
826 | configured through the variable @code{org-startup-folded}, or on a | |
827 | per-file basis by adding one of the following lines anywhere in the | |
828 | buffer: | |
829 | ||
830 | @example | |
831 | #+STARTUP: overview | |
832 | #+STARTUP: content | |
833 | #+STARTUP: showall | |
834 | @end example | |
835 | ||
b349f79f | 836 | @noindent |
a50253cc | 837 | Furthermore, any entries with a @samp{VISIBILITY} property (@pxref{Properties |
b349f79f CD |
838 | and Columns}) will get their visibility adapted accordingly. Allowed values |
839 | for this property are @code{folded}, @code{children}, @code{content}, and | |
840 | @code{all}. | |
841 | @table @kbd | |
842 | @kindex C-u C-u @key{TAB} | |
843 | @item C-u C-u @key{TAB} | |
844 | Switch back to the startup visibility of the buffer, i.e. whatever is | |
845 | requested by startup options and @samp{VISIBILITY} properties in individual | |
846 | entries. | |
847 | @end table | |
848 | ||
a7808fba | 849 | @node Motion, Structure editing, Visibility cycling, Document Structure |
4009494e GM |
850 | @section Motion |
851 | @cindex motion, between headlines | |
852 | @cindex jumping, to headlines | |
853 | @cindex headline navigation | |
854 | The following commands jump to other headlines in the buffer. | |
855 | ||
856 | @table @kbd | |
857 | @kindex C-c C-n | |
858 | @item C-c C-n | |
859 | Next heading. | |
860 | @kindex C-c C-p | |
861 | @item C-c C-p | |
862 | Previous heading. | |
863 | @kindex C-c C-f | |
864 | @item C-c C-f | |
865 | Next heading same level. | |
866 | @kindex C-c C-b | |
867 | @item C-c C-b | |
868 | Previous heading same level. | |
869 | @kindex C-c C-u | |
870 | @item C-c C-u | |
871 | Backward to higher level heading. | |
872 | @kindex C-c C-j | |
873 | @item C-c C-j | |
874 | Jump to a different place without changing the current outline | |
875 | visibility. Shows the document structure in a temporary buffer, where | |
876 | you can use the following keys to find your destination: | |
877 | @example | |
878 | @key{TAB} @r{Cycle visibility.} | |
879 | @key{down} / @key{up} @r{Next/previous visible headline.} | |
71d35b24 CD |
880 | @key{RET} @r{Select this location.} |
881 | @kbd{/} @r{Do a Sparse-tree search} | |
882 | @r{The following keys work if you turn off @code{org-goto-auto-isearch}} | |
4009494e GM |
883 | n / p @r{Next/previous visible headline.} |
884 | f / b @r{Next/previous headline same level.} | |
885 | u @r{One level up.} | |
886 | 0-9 @r{Digit argument.} | |
71d35b24 | 887 | q @r{Quit} |
4009494e | 888 | @end example |
d60b1ba1 | 889 | See also the variable@code{org-goto-interface}. |
4009494e GM |
890 | @end table |
891 | ||
a7808fba | 892 | @node Structure editing, Archiving, Motion, Document Structure |
4009494e GM |
893 | @section Structure editing |
894 | @cindex structure editing | |
895 | @cindex headline, promotion and demotion | |
896 | @cindex promotion, of subtrees | |
897 | @cindex demotion, of subtrees | |
898 | @cindex subtree, cut and paste | |
899 | @cindex pasting, of subtrees | |
900 | @cindex cutting, of subtrees | |
901 | @cindex copying, of subtrees | |
902 | @cindex subtrees, cut and paste | |
903 | ||
904 | @table @kbd | |
905 | @kindex M-@key{RET} | |
906 | @item M-@key{RET} | |
907 | Insert new heading with same level as current. If the cursor is in a | |
908 | plain list item, a new item is created (@pxref{Plain lists}). To force | |
a7808fba | 909 | creation of a new headline, use a prefix argument, or first press @key{RET} |
4009494e GM |
910 | to get to the beginning of the next line. When this command is used in |
911 | the middle of a line, the line is split and the rest of the line becomes | |
28a16a1b CD |
912 | the new headline@footnote{If you do not want the line to be split, |
913 | customize the variable @code{org-M-RET-may-split-line}.}. If the | |
914 | command is used at the beginning of a headline, the new headline is | |
915 | created before the current line. If at the beginning of any other line, | |
916 | the content of that line is made the new heading. If the command is | |
917 | used at the end of a folded subtree (i.e. behind the ellipses at the end | |
918 | of a headline), then a headline like the current one will be inserted | |
919 | after the end of the subtree. | |
dbc28aaa CD |
920 | @kindex C-@key{RET} |
921 | @item C-@key{RET} | |
71d35b24 CD |
922 | Just like @kbd{M-@key{RET}}, except when adding a new heading below the |
923 | current heading, the new heading is placed after the body instead of before | |
924 | it. This command works from anywhere in the entry. | |
4009494e GM |
925 | @kindex M-S-@key{RET} |
926 | @item M-S-@key{RET} | |
927 | Insert new TODO entry with same level as current heading. | |
864c9740 CD |
928 | @kindex C-S-@key{RET} |
929 | @item C-S-@key{RET} | |
930 | Insert new TODO entry with same level as current heading. Like | |
931 | @kbd{C-@key{RET}}, the new headline will be inserted after the current | |
932 | subtree. | |
4009494e GM |
933 | @kindex M-@key{left} |
934 | @item M-@key{left} | |
935 | Promote current heading by one level. | |
936 | @kindex M-@key{right} | |
937 | @item M-@key{right} | |
938 | Demote current heading by one level. | |
939 | @kindex M-S-@key{left} | |
940 | @item M-S-@key{left} | |
941 | Promote the current subtree by one level. | |
942 | @kindex M-S-@key{right} | |
943 | @item M-S-@key{right} | |
944 | Demote the current subtree by one level. | |
945 | @kindex M-S-@key{up} | |
946 | @item M-S-@key{up} | |
947 | Move subtree up (swap with previous subtree of same | |
948 | level). | |
949 | @kindex M-S-@key{down} | |
950 | @item M-S-@key{down} | |
951 | Move subtree down (swap with next subtree of same level). | |
952 | @kindex C-c C-x C-w | |
4009494e | 953 | @item C-c C-x C-w |
4009494e | 954 | Kill subtree, i.e. remove it from buffer but save in kill ring. |
a7808fba | 955 | With a numeric prefix argument N, kill N sequential subtrees. |
4009494e GM |
956 | @kindex C-c C-x M-w |
957 | @item C-c C-x M-w | |
a7808fba CD |
958 | Copy subtree to kill ring. With a numeric prefix argument N, copy the N |
959 | sequential subtrees. | |
4009494e GM |
960 | @kindex C-c C-x C-y |
961 | @item C-c C-x C-y | |
962 | Yank subtree from kill ring. This does modify the level of the subtree to | |
a7808fba CD |
963 | make sure the tree fits in nicely at the yank position. The yank level can |
964 | also be specified with a numeric prefix argument, or by yanking after a | |
4009494e | 965 | headline marker like @samp{****}. |
96c8522a | 966 | @kindex C-y |
e45e3595 CD |
967 | @item C-y |
968 | Depending on the variables @code{org-yank-adjusted-subtrees} and | |
969 | @code{org-yank-folded-subtrees}, Org's internal @code{yank} command will | |
970 | paste subtrees folded and in a clever way, using the same command as @kbd{C-c | |
55033558 CD |
971 | C-x C-y}. With the default settings, no level adjustment will take place, |
972 | but the yanked tree will be folded unless doing so would swallow text | |
973 | previously visible. Any prefix argument to this command will force a normal | |
974 | @code{yank} to be executed, with the prefix passed along. A good way to | |
975 | force a normal yank is @kbd{C-u C-y}. If you use @code{yank-pop} after a | |
976 | yank, it will yank previous kill items plainly, without adjustment and | |
977 | folding. | |
dbc28aaa CD |
978 | @kindex C-c C-w |
979 | @item C-c C-w | |
e45e3595 | 980 | Refile entry or region to a different location. @xref{Refiling notes}. |
4009494e GM |
981 | @kindex C-c ^ |
982 | @item C-c ^ | |
a7808fba CD |
983 | Sort same-level entries. When there is an active region, all entries in the |
984 | region will be sorted. Otherwise the children of the current headline are | |
985 | sorted. The command prompts for the sorting method, which can be | |
986 | alphabetically, numerically, by time (using the first time stamp in each | |
987 | entry), by priority, or by TODO keyword (in the sequence the keywords have | |
988 | been defined in the setup). Reverse sorting is possible as well. You can | |
989 | also supply your own function to extract the sorting key. With a @kbd{C-u} | |
990 | prefix, sorting will be case-sensitive. With two @kbd{C-u C-u} prefixes, | |
991 | duplicate entries will also be removed. | |
b349f79f CD |
992 | @kindex C-x n s |
993 | @item C-x n s | |
994 | Narrow buffer to current subtree. | |
995 | @kindex C-x n w | |
996 | @item C-x n w | |
997 | Widen buffer to remove a narrowing. | |
28a16a1b CD |
998 | @kindex C-c * |
999 | @item C-c * | |
55e0839d CD |
1000 | Turn a normal line or plain list item into a headline (so that it becomes a |
1001 | subheading at its location). Also turn a headline into a normal line by | |
1002 | removing the stars. If there is an active region, turn all lines in the | |
1003 | region into headlines. If the first line in the region was an item, turn | |
1004 | only the item lines into headlines. Finally, if the first line is a | |
28a16a1b | 1005 | headline, remove the stars from all headlines in the region. |
4009494e GM |
1006 | @end table |
1007 | ||
1008 | @cindex region, active | |
1009 | @cindex active region | |
a7808fba CD |
1010 | @cindex Transient mark mode |
1011 | When there is an active region (Transient mark mode), promotion and | |
4009494e GM |
1012 | demotion work on all headlines in the region. To select a region of |
1013 | headlines, it is best to place both point and mark at the beginning of a | |
1014 | line, mark at the beginning of the first headline, and point at the line | |
1015 | just after the last headline to change. Note that when the cursor is | |
1016 | inside a table (@pxref{Tables}), the Meta-Cursor keys have different | |
1017 | functionality. | |
1018 | ||
a7808fba | 1019 | @node Archiving, Sparse trees, Structure editing, Document Structure |
4009494e GM |
1020 | @section Archiving |
1021 | @cindex archiving | |
1022 | ||
1023 | When a project represented by a (sub)tree is finished, you may want | |
1024 | to move the tree out of the way and to stop it from contributing to the | |
a7808fba | 1025 | agenda. Org mode knows two ways of archiving. You can mark a tree with |
4009494e GM |
1026 | the ARCHIVE tag, or you can move an entire (sub)tree to a different |
1027 | location. | |
1028 | ||
1029 | @menu | |
1030 | * ARCHIVE tag:: Marking a tree as inactive | |
1031 | * Moving subtrees:: Moving a tree to an archive file | |
1032 | @end menu | |
1033 | ||
1034 | @node ARCHIVE tag, Moving subtrees, Archiving, Archiving | |
1035 | @subsection The ARCHIVE tag | |
1036 | @cindex internal archiving | |
1037 | ||
1038 | A headline that is marked with the ARCHIVE tag (@pxref{Tags}) stays at | |
1039 | its location in the outline tree, but behaves in the following way: | |
1040 | @itemize @minus | |
1041 | @item | |
1042 | It does not open when you attempt to do so with a visibility cycling | |
1043 | command (@pxref{Visibility cycling}). You can force cycling archived | |
1044 | subtrees with @kbd{C-@key{TAB}}, or by setting the option | |
1045 | @code{org-cycle-open-archived-trees}. Also normal outline commands like | |
1046 | @code{show-all} will open archived subtrees. | |
1047 | @item | |
1048 | During sparse tree construction (@pxref{Sparse trees}), matches in | |
1049 | archived subtrees are not exposed, unless you configure the option | |
1050 | @code{org-sparse-tree-open-archived-trees}. | |
1051 | @item | |
a7808fba | 1052 | During agenda view construction (@pxref{Agenda Views}), the content of |
4009494e | 1053 | archived trees is ignored unless you configure the option |
44ce9197 CD |
1054 | @code{org-agenda-skip-archived-trees}, in which case these trees will always |
1055 | be included. In the agenda you can press the @kbd{v} key to get archives | |
1056 | temporarily included. | |
4009494e GM |
1057 | @item |
1058 | Archived trees are not exported (@pxref{Exporting}), only the headline | |
1059 | is. Configure the details using the variable | |
1060 | @code{org-export-with-archived-trees}. | |
1061 | @end itemize | |
1062 | ||
1063 | The following commands help managing the ARCHIVE tag: | |
1064 | ||
1065 | @table @kbd | |
a7808fba CD |
1066 | @kindex C-c C-x a |
1067 | @item C-c C-x a | |
4009494e | 1068 | Toggle the ARCHIVE tag for the current headline. When the tag is set, |
a7808fba | 1069 | the headline changes to a shadowed face, and the subtree below it is |
4009494e | 1070 | hidden. |
a7808fba CD |
1071 | @kindex C-u C-c C-x a |
1072 | @item C-u C-c C-x a | |
4009494e GM |
1073 | Check if any direct children of the current headline should be archived. |
1074 | To do this, each subtree is checked for open TODO entries. If none are | |
1075 | found, the command offers to set the ARCHIVE tag for the child. If the | |
1076 | cursor is @emph{not} on a headline when this command is invoked, the | |
1077 | level 1 trees will be checked. | |
1078 | @kindex C-@kbd{TAB} | |
1079 | @item C-@kbd{TAB} | |
1080 | Cycle a tree even if it is tagged with ARCHIVE. | |
1081 | @end table | |
1082 | ||
1083 | @node Moving subtrees, , ARCHIVE tag, Archiving | |
1084 | @subsection Moving subtrees | |
1085 | @cindex external archiving | |
1086 | ||
a7808fba | 1087 | Once an entire project is finished, you may want to move it to a different |
44ce9197 | 1088 | location. Org can move it to an @emph{Archive Sibling} in the same tree, to a |
a7808fba | 1089 | different tree in the current file, or to a different file, the archive file. |
4009494e GM |
1090 | |
1091 | @table @kbd | |
a7808fba CD |
1092 | @kindex C-c C-x A |
1093 | @item C-c C-x A | |
44ce9197 CD |
1094 | Move the current entry to the @emph{Archive Sibling}. This is a sibling of |
1095 | the entry with the heading @samp{Archive} and the tag @samp{ARCHIVE} | |
a7808fba CD |
1096 | (@pxref{ARCHIVE tag}). The entry becomes a child of that sibling and in this |
1097 | way retains a lot of its original context, including inherited tags and | |
1098 | approximate position in the outline. | |
4009494e GM |
1099 | @kindex C-c C-x C-s |
1100 | @item C-c C-x C-s | |
1101 | Archive the subtree starting at the cursor position to the location | |
1102 | given by @code{org-archive-location}. Context information that could be | |
a7808fba | 1103 | lost like the file name, the category, inherited tags, and the TODO |
4009494e GM |
1104 | state will be store as properties in the entry. |
1105 | @kindex C-u C-c C-x C-s | |
1106 | @item C-u C-c C-x C-s | |
1107 | Check if any direct children of the current headline could be moved to | |
1108 | the archive. To do this, each subtree is checked for open TODO entries. | |
1109 | If none are found, the command offers to move it to the archive | |
1110 | location. If the cursor is @emph{not} on a headline when this command | |
1111 | is invoked, the level 1 trees will be checked. | |
1112 | @end table | |
1113 | ||
1114 | @cindex archive locations | |
1115 | The default archive location is a file in the same directory as the | |
1116 | current file, with the name derived by appending @file{_archive} to the | |
1117 | current file name. For information and examples on how to change this, | |
1118 | see the documentation string of the variable | |
1119 | @code{org-archive-location}. There is also an in-buffer option for | |
dbc28aaa CD |
1120 | setting this variable, for example@footnote{For backward compatibility, |
1121 | the following also works: If there are several such lines in a file, | |
1122 | each specifies the archive location for the text below it. The first | |
1123 | such line also applies to any text before its definition. However, | |
1124 | using this method is @emph{strongly} deprecated as it is incompatible | |
1125 | with the outline structure of the document. The correct method for | |
55e0839d | 1126 | setting multiple archive locations in a buffer is using properties.}: |
4009494e GM |
1127 | |
1128 | @example | |
1129 | #+ARCHIVE: %s_done:: | |
1130 | @end example | |
1131 | ||
1132 | @noindent | |
dbc28aaa CD |
1133 | If you would like to have a special ARCHIVE location for a single entry |
1134 | or a (sub)tree, give the entry an @code{:ARCHIVE:} property with the | |
a7808fba | 1135 | location as the value (@pxref{Properties and Columns}). |
4009494e | 1136 | |
28a16a1b CD |
1137 | When a subtree is moved, it receives a number of special properties that |
1138 | record context information like the file from where the entry came, it's | |
1139 | outline path the archiving time etc. Configure the variable | |
1140 | @code{org-archive-save-context-info} to adjust the amount of information | |
1141 | added. | |
1142 | ||
a7808fba | 1143 | @node Sparse trees, Plain lists, Archiving, Document Structure |
4009494e GM |
1144 | @section Sparse trees |
1145 | @cindex sparse trees | |
1146 | @cindex trees, sparse | |
1147 | @cindex folding, sparse trees | |
1148 | @cindex occur, command | |
1149 | ||
b349f79f CD |
1150 | An important feature of Org mode is the ability to construct @emph{sparse |
1151 | trees} for selected information in an outline tree, so that the entire | |
1152 | document is folded as much as possible, but the selected information is made | |
1153 | visible along with the headline structure above it@footnote{See also the | |
1154 | variables @code{org-show-hierarchy-above}, @code{org-show-following-heading}, | |
1155 | @code{org-show-siblings}, and @code{org-show-entry-below} for detailed | |
1156 | control on how much context is shown around each match.}. Just try it out | |
1157 | and you will see immediately how it works. | |
dbc28aaa | 1158 | |
a7808fba | 1159 | Org mode contains several commands creating such trees, all these |
dbc28aaa | 1160 | commands can be accessed through a dispatcher: |
4009494e GM |
1161 | |
1162 | @table @kbd | |
1163 | @kindex C-c / | |
1164 | @item C-c / | |
dbc28aaa CD |
1165 | This prompts for an extra key to select a sparse-tree creating command. |
1166 | @kindex C-c / r | |
1167 | @item C-c / r | |
b349f79f CD |
1168 | Occur. Prompts for a regexp and shows a sparse tree with all matches. If |
1169 | the match is in a headline, the headline is made visible. If the match is in | |
1170 | the body of an entry, headline and body are made visible. In order to | |
1171 | provide minimal context, also the full hierarchy of headlines above the match | |
1172 | is shown, as well as the headline following the match. Each match is also | |
1173 | highlighted; the highlights disappear when the buffer is changed by an | |
1174 | editing command@footnote{depending on the option | |
1175 | @code{org-remove-highlights-with-change}}, or by pressing @kbd{C-c C-c}. | |
1176 | When called with a @kbd{C-u} prefix argument, previous highlights are kept, | |
1177 | so several calls to this command can be stacked. | |
4009494e | 1178 | @end table |
dbc28aaa | 1179 | |
4009494e GM |
1180 | @noindent |
1181 | For frequently used sparse trees of specific search strings, you can | |
1182 | use the variable @code{org-agenda-custom-commands} to define fast | |
1183 | keyboard access to specific sparse trees. These commands will then be | |
1184 | accessible through the agenda dispatcher (@pxref{Agenda dispatcher}). | |
1185 | For example: | |
1186 | ||
1187 | @lisp | |
1188 | (setq org-agenda-custom-commands | |
1189 | '(("f" occur-tree "FIXME"))) | |
1190 | @end lisp | |
1191 | ||
1192 | @noindent will define the key @kbd{C-c a f} as a shortcut for creating | |
1193 | a sparse tree matching the string @samp{FIXME}. | |
1194 | ||
dbc28aaa CD |
1195 | The other sparse tree commands select headings based on TODO keywords, |
1196 | tags, or properties and will be discussed later in this manual. | |
4009494e GM |
1197 | |
1198 | @kindex C-c C-e v | |
1199 | @cindex printing sparse trees | |
1200 | @cindex visible text, printing | |
1201 | To print a sparse tree, you can use the Emacs command | |
1202 | @code{ps-print-buffer-with-faces} which does not print invisible parts | |
1203 | of the document @footnote{This does not work under XEmacs, because | |
1204 | XEmacs uses selective display for outlining, not text properties.}. | |
1205 | Or you can use the command @kbd{C-c C-e v} to export only the visible | |
1206 | part of the document and print the resulting file. | |
1207 | ||
a7808fba | 1208 | @node Plain lists, Drawers, Sparse trees, Document Structure |
4009494e GM |
1209 | @section Plain lists |
1210 | @cindex plain lists | |
1211 | @cindex lists, plain | |
1212 | @cindex lists, ordered | |
1213 | @cindex ordered lists | |
1214 | ||
1215 | Within an entry of the outline tree, hand-formatted lists can provide | |
1216 | additional structure. They also provide a way to create lists of | |
a7808fba | 1217 | checkboxes (@pxref{Checkboxes}). Org supports editing such lists, |
dbc28aaa | 1218 | and the HTML exporter (@pxref{Exporting}) parses and formats them. |
4009494e | 1219 | |
b349f79f CD |
1220 | Org knows ordered lists, unordered lists, and description lists. |
1221 | @itemize @bullet | |
1222 | @item | |
1223 | @emph{Unordered} list items start with @samp{-}, @samp{+}, or | |
1224 | @samp{*}@footnote{When using @samp{*} as a bullet, lines must be indented or | |
1225 | they will be seen as top-level headlines. Also, when you are hiding leading | |
1226 | stars to get a clean outline view, plain list items starting with a star are | |
1227 | visually indistinguishable from true headlines. In short: even though | |
1228 | @samp{*} is supported, it may be better to not use it for plain list items.} | |
1229 | as bullets. | |
1230 | @item | |
1231 | @emph{Ordered} list items start with a numeral followed by either a period or | |
1232 | a right parenthesis, such as @samp{1.} or @samp{1)}. | |
1233 | @item | |
1234 | @emph{Description} list items are like unordered list items, but contain the | |
1235 | separator @samp{ :: } to separate the description @emph{term} from the | |
a50253cc | 1236 | description. |
b349f79f CD |
1237 | @end itemize |
1238 | ||
1239 | Items belonging to the same list must have the same indentation on the first | |
1240 | line. In particular, if an ordered list reaches number @samp{10.}, then the | |
1241 | 2--digit numbers must be written left-aligned with the other numbers in the | |
1242 | list. Indentation also determines the end of a list item. It ends before | |
1243 | the next line that is indented like the bullet/number, or less. Empty lines | |
1244 | are part of the previous item, so you can have several paragraphs in one | |
1245 | item. If you would like an empty line to terminate all currently open plain | |
1246 | lists, configure the variable @code{org-empty-line-terminates-plain-lists}. | |
1247 | Here is an example: | |
4009494e GM |
1248 | |
1249 | @example | |
1250 | @group | |
1251 | ** Lord of the Rings | |
1252 | My favorite scenes are (in this order) | |
1253 | 1. The attack of the Rohirrim | |
a50253cc | 1254 | 2. Eowyn's fight with the witch king |
4009494e GM |
1255 | + this was already my favorite scene in the book |
1256 | + I really like Miranda Otto. | |
1257 | 3. Peter Jackson being shot by Legolas | |
1258 | - on DVD only | |
1259 | He makes a really funny face when it happens. | |
a50253cc | 1260 | But in the end, no individual scenes matter but the film as a whole. |
b349f79f | 1261 | Important actors in this film are: |
a50253cc | 1262 | - @b{Elijah Wood} :: He plays Frodo |
ac20fddf | 1263 | - @b{Sean Austin} :: He plays Sam, Frodo's friend. I still remember |
a50253cc | 1264 | him very well from his role as Mikey Walsh in the Goonies. |
4009494e GM |
1265 | @end group |
1266 | @end example | |
1267 | ||
a7808fba CD |
1268 | Org supports these lists by tuning filling and wrapping commands to |
1269 | deal with them correctly@footnote{Org only changes the filling | |
4009494e GM |
1270 | settings for Emacs. For XEmacs, you should use Kyle E. Jones' |
1271 | @file{filladapt.el}. To turn this on, put into @file{.emacs}: | |
b349f79f CD |
1272 | @code{(require 'filladapt)}}, and by exporting them properly |
1273 | (@pxref{Exporting}). | |
4009494e GM |
1274 | |
1275 | The following commands act on items when the cursor is in the first line | |
1276 | of an item (the line with the bullet or number). | |
1277 | ||
1278 | @table @kbd | |
1279 | @kindex @key{TAB} | |
1280 | @item @key{TAB} | |
1281 | Items can be folded just like headline levels if you set the variable | |
1282 | @code{org-cycle-include-plain-lists}. The level of an item is then | |
1283 | given by the indentation of the bullet/number. Items are always | |
1284 | subordinate to real headlines, however; the hierarchies remain | |
1285 | completely separated. | |
1286 | ||
1287 | If @code{org-cycle-include-plain-lists} has not been set, @key{TAB} | |
a7808fba | 1288 | fixes the indentation of the current line in a heuristic way. |
4009494e GM |
1289 | @kindex M-@key{RET} |
1290 | @item M-@key{RET} | |
a7808fba CD |
1291 | Insert new item at current level. With a prefix argument, force a new |
1292 | heading (@pxref{Structure editing}). If this command is used in the middle | |
1293 | of a line, the line is @emph{split} and the rest of the line becomes the new | |
1294 | item@footnote{If you do not want the line to be split, customize the variable | |
1295 | @code{org-M-RET-may-split-line}.}. If this command is executed in the | |
1296 | @emph{whitespace before a bullet or number}, the new item is created | |
1297 | @emph{before} the current item. If the command is executed in the white | |
1298 | space before the text that is part of an item but does not contain the | |
1299 | bullet, a bullet is added to the current line. | |
4009494e GM |
1300 | @kindex M-S-@key{RET} |
1301 | @item M-S-@key{RET} | |
1302 | Insert a new item with a checkbox (@pxref{Checkboxes}). | |
1303 | @kindex S-@key{up} | |
1304 | @kindex S-@key{down} | |
1305 | @item S-@key{up} | |
1306 | @itemx S-@key{down} | |
3da3282e CD |
1307 | @cindex shift-selection-mode |
1308 | Jump to the previous/next item in the current list, but only if | |
1309 | @code{org-support-shift-select} is off. If not, you can still use paragraph | |
1310 | jumping commands like @kbd{C-@key{up}} and @kbd{C-@key{down}} to quite | |
1311 | similar effect. | |
4009494e GM |
1312 | @kindex M-S-@key{up} |
1313 | @kindex M-S-@key{down} | |
1314 | @item M-S-@key{up} | |
1315 | @itemx M-S-@key{down} | |
1316 | Move the item including subitems up/down (swap with previous/next item | |
1317 | of same indentation). If the list is ordered, renumbering is | |
1318 | automatic. | |
1319 | @kindex M-S-@key{left} | |
1320 | @kindex M-S-@key{right} | |
1321 | @item M-S-@key{left} | |
1322 | @itemx M-S-@key{right} | |
1323 | Decrease/increase the indentation of the item, including subitems. | |
1324 | Initially, the item tree is selected based on current indentation. | |
1325 | When these commands are executed several times in direct succession, | |
1326 | the initially selected region is used, even if the new indentation | |
1327 | would imply a different hierarchy. To use the new hierarchy, break | |
1328 | the command chain with a cursor motion or so. | |
1329 | @kindex C-c C-c | |
1330 | @item C-c C-c | |
1331 | If there is a checkbox (@pxref{Checkboxes}) in the item line, toggle the | |
dbc28aaa CD |
1332 | state of the checkbox. If not, this command makes sure that all the |
1333 | items on this list level use the same bullet. Furthermore, if this is | |
a7808fba | 1334 | an ordered list, make sure the numbering is OK. |
4009494e GM |
1335 | @kindex C-c - |
1336 | @item C-c - | |
a7808fba CD |
1337 | Cycle the entire list level through the different itemize/enumerate bullets |
1338 | (@samp{-}, @samp{+}, @samp{*}, @samp{1.}, @samp{1)}). With a numeric prefix | |
1339 | argument N, select the Nth bullet from this list. If there is an active | |
1340 | region when calling this, all lines will be converted to list items. If the | |
1341 | first line already was a list item, any item markers will be removed from the | |
1342 | list. Finally, even without an active region, a normal line will be | |
1343 | converted into a list item. | |
64fb801f CD |
1344 | @kindex S-@key{left} |
1345 | @kindex S-@key{right} | |
1346 | @item S-@key{left}/@key{right} | |
3da3282e CD |
1347 | This command also cycles bullet styles when the cursor in on the bullet or |
1348 | anywhere in an item line, details depending on | |
1349 | @code{org-support-shift-select}. | |
4009494e GM |
1350 | @end table |
1351 | ||
55e0839d | 1352 | @node Drawers, Footnotes, Plain lists, Document Structure |
4009494e GM |
1353 | @section Drawers |
1354 | @cindex drawers | |
1355 | @cindex visibility cycling, drawers | |
1356 | ||
1357 | Sometimes you want to keep information associated with an entry, but you | |
a7808fba | 1358 | normally don't want to see it. For this, Org mode has @emph{drawers}. |
dbc28aaa CD |
1359 | Drawers need to be configured with the variable |
1360 | @code{org-drawers}@footnote{You can define drawers on a per-file basis | |
1361 | with a line like @code{#+DRAWERS: HIDDEN PROPERTIES STATE}}. Drawers | |
4009494e GM |
1362 | look like this: |
1363 | ||
1364 | @example | |
1365 | ** This is a headline | |
1366 | Still outside the drawer | |
1367 | :DRAWERNAME: | |
1368 | This is inside the drawer. | |
1369 | :END: | |
1370 | After the drawer. | |
1371 | @end example | |
1372 | ||
1373 | Visibility cycling (@pxref{Visibility cycling}) on the headline will | |
1374 | hide and show the entry, but keep the drawer collapsed to a single line. | |
1375 | In order to look inside the drawer, you need to move the cursor to the | |
a7808fba | 1376 | drawer line and press @key{TAB} there. Org mode uses a drawer for |
b349f79f CD |
1377 | storing properties (@pxref{Properties and Columns}), and another one for |
1378 | storing clock times (@pxref{Clocking work time}). | |
4009494e | 1379 | |
55e0839d CD |
1380 | @node Footnotes, Orgstruct mode, Drawers, Document Structure |
1381 | @section Footnotes | |
1382 | @cindex footnotes | |
1383 | ||
1384 | Org-mode supports the creation of footnotes. In contrast to the | |
1385 | @file{footnote.el} package, Org-mode's footnotes are designed for work on a | |
1386 | larger document, not only for one-off documents like emails. The basic | |
1387 | syntax is similar to the one used by @file{footnote.el}, i.e. a footnote is | |
1388 | defined in a paragraph that is started by a footnote marker in square | |
1389 | brackets in column 0, no indentation allowed. If you need a paragraph break | |
1390 | inside a footnote, use the LaTeX idiom @samp{\par}. The footnote reference | |
1391 | is simply the marker in square brackets, inside text. For example: | |
1392 | ||
1393 | @example | |
1394 | The Org homepage[fn:1] now looks a lot better than it used to. | |
1395 | ... | |
1396 | [fn:1] The link is: http://orgmode.org | |
1397 | @end example | |
1398 | ||
1399 | Org-mode extends the number-based syntax to @emph{named} footnotes and | |
1400 | optional inline definition. Using plain numbers as markers (as | |
1401 | @file{footnote.el} does) is supported for backward compatibility, but not | |
1402 | encouraged because of possible conflicts with LaTeX snippets @pxref{Embedded | |
1403 | LaTeX}. Here are the valid references: | |
1404 | ||
1405 | @table @code | |
1406 | @item [1] | |
1407 | A plain numeric footnote marker. | |
1408 | @item [fn:name] | |
1409 | A named footnote reference, where @code{name} is a unique label word, or, for | |
1410 | simplicity of automatic creation, a number. | |
1411 | @item [fn:: This is the inline definition of this footnote] | |
1412 | A LaTeX-like anonymous footnote where the definition is given directly at the | |
1413 | reference point. | |
1414 | @item [fn:name: a definition] | |
1415 | An inline definition of a footnote, which also specifies a name for the note. | |
867d4bb3 | 1416 | Since Org allows multiple references to the same note, you can then use |
55e0839d CD |
1417 | @code{[fn:name]} to create additional references. |
1418 | @end table | |
1419 | ||
1420 | Footnote labels can be created automatically, or you create names yourself. | |
1421 | This is handled by the variable @code{org-footnote-auto-label} and its | |
1422 | corresponding @code{#+STARTUP} keywords, see the docstring of that variable | |
1423 | for details. | |
1424 | ||
1425 | @noindent The following command handles footnotes: | |
1426 | ||
1427 | @table @kbd | |
1428 | @kindex C-c C-x f | |
1429 | @item C-c C-x f | |
1430 | The footnote action command. | |
1431 | ||
1432 | When the cursor is on a footnote reference, jump to the definition. When it | |
1433 | is at a definition, jump to the (first) reference. | |
1434 | ||
1435 | Otherwise, create a new footnote. Depending on the variable | |
1436 | @code{org-footnote-define-inline}@footnote{The corresponding in-buffer | |
1437 | setting is: @code{#+STARTUP: fninline} or @code{#+STARTUP: nofninline}}, the | |
1438 | definition will be placed right into the text as part of the reference, or | |
1439 | separately into the location determined by the variable | |
1440 | @code{org-footnote-section}. | |
1441 | ||
1442 | When this command is called with a prefix argument, a menu of additional | |
1443 | options is offered: | |
1444 | @example | |
1445 | s @r{Sort the footnote definitions by reference sequence. During editing,} | |
1446 | @r{Org makes no effort to sort footnote definitions into a particular} | |
1447 | @r{sequence. If you want them sorted, use this command, which will} | |
1448 | @r{also move entries according to @code{org-footnote-section}.} | |
1449 | n @r{Normalize the footnotes by collecting all definitions (including} | |
1450 | @r{inline definitions) into a special section, and then numbering them} | |
1451 | @r{in sequence. The references will then also be numbers. This is} | |
1452 | @r{meant to be the final step before finishing a document (e.g. sending} | |
1453 | @r{off an email). The exporters do this automatically, and so could} | |
1454 | @r{something like @code{message-send-hook}.} | |
1455 | d @r{Delete the footnote at point, and all definitions of and references} | |
1456 | @r{to it.} | |
1457 | @end example | |
1458 | @kindex C-c C-c | |
1459 | @item C-c C-c | |
1460 | If the cursor is on a footnote reference, jump to the definition. If it is a | |
1461 | the definition, jump back to the reference. When called at a footnote | |
1462 | location with a prefix argument, offer the same menu as @kbd{C-c C-x f}. | |
1463 | @kindex C-c C-o | |
1464 | @kindex mouse-1 | |
1465 | @kindex mouse-2 | |
1466 | @item C-c C-c @r{or} mouse-1/2 | |
1467 | Footnote labels are also links to the corresponding definition/reference, and | |
1468 | you can use the usual commands to follow these links. | |
1469 | @end table | |
1470 | ||
1471 | @node Orgstruct mode, , Footnotes, Document Structure | |
4009494e | 1472 | @section The Orgstruct minor mode |
a7808fba | 1473 | @cindex Orgstruct mode |
4009494e GM |
1474 | @cindex minor mode for structure editing |
1475 | ||
a7808fba | 1476 | If you like the intuitive way the Org mode structure editing and list |
4009494e | 1477 | formatting works, you might want to use these commands in other modes |
a7808fba | 1478 | like Text mode or Mail mode as well. The minor mode Orgstruct mode |
4009494e | 1479 | makes this possible. You can always toggle the mode with @kbd{M-x |
a7808fba | 1480 | orgstruct-mode}. To turn it on by default, for example in Mail mode, |
4009494e GM |
1481 | use |
1482 | ||
1483 | @lisp | |
1484 | (add-hook 'mail-mode-hook 'turn-on-orgstruct) | |
1485 | @end lisp | |
1486 | ||
1487 | When this mode is active and the cursor is on a line that looks to | |
a7808fba | 1488 | Org like a headline of the first line of a list item, most |
4009494e GM |
1489 | structure editing commands will work, even if the same keys normally |
1490 | have different functionality in the major mode you are using. If the | |
a7808fba | 1491 | cursor is not in one of those special lines, Orgstruct mode lurks |
4009494e GM |
1492 | silently in the shadow. |
1493 | ||
a7808fba | 1494 | @node Tables, Hyperlinks, Document Structure, Top |
4009494e GM |
1495 | @chapter Tables |
1496 | @cindex tables | |
1497 | @cindex editing tables | |
1498 | ||
a7808fba | 1499 | Org comes with a fast and intuitive table editor. Spreadsheet-like |
dbc28aaa | 1500 | calculations are supported in connection with the Emacs @file{calc} |
28a16a1b | 1501 | package |
dbc28aaa | 1502 | @ifinfo |
a7808fba | 1503 | (@pxref{Top,Calc,,Calc,Gnu Emacs Calculator Manual}). |
dbc28aaa CD |
1504 | @end ifinfo |
1505 | @ifnotinfo | |
1506 | (see the Emacs Calculator manual for more information about the Emacs | |
1507 | calculator). | |
1508 | @end ifnotinfo | |
4009494e GM |
1509 | |
1510 | @menu | |
1511 | * Built-in table editor:: Simple tables | |
28a16a1b | 1512 | * Narrow columns:: Stop wasting space in tables |
4009494e | 1513 | * Column groups:: Grouping to trigger vertical lines |
a7808fba CD |
1514 | * Orgtbl mode:: The table editor as minor mode |
1515 | * The spreadsheet:: The table editor has spreadsheet capabilities | |
864c9740 | 1516 | * Org Plot:: Plotting from org tables |
4009494e GM |
1517 | @end menu |
1518 | ||
1519 | @node Built-in table editor, Narrow columns, Tables, Tables | |
1520 | @section The built-in table editor | |
1521 | @cindex table editor, built-in | |
1522 | ||
a7808fba | 1523 | Org makes it easy to format tables in plain ASCII. Any line with |
4009494e GM |
1524 | @samp{|} as the first non-whitespace character is considered part of a |
1525 | table. @samp{|} is also the column separator. A table might look like | |
1526 | this: | |
1527 | ||
1528 | @example | |
1529 | | Name | Phone | Age | | |
1530 | |-------+-------+-----| | |
1531 | | Peter | 1234 | 17 | | |
1532 | | Anna | 4321 | 25 | | |
1533 | @end example | |
1534 | ||
1535 | A table is re-aligned automatically each time you press @key{TAB} or | |
1536 | @key{RET} or @kbd{C-c C-c} inside the table. @key{TAB} also moves to | |
1537 | the next field (@key{RET} to the next row) and creates new table rows | |
1538 | at the end of the table or before horizontal lines. The indentation | |
1539 | of the table is set by the first line. Any line starting with | |
1540 | @samp{|-} is considered as a horizontal separator line and will be | |
1541 | expanded on the next re-align to span the whole table width. So, to | |
1542 | create the above table, you would only type | |
1543 | ||
1544 | @example | |
1545 | |Name|Phone|Age| | |
1546 | |- | |
1547 | @end example | |
1548 | ||
1549 | @noindent and then press @key{TAB} to align the table and start filling in | |
55e0839d CD |
1550 | fields. Even faster would be to type @code{|Name|Phone|Age} followed by |
1551 | @kbd{C-c @key{RET}}. | |
4009494e | 1552 | |
a7808fba | 1553 | When typing text into a field, Org treats @key{DEL}, |
4009494e GM |
1554 | @key{Backspace}, and all character keys in a special way, so that |
1555 | inserting and deleting avoids shifting other fields. Also, when | |
1556 | typing @emph{immediately after the cursor was moved into a new field | |
1557 | with @kbd{@key{TAB}}, @kbd{S-@key{TAB}} or @kbd{@key{RET}}}, the | |
1558 | field is automatically made blank. If this behavior is too | |
1559 | unpredictable for you, configure the variables | |
1560 | @code{org-enable-table-editor} and @code{org-table-auto-blank-field}. | |
1561 | ||
1562 | @table @kbd | |
1563 | @tsubheading{Creation and conversion} | |
1564 | @kindex C-c | | |
1565 | @item C-c | | |
1566 | Convert the active region to table. If every line contains at least one | |
1567 | TAB character, the function assumes that the material is tab separated. | |
dbc28aaa | 1568 | If every line contains a comma, comma-separated values (CSV) are assumed. |
4009494e | 1569 | If not, lines are split at whitespace into fields. You can use a prefix |
dbc28aaa CD |
1570 | argument to force a specific separator: @kbd{C-u} forces CSV, @kbd{C-u |
1571 | C-u} forces TAB, and a numeric argument N indicates that at least N | |
a7808fba | 1572 | consecutive spaces, or alternatively a TAB will be the separator. |
28a16a1b | 1573 | @* |
a7808fba | 1574 | If there is no active region, this command creates an empty Org |
4009494e GM |
1575 | table. But it's easier just to start typing, like |
1576 | @kbd{|Name|Phone|Age @key{RET} |- @key{TAB}}. | |
1577 | ||
1578 | @tsubheading{Re-aligning and field motion} | |
1579 | @kindex C-c C-c | |
1580 | @item C-c C-c | |
1581 | Re-align the table without moving the cursor. | |
1582 | @c | |
1583 | @kindex @key{TAB} | |
1584 | @item @key{TAB} | |
1585 | Re-align the table, move to the next field. Creates a new row if | |
1586 | necessary. | |
1587 | @c | |
1588 | @kindex S-@key{TAB} | |
1589 | @item S-@key{TAB} | |
1590 | Re-align, move to previous field. | |
1591 | @c | |
1592 | @kindex @key{RET} | |
1593 | @item @key{RET} | |
1594 | Re-align the table and move down to next row. Creates a new row if | |
1595 | necessary. At the beginning or end of a line, @key{RET} still does | |
1596 | NEWLINE, so it can be used to split a table. | |
1597 | ||
1598 | @tsubheading{Column and row editing} | |
1599 | @kindex M-@key{left} | |
1600 | @kindex M-@key{right} | |
1601 | @item M-@key{left} | |
1602 | @itemx M-@key{right} | |
1603 | Move the current column left/right. | |
1604 | @c | |
1605 | @kindex M-S-@key{left} | |
1606 | @item M-S-@key{left} | |
1607 | Kill the current column. | |
1608 | @c | |
1609 | @kindex M-S-@key{right} | |
1610 | @item M-S-@key{right} | |
1611 | Insert a new column to the left of the cursor position. | |
1612 | @c | |
1613 | @kindex M-@key{up} | |
1614 | @kindex M-@key{down} | |
1615 | @item M-@key{up} | |
1616 | @itemx M-@key{down} | |
1617 | Move the current row up/down. | |
1618 | @c | |
1619 | @kindex M-S-@key{up} | |
1620 | @item M-S-@key{up} | |
1621 | Kill the current row or horizontal line. | |
1622 | @c | |
1623 | @kindex M-S-@key{down} | |
1624 | @item M-S-@key{down} | |
a7808fba CD |
1625 | Insert a new row above the current row. With a prefix argument, the line is |
1626 | created below the current one. | |
4009494e GM |
1627 | @c |
1628 | @kindex C-c - | |
1629 | @item C-c - | |
2096a1b6 | 1630 | Insert a horizontal line below current row. With a prefix argument, the line |
4009494e GM |
1631 | is created above the current line. |
1632 | @c | |
55e0839d CD |
1633 | @kindex C-c @key{RET} |
1634 | @item C-c @key{RET} | |
2096a1b6 | 1635 | Insert a horizontal line below current row, and move the cursor into the row |
55e0839d CD |
1636 | below that line. |
1637 | @c | |
4009494e GM |
1638 | @kindex C-c ^ |
1639 | @item C-c ^ | |
1640 | Sort the table lines in the region. The position of point indicates the | |
1641 | column to be used for sorting, and the range of lines is the range | |
1642 | between the nearest horizontal separator lines, or the entire table. If | |
1643 | point is before the first column, you will be prompted for the sorting | |
1644 | column. If there is an active region, the mark specifies the first line | |
1645 | and the sorting column, while point should be in the last line to be | |
1646 | included into the sorting. The command prompts for the sorting type | |
1647 | (alphabetically, numerically, or by time). When called with a prefix | |
1648 | argument, alphabetic sorting will be case-sensitive. | |
1649 | ||
1650 | @tsubheading{Regions} | |
1651 | @kindex C-c C-x M-w | |
1652 | @item C-c C-x M-w | |
1653 | Copy a rectangular region from a table to a special clipboard. Point | |
1654 | and mark determine edge fields of the rectangle. The process ignores | |
1655 | horizontal separator lines. | |
1656 | @c | |
1657 | @kindex C-c C-x C-w | |
1658 | @item C-c C-x C-w | |
1659 | Copy a rectangular region from a table to a special clipboard, and | |
1660 | blank all fields in the rectangle. So this is the ``cut'' operation. | |
1661 | @c | |
1662 | @kindex C-c C-x C-y | |
1663 | @item C-c C-x C-y | |
1664 | Paste a rectangular region into a table. | |
864c9740 | 1665 | The upper left corner ends up in the current field. All involved fields |
4009494e GM |
1666 | will be overwritten. If the rectangle does not fit into the present table, |
1667 | the table is enlarged as needed. The process ignores horizontal separator | |
1668 | lines. | |
1669 | @c | |
28a16a1b | 1670 | @kindex M-@key{RET} |
28a16a1b | 1671 | @itemx M-@kbd{RET} |
4009494e GM |
1672 | Wrap several fields in a column like a paragraph. If there is an active |
1673 | region, and both point and mark are in the same column, the text in the | |
a7808fba CD |
1674 | column is wrapped to minimum width for the given number of lines. A numeric |
1675 | prefix argument may be used to change the number of desired lines. If there | |
1676 | is no region, the current field is split at the cursor position and the text | |
1677 | fragment to the right of the cursor is prepended to the field one line | |
1678 | down. If there is no region, but you specify a prefix argument, the current | |
1679 | field is made blank, and the content is appended to the field above. | |
4009494e GM |
1680 | |
1681 | @tsubheading{Calculations} | |
1682 | @cindex formula, in tables | |
1683 | @cindex calculations, in tables | |
1684 | @cindex region, active | |
1685 | @cindex active region | |
a7808fba | 1686 | @cindex Transient mark mode |
4009494e GM |
1687 | @kindex C-c + |
1688 | @item C-c + | |
1689 | Sum the numbers in the current column, or in the rectangle defined by | |
1690 | the active region. The result is shown in the echo area and can | |
1691 | be inserted with @kbd{C-y}. | |
1692 | @c | |
1693 | @kindex S-@key{RET} | |
1694 | @item S-@key{RET} | |
864c9740 CD |
1695 | When current field is empty, copy from first non-empty field above. When not |
1696 | empty, copy current field down to next row and move cursor along with it. | |
1697 | Depending on the variable @code{org-table-copy-increment}, integer field | |
1698 | values will be incremented during copy. Integers that are too large will not | |
a50253cc | 1699 | be incremented. Also, a @code{0} prefix argument temporarily disables the |
864c9740 | 1700 | increment. This key is also used by CUA mode (@pxref{Cooperation}). |
4009494e GM |
1701 | |
1702 | @tsubheading{Miscellaneous} | |
1703 | @kindex C-c ` | |
1704 | @item C-c ` | |
1705 | Edit the current field in a separate window. This is useful for fields | |
1706 | that are not fully visible (@pxref{Narrow columns}). When called with a | |
1707 | @kbd{C-u} prefix, just make the full field visible, so that it can be | |
1708 | edited in place. | |
1709 | @c | |
4009494e GM |
1710 | @item M-x org-table-import |
1711 | Import a file as a table. The table should be TAB- or whitespace | |
dbc28aaa CD |
1712 | separated. Useful, for example, to import a spreadsheet table or data |
1713 | from a database, because these programs generally can write | |
1714 | TAB-separated text files. This command works by inserting the file into | |
1715 | the buffer and then converting the region to a table. Any prefix | |
1716 | argument is passed on to the converter, which uses it to determine the | |
1717 | separator. | |
4009494e | 1718 | @item C-c | |
a7808fba | 1719 | Tables can also be imported by pasting tabular text into the Org |
4009494e | 1720 | buffer, selecting the pasted text with @kbd{C-x C-x} and then using the |
44ce9197 | 1721 | @kbd{C-c |} command (see above under @i{Creation and conversion}). |
4009494e GM |
1722 | @c |
1723 | @item M-x org-table-export | |
a7808fba CD |
1724 | Export the table, by default as a TAB-separated file. Useful for data |
1725 | exchange with, for example, spreadsheet or database programs. The format | |
1726 | used to export the file can be configured in the variable | |
1727 | @code{org-table-export-default-format}. You may also use properties | |
1728 | @code{TABLE_EXPORT_FILE} and @code{TABLE_EXPORT_FORMAT} to specify the file | |
b349f79f CD |
1729 | name and the format for table export in a subtree. Org supports quite |
1730 | general formats for exported tables. The exporter format is the same as the | |
1731 | format used by Orgtbl radio tables, see @ref{Translator functions} for a | |
1732 | detailed description. | |
4009494e GM |
1733 | @end table |
1734 | ||
1735 | If you don't like the automatic table editor because it gets in your | |
1736 | way on lines which you would like to start with @samp{|}, you can turn | |
1737 | it off with | |
1738 | ||
1739 | @lisp | |
1740 | (setq org-enable-table-editor nil) | |
1741 | @end lisp | |
1742 | ||
1743 | @noindent Then the only table command that still works is | |
1744 | @kbd{C-c C-c} to do a manual re-align. | |
1745 | ||
1746 | @node Narrow columns, Column groups, Built-in table editor, Tables | |
1747 | @section Narrow columns | |
1748 | @cindex narrow columns in tables | |
1749 | ||
1750 | The width of columns is automatically determined by the table editor. | |
1751 | Sometimes a single field or a few fields need to carry more text, | |
1752 | leading to inconveniently wide columns. To limit@footnote{This feature | |
1753 | does not work on XEmacs.} the width of a column, one field anywhere in | |
1754 | the column may contain just the string @samp{<N>} where @samp{N} is an | |
1755 | integer specifying the width of the column in characters. The next | |
1756 | re-align will then set the width of this column to no more than this | |
1757 | value. | |
1758 | ||
1759 | @example | |
1760 | @group | |
1761 | |---+------------------------------| |---+--------| | |
1762 | | | | | | <6> | | |
1763 | | 1 | one | | 1 | one | | |
1764 | | 2 | two | ----\ | 2 | two | | |
1765 | | 3 | This is a long chunk of text | ----/ | 3 | This=> | | |
1766 | | 4 | four | | 4 | four | | |
1767 | |---+------------------------------| |---+--------| | |
1768 | @end group | |
1769 | @end example | |
1770 | ||
1771 | @noindent | |
1772 | Fields that are wider become clipped and end in the string @samp{=>}. | |
1773 | Note that the full text is still in the buffer, it is only invisible. | |
1774 | To see the full text, hold the mouse over the field - a tool-tip window | |
1775 | will show the full content. To edit such a field, use the command | |
1776 | @kbd{C-c `} (that is @kbd{C-c} followed by the backquote). This will | |
1777 | open a new window with the full field. Edit it and finish with @kbd{C-c | |
1778 | C-c}. | |
1779 | ||
1780 | When visiting a file containing a table with narrowed columns, the | |
1781 | necessary character hiding has not yet happened, and the table needs to | |
1782 | be aligned before it looks nice. Setting the option | |
1783 | @code{org-startup-align-all-tables} will realign all tables in a file | |
1784 | upon visiting, but also slow down startup. You can also set this option | |
1785 | on a per-file basis with: | |
1786 | ||
1787 | @example | |
1788 | #+STARTUP: align | |
1789 | #+STARTUP: noalign | |
1790 | @end example | |
1791 | ||
a7808fba | 1792 | @node Column groups, Orgtbl mode, Narrow columns, Tables |
4009494e GM |
1793 | @section Column groups |
1794 | @cindex grouping columns in tables | |
1795 | ||
a7808fba | 1796 | When Org exports tables, it does so by default without vertical |
4009494e GM |
1797 | lines because that is visually more satisfying in general. Occasionally |
1798 | however, vertical lines can be useful to structure a table into groups | |
1799 | of columns, much like horizontal lines can do for groups of rows. In | |
1800 | order to specify column groups, you can use a special row where the | |
1801 | first field contains only @samp{/}. The further fields can either | |
1802 | contain @samp{<} to indicate that this column should start a group, | |
1803 | @samp{>} to indicate the end of a column, or @samp{<>} to make a column | |
a7808fba | 1804 | a group of its own. Boundaries between column groups will upon export be |
4009494e GM |
1805 | marked with vertical lines. Here is an example: |
1806 | ||
1807 | @example | |
1808 | | | N | N^2 | N^3 | N^4 | sqrt(n) | sqrt[4](N) | | |
1809 | |---+----+-----+-----+-----+---------+------------| | |
1810 | | / | <> | < | | > | < | > | | |
1811 | | # | 1 | 1 | 1 | 1 | 1 | 1 | | |
1812 | | # | 2 | 4 | 8 | 16 | 1.4142 | 1.1892 | | |
1813 | | # | 3 | 9 | 27 | 81 | 1.7321 | 1.3161 | | |
1814 | |---+----+-----+-----+-----+---------+------------| | |
44ce9197 | 1815 | #+TBLFM: $3=$2^2::$4=$2^3::$5=$2^4::$6=sqrt($2)::$7=sqrt(sqrt(($2))) |
4009494e GM |
1816 | @end example |
1817 | ||
a7808fba | 1818 | It is also sufficient to just insert the column group starters after |
4009494e GM |
1819 | every vertical line you'd like to have: |
1820 | ||
1821 | @example | |
1822 | | N | N^2 | N^3 | N^4 | sqrt(n) | sqrt[4](N) | | |
1823 | |----+-----+-----+-----+---------+------------| | |
1824 | | / | < | | | < | | | |
1825 | @end example | |
1826 | ||
a7808fba | 1827 | @node Orgtbl mode, The spreadsheet, Column groups, Tables |
4009494e | 1828 | @section The Orgtbl minor mode |
a7808fba | 1829 | @cindex Orgtbl mode |
4009494e GM |
1830 | @cindex minor mode for tables |
1831 | ||
a7808fba CD |
1832 | If you like the intuitive way the Org table editor works, you |
1833 | might also want to use it in other modes like Text mode or Mail mode. | |
1834 | The minor mode Orgtbl mode makes this possible. You can always toggle | |
4009494e GM |
1835 | the mode with @kbd{M-x orgtbl-mode}. To turn it on by default, for |
1836 | example in mail mode, use | |
1837 | ||
1838 | @lisp | |
1839 | (add-hook 'mail-mode-hook 'turn-on-orgtbl) | |
1840 | @end lisp | |
1841 | ||
1842 | Furthermore, with some special setup, it is possible to maintain tables | |
a7808fba | 1843 | in arbitrary syntax with Orgtbl mode. For example, it is possible to |
4009494e | 1844 | construct La@TeX{} tables with the underlying ease and power of |
a7808fba | 1845 | Orgtbl mode, including spreadsheet capabilities. For details, see |
4009494e GM |
1846 | @ref{Tables in arbitrary syntax}. |
1847 | ||
864c9740 | 1848 | @node The spreadsheet, Org Plot, Orgtbl mode, Tables |
4009494e GM |
1849 | @section The spreadsheet |
1850 | @cindex calculations, in tables | |
1851 | @cindex spreadsheet capabilities | |
1852 | @cindex @file{calc} package | |
1853 | ||
1854 | The table editor makes use of the Emacs @file{calc} package to implement | |
1855 | spreadsheet-like capabilities. It can also evaluate Emacs Lisp forms to | |
a7808fba | 1856 | derive fields from other fields. While fully featured, Org's |
4009494e | 1857 | implementation is not identical to other spreadsheets. For example, |
a7808fba | 1858 | Org knows the concept of a @emph{column formula} that will be |
4009494e GM |
1859 | applied to all non-header fields in a column without having to copy the |
1860 | formula to each relevant field. | |
1861 | ||
1862 | @menu | |
1863 | * References:: How to refer to another field or range | |
1864 | * Formula syntax for Calc:: Using Calc to compute stuff | |
1865 | * Formula syntax for Lisp:: Writing formulas in Emacs Lisp | |
1866 | * Field formulas:: Formulas valid for a single field | |
1867 | * Column formulas:: Formulas valid for an entire column | |
1868 | * Editing and debugging formulas:: Fixing formulas | |
1869 | * Updating the table:: Recomputing all dependent fields | |
1870 | * Advanced features:: Field names, parameters and automatic recalc | |
1871 | @end menu | |
1872 | ||
1873 | @node References, Formula syntax for Calc, The spreadsheet, The spreadsheet | |
1874 | @subsection References | |
1875 | @cindex references | |
1876 | ||
1877 | To compute fields in the table from other fields, formulas must | |
a7808fba | 1878 | reference other fields or ranges. In Org, fields can be referenced |
4009494e GM |
1879 | by name, by absolute coordinates, and by relative coordinates. To find |
1880 | out what the coordinates of a field are, press @kbd{C-c ?} in that | |
1881 | field, or press @kbd{C-c @}} to toggle the display of a grid. | |
1882 | ||
1883 | @subsubheading Field references | |
1884 | @cindex field references | |
1885 | @cindex references, to fields | |
1886 | ||
1887 | Formulas can reference the value of another field in two ways. Like in | |
1888 | any other spreadsheet, you may reference fields with a letter/number | |
1889 | combination like @code{B3}, meaning the 2nd field in the 3rd row. | |
1890 | @c Such references are always fixed to that field, they don't change | |
1891 | @c when you copy and paste a formula to a different field. So | |
a7808fba | 1892 | @c Org's @code{B3} behaves like @code{$B$3} in other spreadsheets. |
4009494e GM |
1893 | |
1894 | @noindent | |
a7808fba | 1895 | Org also uses another, more general operator that looks like this: |
4009494e GM |
1896 | @example |
1897 | @@row$column | |
1898 | @end example | |
1899 | ||
1900 | @noindent | |
1901 | Column references can be absolute like @samp{1}, @samp{2},...@samp{N}, | |
73ef3bde | 1902 | or relative to the current column like @samp{+1} or @samp{-2}. |
4009494e GM |
1903 | |
1904 | The row specification only counts data lines and ignores horizontal | |
1905 | separator lines (hlines). You can use absolute row numbers | |
1906 | @samp{1}...@samp{N}, and row numbers relative to the current row like | |
1907 | @samp{+3} or @samp{-1}. Or specify the row relative to one of the | |
dbc28aaa CD |
1908 | hlines: @samp{I} refers to the first hline@footnote{Note that only |
1909 | hlines are counted that @emph{separate} table lines. If the table | |
1910 | starts with a hline above the header, it does not count.}, @samp{II} to | |
1911 | the second etc. @samp{-I} refers to the first such line above the | |
1912 | current line, @samp{+I} to the first such line below the current line. | |
1913 | You can also write @samp{III+2} which is the second data line after the | |
1914 | third hline in the table. Relative row numbers like @samp{-3} will not | |
1915 | cross hlines if the current line is too close to the hline. Instead, | |
1916 | the value directly at the hline is used. | |
4009494e GM |
1917 | |
1918 | @samp{0} refers to the current row and column. Also, if you omit | |
1919 | either the column or the row part of the reference, the current | |
28a16a1b | 1920 | row/column is implied. |
4009494e | 1921 | |
a7808fba | 1922 | Org's references with @emph{unsigned} numbers are fixed references |
4009494e GM |
1923 | in the sense that if you use the same reference in the formula for two |
1924 | different fields, the same field will be referenced each time. | |
a7808fba | 1925 | Org's references with @emph{signed} numbers are floating |
4009494e GM |
1926 | references because the same reference operator can reference different |
1927 | fields depending on the field being calculated by the formula. | |
1928 | ||
b6cb4cd5 | 1929 | As a special case references like @samp{$LR5} and @samp{$LR12} can be used to |
55e0839d CD |
1930 | refer in a stable way to the 5th and 12th field in the last row of the |
1931 | table. | |
b6cb4cd5 | 1932 | |
4009494e GM |
1933 | Here are a few examples: |
1934 | ||
1935 | @example | |
1936 | @@2$3 @r{2nd row, 3rd column} | |
1937 | C2 @r{same as previous} | |
1938 | $5 @r{column 5 in the current row} | |
1939 | E& @r{same as previous} | |
1940 | @@2 @r{current column, row 2} | |
1941 | @@-1$-3 @r{the field one row up, three columns to the left} | |
1942 | @@-I$2 @r{field just under hline above current row, column 2} | |
1943 | @end example | |
1944 | ||
1945 | @subsubheading Range references | |
1946 | @cindex range references | |
1947 | @cindex references, to ranges | |
1948 | ||
1949 | You may reference a rectangular range of fields by specifying two field | |
1950 | references connected by two dots @samp{..}. If both fields are in the | |
1951 | current row, you may simply use @samp{$2..$7}, but if at least one field | |
1952 | is in a different row, you need to use the general @code{@@row$column} | |
1953 | format at least for the first field (i.e the reference must start with | |
1954 | @samp{@@} in order to be interpreted correctly). Examples: | |
1955 | ||
1956 | @example | |
1957 | $1..$3 @r{First three fields in the current row.} | |
1958 | $P..$Q @r{Range, using column names (see under Advanced)} | |
1959 | @@2$1..@@4$3 @r{6 fields between these two fields.} | |
1960 | A2..C4 @r{Same as above.} | |
1961 | @@-1$-2..@@-1 @r{3 numbers from the column to the left, 2 up to current row} | |
1962 | @end example | |
1963 | ||
1964 | @noindent Range references return a vector of values that can be fed | |
1965 | into Calc vector functions. Empty fields in ranges are normally | |
1966 | suppressed, so that the vector contains only the non-empty fields (but | |
1967 | see the @samp{E} mode switch below). If there are no non-empty fields, | |
1968 | @samp{[0]} is returned to avoid syntax errors in formulas. | |
1969 | ||
1970 | @subsubheading Named references | |
1971 | @cindex named references | |
1972 | @cindex references, named | |
1973 | @cindex name, of column or field | |
1974 | @cindex constants, in calculations | |
1975 | ||
1976 | @samp{$name} is interpreted as the name of a column, parameter or | |
1977 | constant. Constants are defined globally through the variable | |
1978 | @code{org-table-formula-constants}, and locally (for the file) through a | |
1979 | line like | |
1980 | ||
1981 | @example | |
1982 | #+CONSTANTS: c=299792458. pi=3.14 eps=2.4e-6 | |
1983 | @end example | |
1984 | ||
1985 | @noindent | |
a7808fba | 1986 | Also properties (@pxref{Properties and Columns}) can be used as |
dbc28aaa CD |
1987 | constants in table formulas: For a property @samp{:Xyz:} use the name |
1988 | @samp{$PROP_Xyz}, and the property will be searched in the current | |
4009494e GM |
1989 | outline entry and in the hierarchy above it. If you have the |
1990 | @file{constants.el} package, it will also be used to resolve constants, | |
1991 | including natural constants like @samp{$h} for Planck's constant, and | |
1992 | units like @samp{$km} for kilometers@footnote{@file{Constant.el} can | |
1993 | supply the values of constants in two different unit systems, @code{SI} | |
1994 | and @code{cgs}. Which one is used depends on the value of the variable | |
1995 | @code{constants-unit-system}. You can use the @code{#+STARTUP} options | |
1996 | @code{constSI} and @code{constcgs} to set this value for the current | |
1997 | buffer.}. Column names and parameters can be specified in special table | |
1998 | lines. These are described below, see @ref{Advanced features}. All | |
1999 | names must start with a letter, and further consist of letters and | |
2000 | numbers. | |
2001 | ||
55e0839d CD |
2002 | @subsubheading Remote references |
2003 | @cindex remote references | |
2004 | @cindex references, remote | |
2005 | @cindex references, to a different table | |
2006 | @cindex name, of column or field | |
2007 | @cindex constants, in calculations | |
2008 | ||
2009 | You may also reference constants, fields and ranges from a different table, | |
2010 | either in the current file or even in a different file. The syntax is | |
2011 | ||
2012 | @example | |
2013 | remote(NAME-OR-ID,REF) | |
2014 | @end example | |
2015 | ||
2016 | @noindent | |
2017 | where NAME can be the name of a table in the current file as set by a | |
2018 | @code{#+TBLNAME: NAME} line before the table. It can also be the ID of an | |
2019 | entry, even in a different file, and the reference then refers to the first | |
2020 | table in that entry. REF is an absolute field or range reference as | |
2021 | described above, valid in the referenced table. | |
2022 | ||
4009494e GM |
2023 | @node Formula syntax for Calc, Formula syntax for Lisp, References, The spreadsheet |
2024 | @subsection Formula syntax for Calc | |
2025 | @cindex formula syntax, Calc | |
2026 | @cindex syntax, of formulas | |
2027 | ||
2028 | A formula can be any algebraic expression understood by the Emacs | |
2029 | @file{Calc} package. @b{Note that @file{calc} has the | |
2030 | non-standard convention that @samp{/} has lower precedence than | |
2031 | @samp{*}, so that @samp{a/b*c} is interpreted as @samp{a/(b*c)}.} Before | |
2032 | evaluation by @code{calc-eval} (@pxref{Calling Calc from | |
a7808fba | 2033 | Your Programs,calc-eval,Calling Calc from Your Lisp Programs,Calc,GNU |
4009494e | 2034 | Emacs Calc Manual}), |
a7808fba | 2035 | @c FIXME: The link to the Calc manual in HTML does not work. |
4009494e GM |
2036 | variable substitution takes place according to the rules described above. |
2037 | @cindex vectors, in table calculations | |
a7808fba | 2038 | The range vectors can be directly fed into the Calc vector functions |
4009494e GM |
2039 | like @samp{vmean} and @samp{vsum}. |
2040 | ||
2041 | @cindex format specifier | |
2042 | @cindex mode, for @file{calc} | |
2043 | A formula can contain an optional mode string after a semicolon. This | |
2044 | string consists of flags to influence Calc and other modes during | |
a7808fba | 2045 | execution. By default, Org uses the standard Calc modes (precision |
44ce9197 | 2046 | 12, angular units degrees, fraction and symbolic modes off). The display |
4009494e GM |
2047 | format, however, has been changed to @code{(float 5)} to keep tables |
2048 | compact. The default settings can be configured using the variable | |
2049 | @code{org-calc-default-modes}. | |
2050 | ||
2051 | @example | |
2052 | p20 @r{switch the internal precision to 20 digits} | |
2053 | n3 s3 e2 f4 @r{normal, scientific, engineering, or fixed display format} | |
2054 | D R @r{angle modes: degrees, radians} | |
2055 | F S @r{fraction and symbolic modes} | |
2056 | N @r{interpret all fields as numbers, use 0 for non-numbers} | |
2057 | T @r{force text interpretation} | |
2058 | E @r{keep empty fields in ranges} | |
2059 | @end example | |
2060 | ||
2061 | @noindent | |
2062 | In addition, you may provide a @code{printf} format specifier to | |
2063 | reformat the final result. A few examples: | |
2064 | ||
2065 | @example | |
2066 | $1+$2 @r{Sum of first and second field} | |
2067 | $1+$2;%.2f @r{Same, format result to two decimals} | |
2068 | exp($2)+exp($1) @r{Math functions can be used} | |
2069 | $0;%.1f @r{Reformat current cell to 1 decimal} | |
2070 | ($3-32)*5/9 @r{Degrees F -> C conversion} | |
2071 | $c/$1/$cm @r{Hz -> cm conversion, using @file{constants.el}} | |
2072 | tan($1);Dp3s1 @r{Compute in degrees, precision 3, display SCI 1} | |
2073 | sin($1);Dp3%.1e @r{Same, but use printf specifier for display} | |
2074 | vmean($2..$7) @r{Compute column range mean, using vector function} | |
2075 | vmean($2..$7);EN @r{Same, but treat empty fields as 0} | |
2076 | taylor($3,x=7,2) @r{taylor series of $3, at x=7, second degree} | |
2077 | @end example | |
2078 | ||
2079 | Calc also contains a complete set of logical operations. For example | |
2080 | ||
2081 | @example | |
2082 | if($1<20,teen,string("")) @r{``teen'' if age $1 less than 20, else empty} | |
2083 | @end example | |
2084 | ||
2085 | @node Formula syntax for Lisp, Field formulas, Formula syntax for Calc, The spreadsheet | |
2086 | @subsection Emacs Lisp forms as formulas | |
2087 | @cindex Lisp forms, as table formulas | |
2088 | ||
2089 | It is also possible to write a formula in Emacs Lisp; this can be useful | |
a50253cc | 2090 | for string manipulation and control structures, if Calc's |
4009494e GM |
2091 | functionality is not enough. If a formula starts with a single quote |
2092 | followed by an opening parenthesis, then it is evaluated as a lisp form. | |
2093 | The evaluation should return either a string or a number. Just as with | |
2094 | @file{calc} formulas, you can specify modes and a printf format after a | |
a7808fba | 2095 | semicolon. With Emacs Lisp forms, you need to be conscious about the way |
4009494e GM |
2096 | field references are interpolated into the form. By default, a |
2097 | reference will be interpolated as a Lisp string (in double quotes) | |
2098 | containing the field. If you provide the @samp{N} mode switch, all | |
2099 | referenced elements will be numbers (non-number fields will be zero) and | |
2100 | interpolated as Lisp numbers, without quotes. If you provide the | |
2101 | @samp{L} flag, all fields will be interpolated literally, without quotes. | |
2102 | I.e., if you want a reference to be interpreted as a string by the Lisp | |
a7808fba | 2103 | form, enclose the reference operator itself in double quotes, like |
4009494e GM |
2104 | @code{"$3"}. Ranges are inserted as space-separated fields, so you can |
2105 | embed them in list or vector syntax. A few examples, note how the | |
2106 | @samp{N} mode is used when we do computations in lisp. | |
2107 | ||
2108 | @example | |
2109 | @r{Swap the first two characters of the content of column 1} | |
2110 | '(concat (substring $1 1 2) (substring $1 0 1) (substring $1 2)) | |
2096a1b6 | 2111 | @r{Add columns 1 and 2, equivalent to Calc's @code{$1+$2}} |
4009494e GM |
2112 | '(+ $1 $2);N |
2113 | @r{Compute the sum of columns 1-4, like Calc's @code{vsum($1..$4)}} | |
2114 | '(apply '+ '($1..$4));N | |
2115 | @end example | |
2116 | ||
2117 | @node Field formulas, Column formulas, Formula syntax for Lisp, The spreadsheet | |
2118 | @subsection Field formulas | |
2119 | @cindex field formula | |
2120 | @cindex formula, for individual table field | |
2121 | ||
2122 | To assign a formula to a particular field, type it directly into the | |
2123 | field, preceded by @samp{:=}, for example @samp{:=$1+$2}. When you | |
2124 | press @key{TAB} or @key{RET} or @kbd{C-c C-c} with the cursor still in | |
2125 | the field, the formula will be stored as the formula for this field, | |
2126 | evaluated, and the current field replaced with the result. | |
2127 | ||
2128 | Formulas are stored in a special line starting with @samp{#+TBLFM:} | |
2129 | directly below the table. If you typed the equation in the 4th field of | |
2130 | the 3rd data line in the table, the formula will look like | |
2131 | @samp{@@3$4=$1+$2}. When inserting/deleting/swapping column and rows | |
2132 | with the appropriate commands, @i{absolute references} (but not relative | |
2133 | ones) in stored formulas are modified in order to still reference the | |
2134 | same field. Of cause this is not true if you edit the table structure | |
2135 | with normal editing commands - then you must fix the equations yourself. | |
b6cb4cd5 CD |
2136 | The left hand side of a formula may also be a named field (@pxref{Advanced |
2137 | features}), or a last-row reference like @samp{$LR3}. | |
4009494e GM |
2138 | |
2139 | Instead of typing an equation into the field, you may also use the | |
2140 | following command | |
2141 | ||
2142 | @table @kbd | |
2143 | @kindex C-u C-c = | |
2144 | @item C-u C-c = | |
2145 | Install a new formula for the current field. The command prompts for a | |
2146 | formula, with default taken from the @samp{#+TBLFM:} line, applies | |
2147 | it to the current field and stores it. | |
2148 | @end table | |
2149 | ||
2150 | @node Column formulas, Editing and debugging formulas, Field formulas, The spreadsheet | |
2151 | @subsection Column formulas | |
2152 | @cindex column formula | |
2153 | @cindex formula, for table column | |
2154 | ||
2155 | Often in a table, the same formula should be used for all fields in a | |
2156 | particular column. Instead of having to copy the formula to all fields | |
a7808fba | 2157 | in that column, Org allows to assign a single formula to an entire |
4009494e GM |
2158 | column. If the table contains horizontal separator hlines, everything |
2159 | before the first such line is considered part of the table @emph{header} | |
2160 | and will not be modified by column formulas. | |
2161 | ||
2162 | To assign a formula to a column, type it directly into any field in the | |
2163 | column, preceded by an equal sign, like @samp{=$1+$2}. When you press | |
2164 | @key{TAB} or @key{RET} or @kbd{C-c C-c} with the cursor still in the | |
2165 | field, the formula will be stored as the formula for the current column, | |
2166 | evaluated and the current field replaced with the result. If the field | |
2167 | contains only @samp{=}, the previously stored formula for this column is | |
a7808fba | 2168 | used. For each column, Org will only remember the most recently |
4009494e GM |
2169 | used formula. In the @samp{TBLFM:} line, column formulas will look like |
2170 | @samp{$4=$1+$2}. | |
2171 | ||
2172 | Instead of typing an equation into the field, you may also use the | |
2173 | following command: | |
2174 | ||
2175 | @table @kbd | |
2176 | @kindex C-c = | |
2177 | @item C-c = | |
a7808fba CD |
2178 | Install a new formula for the current column and replace current field with |
2179 | the result of the formula. The command prompts for a formula, with default | |
2180 | taken from the @samp{#+TBLFM} line, applies it to the current field and | |
2181 | stores it. With a numeric prefix argument(e.g. @kbd{C-5 C-c =}) the command | |
4009494e GM |
2182 | will apply it to that many consecutive fields in the current column. |
2183 | @end table | |
2184 | ||
4009494e | 2185 | @node Editing and debugging formulas, Updating the table, Column formulas, The spreadsheet |
a7808fba | 2186 | @subsection Editing and debugging formulas |
4009494e GM |
2187 | @cindex formula editing |
2188 | @cindex editing, of table formulas | |
2189 | ||
2190 | You can edit individual formulas in the minibuffer or directly in the | |
a7808fba CD |
2191 | field. Org can also prepare a special buffer with all active |
2192 | formulas of a table. When offering a formula for editing, Org | |
4009494e GM |
2193 | converts references to the standard format (like @code{B3} or @code{D&}) |
2194 | if possible. If you prefer to only work with the internal format (like | |
2195 | @code{@@3$2} or @code{$4}), configure the variable | |
2196 | @code{org-table-use-standard-references}. | |
2197 | ||
2198 | @table @kbd | |
2199 | @kindex C-c = | |
2200 | @kindex C-u C-c = | |
2201 | @item C-c = | |
2202 | @itemx C-u C-c = | |
2203 | Edit the formula associated with the current column/field in the | |
2204 | minibuffer. See @ref{Column formulas} and @ref{Field formulas}. | |
2205 | @kindex C-u C-u C-c = | |
2206 | @item C-u C-u C-c = | |
2207 | Re-insert the active formula (either a | |
2208 | field formula, or a column formula) into the current field, so that you | |
2209 | can edit it directly in the field. The advantage over editing in the | |
2210 | minibuffer is that you can use the command @kbd{C-c ?}. | |
2211 | @kindex C-c ? | |
2212 | @item C-c ? | |
2213 | While editing a formula in a table field, highlight the field(s) | |
2214 | referenced by the reference at the cursor position in the formula. | |
2215 | @kindex C-c @} | |
2216 | @item C-c @} | |
2217 | Toggle the display of row and column numbers for a table, using | |
2218 | overlays. These are updated each time the table is aligned, you can | |
2219 | force it with @kbd{C-c C-c}. | |
2220 | @kindex C-c @{ | |
2221 | @item C-c @{ | |
2222 | Toggle the formula debugger on and off. See below. | |
2223 | @kindex C-c ' | |
2224 | @item C-c ' | |
2225 | Edit all formulas for the current table in a special buffer, where the | |
2226 | formulas will be displayed one per line. If the current field has an | |
2227 | active formula, the cursor in the formula editor will mark it. | |
a7808fba | 2228 | While inside the special buffer, Org will automatically highlight |
4009494e GM |
2229 | any field or range reference at the cursor position. You may edit, |
2230 | remove and add formulas, and use the following commands: | |
2231 | @table @kbd | |
2232 | @kindex C-c C-c | |
2233 | @kindex C-x C-s | |
2234 | @item C-c C-c | |
2235 | @itemx C-x C-s | |
2236 | Exit the formula editor and store the modified formulas. With @kbd{C-u} | |
2237 | prefix, also apply the new formulas to the entire table. | |
2238 | @kindex C-c C-q | |
2239 | @item C-c C-q | |
2240 | Exit the formula editor without installing changes. | |
2241 | @kindex C-c C-r | |
2242 | @item C-c C-r | |
2243 | Toggle all references in the formula editor between standard (like | |
2244 | @code{B3}) and internal (like @code{@@3$2}). | |
2245 | @kindex @key{TAB} | |
2246 | @item @key{TAB} | |
2247 | Pretty-print or indent lisp formula at point. When in a line containing | |
2248 | a lisp formula, format the formula according to Emacs Lisp rules. | |
2249 | Another @key{TAB} collapses the formula back again. In the open | |
a7808fba | 2250 | formula, @key{TAB} re-indents just like in Emacs lisp mode. |
4009494e GM |
2251 | @kindex M-@key{TAB} |
2252 | @item M-@key{TAB} | |
a7808fba | 2253 | Complete Lisp symbols, just like in Emacs lisp mode. |
4009494e GM |
2254 | @kindex S-@key{up} |
2255 | @kindex S-@key{down} | |
2256 | @kindex S-@key{left} | |
2257 | @kindex S-@key{right} | |
2258 | @item S-@key{up}/@key{down}/@key{left}/@key{right} | |
2259 | Shift the reference at point. For example, if the reference is | |
2260 | @code{B3} and you press @kbd{S-@key{right}}, it will become @code{C3}. | |
2261 | This also works for relative references, and for hline references. | |
2262 | @kindex M-S-@key{up} | |
2263 | @kindex M-S-@key{down} | |
2264 | @item M-S-@key{up}/@key{down} | |
a7808fba | 2265 | Move the test line for column formulas in the Org buffer up and |
4009494e GM |
2266 | down. |
2267 | @kindex M-@key{up} | |
2268 | @kindex M-@key{down} | |
2269 | @item M-@key{up}/@key{down} | |
2270 | Scroll the window displaying the table. | |
2271 | @kindex C-c @} | |
2272 | @item C-c @} | |
2273 | Turn the coordinate grid in the table on and off. | |
2274 | @end table | |
2275 | @end table | |
2276 | ||
2277 | Making a table field blank does not remove the formula associated with | |
2278 | the field, because that is stored in a different line (the @samp{TBLFM} | |
2279 | line) - during the next recalculation the field will be filled again. | |
2280 | To remove a formula from a field, you have to give an empty reply when | |
2281 | prompted for the formula, or to edit the @samp{#+TBLFM} line. | |
2282 | ||
2283 | @kindex C-c C-c | |
2284 | You may edit the @samp{#+TBLFM} directly and re-apply the changed | |
2285 | equations with @kbd{C-c C-c} in that line, or with the normal | |
2286 | recalculation commands in the table. | |
2287 | ||
2288 | @subsubheading Debugging formulas | |
2289 | @cindex formula debugging | |
2290 | @cindex debugging, of table formulas | |
2291 | When the evaluation of a formula leads to an error, the field content | |
2292 | becomes the string @samp{#ERROR}. If you would like see what is going | |
2293 | on during variable substitution and calculation in order to find a bug, | |
2294 | turn on formula debugging in the @code{Tbl} menu and repeat the | |
2295 | calculation, for example by pressing @kbd{C-u C-u C-c = @key{RET}} in a | |
2296 | field. Detailed information will be displayed. | |
2297 | ||
2298 | @node Updating the table, Advanced features, Editing and debugging formulas, The spreadsheet | |
a7808fba | 2299 | @subsection Updating the table |
4009494e GM |
2300 | @cindex recomputing table fields |
2301 | @cindex updating, table | |
2302 | ||
2303 | Recalculation of a table is normally not automatic, but needs to be | |
2304 | triggered by a command. See @ref{Advanced features} for a way to make | |
2305 | recalculation at least semi-automatically. | |
2306 | ||
2307 | In order to recalculate a line of a table or the entire table, use the | |
2308 | following commands: | |
2309 | ||
2310 | @table @kbd | |
2311 | @kindex C-c * | |
2312 | @item C-c * | |
2313 | Recalculate the current row by first applying the stored column formulas | |
2314 | from left to right, and all field formulas in the current row. | |
2315 | @c | |
2316 | @kindex C-u C-c * | |
2317 | @item C-u C-c * | |
2318 | @kindex C-u C-c C-c | |
2319 | @itemx C-u C-c C-c | |
2320 | Recompute the entire table, line by line. Any lines before the first | |
2321 | hline are left alone, assuming that these are part of the table header. | |
2322 | @c | |
2323 | @kindex C-u C-u C-c * | |
2324 | @kindex C-u C-u C-c C-c | |
2325 | @item C-u C-u C-c * | |
2326 | @itemx C-u C-u C-c C-c | |
2327 | Iterate the table by recomputing it until no further changes occur. | |
2328 | This may be necessary if some computed fields use the value of other | |
2329 | fields that are computed @i{later} in the calculation sequence. | |
2330 | @end table | |
2331 | ||
2332 | @node Advanced features, , Updating the table, The spreadsheet | |
2333 | @subsection Advanced features | |
2334 | ||
2335 | If you want the recalculation of fields to happen automatically, or if | |
2336 | you want to be able to assign @i{names} to fields and columns, you need | |
2337 | to reserve the first column of the table for special marking characters. | |
2338 | @table @kbd | |
2339 | @kindex C-# | |
2340 | @item C-# | |
2341 | Rotate the calculation mark in first column through the states @samp{}, | |
864c9740 CD |
2342 | @samp{#}, @samp{*}, @samp{!}, @samp{$}. When there is an active region, |
2343 | change all marks in the region. | |
4009494e GM |
2344 | @end table |
2345 | ||
2346 | Here is an example of a table that collects exam results of students and | |
2347 | makes use of these features: | |
2348 | ||
2349 | @example | |
2350 | @group | |
2351 | |---+---------+--------+--------+--------+-------+------| | |
2352 | | | Student | Prob 1 | Prob 2 | Prob 3 | Total | Note | | |
2353 | |---+---------+--------+--------+--------+-------+------| | |
2354 | | ! | | P1 | P2 | P3 | Tot | | | |
2355 | | # | Maximum | 10 | 15 | 25 | 50 | 10.0 | | |
2356 | | ^ | | m1 | m2 | m3 | mt | | | |
2357 | |---+---------+--------+--------+--------+-------+------| | |
2358 | | # | Peter | 10 | 8 | 23 | 41 | 8.2 | | |
4009494e GM |
2359 | | # | Sam | 2 | 4 | 3 | 9 | 1.8 | |
2360 | |---+---------+--------+--------+--------+-------+------| | |
2361 | | | Average | | | | 29.7 | | | |
2362 | | ^ | | | | | at | | | |
2363 | | $ | max=50 | | | | | | | |
2364 | |---+---------+--------+--------+--------+-------+------| | |
2365 | #+TBLFM: $6=vsum($P1..$P3)::$7=10*$Tot/$max;%.1f::$at=vmean(@@-II..@@-I);%.1f | |
2366 | @end group | |
2367 | @end example | |
2368 | ||
2369 | @noindent @b{Important}: Please note that for these special tables, | |
2370 | recalculating the table with @kbd{C-u C-c *} will only affect rows that | |
2371 | are marked @samp{#} or @samp{*}, and fields that have a formula assigned | |
2372 | to the field itself. The column formulas are not applied in rows with | |
2373 | empty first field. | |
2374 | ||
2375 | @cindex marking characters, tables | |
2376 | The marking characters have the following meaning: | |
2377 | @table @samp | |
2378 | @item ! | |
2379 | The fields in this line define names for the columns, so that you may | |
2380 | refer to a column as @samp{$Tot} instead of @samp{$6}. | |
2381 | @item ^ | |
2382 | This row defines names for the fields @emph{above} the row. With such | |
2383 | a definition, any formula in the table may use @samp{$m1} to refer to | |
2384 | the value @samp{10}. Also, if you assign a formula to a names field, it | |
2385 | will be stored as @samp{$name=...}. | |
2386 | @item _ | |
2387 | Similar to @samp{^}, but defines names for the fields in the row | |
2388 | @emph{below}. | |
2389 | @item $ | |
2390 | Fields in this row can define @emph{parameters} for formulas. For | |
2391 | example, if a field in a @samp{$} row contains @samp{max=50}, then | |
2392 | formulas in this table can refer to the value 50 using @samp{$max}. | |
2393 | Parameters work exactly like constants, only that they can be defined on | |
2394 | a per-table basis. | |
2395 | @item # | |
2396 | Fields in this row are automatically recalculated when pressing | |
2397 | @key{TAB} or @key{RET} or @kbd{S-@key{TAB}} in this row. Also, this row | |
2398 | is selected for a global recalculation with @kbd{C-u C-c *}. Unmarked | |
2399 | lines will be left alone by this command. | |
2400 | @item * | |
2401 | Selects this line for global recalculation with @kbd{C-u C-c *}, but | |
2402 | not for automatic recalculation. Use this when automatic | |
2403 | recalculation slows down editing too much. | |
2404 | @item | |
2405 | Unmarked lines are exempt from recalculation with @kbd{C-u C-c *}. | |
2406 | All lines that should be recalculated should be marked with @samp{#} | |
2407 | or @samp{*}. | |
2408 | @item / | |
2409 | Do not export this line. Useful for lines that contain the narrowing | |
2410 | @samp{<N>} markers. | |
2411 | @end table | |
2412 | ||
2413 | Finally, just to whet your appetite on what can be done with the | |
2414 | fantastic @file{calc} package, here is a table that computes the Taylor | |
28a16a1b CD |
2415 | series of degree @code{n} at location @code{x} for a couple of |
2416 | functions. | |
4009494e GM |
2417 | |
2418 | @example | |
2419 | @group | |
2420 | |---+-------------+---+-----+--------------------------------------| | |
2421 | | | Func | n | x | Result | | |
2422 | |---+-------------+---+-----+--------------------------------------| | |
2423 | | # | exp(x) | 1 | x | 1 + x | | |
2424 | | # | exp(x) | 2 | x | 1 + x + x^2 / 2 | | |
2425 | | # | exp(x) | 3 | x | 1 + x + x^2 / 2 + x^3 / 6 | | |
2426 | | # | x^2+sqrt(x) | 2 | x=0 | x*(0.5 / 0) + x^2 (2 - 0.25 / 0) / 2 | | |
2427 | | # | x^2+sqrt(x) | 2 | x=1 | 2 + 2.5 x - 2.5 + 0.875 (x - 1)^2 | | |
2428 | | * | tan(x) | 3 | x | 0.0175 x + 1.77e-6 x^3 | | |
2429 | |---+-------------+---+-----+--------------------------------------| | |
2430 | #+TBLFM: $5=taylor($2,$4,$3);n3 | |
2431 | @end group | |
2432 | @end example | |
2433 | ||
864c9740 CD |
2434 | @page |
2435 | @node Org Plot, , The spreadsheet, Tables | |
2436 | @section Org Plot | |
2437 | @cindex graph, in tables | |
2438 | @cindex plot tables using gnuplot | |
2439 | ||
2440 | Org Plot can produce 2D and 3D graphs of information stored in org tables | |
71d35b24 CD |
2441 | using @file{Gnuplot} @uref{http://www.gnuplot.info/} and @file{gnuplot-mode} |
2442 | @uref{http://cars9.uchicago.edu/~ravel/software/gnuplot-mode.html}. To see | |
2443 | this in action ensure that you have both Gnuplot and Gnuplot-mode installed | |
2444 | on your system, then call @code{org-plot/gnuplot} on the following table. | |
864c9740 CD |
2445 | |
2446 | @example | |
2447 | @group | |
2448 | #+PLOT: title:"Citas" ind:1 deps:(3) type:2d with:histograms set:"yrange [0:]" | |
2449 | | Sede | Max cites | H-index | | |
2450 | |-----------+-----------+---------| | |
2451 | | Chile | 257.72 | 21.39 | | |
2452 | | Leeds | 165.77 | 19.68 | | |
2453 | | Sao Paolo | 71.00 | 11.50 | | |
2454 | | Stockholm | 134.19 | 14.33 | | |
2455 | | Morelia | 257.56 | 17.67 | | |
2456 | @end group | |
2457 | @end example | |
2458 | ||
2459 | Notice that Org Plot is smart enough to apply the tables headers as labels. | |
2460 | Further control over the labels, type, content, and appearance of plots can | |
2461 | be exercised through the @code{#+Plot:} lines preceding a table. See below | |
2462 | for a complete list of Org plot options. For more information and examples | |
71d35b24 | 2463 | see the org-plot tutorial at |
d324fa76 | 2464 | @uref{http://orgmode.org/worg/org-tutorials/org-plot.php}. |
864c9740 CD |
2465 | |
2466 | @subsubheading Plot Options | |
2467 | ||
2468 | @table @code | |
2469 | @item set | |
2470 | Specify any @file{gnuplot} option to be set when graphing. | |
2471 | ||
2472 | @item title | |
2473 | Specify the title of the plot. | |
2474 | ||
2475 | @item ind | |
2476 | Specify which column of the table to use as the @code{x} axis. | |
2477 | ||
2478 | @item deps | |
71d35b24 CD |
2479 | Specify the columns to graph as a lisp style list, surrounded by parenthesis |
2480 | and separated by spaces for example @code{dep:(3 4)} to graph the third and | |
2481 | fourth columns (defaults to graphing all other columns aside from the ind | |
2482 | column). | |
864c9740 CD |
2483 | |
2484 | @item type | |
2485 | Specify whether the plot will be @code{2d}, @code{3d}, or @code{grid}. | |
2486 | ||
2487 | @item with | |
2488 | Specify a @code{with} option to be inserted for every col being plotted | |
2489 | (e.g. @code{lines}, @code{points}, @code{boxes}, @code{impulses}, etc...). | |
2490 | Defaults to 'lines'. | |
2491 | ||
2492 | @item file | |
2493 | If you want to plot to a file specify the @code{"path/to/desired/output-file"}. | |
2494 | ||
2495 | @item labels | |
2496 | List of labels to be used for the deps (defaults to column headers if they | |
2497 | exist). | |
2498 | ||
2499 | @item line | |
2500 | Specify an entire line to be inserted in the gnuplot script. | |
2501 | ||
2502 | @item map | |
2503 | When plotting @code{3d} or @code{grid} types, set this to @code{t} to graph a | |
2504 | flat mapping rather than a @code{3d} slope. | |
2505 | ||
e45e3595 CD |
2506 | @item timefmt |
2507 | Specify format of org-mode timestamps as they will be parsed by gnuplot. | |
2508 | Defaults to '%Y-%m-%d-%H:%M:%S'. | |
2509 | ||
864c9740 CD |
2510 | @item script |
2511 | If you want total control you can specify a script file (place the file name | |
2512 | between double quotes) which will be used to plot. Before plotting, every | |
2513 | instance of @code{$datafile} in the specified script will be replaced with | |
2514 | the path to the generated data file. Note even if you set this option you | |
2515 | may still want to specify the plot type, as that can impact the content of | |
2516 | the data file. | |
2517 | @end table | |
2518 | ||
a7808fba | 2519 | @node Hyperlinks, TODO Items, Tables, Top |
4009494e GM |
2520 | @chapter Hyperlinks |
2521 | @cindex hyperlinks | |
2522 | ||
a7808fba | 2523 | Like HTML, Org provides links inside a file, external links to |
dbc28aaa | 2524 | other files, Usenet articles, emails, and much more. |
4009494e GM |
2525 | |
2526 | @menu | |
a7808fba | 2527 | * Link format:: How links in Org are formatted |
4009494e GM |
2528 | * Internal links:: Links to other places in the current file |
2529 | * External links:: URL-like links to the world | |
2530 | * Handling links:: Creating, inserting and following | |
a7808fba | 2531 | * Using links outside Org:: Linking from my C source code? |
4009494e GM |
2532 | * Link abbreviations:: Shortcuts for writing complex links |
2533 | * Search options:: Linking to a specific location | |
2534 | * Custom searches:: When the default search is not enough | |
4009494e GM |
2535 | @end menu |
2536 | ||
2537 | @node Link format, Internal links, Hyperlinks, Hyperlinks | |
2538 | @section Link format | |
2539 | @cindex link format | |
2540 | @cindex format, of links | |
2541 | ||
a7808fba | 2542 | Org will recognize plain URL-like links and activate them as |
4009494e GM |
2543 | clickable links. The general link format, however, looks like this: |
2544 | ||
2545 | @example | |
28a16a1b | 2546 | [[link][description]] @r{or alternatively} [[link]] |
4009494e GM |
2547 | @end example |
2548 | ||
a7808fba | 2549 | Once a link in the buffer is complete (all brackets present), Org |
4009494e GM |
2550 | will change the display so that @samp{description} is displayed instead |
2551 | of @samp{[[link][description]]} and @samp{link} is displayed instead of | |
2552 | @samp{[[link]]}. Links will be highlighted in the face @code{org-link}, | |
2553 | which by default is an underlined face. You can directly edit the | |
2554 | visible part of a link. Note that this can be either the @samp{link} | |
2555 | part (if there is no description) or the @samp{description} part. To | |
2556 | edit also the invisible @samp{link} part, use @kbd{C-c C-l} with the | |
2557 | cursor on the link. | |
2558 | ||
2559 | If you place the cursor at the beginning or just behind the end of the | |
2560 | displayed text and press @key{BACKSPACE}, you will remove the | |
2561 | (invisible) bracket at that location. This makes the link incomplete | |
2562 | and the internals are again displayed as plain text. Inserting the | |
2563 | missing bracket hides the link internals again. To show the | |
2564 | internal structure of all links, use the menu entry | |
2565 | @code{Org->Hyperlinks->Literal links}. | |
2566 | ||
2567 | @node Internal links, External links, Link format, Hyperlinks | |
2568 | @section Internal links | |
2569 | @cindex internal links | |
2570 | @cindex links, internal | |
2571 | @cindex targets, for links | |
2572 | ||
2573 | If the link does not look like a URL, it is considered to be internal in | |
2574 | the current file. Links such as @samp{[[My Target]]} or @samp{[[My | |
2575 | Target][Find my target]]} lead to a text search in the current file. | |
2576 | The link can be followed with @kbd{C-c C-o} when the cursor is on the | |
2577 | link, or with a mouse click (@pxref{Handling links}). The preferred | |
2578 | match for such a link is a dedicated target: the same string in double | |
2579 | angular brackets. Targets may be located anywhere; sometimes it is | |
2580 | convenient to put them into a comment line. For example | |
2581 | ||
2582 | @example | |
2583 | # <<My Target>> | |
2584 | @end example | |
2585 | ||
2586 | @noindent In HTML export (@pxref{HTML export}), such targets will become | |
64fb801f CD |
2587 | named anchors for direct access through @samp{http} links@footnote{Note that |
2588 | text before the first headline is usually not exported, so the first such | |
2589 | target should be after the first headline, or in the line directly before the | |
2590 | first headline.}. | |
4009494e | 2591 | |
a7808fba | 2592 | If no dedicated target exists, Org will search for the words in the |
4009494e GM |
2593 | link. In the above example the search would be for @samp{my target}. |
2594 | Links starting with a star like @samp{*My Target} restrict the search to | |
a7808fba | 2595 | headlines. When searching, Org mode will first try an exact match, but |
4009494e GM |
2596 | then move on to more and more lenient searches. For example, the link |
2597 | @samp{[[*My Targets]]} will find any of the following: | |
2598 | ||
2599 | @example | |
2600 | ** My targets | |
2601 | ** TODO my targets are bright | |
2602 | ** my 20 targets are | |
2603 | @end example | |
2604 | ||
2605 | To insert a link targeting a headline, in-buffer completion can be used. | |
2606 | Just type a star followed by a few optional letters into the buffer and | |
2607 | press @kbd{M-@key{TAB}}. All headlines in the current buffer will be | |
2608 | offered as completions. @xref{Handling links}, for more commands | |
2609 | creating links. | |
2610 | ||
a7808fba | 2611 | Following a link pushes a mark onto Org's own mark ring. You can |
4009494e GM |
2612 | return to the previous position with @kbd{C-c &}. Using this command |
2613 | several times in direct succession goes back to positions recorded | |
2614 | earlier. | |
2615 | ||
2616 | @menu | |
a7808fba | 2617 | * Radio targets:: Make targets trigger links in plain text |
4009494e GM |
2618 | @end menu |
2619 | ||
2620 | @node Radio targets, , Internal links, Internal links | |
2621 | @subsection Radio targets | |
2622 | @cindex radio targets | |
2623 | @cindex targets, radio | |
2624 | @cindex links, radio targets | |
2625 | ||
a7808fba | 2626 | Org can automatically turn any occurrences of certain target names |
4009494e GM |
2627 | in normal text into a link. So without explicitly creating a link, the |
2628 | text connects to the target radioing its position. Radio targets are | |
2629 | enclosed by triple angular brackets. For example, a target @samp{<<<My | |
2630 | Target>>>} causes each occurrence of @samp{my target} in normal text to | |
a7808fba | 2631 | become activated as a link. The Org file is scanned automatically |
4009494e GM |
2632 | for radio targets only when the file is first loaded into Emacs. To |
2633 | update the target list during editing, press @kbd{C-c C-c} with the | |
2634 | cursor on or at a target. | |
2635 | ||
2636 | @node External links, Handling links, Internal links, Hyperlinks | |
2637 | @section External links | |
2638 | @cindex links, external | |
2639 | @cindex external links | |
2640 | @cindex links, external | |
a7808fba | 2641 | @cindex Gnus links |
4009494e | 2642 | @cindex BBDB links |
28a16a1b | 2643 | @cindex IRC links |
4009494e GM |
2644 | @cindex URL links |
2645 | @cindex file links | |
2646 | @cindex VM links | |
2647 | @cindex RMAIL links | |
2648 | @cindex WANDERLUST links | |
2649 | @cindex MH-E links | |
2650 | @cindex USENET links | |
2651 | @cindex SHELL links | |
2652 | @cindex Info links | |
2653 | @cindex elisp links | |
2654 | ||
a7808fba | 2655 | Org supports links to files, websites, Usenet and email messages, |
28a16a1b CD |
2656 | BBDB database entries and links to both IRC conversations and their |
2657 | logs. External links are URL-like locators. They start with a short | |
2658 | identifying string followed by a colon. There can be no space after | |
2659 | the colon. The following list shows examples for each link type. | |
4009494e GM |
2660 | |
2661 | @example | |
a7808fba | 2662 | http://www.astro.uva.nl/~dominik @r{on the web} |
4009494e | 2663 | file:/home/dominik/images/jupiter.jpg @r{file, absolute path} |
44ce9197 | 2664 | /home/dominik/images/jupiter.jpg @r{same as above} |
4009494e | 2665 | file:papers/last.pdf @r{file, relative path} |
44ce9197 | 2666 | ./papers/last.pdf @r{same as above} |
55e0839d CD |
2667 | file:projects.org @r{another org file} |
2668 | file:projects.org::some words @r{text search in org file} | |
2669 | file:projects.org::*task title @r{heading search in org file} | |
2670 | id:B7423F4D-2E8A-471B-8810-C40F074717E9 @r{Link to heading by ID} | |
4009494e | 2671 | news:comp.emacs @r{Usenet link} |
55e0839d | 2672 | mailto:adent@@galaxy.net @r{Mail link} |
4009494e GM |
2673 | vm:folder @r{VM folder link} |
2674 | vm:folder#id @r{VM message link} | |
55e0839d | 2675 | vm://myself@@some.where.org/folder#id @r{VM on remote machine} |
4009494e GM |
2676 | wl:folder @r{WANDERLUST folder link} |
2677 | wl:folder#id @r{WANDERLUST message link} | |
2678 | mhe:folder @r{MH-E folder link} | |
2679 | mhe:folder#id @r{MH-E message link} | |
2680 | rmail:folder @r{RMAIL folder link} | |
2681 | rmail:folder#id @r{RMAIL message link} | |
a7808fba CD |
2682 | gnus:group @r{Gnus group link} |
2683 | gnus:group#id @r{Gnus article link} | |
64fb801f | 2684 | bbdb:R.*Stallman @r{BBDB link (with regexp)} |
28a16a1b | 2685 | irc:/irc.com/#emacs/bob @r{IRC link} |
4009494e | 2686 | shell:ls *.org @r{A shell command} |
64fb801f CD |
2687 | elisp:org-agenda @r{Interactive elisp command} |
2688 | elisp:(find-file-other-frame "Elisp.org") @r{Elisp form to evaluate} | |
4009494e GM |
2689 | @end example |
2690 | ||
2691 | A link should be enclosed in double brackets and may contain a | |
a7808fba | 2692 | descriptive text to be displayed instead of the URL (@pxref{Link |
4009494e GM |
2693 | format}), for example: |
2694 | ||
2695 | @example | |
2696 | [[http://www.gnu.org/software/emacs/][GNU Emacs]] | |
2697 | @end example | |
2698 | ||
2699 | @noindent | |
2700 | If the description is a file name or URL that points to an image, HTML | |
2701 | export (@pxref{HTML export}) will inline the image as a clickable | |
2702 | button. If there is no description at all and the link points to an | |
2703 | image, | |
2704 | that image will be inlined into the exported HTML file. | |
2705 | ||
2706 | @cindex angular brackets, around links | |
2707 | @cindex plain text external links | |
a7808fba | 2708 | Org also finds external links in the normal text and activates them |
4009494e GM |
2709 | as links. If spaces must be part of the link (for example in |
2710 | @samp{bbdb:Richard Stallman}), or if you need to remove ambiguities | |
2711 | about the end of the link, enclose them in angular brackets. | |
2712 | ||
a7808fba | 2713 | @node Handling links, Using links outside Org, External links, Hyperlinks |
4009494e GM |
2714 | @section Handling links |
2715 | @cindex links, handling | |
2716 | ||
a7808fba CD |
2717 | Org provides methods to create a link in the correct syntax, to |
2718 | insert it into an Org file, and to follow the link. | |
4009494e GM |
2719 | |
2720 | @table @kbd | |
2721 | @kindex C-c l | |
2722 | @cindex storing links | |
2723 | @item C-c l | |
55e0839d CD |
2724 | Store a link to the current location. This is a @emph{global} command (you |
2725 | must create the key binding yourself) which can be used in any buffer to | |
2726 | create a link. The link will be stored for later insertion into an Org | |
2727 | buffer (see below). | |
2728 | ||
2729 | For Org files, if there is a @samp{<<target>>} at the cursor, the link points | |
2730 | to the target. Otherwise it points to the current headline, either by text | |
2731 | (unsafe), or, if @file{org-id.el} is loaded and @code{org-link-to-org-use-id} | |
2732 | is set, by ID property. | |
2733 | ||
2734 | For VM, Rmail, Wanderlust, MH-E, Gnus and BBDB buffers, the link will | |
2735 | indicate the current article/entry. For W3 and W3M buffers, the link goes to | |
2736 | the current URL. For IRC links, if you set the variable | |
2737 | @code{org-irc-link-to-logs} to non-nil then @kbd{C-c l} will store a | |
67df9cfb | 2738 | @samp{file:/} style link to the relevant point in the logs for the current |
2096a1b6 | 2739 | conversation. Otherwise an @samp{irc:/} style link to the user/channel/server |
867d4bb3 | 2740 | under the point will be stored. |
55e0839d CD |
2741 | |
2742 | For any other files, the link will point to the file, with a search string | |
2743 | (@pxref{Search options}) pointing to the contents of the current line. If | |
2744 | there is an active region, the selected words will form the basis of the | |
2745 | search string. If the automatically created link is not working correctly or | |
2746 | accurately enough, you can write custom functions to select the search string | |
2747 | and to do the search for particular file types - see @ref{Custom searches}. | |
2748 | The key binding @kbd{C-c l} is only a suggestion - see @ref{Installation}. | |
4009494e GM |
2749 | @c |
2750 | @kindex C-c C-l | |
2751 | @cindex link completion | |
2752 | @cindex completion, of links | |
2753 | @cindex inserting links | |
2754 | @item C-c C-l | |
a7808fba CD |
2755 | Insert a link. This prompts for a link to be inserted into the buffer. You |
2756 | can just type a link, using text for an internal link, or one of the link | |
2757 | type prefixes mentioned in the examples above. All links stored during the | |
2758 | current session are part of the history for this prompt, so you can access | |
2759 | them with @key{up} and @key{down} (or @kbd{M-p/n}). Completion, on the other | |
2760 | hand, will help you to insert valid link prefixes like @samp{http:} or | |
2761 | @samp{ftp:}, including the prefixes defined through link abbreviations | |
2762 | (@pxref{Link abbreviations}). The link will be inserted into the | |
2763 | buffer@footnote{After insertion of a stored link, the link will be removed | |
2764 | from the list of stored links. To keep it in the list later use, use a | |
2765 | triple @kbd{C-u} prefix argument to @kbd{C-c C-l}, or configure the option | |
2766 | @code{org-keep-stored-link-after-insertion}.}, along with a descriptive text. | |
2767 | If some text was selected when this command is called, the selected text | |
2768 | becomes the default description.@* Note that you don't have to use this | |
2769 | command to insert a link. Links in Org are plain text, and you can type | |
2770 | or paste them straight into the buffer. By using this command, the links are | |
2771 | automatically enclosed in double brackets, and you will be asked for the | |
2772 | optional descriptive text. | |
4009494e GM |
2773 | @c |
2774 | @c If the link is a @samp{file:} link and | |
2775 | @c the linked file is located in the same directory as the current file or | |
2776 | @c a subdirectory of it, the path of the file will be inserted relative to | |
2777 | @c the current directory. | |
2778 | @c | |
2779 | @kindex C-u C-c C-l | |
2780 | @cindex file name completion | |
2781 | @cindex completion, of file names | |
2782 | @item C-u C-c C-l | |
2783 | When @kbd{C-c C-l} is called with a @kbd{C-u} prefix argument, a link to | |
2784 | a file will be inserted and you may use file name completion to select | |
2785 | the name of the file. The path to the file is inserted relative to the | |
2786 | directory of the current org file, if the linked file is in the current | |
a7808fba | 2787 | directory or in a sub-directory of it, or if the path is written relative |
4009494e GM |
2788 | to the current directory using @samp{../}. Otherwise an absolute path |
2789 | is used, if possible with @samp{~/} for your home directory. You can | |
2790 | force an absolute path with two @kbd{C-u} prefixes. | |
2791 | @c | |
2792 | @item C-c C-l @r{(with cursor on existing link)} | |
2793 | When the cursor is on an existing link, @kbd{C-c C-l} allows you to edit the | |
2794 | link and description parts of the link. | |
2795 | @c | |
2796 | @cindex following links | |
2797 | @kindex C-c C-o | |
55033558 | 2798 | @kindex RET |
cc6dbcb7 | 2799 | @item C-c C-o |
4009494e | 2800 | Open link at point. This will launch a web browser for URLs (using |
864c9740 CD |
2801 | @command{browse-url-at-point}), run VM/MH-E/Wanderlust/Rmail/Gnus/BBDB for |
2802 | the corresponding links, and execute the command in a shell link. When the | |
2803 | cursor is on an internal link, this commands runs the corresponding search. | |
2804 | When the cursor is on a TAG list in a headline, it creates the corresponding | |
2805 | TAGS view. If the cursor is on a time stamp, it compiles the agenda for that | |
2806 | date. Furthermore, it will visit text and remote files in @samp{file:} links | |
2807 | with Emacs and select a suitable application for local non-text files. | |
2808 | Classification of files is based on file extension only. See option | |
2809 | @code{org-file-apps}. If you want to override the default application and | |
e45e3595 CD |
2810 | visit the file with Emacs, use a @kbd{C-u} prefix. If you want to avoid |
2811 | opening in Emacs, use a @kbd{C-u C-u} prefix. | |
4009494e GM |
2812 | @c |
2813 | @kindex mouse-2 | |
2814 | @kindex mouse-1 | |
2815 | @item mouse-2 | |
2816 | @itemx mouse-1 | |
2817 | On links, @kbd{mouse-2} will open the link just as @kbd{C-c C-o} | |
2818 | would. Under Emacs 22, also @kbd{mouse-1} will follow a link. | |
2819 | @c | |
2820 | @kindex mouse-3 | |
2821 | @item mouse-3 | |
2822 | Like @kbd{mouse-2}, but force file links to be opened with Emacs, and | |
2823 | internal links to be displayed in another window@footnote{See the | |
2824 | variable @code{org-display-internal-link-with-indirect-buffer}}. | |
2825 | @c | |
2826 | @cindex mark ring | |
2827 | @kindex C-c % | |
2828 | @item C-c % | |
2829 | Push the current position onto the mark ring, to be able to return | |
2830 | easily. Commands following an internal link do this automatically. | |
2831 | @c | |
2832 | @cindex links, returning to | |
2833 | @kindex C-c & | |
2834 | @item C-c & | |
2835 | Jump back to a recorded position. A position is recorded by the | |
2836 | commands following internal links, and by @kbd{C-c %}. Using this | |
2837 | command several times in direct succession moves through a ring of | |
2838 | previously recorded positions. | |
2839 | @c | |
2840 | @kindex C-c C-x C-n | |
2841 | @kindex C-c C-x C-p | |
2842 | @cindex links, finding next/previous | |
2843 | @item C-c C-x C-n | |
2844 | @itemx C-c C-x C-p | |
2845 | Move forward/backward to the next link in the buffer. At the limit of | |
2846 | the buffer, the search fails once, and then wraps around. The key | |
2847 | bindings for this are really too long, you might want to bind this also | |
2848 | to @kbd{C-n} and @kbd{C-p} | |
2849 | @lisp | |
2850 | (add-hook 'org-load-hook | |
2851 | (lambda () | |
2852 | (define-key 'org-mode-map "\C-n" 'org-next-link) | |
2853 | (define-key 'org-mode-map "\C-p" 'org-previous-link))) | |
2854 | @end lisp | |
2855 | @end table | |
2856 | ||
a7808fba CD |
2857 | @node Using links outside Org, Link abbreviations, Handling links, Hyperlinks |
2858 | @section Using links outside Org | |
4009494e | 2859 | |
a7808fba CD |
2860 | You can insert and follow links that have Org syntax not only in |
2861 | Org, but in any Emacs buffer. For this, you should create two | |
4009494e GM |
2862 | global commands, like this (please select suitable global keys |
2863 | yourself): | |
2864 | ||
2865 | @lisp | |
2866 | (global-set-key "\C-c L" 'org-insert-link-global) | |
2867 | (global-set-key "\C-c o" 'org-open-at-point-global) | |
2868 | @end lisp | |
2869 | ||
a7808fba | 2870 | @node Link abbreviations, Search options, Using links outside Org, Hyperlinks |
4009494e GM |
2871 | @section Link abbreviations |
2872 | @cindex link abbreviations | |
2873 | @cindex abbreviation, links | |
2874 | ||
2875 | Long URLs can be cumbersome to type, and often many similar links are | |
2876 | needed in a document. For this you can use link abbreviations. An | |
2877 | abbreviated link looks like this | |
2878 | ||
2879 | @example | |
2880 | [[linkword:tag][description]] | |
2881 | @end example | |
2882 | ||
2883 | @noindent | |
2884 | where the tag is optional. Such abbreviations are resolved according to | |
2885 | the information in the variable @code{org-link-abbrev-alist} that | |
2886 | relates the linkwords to replacement text. Here is an example: | |
2887 | ||
2888 | @lisp | |
2889 | @group | |
2890 | (setq org-link-abbrev-alist | |
2891 | '(("bugzilla" . "http://10.1.2.9/bugzilla/show_bug.cgi?id=") | |
2892 | ("google" . "http://www.google.com/search?q=") | |
2893 | ("ads" . "http://adsabs.harvard.edu/cgi-bin/ | |
2894 | nph-abs_connect?author=%s&db_key=AST"))) | |
2895 | @end group | |
2896 | @end lisp | |
2897 | ||
2898 | If the replacement text contains the string @samp{%s}, it will be | |
2899 | replaced with the tag. Otherwise the tag will be appended to the string | |
2900 | in order to create the link. You may also specify a function that will | |
2901 | be called with the tag as the only argument to create the link. | |
2902 | ||
2903 | With the above setting, you could link to a specific bug with | |
2904 | @code{[[bugzilla:129]]}, search the web for @samp{OrgMode} with | |
a7808fba | 2905 | @code{[[google:OrgMode]]} and find out what the Org author is |
4009494e GM |
2906 | doing besides Emacs hacking with @code{[[ads:Dominik,C]]}. |
2907 | ||
a7808fba | 2908 | If you need special abbreviations just for a single Org buffer, you |
4009494e GM |
2909 | can define them in the file with |
2910 | ||
2911 | @example | |
2912 | #+LINK: bugzilla http://10.1.2.9/bugzilla/show_bug.cgi?id= | |
2913 | #+LINK: google http://www.google.com/search?q=%s | |
2914 | @end example | |
2915 | ||
2916 | @noindent | |
2917 | In-buffer completion @pxref{Completion} can be used after @samp{[} to | |
2918 | complete link abbreviations. | |
2919 | ||
2920 | @node Search options, Custom searches, Link abbreviations, Hyperlinks | |
2921 | @section Search options in file links | |
2922 | @cindex search option in file links | |
2923 | @cindex file links, searching | |
2924 | ||
2925 | File links can contain additional information to make Emacs jump to a | |
2926 | particular location in the file when following a link. This can be a | |
2927 | line number or a search option after a double@footnote{For backward | |
2928 | compatibility, line numbers can also follow a single colon.} colon. For | |
2929 | example, when the command @kbd{C-c l} creates a link (@pxref{Handling | |
2930 | links}) to a file, it encodes the words in the current line as a search | |
2931 | string that can be used to find this line back later when following the | |
28a16a1b | 2932 | link with @kbd{C-c C-o}. |
4009494e GM |
2933 | |
2934 | Here is the syntax of the different ways to attach a search to a file | |
2935 | link, together with an explanation: | |
2936 | ||
2937 | @example | |
2938 | [[file:~/code/main.c::255]] | |
2939 | [[file:~/xx.org::My Target]] | |
2940 | [[file:~/xx.org::*My Target]] | |
2941 | [[file:~/xx.org::/regexp/]] | |
2942 | @end example | |
2943 | ||
2944 | @table @code | |
2945 | @item 255 | |
2946 | Jump to line 255. | |
2947 | @item My Target | |
2948 | Search for a link target @samp{<<My Target>>}, or do a text search for | |
2949 | @samp{my target}, similar to the search in internal links, see | |
2950 | @ref{Internal links}. In HTML export (@pxref{HTML export}), such a file | |
2951 | link will become an HTML reference to the corresponding named anchor in | |
2952 | the linked file. | |
2953 | @item *My Target | |
a7808fba | 2954 | In an Org file, restrict search to headlines. |
4009494e GM |
2955 | @item /regexp/ |
2956 | Do a regular expression search for @code{regexp}. This uses the Emacs | |
2957 | command @code{occur} to list all matches in a separate window. If the | |
a7808fba | 2958 | target file is in Org mode, @code{org-occur} is used to create a |
4009494e GM |
2959 | sparse tree with the matches. |
2960 | @c If the target file is a directory, | |
2961 | @c @code{grep} will be used to search all files in the directory. | |
2962 | @end table | |
2963 | ||
2964 | As a degenerate case, a file link with an empty file name can be used | |
2965 | to search the current file. For example, @code{[[file:::find me]]} does | |
2966 | a search for @samp{find me} in the current file, just as | |
2967 | @samp{[[find me]]} would. | |
2968 | ||
dbc28aaa | 2969 | @node Custom searches, , Search options, Hyperlinks |
4009494e GM |
2970 | @section Custom Searches |
2971 | @cindex custom search strings | |
2972 | @cindex search strings, custom | |
2973 | ||
2974 | The default mechanism for creating search strings and for doing the | |
2975 | actual search related to a file link may not work correctly in all | |
2976 | cases. For example, BibTeX database files have many entries like | |
2977 | @samp{year="1993"} which would not result in good search strings, | |
2978 | because the only unique identification for a BibTeX entry is the | |
2979 | citation key. | |
2980 | ||
2981 | If you come across such a problem, you can write custom functions to set | |
2982 | the right search string for a particular file type, and to do the search | |
2983 | for the string in the file. Using @code{add-hook}, these functions need | |
2984 | to be added to the hook variables | |
2985 | @code{org-create-file-search-functions} and | |
2986 | @code{org-execute-file-search-functions}. See the docstring for these | |
a7808fba | 2987 | variables for more information. Org actually uses this mechanism |
4009494e | 2988 | for Bib@TeX{} database files, and you can use the corresponding code as |
44ce9197 | 2989 | an implementation example. See the file @file{org-bibtex.el}. |
4009494e | 2990 | |
a7808fba CD |
2991 | @node TODO Items, Tags, Hyperlinks, Top |
2992 | @chapter TODO Items | |
4009494e GM |
2993 | @cindex TODO items |
2994 | ||
44ce9197 | 2995 | Org mode does not maintain TODO lists as separate documents@footnote{Of |
a50253cc | 2996 | course, you can make a document that contains only long lists of TODO items, |
44ce9197 CD |
2997 | but this is not required.}. Instead, TODO items are an integral part of the |
2998 | notes file, because TODO items usually come up while taking notes! With Org | |
2999 | mode, simply mark any entry in a tree as being a TODO item. In this way, | |
3000 | information is not duplicated, and the entire context from which the TODO | |
3001 | item emerged is always present. | |
4009494e | 3002 | |
dbc28aaa | 3003 | Of course, this technique for managing TODO items scatters them |
a7808fba | 3004 | throughout your notes file. Org mode compensates for this by providing |
dbc28aaa | 3005 | methods to give you an overview of all the things that you have to do. |
4009494e GM |
3006 | |
3007 | @menu | |
3008 | * TODO basics:: Marking and displaying TODO entries | |
3009 | * TODO extensions:: Workflow and assignments | |
dbc28aaa | 3010 | * Progress logging:: Dates and notes for progress |
4009494e GM |
3011 | * Priorities:: Some things are more important than others |
3012 | * Breaking down tasks:: Splitting a task into manageable pieces | |
3013 | * Checkboxes:: Tick-off lists | |
3014 | @end menu | |
3015 | ||
a7808fba | 3016 | @node TODO basics, TODO extensions, TODO Items, TODO Items |
4009494e GM |
3017 | @section Basic TODO functionality |
3018 | ||
dbc28aaa CD |
3019 | Any headline becomes a TODO item when it starts with the word |
3020 | @samp{TODO}, for example: | |
4009494e GM |
3021 | |
3022 | @example | |
3023 | *** TODO Write letter to Sam Fortune | |
3024 | @end example | |
3025 | ||
3026 | @noindent | |
3027 | The most important commands to work with TODO entries are: | |
3028 | ||
3029 | @table @kbd | |
3030 | @kindex C-c C-t | |
3031 | @cindex cycling, of TODO states | |
3032 | @item C-c C-t | |
3033 | Rotate the TODO state of the current item among | |
3034 | ||
3035 | @example | |
3036 | ,-> (unmarked) -> TODO -> DONE --. | |
3037 | '--------------------------------' | |
3038 | @end example | |
3039 | ||
3040 | The same rotation can also be done ``remotely'' from the timeline and | |
3041 | agenda buffers with the @kbd{t} command key (@pxref{Agenda commands}). | |
dbc28aaa CD |
3042 | |
3043 | @kindex C-u C-c C-t | |
3044 | @item C-u C-c C-t | |
3045 | Select a specific keyword using completion or (if it has been set up) | |
28a16a1b CD |
3046 | the fast selection interface. For the latter, you need to assign keys |
3047 | to TODO states, see @ref{Per-file keywords} and @ref{Setting tags} for | |
3048 | more information. | |
dbc28aaa | 3049 | |
4009494e GM |
3050 | @kindex S-@key{right} |
3051 | @kindex S-@key{left} | |
3052 | @item S-@key{right} | |
3053 | @itemx S-@key{left} | |
dbc28aaa CD |
3054 | Select the following/preceding TODO state, similar to cycling. Useful |
3055 | mostly if more than two TODO states are possible (@pxref{TODO | |
3da3282e CD |
3056 | extensions}). See also @ref{Conflicts} for a discussion of the interaction |
3057 | with @code{shift-selection-mode}. | |
4009494e | 3058 | @kindex C-c C-v |
dbc28aaa | 3059 | @kindex C-c / t |
4009494e GM |
3060 | @cindex sparse tree, for TODO |
3061 | @item C-c C-v | |
dbc28aaa | 3062 | @itemx C-c / t |
4009494e GM |
3063 | View TODO items in a @emph{sparse tree} (@pxref{Sparse trees}). Folds |
3064 | the entire buffer, but shows all TODO items and the headings hierarchy | |
a7808fba | 3065 | above them. With a prefix argument, search for a specific TODO. You will be |
4009494e | 3066 | prompted for the keyword, and you can also give a list of keywords like |
a7808fba | 3067 | @code{KWD1|KWD2|...}. With numeric prefix argument N, show the tree for the |
4009494e | 3068 | Nth keyword in the variable @code{org-todo-keywords}. With two prefix |
a7808fba | 3069 | arguments, find all TODO and DONE entries. |
4009494e GM |
3070 | @kindex C-c a t |
3071 | @item C-c a t | |
dbc28aaa | 3072 | Show the global TODO list. Collects the TODO items from all agenda |
a7808fba | 3073 | files (@pxref{Agenda Views}) into a single buffer. The new buffer will |
dbc28aaa CD |
3074 | be in @code{agenda-mode}, which provides commands to examine and |
3075 | manipulate the TODO entries from the new buffer (@pxref{Agenda | |
3076 | commands}). @xref{Global TODO list}, for more information. | |
4009494e GM |
3077 | @kindex S-M-@key{RET} |
3078 | @item S-M-@key{RET} | |
3079 | Insert a new TODO entry below the current one. | |
3080 | @end table | |
3081 | ||
71d35b24 CD |
3082 | @noindent |
3083 | Changing a TODO state can also trigger tag changes. See the docstring of the | |
3084 | option @code{org-todo-state-tags-triggers} for details. | |
3085 | ||
a7808fba | 3086 | @node TODO extensions, Progress logging, TODO basics, TODO Items |
4009494e GM |
3087 | @section Extended use of TODO keywords |
3088 | @cindex extended TODO keywords | |
3089 | ||
dbc28aaa | 3090 | By default, marked TODO entries have one of only two states: TODO and |
a7808fba | 3091 | DONE. Org mode allows you to classify TODO items in more complex ways |
dbc28aaa CD |
3092 | with @emph{TODO keywords} (stored in @code{org-todo-keywords}). With |
3093 | special setup, the TODO keyword system can work differently in different | |
3094 | files. | |
4009494e GM |
3095 | |
3096 | Note that @i{tags} are another way to classify headlines in general and | |
3097 | TODO items in particular (@pxref{Tags}). | |
3098 | ||
3099 | @menu | |
3100 | * Workflow states:: From TODO to DONE in steps | |
dbc28aaa | 3101 | * TODO types:: I do this, Fred does the rest |
4009494e | 3102 | * Multiple sets in one file:: Mixing it all, and still finding your way |
dbc28aaa CD |
3103 | * Fast access to TODO states:: Single letter selection of a state |
3104 | * Per-file keywords:: Different files, different requirements | |
3105 | * Faces for TODO keywords:: Highlighting states | |
ec712abb | 3106 | * TODO dependencies:: When one task needs to wait for others |
4009494e GM |
3107 | @end menu |
3108 | ||
3109 | @node Workflow states, TODO types, TODO extensions, TODO extensions | |
3110 | @subsection TODO keywords as workflow states | |
3111 | @cindex TODO workflow | |
3112 | @cindex workflow states as TODO keywords | |
3113 | ||
3114 | You can use TODO keywords to indicate different @emph{sequential} states | |
3115 | in the process of working on an item, for example@footnote{Changing | |
a7808fba | 3116 | this variable only becomes effective after restarting Org mode in a |
4009494e GM |
3117 | buffer.}: |
3118 | ||
3119 | @lisp | |
3120 | (setq org-todo-keywords | |
3121 | '((sequence "TODO" "FEEDBACK" "VERIFY" "|" "DONE" "DELEGATED"))) | |
3122 | @end lisp | |
3123 | ||
3124 | The vertical bar separates the TODO keywords (states that @emph{need | |
44ce9197 | 3125 | action}) from the DONE states (which need @emph{no further action}). If |
4009494e GM |
3126 | you don't provide the separator bar, the last state is used as the DONE |
3127 | state. | |
3128 | @cindex completion, of TODO keywords | |
3129 | With this setup, the command @kbd{C-c C-t} will cycle an entry from TODO | |
3130 | to FEEDBACK, then to VERIFY, and finally to DONE and DELEGATED. You may | |
a7808fba | 3131 | also use a numeric prefix argument to quickly select a specific state. For |
4009494e | 3132 | example @kbd{C-3 C-c C-t} will change the state immediately to VERIFY. |
28a16a1b CD |
3133 | Or you can use @kbd{S-left} to go backward through the sequence. If you |
3134 | define many keywords, you can use in-buffer completion | |
3135 | (@pxref{Completion}) or even a special one-key selection scheme | |
3136 | (@pxref{Fast access to TODO states}) to insert these words into the | |
a7808fba | 3137 | buffer. Changing a TODO state can be logged with a timestamp, see |
28a16a1b | 3138 | @ref{Tracking TODO state changes} for more information. |
4009494e GM |
3139 | |
3140 | @node TODO types, Multiple sets in one file, Workflow states, TODO extensions | |
3141 | @subsection TODO keywords as types | |
3142 | @cindex TODO types | |
3143 | @cindex names as TODO keywords | |
3144 | @cindex types as TODO keywords | |
3145 | ||
3146 | The second possibility is to use TODO keywords to indicate different | |
3147 | @emph{types} of action items. For example, you might want to indicate | |
3148 | that items are for ``work'' or ``home''. Or, when you work with several | |
3149 | people on a single project, you might want to assign action items | |
3150 | directly to persons, by using their names as TODO keywords. This would | |
3151 | be set up like this: | |
3152 | ||
3153 | @lisp | |
3154 | (setq org-todo-keywords '((type "Fred" "Sara" "Lucy" "|" "DONE"))) | |
3155 | @end lisp | |
3156 | ||
3157 | In this case, different keywords do not indicate a sequence, but rather | |
3158 | different types. So the normal work flow would be to assign a task to a | |
a7808fba CD |
3159 | person, and later to mark it DONE. Org mode supports this style by adapting |
3160 | the workings of the command @kbd{C-c C-t}@footnote{This is also true for the | |
3161 | @kbd{t} command in the timeline and agenda buffers.}. When used several | |
3162 | times in succession, it will still cycle through all names, in order to first | |
3163 | select the right type for a task. But when you return to the item after some | |
3164 | time and execute @kbd{C-c C-t} again, it will switch from any name directly | |
3165 | to DONE. Use prefix arguments or completion to quickly select a specific | |
3166 | name. You can also review the items of a specific TODO type in a sparse tree | |
3167 | by using a numeric prefix to @kbd{C-c C-v}. For example, to see all things | |
3168 | Lucy has to do, you would use @kbd{C-3 C-c C-v}. To collect Lucy's items | |
3169 | from all agenda files into a single buffer, you would use the numeric prefix | |
3170 | argument as well when creating the global TODO list: @kbd{C-3 C-c t}. | |
4009494e | 3171 | |
dbc28aaa | 3172 | @node Multiple sets in one file, Fast access to TODO states, TODO types, TODO extensions |
4009494e | 3173 | @subsection Multiple keyword sets in one file |
a7808fba | 3174 | @cindex TODO keyword sets |
4009494e GM |
3175 | |
3176 | Sometimes you may want to use different sets of TODO keywords in | |
3177 | parallel. For example, you may want to have the basic | |
3178 | @code{TODO}/@code{DONE}, but also a workflow for bug fixing, and a | |
3179 | separate state indicating that an item has been canceled (so it is not | |
3180 | DONE, but also does not require action). Your setup would then look | |
3181 | like this: | |
3182 | ||
3183 | @lisp | |
3184 | (setq org-todo-keywords | |
3185 | '((sequence "TODO" "|" "DONE") | |
3186 | (sequence "REPORT" "BUG" "KNOWNCAUSE" "|" "FIXED") | |
3187 | (sequence "|" "CANCELED"))) | |
3188 | @end lisp | |
3189 | ||
a7808fba | 3190 | The keywords should all be different, this helps Org mode to keep track |
4009494e GM |
3191 | of which subsequence should be used for a given entry. In this setup, |
3192 | @kbd{C-c C-t} only operates within a subsequence, so it switches from | |
3193 | @code{DONE} to (nothing) to @code{TODO}, and from @code{FIXED} to | |
3194 | (nothing) to @code{REPORT}. Therefore you need a mechanism to initially | |
3195 | select the correct sequence. Besides the obvious ways like typing a | |
3196 | keyword or using completion, you may also apply the following commands: | |
3197 | ||
3198 | @table @kbd | |
3199 | @kindex C-S-@key{right} | |
3200 | @kindex C-S-@key{left} | |
3da3282e CD |
3201 | @kindex C-u C-u C-c C-t |
3202 | @item C-u C-u C-c C-t | |
3203 | @itemx C-S-@key{right} | |
4009494e GM |
3204 | @itemx C-S-@key{left} |
3205 | These keys jump from one TODO subset to the next. In the above example, | |
3da3282e CD |
3206 | @kbd{C-u C-u C-c C-t} or @kbd{C-S-@key{right}} would jump from @code{TODO} or |
3207 | @code{DONE} to @code{REPORT}, and any of the words in the second row to | |
3208 | @code{CANCELED}. Note that the @kbd{C-S-} key binding conflict with | |
3209 | @code{shift-selection-mode} (@pxref{Conflicts}). | |
4009494e GM |
3210 | @kindex S-@key{right} |
3211 | @kindex S-@key{left} | |
3212 | @item S-@key{right} | |
3213 | @itemx S-@key{left} | |
3da3282e CD |
3214 | @kbd{S-@key{<left>}} and @kbd{S-@key{<right>}} and walk through @emph{all} |
3215 | keywords from all sets, so for example @kbd{S-@key{<right>}} would switch | |
3216 | from @code{DONE} to @code{REPORT} in the example above. See also | |
3217 | @ref{Conflicts} for a discussion of the interaction with | |
3218 | @code{shift-selection-mode}. | |
4009494e GM |
3219 | @end table |
3220 | ||
dbc28aaa CD |
3221 | @node Fast access to TODO states, Per-file keywords, Multiple sets in one file, TODO extensions |
3222 | @subsection Fast access to TODO states | |
3223 | ||
3224 | If you would like to quickly change an entry to an arbitrary TODO state | |
3225 | instead of cycling through the states, you can set up keys for | |
3226 | single-letter access to the states. This is done by adding the section | |
3227 | key after each keyword, in parenthesis. For example: | |
3228 | ||
3229 | @lisp | |
3230 | (setq org-todo-keywords | |
3231 | '((sequence "TODO(t)" "|" "DONE(d)") | |
3232 | (sequence "REPORT(r)" "BUG(b)" "KNOWNCAUSE(k)" "|" "FIXED(f)") | |
3233 | (sequence "|" "CANCELED(c)"))) | |
3234 | @end lisp | |
3235 | ||
55033558 CD |
3236 | If you then press @code{C-c C-t} followed by the selection key, the entry |
3237 | will be switched to this state. @key{SPC} can be used to remove any TODO | |
3238 | keyword from an entry.@footnote{Check also the variable | |
dbc28aaa | 3239 | @code{org-fast-tag-selection-include-todo}, it allows to change the TODO |
55033558 CD |
3240 | state through the tags interface (@pxref{Setting tags}), in case you like to |
3241 | mingle the two concepts. Note that this means you need to come up with | |
3242 | unique keys across both sets of keywords.} | |
dbc28aaa CD |
3243 | |
3244 | @node Per-file keywords, Faces for TODO keywords, Fast access to TODO states, TODO extensions | |
4009494e GM |
3245 | @subsection Setting up keywords for individual files |
3246 | @cindex keyword options | |
dbc28aaa | 3247 | @cindex per-file keywords |
4009494e GM |
3248 | |
3249 | It can be very useful to use different aspects of the TODO mechanism in | |
3250 | different files. For file-local settings, you need to add special lines | |
3251 | to the file which set the keywords and interpretation for that file | |
3252 | only. For example, to set one of the two examples discussed above, you | |
3253 | need one of the following lines, starting in column zero anywhere in the | |
3254 | file: | |
3255 | ||
3256 | @example | |
3257 | #+SEQ_TODO: TODO FEEDBACK VERIFY | DONE CANCELED | |
3258 | @end example | |
3259 | or | |
3260 | @example | |
3261 | #+TYP_TODO: Fred Sara Lucy Mike | DONE | |
3262 | @end example | |
3263 | ||
3264 | A setup for using several sets in parallel would be: | |
3265 | ||
3266 | @example | |
3267 | #+SEQ_TODO: TODO | DONE | |
3268 | #+SEQ_TODO: REPORT BUG KNOWNCAUSE | FIXED | |
3269 | #+SEQ_TODO: | CANCELED | |
3270 | @end example | |
3271 | ||
3272 | @cindex completion, of option keywords | |
3273 | @kindex M-@key{TAB} | |
3274 | @noindent To make sure you are using the correct keyword, type | |
3275 | @samp{#+} into the buffer and then use @kbd{M-@key{TAB}} completion. | |
3276 | ||
3277 | @cindex DONE, final TODO keyword | |
3278 | Remember that the keywords after the vertical bar (or the last keyword | |
3279 | if no bar is there) must always mean that the item is DONE (although you | |
3280 | may use a different word). After changing one of these lines, use | |
3281 | @kbd{C-c C-c} with the cursor still in the line to make the changes | |
a7808fba CD |
3282 | known to Org mode@footnote{Org mode parses these lines only when |
3283 | Org mode is activated after visiting a file. @kbd{C-c C-c} with the | |
3284 | cursor in a line starting with @samp{#+} is simply restarting Org mode | |
4009494e GM |
3285 | for the current buffer.}. |
3286 | ||
7ddb1b5f | 3287 | @node Faces for TODO keywords, TODO dependencies, Per-file keywords, TODO extensions |
dbc28aaa CD |
3288 | @subsection Faces for TODO keywords |
3289 | @cindex faces, for TODO keywords | |
3290 | ||
a7808fba | 3291 | Org mode highlights TODO keywords with special faces: @code{org-todo} |
dbc28aaa CD |
3292 | for keywords indicating that an item still has to be acted upon, and |
3293 | @code{org-done} for keywords indicating that an item is finished. If | |
3294 | you are using more than 2 different states, you might want to use | |
3295 | special faces for some of them. This can be done using the variable | |
3296 | @code{org-todo-keyword-faces}. For example: | |
3297 | ||
3298 | @lisp | |
96c8522a | 3299 | @group |
dbc28aaa CD |
3300 | (setq org-todo-keyword-faces |
3301 | '(("TODO" . org-warning) | |
3302 | ("DEFERRED" . shadow) | |
3303 | ("CANCELED" . (:foreground "blue" :weight bold)))) | |
96c8522a | 3304 | @end group |
dbc28aaa CD |
3305 | @end lisp |
3306 | ||
28a16a1b CD |
3307 | While using a list with face properties as shown for CANCELED |
3308 | @emph{should} work, this does not aways seem to be the case. If | |
3309 | necessary, define a special face and use that. | |
3310 | ||
7ddb1b5f CD |
3311 | @node TODO dependencies, , Faces for TODO keywords, TODO extensions |
3312 | @subsection TODO dependencies | |
2e461fc1 CD |
3313 | @cindex TODO dependencies |
3314 | @cindex dependencies, of TODO states | |
7ddb1b5f CD |
3315 | |
3316 | The structure of Org files (hierarchy and lists) makes it easy to define TODO | |
3317 | dependencies. Usually, a parent TODO task should not be marked DONE until | |
3318 | all subtasks (defined as children tasks) are marked as DONE. And sometimes | |
3319 | there is a logical sequence to a number of (sub)tasks, so that one task | |
3320 | cannot be acted upon before all siblings above it are done. If you customize | |
3321 | the variable @code{org-enforce-todo-dependencies}, Org will block entries | |
2e461fc1 CD |
3322 | from changing state to DONE while they have children that are not DONE. |
3323 | Furthermore, if an entry has a property @code{ORDERED}, each of its children | |
3324 | will be blocked until all earlier siblings are marked DONE. Here is an | |
3325 | example: | |
7ddb1b5f CD |
3326 | |
3327 | @example | |
3328 | * TODO Blocked until (two) is done | |
3329 | ** DONE one | |
3330 | ** TODO two | |
3331 | ||
3332 | * Parent | |
3333 | :PROPERTIES: | |
3334 | :ORDERED: t | |
3335 | :END: | |
3336 | ** TODO a | |
3337 | ** TODO b, needs to wait for (a) | |
3338 | ** TODO c, needs to wait for (a) and (b) | |
3339 | @end example | |
3340 | ||
bc283609 CD |
3341 | @table @kbd |
3342 | @kindex C-c C-x o | |
3343 | @item C-c C-x o | |
3344 | Toggle the @code{ORDERED} property of the current entry. | |
2e461fc1 CD |
3345 | @kindex C-u C-u C-u C-c C-t |
3346 | @item C-u C-u C-u C-c C-t | |
3347 | Change TODO state, circumventin any state blocking. | |
bc283609 CD |
3348 | @end table |
3349 | ||
7ddb1b5f CD |
3350 | If you set the variable @code{org-agenda-dim-blocked-tasks}, TODO entries |
3351 | that cannot be closed because of such dependencies will be shown in a dimmed | |
3352 | font or even made invisible in agenda views (@pxref{Agenda Views}). | |
3353 | ||
2e461fc1 CD |
3354 | @cindex checkboxes and TODO dependencies |
3355 | You can also block changes of TODO states by looking at checkboxes | |
3356 | (@pxref{Checkboxes}). If you set the variable | |
3357 | @code{org-enforce-todo-checkbox-dependencies}, an entry that has unchecked | |
3358 | checkboxes will be blocked from switching to DONE. | |
3359 | ||
7ddb1b5f CD |
3360 | If you need more complex dependency structures, for example dependencies |
3361 | between entries in different trees or files, check out the contributed | |
3362 | module @file{org-depend.el}. | |
3363 | ||
dbc28aaa | 3364 | @page |
a7808fba CD |
3365 | @node Progress logging, Priorities, TODO extensions, TODO Items |
3366 | @section Progress logging | |
dbc28aaa CD |
3367 | @cindex progress logging |
3368 | @cindex logging, of progress | |
3369 | ||
a7808fba | 3370 | Org mode can automatically record a time stamp and possibly a note when |
28a16a1b CD |
3371 | you mark a TODO item as DONE, or even each time you change the state of |
3372 | a TODO item. This system is highly configurable, settings can be on a | |
3373 | per-keyword basis and can be localized to a file or even a subtree. For | |
3374 | information on how to clock working time for a task, see @ref{Clocking | |
3375 | work time}. | |
dbc28aaa CD |
3376 | |
3377 | @menu | |
3378 | * Closing items:: When was this entry marked DONE? | |
3379 | * Tracking TODO state changes:: When did the status change? | |
3380 | @end menu | |
3381 | ||
3382 | @node Closing items, Tracking TODO state changes, Progress logging, Progress logging | |
3383 | @subsection Closing items | |
3384 | ||
28a16a1b CD |
3385 | The most basic logging is to keep track of @emph{when} a certain TODO |
3386 | item was finished. This is achieved with@footnote{The corresponding | |
3387 | in-buffer setting is: @code{#+STARTUP: logdone}}. | |
dbc28aaa CD |
3388 | |
3389 | @lisp | |
28a16a1b | 3390 | (setq org-log-done 'time) |
dbc28aaa CD |
3391 | @end lisp |
3392 | ||
3393 | @noindent | |
28a16a1b CD |
3394 | Then each time you turn an entry from a TODO (not-done) state into any |
3395 | of the DONE states, a line @samp{CLOSED: [timestamp]} will be inserted | |
3396 | just after the headline. If you turn the entry back into a TODO item | |
3397 | through further state cycling, that line will be removed again. If you | |
3398 | want to record a note along with the timestamp, use@footnote{The | |
3399 | corresponding in-buffer setting is: @code{#+STARTUP: lognotedone}} | |
dbc28aaa CD |
3400 | |
3401 | @lisp | |
28a16a1b | 3402 | (setq org-log-done 'note) |
dbc28aaa CD |
3403 | @end lisp |
3404 | ||
28a16a1b CD |
3405 | @noindent |
3406 | You will then be prompted for a note, and that note will be stored below | |
3407 | the entry with a @samp{Closing Note} heading. | |
3408 | ||
3409 | In the timeline (@pxref{Timeline}) and in the agenda | |
a7808fba | 3410 | (@pxref{Weekly/daily agenda}), you can then use the @kbd{l} key to |
28a16a1b CD |
3411 | display the TODO items with a @samp{CLOSED} timestamp on each day, |
3412 | giving you an overview of what has been done. | |
3413 | ||
dbc28aaa CD |
3414 | @node Tracking TODO state changes, , Closing items, Progress logging |
3415 | @subsection Tracking TODO state changes | |
3416 | ||
3417 | When TODO keywords are used as workflow states (@pxref{Workflow | |
3418 | states}), you might want to keep track of when a state change occurred | |
28a16a1b | 3419 | and maybe take a note about this change. Since it is normally too much |
a7808fba | 3420 | to record a note for every state, Org mode expects configuration on a |
28a16a1b CD |
3421 | per-keyword basis for this. This is achieved by adding special markers |
3422 | @samp{!} (for a time stamp) and @samp{@@} (for a note) in parenthesis | |
3423 | after each keyword. For example, with the setting | |
dbc28aaa CD |
3424 | |
3425 | @lisp | |
28a16a1b CD |
3426 | (setq org-todo-keywords |
3427 | '((sequence "TODO(t)" "WAIT(w@@/!)" "|" "DONE(d!)" "CANCELED(c@@)"))) | |
dbc28aaa CD |
3428 | @end lisp |
3429 | ||
3430 | @noindent | |
28a16a1b CD |
3431 | you not only define global TODO keywords and fast access keys, but also |
3432 | request that a time is recorded when the entry is turned into | |
a7808fba | 3433 | DONE@footnote{It is possible that Org mode will record two time stamps |
28a16a1b CD |
3434 | when you are using both @code{org-log-done} and state change logging. |
3435 | However, it will never prompt for two notes - if you have configured | |
3436 | both, the state change recording note will take precedence and cancel | |
3437 | the @samp{Closing Note}.}, and that a note is recorded when switching to | |
3438 | WAIT or CANCELED. The setting for WAIT is even more special: The | |
3439 | @samp{!} after the slash means that in addition to the note taken when | |
3440 | entering the state, a time stamp should be recorded when @i{leaving} the | |
3441 | WAIT state, if and only if the @i{target} state does not configure | |
3442 | logging for entering it. So it has no effect when switching from WAIT | |
3443 | to DONE, because DONE is configured to record a timestamp only. But | |
3444 | when switching from WAIT back to TODO, the @samp{/!} in the WAIT | |
3445 | setting now triggers a timestamp even though TODO has no logging | |
3446 | configured. | |
3447 | ||
3448 | You can use the exact same syntax for setting logging preferences local | |
3449 | to a buffer: | |
3450 | @example | |
3451 | #+SEQ_TODO: TODO(t) WAIT(w@@/!) | DONE(d!) CANCELED(c@@) | |
3452 | @end example | |
3453 | ||
3454 | In order to define logging settings that are local to a subtree or a | |
3455 | single item, define a LOGGING property in this entry. Any non-empty | |
3456 | LOGGING property resets all logging settings to nil. You may then turn | |
3457 | on logging for this specific tree using STARTUP keywords like | |
3458 | @code{lognotedone} or @code{logrepeat}, as well as adding state specific | |
3459 | settings like @code{TODO(!)}. For example | |
3460 | ||
3461 | @example | |
3462 | * TODO Log each state with only a time | |
3463 | :PROPERTIES: | |
3464 | :LOGGING: TODO(!) WAIT(!) DONE(!) CANCELED(!) | |
3465 | :END: | |
3466 | * TODO Only log when switching to WAIT, and when repeating | |
3467 | :PROPERTIES: | |
3468 | :LOGGING: WAIT(@@) logrepeat | |
3469 | :END: | |
3470 | * TODO No logging at all | |
3471 | :PROPERTIES: | |
3472 | :LOGGING: nil | |
3473 | :END: | |
dbc28aaa CD |
3474 | @end example |
3475 | ||
a7808fba | 3476 | @node Priorities, Breaking down tasks, Progress logging, TODO Items |
4009494e GM |
3477 | @section Priorities |
3478 | @cindex priorities | |
3479 | ||
a7808fba | 3480 | If you use Org mode extensively, you may end up enough TODO items that |
dbc28aaa CD |
3481 | it starts to make sense to prioritize them. Prioritizing can be done by |
3482 | placing a @emph{priority cookie} into the headline of a TODO item, like | |
3483 | this | |
4009494e GM |
3484 | |
3485 | @example | |
3486 | *** TODO [#A] Write letter to Sam Fortune | |
3487 | @end example | |
3488 | ||
3489 | @noindent | |
a7808fba | 3490 | By default, Org mode supports three priorities: @samp{A}, @samp{B}, and |
dbc28aaa CD |
3491 | @samp{C}. @samp{A} is the highest priority. An entry without a cookie |
3492 | is treated as priority @samp{B}. Priorities make a difference only in | |
a7808fba CD |
3493 | the agenda (@pxref{Weekly/daily agenda}); outside the agenda, they have |
3494 | no inherent meaning to Org mode. | |
dbc28aaa CD |
3495 | |
3496 | Priorities can be attached to any outline tree entries; they do not need | |
3497 | to be TODO items. | |
4009494e GM |
3498 | |
3499 | @table @kbd | |
3500 | @kindex @kbd{C-c ,} | |
3501 | @item @kbd{C-c ,} | |
3502 | Set the priority of the current headline. The command prompts for a | |
3503 | priority character @samp{A}, @samp{B} or @samp{C}. When you press | |
3504 | @key{SPC} instead, the priority cookie is removed from the headline. | |
3505 | The priorities can also be changed ``remotely'' from the timeline and | |
3506 | agenda buffer with the @kbd{,} command (@pxref{Agenda commands}). | |
3507 | @c | |
3508 | @kindex S-@key{up} | |
3509 | @kindex S-@key{down} | |
3510 | @item S-@key{up} | |
3511 | @itemx S-@key{down} | |
3da3282e CD |
3512 | Increase/decrease priority of current headline@footnote{See also the option |
3513 | @code{org-priority-start-cycle-with-default'}.}. Note that these keys are | |
3514 | also used to modify time stamps (@pxref{Creating timestamps}). See also | |
3515 | @ref{Conflicts} for a discussion of the interaction with | |
3516 | @code{shift-selection-mode}. | |
4009494e GM |
3517 | @end table |
3518 | ||
3519 | You can change the range of allowed priorities by setting the variables | |
3520 | @code{org-highest-priority}, @code{org-lowest-priority}, and | |
3521 | @code{org-default-priority}. For an individual buffer, you may set | |
3522 | these values (highest, lowest, default) like this (please make sure that | |
3523 | the highest priority is earlier in the alphabet than the lowest | |
3524 | priority): | |
3525 | ||
3526 | @example | |
3527 | #+PRIORITIES: A C B | |
3528 | @end example | |
3529 | ||
a7808fba | 3530 | @node Breaking down tasks, Checkboxes, Priorities, TODO Items |
4009494e GM |
3531 | @section Breaking tasks down into subtasks |
3532 | @cindex tasks, breaking down | |
3533 | ||
3534 | It is often advisable to break down large tasks into smaller, manageable | |
b349f79f CD |
3535 | subtasks. You can do this by creating an outline tree below a TODO item, |
3536 | with detailed subtasks on the tree@footnote{To keep subtasks out of the | |
3537 | global TODO list, see the @code{org-agenda-todo-list-sublevels}.}. To keep | |
3538 | the overview over the fraction of subtasks that are already completed, insert | |
3539 | either @samp{[/]} or @samp{[%]} anywhere in the headline. These cookies will | |
3540 | be updates each time the todo status of a child changes. For example: | |
3541 | ||
3542 | @example | |
3543 | * Organize Party [33%] | |
3544 | ** TODO Call people [1/2] | |
3545 | *** TODO Peter | |
3546 | *** DONE Sarah | |
3547 | ** TODO Buy food | |
3548 | ** DONE Talk to neighbor | |
3549 | @end example | |
3550 | ||
3551 | If you would like a TODO entry to automatically change to DONE when all | |
a50253cc | 3552 | children are done, you can use the following setup: |
b349f79f CD |
3553 | |
3554 | @example | |
3555 | (defun org-summary-todo (n-done n-not-done) | |
3556 | "Switch entry to DONE when all subentries are done, to TODO otherwise." | |
3557 | (let (org-log-done org-log-states) ; turn off logging | |
3558 | (org-todo (if (= n-not-done 0) "DONE" "TODO")))) | |
3559 | ||
3560 | (add-hook 'org-after-todo-statistics-hook 'org-summary-todo) | |
3561 | @end example | |
3562 | ||
3563 | ||
3564 | Another possibility is the use of checkboxes to identify (a hierarchy of) a | |
3565 | large number of subtasks (@pxref{Checkboxes}). | |
4009494e GM |
3566 | |
3567 | ||
a7808fba | 3568 | @node Checkboxes, , Breaking down tasks, TODO Items |
4009494e GM |
3569 | @section Checkboxes |
3570 | @cindex checkboxes | |
3571 | ||
dbc28aaa CD |
3572 | Every item in a plain list (@pxref{Plain lists}) can be made into a |
3573 | checkbox by starting it with the string @samp{[ ]}. This feature is | |
a7808fba | 3574 | similar to TODO items (@pxref{TODO Items}), but is more lightweight. |
dbc28aaa CD |
3575 | Checkboxes are not included into the global TODO list, so they are often |
3576 | great to split a task into a number of simple steps. Or you can use | |
3577 | them in a shopping list. To toggle a checkbox, use @kbd{C-c C-c}, or | |
3578 | use the mouse (thanks to Piotr Zielinski's @file{org-mouse.el}). | |
3579 | ||
3580 | Here is an example of a checkbox list. | |
4009494e GM |
3581 | |
3582 | @example | |
28a16a1b CD |
3583 | * TODO Organize party [2/4] |
3584 | - [-] call people [1/3] | |
4009494e GM |
3585 | - [ ] Peter |
3586 | - [X] Sarah | |
3587 | - [ ] Sam | |
3588 | - [X] order food | |
3589 | - [ ] think about what music to play | |
3590 | - [X] talk to the neighbors | |
3591 | @end example | |
3592 | ||
28a16a1b CD |
3593 | Checkboxes work hierarchically, so if a checkbox item has children that |
3594 | are checkboxes, toggling one of the children checkboxes will make the | |
3595 | parent checkbox reflect if none, some, or all of the children are | |
3596 | checked. | |
3597 | ||
4009494e GM |
3598 | @cindex statistics, for checkboxes |
3599 | @cindex checkbox statistics | |
28a16a1b | 3600 | The @samp{[2/4]} and @samp{[1/3]} in the first and second line are |
dbc28aaa CD |
3601 | cookies indicating how many checkboxes present in this entry have been |
3602 | checked off, and the total number of checkboxes are present. This can | |
3603 | give you an idea on how many checkboxes remain, even without opening a | |
3604 | folded entry. The cookies can be placed into a headline or into (the | |
3605 | first line of) a plain list item. Each cookie covers all checkboxes | |
3606 | structurally below the headline/item on which the cookie appear. You | |
3607 | have to insert the cookie yourself by typing either @samp{[/]} or | |
3608 | @samp{[%]}. With @samp{[/]} you get an @samp{n out of m} result, as in | |
3609 | the examples above. With @samp{[%]} you get information about the | |
4009494e | 3610 | percentage of checkboxes checked (in the above example, this would be |
dbc28aaa | 3611 | @samp{[50%]} and @samp{[33%]}, respectively). |
4009494e GM |
3612 | |
3613 | @noindent The following commands work with checkboxes: | |
3614 | ||
3615 | @table @kbd | |
3616 | @kindex C-c C-c | |
3617 | @item C-c C-c | |
a7808fba | 3618 | Toggle checkbox at point. With a prefix argument, set it to @samp{[-]}, |
4009494e GM |
3619 | which is considered to be an intermediate state. |
3620 | @kindex C-c C-x C-b | |
3621 | @item C-c C-x C-b | |
7ddb1b5f | 3622 | Toggle checkbox status or (with prefix arg) checkbox presence at point. |
4009494e GM |
3623 | @itemize @minus |
3624 | @item | |
3625 | If there is an active region, toggle the first checkbox in the region | |
7ddb1b5f CD |
3626 | and set all remaining boxes to the same status as the first. With a prefix |
3627 | arg, add or remove the checkbox for all items in the region. | |
4009494e GM |
3628 | @item |
3629 | If the cursor is in a headline, toggle checkboxes in the region between | |
3630 | this headline and the next (so @emph{not} the entire subtree). | |
3631 | @item | |
3632 | If there is no active region, just toggle the checkbox at point. | |
3633 | @end itemize | |
3634 | @kindex M-S-@key{RET} | |
3635 | @item M-S-@key{RET} | |
3636 | Insert a new item with a checkbox. | |
3637 | This works only if the cursor is already in a plain list item | |
3638 | (@pxref{Plain lists}). | |
3639 | @kindex C-c # | |
3640 | @item C-c # | |
3641 | Update the checkbox statistics in the current outline entry. When | |
3642 | called with a @kbd{C-u} prefix, update the entire file. Checkbox | |
3643 | statistic cookies are updated automatically if you toggle checkboxes | |
3644 | with @kbd{C-c C-c} and make new ones with @kbd{M-S-@key{RET}}. If you | |
3645 | delete boxes or add/change them by hand, use this command to get things | |
a50253cc | 3646 | back into sync. Or simply toggle any checkbox twice with @kbd{C-c C-c}. |
4009494e GM |
3647 | @end table |
3648 | ||
a7808fba | 3649 | @node Tags, Properties and Columns, TODO Items, Top |
4009494e GM |
3650 | @chapter Tags |
3651 | @cindex tags | |
3652 | @cindex headline tagging | |
3653 | @cindex matching, tags | |
3654 | @cindex sparse tree, tag based | |
3655 | ||
dbc28aaa | 3656 | An excellent way to implement labels and contexts for cross-correlating |
a7808fba | 3657 | information is to assign @i{tags} to headlines. Org mode has extensive |
dbc28aaa | 3658 | support for tags. |
4009494e | 3659 | |
dbc28aaa | 3660 | Every headline can contain a list of tags; they occur at the end of the |
96c8522a CD |
3661 | headline. Tags are normal words containing letters, numbers, @samp{_}, and |
3662 | @samp{@@}. Tags must be preceded and followed by a single colon, e.g., | |
3663 | @samp{:work:}. Several tags can be specified, as in @samp{:work:urgent:}. | |
3664 | Tags will by default get a bold face with the same color as the headline. | |
3665 | You may specify special faces for specific tags using the variable | |
3666 | @code{org-tag-faces}, much in the same way as you can do for TODO keywords | |
3667 | (@pxref{Faces for TODO keywords}). | |
4009494e GM |
3668 | |
3669 | @menu | |
3670 | * Tag inheritance:: Tags use the tree structure of the outline | |
3671 | * Setting tags:: How to assign tags to a headline | |
3672 | * Tag searches:: Searching for combinations of tags | |
3673 | @end menu | |
3674 | ||
3675 | @node Tag inheritance, Setting tags, Tags, Tags | |
3676 | @section Tag inheritance | |
dbc28aaa | 3677 | @cindex tag inheritance |
4009494e GM |
3678 | @cindex inheritance, of tags |
3679 | @cindex sublevels, inclusion into tags match | |
3680 | ||
3681 | @i{Tags} make use of the hierarchical structure of outline trees. If a | |
3682 | heading has a certain tag, all subheadings will inherit the tag as | |
3683 | well. For example, in the list | |
3684 | ||
3685 | @example | |
dbc28aaa CD |
3686 | * Meeting with the French group :work: |
3687 | ** Summary by Frank :boss:notes: | |
3688 | *** TODO Prepare slides for him :action: | |
4009494e GM |
3689 | @end example |
3690 | ||
3691 | @noindent | |
dbc28aaa CD |
3692 | the final heading will have the tags @samp{:work:}, @samp{:boss:}, |
3693 | @samp{:notes:}, and @samp{:action:} even though the final heading is not | |
b349f79f CD |
3694 | explicitly marked with those tags. You can also set tags that all entries in |
3695 | a file should inherit as if these tags would be defined in a hypothetical | |
a50253cc | 3696 | level zero that surrounds the entire file. |
b349f79f CD |
3697 | |
3698 | @example | |
3699 | #+FILETAGS: :Peter:Boss:Secret: | |
3700 | @end example | |
3701 | ||
3702 | @noindent | |
3703 | To limit tag inheritance to specific tags, or to turn it off entirely, use | |
96c8522a CD |
3704 | the variables @code{org-use-tag-inheritance} and |
3705 | @code{org-tags-exclude-from-inheritance}. | |
b349f79f CD |
3706 | |
3707 | When a headline matches during a tags search while tag inheritance is turned | |
96c8522a | 3708 | on, all the sublevels in the same tree will (for a simple match form) match |
07450bee | 3709 | as well@footnote{This is only true if the search does not involve more |
96c8522a CD |
3710 | complex tests including properties (@pxref{Property searches}).}. The list |
3711 | of matches may then become very long. If you only want to see the first tags | |
3712 | match in a subtree, configure the variable | |
3713 | @code{org-tags-match-list-sublevels} (not recommended). | |
4009494e GM |
3714 | |
3715 | @node Setting tags, Tag searches, Tag inheritance, Tags | |
3716 | @section Setting tags | |
3717 | @cindex setting tags | |
3718 | @cindex tags, setting | |
3719 | ||
3720 | @kindex M-@key{TAB} | |
3721 | Tags can simply be typed into the buffer at the end of a headline. | |
3722 | After a colon, @kbd{M-@key{TAB}} offers completion on tags. There is | |
3723 | also a special command for inserting tags: | |
3724 | ||
3725 | @table @kbd | |
71d35b24 CD |
3726 | @kindex C-c C-q |
3727 | @item C-c C-q | |
4009494e | 3728 | @cindex completion, of tags |
a7808fba | 3729 | Enter new tags for the current headline. Org mode will either offer |
4009494e GM |
3730 | completion or a special single-key interface for setting tags, see |
3731 | below. After pressing @key{RET}, the tags will be inserted and aligned | |
3732 | to @code{org-tags-column}. When called with a @kbd{C-u} prefix, all | |
3733 | tags in the current buffer will be aligned to that column, just to make | |
3734 | things look nice. TAGS are automatically realigned after promotion, | |
3735 | demotion, and TODO state changes (@pxref{TODO basics}). | |
71d35b24 CD |
3736 | @kindex C-c C-c |
3737 | @item C-c C-c | |
3738 | When the cursor is in a headline, this does the same as @kbd{C-c C-q}. | |
4009494e GM |
3739 | @end table |
3740 | ||
3741 | Org will support tag insertion based on a @emph{list of tags}. By | |
3742 | default this list is constructed dynamically, containing all tags | |
3743 | currently used in the buffer. You may also globally specify a hard list | |
3744 | of tags with the variable @code{org-tag-alist}. Finally you can set | |
3745 | the default tags for a given file with lines like | |
3746 | ||
3747 | @example | |
dbc28aaa CD |
3748 | #+TAGS: @@work @@home @@tennisclub |
3749 | #+TAGS: laptop car pc sailboat | |
4009494e GM |
3750 | @end example |
3751 | ||
3752 | If you have globally defined your preferred set of tags using the | |
3753 | variable @code{org-tag-alist}, but would like to use a dynamic tag list | |
dbc28aaa | 3754 | in a specific file, add an empty TAGS option line to that file: |
4009494e GM |
3755 | |
3756 | @example | |
3757 | #+TAGS: | |
3758 | @end example | |
3759 | ||
a7808fba CD |
3760 | By default Org mode uses the standard minibuffer completion facilities for |
3761 | entering tags. However, it also implements another, quicker, tag selection | |
3762 | method called @emph{fast tag selection}. This allows you to select and | |
3763 | deselect tags with just a single key press. For this to work well you should | |
3764 | assign unique letters to most of your commonly used tags. You can do this | |
3765 | globally by configuring the variable @code{org-tag-alist} in your | |
3766 | @file{.emacs} file. For example, you may find the need to tag many items in | |
3767 | different files with @samp{:@@home:}. In this case you can set something | |
3768 | like: | |
4009494e GM |
3769 | |
3770 | @lisp | |
dbc28aaa | 3771 | (setq org-tag-alist '(("@@work" . ?w) ("@@home" . ?h) ("laptop" . ?l))) |
4009494e GM |
3772 | @end lisp |
3773 | ||
a7808fba CD |
3774 | @noindent If the tag is only relevant to the file you are working on then you |
3775 | can, instead, set the TAGS option line as: | |
4009494e GM |
3776 | |
3777 | @example | |
dbc28aaa | 3778 | #+TAGS: @@work(w) @@home(h) @@tennisclub(t) laptop(l) pc(p) |
4009494e GM |
3779 | @end example |
3780 | ||
3781 | @noindent | |
a7808fba CD |
3782 | You can also group together tags that are mutually exclusive. By using |
3783 | braces, as in: | |
4009494e GM |
3784 | |
3785 | @example | |
dbc28aaa | 3786 | #+TAGS: @{ @@work(w) @@home(h) @@tennisclub(t) @} laptop(l) pc(p) |
4009494e GM |
3787 | @end example |
3788 | ||
dbc28aaa | 3789 | @noindent you indicate that at most one of @samp{@@work}, @samp{@@home}, |
a7808fba | 3790 | and @samp{@@tennisclub} should be selected. Multiple such groups are allowed. |
4009494e GM |
3791 | |
3792 | @noindent Don't forget to press @kbd{C-c C-c} with the cursor in one of | |
3793 | these lines to activate any changes. | |
3794 | ||
a7808fba CD |
3795 | @noindent |
3796 | To set these mutually exclusive groups in the variable @code{org-mode-alist} | |
3797 | you must use the dummy tags @code{:startgroup} and @code{:endgroup} instead | |
3798 | of the braces. The previous example would be set globally by the following | |
3799 | configuration: | |
3800 | ||
3801 | @lisp | |
3802 | (setq org-tag-alist '((:startgroup . nil) | |
3803 | ("@@work" . ?w) ("@@home" . ?h) | |
3804 | ("@@tennisclub" . ?t) | |
3805 | (:endgroup . nil) | |
3806 | ("laptop" . ?l) ("pc" . ?p))) | |
3807 | @end lisp | |
3808 | ||
3809 | If at least one tag has a selection key then pressing @kbd{C-c C-c} will | |
3810 | automatically present you with a special interface, listing inherited tags, | |
3811 | the tags of the current headline, and a list of all valid tags with | |
3812 | corresponding keys@footnote{Keys will automatically be assigned to tags which | |
3813 | have no configured keys.}. In this interface, you can use the following | |
3814 | keys: | |
4009494e GM |
3815 | |
3816 | @table @kbd | |
3817 | @item a-z... | |
3818 | Pressing keys assigned to tags will add or remove them from the list of | |
3819 | tags in the current line. Selecting a tag in a group of mutually | |
3820 | exclusive tags will turn off any other tags from that group. | |
3821 | @kindex @key{TAB} | |
3822 | @item @key{TAB} | |
3823 | Enter a tag in the minibuffer, even if the tag is not in the predefined | |
3824 | list. You will be able to complete on all tags present in the buffer. | |
3825 | @kindex @key{SPC} | |
3826 | @item @key{SPC} | |
3827 | Clear all tags for this line. | |
3828 | @kindex @key{RET} | |
3829 | @item @key{RET} | |
3830 | Accept the modified set. | |
3831 | @item C-g | |
3832 | Abort without installing changes. | |
3833 | @item q | |
3834 | If @kbd{q} is not assigned to a tag, it aborts like @kbd{C-g}. | |
3835 | @item ! | |
3836 | Turn off groups of mutually exclusive tags. Use this to (as an | |
3837 | exception) assign several tags from such a group. | |
3838 | @item C-c | |
3839 | Toggle auto-exit after the next change (see below). | |
3840 | If you are using expert mode, the first @kbd{C-c} will display the | |
3841 | selection window. | |
3842 | @end table | |
3843 | ||
3844 | @noindent | |
3845 | This method lets you assign tags to a headline with very few keys. With | |
dbc28aaa CD |
3846 | the above setup, you could clear the current tags and set @samp{@@home}, |
3847 | @samp{laptop} and @samp{pc} tags with just the following keys: @kbd{C-c | |
3848 | C-c @key{SPC} h l p @key{RET}}. Switching from @samp{@@home} to | |
3849 | @samp{@@work} would be done with @kbd{C-c C-c w @key{RET}} or | |
4009494e GM |
3850 | alternatively with @kbd{C-c C-c C-c w}. Adding the non-predefined tag |
3851 | @samp{Sarah} could be done with @kbd{C-c C-c @key{TAB} S a r a h | |
3852 | @key{RET} @key{RET}}. | |
3853 | ||
a7808fba | 3854 | If you find that most of the time, you need only a single key press to |
4009494e GM |
3855 | modify your list of tags, set the variable |
3856 | @code{org-fast-tag-selection-single-key}. Then you no longer have to | |
3857 | press @key{RET} to exit fast tag selection - it will immediately exit | |
3858 | after the first change. If you then occasionally need more keys, press | |
3859 | @kbd{C-c} to turn off auto-exit for the current tag selection process | |
3860 | (in effect: start selection with @kbd{C-c C-c C-c} instead of @kbd{C-c | |
3861 | C-c}). If you set the variable to the value @code{expert}, the special | |
3862 | window is not even shown for single-key tag selection, it comes up only | |
3863 | when you press an extra @kbd{C-c}. | |
3864 | ||
3865 | @node Tag searches, , Setting tags, Tags | |
3866 | @section Tag searches | |
3867 | @cindex tag searches | |
3868 | @cindex searching for tags | |
3869 | ||
dbc28aaa | 3870 | Once a system of tags has been set up, it can be used to collect related |
4009494e GM |
3871 | information into special lists. |
3872 | ||
3873 | @table @kbd | |
3874 | @kindex C-c \ | |
dbc28aaa | 3875 | @kindex C-c / T |
4009494e | 3876 | @item C-c \ |
dbc28aaa | 3877 | @itemx C-c / T |
4009494e GM |
3878 | Create a sparse tree with all headlines matching a tags search. With a |
3879 | @kbd{C-u} prefix argument, ignore headlines that are not a TODO line. | |
3880 | @kindex C-c a m | |
3881 | @item C-c a m | |
3882 | Create a global list of tag matches from all agenda files. | |
3883 | @xref{Matching tags and properties}. | |
3884 | @kindex C-c a M | |
3885 | @item C-c a M | |
3886 | Create a global list of tag matches from all agenda files, but check | |
3887 | only TODO items and force checking subitems (see variable | |
3888 | @code{org-tags-match-list-sublevels}). | |
3889 | @end table | |
3890 | ||
3891 | @cindex Boolean logic, for tag searches | |
3892 | A @i{tags} search string can use Boolean operators @samp{&} for AND and | |
3893 | @samp{|} for OR. @samp{&} binds more strongly than @samp{|}. | |
3894 | Parenthesis are currently not implemented. A tag may also be preceded | |
3895 | by @samp{-}, to select against it, and @samp{+} is syntactic sugar for | |
3896 | positive selection. The AND operator @samp{&} is optional when @samp{+} | |
3897 | or @samp{-} is present. Examples: | |
3898 | ||
3899 | @table @samp | |
dbc28aaa CD |
3900 | @item +work-boss |
3901 | Select headlines tagged @samp{:work:}, but discard those also tagged | |
3902 | @samp{:boss:}. | |
3903 | @item work|laptop | |
3904 | Selects lines tagged @samp{:work:} or @samp{:laptop:}. | |
3905 | @item work|laptop&night | |
3906 | Like before, but require the @samp{:laptop:} lines to be tagged also | |
3907 | @samp{:night:}. | |
4009494e GM |
3908 | @end table |
3909 | ||
3910 | @cindex TODO keyword matching, with tags search | |
e45e3595 CD |
3911 | You may also test for TODO keywords (@pxref{TODO extensions}) and properties |
3912 | (@pxref{Properties and Columns}) at the same time as matching tags. For a | |
3913 | guide on how to match properties, see @ref{Property searches}. To match a | |
3914 | specific TODO keyword, include an expression like @samp{+TODO="NEXT"} as one | |
3915 | of the terms in a tags search. | |
3916 | ||
3917 | There is also the possibility to end the tags part of the match (which may | |
3918 | include several terms connected with @samp{|}) with a @samp{/} and then | |
3919 | specify a Boolean expression just for TODO keywords. The syntax is then | |
3920 | similar to the tag matches, but should be applied with consideration: For | |
3921 | example, a positive selection on several TODO keywords can not meaningfully | |
3922 | be combined with boolean AND. However, @emph{negative selection} combined | |
3923 | with AND can be meaningful. To make sure that only lines are checked that | |
3924 | actually have any TODO keyword (resulting in a speed-up), use @kbd{C-c a M}, | |
3925 | or equivalently start the TODO part after the slash with @samp{!}. Examples: | |
4009494e GM |
3926 | |
3927 | @table @samp | |
e45e3595 | 3928 | @item work+TODO="WAITING" |
dbc28aaa | 3929 | Select @samp{:work:}-tagged TODO lines with the specific TODO |
4009494e | 3930 | keyword @samp{WAITING}. |
e45e3595 CD |
3931 | @item work+TODO="WAITING"|home+TODO="WAITING" |
3932 | Waiting tasks both at work and at home. | |
3933 | @item work/WAITING | |
3934 | Same as the first example. | |
dbc28aaa CD |
3935 | @item work/!-WAITING-NEXT |
3936 | Select @samp{:work:}-tagged TODO lines that are neither @samp{WAITING} | |
4009494e | 3937 | nor @samp{NEXT} |
e45e3595 | 3938 | @item work/!+WAITING|+NEXT |
dbc28aaa | 3939 | Select @samp{:work:}-tagged TODO lines that are either @samp{WAITING} or |
4009494e GM |
3940 | @samp{NEXT}. |
3941 | @end table | |
3942 | ||
3943 | @cindex regular expressions, with tags search | |
3944 | Any element of the tag/todo match can be a regular expression - in this | |
3945 | case it must be enclosed in curly braces. For example, | |
dbc28aaa | 3946 | @samp{work+@{^boss.*@}} matches headlines that contain the tag |
e45e3595 CD |
3947 | @samp{:work:} and any tag @i{starting} with @samp{boss}. You may also use a |
3948 | regular expression in @samp{TODO=@{^W@}} which would match TODO keywords | |
3949 | starting with the letter @samp{W}. | |
dbc28aaa CD |
3950 | |
3951 | @cindex level, require for tags/property match | |
3952 | @cindex category, require for tags/property match | |
3953 | You can also require a headline to be of a certain level or category, by | |
3954 | writing instead of any TAG an expression like @samp{LEVEL=3} or | |
3955 | @samp{CATEGORY="work"}, respectively. For example, a search | |
3956 | @samp{+LEVEL=3+boss/-DONE} lists all level three headlines that have the | |
a7808fba | 3957 | tag @samp{boss} and are @emph{not} marked with the TODO keyword DONE. |
dbc28aaa | 3958 | |
e45e3595 CD |
3959 | Accessing TODO, LEVEL, and CATEGORY during a search is fast. Accessing any |
3960 | other properties will slow down the search. | |
3961 | ||
a7808fba | 3962 | @node Properties and Columns, Dates and Times, Tags, Top |
4009494e GM |
3963 | @chapter Properties and Columns |
3964 | @cindex properties | |
3965 | ||
3966 | Properties are a set of key-value pairs associated with an entry. There | |
a7808fba | 3967 | are two main applications for properties in Org mode. First, properties |
dbc28aaa | 3968 | are like tags, but with a value. Second, you can use properties to |
a7808fba | 3969 | implement (very basic) database capabilities in an Org buffer. For |
dbc28aaa CD |
3970 | an example of the first application, imagine maintaining a file where |
3971 | you document bugs and plan releases of a piece of software. Instead of | |
3972 | using tags like @code{:release_1:}, @code{:release_2:}, one can use a | |
3973 | property, say @code{:Release:}, that in different subtrees has different | |
3974 | values, such as @code{1.0} or @code{2.0}. For an example of the second | |
a50253cc | 3975 | application of properties, imagine keeping track of your music CDs, |
dbc28aaa CD |
3976 | where properties could be things such as the album artist, date of |
3977 | release, number of tracks, and so on. | |
3978 | ||
28a16a1b | 3979 | Properties can be conveniently edited and viewed in column view |
dbc28aaa CD |
3980 | (@pxref{Column view}). |
3981 | ||
4009494e GM |
3982 | @menu |
3983 | * Property syntax:: How properties are spelled out | |
a7808fba | 3984 | * Special properties:: Access to other Org mode features |
4009494e | 3985 | * Property searches:: Matching property values |
dbc28aaa | 3986 | * Property inheritance:: Passing values down the tree |
4009494e GM |
3987 | * Column view:: Tabular viewing and editing |
3988 | * Property API:: Properties for Lisp programmers | |
3989 | @end menu | |
3990 | ||
a7808fba CD |
3991 | @node Property syntax, Special properties, Properties and Columns, Properties and Columns |
3992 | @section Property syntax | |
4009494e GM |
3993 | @cindex property syntax |
3994 | @cindex drawer, for properties | |
3995 | ||
3996 | Properties are key-value pairs. They need to be inserted into a special | |
3997 | drawer (@pxref{Drawers}) with the name @code{PROPERTIES}. Each property | |
3998 | is specified on a single line, with the key (surrounded by colons) | |
3999 | first, and the value after it. Here is an example: | |
4000 | ||
4001 | @example | |
4002 | * CD collection | |
4003 | ** Classic | |
4004 | *** Goldberg Variations | |
4005 | :PROPERTIES: | |
4006 | :Title: Goldberg Variations | |
4007 | :Composer: J.S. Bach | |
28a16a1b | 4008 | :Artist: Glen Gould |
4009494e GM |
4009 | :Publisher: Deutsche Grammphon |
4010 | :NDisks: 1 | |
28a16a1b | 4011 | :END: |
4009494e GM |
4012 | @end example |
4013 | ||
dbc28aaa CD |
4014 | You may define the allowed values for a particular property @samp{:Xyz:} |
4015 | by setting a property @samp{:Xyz_ALL:}. This special property is | |
4009494e GM |
4016 | @emph{inherited}, so if you set it in a level 1 entry, it will apply to |
4017 | the entire tree. When allowed values are defined, setting the | |
4018 | corresponding property becomes easier and is less prone to typing | |
4019 | errors. For the example with the CD collection, we can predefine | |
4020 | publishers and the number of disks in a box like this: | |
4021 | ||
4022 | @example | |
4023 | * CD collection | |
4024 | :PROPERTIES: | |
4025 | :NDisks_ALL: 1 2 3 4 | |
64fb801f | 4026 | :Publisher_ALL: "Deutsche Grammophon" Philips EMI |
4009494e GM |
4027 | :END: |
4028 | @end example | |
4029 | ||
4030 | If you want to set properties that can be inherited by any entry in a | |
4031 | file, use a line like | |
4032 | ||
4033 | @example | |
4034 | #+PROPERTY: NDisks_ALL 1 2 3 4 | |
4035 | @end example | |
4036 | ||
4037 | Property values set with the global variable | |
4038 | @code{org-global-properties} can be inherited by all entries in all | |
a7808fba | 4039 | Org files. |
4009494e GM |
4040 | |
4041 | @noindent | |
4042 | The following commands help to work with properties: | |
4043 | ||
4044 | @table @kbd | |
4045 | @kindex M-@key{TAB} | |
4046 | @item M-@key{TAB} | |
4047 | After an initial colon in a line, complete property keys. All keys used | |
4048 | in the current file will be offered as possible completions. | |
dbc28aaa CD |
4049 | @kindex C-c C-x p |
4050 | @item C-c C-x p | |
4051 | Set a property. This prompts for a property name and a value. If | |
4052 | necessary, the property drawer is created as well. | |
4009494e GM |
4053 | @item M-x org-insert-property-drawer |
4054 | Insert a property drawer into the current entry. The drawer will be | |
4055 | inserted early in the entry, but after the lines with planning | |
4056 | information like deadlines. | |
4057 | @kindex C-c C-c | |
4058 | @item C-c C-c | |
4059 | With the cursor in a property drawer, this executes property commands. | |
4060 | @item C-c C-c s | |
4061 | Set a property in the current entry. Both the property and the value | |
4062 | can be inserted using completion. | |
4063 | @kindex S-@key{right} | |
4064 | @kindex S-@key{left} | |
4065 | @item S-@key{left}/@key{right} | |
4066 | Switch property at point to the next/previous allowed value. | |
4067 | @item C-c C-c d | |
4068 | Remove a property from the current entry. | |
4069 | @item C-c C-c D | |
4070 | Globally remove a property, from all entries in the current file. | |
dbc28aaa CD |
4071 | @item C-c C-c c |
4072 | Compute the property at point, using the operator and scope from the | |
4073 | nearest column format definition. | |
4009494e GM |
4074 | @end table |
4075 | ||
a7808fba CD |
4076 | @node Special properties, Property searches, Property syntax, Properties and Columns |
4077 | @section Special properties | |
4009494e GM |
4078 | @cindex properties, special |
4079 | ||
a7808fba | 4080 | Special properties provide alternative access method to Org mode |
4009494e GM |
4081 | features discussed in the previous chapters, like the TODO state or the |
4082 | priority of an entry. This interface exists so that you can include | |
dbc28aaa CD |
4083 | these states into columns view (@pxref{Column view}), or to use them in |
4084 | queries. The following property names are special and should not be | |
4085 | used as keys in the properties drawer: | |
4009494e GM |
4086 | |
4087 | @example | |
4088 | TODO @r{The TODO keyword of the entry.} | |
4089 | TAGS @r{The tags defined directly in the headline.} | |
4090 | ALLTAGS @r{All tags, including inherited ones.} | |
4091 | PRIORITY @r{The priority of the entry, a string with a single letter.} | |
4092 | DEADLINE @r{The deadline time string, without the angular brackets.} | |
4093 | SCHEDULED @r{The scheduling time stamp, without the angular brackets.} | |
dbc28aaa CD |
4094 | TIMESTAMP @r{The first keyword-less time stamp in the entry.} |
4095 | TIMESTAMP_IA @r{The first inactive time stamp in the entry.} | |
4096 | CLOCKSUM @r{The sum of CLOCK intervals in the subtree. @code{org-clock-sum}} | |
4097 | @r{must be run first to compute the values.} | |
4009494e GM |
4098 | @end example |
4099 | ||
a7808fba | 4100 | @node Property searches, Property inheritance, Special properties, Properties and Columns |
4009494e GM |
4101 | @section Property searches |
4102 | @cindex properties, searching | |
dbc28aaa | 4103 | @cindex searching, of properties |
4009494e | 4104 | |
a7808fba CD |
4105 | To create sparse trees and special lists with selection based on properties, |
4106 | the same commands are used as for tag searches (@pxref{Tag searches}), and | |
4107 | the same logic applies. For example, here is a search string: | |
4009494e GM |
4108 | |
4109 | @example | |
44ce9197 CD |
4110 | +work-boss+PRIORITY="A"+Coffee="unlimited"+Effort<2 \ |
4111 | +With=@{Sarah\|Denny@}+SCHEDULED>="<2008-10-11>" | |
4009494e GM |
4112 | @end example |
4113 | ||
4114 | @noindent | |
44ce9197 CD |
4115 | The type of comparison will depend on how the comparison value is written: |
4116 | @itemize @minus | |
4117 | @item | |
a7808fba CD |
4118 | If the comparison value is a plain number, a numerical comparison is done, |
4119 | and the allowed operators are @samp{<}, @samp{=}, @samp{>}, @samp{<=}, | |
44ce9197 CD |
4120 | @samp{>=}, and @samp{<>}. |
4121 | @item | |
4122 | If the comparison value is enclosed in double | |
96c8522a | 4123 | quotes, a string comparison is done, and the same operators are allowed. |
44ce9197 CD |
4124 | @item |
4125 | If the comparison value is enclosed in double quotes @emph{and} angular | |
4126 | brackets (like @samp{DEADLINE<="<2008-12-24 18:30>"}), both values are | |
96c8522a CD |
4127 | assumed to be date/time specifications in the standard Org way, and the |
4128 | comparison will be done accordingly. Special values that will be recognized | |
4129 | are @code{"<now>"} for now (including time), and @code{"<today>"}, and | |
4130 | @code{"<tomorrow>"} for these days at 0:00 hours, i.e. without a time | |
4131 | specification. Also strings like @code{"<+5d>"} or @code{"<-2m>"} with units | |
4132 | @code{d}, @code{w}, @code{m}, and @code{y} for day, week, month, and year, | |
4133 | respectively, can be used. | |
44ce9197 CD |
4134 | @item |
4135 | If the comparison value is enclosed | |
4136 | in curly braces, a regexp match is performed, with @samp{=} meaning that the | |
4137 | regexp matches the property value, and @samp{<>} meaning that it does not | |
96c8522a | 4138 | match. |
44ce9197 CD |
4139 | @end itemize |
4140 | ||
4141 | So the search string in the example finds entries tagged @samp{:work:} but | |
4142 | not @samp{:boss:}, which also have a priority value @samp{A}, a | |
4143 | @samp{:Coffee:} property with the value @samp{unlimited}, an @samp{Effort} | |
4144 | property that is numerically smaller than 2, a @samp{:With:} property that is | |
4145 | matched by the regular expression @samp{Sarah\|Denny}, and that are scheduled | |
4146 | on or after October 11, 2008. | |
a7808fba CD |
4147 | |
4148 | You can configure Org mode to use property inheritance during a search, but | |
4149 | beware that this can slow down searches considerably. See @ref{Property | |
4150 | inheritance} for details. | |
dbc28aaa CD |
4151 | |
4152 | There is also a special command for creating sparse trees based on a | |
4153 | single property: | |
4154 | ||
4155 | @table @kbd | |
4156 | @kindex C-c / p | |
4157 | @item C-c / p | |
4158 | Create a sparse tree based on the value of a property. This first | |
4159 | prompts for the name of a property, and then for a value. A sparse tree | |
4160 | is created with all entries that define this property with the given | |
4161 | value. If you enclose the value into curly braces, it is interpreted as | |
4162 | a regular expression and matched against the property values. | |
4163 | @end table | |
4164 | ||
a7808fba | 4165 | @node Property inheritance, Column view, Property searches, Properties and Columns |
dbc28aaa | 4166 | @section Property Inheritance |
a7808fba CD |
4167 | @cindex properties, inheritance |
4168 | @cindex inheritance, of properties | |
dbc28aaa | 4169 | |
a7808fba | 4170 | The outline structure of Org mode documents lends itself for an |
dbc28aaa | 4171 | inheritance model of properties: If the parent in a tree has a certain |
a7808fba | 4172 | property, the children can inherit this property. Org mode does not |
dbc28aaa CD |
4173 | turn this on by default, because it can slow down property searches |
4174 | significantly and is often not needed. However, if you find inheritance | |
4175 | useful, you can turn it on by setting the variable | |
4176 | @code{org-use-property-inheritance}. It may be set to @code{t}, to make | |
a7808fba CD |
4177 | all properties inherited from the parent, to a list of properties |
4178 | that should be inherited, or to a regular expression that matches | |
4179 | inherited properties. | |
dbc28aaa | 4180 | |
a7808fba | 4181 | Org mode has a few properties for which inheritance is hard-coded, at |
dbc28aaa CD |
4182 | least for the special applications for which they are used: |
4183 | ||
4184 | @table @code | |
4185 | @item COLUMNS | |
4186 | The @code{:COLUMNS:} property defines the format of column view | |
4187 | (@pxref{Column view}). It is inherited in the sense that the level | |
4188 | where a @code{:COLUMNS:} property is defined is used as the starting | |
4189 | point for a column view table, independently of the location in the | |
4190 | subtree from where columns view is turned on. | |
4191 | @item CATEGORY | |
4192 | For agenda view, a category set through a @code{:CATEGORY:} property | |
4193 | applies to the entire subtree. | |
4194 | @item ARCHIVE | |
4195 | For archiving, the @code{:ARCHIVE:} property may define the archive | |
4196 | location for the entire subtree (@pxref{Moving subtrees}). | |
28a16a1b CD |
4197 | @item LOGGING |
4198 | The LOGGING property may define logging settings for an entry or a | |
4199 | subtree (@pxref{Tracking TODO state changes}). | |
dbc28aaa CD |
4200 | @end table |
4201 | ||
a7808fba CD |
4202 | @node Column view, Property API, Property inheritance, Properties and Columns |
4203 | @section Column view | |
4009494e GM |
4204 | |
4205 | A great way to view and edit properties in an outline tree is | |
4206 | @emph{column view}. In column view, each outline item is turned into a | |
4207 | table row. Columns in this table provide access to properties of the | |
a7808fba | 4208 | entries. Org mode implements columns by overlaying a tabular structure |
4009494e GM |
4209 | over the headline of each item. While the headlines have been turned |
4210 | into a table row, you can still change the visibility of the outline | |
4211 | tree. For example, you get a compact table by switching to CONTENTS | |
4212 | view (@kbd{S-@key{TAB} S-@key{TAB}}, or simply @kbd{c} while column view | |
4213 | is active), but you can still open, read, and edit the entry below each | |
4214 | headline. Or, you can switch to column view after executing a sparse | |
4215 | tree command and in this way get a table only for the selected items. | |
a7808fba | 4216 | Column view also works in agenda buffers (@pxref{Agenda Views}) where |
4009494e GM |
4217 | queries have collected selected items, possibly from a number of files. |
4218 | ||
4219 | @menu | |
4220 | * Defining columns:: The COLUMNS format property | |
4221 | * Using column view:: How to create and use column view | |
a7808fba | 4222 | * Capturing column view:: A dynamic block for column view |
4009494e GM |
4223 | @end menu |
4224 | ||
4225 | @node Defining columns, Using column view, Column view, Column view | |
a7808fba | 4226 | @subsection Defining columns |
4009494e GM |
4227 | @cindex column view, for properties |
4228 | @cindex properties, column view | |
4229 | ||
4230 | Setting up a column view first requires defining the columns. This is | |
4231 | done by defining a column format line. | |
4232 | ||
4233 | @menu | |
4234 | * Scope of column definitions:: Where defined, where valid? | |
4235 | * Column attributes:: Appearance and content of a column | |
4236 | @end menu | |
4237 | ||
4238 | @node Scope of column definitions, Column attributes, Defining columns, Defining columns | |
4239 | @subsubsection Scope of column definitions | |
4240 | ||
4241 | To define a column format for an entire file, use a line like | |
4242 | ||
4243 | @example | |
4244 | #+COLUMNS: %25ITEM %TAGS %PRIORITY %TODO | |
4245 | @end example | |
4246 | ||
dbc28aaa CD |
4247 | To specify a format that only applies to a specific tree, add a |
4248 | @code{:COLUMNS:} property to the top node of that tree, for example: | |
4249 | ||
4009494e GM |
4250 | @example |
4251 | ** Top node for columns view | |
4252 | :PROPERTIES: | |
4253 | :COLUMNS: %25ITEM %TAGS %PRIORITY %TODO | |
4254 | :END: | |
4255 | @end example | |
4256 | ||
dbc28aaa | 4257 | If a @code{:COLUMNS:} property is present in an entry, it defines columns |
4009494e GM |
4258 | for the entry itself, and for the entire subtree below it. Since the |
4259 | column definition is part of the hierarchical structure of the document, | |
4260 | you can define columns on level 1 that are general enough for all | |
4261 | sublevels, and more specific columns further down, when you edit a | |
4262 | deeper part of the tree. | |
4263 | ||
4264 | @node Column attributes, , Scope of column definitions, Defining columns | |
4265 | @subsubsection Column attributes | |
4266 | A column definition sets the attributes of a column. The general | |
4267 | definition looks like this: | |
4268 | ||
4269 | @example | |
4270 | %[width]property[(title)][@{summary-type@}] | |
4271 | @end example | |
4272 | ||
4273 | @noindent | |
4274 | Except for the percent sign and the property name, all items are | |
4275 | optional. The individual parts have the following meaning: | |
4276 | ||
4277 | @example | |
4278 | width @r{An integer specifying the width of the column in characters.} | |
4279 | @r{If omitted, the width will be determined automatically.} | |
4280 | property @r{The property that should be edited in this column.} | |
4281 | (title) @r{The header text for the column. If omitted, the} | |
4282 | @r{property name is used.} | |
4283 | @{summary-type@} @r{The summary type. If specified, the column values for} | |
4284 | @r{parent nodes are computed from the children.} | |
4285 | @r{Supported summary types are:} | |
dbc28aaa CD |
4286 | @{+@} @r{Sum numbers in this column.} |
4287 | @{+;%.1f@} @r{Like @samp{+}, but format result with @samp{%.1f}.} | |
4288 | @{$@} @r{Currency, short for @samp{+;%.2f}.} | |
4289 | @{:@} @r{Sum times, HH:MM:SS, plain numbers are hours.} | |
4290 | @{X@} @r{Checkbox status, [X] if all children are [X].} | |
28a16a1b CD |
4291 | @{X/@} @r{Checkbox status, [n/m].} |
4292 | @{X%@} @r{Checkbox status, [n%].} | |
4009494e GM |
4293 | @end example |
4294 | ||
4295 | @noindent | |
4296 | Here is an example for a complete columns definition, along with allowed | |
4297 | values. | |
4298 | ||
4299 | @example | |
dbc28aaa CD |
4300 | :COLUMNS: %20ITEM %9Approved(Approved?)@{X@} %Owner %11Status \@footnote{Please note that the COLUMNS definition must be on a single line - it is wrapped here only because of formatting constraints.} |
4301 | %10Time_Estimate@{:@} %CLOCKSUM | |
4009494e GM |
4302 | :Owner_ALL: Tammy Mark Karl Lisa Don |
4303 | :Status_ALL: "In progress" "Not started yet" "Finished" "" | |
4304 | :Approved_ALL: "[ ]" "[X]" | |
4305 | @end example | |
4306 | ||
4307 | The first column, @samp{%25ITEM}, means the first 25 characters of the | |
4308 | item itself, i.e. of the headline. You probably always should start the | |
28a16a1b CD |
4309 | column definition with the @samp{ITEM} specifier. The other specifiers |
4310 | create columns @samp{Owner} with a list of names as allowed values, for | |
4009494e GM |
4311 | @samp{Status} with four different possible values, and for a checkbox |
4312 | field @samp{Approved}. When no width is given after the @samp{%} | |
4313 | character, the column will be exactly as wide as it needs to be in order | |
4314 | to fully display all values. The @samp{Approved} column does have a | |
4315 | modified title (@samp{Approved?}, with a question mark). Summaries will | |
dbc28aaa | 4316 | be created for the @samp{Time_Estimate} column by adding time duration |
4009494e | 4317 | expressions like HH:MM, and for the @samp{Approved} column, by providing |
dbc28aaa CD |
4318 | an @samp{[X]} status if all children have been checked. The |
4319 | @samp{CLOCKSUM} column is special, it lists the sum of CLOCK intervals | |
4320 | in the subtree. | |
4009494e | 4321 | |
a7808fba CD |
4322 | @node Using column view, Capturing column view, Defining columns, Column view |
4323 | @subsection Using column view | |
4009494e GM |
4324 | |
4325 | @table @kbd | |
4326 | @tsubheading{Turning column view on and off} | |
4327 | @kindex C-c C-x C-c | |
4328 | @item C-c C-x C-c | |
4329 | Create the column view for the local environment. This command searches | |
dbc28aaa | 4330 | the hierarchy, up from point, for a @code{:COLUMNS:} property that defines |
4009494e | 4331 | a format. When one is found, the column view table is established for |
dbc28aaa | 4332 | the entire tree, starting from the entry that contains the @code{:COLUMNS:} |
4009494e GM |
4333 | property. If none is found, the format is taken from the @code{#+COLUMNS} |
4334 | line or from the variable @code{org-columns-default-format}, and column | |
4335 | view is established for the current entry and its subtree. | |
28a16a1b CD |
4336 | @kindex r |
4337 | @item r | |
a7808fba | 4338 | Recreate the column view, to include recent changes made in the buffer. |
28a16a1b CD |
4339 | @kindex g |
4340 | @item g | |
4341 | Same as @kbd{r}. | |
4009494e GM |
4342 | @kindex q |
4343 | @item q | |
4344 | Exit column view. | |
4345 | @tsubheading{Editing values} | |
4346 | @item @key{left} @key{right} @key{up} @key{down} | |
4347 | Move through the column view from field to field. | |
4348 | @kindex S-@key{left} | |
4349 | @kindex S-@key{right} | |
4350 | @item S-@key{left}/@key{right} | |
4351 | Switch to the next/previous allowed value of the field. For this, you | |
4352 | have to have specified allowed values for a property. | |
b349f79f CD |
4353 | @item 1..9,0 |
4354 | Directly select the nth allowed value, @kbd{0} selects the 10th value. | |
4009494e GM |
4355 | @kindex n |
4356 | @kindex p | |
4357 | @itemx n / p | |
4358 | Same as @kbd{S-@key{left}/@key{right}} | |
4359 | @kindex e | |
4360 | @item e | |
4361 | Edit the property at point. For the special properties, this will | |
4362 | invoke the same interface that you normally use to change that | |
4363 | property. For example, when editing a TAGS property, the tag completion | |
4364 | or fast selection interface will pop up. | |
dbc28aaa CD |
4365 | @kindex C-c C-c |
4366 | @item C-c C-c | |
4367 | When there is a checkbox at point, toggle it. | |
4009494e GM |
4368 | @kindex v |
4369 | @item v | |
4370 | View the full value of this property. This is useful if the width of | |
4371 | the column is smaller than that of the value. | |
4372 | @kindex a | |
4373 | @item a | |
4374 | Edit the list of allowed values for this property. If the list is found | |
4375 | in the hierarchy, the modified values is stored there. If no list is | |
4376 | found, the new value is stored in the first entry that is part of the | |
4377 | current column view. | |
4378 | @tsubheading{Modifying the table structure} | |
4379 | @kindex < | |
4380 | @kindex > | |
4381 | @item < / > | |
4382 | Make the column narrower/wider by one character. | |
4383 | @kindex S-M-@key{right} | |
4384 | @item S-M-@key{right} | |
864c9740 | 4385 | Insert a new column, to the left of the current column. |
4009494e GM |
4386 | @kindex S-M-@key{left} |
4387 | @item S-M-@key{left} | |
4388 | Delete the current column. | |
4389 | @end table | |
4390 | ||
a7808fba CD |
4391 | @node Capturing column view, , Using column view, Column view |
4392 | @subsection Capturing column view | |
dbc28aaa CD |
4393 | |
4394 | Since column view is just an overlay over a buffer, it cannot be | |
4395 | exported or printed directly. If you want to capture a column view, use | |
a7808fba | 4396 | this @code{columnview} dynamic block (@pxref{Dynamic blocks}). The frame |
28a16a1b | 4397 | of this block looks like this: |
dbc28aaa | 4398 | |
b349f79f | 4399 | @cindex #+BEGIN: columnview |
dbc28aaa CD |
4400 | @example |
4401 | * The column view | |
4402 | #+BEGIN: columnview :hlines 1 :id "label" | |
4403 | ||
4404 | #+END: | |
4405 | @end example | |
4406 | ||
4407 | @noindent This dynamic block has the following parameters: | |
4408 | ||
4409 | @table @code | |
4410 | @item :id | |
4411 | This is most important parameter. Column view is a feature that is | |
4412 | often localized to a certain (sub)tree, and the capture block might be | |
4413 | in a different location in the file. To identify the tree whose view to | |
4414 | capture, you can use 3 values: | |
4415 | @example | |
4416 | local @r{use the tree in which the capture block is located} | |
4417 | global @r{make a global view, including all headings in the file} | |
55e0839d CD |
4418 | "file:path-to-file" |
4419 | @r{run column view at the top of this file} | |
4420 | "ID" @r{call column view in the tree that has an @code{:ID:}} | |
b349f79f CD |
4421 | @r{property with the value @i{label}. You can use} |
4422 | @r{@kbd{M-x org-id-copy} to create a globally unique ID for} | |
4423 | @r{the current entry and copy it to the kill-ring.} | |
dbc28aaa CD |
4424 | @end example |
4425 | @item :hlines | |
4426 | When @code{t}, insert a hline after every line. When a number N, insert | |
4427 | a hline before each headline with level @code{<= N}. | |
4428 | @item :vlines | |
4429 | When set to @code{t}, enforce column groups to get vertical lines. | |
28a16a1b CD |
4430 | @item :maxlevel |
4431 | When set to a number, don't capture entries below this level. | |
4432 | @item :skip-empty-rows | |
4433 | When set to @code{t}, skip row where the only non-empty specifier of the | |
4434 | column view is @code{ITEM}. | |
4435 | ||
dbc28aaa CD |
4436 | @end table |
4437 | ||
4438 | @noindent | |
4439 | The following commands insert or update the dynamic block: | |
4440 | ||
4441 | @table @kbd | |
864c9740 CD |
4442 | @kindex C-c C-x i |
4443 | @item C-c C-x i | |
dbc28aaa CD |
4444 | Insert a dynamic block capturing a column view. You will be prompted |
4445 | for the scope or id of the view. | |
4446 | @kindex C-c C-c | |
4447 | @item C-c C-c | |
4448 | @kindex C-c C-x C-u | |
4449 | @itemx C-c C-x C-u | |
4450 | Update dynamical block at point. The cursor needs to be in the | |
4451 | @code{#+BEGIN} line of the dynamic block. | |
4452 | @kindex C-u C-c C-x C-u | |
4453 | @item C-u C-c C-x C-u | |
4454 | Update all dynamic blocks (@pxref{Dynamic blocks}). This is useful if | |
a7808fba | 4455 | you have several clock table blocks in a buffer. |
dbc28aaa CD |
4456 | @end table |
4457 | ||
864c9740 CD |
4458 | You can add formulas to the column view table and you may add plotting |
4459 | instructions in front of the table - these will survive an update of the | |
4460 | block. If there is a @code{#+TBLFM:} after the table, the table will | |
4461 | actually be recalculated automatically after an update. | |
4462 | ||
a7808fba | 4463 | @node Property API, , Column view, Properties and Columns |
4009494e GM |
4464 | @section The Property API |
4465 | @cindex properties, API | |
4466 | @cindex API, for properties | |
4467 | ||
4468 | There is a full API for accessing and changing properties. This API can | |
4469 | be used by Emacs Lisp programs to work with properties and to implement | |
4470 | features based on them. For more information see @ref{Using the | |
4471 | property API}. | |
4472 | ||
864c9740 | 4473 | @node Dates and Times, Capture, Properties and Columns, Top |
dbc28aaa CD |
4474 | @chapter Dates and Times |
4475 | @cindex dates | |
4476 | @cindex times | |
4009494e GM |
4477 | @cindex time stamps |
4478 | @cindex date stamps | |
4479 | ||
dbc28aaa CD |
4480 | To assist project planning, TODO items can be labeled with a date and/or |
4481 | a time. The specially formatted string carrying the date and time | |
a7808fba | 4482 | information is called a @emph{timestamp} in Org mode. This may be a |
dbc28aaa | 4483 | little confusing because timestamp is often used as indicating when |
a7808fba | 4484 | something was created or last changed. However, in Org mode this term |
dbc28aaa | 4485 | is used in a much wider sense. |
4009494e GM |
4486 | |
4487 | @menu | |
a7808fba | 4488 | * Timestamps:: Assigning a time to a tree entry |
4009494e GM |
4489 | * Creating timestamps:: Commands which insert timestamps |
4490 | * Deadlines and scheduling:: Planning your work | |
a7808fba CD |
4491 | * Clocking work time:: Tracking how long you spend on a task |
4492 | * Effort estimates:: Planning work effort in advance | |
96c8522a | 4493 | * Relative timer:: Notes with a running timer |
4009494e GM |
4494 | @end menu |
4495 | ||
4496 | ||
a7808fba CD |
4497 | @node Timestamps, Creating timestamps, Dates and Times, Dates and Times |
4498 | @section Timestamps, deadlines and scheduling | |
4009494e GM |
4499 | @cindex time stamps |
4500 | @cindex ranges, time | |
4501 | @cindex date stamps | |
4502 | @cindex deadlines | |
4503 | @cindex scheduling | |
4504 | ||
4505 | A time stamp is a specification of a date (possibly with time or a range | |
4506 | of times) in a special format, either @samp{<2003-09-16 Tue>} or | |
4507 | @samp{<2003-09-16 Tue 09:39>} or @samp{<2003-09-16 Tue | |
dbc28aaa CD |
4508 | 12:00-12:30>}@footnote{This is the standard ISO date/time format. To |
4509 | use an alternative format, see @ref{Custom time format}.}. A time stamp | |
a7808fba | 4510 | can appear anywhere in the headline or body of an Org tree entry. Its |
dbc28aaa | 4511 | presence causes entries to be shown on specific dates in the agenda |
a7808fba | 4512 | (@pxref{Weekly/daily agenda}). We distinguish: |
4009494e GM |
4513 | |
4514 | @table @var | |
dbc28aaa | 4515 | @item Plain time stamp; Event; Appointment |
4009494e GM |
4516 | @cindex timestamp |
4517 | A simple time stamp just assigns a date/time to an item. This is just | |
dbc28aaa CD |
4518 | like writing down an appointment or event in a paper agenda. In the |
4519 | timeline and agenda displays, the headline of an entry associated with a | |
4520 | plain time stamp will be shown exactly on that date. | |
4009494e GM |
4521 | |
4522 | @example | |
4523 | * Meet Peter at the movies <2006-11-01 Wed 19:15> | |
4524 | * Discussion on climate change <2006-11-02 Thu 20:00-22:00> | |
4525 | @end example | |
4526 | ||
4527 | @item Time stamp with repeater interval | |
4528 | @cindex timestamp, with repeater interval | |
4529 | A time stamp may contain a @emph{repeater interval}, indicating that it | |
4530 | applies not only on the given date, but again and again after a certain | |
4531 | interval of N days (d), weeks (w), months(m), or years(y). The | |
4532 | following will show up in the agenda every Wednesday: | |
4533 | ||
4534 | @example | |
4535 | * Pick up Sam at school <2007-05-16 Wed 12:30 +1w> | |
4536 | @end example | |
4537 | ||
4538 | @item Diary-style sexp entries | |
a7808fba | 4539 | For more complex date specifications, Org mode supports using the |
4009494e GM |
4540 | special sexp diary entries implemented in the Emacs calendar/diary |
4541 | package. For example | |
4542 | ||
4543 | @example | |
4544 | * The nerd meeting on every 2nd Thursday of the month | |
4545 | <%%(diary-float t 4 2)> | |
4546 | @end example | |
4547 | ||
4548 | @item Time/Date range | |
4549 | @cindex timerange | |
4550 | @cindex date range | |
4551 | Two time stamps connected by @samp{--} denote a range. The headline | |
4552 | will be shown on the first and last day of the range, and on any dates | |
4553 | that are displayed and fall in the range. Here is an example: | |
4554 | ||
4555 | @example | |
4556 | ** Meeting in Amsterdam | |
4557 | <2004-08-23 Mon>--<2004-08-26 Thu> | |
4558 | @end example | |
4559 | ||
4560 | @item Inactive time stamp | |
4561 | @cindex timestamp, inactive | |
4562 | @cindex inactive timestamp | |
4563 | Just like a plain time stamp, but with square brackets instead of | |
4564 | angular ones. These time stamps are inactive in the sense that they do | |
4565 | @emph{not} trigger an entry to show up in the agenda. | |
4566 | ||
4567 | @example | |
4568 | * Gillian comes late for the fifth time [2006-11-01 Wed] | |
4569 | @end example | |
4570 | ||
4571 | @end table | |
4572 | ||
a7808fba | 4573 | @node Creating timestamps, Deadlines and scheduling, Timestamps, Dates and Times |
4009494e GM |
4574 | @section Creating timestamps |
4575 | @cindex creating timestamps | |
4576 | @cindex timestamps, creating | |
4577 | ||
a7808fba | 4578 | For Org mode to recognize time stamps, they need to be in the specific |
4009494e GM |
4579 | format. All commands listed below produce time stamps in the correct |
4580 | format. | |
4581 | ||
4582 | @table @kbd | |
4583 | @kindex C-c . | |
4584 | @item C-c . | |
864c9740 CD |
4585 | Prompt for a date and insert a corresponding time stamp. When the cursor is |
4586 | at an existing time stamp in the buffer, the command is used to modify this | |
4587 | timestamp instead of inserting a new one. When this command is used twice in | |
4588 | succession, a time range is inserted. | |
4009494e GM |
4589 | @c |
4590 | @kindex C-u C-c . | |
4591 | @item C-u C-c . | |
4592 | Like @kbd{C-c .}, but use the alternative format which contains date | |
4593 | and time. The default time can be rounded to multiples of 5 minutes, | |
4594 | see the option @code{org-time-stamp-rounding-minutes}. | |
4595 | @c | |
4596 | @kindex C-c ! | |
4597 | @item C-c ! | |
4598 | Like @kbd{C-c .}, but insert an inactive time stamp that will not cause | |
4599 | an agenda entry. | |
4600 | @c | |
4601 | @kindex C-c < | |
4602 | @item C-c < | |
4603 | Insert a time stamp corresponding to the cursor date in the Calendar. | |
4604 | @c | |
4605 | @kindex C-c > | |
4606 | @item C-c > | |
4607 | Access the Emacs calendar for the current date. If there is a | |
a7808fba | 4608 | timestamp in the current line, go to the corresponding date |
4009494e GM |
4609 | instead. |
4610 | @c | |
4611 | @kindex C-c C-o | |
4612 | @item C-c C-o | |
4613 | Access the agenda for the date given by the time stamp or -range at | |
a7808fba | 4614 | point (@pxref{Weekly/daily agenda}). |
4009494e GM |
4615 | @c |
4616 | @kindex S-@key{left} | |
4617 | @kindex S-@key{right} | |
4618 | @item S-@key{left} | |
4619 | @itemx S-@key{right} | |
4620 | Change date at cursor by one day. These key bindings conflict with | |
a7808fba | 4621 | CUA mode (@pxref{Conflicts}). |
4009494e GM |
4622 | @c |
4623 | @kindex S-@key{up} | |
4624 | @kindex S-@key{down} | |
4625 | @item S-@key{up} | |
4626 | @itemx S-@key{down} | |
4627 | Change the item under the cursor in a timestamp. The cursor can be on a | |
4628 | year, month, day, hour or minute. Note that if the cursor is in a | |
4629 | headline and not at a time stamp, these same keys modify the priority of | |
4630 | an item. (@pxref{Priorities}). The key bindings also conflict with | |
a7808fba | 4631 | CUA mode (@pxref{Conflicts}). |
4009494e GM |
4632 | @c |
4633 | @kindex C-c C-y | |
4634 | @cindex evaluate time range | |
4635 | @item C-c C-y | |
a7808fba CD |
4636 | Evaluate a time range by computing the difference between start and end. |
4637 | With a prefix argument, insert result after the time range (in a table: into | |
4638 | the following column). | |
4009494e GM |
4639 | @end table |
4640 | ||
4641 | ||
4642 | @menu | |
a7808fba CD |
4643 | * The date/time prompt:: How Org mode helps you entering date and time |
4644 | * Custom time format:: Making dates look different | |
4009494e GM |
4645 | @end menu |
4646 | ||
4647 | @node The date/time prompt, Custom time format, Creating timestamps, Creating timestamps | |
4648 | @subsection The date/time prompt | |
4649 | @cindex date, reading in minibuffer | |
4650 | @cindex time, reading in minibuffer | |
4651 | ||
a7808fba | 4652 | When Org mode prompts for a date/time, the default is shown as an ISO |
dbc28aaa CD |
4653 | date, and the prompt therefore seems to ask for an ISO date. But it |
4654 | will in fact accept any string containing some date and/or time | |
4655 | information, and it is really smart about interpreting your input. You | |
4656 | can, for example, use @kbd{C-y} to paste a (possibly multi-line) string | |
a7808fba | 4657 | copied from an email message. Org mode will find whatever information |
dbc28aaa CD |
4658 | is in there and derive anything you have not specified from the |
4659 | @emph{default date and time}. The default is usually the current date | |
4660 | and time, but when modifying an existing time stamp, or when entering | |
4661 | the second stamp of a range, it is taken from the stamp in the buffer. | |
a7808fba | 4662 | When filling in information, Org mode assumes that most of the time you |
dbc28aaa CD |
4663 | will want to enter a date in the future: If you omit the month/year and |
4664 | the given day/month is @i{before} today, it will assume that you mean a | |
4665 | future date@footnote{See the variable | |
4666 | @code{org-read-date-prefer-future}.}. | |
4667 | ||
07450bee | 4668 | For example, let's assume that today is @b{June 13, 2006}. Here is how |
a7808fba | 4669 | various inputs will be interpreted, the items filled in by Org mode are |
dbc28aaa CD |
4670 | in @b{bold}. |
4671 | ||
4672 | @example | |
4673 | 3-2-5 --> 2003-02-05 | |
4674 | 14 --> @b{2006}-@b{06}-14 | |
4675 | 12 --> @b{2006}-@b{07}-12 | |
4676 | Fri --> nearest Friday (defaultdate or later) | |
07450bee | 4677 | sep 15 --> @b{2006}-09-15 |
dbc28aaa CD |
4678 | feb 15 --> @b{2007}-02-15 |
4679 | sep 12 9 --> 2009-09-12 | |
4680 | 12:45 --> @b{2006}-@b{06}-@b{13} 12:45 | |
4681 | 22 sept 0:34 --> @b{2006}-09-22 0:34 | |
a7808fba CD |
4682 | w4 --> ISO week for of the current year @b{2006} |
4683 | 2012 w4 fri --> Friday of ISO week 4 in 2012 | |
4684 | 2012-w04-5 --> Same as above | |
dbc28aaa CD |
4685 | @end example |
4686 | ||
4687 | Furthermore you can specify a relative date by giving, as the | |
4688 | @emph{first} thing in the input: a plus/minus sign, a number and a | |
4689 | letter [dwmy] to indicate change in days weeks, months, years. With a | |
4690 | single plus or minus, the date is always relative to today. With a | |
4691 | double plus or minus, it is relative to the default date. If instead of | |
4692 | a single letter, you use the abbreviation of day name, the date will be | |
4693 | the nth such day. E.g. | |
4694 | ||
4695 | @example | |
b349f79f CD |
4696 | +0 --> today |
4697 | . --> today | |
dbc28aaa CD |
4698 | +4d --> four days from today |
4699 | +4 --> same as above | |
4700 | +2w --> two weeks from today | |
4701 | ++5 --> five days from default date | |
4702 | +2tue --> second tuesday from now. | |
4009494e GM |
4703 | @end example |
4704 | ||
4705 | The function understands English month and weekday abbreviations. If | |
4706 | you want to use unabbreviated names and/or other languages, configure | |
4707 | the variables @code{parse-time-months} and @code{parse-time-weekdays}. | |
4708 | ||
4709 | @cindex calendar, for selecting date | |
4710 | Parallel to the minibuffer prompt, a calendar is popped up@footnote{If | |
4711 | you don't need/want the calendar, configure the variable | |
4712 | @code{org-popup-calendar-for-date-prompt}.}. When you exit the date | |
4713 | prompt, either by clicking on a date in the calendar, or by pressing | |
4714 | @key{RET}, the date selected in the calendar will be combined with the | |
4715 | information entered at the prompt. You can control the calendar fully | |
4716 | from the minibuffer: | |
4717 | ||
4009494e | 4718 | @kindex < |
4009494e | 4719 | @kindex > |
4009494e | 4720 | @kindex mouse-1 |
4009494e | 4721 | @kindex S-@key{right} |
4009494e | 4722 | @kindex S-@key{left} |
4009494e | 4723 | @kindex S-@key{down} |
4009494e | 4724 | @kindex S-@key{up} |
4009494e | 4725 | @kindex M-S-@key{right} |
4009494e | 4726 | @kindex M-S-@key{left} |
4009494e | 4727 | @kindex @key{RET} |
dbc28aaa CD |
4728 | @example |
4729 | > / < @r{Scroll calendar forward/backward by one month.} | |
4730 | mouse-1 @r{Select date by clicking on it.} | |
4731 | S-@key{right}/@key{left} @r{One day forward/backward.} | |
4732 | S-@key{down}/@key{up} @r{One week forward/backward.} | |
4733 | M-S-@key{right}/@key{left} @r{One month forward/backward.} | |
4734 | @key{RET} @r{Choose date in calendar.} | |
4735 | @end example | |
4736 | ||
a7808fba CD |
4737 | The actions of the date/time prompt may seem complex, but I assure you they |
4738 | will grow on you, and you will start getting annoyed by pretty much any other | |
4739 | way of entering a date/time out there. To help you understand what is going | |
4740 | on, the current interpretation of your input will be displayed live in the | |
4741 | minibuffer@footnote{If you find this distracting, turn the display of with | |
4742 | @code{org-read-date-display-live}.}. | |
4009494e GM |
4743 | |
4744 | @node Custom time format, , The date/time prompt, Creating timestamps | |
4745 | @subsection Custom time format | |
4746 | @cindex custom date/time format | |
4747 | @cindex time format, custom | |
4748 | @cindex date format, custom | |
4749 | ||
a7808fba | 4750 | Org mode uses the standard ISO notation for dates and times as it is |
4009494e GM |
4751 | defined in ISO 8601. If you cannot get used to this and require another |
4752 | representation of date and time to keep you happy, you can get it by | |
4753 | customizing the variables @code{org-display-custom-times} and | |
4754 | @code{org-time-stamp-custom-formats}. | |
4755 | ||
4756 | @table @kbd | |
4757 | @kindex C-c C-x C-t | |
4758 | @item C-c C-x C-t | |
4759 | Toggle the display of custom formats for dates and times. | |
4760 | @end table | |
4761 | ||
4762 | @noindent | |
a7808fba | 4763 | Org mode needs the default format for scanning, so the custom date/time |
4009494e GM |
4764 | format does not @emph{replace} the default format - instead it is put |
4765 | @emph{over} the default format using text properties. This has the | |
4766 | following consequences: | |
4767 | @itemize @bullet | |
28a16a1b | 4768 | @item |
4009494e GM |
4769 | You cannot place the cursor onto a time stamp anymore, only before or |
4770 | after. | |
4771 | @item | |
4772 | The @kbd{S-@key{up}/@key{down}} keys can no longer be used to adjust | |
4773 | each component of a time stamp. If the cursor is at the beginning of | |
4774 | the stamp, @kbd{S-@key{up}/@key{down}} will change the stamp by one day, | |
4775 | just like @kbd{S-@key{left}/@key{right}}. At the end of the stamp, the | |
4776 | time will be changed by one minute. | |
4777 | @item | |
4778 | If the time stamp contains a range of clock times or a repeater, these | |
4779 | will not be overlayed, but remain in the buffer as they were. | |
4780 | @item | |
4781 | When you delete a time stamp character-by-character, it will only | |
4782 | disappear from the buffer after @emph{all} (invisible) characters | |
4783 | belonging to the ISO timestamp have been removed. | |
4784 | @item | |
4785 | If the custom time stamp format is longer than the default and you are | |
4786 | using dates in tables, table alignment will be messed up. If the custom | |
4787 | format is shorter, things do work as expected. | |
4788 | @end itemize | |
4789 | ||
4790 | ||
a7808fba CD |
4791 | @node Deadlines and scheduling, Clocking work time, Creating timestamps, Dates and Times |
4792 | @section Deadlines and scheduling | |
4009494e | 4793 | |
dbc28aaa | 4794 | A time stamp may be preceded by special keywords to facilitate planning: |
4009494e GM |
4795 | |
4796 | @table @var | |
4797 | @item DEADLINE | |
4798 | @cindex DEADLINE keyword | |
dbc28aaa CD |
4799 | |
4800 | Meaning: the task (most likely a TODO item, though not necessarily) is supposed | |
4801 | to be finished on that date. | |
4802 | ||
4803 | On the deadline date, the task will be listed in the agenda. In | |
4804 | addition, the agenda for @emph{today} will carry a warning about the | |
4805 | approaching or missed deadline, starting | |
4806 | @code{org-deadline-warning-days} before the due date, and continuing | |
4807 | until the entry is marked DONE. An example: | |
4009494e GM |
4808 | |
4809 | @example | |
4810 | *** TODO write article about the Earth for the Guide | |
4811 | The editor in charge is [[bbdb:Ford Prefect]] | |
4812 | DEADLINE: <2004-02-29 Sun> | |
4813 | @end example | |
4814 | ||
4815 | You can specify a different lead time for warnings for a specific | |
4816 | deadlines using the following syntax. Here is an example with a warning | |
4817 | period of 5 days @code{DEADLINE: <2004-02-29 Sun -5d>}. | |
4818 | ||
4819 | @item SCHEDULED | |
4820 | @cindex SCHEDULED keyword | |
dbc28aaa CD |
4821 | |
4822 | Meaning: you are planning to start working on that task on the given | |
4823 | date. | |
4824 | ||
4825 | The headline will be listed under the given date@footnote{It will still | |
4826 | be listed on that date after it has been marked DONE. If you don't like | |
4009494e GM |
4827 | this, set the variable @code{org-agenda-skip-scheduled-if-done}.}. In |
4828 | addition, a reminder that the scheduled date has passed will be present | |
4829 | in the compilation for @emph{today}, until the entry is marked DONE. | |
4830 | I.e., the task will automatically be forwarded until completed. | |
4831 | ||
4832 | @example | |
4833 | *** TODO Call Trillian for a date on New Years Eve. | |
4834 | SCHEDULED: <2004-12-25 Sat> | |
4835 | @end example | |
dbc28aaa CD |
4836 | |
4837 | @noindent | |
a7808fba | 4838 | @b{Important:} Scheduling an item in Org mode should @i{not} be |
dbc28aaa CD |
4839 | understood in the same way that we understand @i{scheduling a meeting}. |
4840 | Setting a date for a meeting is just a simple appointment, you should | |
4841 | mark this entry with a simple plain time stamp, to get this item shown | |
4842 | on the date where it applies. This is a frequent mis-understanding from | |
a7808fba | 4843 | Org-users. In Org mode, @i{scheduling} means setting a date when you |
dbc28aaa | 4844 | want to start working on an action item. |
4009494e GM |
4845 | @end table |
4846 | ||
dbc28aaa | 4847 | You may use time stamps with repeaters in scheduling and deadline |
a7808fba | 4848 | entries. Org mode will issue early and late warnings based on the |
dbc28aaa CD |
4849 | assumption that the time stamp represents the @i{nearest instance} of |
4850 | the repeater. However, the use of diary sexp entries like | |
4851 | @c | |
4852 | @code{<%%(diary-float t 42)>} | |
4853 | @c | |
a7808fba | 4854 | in scheduling and deadline timestamps is limited. Org mode does not |
dbc28aaa CD |
4855 | know enough about the internals of each sexp function to issue early and |
4856 | late warnings. However, it will show the item on each day where the | |
4857 | sexp entry matches. | |
4858 | ||
4009494e GM |
4859 | @menu |
4860 | * Inserting deadline/schedule:: Planning items | |
4861 | * Repeated tasks:: Items that show up again and again | |
4862 | @end menu | |
4863 | ||
4864 | @node Inserting deadline/schedule, Repeated tasks, Deadlines and scheduling, Deadlines and scheduling | |
a7808fba | 4865 | @subsection Inserting deadlines or schedules |
4009494e GM |
4866 | |
4867 | The following commands allow to quickly insert a deadline or to schedule | |
4868 | an item: | |
4869 | ||
4870 | @table @kbd | |
4871 | @c | |
4872 | @kindex C-c C-d | |
4873 | @item C-c C-d | |
4874 | Insert @samp{DEADLINE} keyword along with a stamp. The insertion will | |
dbc28aaa CD |
4875 | happen in the line directly following the headline. When called with a |
4876 | prefix arg, an existing deadline will be removed from the entry. | |
4009494e GM |
4877 | @c FIXME Any CLOSED timestamp will be removed.???????? |
4878 | @c | |
dbc28aaa | 4879 | @kindex C-c / d |
4009494e | 4880 | @cindex sparse tree, for deadlines |
dbc28aaa | 4881 | @item C-c / d |
4009494e GM |
4882 | Create a sparse tree with all deadlines that are either past-due, or |
4883 | which will become due within @code{org-deadline-warning-days}. | |
4884 | With @kbd{C-u} prefix, show all deadlines in the file. With a numeric | |
dbc28aaa | 4885 | prefix, check that many days. For example, @kbd{C-1 C-c / d} shows |
4009494e GM |
4886 | all deadlines due tomorrow. |
4887 | @c | |
4888 | @kindex C-c C-s | |
4889 | @item C-c C-s | |
4890 | Insert @samp{SCHEDULED} keyword along with a stamp. The insertion will | |
4891 | happen in the line directly following the headline. Any CLOSED | |
dbc28aaa CD |
4892 | timestamp will be removed. When called with a prefix argument, remove |
4893 | the scheduling date from the entry. | |
b349f79f CD |
4894 | @c |
4895 | @kindex C-c C-x C-k | |
4896 | @kindex k a | |
4897 | @kindex k s | |
4898 | @item C-c C-x C-k | |
4899 | Mark the current entry for agenda action. After you have marked the entry | |
4900 | like this, you can open the agenda or the calendar to find an appropriate | |
4901 | date. With the cursor on the selected date, press @kbd{k s} or @kbd{k d} to | |
4902 | schedule the marked item. | |
4009494e GM |
4903 | @end table |
4904 | ||
4905 | @node Repeated tasks, , Inserting deadline/schedule, Deadlines and scheduling | |
a7808fba | 4906 | @subsection Repeated tasks |
4009494e | 4907 | |
a7808fba | 4908 | Some tasks need to be repeated again and again. Org mode helps to |
28a16a1b CD |
4909 | organize such tasks using a so-called repeater in a DEADLINE, SCHEDULED, |
4910 | or plain time stamp. In the following example | |
4009494e GM |
4911 | @example |
4912 | ** TODO Pay the rent | |
4913 | DEADLINE: <2005-10-01 Sat +1m> | |
4914 | @end example | |
dbc28aaa CD |
4915 | the @code{+1m} is a repeater; the intended interpretation is that the |
4916 | task has a deadline on <2005-10-01> and repeats itself every (one) month | |
28a16a1b CD |
4917 | starting from that time. If you need both a repeater and a special |
4918 | warning period in a deadline entry, the repeater comes first and the | |
4919 | warning period last: @code{DEADLINE: <2005-10-01 Sat +1m -3d>}. | |
4009494e GM |
4920 | |
4921 | Deadlines and scheduled items produce entries in the agenda when they | |
4922 | are over-due, so it is important to be able to mark such an entry as | |
4923 | completed once you have done so. When you mark a DEADLINE or a SCHEDULE | |
a7808fba | 4924 | with the TODO keyword DONE, it will no longer produce entries in the |
28a16a1b | 4925 | agenda. The problem with this is, however, that then also the |
a7808fba | 4926 | @emph{next} instance of the repeated entry will not be active. Org mode |
4009494e GM |
4927 | deals with this in the following way: When you try to mark such an entry |
4928 | DONE (using @kbd{C-c C-t}), it will shift the base date of the repeating | |
4929 | time stamp by the repeater interval, and immediately set the entry state | |
4930 | back to TODO. In the example above, setting the state to DONE would | |
4931 | actually switch the date like this: | |
4932 | ||
4933 | @example | |
4934 | ** TODO Pay the rent | |
4935 | DEADLINE: <2005-11-01 Tue +1m> | |
4936 | @end example | |
4937 | ||
a7808fba CD |
4938 | A timestamp@footnote{You can change this using the option |
4939 | @code{org-log-repeat}, or the @code{#+STARTUP} options @code{logrepeat}, | |
4940 | @code{lognoterepeat}, and @code{nologrepeat}. With @code{lognoterepeat}, you | |
a50253cc | 4941 | will also be prompted for a note.} will be added under the deadline, to keep |
a7808fba | 4942 | a record that you actually acted on the previous instance of this deadline. |
4009494e GM |
4943 | |
4944 | As a consequence of shifting the base date, this entry will no longer be | |
4945 | visible in the agenda when checking past dates, but all future instances | |
4946 | will be visible. | |
4947 | ||
28a16a1b CD |
4948 | With the @samp{+1m} cookie, the date shift will always be exactly one |
4949 | month. So if you have not payed the rent for three months, marking this | |
4950 | entry DONE will still keep it as an overdue deadline. Depending on the | |
4951 | task, this may not be the best way to handle it. For example, if you | |
4952 | forgot to call you father for 3 weeks, it does not make sense to call | |
a7808fba | 4953 | him 3 times in a single day to make up for it. Finally, there are tasks |
28a16a1b | 4954 | like changing batteries which should always repeat a certain time |
a7808fba CD |
4955 | @i{after} the last time you did it. For these tasks, Org mode has |
4956 | special repeaters markers with @samp{++} and @samp{.+}. For example: | |
28a16a1b CD |
4957 | |
4958 | @example | |
4959 | ** TODO Call Father | |
4960 | DEADLINE: <2008-02-10 Sun ++1w> | |
4961 | Marking this DONE will shift the date by at least one week, | |
4962 | but also by as many weeks as it takes to get this date into | |
4963 | the future. However, it stays on a Sunday, even if you called | |
4964 | and marked it done on Saturday. | |
4965 | ** TODO Check the batteries in the smoke detectors | |
4966 | DEADLINE: <2005-11-01 Tue .+1m> | |
4967 | Marking this DONE will shift the date to one month after | |
4968 | today. | |
4969 | @end example | |
4970 | ||
4009494e GM |
4971 | You may have both scheduling and deadline information for a specific |
4972 | task - just make sure that the repeater intervals on both are the same. | |
4973 | ||
a7808fba | 4974 | @node Clocking work time, Effort estimates, Deadlines and scheduling, Dates and Times |
dbc28aaa | 4975 | @section Clocking work time |
4009494e | 4976 | |
a7808fba | 4977 | Org mode allows you to clock the time you spent on specific tasks in a |
4009494e GM |
4978 | project. When you start working on an item, you can start the clock. |
4979 | When you stop working on that task, or when you mark the task done, the | |
4980 | clock is stopped and the corresponding time interval is recorded. It | |
4981 | also computes the total time spent on each subtree of a project. | |
4982 | ||
4983 | @table @kbd | |
4984 | @kindex C-c C-x C-i | |
4985 | @item C-c C-x C-i | |
4986 | Start the clock on the current item (clock-in). This inserts the CLOCK | |
dbc28aaa CD |
4987 | keyword together with a timestamp. If this is not the first clocking of |
4988 | this item, the multiple CLOCK lines will be wrapped into a | |
4989 | @code{:CLOCK:} drawer (see also the variable | |
a7808fba CD |
4990 | @code{org-clock-into-drawer}). When called with a @kbd{C-u} prefix argument, |
4991 | select the task from a list of recently clocked tasks. With two @kbd{C-u | |
4992 | C-u} prefixes, clock into the task at point and mark it as the default task. | |
4993 | The default task will always be available when selecting a clocking task, | |
4994 | with letter @kbd{d}. | |
4009494e GM |
4995 | @kindex C-c C-x C-o |
4996 | @item C-c C-x C-o | |
a20d3598 | 4997 | Stop the clock (clock-out). This inserts another timestamp at the same |
4009494e GM |
4998 | location where the clock was last started. It also directly computes |
4999 | the resulting time in inserts it after the time range as @samp{=> | |
28a16a1b CD |
5000 | HH:MM}. See the variable @code{org-log-note-clock-out} for the |
5001 | possibility to record an additional note together with the clock-out | |
5002 | time stamp@footnote{The corresponding in-buffer setting is: | |
5003 | @code{#+STARTUP: lognoteclock-out}}. | |
4009494e GM |
5004 | @kindex C-c C-y |
5005 | @item C-c C-y | |
5006 | Recompute the time interval after changing one of the time stamps. This | |
5007 | is only necessary if you edit the time stamps directly. If you change | |
5008 | them with @kbd{S-@key{cursor}} keys, the update is automatic. | |
5009 | @kindex C-c C-t | |
5010 | @item C-c C-t | |
5011 | Changing the TODO state of an item to DONE automatically stops the clock | |
5012 | if it is running in this same item. | |
5013 | @kindex C-c C-x C-x | |
5014 | @item C-c C-x C-x | |
5015 | Cancel the current clock. This is useful if a clock was started by | |
5016 | mistake, or if you ended up working on something else. | |
dbc28aaa CD |
5017 | @kindex C-c C-x C-j |
5018 | @item C-c C-x C-j | |
a7808fba CD |
5019 | Jump to the entry that contains the currently running clock. With a |
5020 | @kbd{C-u} prefix arg, select the target task from a list of recently clocked | |
5021 | tasks. | |
4009494e GM |
5022 | @kindex C-c C-x C-d |
5023 | @item C-c C-x C-d | |
5024 | Display time summaries for each subtree in the current buffer. This | |
5025 | puts overlays at the end of each headline, showing the total time | |
5026 | recorded under that heading, including the time of any subheadings. You | |
5027 | can use visibility cycling to study the tree, but the overlays disappear | |
5028 | when you change the buffer (see variable | |
5029 | @code{org-remove-highlights-with-change}) or press @kbd{C-c C-c}. | |
5030 | @kindex C-c C-x C-r | |
5031 | @item C-c C-x C-r | |
5032 | Insert a dynamic block (@pxref{Dynamic blocks}) containing a clock | |
a7808fba | 5033 | report as an Org mode table into the current file. When the cursor is |
dbc28aaa CD |
5034 | at an existing clock table, just update it. When called with a prefix |
5035 | argument, jump to the first clock report in the current document and | |
5036 | update it. | |
b349f79f | 5037 | @cindex #+BEGIN: clocktable |
4009494e | 5038 | @example |
dbc28aaa | 5039 | #+BEGIN: clocktable :maxlevel 2 :emphasize nil :scope file |
4009494e GM |
5040 | #+END: clocktable |
5041 | @end example | |
5042 | @noindent | |
dbc28aaa CD |
5043 | If such a block already exists at point, its content is replaced by the |
5044 | new table. The @samp{BEGIN} line can specify options: | |
4009494e | 5045 | @example |
dbc28aaa | 5046 | :maxlevel @r{Maximum level depth to which times are listed in the table.} |
4009494e | 5047 | :emphasize @r{When @code{t}, emphasize level one and level two items} |
dbc28aaa CD |
5048 | :scope @r{The scope to consider. This can be any of the following:} |
5049 | nil @r{the current buffer or narrowed region} | |
5050 | file @r{the full current buffer} | |
5051 | subtree @r{the subtree where the clocktable is located} | |
5052 | treeN @r{the surrounding level N tree, for example @code{tree3}} | |
5053 | tree @r{the surrounding level 1 tree} | |
5054 | agenda @r{all agenda files} | |
5055 | ("file"..) @r{scan these files} | |
a7808fba CD |
5056 | file-with-archives @r{current file and its archives} |
5057 | agenda-with-archives @r{all agenda files, including archives} | |
5058 | :block @r{The time block to consider. This block is specified either} | |
5059 | @r{absolute, or relative to the current time and may be any of} | |
5060 | @r{these formats:} | |
5061 | 2007-12-31 @r{New year eve 2007} | |
5062 | 2007-12 @r{December 2007} | |
5063 | 2007-W50 @r{ISO-week 50 in 2007} | |
5064 | 2007 @r{the year 2007} | |
5065 | today, yesterday, today-N @r{a relative day} | |
5066 | thisweek, lastweek, thisweek-N @r{a relative week} | |
5067 | thismonth, lastmonth, thismonth-N @r{a relative month} | |
5068 | thisyear, lastyear, thisyear-N @r{a relative year} | |
5069 | @r{Use @kbd{S-@key{left}/@key{right}} keys to shift the time interval.} | |
4009494e GM |
5070 | :tstart @r{A time string specifying when to start considering times} |
5071 | :tend @r{A time string specifying when to stop considering times} | |
a7808fba CD |
5072 | :step @r{@code{week} or @code{day}, to split the table into chunks.} |
5073 | @r{To use this, @code{:block} or @code{:tstart}, @code{:tend} are needed.} | |
28a16a1b | 5074 | :link @r{Link the item headlines in the table to their origins} |
e45e3595 CD |
5075 | :formula @r{Content of a @code{#+TBLFM} line to be added and evaluated.} |
5076 | @r{As a special case, @samp{:formula %} adds column with % time.} | |
5077 | @r{If you do not specify a formula here, any existing formula} | |
5078 | @r{below the clock table will survive updates and be evaluated.} | |
4009494e | 5079 | @end example |
dbc28aaa CD |
5080 | So to get a clock summary of the current level 1 tree, for the current |
5081 | day, you could write | |
4009494e | 5082 | @example |
a7808fba | 5083 | #+BEGIN: clocktable :maxlevel 2 :block today :scope tree1 :link t |
4009494e GM |
5084 | #+END: clocktable |
5085 | @end example | |
5086 | and to use a specific time range you could write@footnote{Note that all | |
5087 | parameters must be specified in a single line - the line is broken here | |
5088 | only to fit it onto the manual.} | |
5089 | @example | |
28a16a1b | 5090 | #+BEGIN: clocktable :tstart "<2006-08-10 Thu 10:00>" |
4009494e | 5091 | :tend "<2006-08-10 Thu 12:00>" |
4009494e GM |
5092 | #+END: clocktable |
5093 | @end example | |
e45e3595 CD |
5094 | A summary of the current subtree with % times would be |
5095 | @example | |
5096 | #+BEGIN: clocktable :scope subtree :link t :formula % | |
5097 | #+END: clocktable | |
5098 | @end example | |
dbc28aaa CD |
5099 | @kindex C-c C-c |
5100 | @item C-c C-c | |
5101 | @kindex C-c C-x C-u | |
5102 | @itemx C-c C-x C-u | |
5103 | Update dynamical block at point. The cursor needs to be in the | |
5104 | @code{#+BEGIN} line of the dynamic block. | |
4009494e GM |
5105 | @kindex C-u C-c C-x C-u |
5106 | @item C-u C-c C-x C-u | |
5107 | Update all dynamic blocks (@pxref{Dynamic blocks}). This is useful if | |
a7808fba CD |
5108 | you have several clock table blocks in a buffer. |
5109 | @kindex S-@key{left} | |
5110 | @kindex S-@key{right} | |
5111 | @item S-@key{left} | |
5112 | @itemx S-@key{right} | |
5113 | Shift the current @code{:block} interval and update the table. The cursor | |
5114 | needs to be in the @code{#+BEGIN: clocktable} line for this command. If | |
5115 | @code{:block} is @code{today}, it will be shifted to @code{today-1} etc. | |
4009494e GM |
5116 | @end table |
5117 | ||
5118 | The @kbd{l} key may be used in the timeline (@pxref{Timeline}) and in | |
a7808fba | 5119 | the agenda (@pxref{Weekly/daily agenda}) to show which tasks have been |
4009494e GM |
5120 | worked on or closed during a day. |
5121 | ||
96c8522a | 5122 | @node Effort estimates, Relative timer, Clocking work time, Dates and Times |
a7808fba | 5123 | @section Effort estimates |
96c8522a | 5124 | @cindex effort estimates |
a7808fba CD |
5125 | |
5126 | If you want to plan your work in a very detailed way, or if you need to | |
5127 | produce offers with quotations of the estimated work effort, you may want to | |
5128 | assign effort estimates to entries. If you are also clocking your work, you | |
5129 | may later want to compare the planned effort with the actual working time, a | |
5130 | great way to improve planning estimates. Effort estimates are stored in a | |
5131 | special property @samp{Effort}@footnote{You may change the property being | |
5132 | used with the variable @code{org-effort-property}.}. Clearly the best way to | |
5133 | work with effort estimates is through column view (@pxref{Column view}). You | |
5134 | should start by setting up discrete values for effort estimates, and a | |
5135 | @code{COLUMNS} format that displays these values together with clock sums (if | |
5136 | you want to clock your time). For a specific buffer you can use | |
5137 | ||
5138 | @example | |
5139 | #+PROPERTY: Effort_ALL 0 0:10 0:30 1:00 2:00 3:00 4:00 5:00 6:00 7:00 8:00 | |
5140 | #+COLUMNS: %40ITEM(Task) %17Effort(Estimated Effort)@{:@} %CLOCKSUM | |
5141 | @end example | |
5142 | ||
5143 | @noindent | |
71d35b24 CD |
5144 | or, even better, you can set up these values globally by customizing the |
5145 | variables @code{org-global-properties} and @code{org-columns-default-format}. | |
5146 | In particular if you want to use this setup also in the agenda, a global | |
5147 | setup may be advised. | |
a7808fba CD |
5148 | |
5149 | The way to assign estimates to individual items is then to switch to column | |
5150 | mode, and to use @kbd{S-@key{right}} and @kbd{S-@key{left}} to change the | |
5151 | value. The values you enter will immediately be summed up in the hierarchy. | |
5152 | In the column next to it, any clocked time will be displayed. | |
5153 | ||
5154 | If you switch to column view in the daily/weekly agenda, the effort column | |
5155 | will summarize the estimated work effort for each day@footnote{Please note | |
5156 | the pitfalls of summing hierarchical data in a flat list (@pxref{Agenda | |
b349f79f | 5157 | column view}).}, and you can use this to find space in your schedule. To get |
a7808fba CD |
5158 | an overview of the entire part of the day that is committed, you can set the |
5159 | option @code{org-agenda-columns-add-appointments-to-effort-sum}. The | |
5160 | appointments on a day that take place over a specified time interval will | |
5161 | then also be added to the load estimate of the day. | |
5162 | ||
71d35b24 CD |
5163 | Effort estimates can be used in secondary agenda filtering that is triggered |
5164 | with the @kbd{/} key in the agenda (@pxref{Agenda commands}). If you have | |
5165 | these estimates defined consistently, two or three key presses will narrow | |
5166 | down the list to stuff that fits into an available time slot. | |
864c9740 | 5167 | |
96c8522a CD |
5168 | @node Relative timer, , Effort estimates, Dates and Times |
5169 | @section Taking notes with a relative timer | |
5170 | @cindex relative timer | |
5171 | ||
5172 | When taking notes during, for example, a meeting or a video viewing, it can | |
5173 | be useful to have access to times relative to a starting time. Org provides | |
5174 | such a relative timer and make it easy to create timed notes. | |
5175 | ||
5176 | @table @kbd | |
5177 | @kindex C-c C-x . | |
5178 | @item C-c C-x . | |
5179 | Insert a relative time into the buffer. The first time you use this, the | |
5180 | timer will be started. When called with a prefix argument, the timer is | |
5181 | restarted. | |
5182 | @kindex C-c C-x - | |
5183 | @item C-c C-x - | |
5184 | Insert a description list item with the current relative time. With a prefix | |
5185 | argument, first reset the timer to 0. | |
5186 | @kindex M-@key{RET} | |
5187 | @item M-@key{RET} | |
377952e0 | 5188 | Once the timer list is started, you can also use @kbd{M-@key{RET}} to insert |
96c8522a | 5189 | new timer items. |
55e0839d CD |
5190 | @kindex C-c C-x , |
5191 | @item C-c C-x , | |
5192 | Pause the timer, or continue it if it is already paused. With prefix | |
5193 | argument, stop it entirely. | |
5194 | @kindex C-u C-c C-x , | |
5195 | @item C-u C-c C-x , | |
5196 | Stop the timer. After this, you can only start a new timer, not continue the | |
5197 | old one. This command also removes the timer from the mode line. | |
96c8522a CD |
5198 | @kindex C-c C-x 0 |
5199 | @item C-c C-x 0 | |
5200 | Reset the timer without inserting anything into the buffer. By default, the | |
5201 | timer is reset to 0. When called with a @kbd{C-u} prefix, reset the timer to | |
5202 | specific starting offset. The user is prompted for the offset, with a | |
5203 | default taken from a timer string at point, if any, So this can be used to | |
5204 | restart taking notes after a break in the process. When called with a double | |
5205 | prefix argument @kbd{C-c C-u}, change all timer strings in the active region | |
5206 | by a certain amount. This can be used to fix timer strings if the timer was | |
5207 | not started at exactly the right moment. | |
5208 | @end table | |
5209 | ||
864c9740 CD |
5210 | @node Capture, Agenda Views, Dates and Times, Top |
5211 | @chapter Capture | |
5212 | @cindex capture | |
5213 | ||
5214 | An important part of any organization system is the ability to quickly | |
5215 | capture new ideas and tasks, and to associate reference material with them. | |
5216 | Org uses the @file{remember} package to create tasks, and stores files | |
5217 | related to a task (@i{attachments}) in a special directory. | |
5218 | ||
5219 | @menu | |
5220 | * Remember:: Capture new tasks/ideas with little interruption | |
5221 | * Attachments:: Add files to tasks. | |
5222 | @end menu | |
5223 | ||
5224 | @node Remember, Attachments, Capture, Capture | |
5225 | @section Remember | |
dbc28aaa CD |
5226 | @cindex @file{remember.el} |
5227 | ||
5228 | The @i{Remember} package by John Wiegley lets you store quick notes with | |
5229 | little interruption of your work flow. See | |
5230 | @uref{http://www.emacswiki.org/cgi-bin/wiki/RememberMode} for more | |
5231 | information. It is an excellent way to add new notes and tasks to | |
a7808fba | 5232 | Org files. Org significantly expands the possibilities of |
dbc28aaa CD |
5233 | @i{remember}: You may define templates for different note types, and |
5234 | associate target files and headlines with specific templates. It also | |
5235 | allows you to select the location where a note should be stored | |
5236 | interactively, on the fly. | |
5237 | ||
5238 | @menu | |
a7808fba | 5239 | * Setting up Remember:: Some code for .emacs to get things going |
dbc28aaa CD |
5240 | * Remember templates:: Define the outline of different note types |
5241 | * Storing notes:: Directly get the note to where it belongs | |
5242 | * Refiling notes:: Moving a note or task to a project | |
5243 | @end menu | |
5244 | ||
a7808fba | 5245 | @node Setting up Remember, Remember templates, Remember, Remember |
864c9740 | 5246 | @subsection Setting up Remember |
dbc28aaa CD |
5247 | |
5248 | The following customization will tell @i{remember} to use org files as | |
a7808fba | 5249 | target, and to create annotations compatible with Org links. |
dbc28aaa CD |
5250 | |
5251 | @example | |
5252 | (org-remember-insinuate) | |
5253 | (setq org-directory "~/path/to/my/orgfiles/") | |
5254 | (setq org-default-notes-file (concat org-directory "/notes.org")) | |
5255 | (define-key global-map "\C-cr" 'org-remember) | |
5256 | @end example | |
5257 | ||
5258 | The last line binds the command @code{org-remember} to a global | |
5259 | key@footnote{Please select your own key, @kbd{C-c r} is only a | |
5260 | suggestion.}. @code{org-remember} basically just calls @code{remember}, | |
5261 | but it makes a few things easier: If there is an active region, it will | |
5262 | automatically copy the region into the remember buffer. It also allows | |
5263 | to jump to the buffer and location where remember notes are being | |
28a16a1b | 5264 | stored: Just call @code{org-remember} with a prefix argument. If you |
a7808fba | 5265 | use two prefix arguments, Org jumps to the location where the last |
28a16a1b | 5266 | remember note was stored. |
dbc28aaa | 5267 | |
64fb801f CD |
5268 | The remember buffer will actually use @code{org-mode} as its major mode, so |
5269 | that all editing features of Org-mode are available. In addition to this, a | |
5270 | minor mode @code{org-remember-mode} is turned on, for the single purpose that | |
5271 | you can use its keymap @code{org-remember-mode-map} to overwrite some of | |
5272 | Org-mode's key bindings. | |
5273 | ||
b349f79f CD |
5274 | You can also call @code{org-remember} in a special way from the agenda, |
5275 | using the @kbd{k r} key combination. With this access, any time stamps | |
5276 | inserted by the selected remember template (see below) will default to | |
5277 | the cursor date in the agenda, rather than to the current date. | |
5278 | ||
a7808fba | 5279 | @node Remember templates, Storing notes, Setting up Remember, Remember |
864c9740 | 5280 | @subsection Remember templates |
dbc28aaa CD |
5281 | @cindex templates, for remember |
5282 | ||
a7808fba | 5283 | In combination with Org, you can use templates to generate |
dbc28aaa CD |
5284 | different types of @i{remember} notes. For example, if you would like |
5285 | to use one template to create general TODO entries, another one for | |
5286 | journal entries, and a third one for collecting random ideas, you could | |
5287 | use: | |
5288 | ||
5289 | @example | |
5290 | (setq org-remember-templates | |
5291 | '(("Todo" ?t "* TODO %?\n %i\n %a" "~/org/TODO.org" "Tasks") | |
5292 | ("Journal" ?j "* %U %?\n\n %i\n %a" "~/org/JOURNAL.org") | |
5293 | ("Idea" ?i "* %^@{Title@}\n %i\n %a" "~/org/JOURNAL.org" "New Ideas"))) | |
5294 | @end example | |
5295 | ||
5296 | @noindent In these entries, the first string is just a name, and the | |
5297 | character specifies how to select the template. It is useful if the | |
b349f79f CD |
5298 | character is also the first letter of the name. The next string specifies |
5299 | the template. Two more (optional) strings give the file in which, and the | |
5300 | headline under which the new note should be stored. The file (if not present | |
5301 | or @code{nil}) defaults to @code{org-default-notes-file}, the heading to | |
5302 | @code{org-remember-default-headline}. If the file name is not an absolute | |
5303 | path, it will be interpreted relative to @code{org-directory}. The heading | |
5304 | can also be the symbols @code{top} or @code{bottom} to send note as level 1 | |
5305 | entries to the beginning or end of the file, respectively. | |
5306 | ||
5307 | An optional sixth element specifies the contexts in which the user can select | |
5308 | the template. This element can be a list of major modes or a function. | |
5309 | @code{org-remember} will first check whether the function returns @code{t} or | |
a50253cc | 5310 | if we are in any of the listed major mode, and exclude templates for which |
b349f79f CD |
5311 | this condition is not fulfilled. Templates that do not specify this element |
5312 | at all, or that use @code{nil} or @code{t} as a value will always be | |
5313 | selectable. | |
28a16a1b CD |
5314 | |
5315 | So for example: | |
5316 | ||
5317 | @example | |
5318 | (setq org-remember-templates | |
5319 | '(("Bug" ?b "* BUG %?\n %i\n %a" "~/org/BUGS.org" "Bugs" (emacs-lisp-mode)) | |
b349f79f | 5320 | ("Journal" ?j "* %U %?\n\n %i\n %a" "~/org/JOURNAL.org" "X" my-check) |
28a16a1b CD |
5321 | ("Idea" ?i "* %^@{Title@}\n %i\n %a" "~/org/JOURNAL.org" "New Ideas"))) |
5322 | @end example | |
5323 | ||
5324 | The first template will only be available when invoking @code{org-remember} | |
5325 | from an buffer in @code{emacs-lisp-mode}. The second template will only be | |
5326 | available when the function @code{my-check} returns @code{t}. The third | |
5327 | template will be proposed in any context. | |
5328 | ||
b349f79f CD |
5329 | When you call @kbd{M-x org-remember} (or @kbd{M-x remember}) to remember |
5330 | something, Org will prompt for a key to select the template (if you have | |
dbc28aaa CD |
5331 | more than one template) and then prepare the buffer like |
5332 | @example | |
5333 | * TODO | |
5334 | [[file:link to where you called remember]] | |
5335 | @end example | |
5336 | ||
5337 | @noindent | |
5338 | During expansion of the template, special @kbd{%}-escapes allow dynamic | |
5339 | insertion of content: | |
5340 | @example | |
5341 | %^@{prompt@} @r{prompt the user for a string and replace this sequence with it.} | |
5342 | @r{You may specify a default value and a completion table with} | |
5343 | @r{%^@{prompt|default|completion2|completion3...@}} | |
5344 | @r{The arrow keys access a prompt-specific history.} | |
b349f79f CD |
5345 | %a @r{annotation, normally the link created with @code{org-store-link}} |
5346 | %A @r{like @code{%a}, but prompt for the description part} | |
5347 | %i @r{initial content, the region when remember is called with C-u.} | |
5348 | @r{The entire text will be indented like @code{%i} itself.} | |
dbc28aaa CD |
5349 | %t @r{time stamp, date only} |
5350 | %T @r{time stamp with date and time} | |
5351 | %u, %U @r{like the above, but inactive time stamps} | |
5352 | %^t @r{like @code{%t}, but prompt for date. Similarly @code{%^T}, @code{%^u}, @code{%^U}} | |
5353 | @r{You may define a prompt like @code{%^@{Birthday@}t}} | |
5354 | %n @r{user name (taken from @code{user-full-name})} | |
a7808fba CD |
5355 | %c @r{Current kill ring head.} |
5356 | %x @r{Content of the X clipboard.} | |
5357 | %^C @r{Interactive selection of which kill or clip to use.} | |
5358 | %^L @r{Like @code{%^C}, but insert as link.} | |
dbc28aaa | 5359 | %^g @r{prompt for tags, with completion on tags in target file.} |
864c9740 CD |
5360 | %k @r{title of currently clocked task} |
5361 | %K @r{link to currently clocked task} | |
dbc28aaa | 5362 | %^G @r{prompt for tags, with completion all tags in all agenda files.} |
864c9740 | 5363 | %^@{prop@}p @r{Prompt the user for a value for property @code{prop}} |
dbc28aaa CD |
5364 | %:keyword @r{specific information for certain link types, see below} |
5365 | %[pathname] @r{insert the contents of the file given by @code{pathname}} | |
5366 | %(sexp) @r{evaluate elisp @code{(sexp)} and replace with the result} | |
5367 | %! @r{immediately store note after completing the template} | |
5368 | @r{(skipping the @kbd{C-c C-c} that normally triggers storing)} | |
b349f79f | 5369 | %& @r{jump to target location immediately after storing note} |
dbc28aaa CD |
5370 | @end example |
5371 | ||
5372 | @noindent | |
5373 | For specific link types, the following keywords will be | |
5374 | defined@footnote{If you define your own link types (@pxref{Adding | |
5375 | hyperlink types}), any property you store with | |
5376 | @code{org-store-link-props} can be accessed in remember templates in a | |
5377 | similar way.}: | |
5378 | ||
5379 | @example | |
5380 | Link type | Available keywords | |
5381 | -------------------+---------------------------------------------- | |
5382 | bbdb | %:name %:company | |
28a16a1b | 5383 | bbdb | %::server %:port %:nick |
dbc28aaa CD |
5384 | vm, wl, mh, rmail | %:type %:subject %:message-id |
5385 | | %:from %:fromname %:fromaddress | |
5386 | | %:to %:toname %:toaddress | |
28a16a1b | 5387 | | %:fromto @r{(either "to NAME" or "from NAME")@footnote{This will always be the other, not the user. See the variable @code{org-from-is-user-regexp}.}} |
dbc28aaa CD |
5388 | gnus | %:group, @r{for messages also all email fields} |
5389 | w3, w3m | %:url | |
5390 | info | %:file %:node | |
5391 | calendar | %:date" | |
5392 | @end example | |
5393 | ||
5394 | @noindent | |
5395 | To place the cursor after template expansion use: | |
5396 | ||
5397 | @example | |
5398 | %? @r{After completing the template, position cursor here.} | |
5399 | @end example | |
5400 | ||
5401 | @noindent | |
28a16a1b | 5402 | If you change your mind about which template to use, call |
dbc28aaa CD |
5403 | @code{org-remember} in the remember buffer. You may then select a new |
5404 | template that will be filled with the previous context information. | |
5405 | ||
5406 | @node Storing notes, Refiling notes, Remember templates, Remember | |
864c9740 | 5407 | @subsection Storing notes |
dbc28aaa | 5408 | |
b349f79f CD |
5409 | When you are finished preparing a note with @i{remember}, you have to press |
5410 | @kbd{C-c C-c} to file the note away. If you have started the clock in the | |
5411 | remember buffer, you will first be asked if you want to clock out | |
5412 | now@footnote{To avoid this query, configure the variable | |
5413 | @code{org-remember-clock-out-on-exit}.}. If you answer @kbd{n}, the clock | |
44ce9197 | 5414 | will continue to run after the note was filed away. |
b349f79f CD |
5415 | |
5416 | The handler will then store the note in the file and under the headline | |
5417 | specified in the template, or it will use the default file and headlines. | |
5418 | The window configuration will be restored, sending you back to the working | |
5419 | context before the call to @code{remember}. To re-use the location found | |
5420 | during the last call to @code{remember}, exit the remember buffer with | |
864c9740 CD |
5421 | @kbd{C-0 C-c C-c}, i.e. specify a zero prefix argument to @kbd{C-c C-c}. |
5422 | Another special case is @kbd{C-2 C-c C-c} which files the note as a child of | |
5423 | the currently clocked item. | |
dbc28aaa CD |
5424 | |
5425 | If you want to store the note directly to a different place, use | |
864c9740 | 5426 | @kbd{C-1 C-c C-c} instead to exit remember@footnote{Configure the |
dbc28aaa CD |
5427 | variable @code{org-remember-store-without-prompt} to make this behavior |
5428 | the default.}. The handler will then first prompt for a target file - | |
5429 | if you press @key{RET}, the value specified for the template is used. | |
5430 | Then the command offers the headings tree of the selected file, with the | |
5431 | cursor position at the default headline (if you had specified one in the | |
5432 | template). You can either immediately press @key{RET} to get the note | |
5433 | placed there. Or you can use the following keys to find a different | |
5434 | location: | |
5435 | @example | |
5436 | @key{TAB} @r{Cycle visibility.} | |
5437 | @key{down} / @key{up} @r{Next/previous visible headline.} | |
5438 | n / p @r{Next/previous visible headline.} | |
5439 | f / b @r{Next/previous headline same level.} | |
5440 | u @r{One level up.} | |
5441 | @c 0-9 @r{Digit argument.} | |
5442 | @end example | |
5443 | @noindent | |
5444 | Pressing @key{RET} or @key{left} or @key{right} | |
5445 | then leads to the following result. | |
5446 | ||
5447 | @multitable @columnfractions 0.2 0.15 0.65 | |
5448 | @item @b{Cursor position} @tab @b{Key} @tab @b{Note gets inserted} | |
5449 | @item on headline @tab @key{RET} @tab as sublevel of the heading at cursor, first or last | |
5450 | @item @tab @tab depending on @code{org-reverse-note-order}. | |
5451 | @item @tab @key{left}/@key{right} @tab as same level, before/after current heading | |
5452 | @item buffer-start @tab @key{RET} @tab as level 2 heading at end of file or level 1 at beginning | |
5453 | @item @tab @tab depending on @code{org-reverse-note-order}. | |
5454 | @item not on headline @tab @key{RET} | |
5455 | @tab at cursor position, level taken from context. | |
5456 | @end multitable | |
5457 | ||
864c9740 CD |
5458 | Before inserting the text into a tree, the function ensures that the text has |
5459 | a headline, i.e. a first line that starts with a @samp{*}. If not, a | |
5460 | headline is constructed from the current date. If you have indented the text | |
5461 | of the note below the headline, the indentation will be adapted if inserting | |
5462 | the note into the tree requires demotion from level 1. | |
dbc28aaa CD |
5463 | |
5464 | @node Refiling notes, , Storing notes, Remember | |
864c9740 | 5465 | @subsection Refiling notes |
dbc28aaa CD |
5466 | @cindex refiling notes |
5467 | ||
5468 | Remember is usually used to quickly capture notes and tasks into one or | |
5469 | a few capture lists. When reviewing the captured data, you may want to | |
5470 | refile some of the entries into a different list, for example into a | |
5471 | project. Cutting, finding the right location and then pasting the note | |
5472 | is cumbersome. To simplify this process, you can use the following | |
5473 | special command: | |
5474 | ||
5475 | @table @kbd | |
5476 | @kindex C-c C-w | |
5477 | @item C-c C-w | |
e45e3595 CD |
5478 | Refile the entry or region at point. This command offers possible locations |
5479 | for refiling the entry and lets you select one with completion. The item (or | |
5480 | all items in the region) is filed below the target heading as a subitem. | |
d60b1ba1 | 5481 | Depending on @code{org-reverse-note-order}, it will be either the first or |
e45e3595 CD |
5482 | last subitem.@* |
5483 | By default, all level 1 headlines in the current buffer are considered to be | |
5484 | targets, but you can have more complex definitions across a number of files. | |
5485 | See the variable @code{org-refile-targets} for details. If you would like to | |
d60b1ba1 CD |
5486 | select a location via a file-path-like completion along the outline path, see |
5487 | the variables @code{org-refile-use-outline-path} and | |
5488 | @code{org-outline-path-complete-in-steps}. | |
28a16a1b CD |
5489 | @kindex C-u C-c C-w |
5490 | @item C-u C-c C-w | |
5491 | Use the refile interface to jump to a heading. | |
5492 | @kindex C-u C-u C-c C-w | |
a7808fba | 5493 | @item C-u C-u C-c C-w |
28a16a1b | 5494 | Jump to the location where @code{org-refile} last moved a tree to. |
dbc28aaa CD |
5495 | @end table |
5496 | ||
864c9740 CD |
5497 | @node Attachments, , Remember, Capture |
5498 | @section Attachments | |
5499 | @cindex attachments | |
5500 | ||
5501 | It is often useful to associate reference material with an outline node/task. | |
5502 | Small chunks of plain text can simply be stored in the subtree of a project. | |
5503 | Hyperlinks (@pxref{Hyperlinks}) can be used to establish associations with | |
5504 | files that live elsewhere on your computer or in the cloud, like emails or | |
5505 | source code files belonging to a project. Another method is @i{attachments}, | |
5506 | which are files located in a directory belonging to an outline node. Org | |
5507 | uses directories named by the unique ID of each entry. These directories are | |
5508 | located in the @file{data} directory which lives in the same directory where | |
5509 | your org-file lives@footnote{If you move entries or Org-files from one | |
5510 | directory to the next, you may want to configure @code{org-attach-directory} | |
5511 | to contain an absolute path.}. If you initialize this directory with | |
5512 | @code{git-init}, Org will automatically commit changes when it sees them. | |
5513 | The attachment system has been contributed to Org by John Wiegley. | |
5514 | ||
55e0839d CD |
5515 | In cases where this seems better, you can also attach a directory of your |
5516 | choice to an entry. You can also make children inherit the attachment | |
5517 | directory from a parent, so that an entire subtree uses the same attached | |
5518 | directory. | |
5519 | ||
864c9740 CD |
5520 | @noindent The following commands deal with attachments. |
5521 | ||
5522 | @table @kbd | |
5523 | ||
5524 | @kindex C-c C-a | |
5525 | @item C-c C-a | |
5526 | The dispatcher for commands related to the attachment system. After these | |
5527 | keys, a list of commands is displayed and you need to press an additional key | |
5528 | to select a command: | |
5529 | ||
5530 | @table @kbd | |
96c8522a CD |
5531 | @kindex C-c C-a a |
5532 | @item a | |
864c9740 CD |
5533 | Select a file and move it into the task's attachment directory. The file |
5534 | will be copied, moved, or linked, depending on @code{org-attach-method}. | |
5535 | Note that hard links are not supported on all systems. | |
5536 | ||
5537 | @kindex C-c C-a c | |
96c8522a CD |
5538 | @kindex C-c C-a m |
5539 | @kindex C-c C-a l | |
864c9740 CD |
5540 | @item c/m/l |
5541 | Attach a file using the copy/move/link method. | |
5542 | Note that hard links are not supported on all systems. | |
5543 | ||
5544 | @kindex C-c C-a n | |
5545 | @item n | |
5546 | Create a new attachment as an Emacs buffer. | |
5547 | ||
5548 | @kindex C-c C-a z | |
5549 | @item z | |
5550 | Synchronize the current task with its attachment directory, in case you added | |
5551 | attachments yourself. | |
5552 | ||
5553 | @kindex C-c C-a o | |
5554 | @item o | |
5555 | Open current task's attachment. If there are more than one, prompt for a | |
5556 | file name first. Opening will follow the rules set by @code{org-file-apps}. | |
a50253cc | 5557 | For more details, see the information on following hyperlinks |
864c9740 CD |
5558 | (@pxref{Handling links}). |
5559 | ||
5560 | @kindex C-c C-a O | |
5561 | @item O | |
5562 | Also open the attachment, but force opening the file in Emacs. | |
5563 | ||
5564 | @kindex C-c C-a f | |
5565 | @item f | |
5566 | Open the current task's attachment directory. | |
5567 | ||
5568 | @kindex C-c C-a F | |
5569 | @item F | |
5570 | Also open the directory, but force using @code{dired} in Emacs. | |
5571 | ||
5572 | @kindex C-c C-a d | |
5573 | @item d | |
5574 | Select and delete a single attachment. | |
5575 | ||
5576 | @kindex C-c C-a D | |
5577 | @item D | |
5578 | Delete all of a task's attachments. A safer way is to open the directory in | |
5579 | dired and delete from there. | |
55e0839d CD |
5580 | |
5581 | @kindex C-c C-a s | |
5582 | @item C-c C-a s | |
5583 | Set a specific directory as the entry's attachment directory. This works by | |
5584 | putting the directory path into the @code{ATTACH_DIR} property. | |
5585 | ||
5586 | @kindex C-c C-a i | |
5587 | @item C-c C-a i | |
5588 | Set the @code{ATTACH_DIR_INHERIT} property, so that children will use the | |
5589 | same directory for attachments as the parent. | |
864c9740 CD |
5590 | @end table |
5591 | @end table | |
5592 | ||
5593 | @node Agenda Views, Embedded LaTeX, Capture, Top | |
4009494e GM |
5594 | @chapter Agenda Views |
5595 | @cindex agenda views | |
5596 | ||
a7808fba | 5597 | Due to the way Org works, TODO items, time-stamped items, and |
4009494e | 5598 | tagged headlines can be scattered throughout a file or even a number of |
dbc28aaa CD |
5599 | files. To get an overview of open action items, or of events that are |
5600 | important for a particular date, this information must be collected, | |
4009494e GM |
5601 | sorted and displayed in an organized way. |
5602 | ||
a7808fba | 5603 | Org can select items based on various criteria, and display them |
28a16a1b | 5604 | in a separate buffer. Seven different view types are provided: |
4009494e GM |
5605 | |
5606 | @itemize @bullet | |
5607 | @item | |
5608 | an @emph{agenda} that is like a calendar and shows information | |
5609 | for specific dates, | |
5610 | @item | |
5611 | a @emph{TODO list} that covers all unfinished | |
5612 | action items, | |
5613 | @item | |
864c9740 CD |
5614 | a @emph{match view}, showings headlines based on the tags, properties and |
5615 | TODO state associated with them, | |
4009494e | 5616 | @item |
a7808fba | 5617 | a @emph{timeline view} that shows all events in a single Org file, |
4009494e GM |
5618 | in time-sorted view, |
5619 | @item | |
28a16a1b CD |
5620 | a @emph{keyword search view} that shows all entries from multiple files |
5621 | that contain specified keywords. | |
5622 | @item | |
4009494e GM |
5623 | a @emph{stuck projects view} showing projects that currently don't move |
5624 | along, and | |
5625 | @item | |
5626 | @emph{custom views} that are special tag/keyword searches and | |
5627 | combinations of different views. | |
5628 | @end itemize | |
5629 | ||
5630 | @noindent | |
5631 | The extracted information is displayed in a special @emph{agenda | |
5632 | buffer}. This buffer is read-only, but provides commands to visit the | |
a7808fba | 5633 | corresponding locations in the original Org files, and even to |
28a16a1b | 5634 | edit these files remotely. |
4009494e GM |
5635 | |
5636 | Two variables control how the agenda buffer is displayed and whether the | |
5637 | window configuration is restored when the agenda exits: | |
5638 | @code{org-agenda-window-setup} and | |
5639 | @code{org-agenda-restore-windows-after-quit}. | |
5640 | ||
5641 | @menu | |
5642 | * Agenda files:: Files being searched for agenda information | |
5643 | * Agenda dispatcher:: Keyboard access to agenda views | |
5644 | * Built-in agenda views:: What is available out of the box? | |
5645 | * Presentation and sorting:: How agenda items are prepared for display | |
a7808fba | 5646 | * Agenda commands:: Remote editing of Org trees |
4009494e | 5647 | * Custom agenda views:: Defining special searches and views |
a7808fba | 5648 | * Agenda column view:: Using column view for collected entries |
4009494e GM |
5649 | @end menu |
5650 | ||
a7808fba | 5651 | @node Agenda files, Agenda dispatcher, Agenda Views, Agenda Views |
4009494e GM |
5652 | @section Agenda files |
5653 | @cindex agenda files | |
5654 | @cindex files for agenda | |
5655 | ||
dbc28aaa CD |
5656 | The information to be shown is normally collected from all @emph{agenda |
5657 | files}, the files listed in the variable | |
5658 | @code{org-agenda-files}@footnote{If the value of that variable is not a | |
5659 | list, but a single file name, then the list of agenda files will be | |
5660 | maintained in that external file.}. If a directory is part of this list, | |
5661 | all files with the extension @file{.org} in this directory will be part | |
5662 | of the list. | |
5663 | ||
a7808fba | 5664 | Thus even if you only work with a single Org file, this file should |
dbc28aaa CD |
5665 | be put into that list@footnote{When using the dispatcher, pressing |
5666 | @kbd{<} before selecting a command will actually limit the command to | |
5667 | the current file, and ignore @code{org-agenda-files} until the next | |
4009494e GM |
5668 | dispatcher command.}. You can customize @code{org-agenda-files}, but |
5669 | the easiest way to maintain it is through the following commands | |
5670 | ||
5671 | @cindex files, adding to agenda list | |
5672 | @table @kbd | |
5673 | @kindex C-c [ | |
5674 | @item C-c [ | |
5675 | Add current file to the list of agenda files. The file is added to | |
5676 | the front of the list. If it was already in the list, it is moved to | |
a7808fba | 5677 | the front. With a prefix argument, file is added/moved to the end. |
4009494e GM |
5678 | @kindex C-c ] |
5679 | @item C-c ] | |
5680 | Remove current file from the list of agenda files. | |
5681 | @kindex C-, | |
5682 | @kindex C-' | |
5683 | @item C-, | |
5684 | @itemx C-' | |
5685 | Cycle through agenda file list, visiting one file after the other. | |
a7808fba CD |
5686 | @kindex M-x org-iswitchb |
5687 | @item M-x org-iswitchb | |
5688 | Command to use an @code{iswitchb}-like interface to switch to and between Org | |
5689 | buffers. | |
4009494e GM |
5690 | @end table |
5691 | ||
5692 | @noindent | |
5693 | The Org menu contains the current list of files and can be used | |
5694 | to visit any of them. | |
5695 | ||
dbc28aaa CD |
5696 | If you would like to focus the agenda temporarily onto a file not in |
5697 | this list, or onto just one file in the list or even only a subtree in a | |
5698 | file, this can be done in different ways. For a single agenda command, | |
5699 | you may press @kbd{<} once or several times in the dispatcher | |
5700 | (@pxref{Agenda dispatcher}). To restrict the agenda scope for an | |
5701 | extended period, use the following commands: | |
5702 | ||
5703 | @table @kbd | |
5704 | @kindex C-c C-x < | |
5705 | @item C-c C-x < | |
5706 | Permanently restrict the agenda to the current subtree. When with a | |
5707 | prefix argument, or with the cursor before the first headline in a file, | |
5708 | the agenda scope is set to the entire file. This restriction remains in | |
5709 | effect until removed with @kbd{C-c C-x >}, or by typing either @kbd{<} | |
5710 | or @kbd{>} in the agenda dispatcher. If there is a window displaying an | |
5711 | agenda view, the new restriction takes effect immediately. | |
67df9cfb CD |
5712 | @kindex C-c C-x > |
5713 | @item C-c C-x > | |
dbc28aaa CD |
5714 | Remove the permanent restriction created by @kbd{C-c C-x <}. |
5715 | @end table | |
5716 | ||
5717 | @noindent | |
5718 | When working with @file{Speedbar}, you can use the following commands in | |
a7808fba | 5719 | the Speedbar frame: |
dbc28aaa CD |
5720 | @table @kbd |
5721 | @kindex < | |
5722 | @item < @r{in the speedbar frame} | |
5723 | Permanently restrict the agenda to the item at the cursor in the | |
a7808fba | 5724 | Speedbar frame, either an Org file or a subtree in such a file. |
dbc28aaa CD |
5725 | If there is a window displaying an agenda view, the new restriction takes |
5726 | effect immediately. | |
67df9cfb | 5727 | @kindex > |
dbc28aaa CD |
5728 | @item > @r{in the speedbar frame} |
5729 | Lift the restriction again. | |
5730 | @end table | |
5731 | ||
a7808fba | 5732 | @node Agenda dispatcher, Built-in agenda views, Agenda files, Agenda Views |
4009494e GM |
5733 | @section The agenda dispatcher |
5734 | @cindex agenda dispatcher | |
5735 | @cindex dispatching agenda commands | |
5736 | The views are created through a dispatcher that should be bound to a | |
5737 | global key, for example @kbd{C-c a} (@pxref{Installation}). In the | |
5738 | following we will assume that @kbd{C-c a} is indeed how the dispatcher | |
5739 | is accessed and list keyboard access to commands accordingly. After | |
5740 | pressing @kbd{C-c a}, an additional letter is required to execute a | |
5741 | command. The dispatcher offers the following default commands: | |
5742 | @table @kbd | |
5743 | @item a | |
a7808fba | 5744 | Create the calendar-like agenda (@pxref{Weekly/daily agenda}). |
4009494e GM |
5745 | @item t @r{/} T |
5746 | Create a list of all TODO items (@pxref{Global TODO list}). | |
5747 | @item m @r{/} M | |
5748 | Create a list of headlines matching a TAGS expression (@pxref{Matching | |
5749 | tags and properties}). | |
5750 | @item L | |
5751 | Create the timeline view for the current buffer (@pxref{Timeline}). | |
28a16a1b CD |
5752 | @item s |
5753 | Create a list of entries selected by a boolean expression of keywords | |
5754 | and/or regular expressions that must or must not occur in the entry. | |
dbc28aaa CD |
5755 | @item / |
5756 | Search for a regular expression in all agenda files and additionally in | |
5757 | the files listed in @code{org-agenda-multi-occur-extra-files}. This | |
5758 | uses the Emacs command @code{multi-occur}. A prefix argument can be | |
5759 | used to specify the number of context lines for each match, default is | |
5760 | 1. | |
28a16a1b CD |
5761 | @item # @r{/} ! |
5762 | Create a list of stuck projects (@pxref{Stuck projects}). | |
dbc28aaa CD |
5763 | @item < |
5764 | Restrict an agenda command to the current buffer@footnote{For backward | |
5765 | compatibility, you can also press @kbd{1} to restrict to the current | |
5766 | buffer.}. After pressing @kbd{<}, you still need to press the character | |
5767 | selecting the command. | |
5768 | @item < < | |
4009494e | 5769 | If there is an active region, restrict the following agenda command to |
dbc28aaa CD |
5770 | the region. Otherwise, restrict it to the current subtree@footnote{For |
5771 | backward compatibility, you can also press @kbd{0} to restrict to the | |
5772 | current buffer.}. After pressing @kbd{< <}, you still need to press the | |
5773 | character selecting the command. | |
4009494e GM |
5774 | @end table |
5775 | ||
5776 | You can also define custom commands that will be accessible through the | |
5777 | dispatcher, just like the default commands. This includes the | |
5778 | possibility to create extended agenda buffers that contain several | |
5779 | blocks together, for example the weekly agenda, the global TODO list and | |
5780 | a number of special tags matches. @xref{Custom agenda views}. | |
5781 | ||
a7808fba | 5782 | @node Built-in agenda views, Presentation and sorting, Agenda dispatcher, Agenda Views |
4009494e GM |
5783 | @section The built-in agenda views |
5784 | ||
5785 | In this section we describe the built-in views. | |
5786 | ||
5787 | @menu | |
a7808fba | 5788 | * Weekly/daily agenda:: The calendar page with current tasks |
4009494e GM |
5789 | * Global TODO list:: All unfinished action items |
5790 | * Matching tags and properties:: Structured information with fine-tuned search | |
5791 | * Timeline:: Time-sorted view for single file | |
28a16a1b | 5792 | * Keyword search:: Finding entries by keyword |
4009494e GM |
5793 | * Stuck projects:: Find projects you need to review |
5794 | @end menu | |
5795 | ||
a7808fba | 5796 | @node Weekly/daily agenda, Global TODO list, Built-in agenda views, Built-in agenda views |
4009494e GM |
5797 | @subsection The weekly/daily agenda |
5798 | @cindex agenda | |
5799 | @cindex weekly agenda | |
5800 | @cindex daily agenda | |
5801 | ||
5802 | The purpose of the weekly/daily @emph{agenda} is to act like a page of a | |
5803 | paper agenda, showing all the tasks for the current week or day. | |
5804 | ||
5805 | @table @kbd | |
5806 | @cindex org-agenda, command | |
5807 | @kindex C-c a a | |
5808 | @item C-c a a | |
864c9740 CD |
5809 | Compile an agenda for the current week from a list of org files. The agenda |
5810 | shows the entries for each day. With a numeric prefix@footnote{For backward | |
5811 | compatibility, the universal prefix @kbd{C-u} causes all TODO entries to be | |
5812 | listed before the agenda. This feature is deprecated, use the dedicated TODO | |
5813 | list, or a block agenda instead (@pxref{Block agenda}).} (like @kbd{C-u 2 1 | |
5814 | C-c a a}) you may set the number of days to be displayed (see also the | |
5815 | variable @code{org-agenda-ndays}) | |
4009494e GM |
5816 | @end table |
5817 | ||
5818 | Remote editing from the agenda buffer means, for example, that you can | |
5819 | change the dates of deadlines and appointments from the agenda buffer. | |
5820 | The commands available in the Agenda buffer are listed in @ref{Agenda | |
5821 | commands}. | |
5822 | ||
5823 | @subsubheading Calendar/Diary integration | |
5824 | @cindex calendar integration | |
5825 | @cindex diary integration | |
5826 | ||
5827 | Emacs contains the calendar and diary by Edward M. Reingold. The | |
5828 | calendar displays a three-month calendar with holidays from different | |
5829 | countries and cultures. The diary allows you to keep track of | |
5830 | anniversaries, lunar phases, sunrise/set, recurrent appointments | |
5831 | (weekly, monthly) and more. In this way, it is quite complementary to | |
a7808fba | 5832 | Org. It can be very useful to combine output from Org with |
4009494e GM |
5833 | the diary. |
5834 | ||
a7808fba | 5835 | In order to include entries from the Emacs diary into Org mode's |
4009494e GM |
5836 | agenda, you only need to customize the variable |
5837 | ||
5838 | @lisp | |
5839 | (setq org-agenda-include-diary t) | |
5840 | @end lisp | |
5841 | ||
5842 | @noindent After that, everything will happen automatically. All diary | |
5843 | entries including holidays, anniversaries etc will be included in the | |
a7808fba | 5844 | agenda buffer created by Org mode. @key{SPC}, @key{TAB}, and |
4009494e GM |
5845 | @key{RET} can be used from the agenda buffer to jump to the diary |
5846 | file in order to edit existing diary entries. The @kbd{i} command to | |
5847 | insert new entries for the current date works in the agenda buffer, as | |
5848 | well as the commands @kbd{S}, @kbd{M}, and @kbd{C} to display | |
5849 | Sunrise/Sunset times, show lunar phases and to convert to other | |
5850 | calendars, respectively. @kbd{c} can be used to switch back and forth | |
5851 | between calendar and agenda. | |
5852 | ||
5853 | If you are using the diary only for sexp entries and holidays, it is | |
5854 | faster to not use the above setting, but instead to copy or even move | |
a7808fba | 5855 | the entries into an Org file. Org mode evaluates diary-style sexp |
4009494e GM |
5856 | entries, and does it faster because there is no overhead for first |
5857 | creating the diary display. Note that the sexp entries must start at | |
5858 | the left margin, no white space is allowed before them. For example, | |
a7808fba | 5859 | the following segment of an Org file will be processed and entries |
4009494e GM |
5860 | will be made in the agenda: |
5861 | ||
5862 | @example | |
5863 | * Birthdays and similar stuff | |
5864 | #+CATEGORY: Holiday | |
5865 | %%(org-calendar-holiday) ; special function for holiday names | |
5866 | #+CATEGORY: Ann | |
5867 | %%(diary-anniversary 14 5 1956) Arthur Dent is %d years old | |
5868 | %%(diary-anniversary 2 10 1869) Mahatma Gandhi would be %d years old | |
5869 | @end example | |
5870 | ||
dbc28aaa CD |
5871 | @subsubheading Appointment reminders |
5872 | @cindex @file{appt.el} | |
5873 | @cindex appointment reminders | |
5874 | ||
5875 | Org can interact with Emacs appointments notification facility. | |
5876 | ||
5877 | To add all the appointments of your agenda files, use the command | |
5878 | @code{org-agenda-to-appt}. This commands also lets you filter through | |
5879 | the list of your appointments and add only those belonging to a specific | |
5880 | category or matching a regular expression. See the docstring for | |
5881 | details. | |
5882 | ||
a7808fba | 5883 | @node Global TODO list, Matching tags and properties, Weekly/daily agenda, Built-in agenda views |
4009494e GM |
5884 | @subsection The global TODO list |
5885 | @cindex global TODO list | |
5886 | @cindex TODO list, global | |
5887 | ||
5888 | The global TODO list contains all unfinished TODO items, formatted and | |
5889 | collected into a single place. | |
5890 | ||
5891 | @table @kbd | |
5892 | @kindex C-c a t | |
5893 | @item C-c a t | |
5894 | Show the global TODO list. This collects the TODO items from all | |
a7808fba | 5895 | agenda files (@pxref{Agenda Views}) into a single buffer. The buffer is in |
4009494e GM |
5896 | @code{agenda-mode}, so there are commands to examine and manipulate |
5897 | the TODO entries directly from that buffer (@pxref{Agenda commands}). | |
5898 | @kindex C-c a T | |
5899 | @item C-c a T | |
5900 | @cindex TODO keyword matching | |
5901 | Like the above, but allows selection of a specific TODO keyword. You | |
5902 | can also do this by specifying a prefix argument to @kbd{C-c a t}. With | |
5903 | a @kbd{C-u} prefix you are prompted for a keyword, and you may also | |
5904 | specify several keywords by separating them with @samp{|} as boolean OR | |
5905 | operator. With a numeric prefix, the Nth keyword in | |
5906 | @code{org-todo-keywords} is selected. | |
5907 | @kindex r | |
5908 | The @kbd{r} key in the agenda buffer regenerates it, and you can give | |
5909 | a prefix argument to this command to change the selected TODO keyword, | |
5910 | for example @kbd{3 r}. If you often need a search for a specific | |
5911 | keyword, define a custom command for it (@pxref{Agenda dispatcher}).@* | |
5912 | Matching specific TODO keywords can also be done as part of a tags | |
5913 | search (@pxref{Tag searches}). | |
5914 | @end table | |
5915 | ||
5916 | Remote editing of TODO items means that you can change the state of a | |
5917 | TODO entry with a single key press. The commands available in the | |
5918 | TODO list are described in @ref{Agenda commands}. | |
5919 | ||
a7808fba CD |
5920 | @cindex sublevels, inclusion into TODO list |
5921 | Normally the global TODO list simply shows all headlines with TODO | |
4009494e GM |
5922 | keywords. This list can become very long. There are two ways to keep |
5923 | it more compact: | |
5924 | @itemize @minus | |
5925 | @item | |
5926 | Some people view a TODO item that has been @emph{scheduled} for | |
a7808fba | 5927 | execution (@pxref{Timestamps}) as no longer @emph{open}. Configure the |
4009494e GM |
5928 | variable @code{org-agenda-todo-ignore-scheduled} to exclude scheduled |
5929 | items from the global TODO list. | |
5930 | @item | |
5931 | TODO items may have sublevels to break up the task into subtasks. In | |
5932 | such cases it may be enough to list only the highest level TODO headline | |
5933 | and omit the sublevels from the global list. Configure the variable | |
5934 | @code{org-agenda-todo-list-sublevels} to get this behavior. | |
5935 | @end itemize | |
5936 | ||
5937 | @node Matching tags and properties, Timeline, Global TODO list, Built-in agenda views | |
a7808fba | 5938 | @subsection Matching tags and properties |
4009494e GM |
5939 | @cindex matching, of tags |
5940 | @cindex matching, of properties | |
5941 | @cindex tags view | |
864c9740 | 5942 | @cindex match view |
4009494e GM |
5943 | |
5944 | If headlines in the agenda files are marked with @emph{tags} | |
5945 | (@pxref{Tags}), you can select headlines based on the tags that apply | |
5946 | to them and collect them into an agenda buffer. | |
5947 | ||
5948 | @table @kbd | |
5949 | @kindex C-c a m | |
5950 | @item C-c a m | |
5951 | Produce a list of all headlines that match a given set of tags. The | |
5952 | command prompts for a selection criterion, which is a boolean logic | |
dbc28aaa CD |
5953 | expression with tags, like @samp{+work+urgent-withboss} or |
5954 | @samp{work|home} (@pxref{Tags}). If you often need a specific search, | |
4009494e GM |
5955 | define a custom command for it (@pxref{Agenda dispatcher}). |
5956 | @kindex C-c a M | |
5957 | @item C-c a M | |
5958 | Like @kbd{C-c a m}, but only select headlines that are also TODO items | |
5959 | and force checking subitems (see variable | |
a7808fba | 5960 | @code{org-tags-match-list-sublevels}). Matching specific TODO keywords |
4009494e GM |
5961 | together with a tags match is also possible, see @ref{Tag searches}. |
5962 | @end table | |
5963 | ||
5964 | The commands available in the tags list are described in @ref{Agenda | |
5965 | commands}. | |
5966 | ||
28a16a1b | 5967 | @node Timeline, Keyword search, Matching tags and properties, Built-in agenda views |
4009494e GM |
5968 | @subsection Timeline for a single file |
5969 | @cindex timeline, single file | |
5970 | @cindex time-sorted view | |
5971 | ||
a7808fba | 5972 | The timeline summarizes all time-stamped items from a single Org mode |
4009494e GM |
5973 | file in a @emph{time-sorted view}. The main purpose of this command is |
5974 | to give an overview over events in a project. | |
5975 | ||
5976 | @table @kbd | |
5977 | @kindex C-c a L | |
5978 | @item C-c a L | |
5979 | Show a time-sorted view of the org file, with all time-stamped items. | |
5980 | When called with a @kbd{C-u} prefix, all unfinished TODO entries | |
5981 | (scheduled or not) are also listed under the current date. | |
5982 | @end table | |
5983 | ||
5984 | @noindent | |
5985 | The commands available in the timeline buffer are listed in | |
5986 | @ref{Agenda commands}. | |
5987 | ||
28a16a1b CD |
5988 | @node Keyword search, Stuck projects, Timeline, Built-in agenda views |
5989 | @subsection Keyword search | |
5990 | @cindex keyword search | |
5991 | @cindex searching, for keywords | |
5992 | ||
a7808fba | 5993 | This agenda view is a general text search facility for Org mode entries. |
28a16a1b CD |
5994 | It is particularly useful to find notes. |
5995 | ||
5996 | @table @kbd | |
5997 | @kindex C-c a s | |
5998 | @item C-c a s | |
5999 | This is a special search that lets you select entries by keywords or | |
6000 | regular expression, using a boolean logic. For example, the search | |
6001 | string | |
6002 | ||
6003 | @example | |
6004 | +computer +wifi -ethernet -@{8\.11[bg]@} | |
6005 | @end example | |
4009494e | 6006 | |
28a16a1b CD |
6007 | @noindent |
6008 | will search for note entries that contain the keywords @code{computer} | |
6009 | and @code{wifi}, but not the keyword @code{ethernet}, and which are also | |
6010 | not matched by the regular expression @code{8\.11[bg]}, meaning to | |
6011 | exclude both 8.11b and 8.11g. | |
6012 | ||
6013 | Note that in addition to the agenda files, this command will also search | |
6014 | the files listed in @code{org-agenda-text-search-extra-files}. | |
6015 | @end table | |
6016 | ||
6017 | @node Stuck projects, , Keyword search, Built-in agenda views | |
4009494e GM |
6018 | @subsection Stuck projects |
6019 | ||
6020 | If you are following a system like David Allen's GTD to organize your | |
6021 | work, one of the ``duties'' you have is a regular review to make sure | |
6022 | that all projects move along. A @emph{stuck} project is a project that | |
6023 | has no defined next actions, so it will never show up in the TODO lists | |
a7808fba | 6024 | Org mode produces. During the review, you need to identify such |
4009494e GM |
6025 | projects and define next actions for them. |
6026 | ||
6027 | @table @kbd | |
6028 | @kindex C-c a # | |
6029 | @item C-c a # | |
6030 | List projects that are stuck. | |
6031 | @kindex C-c a ! | |
6032 | @item C-c a ! | |
6033 | Customize the variable @code{org-stuck-projects} to define what a stuck | |
6034 | project is and how to find it. | |
6035 | @end table | |
6036 | ||
6037 | You almost certainly will have to configure this view before it will | |
6038 | work for you. The built-in default assumes that all your projects are | |
6039 | level-2 headlines, and that a project is not stuck if it has at least | |
a7808fba | 6040 | one entry marked with a TODO keyword TODO or NEXT or NEXTACTION. |
4009494e | 6041 | |
864c9740 | 6042 | Let's assume that you, in your own way of using Org mode, identify |
a7808fba | 6043 | projects with a tag PROJECT, and that you use a TODO keyword MAYBE to |
864c9740 | 6044 | indicate a project that should not be considered yet. Let's further |
a7808fba | 6045 | assume that the TODO keyword DONE marks finished projects, and that NEXT |
4009494e GM |
6046 | and TODO indicate next actions. The tag @@SHOP indicates shopping and |
6047 | is a next action even without the NEXT tag. Finally, if the project | |
6048 | contains the special word IGNORE anywhere, it should not be listed | |
6049 | either. In this case you would start by identifying eligible projects | |
6050 | with a tags/todo match @samp{+PROJECT/-MAYBE-DONE}, and then check for | |
6051 | TODO, NEXT, @@SHOP, and IGNORE in the subtree to identify projects that | |
6052 | are not stuck. The correct customization for this is | |
6053 | ||
6054 | @lisp | |
6055 | (setq org-stuck-projects | |
6056 | '("+PROJECT/-MAYBE-DONE" ("NEXT" "TODO") ("@@SHOP") | |
6057 | "\\<IGNORE\\>")) | |
6058 | @end lisp | |
6059 | ||
6060 | ||
a7808fba | 6061 | @node Presentation and sorting, Agenda commands, Built-in agenda views, Agenda Views |
4009494e GM |
6062 | @section Presentation and sorting |
6063 | @cindex presentation, of agenda items | |
6064 | ||
a7808fba | 6065 | Before displaying items in an agenda view, Org mode visually prepares |
4009494e GM |
6066 | the items and sorts them. Each item occupies a single line. The line |
6067 | starts with a @emph{prefix} that contains the @emph{category} | |
6068 | (@pxref{Categories}) of the item and other important information. You can | |
6069 | customize the prefix using the option @code{org-agenda-prefix-format}. | |
6070 | The prefix is followed by a cleaned-up version of the outline headline | |
6071 | associated with the item. | |
6072 | ||
6073 | @menu | |
6074 | * Categories:: Not all tasks are equal | |
6075 | * Time-of-day specifications:: How the agenda knows the time | |
6076 | * Sorting of agenda items:: The order of things | |
6077 | @end menu | |
6078 | ||
6079 | @node Categories, Time-of-day specifications, Presentation and sorting, Presentation and sorting | |
6080 | @subsection Categories | |
6081 | ||
6082 | @cindex category | |
6083 | The category is a broad label assigned to each agenda item. By default, | |
6084 | the category is simply derived from the file name, but you can also | |
dbc28aaa CD |
6085 | specify it with a special line in the buffer, like this@footnote{For |
6086 | backward compatibility, the following also works: If there are several | |
6087 | such lines in a file, each specifies the category for the text below it. | |
6088 | The first category also applies to any text before the first CATEGORY | |
6089 | line. However, using this method is @emph{strongly} deprecated as it is | |
6090 | incompatible with the outline structure of the document. The correct | |
6091 | method for setting multiple categories in a buffer is using a | |
6092 | property.}: | |
4009494e GM |
6093 | |
6094 | @example | |
6095 | #+CATEGORY: Thesis | |
6096 | @end example | |
6097 | ||
dbc28aaa CD |
6098 | @noindent |
6099 | If you would like to have a special CATEGORY for a single entry or a | |
55e0839d CD |
6100 | (sub)tree, give the entry a @code{:CATEGORY:} property with the |
6101 | special category you want to apply as the value. | |
dbc28aaa CD |
6102 | |
6103 | @noindent | |
6104 | The display in the agenda buffer looks best if the category is not | |
6105 | longer than 10 characters. | |
4009494e GM |
6106 | |
6107 | @node Time-of-day specifications, Sorting of agenda items, Categories, Presentation and sorting | |
a7808fba | 6108 | @subsection Time-of-day specifications |
4009494e GM |
6109 | @cindex time-of-day specification |
6110 | ||
a7808fba | 6111 | Org mode checks each agenda item for a time-of-day specification. The |
4009494e GM |
6112 | time can be part of the time stamp that triggered inclusion into the |
6113 | agenda, for example as in @w{@samp{<2005-05-10 Tue 19:00>}}. Time | |
6114 | ranges can be specified with two time stamps, like | |
6115 | @c | |
6116 | @w{@samp{<2005-05-10 Tue 20:30>--<2005-05-10 Tue 22:15>}}. | |
6117 | ||
6118 | In the headline of the entry itself, a time(range) may also appear as | |
44ce9197 | 6119 | plain text (like @samp{12:45} or a @samp{8:30-1pm}). If the agenda |
a7808fba | 6120 | integrates the Emacs diary (@pxref{Weekly/daily agenda}), time |
4009494e GM |
6121 | specifications in diary entries are recognized as well. |
6122 | ||
a7808fba | 6123 | For agenda display, Org mode extracts the time and displays it in a |
4009494e GM |
6124 | standard 24 hour format as part of the prefix. The example times in |
6125 | the previous paragraphs would end up in the agenda like this: | |
6126 | ||
6127 | @example | |
6128 | 8:30-13:00 Arthur Dent lies in front of the bulldozer | |
6129 | 12:45...... Ford Prefect arrives and takes Arthur to the pub | |
6130 | 19:00...... The Vogon reads his poem | |
a50253cc | 6131 | 20:30-22:15 Marvin escorts the Hitchhikers to the bridge |
4009494e GM |
6132 | @end example |
6133 | ||
6134 | @cindex time grid | |
6135 | If the agenda is in single-day mode, or for the display of today, the | |
6136 | timed entries are embedded in a time grid, like | |
6137 | ||
6138 | @example | |
6139 | 8:00...... ------------------ | |
6140 | 8:30-13:00 Arthur Dent lies in front of the bulldozer | |
6141 | 10:00...... ------------------ | |
6142 | 12:00...... ------------------ | |
6143 | 12:45...... Ford Prefect arrives and takes Arthur to the pub | |
6144 | 14:00...... ------------------ | |
6145 | 16:00...... ------------------ | |
6146 | 18:00...... ------------------ | |
6147 | 19:00...... The Vogon reads his poem | |
6148 | 20:00...... ------------------ | |
2096a1b6 | 6149 | 20:30-22:15 Marvin escorts the Hitchhikers to the bridge |
4009494e GM |
6150 | @end example |
6151 | ||
6152 | The time grid can be turned on and off with the variable | |
6153 | @code{org-agenda-use-time-grid}, and can be configured with | |
6154 | @code{org-agenda-time-grid}. | |
6155 | ||
6156 | @node Sorting of agenda items, , Time-of-day specifications, Presentation and sorting | |
6157 | @subsection Sorting of agenda items | |
6158 | @cindex sorting, of agenda items | |
6159 | @cindex priorities, of agenda items | |
6160 | Before being inserted into a view, the items are sorted. How this is | |
6161 | done depends on the type of view. | |
6162 | @itemize @bullet | |
6163 | @item | |
6164 | For the daily/weekly agenda, the items for each day are sorted. The | |
6165 | default order is to first collect all items containing an explicit | |
6166 | time-of-day specification. These entries will be shown at the beginning | |
6167 | of the list, as a @emph{schedule} for the day. After that, items remain | |
6168 | grouped in categories, in the sequence given by @code{org-agenda-files}. | |
6169 | Within each category, items are sorted by priority (@pxref{Priorities}), | |
6170 | which is composed of the base priority (2000 for priority @samp{A}, 1000 | |
6171 | for @samp{B}, and 0 for @samp{C}), plus additional increments for | |
6172 | overdue scheduled or deadline items. | |
28a16a1b | 6173 | @item |
4009494e GM |
6174 | For the TODO list, items remain in the order of categories, but within |
6175 | each category, sorting takes place according to priority | |
6176 | (@pxref{Priorities}). | |
6177 | @item | |
6178 | For tags matches, items are not sorted at all, but just appear in the | |
6179 | sequence in which they are found in the agenda files. | |
6180 | @end itemize | |
6181 | ||
6182 | Sorting can be customized using the variable | |
a7808fba | 6183 | @code{org-agenda-sorting-strategy}, and may also include criteria based on |
71d35b24 | 6184 | the estimated effort of an entry (@pxref{Effort estimates}). |
4009494e | 6185 | |
a7808fba | 6186 | @node Agenda commands, Custom agenda views, Presentation and sorting, Agenda Views |
4009494e GM |
6187 | @section Commands in the agenda buffer |
6188 | @cindex commands, in agenda buffer | |
6189 | ||
6190 | Entries in the agenda buffer are linked back to the org file or diary | |
6191 | file where they originate. You are not allowed to edit the agenda | |
6192 | buffer itself, but commands are provided to show and jump to the | |
6193 | original entry location, and to edit the org-files ``remotely'' from | |
6194 | the agenda buffer. In this way, all information is stored only once, | |
6195 | removing the risk that your agenda and note files may diverge. | |
6196 | ||
6197 | Some commands can be executed with mouse clicks on agenda lines. For | |
6198 | the other commands, the cursor needs to be in the desired line. | |
6199 | ||
6200 | @table @kbd | |
6201 | @tsubheading{Motion} | |
6202 | @cindex motion commands in agenda | |
6203 | @kindex n | |
6204 | @item n | |
dbc28aaa | 6205 | Next line (same as @key{up} and @kbd{C-p}). |
4009494e GM |
6206 | @kindex p |
6207 | @item p | |
dbc28aaa | 6208 | Previous line (same as @key{down} and @kbd{C-n}). |
a7808fba | 6209 | @tsubheading{View/Go to org file} |
4009494e GM |
6210 | @kindex mouse-3 |
6211 | @kindex @key{SPC} | |
6212 | @item mouse-3 | |
6213 | @itemx @key{SPC} | |
6214 | Display the original location of the item in another window. | |
b6cb4cd5 CD |
6215 | With prefix arg, make sure that the entire entry is made visible in the |
6216 | outline, not only the heading. | |
4009494e GM |
6217 | @c |
6218 | @kindex L | |
6219 | @item L | |
6220 | Display original location and recenter that window. | |
6221 | @c | |
6222 | @kindex mouse-2 | |
6223 | @kindex mouse-1 | |
6224 | @kindex @key{TAB} | |
6225 | @item mouse-2 | |
6226 | @itemx mouse-1 | |
6227 | @itemx @key{TAB} | |
6228 | Go to the original location of the item in another window. Under Emacs | |
6229 | 22, @kbd{mouse-1} will also works for this. | |
6230 | @c | |
6231 | @kindex @key{RET} | |
6232 | @itemx @key{RET} | |
6233 | Go to the original location of the item and delete other windows. | |
6234 | @c | |
6235 | @kindex f | |
6236 | @item f | |
6237 | Toggle Follow mode. In Follow mode, as you move the cursor through | |
6238 | the agenda buffer, the other window always shows the corresponding | |
6239 | location in the org file. The initial setting for this mode in new | |
6240 | agenda buffers can be set with the variable | |
6241 | @code{org-agenda-start-with-follow-mode}. | |
6242 | @c | |
6243 | @kindex b | |
6244 | @item b | |
a7808fba CD |
6245 | Display the entire subtree of the current item in an indirect buffer. With a |
6246 | numeric prefix argument N, go up to level N and then take that tree. If N is | |
6247 | negative, go up that many levels. With a @kbd{C-u} prefix, do not remove the | |
6248 | previously used indirect buffer. | |
4009494e GM |
6249 | @c |
6250 | @kindex l | |
6251 | @item l | |
55e0839d | 6252 | Toggle Logbook mode. In Logbook mode, entries that were marked DONE while |
e45e3595 CD |
6253 | logging was on (variable @code{org-log-done}) are shown in the agenda, as are |
6254 | entries that have been clocked on that day. You can configure the entry | |
6255 | types that should be included in log mode using the variable | |
6256 | @code{org-agenda-log-mode-items}. When called with a @kbd{C-u} prefix, show | |
6257 | all possible logbook entries, including state changes. When called with two | |
6258 | prefix args @kbd{C-u C-u}, show only logging information, nothing else. | |
a7808fba | 6259 | @c |
44ce9197 CD |
6260 | @kindex v |
6261 | @item v | |
55e0839d CD |
6262 | Toggle Archives mode. In archives mode, trees that are marked |
6263 | @code{ARCHIVED} are also scanned when producing the agenda. When you call | |
6264 | this command with a @kbd{C-u} prefix argument, even all archive files are | |
6265 | included. To exit archives mode, press @kbd{v} again. | |
44ce9197 | 6266 | @c |
a7808fba CD |
6267 | @kindex R |
6268 | @item R | |
6269 | Toggle Clockreport mode. In clockreport mode, the daily/weekly agenda will | |
6270 | always show a table with the clocked times for the timespan and file scope | |
6271 | covered by the current agenda view. The initial setting for this mode in new | |
6272 | agenda buffers can be set with the variable | |
6273 | @code{org-agenda-start-with-clockreport-mode}. | |
4009494e GM |
6274 | |
6275 | @tsubheading{Change display} | |
6276 | @cindex display changing, in agenda | |
6277 | @kindex o | |
6278 | @item o | |
6279 | Delete other windows. | |
6280 | @c | |
6281 | @kindex d | |
6282 | @kindex w | |
6283 | @kindex m | |
6284 | @kindex y | |
6285 | @item d w m y | |
6286 | Switch to day/week/month/year view. When switching to day or week view, | |
a7808fba CD |
6287 | this setting becomes the default for subsequent agenda commands. Since |
6288 | month and year views are slow to create, they do not become the default. | |
6289 | A numeric prefix argument may be used to jump directly to a specific day | |
6290 | of the year, ISO week, month, or year, respectively. For example, | |
6291 | @kbd{32 d} jumps to February 1st, @kbd{9 w} to ISO week number 9. When | |
6292 | setting day, week, or month view, a year may be encoded in the prefix | |
6293 | argument as well. For example, @kbd{200712 w} will jump to week 12 in | |
6294 | 2007. If such a year specification has only one or two digits, it will | |
6295 | be mapped to the interval 1938-2037. | |
4009494e GM |
6296 | @c |
6297 | @kindex D | |
6298 | @item D | |
a7808fba | 6299 | Toggle the inclusion of diary entries. See @ref{Weekly/daily agenda}. |
4009494e | 6300 | @c |
28a16a1b CD |
6301 | @kindex G |
6302 | @item G | |
4009494e GM |
6303 | Toggle the time grid on and off. See also the variables |
6304 | @code{org-agenda-use-time-grid} and @code{org-agenda-time-grid}. | |
6305 | @c | |
6306 | @kindex r | |
6307 | @item r | |
6308 | Recreate the agenda buffer, for example to reflect the changes | |
6309 | after modification of the time stamps of items with S-@key{left} and | |
a7808fba | 6310 | S-@key{right}. When the buffer is the global TODO list, a prefix |
4009494e GM |
6311 | argument is interpreted to create a selective list for a specific TODO |
6312 | keyword. | |
28a16a1b CD |
6313 | @kindex g |
6314 | @item g | |
6315 | Same as @kbd{r}. | |
4009494e GM |
6316 | @c |
6317 | @kindex s | |
dbc28aaa | 6318 | @kindex C-x C-s |
4009494e | 6319 | @item s |
dbc28aaa | 6320 | @itemx C-x C-s |
a7808fba | 6321 | Save all Org buffers in the current Emacs session. |
4009494e GM |
6322 | @c |
6323 | @kindex @key{right} | |
6324 | @item @key{right} | |
6325 | Display the following @code{org-agenda-ndays} days. For example, if | |
6326 | the display covers a week, switch to the following week. With prefix | |
6327 | arg, go forward that many times @code{org-agenda-ndays} days. | |
6328 | @c | |
6329 | @kindex @key{left} | |
6330 | @item @key{left} | |
6331 | Display the previous dates. | |
6332 | @c | |
6333 | @kindex . | |
6334 | @item . | |
a7808fba CD |
6335 | Go to today. |
6336 | @c | |
6337 | @kindex C-c C-x C-c | |
6338 | @item C-c C-x C-c | |
6339 | Invoke column view (@pxref{Column view}) in the agenda buffer. The column | |
6340 | view format is taken from the entry at point, or (if there is no entry at | |
6341 | point), from the first entry in the agenda view. So whatever the format for | |
6342 | that entry would be in the original buffer (taken from a property, from a | |
6343 | @code{#+COLUMNS} line, or from the default variable | |
6344 | @code{org-columns-default-format}), will be used in the agenda. | |
4009494e | 6345 | |
864c9740 | 6346 | @tsubheading{Secondary filtering and query editing} |
71d35b24 CD |
6347 | @cindex filtering, by tag and effort, in agenda |
6348 | @cindex tag filtering, in agenda | |
6349 | @cindex effort filtering, in agenda | |
28a16a1b CD |
6350 | @cindex query editing, in agenda |
6351 | ||
864c9740 CD |
6352 | @kindex / |
6353 | @item / | |
71d35b24 CD |
6354 | Filter the current agenda view with respect to a tag and/or effort estimates. |
6355 | The difference between this and a custom agenda commands is that filtering is | |
6356 | very fast, so that you can switch quickly between different filters without | |
6357 | having to recreate the agenda. | |
6358 | ||
6359 | You will be prompted for a tag selection letter. Pressing @key{TAB} at that | |
6360 | prompt will offer use completion to select a tag (including any tags that do | |
6361 | not have a selection character). The command then hides all entries that do | |
6362 | not contain or inherit this tag. When called with prefix arg, remove the | |
6363 | entries that @emph{do} have the tag. A second @kbd{/} at the prompt will | |
6364 | turn off the filter and unhide any hidden entries. If the first key you | |
6365 | press is either @kbd{+} or @kbd{-}, the previous filter will be narrowed by | |
6366 | requiring or forbidding the selected additional tag. Instead of pressing | |
64fb801f CD |
6367 | @kbd{+} or @kbd{-} after @kbd{/}, you can also immediately use the @kbd{\} |
6368 | command. | |
71d35b24 CD |
6369 | |
6370 | In order to filter for effort estimates, you should set-up allowed | |
6371 | efforts globally, for example | |
6372 | @lisp | |
6373 | (setq org-global-properties | |
6374 | '(("Effort_ALL". "0 0:10 0:30 1:00 2:00 3:00 4:00"))) | |
6375 | @end lisp | |
6376 | You can then filter for an effort by first typing an operator, one of @kbd{<}, | |
6377 | @kbd{>}, and @kbd{=}, and then the one-digit index of an effort estimate in | |
6378 | your array of allowed values, where @kbd{0} means the 10th value. The filter | |
6379 | will then restrict to entries with effort smaller-or-equal, equal, or | |
6380 | larger-or-equal than the selected value. If the digits 0-9 are not used as | |
6381 | fast access keys to tags, you can also simply press the index digit directly | |
6382 | without an operator. In this case, @kbd{<} will be assumed. | |
6383 | ||
6384 | @kindex \ | |
6385 | @item \ | |
6386 | Narrow the current agenda filter by an additional condition. When called with | |
6387 | prefix arg, remove the entries that @emph{do} have the tag, or that do match | |
6388 | the effort criterion. You can achieve the same effect by pressing @kbd{+} or | |
6389 | @kbd{-} as the first key after the @kbd{/} command. | |
864c9740 | 6390 | |
28a16a1b CD |
6391 | @kindex [ |
6392 | @kindex ] | |
6393 | @kindex @{ | |
6394 | @kindex @} | |
6395 | @item [ ] @{ @} | |
864c9740 CD |
6396 | In the @i{search view} (@pxref{Keyword search}), these keys add new search |
6397 | words (@kbd{[} and @kbd{]}) or new regular expressions (@kbd{@{} and | |
6398 | @kbd{@}}) to the query string. The opening bracket/brace will add a positive | |
6399 | search term prefixed by @samp{+}, indicating that this search term @i{must} | |
6400 | occur/match in the entry. The closing bracket/brace will add a negative | |
6401 | search term which @i{must not} occur/match in the entry for it to be | |
6402 | selected. | |
28a16a1b CD |
6403 | |
6404 | ||
4009494e GM |
6405 | @tsubheading{Remote editing} |
6406 | @cindex remote editing, from agenda | |
6407 | ||
6408 | @item 0-9 | |
6409 | Digit argument. | |
6410 | @c | |
6411 | @cindex undoing remote-editing events | |
6412 | @cindex remote editing, undo | |
6413 | @kindex C-_ | |
6414 | @item C-_ | |
6415 | Undo a change due to a remote editing command. The change is undone | |
6416 | both in the agenda buffer and in the remote buffer. | |
6417 | @c | |
6418 | @kindex t | |
6419 | @item t | |
6420 | Change the TODO state of the item, both in the agenda and in the | |
6421 | original org file. | |
6422 | @c | |
6423 | @kindex C-k | |
6424 | @item C-k | |
6425 | Delete the current agenda item along with the entire subtree belonging | |
a7808fba | 6426 | to it in the original Org file. If the text to be deleted remotely |
4009494e GM |
6427 | is longer than one line, the kill needs to be confirmed by the user. See |
6428 | variable @code{org-agenda-confirm-kill}. | |
6429 | @c | |
a7808fba CD |
6430 | @kindex a |
6431 | @item a | |
6432 | Toggle the ARCHIVE tag for the current headline. | |
6433 | @c | |
6434 | @kindex A | |
6435 | @item A | |
b349f79f | 6436 | Move the subtree corresponding to the current entry to its @emph{Archive |
a7808fba CD |
6437 | Sibling}. |
6438 | @c | |
4009494e GM |
6439 | @kindex $ |
6440 | @item $ | |
a7808fba | 6441 | Archive the subtree corresponding to the current headline. This means the |
b349f79f | 6442 | entry will be moved to the configured archive location, most likely a |
a7808fba | 6443 | different file. |
4009494e GM |
6444 | @c |
6445 | @kindex T | |
6446 | @item T | |
96c8522a CD |
6447 | Show all tags associated with the current item. This is useful if you have |
6448 | turned off @code{org-agenda-show-inherited-tags}, but still want to see all | |
6449 | tags of a headline occasionally. | |
4009494e GM |
6450 | @c |
6451 | @kindex : | |
6452 | @item : | |
dbc28aaa CD |
6453 | Set tags for the current headline. If there is an active region in the |
6454 | agenda, change a tag for all headings in the region. | |
4009494e | 6455 | @c |
4009494e GM |
6456 | @kindex , |
6457 | @item , | |
a7808fba | 6458 | Set the priority for the current item. Org mode prompts for the |
4009494e GM |
6459 | priority character. If you reply with @key{SPC}, the priority cookie |
6460 | is removed from the entry. | |
6461 | @c | |
6462 | @kindex P | |
6463 | @item P | |
6464 | Display weighted priority of current item. | |
6465 | @c | |
6466 | @kindex + | |
6467 | @kindex S-@key{up} | |
6468 | @item + | |
6469 | @itemx S-@key{up} | |
6470 | Increase the priority of the current item. The priority is changed in | |
6471 | the original buffer, but the agenda is not resorted. Use the @kbd{r} | |
6472 | key for this. | |
6473 | @c | |
6474 | @kindex - | |
6475 | @kindex S-@key{down} | |
6476 | @item - | |
6477 | @itemx S-@key{down} | |
6478 | Decrease the priority of the current item. | |
6479 | @c | |
864c9740 CD |
6480 | @kindex C-c C-a |
6481 | @item C-c C-a | |
6482 | Dispatcher for all command related to attachments. | |
6483 | @c | |
4009494e GM |
6484 | @kindex C-c C-s |
6485 | @item C-c C-s | |
6486 | Schedule this item | |
6487 | @c | |
6488 | @kindex C-c C-d | |
6489 | @item C-c C-d | |
6490 | Set a deadline for this item. | |
6491 | @c | |
b349f79f CD |
6492 | @kindex k |
6493 | @item k | |
6494 | Agenda actions, to set dates for selected items to the cursor date. | |
6495 | This command also works in the calendar! The command prompts for an | |
a50253cc | 6496 | additional key: |
b349f79f CD |
6497 | @example |
6498 | m @r{Mark the entry at point for action. You can also make entries} | |
6499 | @r{in Org files with @kbd{C-c C-x C-k}.} | |
6500 | d @r{Set the deadline of the marked entry to the date at point.} | |
6501 | s @r{Schedule the marked entry at the date at point.} | |
6502 | r @r{Call @code{org-remember} with the cursor date as default date.} | |
6503 | @end example | |
a50253cc | 6504 | Press @kbd{r} afterward to refresh the agenda and see the effect of the |
b349f79f CD |
6505 | command. |
6506 | @c | |
4009494e GM |
6507 | @kindex S-@key{right} |
6508 | @item S-@key{right} | |
a7808fba CD |
6509 | Change the time stamp associated with the current line by one day into the |
6510 | future. With a numeric prefix argument, change it by that many days. For | |
6511 | example, @kbd{3 6 5 S-@key{right}} will change it by a year. The stamp is | |
6512 | changed in the original org file, but the change is not directly reflected in | |
6513 | the agenda buffer. Use the @kbd{r} key to update the buffer. | |
4009494e GM |
6514 | @c |
6515 | @kindex S-@key{left} | |
6516 | @item S-@key{left} | |
6517 | Change the time stamp associated with the current line by one day | |
6518 | into the past. | |
6519 | @c | |
6520 | @kindex > | |
6521 | @item > | |
6522 | Change the time stamp associated with the current line to today. | |
6523 | The key @kbd{>} has been chosen, because it is the same as @kbd{S-.} | |
6524 | on my keyboard. | |
6525 | @c | |
6526 | @kindex I | |
6527 | @item I | |
6528 | Start the clock on the current item. If a clock is running already, it | |
6529 | is stopped first. | |
6530 | @c | |
6531 | @kindex O | |
6532 | @item O | |
6533 | Stop the previously started clock. | |
6534 | @c | |
6535 | @kindex X | |
6536 | @item X | |
6537 | Cancel the currently running clock. | |
6538 | ||
dbc28aaa CD |
6539 | @kindex J |
6540 | @item J | |
6541 | Jump to the running clock in another window. | |
6542 | ||
4009494e GM |
6543 | @tsubheading{Calendar commands} |
6544 | @cindex calendar commands, from agenda | |
6545 | @kindex c | |
6546 | @item c | |
6547 | Open the Emacs calendar and move to the date at the agenda cursor. | |
6548 | @c | |
6549 | @item c | |
a7808fba | 6550 | When in the calendar, compute and show the Org mode agenda for the |
4009494e GM |
6551 | date at the cursor. |
6552 | @c | |
6553 | @cindex diary entries, creating from agenda | |
6554 | @kindex i | |
6555 | @item i | |
6556 | Insert a new entry into the diary. Prompts for the type of entry | |
6557 | (day, weekly, monthly, yearly, anniversary, cyclic) and creates a new | |
6558 | entry in the diary, just as @kbd{i d} etc. would do in the calendar. | |
6559 | The date is taken from the cursor position. | |
6560 | @c | |
6561 | @kindex M | |
6562 | @item M | |
6563 | Show the phases of the moon for the three months around current date. | |
6564 | @c | |
6565 | @kindex S | |
6566 | @item S | |
6567 | Show sunrise and sunset times. The geographical location must be set | |
6568 | with calendar variables, see documentation of the Emacs calendar. | |
6569 | @c | |
6570 | @kindex C | |
6571 | @item C | |
6572 | Convert the date at cursor into many other cultural and historic | |
6573 | calendars. | |
6574 | @c | |
6575 | @kindex H | |
6576 | @item H | |
6577 | Show holidays for three month around the cursor date. | |
a7808fba CD |
6578 | |
6579 | @item M-x org-export-icalendar-combine-agenda-files | |
4009494e | 6580 | Export a single iCalendar file containing entries from all agenda files. |
a7808fba | 6581 | This is a globally available command, and also available in the agenda menu. |
4009494e GM |
6582 | |
6583 | @tsubheading{Exporting to a file} | |
6584 | @kindex C-x C-w | |
6585 | @item C-x C-w | |
6586 | @cindex exporting agenda views | |
6587 | @cindex agenda views, exporting | |
6588 | Write the agenda view to a file. Depending on the extension of the | |
6589 | selected file name, the view will be exported as HTML (extension | |
6590 | @file{.html} or @file{.htm}), Postscript (extension @file{.ps}), or | |
6591 | plain text (any other extension). Use the variable | |
6592 | @code{org-agenda-exporter-settings} to set options for @file{ps-print} | |
6593 | and for @file{htmlize} to be used during export. | |
6594 | ||
6595 | @tsubheading{Quit and Exit} | |
6596 | @kindex q | |
6597 | @item q | |
6598 | Quit agenda, remove the agenda buffer. | |
6599 | @c | |
6600 | @kindex x | |
6601 | @cindex agenda files, removing buffers | |
6602 | @item x | |
6603 | Exit agenda, remove the agenda buffer and all buffers loaded by Emacs | |
6604 | for the compilation of the agenda. Buffers created by the user to | |
6605 | visit org files will not be removed. | |
6606 | @end table | |
6607 | ||
6608 | ||
a7808fba | 6609 | @node Custom agenda views, Agenda column view, Agenda commands, Agenda Views |
4009494e GM |
6610 | @section Custom agenda views |
6611 | @cindex custom agenda views | |
6612 | @cindex agenda views, custom | |
6613 | ||
6614 | Custom agenda commands serve two purposes: to store and quickly access | |
6615 | frequently used TODO and tags searches, and to create special composite | |
6616 | agenda buffers. Custom agenda commands will be accessible through the | |
6617 | dispatcher (@pxref{Agenda dispatcher}), just like the default commands. | |
6618 | ||
6619 | @menu | |
6620 | * Storing searches:: Type once, use often | |
6621 | * Block agenda:: All the stuff you need in a single buffer | |
6622 | * Setting Options:: Changing the rules | |
a7808fba CD |
6623 | * Exporting Agenda Views:: Writing agendas to files |
6624 | * Using the agenda elsewhere:: Using agenda information in other programs | |
4009494e GM |
6625 | @end menu |
6626 | ||
6627 | @node Storing searches, Block agenda, Custom agenda views, Custom agenda views | |
6628 | @subsection Storing searches | |
6629 | ||
6630 | The first application of custom searches is the definition of keyboard | |
6631 | shortcuts for frequently used searches, either creating an agenda | |
6632 | buffer, or a sparse tree (the latter covering of course only the current | |
6633 | buffer). | |
6634 | @kindex C-c a C | |
6635 | Custom commands are configured in the variable | |
6636 | @code{org-agenda-custom-commands}. You can customize this variable, for | |
6637 | example by pressing @kbd{C-c a C}. You can also directly set it with | |
6638 | Emacs Lisp in @file{.emacs}. The following example contains all valid | |
6639 | search types: | |
6640 | ||
6641 | @lisp | |
6642 | @group | |
6643 | (setq org-agenda-custom-commands | |
6644 | '(("w" todo "WAITING") | |
6645 | ("W" todo-tree "WAITING") | |
dbc28aaa CD |
6646 | ("u" tags "+boss-urgent") |
6647 | ("v" tags-todo "+boss-urgent") | |
6648 | ("U" tags-tree "+boss-urgent") | |
6649 | ("f" occur-tree "\\<FIXME\\>") | |
6650 | ("h" . "HOME+Name tags searches") ; description for "h" prefix | |
6651 | ("hl" tags "+home+Lisa") | |
6652 | ("hp" tags "+home+Peter") | |
6653 | ("hk" tags "+home+Kim"))) | |
4009494e GM |
6654 | @end group |
6655 | @end lisp | |
6656 | ||
6657 | @noindent | |
dbc28aaa CD |
6658 | The initial string in each entry defines the keys you have to press |
6659 | after the dispatcher command @kbd{C-c a} in order to access the command. | |
6660 | Usually this will be just a single character, but if you have many | |
6661 | similar commands, you can also define two-letter combinations where the | |
6662 | first character is the same in several combinations and serves as a | |
6663 | prefix key@footnote{You can provide a description for a prefix key by | |
6664 | inserting a cons cell with the prefix and the description.}. The second | |
6665 | parameter is the search type, followed by the string or regular | |
6666 | expression to be used for the matching. The example above will | |
6667 | therefore define: | |
4009494e GM |
6668 | |
6669 | @table @kbd | |
6670 | @item C-c a w | |
6671 | as a global search for TODO entries with @samp{WAITING} as the TODO | |
6672 | keyword | |
6673 | @item C-c a W | |
6674 | as the same search, but only in the current buffer and displaying the | |
6675 | results as a sparse tree | |
6676 | @item C-c a u | |
dbc28aaa CD |
6677 | as a global tags search for headlines marked @samp{:boss:} but not |
6678 | @samp{:urgent:} | |
4009494e GM |
6679 | @item C-c a v |
6680 | as the same search as @kbd{C-c a u}, but limiting the search to | |
6681 | headlines that are also TODO items | |
6682 | @item C-c a U | |
6683 | as the same search as @kbd{C-c a u}, but only in the current buffer and | |
6684 | displaying the result as a sparse tree | |
6685 | @item C-c a f | |
6686 | to create a sparse tree (again: current buffer only) with all entries | |
dbc28aaa CD |
6687 | containing the word @samp{FIXME} |
6688 | @item C-c a h | |
6689 | as a prefix command for a HOME tags search where you have to press an | |
6690 | additional key (@kbd{l}, @kbd{p} or @kbd{k}) to select a name (Lisa, | |
6691 | Peter, or Kim) as additional tag to match. | |
4009494e GM |
6692 | @end table |
6693 | ||
6694 | @node Block agenda, Setting Options, Storing searches, Custom agenda views | |
6695 | @subsection Block agenda | |
6696 | @cindex block agenda | |
6697 | @cindex agenda, with block views | |
6698 | ||
6699 | Another possibility is the construction of agenda views that comprise | |
6700 | the results of @emph{several} commands, each of which creates a block in | |
6701 | the agenda buffer. The available commands include @code{agenda} for the | |
6702 | daily or weekly agenda (as created with @kbd{C-c a a}), @code{alltodo} | |
a7808fba | 6703 | for the global TODO list (as constructed with @kbd{C-c a t}), and the |
4009494e GM |
6704 | matching commands discussed above: @code{todo}, @code{tags}, and |
6705 | @code{tags-todo}. Here are two examples: | |
6706 | ||
6707 | @lisp | |
6708 | @group | |
6709 | (setq org-agenda-custom-commands | |
6710 | '(("h" "Agenda and Home-related tasks" | |
28a16a1b | 6711 | ((agenda "") |
dbc28aaa CD |
6712 | (tags-todo "home") |
6713 | (tags "garden"))) | |
4009494e | 6714 | ("o" "Agenda and Office-related tasks" |
28a16a1b | 6715 | ((agenda "") |
dbc28aaa CD |
6716 | (tags-todo "work") |
6717 | (tags "office"))))) | |
4009494e GM |
6718 | @end group |
6719 | @end lisp | |
6720 | ||
6721 | @noindent | |
6722 | This will define @kbd{C-c a h} to create a multi-block view for stuff | |
6723 | you need to attend to at home. The resulting agenda buffer will contain | |
6724 | your agenda for the current week, all TODO items that carry the tag | |
dbc28aaa | 6725 | @samp{home}, and also all lines tagged with @samp{garden}. Finally the |
4009494e GM |
6726 | command @kbd{C-c a o} provides a similar view for office tasks. |
6727 | ||
4009494e | 6728 | @node Setting Options, Exporting Agenda Views, Block agenda, Custom agenda views |
a7808fba | 6729 | @subsection Setting options for custom commands |
4009494e GM |
6730 | @cindex options, for custom agenda views |
6731 | ||
a7808fba | 6732 | Org mode contains a number of variables regulating agenda construction |
4009494e GM |
6733 | and display. The global variables define the behavior for all agenda |
6734 | commands, including the custom commands. However, if you want to change | |
6735 | some settings just for a single custom view, you can do so. Setting | |
6736 | options requires inserting a list of variable names and values at the | |
6737 | right spot in @code{org-agenda-custom-commands}. For example: | |
6738 | ||
6739 | @lisp | |
6740 | @group | |
6741 | (setq org-agenda-custom-commands | |
6742 | '(("w" todo "WAITING" | |
6743 | ((org-agenda-sorting-strategy '(priority-down)) | |
6744 | (org-agenda-prefix-format " Mixed: "))) | |
dbc28aaa | 6745 | ("U" tags-tree "+boss-urgent" |
4009494e | 6746 | ((org-show-following-heading nil) |
28a16a1b CD |
6747 | (org-show-hierarchy-above nil))) |
6748 | ("N" search "" | |
6749 | ((org-agenda-files '("~org/notes.org")) | |
6750 | (org-agenda-text-search-extra-files nil))))) | |
4009494e GM |
6751 | @end group |
6752 | @end lisp | |
6753 | ||
6754 | @noindent | |
6755 | Now the @kbd{C-c a w} command will sort the collected entries only by | |
dbc28aaa | 6756 | priority, and the prefix format is modified to just say @samp{ Mixed: } |
4009494e GM |
6757 | instead of giving the category of the entry. The sparse tags tree of |
6758 | @kbd{C-c a U} will now turn out ultra-compact, because neither the | |
6759 | headline hierarchy above the match, nor the headline following the match | |
28a16a1b CD |
6760 | will be shown. The command @kbd{C-c a N} will do a text search limited |
6761 | to only a single file. | |
4009494e GM |
6762 | |
6763 | For command sets creating a block agenda, | |
6764 | @code{org-agenda-custom-commands} has two separate spots for setting | |
6765 | options. You can add options that should be valid for just a single | |
6766 | command in the set, and options that should be valid for all commands in | |
6767 | the set. The former are just added to the command entry, the latter | |
6768 | must come after the list of command entries. Going back to the block | |
6769 | agenda example (@pxref{Block agenda}), let's change the sorting strategy | |
6770 | for the @kbd{C-c a h} commands to @code{priority-down}, but let's sort | |
6771 | the results for GARDEN tags query in the opposite order, | |
6772 | @code{priority-up}. This would look like this: | |
6773 | ||
6774 | @lisp | |
6775 | @group | |
6776 | (setq org-agenda-custom-commands | |
6777 | '(("h" "Agenda and Home-related tasks" | |
6778 | ((agenda) | |
dbc28aaa CD |
6779 | (tags-todo "home") |
6780 | (tags "garden" | |
4009494e GM |
6781 | ((org-agenda-sorting-strategy '(priority-up))))) |
6782 | ((org-agenda-sorting-strategy '(priority-down)))) | |
6783 | ("o" "Agenda and Office-related tasks" | |
6784 | ((agenda) | |
dbc28aaa CD |
6785 | (tags-todo "work") |
6786 | (tags "office"))))) | |
4009494e GM |
6787 | @end group |
6788 | @end lisp | |
6789 | ||
6790 | As you see, the values and parenthesis setting is a little complex. | |
6791 | When in doubt, use the customize interface to set this variable - it | |
6792 | fully supports its structure. Just one caveat: When setting options in | |
6793 | this interface, the @emph{values} are just lisp expressions. So if the | |
6794 | value is a string, you need to add the double quotes around the value | |
6795 | yourself. | |
6796 | ||
6797 | ||
a7808fba | 6798 | @node Exporting Agenda Views, Using the agenda elsewhere, Setting Options, Custom agenda views |
4009494e GM |
6799 | @subsection Exporting Agenda Views |
6800 | @cindex agenda views, exporting | |
6801 | ||
3da3282e CD |
6802 | If you are away from your computer, it can be very useful to have a printed |
6803 | version of some agenda views to carry around. Org mode can export custom | |
6804 | agenda views as plain text, HTML@footnote{You need to install Hrvoje Niksic's | |
6805 | @file{htmlize.el}.}, Postscript, and iCalendar files. If you want to do this | |
6806 | only occasionally, use the command | |
4009494e GM |
6807 | |
6808 | @table @kbd | |
6809 | @kindex C-x C-w | |
6810 | @item C-x C-w | |
6811 | @cindex exporting agenda views | |
6812 | @cindex agenda views, exporting | |
6813 | Write the agenda view to a file. Depending on the extension of the | |
6814 | selected file name, the view will be exported as HTML (extension | |
28a16a1b CD |
6815 | @file{.html} or @file{.htm}), Postscript (extension @file{.ps}), |
6816 | iCalendar (extension @file{.ics}), or plain text (any other extension). | |
6817 | Use the variable @code{org-agenda-exporter-settings} to | |
6818 | set options for @file{ps-print} and for @file{htmlize} to be used during | |
6819 | export, for example | |
6820 | ||
4009494e GM |
6821 | @lisp |
6822 | (setq org-agenda-exporter-settings | |
6823 | '((ps-number-of-columns 2) | |
6824 | (ps-landscape-mode t) | |
6825 | (htmlize-output-type 'css))) | |
6826 | @end lisp | |
6827 | @end table | |
6828 | ||
6829 | If you need to export certain agenda views frequently, you can associate | |
6830 | any custom agenda command with a list of output file names | |
6831 | @footnote{If you want to store standard views like the weekly agenda | |
6832 | or the global TODO list as well, you need to define custom commands for | |
28a16a1b | 6833 | them in order to be able to specify file names.}. Here is an example |
4009494e GM |
6834 | that first does define custom commands for the agenda and the global |
6835 | todo list, together with a number of files to which to export them. | |
28a16a1b | 6836 | Then we define two block agenda commands and specify file names for them |
4009494e GM |
6837 | as well. File names can be relative to the current working directory, |
6838 | or absolute. | |
6839 | ||
6840 | @lisp | |
6841 | @group | |
6842 | (setq org-agenda-custom-commands | |
6843 | '(("X" agenda "" nil ("agenda.html" "agenda.ps")) | |
6844 | ("Y" alltodo "" nil ("todo.html" "todo.txt" "todo.ps")) | |
6845 | ("h" "Agenda and Home-related tasks" | |
28a16a1b | 6846 | ((agenda "") |
dbc28aaa CD |
6847 | (tags-todo "home") |
6848 | (tags "garden")) | |
4009494e GM |
6849 | nil |
6850 | ("~/views/home.html")) | |
6851 | ("o" "Agenda and Office-related tasks" | |
6852 | ((agenda) | |
dbc28aaa CD |
6853 | (tags-todo "work") |
6854 | (tags "office")) | |
4009494e | 6855 | nil |
28a16a1b | 6856 | ("~/views/office.ps" "~/calendars/office.ics")))) |
4009494e GM |
6857 | @end group |
6858 | @end lisp | |
6859 | ||
6860 | The extension of the file name determines the type of export. If it is | |
a7808fba | 6861 | @file{.html}, Org mode will use the @file{htmlize.el} package to convert |
4009494e GM |
6862 | the buffer to HTML and save it to this file name. If the extension is |
6863 | @file{.ps}, @code{ps-print-buffer-with-faces} is used to produce | |
28a16a1b CD |
6864 | postscript output. If the extension is @file{.ics}, iCalendar export is |
6865 | run export over all files that were used to construct the agenda, and | |
6866 | limit the export to entries listed in the agenda now. Any other | |
6867 | extension produces a plain ASCII file. | |
4009494e GM |
6868 | |
6869 | The export files are @emph{not} created when you use one of those | |
28a16a1b CD |
6870 | commands interactively because this might use too much overhead. |
6871 | Instead, there is a special command to produce @emph{all} specified | |
6872 | files in one step: | |
4009494e GM |
6873 | |
6874 | @table @kbd | |
6875 | @kindex C-c a e | |
6876 | @item C-c a e | |
28a16a1b | 6877 | Export all agenda views that have export file names associated with |
4009494e GM |
6878 | them. |
6879 | @end table | |
6880 | ||
6881 | You can use the options section of the custom agenda commands to also | |
6882 | set options for the export commands. For example: | |
6883 | ||
6884 | @lisp | |
6885 | (setq org-agenda-custom-commands | |
6886 | '(("X" agenda "" | |
6887 | ((ps-number-of-columns 2) | |
6888 | (ps-landscape-mode t) | |
6889 | (org-agenda-prefix-format " [ ] ") | |
6890 | (org-agenda-with-colors nil) | |
6891 | (org-agenda-remove-tags t)) | |
6892 | ("theagenda.ps")))) | |
6893 | @end lisp | |
6894 | ||
6895 | @noindent | |
6896 | This command sets two options for the postscript exporter, to make it | |
6897 | print in two columns in landscape format - the resulting page can be cut | |
6898 | in two and then used in a paper agenda. The remaining settings modify | |
6899 | the agenda prefix to omit category and scheduling information, and | |
6900 | instead include a checkbox to check off items. We also remove the tags | |
6901 | to make the lines compact, and we don't want to use colors for the | |
6902 | black-and-white printer. Settings specified in | |
6903 | @code{org-agenda-exporter-settings} will also apply, but the settings | |
6904 | in @code{org-agenda-custom-commands} take precedence. | |
6905 | ||
6906 | @noindent | |
6907 | From the command line you may also use | |
6908 | @example | |
6909 | emacs -f org-batch-store-agenda-views -kill | |
6910 | @end example | |
6911 | @noindent | |
71d35b24 CD |
6912 | or, if you need to modify some parameters@footnote{Quoting may depend on the |
6913 | system you use, please check th FAQ for examples.} | |
4009494e GM |
6914 | @example |
6915 | emacs -eval '(org-batch-store-agenda-views \ | |
6916 | org-agenda-ndays 30 \ | |
dbc28aaa | 6917 | org-agenda-start-day "2007-11-01" \ |
4009494e GM |
6918 | org-agenda-include-diary nil \ |
6919 | org-agenda-files (quote ("~/org/project.org")))' \ | |
6920 | -kill | |
6921 | @end example | |
6922 | @noindent | |
6923 | which will create the agenda views restricted to the file | |
6924 | @file{~/org/project.org}, without diary entries and with 30 days | |
28a16a1b | 6925 | extent. |
4009494e | 6926 | |
a7808fba CD |
6927 | @node Using the agenda elsewhere, , Exporting Agenda Views, Custom agenda views |
6928 | @subsection Using agenda information outside of Org | |
4009494e GM |
6929 | @cindex agenda, pipe |
6930 | @cindex Scripts, for agenda processing | |
6931 | ||
a7808fba | 6932 | Org provides commands to access agenda information for the command |
4009494e GM |
6933 | line in emacs batch mode. This extracted information can be sent |
6934 | directly to a printer, or it can be read by a program that does further | |
6935 | processing of the data. The first of these commands is the function | |
6936 | @code{org-batch-agenda}, that produces an agenda view and sends it as | |
6937 | ASCII text to STDOUT. The command takes a single string as parameter. | |
6938 | If the string has length 1, it is used as a key to one of the commands | |
6939 | you have configured in @code{org-agenda-custom-commands}, basically any | |
6940 | key you can use after @kbd{C-c a}. For example, to directly print the | |
6941 | current TODO list, you could use | |
6942 | ||
6943 | @example | |
6944 | emacs -batch -l ~/.emacs -eval '(org-batch-agenda "t")' | lpr | |
6945 | @end example | |
6946 | ||
6947 | If the parameter is a string with 2 or more characters, it is used as a | |
6948 | tags/todo match string. For example, to print your local shopping list | |
6949 | (all items with the tag @samp{shop}, but excluding the tag | |
6950 | @samp{NewYork}), you could use | |
6951 | ||
6952 | @example | |
28a16a1b | 6953 | emacs -batch -l ~/.emacs \ |
4009494e GM |
6954 | -eval '(org-batch-agenda "+shop-NewYork")' | lpr |
6955 | @end example | |
6956 | ||
6957 | @noindent | |
6958 | You may also modify parameters on the fly like this: | |
6959 | ||
6960 | @example | |
6961 | emacs -batch -l ~/.emacs \ | |
6962 | -eval '(org-batch-agenda "a" \ | |
6963 | org-agenda-ndays 30 \ | |
6964 | org-agenda-include-diary nil \ | |
6965 | org-agenda-files (quote ("~/org/project.org")))' \ | |
6966 | | lpr | |
6967 | @end example | |
6968 | ||
6969 | @noindent | |
6970 | which will produce a 30 day agenda, fully restricted to the Org file | |
6971 | @file{~/org/projects.org}, not even including the diary. | |
6972 | ||
6973 | If you want to process the agenda data in more sophisticated ways, you | |
6974 | can use the command @code{org-batch-agenda-csv} to get a comma-separated | |
6975 | list of values for each agenda item. Each line in the output will | |
6976 | contain a number of fields separated by commas. The fields in a line | |
6977 | are: | |
6978 | ||
6979 | @example | |
6980 | category @r{The category of the item} | |
6981 | head @r{The headline, without TODO kwd, TAGS and PRIORITY} | |
6982 | type @r{The type of the agenda entry, can be} | |
6983 | todo @r{selected in TODO match} | |
6984 | tagsmatch @r{selected in tags match} | |
6985 | diary @r{imported from diary} | |
6986 | deadline @r{a deadline} | |
6987 | scheduled @r{scheduled} | |
6988 | timestamp @r{appointment, selected by timestamp} | |
6989 | closed @r{entry was closed on date} | |
6990 | upcoming-deadline @r{warning about nearing deadline} | |
6991 | past-scheduled @r{forwarded scheduled item} | |
6992 | block @r{entry has date block including date} | |
a7808fba | 6993 | todo @r{The TODO keyword, if any} |
4009494e GM |
6994 | tags @r{All tags including inherited ones, separated by colons} |
6995 | date @r{The relevant date, like 2007-2-14} | |
6996 | time @r{The time, like 15:00-16:50} | |
6997 | extra @r{String with extra planning info} | |
6998 | priority-l @r{The priority letter if any was given} | |
6999 | priority-n @r{The computed numerical priority} | |
7000 | @end example | |
7001 | ||
7002 | @noindent | |
7003 | Time and date will only be given if a timestamp (or deadline/scheduled) | |
7004 | lead to the selection of the item. | |
7005 | ||
7006 | A CSV list like this is very easy to use in a post processing script. | |
7007 | For example, here is a Perl program that gets the TODO list from | |
a7808fba | 7008 | Emacs/Org and prints all the items, preceded by a checkbox: |
4009494e GM |
7009 | |
7010 | @example | |
7011 | @group | |
7012 | #!/usr/bin/perl | |
7013 | ||
7014 | # define the Emacs command to run | |
7015 | $cmd = "emacs -batch -l ~/.emacs -eval '(org-batch-agenda-csv \"t\")'"; | |
7016 | ||
7017 | # run it and capture the output | |
7018 | $agenda = qx@{$cmd 2>/dev/null@}; | |
7019 | ||
7020 | # loop over all lines | |
7021 | foreach $line (split(/\n/,$agenda)) @{ | |
7022 | ||
7023 | # get the individual values | |
7024 | ($category,$head,$type,$todo,$tags,$date,$time,$extra, | |
7025 | $priority_l,$priority_n) = split(/,/,$line); | |
7026 | ||
a50253cc | 7027 | # process and print |
4009494e GM |
7028 | print "[ ] $head\n"; |
7029 | @} | |
7030 | @end group | |
7031 | @end example | |
7032 | ||
a7808fba CD |
7033 | @node Agenda column view, , Custom agenda views, Agenda Views |
7034 | @section Using column view in the agenda | |
7035 | @cindex column view, in agenda | |
7036 | @cindex agenda, column view | |
7037 | ||
7038 | Column view (@pxref{Column view}) is normally used to view and edit | |
7039 | properties embedded in the hierarchical structure of an Org file. It can be | |
7040 | quite useful to use column view also from the agenda, where entries are | |
7041 | collected by certain criteria. | |
7042 | ||
7043 | @table @kbd | |
7044 | @kindex C-c C-x C-c | |
7045 | @item C-c C-x C-c | |
7046 | Turn on column view in the agenda. | |
7047 | @end table | |
7048 | ||
7049 | To understand how to use this properly, it is important to realize that the | |
7050 | entries in the agenda are no longer in their proper outline environment. | |
7051 | This causes the following issues: | |
7052 | ||
7053 | @enumerate | |
7054 | @item | |
7055 | Org needs to make a decision which @code{COLUMNS} format to use. Since the | |
7056 | entries in the agenda are collected from different files, and different files | |
7057 | may have different @code{COLUMNS} formats, this is a non-trivial problem. | |
7058 | Org first checks if the variable @code{org-overriding-columns-format} is | |
7059 | currently set, and if yes takes the format from there. Otherwise it takes | |
7060 | the format associated with the first item in the agenda, or, if that item | |
7061 | does not have a specific format (defined in a property, or in it's file), it | |
7062 | uses @code{org-columns-default-format}. | |
7063 | @item | |
7064 | If any of the columns has a summary type defined (@pxref{Column attributes}), | |
7065 | turning on column view in the agenda will visit all relevant agenda files and | |
7066 | make sure that the computations of this property are up to date. This is | |
7067 | also true for the special @code{CLOCKSUM} property. Org will then sum the | |
7068 | values displayed in the agenda. In the daily/weekly agenda, the sums will | |
7069 | cover a single day, in all other views they cover the entire block. It is | |
7070 | vital to realize that the agenda may show the same entry @emph{twice} (for | |
7071 | example as scheduled and as a deadline), and it may show two entries from the | |
7072 | same hierarchy (for example a @emph{parent} and it's @emph{child}). In these | |
7073 | cases, the summation in the agenda will lead to incorrect results because | |
7074 | some values will count double. | |
7075 | @item | |
7076 | When the column view in the agenda shows the @code{CLOCKSUM}, that is always | |
7077 | the entire clocked time for this item. So even in the daily/weekly agenda, | |
7078 | the clocksum listed in column view may originate from times outside the | |
7079 | current view. This has the advantage that you can compare these values with | |
7080 | a column listing the planned total effort for a task - one of the major | |
7081 | applications for column view in the agenda. If you want information about | |
7082 | clocked time in the displayed period use clock table mode (press @kbd{R} in | |
7083 | the agenda). | |
7084 | @end enumerate | |
7085 | ||
7086 | ||
7087 | @node Embedded LaTeX, Exporting, Agenda Views, Top | |
4009494e GM |
7088 | @chapter Embedded LaTeX |
7089 | @cindex @TeX{} interpretation | |
7090 | @cindex La@TeX{} interpretation | |
7091 | ||
7092 | Plain ASCII is normally sufficient for almost all note taking. One | |
a7808fba CD |
7093 | exception, however, are scientific notes which need to be able to contain |
7094 | mathematical symbols and the occasional formula. La@TeX{}@footnote{La@TeX{} | |
7095 | is a macro system based on Donald E. Knuth's @TeX{} system. Many of the | |
7096 | features described here as ``La@TeX{}'' are really from @TeX{}, but for | |
7097 | simplicity I am blurring this distinction.} is widely used to typeset | |
7098 | scientific documents. Org mode supports embedding La@TeX{} code into its | |
7099 | files, because many academics are used to reading La@TeX{} source code, and | |
7100 | because it can be readily processed into images for HTML production. | |
4009494e GM |
7101 | |
7102 | It is not necessary to mark La@TeX{} macros and code in any special way. | |
a7808fba | 7103 | If you observe a few conventions, Org mode knows how to find it and what |
4009494e GM |
7104 | to do with it. |
7105 | ||
7106 | @menu | |
7107 | * Math symbols:: TeX macros for symbols and Greek letters | |
a7808fba | 7108 | * Subscripts and superscripts:: Simple syntax for raising/lowering text |
4009494e GM |
7109 | * LaTeX fragments:: Complex formulas made easy |
7110 | * Processing LaTeX fragments:: Previewing LaTeX processing | |
7111 | * CDLaTeX mode:: Speed up entering of formulas | |
7112 | @end menu | |
7113 | ||
a7808fba | 7114 | @node Math symbols, Subscripts and superscripts, Embedded LaTeX, Embedded LaTeX |
4009494e GM |
7115 | @section Math symbols |
7116 | @cindex math symbols | |
7117 | @cindex TeX macros | |
7118 | ||
55e0839d CD |
7119 | You can use La@TeX{} macros to insert special symbols like @samp{\alpha} to |
7120 | indicate the Greek letter, or @samp{\to} to indicate an arrow. Completion | |
7121 | for these macros is available, just type @samp{\} and maybe a few letters, | |
7122 | and press @kbd{M-@key{TAB}} to see possible completions. Unlike La@TeX{} | |
7123 | code, Org mode allows these macros to be present without surrounding math | |
7124 | delimiters, for example: | |
4009494e GM |
7125 | |
7126 | @example | |
7127 | Angles are written as Greek letters \alpha, \beta and \gamma. | |
7128 | @end example | |
7129 | ||
7130 | During HTML export (@pxref{HTML export}), these symbols are translated | |
7131 | into the proper syntax for HTML, for the above examples this is | |
864c9740 CD |
7132 | @samp{α} and @samp{→}, respectively. If you need such a symbol |
7133 | inside a word, terminate it like this: @samp{\Aacute@{@}stor}. | |
4009494e | 7134 | |
a7808fba CD |
7135 | @node Subscripts and superscripts, LaTeX fragments, Math symbols, Embedded LaTeX |
7136 | @section Subscripts and superscripts | |
4009494e GM |
7137 | @cindex subscript |
7138 | @cindex superscript | |
7139 | ||
7140 | Just like in La@TeX{}, @samp{^} and @samp{_} are used to indicate super- | |
7141 | and subscripts. Again, these can be used without embedding them in | |
7142 | math-mode delimiters. To increase the readability of ASCII text, it is | |
7143 | not necessary (but OK) to surround multi-character sub- and superscripts | |
7144 | with curly braces. For example | |
7145 | ||
7146 | @example | |
7147 | The mass if the sun is M_sun = 1.989 x 10^30 kg. The radius of | |
7148 | the sun is R_@{sun@} = 6.96 x 10^8 m. | |
7149 | @end example | |
7150 | ||
7151 | To avoid interpretation as raised or lowered text, you can quote | |
7152 | @samp{^} and @samp{_} with a backslash: @samp{\_} and @samp{\^}. | |
7153 | ||
7154 | During HTML export (@pxref{HTML export}), subscript and superscripts | |
7155 | are surrounded with @code{<sub>} and @code{<sup>} tags, respectively. | |
7156 | ||
a7808fba | 7157 | @node LaTeX fragments, Processing LaTeX fragments, Subscripts and superscripts, Embedded LaTeX |
4009494e GM |
7158 | @section LaTeX fragments |
7159 | @cindex LaTeX fragments | |
7160 | ||
7161 | With symbols, sub- and superscripts, HTML is pretty much at its end when | |
7162 | it comes to representing mathematical formulas@footnote{Yes, there is | |
7163 | MathML, but that is not yet fully supported by many browsers, and there | |
7164 | is no decent converter for turning La@TeX{} or ASCII representations of | |
7165 | formulas into MathML. So for the time being, converting formulas into | |
7166 | images seems the way to go.}. More complex expressions need a dedicated | |
a7808fba | 7167 | formula processor. To this end, Org mode can contain arbitrary La@TeX{} |
4009494e GM |
7168 | fragments. It provides commands to preview the typeset result of these |
7169 | fragments, and upon export to HTML, all fragments will be converted to | |
7170 | images and inlined into the HTML document@footnote{The La@TeX{} export | |
7171 | will not use images for displaying La@TeX{} fragments but include these | |
7172 | fragments directly into the La@TeX{} code.}. For this to work you | |
7173 | need to be on a system with a working La@TeX{} installation. You also | |
7174 | need the @file{dvipng} program, available at | |
7175 | @url{http://sourceforge.net/projects/dvipng/}. The La@TeX{} header that | |
7176 | will be used when processing a fragment can be configured with the | |
7177 | variable @code{org-format-latex-header}. | |
7178 | ||
7179 | La@TeX{} fragments don't need any special marking at all. The following | |
7180 | snippets will be identified as La@TeX{} source code: | |
7181 | @itemize @bullet | |
7182 | @item | |
7183 | Environments of any kind. The only requirement is that the | |
7184 | @code{\begin} statement appears on a new line, preceded by only | |
7185 | whitespace. | |
7186 | @item | |
7187 | Text within the usual La@TeX{} math delimiters. To avoid conflicts with | |
55e0839d CD |
7188 | currency specifications, single @samp{$} characters are only recognized as |
7189 | math delimiters if the enclosed text contains at most two line breaks, is | |
7190 | directly attached to the @samp{$} characters with no whitespace in between, | |
7191 | and if the closing @samp{$} is followed by whitespace, punctuation or a dash. | |
7192 | For the other delimiters, there is no such restriction, so when in doubt, use | |
7193 | @samp{\(...\)} as inline math delimiters. | |
4009494e GM |
7194 | @end itemize |
7195 | ||
7196 | @noindent For example: | |
7197 | ||
7198 | @example | |
7199 | \begin@{equation@} % arbitrary environments, | |
7200 | x=\sqrt@{b@} % even tables, figures | |
7201 | \end@{equation@} % etc | |
7202 | ||
7203 | If $a^2=b$ and \( b=2 \), then the solution must be | |
7204 | either $$ a=+\sqrt@{2@} $$ or \[ a=-\sqrt@{2@} \]. | |
7205 | @end example | |
7206 | ||
7207 | @noindent | |
7208 | If you need any of the delimiter ASCII sequences for other purposes, you | |
7209 | can configure the option @code{org-format-latex-options} to deselect the | |
7210 | ones you do not wish to have interpreted by the La@TeX{} converter. | |
7211 | ||
7212 | @node Processing LaTeX fragments, CDLaTeX mode, LaTeX fragments, Embedded LaTeX | |
7213 | @section Processing LaTeX fragments | |
7214 | @cindex LaTeX fragments, preview | |
7215 | ||
7216 | La@TeX{} fragments can be processed to produce a preview images of the | |
7217 | typeset expressions: | |
7218 | ||
7219 | @table @kbd | |
7220 | @kindex C-c C-x C-l | |
7221 | @item C-c C-x C-l | |
7222 | Produce a preview image of the La@TeX{} fragment at point and overlay it | |
7223 | over the source code. If there is no fragment at point, process all | |
7224 | fragments in the current entry (between two headlines). When called | |
7225 | with a prefix argument, process the entire subtree. When called with | |
7226 | two prefix arguments, or when the cursor is before the first headline, | |
7227 | process the entire buffer. | |
7228 | @kindex C-c C-c | |
7229 | @item C-c C-c | |
7230 | Remove the overlay preview images. | |
7231 | @end table | |
7232 | ||
7233 | During HTML export (@pxref{HTML export}), all La@TeX{} fragments are | |
7234 | converted into images and inlined into the document if the following | |
7235 | setting is active: | |
7236 | ||
7237 | @lisp | |
7238 | (setq org-export-with-LaTeX-fragments t) | |
7239 | @end lisp | |
7240 | ||
7241 | @node CDLaTeX mode, , Processing LaTeX fragments, Embedded LaTeX | |
7242 | @section Using CDLaTeX to enter math | |
7243 | @cindex CDLaTeX | |
7244 | ||
a7808fba | 7245 | CDLaTeX mode is a minor mode that is normally used in combination with a |
4009494e | 7246 | major La@TeX{} mode like AUCTeX in order to speed-up insertion of |
a7808fba CD |
7247 | environments and math templates. Inside Org mode, you can make use of |
7248 | some of the features of CDLaTeX mode. You need to install | |
4009494e GM |
7249 | @file{cdlatex.el} and @file{texmathp.el} (the latter comes also with |
7250 | AUCTeX) from @url{http://www.astro.uva.nl/~dominik/Tools/cdlatex}. | |
a7808fba CD |
7251 | Don't use CDLaTeX mode itself under Org mode, but use the light |
7252 | version @code{org-cdlatex-mode} that comes as part of Org mode. Turn it | |
4009494e | 7253 | on for the current buffer with @code{M-x org-cdlatex-mode}, or for all |
a7808fba | 7254 | Org files with |
4009494e GM |
7255 | |
7256 | @lisp | |
7257 | (add-hook 'org-mode-hook 'turn-on-org-cdlatex) | |
7258 | @end lisp | |
7259 | ||
7260 | When this mode is enabled, the following features are present (for more | |
a7808fba | 7261 | details see the documentation of CDLaTeX mode): |
4009494e GM |
7262 | @itemize @bullet |
7263 | @kindex C-c @{ | |
7264 | @item | |
7265 | Environment templates can be inserted with @kbd{C-c @{}. | |
7266 | @item | |
7267 | @kindex @key{TAB} | |
7268 | The @key{TAB} key will do template expansion if the cursor is inside a | |
a7808fba | 7269 | La@TeX{} fragment@footnote{Org mode has a method to test if the cursor is |
4009494e GM |
7270 | inside such a fragment, see the documentation of the function |
7271 | @code{org-inside-LaTeX-fragment-p}.}. For example, @key{TAB} will | |
7272 | expand @code{fr} to @code{\frac@{@}@{@}} and position the cursor | |
7273 | correctly inside the first brace. Another @key{TAB} will get you into | |
7274 | the second brace. Even outside fragments, @key{TAB} will expand | |
7275 | environment abbreviations at the beginning of a line. For example, if | |
7276 | you write @samp{equ} at the beginning of a line and press @key{TAB}, | |
7277 | this abbreviation will be expanded to an @code{equation} environment. | |
7278 | To get a list of all abbreviations, type @kbd{M-x cdlatex-command-help}. | |
7279 | @item | |
7280 | @kindex _ | |
7281 | @kindex ^ | |
7282 | Pressing @kbd{_} and @kbd{^} inside a La@TeX{} fragment will insert these | |
7283 | characters together with a pair of braces. If you use @key{TAB} to move | |
7284 | out of the braces, and if the braces surround only a single character or | |
7285 | macro, they are removed again (depending on the variable | |
7286 | @code{cdlatex-simplify-sub-super-scripts}). | |
7287 | @item | |
7288 | @kindex ` | |
7289 | Pressing the backquote @kbd{`} followed by a character inserts math | |
7290 | macros, also outside La@TeX{} fragments. If you wait more than 1.5 seconds | |
7291 | after the backquote, a help window will pop up. | |
7292 | @item | |
7293 | @kindex ' | |
7294 | Pressing the normal quote @kbd{'} followed by another character modifies | |
7295 | the symbol before point with an accent or a font. If you wait more than | |
7296 | 1.5 seconds after the backquote, a help window will pop up. Character | |
7297 | modification will work only inside La@TeX{} fragments, outside the quote | |
7298 | is normal. | |
7299 | @end itemize | |
7300 | ||
7301 | @node Exporting, Publishing, Embedded LaTeX, Top | |
7302 | @chapter Exporting | |
7303 | @cindex exporting | |
7304 | ||
a7808fba | 7305 | Org mode documents can be exported into a variety of other formats. For |
4009494e | 7306 | printing and sharing of notes, ASCII export produces a readable and |
a7808fba | 7307 | simple version of an Org file. HTML export allows you to publish a |
4009494e GM |
7308 | notes file on the web, while the XOXO format provides a solid base for |
7309 | exchange with a broad range of other applications. La@TeX{} export lets | |
a7808fba | 7310 | you use Org mode and its structured editing functions to easily create |
4009494e GM |
7311 | La@TeX{} files. To incorporate entries with associated times like |
7312 | deadlines or appointments into a desktop calendar program like iCal, | |
a7808fba CD |
7313 | Org mode can also produce extracts in the iCalendar format. Currently |
7314 | Org mode only supports export, not import of these different formats. | |
4009494e | 7315 | |
b6cb4cd5 CD |
7316 | Org supports export of selected regions when @code{transient-mark-mode} is |
7317 | enabled (default in Emacs 23). | |
7318 | ||
b349f79f CD |
7319 | @menu |
7320 | * Markup rules:: Which structures are recognized? | |
864c9740 | 7321 | * Selective export:: Using tags to select and exclude trees |
b349f79f CD |
7322 | * Export options:: Per-file export settings |
7323 | * The export dispatcher:: How to access exporter commands | |
7324 | * ASCII export:: Exporting to plain ASCII | |
7325 | * HTML export:: Exporting to HTML | |
71d35b24 | 7326 | * LaTeX and PDF export:: Exporting to LaTeX, and processing to PDF |
b349f79f CD |
7327 | * XOXO export:: Exporting to XOXO |
7328 | * iCalendar export:: Exporting in iCalendar format | |
7329 | @end menu | |
7330 | ||
864c9740 | 7331 | @node Markup rules, Selective export, Exporting, Exporting |
b349f79f CD |
7332 | @section Markup rules |
7333 | ||
7334 | When exporting Org mode documents, the exporter tries to reflect the | |
7335 | structure of the document as accurately as possible in the back-end. Since | |
7336 | export targets like HTML or La@TeX{} allow much richer formatting, Org mode | |
7337 | has rules how to prepare text for rich export. This section summarizes the | |
7338 | markup rule used in an Org mode buffer. | |
7339 | ||
7340 | @menu | |
7341 | * Document title:: How the document title is determined | |
7342 | * Headings and sections:: The main structure of the exported document | |
7343 | * Table of contents:: If, where, how to create a table of contents | |
7344 | * Initial text:: Text before the first headline | |
7345 | * Lists:: Plain lists are exported | |
7346 | * Paragraphs:: What determines beginning and ending | |
7347 | * Literal examples:: Source code and other examples | |
7348 | * Include files:: Include the contents of a file during export | |
7349 | * Tables exported:: Tables are exported richly | |
67df9cfb | 7350 | * Inlined images:: How to inline images during export |
867d4bb3 | 7351 | * Footnote markup:: |
b349f79f CD |
7352 | * Emphasis and monospace:: To bold or not to bold |
7353 | * TeX macros and LaTeX fragments:: Create special, rich export. | |
7354 | * Horizontal rules:: A line across the page | |
7355 | * Comment lines:: Some lines will not be exported | |
7356 | @end menu | |
7357 | ||
7358 | @node Document title, Headings and sections, Markup rules, Markup rules | |
7359 | @subheading Document title | |
7360 | @cindex document title, markup rules | |
7361 | ||
7362 | @noindent | |
7363 | The title of the exported document is taken from the special line | |
7364 | ||
7365 | @example | |
7366 | #+TITLE: This is the title of the document | |
7367 | @end example | |
7368 | ||
7369 | @noindent | |
7370 | If this line does not exist, the title is derived from the first non-empty, | |
7371 | non-comment line in the buffer. If no such line exists, or if you have | |
7372 | turned off exporting of the text before the first headline (see below), the | |
7373 | title will be the file name without extension. | |
7374 | ||
7375 | If you are exporting only a subtree by marking is as the region, the heading | |
7376 | of the subtree will become the title of the document. If the subtree has a | |
7377 | property @code{EXPORT_TITLE}, that will take precedence. | |
7378 | ||
7379 | @node Headings and sections, Table of contents, Document title, Markup rules | |
7380 | @subheading Headings and sections | |
7381 | @cindex headings and sections, markup rules | |
7382 | ||
7383 | The outline structure of the document as described in @ref{Document | |
7384 | Structure} forms the basis for defining sections of the exported document. | |
7385 | However, since the outline structure is also used for (for example) lists of | |
7386 | tasks, only the first three outline levels will be used as headings. Deeper | |
7387 | levels will become itemized lists. You can change the location of this | |
7388 | switch, globally by setting the variable @code{org-headline-levels}, or on a | |
7389 | per file basis with a line | |
7390 | ||
7391 | @example | |
7392 | #+OPTIONS: H:4 | |
7393 | @end example | |
7394 | ||
7395 | @node Table of contents, Initial text, Headings and sections, Markup rules | |
7396 | @subheading Table of contents | |
7397 | @cindex table of contents, markup rules | |
7398 | ||
7399 | The table of contents is normally inserted directly before the first headline | |
7400 | of the file. If you would like to get it to a different location, insert the | |
7401 | string @code{[TABLE-OF-CONTENTS]} on a line by itself at the desired | |
7402 | location. The depth of the table of contents is by default the same as the | |
7403 | number of headline levels, but you can choose a smaller number or turn off | |
7404 | the table of contents entirely by configuring the variable | |
7405 | @code{org-export-with-toc}, or on a per-file basis with a line like | |
7406 | ||
7407 | @example | |
7408 | #+OPTIONS: toc:2 (only to two levels in TOC) | |
7409 | #+OPTIONS: toc:nil (no TOC at all) | |
7410 | @end example | |
7411 | ||
7412 | @node Initial text, Lists, Table of contents, Markup rules | |
7413 | @subheading Text before the first headline | |
7414 | @cindex text before first headline, markup rules | |
7415 | @cindex #+TEXT | |
7416 | ||
7417 | Org mode normally exports the text before the first headline, and even uses | |
7418 | the first line as the document title. The text will be fully marked up. If | |
7419 | you need to include literal HTML or La@TeX{} code, use the special constructs | |
7420 | described below in the sections for the individual exporters. | |
7421 | ||
7422 | Some people like to use the space before the first headline for setup and | |
7423 | internal links and therefore would like to control the exported text before | |
7424 | the first headline in a different way. You can do so by setting the variable | |
7425 | @code{org-export-skip-text-before-1st-heading} to @code{t}. On a per-file | |
7426 | basis, you can get the same effect with @samp{#+OPTIONS: skip:t}. | |
7427 | ||
7428 | @noindent | |
7429 | If you still want to have some text before the first headline, use the | |
7430 | @code{#+TEXT} construct: | |
7431 | ||
7432 | @example | |
7433 | #+OPTIONS: skip:t | |
7434 | #+TEXT: This text will go before the *first* headline. | |
7435 | #+TEXT: [TABLE-OF-CONTENTS] | |
7436 | #+TEXT: This goes between the table of contents and the first headline | |
7437 | @end example | |
7438 | ||
7439 | @node Lists, Paragraphs, Initial text, Markup rules | |
7440 | @subheading Lists | |
7441 | @cindex lists, markup rules | |
7442 | ||
7443 | Plain lists as described in @ref{Plain lists} are translated to the back-ends | |
7444 | syntax for such lists. Most back-ends support unordered, ordered, and | |
7445 | description lists. | |
7446 | ||
7447 | @node Paragraphs, Literal examples, Lists, Markup rules | |
7448 | @subheading Paragraphs, line breaks, and quoting | |
7449 | @cindex paragraphs, markup rules | |
7450 | ||
7451 | Paragraphs are separated by at least one empty line. If you need to enforce | |
7452 | a line break within a paragraph, use @samp{\\} at the end of a line. | |
7453 | ||
7454 | To keep the line breaks in a region, but otherwise use normal formatting, you | |
7455 | can use this construct, which can also be used to format poetry. | |
7456 | ||
7457 | @example | |
7458 | #+BEGIN_VERSE | |
864c9740 CD |
7459 | Great clouds overhead |
7460 | Tiny black birds rise and fall | |
7461 | Snow covers Emacs | |
96c8522a | 7462 | |
864c9740 | 7463 | -- AlexSchroeder |
b349f79f CD |
7464 | #+END_VERSE |
7465 | @end example | |
7466 | ||
7467 | When quoting a passage from another document, it is customary to format this | |
7468 | as a paragraph that is indented on both the left and the right margin. You | |
7469 | can include quotations in Org mode documents like this: | |
7470 | ||
7471 | @example | |
7472 | #+BEGIN_QUOTE | |
7473 | Everything should be made as simple as possible, | |
7474 | but not any simpler -- Albert Einstein | |
7475 | #+END_QUOTE | |
7476 | @end example | |
7477 | ||
7478 | ||
7479 | @node Literal examples, Include files, Paragraphs, Markup rules | |
7480 | @subheading Literal examples | |
7481 | @cindex literal examples, markup rules | |
55e0839d | 7482 | @cindex code line refenences, markup rules |
b349f79f CD |
7483 | |
7484 | You can include literal examples that should not be subjected to | |
7485 | markup. Such examples will be typeset in monospace, so this is well suited | |
7486 | for source code and similar examples. | |
7487 | @cindex #+BEGIN_EXAMPLE | |
7488 | ||
7489 | @example | |
7490 | #+BEGIN_EXAMPLE | |
7491 | Some example from a text file. | |
7492 | #+END_EXAMPLE | |
7493 | @end example | |
7494 | ||
7495 | For simplicity when using small examples, you can also start the example | |
55e0839d CD |
7496 | lines with a colon followed by a space. There may also be additional |
7497 | whitespace before the colon: | |
b349f79f CD |
7498 | |
7499 | @example | |
55e0839d CD |
7500 | Here is an example |
7501 | : Some example from a text file. | |
b349f79f CD |
7502 | @end example |
7503 | ||
7504 | @cindex formatting source code, markup rules | |
7505 | If the example is source code from a programming language, or any other text | |
7506 | that can be marked up by font-lock in Emacs, you can ask for the example to | |
7507 | look like the fontified Emacs buffer@footnote{Currently this works only for | |
7508 | the HTML back-end, and requires the @file{htmlize.el} package version 1.34 or | |
7509 | later.}. This is done with the @samp{src} block, where you also need to | |
7510 | specify the name of the major mode that should be used to fontify the | |
7511 | example: | |
7512 | @cindex #+BEGIN_SRC | |
7513 | ||
7514 | @example | |
7515 | #+BEGIN_SRC emacs-lisp | |
7516 | (defun org-xor (a b) | |
7517 | "Exclusive or." | |
7518 | (if a (not b) b)) | |
7519 | #+END_SRC | |
7520 | @end example | |
7521 | ||
55e0839d CD |
7522 | Both in @code{example} and in @code{src} snippets, you can add a @code{-n} |
7523 | switch to the end of the @code{BEGIN} line, to get the lines of the example | |
7524 | numbered. If you use a @code{+n} switch, the numbering from the previous | |
7525 | numbered snippet will be continued in the current one. In literal examples, | |
7526 | Org will interpret strings like @samp{(ref:name)} as labels, and use them as | |
7527 | targets for special hyperlinks like @code{[[(name)]]} (i.e. the reference | |
2096a1b6 | 7528 | name enclosed in single parenthesis). In HTML, hovering the mouse over such |
55e0839d CD |
7529 | a link will remote-highlight the corresponding code line, which is kind of |
7530 | cool. If the example/src snippet is numbered, you can also add a @code{-r} | |
7531 | switch. Then labels will be @i{removed} from the source code and the links | |
7532 | will be @i{replaced}@footnote{If you want to explain the use of such labels | |
7533 | themelves in org-mode example code, you can use the @code{-k} switch to make | |
7534 | sure they are not touched.} with line numbers from the code listing. Here is | |
7535 | an example: | |
7536 | ||
7537 | @example | |
7538 | #+BEGIN_SRC emacs-lisp -n -r | |
7539 | (save-excursion (ref:sc) | |
7540 | (goto-char (point-min)) (ref:jump) | |
7541 | #+END SRC | |
7542 | In line [[(sc)]] we remember the current positon. [[(jump)][Line (jump)]] | |
7543 | jumps to point-min. | |
7544 | @end example | |
7545 | ||
7546 | If the syntax for the label format conflicts with the language syntax, use a | |
7547 | @code{-l} switch to change the format, for example @samp{#+BEGIN_SRC pascal | |
7548 | -n -r -l "((%s))"}. See also the variable @code{org-coderef-label-format}. | |
7549 | ||
2096a1b6 GM |
7550 | HTML export also allows examples to be published as text areas, @pxref{Text |
7551 | areas in HTML export}. | |
55e0839d | 7552 | |
b349f79f CD |
7553 | @table @kbd |
7554 | @kindex C-c ' | |
7555 | @item C-c ' | |
7556 | Edit the source code example at point in its native mode. This works by | |
7557 | switching to an indirect buffer, narrowing the buffer and switching to the | |
864c9740 CD |
7558 | other mode. You need to exit by pressing @kbd{C-c '} again@footnote{Upon |
7559 | exit, lines starting with @samp{*} or @samp{#} will get a comma prepended, to | |
7560 | keep them from being interpreted by Org as outline nodes or special | |
7561 | comments. These commas will be striped for editing with @kbd{C-c '}, and | |
7562 | also for export.}. Fixed-width | |
7563 | regions (where each line starts with a colon followed by a space) will be | |
7564 | edited using @code{artist-mode}@footnote{You may select a different-mode with | |
7565 | the variable @code{org-edit-fixed-width-region-mode}.} to allow creating | |
7566 | ASCII drawings easily. Using this command in an empty line will create a new | |
7567 | fixed-width region. | |
55e0839d CD |
7568 | @kindex C-c l |
7569 | @item C-c l | |
7570 | Calling @code{org-store-link} while editing a source code example in a | |
7571 | temporary buffer created with @kbd{C-c '} will prompt for a label, make sure | |
7572 | that it is unique in the current buffer, and insert it with the proper | |
7573 | formatting like @samp{(ref:label)} at the end of the current line. Then the | |
7574 | label is stored as a link @samp{(label)}, for retrieval with @kbd{C-c C-l}. | |
b349f79f CD |
7575 | @end table |
7576 | ||
7577 | ||
7578 | @node Include files, Tables exported, Literal examples, Markup rules | |
7579 | @subheading Include files | |
7580 | @cindex include files, markup rules | |
7581 | ||
7582 | During export, you can include the content of another file. For example, to | |
7583 | include your .emacs file, you could use: | |
7584 | @cindex #+INCLUDE | |
7585 | ||
7586 | @example | |
7587 | #+INCLUDE: "~/.emacs" src emacs-lisp | |
7588 | @end example | |
7589 | ||
7590 | The optional second and third parameter are the markup (@samp{quote}, | |
7591 | @samp{example}, or @samp{src}), and, if the markup is @samp{src}, the | |
7592 | language for formatting the contents. The markup is optional, if it is not | |
7593 | given, the text will be assumed to be in Org mode format and will be | |
44ce9197 CD |
7594 | processed normally. The include line will also allow additional keyword |
7595 | parameters @code{:prefix1} and @code{:prefix} to specify prefixes for the | |
55e0839d CD |
7596 | first line and for each following line, as well as any options accepted by |
7597 | the selected markup. For example, to include a file as an item, use | |
44ce9197 CD |
7598 | |
7599 | @example | |
7600 | #+INCLUDE: "~/snippets/xx" :prefix1 " + " :prefix " " | |
7601 | @end example | |
b349f79f CD |
7602 | |
7603 | @table @kbd | |
7604 | @kindex C-c ' | |
7605 | @item C-c ' | |
7606 | Visit the include file at point. | |
7607 | @end table | |
7608 | ||
67df9cfb | 7609 | @node Tables exported, Inlined images, Include files, Markup rules |
b349f79f CD |
7610 | @subheading Tables |
7611 | @cindex tables, markup rules | |
7612 | ||
7613 | Both the native Org mode tables (@pxref{Tables}) and tables formatted with | |
7614 | the @file{table.el} package will be exported properly. For Org mode tables, | |
7615 | the lines before the first horizontal separator line will become table header | |
a50253cc | 7616 | lines. You can use the following lines somewhere before the table to assign |
67df9cfb CD |
7617 | a caption and a label for cross references: |
7618 | ||
7619 | @example | |
7620 | #+CAPTION: This is the caption for the next table (or link) | |
7621 | #+LABEL: tbl:basic-data | |
7622 | @end example | |
7623 | ||
55e0839d | 7624 | @node Inlined images, Footnote markup, Tables exported, Markup rules |
67df9cfb CD |
7625 | @subheading Inlined Images |
7626 | @cindex inlined images, markup rules | |
7627 | ||
7628 | Some backends (HTML and LaTeX) allow to directly include images into the | |
7629 | exported document. Org does this, if a link to an image files does not have | |
7630 | a description part, for example @code{[[./img/a.jpg]]}. If you wish to | |
7631 | define a caption for the image and maybe a label for internal cross | |
7632 | references, you can use (before, but close to the link) | |
7633 | ||
7634 | @example | |
7635 | #+CAPTION: This is the caption for the next figure link (or table) | |
7636 | #+LABEL: fig:SED-HR4049 | |
7637 | @end example | |
b349f79f | 7638 | |
67df9cfb CD |
7639 | You may also define additional attributes for the figure. As this is |
7640 | backend-specific, see the sections about the individual backends for more | |
7641 | information. | |
7642 | ||
55e0839d CD |
7643 | @node Footnote markup, Emphasis and monospace, Inlined images, Markup rules |
7644 | @subheading Footnote markup | |
b349f79f CD |
7645 | @cindex footnotes, markup rules |
7646 | @cindex @file{footnote.el} | |
7647 | ||
55e0839d CD |
7648 | Footnotes defined in the way descriped in @ref{Footnotes} will be exported by |
7649 | all backends. Org does allow multiple references to the same note, and | |
7650 | different backends support this to varying degree. | |
b349f79f | 7651 | |
55e0839d | 7652 | @node Emphasis and monospace, TeX macros and LaTeX fragments, Footnote markup, Markup rules |
b349f79f CD |
7653 | @subheading Emphasis and monospace |
7654 | ||
7655 | @cindex underlined text, markup rules | |
7656 | @cindex bold text, markup rules | |
7657 | @cindex italic text, markup rules | |
7658 | @cindex verbatim text, markup rules | |
7659 | @cindex code text, markup rules | |
7660 | @cindex strike-through text, markup rules | |
7661 | You can make words @b{*bold*}, @i{/italic/}, _underlined_, @code{=code=} | |
7662 | and @code{~verbatim~}, and, if you must, @samp{+strike-through+}. Text | |
7663 | in the code and verbatim string is not processed for Org mode specific | |
7664 | syntax, it is exported verbatim. | |
7665 | ||
7666 | @node TeX macros and LaTeX fragments, Horizontal rules, Emphasis and monospace, Markup rules | |
7667 | @subheading @TeX{} macros and La@TeX{} fragments | |
7668 | @cindex LaTeX fragments, markup rules | |
7669 | @cindex TeX macros, markup rules | |
7670 | @cindex HTML entities | |
7671 | @cindex LaTeX entities | |
7672 | ||
7673 | A @TeX{}-like syntax is used to specify special characters. Where possible, | |
7674 | these will be transformed into the native format of the exporter back-end. | |
7675 | Strings like @code{\alpha} will be exported as @code{α} in the HTML | |
7676 | output, and as @code{$\alpha$} in the La@TeX{} output. Similarly, | |
7677 | @code{\nbsp} will become @code{ } in HTML and @code{~} in La@TeX{}. | |
7678 | This applies for a large number of entities, with names taken from both HTML | |
7679 | and La@TeX{}, see the variable @code{org-html-entities} for the complete | |
7680 | list. If you are unsure about a name, use @kbd{M-@key{TAB}} for completion | |
55e0839d | 7681 | after having typed the backslash and maybe a few characters |
b349f79f CD |
7682 | (@pxref{Completion}). |
7683 | ||
7684 | La@TeX{} fragments are converted into images for HTML export, and they are | |
7685 | written literally into the La@TeX{} export. See also @ref{Embedded LaTeX}. | |
7686 | ||
7687 | Finally, @samp{\-} is treated as a shy hyphen, and @samp{--}, @samp{---}, and | |
7688 | @samp{...} are all converted into special commands creating hyphens of | |
7689 | different lengths or a compact set of dots. | |
7690 | ||
7691 | @node Horizontal rules, Comment lines, TeX macros and LaTeX fragments, Markup rules | |
7692 | @subheading Horizontal rules | |
7693 | @cindex horizontal rules, markup rules | |
7694 | A line consisting of only dashes, and at least 5 of them, will be | |
7695 | exported as a horizontal line (@samp{<hr/>} in HTML). | |
7696 | ||
7697 | @node Comment lines, , Horizontal rules, Markup rules | |
7698 | @subheading Comment lines | |
7699 | @cindex comment lines | |
7700 | @cindex exporting, not | |
7701 | ||
7702 | Lines starting with @samp{#} in column zero are treated as comments and will | |
7703 | never be exported. Also entire subtrees starting with the word | |
7704 | @samp{COMMENT} will never be exported. Finally, regions surrounded by | |
7705 | @samp{#+BEGIN_COMMENT} ... @samp{#+END_COMMENT} will not be exported. | |
7706 | ||
7707 | @table @kbd | |
7708 | @kindex C-c ; | |
7709 | @item C-c ; | |
7710 | Toggle the COMMENT keyword at the beginning of an entry. | |
7711 | @end table | |
7712 | ||
864c9740 CD |
7713 | @node Selective export, Export options, Markup rules, Exporting |
7714 | @section Selective export | |
7715 | @cindex export, selective by tags | |
7716 | ||
7717 | You may use tags to select the parts of a document that should be exported, | |
7718 | or to exclude parts from export. This behavior is governed by two variables: | |
7719 | @code{org-export-select-tags} and @code{org-export-exclude-tags}. | |
7720 | ||
7721 | Org first checks if any of the @emph{select} tags is present in the buffer. | |
7722 | If yes, all trees that do not carry one of these tags will be excluded. If a | |
7723 | selected tree is a subtree, the heading hierarchy above it will also be | |
7724 | selected for export, but not the text below those headings. | |
7725 | ||
7726 | @noindent | |
7727 | If none of the select tags is found, the whole buffer will be selected for | |
7728 | export. | |
7729 | ||
7730 | @noindent | |
7731 | Finally, all subtrees that are marked by any of the @emph{exclude} tags will | |
7732 | be removed from the export buffer. | |
7733 | ||
7734 | @node Export options, The export dispatcher, Selective export, Exporting | |
b349f79f CD |
7735 | @section Export options |
7736 | @cindex options, for export | |
7737 | ||
7738 | @cindex completion, of option keywords | |
7739 | The exporter recognizes special lines in the buffer which provide | |
7740 | additional information. These lines may be put anywhere in the file. | |
7741 | The whole set of lines can be inserted into the buffer with @kbd{C-c | |
7742 | C-e t}. For individual lines, a good way to make sure the keyword is | |
7743 | correct is to type @samp{#+} and then use @kbd{M-@key{TAB}} completion | |
7744 | (@pxref{Completion}). | |
7745 | ||
7746 | @table @kbd | |
7747 | @kindex C-c C-e t | |
7748 | @item C-c C-e t | |
7749 | Insert template with export options, see example below. | |
7750 | @end table | |
7751 | ||
7752 | @cindex #+TITLE: | |
7753 | @cindex #+AUTHOR: | |
7754 | @cindex #+DATE: | |
7755 | @cindex #+EMAIL: | |
7756 | @cindex #+LANGUAGE: | |
7757 | @cindex #+TEXT: | |
7758 | @cindex #+OPTIONS: | |
7759 | @cindex #+LINK_UP: | |
7760 | @cindex #+LINK_HOME: | |
864c9740 CD |
7761 | @cindex #+EXPORT_SELECT_TAGS: |
7762 | @cindex #+EXPORT_EXCLUDE_TAGS: | |
b349f79f CD |
7763 | @example |
7764 | #+TITLE: the title to be shown (default is the buffer name) | |
7765 | #+AUTHOR: the author (default taken from @code{user-full-name}) | |
7766 | #+DATE: A date, fixed, of a format string for @code{format-time-string} | |
7767 | #+EMAIL: his/her email address (default from @code{user-mail-address}) | |
7768 | #+LANGUAGE: language for HTML, e.g. @samp{en} (@code{org-export-default-language}) | |
7769 | #+TEXT: Some descriptive text to be inserted at the beginning. | |
7770 | #+TEXT: Several lines may be given. | |
7771 | #+OPTIONS: H:2 num:t toc:t \n:nil @@:t ::t |:t ^:t f:t TeX:t ... | |
7772 | #+LINK_UP: the ``up'' link of an exported page | |
7773 | #+LINK_HOME: the ``home'' link of an exported page | |
864c9740 CD |
7774 | #+EXPORT_SELECT_TAGS: Tags that select a tree for export |
7775 | #+EXPORT_EXCLUDE_TAGS: Tags that exclude a tree from export | |
b349f79f CD |
7776 | @end example |
7777 | ||
7778 | @noindent | |
7779 | The OPTIONS line is a compact@footnote{If you want to configure many options | |
7780 | this way, you can use several OPTIONS lines.} form to specify export settings. Here | |
7781 | you can: | |
7782 | @cindex headline levels | |
7783 | @cindex section-numbers | |
7784 | @cindex table of contents | |
7785 | @cindex line-break preservation | |
7786 | @cindex quoted HTML tags | |
7787 | @cindex fixed-width sections | |
7788 | @cindex tables | |
7789 | @cindex @TeX{}-like syntax for sub- and superscripts | |
7790 | @cindex footnotes | |
7791 | @cindex special strings | |
7792 | @cindex emphasized text | |
7793 | @cindex @TeX{} macros | |
7794 | @cindex La@TeX{} fragments | |
7795 | @cindex author info, in export | |
7796 | @cindex time info, in export | |
7797 | @example | |
7798 | H: @r{set the number of headline levels for export} | |
7799 | num: @r{turn on/off section-numbers} | |
7800 | toc: @r{turn on/off table of contents, or set level limit (integer)} | |
7801 | \n: @r{turn on/off line-break-preservation} | |
7802 | @@: @r{turn on/off quoted HTML tags} | |
7803 | :: @r{turn on/off fixed-width sections} | |
7804 | |: @r{turn on/off tables} | |
7805 | ^: @r{turn on/off @TeX{}-like syntax for sub- and superscripts. If} | |
7806 | @r{you write "^:@{@}", @code{a_@{b@}} will be interpreted, but} | |
7807 | @r{the simple @code{a_b} will be left as it is.} | |
7808 | -: @r{turn on/off conversion of special strings.} | |
7809 | f: @r{turn on/off footnotes like this[1].} | |
96c8522a CD |
7810 | todo: @r{turn on/off inclusion of TODO keywords into exported text} |
7811 | pri: @r{turn on/off priority cookies} | |
7812 | tags: @r{turn on/off inclusion of tags, may also be @code{not-in-toc}} | |
7813 | <: @r{turn on/off inclusion of any time/date stamps like DEADLINES} | |
b349f79f CD |
7814 | *: @r{turn on/off emphasized text (bold, italic, underlined)} |
7815 | TeX: @r{turn on/off simple @TeX{} macros in plain text} | |
7816 | LaTeX: @r{turn on/off La@TeX{} fragments} | |
7817 | skip: @r{turn on/off skipping the text before the first heading} | |
7818 | author: @r{turn on/off inclusion of author name/email into exported file} | |
dd12e1c6 | 7819 | creator: @r{turn on/off inclusion of creator info into exported file} |
b349f79f CD |
7820 | timestamp: @r{turn on/off inclusion creation time into exported file} |
7821 | d: @r{turn on/off inclusion of drawers} | |
7822 | @end example | |
7823 | ||
7824 | These options take effect in both the HTML and La@TeX{} export, except | |
7825 | for @code{TeX} and @code{LaTeX}, which are respectively @code{t} and | |
7826 | @code{nil} for the La@TeX{} export. | |
7827 | ||
7828 | When exporting only a single subtree by selecting it with @kbd{C-c @@} before | |
7829 | calling an export command, the subtree can overrule some of the file's export | |
7830 | settings with properties @code{EXPORT_FILE_NAME}, @code{EXPORT_TITLE}, | |
7831 | @code{EXPORT_TEXT}, and @code{EXPORT_OPTIONS}. | |
7832 | ||
7833 | @node The export dispatcher, ASCII export, Export options, Exporting | |
7834 | @section The export dispatcher | |
7835 | @cindex dispatcher, for export commands | |
7836 | ||
7837 | All export commands can be reached using the export dispatcher, which is a | |
7838 | prefix key that prompts for an additional key specifying the command. | |
7839 | Normally the entire file is exported, but if there is an active region that | |
7840 | contains one outline tree, the first heading is used as document title and | |
7841 | the subtrees are exported. | |
4009494e GM |
7842 | |
7843 | @table @kbd | |
7844 | @kindex C-c C-e | |
7845 | @item C-c C-e | |
7846 | Dispatcher for export and publishing commands. Displays a help-window | |
7847 | listing the additional key(s) needed to launch an export or publishing | |
64fb801f CD |
7848 | command. The prefix arg is passed through to the exporter. A double prefix |
7849 | @kbd{C-u C-u} causes most commands to be executed in the background, in a | |
7850 | separate emacs process@footnote{To make this behavior the default, customize | |
7851 | the variable @code{org-export-run-in-background}.}. | |
b349f79f CD |
7852 | @kindex C-c C-e v |
7853 | @item C-c C-e v | |
7854 | Like @kbd{C-c C-e}, but only export the text that is currently visible | |
7855 | (i.e. not hidden by outline visibility). | |
a7808fba CD |
7856 | @kindex C-u C-u C-c C-e |
7857 | @item C-u C-u C-c C-e | |
7858 | Call an the exporter, but reverse the setting of | |
7859 | @code{org-export-run-in-background}, i.e. request background processing if | |
7860 | not set, or force processing in the current Emacs process if st. | |
4009494e GM |
7861 | @end table |
7862 | ||
b349f79f | 7863 | @node ASCII export, HTML export, The export dispatcher, Exporting |
4009494e GM |
7864 | @section ASCII export |
7865 | @cindex ASCII export | |
7866 | ||
a7808fba | 7867 | ASCII export produces a simple and very readable version of an Org mode |
4009494e GM |
7868 | file. |
7869 | ||
7870 | @cindex region, active | |
7871 | @cindex active region | |
b6cb4cd5 | 7872 | @cindex transient-mark-mode |
4009494e GM |
7873 | @table @kbd |
7874 | @kindex C-c C-e a | |
7875 | @item C-c C-e a | |
7876 | Export as ASCII file. For an org file @file{myfile.org}, the ASCII file | |
7877 | will be @file{myfile.txt}. The file will be overwritten without | |
b6cb4cd5 CD |
7878 | warning. If there is an active region@footnote{this requires |
7879 | @code{transient-mark-mode} to be turned on}, only the region will be | |
b349f79f CD |
7880 | exported. If the selected region is a single tree@footnote{To select the |
7881 | current subtree, use @kbd{C-c @@}.}, the tree head will | |
4009494e | 7882 | become the document title. If the tree head entry has or inherits an |
b349f79f | 7883 | @code{EXPORT_FILE_NAME} property, that name will be used for the |
28a16a1b | 7884 | export. |
4009494e GM |
7885 | @kindex C-c C-e v a |
7886 | @item C-c C-e v a | |
7887 | Export only the visible part of the document. | |
7888 | @end table | |
7889 | ||
7890 | @cindex headline levels, for exporting | |
7891 | In the exported version, the first 3 outline levels will become | |
7892 | headlines, defining a general document structure. Additional levels | |
7893 | will be exported as itemized lists. If you want that transition to occur | |
7894 | at a different level, specify it with a prefix argument. For example, | |
7895 | ||
7896 | @example | |
7897 | @kbd{C-1 C-c C-e a} | |
7898 | @end example | |
7899 | ||
7900 | @noindent | |
7901 | creates only top level headlines and does the rest as items. When | |
7902 | headlines are converted to items, the indentation of the text following | |
7903 | the headline is changed to fit nicely under the item. This is done with | |
a7808fba | 7904 | the assumption that the first body line indicates the base indentation of |
4009494e GM |
7905 | the body text. Any indentation larger than this is adjusted to preserve |
7906 | the layout relative to the first line. Should there be lines with less | |
7907 | indentation than the first, these are left alone. | |
7908 | ||
71d35b24 | 7909 | @node HTML export, LaTeX and PDF export, ASCII export, Exporting |
4009494e GM |
7910 | @section HTML export |
7911 | @cindex HTML export | |
7912 | ||
a7808fba | 7913 | Org mode contains an HTML (XHTML 1.0 strict) exporter with extensive |
b6cb4cd5 | 7914 | HTML formatting, in ways similar to John Gruber's @emph{markdown} |
4009494e GM |
7915 | language, but with additional support for tables. |
7916 | ||
7917 | @menu | |
b349f79f | 7918 | * HTML Export commands:: How to invoke HTML export |
a7808fba | 7919 | * Quoting HTML tags:: Using direct HTML in Org mode |
4009494e | 7920 | * Links:: Transformation of links for HTML |
55e0839d CD |
7921 | * Images in HTML export:: How to insert figures into HTML output |
7922 | * Text areas in HTML export:: An alternative way to show an example | |
a7808fba CD |
7923 | * CSS support:: Changing the appearance of the output |
7924 | * Javascript support:: Info and Folding in a web browser | |
4009494e GM |
7925 | @end menu |
7926 | ||
7927 | @node HTML Export commands, Quoting HTML tags, HTML export, HTML export | |
7928 | @subsection HTML export commands | |
7929 | ||
7930 | @cindex region, active | |
7931 | @cindex active region | |
b6cb4cd5 | 7932 | @cindex transient-mark-mode |
4009494e GM |
7933 | @table @kbd |
7934 | @kindex C-c C-e h | |
7935 | @item C-c C-e h | |
b349f79f CD |
7936 | Export as HTML file @file{myfile.html}. For an org file @file{myfile.org}, |
7937 | the ASCII file will be @file{myfile.html}. The file will be overwritten | |
b6cb4cd5 CD |
7938 | without warning. If there is an active region@footnote{this requires |
7939 | @code{transient-mark-mode} to be turned on}, only the region will be | |
b349f79f CD |
7940 | exported. If the selected region is a single tree@footnote{To select the |
7941 | current subtree, use @kbd{C-c @@}.}, the tree head will become the document | |
b6cb4cd5 | 7942 | title. If the tree head entry has, or inherits, an @code{EXPORT_FILE_NAME} |
b349f79f | 7943 | property, that name will be used for the export. |
4009494e GM |
7944 | @kindex C-c C-e b |
7945 | @item C-c C-e b | |
7946 | Export as HTML file and immediately open it with a browser. | |
7947 | @kindex C-c C-e H | |
7948 | @item C-c C-e H | |
7949 | Export to a temporary buffer, do not create a file. | |
7950 | @kindex C-c C-e R | |
dbc28aaa | 7951 | @item C-c C-e R |
a7808fba CD |
7952 | Export the active region to a temporary buffer. With a prefix argument, do |
7953 | not produce the file header and footer, but just the plain HTML section for | |
7954 | the region. This is good for cut-and-paste operations. | |
4009494e GM |
7955 | @kindex C-c C-e v h |
7956 | @kindex C-c C-e v b | |
7957 | @kindex C-c C-e v H | |
7958 | @kindex C-c C-e v R | |
7959 | @item C-c C-e v h | |
7960 | @item C-c C-e v b | |
7961 | @item C-c C-e v H | |
7962 | @item C-c C-e v R | |
7963 | Export only the visible part of the document. | |
7964 | @item M-x org-export-region-as-html | |
a7808fba | 7965 | Convert the region to HTML under the assumption that it was Org mode |
4009494e GM |
7966 | syntax before. This is a global command that can be invoked in any |
7967 | buffer. | |
7968 | @item M-x org-replace-region-by-HTML | |
a7808fba | 7969 | Replace the active region (assumed to be in Org mode syntax) by HTML |
4009494e GM |
7970 | code. |
7971 | @end table | |
7972 | ||
7973 | @cindex headline levels, for exporting | |
a7808fba CD |
7974 | In the exported version, the first 3 outline levels will become headlines, |
7975 | defining a general document structure. Additional levels will be exported as | |
7976 | itemized lists. If you want that transition to occur at a different level, | |
7977 | specify it with a numeric prefix argument. For example, | |
4009494e GM |
7978 | |
7979 | @example | |
7980 | @kbd{C-2 C-c C-e b} | |
7981 | @end example | |
7982 | ||
7983 | @noindent | |
7984 | creates two levels of headings and does the rest as items. | |
7985 | ||
7986 | @node Quoting HTML tags, Links, HTML Export commands, HTML export | |
7987 | @subsection Quoting HTML tags | |
7988 | ||
7989 | Plain @samp{<} and @samp{>} are always transformed to @samp{<} and | |
7990 | @samp{>} in HTML export. If you want to include simple HTML tags | |
7991 | which should be interpreted as such, mark them with @samp{@@} as in | |
7992 | @samp{@@<b>bold text@@</b>}. Note that this really works only for | |
7993 | simple tags. For more extensive HTML that should be copied verbatim to | |
7994 | the exported file use either | |
7995 | ||
7996 | @example | |
7997 | #+HTML: Literal HTML code for export | |
7998 | @end example | |
7999 | ||
8000 | @noindent or | |
b349f79f | 8001 | @cindex #+BEGIN_HTML |
4009494e GM |
8002 | |
8003 | @example | |
8004 | #+BEGIN_HTML | |
8005 | All lines between these markers are exported literally | |
8006 | #+END_HTML | |
8007 | @end example | |
8008 | ||
8009 | ||
67df9cfb | 8010 | @node Links, Images in HTML export, Quoting HTML tags, HTML export |
4009494e GM |
8011 | @subsection Links |
8012 | ||
8013 | @cindex links, in HTML export | |
8014 | @cindex internal links, in HTML export | |
8015 | @cindex external links, in HTML export | |
55e0839d CD |
8016 | Internal links (@pxref{Internal links}) will continue to work in HTML. This |
8017 | does include automatic links created by radio targets (@pxref{Radio | |
8018 | targets}). Links to external files will still work if the target file is on | |
8019 | the same @i{relative} path as the published Org file. Links to other | |
8020 | @file{.org} files will be translated into HTML links under the assumption | |
8021 | that an HTML version also exists of the linked file, at the same relative | |
8022 | path. @samp{id:} links can then be used to jump to specific entries across | |
8023 | files. For information related to linking files while publishing them to a | |
8024 | publishing directory see @ref{Publishing links}. | |
4009494e | 8025 | |
44ce9197 | 8026 | If you want to specify attributes for links, you can do so using a special |
a50253cc | 8027 | @code{#+ATTR_HTML} line to define attributes that will be added to the |
67df9cfb CD |
8028 | @code{<a>} or @code{<img>} tags. Here is an example that sets @code{alt} and |
8029 | @code{title} attributes for an inlined image: | |
44ce9197 CD |
8030 | |
8031 | @example | |
67df9cfb CD |
8032 | #+ATTR_HTML: alt="This is image A" title="Image with no action" |
8033 | [[./img/a.jpg]] | |
44ce9197 CD |
8034 | @end example |
8035 | ||
55e0839d | 8036 | @node Images in HTML export, Text areas in HTML export, Links, HTML export |
4009494e GM |
8037 | @subsection Images |
8038 | ||
8039 | @cindex images, inline in HTML | |
8040 | @cindex inlining images in HTML | |
a7808fba | 8041 | HTML export can inline images given as links in the Org file, and |
4009494e GM |
8042 | it can make an image the clickable part of a link. By |
8043 | default@footnote{but see the variable | |
8044 | @code{org-export-html-inline-images}}, images are inlined if a link does | |
8045 | not have a description. So @samp{[[file:myimg.jpg]]} will be inlined, | |
8046 | while @samp{[[file:myimg.jpg][the image]]} will just produce a link | |
8047 | @samp{the image} that points to the image. If the description part | |
8048 | itself is a @code{file:} link or a @code{http:} URL pointing to an | |
8049 | image, this image will be inlined and activated so that clicking on the | |
8050 | image will activate the link. For example, to include a thumbnail that | |
8051 | will link to a high resolution version of the image, you could use: | |
8052 | ||
8053 | @example | |
8054 | [[file:highres.jpg][file:thumb.jpg]] | |
8055 | @end example | |
8056 | ||
8057 | @noindent | |
8058 | and you could use @code{http} addresses just as well. | |
8059 | ||
55e0839d CD |
8060 | @node Text areas in HTML export, CSS support, Images in HTML export, HTML export |
8061 | @subsection Text areas | |
8062 | ||
8063 | @cindex text areas, in HTML | |
8064 | An alternative way to publish literal code examples in HTML is to use text | |
8065 | areas, where the example can even be edited before pasting it into an | |
8066 | application. It is triggered by a @code{-t} switch at an @code{example} or | |
8067 | @code{src} block. Using this switch disables any options for syntax and | |
8068 | label highlighting, and line numbering, which may be present. You may also | |
8069 | use @code{-h} and @code{-w} switches to specify the height and width of the | |
8070 | text area, which default to the number of lines in the example, and 80, | |
8071 | respectively. For example | |
8072 | ||
8073 | @example | |
8074 | #+BEGIN_EXAMPLE -t -w 40 | |
8075 | (defun org-xor (a b) | |
8076 | "Exclusive or." | |
8077 | (if a (not b) b)) | |
8078 | #+END_EXAMPLE | |
8079 | @end example | |
8080 | ||
8081 | ||
8082 | @node CSS support, Javascript support, Text areas in HTML export, HTML export | |
4009494e | 8083 | @subsection CSS support |
a7808fba CD |
8084 | @cindex CSS, for HTML export |
8085 | @cindex HTML export, CSS | |
4009494e | 8086 | |
55e0839d CD |
8087 | You can also give style information for the exported file. The HTML exporter |
8088 | assigns the following special CSS classes to appropriate parts of the | |
8089 | document - your style specifications may change these, in addition to any of | |
8090 | the standard classes like for headlines, tables etc. | |
4009494e | 8091 | @example |
55e0839d CD |
8092 | .todo @r{TODO keywords} |
8093 | .done @r{the DONE keyword} | |
8094 | .timestamp @r{time stamp} | |
8095 | .timestamp-kwd @r{keyword associated with a time stamp, like SCHEDULED} | |
8096 | .tag @r{tag in a headline} | |
8097 | .target @r{target for links} | |
8098 | div.figure @r{how to format an inlined image} | |
8099 | .linenr @r{the line number in a code example} | |
8100 | .code-highlighted @r{for highlighting referenced code lines} | |
4009494e GM |
8101 | @end example |
8102 | ||
44ce9197 | 8103 | Each exported files contains a compact default style that defines these |
e45e3595 CD |
8104 | classes in a basic way@footnote{This style is defined in the constant |
8105 | @code{org-export-html-style-default}, which you should not modify. To turn | |
8106 | inclusion of these defaults off, customize | |
8107 | @code{org-export-html-style-include-default}}. You may overwrite these | |
8108 | settings, or add to them by using the variables @code{org-export-html-style} | |
8109 | (for Org-wide settings) and @code{org-export-html-style-extra} (for more | |
8110 | granular settings, like file-local settings). To set the latter variable | |
8111 | individually for each file, you can use | |
4009494e GM |
8112 | |
8113 | @example | |
864c9740 | 8114 | #+STYLE: <link rel="stylesheet" type="text/css" href="stylesheet.css" /> |
4009494e GM |
8115 | @end example |
8116 | ||
864c9740 | 8117 | @noindent |
e45e3595 CD |
8118 | For longer style definitions, you can use several such lines. You could also |
8119 | directly write a @code{<style>} @code{</style>} section in this way, without | |
8120 | referring to an external file. | |
4009494e GM |
8121 | |
8122 | @c FIXME: More about header and footer styles | |
8123 | @c FIXME: Talk about links and targets. | |
8124 | ||
a7808fba CD |
8125 | @node Javascript support, , CSS support, HTML export |
8126 | @subsection Javascript supported display of web pages | |
8127 | ||
8128 | @emph{Sebastian Rose} has written a JavaScript program especially designed to | |
8129 | enhance the web viewing experience of HTML files created with Org. This | |
55e0839d CD |
8130 | program allows you to view large files in two different ways. The first one |
8131 | is an @emph{Info}-like mode where each section is displayed separately and | |
a7808fba CD |
8132 | navigation can be done with the @kbd{n} and @kbd{p} keys (and some other keys |
8133 | as well, press @kbd{?} for an overview of the available keys). The second | |
55e0839d CD |
8134 | view type is a @emph{folding} view much like Org provides inside Emacs. The |
8135 | script is available at @url{http://orgmode.org/org-info.js} and you can find | |
8136 | the documentation for it at @url{http://orgmode.org/worg/code/org-info-js/}. | |
8137 | We are serving the script from our site, but if you use it a lot, you might | |
8138 | not want to be dependent on @url{orgmode.org} and prefer to install a local | |
8139 | copy on your own web server. | |
a7808fba | 8140 | |
b349f79f | 8141 | To use the script, you need to make sure that the @file{org-jsinfo.el} module |
b6cb4cd5 CD |
8142 | gets loaded. It should be loaded by default, but you can try @kbd{M-x |
8143 | customize-variable @key{RET} org-modules @key{RET}} to convince yourself that | |
8144 | this is indeed the case. All it then takes to make use of the program is | |
8145 | adding a single line to the Org file: | |
a7808fba CD |
8146 | |
8147 | @example | |
b349f79f | 8148 | #+INFOJS_OPT: view:info toc:nil |
a7808fba CD |
8149 | @end example |
8150 | ||
8151 | @noindent | |
8152 | If this line is found, the HTML header will automatically contain the code | |
8153 | needed to invoke the script. Using the line above, you can set the following | |
8154 | viewing options: | |
8155 | ||
8156 | @example | |
8157 | path: @r{The path to the script. The default is to grab the script from} | |
8158 | @r{@url{http://orgmode.org/org-info.js}, but you might want to have} | |
8159 | @r{a local copy and use a path like @samp{../scripts/org-info.js}.} | |
b349f79f | 8160 | view: @r{Initial view when website is first shown. Possible values are:} |
a7808fba CD |
8161 | info @r{Info-like interface with one section per page.} |
8162 | overview @r{Folding interface, initially showing only top-level.} | |
8163 | content @r{Folding interface, starting with all headlines visible.} | |
8164 | showall @r{Folding interface, all headlines and text visible.} | |
8165 | sdepth: @r{Maximum headline level that will still become an independent} | |
8166 | @r{section for info and folding modes. The default is taken from} | |
8167 | @r{@code{org-headline-levels} (= the @code{H} switch in @code{#+OPTIONS}).} | |
8168 | @r{If this is smaller than in @code{org-headline-levels}, each} | |
8169 | @r{info/folding section can still contain children headlines.} | |
8170 | toc: @r{Should the table of content @emph{initially} be visible?} | |
8171 | @r{Even when @code{nil}, you can always get to the toc with @kbd{i}.} | |
8172 | tdepth: @r{The depth of the table of contents. The defaults are taken from} | |
8173 | @r{the variables @code{org-headline-levels} and @code{org-export-with-toc}.} | |
b349f79f CD |
8174 | ftoc: @r{Does the css of the page specify a fixed position for the toc?} |
8175 | @r{If yes, the toc will never be displayed as a section.} | |
a7808fba | 8176 | ltoc: @r{Should there be short contents (children) in each section?} |
55033558 | 8177 | @r{Make this @code{above} it the section should be above initial text.} |
a7808fba CD |
8178 | mouse: @r{Headings are highlighted when the mouse is over them. Should be} |
8179 | @r{@samp{underline} (default) or a background color like @samp{#cccccc}.} | |
8180 | buttons: @r{Should view-toggle buttons be everywhere? When @code{nil} (the} | |
8181 | @r{default), only one such button will be present.} | |
8182 | @end example | |
8183 | ||
8184 | You can choose default values for these options by customizing the variable | |
8185 | @code{org-infojs-options}. If you always want to apply the script to your | |
8186 | pages, configure the variable @code{org-export-html-use-infojs}. | |
8187 | ||
71d35b24 CD |
8188 | @node LaTeX and PDF export, XOXO export, HTML export, Exporting |
8189 | @section LaTeX and PDF export | |
4009494e | 8190 | @cindex LaTeX export |
71d35b24 | 8191 | @cindex PDF export |
4009494e | 8192 | |
71d35b24 CD |
8193 | Org mode contains a La@TeX{} exporter written by Bastien Guerry. With |
8194 | further processing, this backend is also used to produce PDF output. Since | |
8195 | the LaTeX output uses @file{hyperref} to implement links and cross | |
8196 | references, the PDF output file will be fully linked. | |
4009494e GM |
8197 | |
8198 | @menu | |
a50253cc | 8199 | * LaTeX/PDF export commands:: Which key invokes which commands |
4009494e | 8200 | * Quoting LaTeX code:: Incorporating literal LaTeX code |
a7808fba | 8201 | * Sectioning structure:: Changing sectioning in LaTeX output |
67df9cfb CD |
8202 | * Tables in LaTeX export:: Options for exporting tables to LaTeX |
8203 | * Images in LaTeX export:: How to insert figures into LaTeX output | |
4009494e GM |
8204 | @end menu |
8205 | ||
71d35b24 | 8206 | @node LaTeX/PDF export commands, Quoting LaTeX code, LaTeX and PDF export, LaTeX and PDF export |
4009494e GM |
8207 | @subsection LaTeX export commands |
8208 | ||
b6cb4cd5 CD |
8209 | @cindex region, active |
8210 | @cindex active region | |
8211 | @cindex transient-mark-mode | |
4009494e GM |
8212 | @table @kbd |
8213 | @kindex C-c C-e l | |
8214 | @item C-c C-e l | |
b349f79f CD |
8215 | Export as La@TeX{} file @file{myfile.tex}. For an org file |
8216 | @file{myfile.org}, the ASCII file will be @file{myfile.tex}. The file will | |
b6cb4cd5 CD |
8217 | be overwritten without warning. If there is an active region@footnote{this |
8218 | requires @code{transient-mark-mode} to be turned on}, only the region will be | |
8219 | exported. If the selected region is a single tree@footnote{To select the | |
8220 | current subtree, use @kbd{C-c @@}.}, the tree head will become the document | |
8221 | title. If the tree head entry has or inherits an @code{EXPORT_FILE_NAME} | |
8222 | property, that name will be used for the export. | |
4009494e GM |
8223 | @kindex C-c C-e L |
8224 | @item C-c C-e L | |
8225 | Export to a temporary buffer, do not create a file. | |
8226 | @kindex C-c C-e v l | |
8227 | @kindex C-c C-e v L | |
8228 | @item C-c C-e v l | |
8229 | @item C-c C-e v L | |
8230 | Export only the visible part of the document. | |
8231 | @item M-x org-export-region-as-latex | |
a7808fba | 8232 | Convert the region to La@TeX{} under the assumption that it was Org mode |
4009494e GM |
8233 | syntax before. This is a global command that can be invoked in any |
8234 | buffer. | |
8235 | @item M-x org-replace-region-by-latex | |
a7808fba | 8236 | Replace the active region (assumed to be in Org mode syntax) by La@TeX{} |
4009494e | 8237 | code. |
71d35b24 CD |
8238 | @kindex C-c C-e p |
8239 | @item C-c C-e p | |
8240 | Export as LaTeX and then process to PDF. | |
8241 | @kindex C-c C-e d | |
8242 | @item C-c C-e d | |
8243 | Export as LaTeX and then process to PDF, then open the resulting PDF file. | |
4009494e GM |
8244 | @end table |
8245 | ||
8246 | @cindex headline levels, for exporting | |
8247 | In the exported version, the first 3 outline levels will become | |
8248 | headlines, defining a general document structure. Additional levels | |
8249 | will be exported as description lists. The exporter can ignore them or | |
8250 | convert them to a custom string depending on | |
8251 | @code{org-latex-low-levels}. | |
8252 | ||
8253 | If you want that transition to occur at a different level, specify it | |
a7808fba | 8254 | with a numeric prefix argument. For example, |
4009494e GM |
8255 | |
8256 | @example | |
8257 | @kbd{C-2 C-c C-e l} | |
8258 | @end example | |
8259 | ||
8260 | @noindent | |
8261 | creates two levels of headings and does the rest as items. | |
8262 | ||
71d35b24 | 8263 | @node Quoting LaTeX code, Sectioning structure, LaTeX/PDF export commands, LaTeX and PDF export |
4009494e GM |
8264 | @subsection Quoting LaTeX code |
8265 | ||
8266 | Embedded La@TeX{} as described in @ref{Embedded LaTeX} will be correctly | |
55e0839d CD |
8267 | inserted into the La@TeX{} file. This includes simple macros like |
8268 | @samp{\ref@{LABEL@}} to create a cross reference to a figure. Furthermore, | |
8269 | you can add special code that should only be present in La@TeX{} export with | |
8270 | the following constructs: | |
4009494e GM |
8271 | |
8272 | @example | |
8273 | #+LaTeX: Literal LaTeX code for export | |
8274 | @end example | |
8275 | ||
8276 | @noindent or | |
b349f79f | 8277 | @cindex #+BEGIN_LaTeX |
4009494e GM |
8278 | |
8279 | @example | |
8280 | #+BEGIN_LaTeX | |
8281 | All lines between these markers are exported literally | |
8282 | #+END_LaTeX | |
8283 | @end example | |
dbc28aaa | 8284 | |
55e0839d | 8285 | @node Sectioning structure, Tables in LaTeX export, Quoting LaTeX code, LaTeX and PDF export |
dbc28aaa CD |
8286 | @subsection Sectioning structure |
8287 | @cindex LaTeX class | |
8288 | @cindex LaTeX sectioning structure | |
8289 | ||
8290 | By default, the La@TeX{} output uses the class @code{article}. | |
8291 | ||
8292 | You can change this globally by setting a different value for | |
71d35b24 | 8293 | @code{org-export-latex-default-class} or locally by adding an option like |
55e0839d CD |
8294 | @code{#+LaTeX_CLASS: myclass} in your file, or with a @code{:LaTeX_CLASS:} |
8295 | property that applies when exporting a region containing only this (sub)tree. | |
8296 | The class should be listed in @code{org-export-latex-classes}, where you can | |
8297 | also define the sectioning structure for each class, as well as defining | |
8298 | additional classes. | |
dbc28aaa | 8299 | |
67df9cfb CD |
8300 | @node Tables in LaTeX export, Images in LaTeX export, Sectioning structure, LaTeX and PDF export |
8301 | @subsection Tables in LaTeX export | |
8302 | @cindex tables, in LaTeX export | |
8303 | ||
8304 | For LaTeX export of a table, you can specify a label and a caption | |
55e0839d | 8305 | (@pxref{Markup rules}). You can also use the @code{ATTR_LaTeX} line to |
67df9cfb CD |
8306 | request a longtable environment for the table, so that it may span several |
8307 | pages: | |
8308 | ||
8309 | @example | |
8310 | #+CAPTION: A long table | |
8311 | #+LABEL: tbl:long | |
8312 | #+ATTR_LaTeX: longtable | |
8313 | | ..... | ..... | | |
8314 | | ..... | ..... | | |
8315 | @end example | |
8316 | ||
8317 | ||
8318 | @node Images in LaTeX export, , Tables in LaTeX export, LaTeX and PDF export | |
8319 | @subsection Images in LaTeX export | |
8320 | @cindex images, inline in LaTeX | |
8321 | @cindex inlining images in LaTeX | |
8322 | ||
8323 | Images that are linked to without a description part in the link, like | |
8324 | @samp{[[file:img.jpg]]} or @samp{[[./img.jpg]]} will be inserted into the PDF | |
8325 | output files resulting from LaTeX output. Org will use an | |
8326 | @code{\includegraphics} macro to insert the image. If you have specified a | |
8327 | caption and/or a label as described in @ref{Markup rules}, the figure will | |
a50253cc | 8328 | be wrapped into a @code{figure} environment and thus become a floating |
67df9cfb CD |
8329 | element. Finally, you can use an @code{#+ATTR_LaTeX:} line to specify the |
8330 | options that can be used in the optional argument of the | |
8331 | @code{\includegraphics} macro. | |
8332 | ||
8333 | @example | |
8334 | #+CAPTION: The black-body emission of the disk around HR 4049 | |
8335 | #+LABEL: fig:SED-HR4049 | |
8336 | #+ATTR_LaTeX: width=5cm,angle=90 | |
8337 | [[./img/sed-hr4049.pdf]] | |
8338 | @end example | |
8339 | ||
55e0839d CD |
8340 | If you need references to a label created in this way, write |
8341 | @samp{\ref@{fig:SED-HR4049@}} just like in LaTeX. The default settings will | |
8342 | recognize files types that can be included as images during processing by | |
8343 | pdflatex (@file{png}, @file{jpg}, and @file{pdf} files). If you process your | |
8344 | files in a different way, you may need to customize the variable | |
8345 | @code{org-export-latex-inline-image-extensions}. | |
67df9cfb | 8346 | |
71d35b24 | 8347 | @node XOXO export, iCalendar export, LaTeX and PDF export, Exporting |
4009494e GM |
8348 | @section XOXO export |
8349 | @cindex XOXO export | |
8350 | ||
a7808fba | 8351 | Org mode contains an exporter that produces XOXO-style output. |
4009494e | 8352 | Currently, this exporter only handles the general outline structure and |
a7808fba | 8353 | does not interpret any additional Org mode features. |
4009494e GM |
8354 | |
8355 | @table @kbd | |
8356 | @kindex C-c C-e x | |
8357 | @item C-c C-e x | |
8358 | Export as XOXO file @file{myfile.html}. | |
8359 | @kindex C-c C-e v | |
8360 | @item C-c C-e v x | |
8361 | Export only the visible part of the document. | |
8362 | @end table | |
8363 | ||
b349f79f | 8364 | @node iCalendar export, , XOXO export, Exporting |
4009494e GM |
8365 | @section iCalendar export |
8366 | @cindex iCalendar export | |
8367 | ||
44ce9197 CD |
8368 | Some people like to use Org mode for keeping track of projects, but still |
8369 | prefer a standard calendar application for anniversaries and appointments. | |
8370 | In this case it can be useful to have deadlines and other time-stamped items | |
8371 | in Org files show up in the calendar application. Org mode can export | |
8372 | calendar information in the standard iCalendar format. If you also want to | |
8373 | have TODO entries included in the export, configure the variable | |
8374 | @code{org-icalendar-include-todo}. iCalendar export will export plain time | |
8375 | stamps as VEVENT, and TODO items as VTODO. It will also create events from | |
8376 | deadlines that are in non-TODO items. Deadlines and scheduling dates in TODO | |
8377 | items will be used to set the start and due dates for the todo | |
8378 | entry@footnote{See the variables @code{org-icalendar-use-deadline} and | |
864c9740 CD |
8379 | @code{org-icalendar-use-scheduled}.}. As categories, it will use the tags |
8380 | locally defined in the heading, and the file/tree category@footnote{To add | |
8381 | inherited tags or the TODO state, configure the variable | |
96c8522a | 8382 | @code{org-icalendar-categories}.}. |
4009494e | 8383 | |
b349f79f CD |
8384 | The iCalendar standard requires each entry to have a globally unique |
8385 | identifier (UID). Org creates these identifiers during export. If you set | |
8386 | the variable @code{org-icalendar-store-UID}, the UID will be stored in the | |
8387 | @code{:ID:} property of the entry and re-used next time you report this | |
8388 | entry. Since a single entry can give rise to multiple iCalendar entries (as | |
8389 | a timestamp, a deadline, a scheduled item, and as a TODO item), Org adds | |
8390 | prefixes to the UID, depending on what triggered the inclusion of the entry. | |
8391 | In this way the UID remains unique, but a synchronization program can still | |
8392 | figure out from which entry all the different instances originate. | |
8393 | ||
4009494e GM |
8394 | @table @kbd |
8395 | @kindex C-c C-e i | |
8396 | @item C-c C-e i | |
8397 | Create iCalendar entries for the current file and store them in the same | |
8398 | directory, using a file extension @file{.ics}. | |
8399 | @kindex C-c C-e I | |
8400 | @item C-c C-e I | |
8401 | Like @kbd{C-c C-e i}, but do this for all files in | |
8402 | @code{org-agenda-files}. For each of these files, a separate iCalendar | |
8403 | file will be written. | |
8404 | @kindex C-c C-e c | |
8405 | @item C-c C-e c | |
8406 | Create a single large iCalendar file from all files in | |
8407 | @code{org-agenda-files} and write it to the file given by | |
8408 | @code{org-combined-agenda-icalendar-file}. | |
8409 | @end table | |
8410 | ||
96c8522a CD |
8411 | The export will honor SUMMARY, DESCRIPTION and LOCATION@footnote{The LOCATION |
8412 | property can be inherited from higher in the hierarchy if you configure | |
8413 | @code{org-use-property-inheritance} accordingly.} properties if the selected | |
8414 | entries have them. If not, the summary will be derived from the headline, | |
8415 | and the description from the body (limited to | |
28a16a1b | 8416 | @code{org-icalendar-include-body} characters). |
dbc28aaa | 8417 | |
44ce9197 | 8418 | How this calendar is best read and updated, that depends on the application |
4009494e GM |
8419 | you are using. The FAQ covers this issue. |
8420 | ||
4009494e GM |
8421 | @node Publishing, Miscellaneous, Exporting, Top |
8422 | @chapter Publishing | |
8423 | @cindex publishing | |
8424 | ||
a7808fba | 8425 | Org includes@footnote{@file{org-publish.el} is not distributed with |
4009494e GM |
8426 | Emacs 21, if you are still using Emacs 21, you need you need to download |
8427 | this file separately.} a publishing management system that allows you to | |
8428 | configure automatic HTML conversion of @emph{projects} composed of | |
8429 | interlinked org files. This system is called @emph{org-publish}. You can | |
8430 | also configure org-publish to automatically upload your exported HTML | |
8431 | pages and related attachments, such as images and source code files, to | |
a7808fba | 8432 | a web server. Org-publish turns Org into a web-site authoring tool. |
4009494e GM |
8433 | |
8434 | You can also use Org-publish to convert files into La@TeX{}, or even | |
8435 | combine HTML and La@TeX{} conversion so that files are available in both | |
8436 | formats on the server@footnote{Since La@TeX{} files on a server are not | |
8437 | that helpful, you surely want to perform further conversion on them -- | |
8438 | e.g. convert them to @code{PDF} format.}. | |
8439 | ||
a7808fba | 8440 | Org-publish has been contributed to Org by David O'Toole. |
4009494e GM |
8441 | |
8442 | @menu | |
8443 | * Configuration:: Defining projects | |
8444 | * Sample configuration:: Example projects | |
8445 | * Triggering publication:: Publication commands | |
8446 | @end menu | |
8447 | ||
8448 | @node Configuration, Sample configuration, Publishing, Publishing | |
8449 | @section Configuration | |
8450 | ||
8451 | Publishing needs significant configuration to specify files, destination | |
8452 | and many other properties of a project. | |
8453 | ||
8454 | @menu | |
8455 | * Project alist:: The central configuration variable | |
8456 | * Sources and destinations:: From here to there | |
8457 | * Selecting files:: What files are part of the project? | |
8458 | * Publishing action:: Setting the function doing the publishing | |
8459 | * Publishing options:: Tweaking HTML export | |
8460 | * Publishing links:: Which links keep working after publishing? | |
8461 | * Project page index:: Publishing a list of project files | |
8462 | @end menu | |
8463 | ||
8464 | @node Project alist, Sources and destinations, Configuration, Configuration | |
8465 | @subsection The variable @code{org-publish-project-alist} | |
8466 | @cindex org-publish-project-alist | |
8467 | @cindex projects, for publishing | |
8468 | ||
8469 | Org-publish is configured almost entirely through setting the value of | |
8470 | one variable, called @code{org-publish-project-alist}. | |
8471 | Each element of the list configures one project, and may be in one of | |
8472 | the two following forms: | |
8473 | ||
8474 | @lisp | |
dbc28aaa | 8475 | ("project-name" :property value :property value ...) |
4009494e | 8476 | |
28a16a1b CD |
8477 | @r{or} |
8478 | ||
dbc28aaa | 8479 | ("project-name" :components ("project-name" "project-name" ...)) |
4009494e GM |
8480 | |
8481 | @end lisp | |
8482 | ||
8483 | In both cases, projects are configured by specifying property values. | |
8484 | A project defines the set of files that will be published, as well as | |
8485 | the publishing configuration to use when publishing those files. When | |
8486 | a project takes the second form listed above, the individual members | |
8487 | of the ``components'' property are taken to be components of the | |
8488 | project, which group together files requiring different publishing | |
8489 | options. When you publish such a ``meta-project'' all the components | |
96c8522a CD |
8490 | will also publish. The @code{:components} are published in the sequence |
8491 | provided. | |
4009494e GM |
8492 | |
8493 | @node Sources and destinations, Selecting files, Project alist, Configuration | |
8494 | @subsection Sources and destinations for files | |
8495 | @cindex directories, for publishing | |
8496 | ||
8497 | Most properties are optional, but some should always be set. In | |
8498 | particular, org-publish needs to know where to look for source files, | |
8499 | and where to put published files. | |
8500 | ||
8501 | @multitable @columnfractions 0.3 0.7 | |
8502 | @item @code{:base-directory} | |
8503 | @tab Directory containing publishing source files | |
8504 | @item @code{:publishing-directory} | |
8505 | @tab Directory (possibly remote) where output files will be published. | |
8506 | @item @code{:preparation-function} | |
b349f79f | 8507 | @tab Function called before starting the publishing process, for example to |
4009494e | 8508 | run @code{make} for updating files to be published. |
b349f79f CD |
8509 | @item @code{:completion-function} |
8510 | @tab Function called after finishing the publishing process, for example to | |
8511 | change permissions of the resulting files. | |
4009494e GM |
8512 | @end multitable |
8513 | @noindent | |
8514 | ||
8515 | @node Selecting files, Publishing action, Sources and destinations, Configuration | |
8516 | @subsection Selecting files | |
8517 | @cindex files, selecting for publishing | |
8518 | ||
8519 | By default, all files with extension @file{.org} in the base directory | |
8520 | are considered part of the project. This can be modified by setting the | |
28a16a1b | 8521 | properties |
4009494e GM |
8522 | @multitable @columnfractions 0.25 0.75 |
8523 | @item @code{:base-extension} | |
8524 | @tab Extension (without the dot!) of source files. This actually is a | |
8525 | regular expression. | |
8526 | ||
28a16a1b | 8527 | @item @code{:exclude} |
4009494e GM |
8528 | @tab Regular expression to match file names that should not be |
8529 | published, even though they have been selected on the basis of their | |
8530 | extension. | |
8531 | ||
8532 | @item @code{:include} | |
8533 | @tab List of files to be included regardless of @code{:base-extension} | |
8534 | and @code{:exclude}. | |
8535 | @end multitable | |
8536 | ||
8537 | @node Publishing action, Publishing options, Selecting files, Configuration | |
a7808fba | 8538 | @subsection Publishing action |
4009494e GM |
8539 | @cindex action, for publishing |
8540 | ||
8541 | Publishing means that a file is copied to the destination directory and | |
71d35b24 CD |
8542 | possibly transformed in the process. The default transformation is to export |
8543 | Org files as HTML files, and this is done by the function | |
8544 | @code{org-publish-org-to-html} which calls the HTML exporter (@pxref{HTML | |
8545 | export}). But you also can publish your files in La@TeX{} by using the | |
8546 | function @code{org-publish-org-to-latex} instead, or as PDF files using | |
8547 | @code{org-publish-org-to-pdf}. Other files like images only need to be | |
8548 | copied to the publishing destination. For non-Org files, you need to provide | |
8549 | your own publishing function: | |
4009494e GM |
8550 | |
8551 | @multitable @columnfractions 0.3 0.7 | |
8552 | @item @code{:publishing-function} | |
8553 | @tab Function executing the publication of a file. This may also be a | |
8554 | list of functions, which will all be called in turn. | |
8555 | @end multitable | |
8556 | ||
8557 | The function must accept two arguments: a property list containing at | |
8558 | least a @code{:publishing-directory} property, and the name of the file | |
8559 | to be published. It should take the specified file, make the necessary | |
8560 | transformation (if any) and place the result into the destination folder. | |
8561 | You can write your own publishing function, but @code{org-publish} | |
8562 | provides one for attachments (files that only need to be copied): | |
8563 | @code{org-publish-attachment}. | |
8564 | ||
8565 | @node Publishing options, Publishing links, Publishing action, Configuration | |
8566 | @subsection Options for the HTML/LaTeX exporters | |
8567 | @cindex options, for publishing | |
8568 | ||
8569 | The property list can be used to set many export options for the HTML | |
8570 | and La@TeX{} exporters. In most cases, these properties correspond to user | |
a7808fba | 8571 | variables in Org. The table below lists these properties along |
4009494e GM |
8572 | with the variable they belong to. See the documentation string for the |
8573 | respective variable for details. | |
8574 | ||
96c8522a CD |
8575 | @multitable @columnfractions 0.32 0.68 |
8576 | @item @code{:link-up} @tab @code{org-export-html-link-up} | |
8577 | @item @code{:link-home} @tab @code{org-export-html-link-home} | |
4009494e | 8578 | @item @code{:language} @tab @code{org-export-default-language} |
96c8522a | 8579 | @item @code{:customtime} @tab @code{org-display-custom-times} |
4009494e GM |
8580 | @item @code{:headline-levels} @tab @code{org-export-headline-levels} |
8581 | @item @code{:section-numbers} @tab @code{org-export-with-section-numbers} | |
96c8522a | 8582 | @item @code{:section-number-format} @tab @code{org-export-section-number-format} |
4009494e | 8583 | @item @code{:table-of-contents} @tab @code{org-export-with-toc} |
96c8522a | 8584 | @item @code{:preserve-breaks} @tab @code{org-export-preserve-breaks} |
4009494e GM |
8585 | @item @code{:archived-trees} @tab @code{org-export-with-archived-trees} |
8586 | @item @code{:emphasize} @tab @code{org-export-with-emphasize} | |
8587 | @item @code{:sub-superscript} @tab @code{org-export-with-sub-superscripts} | |
dbc28aaa | 8588 | @item @code{:special-strings} @tab @code{org-export-with-special-strings} |
96c8522a CD |
8589 | @item @code{:footnotes} @tab @code{org-export-with-footnotes} |
8590 | @item @code{:drawers} @tab @code{org-export-with-drawers} | |
8591 | @item @code{:tags} @tab @code{org-export-with-tags} | |
8592 | @item @code{:todo-keywords} @tab @code{org-export-with-todo-keywords} | |
8593 | @item @code{:priority} @tab @code{org-export-with-priority} | |
4009494e GM |
8594 | @item @code{:TeX-macros} @tab @code{org-export-with-TeX-macros} |
8595 | @item @code{:LaTeX-fragments} @tab @code{org-export-with-LaTeX-fragments} | |
96c8522a | 8596 | @item @code{:skip-before-1st-heading} @tab @code{org-export-skip-text-before-1st-heading} |
4009494e | 8597 | @item @code{:fixed-width} @tab @code{org-export-with-fixed-width} |
44ce9197 CD |
8598 | @item @code{:timestamps} @tab @code{org-export-with-timestamps} |
8599 | @item @code{:author-info} @tab @code{org-export-author-info} | |
8600 | @item @code{:creator-info} @tab @code{org-export-creator-info} | |
4009494e GM |
8601 | @item @code{:tables} @tab @code{org-export-with-tables} |
8602 | @item @code{:table-auto-headline} @tab @code{org-export-highlight-first-table-line} | |
e45e3595 | 8603 | @item @code{:style-include-default} @tab @code{org-export-html-style-include-default} |
4009494e | 8604 | @item @code{:style} @tab @code{org-export-html-style} |
44ce9197 | 8605 | @item @code{:style-extra} @tab @code{org-export-html-style-extra} |
4009494e GM |
8606 | @item @code{:convert-org-links} @tab @code{org-export-html-link-org-files-as-html} |
8607 | @item @code{:inline-images} @tab @code{org-export-html-inline-images} | |
96c8522a CD |
8608 | @item @code{:html-extension} @tab @code{org-export-html-extension} |
8609 | @item @code{:html-table-tag} @tab @code{org-export-html-table-tag} | |
4009494e GM |
8610 | @item @code{:expand-quoted-html} @tab @code{org-export-html-expand} |
8611 | @item @code{:timestamp} @tab @code{org-export-html-with-timestamp} | |
8612 | @item @code{:publishing-directory} @tab @code{org-export-publishing-directory} | |
8613 | @item @code{:preamble} @tab @code{org-export-html-preamble} | |
8614 | @item @code{:postamble} @tab @code{org-export-html-postamble} | |
8615 | @item @code{:auto-preamble} @tab @code{org-export-html-auto-preamble} | |
8616 | @item @code{:auto-postamble} @tab @code{org-export-html-auto-postamble} | |
8617 | @item @code{:author} @tab @code{user-full-name} | |
8618 | @item @code{:email} @tab @code{user-mail-address} | |
864c9740 CD |
8619 | @item @code{:select-tags} @tab @code{org-export-select-tags} |
8620 | @item @code{:exclude-tags} @tab @code{org-export-exclude-tags} | |
4009494e GM |
8621 | @end multitable |
8622 | ||
dbc28aaa CD |
8623 | If you use several email addresses, separate them by a semi-column. |
8624 | ||
4009494e GM |
8625 | Most of the @code{org-export-with-*} variables have the same effect in |
8626 | both HTML and La@TeX{} exporters, except for @code{:TeX-macros} and | |
8627 | @code{:LaTeX-fragments}, respectively @code{nil} and @code{t} in the | |
8628 | La@TeX{} export. | |
8629 | ||
dbc28aaa CD |
8630 | When a property is given a value in @code{org-publish-project-alist}, |
8631 | its setting overrides the value of the corresponding user variable (if | |
8632 | any) during publishing. Options set within a file (@pxref{Export | |
4009494e GM |
8633 | options}), however, override everything. |
8634 | ||
8635 | @node Publishing links, Project page index, Publishing options, Configuration | |
8636 | @subsection Links between published files | |
8637 | @cindex links, publishing | |
8638 | ||
a7808fba | 8639 | To create a link from one Org file to another, you would use |
4009494e GM |
8640 | something like @samp{[[file:foo.org][The foo]]} or simply |
8641 | @samp{file:foo.org.} (@pxref{Hyperlinks}). Upon publishing this link | |
8642 | becomes a link to @file{foo.html}. In this way, you can interlink the | |
8643 | pages of your "org web" project and the links will work as expected when | |
8644 | you publish them to HTML. | |
8645 | ||
8646 | You may also link to related files, such as images. Provided you are | |
8647 | careful with relative pathnames, and provided you have also configured | |
dbc28aaa | 8648 | @code{org-publish} to upload the related files, these links will work |
b6cb4cd5 | 8649 | too. See @ref{Complex example} for an example of this usage. |
4009494e | 8650 | |
a7808fba | 8651 | Sometime an Org file to be published may contain links that are |
4009494e | 8652 | only valid in your production environment, but not in the publishing |
28a16a1b | 8653 | location. In this case, use the property |
4009494e GM |
8654 | |
8655 | @multitable @columnfractions 0.4 0.6 | |
8656 | @item @code{:link-validation-function} | |
8657 | @tab Function to validate links | |
8658 | @end multitable | |
8659 | ||
8660 | @noindent | |
8661 | to define a function for checking link validity. This function must | |
8662 | accept two arguments, the file name and a directory relative to which | |
8663 | the file name is interpreted in the production environment. If this | |
8664 | function returns @code{nil}, then the HTML generator will only insert a | |
8665 | description into the HTML file, but no link. One option for this | |
8666 | function is @code{org-publish-validate-link} which checks if the given | |
8667 | file is part of any project in @code{org-publish-project-alist}. | |
8668 | ||
8669 | @node Project page index, , Publishing links, Configuration | |
8670 | @subsection Project page index | |
8671 | @cindex index, of published pages | |
8672 | ||
8673 | The following properties may be used to control publishing of an | |
8674 | index of files or summary page for a given project. | |
8675 | ||
8676 | @multitable @columnfractions 0.25 0.75 | |
8677 | @item @code{:auto-index} | |
8678 | @tab When non-nil, publish an index during org-publish-current-project or | |
8679 | org-publish-all. | |
8680 | ||
8681 | @item @code{:index-filename} | |
8682 | @tab Filename for output of index. Defaults to @file{index.org} (which | |
8683 | becomes @file{index.html}). | |
8684 | ||
8685 | @item @code{:index-title} | |
8686 | @tab Title of index page. Defaults to name of file. | |
8687 | ||
8688 | @item @code{:index-function} | |
a7808fba | 8689 | @tab Plug-in function to use for generation of index. |
4009494e GM |
8690 | Defaults to @code{org-publish-org-index}, which generates a plain list |
8691 | of links to all files in the project. | |
8692 | @end multitable | |
8693 | ||
8694 | @node Sample configuration, Triggering publication, Configuration, Publishing | |
8695 | @section Sample configuration | |
8696 | ||
8697 | Below we provide two example configurations. The first one is a simple | |
a7808fba | 8698 | project publishing only a set of Org files. The second example is |
4009494e GM |
8699 | more complex, with a multi-component project. |
8700 | ||
8701 | @menu | |
8702 | * Simple example:: One-component publishing | |
8703 | * Complex example:: A multi-component publishing example | |
8704 | @end menu | |
8705 | ||
8706 | @node Simple example, Complex example, Sample configuration, Sample configuration | |
8707 | @subsection Example: simple publishing configuration | |
8708 | ||
a7808fba | 8709 | This example publishes a set of Org files to the @file{public_html} |
4009494e GM |
8710 | directory on the local machine. |
8711 | ||
8712 | @lisp | |
8713 | (setq org-publish-project-alist | |
28a16a1b | 8714 | '(("org" |
4009494e GM |
8715 | :base-directory "~/org/" |
8716 | :publishing-directory "~/public_html" | |
8717 | :section-numbers nil | |
8718 | :table-of-contents nil | |
e45e3595 | 8719 | :style "<link rel=\"stylesheet\" |
4009494e GM |
8720 | href=\"../other/mystyle.css\" |
8721 | type=\"text/css\">"))) | |
8722 | @end lisp | |
8723 | ||
8724 | @node Complex example, , Simple example, Sample configuration | |
8725 | @subsection Example: complex publishing configuration | |
8726 | ||
8727 | This more complicated example publishes an entire website, including | |
8728 | org files converted to HTML, image files, emacs lisp source code, and | |
a7808fba | 8729 | style sheets. The publishing-directory is remote and private files are |
4009494e GM |
8730 | excluded. |
8731 | ||
8732 | To ensure that links are preserved, care should be taken to replicate | |
8733 | your directory structure on the web server, and to use relative file | |
8734 | paths. For example, if your org files are kept in @file{~/org} and your | |
8735 | publishable images in @file{~/images}, you'd link to an image with | |
8736 | @c | |
8737 | @example | |
8738 | file:../images/myimage.png | |
8739 | @end example | |
8740 | @c | |
8741 | On the web server, the relative path to the image should be the | |
8742 | same. You can accomplish this by setting up an "images" folder in the | |
a7808fba | 8743 | right place on the web server, and publishing images to it. |
4009494e GM |
8744 | |
8745 | @lisp | |
8746 | (setq org-publish-project-alist | |
8747 | '(("orgfiles" | |
8748 | :base-directory "~/org/" | |
8749 | :base-extension "org" | |
8750 | :publishing-directory "/ssh:user@@host:~/html/notebook/" | |
8751 | :publishing-function org-publish-org-to-html | |
8752 | :exclude "PrivatePage.org" ;; regexp | |
8753 | :headline-levels 3 | |
8754 | :section-numbers nil | |
8755 | :table-of-contents nil | |
e45e3595 | 8756 | :style "<link rel=\"stylesheet\" |
4009494e GM |
8757 | href=\"../other/mystyle.css\" type=\"text/css\">" |
8758 | :auto-preamble t | |
8759 | :auto-postamble nil) | |
28a16a1b | 8760 | |
4009494e GM |
8761 | ("images" |
8762 | :base-directory "~/images/" | |
8763 | :base-extension "jpg\\|gif\\|png" | |
8764 | :publishing-directory "/ssh:user@@host:~/html/images/" | |
8765 | :publishing-function org-publish-attachment) | |
28a16a1b | 8766 | |
4009494e GM |
8767 | ("other" |
8768 | :base-directory "~/other/" | |
8769 | :base-extension "css\\|el" | |
8770 | :publishing-directory "/ssh:user@@host:~/html/other/" | |
8771 | :publishing-function org-publish-attachment) | |
8772 | ("website" :components ("orgfiles" "images" "other")))) | |
8773 | @end lisp | |
8774 | ||
8775 | @node Triggering publication, , Sample configuration, Publishing | |
8776 | @section Triggering publication | |
8777 | ||
8778 | Once org-publish is properly configured, you can publish with the | |
28a16a1b | 8779 | following functions: |
4009494e GM |
8780 | |
8781 | @table @kbd | |
8782 | @item C-c C-e C | |
8783 | Prompt for a specific project and publish all files that belong to it. | |
8784 | @item C-c C-e P | |
8785 | Publish the project containing the current file. | |
8786 | @item C-c C-e F | |
8787 | Publish only the current file. | |
8788 | @item C-c C-e A | |
8789 | Publish all projects. | |
8790 | @end table | |
8791 | ||
8792 | Org uses timestamps to track when a file has changed. The above | |
8793 | functions normally only publish changed files. You can override this and | |
8794 | force publishing of all files by giving a prefix argument. | |
8795 | ||
b349f79f | 8796 | @node Miscellaneous, Extensions, Publishing, Top |
4009494e GM |
8797 | @chapter Miscellaneous |
8798 | ||
8799 | @menu | |
8800 | * Completion:: M-TAB knows what you need | |
a7808fba | 8801 | * Customization:: Adapting Org to your taste |
4009494e GM |
8802 | * In-buffer settings:: Overview of the #+KEYWORDS |
8803 | * The very busy C-c C-c key:: When in doubt, press C-c C-c | |
8804 | * Clean view:: Getting rid of leading stars in the outline | |
a7808fba | 8805 | * TTY keys:: Using Org on a tty |
4009494e GM |
8806 | * Interaction:: Other Emacs packages |
8807 | * Bugs:: Things which do not work perfectly | |
8808 | @end menu | |
8809 | ||
8810 | @node Completion, Customization, Miscellaneous, Miscellaneous | |
8811 | @section Completion | |
8812 | @cindex completion, of @TeX{} symbols | |
8813 | @cindex completion, of TODO keywords | |
8814 | @cindex completion, of dictionary words | |
8815 | @cindex completion, of option keywords | |
8816 | @cindex completion, of tags | |
8817 | @cindex completion, of property keys | |
8818 | @cindex completion, of link abbreviations | |
8819 | @cindex @TeX{} symbol completion | |
8820 | @cindex TODO keywords completion | |
8821 | @cindex dictionary word completion | |
8822 | @cindex option keyword completion | |
8823 | @cindex tag completion | |
8824 | @cindex link abbreviations, completion of | |
8825 | ||
a7808fba | 8826 | Org supports in-buffer completion. This type of completion does |
4009494e GM |
8827 | not make use of the minibuffer. You simply type a few letters into |
8828 | the buffer and use the key to complete text right there. | |
8829 | ||
8830 | @table @kbd | |
8831 | @kindex M-@key{TAB} | |
8832 | @item M-@key{TAB} | |
8833 | Complete word at point | |
8834 | @itemize @bullet | |
8835 | @item | |
8836 | At the beginning of a headline, complete TODO keywords. | |
8837 | @item | |
8838 | After @samp{\}, complete @TeX{} symbols supported by the exporter. | |
8839 | @item | |
8840 | After @samp{*}, complete headlines in the current buffer so that they | |
8841 | can be used in search links like @samp{[[*find this headline]]}. | |
8842 | @item | |
8843 | After @samp{:} in a headline, complete tags. The list of tags is taken | |
8844 | from the variable @code{org-tag-alist} (possibly set through the | |
8845 | @samp{#+TAGS} in-buffer option, @pxref{Setting tags}), or it is created | |
8846 | dynamically from all tags used in the current buffer. | |
8847 | @item | |
8848 | After @samp{:} and not in a headline, complete property keys. The list | |
8849 | of keys is constructed dynamically from all keys used in the current | |
8850 | buffer. | |
8851 | @item | |
8852 | After @samp{[}, complete link abbreviations (@pxref{Link abbreviations}). | |
8853 | @item | |
8854 | After @samp{#+}, complete the special keywords like @samp{TYP_TODO} or | |
a7808fba | 8855 | @samp{OPTIONS} which set file-specific options for Org mode. When the |
4009494e GM |
8856 | option keyword is already complete, pressing @kbd{M-@key{TAB}} again |
8857 | will insert example settings for this keyword. | |
8858 | @item | |
8859 | In the line after @samp{#+STARTUP: }, complete startup keywords, | |
8860 | i.e. valid keys for this line. | |
8861 | @item | |
a7808fba | 8862 | Elsewhere, complete dictionary words using Ispell. |
4009494e GM |
8863 | @end itemize |
8864 | @end table | |
8865 | ||
8866 | @node Customization, In-buffer settings, Completion, Miscellaneous | |
8867 | @section Customization | |
8868 | @cindex customization | |
8869 | @cindex options, for customization | |
8870 | @cindex variables, for customization | |
8871 | ||
8872 | There are more than 180 variables that can be used to customize | |
a7808fba | 8873 | Org. For the sake of compactness of the manual, I am not |
4009494e GM |
8874 | describing the variables here. A structured overview of customization |
8875 | variables is available with @kbd{M-x org-customize}. Or select | |
8876 | @code{Browse Org Group} from the @code{Org->Customization} menu. Many | |
8877 | settings can also be activated on a per-file basis, by putting special | |
8878 | lines into the buffer (@pxref{In-buffer settings}). | |
8879 | ||
8880 | @node In-buffer settings, The very busy C-c C-c key, Customization, Miscellaneous | |
8881 | @section Summary of in-buffer settings | |
8882 | @cindex in-buffer settings | |
8883 | @cindex special keywords | |
8884 | ||
a7808fba | 8885 | Org mode uses special lines in the buffer to define settings on a |
4009494e GM |
8886 | per-file basis. These lines start with a @samp{#+} followed by a |
8887 | keyword, a colon, and then individual words defining a setting. Several | |
8888 | setting words can be in the same line, but you can also have multiple | |
8889 | lines for the keyword. While these settings are described throughout | |
8890 | the manual, here is a summary. After changing any of those lines in the | |
8891 | buffer, press @kbd{C-c C-c} with the cursor still in the line to | |
8892 | activate the changes immediately. Otherwise they become effective only | |
8893 | when the file is visited again in a new Emacs session. | |
8894 | ||
8895 | @table @kbd | |
8896 | @item #+ARCHIVE: %s_done:: | |
8897 | This line sets the archive location for the agenda file. It applies for | |
8898 | all subsequent lines until the next @samp{#+ARCHIVE} line, or the end | |
8899 | of the file. The first such line also applies to any entries before it. | |
8900 | The corresponding variable is @code{org-archive-location}. | |
8901 | @item #+CATEGORY: | |
8902 | This line sets the category for the agenda file. The category applies | |
8903 | for all subsequent lines until the next @samp{#+CATEGORY} line, or the | |
8904 | end of the file. The first such line also applies to any entries before it. | |
8905 | @item #+COLUMNS: %25ITEM ..... | |
8906 | Set the default format for columns view. This format applies when | |
dbc28aaa CD |
8907 | columns view is invoked in location where no @code{COLUMNS} property |
8908 | applies. | |
4009494e GM |
8909 | @item #+CONSTANTS: name1=value1 ... |
8910 | Set file-local values for constants to be used in table formulas. This | |
8911 | line set the local variable @code{org-table-formula-constants-local}. | |
dbc28aaa | 8912 | The global version of this variable is |
4009494e | 8913 | @code{org-table-formula-constants}. |
b349f79f CD |
8914 | @item #+FILETAGS: :tag1:tag2:tag3: |
8915 | Set tags that can be inherited by any entry in the file, including the | |
8916 | top-level entries. | |
dbc28aaa CD |
8917 | @item #+DRAWERS: NAME1 ..... |
8918 | Set the file-local set of drawers. The corresponding global variable is | |
8919 | @code{org-drawers}. | |
4009494e GM |
8920 | @item #+LINK: linkword replace |
8921 | These lines (several are allowed) specify link abbreviations. | |
8922 | @xref{Link abbreviations}. The corresponding variable is | |
8923 | @code{org-link-abbrev-alist}. | |
8924 | @item #+PRIORITIES: highest lowest default | |
8925 | This line sets the limits and the default for the priorities. All three | |
8926 | must be either letters A-Z or numbers 0-9. The highest priority must | |
8927 | have a lower ASCII number that the lowest priority. | |
8928 | @item #+PROPERTY: Property_Name Value | |
8929 | This line sets a default inheritance value for entries in the current | |
8930 | buffer, most useful for specifying the allowed values of a property. | |
b349f79f CD |
8931 | @item #+SETUPFILE: file |
8932 | This line defines a file that holds more in-buffer setup. Normally this is | |
8933 | entirely ignored. Only when the buffer is parsed for option-setting lines | |
8934 | (i.e. when starting Org mode for a file, when pressing @kbd{C-c C-c} in a | |
8935 | settings line, or when exporting), then the contents of this file are parsed | |
a50253cc | 8936 | as if they had been included in the buffer. In particular, the file can be |
b349f79f CD |
8937 | any other Org mode file with internal setup. You can visit the file the |
8938 | cursor is in the line with @kbd{C-c '}. | |
4009494e | 8939 | @item #+STARTUP: |
a7808fba CD |
8940 | This line sets options to be used at startup of Org mode, when an |
8941 | Org file is being visited. The first set of options deals with the | |
4009494e GM |
8942 | initial visibility of the outline tree. The corresponding variable for |
8943 | global default settings is @code{org-startup-folded}, with a default | |
8944 | value @code{t}, which means @code{overview}. | |
8945 | @cindex @code{overview}, STARTUP keyword | |
8946 | @cindex @code{content}, STARTUP keyword | |
8947 | @cindex @code{showall}, STARTUP keyword | |
8948 | @example | |
8949 | overview @r{top-level headlines only} | |
8950 | content @r{all headlines} | |
8951 | showall @r{no folding at all, show everything} | |
8952 | @end example | |
8953 | Then there are options for aligning tables upon visiting a file. This | |
8954 | is useful in files containing narrowed table columns. The corresponding | |
8955 | variable is @code{org-startup-align-all-tables}, with a default value | |
28a16a1b | 8956 | @code{nil}. |
4009494e GM |
8957 | @cindex @code{align}, STARTUP keyword |
8958 | @cindex @code{noalign}, STARTUP keyword | |
8959 | @example | |
8960 | align @r{align all tables} | |
8961 | noalign @r{don't align tables on startup} | |
8962 | @end example | |
28a16a1b CD |
8963 | Logging closing and reinstating TODO items, and clock intervals |
8964 | (variables @code{org-log-done}, @code{org-log-note-clock-out}, and | |
8965 | @code{org-log-repeat}) can be configured using these options. | |
4009494e | 8966 | @cindex @code{logdone}, STARTUP keyword |
4009494e | 8967 | @cindex @code{lognotedone}, STARTUP keyword |
28a16a1b | 8968 | @cindex @code{nologdone}, STARTUP keyword |
4009494e | 8969 | @cindex @code{lognoteclock-out}, STARTUP keyword |
28a16a1b | 8970 | @cindex @code{nolognoteclock-out}, STARTUP keyword |
4009494e | 8971 | @cindex @code{logrepeat}, STARTUP keyword |
28a16a1b | 8972 | @cindex @code{lognoterepeat}, STARTUP keyword |
4009494e GM |
8973 | @cindex @code{nologrepeat}, STARTUP keyword |
8974 | @example | |
28a16a1b CD |
8975 | logdone @r{record a timestamp when an item is marked DONE} |
8976 | lognotedone @r{record timestamp and a note when DONE} | |
8977 | nologdone @r{don't record when items are marked DONE} | |
8978 | logrepeat @r{record a time when reinstating a repeating item} | |
8979 | lognoterepeat @r{record a note when reinstating a repeating item} | |
8980 | nologrepeat @r{do not record when reinstating repeating item} | |
8981 | lognoteclock-out @r{record a note when clocking out} | |
8982 | nolognoteclock-out @r{don't record a note when clocking out} | |
4009494e | 8983 | @end example |
b349f79f CD |
8984 | Here are the options for hiding leading stars in outline headings, and for |
8985 | indenting outlines. The corresponding variables are | |
8986 | @code{org-hide-leading-stars} and @code{org-odd-levels-only}, both with a | |
8987 | default setting @code{nil} (meaning @code{showstars} and @code{oddeven}). | |
4009494e GM |
8988 | @cindex @code{hidestars}, STARTUP keyword |
8989 | @cindex @code{showstars}, STARTUP keyword | |
8990 | @cindex @code{odd}, STARTUP keyword | |
8991 | @cindex @code{even}, STARTUP keyword | |
8992 | @example | |
8993 | hidestars @r{make all but one of the stars starting a headline invisible.} | |
8994 | showstars @r{show all stars starting a headline} | |
b349f79f CD |
8995 | indent @r{virtual indentation according to outline level} |
8996 | noindent @r{no virtual indentation according to outline level} | |
4009494e GM |
8997 | odd @r{allow only odd outline levels (1,3,...)} |
8998 | oddeven @r{allow all outline levels} | |
8999 | @end example | |
9000 | To turn on custom format overlays over time stamps (variables | |
9001 | @code{org-put-time-stamp-overlays} and | |
9002 | @code{org-time-stamp-overlay-formats}), use | |
9003 | @cindex @code{customtime}, STARTUP keyword | |
9004 | @example | |
9005 | customtime @r{overlay custom time format} | |
9006 | @end example | |
9007 | The following options influence the table spreadsheet (variable | |
9008 | @code{constants-unit-system}). | |
9009 | @cindex @code{constcgs}, STARTUP keyword | |
9010 | @cindex @code{constSI}, STARTUP keyword | |
9011 | @example | |
9012 | constcgs @r{@file{constants.el} should use the c-g-s unit system} | |
9013 | constSI @r{@file{constants.el} should use the SI unit system} | |
9014 | @end example | |
55e0839d CD |
9015 | To influence footnote settings, use the following keywords. The |
9016 | corresponding variables are @code{org-footnote-define-inline} and | |
9017 | @code{org-footnote-auto-label}. | |
9018 | @cindex @code{fninline}, STARTUP keyword | |
9019 | @cindex @code{fnnoinline}, STARTUP keyword | |
9020 | @cindex @code{fnlocal}, STARTUP keyword | |
9021 | @cindex @code{fnprompt}, STARTUP keyword | |
9022 | @cindex @code{fnauto}, STARTUP keyword | |
9023 | @cindex @code{fnconfirm}, STARTUP keyword | |
9024 | @cindex @code{fnplain}, STARTUP keyword | |
9025 | @example | |
9026 | fninline @r{define footnotes inline} | |
9027 | fnnoinline @r{define footnotes in separate section} | |
9028 | fnlocal @r{define footnotes near first reference, but not inline} | |
9029 | fnprompt @r{prompt for footnote labels} | |
9030 | fnauto @r{create [fn:1]-like labels automatically (default)} | |
9031 | fnconfirm @r{offer automatic label for editing or confirmation} | |
9032 | fnplain @r{create [1]-like labels automatically} | |
9033 | @end example | |
4009494e | 9034 | @item #+TAGS: TAG1(c1) TAG2(c2) |
cad1d376 | 9035 | These lines (several such lines are allowed) specify the valid tags in |
4009494e GM |
9036 | this file, and (potentially) the corresponding @emph{fast tag selection} |
9037 | keys. The corresponding variable is @code{org-tag-alist}. | |
9038 | @item #+TBLFM: | |
9039 | This line contains the formulas for the table directly above the line. | |
dbc28aaa | 9040 | @item #+TITLE:, #+AUTHOR:, #+EMAIL:, #+LANGUAGE:, #+TEXT:, #+OPTIONS, #+DATE: |
4009494e GM |
9041 | These lines provide settings for exporting files. For more details see |
9042 | @ref{Export options}. | |
9043 | @item #+SEQ_TODO: #+TYP_TODO: | |
9044 | These lines set the TODO keywords and their interpretation in the | |
9045 | current file. The corresponding variables are @code{org-todo-keywords} | |
9046 | and @code{org-todo-interpretation}. | |
9047 | @end table | |
9048 | ||
9049 | @node The very busy C-c C-c key, Clean view, In-buffer settings, Miscellaneous | |
9050 | @section The very busy C-c C-c key | |
9051 | @kindex C-c C-c | |
9052 | @cindex C-c C-c, overview | |
9053 | ||
a7808fba | 9054 | The key @kbd{C-c C-c} has many purposes in Org, which are all |
4009494e GM |
9055 | mentioned scattered throughout this manual. One specific function of |
9056 | this key is to add @emph{tags} to a headline (@pxref{Tags}). In many | |
a7808fba | 9057 | other circumstances it means something like @emph{Hey Org, look |
4009494e GM |
9058 | here and update according to what you see here}. Here is a summary of |
9059 | what this means in different contexts. | |
9060 | ||
9061 | @itemize @minus | |
9062 | @item | |
9063 | If there are highlights in the buffer from the creation of a sparse | |
9064 | tree, or from clock display, remove these highlights. | |
9065 | @item | |
9066 | If the cursor is in one of the special @code{#+KEYWORD} lines, this | |
9067 | triggers scanning the buffer for these lines and updating the | |
28a16a1b | 9068 | information. |
4009494e GM |
9069 | @item |
9070 | If the cursor is inside a table, realign the table. This command | |
9071 | works even if the automatic table editor has been turned off. | |
9072 | @item | |
9073 | If the cursor is on a @code{#+TBLFM} line, re-apply the formulas to | |
9074 | the entire table. | |
9075 | @item | |
9076 | If the cursor is inside a table created by the @file{table.el} package, | |
9077 | activate that table. | |
9078 | @item | |
9079 | If the current buffer is a remember buffer, close the note and file it. | |
9080 | With a prefix argument, file it, without further interaction, to the | |
9081 | default location. | |
9082 | @item | |
9083 | If the cursor is on a @code{<<<target>>>}, update radio targets and | |
9084 | corresponding links in this buffer. | |
9085 | @item | |
9086 | If the cursor is in a property line or at the start or end of a property | |
9087 | drawer, offer property commands. | |
9088 | @item | |
55e0839d CD |
9089 | If the cursor is at a footnote reference, go to the corresponding |
9090 | definition, and vice versa. | |
9091 | @item | |
4009494e GM |
9092 | If the cursor is in a plain list item with a checkbox, toggle the status |
9093 | of the checkbox. | |
9094 | @item | |
9095 | If the cursor is on a numbered item in a plain list, renumber the | |
9096 | ordered list. | |
dbc28aaa CD |
9097 | @item |
9098 | If the cursor is on the @code{#+BEGIN} line of a dynamical block, the | |
9099 | block is updated. | |
4009494e GM |
9100 | @end itemize |
9101 | ||
9102 | @node Clean view, TTY keys, The very busy C-c C-c key, Miscellaneous | |
9103 | @section A cleaner outline view | |
9104 | @cindex hiding leading stars | |
b349f79f CD |
9105 | @cindex dynamic indentation |
9106 | @cindex odd-levels-only outlines | |
4009494e GM |
9107 | @cindex clean outline view |
9108 | ||
b349f79f CD |
9109 | Some people find it noisy and distracting that the Org headlines are starting |
9110 | with a potentially large number of stars, and that text below the headlines | |
9111 | is not indented. This is not really a problem when you are writing a book | |
9112 | where the outline headings are really section headlines. However, in a more | |
9113 | list-oriented outline, it is clear that an indented structure is a lot | |
9114 | cleaner, as can be seen by comparing the two columns in the following | |
96c8522a | 9115 | example: |
4009494e GM |
9116 | |
9117 | @example | |
b349f79f CD |
9118 | @group |
9119 | * Top level headline | * Top level headline | |
9120 | ** Second level | * Second level | |
9121 | *** 3rd level | * 3rd level | |
9122 | some text | some text | |
9123 | *** 3rd level | * 3rd level | |
9124 | more text | more text | |
9125 | * Another top level headline | * Another top level headline | |
9126 | @end group | |
4009494e GM |
9127 | @end example |
9128 | ||
9129 | @noindent | |
b349f79f CD |
9130 | It is non-trivial to make such a look work in Emacs, but Org contains three |
9131 | separate features that, combined, achieve just that. | |
4009494e | 9132 | |
b349f79f | 9133 | @enumerate |
96c8522a | 9134 | @item |
b349f79f CD |
9135 | @emph{Indentation of text below headlines}@* |
9136 | You may indent text below each headline to make the left boundary line up | |
9137 | with the headline, like | |
4009494e | 9138 | |
b349f79f CD |
9139 | @example |
9140 | *** 3rd level | |
9141 | more text, now indented | |
9142 | @end example | |
9143 | ||
9144 | A good way to get this indentation is by hand, and Org supports this with | |
9145 | paragraph filling, line wrapping, and structure editing@footnote{See also the | |
9146 | variable @code{org-adapt-indentation}.} preserving or adapting the | |
9147 | indentation appropriate. A different approach would be to have a way to | |
9148 | automatically indent lines according to outline structure by adding overlays | |
9149 | or text properties. But I have not yet found a robust and efficient way to | |
9150 | do this in large files. | |
9151 | ||
9152 | @item | |
9153 | @emph{Hiding leading stars}@* You can modify the display in such a way that | |
9154 | all leading stars become invisible. To do this in a global way, configure | |
9155 | the variable @code{org-hide-leading-stars} or change this on a per-file basis | |
9156 | with | |
4009494e GM |
9157 | |
9158 | @example | |
4009494e GM |
9159 | #+STARTUP: hidestars |
9160 | @end example | |
9161 | ||
864c9740 CD |
9162 | @noindent |
9163 | Note that the opposite behavior is selected with @code{showstars}. | |
9164 | ||
b349f79f | 9165 | With hidden stars, the tree becomes: |
4009494e GM |
9166 | |
9167 | @example | |
b349f79f | 9168 | @group |
4009494e GM |
9169 | * Top level headline |
9170 | * Second level | |
9171 | * 3rd level | |
b349f79f CD |
9172 | ... |
9173 | @end group | |
4009494e GM |
9174 | @end example |
9175 | ||
9176 | @noindent | |
9177 | Note that the leading stars are not truly replaced by whitespace, they | |
9178 | are only fontified with the face @code{org-hide} that uses the | |
9179 | background color as font color. If you are not using either white or | |
9180 | black background, you may have to customize this face to get the wanted | |
9181 | effect. Another possibility is to set this font such that the extra | |
9182 | stars are @i{almost} invisible, for example using the color | |
9183 | @code{grey90} on a white background. | |
9184 | ||
b349f79f CD |
9185 | @item |
9186 | Things become cleaner still if you skip all the even levels and use only odd | |
9187 | levels 1, 3, 5..., effectively adding two stars to go from one outline level | |
9188 | to the next. In this way we get the outline view shown at the beginning of | |
9189 | this section. In order to make the structure editing and export commands | |
9190 | handle this convention correctly, configure the variable | |
9191 | @code{org-odd-levels-only}, or set this on a per-file basis with one of the | |
9192 | following lines: | |
4009494e GM |
9193 | |
9194 | @example | |
9195 | #+STARTUP: odd | |
9196 | #+STARTUP: oddeven | |
9197 | @end example | |
9198 | ||
a7808fba | 9199 | You can convert an Org file from single-star-per-level to the |
4009494e GM |
9200 | double-star-per-level convention with @kbd{M-x org-convert-to-odd-levels |
9201 | RET} in that file. The reverse operation is @kbd{M-x | |
9202 | org-convert-to-oddeven-levels}. | |
b349f79f | 9203 | @end enumerate |
4009494e GM |
9204 | |
9205 | @node TTY keys, Interaction, Clean view, Miscellaneous | |
a7808fba CD |
9206 | @section Using Org on a tty |
9207 | @cindex tty key bindings | |
4009494e | 9208 | |
a7808fba CD |
9209 | Because Org contains a large number of commands, by default much of |
9210 | Org's core commands are bound to keys that are generally not | |
dbc28aaa CD |
9211 | accessible on a tty, such as the cursor keys (@key{left}, @key{right}, |
9212 | @key{up}, @key{down}), @key{TAB} and @key{RET}, in particular when used | |
9213 | together with modifiers like @key{Meta} and/or @key{Shift}. To access | |
9214 | these commands on a tty when special keys are unavailable, the following | |
9215 | alternative bindings can be used. The tty bindings below will likely be | |
9216 | more cumbersome; you may find for some of the bindings below that a | |
9217 | customized work-around suits you better. For example, changing a time | |
9218 | stamp is really only fun with @kbd{S-@key{cursor}} keys, whereas on a | |
9219 | tty you would rather use @kbd{C-c .} to re-insert the timestamp. | |
4009494e GM |
9220 | |
9221 | @multitable @columnfractions 0.15 0.2 0.2 | |
9222 | @item @b{Default} @tab @b{Alternative 1} @tab @b{Alternative 2} | |
9223 | @item @kbd{S-@key{TAB}} @tab @kbd{C-u @key{TAB}} @tab | |
9224 | @item @kbd{M-@key{left}} @tab @kbd{C-c C-x l} @tab @kbd{@key{Esc} @key{left}} | |
9225 | @item @kbd{M-S-@key{left}} @tab @kbd{C-c C-x L} @tab | |
71d35b24 | 9226 | @item @kbd{M-@key{right}} @tab @kbd{C-c C-x i} @tab @kbd{@key{Esc} @key{right}} |
4009494e GM |
9227 | @item @kbd{M-S-@key{right}} @tab @kbd{C-c C-x R} @tab |
9228 | @item @kbd{M-@key{up}} @tab @kbd{C-c C-x u} @tab @kbd{@key{Esc} @key{up}} | |
9229 | @item @kbd{M-S-@key{up}} @tab @kbd{C-c C-x U} @tab | |
9230 | @item @kbd{M-@key{down}} @tab @kbd{C-c C-x d} @tab @kbd{@key{Esc} @key{down}} | |
9231 | @item @kbd{M-S-@key{down}} @tab @kbd{C-c C-x D} @tab | |
9232 | @item @kbd{S-@key{RET}} @tab @kbd{C-c C-x c} @tab | |
9233 | @item @kbd{M-@key{RET}} @tab @kbd{C-c C-x m} @tab @kbd{@key{Esc} @key{RET}} | |
9234 | @item @kbd{M-S-@key{RET}} @tab @kbd{C-c C-x M} @tab | |
9235 | @item @kbd{S-@key{left}} @tab @kbd{C-c @key{left}} @tab | |
9236 | @item @kbd{S-@key{right}} @tab @kbd{C-c @key{right}} @tab | |
9237 | @item @kbd{S-@key{up}} @tab @kbd{C-c @key{up}} @tab | |
9238 | @item @kbd{S-@key{down}} @tab @kbd{C-c @key{down}} @tab | |
9239 | @item @kbd{C-S-@key{left}} @tab @kbd{C-c C-x @key{left}} @tab | |
9240 | @item @kbd{C-S-@key{right}} @tab @kbd{C-c C-x @key{right}} @tab | |
9241 | @end multitable | |
9242 | ||
9243 | @node Interaction, Bugs, TTY keys, Miscellaneous | |
9244 | @section Interaction with other packages | |
9245 | @cindex packages, interaction with other | |
a7808fba | 9246 | Org lives in the world of GNU Emacs and interacts in various ways |
4009494e GM |
9247 | with other code out there. |
9248 | ||
9249 | @menu | |
a7808fba | 9250 | * Cooperation:: Packages Org cooperates with |
4009494e GM |
9251 | * Conflicts:: Packages that lead to conflicts |
9252 | @end menu | |
9253 | ||
9254 | @node Cooperation, Conflicts, Interaction, Interaction | |
a7808fba | 9255 | @subsection Packages that Org cooperates with |
4009494e GM |
9256 | |
9257 | @table @asis | |
9258 | @cindex @file{calc.el} | |
9259 | @item @file{calc.el} by Dave Gillespie | |
a7808fba CD |
9260 | Org uses the Calc package for implementing spreadsheet |
9261 | functionality in its tables (@pxref{The spreadsheet}). Org | |
9262 | checks for the availability of Calc by looking for the function | |
9263 | @code{calc-eval} which should be autoloaded in your setup if Calc has | |
9264 | been installed properly. As of Emacs 22, Calc is part of the Emacs | |
4009494e | 9265 | distribution. Another possibility for interaction between the two |
a7808fba CD |
9266 | packages is using Calc for embedded calculations. @xref{Embedded Mode, |
9267 | , Embedded Mode, Calc, GNU Emacs Calc Manual}. | |
4009494e GM |
9268 | @cindex @file{constants.el} |
9269 | @item @file{constants.el} by Carsten Dominik | |
9270 | In a table formula (@pxref{The spreadsheet}), it is possible to use | |
9271 | names for natural constants or units. Instead of defining your own | |
9272 | constants in the variable @code{org-table-formula-constants}, install | |
9273 | the @file{constants} package which defines a large number of constants | |
9274 | and units, and lets you use unit prefixes like @samp{M} for | |
9275 | @samp{Mega} etc. You will need version 2.0 of this package, available | |
a7808fba | 9276 | at @url{http://www.astro.uva.nl/~dominik/Tools}. Org checks for |
4009494e GM |
9277 | the function @code{constants-get}, which has to be autoloaded in your |
9278 | setup. See the installation instructions in the file | |
9279 | @file{constants.el}. | |
9280 | @item @file{cdlatex.el} by Carsten Dominik | |
9281 | @cindex @file{cdlatex.el} | |
a7808fba CD |
9282 | Org mode can make use of the CDLaTeX package to efficiently enter |
9283 | La@TeX{} fragments into Org files. See @ref{CDLaTeX mode}. | |
dbc28aaa CD |
9284 | @item @file{imenu.el} by Ake Stenhoff and Lars Lindberg |
9285 | @cindex @file{imenu.el} | |
a7808fba CD |
9286 | Imenu allows menu access to an index of items in a file. Org mode |
9287 | supports Imenu - all you need to do to get the index is the following: | |
dbc28aaa | 9288 | @lisp |
28a16a1b | 9289 | (add-hook 'org-mode-hook |
a7808fba | 9290 | (lambda () (imenu-add-to-menubar "Imenu"))) |
dbc28aaa CD |
9291 | @end lisp |
9292 | By default the index is two levels deep - you can modify the depth using | |
9293 | the option @code{org-imenu-depth}. | |
4009494e GM |
9294 | @item @file{remember.el} by John Wiegley |
9295 | @cindex @file{remember.el} | |
a7808fba | 9296 | Org cooperates with remember, see @ref{Remember}. |
4009494e | 9297 | @file{Remember.el} is not part of Emacs, find it on the web. |
dbc28aaa CD |
9298 | @item @file{speedbar.el} by Eric M. Ludlam |
9299 | @cindex @file{speedbar.el} | |
9300 | Speedbar is a package that creates a special frame displaying files and | |
a7808fba CD |
9301 | index items in files. Org mode supports Speedbar and allows you to |
9302 | drill into Org files directly from the Speedbar. It also allows to | |
dbc28aaa | 9303 | restrict the scope of agenda commands to a file or a subtree by using |
a7808fba | 9304 | the command @kbd{<} in the Speedbar frame. |
4009494e GM |
9305 | @cindex @file{table.el} |
9306 | @item @file{table.el} by Takaaki Ota | |
9307 | @kindex C-c C-c | |
9308 | @cindex table editor, @file{table.el} | |
9309 | @cindex @file{table.el} | |
9310 | ||
9311 | Complex ASCII tables with automatic line wrapping, column- and | |
9312 | row-spanning, and alignment can be created using the Emacs table | |
9313 | package by Takaaki Ota (@uref{http://sourceforge.net/projects/table}, | |
9314 | and also part of Emacs 22). | |
a7808fba | 9315 | When @key{TAB} or @kbd{C-c C-c} is pressed in such a table, Org mode |
4009494e | 9316 | will call @command{table-recognize-table} and move the cursor into the |
a7808fba CD |
9317 | table. Inside a table, the keymap of Org mode is inactive. In order |
9318 | to execute Org mode-related commands, leave the table. | |
4009494e GM |
9319 | |
9320 | @table @kbd | |
9321 | @kindex C-c C-c | |
9322 | @item C-c C-c | |
9323 | Recognize @file{table.el} table. Works when the cursor is in a | |
9324 | table.el table. | |
9325 | @c | |
9326 | @kindex C-c ~ | |
9327 | @item C-c ~ | |
9328 | Insert a table.el table. If there is already a table at point, this | |
a7808fba | 9329 | command converts it between the table.el format and the Org mode |
4009494e GM |
9330 | format. See the documentation string of the command |
9331 | @code{org-convert-table} for the restrictions under which this is | |
9332 | possible. | |
9333 | @end table | |
9334 | @file{table.el} is part of Emacs 22. | |
9335 | @cindex @file{footnote.el} | |
9336 | @item @file{footnote.el} by Steven L. Baur | |
55e0839d CD |
9337 | Org mode recognizes numerical footnotes as provided by this package. |
9338 | However, Org-mode also has its own footnote support (@pxref{Footnotes}), | |
9339 | which makes using @file{footnote.el} unnecessary. | |
4009494e GM |
9340 | @end table |
9341 | ||
9342 | @node Conflicts, , Cooperation, Interaction | |
a7808fba | 9343 | @subsection Packages that lead to conflicts with Org mode |
4009494e GM |
9344 | |
9345 | @table @asis | |
9346 | ||
3da3282e CD |
9347 | @cindex @code{shift-selection-mode} |
9348 | In Emacs 23, @code{shift-selection-mode} is on by default, meaning that | |
9349 | cursor motions combined with the shift key should start or enlarge regions. | |
9350 | This conflicts with the use of @kbd{S-@key{cursor}} commands in Org to change | |
9351 | timestamps, TODO keywords, priorities, and item bullet types if the cursor is | |
9352 | at such a location. By default, @kbd{S-@key{cursor}} commands outside | |
9353 | special contexts don't do anything, but you can customize the variable | |
9354 | @code{org-support-shift-select}. Org-mode then tries to accommodate shift | |
9355 | selection by (i) using it outside of the special contexts where special | |
9356 | commands apply, and by (ii) extending an existing active region even if the | |
9357 | cursor moves across a special context. | |
4009494e GM |
9358 | |
9359 | @cindex @file{CUA.el} | |
9360 | @item @file{CUA.el} by Kim. F. Storm | |
3da3282e CD |
9361 | Key bindings in Org conflict with the @kbd{S-<cursor>} keys used by CUA mode |
9362 | (as well as pc-select-mode and s-region-mode) to select and extend the | |
9363 | region. In fact, Emacs 23 has this built-in in the form of | |
9364 | @code{shift-selection-mode}, see previous paragraph. If you are using Emacs | |
9365 | 23 you probably don't want to use another package for this purpose. However, | |
9366 | if you prefer to leave these keys to a different package while working in | |
9367 | Org-mode, configure the variable @code{org-replace-disputed-keys}. When set, | |
9368 | Org will move the following key bindings in Org files, and in the agenda | |
9369 | buffer (but not during date selection). | |
4009494e GM |
9370 | |
9371 | @example | |
3da3282e CD |
9372 | S-UP -> M-p S-DOWN -> M-n |
9373 | S-LEFT -> M-- S-RIGHT -> M-+ | |
9374 | C-S-LEFT -> M-S-- C-S-RIGHT -> M-S-+ | |
4009494e GM |
9375 | @end example |
9376 | ||
9377 | Yes, these are unfortunately more difficult to remember. If you want | |
9378 | to have other replacement keys, look at the variable | |
9379 | @code{org-disputed-keys}. | |
3da3282e | 9380 | |
4009494e GM |
9381 | @item @file{windmove.el} by Hovav Shacham |
9382 | @cindex @file{windmove.el} | |
9383 | Also this package uses the @kbd{S-<cursor>} keys, so everything written | |
9384 | in the paragraph above about CUA mode also applies here. | |
9385 | ||
4009494e GM |
9386 | @end table |
9387 | ||
9388 | ||
9389 | @node Bugs, , Interaction, Miscellaneous | |
9390 | @section Bugs | |
9391 | @cindex bugs | |
9392 | ||
9393 | Here is a list of things that should work differently, but which I | |
9394 | have found too hard to fix. | |
9395 | ||
9396 | @itemize @bullet | |
9397 | @item | |
9398 | If a table field starts with a link, and if the corresponding table | |
9399 | column is narrowed (@pxref{Narrow columns}) to a width too small to | |
9400 | display the link, the field would look entirely empty even though it is | |
a7808fba | 9401 | not. To prevent this, Org throws an error. The work-around is to |
4009494e GM |
9402 | make the column wide enough to fit the link, or to add some text (at |
9403 | least 2 characters) before the link in the same field. | |
9404 | @item | |
9405 | Narrowing table columns does not work on XEmacs, because the | |
9406 | @code{format} function does not transport text properties. | |
9407 | @item | |
9408 | Text in an entry protected with the @samp{QUOTE} keyword should not | |
9409 | autowrap. | |
9410 | @item | |
9411 | When the application called by @kbd{C-c C-o} to open a file link fails | |
9412 | (for example because the application does not exist or refuses to open | |
9413 | the file), it does so silently. No error message is displayed. | |
9414 | @item | |
9415 | Recalculating a table line applies the formulas from left to right. | |
9416 | If a formula uses @emph{calculated} fields further down the row, | |
9417 | multiple recalculation may be needed to get all fields consistent. You | |
9418 | may use the command @code{org-table-iterate} (@kbd{C-u C-c *}) to | |
9419 | recalculate until convergence. | |
9420 | @item | |
4009494e GM |
9421 | The exporters work well, but could be made more efficient. |
9422 | @end itemize | |
9423 | ||
9424 | ||
b349f79f CD |
9425 | @node Extensions, Hacking, Miscellaneous, Top |
9426 | @appendix Extensions | |
9427 | ||
9428 | This appendix lists the extension modules that have been written for Org. | |
9429 | Many of these extensions live in the @file{contrib} directory of the Org | |
9430 | distribution, others are available somewhere on the web. | |
4009494e | 9431 | |
b349f79f CD |
9432 | @menu |
9433 | * Extensions in the contrib directory:: These come with the Org distro | |
9434 | * Other extensions:: These you have to find on the web. | |
9435 | @end menu | |
9436 | ||
9437 | @node Extensions in the contrib directory, Other extensions, Extensions, Extensions | |
9438 | @section Extensions in the @file{contrib} directory | |
9439 | ||
64fb801f CD |
9440 | A number of extension are distributed with Org when you download it from its |
9441 | homepage. Please note that these extensions are @emph{not} distributed as | |
9442 | part of Emacs, so if you use Org as delivered with Emacs, you still need to | |
9443 | go to @url{http://orgmode.org} to get access to these modules. | |
9444 | ||
b349f79f CD |
9445 | @table @asis |
9446 | @item @file{org-annotate-file.el} by @i{Philip Jackson} | |
55e0839d CD |
9447 | Annotate a file with org syntax, in a separate file, with links back to the |
9448 | annotated file. | |
9449 | ||
96c8522a | 9450 | @item @file{org-annotation-helper.el} by @i{Bastien Guerry and Daniel E. German} |
55e0839d CD |
9451 | Call @i{remember} directly from Firefox/Opera, or from Adobe Reader. When |
9452 | activating a special link or bookmark, Emacs receives a trigger to create a | |
9453 | note with a link back to the website. Requires some setup, a detailed | |
9454 | description is in @file{contrib/packages/org-annotation-helper}. | |
9455 | ||
b349f79f | 9456 | @item @file{org-bookmark.el} by @i{Tokuya Kameshima} |
55e0839d CD |
9457 | Support for links to Emacs bookmarks. |
9458 | ||
b349f79f | 9459 | @item @file{org-depend.el} by @i{Carsten Dominik} |
55e0839d CD |
9460 | TODO dependencies for Org-mode. Make TODO state changes in one entry trigger |
9461 | changes in another, or be blocked by the state of another entry. Also, | |
9462 | easily create chains of TODO items with exactly one active item at any time. | |
9463 | ||
b349f79f | 9464 | @item @file{org-elisp-symbol.el} by @i{Bastien Guerry} |
55e0839d CD |
9465 | Org links to emacs-lisp symbols. This can create annotated links that |
9466 | exactly point to the definition location of a variable of function. | |
9467 | ||
b349f79f | 9468 | @item @file{org-eval.el} by @i{Carsten Dominik} |
55e0839d CD |
9469 | The @code{<lisp>} tag, adapted from Emacs Wiki and Emacs Muse, allows text to |
9470 | be included in a document that is the result of evaluating some code. Other | |
9471 | scripting languages like @code{perl} can be supported with this package as | |
9472 | well. | |
9473 | ||
64fb801f | 9474 | @item @file{org-eval-light.el} by @i{Eric Schulte} |
55e0839d CD |
9475 | User-controlled evaluation of code in an Org buffer. |
9476 | ||
64fb801f | 9477 | @item @file{org-exp-blocks.el} by @i{Eric Schulte} |
55e0839d CD |
9478 | Preprocess user-defined blocks for export. |
9479 | ||
b349f79f | 9480 | @item @file{org-expiry.el} by @i{Bastien Guerry} |
55e0839d CD |
9481 | Expiry mechanism for Org entries. |
9482 | ||
b349f79f | 9483 | @item @file{org-indent.el} by @i{Carsten Dominik} |
55e0839d CD |
9484 | Dynamic indentation of Org outlines. The plan is to indent an outline |
9485 | according to level, but so far this is too hard for a proper and stable | |
9486 | implementation. Still, it works somewhat. | |
9487 | ||
b349f79f | 9488 | @item @file{org-interactive-query.el} by @i{Christopher League} |
55e0839d | 9489 | Interactive modification of tags queries. After running a general query in |
3da3282e CD |
9490 | Org, this package allows you to narrow down the results by adding more tags |
9491 | or keywords. | |
55e0839d | 9492 | |
b349f79f | 9493 | @item @file{org-mairix.el} by @i{Georg C. F. Greve} |
55e0839d CD |
9494 | Hook mairix search into Org for different MUAs. |
9495 | ||
b349f79f | 9496 | @item @file{org-man.el} by @i{Carsten Dominik} |
55e0839d CD |
9497 | Support for links to manpages in Org-mode. |
9498 | ||
b349f79f | 9499 | @item @file{org-mtags.el} by @i{Carsten Dominik} |
55e0839d CD |
9500 | Support for some Muse-like tags in Org-mode. This package allows you to |
9501 | write @code{<example>} and @code{<src>} and other syntax copied from Emacs | |
9502 | Muse, right inside an Org file. The goal here is to make it easy to publish | |
9503 | the same file using either org-publish or Muse. | |
9504 | ||
a50253cc | 9505 | @item @file{org-panel.el} by @i{Lennart Borgman} |
55e0839d CD |
9506 | Simplified and display-aided access to some Org commands. |
9507 | ||
b349f79f | 9508 | @item @file{org-registry.el} by @i{Bastien Guerry} |
55e0839d CD |
9509 | A registry for Org links, to find out from where links point to a given file |
9510 | or location. | |
9511 | ||
b349f79f | 9512 | @item @file{org2rem.el} by @i{Bastien Guerry} |
55e0839d CD |
9513 | Convert org appointments into reminders for the @file{remind} program. |
9514 | ||
b349f79f | 9515 | @item @file{org-screen.el} by @i{Andrew Hyatt} |
55e0839d CD |
9516 | Visit screen sessions through Org-mode links. |
9517 | ||
b349f79f | 9518 | @item @file{org-toc.el} by @i{Bastien Guerry} |
55e0839d CD |
9519 | Table of contents in a separate buffer, with fast access to sections and easy |
9520 | visibility cycling. | |
9521 | ||
b349f79f | 9522 | @item @file{orgtbl-sqlinsert.el} by @i{Jason Riedy} |
55e0839d CD |
9523 | Convert Org-mode tables to SQL insertions. Documentation for this can be |
9524 | found on the Worg pages. | |
9525 | ||
b349f79f CD |
9526 | @end table |
9527 | ||
b349f79f CD |
9528 | @node Other extensions, , Extensions in the contrib directory, Extensions |
9529 | @section Other extensions | |
9530 | ||
9531 | @i{TO BE DONE} | |
9532 | ||
9533 | @node Hacking, History and Acknowledgments, Extensions, Top | |
9534 | @appendix Hacking | |
9535 | ||
9536 | This appendix covers some aspects where users can extend the functionality of | |
a7808fba | 9537 | Org. |
4009494e GM |
9538 | |
9539 | @menu | |
4009494e GM |
9540 | * Adding hyperlink types:: New custom link types |
9541 | * Tables in arbitrary syntax:: Orgtbl for LaTeX and other programs | |
9542 | * Dynamic blocks:: Automatically filled blocks | |
9543 | * Special agenda views:: Customized views | |
9544 | * Using the property API:: Writing programs that use entry properties | |
b349f79f | 9545 | * Using the mapping API:: Mapping over all or selected entries |
4009494e GM |
9546 | @end menu |
9547 | ||
b349f79f | 9548 | @node Adding hyperlink types, Tables in arbitrary syntax, Hacking, Hacking |
4009494e GM |
9549 | @section Adding hyperlink types |
9550 | @cindex hyperlinks, adding new types | |
9551 | ||
a7808fba | 9552 | Org has a large number of hyperlink types built-in |
4009494e | 9553 | (@pxref{Hyperlinks}). If you would like to add new link types, it |
864c9740 | 9554 | provides an interface for doing so. Let's look at an example file |
4009494e | 9555 | @file{org-man.el} that will add support for creating links like |
a7808fba | 9556 | @samp{[[man:printf][The printf manpage]]} to show Unix manual pages inside |
4009494e GM |
9557 | emacs: |
9558 | ||
9559 | @lisp | |
a7808fba | 9560 | ;;; org-man.el - Support for links to manpages in Org |
4009494e GM |
9561 | |
9562 | (require 'org) | |
9563 | ||
9564 | (org-add-link-type "man" 'org-man-open) | |
9565 | (add-hook 'org-store-link-functions 'org-man-store-link) | |
9566 | ||
9567 | (defcustom org-man-command 'man | |
9568 | "The Emacs command to be used to display a man page." | |
9569 | :group 'org-link | |
9570 | :type '(choice (const man) (const woman))) | |
9571 | ||
9572 | (defun org-man-open (path) | |
9573 | "Visit the manpage on PATH. | |
9574 | PATH should be a topic that can be thrown at the man command." | |
9575 | (funcall org-man-command path)) | |
9576 | ||
9577 | (defun org-man-store-link () | |
9578 | "Store a link to a manpage." | |
9579 | (when (memq major-mode '(Man-mode woman-mode)) | |
9580 | ;; This is a man page, we do make this link | |
9581 | (let* ((page (org-man-get-page-name)) | |
9582 | (link (concat "man:" page)) | |
9583 | (description (format "Manpage for %s" page))) | |
9584 | (org-store-link-props | |
9585 | :type "man" | |
9586 | :link link | |
9587 | :description description)))) | |
9588 | ||
9589 | (defun org-man-get-page-name () | |
9590 | "Extract the page name from the buffer name." | |
9591 | ;; This works for both `Man-mode' and `woman-mode'. | |
9592 | (if (string-match " \\(\\S-+\\)\\*" (buffer-name)) | |
9593 | (match-string 1 (buffer-name)) | |
9594 | (error "Cannot create link to this man page"))) | |
9595 | ||
9596 | (provide 'org-man) | |
9597 | ||
9598 | ;;; org-man.el ends here | |
9599 | @end lisp | |
9600 | ||
9601 | @noindent | |
9602 | You would activate this new link type in @file{.emacs} with | |
9603 | ||
9604 | @lisp | |
9605 | (require 'org-man) | |
9606 | @end lisp | |
9607 | ||
9608 | @noindent | |
864c9740 | 9609 | Let's go through the file and see what it does. |
4009494e | 9610 | @enumerate |
28a16a1b | 9611 | @item |
4009494e GM |
9612 | It does @code{(require 'org)} to make sure that @file{org.el} has been |
9613 | loaded. | |
9614 | @item | |
9615 | The next line calls @code{org-add-link-type} to define a new link type | |
9616 | with prefix @samp{man}. The call also contains the name of a function | |
9617 | that will be called to follow such a link. | |
9618 | @item | |
9619 | The next line adds a function to @code{org-store-link-functions}, in | |
9620 | order to allow the command @kbd{C-c l} to record a useful link in a | |
9621 | buffer displaying a man page. | |
9622 | @end enumerate | |
9623 | ||
9624 | The rest of the file defines the necessary variables and functions. | |
9625 | First there is a customization variable that determines which emacs | |
a7808fba | 9626 | command should be used to display man pages. There are two options, |
4009494e GM |
9627 | @code{man} and @code{woman}. Then the function to follow a link is |
9628 | defined. It gets the link path as an argument - in this case the link | |
9629 | path is just a topic for the manual command. The function calls the | |
9630 | value of @code{org-man-command} to display the man page. | |
9631 | ||
9632 | Finally the function @code{org-man-store-link} is defined. When you try | |
9633 | to store a link with @kbd{C-c l}, also this function will be called to | |
9634 | try to make a link. The function must first decide if it is supposed to | |
9635 | create the link for this buffer type, we do this by checking the value | |
9636 | of the variable @code{major-mode}. If not, the function must exit and | |
a7808fba CD |
9637 | return the value @code{nil}. If yes, the link is created by getting the |
9638 | manual topic from the buffer name and prefixing it with the string | |
4009494e GM |
9639 | @samp{man:}. Then it must call the command @code{org-store-link-props} |
9640 | and set the @code{:type} and @code{:link} properties. Optionally you | |
9641 | can also set the @code{:description} property to provide a default for | |
a7808fba | 9642 | the link description when the link is later inserted into an Org |
4009494e GM |
9643 | buffer with @kbd{C-c C-l}. |
9644 | ||
b349f79f | 9645 | @node Tables in arbitrary syntax, Dynamic blocks, Adding hyperlink types, Hacking |
a7808fba | 9646 | @section Tables and lists in arbitrary syntax |
4009494e | 9647 | @cindex tables, in other modes |
dbc28aaa | 9648 | @cindex lists, in other modes |
a7808fba | 9649 | @cindex Orgtbl mode |
4009494e | 9650 | |
a7808fba | 9651 | Since Orgtbl mode can be used as a minor mode in arbitrary buffers, a |
4009494e | 9652 | frequent feature request has been to make it work with native tables in |
dbc28aaa CD |
9653 | specific languages, for example La@TeX{}. However, this is extremely |
9654 | hard to do in a general way, would lead to a customization nightmare, | |
a7808fba | 9655 | and would take away much of the simplicity of the Orgtbl mode table |
dbc28aaa CD |
9656 | editor. |
9657 | ||
4009494e | 9658 | |
a7808fba | 9659 | This appendix describes a different approach. We keep the Orgtbl mode |
4009494e GM |
9660 | table in its native format (the @i{source table}), and use a custom |
9661 | function to @i{translate} the table to the correct syntax, and to | |
9662 | @i{install} it in the right location (the @i{target table}). This puts | |
9663 | the burden of writing conversion functions on the user, but it allows | |
9664 | for a very flexible system. | |
9665 | ||
dbc28aaa CD |
9666 | Bastien added the ability to do the same with lists. You can use Org's |
9667 | facilities to edit and structure lists by turning @code{orgstruct-mode} | |
9668 | on, then locally exporting such lists in another format (HTML, La@TeX{} | |
a7808fba | 9669 | or Texinfo.) |
dbc28aaa CD |
9670 | |
9671 | ||
4009494e GM |
9672 | @menu |
9673 | * Radio tables:: Sending and receiving | |
9674 | * A LaTeX example:: Step by step, almost a tutorial | |
9675 | * Translator functions:: Copy and modify | |
a7808fba | 9676 | * Radio lists:: Doing the same for lists |
4009494e GM |
9677 | @end menu |
9678 | ||
9679 | @node Radio tables, A LaTeX example, Tables in arbitrary syntax, Tables in arbitrary syntax | |
9680 | @subsection Radio tables | |
9681 | @cindex radio tables | |
9682 | ||
9683 | To define the location of the target table, you first need to create two | |
9684 | lines that are comments in the current mode, but contain magic words for | |
a7808fba | 9685 | Orgtbl mode to find. Orgtbl mode will insert the translated table |
4009494e GM |
9686 | between these lines, replacing whatever was there before. For example: |
9687 | ||
9688 | @example | |
9689 | /* BEGIN RECEIVE ORGTBL table_name */ | |
9690 | /* END RECEIVE ORGTBL table_name */ | |
9691 | @end example | |
9692 | ||
9693 | @noindent | |
9694 | Just above the source table, we put a special line that tells | |
a7808fba | 9695 | Orgtbl mode how to translate this table and where to install it. For |
4009494e GM |
9696 | example: |
9697 | @example | |
9698 | #+ORGTBL: SEND table_name translation_function arguments.... | |
9699 | @end example | |
9700 | ||
9701 | @noindent | |
9702 | @code{table_name} is the reference name for the table that is also used | |
9703 | in the receiver lines. @code{translation_function} is the Lisp function | |
9704 | that does the translation. Furthermore, the line can contain a list of | |
9705 | arguments (alternating key and value) at the end. The arguments will be | |
9706 | passed as a property list to the translation function for | |
9707 | interpretation. A few standard parameters are already recognized and | |
9708 | acted upon before the translation function is called: | |
9709 | ||
9710 | @table @code | |
9711 | @item :skip N | |
b349f79f CD |
9712 | Skip the first N lines of the table. Hlines do count as separate lines for |
9713 | this parameter! | |
9714 | ||
4009494e GM |
9715 | @item :skipcols (n1 n2 ...) |
9716 | List of columns that should be skipped. If the table has a column with | |
9717 | calculation marks, that column is automatically discarded as well. | |
9718 | Please note that the translator function sees the table @emph{after} the | |
9719 | removal of these columns, the function never knows that there have been | |
9720 | additional columns. | |
9721 | @end table | |
9722 | ||
9723 | @noindent | |
9724 | The one problem remaining is how to keep the source table in the buffer | |
9725 | without disturbing the normal workings of the file, for example during | |
9726 | compilation of a C file or processing of a La@TeX{} file. There are a | |
9727 | number of different solutions: | |
9728 | ||
9729 | @itemize @bullet | |
9730 | @item | |
9731 | The table could be placed in a block comment if that is supported by the | |
a7808fba | 9732 | language. For example, in C mode you could wrap the table between |
4009494e | 9733 | @samp{/*} and @samp{*/} lines. |
28a16a1b | 9734 | @item |
4009494e GM |
9735 | Sometimes it is possible to put the table after some kind of @i{END} |
9736 | statement, for example @samp{\bye} in TeX and @samp{\end@{document@}} | |
9737 | in La@TeX{}. | |
9738 | @item | |
9739 | You can just comment the table line by line whenever you want to process | |
9740 | the file, and uncomment it whenever you need to edit the table. This | |
9741 | only sounds tedious - the command @kbd{M-x orgtbl-toggle-comment} does | |
9742 | make this comment-toggling very easy, in particular if you bind it to a | |
9743 | key. | |
9744 | @end itemize | |
9745 | ||
9746 | @node A LaTeX example, Translator functions, Radio tables, Tables in arbitrary syntax | |
dbc28aaa | 9747 | @subsection A LaTeX example of radio tables |
a7808fba | 9748 | @cindex LaTeX, and Orgtbl mode |
4009494e GM |
9749 | |
9750 | The best way to wrap the source table in La@TeX{} is to use the | |
9751 | @code{comment} environment provided by @file{comment.sty}. It has to be | |
9752 | activated by placing @code{\usepackage@{comment@}} into the document | |
a7808fba CD |
9753 | header. Orgtbl mode can insert a radio table skeleton@footnote{By |
9754 | default this works only for La@TeX{}, HTML, and Texinfo. Configure the | |
4009494e GM |
9755 | variable @code{orgtbl-radio-tables} to install templates for other |
9756 | modes.} with the command @kbd{M-x orgtbl-insert-radio-table}. You will | |
55e0839d | 9757 | be prompted for a table name, let's say we use @samp{salesfigures}. You |
4009494e GM |
9758 | will then get the following template: |
9759 | ||
b349f79f | 9760 | @cindex #+ORGTBL: SEND |
4009494e GM |
9761 | @example |
9762 | % BEGIN RECEIVE ORGTBL salesfigures | |
9763 | % END RECEIVE ORGTBL salesfigures | |
9764 | \begin@{comment@} | |
9765 | #+ORGTBL: SEND salesfigures orgtbl-to-latex | |
9766 | | | | | |
9767 | \end@{comment@} | |
9768 | @end example | |
9769 | ||
9770 | @noindent | |
a7808fba | 9771 | The @code{#+ORGTBL: SEND} line tells Orgtbl mode to use the function |
4009494e GM |
9772 | @code{orgtbl-to-latex} to convert the table into La@TeX{} and to put it |
9773 | into the receiver location with name @code{salesfigures}. You may now | |
9774 | fill in the table, feel free to use the spreadsheet features@footnote{If | |
9775 | the @samp{#+TBLFM} line contains an odd number of dollar characters, | |
a7808fba | 9776 | this may cause problems with font-lock in LaTeX mode. As shown in the |
4009494e GM |
9777 | example you can fix this by adding an extra line inside the |
9778 | @code{comment} environment that is used to balance the dollar | |
9779 | expressions. If you are using AUCTeX with the font-latex library, a | |
9780 | much better solution is to add the @code{comment} environment to the | |
9781 | variable @code{LaTeX-verbatim-environments}.}: | |
9782 | ||
9783 | @example | |
9784 | % BEGIN RECEIVE ORGTBL salesfigures | |
9785 | % END RECEIVE ORGTBL salesfigures | |
9786 | \begin@{comment@} | |
9787 | #+ORGTBL: SEND salesfigures orgtbl-to-latex | |
9788 | | Month | Days | Nr sold | per day | | |
9789 | |-------+------+---------+---------| | |
9790 | | Jan | 23 | 55 | 2.4 | | |
9791 | | Feb | 21 | 16 | 0.8 | | |
9792 | | March | 22 | 278 | 12.6 | | |
9793 | #+TBLFM: $4=$3/$2;%.1f | |
9794 | % $ (optional extra dollar to keep font-lock happy, see footnote) | |
9795 | \end@{comment@} | |
9796 | @end example | |
9797 | ||
9798 | @noindent | |
9799 | When you are done, press @kbd{C-c C-c} in the table to get the converted | |
9800 | table inserted between the two marker lines. | |
9801 | ||
55e0839d | 9802 | Now let's assume you want to make the table header by hand, because you |
4009494e GM |
9803 | want to control how columns are aligned etc. In this case we make sure |
9804 | that the table translator does skip the first 2 lines of the source | |
9805 | table, and tell the command to work as a @i{splice}, i.e. to not produce | |
9806 | header and footer commands of the target table: | |
9807 | ||
9808 | @example | |
9809 | \begin@{tabular@}@{lrrr@} | |
9810 | Month & \multicolumn@{1@}@{c@}@{Days@} & Nr.\ sold & per day\\ | |
9811 | % BEGIN RECEIVE ORGTBL salesfigures | |
9812 | % END RECEIVE ORGTBL salesfigures | |
9813 | \end@{tabular@} | |
9814 | % | |
9815 | \begin@{comment@} | |
9816 | #+ORGTBL: SEND salesfigures orgtbl-to-latex :splice t :skip 2 | |
9817 | | Month | Days | Nr sold | per day | | |
9818 | |-------+------+---------+---------| | |
9819 | | Jan | 23 | 55 | 2.4 | | |
9820 | | Feb | 21 | 16 | 0.8 | | |
9821 | | March | 22 | 278 | 12.6 | | |
9822 | #+TBLFM: $4=$3/$2;%.1f | |
9823 | \end@{comment@} | |
9824 | @end example | |
9825 | ||
9826 | The La@TeX{} translator function @code{orgtbl-to-latex} is already part of | |
a7808fba | 9827 | Orgtbl mode. It uses a @code{tabular} environment to typeset the table |
4009494e | 9828 | and marks horizontal lines with @code{\hline}. Furthermore, it |
b349f79f | 9829 | interprets the following parameters (see also @ref{Translator functions}): |
4009494e GM |
9830 | |
9831 | @table @code | |
9832 | @item :splice nil/t | |
9833 | When set to t, return only table body lines, don't wrap them into a | |
9834 | tabular environment. Default is nil. | |
9835 | ||
9836 | @item :fmt fmt | |
9837 | A format to be used to wrap each field, should contain @code{%s} for the | |
9838 | original field value. For example, to wrap each field value in dollars, | |
9839 | you could use @code{:fmt "$%s$"}. This may also be a property list with | |
9840 | column numbers and formats. for example @code{:fmt (2 "$%s$" 4 "%s\\%%")}. | |
a7808fba CD |
9841 | A function of one argument can be used in place of the strings; the |
9842 | function must return a formatted string. | |
4009494e GM |
9843 | |
9844 | @item :efmt efmt | |
9845 | Use this format to print numbers with exponentials. The format should | |
9846 | have @code{%s} twice for inserting mantissa and exponent, for example | |
9847 | @code{"%s\\times10^@{%s@}"}. The default is @code{"%s\\,(%s)"}. This | |
9848 | may also be a property list with column numbers and formats, for example | |
9849 | @code{:efmt (2 "$%s\\times10^@{%s@}$" 4 "$%s\\cdot10^@{%s@}$")}. After | |
9850 | @code{efmt} has been applied to a value, @code{fmt} will also be | |
a7808fba CD |
9851 | applied. Similar to @code{fmt}, functions of two arguments can be |
9852 | supplied instead of strings. | |
4009494e GM |
9853 | @end table |
9854 | ||
dbc28aaa | 9855 | @node Translator functions, Radio lists, A LaTeX example, Tables in arbitrary syntax |
4009494e | 9856 | @subsection Translator functions |
a7808fba | 9857 | @cindex HTML, and Orgtbl mode |
4009494e GM |
9858 | @cindex translator function |
9859 | ||
b349f79f CD |
9860 | Orgtbl mode has several translator functions built-in: @code{orgtbl-to-csv} |
9861 | (comma-separated values), @code{orgtbl-to-tsv} (TAB-separated values) | |
9862 | @code{orgtbl-to-latex}, @code{orgtbl-to-html}, and @code{orgtbl-to-texinfo}. | |
9863 | Except for @code{orgtbl-to-html}@footnote{The HTML translator uses the same | |
9864 | code that produces tables during HTML export.}, these all use a generic | |
9865 | translator, @code{orgtbl-to-generic}. For example, @code{orgtbl-to-latex} | |
9866 | itself is a very short function that computes the column definitions for the | |
9867 | @code{tabular} environment, defines a few field and line separators and then | |
9868 | hands over to the generic translator. Here is the entire code: | |
4009494e GM |
9869 | |
9870 | @lisp | |
9871 | @group | |
9872 | (defun orgtbl-to-latex (table params) | |
a7808fba | 9873 | "Convert the Orgtbl mode TABLE to LaTeX." |
4009494e GM |
9874 | (let* ((alignment (mapconcat (lambda (x) (if x "r" "l")) |
9875 | org-table-last-alignment "")) | |
9876 | (params2 | |
9877 | (list | |
9878 | :tstart (concat "\\begin@{tabular@}@{" alignment "@}") | |
9879 | :tend "\\end@{tabular@}" | |
9880 | :lstart "" :lend " \\\\" :sep " & " | |
9881 | :efmt "%s\\,(%s)" :hline "\\hline"))) | |
9882 | (orgtbl-to-generic table (org-combine-plists params2 params)))) | |
9883 | @end group | |
9884 | @end lisp | |
9885 | ||
9886 | As you can see, the properties passed into the function (variable | |
9887 | @var{PARAMS}) are combined with the ones newly defined in the function | |
9888 | (variable @var{PARAMS2}). The ones passed into the function (i.e. the | |
9889 | ones set by the @samp{ORGTBL SEND} line) take precedence. So if you | |
9890 | would like to use the La@TeX{} translator, but wanted the line endings to | |
9891 | be @samp{\\[2mm]} instead of the default @samp{\\}, you could just | |
9892 | overrule the default with | |
9893 | ||
9894 | @example | |
9895 | #+ORGTBL: SEND test orgtbl-to-latex :lend " \\\\[2mm]" | |
9896 | @end example | |
9897 | ||
9898 | For a new language, you can either write your own converter function in | |
9899 | analogy with the La@TeX{} translator, or you can use the generic function | |
9900 | directly. For example, if you have a language where a table is started | |
9901 | with @samp{!BTBL!}, ended with @samp{!ETBL!}, and where table lines are | |
9902 | started with @samp{!BL!}, ended with @samp{!EL!} and where the field | |
9903 | separator is a TAB, you could call the generic translator like this (on | |
9904 | a single line!): | |
9905 | ||
9906 | @example | |
9907 | #+ORGTBL: SEND test orgtbl-to-generic :tstart "!BTBL!" :tend "!ETBL!" | |
9908 | :lstart "!BL! " :lend " !EL!" :sep "\t" | |
9909 | @end example | |
9910 | ||
9911 | @noindent | |
9912 | Please check the documentation string of the function | |
9913 | @code{orgtbl-to-generic} for a full list of parameters understood by | |
9914 | that function and remember that you can pass each of them into | |
9915 | @code{orgtbl-to-latex}, @code{orgtbl-to-texinfo}, and any other function | |
9916 | using the generic function. | |
9917 | ||
9918 | Of course you can also write a completely new function doing complicated | |
9919 | things the generic translator cannot do. A translator function takes | |
9920 | two arguments. The first argument is the table, a list of lines, each | |
9921 | line either the symbol @code{hline} or a list of fields. The second | |
9922 | argument is the property list containing all parameters specified in the | |
9923 | @samp{#+ORGTBL: SEND} line. The function must return a single string | |
9924 | containing the formatted table. If you write a generally useful | |
9925 | translator, please post it on @code{emacs-orgmode@@gnu.org} so that | |
9926 | others can benefit from your work. | |
9927 | ||
dbc28aaa CD |
9928 | @node Radio lists, , Translator functions, Tables in arbitrary syntax |
9929 | @subsection Radio lists | |
9930 | @cindex radio lists | |
9931 | @cindex org-list-insert-radio-list | |
9932 | ||
9933 | Sending and receiving radio lists works exactly the same way than | |
9934 | sending and receiving radio tables (@pxref{Radio tables}) @footnote{You | |
9935 | need to load the @code{org-export-latex.el} package to use radio lists | |
9936 | since the relevant code is there for now.}. As for radio tables, you | |
a7808fba | 9937 | can insert radio lists templates in HTML, La@TeX{} and Texinfo modes by |
dbc28aaa CD |
9938 | calling @code{org-list-insert-radio-list}. |
9939 | ||
9940 | Here are the differences with radio tables: | |
9941 | ||
9942 | @itemize @minus | |
9943 | @item | |
9944 | Use @code{ORGLST} instead of @code{ORGTBL}. | |
9945 | @item | |
9946 | The available translation functions for radio lists don't take | |
9947 | parameters. | |
28a16a1b | 9948 | @item |
dbc28aaa CD |
9949 | `C-c C-c' will work when pressed on the first item of the list. |
9950 | @end itemize | |
9951 | ||
9952 | Here is a La@TeX{} example. Let's say that you have this in your | |
9953 | La@TeX{} file: | |
9954 | ||
9955 | @example | |
9956 | % BEGIN RECEIVE ORGLST to-buy | |
9957 | % END RECEIVE ORGLST to-buy | |
9958 | \begin@{comment@} | |
9959 | #+ORGLIST: SEND to-buy orgtbl-to-latex | |
9960 | - a new house | |
9961 | - a new computer | |
9962 | + a new keyboard | |
9963 | + a new mouse | |
9964 | - a new life | |
9965 | \end@{comment@} | |
9966 | @end example | |
9967 | ||
9968 | Pressing `C-c C-c' on @code{a new house} and will insert the converted | |
9969 | La@TeX{} list between the two marker lines. | |
9970 | ||
b349f79f | 9971 | @node Dynamic blocks, Special agenda views, Tables in arbitrary syntax, Hacking |
4009494e GM |
9972 | @section Dynamic blocks |
9973 | @cindex dynamic blocks | |
9974 | ||
a7808fba | 9975 | Org documents can contain @emph{dynamic blocks}. These are |
4009494e GM |
9976 | specially marked regions that are updated by some user-written function. |
9977 | A good example for such a block is the clock table inserted by the | |
9978 | command @kbd{C-c C-x C-r} (@pxref{Clocking work time}). | |
9979 | ||
9980 | Dynamic block are enclosed by a BEGIN-END structure that assigns a name | |
9981 | to the block and can also specify parameters for the function producing | |
9982 | the content of the block. | |
9983 | ||
b349f79f | 9984 | #+BEGIN:dynamic block |
4009494e GM |
9985 | @example |
9986 | #+BEGIN: myblock :parameter1 value1 :parameter2 value2 ... | |
9987 | ||
9988 | #+END: | |
9989 | @end example | |
9990 | ||
9991 | Dynamic blocks are updated with the following commands | |
9992 | ||
9993 | @table @kbd | |
9994 | @kindex C-c C-x C-u | |
9995 | @item C-c C-x C-u | |
9996 | Update dynamic block at point. | |
9997 | @kindex C-u C-c C-x C-u | |
9998 | @item C-u C-c C-x C-u | |
9999 | Update all dynamic blocks in the current file. | |
10000 | @end table | |
10001 | ||
10002 | Updating a dynamic block means to remove all the text between BEGIN and | |
10003 | END, parse the BEGIN line for parameters and then call the specific | |
28a16a1b CD |
10004 | writer function for this block to insert the new content. If you want |
10005 | to use the original content in the writer function, you can use the | |
10006 | extra parameter @code{:content}. | |
10007 | ||
10008 | For a block with name @code{myblock}, the writer function is | |
4009494e GM |
10009 | @code{org-dblock-write:myblock} with as only parameter a property list |
10010 | with the parameters given in the begin line. Here is a trivial example | |
10011 | of a block that keeps track of when the block update function was last | |
10012 | run: | |
10013 | ||
10014 | @example | |
10015 | #+BEGIN: block-update-time :format "on %m/%d/%Y at %H:%M" | |
10016 | ||
10017 | #+END: | |
10018 | @end example | |
10019 | ||
10020 | @noindent | |
10021 | The corresponding block writer function could look like this: | |
10022 | ||
10023 | @lisp | |
10024 | (defun org-dblock-write:block-update-time (params) | |
10025 | (let ((fmt (or (plist-get params :format) "%d. %m. %Y"))) | |
10026 | (insert "Last block update at: " | |
10027 | (format-time-string fmt (current-time))))) | |
10028 | @end lisp | |
10029 | ||
10030 | If you want to make sure that all dynamic blocks are always up-to-date, | |
10031 | you could add the function @code{org-update-all-dblocks} to a hook, for | |
10032 | example @code{before-save-hook}. @code{org-update-all-dblocks} is | |
a7808fba CD |
10033 | written in a way that is does nothing in buffers that are not in |
10034 | @code{org-mode}. | |
4009494e | 10035 | |
b349f79f | 10036 | @node Special agenda views, Using the property API, Dynamic blocks, Hacking |
a7808fba | 10037 | @section Special agenda views |
4009494e GM |
10038 | @cindex agenda views, user-defined |
10039 | ||
a7808fba | 10040 | Org provides a special hook that can be used to narrow down the |
4009494e GM |
10041 | selection made by any of the agenda views. You may specify a function |
10042 | that is used at each match to verify if the match should indeed be part | |
10043 | of the agenda view, and if not, how much should be skipped. | |
10044 | ||
10045 | Let's say you want to produce a list of projects that contain a WAITING | |
10046 | tag anywhere in the project tree. Let's further assume that you have | |
a7808fba CD |
10047 | marked all tree headings that define a project with the TODO keyword |
10048 | PROJECT. In this case you would run a TODO search for the keyword | |
4009494e GM |
10049 | PROJECT, but skip the match unless there is a WAITING tag anywhere in |
10050 | the subtree belonging to the project line. | |
10051 | ||
10052 | To achieve this, you must write a function that searches the subtree for | |
10053 | the tag. If the tag is found, the function must return @code{nil} to | |
10054 | indicate that this match should not be skipped. If there is no such | |
10055 | tag, return the location of the end of the subtree, to indicate that | |
10056 | search should continue from there. | |
10057 | ||
10058 | @lisp | |
10059 | (defun my-skip-unless-waiting () | |
10060 | "Skip trees that are not waiting" | |
10061 | (let ((subtree-end (save-excursion (org-end-of-subtree t)))) | |
dbc28aaa | 10062 | (if (re-search-forward ":waiting:" subtree-end t) |
4009494e GM |
10063 | nil ; tag found, do not skip |
10064 | subtree-end))) ; tag not found, continue after end of subtree | |
10065 | @end lisp | |
10066 | ||
10067 | Now you may use this function in an agenda custom command, for example | |
10068 | like this: | |
10069 | ||
10070 | @lisp | |
10071 | (org-add-agenda-custom-command | |
10072 | '("b" todo "PROJECT" | |
e45e3595 | 10073 | ((org-agenda-skip-function 'my-skip-unless-waiting) |
4009494e GM |
10074 | (org-agenda-overriding-header "Projects waiting for something: ")))) |
10075 | @end lisp | |
10076 | ||
10077 | Note that this also binds @code{org-agenda-overriding-header} to get a | |
10078 | meaningful header in the agenda view. | |
10079 | ||
a7808fba CD |
10080 | A general way to create custom searches is to base them on a search for |
10081 | entries with a certain level limit. If you want to study all entries with | |
10082 | your custom search function, simply do a search for @samp{LEVEL>0}, and then | |
10083 | use @code{org-agenda-skip-function} to select the entries you really want to | |
10084 | have. | |
10085 | ||
4009494e GM |
10086 | You may also put a Lisp form into @code{org-agenda-skip-function}. In |
10087 | particular, you may use the functions @code{org-agenda-skip-entry-if} | |
10088 | and @code{org-agenda-skip-subtree-if} in this form, for example: | |
10089 | ||
10090 | @table @code | |
10091 | @item '(org-agenda-skip-entry-if 'scheduled) | |
10092 | Skip current entry if it has been scheduled. | |
10093 | @item '(org-agenda-skip-entry-if 'notscheduled) | |
10094 | Skip current entry if it has not been scheduled. | |
10095 | @item '(org-agenda-skip-entry-if 'deadline) | |
10096 | Skip current entry if it has a deadline. | |
10097 | @item '(org-agenda-skip-entry-if 'scheduled 'deadline) | |
10098 | Skip current entry if it has a deadline, or if it is scheduled. | |
10099 | @item '(org-agenda-skip-entry 'regexp "regular expression") | |
dbc28aaa CD |
10100 | Skip current entry if the regular expression matches in the entry. |
10101 | @item '(org-agenda-skip-entry 'notregexp "regular expression") | |
10102 | Skip current entry unless the regular expression matches. | |
4009494e GM |
10103 | @item '(org-agenda-skip-subtree-if 'regexp "regular expression") |
10104 | Same as above, but check and skip the entire subtree. | |
10105 | @end table | |
10106 | ||
10107 | Therefore we could also have written the search for WAITING projects | |
10108 | like this, even without defining a special function: | |
10109 | ||
10110 | @lisp | |
10111 | (org-add-agenda-custom-command | |
10112 | '("b" todo "PROJECT" | |
10113 | ((org-agenda-skip-function '(org-agenda-skip-subtree-if | |
dbc28aaa | 10114 | 'regexp ":waiting:")) |
4009494e GM |
10115 | (org-agenda-overriding-header "Projects waiting for something: ")))) |
10116 | @end lisp | |
10117 | ||
b349f79f | 10118 | @node Using the property API, Using the mapping API, Special agenda views, Hacking |
4009494e GM |
10119 | @section Using the property API |
10120 | @cindex API, for properties | |
10121 | @cindex properties, API | |
10122 | ||
10123 | Here is a description of the functions that can be used to work with | |
10124 | properties. | |
10125 | ||
10126 | @defun org-entry-properties &optional pom which | |
10127 | Get all properties of the entry at point-or-marker POM. | |
10128 | This includes the TODO keyword, the tags, time strings for deadline, | |
10129 | scheduled, and clocking, and any additional properties defined in the | |
10130 | entry. The return value is an alist, keys may occur multiple times | |
10131 | if the property key was used several times. | |
10132 | POM may also be nil, in which case the current entry is used. | |
10133 | If WHICH is nil or `all', get all properties. If WHICH is | |
10134 | `special' or `standard', only get that subclass. | |
10135 | @end defun | |
10136 | @defun org-entry-get pom property &optional inherit | |
a7808fba CD |
10137 | Get value of PROPERTY for entry at point-or-marker POM. By default, |
10138 | this only looks at properties defined locally in the entry. If INHERIT | |
10139 | is non-nil and the entry does not have the property, then also check | |
10140 | higher levels of the hierarchy. If INHERIT is the symbol | |
10141 | @code{selective}, use inheritance if and only if the setting of | |
10142 | @code{org-use-property-inheritance} selects PROPERTY for inheritance. | |
4009494e GM |
10143 | @end defun |
10144 | ||
10145 | @defun org-entry-delete pom property | |
10146 | Delete the property PROPERTY from entry at point-or-marker POM. | |
10147 | @end defun | |
10148 | ||
10149 | @defun org-entry-put pom property value | |
10150 | Set PROPERTY to VALUE for entry at point-or-marker POM. | |
10151 | @end defun | |
10152 | ||
10153 | @defun org-buffer-property-keys &optional include-specials | |
10154 | Get all property keys in the current buffer. | |
10155 | @end defun | |
10156 | ||
10157 | @defun org-insert-property-drawer | |
10158 | Insert a property drawer at point. | |
10159 | @end defun | |
10160 | ||
864c9740 CD |
10161 | @defun org-entry-put-multivalued-property pom property &rest values |
10162 | Set PROPERTY at point-or-marker POM to VALUES. VALUES should be a list of | |
10163 | strings. They will be concatenated, with spaces as separators. | |
10164 | @end defun | |
10165 | ||
10166 | @defun org-entry-get-multivalued-property pom property | |
10167 | Treat the value of the property PROPERTY as a whitespace-separated list of | |
10168 | values and return the values as a list of strings. | |
10169 | @end defun | |
10170 | ||
a7808fba CD |
10171 | @defun org-entry-add-to-multivalued-property pom property value |
10172 | Treat the value of the property PROPERTY as a whitespace-separated list of | |
10173 | values and make sure that VALUE is in this list. | |
10174 | @end defun | |
10175 | ||
10176 | @defun org-entry-remove-from-multivalued-property pom property value | |
10177 | Treat the value of the property PROPERTY as a whitespace-separated list of | |
10178 | values and make sure that VALUE is @emph{not} in this list. | |
10179 | @end defun | |
10180 | ||
10181 | @defun org-entry-member-in-multivalued-property pom property value | |
10182 | Treat the value of the property PROPERTY as a whitespace-separated list of | |
10183 | values and check if VALUE is in this list. | |
10184 | @end defun | |
10185 | ||
b349f79f CD |
10186 | @node Using the mapping API, , Using the property API, Hacking |
10187 | @section Using the mapping API | |
10188 | @cindex API, for mapping | |
10189 | @cindex mapping entries, API | |
10190 | ||
10191 | Org has sophisticated mapping capabilities to find all entries satisfying | |
10192 | certain criteria. Internally, this functionality is used to produce agenda | |
10193 | views, but there is also an API that can be used to execute arbitrary | |
10194 | functions for each or selected entries. The main entry point for this API | |
96c8522a | 10195 | is: |
b349f79f CD |
10196 | |
10197 | @defun org-map-entries func &optional match scope &rest skip | |
10198 | Call FUNC at each headline selected by MATCH in SCOPE. | |
10199 | ||
10200 | FUNC is a function or a lisp form. The function will be called without | |
10201 | arguments, with the cursor positioned at the beginning of the headline. | |
10202 | The return values of all calls to the function will be collected and | |
10203 | returned as a list. | |
10204 | ||
864c9740 | 10205 | MATCH is a tags/property/todo match as it is used in the agenda match view. |
b349f79f CD |
10206 | Only headlines that are matched by this query will be considered during |
10207 | the iteration. When MATCH is nil or t, all headlines will be | |
10208 | visited by the iteration. | |
10209 | ||
10210 | SCOPE determines the scope of this command. It can be any of: | |
10211 | ||
10212 | @example | |
10213 | nil @r{the current buffer, respecting the restriction if any} | |
10214 | tree @r{the subtree started with the entry at point} | |
10215 | file @r{the current buffer, without restriction} | |
10216 | file-with-archives | |
10217 | @r{the current buffer, and any archives associated with it} | |
10218 | agenda @r{all agenda files} | |
10219 | agenda-with-archives | |
10220 | @r{all agenda files with any archive files associated with them} | |
10221 | (file1 file2 ...) | |
10222 | @r{if this is a list, all files in the list will be scanned} | |
10223 | @end example | |
10224 | ||
10225 | The remaining args are treated as settings for the skipping facilities of | |
10226 | the scanner. The following items can be given here: | |
10227 | ||
10228 | @example | |
10229 | archive @r{skip trees with the archive tag} | |
10230 | comment @r{skip trees with the COMMENT keyword} | |
10231 | function or Lisp form | |
10232 | @r{will be used as value for @code{org-agenda-skip-function},} | |
867d4bb3 | 10233 | @r{so whenever the function returns t, FUNC} |
b349f79f CD |
10234 | @r{will not be called for that entry and search will} |
10235 | @r{continue from the point where the function leaves it} | |
10236 | @end example | |
10237 | @end defun | |
10238 | ||
10239 | The function given to that mapping routine can really do anything you like. | |
a50253cc GM |
10240 | It can use the property API (@pxref{Using the property API}) to gather more |
10241 | information about the entry, or in order to change metadata in the entry. | |
b349f79f | 10242 | Here are a couple of functions that might be handy: |
96c8522a | 10243 | |
b349f79f CD |
10244 | @defun org-todo &optional arg |
10245 | Change the TODO state of the entry, see the docstring of the functions for | |
10246 | the many possible values for the argument ARG. | |
10247 | @end defun | |
10248 | ||
10249 | @defun org-priority &optional action | |
10250 | Change the priority of the entry, see the docstring of this function for the | |
10251 | possible values for ACTION. | |
10252 | @end defun | |
10253 | ||
10254 | @defun org-toggle-tag tag &optional onoff | |
10255 | Toggle the tag TAG in the current entry. Setting ONOFF to either @code{on} | |
10256 | or @code{off} will not toggle tag, but ensure that it is either on or off. | |
10257 | @end defun | |
10258 | ||
10259 | @defun org-promote | |
10260 | Promote the current entry. | |
10261 | @end defun | |
10262 | ||
10263 | @defun org-demote | |
10264 | Demote the current entry. | |
10265 | @end defun | |
10266 | ||
10267 | Here is a simple example that will turn all entries in the current file with | |
10268 | a tag @code{TOMORROW} into TODO entries with the keyword @code{UPCOMING}. | |
10269 | Entries in comment trees and in archive trees will be ignored. | |
10270 | ||
10271 | @lisp | |
10272 | (org-map-entries | |
10273 | '(org-todo "UPCOMING") | |
10274 | "+TOMORROW" 'file 'archive 'comment) | |
10275 | @end lisp | |
10276 | ||
10277 | The following example counts the number of entries with TODO keyword | |
10278 | @code{WAITING}, in all agenda files. | |
10279 | ||
10280 | @lisp | |
96c8522a | 10281 | (length (org-map-entries t "/+WAITING" 'agenda)) |
b349f79f CD |
10282 | @end lisp |
10283 | ||
10284 | @node History and Acknowledgments, Main Index, Hacking, Top | |
4009494e GM |
10285 | @appendix History and Acknowledgments |
10286 | @cindex acknowledgments | |
10287 | @cindex history | |
10288 | @cindex thanks | |
10289 | ||
a7808fba CD |
10290 | Org was borne in 2003, out of frustration over the user interface |
10291 | of the Emacs Outline mode. I was trying to organize my notes and | |
4009494e GM |
10292 | projects, and using Emacs seemed to be the natural way to go. However, |
10293 | having to remember eleven different commands with two or three keys per | |
a7808fba | 10294 | command, only to hide and show parts of the outline tree, that seemed |
4009494e GM |
10295 | entirely unacceptable to me. Also, when using outlines to take notes, I |
10296 | constantly want to restructure the tree, organizing it parallel to my | |
10297 | thoughts and plans. @emph{Visibility cycling} and @emph{structure | |
10298 | editing} were originally implemented in the package | |
10299 | @file{outline-magic.el}, but quickly moved to the more general | |
10300 | @file{org.el}. As this environment became comfortable for project | |
10301 | planning, the next step was adding @emph{TODO entries}, basic @emph{time | |
10302 | stamps}, and @emph{table support}. These areas highlight the two main | |
a7808fba | 10303 | goals that Org still has today: To create a new, outline-based, |
4009494e GM |
10304 | plain text mode with innovative and intuitive editing features, and to |
10305 | incorporate project planning functionality directly into a notes file. | |
10306 | ||
a50253cc | 10307 | A special thanks goes to @i{Bastien Guerry} who has not only written a large |
a7808fba CD |
10308 | number of extensions to Org (most of them integrated into the core by now), |
10309 | but has also helped the development and maintenance of Org so much that he | |
7ddb1b5f | 10310 | should be considered the main co-contributor to this package. |
a7808fba | 10311 | |
4009494e GM |
10312 | Since the first release, literally thousands of emails to me or on |
10313 | @code{emacs-orgmode@@gnu.org} have provided a constant stream of bug | |
10314 | reports, feedback, new ideas, and sometimes patches and add-on code. | |
10315 | Many thanks to everyone who has helped to improve this package. I am | |
10316 | trying to keep here a list of the people who had significant influence | |
a7808fba | 10317 | in shaping one or more aspects of Org. The list may not be |
4009494e GM |
10318 | complete, if I have forgotten someone, please accept my apologies and |
10319 | let me know. | |
10320 | ||
10321 | @itemize @bullet | |
10322 | ||
10323 | @item | |
10324 | @i{Russel Adams} came up with the idea for drawers. | |
10325 | @item | |
a7808fba | 10326 | @i{Thomas Baumann} wrote @file{org-bbdb.el} and @file{org-mhe.el}. |
4009494e | 10327 | @item |
b349f79f CD |
10328 | @i{Christophe Bataillon} created the great unicorn logo that we use on the |
10329 | Org-mode website. | |
10330 | @item | |
4009494e GM |
10331 | @i{Alex Bochannek} provided a patch for rounding time stamps. |
10332 | @item | |
10333 | @i{Charles Cave}'s suggestion sparked the implementation of templates | |
10334 | for Remember. | |
10335 | @item | |
10336 | @i{Pavel Chalmoviansky} influenced the agenda treatment of items with | |
10337 | specified time. | |
10338 | @item | |
10339 | @i{Gregory Chernov} patched support for lisp forms into table | |
10340 | calculations and improved XEmacs compatibility, in particular by porting | |
10341 | @file{nouline.el} to XEmacs. | |
10342 | @item | |
10343 | @i{Sacha Chua} suggested to copy some linking code from Planner. | |
10344 | @item | |
5fbc0f11 | 10345 | @i{Eddward DeVilla} proposed and tested checkbox statistics. He also |
4009494e GM |
10346 | came up with the idea of properties, and that there should be an API for |
10347 | them. | |
10348 | @item | |
10349 | @i{Kees Dullemond} used to edit projects lists directly in HTML and so | |
10350 | inspired some of the early development, including HTML export. He also | |
10351 | asked for a way to narrow wide table columns. | |
10352 | @item | |
a7808fba | 10353 | @i{Christian Egli} converted the documentation into Texinfo format, |
4009494e GM |
10354 | patched CSS formatting into the HTML exporter, and inspired the agenda. |
10355 | @item | |
10356 | @i{David Emery} provided a patch for custom CSS support in exported | |
10357 | HTML agendas. | |
10358 | @item | |
10359 | @i{Nic Ferrier} contributed mailcap and XOXO support. | |
10360 | @item | |
28a16a1b CD |
10361 | @i{Miguel A. Figueroa-Villanueva} implemented hierarchical checkboxes. |
10362 | @item | |
4009494e GM |
10363 | @i{John Foerch} figured out how to make incremental search show context |
10364 | around a match in a hidden outline tree. | |
10365 | @item | |
dbc28aaa | 10366 | @i{Niels Giesen} had the idea to automatically archive DONE trees. |
4009494e | 10367 | @item |
a7808fba CD |
10368 | @i{Bastien Guerry} wrote the La@TeX{} exporter and @file{org-bibtex.el}, and |
10369 | has been prolific with patches, ideas, and bug reports. | |
4009494e GM |
10370 | @item |
10371 | @i{Kai Grossjohann} pointed out key-binding conflicts with other packages. | |
10372 | @item | |
a7808fba CD |
10373 | @i{Bernt Hansen} has driven much of the support for auto-repeating tasks, |
10374 | task state change logging, and the clocktable. His clear explanations have | |
10375 | been critical when we started to adopt the GIT version control system. | |
10376 | @item | |
864c9740 CD |
10377 | @i{Manuel Hermenegildo} has contributed various ideas, small fixed and |
10378 | patches. | |
10379 | @item | |
a7808fba CD |
10380 | @i{Phil Jackson} wrote @file{org-irc.el}. |
10381 | @item | |
4009494e GM |
10382 | @i{Scott Jaderholm} proposed footnotes, control over whitespace between |
10383 | folded entries, and column view for properties. | |
10384 | @item | |
a7808fba CD |
10385 | @i{Tokuya Kameshima} wrote @file{org-wl.el} and @file{org-mew.el}. |
10386 | @item | |
4009494e GM |
10387 | @i{Shidai Liu} ("Leo") asked for embedded La@TeX{} and tested it. He also |
10388 | provided frequent feedback and some patches. | |
10389 | @item | |
55e0839d CD |
10390 | @i{Matt Lundin} has proposed last-row references for table formulas and named |
10391 | invisible anchors. He has also worked a lot on the FAQ. | |
10392 | @item | |
4009494e GM |
10393 | @i{Jason F. McBrayer} suggested agenda export to CSV format. |
10394 | @item | |
dbc28aaa CD |
10395 | @i{Max Mikhanosha} came up with the idea of refiling. |
10396 | @item | |
4009494e GM |
10397 | @i{Dmitri Minaev} sent a patch to set priority limits on a per-file |
10398 | basis. | |
10399 | @item | |
10400 | @i{Stefan Monnier} provided a patch to keep the Emacs-Lisp compiler | |
10401 | happy. | |
10402 | @item | |
dbc28aaa CD |
10403 | @i{Rick Moynihan} proposed to allow multiple TODO sequences in a file |
10404 | and to be able to quickly restrict the agenda to a subtree. | |
4009494e GM |
10405 | @item |
10406 | @i{Todd Neal} provided patches for links to Info files and elisp forms. | |
10407 | @item | |
10408 | @i{Tim O'Callaghan} suggested in-file links, search options for general | |
10409 | file links, and TAGS. | |
10410 | @item | |
10411 | @i{Takeshi Okano} translated the manual and David O'Toole's tutorial | |
10412 | into Japanese. | |
10413 | @item | |
10414 | @i{Oliver Oppitz} suggested multi-state TODO items. | |
10415 | @item | |
10416 | @i{Scott Otterson} sparked the introduction of descriptive text for | |
10417 | links, among other things. | |
10418 | @item | |
10419 | @i{Pete Phillips} helped during the development of the TAGS feature, and | |
10420 | provided frequent feedback. | |
10421 | @item | |
10422 | @i{T.V. Raman} reported bugs and suggested improvements. | |
10423 | @item | |
10424 | @i{Matthias Rempe} (Oelde) provided ideas, Windows support, and quality | |
10425 | control. | |
10426 | @item | |
55e0839d CD |
10427 | @i{Paul Rivier} provided the basic implementation of named footnotes. |
10428 | @item | |
4009494e GM |
10429 | @i{Kevin Rogers} contributed code to access VM files on remote hosts. |
10430 | @item | |
a7808fba CD |
10431 | @i{Sebastian Rose} wrote @file{org-info.js}, a Java script for displaying |
10432 | webpages derived from Org using an Info-like, or a folding interface with | |
10433 | single key navigation. | |
10434 | @item | |
4009494e GM |
10435 | @i{Frank Ruell} solved the mystery of the @code{keymapp nil} bug, a |
10436 | conflict with @file{allout.el}. | |
10437 | @item | |
b349f79f CD |
10438 | @i{Jason Riedy} generalized the send-receive mechanism for orgtbl tables with |
10439 | extensive patches. | |
4009494e | 10440 | @item |
b349f79f CD |
10441 | @i{Philip Rooke} created the Org reference card, provided lots |
10442 | of feedback, developed and applied standards to the Org documentation. | |
4009494e GM |
10443 | @item |
10444 | @i{Christian Schlauer} proposed angular brackets around links, among | |
10445 | other things. | |
10446 | @item | |
864c9740 CD |
10447 | @i{Eric Schulte} wrote @file{org-plot.el}. |
10448 | @item | |
b349f79f | 10449 | Linking to VM/BBDB/Gnus was first inspired by @i{Tom Shannon}'s |
4009494e GM |
10450 | @file{organizer-mode.el}. |
10451 | @item | |
55e0839d CD |
10452 | @i{Ilya Shlyakhter} proposed the Archive Sibling, line numbering in literal |
10453 | examples, and remote highlighting for referenced code lines. | |
a7808fba | 10454 | @item |
64fb801f CD |
10455 | @i{Stathis Sideris} wrote the @file{ditaa.jar} ASCII to PNG converter that is |
10456 | now packaged into Org's @file{contrib} directory. | |
10457 | @item | |
4009494e GM |
10458 | @i{Daniel Sinder} came up with the idea of internal archiving by locking |
10459 | subtrees. | |
10460 | @item | |
10461 | @i{Dale Smith} proposed link abbreviations. | |
10462 | @item | |
864c9740 CD |
10463 | @i{James TD Smith} has contributed a large number of patches for useful |
10464 | tweaks and features. | |
10465 | @item | |
b349f79f CD |
10466 | @i{Adam Spiers} asked for global linking commands, inspired the link |
10467 | extension system, added support for mairix, and proposed the mapping API. | |
4009494e | 10468 | @item |
96c8522a CD |
10469 | @i{Andy Stewart} contributed code to @file{org-w3m.el}, to copy HTML content |
10470 | with links transformation to Org syntax. | |
10471 | @item | |
4009494e GM |
10472 | @i{David O'Toole} wrote @file{org-publish.el} and drafted the manual |
10473 | chapter about publishing. | |
10474 | @item | |
10475 | @i{J@"urgen Vollmer} contributed code generating the table of contents | |
10476 | in HTML output. | |
10477 | @item | |
10478 | @i{Chris Wallace} provided a patch implementing the @samp{QUOTE} | |
10479 | keyword. | |
10480 | @item | |
10481 | @i{David Wainberg} suggested archiving, and improvements to the linking | |
10482 | system. | |
10483 | @item | |
b349f79f | 10484 | @i{John Wiegley} wrote @file{emacs-wiki.el}, @file{planner.el}, and |
7ddb1b5f CD |
10485 | @file{muse.el}, which have some overlap with Org. Initially the development |
10486 | of Org was fully independent because I was not aware of the existence of | |
10487 | these packages. But with time I have occasionally looked at John's code and | |
10488 | learned a lot from it. John has also contributed a number of great ideas and | |
10489 | patches directly to Org, including the attachment system | |
10490 | (@file{org-attach.el}), integration with Apple Mail | |
10491 | (@file{org-mac-message.el}), and hierarchical dependencies of TODO items. | |
4009494e GM |
10492 | @item |
10493 | @i{Carsten Wimmer} suggested some changes and helped fix a bug in | |
a7808fba | 10494 | linking to Gnus. |
4009494e | 10495 | @item |
a7808fba | 10496 | @i{Roland Winkler} requested additional key bindings to make Org |
4009494e GM |
10497 | work on a tty. |
10498 | @item | |
10499 | @i{Piotr Zielinski} wrote @file{org-mouse.el}, proposed agenda blocks | |
10500 | and contributed various ideas and code snippets. | |
10501 | @end itemize | |
10502 | ||
10503 | ||
dbc28aaa CD |
10504 | @node Main Index, Key Index, History and Acknowledgments, Top |
10505 | @unnumbered The Main Index | |
4009494e GM |
10506 | |
10507 | @printindex cp | |
10508 | ||
dbc28aaa | 10509 | @node Key Index, , Main Index, Top |
4009494e GM |
10510 | @unnumbered Key Index |
10511 | ||
10512 | @printindex ky | |
10513 | ||
10514 | @bye | |
10515 | ||
10516 | @ignore | |
a7808fba | 10517 | arch-tag: 7893d1Fe-cc57-4d13-b5e5-f494a1CBC7ac |
4009494e | 10518 | @end ignore |
a7808fba CD |
10519 | |
10520 | @c Local variables: | |
10521 | @c ispell-local-dictionary: "en_US-w_accents" | |
10522 | @c ispell-local-pdict: "./.aspell.org.pws" | |
10523 | @c fill-column: 77 | |
10524 | @c End: | |
44ce9197 | 10525 |