Commit | Line | Data |
---|---|---|
86fbb8ca | 1 | |
4009494e GM |
2 | \input texinfo |
3 | @c %**start of header | |
311f0356 | 4 | @setfilename ../../info/org |
a7808fba | 5 | @settitle The Org Manual |
4009494e | 6 | |
801a68c8 BG |
7 | @set VERSION 7.8.09 |
8 | @set DATE April 2012 | |
86fbb8ca CD |
9 | |
10 | @c Use proper quote and backtick for code sections in PDF output | |
11 | @c Cf. Texinfo manual 14.2 | |
12 | @set txicodequoteundirected | |
13 | @set txicodequotebacktick | |
4009494e | 14 | |
4009494e | 15 | @c Version and Contact Info |
dbc28aaa | 16 | @set MAINTAINERSITE @uref{http://orgmode.org,maintainers webpage} |
4009494e GM |
17 | @set AUTHOR Carsten Dominik |
18 | @set MAINTAINER Carsten Dominik | |
dbc28aaa CD |
19 | @set MAINTAINEREMAIL @email{carsten at orgmode dot org} |
20 | @set MAINTAINERCONTACT @uref{mailto:carsten at orgmode dot org,contact the maintainer} | |
4009494e GM |
21 | @c %**end of header |
22 | @finalout | |
23 | ||
acedf35c CD |
24 | |
25 | @c ----------------------------------------------------------------------------- | |
26 | ||
27 | @c Macro definitions for commands and keys | |
28 | @c ======================================= | |
29 | ||
30 | @c The behavior of the key/command macros will depend on the flag cmdnames | |
31 | @c When set, commands names are shown. When clear, they are not shown. | |
32 | ||
33 | @set cmdnames | |
34 | ||
35 | @c Below we define the following macros for Org key tables: | |
36 | ||
ce57c2fe | 37 | @c orgkey{key} A key item |
acedf35c | 38 | @c orgcmd{key,cmd} Key with command name |
27e428e7 | 39 | @c xorgcmd{key,cmd} Key with command name as @itemx |
acedf35c CD |
40 | @c orgcmdnki{key,cmd} Like orgcmd, but do not index the key |
41 | @c orgcmdtkc{text,key,cmd} Like orgcmd,special text instead of key | |
42 | @c orgcmdkkc{key1,key2,cmd} Two keys with one command name, use "or" | |
43 | @c orgcmdkxkc{key1,key2,cmd} Two keys with one command name, but | |
44 | @c different functions, so format as @itemx | |
45 | @c orgcmdkskc{key1,key2,cmd} Same as orgcmdkkc, but use "or short" | |
46 | @c xorgcmdkskc{key1,key2,cmd} Same as previous, but use @itemx | |
47 | @c orgcmdkkcc{key1,key2,cmd1,cmd2} Two keys and two commands | |
48 | ||
49 | @c a key but no command | |
50 | @c Inserts: @item key | |
51 | @macro orgkey{key} | |
52 | @kindex \key\ | |
53 | @item @kbd{\key\} | |
54 | @end macro | |
55 | ||
56 | @macro xorgkey{key} | |
57 | @kindex \key\ | |
58 | @itemx @kbd{\key\} | |
59 | @end macro | |
60 | ||
61 | @c one key with a command | |
62 | @c Inserts: @item KEY COMMAND | |
afe98dfa | 63 | @macro orgcmd{key,command} |
acedf35c | 64 | @ifset cmdnames |
afe98dfa CD |
65 | @kindex \key\ |
66 | @findex \command\ | |
acedf35c | 67 | @iftex |
afe98dfa CD |
68 | @item @kbd{\key\} @hskip 0pt plus 1filll @code{\command\} |
69 | @end iftex | |
70 | @ifnottex | |
acedf35c CD |
71 | @item @kbd{\key\} @tie{}@tie{}@tie{}@tie{}(@code{\command\}) |
72 | @end ifnottex | |
73 | @end ifset | |
74 | @ifclear cmdnames | |
75 | @kindex \key\ | |
76 | @item @kbd{\key\} | |
77 | @end ifclear | |
78 | @end macro | |
79 | ||
80 | @c One key with one command, formatted using @itemx | |
81 | @c Inserts: @itemx KEY COMMAND | |
82 | @macro xorgcmd{key,command} | |
83 | @ifset cmdnames | |
84 | @kindex \key\ | |
85 | @findex \command\ | |
86 | @iftex | |
87 | @itemx @kbd{\key\} @hskip 0pt plus 1filll @code{\command\} | |
88 | @end iftex | |
89 | @ifnottex | |
90 | @itemx @kbd{\key\} @tie{}@tie{}@tie{}@tie{}(@code{\command\}) | |
91 | @end ifnottex | |
92 | @end ifset | |
93 | @ifclear cmdnames | |
afe98dfa | 94 | @kindex \key\ |
acedf35c CD |
95 | @itemx @kbd{\key\} |
96 | @end ifclear | |
97 | @end macro | |
98 | ||
99 | @c one key with a command, bit do not index the key | |
100 | @c Inserts: @item KEY COMMAND | |
101 | @macro orgcmdnki{key,command} | |
102 | @ifset cmdnames | |
afe98dfa | 103 | @findex \command\ |
acedf35c CD |
104 | @iftex |
105 | @item @kbd{\key\} @hskip 0pt plus 1filll @code{\command\} | |
106 | @end iftex | |
107 | @ifnottex | |
afe98dfa CD |
108 | @item @kbd{\key\} @tie{}@tie{}@tie{}@tie{}(@code{\command\}) |
109 | @end ifnottex | |
acedf35c CD |
110 | @end ifset |
111 | @ifclear cmdnames | |
112 | @item @kbd{\key\} | |
113 | @end ifclear | |
afe98dfa CD |
114 | @end macro |
115 | ||
acedf35c CD |
116 | @c one key with a command, and special text to replace key in item |
117 | @c Inserts: @item TEXT COMMAND | |
118 | @macro orgcmdtkc{text,key,command} | |
119 | @ifset cmdnames | |
afe98dfa | 120 | @kindex \key\ |
acedf35c CD |
121 | @findex \command\ |
122 | @iftex | |
123 | @item @kbd{\text\} @hskip 0pt plus 1filll @code{\command\} | |
124 | @end iftex | |
125 | @ifnottex | |
126 | @item @kbd{\text\} @tie{}@tie{}@tie{}@tie{}(@code{\command\}) | |
127 | @end ifnottex | |
128 | @end ifset | |
129 | @ifclear cmdnames | |
130 | @kindex \key\ | |
131 | @item @kbd{\text\} | |
132 | @end ifclear | |
afe98dfa CD |
133 | @end macro |
134 | ||
acedf35c CD |
135 | @c two keys with one command |
136 | @c Inserts: @item KEY1 or KEY2 COMMAND | |
137 | @macro orgcmdkkc{key1,key2,command} | |
138 | @ifset cmdnames | |
139 | @kindex \key1\ | |
140 | @kindex \key2\ | |
141 | @findex \command\ | |
c8d0cf5c | 142 | @iftex |
acedf35c | 143 | @item @kbd{\key1\} @ @r{or} @ @kbd{\key2\} @hskip 0pt plus 1filll @code{\command\} |
c8d0cf5c | 144 | @end iftex |
acedf35c CD |
145 | @ifnottex |
146 | @item @kbd{\key1\} @ @r{or} @ @kbd{\key2\} @tie{}@tie{}@tie{}@tie{}(@code{\command\}) | |
147 | @end ifnottex | |
148 | @end ifset | |
149 | @ifclear cmdnames | |
150 | @kindex \key1\ | |
151 | @kindex \key2\ | |
152 | @item @kbd{\key1\} @ @r{or} @ @kbd{\key2\} | |
153 | @end ifclear | |
c8d0cf5c | 154 | @end macro |
acedf35c CD |
155 | |
156 | @c Two keys with one command name, but different functions, so format as | |
157 | @c @itemx | |
158 | @c Inserts: @item KEY1 | |
159 | @c @itemx KEY2 COMMAND | |
160 | @macro orgcmdkxkc{key1,key2,command} | |
161 | @ifset cmdnames | |
162 | @kindex \key1\ | |
163 | @kindex \key2\ | |
164 | @findex \command\ | |
165 | @iftex | |
166 | @item @kbd{\key1\} | |
167 | @itemx @kbd{\key2\} @hskip 0pt plus 1filll @code{\command\} | |
168 | @end iftex | |
169 | @ifnottex | |
170 | @item @kbd{\key1\} | |
171 | @itemx @kbd{\key2\} @tie{}@tie{}@tie{}@tie{}(@code{\command\}) | |
172 | @end ifnottex | |
173 | @end ifset | |
174 | @ifclear cmdnames | |
175 | @kindex \key1\ | |
176 | @kindex \key2\ | |
177 | @item @kbd{\key1\} | |
178 | @itemx @kbd{\key2\} | |
179 | @end ifclear | |
c8d0cf5c | 180 | @end macro |
acedf35c CD |
181 | |
182 | @c Same as previous, but use "or short" | |
183 | @c Inserts: @item KEY1 or short KEY2 COMMAND | |
184 | @macro orgcmdkskc{key1,key2,command} | |
185 | @ifset cmdnames | |
186 | @kindex \key1\ | |
187 | @kindex \key2\ | |
188 | @findex \command\ | |
189 | @iftex | |
190 | @item @kbd{\key1\} @ @r{or short} @ @kbd{\key2\} @hskip 0pt plus 1filll @code{\command\} | |
191 | @end iftex | |
192 | @ifnottex | |
193 | @item @kbd{\key1\} @ @r{or short} @ @kbd{\key2\} @tie{}@tie{}@tie{}@tie{}(@code{\command\}) | |
194 | @end ifnottex | |
195 | @end ifset | |
196 | @ifclear cmdnames | |
197 | @kindex \key1\ | |
198 | @kindex \key2\ | |
199 | @item @kbd{\key1\} @ @r{or short} @ @kbd{\key2\} | |
200 | @end ifclear | |
c8d0cf5c | 201 | @end macro |
acedf35c CD |
202 | |
203 | @c Same as previous, but use @itemx | |
204 | @c Inserts: @itemx KEY1 or short KEY2 COMMAND | |
205 | @macro xorgcmdkskc{key1,key2,command} | |
206 | @ifset cmdnames | |
207 | @kindex \key1\ | |
208 | @kindex \key2\ | |
209 | @findex \command\ | |
210 | @iftex | |
211 | @itemx @kbd{\key1\} @ @r{or short} @ @kbd{\key2\} @hskip 0pt plus 1filll @code{\command\} | |
212 | @end iftex | |
213 | @ifnottex | |
214 | @itemx @kbd{\key1\} @ @r{or short} @ @kbd{\key2\} @tie{}@tie{}@tie{}@tie{}(@code{\command\}) | |
215 | @end ifnottex | |
216 | @end ifset | |
217 | @ifclear cmdnames | |
218 | @kindex \key1\ | |
219 | @kindex \key2\ | |
220 | @itemx @kbd{\key1\} @ @r{or short} @ @kbd{\key2\} | |
221 | @end ifclear | |
c8d0cf5c | 222 | @end macro |
4009494e | 223 | |
acedf35c CD |
224 | @c two keys with two commands |
225 | @c Inserts: @item KEY1 COMMAND1 | |
226 | @c @itemx KEY2 COMMAND2 | |
227 | @macro orgcmdkkcc{key1,key2,command1,command2} | |
228 | @ifset cmdnames | |
229 | @kindex \key1\ | |
230 | @kindex \key2\ | |
231 | @findex \command1\ | |
232 | @findex \command2\ | |
233 | @iftex | |
234 | @item @kbd{\key1\} @hskip 0pt plus 1filll @code{\command1\} | |
235 | @itemx @kbd{\key2\} @hskip 0pt plus 1filll @code{\command2\} | |
236 | @end iftex | |
237 | @ifnottex | |
238 | @item @kbd{\key1\} @tie{}@tie{}@tie{}@tie{}(@code{\command1\}) | |
239 | @itemx @kbd{\key2\} @tie{}@tie{}@tie{}@tie{}(@code{\command2\}) | |
240 | @end ifnottex | |
241 | @end ifset | |
242 | @ifclear cmdnames | |
243 | @kindex \key1\ | |
244 | @kindex \key2\ | |
245 | @item @kbd{\key1\} | |
246 | @itemx @kbd{\key2\} | |
247 | @end ifclear | |
248 | @end macro | |
249 | @c ----------------------------------------------------------------------------- | |
250 | ||
251 | @iftex | |
252 | @c @hyphenation{time-stamp time-stamps time-stamp-ing time-stamp-ed} | |
253 | @end iftex | |
254 | ||
4009494e GM |
255 | @c Subheadings inside a table. |
256 | @macro tsubheading{text} | |
257 | @ifinfo | |
258 | @subsubheading \text\ | |
259 | @end ifinfo | |
260 | @ifnotinfo | |
261 | @item @b{\text\} | |
262 | @end ifnotinfo | |
263 | @end macro | |
264 | ||
265 | @copying | |
c8d0cf5c | 266 | This manual is for Org version @value{VERSION}. |
4009494e | 267 | |
dfd98937 | 268 | Copyright @copyright{} 2004-2012 Free Software Foundation, Inc. |
4009494e GM |
269 | |
270 | @quotation | |
271 | Permission is granted to copy, distribute and/or modify this document | |
d60b1ba1 | 272 | under the terms of the GNU Free Documentation License, Version 1.3 or |
4009494e GM |
273 | any later version published by the Free Software Foundation; with no |
274 | Invariant Sections, with the Front-Cover texts being ``A GNU Manual,'' | |
47271179 GM |
275 | and with the Back-Cover Texts as in (a) below. A copy of the license |
276 | is included in the section entitled ``GNU Free Documentation License.'' | |
4009494e | 277 | |
6f093307 GM |
278 | (a) The FSF's Back-Cover Text is: ``You have the freedom to copy and |
279 | modify this GNU manual. Buying copies from the FSF supports it in | |
280 | developing GNU and promoting software freedom.'' | |
5b14aca9 GM |
281 | |
282 | This document is part of a collection distributed under the GNU Free | |
283 | Documentation License. If you want to distribute this document | |
284 | separately from the collection, you can do so by adding a copy of the | |
285 | license to the document, as described in section 6 of the license. | |
4009494e GM |
286 | @end quotation |
287 | @end copying | |
288 | ||
9e7a4bcf | 289 | @dircategory Emacs editing modes |
5dc584b5 | 290 | @direntry |
86fbb8ca | 291 | * Org Mode: (org). Outline-based notes management and organizer |
5dc584b5 KB |
292 | @end direntry |
293 | ||
4009494e | 294 | @titlepage |
a7808fba | 295 | @title The Org Manual |
4009494e GM |
296 | |
297 | @subtitle Release @value{VERSION} | |
298 | @author by Carsten Dominik | |
e66ba1df | 299 | with contributions by David O'Toole, Bastien Guerry, Philip Rooke, Dan Davison, Eric Schulte, Thomas Dye and Jambunathan K. |
4009494e GM |
300 | |
301 | @c The following two commands start the copyright page. | |
302 | @page | |
303 | @vskip 0pt plus 1filll | |
304 | @insertcopying | |
305 | @end titlepage | |
306 | ||
307 | @c Output the table of contents at the beginning. | |
308 | @contents | |
309 | ||
310 | @ifnottex | |
311 | @node Top, Introduction, (dir), (dir) | |
312 | @top Org Mode Manual | |
313 | ||
314 | @insertcopying | |
315 | @end ifnottex | |
316 | ||
317 | @menu | |
c0468714 GM |
318 | * Introduction:: Getting started |
319 | * Document Structure:: A tree works like your brain | |
320 | * Tables:: Pure magic for quick formatting | |
321 | * Hyperlinks:: Notes in context | |
322 | * TODO Items:: Every tree branch can be a TODO item | |
323 | * Tags:: Tagging headlines and matching sets of tags | |
324 | * Properties and Columns:: Storing information about an entry | |
325 | * Dates and Times:: Making items useful for planning | |
326 | * Capture - Refile - Archive:: The ins and outs for projects | |
327 | * Agenda Views:: Collecting information into views | |
328 | * Markup:: Prepare text for rich export | |
329 | * Exporting:: Sharing and publishing of notes | |
330 | * Publishing:: Create a web site of linked Org files | |
331 | * Working With Source Code:: Export, evaluate, and tangle code blocks | |
332 | * Miscellaneous:: All the rest which did not fit elsewhere | |
333 | * Hacking:: How to hack your way around | |
334 | * MobileOrg:: Viewing and capture on a mobile device | |
335 | * History and Acknowledgments:: How Org came into being | |
336 | * Main Index:: An index of Org's concepts and features | |
337 | * Key Index:: Key bindings and where they are described | |
afe98dfa | 338 | * Command and Function Index:: Command names and some internal functions |
c0468714 | 339 | * Variable Index:: Variables mentioned in the manual |
4009494e GM |
340 | |
341 | @detailmenu | |
342 | --- The Detailed Node Listing --- | |
343 | ||
344 | Introduction | |
345 | ||
c0468714 GM |
346 | * Summary:: Brief summary of what Org does |
347 | * Installation:: How to install a downloaded version of Org | |
348 | * Activation:: How to activate Org for certain buffers | |
349 | * Feedback:: Bug reports, ideas, patches etc. | |
350 | * Conventions:: Type-setting conventions in the manual | |
86fbb8ca CD |
351 | |
352 | Document structure | |
353 | ||
c0468714 GM |
354 | * Outlines:: Org is based on Outline mode |
355 | * Headlines:: How to typeset Org tree headlines | |
356 | * Visibility cycling:: Show and hide, much simplified | |
357 | * Motion:: Jumping to other headlines | |
358 | * Structure editing:: Changing sequence and level of headlines | |
359 | * Sparse trees:: Matches embedded in context | |
360 | * Plain lists:: Additional structure within an entry | |
361 | * Drawers:: Tucking stuff away | |
362 | * Blocks:: Folding blocks | |
363 | * Footnotes:: How footnotes are defined in Org's syntax | |
364 | * Orgstruct mode:: Structure editing outside Org | |
4009494e | 365 | |
4009494e GM |
366 | Tables |
367 | ||
c0468714 GM |
368 | * Built-in table editor:: Simple tables |
369 | * Column width and alignment:: Overrule the automatic settings | |
370 | * Column groups:: Grouping to trigger vertical lines | |
371 | * Orgtbl mode:: The table editor as minor mode | |
372 | * The spreadsheet:: The table editor has spreadsheet capabilities | |
373 | * Org-Plot:: Plotting from org tables | |
4009494e GM |
374 | |
375 | The spreadsheet | |
376 | ||
c0468714 GM |
377 | * References:: How to refer to another field or range |
378 | * Formula syntax for Calc:: Using Calc to compute stuff | |
379 | * Formula syntax for Lisp:: Writing formulas in Emacs Lisp | |
ce57c2fe BG |
380 | * Durations and time values:: How to compute durations and time values |
381 | * Field and range formulas:: Formula for specific (ranges of) fields | |
c0468714 | 382 | * Column formulas:: Formulas valid for an entire column |
4009494e | 383 | * Editing and debugging formulas:: Fixing formulas |
c0468714 | 384 | * Updating the table:: Recomputing all dependent fields |
e66ba1df | 385 | * Advanced features:: Field and column names, parameters and automatic recalc |
4009494e GM |
386 | |
387 | Hyperlinks | |
388 | ||
c0468714 GM |
389 | * Link format:: How links in Org are formatted |
390 | * Internal links:: Links to other places in the current file | |
391 | * External links:: URL-like links to the world | |
392 | * Handling links:: Creating, inserting and following | |
393 | * Using links outside Org:: Linking from my C source code? | |
394 | * Link abbreviations:: Shortcuts for writing complex links | |
395 | * Search options:: Linking to a specific location | |
396 | * Custom searches:: When the default search is not enough | |
4009494e GM |
397 | |
398 | Internal links | |
399 | ||
c0468714 | 400 | * Radio targets:: Make targets trigger links in plain text |
4009494e | 401 | |
86fbb8ca | 402 | TODO items |
4009494e | 403 | |
c0468714 GM |
404 | * TODO basics:: Marking and displaying TODO entries |
405 | * TODO extensions:: Workflow and assignments | |
406 | * Progress logging:: Dates and notes for progress | |
407 | * Priorities:: Some things are more important than others | |
408 | * Breaking down tasks:: Splitting a task into manageable pieces | |
409 | * Checkboxes:: Tick-off lists | |
4009494e GM |
410 | |
411 | Extended use of TODO keywords | |
412 | ||
c0468714 GM |
413 | * Workflow states:: From TODO to DONE in steps |
414 | * TODO types:: I do this, Fred does the rest | |
415 | * Multiple sets in one file:: Mixing it all, and still finding your way | |
416 | * Fast access to TODO states:: Single letter selection of a state | |
417 | * Per-file keywords:: Different files, different requirements | |
418 | * Faces for TODO keywords:: Highlighting states | |
419 | * TODO dependencies:: When one task needs to wait for others | |
dbc28aaa | 420 | |
a7808fba | 421 | Progress logging |
dbc28aaa | 422 | |
c0468714 GM |
423 | * Closing items:: When was this entry marked DONE? |
424 | * Tracking TODO state changes:: When did the status change? | |
425 | * Tracking your habits:: How consistent have you been? | |
4009494e GM |
426 | |
427 | Tags | |
428 | ||
c0468714 GM |
429 | * Tag inheritance:: Tags use the tree structure of the outline |
430 | * Setting tags:: How to assign tags to a headline | |
431 | * Tag searches:: Searching for combinations of tags | |
4009494e | 432 | |
86fbb8ca | 433 | Properties and columns |
4009494e | 434 | |
c0468714 | 435 | * Property syntax:: How properties are spelled out |
e66ba1df | 436 | * Special properties:: Access to other Org mode features |
c0468714 GM |
437 | * Property searches:: Matching property values |
438 | * Property inheritance:: Passing values down the tree | |
439 | * Column view:: Tabular viewing and editing | |
440 | * Property API:: Properties for Lisp programmers | |
4009494e | 441 | |
a7808fba | 442 | Column view |
4009494e | 443 | |
c0468714 GM |
444 | * Defining columns:: The COLUMNS format property |
445 | * Using column view:: How to create and use column view | |
446 | * Capturing column view:: A dynamic block for column view | |
4009494e | 447 | |
a7808fba | 448 | Defining columns |
4009494e | 449 | |
c0468714 GM |
450 | * Scope of column definitions:: Where defined, where valid? |
451 | * Column attributes:: Appearance and content of a column | |
4009494e | 452 | |
86fbb8ca | 453 | Dates and times |
4009494e | 454 | |
c0468714 GM |
455 | * Timestamps:: Assigning a time to a tree entry |
456 | * Creating timestamps:: Commands which insert timestamps | |
457 | * Deadlines and scheduling:: Planning your work | |
458 | * Clocking work time:: Tracking how long you spend on a task | |
c0468714 GM |
459 | * Effort estimates:: Planning work effort in advance |
460 | * Relative timer:: Notes with a running timer | |
afe98dfa | 461 | * Countdown timer:: Starting a countdown timer for a task |
4009494e GM |
462 | |
463 | Creating timestamps | |
464 | ||
e66ba1df | 465 | * The date/time prompt:: How Org mode helps you entering date and time |
c0468714 | 466 | * Custom time format:: Making dates look different |
4009494e | 467 | |
a7808fba | 468 | Deadlines and scheduling |
4009494e | 469 | |
c0468714 GM |
470 | * Inserting deadline/schedule:: Planning items |
471 | * Repeated tasks:: Items that show up again and again | |
4009494e | 472 | |
acedf35c CD |
473 | Clocking work time |
474 | ||
475 | * Clocking commands:: Starting and stopping a clock | |
476 | * The clock table:: Detailed reports | |
477 | * Resolving idle time:: Resolving time when you've been idle | |
478 | ||
a351880d | 479 | Capture - Refile - Archive |
864c9740 | 480 | |
c0468714 GM |
481 | * Capture:: Capturing new stuff |
482 | * Attachments:: Add files to tasks | |
483 | * RSS Feeds:: Getting input from RSS feeds | |
ce57c2fe | 484 | * Protocols:: External (e.g.@: Browser) access to Emacs and Org |
c0468714 GM |
485 | * Refiling notes:: Moving a tree from one place to another |
486 | * Archiving:: What to do with finished projects | |
86fbb8ca CD |
487 | |
488 | Capture | |
489 | ||
c0468714 GM |
490 | * Setting up capture:: Where notes will be stored |
491 | * Using capture:: Commands to invoke and terminate capture | |
492 | * Capture templates:: Define the outline of different note types | |
864c9740 | 493 | |
86fbb8ca | 494 | Capture templates |
4009494e | 495 | |
c0468714 GM |
496 | * Template elements:: What is needed for a complete template entry |
497 | * Template expansion:: Filling in information about time and context | |
a351880d CD |
498 | |
499 | Archiving | |
500 | ||
c0468714 GM |
501 | * Moving subtrees:: Moving a tree to an archive file |
502 | * Internal archiving:: Switch off a tree but keep it in the file | |
4009494e | 503 | |
86fbb8ca | 504 | Agenda views |
4009494e | 505 | |
c0468714 GM |
506 | * Agenda files:: Files being searched for agenda information |
507 | * Agenda dispatcher:: Keyboard access to agenda views | |
508 | * Built-in agenda views:: What is available out of the box? | |
509 | * Presentation and sorting:: How agenda items are prepared for display | |
510 | * Agenda commands:: Remote editing of Org trees | |
511 | * Custom agenda views:: Defining special searches and views | |
512 | * Exporting Agenda Views:: Writing a view to a file | |
513 | * Agenda column view:: Using column view for collected entries | |
4009494e GM |
514 | |
515 | The built-in agenda views | |
516 | ||
c0468714 GM |
517 | * Weekly/daily agenda:: The calendar page with current tasks |
518 | * Global TODO list:: All unfinished action items | |
4009494e | 519 | * Matching tags and properties:: Structured information with fine-tuned search |
c0468714 GM |
520 | * Timeline:: Time-sorted view for single file |
521 | * Search view:: Find entries by searching for text | |
522 | * Stuck projects:: Find projects you need to review | |
4009494e GM |
523 | |
524 | Presentation and sorting | |
525 | ||
c0468714 GM |
526 | * Categories:: Not all tasks are equal |
527 | * Time-of-day specifications:: How the agenda knows the time | |
528 | * Sorting of agenda items:: The order of things | |
4009494e GM |
529 | |
530 | Custom agenda views | |
531 | ||
c0468714 GM |
532 | * Storing searches:: Type once, use often |
533 | * Block agenda:: All the stuff you need in a single buffer | |
534 | * Setting Options:: Changing the rules | |
4009494e | 535 | |
a351880d CD |
536 | Markup for rich export |
537 | ||
c0468714 GM |
538 | * Structural markup elements:: The basic structure as seen by the exporter |
539 | * Images and tables:: Tables and Images will be included | |
540 | * Literal examples:: Source code examples with special formatting | |
541 | * Include files:: Include additional files into a document | |
542 | * Index entries:: Making an index | |
543 | * Macro replacement:: Use macros to create complex output | |
e66ba1df | 544 | * Embedded @LaTeX{}:: LaTeX can be freely used inside Org documents |
a351880d CD |
545 | |
546 | Structural markup elements | |
547 | ||
c0468714 GM |
548 | * Document title:: Where the title is taken from |
549 | * Headings and sections:: The document structure as seen by the exporter | |
550 | * Table of contents:: The if and where of the table of contents | |
551 | * Initial text:: Text before the first heading? | |
552 | * Lists:: Lists | |
553 | * Paragraphs:: Paragraphs | |
554 | * Footnote markup:: Footnotes | |
555 | * Emphasis and monospace:: Bold, italic, etc. | |
556 | * Horizontal rules:: Make a line | |
557 | * Comment lines:: What will *not* be exported | |
a351880d | 558 | |
acedf35c | 559 | Embedded @LaTeX{} |
4009494e | 560 | |
c0468714 GM |
561 | * Special symbols:: Greek letters and other symbols |
562 | * Subscripts and superscripts:: Simple syntax for raising/lowering text | |
e66ba1df BG |
563 | * @LaTeX{} fragments:: Complex formulas made easy |
564 | * Previewing @LaTeX{} fragments:: What will this snippet look like? | |
c0468714 | 565 | * CDLaTeX mode:: Speed up entering of formulas |
4009494e GM |
566 | |
567 | Exporting | |
568 | ||
c0468714 GM |
569 | * Selective export:: Using tags to select and exclude trees |
570 | * Export options:: Per-file export settings | |
571 | * The export dispatcher:: How to access exporter commands | |
572 | * ASCII/Latin-1/UTF-8 export:: Exporting to flat files with encoding | |
573 | * HTML export:: Exporting to HTML | |
e66ba1df | 574 | * @LaTeX{} and PDF export:: Exporting to @LaTeX{}, and processing to PDF |
c0468714 | 575 | * DocBook export:: Exporting to DocBook |
e66ba1df | 576 | * OpenDocument Text export:: Exporting to OpenDocument Text |
c0468714 GM |
577 | * TaskJuggler export:: Exporting to TaskJuggler |
578 | * Freemind export:: Exporting to Freemind mind maps | |
579 | * XOXO export:: Exporting to XOXO | |
580 | * iCalendar export:: Exporting in iCalendar format | |
b349f79f | 581 | |
4009494e GM |
582 | HTML export |
583 | ||
c0468714 | 584 | * HTML Export commands:: How to invoke HTML export |
ce57c2fe | 585 | * HTML preamble and postamble:: How to insert a preamble and a postamble |
e66ba1df | 586 | * Quoting HTML tags:: Using direct HTML in Org mode |
c0468714 GM |
587 | * Links in HTML export:: How links will be interpreted and formatted |
588 | * Tables in HTML export:: How to modify the formatting of tables | |
589 | * Images in HTML export:: How to insert figures into HTML output | |
afe98dfa | 590 | * Math formatting in HTML export:: Beautiful math also on the web |
c0468714 GM |
591 | * Text areas in HTML export:: An alternative way to show an example |
592 | * CSS support:: Changing the appearance of the output | |
593 | * JavaScript support:: Info and Folding in a web browser | |
4009494e | 594 | |
acedf35c | 595 | @LaTeX{} and PDF export |
4009494e | 596 | |
e66ba1df | 597 | * @LaTeX{}/PDF export commands:: |
c0468714 | 598 | * Header and sectioning:: Setting up the export file structure |
e66ba1df BG |
599 | * Quoting @LaTeX{} code:: Incorporating literal @LaTeX{} code |
600 | * Tables in @LaTeX{} export:: Options for exporting tables to @LaTeX{} | |
601 | * Images in @LaTeX{} export:: How to insert figures into @LaTeX{} output | |
c0468714 | 602 | * Beamer class export:: Turning the file into a presentation |
c8d0cf5c CD |
603 | |
604 | DocBook export | |
605 | ||
c0468714 GM |
606 | * DocBook export commands:: How to invoke DocBook export |
607 | * Quoting DocBook code:: Incorporating DocBook code in Org files | |
608 | * Recursive sections:: Recursive sections in DocBook | |
609 | * Tables in DocBook export:: Tables are exported as HTML tables | |
610 | * Images in DocBook export:: How to insert figures into DocBook output | |
611 | * Special characters:: How to handle special characters | |
4009494e | 612 | |
e66ba1df | 613 | OpenDocument Text export |
ce57c2fe | 614 | |
153ae947 BG |
615 | * Pre-requisites for ODT export:: What packages ODT exporter relies on |
616 | * ODT export commands:: How to invoke ODT export | |
617 | * Extending ODT export:: How to produce @samp{doc}, @samp{pdf} files | |
e66ba1df | 618 | * Applying custom styles:: How to apply custom styles to the output |
153ae947 BG |
619 | * Links in ODT export:: How links will be interpreted and formatted |
620 | * Tables in ODT export:: How Tables are exported | |
621 | * Images in ODT export:: How to insert images | |
622 | * Math formatting in ODT export:: How @LaTeX{} fragments are formatted | |
623 | * Labels and captions in ODT export:: How captions are rendered | |
624 | * Literal examples in ODT export:: How source and example blocks are formatted | |
625 | * Advanced topics in ODT export:: Read this if you are a power user | |
e66ba1df | 626 | |
153ae947 | 627 | Math formatting in ODT export |
e66ba1df BG |
628 | |
629 | * Working with @LaTeX{} math snippets:: How to embed @LaTeX{} math fragments | |
630 | * Working with MathML or OpenDocument formula files:: How to embed equations in native format | |
631 | ||
153ae947 | 632 | Advanced topics in ODT export |
e66ba1df | 633 | |
153ae947 | 634 | * Configuring a document converter:: How to register a document converter |
e66ba1df BG |
635 | * Working with OpenDocument style files:: Explore the internals |
636 | * Creating one-off styles:: How to produce custom highlighting etc | |
153ae947 | 637 | * Customizing tables in ODT export:: How to define and use Table templates |
e66ba1df | 638 | * Validating OpenDocument XML:: How to debug corrupt OpenDocument files |
ce57c2fe | 639 | |
4009494e GM |
640 | Publishing |
641 | ||
c0468714 GM |
642 | * Configuration:: Defining projects |
643 | * Uploading files:: How to get files up on the server | |
644 | * Sample configuration:: Example projects | |
645 | * Triggering publication:: Publication commands | |
4009494e GM |
646 | |
647 | Configuration | |
648 | ||
c0468714 GM |
649 | * Project alist:: The central configuration variable |
650 | * Sources and destinations:: From here to there | |
651 | * Selecting files:: What files are part of the project? | |
652 | * Publishing action:: Setting the function doing the publishing | |
ce57c2fe | 653 | * Publishing options:: Tweaking HTML/@LaTeX{} export |
c0468714 GM |
654 | * Publishing links:: Which links keep working after publishing? |
655 | * Sitemap:: Generating a list of all pages | |
656 | * Generating an index:: An index that reaches across pages | |
4009494e GM |
657 | |
658 | Sample configuration | |
659 | ||
c0468714 GM |
660 | * Simple example:: One-component publishing |
661 | * Complex example:: A multi-component publishing example | |
86fbb8ca CD |
662 | |
663 | Working with source code | |
664 | ||
c0468714 GM |
665 | * Structure of code blocks:: Code block syntax described |
666 | * Editing source code:: Language major-mode editing | |
667 | * Exporting code blocks:: Export contents and/or results | |
668 | * Extracting source code:: Create pure source code files | |
e66ba1df | 669 | * Evaluating code blocks:: Place results of evaluation in the Org mode buffer |
c0468714 GM |
670 | * Library of Babel:: Use and contribute to a library of useful code blocks |
671 | * Languages:: List of supported code block languages | |
672 | * Header arguments:: Configure code block functionality | |
673 | * Results of evaluation:: How evaluation results are handled | |
e66ba1df | 674 | * Noweb reference syntax:: Literate programming in Org mode |
86fbb8ca | 675 | * Key bindings and useful functions:: Work quickly with code blocks |
c0468714 | 676 | * Batch execution:: Call functions from the command line |
86fbb8ca CD |
677 | |
678 | Header arguments | |
679 | ||
c0468714 GM |
680 | * Using header arguments:: Different ways to set header arguments |
681 | * Specific header arguments:: List of header arguments | |
86fbb8ca CD |
682 | |
683 | Using header arguments | |
684 | ||
685 | * System-wide header arguments:: Set global default values | |
c0468714 | 686 | * Language-specific header arguments:: Set default values by language |
86fbb8ca | 687 | * Buffer-wide header arguments:: Set default values for a specific buffer |
e66ba1df | 688 | * Header arguments in Org mode properties:: Set default values for a buffer or heading |
86fbb8ca | 689 | * Code block specific header arguments:: The most common way to set values |
afe98dfa | 690 | * Header arguments in function calls:: The most specific level |
86fbb8ca CD |
691 | |
692 | Specific header arguments | |
693 | ||
c0468714 | 694 | * var:: Pass arguments to code blocks |
afe98dfa CD |
695 | * results:: Specify the type of results and how they will |
696 | be collected and handled | |
c0468714 | 697 | * file:: Specify a path for file output |
afe98dfa CD |
698 | * dir:: Specify the default (possibly remote) |
699 | directory for code block execution | |
c0468714 GM |
700 | * exports:: Export code and/or results |
701 | * tangle:: Toggle tangling and specify file name | |
ce57c2fe BG |
702 | * mkdirp:: Toggle creation of parent directories of target |
703 | files during tangling | |
afe98dfa CD |
704 | * comments:: Toggle insertion of comments in tangled |
705 | code files | |
ce57c2fe BG |
706 | * padline:: Control insertion of padding lines in tangled |
707 | code files | |
afe98dfa CD |
708 | * no-expand:: Turn off variable assignment and noweb |
709 | expansion during tangling | |
c0468714 GM |
710 | * session:: Preserve the state of code evaluation |
711 | * noweb:: Toggle expansion of noweb references | |
ce57c2fe | 712 | * noweb-ref:: Specify block's noweb reference resolution target |
153ae947 | 713 | * noweb-sep:: String used to separate noweb references |
c0468714 | 714 | * cache:: Avoid re-evaluating unchanged code blocks |
ce57c2fe | 715 | * sep:: Delimiter for writing tabular results outside Org |
c0468714 GM |
716 | * hlines:: Handle horizontal lines in tables |
717 | * colnames:: Handle column names in tables | |
718 | * rownames:: Handle row names in tables | |
719 | * shebang:: Make tangled files executable | |
afe98dfa | 720 | * eval:: Limit evaluation of specific code blocks |
4009494e GM |
721 | |
722 | Miscellaneous | |
723 | ||
c0468714 | 724 | * Completion:: M-TAB knows what you need |
afe98dfa | 725 | * Easy Templates:: Quick insertion of structural elements |
c0468714 GM |
726 | * Speed keys:: Electric commands at the beginning of a headline |
727 | * Code evaluation security:: Org mode files evaluate inline code | |
728 | * Customization:: Adapting Org to your taste | |
729 | * In-buffer settings:: Overview of the #+KEYWORDS | |
730 | * The very busy C-c C-c key:: When in doubt, press C-c C-c | |
731 | * Clean view:: Getting rid of leading stars in the outline | |
732 | * TTY keys:: Using Org on a tty | |
733 | * Interaction:: Other Emacs packages | |
ce57c2fe | 734 | * org-crypt.el:: Encrypting Org files |
4009494e GM |
735 | |
736 | Interaction with other packages | |
737 | ||
c0468714 GM |
738 | * Cooperation:: Packages Org cooperates with |
739 | * Conflicts:: Packages that lead to conflicts | |
4009494e | 740 | |
b349f79f | 741 | Hacking |
4009494e | 742 | |
c0468714 GM |
743 | * Hooks:: Who to reach into Org's internals |
744 | * Add-on packages:: Available extensions | |
745 | * Adding hyperlink types:: New custom link types | |
746 | * Context-sensitive commands:: How to add functionality to such commands | |
acedf35c | 747 | * Tables in arbitrary syntax:: Orgtbl for @LaTeX{} and other programs |
c0468714 GM |
748 | * Dynamic blocks:: Automatically filled blocks |
749 | * Special agenda views:: Customized views | |
c8d0cf5c | 750 | * Extracting agenda information:: Postprocessing of agenda information |
c0468714 GM |
751 | * Using the property API:: Writing programs that use entry properties |
752 | * Using the mapping API:: Mapping over all or selected entries | |
4009494e | 753 | |
a7808fba | 754 | Tables and lists in arbitrary syntax |
4009494e | 755 | |
c0468714 | 756 | * Radio tables:: Sending and receiving radio tables |
e66ba1df | 757 | * A @LaTeX{} example:: Step by step, almost a tutorial |
c0468714 GM |
758 | * Translator functions:: Copy and modify |
759 | * Radio lists:: Doing the same for lists | |
4009494e | 760 | |
7006d207 CD |
761 | MobileOrg |
762 | ||
c0468714 GM |
763 | * Setting up the staging area:: Where to interact with the mobile device |
764 | * Pushing to MobileOrg:: Uploading Org files and agendas | |
765 | * Pulling from MobileOrg:: Integrating captured and flagged items | |
7006d207 | 766 | |
4009494e GM |
767 | @end detailmenu |
768 | @end menu | |
769 | ||
a7808fba | 770 | @node Introduction, Document Structure, Top, Top |
4009494e GM |
771 | @chapter Introduction |
772 | @cindex introduction | |
773 | ||
774 | @menu | |
c0468714 GM |
775 | * Summary:: Brief summary of what Org does |
776 | * Installation:: How to install a downloaded version of Org | |
777 | * Activation:: How to activate Org for certain buffers | |
778 | * Feedback:: Bug reports, ideas, patches etc. | |
779 | * Conventions:: Type-setting conventions in the manual | |
4009494e GM |
780 | @end menu |
781 | ||
782 | @node Summary, Installation, Introduction, Introduction | |
783 | @section Summary | |
784 | @cindex summary | |
785 | ||
a7808fba | 786 | Org is a mode for keeping notes, maintaining TODO lists, and doing |
4009494e GM |
787 | project planning with a fast and effective plain-text system. |
788 | ||
a7808fba CD |
789 | Org develops organizational tasks around NOTES files that contain |
790 | lists or information about projects as plain text. Org is | |
791 | implemented on top of Outline mode, which makes it possible to keep the | |
4009494e GM |
792 | content of large files well structured. Visibility cycling and |
793 | structure editing help to work with the tree. Tables are easily created | |
a7808fba | 794 | with a built-in table editor. Org supports TODO items, deadlines, |
c8d0cf5c | 795 | timestamps, and scheduling. It dynamically compiles entries into an |
4009494e GM |
796 | agenda that utilizes and smoothly integrates much of the Emacs calendar |
797 | and diary. Plain text URL-like links connect to websites, emails, | |
798 | Usenet messages, BBDB entries, and any files related to the projects. | |
a7808fba | 799 | For printing and sharing of notes, an Org file can be exported as a |
dbc28aaa | 800 | structured ASCII file, as HTML, or (TODO and agenda items only) as an |
4009494e | 801 | iCalendar file. It can also serve as a publishing tool for a set of |
a7808fba | 802 | linked web pages. |
4009494e | 803 | |
86fbb8ca CD |
804 | As a project planning environment, Org works by adding metadata to outline |
805 | nodes. Based on this data, specific entries can be extracted in queries and | |
806 | create dynamic @i{agenda views}. | |
807 | ||
acedf35c CD |
808 | Org mode contains the Org Babel environment which allows you to work with |
809 | embedded source code blocks in a file, to facilitate code evaluation, | |
ce57c2fe | 810 | documentation, and literate programming techniques. |
86fbb8ca CD |
811 | |
812 | Org's automatic, context-sensitive table editor with spreadsheet | |
813 | capabilities can be integrated into any major mode by activating the | |
814 | minor Orgtbl mode. Using a translation step, it can be used to maintain | |
acedf35c | 815 | tables in arbitrary file types, for example in @LaTeX{}. The structure |
86fbb8ca CD |
816 | editing and list creation capabilities can be used outside Org with |
817 | the minor Orgstruct mode. | |
4009494e | 818 | |
a7808fba | 819 | Org keeps simple things simple. When first fired up, it should |
4009494e GM |
820 | feel like a straightforward, easy to use outliner. Complexity is not |
821 | imposed, but a large amount of functionality is available when you need | |
86fbb8ca CD |
822 | it. Org is a toolbox and can be used in different ways and for different |
823 | ends, for example: | |
4009494e GM |
824 | |
825 | @example | |
c8d0cf5c CD |
826 | @r{@bullet{} an outline extension with visibility cycling and structure editing} |
827 | @r{@bullet{} an ASCII system and table editor for taking structured notes} | |
c8d0cf5c CD |
828 | @r{@bullet{} a TODO list editor} |
829 | @r{@bullet{} a full agenda and planner with deadlines and work scheduling} | |
830 | @pindex GTD, Getting Things Done | |
86fbb8ca | 831 | @r{@bullet{} an environment in which to implement David Allen's GTD system} |
acedf35c | 832 | @r{@bullet{} a simple hypertext system, with HTML and @LaTeX{} export} |
c8d0cf5c | 833 | @r{@bullet{} a publishing tool to create a set of interlinked webpages} |
86fbb8ca | 834 | @r{@bullet{} an environment for literate programming} |
4009494e GM |
835 | @end example |
836 | ||
4009494e GM |
837 | |
838 | @cindex FAQ | |
a7808fba CD |
839 | There is a website for Org which provides links to the newest |
840 | version of Org, as well as additional information, frequently asked | |
c8d0cf5c | 841 | questions (FAQ), links to tutorials, etc@. This page is located at |
dbc28aaa | 842 | @uref{http://orgmode.org}. |
4009494e | 843 | |
ce57c2fe BG |
844 | @cindex print edition |
845 | The version 7.3 of this manual is available as a | |
846 | @uref{http://www.network-theory.co.uk/org/manual/, paperback book from Network | |
847 | Theory Ltd.} | |
848 | ||
4009494e GM |
849 | @page |
850 | ||
851 | ||
852 | @node Installation, Activation, Summary, Introduction | |
853 | @section Installation | |
854 | @cindex installation | |
855 | @cindex XEmacs | |
856 | ||
7006d207 CD |
857 | @b{Important:} @i{If you are using a version of Org that is part of the Emacs |
858 | distribution or an XEmacs package, please skip this section and go directly | |
ce57c2fe BG |
859 | to @ref{Activation}. To see what version of Org (if any) is part of your |
860 | Emacs distribution, type @kbd{M-x load-library RET org} and then @kbd{M-x | |
861 | org-version}.} | |
4009494e | 862 | |
a7808fba | 863 | If you have downloaded Org from the Web, either as a distribution @file{.zip} |
c8d0cf5c CD |
864 | or @file{.tar} file, or as a Git archive, you must take the following steps |
865 | to install it: go into the unpacked Org distribution directory and edit the | |
a7808fba CD |
866 | top section of the file @file{Makefile}. You must set the name of the Emacs |
867 | binary (likely either @file{emacs} or @file{xemacs}), and the paths to the | |
868 | directories where local Lisp and Info files are kept. If you don't have | |
869 | access to the system-wide directories, you can simply run Org directly from | |
870 | the distribution directory by adding the @file{lisp} subdirectory to the | |
871 | Emacs load path. To do this, add the following line to @file{.emacs}: | |
4009494e GM |
872 | |
873 | @example | |
a7808fba CD |
874 | (setq load-path (cons "~/path/to/orgdir/lisp" load-path)) |
875 | @end example | |
876 | ||
877 | @noindent | |
878 | If you plan to use code from the @file{contrib} subdirectory, do a similar | |
879 | step for this directory: | |
880 | ||
881 | @example | |
882 | (setq load-path (cons "~/path/to/orgdir/contrib/lisp" load-path)) | |
4009494e GM |
883 | @end example |
884 | ||
a7808fba | 885 | @noindent Now byte-compile the Lisp files with the shell command: |
4009494e GM |
886 | |
887 | @example | |
888 | make | |
4009494e GM |
889 | @end example |
890 | ||
a7808fba | 891 | @noindent If you are running Org from the distribution directory, this is |
c8d0cf5c CD |
892 | all. If you want to install Org into the system directories, use (as |
893 | administrator) | |
4009494e GM |
894 | |
895 | @example | |
a7808fba | 896 | make install |
c8d0cf5c CD |
897 | @end example |
898 | ||
899 | Installing Info files is system dependent, because of differences in the | |
ce57c2fe BG |
900 | @file{install-info} program. The following should correctly install the Info |
901 | files on most systems, please send a bug report if not@footnote{The output | |
902 | from install-info (if any) is also system dependent. In particular Debian | |
903 | and its derivatives use two different versions of install-info and you may | |
904 | see the message: | |
905 | ||
906 | @example | |
907 | This is not dpkg install-info anymore, but GNU install-info | |
908 | See the man page for ginstall-info for command line arguments | |
909 | @end example | |
910 | ||
911 | @noindent which can be safely ignored.}. | |
c8d0cf5c CD |
912 | |
913 | @example | |
4009494e GM |
914 | make install-info |
915 | @end example | |
916 | ||
7006d207 CD |
917 | Then add the following line to @file{.emacs}. It is needed so that |
918 | Emacs can autoload functions that are located in files not immediately loaded | |
e66ba1df | 919 | when Org mode starts. |
4009494e | 920 | @lisp |
4009494e GM |
921 | (require 'org-install) |
922 | @end lisp | |
923 | ||
55e0839d | 924 | Do not forget to activate Org as described in the following section. |
7006d207 | 925 | @page |
a7808fba | 926 | |
4009494e GM |
927 | @node Activation, Feedback, Installation, Introduction |
928 | @section Activation | |
929 | @cindex activation | |
930 | @cindex autoload | |
a7808fba CD |
931 | @cindex global key bindings |
932 | @cindex key bindings, global | |
4009494e | 933 | |
ce57c2fe BG |
934 | To make sure files with extension @file{.org} use Org mode, add the following |
935 | line to your @file{.emacs} file. | |
4009494e | 936 | @lisp |
4009494e | 937 | (add-to-list 'auto-mode-alist '("\\.org\\'" . org-mode)) |
ce57c2fe BG |
938 | @end lisp |
939 | @noindent Org mode buffers need font-lock to be turned on - this is the | |
940 | default in Emacs@footnote{If you don't use font-lock globally, turn it on in | |
941 | Org buffer with @code{(add-hook 'org-mode-hook 'turn-on-font-lock)}}. | |
942 | ||
943 | The four Org commands @command{org-store-link}, @command{org-capture}, | |
944 | @command{org-agenda}, and @command{org-iswitchb} should be accessible through | |
945 | global keys (i.e.@: anywhere in Emacs, not just in Org buffers). Here are | |
946 | suggested bindings for these keys, please modify the keys to your own | |
947 | liking. | |
948 | @lisp | |
4009494e | 949 | (global-set-key "\C-cl" 'org-store-link) |
ce57c2fe | 950 | (global-set-key "\C-cc" 'org-capture) |
4009494e | 951 | (global-set-key "\C-ca" 'org-agenda) |
a7808fba | 952 | (global-set-key "\C-cb" 'org-iswitchb) |
4009494e GM |
953 | @end lisp |
954 | ||
e66ba1df | 955 | @cindex Org mode, turning on |
4009494e | 956 | With this setup, all files with extension @samp{.org} will be put |
e66ba1df | 957 | into Org mode. As an alternative, make the first line of a file look |
4009494e GM |
958 | like this: |
959 | ||
960 | @example | |
961 | MY PROJECTS -*- mode: org; -*- | |
962 | @end example | |
963 | ||
c8d0cf5c | 964 | @vindex org-insert-mode-line-in-empty-file |
e66ba1df | 965 | @noindent which will select Org mode for this buffer no matter what |
4009494e GM |
966 | the file's name is. See also the variable |
967 | @code{org-insert-mode-line-in-empty-file}. | |
968 | ||
c8d0cf5c CD |
969 | Many commands in Org work on the region if the region is @i{active}. To make |
970 | use of this, you need to have @code{transient-mark-mode} | |
971 | (@code{zmacs-regions} in XEmacs) turned on. In Emacs 23 this is the default, | |
972 | in Emacs 22 you need to do this yourself with | |
b6cb4cd5 CD |
973 | @lisp |
974 | (transient-mark-mode 1) | |
975 | @end lisp | |
c8d0cf5c CD |
976 | @noindent If you do not like @code{transient-mark-mode}, you can create an |
977 | active region by using the mouse to select a region, or pressing | |
978 | @kbd{C-@key{SPC}} twice before moving the cursor. | |
b6cb4cd5 | 979 | |
dbc28aaa | 980 | @node Feedback, Conventions, Activation, Introduction |
4009494e GM |
981 | @section Feedback |
982 | @cindex feedback | |
983 | @cindex bug reports | |
984 | @cindex maintainer | |
985 | @cindex author | |
986 | ||
b349f79f | 987 | If you find problems with Org, or if you have questions, remarks, or ideas |
c8d0cf5c | 988 | about it, please mail to the Org mailing list @email{emacs-orgmode@@gnu.org}. |
6eb02347 | 989 | If you are not a member of the mailing list, your mail will be passed to the |
afe98dfa CD |
990 | list after a moderator has approved it@footnote{Please consider subscribing |
991 | to the mailing list, in order to minimize the work the mailing list | |
992 | moderators have to do.}. | |
993 | ||
994 | For bug reports, please first try to reproduce the bug with the latest | |
acedf35c | 995 | version of Org available---if you are running an outdated version, it is |
afe98dfa CD |
996 | quite possible that the bug has been fixed already. If the bug persists, |
997 | prepare a report and provide as much information as possible, including the | |
998 | version information of Emacs (@kbd{M-x emacs-version @key{RET}}) and Org | |
6eb02347 CD |
999 | (@kbd{M-x org-version @key{RET}}), as well as the Org related setup in |
1000 | @file{.emacs}. The easiest way to do this is to use the command | |
1001 | @example | |
1002 | @kbd{M-x org-submit-bug-report} | |
1003 | @end example | |
1004 | @noindent which will put all this information into an Emacs mail buffer so | |
1005 | that you only need to add your description. If you re not sending the Email | |
1006 | from within Emacs, please copy and paste the content into your Email program. | |
1007 | ||
e66ba1df BG |
1008 | Sometimes you might face a problem due to an error in your Emacs or Org mode |
1009 | setup. Before reporting a bug, it is very helpful to start Emacs with minimal | |
7bd20f91 | 1010 | customizations and reproduce the problem. Doing so often helps you determine |
27e428e7 | 1011 | if the problem is with your customization or with Org mode itself. You can |
e66ba1df BG |
1012 | start a typical minimal session with a command like the example below. |
1013 | ||
1014 | @example | |
1015 | $ emacs -Q -l /path/to/minimal-org.el | |
1016 | @end example | |
1017 | ||
1018 | However if you are using Org mode as distributed with Emacs, a minimal setup | |
1019 | is not necessary. In that case it is sufficient to start Emacs as @code{emacs | |
1020 | -Q}. The @code{minimal-org.el} setup file can have contents as shown below. | |
1021 | ||
1022 | @example | |
1023 | ;;; Minimal setup to load latest `org-mode' | |
1024 | ||
1025 | ;; activate debugging | |
1026 | (setq debug-on-error t | |
1027 | debug-on-signal nil | |
1028 | debug-on-quit nil) | |
1029 | ||
1030 | ;; add latest org-mode to load path | |
1031 | (add-to-list 'load-path (expand-file-name "/path/to/org-mode/lisp")) | |
1032 | (add-to-list 'load-path (expand-file-name "/path/to/org-mode/contrib/lisp")) | |
1033 | ||
1034 | ;; activate org | |
1035 | (require 'org-install) | |
1036 | @end example | |
1037 | ||
6eb02347 CD |
1038 | If an error occurs, a backtrace can be very useful (see below on how to |
1039 | create one). Often a small example file helps, along with clear information | |
1040 | about: | |
4009494e GM |
1041 | |
1042 | @enumerate | |
1043 | @item What exactly did you do? | |
1044 | @item What did you expect to happen? | |
1045 | @item What happened instead? | |
1046 | @end enumerate | |
afe98dfa | 1047 | @noindent Thank you for helping to improve this program. |
4009494e GM |
1048 | |
1049 | @subsubheading How to create a useful backtrace | |
1050 | ||
1051 | @cindex backtrace of an error | |
a7808fba | 1052 | If working with Org produces an error with a message you don't |
4009494e | 1053 | understand, you may have hit a bug. The best way to report this is by |
c8d0cf5c | 1054 | providing, in addition to what was mentioned above, a @emph{backtrace}. |
4009494e GM |
1055 | This is information from the built-in debugger about where and how the |
1056 | error occurred. Here is how to produce a useful backtrace: | |
1057 | ||
1058 | @enumerate | |
1059 | @item | |
e66ba1df | 1060 | Reload uncompiled versions of all Org mode Lisp files. The backtrace |
c8d0cf5c CD |
1061 | contains much more information if it is produced with uncompiled code. |
1062 | To do this, use | |
4009494e | 1063 | @example |
c8d0cf5c | 1064 | C-u M-x org-reload RET |
4009494e | 1065 | @end example |
c8d0cf5c CD |
1066 | @noindent |
1067 | or select @code{Org -> Refresh/Reload -> Reload Org uncompiled} from the | |
1068 | menu. | |
4009494e GM |
1069 | @item |
1070 | Go to the @code{Options} menu and select @code{Enter Debugger on Error} | |
1071 | (XEmacs has this option in the @code{Troubleshooting} sub-menu). | |
1072 | @item | |
1073 | Do whatever you have to do to hit the error. Don't forget to | |
1074 | document the steps you take. | |
1075 | @item | |
1076 | When you hit the error, a @file{*Backtrace*} buffer will appear on the | |
1077 | screen. Save this buffer to a file (for example using @kbd{C-x C-w}) and | |
1078 | attach it to your bug report. | |
1079 | @end enumerate | |
1080 | ||
dbc28aaa CD |
1081 | @node Conventions, , Feedback, Introduction |
1082 | @section Typesetting conventions used in this manual | |
1083 | ||
a7808fba | 1084 | Org uses three types of keywords: TODO keywords, tags, and property |
dbc28aaa CD |
1085 | names. In this manual we use the following conventions: |
1086 | ||
1087 | @table @code | |
1088 | @item TODO | |
1089 | @itemx WAITING | |
1090 | TODO keywords are written with all capitals, even if they are | |
1091 | user-defined. | |
1092 | @item boss | |
1093 | @itemx ARCHIVE | |
1094 | User-defined tags are written in lowercase; built-in tags with special | |
1095 | meaning are written with all capitals. | |
1096 | @item Release | |
1097 | @itemx PRIORITY | |
1098 | User-defined properties are capitalized; built-in properties with | |
1099 | special meaning are written with all capitals. | |
1100 | @end table | |
1101 | ||
acedf35c CD |
1102 | The manual lists both the keys and the corresponding commands for accessing |
1103 | functionality. Org mode often uses the same key for different functions, | |
1104 | depending on context. The command that is bound to such keys has a generic | |
1105 | name, like @code{org-metaright}. In the manual we will, wherever possible, | |
1106 | give the function that is internally called by the generic command. For | |
1107 | example, in the chapter on document structure, @kbd{M-@key{right}} will be | |
1108 | listed to call @code{org-do-demote}, while in the chapter on tables, it will | |
1109 | be listed to call org-table-move-column-right. | |
1110 | ||
1111 | If you prefer, you can compile the manual without the command names by | |
1112 | unsetting the flag @code{cmdnames} in @file{org.texi}. | |
1113 | ||
a7808fba | 1114 | @node Document Structure, Tables, Introduction, Top |
86fbb8ca | 1115 | @chapter Document structure |
4009494e GM |
1116 | @cindex document structure |
1117 | @cindex structure of document | |
1118 | ||
c8d0cf5c | 1119 | Org is based on Outline mode and provides flexible commands to |
4009494e GM |
1120 | edit the structure of the document. |
1121 | ||
1122 | @menu | |
c0468714 GM |
1123 | * Outlines:: Org is based on Outline mode |
1124 | * Headlines:: How to typeset Org tree headlines | |
1125 | * Visibility cycling:: Show and hide, much simplified | |
1126 | * Motion:: Jumping to other headlines | |
1127 | * Structure editing:: Changing sequence and level of headlines | |
1128 | * Sparse trees:: Matches embedded in context | |
1129 | * Plain lists:: Additional structure within an entry | |
1130 | * Drawers:: Tucking stuff away | |
1131 | * Blocks:: Folding blocks | |
1132 | * Footnotes:: How footnotes are defined in Org's syntax | |
1133 | * Orgstruct mode:: Structure editing outside Org | |
4009494e GM |
1134 | @end menu |
1135 | ||
a7808fba | 1136 | @node Outlines, Headlines, Document Structure, Document Structure |
4009494e GM |
1137 | @section Outlines |
1138 | @cindex outlines | |
a7808fba | 1139 | @cindex Outline mode |
4009494e | 1140 | |
a7808fba | 1141 | Org is implemented on top of Outline mode. Outlines allow a |
4009494e GM |
1142 | document to be organized in a hierarchical structure, which (at least |
1143 | for me) is the best representation of notes and thoughts. An overview | |
1144 | of this structure is achieved by folding (hiding) large parts of the | |
1145 | document to show only the general document structure and the parts | |
a7808fba | 1146 | currently being worked on. Org greatly simplifies the use of |
4009494e | 1147 | outlines by compressing the entire show/hide functionality into a single |
c8d0cf5c | 1148 | command, @command{org-cycle}, which is bound to the @key{TAB} key. |
4009494e | 1149 | |
a7808fba | 1150 | @node Headlines, Visibility cycling, Outlines, Document Structure |
4009494e GM |
1151 | @section Headlines |
1152 | @cindex headlines | |
1153 | @cindex outline tree | |
c8d0cf5c | 1154 | @vindex org-special-ctrl-a/e |
86fbb8ca CD |
1155 | @vindex org-special-ctrl-k |
1156 | @vindex org-ctrl-k-protect-subtree | |
4009494e | 1157 | |
86fbb8ca CD |
1158 | Headlines define the structure of an outline tree. The headlines in Org |
1159 | start with one or more stars, on the left margin@footnote{See the variables | |
1160 | @code{org-special-ctrl-a/e}, @code{org-special-ctrl-k}, and | |
1161 | @code{org-ctrl-k-protect-subtree} to configure special behavior of @kbd{C-a}, | |
1162 | @kbd{C-e}, and @kbd{C-k} in headlines.}. For example: | |
4009494e GM |
1163 | |
1164 | @example | |
1165 | * Top level headline | |
1166 | ** Second level | |
1167 | *** 3rd level | |
1168 | some text | |
1169 | *** 3rd level | |
1170 | more text | |
1171 | ||
1172 | * Another top level headline | |
1173 | @end example | |
1174 | ||
1175 | @noindent Some people find the many stars too noisy and would prefer an | |
1176 | outline that has whitespace followed by a single star as headline | |
c8d0cf5c | 1177 | starters. @ref{Clean view}, describes a setup to realize this. |
4009494e | 1178 | |
c8d0cf5c | 1179 | @vindex org-cycle-separator-lines |
4009494e GM |
1180 | An empty line after the end of a subtree is considered part of it and |
1181 | will be hidden when the subtree is folded. However, if you leave at | |
1182 | least two empty lines, one empty line will remain visible after folding | |
1183 | the subtree, in order to structure the collapsed view. See the | |
1184 | variable @code{org-cycle-separator-lines} to modify this behavior. | |
1185 | ||
a7808fba | 1186 | @node Visibility cycling, Motion, Headlines, Document Structure |
4009494e GM |
1187 | @section Visibility cycling |
1188 | @cindex cycling, visibility | |
1189 | @cindex visibility cycling | |
1190 | @cindex trees, visibility | |
1191 | @cindex show hidden text | |
1192 | @cindex hide text | |
1193 | ||
1194 | Outlines make it possible to hide parts of the text in the buffer. | |
a7808fba | 1195 | Org uses just two commands, bound to @key{TAB} and |
4009494e GM |
1196 | @kbd{S-@key{TAB}} to change the visibility in the buffer. |
1197 | ||
1198 | @cindex subtree visibility states | |
1199 | @cindex subtree cycling | |
1200 | @cindex folded, subtree visibility state | |
1201 | @cindex children, subtree visibility state | |
1202 | @cindex subtree, subtree visibility state | |
afe98dfa CD |
1203 | @table @asis |
1204 | @orgcmd{@key{TAB},org-cycle} | |
4009494e GM |
1205 | @emph{Subtree cycling}: Rotate current subtree among the states |
1206 | ||
1207 | @example | |
1208 | ,-> FOLDED -> CHILDREN -> SUBTREE --. | |
1209 | '-----------------------------------' | |
1210 | @end example | |
1211 | ||
c8d0cf5c CD |
1212 | @vindex org-cycle-emulate-tab |
1213 | @vindex org-cycle-global-at-bob | |
4009494e GM |
1214 | The cursor must be on a headline for this to work@footnote{see, however, |
1215 | the option @code{org-cycle-emulate-tab}.}. When the cursor is at the | |
1216 | beginning of the buffer and the first line is not a headline, then | |
1217 | @key{TAB} actually runs global cycling (see below)@footnote{see the | |
1218 | option @code{org-cycle-global-at-bob}.}. Also when called with a prefix | |
1219 | argument (@kbd{C-u @key{TAB}}), global cycling is invoked. | |
1220 | ||
1221 | @cindex global visibility states | |
1222 | @cindex global cycling | |
1223 | @cindex overview, global visibility state | |
1224 | @cindex contents, global visibility state | |
1225 | @cindex show all, global visibility state | |
afe98dfa | 1226 | @orgcmd{S-@key{TAB},org-global-cycle} |
4009494e GM |
1227 | @itemx C-u @key{TAB} |
1228 | @emph{Global cycling}: Rotate the entire buffer among the states | |
1229 | ||
1230 | @example | |
1231 | ,-> OVERVIEW -> CONTENTS -> SHOW ALL --. | |
1232 | '--------------------------------------' | |
1233 | @end example | |
1234 | ||
a7808fba CD |
1235 | When @kbd{S-@key{TAB}} is called with a numeric prefix argument N, the |
1236 | CONTENTS view up to headlines of level N will be shown. Note that inside | |
1237 | tables, @kbd{S-@key{TAB}} jumps to the previous field. | |
4009494e GM |
1238 | |
1239 | @cindex show all, command | |
afe98dfa | 1240 | @orgcmd{C-u C-u C-u @key{TAB},show-all} |
864c9740 | 1241 | Show all, including drawers. |
afe98dfa | 1242 | @orgcmd{C-c C-r,org-reveal} |
a7808fba CD |
1243 | Reveal context around point, showing the current entry, the following heading |
1244 | and the hierarchy above. Useful for working near a location that has been | |
1245 | exposed by a sparse tree command (@pxref{Sparse trees}) or an agenda command | |
1246 | (@pxref{Agenda commands}). With a prefix argument show, on each | |
27e428e7 | 1247 | level, all sibling headings. With a double prefix argument, also show the |
e66ba1df | 1248 | entire subtree of the parent. |
afe98dfa | 1249 | @orgcmd{C-c C-k,show-branches} |
86fbb8ca | 1250 | Expose all the headings of the subtree, CONTENT view for just one subtree. |
afe98dfa | 1251 | @orgcmd{C-c C-x b,org-tree-to-indirect-buffer} |
4009494e GM |
1252 | Show the current subtree in an indirect buffer@footnote{The indirect |
1253 | buffer | |
1254 | @ifinfo | |
1255 | (@pxref{Indirect Buffers,,,emacs,GNU Emacs Manual}) | |
1256 | @end ifinfo | |
1257 | @ifnotinfo | |
1258 | (see the Emacs manual for more information about indirect buffers) | |
1259 | @end ifnotinfo | |
1260 | will contain the entire buffer, but will be narrowed to the current | |
1261 | tree. Editing the indirect buffer will also change the original buffer, | |
a7808fba CD |
1262 | but without affecting visibility in that buffer.}. With a numeric |
1263 | prefix argument N, go up to level N and then take that tree. If N is | |
1264 | negative then go up that many levels. With a @kbd{C-u} prefix, do not remove | |
4009494e | 1265 | the previously used indirect buffer. |
ce57c2fe BG |
1266 | @orgcmd{C-c C-x v,org-copy-visible} |
1267 | Copy the @i{visible} text in the region into the kill ring. | |
4009494e GM |
1268 | @end table |
1269 | ||
c8d0cf5c CD |
1270 | @vindex org-startup-folded |
1271 | @cindex @code{overview}, STARTUP keyword | |
1272 | @cindex @code{content}, STARTUP keyword | |
1273 | @cindex @code{showall}, STARTUP keyword | |
7006d207 | 1274 | @cindex @code{showeverything}, STARTUP keyword |
c8d0cf5c | 1275 | |
a7808fba | 1276 | When Emacs first visits an Org file, the global state is set to |
ce57c2fe | 1277 | OVERVIEW, i.e.@: only the top level headlines are visible. This can be |
4009494e GM |
1278 | configured through the variable @code{org-startup-folded}, or on a |
1279 | per-file basis by adding one of the following lines anywhere in the | |
1280 | buffer: | |
1281 | ||
1282 | @example | |
1283 | #+STARTUP: overview | |
1284 | #+STARTUP: content | |
1285 | #+STARTUP: showall | |
7006d207 | 1286 | #+STARTUP: showeverything |
4009494e GM |
1287 | @end example |
1288 | ||
c8d0cf5c | 1289 | @cindex property, VISIBILITY |
b349f79f | 1290 | @noindent |
a50253cc | 1291 | Furthermore, any entries with a @samp{VISIBILITY} property (@pxref{Properties |
b349f79f CD |
1292 | and Columns}) will get their visibility adapted accordingly. Allowed values |
1293 | for this property are @code{folded}, @code{children}, @code{content}, and | |
1294 | @code{all}. | |
afe98dfa CD |
1295 | @table @asis |
1296 | @orgcmd{C-u C-u @key{TAB},org-set-startup-visibility} | |
ce57c2fe | 1297 | Switch back to the startup visibility of the buffer, i.e.@: whatever is |
b349f79f CD |
1298 | requested by startup options and @samp{VISIBILITY} properties in individual |
1299 | entries. | |
1300 | @end table | |
1301 | ||
a7808fba | 1302 | @node Motion, Structure editing, Visibility cycling, Document Structure |
4009494e GM |
1303 | @section Motion |
1304 | @cindex motion, between headlines | |
1305 | @cindex jumping, to headlines | |
1306 | @cindex headline navigation | |
1307 | The following commands jump to other headlines in the buffer. | |
1308 | ||
afe98dfa CD |
1309 | @table @asis |
1310 | @orgcmd{C-c C-n,outline-next-visible-heading} | |
4009494e | 1311 | Next heading. |
afe98dfa | 1312 | @orgcmd{C-c C-p,outline-previous-visible-heading} |
4009494e | 1313 | Previous heading. |
afe98dfa | 1314 | @orgcmd{C-c C-f,org-forward-same-level} |
4009494e | 1315 | Next heading same level. |
afe98dfa | 1316 | @orgcmd{C-c C-b,org-backward-same-level} |
4009494e | 1317 | Previous heading same level. |
afe98dfa | 1318 | @orgcmd{C-c C-u,outline-up-heading} |
4009494e | 1319 | Backward to higher level heading. |
afe98dfa | 1320 | @orgcmd{C-c C-j,org-goto} |
4009494e GM |
1321 | Jump to a different place without changing the current outline |
1322 | visibility. Shows the document structure in a temporary buffer, where | |
1323 | you can use the following keys to find your destination: | |
c8d0cf5c | 1324 | @vindex org-goto-auto-isearch |
4009494e GM |
1325 | @example |
1326 | @key{TAB} @r{Cycle visibility.} | |
1327 | @key{down} / @key{up} @r{Next/previous visible headline.} | |
71d35b24 CD |
1328 | @key{RET} @r{Select this location.} |
1329 | @kbd{/} @r{Do a Sparse-tree search} | |
1330 | @r{The following keys work if you turn off @code{org-goto-auto-isearch}} | |
4009494e GM |
1331 | n / p @r{Next/previous visible headline.} |
1332 | f / b @r{Next/previous headline same level.} | |
1333 | u @r{One level up.} | |
1334 | 0-9 @r{Digit argument.} | |
71d35b24 | 1335 | q @r{Quit} |
4009494e | 1336 | @end example |
c8d0cf5c CD |
1337 | @vindex org-goto-interface |
1338 | @noindent | |
1339 | See also the variable @code{org-goto-interface}. | |
4009494e GM |
1340 | @end table |
1341 | ||
a351880d | 1342 | @node Structure editing, Sparse trees, Motion, Document Structure |
4009494e GM |
1343 | @section Structure editing |
1344 | @cindex structure editing | |
1345 | @cindex headline, promotion and demotion | |
1346 | @cindex promotion, of subtrees | |
1347 | @cindex demotion, of subtrees | |
1348 | @cindex subtree, cut and paste | |
1349 | @cindex pasting, of subtrees | |
1350 | @cindex cutting, of subtrees | |
1351 | @cindex copying, of subtrees | |
6eb02347 | 1352 | @cindex sorting, of subtrees |
4009494e GM |
1353 | @cindex subtrees, cut and paste |
1354 | ||
afe98dfa CD |
1355 | @table @asis |
1356 | @orgcmd{M-@key{RET},org-insert-heading} | |
c8d0cf5c | 1357 | @vindex org-M-RET-may-split-line |
ce57c2fe BG |
1358 | Insert new heading with same level as current. If the cursor is in a plain |
1359 | list item, a new item is created (@pxref{Plain lists}). To force creation of | |
1360 | a new headline, use a prefix argument. When this command is used in the | |
1361 | middle of a line, the line is split and the rest of the line becomes the new | |
1362 | headline@footnote{If you do not want the line to be split, customize the | |
1363 | variable @code{org-M-RET-may-split-line}.}. If the command is used at the | |
1364 | beginning of a headline, the new headline is created before the current line. | |
1365 | If at the beginning of any other line, the content of that line is made the | |
1366 | new heading. If the command is used at the end of a folded subtree (i.e.@: | |
1367 | behind the ellipses at the end of a headline), then a headline like the | |
1368 | current one will be inserted after the end of the subtree. | |
afe98dfa | 1369 | @orgcmd{C-@key{RET},org-insert-heading-respect-content} |
71d35b24 CD |
1370 | Just like @kbd{M-@key{RET}}, except when adding a new heading below the |
1371 | current heading, the new heading is placed after the body instead of before | |
1372 | it. This command works from anywhere in the entry. | |
afe98dfa | 1373 | @orgcmd{M-S-@key{RET},org-insert-todo-heading} |
c8d0cf5c CD |
1374 | @vindex org-treat-insert-todo-heading-as-state-change |
1375 | Insert new TODO entry with same level as current heading. See also the | |
1376 | variable @code{org-treat-insert-todo-heading-as-state-change}. | |
afe98dfa | 1377 | @orgcmd{C-S-@key{RET},org-insert-todo-heading-respect-content} |
864c9740 CD |
1378 | Insert new TODO entry with same level as current heading. Like |
1379 | @kbd{C-@key{RET}}, the new headline will be inserted after the current | |
1380 | subtree. | |
afe98dfa | 1381 | @orgcmd{@key{TAB},org-cycle} |
a351880d CD |
1382 | In a new entry with no text yet, the first @key{TAB} demotes the entry to |
1383 | become a child of the previous one. The next @key{TAB} makes it a parent, | |
1384 | and so on, all the way to top level. Yet another @key{TAB}, and you are back | |
1385 | to the initial level. | |
afe98dfa | 1386 | @orgcmd{M-@key{left},org-do-promote} |
4009494e | 1387 | Promote current heading by one level. |
afe98dfa | 1388 | @orgcmd{M-@key{right},org-do-demote} |
4009494e | 1389 | Demote current heading by one level. |
afe98dfa | 1390 | @orgcmd{M-S-@key{left},org-promote-subtree} |
4009494e | 1391 | Promote the current subtree by one level. |
afe98dfa | 1392 | @orgcmd{M-S-@key{right},org-demote-subtree} |
4009494e | 1393 | Demote the current subtree by one level. |
afe98dfa | 1394 | @orgcmd{M-S-@key{up},org-move-subtree-up} |
4009494e GM |
1395 | Move subtree up (swap with previous subtree of same |
1396 | level). | |
afe98dfa | 1397 | @orgcmd{M-S-@key{down},org-move-subtree-down} |
4009494e | 1398 | Move subtree down (swap with next subtree of same level). |
afe98dfa | 1399 | @orgcmd{C-c C-x C-w,org-cut-subtree} |
ce57c2fe | 1400 | Kill subtree, i.e.@: remove it from buffer but save in kill ring. |
a7808fba | 1401 | With a numeric prefix argument N, kill N sequential subtrees. |
afe98dfa | 1402 | @orgcmd{C-c C-x M-w,org-copy-subtree} |
a7808fba CD |
1403 | Copy subtree to kill ring. With a numeric prefix argument N, copy the N |
1404 | sequential subtrees. | |
afe98dfa | 1405 | @orgcmd{C-c C-x C-y,org-paste-subtree} |
4009494e | 1406 | Yank subtree from kill ring. This does modify the level of the subtree to |
a7808fba CD |
1407 | make sure the tree fits in nicely at the yank position. The yank level can |
1408 | also be specified with a numeric prefix argument, or by yanking after a | |
4009494e | 1409 | headline marker like @samp{****}. |
afe98dfa | 1410 | @orgcmd{C-y,org-yank} |
c8d0cf5c CD |
1411 | @vindex org-yank-adjusted-subtrees |
1412 | @vindex org-yank-folded-subtrees | |
e45e3595 CD |
1413 | Depending on the variables @code{org-yank-adjusted-subtrees} and |
1414 | @code{org-yank-folded-subtrees}, Org's internal @code{yank} command will | |
1415 | paste subtrees folded and in a clever way, using the same command as @kbd{C-c | |
55033558 CD |
1416 | C-x C-y}. With the default settings, no level adjustment will take place, |
1417 | but the yanked tree will be folded unless doing so would swallow text | |
1418 | previously visible. Any prefix argument to this command will force a normal | |
1419 | @code{yank} to be executed, with the prefix passed along. A good way to | |
1420 | force a normal yank is @kbd{C-u C-y}. If you use @code{yank-pop} after a | |
1421 | yank, it will yank previous kill items plainly, without adjustment and | |
1422 | folding. | |
afe98dfa | 1423 | @orgcmd{C-c C-x c,org-clone-subtree-with-time-shift} |
c8d0cf5c CD |
1424 | Clone a subtree by making a number of sibling copies of it. You will be |
1425 | prompted for the number of copies to make, and you can also specify if any | |
1426 | timestamps in the entry should be shifted. This can be useful, for example, | |
1427 | to create a number of tasks related to a series of lectures to prepare. For | |
1428 | more details, see the docstring of the command | |
1429 | @code{org-clone-subtree-with-time-shift}. | |
afe98dfa | 1430 | @orgcmd{C-c C-w,org-refile} |
e45e3595 | 1431 | Refile entry or region to a different location. @xref{Refiling notes}. |
afe98dfa | 1432 | @orgcmd{C-c ^,org-sort-entries-or-items} |
a7808fba CD |
1433 | Sort same-level entries. When there is an active region, all entries in the |
1434 | region will be sorted. Otherwise the children of the current headline are | |
1435 | sorted. The command prompts for the sorting method, which can be | |
c8d0cf5c CD |
1436 | alphabetically, numerically, by time (first timestamp with active preferred, |
1437 | creation time, scheduled time, deadline time), by priority, by TODO keyword | |
1438 | (in the sequence the keywords have been defined in the setup) or by the value | |
1439 | of a property. Reverse sorting is possible as well. You can also supply | |
1440 | your own function to extract the sorting key. With a @kbd{C-u} prefix, | |
153ae947 | 1441 | sorting will be case-sensitive. |
afe98dfa | 1442 | @orgcmd{C-x n s,org-narrow-to-subtree} |
b349f79f | 1443 | Narrow buffer to current subtree. |
ce57c2fe BG |
1444 | @orgcmd{C-x n b,org-narrow-to-block} |
1445 | Narrow buffer to current block. | |
afe98dfa | 1446 | @orgcmd{C-x n w,widen} |
c8d0cf5c | 1447 | Widen buffer to remove narrowing. |
afe98dfa | 1448 | @orgcmd{C-c *,org-toggle-heading} |
55e0839d CD |
1449 | Turn a normal line or plain list item into a headline (so that it becomes a |
1450 | subheading at its location). Also turn a headline into a normal line by | |
1451 | removing the stars. If there is an active region, turn all lines in the | |
1452 | region into headlines. If the first line in the region was an item, turn | |
1453 | only the item lines into headlines. Finally, if the first line is a | |
28a16a1b | 1454 | headline, remove the stars from all headlines in the region. |
4009494e GM |
1455 | @end table |
1456 | ||
1457 | @cindex region, active | |
1458 | @cindex active region | |
c8d0cf5c CD |
1459 | @cindex transient mark mode |
1460 | When there is an active region (Transient Mark mode), promotion and | |
4009494e GM |
1461 | demotion work on all headlines in the region. To select a region of |
1462 | headlines, it is best to place both point and mark at the beginning of a | |
1463 | line, mark at the beginning of the first headline, and point at the line | |
1464 | just after the last headline to change. Note that when the cursor is | |
1465 | inside a table (@pxref{Tables}), the Meta-Cursor keys have different | |
1466 | functionality. | |
1467 | ||
28a16a1b | 1468 | |
a351880d | 1469 | @node Sparse trees, Plain lists, Structure editing, Document Structure |
4009494e GM |
1470 | @section Sparse trees |
1471 | @cindex sparse trees | |
1472 | @cindex trees, sparse | |
1473 | @cindex folding, sparse trees | |
1474 | @cindex occur, command | |
1475 | ||
c8d0cf5c CD |
1476 | @vindex org-show-hierarchy-above |
1477 | @vindex org-show-following-heading | |
1478 | @vindex org-show-siblings | |
1479 | @vindex org-show-entry-below | |
e66ba1df | 1480 | An important feature of Org mode is the ability to construct @emph{sparse |
b349f79f CD |
1481 | trees} for selected information in an outline tree, so that the entire |
1482 | document is folded as much as possible, but the selected information is made | |
1483 | visible along with the headline structure above it@footnote{See also the | |
1484 | variables @code{org-show-hierarchy-above}, @code{org-show-following-heading}, | |
1485 | @code{org-show-siblings}, and @code{org-show-entry-below} for detailed | |
1486 | control on how much context is shown around each match.}. Just try it out | |
1487 | and you will see immediately how it works. | |
dbc28aaa | 1488 | |
e66ba1df | 1489 | Org mode contains several commands creating such trees, all these |
dbc28aaa | 1490 | commands can be accessed through a dispatcher: |
4009494e | 1491 | |
afe98dfa CD |
1492 | @table @asis |
1493 | @orgcmd{C-c /,org-sparse-tree} | |
dbc28aaa | 1494 | This prompts for an extra key to select a sparse-tree creating command. |
acedf35c | 1495 | @orgcmd{C-c / r,org-occur} |
c8d0cf5c | 1496 | @vindex org-remove-highlights-with-change |
ce57c2fe | 1497 | Prompts for a regexp and shows a sparse tree with all matches. If |
b349f79f CD |
1498 | the match is in a headline, the headline is made visible. If the match is in |
1499 | the body of an entry, headline and body are made visible. In order to | |
1500 | provide minimal context, also the full hierarchy of headlines above the match | |
1501 | is shown, as well as the headline following the match. Each match is also | |
1502 | highlighted; the highlights disappear when the buffer is changed by an | |
c8d0cf5c | 1503 | editing command@footnote{This depends on the option |
b349f79f CD |
1504 | @code{org-remove-highlights-with-change}}, or by pressing @kbd{C-c C-c}. |
1505 | When called with a @kbd{C-u} prefix argument, previous highlights are kept, | |
1506 | so several calls to this command can be stacked. | |
ce57c2fe BG |
1507 | @orgcmdkkc{M-g n,M-g M-n,next-error} |
1508 | Jump to the next sparse tree match in this buffer. | |
1509 | @orgcmdkkc{M-g p,M-g M-p,previous-error} | |
1510 | Jump to the previous sparse tree match in this buffer. | |
4009494e | 1511 | @end table |
dbc28aaa | 1512 | |
ce57c2fe | 1513 | |
4009494e | 1514 | @noindent |
c8d0cf5c | 1515 | @vindex org-agenda-custom-commands |
4009494e GM |
1516 | For frequently used sparse trees of specific search strings, you can |
1517 | use the variable @code{org-agenda-custom-commands} to define fast | |
1518 | keyboard access to specific sparse trees. These commands will then be | |
1519 | accessible through the agenda dispatcher (@pxref{Agenda dispatcher}). | |
1520 | For example: | |
1521 | ||
1522 | @lisp | |
1523 | (setq org-agenda-custom-commands | |
1524 | '(("f" occur-tree "FIXME"))) | |
1525 | @end lisp | |
1526 | ||
1527 | @noindent will define the key @kbd{C-c a f} as a shortcut for creating | |
1528 | a sparse tree matching the string @samp{FIXME}. | |
1529 | ||
dbc28aaa CD |
1530 | The other sparse tree commands select headings based on TODO keywords, |
1531 | tags, or properties and will be discussed later in this manual. | |
4009494e GM |
1532 | |
1533 | @kindex C-c C-e v | |
1534 | @cindex printing sparse trees | |
1535 | @cindex visible text, printing | |
1536 | To print a sparse tree, you can use the Emacs command | |
1537 | @code{ps-print-buffer-with-faces} which does not print invisible parts | |
1538 | of the document @footnote{This does not work under XEmacs, because | |
1539 | XEmacs uses selective display for outlining, not text properties.}. | |
1540 | Or you can use the command @kbd{C-c C-e v} to export only the visible | |
1541 | part of the document and print the resulting file. | |
1542 | ||
a7808fba | 1543 | @node Plain lists, Drawers, Sparse trees, Document Structure |
4009494e GM |
1544 | @section Plain lists |
1545 | @cindex plain lists | |
1546 | @cindex lists, plain | |
1547 | @cindex lists, ordered | |
1548 | @cindex ordered lists | |
1549 | ||
1550 | Within an entry of the outline tree, hand-formatted lists can provide | |
afe98dfa CD |
1551 | additional structure. They also provide a way to create lists of checkboxes |
1552 | (@pxref{Checkboxes}). Org supports editing such lists, and every exporter | |
1553 | (@pxref{Exporting}) can parse and format them. | |
4009494e | 1554 | |
b349f79f CD |
1555 | Org knows ordered lists, unordered lists, and description lists. |
1556 | @itemize @bullet | |
1557 | @item | |
1558 | @emph{Unordered} list items start with @samp{-}, @samp{+}, or | |
1559 | @samp{*}@footnote{When using @samp{*} as a bullet, lines must be indented or | |
1560 | they will be seen as top-level headlines. Also, when you are hiding leading | |
ce57c2fe BG |
1561 | stars to get a clean outline view, plain list items starting with a star may |
1562 | be hard to distinguish from true headlines. In short: even though @samp{*} | |
1563 | is supported, it may be better to not use it for plain list items.} as | |
1564 | bullets. | |
b349f79f | 1565 | @item |
afe98dfa | 1566 | @vindex org-plain-list-ordered-item-terminator |
ce57c2fe | 1567 | @vindex org-alphabetical-lists |
b349f79f | 1568 | @emph{Ordered} list items start with a numeral followed by either a period or |
afe98dfa CD |
1569 | a right parenthesis@footnote{You can filter out any of them by configuring |
1570 | @code{org-plain-list-ordered-item-terminator}.}, such as @samp{1.} or | |
ce57c2fe BG |
1571 | @samp{1)}@footnote{You can also get @samp{a.}, @samp{A.}, @samp{a)} and |
1572 | @samp{A)} by configuring @code{org-alphabetical-lists}. To minimize | |
1573 | confusion with normal text, those are limited to one character only. Beyond | |
1574 | that limit, bullets will automatically fallback to numbers.}. If you want a | |
1575 | list to start with a different value (e.g.@: 20), start the text of the item | |
1576 | with @code{[@@20]}@footnote{If there's a checkbox in the item, the cookie | |
1577 | must be put @emph{before} the checkbox. If you have activated alphabetical | |
1578 | lists, you can also use counters like @code{[@@b]}.}. Those constructs can | |
1579 | be used in any item of the list in order to enforce a particular numbering. | |
b349f79f | 1580 | @item |
a351880d | 1581 | @emph{Description} list items are unordered list items, and contain the |
ce57c2fe | 1582 | separator @samp{ :: } to distinguish the description @emph{term} from the |
a50253cc | 1583 | description. |
b349f79f CD |
1584 | @end itemize |
1585 | ||
1586 | Items belonging to the same list must have the same indentation on the first | |
1587 | line. In particular, if an ordered list reaches number @samp{10.}, then the | |
1588 | 2--digit numbers must be written left-aligned with the other numbers in the | |
ce57c2fe BG |
1589 | list. An item ends before the next line that is less or equally indented |
1590 | than its bullet/number. | |
afe98dfa | 1591 | |
afe98dfa | 1592 | @vindex org-empty-line-terminates-plain-lists |
153ae947 BG |
1593 | A list ends whenever every item has ended, which means before any line less |
1594 | or equally indented than items at top level. It also ends before two blank | |
ce57c2fe | 1595 | lines@footnote{See also @code{org-empty-line-terminates-plain-lists}.}. In |
153ae947 | 1596 | that case, all items are closed. Here is an example: |
4009494e GM |
1597 | |
1598 | @example | |
1599 | @group | |
1600 | ** Lord of the Rings | |
1601 | My favorite scenes are (in this order) | |
1602 | 1. The attack of the Rohirrim | |
a50253cc | 1603 | 2. Eowyn's fight with the witch king |
4009494e GM |
1604 | + this was already my favorite scene in the book |
1605 | + I really like Miranda Otto. | |
1606 | 3. Peter Jackson being shot by Legolas | |
afe98dfa | 1607 | - on DVD only |
ce57c2fe | 1608 | He makes a really funny face when it happens. |
a50253cc | 1609 | But in the end, no individual scenes matter but the film as a whole. |
b349f79f | 1610 | Important actors in this film are: |
a50253cc | 1611 | - @b{Elijah Wood} :: He plays Frodo |
ac20fddf | 1612 | - @b{Sean Austin} :: He plays Sam, Frodo's friend. I still remember |
c8d0cf5c | 1613 | him very well from his role as Mikey Walsh in @i{The Goonies}. |
4009494e GM |
1614 | @end group |
1615 | @end example | |
1616 | ||
c8d0cf5c CD |
1617 | Org supports these lists by tuning filling and wrapping commands to deal with |
1618 | them correctly@footnote{Org only changes the filling settings for Emacs. For | |
1619 | XEmacs, you should use Kyle E. Jones' @file{filladapt.el}. To turn this on, | |
1620 | put into @file{.emacs}: @code{(require 'filladapt)}}, and by exporting them | |
1621 | properly (@pxref{Exporting}). Since indentation is what governs the | |
1622 | structure of these lists, many structural constructs like @code{#+BEGIN_...} | |
ce57c2fe | 1623 | blocks can be indented to signal that they belong to a particular item. |
4009494e | 1624 | |
86fbb8ca | 1625 | @vindex org-list-demote-modify-bullet |
ce57c2fe | 1626 | @vindex org-list-indent-offset |
86fbb8ca CD |
1627 | If you find that using a different bullet for a sub-list (than that used for |
1628 | the current list-level) improves readability, customize the variable | |
ce57c2fe BG |
1629 | @code{org-list-demote-modify-bullet}. To get a greater difference of |
1630 | indentation between items and theirs sub-items, customize | |
1631 | @code{org-list-indent-offset}. | |
86fbb8ca | 1632 | |
afe98dfa CD |
1633 | @vindex org-list-automatic-rules |
1634 | The following commands act on items when the cursor is in the first line of | |
1635 | an item (the line with the bullet or number). Some of them imply the | |
acedf35c | 1636 | application of automatic rules to keep list structure intact. If some of |
afe98dfa CD |
1637 | these actions get in your way, configure @code{org-list-automatic-rules} |
1638 | to disable them individually. | |
4009494e | 1639 | |
afe98dfa CD |
1640 | @table @asis |
1641 | @orgcmd{@key{TAB},org-cycle} | |
e66ba1df | 1642 | @cindex cycling, in plain lists |
c8d0cf5c CD |
1643 | @vindex org-cycle-include-plain-lists |
1644 | Items can be folded just like headline levels. Normally this works only if | |
1645 | the cursor is on a plain list item. For more details, see the variable | |
acedf35c CD |
1646 | @code{org-cycle-include-plain-lists}. If this variable is set to |
1647 | @code{integrate}, plain list items will be treated like low-level | |
e66ba1df BG |
1648 | headlines. The level of an item is then given by the indentation of the |
1649 | bullet/number. Items are always subordinate to real headlines, however; the | |
1650 | hierarchies remain completely separated. In a new item with no text yet, the | |
1651 | first @key{TAB} demotes the item to become a child of the previous | |
1652 | one. Subsequent @key{TAB}s move the item to meaningful levels in the list | |
1653 | and eventually get it back to its initial position. | |
afe98dfa | 1654 | @orgcmd{M-@key{RET},org-insert-heading} |
c8d0cf5c | 1655 | @vindex org-M-RET-may-split-line |
afe98dfa | 1656 | @vindex org-list-automatic-rules |
a7808fba CD |
1657 | Insert new item at current level. With a prefix argument, force a new |
1658 | heading (@pxref{Structure editing}). If this command is used in the middle | |
ce57c2fe BG |
1659 | of an item, that item is @emph{split} in two, and the second part becomes the |
1660 | new item@footnote{If you do not want the item to be split, customize the | |
1661 | variable @code{org-M-RET-may-split-line}.}. If this command is executed | |
1662 | @emph{before item's body}, the new item is created @emph{before} the current | |
1663 | one. | |
e66ba1df BG |
1664 | @end table |
1665 | ||
1666 | @table @kbd | |
4009494e | 1667 | @kindex M-S-@key{RET} |
e66ba1df | 1668 | @item M-S-RET |
4009494e | 1669 | Insert a new item with a checkbox (@pxref{Checkboxes}). |
4009494e | 1670 | @kindex S-@key{down} |
e66ba1df BG |
1671 | @item S-up |
1672 | @itemx S-down | |
3da3282e | 1673 | @cindex shift-selection-mode |
c8d0cf5c | 1674 | @vindex org-support-shift-select |
ce57c2fe BG |
1675 | @vindex org-list-use-circular-motion |
1676 | Jump to the previous/next item in the current list@footnote{If you want to | |
1677 | cycle around items that way, you may customize | |
1678 | @code{org-list-use-circular-motion}.}, but only if | |
3da3282e CD |
1679 | @code{org-support-shift-select} is off. If not, you can still use paragraph |
1680 | jumping commands like @kbd{C-@key{up}} and @kbd{C-@key{down}} to quite | |
1681 | similar effect. | |
ce57c2fe BG |
1682 | @kindex M-@key{up} |
1683 | @kindex M-@key{down} | |
e66ba1df BG |
1684 | @item M-up |
1685 | @itemx M-down | |
ce57c2fe BG |
1686 | Move the item including subitems up/down@footnote{See |
1687 | @code{org-liste-use-circular-motion} for a cyclic behavior.} (swap with | |
1688 | previous/next item of same indentation). If the list is ordered, renumbering | |
1689 | is automatic. | |
86fbb8ca CD |
1690 | @kindex M-@key{left} |
1691 | @kindex M-@key{right} | |
e66ba1df BG |
1692 | @item M-left |
1693 | @itemx M-right | |
86fbb8ca | 1694 | Decrease/increase the indentation of an item, leaving children alone. |
4009494e GM |
1695 | @kindex M-S-@key{left} |
1696 | @kindex M-S-@key{right} | |
e66ba1df BG |
1697 | @item M-S-left |
1698 | @itemx M-S-right | |
4009494e | 1699 | Decrease/increase the indentation of the item, including subitems. |
afe98dfa CD |
1700 | Initially, the item tree is selected based on current indentation. When |
1701 | these commands are executed several times in direct succession, the initially | |
1702 | selected region is used, even if the new indentation would imply a different | |
1703 | hierarchy. To use the new hierarchy, break the command chain with a cursor | |
1704 | motion or so. | |
1705 | ||
1706 | As a special case, using this command on the very first item of a list will | |
1707 | move the whole list. This behavior can be disabled by configuring | |
1708 | @code{org-list-automatic-rules}. The global indentation of a list has no | |
1709 | influence on the text @emph{after} the list. | |
4009494e GM |
1710 | @kindex C-c C-c |
1711 | @item C-c C-c | |
1712 | If there is a checkbox (@pxref{Checkboxes}) in the item line, toggle the | |
ce57c2fe BG |
1713 | state of the checkbox. In any case, verify bullets and indentation |
1714 | consistency in the whole list. | |
4009494e | 1715 | @kindex C-c - |
afe98dfa CD |
1716 | @vindex org-plain-list-ordered-item-terminator |
1717 | @vindex org-list-automatic-rules | |
4009494e | 1718 | @item C-c - |
a7808fba | 1719 | Cycle the entire list level through the different itemize/enumerate bullets |
afe98dfa CD |
1720 | (@samp{-}, @samp{+}, @samp{*}, @samp{1.}, @samp{1)}) or a subset of them, |
1721 | depending on @code{org-plain-list-ordered-item-terminator}, the type of list, | |
1722 | and its position@footnote{See @code{bullet} rule in | |
1723 | @code{org-list-automatic-rules} for more information.}. With a numeric | |
1724 | prefix argument N, select the Nth bullet from this list. If there is an | |
ce57c2fe BG |
1725 | active region when calling this, selected text will be changed into an item. |
1726 | With a prefix argument, all lines will be converted to list items. If the | |
1727 | first line already was a list item, any item marker will be removed from the | |
1728 | list. Finally, even without an active region, a normal line will be | |
a7808fba | 1729 | converted into a list item. |
c8d0cf5c CD |
1730 | @kindex C-c * |
1731 | @item C-c * | |
1732 | Turn a plain list item into a headline (so that it becomes a subheading at | |
ce57c2fe BG |
1733 | its location). @xref{Structure editing}, for a detailed explanation. |
1734 | @kindex C-c C-* | |
1735 | @item C-c C-* | |
1736 | Turn the whole plain list into a subtree of the current heading. Checkboxes | |
1737 | (@pxref{Checkboxes}) will become TODO (resp. DONE) keywords when unchecked | |
1738 | (resp. checked). | |
64fb801f CD |
1739 | @kindex S-@key{left} |
1740 | @kindex S-@key{right} | |
e66ba1df | 1741 | @item S-left/right |
c8d0cf5c | 1742 | @vindex org-support-shift-select |
3da3282e CD |
1743 | This command also cycles bullet styles when the cursor in on the bullet or |
1744 | anywhere in an item line, details depending on | |
1745 | @code{org-support-shift-select}. | |
c8d0cf5c CD |
1746 | @kindex C-c ^ |
1747 | @item C-c ^ | |
1748 | Sort the plain list. You will be prompted for the sorting method: | |
1749 | numerically, alphabetically, by time, or by custom function. | |
4009494e GM |
1750 | @end table |
1751 | ||
c8d0cf5c | 1752 | @node Drawers, Blocks, Plain lists, Document Structure |
4009494e GM |
1753 | @section Drawers |
1754 | @cindex drawers | |
c8d0cf5c | 1755 | @cindex #+DRAWERS |
4009494e GM |
1756 | @cindex visibility cycling, drawers |
1757 | ||
c8d0cf5c | 1758 | @vindex org-drawers |
4009494e | 1759 | Sometimes you want to keep information associated with an entry, but you |
e66ba1df | 1760 | normally don't want to see it. For this, Org mode has @emph{drawers}. |
dbc28aaa CD |
1761 | Drawers need to be configured with the variable |
1762 | @code{org-drawers}@footnote{You can define drawers on a per-file basis | |
1763 | with a line like @code{#+DRAWERS: HIDDEN PROPERTIES STATE}}. Drawers | |
4009494e GM |
1764 | look like this: |
1765 | ||
1766 | @example | |
1767 | ** This is a headline | |
1768 | Still outside the drawer | |
1769 | :DRAWERNAME: | |
ce57c2fe | 1770 | This is inside the drawer. |
4009494e GM |
1771 | :END: |
1772 | After the drawer. | |
1773 | @end example | |
1774 | ||
c8d0cf5c CD |
1775 | Visibility cycling (@pxref{Visibility cycling}) on the headline will hide and |
1776 | show the entry, but keep the drawer collapsed to a single line. In order to | |
1777 | look inside the drawer, you need to move the cursor to the drawer line and | |
e66ba1df | 1778 | press @key{TAB} there. Org mode uses the @code{PROPERTIES} drawer for |
c8d0cf5c CD |
1779 | storing properties (@pxref{Properties and Columns}), and you can also arrange |
1780 | for state change notes (@pxref{Tracking TODO state changes}) and clock times | |
ed21c5c8 | 1781 | (@pxref{Clocking work time}) to be stored in a drawer @code{LOGBOOK}. If you |
acedf35c | 1782 | want to store a quick note in the LOGBOOK drawer, in a similar way to state changes, use |
ed21c5c8 CD |
1783 | |
1784 | @table @kbd | |
1785 | @kindex C-c C-z | |
1786 | @item C-c C-z | |
1787 | Add a time-stamped note to the LOGBOOK drawer. | |
1788 | @end table | |
c8d0cf5c CD |
1789 | |
1790 | @node Blocks, Footnotes, Drawers, Document Structure | |
1791 | @section Blocks | |
1792 | ||
1793 | @vindex org-hide-block-startup | |
1794 | @cindex blocks, folding | |
e66ba1df | 1795 | Org mode uses begin...end blocks for various purposes from including source |
c8d0cf5c CD |
1796 | code examples (@pxref{Literal examples}) to capturing time logging |
1797 | information (@pxref{Clocking work time}). These blocks can be folded and | |
1798 | unfolded by pressing TAB in the begin line. You can also get all blocks | |
1799 | folded at startup by configuring the variable @code{org-hide-block-startup} | |
1800 | or on a per-file basis by using | |
4009494e | 1801 | |
c8d0cf5c CD |
1802 | @cindex @code{hideblocks}, STARTUP keyword |
1803 | @cindex @code{nohideblocks}, STARTUP keyword | |
1804 | @example | |
1805 | #+STARTUP: hideblocks | |
1806 | #+STARTUP: nohideblocks | |
1807 | @end example | |
1808 | ||
1809 | @node Footnotes, Orgstruct mode, Blocks, Document Structure | |
55e0839d CD |
1810 | @section Footnotes |
1811 | @cindex footnotes | |
1812 | ||
e66ba1df BG |
1813 | Org mode supports the creation of footnotes. In contrast to the |
1814 | @file{footnote.el} package, Org mode's footnotes are designed for work on a | |
55e0839d | 1815 | larger document, not only for one-off documents like emails. The basic |
ce57c2fe | 1816 | syntax is similar to the one used by @file{footnote.el}, i.e.@: a footnote is |
55e0839d CD |
1817 | defined in a paragraph that is started by a footnote marker in square |
1818 | brackets in column 0, no indentation allowed. If you need a paragraph break | |
acedf35c | 1819 | inside a footnote, use the @LaTeX{} idiom @samp{\par}. The footnote reference |
55e0839d CD |
1820 | is simply the marker in square brackets, inside text. For example: |
1821 | ||
1822 | @example | |
1823 | The Org homepage[fn:1] now looks a lot better than it used to. | |
1824 | ... | |
1825 | [fn:1] The link is: http://orgmode.org | |
1826 | @end example | |
1827 | ||
e66ba1df | 1828 | Org mode extends the number-based syntax to @emph{named} footnotes and |
55e0839d CD |
1829 | optional inline definition. Using plain numbers as markers (as |
1830 | @file{footnote.el} does) is supported for backward compatibility, but not | |
acedf35c | 1831 | encouraged because of possible conflicts with @LaTeX{} snippets (@pxref{Embedded |
e66ba1df | 1832 | @LaTeX{}}). Here are the valid references: |
55e0839d CD |
1833 | |
1834 | @table @code | |
1835 | @item [1] | |
c8d0cf5c | 1836 | A plain numeric footnote marker. Compatible with @file{footnote.el}, but not |
86fbb8ca | 1837 | recommended because something like @samp{[1]} could easily be part of a code |
c8d0cf5c | 1838 | snippet. |
55e0839d CD |
1839 | @item [fn:name] |
1840 | A named footnote reference, where @code{name} is a unique label word, or, for | |
1841 | simplicity of automatic creation, a number. | |
1842 | @item [fn:: This is the inline definition of this footnote] | |
acedf35c | 1843 | A @LaTeX{}-like anonymous footnote where the definition is given directly at the |
55e0839d CD |
1844 | reference point. |
1845 | @item [fn:name: a definition] | |
1846 | An inline definition of a footnote, which also specifies a name for the note. | |
867d4bb3 | 1847 | Since Org allows multiple references to the same note, you can then use |
55e0839d CD |
1848 | @code{[fn:name]} to create additional references. |
1849 | @end table | |
1850 | ||
c8d0cf5c CD |
1851 | @vindex org-footnote-auto-label |
1852 | Footnote labels can be created automatically, or you can create names yourself. | |
55e0839d | 1853 | This is handled by the variable @code{org-footnote-auto-label} and its |
acedf35c | 1854 | corresponding @code{#+STARTUP} keywords. See the docstring of that variable |
55e0839d CD |
1855 | for details. |
1856 | ||
1857 | @noindent The following command handles footnotes: | |
1858 | ||
1859 | @table @kbd | |
1860 | @kindex C-c C-x f | |
1861 | @item C-c C-x f | |
1862 | The footnote action command. | |
1863 | ||
1864 | When the cursor is on a footnote reference, jump to the definition. When it | |
1865 | is at a definition, jump to the (first) reference. | |
1866 | ||
c8d0cf5c CD |
1867 | @vindex org-footnote-define-inline |
1868 | @vindex org-footnote-section | |
1869 | @vindex org-footnote-auto-adjust | |
55e0839d CD |
1870 | Otherwise, create a new footnote. Depending on the variable |
1871 | @code{org-footnote-define-inline}@footnote{The corresponding in-buffer | |
1872 | setting is: @code{#+STARTUP: fninline} or @code{#+STARTUP: nofninline}}, the | |
1873 | definition will be placed right into the text as part of the reference, or | |
1874 | separately into the location determined by the variable | |
1875 | @code{org-footnote-section}. | |
1876 | ||
1877 | When this command is called with a prefix argument, a menu of additional | |
1878 | options is offered: | |
1879 | @example | |
1880 | s @r{Sort the footnote definitions by reference sequence. During editing,} | |
1881 | @r{Org makes no effort to sort footnote definitions into a particular} | |
1882 | @r{sequence. If you want them sorted, use this command, which will} | |
c8d0cf5c CD |
1883 | @r{also move entries according to @code{org-footnote-section}. Automatic} |
1884 | @r{sorting after each insertion/deletion can be configured using the} | |
1885 | @r{variable @code{org-footnote-auto-adjust}.} | |
1886 | r @r{Renumber the simple @code{fn:N} footnotes. Automatic renumbering} | |
1887 | @r{after each insertion/deletion can be configured using the variable} | |
1888 | @r{@code{org-footnote-auto-adjust}.} | |
1889 | S @r{Short for first @code{r}, then @code{s} action.} | |
55e0839d CD |
1890 | n @r{Normalize the footnotes by collecting all definitions (including} |
1891 | @r{inline definitions) into a special section, and then numbering them} | |
1892 | @r{in sequence. The references will then also be numbers. This is} | |
ce57c2fe | 1893 | @r{meant to be the final step before finishing a document (e.g.@: sending} |
55e0839d CD |
1894 | @r{off an email). The exporters do this automatically, and so could} |
1895 | @r{something like @code{message-send-hook}.} | |
1896 | d @r{Delete the footnote at point, and all definitions of and references} | |
1897 | @r{to it.} | |
1898 | @end example | |
c8d0cf5c CD |
1899 | Depending on the variable @code{org-footnote-auto-adjust}@footnote{the |
1900 | corresponding in-buffer options are @code{fnadjust} and @code{nofnadjust}.}, | |
1901 | renumbering and sorting footnotes can be automatic after each insertion or | |
1902 | deletion. | |
1903 | ||
55e0839d CD |
1904 | @kindex C-c C-c |
1905 | @item C-c C-c | |
1906 | If the cursor is on a footnote reference, jump to the definition. If it is a | |
1907 | the definition, jump back to the reference. When called at a footnote | |
1908 | location with a prefix argument, offer the same menu as @kbd{C-c C-x f}. | |
1909 | @kindex C-c C-o | |
1910 | @kindex mouse-1 | |
1911 | @kindex mouse-2 | |
c8d0cf5c | 1912 | @item C-c C-o @r{or} mouse-1/2 |
55e0839d CD |
1913 | Footnote labels are also links to the corresponding definition/reference, and |
1914 | you can use the usual commands to follow these links. | |
1915 | @end table | |
1916 | ||
1917 | @node Orgstruct mode, , Footnotes, Document Structure | |
4009494e | 1918 | @section The Orgstruct minor mode |
a7808fba | 1919 | @cindex Orgstruct mode |
4009494e GM |
1920 | @cindex minor mode for structure editing |
1921 | ||
e66ba1df | 1922 | If you like the intuitive way the Org mode structure editing and list |
c8d0cf5c CD |
1923 | formatting works, you might want to use these commands in other modes like |
1924 | Text mode or Mail mode as well. The minor mode @code{orgstruct-mode} makes | |
1925 | this possible. Toggle the mode with @kbd{M-x orgstruct-mode}, or | |
ce57c2fe | 1926 | turn it on by default, for example in Message mode, with one of: |
4009494e GM |
1927 | |
1928 | @lisp | |
ce57c2fe BG |
1929 | (add-hook 'message-mode-hook 'turn-on-orgstruct) |
1930 | (add-hook 'message-mode-hook 'turn-on-orgstruct++) | |
4009494e GM |
1931 | @end lisp |
1932 | ||
c8d0cf5c CD |
1933 | When this mode is active and the cursor is on a line that looks to Org like a |
1934 | headline or the first line of a list item, most structure editing commands | |
1935 | will work, even if the same keys normally have different functionality in the | |
1936 | major mode you are using. If the cursor is not in one of those special | |
acedf35c | 1937 | lines, Orgstruct mode lurks silently in the shadows. When you use |
c8d0cf5c CD |
1938 | @code{orgstruct++-mode}, Org will also export indentation and autofill |
1939 | settings into that mode, and detect item context after the first line of an | |
1940 | item. | |
4009494e | 1941 | |
a7808fba | 1942 | @node Tables, Hyperlinks, Document Structure, Top |
4009494e GM |
1943 | @chapter Tables |
1944 | @cindex tables | |
1945 | @cindex editing tables | |
1946 | ||
a7808fba | 1947 | Org comes with a fast and intuitive table editor. Spreadsheet-like |
acedf35c | 1948 | calculations are supported using the Emacs @file{calc} package |
153ae947 | 1949 | (@pxref{Top, Calc, , calc, Gnu Emacs Calculator Manual}). |
4009494e GM |
1950 | |
1951 | @menu | |
c0468714 GM |
1952 | * Built-in table editor:: Simple tables |
1953 | * Column width and alignment:: Overrule the automatic settings | |
1954 | * Column groups:: Grouping to trigger vertical lines | |
1955 | * Orgtbl mode:: The table editor as minor mode | |
1956 | * The spreadsheet:: The table editor has spreadsheet capabilities | |
1957 | * Org-Plot:: Plotting from org tables | |
4009494e GM |
1958 | @end menu |
1959 | ||
c8d0cf5c | 1960 | @node Built-in table editor, Column width and alignment, Tables, Tables |
4009494e GM |
1961 | @section The built-in table editor |
1962 | @cindex table editor, built-in | |
1963 | ||
ce57c2fe BG |
1964 | Org makes it easy to format tables in plain ASCII. Any line with @samp{|} as |
1965 | the first non-whitespace character is considered part of a table. @samp{|} | |
1966 | is also the column separator@footnote{To insert a vertical bar into a table | |
1967 | field, use @code{\vert} or, inside a word @code{abc\vert@{@}def}.}. A table | |
1968 | might look like this: | |
4009494e GM |
1969 | |
1970 | @example | |
1971 | | Name | Phone | Age | | |
1972 | |-------+-------+-----| | |
1973 | | Peter | 1234 | 17 | | |
1974 | | Anna | 4321 | 25 | | |
1975 | @end example | |
1976 | ||
1977 | A table is re-aligned automatically each time you press @key{TAB} or | |
1978 | @key{RET} or @kbd{C-c C-c} inside the table. @key{TAB} also moves to | |
1979 | the next field (@key{RET} to the next row) and creates new table rows | |
1980 | at the end of the table or before horizontal lines. The indentation | |
1981 | of the table is set by the first line. Any line starting with | |
1982 | @samp{|-} is considered as a horizontal separator line and will be | |
1983 | expanded on the next re-align to span the whole table width. So, to | |
1984 | create the above table, you would only type | |
1985 | ||
1986 | @example | |
1987 | |Name|Phone|Age| | |
1988 | |- | |
1989 | @end example | |
1990 | ||
1991 | @noindent and then press @key{TAB} to align the table and start filling in | |
55e0839d CD |
1992 | fields. Even faster would be to type @code{|Name|Phone|Age} followed by |
1993 | @kbd{C-c @key{RET}}. | |
4009494e | 1994 | |
c8d0cf5c CD |
1995 | @vindex org-enable-table-editor |
1996 | @vindex org-table-auto-blank-field | |
a7808fba | 1997 | When typing text into a field, Org treats @key{DEL}, |
4009494e GM |
1998 | @key{Backspace}, and all character keys in a special way, so that |
1999 | inserting and deleting avoids shifting other fields. Also, when | |
2000 | typing @emph{immediately after the cursor was moved into a new field | |
2001 | with @kbd{@key{TAB}}, @kbd{S-@key{TAB}} or @kbd{@key{RET}}}, the | |
2002 | field is automatically made blank. If this behavior is too | |
2003 | unpredictable for you, configure the variables | |
2004 | @code{org-enable-table-editor} and @code{org-table-auto-blank-field}. | |
2005 | ||
2006 | @table @kbd | |
2007 | @tsubheading{Creation and conversion} | |
afe98dfa | 2008 | @orgcmd{C-c |,org-table-create-or-convert-from-region} |
ce57c2fe | 2009 | Convert the active region to table. If every line contains at least one |
4009494e | 2010 | TAB character, the function assumes that the material is tab separated. |
dbc28aaa | 2011 | If every line contains a comma, comma-separated values (CSV) are assumed. |
4009494e | 2012 | If not, lines are split at whitespace into fields. You can use a prefix |
dbc28aaa CD |
2013 | argument to force a specific separator: @kbd{C-u} forces CSV, @kbd{C-u |
2014 | C-u} forces TAB, and a numeric argument N indicates that at least N | |
a7808fba | 2015 | consecutive spaces, or alternatively a TAB will be the separator. |
28a16a1b | 2016 | @* |
a7808fba | 2017 | If there is no active region, this command creates an empty Org |
ce57c2fe | 2018 | table. But it is easier just to start typing, like |
4009494e GM |
2019 | @kbd{|Name|Phone|Age @key{RET} |- @key{TAB}}. |
2020 | ||
2021 | @tsubheading{Re-aligning and field motion} | |
acedf35c | 2022 | @orgcmd{C-c C-c,org-table-align} |
4009494e GM |
2023 | Re-align the table without moving the cursor. |
2024 | @c | |
acedf35c | 2025 | @orgcmd{<TAB>,org-table-next-field} |
4009494e GM |
2026 | Re-align the table, move to the next field. Creates a new row if |
2027 | necessary. | |
2028 | @c | |
acedf35c | 2029 | @orgcmd{S-@key{TAB},org-table-previous-field} |
4009494e GM |
2030 | Re-align, move to previous field. |
2031 | @c | |
acedf35c | 2032 | @orgcmd{@key{RET},org-table-next-row} |
4009494e GM |
2033 | Re-align the table and move down to next row. Creates a new row if |
2034 | necessary. At the beginning or end of a line, @key{RET} still does | |
2035 | NEWLINE, so it can be used to split a table. | |
c8d0cf5c | 2036 | @c |
acedf35c | 2037 | @orgcmd{M-a,org-table-beginning-of-field} |
c8d0cf5c | 2038 | Move to beginning of the current table field, or on to the previous field. |
acedf35c | 2039 | @orgcmd{M-e,org-table-end-of-field} |
c8d0cf5c | 2040 | Move to end of the current table field, or on to the next field. |
4009494e GM |
2041 | |
2042 | @tsubheading{Column and row editing} | |
acedf35c | 2043 | @orgcmdkkcc{M-@key{left},M-@key{right},org-table-move-column-left,org-table-move-column-right} |
4009494e GM |
2044 | Move the current column left/right. |
2045 | @c | |
acedf35c | 2046 | @orgcmd{M-S-@key{left},org-table-delete-column} |
4009494e GM |
2047 | Kill the current column. |
2048 | @c | |
acedf35c | 2049 | @orgcmd{M-S-@key{right},org-table-insert-column} |
4009494e GM |
2050 | Insert a new column to the left of the cursor position. |
2051 | @c | |
acedf35c | 2052 | @orgcmdkkcc{M-@key{up},M-@key{down},org-table-move-row-up,org-table-move-row-down} |
4009494e GM |
2053 | Move the current row up/down. |
2054 | @c | |
acedf35c | 2055 | @orgcmd{M-S-@key{up},org-table-kill-row} |
4009494e GM |
2056 | Kill the current row or horizontal line. |
2057 | @c | |
acedf35c | 2058 | @orgcmd{M-S-@key{down},org-table-insert-row} |
a7808fba CD |
2059 | Insert a new row above the current row. With a prefix argument, the line is |
2060 | created below the current one. | |
4009494e | 2061 | @c |
acedf35c | 2062 | @orgcmd{C-c -,org-table-insert-hline} |
2096a1b6 | 2063 | Insert a horizontal line below current row. With a prefix argument, the line |
4009494e GM |
2064 | is created above the current line. |
2065 | @c | |
acedf35c | 2066 | @orgcmd{C-c @key{RET},org-table-hline-and-move} |
2096a1b6 | 2067 | Insert a horizontal line below current row, and move the cursor into the row |
55e0839d CD |
2068 | below that line. |
2069 | @c | |
acedf35c | 2070 | @orgcmd{C-c ^,org-table-sort-lines} |
4009494e GM |
2071 | Sort the table lines in the region. The position of point indicates the |
2072 | column to be used for sorting, and the range of lines is the range | |
2073 | between the nearest horizontal separator lines, or the entire table. If | |
2074 | point is before the first column, you will be prompted for the sorting | |
2075 | column. If there is an active region, the mark specifies the first line | |
2076 | and the sorting column, while point should be in the last line to be | |
2077 | included into the sorting. The command prompts for the sorting type | |
2078 | (alphabetically, numerically, or by time). When called with a prefix | |
2079 | argument, alphabetic sorting will be case-sensitive. | |
2080 | ||
2081 | @tsubheading{Regions} | |
acedf35c | 2082 | @orgcmd{C-c C-x M-w,org-table-copy-region} |
c8d0cf5c CD |
2083 | Copy a rectangular region from a table to a special clipboard. Point and |
2084 | mark determine edge fields of the rectangle. If there is no active region, | |
2085 | copy just the current field. The process ignores horizontal separator lines. | |
4009494e | 2086 | @c |
acedf35c | 2087 | @orgcmd{C-c C-x C-w,org-table-cut-region} |
4009494e GM |
2088 | Copy a rectangular region from a table to a special clipboard, and |
2089 | blank all fields in the rectangle. So this is the ``cut'' operation. | |
2090 | @c | |
acedf35c | 2091 | @orgcmd{C-c C-x C-y,org-table-paste-rectangle} |
4009494e | 2092 | Paste a rectangular region into a table. |
864c9740 | 2093 | The upper left corner ends up in the current field. All involved fields |
4009494e GM |
2094 | will be overwritten. If the rectangle does not fit into the present table, |
2095 | the table is enlarged as needed. The process ignores horizontal separator | |
2096 | lines. | |
2097 | @c | |
acedf35c CD |
2098 | @orgcmd{M-@key{RET},org-table-wrap-region} |
2099 | Split the current field at the cursor position and move the rest to the line | |
2100 | below. If there is an active region, and both point and mark are in the same | |
2101 | column, the text in the column is wrapped to minimum width for the given | |
2102 | number of lines. A numeric prefix argument may be used to change the number | |
2103 | of desired lines. If there is no region, but you specify a prefix argument, | |
2104 | the current field is made blank, and the content is appended to the field | |
2105 | above. | |
4009494e GM |
2106 | |
2107 | @tsubheading{Calculations} | |
2108 | @cindex formula, in tables | |
2109 | @cindex calculations, in tables | |
2110 | @cindex region, active | |
2111 | @cindex active region | |
c8d0cf5c | 2112 | @cindex transient mark mode |
acedf35c | 2113 | @orgcmd{C-c +,org-table-sum} |
4009494e GM |
2114 | Sum the numbers in the current column, or in the rectangle defined by |
2115 | the active region. The result is shown in the echo area and can | |
2116 | be inserted with @kbd{C-y}. | |
2117 | @c | |
acedf35c | 2118 | @orgcmd{S-@key{RET},org-table-copy-down} |
c8d0cf5c | 2119 | @vindex org-table-copy-increment |
864c9740 CD |
2120 | When current field is empty, copy from first non-empty field above. When not |
2121 | empty, copy current field down to next row and move cursor along with it. | |
2122 | Depending on the variable @code{org-table-copy-increment}, integer field | |
2123 | values will be incremented during copy. Integers that are too large will not | |
a50253cc | 2124 | be incremented. Also, a @code{0} prefix argument temporarily disables the |
c8d0cf5c CD |
2125 | increment. This key is also used by shift-selection and related modes |
2126 | (@pxref{Conflicts}). | |
4009494e GM |
2127 | |
2128 | @tsubheading{Miscellaneous} | |
acedf35c | 2129 | @orgcmd{C-c `,org-table-edit-field} |
c8d0cf5c CD |
2130 | Edit the current field in a separate window. This is useful for fields that |
2131 | are not fully visible (@pxref{Column width and alignment}). When called with | |
2132 | a @kbd{C-u} prefix, just make the full field visible, so that it can be | |
ce57c2fe BG |
2133 | edited in place. When called with two @kbd{C-u} prefixes, make the editor |
2134 | window follow the cursor through the table and always show the current | |
2135 | field. The follow mode exits automatically when the cursor leaves the table, | |
2136 | or when you repeat this command with @kbd{C-u C-u C-c `}. | |
4009494e | 2137 | @c |
4009494e | 2138 | @item M-x org-table-import |
c8d0cf5c CD |
2139 | Import a file as a table. The table should be TAB or whitespace |
2140 | separated. Use, for example, to import a spreadsheet table or data | |
dbc28aaa CD |
2141 | from a database, because these programs generally can write |
2142 | TAB-separated text files. This command works by inserting the file into | |
2143 | the buffer and then converting the region to a table. Any prefix | |
2144 | argument is passed on to the converter, which uses it to determine the | |
2145 | separator. | |
acedf35c | 2146 | @orgcmd{C-c |,org-table-create-or-convert-from-region} |
a7808fba | 2147 | Tables can also be imported by pasting tabular text into the Org |
4009494e | 2148 | buffer, selecting the pasted text with @kbd{C-x C-x} and then using the |
44ce9197 | 2149 | @kbd{C-c |} command (see above under @i{Creation and conversion}). |
4009494e GM |
2150 | @c |
2151 | @item M-x org-table-export | |
acedf35c | 2152 | @findex org-table-export |
c8d0cf5c CD |
2153 | @vindex org-table-export-default-format |
2154 | Export the table, by default as a TAB-separated file. Use for data | |
a7808fba CD |
2155 | exchange with, for example, spreadsheet or database programs. The format |
2156 | used to export the file can be configured in the variable | |
2157 | @code{org-table-export-default-format}. You may also use properties | |
2158 | @code{TABLE_EXPORT_FILE} and @code{TABLE_EXPORT_FORMAT} to specify the file | |
b349f79f CD |
2159 | name and the format for table export in a subtree. Org supports quite |
2160 | general formats for exported tables. The exporter format is the same as the | |
c8d0cf5c | 2161 | format used by Orgtbl radio tables, see @ref{Translator functions}, for a |
b349f79f | 2162 | detailed description. |
4009494e GM |
2163 | @end table |
2164 | ||
2165 | If you don't like the automatic table editor because it gets in your | |
2166 | way on lines which you would like to start with @samp{|}, you can turn | |
2167 | it off with | |
2168 | ||
2169 | @lisp | |
2170 | (setq org-enable-table-editor nil) | |
2171 | @end lisp | |
2172 | ||
2173 | @noindent Then the only table command that still works is | |
2174 | @kbd{C-c C-c} to do a manual re-align. | |
2175 | ||
c8d0cf5c CD |
2176 | @node Column width and alignment, Column groups, Built-in table editor, Tables |
2177 | @section Column width and alignment | |
4009494e | 2178 | @cindex narrow columns in tables |
c8d0cf5c CD |
2179 | @cindex alignment in tables |
2180 | ||
2181 | The width of columns is automatically determined by the table editor. And | |
2182 | also the alignment of a column is determined automatically from the fraction | |
2183 | of number-like versus non-number fields in the column. | |
4009494e | 2184 | |
ed21c5c8 CD |
2185 | Sometimes a single field or a few fields need to carry more text, leading to |
2186 | inconveniently wide columns. Or maybe you want to make a table with several | |
2187 | columns having a fixed width, regardless of content. To set@footnote{This | |
2188 | feature does not work on XEmacs.} the width of a column, one field anywhere | |
2189 | in the column may contain just the string @samp{<N>} where @samp{N} is an | |
2190 | integer specifying the width of the column in characters. The next re-align | |
2191 | will then set the width of this column to this value. | |
4009494e GM |
2192 | |
2193 | @example | |
2194 | @group | |
2195 | |---+------------------------------| |---+--------| | |
2196 | | | | | | <6> | | |
2197 | | 1 | one | | 1 | one | | |
2198 | | 2 | two | ----\ | 2 | two | | |
2199 | | 3 | This is a long chunk of text | ----/ | 3 | This=> | | |
2200 | | 4 | four | | 4 | four | | |
2201 | |---+------------------------------| |---+--------| | |
2202 | @end group | |
2203 | @end example | |
2204 | ||
2205 | @noindent | |
2206 | Fields that are wider become clipped and end in the string @samp{=>}. | |
acedf35c | 2207 | Note that the full text is still in the buffer but is hidden. |
c8d0cf5c | 2208 | To see the full text, hold the mouse over the field---a tool-tip window |
4009494e GM |
2209 | will show the full content. To edit such a field, use the command |
2210 | @kbd{C-c `} (that is @kbd{C-c} followed by the backquote). This will | |
2211 | open a new window with the full field. Edit it and finish with @kbd{C-c | |
2212 | C-c}. | |
2213 | ||
c8d0cf5c | 2214 | @vindex org-startup-align-all-tables |
4009494e GM |
2215 | When visiting a file containing a table with narrowed columns, the |
2216 | necessary character hiding has not yet happened, and the table needs to | |
2217 | be aligned before it looks nice. Setting the option | |
2218 | @code{org-startup-align-all-tables} will realign all tables in a file | |
2219 | upon visiting, but also slow down startup. You can also set this option | |
2220 | on a per-file basis with: | |
2221 | ||
2222 | @example | |
2223 | #+STARTUP: align | |
2224 | #+STARTUP: noalign | |
2225 | @end example | |
2226 | ||
c8d0cf5c | 2227 | If you would like to overrule the automatic alignment of number-rich columns |
acedf35c | 2228 | to the right and of string-rich column to the left, you can use @samp{<r>}, |
afe98dfa CD |
2229 | @samp{c}@footnote{Centering does not work inside Emacs, but it does have an |
2230 | effect when exporting to HTML.} or @samp{<l>} in a similar fashion. You may | |
2231 | also combine alignment and field width like this: @samp{<l10>}. | |
c8d0cf5c | 2232 | |
86fbb8ca CD |
2233 | Lines which only contain these formatting cookies will be removed |
2234 | automatically when exporting the document. | |
2235 | ||
c8d0cf5c | 2236 | @node Column groups, Orgtbl mode, Column width and alignment, Tables |
4009494e GM |
2237 | @section Column groups |
2238 | @cindex grouping columns in tables | |
2239 | ||
a7808fba | 2240 | When Org exports tables, it does so by default without vertical |
4009494e GM |
2241 | lines because that is visually more satisfying in general. Occasionally |
2242 | however, vertical lines can be useful to structure a table into groups | |
2243 | of columns, much like horizontal lines can do for groups of rows. In | |
2244 | order to specify column groups, you can use a special row where the | |
2245 | first field contains only @samp{/}. The further fields can either | |
2246 | contain @samp{<} to indicate that this column should start a group, | |
153ae947 BG |
2247 | @samp{>} to indicate the end of a column, or @samp{<>} (no space between @samp{<} |
2248 | and @samp{>}) to make a column | |
a7808fba | 2249 | a group of its own. Boundaries between column groups will upon export be |
4009494e GM |
2250 | marked with vertical lines. Here is an example: |
2251 | ||
2252 | @example | |
86fbb8ca CD |
2253 | | N | N^2 | N^3 | N^4 | sqrt(n) | sqrt[4](N) | |
2254 | |---+-----+-----+-----+---------+------------| | |
2255 | | / | < | | > | < | > | | |
2256 | | 1 | 1 | 1 | 1 | 1 | 1 | | |
2257 | | 2 | 4 | 8 | 16 | 1.4142 | 1.1892 | | |
2258 | | 3 | 9 | 27 | 81 | 1.7321 | 1.3161 | | |
2259 | |---+-----+-----+-----+---------+------------| | |
2260 | #+TBLFM: $2=$1^2::$3=$1^3::$4=$1^4::$5=sqrt($1)::$6=sqrt(sqrt(($1))) | |
4009494e GM |
2261 | @end example |
2262 | ||
a7808fba | 2263 | It is also sufficient to just insert the column group starters after |
86fbb8ca | 2264 | every vertical line you would like to have: |
4009494e GM |
2265 | |
2266 | @example | |
2267 | | N | N^2 | N^3 | N^4 | sqrt(n) | sqrt[4](N) | | |
2268 | |----+-----+-----+-----+---------+------------| | |
2269 | | / | < | | | < | | | |
2270 | @end example | |
2271 | ||
a7808fba | 2272 | @node Orgtbl mode, The spreadsheet, Column groups, Tables |
4009494e | 2273 | @section The Orgtbl minor mode |
a7808fba | 2274 | @cindex Orgtbl mode |
4009494e GM |
2275 | @cindex minor mode for tables |
2276 | ||
a7808fba CD |
2277 | If you like the intuitive way the Org table editor works, you |
2278 | might also want to use it in other modes like Text mode or Mail mode. | |
2279 | The minor mode Orgtbl mode makes this possible. You can always toggle | |
4009494e | 2280 | the mode with @kbd{M-x orgtbl-mode}. To turn it on by default, for |
ce57c2fe | 2281 | example in Message mode, use |
4009494e GM |
2282 | |
2283 | @lisp | |
ce57c2fe | 2284 | (add-hook 'message-mode-hook 'turn-on-orgtbl) |
4009494e GM |
2285 | @end lisp |
2286 | ||
2287 | Furthermore, with some special setup, it is possible to maintain tables | |
a7808fba | 2288 | in arbitrary syntax with Orgtbl mode. For example, it is possible to |
acedf35c | 2289 | construct @LaTeX{} tables with the underlying ease and power of |
a7808fba | 2290 | Orgtbl mode, including spreadsheet capabilities. For details, see |
4009494e GM |
2291 | @ref{Tables in arbitrary syntax}. |
2292 | ||
c8d0cf5c | 2293 | @node The spreadsheet, Org-Plot, Orgtbl mode, Tables |
4009494e GM |
2294 | @section The spreadsheet |
2295 | @cindex calculations, in tables | |
2296 | @cindex spreadsheet capabilities | |
2297 | @cindex @file{calc} package | |
2298 | ||
2299 | The table editor makes use of the Emacs @file{calc} package to implement | |
2300 | spreadsheet-like capabilities. It can also evaluate Emacs Lisp forms to | |
ed21c5c8 CD |
2301 | derive fields from other fields. While fully featured, Org's implementation |
2302 | is not identical to other spreadsheets. For example, Org knows the concept | |
2303 | of a @emph{column formula} that will be applied to all non-header fields in a | |
2304 | column without having to copy the formula to each relevant field. There is | |
2305 | also a formula debugger, and a formula editor with features for highlighting | |
2306 | fields in the table corresponding to the references at the point in the | |
2307 | formula, moving these references by arrow keys | |
4009494e GM |
2308 | |
2309 | @menu | |
c0468714 GM |
2310 | * References:: How to refer to another field or range |
2311 | * Formula syntax for Calc:: Using Calc to compute stuff | |
2312 | * Formula syntax for Lisp:: Writing formulas in Emacs Lisp | |
ce57c2fe BG |
2313 | * Durations and time values:: How to compute durations and time values |
2314 | * Field and range formulas:: Formula for specific (ranges of) fields | |
c0468714 | 2315 | * Column formulas:: Formulas valid for an entire column |
4009494e | 2316 | * Editing and debugging formulas:: Fixing formulas |
c0468714 | 2317 | * Updating the table:: Recomputing all dependent fields |
e66ba1df | 2318 | * Advanced features:: Field and column names, parameters and automatic recalc |
4009494e GM |
2319 | @end menu |
2320 | ||
2321 | @node References, Formula syntax for Calc, The spreadsheet, The spreadsheet | |
2322 | @subsection References | |
2323 | @cindex references | |
2324 | ||
2325 | To compute fields in the table from other fields, formulas must | |
a7808fba | 2326 | reference other fields or ranges. In Org, fields can be referenced |
4009494e GM |
2327 | by name, by absolute coordinates, and by relative coordinates. To find |
2328 | out what the coordinates of a field are, press @kbd{C-c ?} in that | |
2329 | field, or press @kbd{C-c @}} to toggle the display of a grid. | |
2330 | ||
2331 | @subsubheading Field references | |
2332 | @cindex field references | |
2333 | @cindex references, to fields | |
2334 | ||
2335 | Formulas can reference the value of another field in two ways. Like in | |
2336 | any other spreadsheet, you may reference fields with a letter/number | |
2337 | combination like @code{B3}, meaning the 2nd field in the 3rd row. | |
ce57c2fe BG |
2338 | @vindex org-table-use-standard-references |
2339 | However, Org prefers@footnote{Org will understand references typed by the | |
2340 | user as @samp{B4}, but it will not use this syntax when offering a formula | |
2341 | for editing. You can customize this behavior using the variable | |
2342 | @code{org-table-use-standard-references}.} to use another, more general | |
2343 | representation that looks like this: | |
4009494e | 2344 | @example |
c8d0cf5c | 2345 | @@@var{row}$@var{column} |
4009494e GM |
2346 | @end example |
2347 | ||
ce57c2fe BG |
2348 | Column specifications can be absolute like @code{$1}, |
2349 | @code{$2},...@code{$@var{N}}, or relative to the current column (i.e.@: the | |
2350 | column of the field which is being computed) like @code{$+1} or @code{$-2}. | |
2351 | @code{$<} and @code{$>} are immutable references to the first and last | |
2352 | column, respectively, and you can use @code{$>>>} to indicate the third | |
2353 | column from the right. | |
2354 | ||
2355 | The row specification only counts data lines and ignores horizontal separator | |
2356 | lines (hlines). Like with columns, you can use absolute row numbers | |
2357 | @code{@@1}, @code{@@2},...@code{@@@var{N}}, and row numbers relative to the | |
2358 | current row like @code{@@+3} or @code{@@-1}. @code{@@<} and @code{@@>} are | |
2359 | immutable references the first and last@footnote{For backward compatibility | |
2360 | you can also use special names like @code{$LR5} and @code{$LR12} to refer in | |
2361 | a stable way to the 5th and 12th field in the last row of the table. | |
2362 | However, this syntax is deprecated, it should not be used for new documents. | |
2363 | Use @code{@@>$} instead.} row in the table, respectively. You may also | |
2364 | specify the row relative to one of the hlines: @code{@@I} refers to the first | |
2365 | hline, @code{@@II} to the second, etc@. @code{@@-I} refers to the first such | |
2366 | line above the current line, @code{@@+I} to the first such line below the | |
2367 | current line. You can also write @code{@@III+2} which is the second data line | |
2368 | after the third hline in the table. | |
2369 | ||
2370 | @code{@@0} and @code{$0} refer to the current row and column, respectively, | |
2371 | i.e. to the row/column for the field being computed. Also, if you omit | |
2372 | either the column or the row part of the reference, the current row/column is | |
2373 | implied. | |
4009494e | 2374 | |
a7808fba | 2375 | Org's references with @emph{unsigned} numbers are fixed references |
4009494e GM |
2376 | in the sense that if you use the same reference in the formula for two |
2377 | different fields, the same field will be referenced each time. | |
a7808fba | 2378 | Org's references with @emph{signed} numbers are floating |
4009494e GM |
2379 | references because the same reference operator can reference different |
2380 | fields depending on the field being calculated by the formula. | |
2381 | ||
2382 | Here are a few examples: | |
2383 | ||
2384 | @example | |
ce57c2fe BG |
2385 | @@2$3 @r{2nd row, 3rd column (same as @code{C2})} |
2386 | $5 @r{column 5 in the current row (same as @code{E&})} | |
4009494e GM |
2387 | @@2 @r{current column, row 2} |
2388 | @@-1$-3 @r{the field one row up, three columns to the left} | |
2389 | @@-I$2 @r{field just under hline above current row, column 2} | |
ce57c2fe | 2390 | @@>$5 @r{field in the last row, in column 5} |
4009494e GM |
2391 | @end example |
2392 | ||
2393 | @subsubheading Range references | |
2394 | @cindex range references | |
2395 | @cindex references, to ranges | |
2396 | ||
2397 | You may reference a rectangular range of fields by specifying two field | |
2398 | references connected by two dots @samp{..}. If both fields are in the | |
2399 | current row, you may simply use @samp{$2..$7}, but if at least one field | |
2400 | is in a different row, you need to use the general @code{@@row$column} | |
2401 | format at least for the first field (i.e the reference must start with | |
2402 | @samp{@@} in order to be interpreted correctly). Examples: | |
2403 | ||
2404 | @example | |
ce57c2fe BG |
2405 | $1..$3 @r{first three fields in the current row} |
2406 | $P..$Q @r{range, using column names (see under Advanced)} | |
2407 | $<<<..$>> @r{start in third column, continue to the one but last} | |
2408 | @@2$1..@@4$3 @r{6 fields between these two fields (same as @code{A2..C4})} | |
4009494e | 2409 | @@-1$-2..@@-1 @r{3 numbers from the column to the left, 2 up to current row} |
ce57c2fe | 2410 | @@I..II @r{between first and second hline, short for @code{@@I..@@II}} |
4009494e GM |
2411 | @end example |
2412 | ||
2413 | @noindent Range references return a vector of values that can be fed | |
2414 | into Calc vector functions. Empty fields in ranges are normally | |
2415 | suppressed, so that the vector contains only the non-empty fields (but | |
2416 | see the @samp{E} mode switch below). If there are no non-empty fields, | |
2417 | @samp{[0]} is returned to avoid syntax errors in formulas. | |
2418 | ||
ed21c5c8 CD |
2419 | @subsubheading Field coordinates in formulas |
2420 | @cindex field coordinates | |
2421 | @cindex coordinates, of field | |
2422 | @cindex row, of field coordinates | |
2423 | @cindex column, of field coordinates | |
2424 | ||
2425 | For Calc formulas and Lisp formulas @code{@@#} and @code{$#} can be used to | |
2426 | get the row or column number of the field where the formula result goes. | |
2427 | The traditional Lisp formula equivalents are @code{org-table-current-dline} | |
2428 | and @code{org-table-current-column}. Examples: | |
2429 | ||
2430 | @example | |
2431 | if(@@# % 2, $#, string("")) @r{column number on odd lines only} | |
2432 | $3 = remote(FOO, @@@@#$2) @r{copy column 2 from table FOO into} | |
2433 | @r{column 3 of the current table} | |
2434 | @end example | |
2435 | ||
2436 | @noindent For the second example, table FOO must have at least as many rows | |
ce57c2fe | 2437 | as the current table. Note that this is inefficient@footnote{The computation time scales as |
ed21c5c8 CD |
2438 | O(N^2) because table FOO is parsed for each field to be copied.} for large |
2439 | number of rows. | |
2440 | ||
4009494e GM |
2441 | @subsubheading Named references |
2442 | @cindex named references | |
2443 | @cindex references, named | |
2444 | @cindex name, of column or field | |
2445 | @cindex constants, in calculations | |
c8d0cf5c | 2446 | @cindex #+CONSTANTS |
4009494e | 2447 | |
c8d0cf5c | 2448 | @vindex org-table-formula-constants |
4009494e GM |
2449 | @samp{$name} is interpreted as the name of a column, parameter or |
2450 | constant. Constants are defined globally through the variable | |
2451 | @code{org-table-formula-constants}, and locally (for the file) through a | |
2452 | line like | |
2453 | ||
2454 | @example | |
2455 | #+CONSTANTS: c=299792458. pi=3.14 eps=2.4e-6 | |
2456 | @end example | |
2457 | ||
2458 | @noindent | |
c8d0cf5c CD |
2459 | @vindex constants-unit-system |
2460 | @pindex constants.el | |
a7808fba | 2461 | Also properties (@pxref{Properties and Columns}) can be used as |
c8d0cf5c | 2462 | constants in table formulas: for a property @samp{:Xyz:} use the name |
dbc28aaa | 2463 | @samp{$PROP_Xyz}, and the property will be searched in the current |
4009494e GM |
2464 | outline entry and in the hierarchy above it. If you have the |
2465 | @file{constants.el} package, it will also be used to resolve constants, | |
2466 | including natural constants like @samp{$h} for Planck's constant, and | |
c8d0cf5c | 2467 | units like @samp{$km} for kilometers@footnote{@file{constants.el} can |
4009494e GM |
2468 | supply the values of constants in two different unit systems, @code{SI} |
2469 | and @code{cgs}. Which one is used depends on the value of the variable | |
2470 | @code{constants-unit-system}. You can use the @code{#+STARTUP} options | |
2471 | @code{constSI} and @code{constcgs} to set this value for the current | |
2472 | buffer.}. Column names and parameters can be specified in special table | |
2473 | lines. These are described below, see @ref{Advanced features}. All | |
2474 | names must start with a letter, and further consist of letters and | |
2475 | numbers. | |
2476 | ||
55e0839d CD |
2477 | @subsubheading Remote references |
2478 | @cindex remote references | |
2479 | @cindex references, remote | |
2480 | @cindex references, to a different table | |
2481 | @cindex name, of column or field | |
2482 | @cindex constants, in calculations | |
c8d0cf5c | 2483 | @cindex #+TBLNAME |
55e0839d CD |
2484 | |
2485 | You may also reference constants, fields and ranges from a different table, | |
2486 | either in the current file or even in a different file. The syntax is | |
2487 | ||
2488 | @example | |
2489 | remote(NAME-OR-ID,REF) | |
2490 | @end example | |
2491 | ||
2492 | @noindent | |
2493 | where NAME can be the name of a table in the current file as set by a | |
2494 | @code{#+TBLNAME: NAME} line before the table. It can also be the ID of an | |
2495 | entry, even in a different file, and the reference then refers to the first | |
2496 | table in that entry. REF is an absolute field or range reference as | |
c8d0cf5c CD |
2497 | described above for example @code{@@3$3} or @code{$somename}, valid in the |
2498 | referenced table. | |
55e0839d | 2499 | |
4009494e GM |
2500 | @node Formula syntax for Calc, Formula syntax for Lisp, References, The spreadsheet |
2501 | @subsection Formula syntax for Calc | |
2502 | @cindex formula syntax, Calc | |
2503 | @cindex syntax, of formulas | |
2504 | ||
2505 | A formula can be any algebraic expression understood by the Emacs | |
2506 | @file{Calc} package. @b{Note that @file{calc} has the | |
2507 | non-standard convention that @samp{/} has lower precedence than | |
2508 | @samp{*}, so that @samp{a/b*c} is interpreted as @samp{a/(b*c)}.} Before | |
2509 | evaluation by @code{calc-eval} (@pxref{Calling Calc from | |
153ae947 | 2510 | Your Programs, calc-eval, Calling Calc from Your Lisp Programs, calc, GNU |
4009494e | 2511 | Emacs Calc Manual}), |
4009494e GM |
2512 | variable substitution takes place according to the rules described above. |
2513 | @cindex vectors, in table calculations | |
a7808fba | 2514 | The range vectors can be directly fed into the Calc vector functions |
4009494e GM |
2515 | like @samp{vmean} and @samp{vsum}. |
2516 | ||
2517 | @cindex format specifier | |
2518 | @cindex mode, for @file{calc} | |
c8d0cf5c | 2519 | @vindex org-calc-default-modes |
4009494e GM |
2520 | A formula can contain an optional mode string after a semicolon. This |
2521 | string consists of flags to influence Calc and other modes during | |
a7808fba | 2522 | execution. By default, Org uses the standard Calc modes (precision |
44ce9197 | 2523 | 12, angular units degrees, fraction and symbolic modes off). The display |
c8d0cf5c | 2524 | format, however, has been changed to @code{(float 8)} to keep tables |
4009494e GM |
2525 | compact. The default settings can be configured using the variable |
2526 | @code{org-calc-default-modes}. | |
2527 | ||
2528 | @example | |
ed21c5c8 CD |
2529 | p20 @r{set the internal Calc calculation precision to 20 digits} |
2530 | n3 s3 e2 f4 @r{Normal, scientific, engineering, or fixed} | |
2531 | @r{format of the result of Calc passed back to Org.} | |
2532 | @r{Calc formatting is unlimited in precision as} | |
2533 | @r{long as the Calc calculation precision is greater.} | |
4009494e GM |
2534 | D R @r{angle modes: degrees, radians} |
2535 | F S @r{fraction and symbolic modes} | |
2536 | N @r{interpret all fields as numbers, use 0 for non-numbers} | |
4009494e | 2537 | E @r{keep empty fields in ranges} |
c8d0cf5c | 2538 | L @r{literal} |
4009494e GM |
2539 | @end example |
2540 | ||
2541 | @noindent | |
ed21c5c8 CD |
2542 | Unless you use large integer numbers or high-precision-calculation |
2543 | and -display for floating point numbers you may alternatively provide a | |
2544 | @code{printf} format specifier to reformat the Calc result after it has been | |
2545 | passed back to Org instead of letting Calc already do the | |
2546 | formatting@footnote{The @code{printf} reformatting is limited in precision | |
2547 | because the value passed to it is converted into an @code{integer} or | |
2548 | @code{double}. The @code{integer} is limited in size by truncating the | |
2549 | signed value to 32 bits. The @code{double} is limited in precision to 64 | |
2550 | bits overall which leaves approximately 16 significant decimal digits.}. | |
2551 | A few examples: | |
4009494e GM |
2552 | |
2553 | @example | |
2554 | $1+$2 @r{Sum of first and second field} | |
2555 | $1+$2;%.2f @r{Same, format result to two decimals} | |
2556 | exp($2)+exp($1) @r{Math functions can be used} | |
2557 | $0;%.1f @r{Reformat current cell to 1 decimal} | |
2558 | ($3-32)*5/9 @r{Degrees F -> C conversion} | |
2559 | $c/$1/$cm @r{Hz -> cm conversion, using @file{constants.el}} | |
2560 | tan($1);Dp3s1 @r{Compute in degrees, precision 3, display SCI 1} | |
2561 | sin($1);Dp3%.1e @r{Same, but use printf specifier for display} | |
2562 | vmean($2..$7) @r{Compute column range mean, using vector function} | |
2563 | vmean($2..$7);EN @r{Same, but treat empty fields as 0} | |
acedf35c | 2564 | taylor($3,x=7,2) @r{Taylor series of $3, at x=7, second degree} |
4009494e GM |
2565 | @end example |
2566 | ||
2567 | Calc also contains a complete set of logical operations. For example | |
2568 | ||
2569 | @example | |
ce57c2fe | 2570 | if($1<20,teen,string("")) @r{"teen" if age $1 less than 20, else empty} |
4009494e GM |
2571 | @end example |
2572 | ||
ce57c2fe BG |
2573 | Note that you can also use two org-specific flags @code{T} and @code{t} for |
2574 | durations computations @ref{Durations and time values}. | |
2575 | ||
2576 | @node Formula syntax for Lisp, Durations and time values, Formula syntax for Calc, The spreadsheet | |
4009494e GM |
2577 | @subsection Emacs Lisp forms as formulas |
2578 | @cindex Lisp forms, as table formulas | |
2579 | ||
acedf35c CD |
2580 | It is also possible to write a formula in Emacs Lisp; this can be useful for |
2581 | string manipulation and control structures, if Calc's functionality is not | |
2582 | enough. If a formula starts with a single-quote followed by an opening | |
2583 | parenthesis, then it is evaluated as a Lisp form. The evaluation should | |
2584 | return either a string or a number. Just as with @file{calc} formulas, you | |
2585 | can specify modes and a printf format after a semicolon. With Emacs Lisp | |
2586 | forms, you need to be conscious about the way field references are | |
2587 | interpolated into the form. By default, a reference will be interpolated as | |
2588 | a Lisp string (in double-quotes) containing the field. If you provide the | |
2589 | @samp{N} mode switch, all referenced elements will be numbers (non-number | |
2590 | fields will be zero) and interpolated as Lisp numbers, without quotes. If | |
2591 | you provide the @samp{L} flag, all fields will be interpolated literally, | |
2592 | without quotes. I.e., if you want a reference to be interpreted as a string | |
2593 | by the Lisp form, enclose the reference operator itself in double-quotes, | |
2594 | like @code{"$3"}. Ranges are inserted as space-separated fields, so you can | |
ce57c2fe | 2595 | embed them in list or vector syntax. Here are a few examples---note how the |
acedf35c | 2596 | @samp{N} mode is used when we do computations in Lisp: |
4009494e GM |
2597 | |
2598 | @example | |
2599 | @r{Swap the first two characters of the content of column 1} | |
2600 | '(concat (substring $1 1 2) (substring $1 0 1) (substring $1 2)) | |
2096a1b6 | 2601 | @r{Add columns 1 and 2, equivalent to Calc's @code{$1+$2}} |
4009494e GM |
2602 | '(+ $1 $2);N |
2603 | @r{Compute the sum of columns 1-4, like Calc's @code{vsum($1..$4)}} | |
2604 | '(apply '+ '($1..$4));N | |
2605 | @end example | |
2606 | ||
ce57c2fe BG |
2607 | @node Durations and time values, Field and range formulas, Formula syntax for Lisp, The spreadsheet |
2608 | @subsection Durations and time values | |
2609 | @cindex Duration, computing | |
2610 | @cindex Time, computing | |
2611 | @vindex org-table-duration-custom-format | |
2612 | ||
2613 | If you want to compute time values use the @code{T} flag, either in Calc | |
2614 | formulas or Elisp formulas: | |
2615 | ||
2616 | @example | |
2617 | @group | |
2618 | | Task 1 | Task 2 | Total | | |
2619 | |---------+----------+----------| | |
2620 | | 2:12 | 1:47 | 03:59:00 | | |
2621 | | 3:02:20 | -2:07:00 | 0.92 | | |
2622 | #+TBLFM: @@2$3=$1+$2;T::@@3$3=$1+$2;t | |
2623 | @end group | |
2624 | @end example | |
2625 | ||
2626 | Input duration values must be of the form @code{[HH:MM[:SS]}, where seconds | |
2627 | are optional. With the @code{T} flag, computed durations will be displayed | |
2628 | as @code{[HH:MM:SS} (see the first formula above). With the @code{t} flag, | |
2629 | computed durations will be displayed according to the value of the variable | |
2630 | @code{org-table-duration-custom-format}, which defaults to @code{'hours} and | |
2631 | will display the result as a fraction of hours (see the second formula in the | |
2632 | example above). | |
2633 | ||
2634 | Negative duration values can be manipulated as well, and integers will be | |
2635 | considered as seconds in addition and subtraction. | |
2636 | ||
2637 | @node Field and range formulas, Column formulas, Durations and time values, The spreadsheet | |
2638 | @subsection Field and range formulas | |
4009494e | 2639 | @cindex field formula |
ce57c2fe | 2640 | @cindex range formula |
4009494e | 2641 | @cindex formula, for individual table field |
ce57c2fe | 2642 | @cindex formula, for range of fields |
4009494e | 2643 | |
ce57c2fe BG |
2644 | To assign a formula to a particular field, type it directly into the field, |
2645 | preceded by @samp{:=}, for example @samp{:=vsum(@@II..III)}. When you press | |
2646 | @key{TAB} or @key{RET} or @kbd{C-c C-c} with the cursor still in the field, | |
2647 | the formula will be stored as the formula for this field, evaluated, and the | |
2648 | current field will be replaced with the result. | |
4009494e | 2649 | |
c8d0cf5c | 2650 | @cindex #+TBLFM |
ce57c2fe BG |
2651 | Formulas are stored in a special line starting with @samp{#+TBLFM:} directly |
2652 | below the table. If you type the equation in the 4th field of the 3rd data | |
2653 | line in the table, the formula will look like @samp{@@3$4=$1+$2}. When | |
2654 | inserting/deleting/swapping column and rows with the appropriate commands, | |
2655 | @i{absolute references} (but not relative ones) in stored formulas are | |
2656 | modified in order to still reference the same field. To avoid this from | |
2657 | happening, in particular in range references, anchor ranges at the table | |
2658 | borders (using @code{@@<}, @code{@@>}, @code{$<}, @code{$>}), or at hlines | |
2659 | using the @code{@@I} notation. Automatic adaptation of field references does | |
2660 | of cause not happen if you edit the table structure with normal editing | |
2661 | commands---then you must fix the equations yourself. | |
2662 | ||
2663 | Instead of typing an equation into the field, you may also use the following | |
2664 | command | |
4009494e GM |
2665 | |
2666 | @table @kbd | |
acedf35c | 2667 | @orgcmd{C-u C-c =,org-table-eval-formula} |
4009494e | 2668 | Install a new formula for the current field. The command prompts for a |
c8d0cf5c CD |
2669 | formula with default taken from the @samp{#+TBLFM:} line, applies |
2670 | it to the current field, and stores it. | |
4009494e GM |
2671 | @end table |
2672 | ||
ce57c2fe BG |
2673 | The left-hand side of a formula can also be a special expression in order to |
2674 | assign the formula to a number of different fields. There is no keyboard | |
2675 | shortcut to enter such range formulas. To add them, use the formula editor | |
2676 | (@pxref{Editing and debugging formulas}) or edit the @code{#+TBLFM:} line | |
2677 | directly. | |
2678 | ||
2679 | @table @code | |
2680 | @item $2= | |
2681 | Column formula, valid for the entire column. This is so common that Org | |
2682 | treats these formulas in a special way, see @ref{Column formulas}. | |
2683 | @item @@3= | |
2684 | Row formula, applies to all fields in the specified row. @code{@@>=} means | |
2685 | the last row. | |
2686 | @item @@1$2..@@4$3= | |
2687 | Range formula, applies to all fields in the given rectangular range. This | |
2688 | can also be used to assign a formula to some but not all fields in a row. | |
2689 | @item $name= | |
2690 | Named field, see @ref{Advanced features}. | |
2691 | @end table | |
2692 | ||
2693 | @node Column formulas, Editing and debugging formulas, Field and range formulas, The spreadsheet | |
4009494e GM |
2694 | @subsection Column formulas |
2695 | @cindex column formula | |
2696 | @cindex formula, for table column | |
2697 | ||
ce57c2fe BG |
2698 | When you assign a formula to a simple column reference like @code{$3=}, the |
2699 | same formula will be used in all fields of that column, with the following | |
2700 | very convenient exceptions: (i) If the table contains horizontal separator | |
2701 | hlines, everything before the first such line is considered part of the table | |
2702 | @emph{header} and will not be modified by column formulas. (ii) Fields that | |
2703 | already get a value from a field/range formula will be left alone by column | |
2704 | formulas. These conditions make column formulas very easy to use. | |
4009494e GM |
2705 | |
2706 | To assign a formula to a column, type it directly into any field in the | |
2707 | column, preceded by an equal sign, like @samp{=$1+$2}. When you press | |
c8d0cf5c CD |
2708 | @key{TAB} or @key{RET} or @kbd{C-c C-c} with the cursor still in the field, |
2709 | the formula will be stored as the formula for the current column, evaluated | |
2710 | and the current field replaced with the result. If the field contains only | |
2711 | @samp{=}, the previously stored formula for this column is used. For each | |
2712 | column, Org will only remember the most recently used formula. In the | |
ce57c2fe BG |
2713 | @samp{#+TBLFM:} line, column formulas will look like @samp{$4=$1+$2}. The |
2714 | left-hand side of a column formula can not be the name of column, it must be | |
2715 | the numeric column reference or @code{$>}. | |
4009494e GM |
2716 | |
2717 | Instead of typing an equation into the field, you may also use the | |
2718 | following command: | |
2719 | ||
2720 | @table @kbd | |
acedf35c | 2721 | @orgcmd{C-c =,org-table-eval-formula} |
a7808fba CD |
2722 | Install a new formula for the current column and replace current field with |
2723 | the result of the formula. The command prompts for a formula, with default | |
2724 | taken from the @samp{#+TBLFM} line, applies it to the current field and | |
ce57c2fe | 2725 | stores it. With a numeric prefix argument(e.g.@: @kbd{C-5 C-c =}) the command |
4009494e GM |
2726 | will apply it to that many consecutive fields in the current column. |
2727 | @end table | |
2728 | ||
4009494e | 2729 | @node Editing and debugging formulas, Updating the table, Column formulas, The spreadsheet |
a7808fba | 2730 | @subsection Editing and debugging formulas |
4009494e GM |
2731 | @cindex formula editing |
2732 | @cindex editing, of table formulas | |
2733 | ||
c8d0cf5c | 2734 | @vindex org-table-use-standard-references |
4009494e | 2735 | You can edit individual formulas in the minibuffer or directly in the |
a7808fba CD |
2736 | field. Org can also prepare a special buffer with all active |
2737 | formulas of a table. When offering a formula for editing, Org | |
4009494e GM |
2738 | converts references to the standard format (like @code{B3} or @code{D&}) |
2739 | if possible. If you prefer to only work with the internal format (like | |
2740 | @code{@@3$2} or @code{$4}), configure the variable | |
2741 | @code{org-table-use-standard-references}. | |
2742 | ||
2743 | @table @kbd | |
acedf35c | 2744 | @orgcmdkkc{C-c =,C-u C-c =,org-table-eval-formula} |
4009494e | 2745 | Edit the formula associated with the current column/field in the |
ce57c2fe | 2746 | minibuffer. See @ref{Column formulas}, and @ref{Field and range formulas}. |
acedf35c | 2747 | @orgcmd{C-u C-u C-c =,org-table-eval-formula} |
4009494e GM |
2748 | Re-insert the active formula (either a |
2749 | field formula, or a column formula) into the current field, so that you | |
2750 | can edit it directly in the field. The advantage over editing in the | |
2751 | minibuffer is that you can use the command @kbd{C-c ?}. | |
acedf35c | 2752 | @orgcmd{C-c ?,org-table-field-info} |
4009494e GM |
2753 | While editing a formula in a table field, highlight the field(s) |
2754 | referenced by the reference at the cursor position in the formula. | |
2755 | @kindex C-c @} | |
acedf35c | 2756 | @findex org-table-toggle-coordinate-overlays |
4009494e | 2757 | @item C-c @} |
acedf35c CD |
2758 | Toggle the display of row and column numbers for a table, using overlays |
2759 | (@command{org-table-toggle-coordinate-overlays}). These are updated each | |
2760 | time the table is aligned; you can force it with @kbd{C-c C-c}. | |
4009494e | 2761 | @kindex C-c @{ |
acedf35c | 2762 | @findex org-table-toggle-formula-debugger |
4009494e | 2763 | @item C-c @{ |
acedf35c CD |
2764 | Toggle the formula debugger on and off |
2765 | (@command{org-table-toggle-formula-debugger}). See below. | |
2766 | @orgcmd{C-c ',org-table-edit-formulas} | |
4009494e GM |
2767 | Edit all formulas for the current table in a special buffer, where the |
2768 | formulas will be displayed one per line. If the current field has an | |
2769 | active formula, the cursor in the formula editor will mark it. | |
a7808fba | 2770 | While inside the special buffer, Org will automatically highlight |
4009494e GM |
2771 | any field or range reference at the cursor position. You may edit, |
2772 | remove and add formulas, and use the following commands: | |
2773 | @table @kbd | |
acedf35c | 2774 | @orgcmdkkc{C-c C-c,C-x C-s,org-table-fedit-finish} |
4009494e GM |
2775 | Exit the formula editor and store the modified formulas. With @kbd{C-u} |
2776 | prefix, also apply the new formulas to the entire table. | |
acedf35c | 2777 | @orgcmd{C-c C-q,org-table-fedit-abort} |
4009494e | 2778 | Exit the formula editor without installing changes. |
acedf35c | 2779 | @orgcmd{C-c C-r,org-table-fedit-toggle-ref-type} |
4009494e GM |
2780 | Toggle all references in the formula editor between standard (like |
2781 | @code{B3}) and internal (like @code{@@3$2}). | |
acedf35c | 2782 | @orgcmd{@key{TAB},org-table-fedit-lisp-indent} |
c8d0cf5c CD |
2783 | Pretty-print or indent Lisp formula at point. When in a line containing |
2784 | a Lisp formula, format the formula according to Emacs Lisp rules. | |
4009494e | 2785 | Another @key{TAB} collapses the formula back again. In the open |
c8d0cf5c | 2786 | formula, @key{TAB} re-indents just like in Emacs Lisp mode. |
acedf35c | 2787 | @orgcmd{M-@key{TAB},lisp-complete-symbol} |
c8d0cf5c | 2788 | Complete Lisp symbols, just like in Emacs Lisp mode. |
4009494e GM |
2789 | @kindex S-@key{up} |
2790 | @kindex S-@key{down} | |
2791 | @kindex S-@key{left} | |
2792 | @kindex S-@key{right} | |
acedf35c CD |
2793 | @findex org-table-fedit-ref-up |
2794 | @findex org-table-fedit-ref-down | |
2795 | @findex org-table-fedit-ref-left | |
2796 | @findex org-table-fedit-ref-right | |
4009494e GM |
2797 | @item S-@key{up}/@key{down}/@key{left}/@key{right} |
2798 | Shift the reference at point. For example, if the reference is | |
2799 | @code{B3} and you press @kbd{S-@key{right}}, it will become @code{C3}. | |
c8d0cf5c | 2800 | This also works for relative references and for hline references. |
acedf35c | 2801 | @orgcmdkkcc{M-S-@key{up},M-S-@key{down},org-table-fedit-line-up,org-table-fedit-line-down} |
a7808fba | 2802 | Move the test line for column formulas in the Org buffer up and |
4009494e | 2803 | down. |
acedf35c | 2804 | @orgcmdkkcc{M-@key{up},M-@key{down},org-table-fedit-scroll-down,org-table-fedit-scroll-up} |
4009494e GM |
2805 | Scroll the window displaying the table. |
2806 | @kindex C-c @} | |
acedf35c | 2807 | @findex org-table-toggle-coordinate-overlays |
4009494e GM |
2808 | @item C-c @} |
2809 | Turn the coordinate grid in the table on and off. | |
2810 | @end table | |
2811 | @end table | |
2812 | ||
2813 | Making a table field blank does not remove the formula associated with | |
c8d0cf5c CD |
2814 | the field, because that is stored in a different line (the @samp{#+TBLFM} |
2815 | line)---during the next recalculation the field will be filled again. | |
4009494e GM |
2816 | To remove a formula from a field, you have to give an empty reply when |
2817 | prompted for the formula, or to edit the @samp{#+TBLFM} line. | |
2818 | ||
2819 | @kindex C-c C-c | |
2820 | You may edit the @samp{#+TBLFM} directly and re-apply the changed | |
c8d0cf5c | 2821 | equations with @kbd{C-c C-c} in that line or with the normal |
4009494e GM |
2822 | recalculation commands in the table. |
2823 | ||
2824 | @subsubheading Debugging formulas | |
2825 | @cindex formula debugging | |
2826 | @cindex debugging, of table formulas | |
2827 | When the evaluation of a formula leads to an error, the field content | |
2828 | becomes the string @samp{#ERROR}. If you would like see what is going | |
2829 | on during variable substitution and calculation in order to find a bug, | |
2830 | turn on formula debugging in the @code{Tbl} menu and repeat the | |
2831 | calculation, for example by pressing @kbd{C-u C-u C-c = @key{RET}} in a | |
2832 | field. Detailed information will be displayed. | |
2833 | ||
2834 | @node Updating the table, Advanced features, Editing and debugging formulas, The spreadsheet | |
a7808fba | 2835 | @subsection Updating the table |
4009494e GM |
2836 | @cindex recomputing table fields |
2837 | @cindex updating, table | |
2838 | ||
2839 | Recalculation of a table is normally not automatic, but needs to be | |
c8d0cf5c CD |
2840 | triggered by a command. See @ref{Advanced features}, for a way to make |
2841 | recalculation at least semi-automatic. | |
4009494e GM |
2842 | |
2843 | In order to recalculate a line of a table or the entire table, use the | |
2844 | following commands: | |
2845 | ||
2846 | @table @kbd | |
acedf35c | 2847 | @orgcmd{C-c *,org-table-recalculate} |
4009494e | 2848 | Recalculate the current row by first applying the stored column formulas |
ce57c2fe | 2849 | from left to right, and all field/range formulas in the current row. |
4009494e GM |
2850 | @c |
2851 | @kindex C-u C-c * | |
2852 | @item C-u C-c * | |
2853 | @kindex C-u C-c C-c | |
2854 | @itemx C-u C-c C-c | |
2855 | Recompute the entire table, line by line. Any lines before the first | |
2856 | hline are left alone, assuming that these are part of the table header. | |
2857 | @c | |
acedf35c | 2858 | @orgcmdkkc{C-u C-u C-c *,C-u C-u C-c C-c,org-table-iterate} |
4009494e GM |
2859 | Iterate the table by recomputing it until no further changes occur. |
2860 | This may be necessary if some computed fields use the value of other | |
2861 | fields that are computed @i{later} in the calculation sequence. | |
86fbb8ca | 2862 | @item M-x org-table-recalculate-buffer-tables |
acedf35c | 2863 | @findex org-table-recalculate-buffer-tables |
86fbb8ca CD |
2864 | Recompute all tables in the current buffer. |
2865 | @item M-x org-table-iterate-buffer-tables | |
acedf35c | 2866 | @findex org-table-iterate-buffer-tables |
86fbb8ca CD |
2867 | Iterate all tables in the current buffer, in order to converge table-to-table |
2868 | dependencies. | |
4009494e GM |
2869 | @end table |
2870 | ||
2871 | @node Advanced features, , Updating the table, The spreadsheet | |
2872 | @subsection Advanced features | |
2873 | ||
e66ba1df BG |
2874 | If you want the recalculation of fields to happen automatically, or if you |
2875 | want to be able to assign @i{names}@footnote{Such names must start by an | |
2876 | alphabetic character and use only alphanumeric/underscore characters.} to | |
2877 | fields and columns, you need to reserve the first column of the table for | |
2878 | special marking characters. | |
ce57c2fe | 2879 | |
4009494e | 2880 | @table @kbd |
acedf35c | 2881 | @orgcmd{C-#,org-table-rotate-recalc-marks} |
a351880d | 2882 | Rotate the calculation mark in first column through the states @samp{ }, |
864c9740 CD |
2883 | @samp{#}, @samp{*}, @samp{!}, @samp{$}. When there is an active region, |
2884 | change all marks in the region. | |
4009494e GM |
2885 | @end table |
2886 | ||
2887 | Here is an example of a table that collects exam results of students and | |
2888 | makes use of these features: | |
2889 | ||
2890 | @example | |
2891 | @group | |
2892 | |---+---------+--------+--------+--------+-------+------| | |
2893 | | | Student | Prob 1 | Prob 2 | Prob 3 | Total | Note | | |
2894 | |---+---------+--------+--------+--------+-------+------| | |
2895 | | ! | | P1 | P2 | P3 | Tot | | | |
2896 | | # | Maximum | 10 | 15 | 25 | 50 | 10.0 | | |
2897 | | ^ | | m1 | m2 | m3 | mt | | | |
2898 | |---+---------+--------+--------+--------+-------+------| | |
2899 | | # | Peter | 10 | 8 | 23 | 41 | 8.2 | | |
4009494e GM |
2900 | | # | Sam | 2 | 4 | 3 | 9 | 1.8 | |
2901 | |---+---------+--------+--------+--------+-------+------| | |
2902 | | | Average | | | | 29.7 | | | |
2903 | | ^ | | | | | at | | | |
2904 | | $ | max=50 | | | | | | | |
2905 | |---+---------+--------+--------+--------+-------+------| | |
2906 | #+TBLFM: $6=vsum($P1..$P3)::$7=10*$Tot/$max;%.1f::$at=vmean(@@-II..@@-I);%.1f | |
2907 | @end group | |
2908 | @end example | |
2909 | ||
c8d0cf5c | 2910 | @noindent @b{Important}: please note that for these special tables, |
4009494e GM |
2911 | recalculating the table with @kbd{C-u C-c *} will only affect rows that |
2912 | are marked @samp{#} or @samp{*}, and fields that have a formula assigned | |
2913 | to the field itself. The column formulas are not applied in rows with | |
2914 | empty first field. | |
2915 | ||
2916 | @cindex marking characters, tables | |
2917 | The marking characters have the following meaning: | |
2918 | @table @samp | |
2919 | @item ! | |
2920 | The fields in this line define names for the columns, so that you may | |
2921 | refer to a column as @samp{$Tot} instead of @samp{$6}. | |
2922 | @item ^ | |
2923 | This row defines names for the fields @emph{above} the row. With such | |
2924 | a definition, any formula in the table may use @samp{$m1} to refer to | |
2925 | the value @samp{10}. Also, if you assign a formula to a names field, it | |
2926 | will be stored as @samp{$name=...}. | |
2927 | @item _ | |
2928 | Similar to @samp{^}, but defines names for the fields in the row | |
2929 | @emph{below}. | |
2930 | @item $ | |
2931 | Fields in this row can define @emph{parameters} for formulas. For | |
2932 | example, if a field in a @samp{$} row contains @samp{max=50}, then | |
2933 | formulas in this table can refer to the value 50 using @samp{$max}. | |
2934 | Parameters work exactly like constants, only that they can be defined on | |
2935 | a per-table basis. | |
2936 | @item # | |
2937 | Fields in this row are automatically recalculated when pressing | |
2938 | @key{TAB} or @key{RET} or @kbd{S-@key{TAB}} in this row. Also, this row | |
2939 | is selected for a global recalculation with @kbd{C-u C-c *}. Unmarked | |
2940 | lines will be left alone by this command. | |
2941 | @item * | |
2942 | Selects this line for global recalculation with @kbd{C-u C-c *}, but | |
2943 | not for automatic recalculation. Use this when automatic | |
2944 | recalculation slows down editing too much. | |
2945 | @item | |
2946 | Unmarked lines are exempt from recalculation with @kbd{C-u C-c *}. | |
2947 | All lines that should be recalculated should be marked with @samp{#} | |
2948 | or @samp{*}. | |
2949 | @item / | |
2950 | Do not export this line. Useful for lines that contain the narrowing | |
6eb02347 | 2951 | @samp{<N>} markers or column group markers. |
4009494e GM |
2952 | @end table |
2953 | ||
c8d0cf5c CD |
2954 | Finally, just to whet your appetite for what can be done with the |
2955 | fantastic @file{calc.el} package, here is a table that computes the Taylor | |
28a16a1b CD |
2956 | series of degree @code{n} at location @code{x} for a couple of |
2957 | functions. | |
4009494e GM |
2958 | |
2959 | @example | |
2960 | @group | |
2961 | |---+-------------+---+-----+--------------------------------------| | |
2962 | | | Func | n | x | Result | | |
2963 | |---+-------------+---+-----+--------------------------------------| | |
2964 | | # | exp(x) | 1 | x | 1 + x | | |
2965 | | # | exp(x) | 2 | x | 1 + x + x^2 / 2 | | |
2966 | | # | exp(x) | 3 | x | 1 + x + x^2 / 2 + x^3 / 6 | | |
2967 | | # | x^2+sqrt(x) | 2 | x=0 | x*(0.5 / 0) + x^2 (2 - 0.25 / 0) / 2 | | |
2968 | | # | x^2+sqrt(x) | 2 | x=1 | 2 + 2.5 x - 2.5 + 0.875 (x - 1)^2 | | |
2969 | | * | tan(x) | 3 | x | 0.0175 x + 1.77e-6 x^3 | | |
2970 | |---+-------------+---+-----+--------------------------------------| | |
2971 | #+TBLFM: $5=taylor($2,$4,$3);n3 | |
2972 | @end group | |
2973 | @end example | |
2974 | ||
c8d0cf5c CD |
2975 | @node Org-Plot, , The spreadsheet, Tables |
2976 | @section Org-Plot | |
864c9740 | 2977 | @cindex graph, in tables |
86fbb8ca | 2978 | @cindex plot tables using Gnuplot |
c8d0cf5c | 2979 | @cindex #+PLOT |
864c9740 | 2980 | |
c8d0cf5c | 2981 | Org-Plot can produce 2D and 3D graphs of information stored in org tables |
71d35b24 CD |
2982 | using @file{Gnuplot} @uref{http://www.gnuplot.info/} and @file{gnuplot-mode} |
2983 | @uref{http://cars9.uchicago.edu/~ravel/software/gnuplot-mode.html}. To see | |
c8d0cf5c | 2984 | this in action, ensure that you have both Gnuplot and Gnuplot mode installed |
71d35b24 | 2985 | on your system, then call @code{org-plot/gnuplot} on the following table. |
864c9740 CD |
2986 | |
2987 | @example | |
2988 | @group | |
2989 | #+PLOT: title:"Citas" ind:1 deps:(3) type:2d with:histograms set:"yrange [0:]" | |
2990 | | Sede | Max cites | H-index | | |
2991 | |-----------+-----------+---------| | |
2992 | | Chile | 257.72 | 21.39 | | |
2993 | | Leeds | 165.77 | 19.68 | | |
2994 | | Sao Paolo | 71.00 | 11.50 | | |
2995 | | Stockholm | 134.19 | 14.33 | | |
2996 | | Morelia | 257.56 | 17.67 | | |
2997 | @end group | |
2998 | @end example | |
2999 | ||
c8d0cf5c | 3000 | Notice that Org Plot is smart enough to apply the table's headers as labels. |
864c9740 | 3001 | Further control over the labels, type, content, and appearance of plots can |
c8d0cf5c CD |
3002 | be exercised through the @code{#+PLOT:} lines preceding a table. See below |
3003 | for a complete list of Org-plot options. For more information and examples | |
3004 | see the Org-plot tutorial at | |
ce57c2fe | 3005 | @uref{http://orgmode.org/worg/org-tutorials/org-plot.html}. |
864c9740 CD |
3006 | |
3007 | @subsubheading Plot Options | |
3008 | ||
3009 | @table @code | |
3010 | @item set | |
c8d0cf5c | 3011 | Specify any @command{gnuplot} option to be set when graphing. |
864c9740 CD |
3012 | |
3013 | @item title | |
3014 | Specify the title of the plot. | |
3015 | ||
3016 | @item ind | |
3017 | Specify which column of the table to use as the @code{x} axis. | |
3018 | ||
3019 | @item deps | |
c8d0cf5c | 3020 | Specify the columns to graph as a Lisp style list, surrounded by parentheses |
71d35b24 | 3021 | and separated by spaces for example @code{dep:(3 4)} to graph the third and |
c8d0cf5c | 3022 | fourth columns (defaults to graphing all other columns aside from the @code{ind} |
71d35b24 | 3023 | column). |
864c9740 CD |
3024 | |
3025 | @item type | |
3026 | Specify whether the plot will be @code{2d}, @code{3d}, or @code{grid}. | |
3027 | ||
3028 | @item with | |
3029 | Specify a @code{with} option to be inserted for every col being plotted | |
ce57c2fe | 3030 | (e.g.@: @code{lines}, @code{points}, @code{boxes}, @code{impulses}, etc...). |
223b43fa | 3031 | Defaults to @code{lines}. |
864c9740 CD |
3032 | |
3033 | @item file | |
c8d0cf5c | 3034 | If you want to plot to a file, specify @code{"@var{path/to/desired/output-file}"}. |
864c9740 CD |
3035 | |
3036 | @item labels | |
acedf35c CD |
3037 | List of labels to be used for the @code{deps} (defaults to the column headers |
3038 | if they exist). | |
864c9740 CD |
3039 | |
3040 | @item line | |
c8d0cf5c | 3041 | Specify an entire line to be inserted in the Gnuplot script. |
864c9740 CD |
3042 | |
3043 | @item map | |
3044 | When plotting @code{3d} or @code{grid} types, set this to @code{t} to graph a | |
3045 | flat mapping rather than a @code{3d} slope. | |
3046 | ||
e45e3595 | 3047 | @item timefmt |
e66ba1df | 3048 | Specify format of Org mode timestamps as they will be parsed by Gnuplot. |
223b43fa | 3049 | Defaults to @samp{%Y-%m-%d-%H:%M:%S}. |
e45e3595 | 3050 | |
864c9740 | 3051 | @item script |
c8d0cf5c CD |
3052 | If you want total control, you can specify a script file (place the file name |
3053 | between double-quotes) which will be used to plot. Before plotting, every | |
864c9740 | 3054 | instance of @code{$datafile} in the specified script will be replaced with |
c8d0cf5c | 3055 | the path to the generated data file. Note: even if you set this option, you |
864c9740 CD |
3056 | may still want to specify the plot type, as that can impact the content of |
3057 | the data file. | |
3058 | @end table | |
3059 | ||
a7808fba | 3060 | @node Hyperlinks, TODO Items, Tables, Top |
4009494e GM |
3061 | @chapter Hyperlinks |
3062 | @cindex hyperlinks | |
3063 | ||
a7808fba | 3064 | Like HTML, Org provides links inside a file, external links to |
dbc28aaa | 3065 | other files, Usenet articles, emails, and much more. |
4009494e GM |
3066 | |
3067 | @menu | |
c0468714 GM |
3068 | * Link format:: How links in Org are formatted |
3069 | * Internal links:: Links to other places in the current file | |
3070 | * External links:: URL-like links to the world | |
3071 | * Handling links:: Creating, inserting and following | |
3072 | * Using links outside Org:: Linking from my C source code? | |
3073 | * Link abbreviations:: Shortcuts for writing complex links | |
3074 | * Search options:: Linking to a specific location | |
3075 | * Custom searches:: When the default search is not enough | |
4009494e GM |
3076 | @end menu |
3077 | ||
3078 | @node Link format, Internal links, Hyperlinks, Hyperlinks | |
3079 | @section Link format | |
3080 | @cindex link format | |
3081 | @cindex format, of links | |
3082 | ||
a7808fba | 3083 | Org will recognize plain URL-like links and activate them as |
4009494e GM |
3084 | clickable links. The general link format, however, looks like this: |
3085 | ||
3086 | @example | |
28a16a1b | 3087 | [[link][description]] @r{or alternatively} [[link]] |
4009494e GM |
3088 | @end example |
3089 | ||
c8d0cf5c | 3090 | @noindent |
a7808fba | 3091 | Once a link in the buffer is complete (all brackets present), Org |
4009494e GM |
3092 | will change the display so that @samp{description} is displayed instead |
3093 | of @samp{[[link][description]]} and @samp{link} is displayed instead of | |
3094 | @samp{[[link]]}. Links will be highlighted in the face @code{org-link}, | |
3095 | which by default is an underlined face. You can directly edit the | |
3096 | visible part of a link. Note that this can be either the @samp{link} | |
3097 | part (if there is no description) or the @samp{description} part. To | |
3098 | edit also the invisible @samp{link} part, use @kbd{C-c C-l} with the | |
3099 | cursor on the link. | |
3100 | ||
3101 | If you place the cursor at the beginning or just behind the end of the | |
3102 | displayed text and press @key{BACKSPACE}, you will remove the | |
3103 | (invisible) bracket at that location. This makes the link incomplete | |
3104 | and the internals are again displayed as plain text. Inserting the | |
3105 | missing bracket hides the link internals again. To show the | |
3106 | internal structure of all links, use the menu entry | |
3107 | @code{Org->Hyperlinks->Literal links}. | |
3108 | ||
3109 | @node Internal links, External links, Link format, Hyperlinks | |
3110 | @section Internal links | |
3111 | @cindex internal links | |
3112 | @cindex links, internal | |
3113 | @cindex targets, for links | |
3114 | ||
c8d0cf5c CD |
3115 | @cindex property, CUSTOM_ID |
3116 | If the link does not look like a URL, it is considered to be internal in the | |
3117 | current file. The most important case is a link like | |
3118 | @samp{[[#my-custom-id]]} which will link to the entry with the | |
3119 | @code{CUSTOM_ID} property @samp{my-custom-id}. Such custom IDs are very good | |
3120 | for HTML export (@pxref{HTML export}) where they produce pretty section | |
3121 | links. You are responsible yourself to make sure these custom IDs are unique | |
3122 | in a file. | |
3123 | ||
3124 | Links such as @samp{[[My Target]]} or @samp{[[My Target][Find my target]]} | |
3125 | lead to a text search in the current file. | |
3126 | ||
3127 | The link can be followed with @kbd{C-c C-o} when the cursor is on the link, | |
3128 | or with a mouse click (@pxref{Handling links}). Links to custom IDs will | |
3129 | point to the corresponding headline. The preferred match for a text link is | |
3130 | a @i{dedicated target}: the same string in double angular brackets. Targets | |
3131 | may be located anywhere; sometimes it is convenient to put them into a | |
ce57c2fe | 3132 | comment line. For example |
4009494e GM |
3133 | |
3134 | @example | |
3135 | # <<My Target>> | |
3136 | @end example | |
3137 | ||
3138 | @noindent In HTML export (@pxref{HTML export}), such targets will become | |
64fb801f CD |
3139 | named anchors for direct access through @samp{http} links@footnote{Note that |
3140 | text before the first headline is usually not exported, so the first such | |
3141 | target should be after the first headline, or in the line directly before the | |
3142 | first headline.}. | |
4009494e | 3143 | |
afe98dfa CD |
3144 | If no dedicated target exists, Org will search for a headline that is exactly |
3145 | the link text but may also include a TODO keyword and tags@footnote{To insert | |
3146 | a link targeting a headline, in-buffer completion can be used. Just type a | |
3147 | star followed by a few optional letters into the buffer and press | |
3148 | @kbd{M-@key{TAB}}. All headlines in the current buffer will be offered as | |
3149 | completions.}. In non-Org files, the search will look for the words in the | |
acedf35c | 3150 | link text. In the above example the search would be for @samp{my target}. |
4009494e | 3151 | |
a7808fba | 3152 | Following a link pushes a mark onto Org's own mark ring. You can |
4009494e GM |
3153 | return to the previous position with @kbd{C-c &}. Using this command |
3154 | several times in direct succession goes back to positions recorded | |
3155 | earlier. | |
3156 | ||
3157 | @menu | |
c0468714 | 3158 | * Radio targets:: Make targets trigger links in plain text |
4009494e GM |
3159 | @end menu |
3160 | ||
3161 | @node Radio targets, , Internal links, Internal links | |
3162 | @subsection Radio targets | |
3163 | @cindex radio targets | |
3164 | @cindex targets, radio | |
3165 | @cindex links, radio targets | |
3166 | ||
a7808fba | 3167 | Org can automatically turn any occurrences of certain target names |
4009494e GM |
3168 | in normal text into a link. So without explicitly creating a link, the |
3169 | text connects to the target radioing its position. Radio targets are | |
3170 | enclosed by triple angular brackets. For example, a target @samp{<<<My | |
3171 | Target>>>} causes each occurrence of @samp{my target} in normal text to | |
a7808fba | 3172 | become activated as a link. The Org file is scanned automatically |
4009494e GM |
3173 | for radio targets only when the file is first loaded into Emacs. To |
3174 | update the target list during editing, press @kbd{C-c C-c} with the | |
3175 | cursor on or at a target. | |
3176 | ||
3177 | @node External links, Handling links, Internal links, Hyperlinks | |
3178 | @section External links | |
3179 | @cindex links, external | |
3180 | @cindex external links | |
3181 | @cindex links, external | |
a7808fba | 3182 | @cindex Gnus links |
4009494e | 3183 | @cindex BBDB links |
28a16a1b | 3184 | @cindex IRC links |
4009494e GM |
3185 | @cindex URL links |
3186 | @cindex file links | |
3187 | @cindex VM links | |
3188 | @cindex RMAIL links | |
3189 | @cindex WANDERLUST links | |
3190 | @cindex MH-E links | |
3191 | @cindex USENET links | |
3192 | @cindex SHELL links | |
3193 | @cindex Info links | |
c8d0cf5c | 3194 | @cindex Elisp links |
4009494e | 3195 | |
a7808fba | 3196 | Org supports links to files, websites, Usenet and email messages, |
28a16a1b CD |
3197 | BBDB database entries and links to both IRC conversations and their |
3198 | logs. External links are URL-like locators. They start with a short | |
3199 | identifying string followed by a colon. There can be no space after | |
3200 | the colon. The following list shows examples for each link type. | |
4009494e GM |
3201 | |
3202 | @example | |
a7808fba | 3203 | http://www.astro.uva.nl/~dominik @r{on the web} |
86fbb8ca | 3204 | doi:10.1000/182 @r{DOI for an electronic resource} |
4009494e | 3205 | file:/home/dominik/images/jupiter.jpg @r{file, absolute path} |
44ce9197 | 3206 | /home/dominik/images/jupiter.jpg @r{same as above} |
4009494e | 3207 | file:papers/last.pdf @r{file, relative path} |
44ce9197 | 3208 | ./papers/last.pdf @r{same as above} |
ed21c5c8 CD |
3209 | file:/myself@@some.where:papers/last.pdf @r{file, path on remote machine} |
3210 | /myself@@some.where:papers/last.pdf @r{same as above} | |
e66ba1df | 3211 | file:sometextfile::NNN @r{file, jump to line number} |
c8d0cf5c | 3212 | file:projects.org @r{another Org file} |
e66ba1df BG |
3213 | file:projects.org::some words @r{text search in Org file}@footnote{ |
3214 | The actual behavior of the search will depend on the value of | |
3215 | the variable @code{org-link-search-must-match-exact-headline}. If its value | |
3216 | is nil, then a fuzzy text search will be done. If it is t, then only the | |
3217 | exact headline will be matched. If the value is @code{'query-to-create}, | |
3218 | then an exact headline will be searched; if it is not found, then the user | |
3219 | will be queried to create it.} | |
c8d0cf5c | 3220 | file:projects.org::*task title @r{heading search in Org file} |
e66ba1df BG |
3221 | file+sys:/path/to/file @r{open via OS, like double-click} |
3222 | file+emacs:/path/to/file @r{force opening by Emacs} | |
3223 | docview:papers/last.pdf::NNN @r{open in doc-view mode at page} | |
55e0839d | 3224 | id:B7423F4D-2E8A-471B-8810-C40F074717E9 @r{Link to heading by ID} |
4009494e | 3225 | news:comp.emacs @r{Usenet link} |
55e0839d | 3226 | mailto:adent@@galaxy.net @r{Mail link} |
4009494e GM |
3227 | vm:folder @r{VM folder link} |
3228 | vm:folder#id @r{VM message link} | |
55e0839d | 3229 | vm://myself@@some.where.org/folder#id @r{VM on remote machine} |
4009494e GM |
3230 | wl:folder @r{WANDERLUST folder link} |
3231 | wl:folder#id @r{WANDERLUST message link} | |
3232 | mhe:folder @r{MH-E folder link} | |
3233 | mhe:folder#id @r{MH-E message link} | |
3234 | rmail:folder @r{RMAIL folder link} | |
3235 | rmail:folder#id @r{RMAIL message link} | |
a7808fba CD |
3236 | gnus:group @r{Gnus group link} |
3237 | gnus:group#id @r{Gnus article link} | |
64fb801f | 3238 | bbdb:R.*Stallman @r{BBDB link (with regexp)} |
28a16a1b | 3239 | irc:/irc.com/#emacs/bob @r{IRC link} |
e66ba1df | 3240 | info:org#External links @r{Info node link} |
4009494e | 3241 | shell:ls *.org @r{A shell command} |
c8d0cf5c | 3242 | elisp:org-agenda @r{Interactive Elisp command} |
64fb801f | 3243 | elisp:(find-file-other-frame "Elisp.org") @r{Elisp form to evaluate} |
4009494e GM |
3244 | @end example |
3245 | ||
ce57c2fe BG |
3246 | For customizing Org to add new link types @ref{Adding hyperlink types}. |
3247 | ||
4009494e | 3248 | A link should be enclosed in double brackets and may contain a |
a7808fba | 3249 | descriptive text to be displayed instead of the URL (@pxref{Link |
4009494e GM |
3250 | format}), for example: |
3251 | ||
3252 | @example | |
3253 | [[http://www.gnu.org/software/emacs/][GNU Emacs]] | |
3254 | @end example | |
3255 | ||
3256 | @noindent | |
3257 | If the description is a file name or URL that points to an image, HTML | |
3258 | export (@pxref{HTML export}) will inline the image as a clickable | |
3259 | button. If there is no description at all and the link points to an | |
3260 | image, | |
3261 | that image will be inlined into the exported HTML file. | |
3262 | ||
c8d0cf5c | 3263 | @cindex square brackets, around links |
4009494e | 3264 | @cindex plain text external links |
a7808fba | 3265 | Org also finds external links in the normal text and activates them |
4009494e GM |
3266 | as links. If spaces must be part of the link (for example in |
3267 | @samp{bbdb:Richard Stallman}), or if you need to remove ambiguities | |
c8d0cf5c | 3268 | about the end of the link, enclose them in square brackets. |
4009494e | 3269 | |
a7808fba | 3270 | @node Handling links, Using links outside Org, External links, Hyperlinks |
4009494e GM |
3271 | @section Handling links |
3272 | @cindex links, handling | |
3273 | ||
a7808fba CD |
3274 | Org provides methods to create a link in the correct syntax, to |
3275 | insert it into an Org file, and to follow the link. | |
4009494e GM |
3276 | |
3277 | @table @kbd | |
acedf35c | 3278 | @orgcmd{C-c l,org-store-link} |
4009494e | 3279 | @cindex storing links |
55e0839d CD |
3280 | Store a link to the current location. This is a @emph{global} command (you |
3281 | must create the key binding yourself) which can be used in any buffer to | |
3282 | create a link. The link will be stored for later insertion into an Org | |
c8d0cf5c CD |
3283 | buffer (see below). What kind of link will be created depends on the current |
3284 | buffer: | |
55e0839d | 3285 | |
e66ba1df | 3286 | @b{Org mode buffers}@* |
55e0839d | 3287 | For Org files, if there is a @samp{<<target>>} at the cursor, the link points |
c8d0cf5c | 3288 | to the target. Otherwise it points to the current headline, which will also |
ce57c2fe BG |
3289 | be the description@footnote{If the headline contains a timestamp, it will be |
3290 | removed from the link and result in a wrong link -- you should avoid putting | |
3291 | timestamp in the headline.}. | |
c8d0cf5c CD |
3292 | |
3293 | @vindex org-link-to-org-use-id | |
3294 | @cindex property, CUSTOM_ID | |
3295 | @cindex property, ID | |
3296 | If the headline has a @code{CUSTOM_ID} property, a link to this custom ID | |
3297 | will be stored. In addition or alternatively (depending on the value of | |
3298 | @code{org-link-to-org-use-id}), a globally unique @code{ID} property will be | |
3299 | created and/or used to construct a link. So using this command in Org | |
3300 | buffers will potentially create two links: a human-readable from the custom | |
3301 | ID, and one that is globally unique and works even if the entry is moved from | |
3302 | file to file. Later, when inserting the link, you need to decide which one | |
3303 | to use. | |
3304 | ||
3305 | @b{Email/News clients: VM, Rmail, Wanderlust, MH-E, Gnus}@* | |
3306 | Pretty much all Emacs mail clients are supported. The link will point to the | |
3307 | current article, or, in some GNUS buffers, to the group. The description is | |
3308 | constructed from the author and the subject. | |
3309 | ||
3310 | @b{Web browsers: W3 and W3M}@* | |
3311 | Here the link will be the current URL, with the page title as description. | |
3312 | ||
3313 | @b{Contacts: BBDB}@* | |
3314 | Links created in a BBDB buffer will point to the current entry. | |
3315 | ||
3316 | @b{Chat: IRC}@* | |
3317 | @vindex org-irc-link-to-logs | |
3318 | For IRC links, if you set the variable @code{org-irc-link-to-logs} to | |
3319 | @code{t}, a @samp{file:/} style link to the relevant point in the logs for | |
3320 | the current conversation is created. Otherwise an @samp{irc:/} style link to | |
3321 | the user/channel/server under the point will be stored. | |
3322 | ||
3323 | @b{Other files}@* | |
55e0839d CD |
3324 | For any other files, the link will point to the file, with a search string |
3325 | (@pxref{Search options}) pointing to the contents of the current line. If | |
3326 | there is an active region, the selected words will form the basis of the | |
3327 | search string. If the automatically created link is not working correctly or | |
3328 | accurately enough, you can write custom functions to select the search string | |
c8d0cf5c CD |
3329 | and to do the search for particular file types---see @ref{Custom searches}. |
3330 | The key binding @kbd{C-c l} is only a suggestion---see @ref{Installation}. | |
7006d207 CD |
3331 | |
3332 | @b{Agenda view}@* | |
3333 | When the cursor is in an agenda view, the created link points to the | |
3334 | entry referenced by the current line. | |
3335 | ||
4009494e | 3336 | @c |
acedf35c | 3337 | @orgcmd{C-c C-l,org-insert-link} |
4009494e GM |
3338 | @cindex link completion |
3339 | @cindex completion, of links | |
3340 | @cindex inserting links | |
c8d0cf5c CD |
3341 | @vindex org-keep-stored-link-after-insertion |
3342 | Insert a link@footnote{ Note that you don't have to use this command to | |
3343 | insert a link. Links in Org are plain text, and you can type or paste them | |
3344 | straight into the buffer. By using this command, the links are automatically | |
3345 | enclosed in double brackets, and you will be asked for the optional | |
3346 | descriptive text.}. This prompts for a link to be inserted into the buffer. | |
3347 | You can just type a link, using text for an internal link, or one of the link | |
3348 | type prefixes mentioned in the examples above. The link will be inserted | |
3349 | into the buffer@footnote{After insertion of a stored link, the link will be | |
3350 | removed from the list of stored links. To keep it in the list later use, use | |
3351 | a triple @kbd{C-u} prefix argument to @kbd{C-c C-l}, or configure the option | |
a7808fba CD |
3352 | @code{org-keep-stored-link-after-insertion}.}, along with a descriptive text. |
3353 | If some text was selected when this command is called, the selected text | |
c8d0cf5c CD |
3354 | becomes the default description. |
3355 | ||
3356 | @b{Inserting stored links}@* | |
3357 | All links stored during the | |
3358 | current session are part of the history for this prompt, so you can access | |
3359 | them with @key{up} and @key{down} (or @kbd{M-p/n}). | |
3360 | ||
3361 | @b{Completion support}@* Completion with @key{TAB} will help you to insert | |
3362 | valid link prefixes like @samp{http:} or @samp{ftp:}, including the prefixes | |
3363 | defined through link abbreviations (@pxref{Link abbreviations}). If you | |
3364 | press @key{RET} after inserting only the @var{prefix}, Org will offer | |
3365 | specific completion support for some link types@footnote{This works by | |
3366 | calling a special function @code{org-PREFIX-complete-link}.} For | |
3367 | example, if you type @kbd{file @key{RET}}, file name completion (alternative | |
3368 | access: @kbd{C-u C-c C-l}, see below) will be offered, and after @kbd{bbdb | |
3369 | @key{RET}} you can complete contact names. | |
acedf35c | 3370 | @orgkey C-u C-c C-l |
4009494e GM |
3371 | @cindex file name completion |
3372 | @cindex completion, of file names | |
4009494e GM |
3373 | When @kbd{C-c C-l} is called with a @kbd{C-u} prefix argument, a link to |
3374 | a file will be inserted and you may use file name completion to select | |
3375 | the name of the file. The path to the file is inserted relative to the | |
c8d0cf5c | 3376 | directory of the current Org file, if the linked file is in the current |
a7808fba | 3377 | directory or in a sub-directory of it, or if the path is written relative |
4009494e GM |
3378 | to the current directory using @samp{../}. Otherwise an absolute path |
3379 | is used, if possible with @samp{~/} for your home directory. You can | |
3380 | force an absolute path with two @kbd{C-u} prefixes. | |
3381 | @c | |
86fbb8ca | 3382 | @item C-c C-l @ @r{(with cursor on existing link)} |
4009494e GM |
3383 | When the cursor is on an existing link, @kbd{C-c C-l} allows you to edit the |
3384 | link and description parts of the link. | |
3385 | @c | |
3386 | @cindex following links | |
acedf35c | 3387 | @orgcmd{C-c C-o,org-open-at-point} |
c8d0cf5c | 3388 | @vindex org-file-apps |
e66ba1df | 3389 | @vindex org-link-frame-setup |
4009494e | 3390 | Open link at point. This will launch a web browser for URLs (using |
864c9740 CD |
3391 | @command{browse-url-at-point}), run VM/MH-E/Wanderlust/Rmail/Gnus/BBDB for |
3392 | the corresponding links, and execute the command in a shell link. When the | |
04d3bb6c | 3393 | cursor is on an internal link, this command runs the corresponding search. |
864c9740 | 3394 | When the cursor is on a TAG list in a headline, it creates the corresponding |
c8d0cf5c | 3395 | TAGS view. If the cursor is on a timestamp, it compiles the agenda for that |
864c9740 CD |
3396 | date. Furthermore, it will visit text and remote files in @samp{file:} links |
3397 | with Emacs and select a suitable application for local non-text files. | |
3398 | Classification of files is based on file extension only. See option | |
3399 | @code{org-file-apps}. If you want to override the default application and | |
e45e3595 | 3400 | visit the file with Emacs, use a @kbd{C-u} prefix. If you want to avoid |
6eb02347 CD |
3401 | opening in Emacs, use a @kbd{C-u C-u} prefix.@* |
3402 | If the cursor is on a headline, but not on a link, offer all links in the | |
e66ba1df BG |
3403 | headline and entry text. If you want to setup the frame configuration for |
3404 | following links, customize @code{org-link-frame-setup}. | |
3405 | ||
acedf35c CD |
3406 | @orgkey @key{RET} |
3407 | @vindex org-return-follows-link | |
3408 | When @code{org-return-follows-link} is set, @kbd{@key{RET}} will also follow | |
3409 | the link at point. | |
4009494e GM |
3410 | @c |
3411 | @kindex mouse-2 | |
3412 | @kindex mouse-1 | |
3413 | @item mouse-2 | |
3414 | @itemx mouse-1 | |
3415 | On links, @kbd{mouse-2} will open the link just as @kbd{C-c C-o} | |
acedf35c | 3416 | would. Under Emacs 22 and later, @kbd{mouse-1} will also follow a link. |
4009494e GM |
3417 | @c |
3418 | @kindex mouse-3 | |
3419 | @item mouse-3 | |
c8d0cf5c | 3420 | @vindex org-display-internal-link-with-indirect-buffer |
4009494e GM |
3421 | Like @kbd{mouse-2}, but force file links to be opened with Emacs, and |
3422 | internal links to be displayed in another window@footnote{See the | |
3423 | variable @code{org-display-internal-link-with-indirect-buffer}}. | |
3424 | @c | |
acedf35c | 3425 | @orgcmd{C-c C-x C-v,org-toggle-inline-images} |
86fbb8ca CD |
3426 | @cindex inlining images |
3427 | @cindex images, inlining | |
afe98dfa CD |
3428 | @vindex org-startup-with-inline-images |
3429 | @cindex @code{inlineimages}, STARTUP keyword | |
3430 | @cindex @code{noinlineimages}, STARTUP keyword | |
86fbb8ca | 3431 | Toggle the inline display of linked images. Normally this will only inline |
ce57c2fe | 3432 | images that have no description part in the link, i.e.@: images that will also |
86fbb8ca | 3433 | be inlined during export. When called with a prefix argument, also display |
afe98dfa CD |
3434 | images that do have a link description. You can ask for inline images to be |
3435 | displayed at startup by configuring the variable | |
3436 | @code{org-startup-with-inline-images}@footnote{with corresponding | |
3437 | @code{#+STARTUP} keywords @code{inlineimages} and @code{inlineimages}}. | |
acedf35c | 3438 | @orgcmd{C-c %,org-mark-ring-push} |
4009494e | 3439 | @cindex mark ring |
4009494e | 3440 | Push the current position onto the mark ring, to be able to return |
ce57c2fe | 3441 | easily. Commands following an internal link do this automatically. |
4009494e | 3442 | @c |
acedf35c | 3443 | @orgcmd{C-c &,org-mark-ring-goto} |
4009494e | 3444 | @cindex links, returning to |
4009494e GM |
3445 | Jump back to a recorded position. A position is recorded by the |
3446 | commands following internal links, and by @kbd{C-c %}. Using this | |
3447 | command several times in direct succession moves through a ring of | |
3448 | previously recorded positions. | |
3449 | @c | |
acedf35c | 3450 | @orgcmdkkcc{C-c C-x C-n,C-c C-x C-p,org-next-link,org-previous-link} |
4009494e | 3451 | @cindex links, finding next/previous |
4009494e GM |
3452 | Move forward/backward to the next link in the buffer. At the limit of |
3453 | the buffer, the search fails once, and then wraps around. The key | |
acedf35c | 3454 | bindings for this are really too long; you might want to bind this also |
4009494e GM |
3455 | to @kbd{C-n} and @kbd{C-p} |
3456 | @lisp | |
3457 | (add-hook 'org-load-hook | |
3458 | (lambda () | |
ce57c2fe BG |
3459 | (define-key org-mode-map "\C-n" 'org-next-link) |
3460 | (define-key org-mode-map "\C-p" 'org-previous-link))) | |
4009494e GM |
3461 | @end lisp |
3462 | @end table | |
3463 | ||
a7808fba CD |
3464 | @node Using links outside Org, Link abbreviations, Handling links, Hyperlinks |
3465 | @section Using links outside Org | |
4009494e | 3466 | |
a7808fba CD |
3467 | You can insert and follow links that have Org syntax not only in |
3468 | Org, but in any Emacs buffer. For this, you should create two | |
4009494e GM |
3469 | global commands, like this (please select suitable global keys |
3470 | yourself): | |
3471 | ||
3472 | @lisp | |
3473 | (global-set-key "\C-c L" 'org-insert-link-global) | |
3474 | (global-set-key "\C-c o" 'org-open-at-point-global) | |
3475 | @end lisp | |
3476 | ||
a7808fba | 3477 | @node Link abbreviations, Search options, Using links outside Org, Hyperlinks |
4009494e GM |
3478 | @section Link abbreviations |
3479 | @cindex link abbreviations | |
3480 | @cindex abbreviation, links | |
3481 | ||
3482 | Long URLs can be cumbersome to type, and often many similar links are | |
3483 | needed in a document. For this you can use link abbreviations. An | |
3484 | abbreviated link looks like this | |
3485 | ||
3486 | @example | |
3487 | [[linkword:tag][description]] | |
3488 | @end example | |
3489 | ||
3490 | @noindent | |
c8d0cf5c | 3491 | @vindex org-link-abbrev-alist |
86fbb8ca CD |
3492 | where the tag is optional. |
3493 | The @i{linkword} must be a word, starting with a letter, followed by | |
3494 | letters, numbers, @samp{-}, and @samp{_}. Abbreviations are resolved | |
c8d0cf5c CD |
3495 | according to the information in the variable @code{org-link-abbrev-alist} |
3496 | that relates the linkwords to replacement text. Here is an example: | |
4009494e | 3497 | |
afe98dfa | 3498 | @smalllisp |
4009494e GM |
3499 | @group |
3500 | (setq org-link-abbrev-alist | |
3501 | '(("bugzilla" . "http://10.1.2.9/bugzilla/show_bug.cgi?id=") | |
3502 | ("google" . "http://www.google.com/search?q=") | |
afe98dfa CD |
3503 | ("gmap" . "http://maps.google.com/maps?q=%s") |
3504 | ("omap" . "http://nominatim.openstreetmap.org/search?q=%s&polygon=1") | |
3505 | ("ads" . "http://adsabs.harvard.edu/cgi-bin/nph-abs_connect?author=%s&db_key=AST"))) | |
4009494e | 3506 | @end group |
afe98dfa | 3507 | @end smalllisp |
4009494e GM |
3508 | |
3509 | If the replacement text contains the string @samp{%s}, it will be | |
3510 | replaced with the tag. Otherwise the tag will be appended to the string | |
3511 | in order to create the link. You may also specify a function that will | |
3512 | be called with the tag as the only argument to create the link. | |
3513 | ||
3514 | With the above setting, you could link to a specific bug with | |
3515 | @code{[[bugzilla:129]]}, search the web for @samp{OrgMode} with | |
afe98dfa CD |
3516 | @code{[[google:OrgMode]]}, show the map location of the Free Software |
3517 | Foundation @code{[[gmap:51 Franklin Street, Boston]]} or of Carsten office | |
3518 | @code{[[omap:Science Park 904, Amsterdam, The Netherlands]]} and find out | |
3519 | what the Org author is doing besides Emacs hacking with | |
3520 | @code{[[ads:Dominik,C]]}. | |
4009494e | 3521 | |
a7808fba | 3522 | If you need special abbreviations just for a single Org buffer, you |
4009494e GM |
3523 | can define them in the file with |
3524 | ||
c8d0cf5c | 3525 | @cindex #+LINK |
4009494e GM |
3526 | @example |
3527 | #+LINK: bugzilla http://10.1.2.9/bugzilla/show_bug.cgi?id= | |
3528 | #+LINK: google http://www.google.com/search?q=%s | |
3529 | @end example | |
3530 | ||
3531 | @noindent | |
c8d0cf5c CD |
3532 | In-buffer completion (@pxref{Completion}) can be used after @samp{[} to |
3533 | complete link abbreviations. You may also define a function | |
ce57c2fe | 3534 | @code{org-PREFIX-complete-link} that implements special (e.g.@: completion) |
c8d0cf5c CD |
3535 | support for inserting such a link with @kbd{C-c C-l}. Such a function should |
3536 | not accept any arguments, and return the full link with prefix. | |
4009494e GM |
3537 | |
3538 | @node Search options, Custom searches, Link abbreviations, Hyperlinks | |
3539 | @section Search options in file links | |
3540 | @cindex search option in file links | |
3541 | @cindex file links, searching | |
3542 | ||
3543 | File links can contain additional information to make Emacs jump to a | |
3544 | particular location in the file when following a link. This can be a | |
3545 | line number or a search option after a double@footnote{For backward | |
ce57c2fe | 3546 | compatibility, line numbers can also follow a single colon.} colon. For |
4009494e GM |
3547 | example, when the command @kbd{C-c l} creates a link (@pxref{Handling |
3548 | links}) to a file, it encodes the words in the current line as a search | |
3549 | string that can be used to find this line back later when following the | |
28a16a1b | 3550 | link with @kbd{C-c C-o}. |
4009494e GM |
3551 | |
3552 | Here is the syntax of the different ways to attach a search to a file | |
3553 | link, together with an explanation: | |
3554 | ||
3555 | @example | |
3556 | [[file:~/code/main.c::255]] | |
3557 | [[file:~/xx.org::My Target]] | |
3558 | [[file:~/xx.org::*My Target]] | |
ed21c5c8 | 3559 | [[file:~/xx.org::#my-custom-id]] |
4009494e GM |
3560 | [[file:~/xx.org::/regexp/]] |
3561 | @end example | |
3562 | ||
3563 | @table @code | |
3564 | @item 255 | |
3565 | Jump to line 255. | |
3566 | @item My Target | |
3567 | Search for a link target @samp{<<My Target>>}, or do a text search for | |
3568 | @samp{my target}, similar to the search in internal links, see | |
3569 | @ref{Internal links}. In HTML export (@pxref{HTML export}), such a file | |
3570 | link will become an HTML reference to the corresponding named anchor in | |
3571 | the linked file. | |
3572 | @item *My Target | |
a7808fba | 3573 | In an Org file, restrict search to headlines. |
ed21c5c8 CD |
3574 | @item #my-custom-id |
3575 | Link to a heading with a @code{CUSTOM_ID} property | |
4009494e GM |
3576 | @item /regexp/ |
3577 | Do a regular expression search for @code{regexp}. This uses the Emacs | |
3578 | command @code{occur} to list all matches in a separate window. If the | |
e66ba1df | 3579 | target file is in Org mode, @code{org-occur} is used to create a |
4009494e GM |
3580 | sparse tree with the matches. |
3581 | @c If the target file is a directory, | |
3582 | @c @code{grep} will be used to search all files in the directory. | |
3583 | @end table | |
3584 | ||
3585 | As a degenerate case, a file link with an empty file name can be used | |
3586 | to search the current file. For example, @code{[[file:::find me]]} does | |
3587 | a search for @samp{find me} in the current file, just as | |
3588 | @samp{[[find me]]} would. | |
3589 | ||
dbc28aaa | 3590 | @node Custom searches, , Search options, Hyperlinks |
4009494e GM |
3591 | @section Custom Searches |
3592 | @cindex custom search strings | |
3593 | @cindex search strings, custom | |
3594 | ||
3595 | The default mechanism for creating search strings and for doing the | |
3596 | actual search related to a file link may not work correctly in all | |
c8d0cf5c | 3597 | cases. For example, Bib@TeX{} database files have many entries like |
4009494e | 3598 | @samp{year="1993"} which would not result in good search strings, |
c8d0cf5c | 3599 | because the only unique identification for a Bib@TeX{} entry is the |
4009494e GM |
3600 | citation key. |
3601 | ||
c8d0cf5c CD |
3602 | @vindex org-create-file-search-functions |
3603 | @vindex org-execute-file-search-functions | |
4009494e GM |
3604 | If you come across such a problem, you can write custom functions to set |
3605 | the right search string for a particular file type, and to do the search | |
3606 | for the string in the file. Using @code{add-hook}, these functions need | |
3607 | to be added to the hook variables | |
3608 | @code{org-create-file-search-functions} and | |
3609 | @code{org-execute-file-search-functions}. See the docstring for these | |
a7808fba | 3610 | variables for more information. Org actually uses this mechanism |
4009494e | 3611 | for Bib@TeX{} database files, and you can use the corresponding code as |
44ce9197 | 3612 | an implementation example. See the file @file{org-bibtex.el}. |
4009494e | 3613 | |
a7808fba | 3614 | @node TODO Items, Tags, Hyperlinks, Top |
86fbb8ca | 3615 | @chapter TODO items |
4009494e GM |
3616 | @cindex TODO items |
3617 | ||
e66ba1df | 3618 | Org mode does not maintain TODO lists as separate documents@footnote{Of |
a50253cc | 3619 | course, you can make a document that contains only long lists of TODO items, |
44ce9197 CD |
3620 | but this is not required.}. Instead, TODO items are an integral part of the |
3621 | notes file, because TODO items usually come up while taking notes! With Org | |
3622 | mode, simply mark any entry in a tree as being a TODO item. In this way, | |
3623 | information is not duplicated, and the entire context from which the TODO | |
3624 | item emerged is always present. | |
4009494e | 3625 | |
dbc28aaa | 3626 | Of course, this technique for managing TODO items scatters them |
e66ba1df | 3627 | throughout your notes file. Org mode compensates for this by providing |
dbc28aaa | 3628 | methods to give you an overview of all the things that you have to do. |
4009494e GM |
3629 | |
3630 | @menu | |
c0468714 GM |
3631 | * TODO basics:: Marking and displaying TODO entries |
3632 | * TODO extensions:: Workflow and assignments | |
3633 | * Progress logging:: Dates and notes for progress | |
3634 | * Priorities:: Some things are more important than others | |
3635 | * Breaking down tasks:: Splitting a task into manageable pieces | |
3636 | * Checkboxes:: Tick-off lists | |
4009494e GM |
3637 | @end menu |
3638 | ||
a7808fba | 3639 | @node TODO basics, TODO extensions, TODO Items, TODO Items |
4009494e GM |
3640 | @section Basic TODO functionality |
3641 | ||
dbc28aaa CD |
3642 | Any headline becomes a TODO item when it starts with the word |
3643 | @samp{TODO}, for example: | |
4009494e GM |
3644 | |
3645 | @example | |
3646 | *** TODO Write letter to Sam Fortune | |
3647 | @end example | |
3648 | ||
3649 | @noindent | |
3650 | The most important commands to work with TODO entries are: | |
3651 | ||
3652 | @table @kbd | |
acedf35c | 3653 | @orgcmd{C-c C-t,org-todo} |
4009494e | 3654 | @cindex cycling, of TODO states |
4009494e GM |
3655 | Rotate the TODO state of the current item among |
3656 | ||
3657 | @example | |
3658 | ,-> (unmarked) -> TODO -> DONE --. | |
3659 | '--------------------------------' | |
3660 | @end example | |
3661 | ||
3662 | The same rotation can also be done ``remotely'' from the timeline and | |
3663 | agenda buffers with the @kbd{t} command key (@pxref{Agenda commands}). | |
dbc28aaa | 3664 | |
acedf35c | 3665 | @orgkey{C-u C-c C-t} |
dbc28aaa | 3666 | Select a specific keyword using completion or (if it has been set up) |
28a16a1b | 3667 | the fast selection interface. For the latter, you need to assign keys |
c8d0cf5c | 3668 | to TODO states, see @ref{Per-file keywords}, and @ref{Setting tags}, for |
28a16a1b | 3669 | more information. |
dbc28aaa | 3670 | |
4009494e GM |
3671 | @kindex S-@key{right} |
3672 | @kindex S-@key{left} | |
acedf35c | 3673 | @item S-@key{right} @ @r{/} @ S-@key{left} |
c8d0cf5c | 3674 | @vindex org-treat-S-cursor-todo-selection-as-state-change |
dbc28aaa CD |
3675 | Select the following/preceding TODO state, similar to cycling. Useful |
3676 | mostly if more than two TODO states are possible (@pxref{TODO | |
c8d0cf5c CD |
3677 | extensions}). See also @ref{Conflicts}, for a discussion of the interaction |
3678 | with @code{shift-selection-mode}. See also the variable | |
3679 | @code{org-treat-S-cursor-todo-selection-as-state-change}. | |
acedf35c | 3680 | @orgcmd{C-c / t,org-show-todo-key} |
4009494e | 3681 | @cindex sparse tree, for TODO |
c8d0cf5c CD |
3682 | @vindex org-todo-keywords |
3683 | View TODO items in a @emph{sparse tree} (@pxref{Sparse trees}). Folds the | |
86fbb8ca CD |
3684 | entire buffer, but shows all TODO items (with not-DONE state) and the |
3685 | headings hierarchy above them. With a prefix argument (or by using @kbd{C-c | |
3686 | / T}), search for a specific TODO. You will be prompted for the keyword, and | |
3687 | you can also give a list of keywords like @code{KWD1|KWD2|...} to list | |
ce57c2fe | 3688 | entries that match any one of these keywords. With a numeric prefix argument |
86fbb8ca CD |
3689 | N, show the tree for the Nth keyword in the variable |
3690 | @code{org-todo-keywords}. With two prefix arguments, find all TODO states, | |
3691 | both un-done and done. | |
acedf35c | 3692 | @orgcmd{C-c a t,org-todo-list} |
86fbb8ca CD |
3693 | Show the global TODO list. Collects the TODO items (with not-DONE states) |
3694 | from all agenda files (@pxref{Agenda Views}) into a single buffer. The new | |
3695 | buffer will be in @code{agenda-mode}, which provides commands to examine and | |
3696 | manipulate the TODO entries from the new buffer (@pxref{Agenda commands}). | |
3697 | @xref{Global TODO list}, for more information. | |
acedf35c | 3698 | @orgcmd{S-M-@key{RET},org-insert-todo-heading} |
4009494e GM |
3699 | Insert a new TODO entry below the current one. |
3700 | @end table | |
3701 | ||
71d35b24 | 3702 | @noindent |
c8d0cf5c | 3703 | @vindex org-todo-state-tags-triggers |
71d35b24 CD |
3704 | Changing a TODO state can also trigger tag changes. See the docstring of the |
3705 | option @code{org-todo-state-tags-triggers} for details. | |
3706 | ||
a7808fba | 3707 | @node TODO extensions, Progress logging, TODO basics, TODO Items |
4009494e GM |
3708 | @section Extended use of TODO keywords |
3709 | @cindex extended TODO keywords | |
3710 | ||
c8d0cf5c | 3711 | @vindex org-todo-keywords |
dbc28aaa | 3712 | By default, marked TODO entries have one of only two states: TODO and |
e66ba1df | 3713 | DONE. Org mode allows you to classify TODO items in more complex ways |
dbc28aaa CD |
3714 | with @emph{TODO keywords} (stored in @code{org-todo-keywords}). With |
3715 | special setup, the TODO keyword system can work differently in different | |
3716 | files. | |
4009494e GM |
3717 | |
3718 | Note that @i{tags} are another way to classify headlines in general and | |
3719 | TODO items in particular (@pxref{Tags}). | |
3720 | ||
3721 | @menu | |
c0468714 GM |
3722 | * Workflow states:: From TODO to DONE in steps |
3723 | * TODO types:: I do this, Fred does the rest | |
3724 | * Multiple sets in one file:: Mixing it all, and still finding your way | |
3725 | * Fast access to TODO states:: Single letter selection of a state | |
3726 | * Per-file keywords:: Different files, different requirements | |
3727 | * Faces for TODO keywords:: Highlighting states | |
3728 | * TODO dependencies:: When one task needs to wait for others | |
4009494e GM |
3729 | @end menu |
3730 | ||
3731 | @node Workflow states, TODO types, TODO extensions, TODO extensions | |
3732 | @subsection TODO keywords as workflow states | |
3733 | @cindex TODO workflow | |
3734 | @cindex workflow states as TODO keywords | |
3735 | ||
3736 | You can use TODO keywords to indicate different @emph{sequential} states | |
3737 | in the process of working on an item, for example@footnote{Changing | |
e66ba1df | 3738 | this variable only becomes effective after restarting Org mode in a |
4009494e GM |
3739 | buffer.}: |
3740 | ||
3741 | @lisp | |
3742 | (setq org-todo-keywords | |
3743 | '((sequence "TODO" "FEEDBACK" "VERIFY" "|" "DONE" "DELEGATED"))) | |
3744 | @end lisp | |
3745 | ||
3746 | The vertical bar separates the TODO keywords (states that @emph{need | |
44ce9197 | 3747 | action}) from the DONE states (which need @emph{no further action}). If |
4009494e GM |
3748 | you don't provide the separator bar, the last state is used as the DONE |
3749 | state. | |
3750 | @cindex completion, of TODO keywords | |
3751 | With this setup, the command @kbd{C-c C-t} will cycle an entry from TODO | |
3752 | to FEEDBACK, then to VERIFY, and finally to DONE and DELEGATED. You may | |
a7808fba | 3753 | also use a numeric prefix argument to quickly select a specific state. For |
4009494e | 3754 | example @kbd{C-3 C-c C-t} will change the state immediately to VERIFY. |
560bb6ea | 3755 | Or you can use @kbd{S-@key{left}} to go backward through the sequence. If you |
28a16a1b CD |
3756 | define many keywords, you can use in-buffer completion |
3757 | (@pxref{Completion}) or even a special one-key selection scheme | |
3758 | (@pxref{Fast access to TODO states}) to insert these words into the | |
a7808fba | 3759 | buffer. Changing a TODO state can be logged with a timestamp, see |
c8d0cf5c | 3760 | @ref{Tracking TODO state changes}, for more information. |
4009494e GM |
3761 | |
3762 | @node TODO types, Multiple sets in one file, Workflow states, TODO extensions | |
3763 | @subsection TODO keywords as types | |
3764 | @cindex TODO types | |
3765 | @cindex names as TODO keywords | |
3766 | @cindex types as TODO keywords | |
3767 | ||
3768 | The second possibility is to use TODO keywords to indicate different | |
3769 | @emph{types} of action items. For example, you might want to indicate | |
3770 | that items are for ``work'' or ``home''. Or, when you work with several | |
3771 | people on a single project, you might want to assign action items | |
3772 | directly to persons, by using their names as TODO keywords. This would | |
3773 | be set up like this: | |
3774 | ||
3775 | @lisp | |
3776 | (setq org-todo-keywords '((type "Fred" "Sara" "Lucy" "|" "DONE"))) | |
3777 | @end lisp | |
3778 | ||
3779 | In this case, different keywords do not indicate a sequence, but rather | |
3780 | different types. So the normal work flow would be to assign a task to a | |
e66ba1df | 3781 | person, and later to mark it DONE. Org mode supports this style by adapting |
a7808fba CD |
3782 | the workings of the command @kbd{C-c C-t}@footnote{This is also true for the |
3783 | @kbd{t} command in the timeline and agenda buffers.}. When used several | |
3784 | times in succession, it will still cycle through all names, in order to first | |
3785 | select the right type for a task. But when you return to the item after some | |
3786 | time and execute @kbd{C-c C-t} again, it will switch from any name directly | |
3787 | to DONE. Use prefix arguments or completion to quickly select a specific | |
3788 | name. You can also review the items of a specific TODO type in a sparse tree | |
86fbb8ca CD |
3789 | by using a numeric prefix to @kbd{C-c / t}. For example, to see all things |
3790 | Lucy has to do, you would use @kbd{C-3 C-c / t}. To collect Lucy's items | |
a7808fba | 3791 | from all agenda files into a single buffer, you would use the numeric prefix |
86fbb8ca | 3792 | argument as well when creating the global TODO list: @kbd{C-3 C-c a t}. |
4009494e | 3793 | |
dbc28aaa | 3794 | @node Multiple sets in one file, Fast access to TODO states, TODO types, TODO extensions |
4009494e | 3795 | @subsection Multiple keyword sets in one file |
a7808fba | 3796 | @cindex TODO keyword sets |
4009494e GM |
3797 | |
3798 | Sometimes you may want to use different sets of TODO keywords in | |
3799 | parallel. For example, you may want to have the basic | |
3800 | @code{TODO}/@code{DONE}, but also a workflow for bug fixing, and a | |
3801 | separate state indicating that an item has been canceled (so it is not | |
3802 | DONE, but also does not require action). Your setup would then look | |
3803 | like this: | |
3804 | ||
3805 | @lisp | |
3806 | (setq org-todo-keywords | |
3807 | '((sequence "TODO" "|" "DONE") | |
3808 | (sequence "REPORT" "BUG" "KNOWNCAUSE" "|" "FIXED") | |
3809 | (sequence "|" "CANCELED"))) | |
3810 | @end lisp | |
3811 | ||
e66ba1df | 3812 | The keywords should all be different, this helps Org mode to keep track |
4009494e GM |
3813 | of which subsequence should be used for a given entry. In this setup, |
3814 | @kbd{C-c C-t} only operates within a subsequence, so it switches from | |
3815 | @code{DONE} to (nothing) to @code{TODO}, and from @code{FIXED} to | |
3816 | (nothing) to @code{REPORT}. Therefore you need a mechanism to initially | |
3817 | select the correct sequence. Besides the obvious ways like typing a | |
3818 | keyword or using completion, you may also apply the following commands: | |
3819 | ||
3820 | @table @kbd | |
3821 | @kindex C-S-@key{right} | |
3822 | @kindex C-S-@key{left} | |
3da3282e CD |
3823 | @kindex C-u C-u C-c C-t |
3824 | @item C-u C-u C-c C-t | |
3825 | @itemx C-S-@key{right} | |
4009494e GM |
3826 | @itemx C-S-@key{left} |
3827 | These keys jump from one TODO subset to the next. In the above example, | |
3da3282e CD |
3828 | @kbd{C-u C-u C-c C-t} or @kbd{C-S-@key{right}} would jump from @code{TODO} or |
3829 | @code{DONE} to @code{REPORT}, and any of the words in the second row to | |
3830 | @code{CANCELED}. Note that the @kbd{C-S-} key binding conflict with | |
3831 | @code{shift-selection-mode} (@pxref{Conflicts}). | |
4009494e GM |
3832 | @kindex S-@key{right} |
3833 | @kindex S-@key{left} | |
3834 | @item S-@key{right} | |
3835 | @itemx S-@key{left} | |
3da3282e CD |
3836 | @kbd{S-@key{<left>}} and @kbd{S-@key{<right>}} and walk through @emph{all} |
3837 | keywords from all sets, so for example @kbd{S-@key{<right>}} would switch | |
3838 | from @code{DONE} to @code{REPORT} in the example above. See also | |
c8d0cf5c | 3839 | @ref{Conflicts}, for a discussion of the interaction with |
3da3282e | 3840 | @code{shift-selection-mode}. |
4009494e GM |
3841 | @end table |
3842 | ||
dbc28aaa CD |
3843 | @node Fast access to TODO states, Per-file keywords, Multiple sets in one file, TODO extensions |
3844 | @subsection Fast access to TODO states | |
3845 | ||
3846 | If you would like to quickly change an entry to an arbitrary TODO state | |
3847 | instead of cycling through the states, you can set up keys for | |
3848 | single-letter access to the states. This is done by adding the section | |
c8d0cf5c | 3849 | key after each keyword, in parentheses. For example: |
dbc28aaa CD |
3850 | |
3851 | @lisp | |
3852 | (setq org-todo-keywords | |
3853 | '((sequence "TODO(t)" "|" "DONE(d)") | |
3854 | (sequence "REPORT(r)" "BUG(b)" "KNOWNCAUSE(k)" "|" "FIXED(f)") | |
3855 | (sequence "|" "CANCELED(c)"))) | |
3856 | @end lisp | |
3857 | ||
c8d0cf5c | 3858 | @vindex org-fast-tag-selection-include-todo |
ce57c2fe BG |
3859 | If you then press @kbd{C-c C-t} followed by the selection key, the entry |
3860 | will be switched to this state. @kbd{SPC} can be used to remove any TODO | |
55033558 | 3861 | keyword from an entry.@footnote{Check also the variable |
c8d0cf5c | 3862 | @code{org-fast-tag-selection-include-todo}, it allows you to change the TODO |
55033558 CD |
3863 | state through the tags interface (@pxref{Setting tags}), in case you like to |
3864 | mingle the two concepts. Note that this means you need to come up with | |
3865 | unique keys across both sets of keywords.} | |
dbc28aaa CD |
3866 | |
3867 | @node Per-file keywords, Faces for TODO keywords, Fast access to TODO states, TODO extensions | |
4009494e GM |
3868 | @subsection Setting up keywords for individual files |
3869 | @cindex keyword options | |
dbc28aaa | 3870 | @cindex per-file keywords |
c8d0cf5c CD |
3871 | @cindex #+TODO |
3872 | @cindex #+TYP_TODO | |
3873 | @cindex #+SEQ_TODO | |
4009494e GM |
3874 | |
3875 | It can be very useful to use different aspects of the TODO mechanism in | |
3876 | different files. For file-local settings, you need to add special lines | |
3877 | to the file which set the keywords and interpretation for that file | |
3878 | only. For example, to set one of the two examples discussed above, you | |
3879 | need one of the following lines, starting in column zero anywhere in the | |
3880 | file: | |
3881 | ||
3882 | @example | |
c8d0cf5c | 3883 | #+TODO: TODO FEEDBACK VERIFY | DONE CANCELED |
4009494e | 3884 | @end example |
c8d0cf5c CD |
3885 | @noindent (you may also write @code{#+SEQ_TODO} to be explicit about the |
3886 | interpretation, but it means the same as @code{#+TODO}), or | |
4009494e GM |
3887 | @example |
3888 | #+TYP_TODO: Fred Sara Lucy Mike | DONE | |
3889 | @end example | |
3890 | ||
3891 | A setup for using several sets in parallel would be: | |
3892 | ||
3893 | @example | |
c8d0cf5c CD |
3894 | #+TODO: TODO | DONE |
3895 | #+TODO: REPORT BUG KNOWNCAUSE | FIXED | |
3896 | #+TODO: | CANCELED | |
4009494e GM |
3897 | @end example |
3898 | ||
3899 | @cindex completion, of option keywords | |
3900 | @kindex M-@key{TAB} | |
3901 | @noindent To make sure you are using the correct keyword, type | |
3902 | @samp{#+} into the buffer and then use @kbd{M-@key{TAB}} completion. | |
3903 | ||
3904 | @cindex DONE, final TODO keyword | |
3905 | Remember that the keywords after the vertical bar (or the last keyword | |
3906 | if no bar is there) must always mean that the item is DONE (although you | |
3907 | may use a different word). After changing one of these lines, use | |
3908 | @kbd{C-c C-c} with the cursor still in the line to make the changes | |
e66ba1df BG |
3909 | known to Org mode@footnote{Org mode parses these lines only when |
3910 | Org mode is activated after visiting a file. @kbd{C-c C-c} with the | |
3911 | cursor in a line starting with @samp{#+} is simply restarting Org mode | |
4009494e GM |
3912 | for the current buffer.}. |
3913 | ||
7ddb1b5f | 3914 | @node Faces for TODO keywords, TODO dependencies, Per-file keywords, TODO extensions |
dbc28aaa CD |
3915 | @subsection Faces for TODO keywords |
3916 | @cindex faces, for TODO keywords | |
3917 | ||
c8d0cf5c CD |
3918 | @vindex org-todo @r{(face)} |
3919 | @vindex org-done @r{(face)} | |
3920 | @vindex org-todo-keyword-faces | |
e66ba1df | 3921 | Org mode highlights TODO keywords with special faces: @code{org-todo} |
dbc28aaa CD |
3922 | for keywords indicating that an item still has to be acted upon, and |
3923 | @code{org-done} for keywords indicating that an item is finished. If | |
3924 | you are using more than 2 different states, you might want to use | |
3925 | special faces for some of them. This can be done using the variable | |
3926 | @code{org-todo-keyword-faces}. For example: | |
3927 | ||
3928 | @lisp | |
96c8522a | 3929 | @group |
dbc28aaa | 3930 | (setq org-todo-keyword-faces |
ed21c5c8 CD |
3931 | '(("TODO" . org-warning) ("STARTED" . "yellow") |
3932 | ("CANCELED" . (:foreground "blue" :weight bold)))) | |
96c8522a | 3933 | @end group |
dbc28aaa CD |
3934 | @end lisp |
3935 | ||
ed21c5c8 | 3936 | While using a list with face properties as shown for CANCELED @emph{should} |
27e428e7 | 3937 | work, this does not always seem to be the case. If necessary, define a |
ed21c5c8 CD |
3938 | special face and use that. A string is interpreted as a color. The variable |
3939 | @code{org-faces-easy-properties} determines if that color is interpreted as a | |
3940 | foreground or a background color. | |
28a16a1b | 3941 | |
7ddb1b5f CD |
3942 | @node TODO dependencies, , Faces for TODO keywords, TODO extensions |
3943 | @subsection TODO dependencies | |
2e461fc1 CD |
3944 | @cindex TODO dependencies |
3945 | @cindex dependencies, of TODO states | |
7ddb1b5f | 3946 | |
c8d0cf5c CD |
3947 | @vindex org-enforce-todo-dependencies |
3948 | @cindex property, ORDERED | |
7ddb1b5f CD |
3949 | The structure of Org files (hierarchy and lists) makes it easy to define TODO |
3950 | dependencies. Usually, a parent TODO task should not be marked DONE until | |
3951 | all subtasks (defined as children tasks) are marked as DONE. And sometimes | |
3952 | there is a logical sequence to a number of (sub)tasks, so that one task | |
3953 | cannot be acted upon before all siblings above it are done. If you customize | |
3954 | the variable @code{org-enforce-todo-dependencies}, Org will block entries | |
2e461fc1 CD |
3955 | from changing state to DONE while they have children that are not DONE. |
3956 | Furthermore, if an entry has a property @code{ORDERED}, each of its children | |
3957 | will be blocked until all earlier siblings are marked DONE. Here is an | |
3958 | example: | |
7ddb1b5f CD |
3959 | |
3960 | @example | |
3961 | * TODO Blocked until (two) is done | |
3962 | ** DONE one | |
3963 | ** TODO two | |
3964 | ||
3965 | * Parent | |
3966 | :PROPERTIES: | |
ce57c2fe | 3967 | :ORDERED: t |
7ddb1b5f CD |
3968 | :END: |
3969 | ** TODO a | |
3970 | ** TODO b, needs to wait for (a) | |
3971 | ** TODO c, needs to wait for (a) and (b) | |
3972 | @end example | |
3973 | ||
bc283609 | 3974 | @table @kbd |
acedf35c | 3975 | @orgcmd{C-c C-x o,org-toggle-ordered-property} |
c8d0cf5c CD |
3976 | @vindex org-track-ordered-property-with-tag |
3977 | @cindex property, ORDERED | |
3978 | Toggle the @code{ORDERED} property of the current entry. A property is used | |
3979 | for this behavior because this should be local to the current entry, not | |
3980 | inherited like a tag. However, if you would like to @i{track} the value of | |
3981 | this property with a tag for better visibility, customize the variable | |
3982 | @code{org-track-ordered-property-with-tag}. | |
acedf35c | 3983 | @orgkey{C-u C-u C-u C-c C-t} |
c8d0cf5c | 3984 | Change TODO state, circumventing any state blocking. |
bc283609 CD |
3985 | @end table |
3986 | ||
c8d0cf5c | 3987 | @vindex org-agenda-dim-blocked-tasks |
7ddb1b5f CD |
3988 | If you set the variable @code{org-agenda-dim-blocked-tasks}, TODO entries |
3989 | that cannot be closed because of such dependencies will be shown in a dimmed | |
3990 | font or even made invisible in agenda views (@pxref{Agenda Views}). | |
3991 | ||
2e461fc1 | 3992 | @cindex checkboxes and TODO dependencies |
c8d0cf5c | 3993 | @vindex org-enforce-todo-dependencies |
2e461fc1 CD |
3994 | You can also block changes of TODO states by looking at checkboxes |
3995 | (@pxref{Checkboxes}). If you set the variable | |
3996 | @code{org-enforce-todo-checkbox-dependencies}, an entry that has unchecked | |
3997 | checkboxes will be blocked from switching to DONE. | |
3998 | ||
7ddb1b5f CD |
3999 | If you need more complex dependency structures, for example dependencies |
4000 | between entries in different trees or files, check out the contributed | |
4001 | module @file{org-depend.el}. | |
4002 | ||
dbc28aaa | 4003 | @page |
a7808fba CD |
4004 | @node Progress logging, Priorities, TODO extensions, TODO Items |
4005 | @section Progress logging | |
dbc28aaa CD |
4006 | @cindex progress logging |
4007 | @cindex logging, of progress | |
4008 | ||
e66ba1df | 4009 | Org mode can automatically record a timestamp and possibly a note when |
28a16a1b CD |
4010 | you mark a TODO item as DONE, or even each time you change the state of |
4011 | a TODO item. This system is highly configurable, settings can be on a | |
4012 | per-keyword basis and can be localized to a file or even a subtree. For | |
4013 | information on how to clock working time for a task, see @ref{Clocking | |
4014 | work time}. | |
dbc28aaa CD |
4015 | |
4016 | @menu | |
c0468714 GM |
4017 | * Closing items:: When was this entry marked DONE? |
4018 | * Tracking TODO state changes:: When did the status change? | |
4019 | * Tracking your habits:: How consistent have you been? | |
dbc28aaa CD |
4020 | @end menu |
4021 | ||
4022 | @node Closing items, Tracking TODO state changes, Progress logging, Progress logging | |
4023 | @subsection Closing items | |
4024 | ||
28a16a1b CD |
4025 | The most basic logging is to keep track of @emph{when} a certain TODO |
4026 | item was finished. This is achieved with@footnote{The corresponding | |
acedf35c | 4027 | in-buffer setting is: @code{#+STARTUP: logdone}} |
dbc28aaa CD |
4028 | |
4029 | @lisp | |
28a16a1b | 4030 | (setq org-log-done 'time) |
dbc28aaa CD |
4031 | @end lisp |
4032 | ||
4033 | @noindent | |
28a16a1b CD |
4034 | Then each time you turn an entry from a TODO (not-done) state into any |
4035 | of the DONE states, a line @samp{CLOSED: [timestamp]} will be inserted | |
4036 | just after the headline. If you turn the entry back into a TODO item | |
4037 | through further state cycling, that line will be removed again. If you | |
4038 | want to record a note along with the timestamp, use@footnote{The | |
4039 | corresponding in-buffer setting is: @code{#+STARTUP: lognotedone}} | |
dbc28aaa CD |
4040 | |
4041 | @lisp | |
28a16a1b | 4042 | (setq org-log-done 'note) |
dbc28aaa CD |
4043 | @end lisp |
4044 | ||
28a16a1b CD |
4045 | @noindent |
4046 | You will then be prompted for a note, and that note will be stored below | |
4047 | the entry with a @samp{Closing Note} heading. | |
4048 | ||
4049 | In the timeline (@pxref{Timeline}) and in the agenda | |
a7808fba | 4050 | (@pxref{Weekly/daily agenda}), you can then use the @kbd{l} key to |
28a16a1b CD |
4051 | display the TODO items with a @samp{CLOSED} timestamp on each day, |
4052 | giving you an overview of what has been done. | |
4053 | ||
a351880d | 4054 | @node Tracking TODO state changes, Tracking your habits, Closing items, Progress logging |
dbc28aaa | 4055 | @subsection Tracking TODO state changes |
c8d0cf5c CD |
4056 | @cindex drawer, for state change recording |
4057 | ||
4058 | @vindex org-log-states-order-reversed | |
4059 | @vindex org-log-into-drawer | |
4060 | @cindex property, LOG_INTO_DRAWER | |
4061 | When TODO keywords are used as workflow states (@pxref{Workflow states}), you | |
4062 | might want to keep track of when a state change occurred and maybe take a | |
4063 | note about this change. You can either record just a timestamp, or a | |
4064 | time-stamped note for a change. These records will be inserted after the | |
4065 | headline as an itemized list, newest first@footnote{See the variable | |
4066 | @code{org-log-states-order-reversed}}. When taking a lot of notes, you might | |
4067 | want to get the notes out of the way into a drawer (@pxref{Drawers}). | |
4068 | Customize the variable @code{org-log-into-drawer} to get this | |
4069 | behavior---the recommended drawer for this is called @code{LOGBOOK}. You can | |
4070 | also overrule the setting of this variable for a subtree by setting a | |
4071 | @code{LOG_INTO_DRAWER} property. | |
4072 | ||
e66ba1df | 4073 | Since it is normally too much to record a note for every state, Org mode |
c8d0cf5c | 4074 | expects configuration on a per-keyword basis for this. This is achieved by |
e66ba1df BG |
4075 | adding special markers @samp{!} (for a timestamp) or @samp{@@} (for a note |
4076 | with timestamp) in parentheses after each keyword. For example, with the | |
4077 | setting | |
dbc28aaa CD |
4078 | |
4079 | @lisp | |
28a16a1b CD |
4080 | (setq org-todo-keywords |
4081 | '((sequence "TODO(t)" "WAIT(w@@/!)" "|" "DONE(d!)" "CANCELED(c@@)"))) | |
dbc28aaa CD |
4082 | @end lisp |
4083 | ||
e66ba1df BG |
4084 | To record a timestamp without a note for TODO keywords configured with |
4085 | @samp{@@}, just type @kbd{C-c C-c} to enter a blank note when prompted. | |
4086 | ||
dbc28aaa | 4087 | @noindent |
c8d0cf5c | 4088 | @vindex org-log-done |
28a16a1b | 4089 | you not only define global TODO keywords and fast access keys, but also |
c8d0cf5c | 4090 | request that a time is recorded when the entry is set to |
e66ba1df | 4091 | DONE@footnote{It is possible that Org mode will record two timestamps |
28a16a1b | 4092 | when you are using both @code{org-log-done} and state change logging. |
c8d0cf5c | 4093 | However, it will never prompt for two notes---if you have configured |
28a16a1b CD |
4094 | both, the state change recording note will take precedence and cancel |
4095 | the @samp{Closing Note}.}, and that a note is recorded when switching to | |
c8d0cf5c | 4096 | WAIT or CANCELED. The setting for WAIT is even more special: the |
28a16a1b | 4097 | @samp{!} after the slash means that in addition to the note taken when |
c8d0cf5c | 4098 | entering the state, a timestamp should be recorded when @i{leaving} the |
28a16a1b CD |
4099 | WAIT state, if and only if the @i{target} state does not configure |
4100 | logging for entering it. So it has no effect when switching from WAIT | |
4101 | to DONE, because DONE is configured to record a timestamp only. But | |
4102 | when switching from WAIT back to TODO, the @samp{/!} in the WAIT | |
4103 | setting now triggers a timestamp even though TODO has no logging | |
4104 | configured. | |
4105 | ||
4106 | You can use the exact same syntax for setting logging preferences local | |
4107 | to a buffer: | |
4108 | @example | |
c8d0cf5c | 4109 | #+TODO: TODO(t) WAIT(w@@/!) | DONE(d!) CANCELED(c@@) |
28a16a1b CD |
4110 | @end example |
4111 | ||
c8d0cf5c | 4112 | @cindex property, LOGGING |
28a16a1b CD |
4113 | In order to define logging settings that are local to a subtree or a |
4114 | single item, define a LOGGING property in this entry. Any non-empty | |
4115 | LOGGING property resets all logging settings to nil. You may then turn | |
4116 | on logging for this specific tree using STARTUP keywords like | |
4117 | @code{lognotedone} or @code{logrepeat}, as well as adding state specific | |
4118 | settings like @code{TODO(!)}. For example | |
4119 | ||
4120 | @example | |
4121 | * TODO Log each state with only a time | |
4122 | :PROPERTIES: | |
4123 | :LOGGING: TODO(!) WAIT(!) DONE(!) CANCELED(!) | |
4124 | :END: | |
4125 | * TODO Only log when switching to WAIT, and when repeating | |
4126 | :PROPERTIES: | |
4127 | :LOGGING: WAIT(@@) logrepeat | |
4128 | :END: | |
4129 | * TODO No logging at all | |
4130 | :PROPERTIES: | |
4131 | :LOGGING: nil | |
4132 | :END: | |
dbc28aaa CD |
4133 | @end example |
4134 | ||
a351880d CD |
4135 | @node Tracking your habits, , Tracking TODO state changes, Progress logging |
4136 | @subsection Tracking your habits | |
4137 | @cindex habits | |
4138 | ||
4139 | Org has the ability to track the consistency of a special category of TODOs, | |
4140 | called ``habits''. A habit has the following properties: | |
4141 | ||
4142 | @enumerate | |
4143 | @item | |
4144 | You have enabled the @code{habits} module by customizing the variable | |
4145 | @code{org-modules}. | |
4146 | @item | |
ce57c2fe | 4147 | The habit is a TODO item, with a TODO keyword representing an open state. |
a351880d CD |
4148 | @item |
4149 | The property @code{STYLE} is set to the value @code{habit}. | |
4150 | @item | |
afe98dfa CD |
4151 | The TODO has a scheduled date, usually with a @code{.+} style repeat |
4152 | interval. A @code{++} style may be appropriate for habits with time | |
4153 | constraints, e.g., must be done on weekends, or a @code{+} style for an | |
4154 | unusual habit that can have a backlog, e.g., weekly reports. | |
a351880d CD |
4155 | @item |
4156 | The TODO may also have minimum and maximum ranges specified by using the | |
4157 | syntax @samp{.+2d/3d}, which says that you want to do the task at least every | |
4158 | three days, but at most every two days. | |
4159 | @item | |
4160 | You must also have state logging for the @code{DONE} state enabled, in order | |
ce57c2fe BG |
4161 | for historical data to be represented in the consistency graph. If it is not |
4162 | enabled it is not an error, but the consistency graphs will be largely | |
a351880d CD |
4163 | meaningless. |
4164 | @end enumerate | |
4165 | ||
4166 | To give you an idea of what the above rules look like in action, here's an | |
4167 | actual habit with some history: | |
4168 | ||
4169 | @example | |
4170 | ** TODO Shave | |
4171 | SCHEDULED: <2009-10-17 Sat .+2d/4d> | |
4172 | - State "DONE" from "TODO" [2009-10-15 Thu] | |
4173 | - State "DONE" from "TODO" [2009-10-12 Mon] | |
4174 | - State "DONE" from "TODO" [2009-10-10 Sat] | |
4175 | - State "DONE" from "TODO" [2009-10-04 Sun] | |
4176 | - State "DONE" from "TODO" [2009-10-02 Fri] | |
4177 | - State "DONE" from "TODO" [2009-09-29 Tue] | |
4178 | - State "DONE" from "TODO" [2009-09-25 Fri] | |
4179 | - State "DONE" from "TODO" [2009-09-19 Sat] | |
4180 | - State "DONE" from "TODO" [2009-09-16 Wed] | |
4181 | - State "DONE" from "TODO" [2009-09-12 Sat] | |
4182 | :PROPERTIES: | |
4183 | :STYLE: habit | |
4184 | :LAST_REPEAT: [2009-10-19 Mon 00:36] | |
4185 | :END: | |
4186 | @end example | |
4187 | ||
4188 | What this habit says is: I want to shave at most every 2 days (given by the | |
4189 | @code{SCHEDULED} date and repeat interval) and at least every 4 days. If | |
4190 | today is the 15th, then the habit first appears in the agenda on Oct 17, | |
4191 | after the minimum of 2 days has elapsed, and will appear overdue on Oct 19, | |
4192 | after four days have elapsed. | |
4193 | ||
4194 | What's really useful about habits is that they are displayed along with a | |
4195 | consistency graph, to show how consistent you've been at getting that task | |
4196 | done in the past. This graph shows every day that the task was done over the | |
4197 | past three weeks, with colors for each day. The colors used are: | |
4198 | ||
4199 | @table @code | |
4200 | @item Blue | |
4201 | If the task wasn't to be done yet on that day. | |
4202 | @item Green | |
4203 | If the task could have been done on that day. | |
4204 | @item Yellow | |
4205 | If the task was going to be overdue the next day. | |
4206 | @item Red | |
4207 | If the task was overdue on that day. | |
4208 | @end table | |
4209 | ||
86fbb8ca | 4210 | In addition to coloring each day, the day is also marked with an asterisk if |
a351880d CD |
4211 | the task was actually done that day, and an exclamation mark to show where |
4212 | the current day falls in the graph. | |
4213 | ||
4214 | There are several configuration variables that can be used to change the way | |
4215 | habits are displayed in the agenda. | |
4216 | ||
4217 | @table @code | |
4218 | @item org-habit-graph-column | |
4219 | The buffer column at which the consistency graph should be drawn. This will | |
ce57c2fe | 4220 | overwrite any text in that column, so it is a good idea to keep your habits' |
a351880d CD |
4221 | titles brief and to the point. |
4222 | @item org-habit-preceding-days | |
4223 | The amount of history, in days before today, to appear in consistency graphs. | |
4224 | @item org-habit-following-days | |
4225 | The number of days after today that will appear in consistency graphs. | |
4226 | @item org-habit-show-habits-only-for-today | |
4227 | If non-nil, only show habits in today's agenda view. This is set to true by | |
4228 | default. | |
4229 | @end table | |
4230 | ||
4231 | Lastly, pressing @kbd{K} in the agenda buffer will cause habits to | |
4232 | temporarily be disabled and they won't appear at all. Press @kbd{K} again to | |
4233 | bring them back. They are also subject to tag filtering, if you have habits | |
4234 | which should only be done in certain contexts, for example. | |
4235 | ||
a7808fba | 4236 | @node Priorities, Breaking down tasks, Progress logging, TODO Items |
4009494e GM |
4237 | @section Priorities |
4238 | @cindex priorities | |
4239 | ||
e66ba1df | 4240 | If you use Org mode extensively, you may end up with enough TODO items that |
dbc28aaa | 4241 | it starts to make sense to prioritize them. Prioritizing can be done by |
86fbb8ca | 4242 | placing a @emph{priority cookie} into the headline of a TODO item, like this |
4009494e GM |
4243 | |
4244 | @example | |
4245 | *** TODO [#A] Write letter to Sam Fortune | |
4246 | @end example | |
4247 | ||
4248 | @noindent | |
ed21c5c8 | 4249 | @vindex org-priority-faces |
e66ba1df | 4250 | By default, Org mode supports three priorities: @samp{A}, @samp{B}, and |
ed21c5c8 | 4251 | @samp{C}. @samp{A} is the highest priority. An entry without a cookie is |
afe98dfa CD |
4252 | treated just like priority @samp{B}. Priorities make a difference only for |
4253 | sorting in the agenda (@pxref{Weekly/daily agenda}); outside the agenda, they | |
e66ba1df | 4254 | have no inherent meaning to Org mode. The cookies can be highlighted with |
afe98dfa | 4255 | special faces by customizing the variable @code{org-priority-faces}. |
dbc28aaa | 4256 | |
afe98dfa CD |
4257 | Priorities can be attached to any outline node; they do not need to be TODO |
4258 | items. | |
4009494e GM |
4259 | |
4260 | @table @kbd | |
4009494e | 4261 | @item @kbd{C-c ,} |
acedf35c CD |
4262 | @kindex @kbd{C-c ,} |
4263 | @findex org-priority | |
4264 | Set the priority of the current headline (@command{org-priority}). The | |
4265 | command prompts for a priority character @samp{A}, @samp{B} or @samp{C}. | |
4266 | When you press @key{SPC} instead, the priority cookie is removed from the | |
4267 | headline. The priorities can also be changed ``remotely'' from the timeline | |
4268 | and agenda buffer with the @kbd{,} command (@pxref{Agenda commands}). | |
4009494e | 4269 | @c |
acedf35c | 4270 | @orgcmdkkcc{S-@key{up},S-@key{down},org-priority-up,org-priority-down} |
c8d0cf5c | 4271 | @vindex org-priority-start-cycle-with-default |
3da3282e | 4272 | Increase/decrease priority of current headline@footnote{See also the option |
c8d0cf5c CD |
4273 | @code{org-priority-start-cycle-with-default}.}. Note that these keys are |
4274 | also used to modify timestamps (@pxref{Creating timestamps}). See also | |
4275 | @ref{Conflicts}, for a discussion of the interaction with | |
3da3282e | 4276 | @code{shift-selection-mode}. |
4009494e GM |
4277 | @end table |
4278 | ||
c8d0cf5c CD |
4279 | @vindex org-highest-priority |
4280 | @vindex org-lowest-priority | |
4281 | @vindex org-default-priority | |
4009494e GM |
4282 | You can change the range of allowed priorities by setting the variables |
4283 | @code{org-highest-priority}, @code{org-lowest-priority}, and | |
4284 | @code{org-default-priority}. For an individual buffer, you may set | |
4285 | these values (highest, lowest, default) like this (please make sure that | |
4286 | the highest priority is earlier in the alphabet than the lowest | |
4287 | priority): | |
4288 | ||
c8d0cf5c | 4289 | @cindex #+PRIORITIES |
4009494e GM |
4290 | @example |
4291 | #+PRIORITIES: A C B | |
4292 | @end example | |
4293 | ||
a7808fba | 4294 | @node Breaking down tasks, Checkboxes, Priorities, TODO Items |
4009494e GM |
4295 | @section Breaking tasks down into subtasks |
4296 | @cindex tasks, breaking down | |
6eb02347 | 4297 | @cindex statistics, for TODO items |
4009494e | 4298 | |
c8d0cf5c | 4299 | @vindex org-agenda-todo-list-sublevels |
4009494e | 4300 | It is often advisable to break down large tasks into smaller, manageable |
b349f79f CD |
4301 | subtasks. You can do this by creating an outline tree below a TODO item, |
4302 | with detailed subtasks on the tree@footnote{To keep subtasks out of the | |
4303 | global TODO list, see the @code{org-agenda-todo-list-sublevels}.}. To keep | |
4304 | the overview over the fraction of subtasks that are already completed, insert | |
4305 | either @samp{[/]} or @samp{[%]} anywhere in the headline. These cookies will | |
86fbb8ca | 4306 | be updated each time the TODO status of a child changes, or when pressing |
6eb02347 | 4307 | @kbd{C-c C-c} on the cookie. For example: |
b349f79f CD |
4308 | |
4309 | @example | |
4310 | * Organize Party [33%] | |
4311 | ** TODO Call people [1/2] | |
4312 | *** TODO Peter | |
4313 | *** DONE Sarah | |
4314 | ** TODO Buy food | |
4315 | ** DONE Talk to neighbor | |
4316 | @end example | |
4317 | ||
c8d0cf5c CD |
4318 | @cindex property, COOKIE_DATA |
4319 | If a heading has both checkboxes and TODO children below it, the meaning of | |
4320 | the statistics cookie become ambiguous. Set the property | |
4321 | @code{COOKIE_DATA} to either @samp{checkbox} or @samp{todo} to resolve | |
4322 | this issue. | |
4323 | ||
6eb02347 CD |
4324 | @vindex org-hierarchical-todo-statistics |
4325 | If you would like to have the statistics cookie count any TODO entries in the | |
a351880d | 4326 | subtree (not just direct children), configure the variable |
6eb02347 CD |
4327 | @code{org-hierarchical-todo-statistics}. To do this for a single subtree, |
4328 | include the word @samp{recursive} into the value of the @code{COOKIE_DATA} | |
4329 | property. | |
4330 | ||
4331 | @example | |
4332 | * Parent capturing statistics [2/20] | |
4333 | :PROPERTIES: | |
4334 | :COOKIE_DATA: todo recursive | |
4335 | :END: | |
4336 | @end example | |
4337 | ||
c8d0cf5c CD |
4338 | If you would like a TODO entry to automatically change to DONE |
4339 | when all children are done, you can use the following setup: | |
b349f79f CD |
4340 | |
4341 | @example | |
4342 | (defun org-summary-todo (n-done n-not-done) | |
4343 | "Switch entry to DONE when all subentries are done, to TODO otherwise." | |
4344 | (let (org-log-done org-log-states) ; turn off logging | |
4345 | (org-todo (if (= n-not-done 0) "DONE" "TODO")))) | |
4346 | ||
4347 | (add-hook 'org-after-todo-statistics-hook 'org-summary-todo) | |
4348 | @end example | |
4349 | ||
4350 | ||
4351 | Another possibility is the use of checkboxes to identify (a hierarchy of) a | |
4352 | large number of subtasks (@pxref{Checkboxes}). | |
4009494e GM |
4353 | |
4354 | ||
a7808fba | 4355 | @node Checkboxes, , Breaking down tasks, TODO Items |
4009494e GM |
4356 | @section Checkboxes |
4357 | @cindex checkboxes | |
4358 | ||
afe98dfa CD |
4359 | @vindex org-list-automatic-rules |
4360 | Every item in a plain list@footnote{With the exception of description | |
ce57c2fe | 4361 | lists. But you can allow it by modifying @code{org-list-automatic-rules} |
afe98dfa CD |
4362 | accordingly.} (@pxref{Plain lists}) can be made into a checkbox by starting |
4363 | it with the string @samp{[ ]}. This feature is similar to TODO items | |
4364 | (@pxref{TODO Items}), but is more lightweight. Checkboxes are not included | |
4365 | into the global TODO list, so they are often great to split a task into a | |
4366 | number of simple steps. Or you can use them in a shopping list. To toggle a | |
4367 | checkbox, use @kbd{C-c C-c}, or use the mouse (thanks to Piotr Zielinski's | |
4368 | @file{org-mouse.el}). | |
dbc28aaa CD |
4369 | |
4370 | Here is an example of a checkbox list. | |
4009494e GM |
4371 | |
4372 | @example | |
28a16a1b CD |
4373 | * TODO Organize party [2/4] |
4374 | - [-] call people [1/3] | |
4009494e GM |
4375 | - [ ] Peter |
4376 | - [X] Sarah | |
4377 | - [ ] Sam | |
4378 | - [X] order food | |
4379 | - [ ] think about what music to play | |
4380 | - [X] talk to the neighbors | |
4381 | @end example | |
4382 | ||
28a16a1b CD |
4383 | Checkboxes work hierarchically, so if a checkbox item has children that |
4384 | are checkboxes, toggling one of the children checkboxes will make the | |
4385 | parent checkbox reflect if none, some, or all of the children are | |
4386 | checked. | |
4387 | ||
4009494e GM |
4388 | @cindex statistics, for checkboxes |
4389 | @cindex checkbox statistics | |
c8d0cf5c | 4390 | @cindex property, COOKIE_DATA |
6eb02347 | 4391 | @vindex org-hierarchical-checkbox-statistics |
c8d0cf5c CD |
4392 | The @samp{[2/4]} and @samp{[1/3]} in the first and second line are cookies |
4393 | indicating how many checkboxes present in this entry have been checked off, | |
4394 | and the total number of checkboxes present. This can give you an idea on how | |
4395 | many checkboxes remain, even without opening a folded entry. The cookies can | |
4396 | be placed into a headline or into (the first line of) a plain list item. | |
4397 | Each cookie covers checkboxes of direct children structurally below the | |
4398 | headline/item on which the cookie appears@footnote{Set the variable | |
6eb02347 | 4399 | @code{org-hierarchical-checkbox-statistics} if you want such cookies to |
ce57c2fe | 4400 | count all checkboxes below the cookie, not just those belonging to direct |
c8d0cf5c CD |
4401 | children.}. You have to insert the cookie yourself by typing either |
4402 | @samp{[/]} or @samp{[%]}. With @samp{[/]} you get an @samp{n out of m} | |
4403 | result, as in the examples above. With @samp{[%]} you get information about | |
4404 | the percentage of checkboxes checked (in the above example, this would be | |
4405 | @samp{[50%]} and @samp{[33%]}, respectively). In a headline, a cookie can | |
4406 | count either checkboxes below the heading or TODO states of children, and it | |
4407 | will display whatever was changed last. Set the property @code{COOKIE_DATA} | |
4408 | to either @samp{checkbox} or @samp{todo} to resolve this issue. | |
4409 | ||
4410 | @cindex blocking, of checkboxes | |
4411 | @cindex checkbox blocking | |
4412 | @cindex property, ORDERED | |
4413 | If the current outline node has an @code{ORDERED} property, checkboxes must | |
4414 | be checked off in sequence, and an error will be thrown if you try to check | |
4415 | off a box while there are unchecked boxes above it. | |
4009494e GM |
4416 | |
4417 | @noindent The following commands work with checkboxes: | |
4418 | ||
4419 | @table @kbd | |
acedf35c | 4420 | @orgcmd{C-c C-c,org-toggle-checkbox} |
27e428e7 | 4421 | Toggle checkbox status or (with prefix arg) checkbox presence at point. |
e66ba1df BG |
4422 | With a single prefix argument, add an empty checkbox or remove the current |
4423 | one@footnote{`C-u C-c C-c' on the @emph{first} item of a list with no checkbox | |
4424 | will add checkboxes to the rest of the list.}. With a double prefix argument, set it to @samp{[-]}, which is | |
4425 | considered to be an intermediate state. | |
acedf35c | 4426 | @orgcmd{C-c C-x C-b,org-toggle-checkbox} |
c8d0cf5c CD |
4427 | Toggle checkbox status or (with prefix arg) checkbox presence at point. With |
4428 | double prefix argument, set it to @samp{[-]}, which is considered to be an | |
4429 | intermediate state. | |
4009494e GM |
4430 | @itemize @minus |
4431 | @item | |
4432 | If there is an active region, toggle the first checkbox in the region | |
7ddb1b5f CD |
4433 | and set all remaining boxes to the same status as the first. With a prefix |
4434 | arg, add or remove the checkbox for all items in the region. | |
4009494e GM |
4435 | @item |
4436 | If the cursor is in a headline, toggle checkboxes in the region between | |
4437 | this headline and the next (so @emph{not} the entire subtree). | |
4438 | @item | |
4439 | If there is no active region, just toggle the checkbox at point. | |
4440 | @end itemize | |
acedf35c | 4441 | @orgcmd{M-S-@key{RET},org-insert-todo-heading} |
ce57c2fe BG |
4442 | Insert a new item with a checkbox. This works only if the cursor is already |
4443 | in a plain list item (@pxref{Plain lists}). | |
acedf35c | 4444 | @orgcmd{C-c C-x o,org-toggle-ordered-property} |
c8d0cf5c CD |
4445 | @vindex org-track-ordered-property-with-tag |
4446 | @cindex property, ORDERED | |
4447 | Toggle the @code{ORDERED} property of the entry, to toggle if checkboxes must | |
4448 | be checked off in sequence. A property is used for this behavior because | |
4449 | this should be local to the current entry, not inherited like a tag. | |
4450 | However, if you would like to @i{track} the value of this property with a tag | |
4451 | for better visibility, customize the variable | |
4452 | @code{org-track-ordered-property-with-tag}. | |
acedf35c | 4453 | @orgcmd{C-c #,org-update-statistics-cookies} |
6eb02347 CD |
4454 | Update the statistics cookie in the current outline entry. When called with |
4455 | a @kbd{C-u} prefix, update the entire file. Checkbox statistic cookies are | |
4456 | updated automatically if you toggle checkboxes with @kbd{C-c C-c} and make | |
4457 | new ones with @kbd{M-S-@key{RET}}. TODO statistics cookies update when | |
4458 | changing TODO states. If you delete boxes/entries or add/change them by | |
ce57c2fe | 4459 | hand, use this command to get things back into sync. |
4009494e GM |
4460 | @end table |
4461 | ||
a7808fba | 4462 | @node Tags, Properties and Columns, TODO Items, Top |
4009494e GM |
4463 | @chapter Tags |
4464 | @cindex tags | |
4465 | @cindex headline tagging | |
4466 | @cindex matching, tags | |
4467 | @cindex sparse tree, tag based | |
4468 | ||
dbc28aaa | 4469 | An excellent way to implement labels and contexts for cross-correlating |
e66ba1df | 4470 | information is to assign @i{tags} to headlines. Org mode has extensive |
dbc28aaa | 4471 | support for tags. |
4009494e | 4472 | |
c8d0cf5c | 4473 | @vindex org-tag-faces |
dbc28aaa | 4474 | Every headline can contain a list of tags; they occur at the end of the |
96c8522a | 4475 | headline. Tags are normal words containing letters, numbers, @samp{_}, and |
a351880d | 4476 | @samp{@@}. Tags must be preceded and followed by a single colon, e.g., |
96c8522a | 4477 | @samp{:work:}. Several tags can be specified, as in @samp{:work:urgent:}. |
c8d0cf5c | 4478 | Tags will by default be in bold face with the same color as the headline. |
96c8522a | 4479 | You may specify special faces for specific tags using the variable |
c8d0cf5c | 4480 | @code{org-tag-faces}, in much the same way as you can for TODO keywords |
96c8522a | 4481 | (@pxref{Faces for TODO keywords}). |
4009494e GM |
4482 | |
4483 | @menu | |
c0468714 GM |
4484 | * Tag inheritance:: Tags use the tree structure of the outline |
4485 | * Setting tags:: How to assign tags to a headline | |
4486 | * Tag searches:: Searching for combinations of tags | |
4009494e GM |
4487 | @end menu |
4488 | ||
4489 | @node Tag inheritance, Setting tags, Tags, Tags | |
4490 | @section Tag inheritance | |
dbc28aaa | 4491 | @cindex tag inheritance |
4009494e GM |
4492 | @cindex inheritance, of tags |
4493 | @cindex sublevels, inclusion into tags match | |
4494 | ||
4495 | @i{Tags} make use of the hierarchical structure of outline trees. If a | |
4496 | heading has a certain tag, all subheadings will inherit the tag as | |
4497 | well. For example, in the list | |
4498 | ||
4499 | @example | |
dbc28aaa CD |
4500 | * Meeting with the French group :work: |
4501 | ** Summary by Frank :boss:notes: | |
4502 | *** TODO Prepare slides for him :action: | |
4009494e GM |
4503 | @end example |
4504 | ||
4505 | @noindent | |
dbc28aaa CD |
4506 | the final heading will have the tags @samp{:work:}, @samp{:boss:}, |
4507 | @samp{:notes:}, and @samp{:action:} even though the final heading is not | |
b349f79f | 4508 | explicitly marked with those tags. You can also set tags that all entries in |
c8d0cf5c | 4509 | a file should inherit just as if these tags were defined in a hypothetical |
7006d207 CD |
4510 | level zero that surrounds the entire file. Use a line like this@footnote{As |
4511 | with all these in-buffer settings, pressing @kbd{C-c C-c} activates any | |
4512 | changes in the line.}: | |
b349f79f | 4513 | |
c8d0cf5c | 4514 | @cindex #+FILETAGS |
b349f79f CD |
4515 | @example |
4516 | #+FILETAGS: :Peter:Boss:Secret: | |
4517 | @end example | |
4518 | ||
4519 | @noindent | |
c8d0cf5c CD |
4520 | @vindex org-use-tag-inheritance |
4521 | @vindex org-tags-exclude-from-inheritance | |
b349f79f | 4522 | To limit tag inheritance to specific tags, or to turn it off entirely, use |
96c8522a CD |
4523 | the variables @code{org-use-tag-inheritance} and |
4524 | @code{org-tags-exclude-from-inheritance}. | |
b349f79f | 4525 | |
c8d0cf5c | 4526 | @vindex org-tags-match-list-sublevels |
b349f79f | 4527 | When a headline matches during a tags search while tag inheritance is turned |
96c8522a | 4528 | on, all the sublevels in the same tree will (for a simple match form) match |
07450bee | 4529 | as well@footnote{This is only true if the search does not involve more |
96c8522a CD |
4530 | complex tests including properties (@pxref{Property searches}).}. The list |
4531 | of matches may then become very long. If you only want to see the first tags | |
4532 | match in a subtree, configure the variable | |
4533 | @code{org-tags-match-list-sublevels} (not recommended). | |
4009494e GM |
4534 | |
4535 | @node Setting tags, Tag searches, Tag inheritance, Tags | |
4536 | @section Setting tags | |
4537 | @cindex setting tags | |
4538 | @cindex tags, setting | |
4539 | ||
4540 | @kindex M-@key{TAB} | |
4541 | Tags can simply be typed into the buffer at the end of a headline. | |
4542 | After a colon, @kbd{M-@key{TAB}} offers completion on tags. There is | |
4543 | also a special command for inserting tags: | |
4544 | ||
4545 | @table @kbd | |
acedf35c | 4546 | @orgcmd{C-c C-q,org-set-tags-command} |
4009494e | 4547 | @cindex completion, of tags |
c8d0cf5c | 4548 | @vindex org-tags-column |
e66ba1df | 4549 | Enter new tags for the current headline. Org mode will either offer |
4009494e GM |
4550 | completion or a special single-key interface for setting tags, see |
4551 | below. After pressing @key{RET}, the tags will be inserted and aligned | |
4552 | to @code{org-tags-column}. When called with a @kbd{C-u} prefix, all | |
4553 | tags in the current buffer will be aligned to that column, just to make | |
4554 | things look nice. TAGS are automatically realigned after promotion, | |
4555 | demotion, and TODO state changes (@pxref{TODO basics}). | |
acedf35c | 4556 | @orgcmd{C-c C-c,org-set-tags-command} |
71d35b24 | 4557 | When the cursor is in a headline, this does the same as @kbd{C-c C-q}. |
4009494e GM |
4558 | @end table |
4559 | ||
c8d0cf5c | 4560 | @vindex org-tag-alist |
ce57c2fe | 4561 | Org supports tag insertion based on a @emph{list of tags}. By |
4009494e GM |
4562 | default this list is constructed dynamically, containing all tags |
4563 | currently used in the buffer. You may also globally specify a hard list | |
4564 | of tags with the variable @code{org-tag-alist}. Finally you can set | |
4565 | the default tags for a given file with lines like | |
4566 | ||
c8d0cf5c | 4567 | @cindex #+TAGS |
4009494e | 4568 | @example |
dbc28aaa CD |
4569 | #+TAGS: @@work @@home @@tennisclub |
4570 | #+TAGS: laptop car pc sailboat | |
4009494e GM |
4571 | @end example |
4572 | ||
4573 | If you have globally defined your preferred set of tags using the | |
4574 | variable @code{org-tag-alist}, but would like to use a dynamic tag list | |
dbc28aaa | 4575 | in a specific file, add an empty TAGS option line to that file: |
4009494e GM |
4576 | |
4577 | @example | |
4578 | #+TAGS: | |
4579 | @end example | |
4580 | ||
c8d0cf5c CD |
4581 | @vindex org-tag-persistent-alist |
4582 | If you have a preferred set of tags that you would like to use in every file, | |
4583 | in addition to those defined on a per-file basis by TAGS option lines, then | |
4584 | you may specify a list of tags with the variable | |
4585 | @code{org-tag-persistent-alist}. You may turn this off on a per-file basis | |
4586 | by adding a STARTUP option line to that file: | |
4587 | ||
4588 | @example | |
4589 | #+STARTUP: noptag | |
4590 | @end example | |
4591 | ||
e66ba1df | 4592 | By default Org mode uses the standard minibuffer completion facilities for |
a7808fba CD |
4593 | entering tags. However, it also implements another, quicker, tag selection |
4594 | method called @emph{fast tag selection}. This allows you to select and | |
4595 | deselect tags with just a single key press. For this to work well you should | |
4596 | assign unique letters to most of your commonly used tags. You can do this | |
4597 | globally by configuring the variable @code{org-tag-alist} in your | |
4598 | @file{.emacs} file. For example, you may find the need to tag many items in | |
4599 | different files with @samp{:@@home:}. In this case you can set something | |
4600 | like: | |
4009494e GM |
4601 | |
4602 | @lisp | |
dbc28aaa | 4603 | (setq org-tag-alist '(("@@work" . ?w) ("@@home" . ?h) ("laptop" . ?l))) |
4009494e GM |
4604 | @end lisp |
4605 | ||
c8d0cf5c CD |
4606 | @noindent If the tag is only relevant to the file you are working on, then you |
4607 | can instead set the TAGS option line as: | |
4009494e GM |
4608 | |
4609 | @example | |
dbc28aaa | 4610 | #+TAGS: @@work(w) @@home(h) @@tennisclub(t) laptop(l) pc(p) |
4009494e GM |
4611 | @end example |
4612 | ||
c8d0cf5c CD |
4613 | @noindent The tags interface will show the available tags in a splash |
4614 | window. If you want to start a new line after a specific tag, insert | |
4615 | @samp{\n} into the tag list | |
4616 | ||
4617 | @example | |
4618 | #+TAGS: @@work(w) @@home(h) @@tennisclub(t) \n laptop(l) pc(p) | |
4619 | @end example | |
4620 | ||
4621 | @noindent or write them in two lines: | |
4622 | ||
4623 | @example | |
4624 | #+TAGS: @@work(w) @@home(h) @@tennisclub(t) | |
4625 | #+TAGS: laptop(l) pc(p) | |
4626 | @end example | |
4627 | ||
4009494e | 4628 | @noindent |
c8d0cf5c | 4629 | You can also group together tags that are mutually exclusive by using |
a7808fba | 4630 | braces, as in: |
4009494e GM |
4631 | |
4632 | @example | |
dbc28aaa | 4633 | #+TAGS: @{ @@work(w) @@home(h) @@tennisclub(t) @} laptop(l) pc(p) |
4009494e GM |
4634 | @end example |
4635 | ||
dbc28aaa | 4636 | @noindent you indicate that at most one of @samp{@@work}, @samp{@@home}, |
a7808fba | 4637 | and @samp{@@tennisclub} should be selected. Multiple such groups are allowed. |
4009494e GM |
4638 | |
4639 | @noindent Don't forget to press @kbd{C-c C-c} with the cursor in one of | |
4640 | these lines to activate any changes. | |
4641 | ||
a7808fba | 4642 | @noindent |
c8d0cf5c | 4643 | To set these mutually exclusive groups in the variable @code{org-tags-alist}, |
a7808fba | 4644 | you must use the dummy tags @code{:startgroup} and @code{:endgroup} instead |
c8d0cf5c CD |
4645 | of the braces. Similarly, you can use @code{:newline} to indicate a line |
4646 | break. The previous example would be set globally by the following | |
a7808fba CD |
4647 | configuration: |
4648 | ||
4649 | @lisp | |
4650 | (setq org-tag-alist '((:startgroup . nil) | |
4651 | ("@@work" . ?w) ("@@home" . ?h) | |
4652 | ("@@tennisclub" . ?t) | |
4653 | (:endgroup . nil) | |
4654 | ("laptop" . ?l) ("pc" . ?p))) | |
4655 | @end lisp | |
4656 | ||
4657 | If at least one tag has a selection key then pressing @kbd{C-c C-c} will | |
4658 | automatically present you with a special interface, listing inherited tags, | |
4659 | the tags of the current headline, and a list of all valid tags with | |
4660 | corresponding keys@footnote{Keys will automatically be assigned to tags which | |
4661 | have no configured keys.}. In this interface, you can use the following | |
4662 | keys: | |
4009494e GM |
4663 | |
4664 | @table @kbd | |
4665 | @item a-z... | |
4666 | Pressing keys assigned to tags will add or remove them from the list of | |
4667 | tags in the current line. Selecting a tag in a group of mutually | |
4668 | exclusive tags will turn off any other tags from that group. | |
4669 | @kindex @key{TAB} | |
4670 | @item @key{TAB} | |
4671 | Enter a tag in the minibuffer, even if the tag is not in the predefined | |
4672 | list. You will be able to complete on all tags present in the buffer. | |
ce57c2fe BG |
4673 | You can also add several tags: just separate them with a comma. |
4674 | ||
4009494e GM |
4675 | @kindex @key{SPC} |
4676 | @item @key{SPC} | |
4677 | Clear all tags for this line. | |
4678 | @kindex @key{RET} | |
4679 | @item @key{RET} | |
4680 | Accept the modified set. | |
4681 | @item C-g | |
4682 | Abort without installing changes. | |
4683 | @item q | |
4684 | If @kbd{q} is not assigned to a tag, it aborts like @kbd{C-g}. | |
4685 | @item ! | |
4686 | Turn off groups of mutually exclusive tags. Use this to (as an | |
4687 | exception) assign several tags from such a group. | |
4688 | @item C-c | |
4689 | Toggle auto-exit after the next change (see below). | |
4690 | If you are using expert mode, the first @kbd{C-c} will display the | |
4691 | selection window. | |
4692 | @end table | |
4693 | ||
4694 | @noindent | |
4695 | This method lets you assign tags to a headline with very few keys. With | |
dbc28aaa CD |
4696 | the above setup, you could clear the current tags and set @samp{@@home}, |
4697 | @samp{laptop} and @samp{pc} tags with just the following keys: @kbd{C-c | |
4698 | C-c @key{SPC} h l p @key{RET}}. Switching from @samp{@@home} to | |
4699 | @samp{@@work} would be done with @kbd{C-c C-c w @key{RET}} or | |
4009494e GM |
4700 | alternatively with @kbd{C-c C-c C-c w}. Adding the non-predefined tag |
4701 | @samp{Sarah} could be done with @kbd{C-c C-c @key{TAB} S a r a h | |
4702 | @key{RET} @key{RET}}. | |
4703 | ||
c8d0cf5c CD |
4704 | @vindex org-fast-tag-selection-single-key |
4705 | If you find that most of the time you need only a single key press to | |
4009494e GM |
4706 | modify your list of tags, set the variable |
4707 | @code{org-fast-tag-selection-single-key}. Then you no longer have to | |
c8d0cf5c | 4708 | press @key{RET} to exit fast tag selection---it will immediately exit |
4009494e GM |
4709 | after the first change. If you then occasionally need more keys, press |
4710 | @kbd{C-c} to turn off auto-exit for the current tag selection process | |
4711 | (in effect: start selection with @kbd{C-c C-c C-c} instead of @kbd{C-c | |
4712 | C-c}). If you set the variable to the value @code{expert}, the special | |
4713 | window is not even shown for single-key tag selection, it comes up only | |
4714 | when you press an extra @kbd{C-c}. | |
4715 | ||
4716 | @node Tag searches, , Setting tags, Tags | |
4717 | @section Tag searches | |
4718 | @cindex tag searches | |
4719 | @cindex searching for tags | |
4720 | ||
dbc28aaa | 4721 | Once a system of tags has been set up, it can be used to collect related |
4009494e GM |
4722 | information into special lists. |
4723 | ||
4724 | @table @kbd | |
ce57c2fe | 4725 | @orgcmdkkc{C-c / m,C-c \\,org-match-sparse-tree} |
4009494e GM |
4726 | Create a sparse tree with all headlines matching a tags search. With a |
4727 | @kbd{C-u} prefix argument, ignore headlines that are not a TODO line. | |
acedf35c | 4728 | @orgcmd{C-c a m,org-tags-view} |
4009494e GM |
4729 | Create a global list of tag matches from all agenda files. |
4730 | @xref{Matching tags and properties}. | |
acedf35c | 4731 | @orgcmd{C-c a M,org-tags-view} |
c8d0cf5c | 4732 | @vindex org-tags-match-list-sublevels |
4009494e GM |
4733 | Create a global list of tag matches from all agenda files, but check |
4734 | only TODO items and force checking subitems (see variable | |
4735 | @code{org-tags-match-list-sublevels}). | |
4736 | @end table | |
4737 | ||
c8d0cf5c CD |
4738 | These commands all prompt for a match string which allows basic Boolean logic |
4739 | like @samp{+boss+urgent-project1}, to find entries with tags @samp{boss} and | |
4740 | @samp{urgent}, but not @samp{project1}, or @samp{Kathy|Sally} to find entries | |
4741 | which are tagged, like @samp{Kathy} or @samp{Sally}. The full syntax of the search | |
4742 | string is rich and allows also matching against TODO keywords, entry levels | |
4743 | and properties. For a complete description with many examples, see | |
4744 | @ref{Matching tags and properties}. | |
dbc28aaa | 4745 | |
e45e3595 | 4746 | |
a7808fba | 4747 | @node Properties and Columns, Dates and Times, Tags, Top |
86fbb8ca | 4748 | @chapter Properties and columns |
4009494e GM |
4749 | @cindex properties |
4750 | ||
e66ba1df BG |
4751 | A property is a key-value pair associated with an entry. Properties can be |
4752 | set so they are associated with a single entry, with every entry in a tree, | |
4753 | or with every entry in an Org mode file. | |
4754 | ||
4755 | There are two main applications for properties in Org mode. First, | |
4756 | properties are like tags, but with a value. Imagine maintaining a file where | |
c8d0cf5c | 4757 | you document bugs and plan releases for a piece of software. Instead of |
e66ba1df | 4758 | using tags like @code{:release_1:}, @code{:release_2:}, you can use a |
dbc28aaa | 4759 | property, say @code{:Release:}, that in different subtrees has different |
e66ba1df BG |
4760 | values, such as @code{1.0} or @code{2.0}. Second, you can use properties to |
4761 | implement (very basic) database capabilities in an Org buffer. Imagine | |
4762 | keeping track of your music CDs, where properties could be things such as the | |
4763 | album, artist, date of release, number of tracks, and so on. | |
dbc28aaa | 4764 | |
28a16a1b | 4765 | Properties can be conveniently edited and viewed in column view |
dbc28aaa CD |
4766 | (@pxref{Column view}). |
4767 | ||
4009494e | 4768 | @menu |
c0468714 | 4769 | * Property syntax:: How properties are spelled out |
e66ba1df | 4770 | * Special properties:: Access to other Org mode features |
c0468714 GM |
4771 | * Property searches:: Matching property values |
4772 | * Property inheritance:: Passing values down the tree | |
4773 | * Column view:: Tabular viewing and editing | |
4774 | * Property API:: Properties for Lisp programmers | |
4009494e GM |
4775 | @end menu |
4776 | ||
a7808fba CD |
4777 | @node Property syntax, Special properties, Properties and Columns, Properties and Columns |
4778 | @section Property syntax | |
4009494e GM |
4779 | @cindex property syntax |
4780 | @cindex drawer, for properties | |
4781 | ||
e66ba1df BG |
4782 | Properties are key-value pairs. When they are associated with a single entry |
4783 | or with a tree they need to be inserted into a special | |
4009494e GM |
4784 | drawer (@pxref{Drawers}) with the name @code{PROPERTIES}. Each property |
4785 | is specified on a single line, with the key (surrounded by colons) | |
4786 | first, and the value after it. Here is an example: | |
4787 | ||
4788 | @example | |
4789 | * CD collection | |
4790 | ** Classic | |
4791 | *** Goldberg Variations | |
4792 | :PROPERTIES: | |
4793 | :Title: Goldberg Variations | |
4794 | :Composer: J.S. Bach | |
28a16a1b | 4795 | :Artist: Glen Gould |
c8d0cf5c | 4796 | :Publisher: Deutsche Grammophon |
4009494e | 4797 | :NDisks: 1 |
28a16a1b | 4798 | :END: |
4009494e GM |
4799 | @end example |
4800 | ||
e66ba1df BG |
4801 | Depending on the value of @code{org-use-property-inheritance}, a property set |
4802 | this way will either be associated with a single entry, or the sub-tree | |
4803 | defined by the entry, see @ref{Property inheritance}. | |
4804 | ||
dbc28aaa CD |
4805 | You may define the allowed values for a particular property @samp{:Xyz:} |
4806 | by setting a property @samp{:Xyz_ALL:}. This special property is | |
4009494e GM |
4807 | @emph{inherited}, so if you set it in a level 1 entry, it will apply to |
4808 | the entire tree. When allowed values are defined, setting the | |
4809 | corresponding property becomes easier and is less prone to typing | |
4810 | errors. For the example with the CD collection, we can predefine | |
4811 | publishers and the number of disks in a box like this: | |
4812 | ||
4813 | @example | |
4814 | * CD collection | |
4815 | :PROPERTIES: | |
4816 | :NDisks_ALL: 1 2 3 4 | |
64fb801f | 4817 | :Publisher_ALL: "Deutsche Grammophon" Philips EMI |
4009494e GM |
4818 | :END: |
4819 | @end example | |
4820 | ||
4821 | If you want to set properties that can be inherited by any entry in a | |
4822 | file, use a line like | |
c8d0cf5c CD |
4823 | @cindex property, _ALL |
4824 | @cindex #+PROPERTY | |
4009494e GM |
4825 | @example |
4826 | #+PROPERTY: NDisks_ALL 1 2 3 4 | |
4827 | @end example | |
4828 | ||
e66ba1df BG |
4829 | If you want to add to the value of an existing property, append a @code{+} to |
4830 | the property name. The following results in the property @code{var} having | |
4831 | the value ``foo=1 bar=2''. | |
4832 | @cindex property, + | |
4833 | @example | |
4834 | #+PROPERTY: var foo=1 | |
4835 | #+PROPERTY: var+ bar=2 | |
4836 | @end example | |
4837 | ||
4838 | It is also possible to add to the values of inherited properties. The | |
4839 | following results in the @code{genres} property having the value ``Classic | |
4840 | Baroque'' under the @code{Goldberg Variations} subtree. | |
4841 | @cindex property, + | |
4842 | @example | |
4843 | * CD collection | |
4844 | ** Classic | |
4845 | :PROPERTIES: | |
4846 | :GENRES: Classic | |
4847 | :END: | |
4848 | *** Goldberg Variations | |
4849 | :PROPERTIES: | |
4850 | :Title: Goldberg Variations | |
4851 | :Composer: J.S. Bach | |
4852 | :Artist: Glen Gould | |
4853 | :Publisher: Deutsche Grammophon | |
4854 | :NDisks: 1 | |
4855 | :GENRES+: Baroque | |
4856 | :END: | |
4857 | @end example | |
4858 | Note that a property can only have one entry per Drawer. | |
4859 | ||
c8d0cf5c | 4860 | @vindex org-global-properties |
4009494e GM |
4861 | Property values set with the global variable |
4862 | @code{org-global-properties} can be inherited by all entries in all | |
a7808fba | 4863 | Org files. |
4009494e GM |
4864 | |
4865 | @noindent | |
4866 | The following commands help to work with properties: | |
4867 | ||
4868 | @table @kbd | |
ce57c2fe | 4869 | @orgcmd{M-@key{TAB},pcomplete} |
4009494e GM |
4870 | After an initial colon in a line, complete property keys. All keys used |
4871 | in the current file will be offered as possible completions. | |
acedf35c | 4872 | @orgcmd{C-c C-x p,org-set-property} |
dbc28aaa CD |
4873 | Set a property. This prompts for a property name and a value. If |
4874 | necessary, the property drawer is created as well. | |
4009494e | 4875 | @item M-x org-insert-property-drawer |
acedf35c | 4876 | @findex org-insert-property-drawer |
4009494e GM |
4877 | Insert a property drawer into the current entry. The drawer will be |
4878 | inserted early in the entry, but after the lines with planning | |
4879 | information like deadlines. | |
acedf35c | 4880 | @orgcmd{C-c C-c,org-property-action} |
4009494e | 4881 | With the cursor in a property drawer, this executes property commands. |
acedf35c | 4882 | @orgcmd{C-c C-c s,org-set-property} |
4009494e GM |
4883 | Set a property in the current entry. Both the property and the value |
4884 | can be inserted using completion. | |
acedf35c | 4885 | @orgcmdkkcc{S-@key{right},S-@key{left},org-property-next-allowed-value,org-property-previous-allowed-value} |
4009494e | 4886 | Switch property at point to the next/previous allowed value. |
acedf35c | 4887 | @orgcmd{C-c C-c d,org-delete-property} |
4009494e | 4888 | Remove a property from the current entry. |
acedf35c | 4889 | @orgcmd{C-c C-c D,org-delete-property-globally} |
4009494e | 4890 | Globally remove a property, from all entries in the current file. |
acedf35c | 4891 | @orgcmd{C-c C-c c,org-compute-property-at-point} |
dbc28aaa CD |
4892 | Compute the property at point, using the operator and scope from the |
4893 | nearest column format definition. | |
4009494e GM |
4894 | @end table |
4895 | ||
a7808fba CD |
4896 | @node Special properties, Property searches, Property syntax, Properties and Columns |
4897 | @section Special properties | |
4009494e GM |
4898 | @cindex properties, special |
4899 | ||
e66ba1df | 4900 | Special properties provide an alternative access method to Org mode features, |
ce57c2fe BG |
4901 | like the TODO state or the priority of an entry, discussed in the previous |
4902 | chapters. This interface exists so that you can include these states in a | |
4903 | column view (@pxref{Column view}), or to use them in queries. The following | |
4904 | property names are special and (except for @code{:CATEGORY:}) should not be | |
dbc28aaa | 4905 | used as keys in the properties drawer: |
4009494e | 4906 | |
c8d0cf5c CD |
4907 | @cindex property, special, TODO |
4908 | @cindex property, special, TAGS | |
4909 | @cindex property, special, ALLTAGS | |
4910 | @cindex property, special, CATEGORY | |
4911 | @cindex property, special, PRIORITY | |
4912 | @cindex property, special, DEADLINE | |
4913 | @cindex property, special, SCHEDULED | |
4914 | @cindex property, special, CLOSED | |
4915 | @cindex property, special, TIMESTAMP | |
4916 | @cindex property, special, TIMESTAMP_IA | |
4917 | @cindex property, special, CLOCKSUM | |
ed21c5c8 | 4918 | @cindex property, special, BLOCKED |
c8d0cf5c CD |
4919 | @c guessing that ITEM is needed in this area; also, should this list be sorted? |
4920 | @cindex property, special, ITEM | |
ce57c2fe | 4921 | @cindex property, special, FILE |
4009494e GM |
4922 | @example |
4923 | TODO @r{The TODO keyword of the entry.} | |
4924 | TAGS @r{The tags defined directly in the headline.} | |
4925 | ALLTAGS @r{All tags, including inherited ones.} | |
c8d0cf5c | 4926 | CATEGORY @r{The category of an entry.} |
4009494e GM |
4927 | PRIORITY @r{The priority of the entry, a string with a single letter.} |
4928 | DEADLINE @r{The deadline time string, without the angular brackets.} | |
c8d0cf5c CD |
4929 | SCHEDULED @r{The scheduling timestamp, without the angular brackets.} |
4930 | CLOSED @r{When was this entry closed?} | |
4931 | TIMESTAMP @r{The first keyword-less timestamp in the entry.} | |
4932 | TIMESTAMP_IA @r{The first inactive timestamp in the entry.} | |
dbc28aaa | 4933 | CLOCKSUM @r{The sum of CLOCK intervals in the subtree. @code{org-clock-sum}} |
ce57c2fe | 4934 | @r{must be run first to compute the values in the current buffer.} |
ed21c5c8 | 4935 | BLOCKED @r{"t" if task is currently blocked by children or siblings} |
c8d0cf5c | 4936 | ITEM @r{The content of the entry.} |
ce57c2fe | 4937 | FILE @r{The filename the entry is located in.} |
4009494e GM |
4938 | @end example |
4939 | ||
a7808fba | 4940 | @node Property searches, Property inheritance, Special properties, Properties and Columns |
4009494e GM |
4941 | @section Property searches |
4942 | @cindex properties, searching | |
dbc28aaa | 4943 | @cindex searching, of properties |
4009494e | 4944 | |
a7808fba | 4945 | To create sparse trees and special lists with selection based on properties, |
c8d0cf5c CD |
4946 | the same commands are used as for tag searches (@pxref{Tag searches}). |
4947 | @table @kbd | |
acedf35c | 4948 | @orgcmdkkc{C-c / m,C-c \,org-match-sparse-tree} |
c8d0cf5c CD |
4949 | Create a sparse tree with all matching entries. With a |
4950 | @kbd{C-u} prefix argument, ignore headlines that are not a TODO line. | |
acedf35c | 4951 | @orgcmd{C-c a m,org-tags-view} |
c8d0cf5c CD |
4952 | Create a global list of tag/property matches from all agenda files. |
4953 | @xref{Matching tags and properties}. | |
acedf35c | 4954 | @orgcmd{C-c a M,org-tags-view} |
c8d0cf5c CD |
4955 | @vindex org-tags-match-list-sublevels |
4956 | Create a global list of tag matches from all agenda files, but check | |
4957 | only TODO items and force checking of subitems (see variable | |
4958 | @code{org-tags-match-list-sublevels}). | |
4959 | @end table | |
a7808fba | 4960 | |
c8d0cf5c CD |
4961 | The syntax for the search string is described in @ref{Matching tags and |
4962 | properties}. | |
dbc28aaa CD |
4963 | |
4964 | There is also a special command for creating sparse trees based on a | |
4965 | single property: | |
4966 | ||
4967 | @table @kbd | |
acedf35c | 4968 | @orgkey{C-c / p} |
dbc28aaa CD |
4969 | Create a sparse tree based on the value of a property. This first |
4970 | prompts for the name of a property, and then for a value. A sparse tree | |
4971 | is created with all entries that define this property with the given | |
acedf35c | 4972 | value. If you enclose the value in curly braces, it is interpreted as |
dbc28aaa CD |
4973 | a regular expression and matched against the property values. |
4974 | @end table | |
4975 | ||
a7808fba | 4976 | @node Property inheritance, Column view, Property searches, Properties and Columns |
dbc28aaa | 4977 | @section Property Inheritance |
a7808fba CD |
4978 | @cindex properties, inheritance |
4979 | @cindex inheritance, of properties | |
dbc28aaa | 4980 | |
c8d0cf5c | 4981 | @vindex org-use-property-inheritance |
e66ba1df | 4982 | The outline structure of Org mode documents lends itself to an |
c8d0cf5c | 4983 | inheritance model of properties: if the parent in a tree has a certain |
e66ba1df | 4984 | property, the children can inherit this property. Org mode does not |
dbc28aaa CD |
4985 | turn this on by default, because it can slow down property searches |
4986 | significantly and is often not needed. However, if you find inheritance | |
4987 | useful, you can turn it on by setting the variable | |
c8d0cf5c | 4988 | @code{org-use-property-inheritance}. It may be set to @code{t} to make |
a7808fba CD |
4989 | all properties inherited from the parent, to a list of properties |
4990 | that should be inherited, or to a regular expression that matches | |
86fbb8ca | 4991 | inherited properties. If a property has the value @samp{nil}, this is |
acedf35c | 4992 | interpreted as an explicit undefine of the property, so that inheritance |
86fbb8ca | 4993 | search will stop at this value and return @code{nil}. |
dbc28aaa | 4994 | |
e66ba1df | 4995 | Org mode has a few properties for which inheritance is hard-coded, at |
dbc28aaa CD |
4996 | least for the special applications for which they are used: |
4997 | ||
c8d0cf5c | 4998 | @cindex property, COLUMNS |
dbc28aaa CD |
4999 | @table @code |
5000 | @item COLUMNS | |
5001 | The @code{:COLUMNS:} property defines the format of column view | |
5002 | (@pxref{Column view}). It is inherited in the sense that the level | |
5003 | where a @code{:COLUMNS:} property is defined is used as the starting | |
5004 | point for a column view table, independently of the location in the | |
5005 | subtree from where columns view is turned on. | |
5006 | @item CATEGORY | |
c8d0cf5c | 5007 | @cindex property, CATEGORY |
dbc28aaa CD |
5008 | For agenda view, a category set through a @code{:CATEGORY:} property |
5009 | applies to the entire subtree. | |
5010 | @item ARCHIVE | |
c8d0cf5c | 5011 | @cindex property, ARCHIVE |
dbc28aaa CD |
5012 | For archiving, the @code{:ARCHIVE:} property may define the archive |
5013 | location for the entire subtree (@pxref{Moving subtrees}). | |
28a16a1b | 5014 | @item LOGGING |
c8d0cf5c | 5015 | @cindex property, LOGGING |
28a16a1b CD |
5016 | The LOGGING property may define logging settings for an entry or a |
5017 | subtree (@pxref{Tracking TODO state changes}). | |
dbc28aaa CD |
5018 | @end table |
5019 | ||
a7808fba CD |
5020 | @node Column view, Property API, Property inheritance, Properties and Columns |
5021 | @section Column view | |
4009494e GM |
5022 | |
5023 | A great way to view and edit properties in an outline tree is | |
c8d0cf5c | 5024 | @emph{column view}. In column view, each outline node is turned into a |
4009494e | 5025 | table row. Columns in this table provide access to properties of the |
e66ba1df | 5026 | entries. Org mode implements columns by overlaying a tabular structure |
4009494e GM |
5027 | over the headline of each item. While the headlines have been turned |
5028 | into a table row, you can still change the visibility of the outline | |
5029 | tree. For example, you get a compact table by switching to CONTENTS | |
5030 | view (@kbd{S-@key{TAB} S-@key{TAB}}, or simply @kbd{c} while column view | |
5031 | is active), but you can still open, read, and edit the entry below each | |
5032 | headline. Or, you can switch to column view after executing a sparse | |
5033 | tree command and in this way get a table only for the selected items. | |
a7808fba | 5034 | Column view also works in agenda buffers (@pxref{Agenda Views}) where |
4009494e GM |
5035 | queries have collected selected items, possibly from a number of files. |
5036 | ||
5037 | @menu | |
c0468714 GM |
5038 | * Defining columns:: The COLUMNS format property |
5039 | * Using column view:: How to create and use column view | |
5040 | * Capturing column view:: A dynamic block for column view | |
4009494e GM |
5041 | @end menu |
5042 | ||
5043 | @node Defining columns, Using column view, Column view, Column view | |
a7808fba | 5044 | @subsection Defining columns |
4009494e GM |
5045 | @cindex column view, for properties |
5046 | @cindex properties, column view | |
5047 | ||
5048 | Setting up a column view first requires defining the columns. This is | |
5049 | done by defining a column format line. | |
5050 | ||
5051 | @menu | |
c0468714 GM |
5052 | * Scope of column definitions:: Where defined, where valid? |
5053 | * Column attributes:: Appearance and content of a column | |
4009494e GM |
5054 | @end menu |
5055 | ||
5056 | @node Scope of column definitions, Column attributes, Defining columns, Defining columns | |
5057 | @subsubsection Scope of column definitions | |
5058 | ||
5059 | To define a column format for an entire file, use a line like | |
5060 | ||
c8d0cf5c | 5061 | @cindex #+COLUMNS |
4009494e GM |
5062 | @example |
5063 | #+COLUMNS: %25ITEM %TAGS %PRIORITY %TODO | |
5064 | @end example | |
5065 | ||
dbc28aaa CD |
5066 | To specify a format that only applies to a specific tree, add a |
5067 | @code{:COLUMNS:} property to the top node of that tree, for example: | |
5068 | ||
4009494e GM |
5069 | @example |
5070 | ** Top node for columns view | |
5071 | :PROPERTIES: | |
5072 | :COLUMNS: %25ITEM %TAGS %PRIORITY %TODO | |
5073 | :END: | |
5074 | @end example | |
5075 | ||
dbc28aaa | 5076 | If a @code{:COLUMNS:} property is present in an entry, it defines columns |
4009494e GM |
5077 | for the entry itself, and for the entire subtree below it. Since the |
5078 | column definition is part of the hierarchical structure of the document, | |
5079 | you can define columns on level 1 that are general enough for all | |
5080 | sublevels, and more specific columns further down, when you edit a | |
5081 | deeper part of the tree. | |
5082 | ||
5083 | @node Column attributes, , Scope of column definitions, Defining columns | |
5084 | @subsubsection Column attributes | |
5085 | A column definition sets the attributes of a column. The general | |
5086 | definition looks like this: | |
5087 | ||
5088 | @example | |
c8d0cf5c | 5089 | %[@var{width}]@var{property}[(@var{title})][@{@var{summary-type}@}] |
4009494e GM |
5090 | @end example |
5091 | ||
5092 | @noindent | |
5093 | Except for the percent sign and the property name, all items are | |
5094 | optional. The individual parts have the following meaning: | |
5095 | ||
5096 | @example | |
c8d0cf5c | 5097 | @var{width} @r{An integer specifying the width of the column in characters.} |
72d803ad | 5098 | @r{If omitted, the width will be determined automatically.} |
c8d0cf5c | 5099 | @var{property} @r{The property that should be edited in this column.} |
72d803ad CD |
5100 | @r{Special properties representing meta data are allowed here} |
5101 | @r{as well (@pxref{Special properties})} | |
ce57c2fe | 5102 | @var{title} @r{The header text for the column. If omitted, the property} |
afe98dfa | 5103 | @r{name is used.} |
c8d0cf5c | 5104 | @{@var{summary-type}@} @r{The summary type. If specified, the column values for} |
72d803ad CD |
5105 | @r{parent nodes are computed from the children.} |
5106 | @r{Supported summary types are:} | |
5107 | @{+@} @r{Sum numbers in this column.} | |
5108 | @{+;%.1f@} @r{Like @samp{+}, but format result with @samp{%.1f}.} | |
5109 | @{$@} @r{Currency, short for @samp{+;%.2f}.} | |
86fbb8ca | 5110 | @{:@} @r{Sum times, HH:MM, plain numbers are hours.} |
72d803ad CD |
5111 | @{X@} @r{Checkbox status, @samp{[X]} if all children are @samp{[X]}.} |
5112 | @{X/@} @r{Checkbox status, @samp{[n/m]}.} | |
5113 | @{X%@} @r{Checkbox status, @samp{[n%]}.} | |
5114 | @{min@} @r{Smallest number in column.} | |
5115 | @{max@} @r{Largest number.} | |
5116 | @{mean@} @r{Arithmetic mean of numbers.} | |
5117 | @{:min@} @r{Smallest time value in column.} | |
5118 | @{:max@} @r{Largest time value.} | |
5119 | @{:mean@} @r{Arithmetic mean of time values.} | |
afe98dfa CD |
5120 | @{@@min@} @r{Minimum age (in days/hours/mins/seconds).} |
5121 | @{@@max@} @r{Maximum age (in days/hours/mins/seconds).} | |
5122 | @{@@mean@} @r{Arithmetic mean of ages (in days/hours/mins/seconds).} | |
5123 | @{est+@} @r{Add low-high estimates.} | |
4009494e GM |
5124 | @end example |
5125 | ||
5126 | @noindent | |
a351880d | 5127 | Be aware that you can only have one summary type for any property you |
ce57c2fe | 5128 | include. Subsequent columns referencing the same property will all display the |
a351880d CD |
5129 | same summary information. |
5130 | ||
afe98dfa CD |
5131 | The @code{est+} summary type requires further explanation. It is used for |
5132 | combining estimates, expressed as low-high ranges. For example, instead | |
5133 | of estimating a particular task will take 5 days, you might estimate it as | |
acedf35c | 5134 | 5-6 days if you're fairly confident you know how much work is required, or |
afe98dfa CD |
5135 | 1-10 days if you don't really know what needs to be done. Both ranges |
5136 | average at 5.5 days, but the first represents a more predictable delivery. | |
5137 | ||
5138 | When combining a set of such estimates, simply adding the lows and highs | |
ce57c2fe | 5139 | produces an unrealistically wide result. Instead, @code{est+} adds the |
afe98dfa CD |
5140 | statistical mean and variance of the sub-tasks, generating a final estimate |
5141 | from the sum. For example, suppose you had ten tasks, each of which was | |
5142 | estimated at 0.5 to 2 days of work. Straight addition produces an estimate | |
5143 | of 5 to 20 days, representing what to expect if everything goes either | |
ce57c2fe | 5144 | extremely well or extremely poorly. In contrast, @code{est+} estimates the |
afe98dfa CD |
5145 | full job more realistically, at 10-15 days. |
5146 | ||
4009494e GM |
5147 | Here is an example for a complete columns definition, along with allowed |
5148 | values. | |
5149 | ||
5150 | @example | |
7006d207 | 5151 | :COLUMNS: %25ITEM %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.} |
c0468714 | 5152 | %10Time_Estimate@{:@} %CLOCKSUM |
4009494e GM |
5153 | :Owner_ALL: Tammy Mark Karl Lisa Don |
5154 | :Status_ALL: "In progress" "Not started yet" "Finished" "" | |
5155 | :Approved_ALL: "[ ]" "[X]" | |
5156 | @end example | |
5157 | ||
c8d0cf5c | 5158 | @noindent |
4009494e | 5159 | The first column, @samp{%25ITEM}, means the first 25 characters of the |
ce57c2fe | 5160 | item itself, i.e.@: of the headline. You probably always should start the |
28a16a1b CD |
5161 | column definition with the @samp{ITEM} specifier. The other specifiers |
5162 | create columns @samp{Owner} with a list of names as allowed values, for | |
4009494e GM |
5163 | @samp{Status} with four different possible values, and for a checkbox |
5164 | field @samp{Approved}. When no width is given after the @samp{%} | |
5165 | character, the column will be exactly as wide as it needs to be in order | |
5166 | to fully display all values. The @samp{Approved} column does have a | |
5167 | modified title (@samp{Approved?}, with a question mark). Summaries will | |
dbc28aaa | 5168 | be created for the @samp{Time_Estimate} column by adding time duration |
4009494e | 5169 | expressions like HH:MM, and for the @samp{Approved} column, by providing |
dbc28aaa CD |
5170 | an @samp{[X]} status if all children have been checked. The |
5171 | @samp{CLOCKSUM} column is special, it lists the sum of CLOCK intervals | |
5172 | in the subtree. | |
4009494e | 5173 | |
a7808fba CD |
5174 | @node Using column view, Capturing column view, Defining columns, Column view |
5175 | @subsection Using column view | |
4009494e GM |
5176 | |
5177 | @table @kbd | |
5178 | @tsubheading{Turning column view on and off} | |
acedf35c | 5179 | @orgcmd{C-c C-x C-c,org-columns} |
c8d0cf5c CD |
5180 | @vindex org-columns-default-format |
5181 | Turn on column view. If the cursor is before the first headline in the file, | |
5182 | column view is turned on for the entire file, using the @code{#+COLUMNS} | |
a351880d | 5183 | definition. If the cursor is somewhere inside the outline, this command |
c8d0cf5c CD |
5184 | searches the hierarchy, up from point, for a @code{:COLUMNS:} property that |
5185 | defines a format. When one is found, the column view table is established | |
5186 | for the tree starting at the entry that contains the @code{:COLUMNS:} | |
5187 | property. If no such property is found, the format is taken from the | |
5188 | @code{#+COLUMNS} line or from the variable @code{org-columns-default-format}, | |
5189 | and column view is established for the current entry and its subtree. | |
acedf35c | 5190 | @orgcmd{r,org-columns-redo} |
a7808fba | 5191 | Recreate the column view, to include recent changes made in the buffer. |
acedf35c | 5192 | @orgcmd{g,org-columns-redo} |
28a16a1b | 5193 | Same as @kbd{r}. |
acedf35c | 5194 | @orgcmd{q,org-columns-quit} |
4009494e GM |
5195 | Exit column view. |
5196 | @tsubheading{Editing values} | |
5197 | @item @key{left} @key{right} @key{up} @key{down} | |
5198 | Move through the column view from field to field. | |
5199 | @kindex S-@key{left} | |
5200 | @kindex S-@key{right} | |
5201 | @item S-@key{left}/@key{right} | |
5202 | Switch to the next/previous allowed value of the field. For this, you | |
5203 | have to have specified allowed values for a property. | |
b349f79f | 5204 | @item 1..9,0 |
acedf35c CD |
5205 | Directly select the Nth allowed value, @kbd{0} selects the 10th value. |
5206 | @orgcmdkkcc{n,p,org-columns-next-allowed-value,org-columns-previous-allowed-value} | |
4009494e | 5207 | Same as @kbd{S-@key{left}/@key{right}} |
acedf35c | 5208 | @orgcmd{e,org-columns-edit-value} |
4009494e GM |
5209 | Edit the property at point. For the special properties, this will |
5210 | invoke the same interface that you normally use to change that | |
5211 | property. For example, when editing a TAGS property, the tag completion | |
5212 | or fast selection interface will pop up. | |
acedf35c | 5213 | @orgcmd{C-c C-c,org-columns-set-tags-or-toggle} |
dbc28aaa | 5214 | When there is a checkbox at point, toggle it. |
acedf35c | 5215 | @orgcmd{v,org-columns-show-value} |
4009494e GM |
5216 | View the full value of this property. This is useful if the width of |
5217 | the column is smaller than that of the value. | |
acedf35c | 5218 | @orgcmd{a,org-columns-edit-allowed} |
4009494e GM |
5219 | Edit the list of allowed values for this property. If the list is found |
5220 | in the hierarchy, the modified values is stored there. If no list is | |
5221 | found, the new value is stored in the first entry that is part of the | |
5222 | current column view. | |
5223 | @tsubheading{Modifying the table structure} | |
acedf35c | 5224 | @orgcmdkkcc{<,>,org-columns-narrow,org-columns-widen} |
4009494e | 5225 | Make the column narrower/wider by one character. |
acedf35c | 5226 | @orgcmd{S-M-@key{right},org-columns-new} |
864c9740 | 5227 | Insert a new column, to the left of the current column. |
acedf35c | 5228 | @orgcmd{S-M-@key{left},org-columns-delete} |
4009494e GM |
5229 | Delete the current column. |
5230 | @end table | |
5231 | ||
a7808fba CD |
5232 | @node Capturing column view, , Using column view, Column view |
5233 | @subsection Capturing column view | |
dbc28aaa CD |
5234 | |
5235 | Since column view is just an overlay over a buffer, it cannot be | |
5236 | exported or printed directly. If you want to capture a column view, use | |
c8d0cf5c | 5237 | a @code{columnview} dynamic block (@pxref{Dynamic blocks}). The frame |
28a16a1b | 5238 | of this block looks like this: |
dbc28aaa | 5239 | |
c8d0cf5c | 5240 | @cindex #+BEGIN, columnview |
dbc28aaa CD |
5241 | @example |
5242 | * The column view | |
5243 | #+BEGIN: columnview :hlines 1 :id "label" | |
5244 | ||
5245 | #+END: | |
5246 | @end example | |
5247 | ||
5248 | @noindent This dynamic block has the following parameters: | |
5249 | ||
5250 | @table @code | |
5251 | @item :id | |
c8d0cf5c | 5252 | This is the most important parameter. Column view is a feature that is |
dbc28aaa | 5253 | often localized to a certain (sub)tree, and the capture block might be |
c8d0cf5c CD |
5254 | at a different location in the file. To identify the tree whose view to |
5255 | capture, you can use 4 values: | |
5256 | @cindex property, ID | |
dbc28aaa CD |
5257 | @example |
5258 | local @r{use the tree in which the capture block is located} | |
5259 | global @r{make a global view, including all headings in the file} | |
c8d0cf5c | 5260 | "file:@var{path-to-file}" |
55e0839d | 5261 | @r{run column view at the top of this file} |
c8d0cf5c | 5262 | "@var{ID}" @r{call column view in the tree that has an @code{:ID:}} |
b349f79f CD |
5263 | @r{property with the value @i{label}. You can use} |
5264 | @r{@kbd{M-x org-id-copy} to create a globally unique ID for} | |
5265 | @r{the current entry and copy it to the kill-ring.} | |
dbc28aaa CD |
5266 | @end example |
5267 | @item :hlines | |
c8d0cf5c CD |
5268 | When @code{t}, insert an hline after every line. When a number @var{N}, insert |
5269 | an hline before each headline with level @code{<= @var{N}}. | |
dbc28aaa | 5270 | @item :vlines |
c8d0cf5c | 5271 | When set to @code{t}, force column groups to get vertical lines. |
28a16a1b CD |
5272 | @item :maxlevel |
5273 | When set to a number, don't capture entries below this level. | |
5274 | @item :skip-empty-rows | |
c8d0cf5c | 5275 | When set to @code{t}, skip rows where the only non-empty specifier of the |
28a16a1b CD |
5276 | column view is @code{ITEM}. |
5277 | ||
dbc28aaa CD |
5278 | @end table |
5279 | ||
5280 | @noindent | |
5281 | The following commands insert or update the dynamic block: | |
5282 | ||
5283 | @table @kbd | |
acedf35c | 5284 | @orgcmd{C-c C-x i,org-insert-columns-dblock} |
dbc28aaa | 5285 | Insert a dynamic block capturing a column view. You will be prompted |
c8d0cf5c | 5286 | for the scope or ID of the view. |
acedf35c | 5287 | @orgcmdkkc{C-c C-c,C-c C-x C-u,org-dblock-update} |
c8d0cf5c | 5288 | Update dynamic block at point. The cursor needs to be in the |
dbc28aaa | 5289 | @code{#+BEGIN} line of the dynamic block. |
acedf35c | 5290 | @orgcmd{C-u C-c C-x C-u,org-update-all-dblocks} |
dbc28aaa | 5291 | Update all dynamic blocks (@pxref{Dynamic blocks}). This is useful if |
acedf35c CD |
5292 | you have several clock table blocks, column-capturing blocks or other dynamic |
5293 | blocks in a buffer. | |
dbc28aaa CD |
5294 | @end table |
5295 | ||
864c9740 | 5296 | You can add formulas to the column view table and you may add plotting |
c8d0cf5c | 5297 | instructions in front of the table---these will survive an update of the |
864c9740 CD |
5298 | block. If there is a @code{#+TBLFM:} after the table, the table will |
5299 | actually be recalculated automatically after an update. | |
5300 | ||
c8d0cf5c CD |
5301 | An alternative way to capture and process property values into a table is |
5302 | provided by Eric Schulte's @file{org-collector.el} which is a contributed | |
5303 | package@footnote{Contributed packages are not part of Emacs, but are | |
5304 | distributed with the main distribution of Org (visit | |
5305 | @uref{http://orgmode.org}).}. It provides a general API to collect | |
5306 | properties from entries in a certain scope, and arbitrary Lisp expressions to | |
5307 | process these values before inserting them into a table or a dynamic block. | |
5308 | ||
a7808fba | 5309 | @node Property API, , Column view, Properties and Columns |
4009494e GM |
5310 | @section The Property API |
5311 | @cindex properties, API | |
5312 | @cindex API, for properties | |
5313 | ||
5314 | There is a full API for accessing and changing properties. This API can | |
5315 | be used by Emacs Lisp programs to work with properties and to implement | |
5316 | features based on them. For more information see @ref{Using the | |
5317 | property API}. | |
5318 | ||
a351880d | 5319 | @node Dates and Times, Capture - Refile - Archive, Properties and Columns, Top |
86fbb8ca | 5320 | @chapter Dates and times |
dbc28aaa CD |
5321 | @cindex dates |
5322 | @cindex times | |
c8d0cf5c CD |
5323 | @cindex timestamp |
5324 | @cindex date stamp | |
4009494e | 5325 | |
dbc28aaa CD |
5326 | To assist project planning, TODO items can be labeled with a date and/or |
5327 | a time. The specially formatted string carrying the date and time | |
e66ba1df | 5328 | information is called a @emph{timestamp} in Org mode. This may be a |
dbc28aaa | 5329 | little confusing because timestamp is often used as indicating when |
e66ba1df | 5330 | something was created or last changed. However, in Org mode this term |
dbc28aaa | 5331 | is used in a much wider sense. |
4009494e GM |
5332 | |
5333 | @menu | |
c0468714 GM |
5334 | * Timestamps:: Assigning a time to a tree entry |
5335 | * Creating timestamps:: Commands which insert timestamps | |
5336 | * Deadlines and scheduling:: Planning your work | |
5337 | * Clocking work time:: Tracking how long you spend on a task | |
c0468714 GM |
5338 | * Effort estimates:: Planning work effort in advance |
5339 | * Relative timer:: Notes with a running timer | |
afe98dfa | 5340 | * Countdown timer:: Starting a countdown timer for a task |
4009494e GM |
5341 | @end menu |
5342 | ||
5343 | ||
a7808fba | 5344 | @node Timestamps, Creating timestamps, Dates and Times, Dates and Times |
c8d0cf5c CD |
5345 | @section Timestamps, deadlines, and scheduling |
5346 | @cindex timestamps | |
4009494e GM |
5347 | @cindex ranges, time |
5348 | @cindex date stamps | |
5349 | @cindex deadlines | |
5350 | @cindex scheduling | |
5351 | ||
7006d207 | 5352 | A timestamp is a specification of a date (possibly with a time or a range of |
e66ba1df BG |
5353 | times) in a special format, either @samp{<2003-09-16 Tue>}@footnote{In this |
5354 | simplest form, the day name is optional when you type the date yourself. | |
5355 | However, any dates inserted or modified by Org will add that day name, for | |
5356 | reading convenience.} or @samp{<2003-09-16 Tue 09:39>} or @samp{<2003-09-16 | |
5357 | Tue 12:00-12:30>}@footnote{This is inspired by the standard ISO 8601 | |
5358 | date/time format. To use an alternative format, see @ref{Custom time | |
5359 | format}.}. A timestamp can appear anywhere in the headline or body of an Org | |
5360 | tree entry. Its presence causes entries to be shown on specific dates in the | |
5361 | agenda (@pxref{Weekly/daily agenda}). We distinguish: | |
4009494e GM |
5362 | |
5363 | @table @var | |
c8d0cf5c | 5364 | @item Plain timestamp; Event; Appointment |
4009494e | 5365 | @cindex timestamp |
e66ba1df | 5366 | @cindex appointment |
c8d0cf5c | 5367 | A simple timestamp just assigns a date/time to an item. This is just |
dbc28aaa CD |
5368 | like writing down an appointment or event in a paper agenda. In the |
5369 | timeline and agenda displays, the headline of an entry associated with a | |
c8d0cf5c | 5370 | plain timestamp will be shown exactly on that date. |
4009494e GM |
5371 | |
5372 | @example | |
5373 | * Meet Peter at the movies <2006-11-01 Wed 19:15> | |
5374 | * Discussion on climate change <2006-11-02 Thu 20:00-22:00> | |
5375 | @end example | |
5376 | ||
c8d0cf5c | 5377 | @item Timestamp with repeater interval |
4009494e | 5378 | @cindex timestamp, with repeater interval |
c8d0cf5c | 5379 | A timestamp may contain a @emph{repeater interval}, indicating that it |
4009494e | 5380 | applies not only on the given date, but again and again after a certain |
c8d0cf5c | 5381 | interval of N days (d), weeks (w), months (m), or years (y). The |
4009494e GM |
5382 | following will show up in the agenda every Wednesday: |
5383 | ||
5384 | @example | |
5385 | * Pick up Sam at school <2007-05-16 Wed 12:30 +1w> | |
5386 | @end example | |
5387 | ||
5388 | @item Diary-style sexp entries | |
e66ba1df | 5389 | For more complex date specifications, Org mode supports using the special |
ce57c2fe BG |
5390 | sexp diary entries implemented in the Emacs calendar/diary |
5391 | package@footnote{When working with the standard diary sexp functions, you | |
5392 | need to be very careful with the order of the arguments. That order depend | |
5393 | evilly on the variable @code{calendar-date-style} (or, for older Emacs | |
5394 | versions, @code{european-calendar-style}). For example, to specify a date | |
5395 | December 12, 2005, the call might look like @code{(diary-date 12 1 2005)} or | |
5396 | @code{(diary-date 1 12 2005)} or @code{(diary-date 2005 12 1)}, depending on | |
e66ba1df | 5397 | the settings. This has been the source of much confusion. Org mode users |
ce57c2fe BG |
5398 | can resort to special versions of these functions like @code{org-date} or |
5399 | @code{org-anniversary}. These work just like the corresponding @code{diary-} | |
5400 | functions, but with stable ISO order of arguments (year, month, day) wherever | |
153ae947 BG |
5401 | applicable, independent of the value of @code{calendar-date-style}.}. For |
5402 | example with optional time | |
4009494e GM |
5403 | |
5404 | @example | |
153ae947 | 5405 | * 22:00-23:00 The nerd meeting on every 2nd Thursday of the month |
ce57c2fe | 5406 | <%%(org-float t 4 2)> |
4009494e GM |
5407 | @end example |
5408 | ||
5409 | @item Time/Date range | |
5410 | @cindex timerange | |
5411 | @cindex date range | |
c8d0cf5c | 5412 | Two timestamps connected by @samp{--} denote a range. The headline |
4009494e GM |
5413 | will be shown on the first and last day of the range, and on any dates |
5414 | that are displayed and fall in the range. Here is an example: | |
5415 | ||
5416 | @example | |
5417 | ** Meeting in Amsterdam | |
5418 | <2004-08-23 Mon>--<2004-08-26 Thu> | |
5419 | @end example | |
5420 | ||
c8d0cf5c | 5421 | @item Inactive timestamp |
4009494e GM |
5422 | @cindex timestamp, inactive |
5423 | @cindex inactive timestamp | |
c8d0cf5c CD |
5424 | Just like a plain timestamp, but with square brackets instead of |
5425 | angular ones. These timestamps are inactive in the sense that they do | |
4009494e GM |
5426 | @emph{not} trigger an entry to show up in the agenda. |
5427 | ||
5428 | @example | |
5429 | * Gillian comes late for the fifth time [2006-11-01 Wed] | |
5430 | @end example | |
5431 | ||
5432 | @end table | |
5433 | ||
a7808fba | 5434 | @node Creating timestamps, Deadlines and scheduling, Timestamps, Dates and Times |
4009494e GM |
5435 | @section Creating timestamps |
5436 | @cindex creating timestamps | |
5437 | @cindex timestamps, creating | |
5438 | ||
e66ba1df | 5439 | For Org mode to recognize timestamps, they need to be in the specific |
c8d0cf5c | 5440 | format. All commands listed below produce timestamps in the correct |
4009494e GM |
5441 | format. |
5442 | ||
5443 | @table @kbd | |
afe98dfa | 5444 | @orgcmd{C-c .,org-time-stamp} |
c8d0cf5c CD |
5445 | Prompt for a date and insert a corresponding timestamp. When the cursor is |
5446 | at an existing timestamp in the buffer, the command is used to modify this | |
864c9740 CD |
5447 | timestamp instead of inserting a new one. When this command is used twice in |
5448 | succession, a time range is inserted. | |
4009494e | 5449 | @c |
afe98dfa | 5450 | @orgcmd{C-c !,org-time-stamp-inactive} |
c8d0cf5c | 5451 | Like @kbd{C-c .}, but insert an inactive timestamp that will not cause |
4009494e GM |
5452 | an agenda entry. |
5453 | @c | |
c8d0cf5c CD |
5454 | @kindex C-u C-c . |
5455 | @kindex C-u C-c ! | |
5456 | @item C-u C-c . | |
5457 | @itemx C-u C-c ! | |
5458 | @vindex org-time-stamp-rounding-minutes | |
5459 | Like @kbd{C-c .} and @kbd{C-c !}, but use the alternative format which | |
5460 | contains date and time. The default time can be rounded to multiples of 5 | |
5461 | minutes, see the option @code{org-time-stamp-rounding-minutes}. | |
5462 | @c | |
e66ba1df BG |
5463 | @orgkey{C-c C-c} |
5464 | Normalize timestamp, insert/fix day name if missing or wrong. | |
5465 | @c | |
afe98dfa | 5466 | @orgcmd{C-c <,org-date-from-calendar} |
c8d0cf5c | 5467 | Insert a timestamp corresponding to the cursor date in the Calendar. |
4009494e | 5468 | @c |
afe98dfa | 5469 | @orgcmd{C-c >,org-goto-calendar} |
4009494e | 5470 | Access the Emacs calendar for the current date. If there is a |
a7808fba | 5471 | timestamp in the current line, go to the corresponding date |
4009494e GM |
5472 | instead. |
5473 | @c | |
afe98dfa | 5474 | @orgcmd{C-c C-o,org-open-at-point} |
c8d0cf5c | 5475 | Access the agenda for the date given by the timestamp or -range at |
a7808fba | 5476 | point (@pxref{Weekly/daily agenda}). |
4009494e | 5477 | @c |
acedf35c | 5478 | @orgcmdkkcc{S-@key{left},S-@key{right},org-timestamp-down-day,org-timestamp-up-day} |
4009494e | 5479 | Change date at cursor by one day. These key bindings conflict with |
c8d0cf5c | 5480 | shift-selection and related modes (@pxref{Conflicts}). |
4009494e | 5481 | @c |
acedf35c | 5482 | @orgcmdkkcc{S-@key{up},S-@key{down},org-timestamp-up,org-timestamp-down-down} |
4009494e | 5483 | Change the item under the cursor in a timestamp. The cursor can be on a |
c8d0cf5c CD |
5484 | year, month, day, hour or minute. When the timestamp contains a time range |
5485 | like @samp{15:30-16:30}, modifying the first time will also shift the second, | |
5486 | shifting the time block with constant length. To change the length, modify | |
5487 | the second time. Note that if the cursor is in a headline and not at a | |
5488 | timestamp, these same keys modify the priority of an item. | |
ce57c2fe | 5489 | (@pxref{Priorities}). The key bindings also conflict with shift-selection and |
c8d0cf5c | 5490 | related modes (@pxref{Conflicts}). |
4009494e | 5491 | @c |
acedf35c | 5492 | @orgcmd{C-c C-y,org-evaluate-time-range} |
4009494e | 5493 | @cindex evaluate time range |
a7808fba CD |
5494 | Evaluate a time range by computing the difference between start and end. |
5495 | With a prefix argument, insert result after the time range (in a table: into | |
5496 | the following column). | |
4009494e GM |
5497 | @end table |
5498 | ||
5499 | ||
5500 | @menu | |
e66ba1df | 5501 | * The date/time prompt:: How Org mode helps you entering date and time |
c0468714 | 5502 | * Custom time format:: Making dates look different |
4009494e GM |
5503 | @end menu |
5504 | ||
5505 | @node The date/time prompt, Custom time format, Creating timestamps, Creating timestamps | |
5506 | @subsection The date/time prompt | |
5507 | @cindex date, reading in minibuffer | |
5508 | @cindex time, reading in minibuffer | |
5509 | ||
c8d0cf5c | 5510 | @vindex org-read-date-prefer-future |
e66ba1df | 5511 | When Org mode prompts for a date/time, the default is shown in default |
7006d207 CD |
5512 | date/time format, and the prompt therefore seems to ask for a specific |
5513 | format. But it will in fact accept any string containing some date and/or | |
5514 | time information, and it is really smart about interpreting your input. You | |
dbc28aaa | 5515 | can, for example, use @kbd{C-y} to paste a (possibly multi-line) string |
e66ba1df | 5516 | copied from an email message. Org mode will find whatever information is in |
7006d207 CD |
5517 | there and derive anything you have not specified from the @emph{default date |
5518 | and time}. The default is usually the current date and time, but when | |
5519 | modifying an existing timestamp, or when entering the second stamp of a | |
5520 | range, it is taken from the stamp in the buffer. When filling in | |
e66ba1df | 5521 | information, Org mode assumes that most of the time you will want to enter a |
7006d207 CD |
5522 | date in the future: if you omit the month/year and the given day/month is |
5523 | @i{before} today, it will assume that you mean a future date@footnote{See the | |
a351880d CD |
5524 | variable @code{org-read-date-prefer-future}. You may set that variable to |
5525 | the symbol @code{time} to even make a time before now shift the date to | |
5526 | tomorrow.}. If the date has been automatically shifted into the future, the | |
5527 | time prompt will show this with @samp{(=>F).} | |
dbc28aaa | 5528 | |
07450bee | 5529 | For example, let's assume that today is @b{June 13, 2006}. Here is how |
e66ba1df | 5530 | various inputs will be interpreted, the items filled in by Org mode are |
dbc28aaa CD |
5531 | in @b{bold}. |
5532 | ||
5533 | @example | |
ce57c2fe BG |
5534 | 3-2-5 @result{} 2003-02-05 |
5535 | 2/5/3 @result{} 2003-02-05 | |
5536 | 14 @result{} @b{2006}-@b{06}-14 | |
5537 | 12 @result{} @b{2006}-@b{07}-12 | |
5538 | 2/5 @result{} @b{2007}-02-05 | |
5539 | Fri @result{} nearest Friday (default date or later) | |
5540 | sep 15 @result{} @b{2006}-09-15 | |
5541 | feb 15 @result{} @b{2007}-02-15 | |
5542 | sep 12 9 @result{} 2009-09-12 | |
5543 | 12:45 @result{} @b{2006}-@b{06}-@b{13} 12:45 | |
5544 | 22 sept 0:34 @result{} @b{2006}-09-22 0:34 | |
5545 | w4 @result{} ISO week for of the current year @b{2006} | |
5546 | 2012 w4 fri @result{} Friday of ISO week 4 in 2012 | |
5547 | 2012-w04-5 @result{} Same as above | |
dbc28aaa CD |
5548 | @end example |
5549 | ||
5550 | Furthermore you can specify a relative date by giving, as the | |
5551 | @emph{first} thing in the input: a plus/minus sign, a number and a | |
c8d0cf5c | 5552 | letter ([dwmy]) to indicate change in days, weeks, months, or years. With a |
dbc28aaa CD |
5553 | single plus or minus, the date is always relative to today. With a |
5554 | double plus or minus, it is relative to the default date. If instead of | |
5555 | a single letter, you use the abbreviation of day name, the date will be | |
ce57c2fe | 5556 | the Nth such day, e.g.@: |
dbc28aaa CD |
5557 | |
5558 | @example | |
ce57c2fe BG |
5559 | +0 @result{} today |
5560 | . @result{} today | |
5561 | +4d @result{} four days from today | |
5562 | +4 @result{} same as above | |
5563 | +2w @result{} two weeks from today | |
5564 | ++5 @result{} five days from default date | |
5565 | +2tue @result{} second Tuesday from now. | |
4009494e GM |
5566 | @end example |
5567 | ||
c8d0cf5c CD |
5568 | @vindex parse-time-months |
5569 | @vindex parse-time-weekdays | |
4009494e GM |
5570 | The function understands English month and weekday abbreviations. If |
5571 | you want to use unabbreviated names and/or other languages, configure | |
5572 | the variables @code{parse-time-months} and @code{parse-time-weekdays}. | |
5573 | ||
ce57c2fe BG |
5574 | @vindex org-read-date-force-compatible-dates |
5575 | Not all dates can be represented in a given Emacs implementation. By default | |
5576 | Org mode forces dates into the compatibility range 1970--2037 which works on | |
5577 | all Emacs implementations. If you want to use dates outside of this range, | |
5578 | read the docstring of the variable | |
5579 | @code{org-read-date-force-compatible-dates}. | |
5580 | ||
afe98dfa | 5581 | You can specify a time range by giving start and end times or by giving a |
ce57c2fe BG |
5582 | start time and a duration (in HH:MM format). Use one or two dash(es) as the |
5583 | separator in the former case and use '+' as the separator in the latter | |
5584 | case, e.g.@: | |
afe98dfa CD |
5585 | |
5586 | @example | |
ce57c2fe BG |
5587 | 11am-1:15pm @result{} 11:00-13:15 |
5588 | 11am--1:15pm @result{} same as above | |
5589 | 11am+2:15 @result{} same as above | |
afe98dfa CD |
5590 | @end example |
5591 | ||
4009494e | 5592 | @cindex calendar, for selecting date |
c8d0cf5c | 5593 | @vindex org-popup-calendar-for-date-prompt |
4009494e GM |
5594 | Parallel to the minibuffer prompt, a calendar is popped up@footnote{If |
5595 | you don't need/want the calendar, configure the variable | |
5596 | @code{org-popup-calendar-for-date-prompt}.}. When you exit the date | |
5597 | prompt, either by clicking on a date in the calendar, or by pressing | |
5598 | @key{RET}, the date selected in the calendar will be combined with the | |
5599 | information entered at the prompt. You can control the calendar fully | |
5600 | from the minibuffer: | |
5601 | ||
4009494e | 5602 | @kindex < |
4009494e | 5603 | @kindex > |
86fbb8ca CD |
5604 | @kindex M-v |
5605 | @kindex C-v | |
4009494e | 5606 | @kindex mouse-1 |
4009494e | 5607 | @kindex S-@key{right} |
4009494e | 5608 | @kindex S-@key{left} |
4009494e | 5609 | @kindex S-@key{down} |
4009494e | 5610 | @kindex S-@key{up} |
4009494e | 5611 | @kindex M-S-@key{right} |
4009494e | 5612 | @kindex M-S-@key{left} |
4009494e | 5613 | @kindex @key{RET} |
dbc28aaa | 5614 | @example |
86fbb8ca | 5615 | @key{RET} @r{Choose date at cursor in calendar.} |
dbc28aaa CD |
5616 | mouse-1 @r{Select date by clicking on it.} |
5617 | S-@key{right}/@key{left} @r{One day forward/backward.} | |
5618 | S-@key{down}/@key{up} @r{One week forward/backward.} | |
5619 | M-S-@key{right}/@key{left} @r{One month forward/backward.} | |
86fbb8ca CD |
5620 | > / < @r{Scroll calendar forward/backward by one month.} |
5621 | M-v / C-v @r{Scroll calendar forward/backward by 3 months.} | |
dbc28aaa CD |
5622 | @end example |
5623 | ||
c8d0cf5c | 5624 | @vindex org-read-date-display-live |
a7808fba CD |
5625 | The actions of the date/time prompt may seem complex, but I assure you they |
5626 | will grow on you, and you will start getting annoyed by pretty much any other | |
5627 | way of entering a date/time out there. To help you understand what is going | |
5628 | on, the current interpretation of your input will be displayed live in the | |
5629 | minibuffer@footnote{If you find this distracting, turn the display of with | |
5630 | @code{org-read-date-display-live}.}. | |
4009494e GM |
5631 | |
5632 | @node Custom time format, , The date/time prompt, Creating timestamps | |
5633 | @subsection Custom time format | |
5634 | @cindex custom date/time format | |
5635 | @cindex time format, custom | |
5636 | @cindex date format, custom | |
5637 | ||
c8d0cf5c CD |
5638 | @vindex org-display-custom-times |
5639 | @vindex org-time-stamp-custom-formats | |
e66ba1df | 5640 | Org mode uses the standard ISO notation for dates and times as it is |
4009494e GM |
5641 | defined in ISO 8601. If you cannot get used to this and require another |
5642 | representation of date and time to keep you happy, you can get it by | |
5643 | customizing the variables @code{org-display-custom-times} and | |
5644 | @code{org-time-stamp-custom-formats}. | |
5645 | ||
5646 | @table @kbd | |
acedf35c | 5647 | @orgcmd{C-c C-x C-t,org-toggle-time-stamp-overlays} |
4009494e GM |
5648 | Toggle the display of custom formats for dates and times. |
5649 | @end table | |
5650 | ||
5651 | @noindent | |
e66ba1df | 5652 | Org mode needs the default format for scanning, so the custom date/time |
c8d0cf5c | 5653 | format does not @emph{replace} the default format---instead it is put |
4009494e GM |
5654 | @emph{over} the default format using text properties. This has the |
5655 | following consequences: | |
5656 | @itemize @bullet | |
28a16a1b | 5657 | @item |
c8d0cf5c | 5658 | You cannot place the cursor onto a timestamp anymore, only before or |
4009494e GM |
5659 | after. |
5660 | @item | |
5661 | The @kbd{S-@key{up}/@key{down}} keys can no longer be used to adjust | |
c8d0cf5c | 5662 | each component of a timestamp. If the cursor is at the beginning of |
4009494e GM |
5663 | the stamp, @kbd{S-@key{up}/@key{down}} will change the stamp by one day, |
5664 | just like @kbd{S-@key{left}/@key{right}}. At the end of the stamp, the | |
5665 | time will be changed by one minute. | |
5666 | @item | |
c8d0cf5c | 5667 | If the timestamp contains a range of clock times or a repeater, these |
acedf35c | 5668 | will not be overlaid, but remain in the buffer as they were. |
4009494e | 5669 | @item |
c8d0cf5c | 5670 | When you delete a timestamp character-by-character, it will only |
4009494e GM |
5671 | disappear from the buffer after @emph{all} (invisible) characters |
5672 | belonging to the ISO timestamp have been removed. | |
5673 | @item | |
c8d0cf5c | 5674 | If the custom timestamp format is longer than the default and you are |
4009494e GM |
5675 | using dates in tables, table alignment will be messed up. If the custom |
5676 | format is shorter, things do work as expected. | |
5677 | @end itemize | |
5678 | ||
5679 | ||
a7808fba CD |
5680 | @node Deadlines and scheduling, Clocking work time, Creating timestamps, Dates and Times |
5681 | @section Deadlines and scheduling | |
4009494e | 5682 | |
c8d0cf5c | 5683 | A timestamp may be preceded by special keywords to facilitate planning: |
4009494e GM |
5684 | |
5685 | @table @var | |
5686 | @item DEADLINE | |
5687 | @cindex DEADLINE keyword | |
dbc28aaa CD |
5688 | |
5689 | Meaning: the task (most likely a TODO item, though not necessarily) is supposed | |
5690 | to be finished on that date. | |
5691 | ||
c8d0cf5c | 5692 | @vindex org-deadline-warning-days |
dbc28aaa CD |
5693 | On the deadline date, the task will be listed in the agenda. In |
5694 | addition, the agenda for @emph{today} will carry a warning about the | |
5695 | approaching or missed deadline, starting | |
5696 | @code{org-deadline-warning-days} before the due date, and continuing | |
5697 | until the entry is marked DONE. An example: | |
4009494e GM |
5698 | |
5699 | @example | |
5700 | *** TODO write article about the Earth for the Guide | |
4009494e | 5701 | DEADLINE: <2004-02-29 Sun> |
801a68c8 | 5702 | The editor in charge is [[bbdb:Ford Prefect]] |
4009494e GM |
5703 | @end example |
5704 | ||
5705 | You can specify a different lead time for warnings for a specific | |
5706 | deadlines using the following syntax. Here is an example with a warning | |
5707 | period of 5 days @code{DEADLINE: <2004-02-29 Sun -5d>}. | |
5708 | ||
5709 | @item SCHEDULED | |
5710 | @cindex SCHEDULED keyword | |
dbc28aaa CD |
5711 | |
5712 | Meaning: you are planning to start working on that task on the given | |
5713 | date. | |
5714 | ||
c8d0cf5c | 5715 | @vindex org-agenda-skip-scheduled-if-done |
dbc28aaa CD |
5716 | The headline will be listed under the given date@footnote{It will still |
5717 | be listed on that date after it has been marked DONE. If you don't like | |
4009494e GM |
5718 | this, set the variable @code{org-agenda-skip-scheduled-if-done}.}. In |
5719 | addition, a reminder that the scheduled date has passed will be present | |
ce57c2fe | 5720 | in the compilation for @emph{today}, until the entry is marked DONE, i.e.@: |
acedf35c | 5721 | the task will automatically be forwarded until completed. |
4009494e GM |
5722 | |
5723 | @example | |
5724 | *** TODO Call Trillian for a date on New Years Eve. | |
5725 | SCHEDULED: <2004-12-25 Sat> | |
5726 | @end example | |
dbc28aaa CD |
5727 | |
5728 | @noindent | |
e66ba1df | 5729 | @b{Important:} Scheduling an item in Org mode should @i{not} be |
dbc28aaa CD |
5730 | understood in the same way that we understand @i{scheduling a meeting}. |
5731 | Setting a date for a meeting is just a simple appointment, you should | |
c8d0cf5c CD |
5732 | mark this entry with a simple plain timestamp, to get this item shown |
5733 | on the date where it applies. This is a frequent misunderstanding by | |
e66ba1df | 5734 | Org users. In Org mode, @i{scheduling} means setting a date when you |
dbc28aaa | 5735 | want to start working on an action item. |
4009494e GM |
5736 | @end table |
5737 | ||
c8d0cf5c | 5738 | You may use timestamps with repeaters in scheduling and deadline |
e66ba1df | 5739 | entries. Org mode will issue early and late warnings based on the |
c8d0cf5c | 5740 | assumption that the timestamp represents the @i{nearest instance} of |
dbc28aaa CD |
5741 | the repeater. However, the use of diary sexp entries like |
5742 | @c | |
ce57c2fe | 5743 | @code{<%%(org-float t 42)>} |
dbc28aaa | 5744 | @c |
e66ba1df | 5745 | in scheduling and deadline timestamps is limited. Org mode does not |
dbc28aaa CD |
5746 | know enough about the internals of each sexp function to issue early and |
5747 | late warnings. However, it will show the item on each day where the | |
5748 | sexp entry matches. | |
5749 | ||
4009494e | 5750 | @menu |
c0468714 GM |
5751 | * Inserting deadline/schedule:: Planning items |
5752 | * Repeated tasks:: Items that show up again and again | |
4009494e GM |
5753 | @end menu |
5754 | ||
5755 | @node Inserting deadline/schedule, Repeated tasks, Deadlines and scheduling, Deadlines and scheduling | |
a7808fba | 5756 | @subsection Inserting deadlines or schedules |
4009494e | 5757 | |
ce57c2fe BG |
5758 | The following commands allow you to quickly insert@footnote{The @samp{SCHEDULED} and |
5759 | @samp{DEADLINE} dates are inserted on the line right below the headline. Don't put | |
5760 | any text between this line and the headline.} a deadline or to schedule | |
4009494e GM |
5761 | an item: |
5762 | ||
5763 | @table @kbd | |
5764 | @c | |
acedf35c | 5765 | @orgcmd{C-c C-d,org-deadline} |
a351880d | 5766 | Insert @samp{DEADLINE} keyword along with a stamp. The insertion will happen |
ce57c2fe | 5767 | in the line directly following the headline. Any CLOSED timestamp will be |
91af3942 | 5768 | removed. When called with a prefix arg, an existing deadline will be removed |
ce57c2fe | 5769 | from the entry. Depending on the variable @code{org-log-redeadline}@footnote{with corresponding |
a351880d CD |
5770 | @code{#+STARTUP} keywords @code{logredeadline}, @code{lognoteredeadline}, |
5771 | and @code{nologredeadline}}, a note will be taken when changing an existing | |
5772 | deadline. | |
ce57c2fe | 5773 | |
acedf35c | 5774 | @orgcmd{C-c C-s,org-schedule} |
4009494e | 5775 | Insert @samp{SCHEDULED} keyword along with a stamp. The insertion will |
a351880d CD |
5776 | happen in the line directly following the headline. Any CLOSED timestamp |
5777 | will be removed. When called with a prefix argument, remove the scheduling | |
5778 | date from the entry. Depending on the variable | |
5779 | @code{org-log-reschedule}@footnote{with corresponding @code{#+STARTUP} | |
ce57c2fe BG |
5780 | keywords @code{logreschedule}, @code{lognotereschedule}, and |
5781 | @code{nologreschedule}}, a note will be taken when changing an existing | |
a351880d | 5782 | scheduling time. |
b349f79f | 5783 | @c |
acedf35c | 5784 | @orgcmd{C-c C-x C-k,org-mark-entry-for-agenda-action} |
b349f79f CD |
5785 | @kindex k a |
5786 | @kindex k s | |
b349f79f CD |
5787 | Mark the current entry for agenda action. After you have marked the entry |
5788 | like this, you can open the agenda or the calendar to find an appropriate | |
5789 | date. With the cursor on the selected date, press @kbd{k s} or @kbd{k d} to | |
5790 | schedule the marked item. | |
c8d0cf5c | 5791 | @c |
acedf35c | 5792 | @orgcmd{C-c / d,org-check-deadlines} |
c8d0cf5c | 5793 | @cindex sparse tree, for deadlines |
c8d0cf5c CD |
5794 | @vindex org-deadline-warning-days |
5795 | Create a sparse tree with all deadlines that are either past-due, or | |
5796 | which will become due within @code{org-deadline-warning-days}. | |
5797 | With @kbd{C-u} prefix, show all deadlines in the file. With a numeric | |
5798 | prefix, check that many days. For example, @kbd{C-1 C-c / d} shows | |
5799 | all deadlines due tomorrow. | |
5800 | @c | |
acedf35c | 5801 | @orgcmd{C-c / b,org-check-before-date} |
c8d0cf5c CD |
5802 | Sparse tree for deadlines and scheduled items before a given date. |
5803 | @c | |
acedf35c | 5804 | @orgcmd{C-c / a,org-check-after-date} |
c8d0cf5c | 5805 | Sparse tree for deadlines and scheduled items after a given date. |
4009494e GM |
5806 | @end table |
5807 | ||
ce57c2fe BG |
5808 | Note that @code{org-schedule} and @code{org-deadline} supports |
5809 | setting the date by indicating a relative time: e.g. +1d will set | |
5810 | the date to the next day after today, and --1w will set the date | |
5811 | to the previous week before any current timestamp. | |
5812 | ||
4009494e | 5813 | @node Repeated tasks, , Inserting deadline/schedule, Deadlines and scheduling |
a7808fba | 5814 | @subsection Repeated tasks |
c8d0cf5c CD |
5815 | @cindex tasks, repeated |
5816 | @cindex repeated tasks | |
4009494e | 5817 | |
e66ba1df | 5818 | Some tasks need to be repeated again and again. Org mode helps to |
28a16a1b | 5819 | organize such tasks using a so-called repeater in a DEADLINE, SCHEDULED, |
c8d0cf5c | 5820 | or plain timestamp. In the following example |
4009494e GM |
5821 | @example |
5822 | ** TODO Pay the rent | |
5823 | DEADLINE: <2005-10-01 Sat +1m> | |
5824 | @end example | |
c8d0cf5c CD |
5825 | @noindent |
5826 | the @code{+1m} is a repeater; the intended interpretation is that the task | |
5827 | has a deadline on <2005-10-01> and repeats itself every (one) month starting | |
5828 | from that time. If you need both a repeater and a special warning period in | |
5829 | a deadline entry, the repeater should come first and the warning period last: | |
5830 | @code{DEADLINE: <2005-10-01 Sat +1m -3d>}. | |
4009494e | 5831 | |
86fbb8ca CD |
5832 | @vindex org-todo-repeat-to-state |
5833 | Deadlines and scheduled items produce entries in the agenda when they are | |
5834 | over-due, so it is important to be able to mark such an entry as completed | |
5835 | once you have done so. When you mark a DEADLINE or a SCHEDULE with the TODO | |
5836 | keyword DONE, it will no longer produce entries in the agenda. The problem | |
5837 | with this is, however, that then also the @emph{next} instance of the | |
e66ba1df | 5838 | repeated entry will not be active. Org mode deals with this in the following |
86fbb8ca CD |
5839 | way: When you try to mark such an entry DONE (using @kbd{C-c C-t}), it will |
5840 | shift the base date of the repeating timestamp by the repeater interval, and | |
5841 | immediately set the entry state back to TODO@footnote{In fact, the target | |
5842 | state is taken from, in this sequence, the @code{REPEAT_TO_STATE} property or | |
5843 | the variable @code{org-todo-repeat-to-state}. If neither of these is | |
5844 | specified, the target state defaults to the first state of the TODO state | |
5845 | sequence.}. In the example above, setting the state to DONE would actually | |
5846 | switch the date like this: | |
4009494e GM |
5847 | |
5848 | @example | |
5849 | ** TODO Pay the rent | |
5850 | DEADLINE: <2005-11-01 Tue +1m> | |
5851 | @end example | |
5852 | ||
c8d0cf5c | 5853 | @vindex org-log-repeat |
a7808fba CD |
5854 | A timestamp@footnote{You can change this using the option |
5855 | @code{org-log-repeat}, or the @code{#+STARTUP} options @code{logrepeat}, | |
5856 | @code{lognoterepeat}, and @code{nologrepeat}. With @code{lognoterepeat}, you | |
a50253cc | 5857 | will also be prompted for a note.} will be added under the deadline, to keep |
a7808fba | 5858 | a record that you actually acted on the previous instance of this deadline. |
4009494e GM |
5859 | |
5860 | As a consequence of shifting the base date, this entry will no longer be | |
5861 | visible in the agenda when checking past dates, but all future instances | |
5862 | will be visible. | |
5863 | ||
28a16a1b | 5864 | With the @samp{+1m} cookie, the date shift will always be exactly one |
c8d0cf5c | 5865 | month. So if you have not paid the rent for three months, marking this |
28a16a1b CD |
5866 | entry DONE will still keep it as an overdue deadline. Depending on the |
5867 | task, this may not be the best way to handle it. For example, if you | |
acedf35c | 5868 | forgot to call your father for 3 weeks, it does not make sense to call |
a7808fba | 5869 | him 3 times in a single day to make up for it. Finally, there are tasks |
28a16a1b | 5870 | like changing batteries which should always repeat a certain time |
e66ba1df | 5871 | @i{after} the last time you did it. For these tasks, Org mode has |
acedf35c | 5872 | special repeaters @samp{++} and @samp{.+}. For example: |
28a16a1b CD |
5873 | |
5874 | @example | |
5875 | ** TODO Call Father | |
5876 | DEADLINE: <2008-02-10 Sun ++1w> | |
5877 | Marking this DONE will shift the date by at least one week, | |
5878 | but also by as many weeks as it takes to get this date into | |
5879 | the future. However, it stays on a Sunday, even if you called | |
5880 | and marked it done on Saturday. | |
5881 | ** TODO Check the batteries in the smoke detectors | |
5882 | DEADLINE: <2005-11-01 Tue .+1m> | |
5883 | Marking this DONE will shift the date to one month after | |
5884 | today. | |
5885 | @end example | |
5886 | ||
4009494e | 5887 | You may have both scheduling and deadline information for a specific |
c8d0cf5c CD |
5888 | task---just make sure that the repeater intervals on both are the same. |
5889 | ||
5890 | An alternative to using a repeater is to create a number of copies of a task | |
5891 | subtree, with dates shifted in each copy. The command @kbd{C-c C-x c} was | |
5892 | created for this purpose, it is described in @ref{Structure editing}. | |
5893 | ||
4009494e | 5894 | |
acedf35c | 5895 | @node Clocking work time, Effort estimates, Deadlines and scheduling, Dates and Times |
dbc28aaa | 5896 | @section Clocking work time |
acedf35c CD |
5897 | @cindex clocking time |
5898 | @cindex time clocking | |
4009494e | 5899 | |
e66ba1df | 5900 | Org mode allows you to clock the time you spend on specific tasks in a |
4009494e GM |
5901 | project. When you start working on an item, you can start the clock. |
5902 | When you stop working on that task, or when you mark the task done, the | |
5903 | clock is stopped and the corresponding time interval is recorded. It | |
a351880d CD |
5904 | also computes the total time spent on each subtree of a project. And it |
5905 | remembers a history or tasks recently clocked, to that you can jump quickly | |
5906 | between a number of tasks absorbing your time. | |
c8d0cf5c | 5907 | |
a351880d | 5908 | To save the clock history across Emacs sessions, use |
c8d0cf5c | 5909 | @lisp |
a351880d | 5910 | (setq org-clock-persist 'history) |
c8d0cf5c CD |
5911 | (org-clock-persistence-insinuate) |
5912 | @end lisp | |
a351880d CD |
5913 | When you clock into a new task after resuming Emacs, the incomplete |
5914 | clock@footnote{To resume the clock under the assumption that you have worked | |
5915 | on this task while outside Emacs, use @code{(setq org-clock-persist t)}.} | |
5916 | will be found (@pxref{Resolving idle time}) and you will be prompted about | |
5917 | what to do with it. | |
c8d0cf5c | 5918 | |
acedf35c CD |
5919 | @menu |
5920 | * Clocking commands:: Starting and stopping a clock | |
5921 | * The clock table:: Detailed reports | |
5922 | * Resolving idle time:: Resolving time when you've been idle | |
5923 | @end menu | |
5924 | ||
5925 | @node Clocking commands, The clock table, Clocking work time, Clocking work time | |
5926 | @subsection Clocking commands | |
5927 | ||
4009494e | 5928 | @table @kbd |
acedf35c | 5929 | @orgcmd{C-c C-x C-i,org-clock-in} |
c8d0cf5c | 5930 | @vindex org-clock-into-drawer |
ce57c2fe | 5931 | @cindex property, LOG_INTO_DRAWER |
4009494e | 5932 | Start the clock on the current item (clock-in). This inserts the CLOCK |
dbc28aaa CD |
5933 | keyword together with a timestamp. If this is not the first clocking of |
5934 | this item, the multiple CLOCK lines will be wrapped into a | |
c8d0cf5c | 5935 | @code{:LOGBOOK:} drawer (see also the variable |
ce57c2fe BG |
5936 | @code{org-clock-into-drawer}). You can also overrule |
5937 | the setting of this variable for a subtree by setting a | |
5938 | @code{CLOCK_INTO_DRAWER} or @code{LOG_INTO_DRAWER} property. | |
5939 | When called with a @kbd{C-u} prefix argument, | |
a7808fba CD |
5940 | select the task from a list of recently clocked tasks. With two @kbd{C-u |
5941 | C-u} prefixes, clock into the task at point and mark it as the default task. | |
5942 | The default task will always be available when selecting a clocking task, | |
c8d0cf5c CD |
5943 | with letter @kbd{d}.@* |
5944 | @cindex property: CLOCK_MODELINE_TOTAL | |
5945 | @cindex property: LAST_REPEAT | |
5946 | @vindex org-clock-modeline-total | |
5947 | While the clock is running, the current clocking time is shown in the mode | |
5948 | line, along with the title of the task. The clock time shown will be all | |
5949 | time ever clocked for this task and its children. If the task has an effort | |
5950 | estimate (@pxref{Effort estimates}), the mode line displays the current | |
5951 | clocking time against it@footnote{To add an effort estimate ``on the fly'', | |
5952 | hook a function doing this to @code{org-clock-in-prepare-hook}.} If the task | |
5953 | is a repeating one (@pxref{Repeated tasks}), only the time since the last | |
5954 | reset of the task @footnote{as recorded by the @code{LAST_REPEAT} property} | |
5955 | will be shown. More control over what time is shown can be exercised with | |
5956 | the @code{CLOCK_MODELINE_TOTAL} property. It may have the values | |
5957 | @code{current} to show only the current clocking instance, @code{today} to | |
5958 | show all time clocked on this tasks today (see also the variable | |
5959 | @code{org-extend-today-until}), @code{all} to include all time, or | |
5960 | @code{auto} which is the default@footnote{See also the variable | |
5961 | @code{org-clock-modeline-total}.}.@* Clicking with @kbd{mouse-1} onto the | |
5962 | mode line entry will pop up a menu with clocking options. | |
acedf35c CD |
5963 | @c |
5964 | @orgcmd{C-c C-x C-o,org-clock-out} | |
c8d0cf5c | 5965 | @vindex org-log-note-clock-out |
a20d3598 | 5966 | Stop the clock (clock-out). This inserts another timestamp at the same |
4009494e GM |
5967 | location where the clock was last started. It also directly computes |
5968 | the resulting time in inserts it after the time range as @samp{=> | |
28a16a1b CD |
5969 | HH:MM}. See the variable @code{org-log-note-clock-out} for the |
5970 | possibility to record an additional note together with the clock-out | |
c8d0cf5c | 5971 | timestamp@footnote{The corresponding in-buffer setting is: |
28a16a1b | 5972 | @code{#+STARTUP: lognoteclock-out}}. |
acedf35c | 5973 | @orgcmd{C-c C-x C-e,org-clock-modify-effort-estimate} |
c8d0cf5c | 5974 | Update the effort estimate for the current clock task. |
4009494e | 5975 | @kindex C-c C-y |
c8d0cf5c | 5976 | @kindex C-c C-c |
acedf35c | 5977 | @orgcmdkkc{C-c C-c,C-c C-y,org-evaluate-time-range} |
c8d0cf5c CD |
5978 | Recompute the time interval after changing one of the timestamps. This |
5979 | is only necessary if you edit the timestamps directly. If you change | |
4009494e | 5980 | them with @kbd{S-@key{cursor}} keys, the update is automatic. |
ce57c2fe BG |
5981 | @orgcmd{C-S-@key{up/down},org-clock-timestamps-up/down} |
5982 | On @code{CLOCK} log lines, increase/decrease both timestamps at the same | |
5983 | time so that duration keeps the same. | |
acedf35c | 5984 | @orgcmd{C-c C-t,org-todo} |
4009494e GM |
5985 | Changing the TODO state of an item to DONE automatically stops the clock |
5986 | if it is running in this same item. | |
acedf35c | 5987 | @orgcmd{C-c C-x C-x,org-clock-cancel} |
4009494e GM |
5988 | Cancel the current clock. This is useful if a clock was started by |
5989 | mistake, or if you ended up working on something else. | |
acedf35c | 5990 | @orgcmd{C-c C-x C-j,org-clock-goto} |
afe98dfa CD |
5991 | Jump to the headline of the currently clocked in task. With a @kbd{C-u} |
5992 | prefix arg, select the target task from a list of recently clocked tasks. | |
acedf35c | 5993 | @orgcmd{C-c C-x C-d,org-clock-display} |
c8d0cf5c | 5994 | @vindex org-remove-highlights-with-change |
ce57c2fe BG |
5995 | Display time summaries for each subtree in the current buffer. This puts |
5996 | overlays at the end of each headline, showing the total time recorded under | |
5997 | that heading, including the time of any subheadings. You can use visibility | |
5998 | cycling to study the tree, but the overlays disappear when you change the | |
5999 | buffer (see variable @code{org-remove-highlights-with-change}) or press | |
6000 | @kbd{C-c C-c}. | |
acedf35c CD |
6001 | @end table |
6002 | ||
6003 | The @kbd{l} key may be used in the timeline (@pxref{Timeline}) and in | |
6004 | the agenda (@pxref{Weekly/daily agenda}) to show which tasks have been | |
6005 | worked on or closed during a day. | |
6006 | ||
6007 | @node The clock table, Resolving idle time, Clocking commands, Clocking work time | |
6008 | @subsection The clock table | |
6009 | @cindex clocktable, dynamic block | |
6010 | @cindex report, of clocked time | |
6011 | ||
6012 | Org mode can produce quite complex reports based on the time clocking | |
6013 | information. Such a report is called a @emph{clock table}, because it is | |
6014 | formatted as one or several Org tables. | |
6015 | ||
6016 | @table @kbd | |
6017 | @orgcmd{C-c C-x C-r,org-clock-report} | |
4009494e | 6018 | Insert a dynamic block (@pxref{Dynamic blocks}) containing a clock |
e66ba1df | 6019 | report as an Org mode table into the current file. When the cursor is |
dbc28aaa CD |
6020 | at an existing clock table, just update it. When called with a prefix |
6021 | argument, jump to the first clock report in the current document and | |
e66ba1df BG |
6022 | update it. The clock table always includes also trees with |
6023 | @code{:ARCHIVE:} tag. | |
acedf35c CD |
6024 | @orgcmdkkc{C-c C-c,C-c C-x C-u,org-dblock-update} |
6025 | Update dynamic block at point. The cursor needs to be in the | |
6026 | @code{#+BEGIN} line of the dynamic block. | |
6027 | @orgkey{C-u C-c C-x C-u} | |
6028 | Update all dynamic blocks (@pxref{Dynamic blocks}). This is useful if | |
6029 | you have several clock table blocks in a buffer. | |
6030 | @orgcmdkxkc{S-@key{left},S-@key{right},org-clocktable-try-shift} | |
6031 | Shift the current @code{:block} interval and update the table. The cursor | |
6032 | needs to be in the @code{#+BEGIN: clocktable} line for this command. If | |
6033 | @code{:block} is @code{today}, it will be shifted to @code{today-1} etc. | |
6034 | @end table | |
6035 | ||
6036 | ||
6037 | Here is an example of the frame for a clock table as it is inserted into the | |
6038 | buffer with the @kbd{C-c C-x C-r} command: | |
6039 | ||
c8d0cf5c | 6040 | @cindex #+BEGIN, clocktable |
4009494e | 6041 | @example |
dbc28aaa | 6042 | #+BEGIN: clocktable :maxlevel 2 :emphasize nil :scope file |
4009494e GM |
6043 | #+END: clocktable |
6044 | @end example | |
6045 | @noindent | |
acedf35c CD |
6046 | @vindex org-clocktable-defaults |
6047 | The @samp{BEGIN} line and specify a number of options to define the scope, | |
6048 | structure, and formatting of the report. Defaults for all these options can | |
6049 | be configured in the variable @code{org-clocktable-defaults}. | |
6050 | ||
6051 | @noindent First there are options that determine which clock entries are to | |
6052 | be selected: | |
4009494e | 6053 | @example |
dbc28aaa | 6054 | :maxlevel @r{Maximum level depth to which times are listed in the table.} |
acedf35c | 6055 | @r{Clocks at deeper levels will be summed into the upper level.} |
dbc28aaa CD |
6056 | :scope @r{The scope to consider. This can be any of the following:} |
6057 | nil @r{the current buffer or narrowed region} | |
6058 | file @r{the full current buffer} | |
6059 | subtree @r{the subtree where the clocktable is located} | |
c8d0cf5c | 6060 | tree@var{N} @r{the surrounding level @var{N} tree, for example @code{tree3}} |
dbc28aaa CD |
6061 | tree @r{the surrounding level 1 tree} |
6062 | agenda @r{all agenda files} | |
6063 | ("file"..) @r{scan these files} | |
a7808fba CD |
6064 | file-with-archives @r{current file and its archives} |
6065 | agenda-with-archives @r{all agenda files, including archives} | |
6066 | :block @r{The time block to consider. This block is specified either} | |
6067 | @r{absolute, or relative to the current time and may be any of} | |
6068 | @r{these formats:} | |
6069 | 2007-12-31 @r{New year eve 2007} | |
6070 | 2007-12 @r{December 2007} | |
6071 | 2007-W50 @r{ISO-week 50 in 2007} | |
acedf35c | 6072 | 2007-Q2 @r{2nd quarter in 2007} |
a7808fba | 6073 | 2007 @r{the year 2007} |
c8d0cf5c CD |
6074 | today, yesterday, today-@var{N} @r{a relative day} |
6075 | thisweek, lastweek, thisweek-@var{N} @r{a relative week} | |
6076 | thismonth, lastmonth, thismonth-@var{N} @r{a relative month} | |
6077 | thisyear, lastyear, thisyear-@var{N} @r{a relative year} | |
a7808fba | 6078 | @r{Use @kbd{S-@key{left}/@key{right}} keys to shift the time interval.} |
c8d0cf5c CD |
6079 | :tstart @r{A time string specifying when to start considering times.} |
6080 | :tend @r{A time string specifying when to stop considering times.} | |
a7808fba CD |
6081 | :step @r{@code{week} or @code{day}, to split the table into chunks.} |
6082 | @r{To use this, @code{:block} or @code{:tstart}, @code{:tend} are needed.} | |
acedf35c CD |
6083 | :stepskip0 @r{Do not show steps that have zero time.} |
6084 | :fileskip0 @r{Do not show table sections from files which did not contribute.} | |
ce57c2fe BG |
6085 | :tags @r{A tags match to select entries that should contribute. See} |
6086 | @r{@ref{Matching tags and properties} for the match syntax.} | |
acedf35c CD |
6087 | @end example |
6088 | ||
6089 | Then there are options which determine the formatting of the table. There | |
6090 | options are interpreted by the function @code{org-clocktable-write-default}, | |
6091 | but you can specify your own function using the @code{:formatter} parameter. | |
6092 | @example | |
6093 | :emphasize @r{When @code{t}, emphasize level one and level two items.} | |
ce57c2fe | 6094 | :lang @r{Language@footnote{Language terms can be set through the variable @code{org-clock-clocktable-language-setup}.} to use for descriptive cells like "Task".} |
c8d0cf5c | 6095 | :link @r{Link the item headlines in the table to their origins.} |
acedf35c CD |
6096 | :narrow @r{An integer to limit the width of the headline column in} |
6097 | @r{the org table. If you write it like @samp{50!}, then the} | |
6098 | @r{headline will also be shortened in export.} | |
6099 | :indent @r{Indent each headline field according to its level.} | |
6100 | :tcolumns @r{Number of columns to be used for times. If this is smaller} | |
6101 | @r{than @code{:maxlevel}, lower levels will be lumped into one column.} | |
6102 | :level @r{Should a level number column be included?} | |
6103 | :compact @r{Abbreviation for @code{:level nil :indent t :narrow 40! :tcolumns 1}} | |
6104 | @r{All are overwritten except if there is an explicit @code{:narrow}} | |
6105 | :timestamp @r{A timestamp for the entry, when available. Look for SCHEDULED,} | |
6106 | @r{DEADLINE, TIMESTAMP and TIMESTAMP_IA, in this order.} | |
ce57c2fe BG |
6107 | :properties @r{List of properties that should be shown in the table. Each} |
6108 | @r{property will get its own column.} | |
6109 | :inherit-props @r{When this flag is @code{t}, the values for @code{:properties} will be inherited.} | |
e45e3595 | 6110 | :formula @r{Content of a @code{#+TBLFM} line to be added and evaluated.} |
c8d0cf5c | 6111 | @r{As a special case, @samp{:formula %} adds a column with % time.} |
acedf35c | 6112 | @r{If you do not specify a formula here, any existing formula} |
e45e3595 | 6113 | @r{below the clock table will survive updates and be evaluated.} |
acedf35c | 6114 | :formatter @r{A function to format clock data and insert it into the buffer.} |
4009494e | 6115 | @end example |
c8d0cf5c | 6116 | To get a clock summary of the current level 1 tree, for the current |
dbc28aaa | 6117 | day, you could write |
4009494e | 6118 | @example |
a7808fba | 6119 | #+BEGIN: clocktable :maxlevel 2 :block today :scope tree1 :link t |
4009494e GM |
6120 | #+END: clocktable |
6121 | @end example | |
c8d0cf5c | 6122 | @noindent |
4009494e | 6123 | and to use a specific time range you could write@footnote{Note that all |
c8d0cf5c CD |
6124 | parameters must be specified in a single line---the line is broken here |
6125 | only to fit it into the manual.} | |
4009494e | 6126 | @example |
28a16a1b | 6127 | #+BEGIN: clocktable :tstart "<2006-08-10 Thu 10:00>" |
4009494e | 6128 | :tend "<2006-08-10 Thu 12:00>" |
4009494e GM |
6129 | #+END: clocktable |
6130 | @end example | |
e45e3595 CD |
6131 | A summary of the current subtree with % times would be |
6132 | @example | |
6133 | #+BEGIN: clocktable :scope subtree :link t :formula % | |
6134 | #+END: clocktable | |
6135 | @end example | |
acedf35c CD |
6136 | A horizontally compact representation of everything clocked during last week |
6137 | would be | |
6138 | @example | |
6139 | #+BEGIN: clocktable :scope agenda :block lastweek :compact t | |
6140 | #+END: clocktable | |
6141 | @end example | |
4009494e | 6142 | |
acedf35c CD |
6143 | @node Resolving idle time, , The clock table, Clocking work time |
6144 | @subsection Resolving idle time | |
a351880d CD |
6145 | @cindex resolve idle time |
6146 | ||
6147 | @cindex idle, resolve, dangling | |
6148 | If you clock in on a work item, and then walk away from your | |
6149 | computer---perhaps to take a phone call---you often need to ``resolve'' the | |
6150 | time you were away by either subtracting it from the current clock, or | |
6151 | applying it to another one. | |
6152 | ||
6153 | @vindex org-clock-idle-time | |
6154 | By customizing the variable @code{org-clock-idle-time} to some integer, such | |
6155 | as 10 or 15, Emacs can alert you when you get back to your computer after | |
6156 | being idle for that many minutes@footnote{On computers using Mac OS X, | |
153ae947 | 6157 | idleness is based on actual user idleness, not just Emacs' idle time. For |
a351880d CD |
6158 | X11, you can install a utility program @file{x11idle.c}, available in the |
6159 | UTILITIES directory of the Org git distribution, to get the same general | |
6160 | treatment of idleness. On other systems, idle time refers to Emacs idle time | |
6161 | only.}, and ask what you want to do with the idle time. There will be a | |
6162 | question waiting for you when you get back, indicating how much idle time has | |
6163 | passed (constantly updated with the current amount), as well as a set of | |
6164 | choices to correct the discrepancy: | |
6165 | ||
6166 | @table @kbd | |
6167 | @item k | |
6168 | To keep some or all of the minutes and stay clocked in, press @kbd{k}. Org | |
6169 | will ask how many of the minutes to keep. Press @key{RET} to keep them all, | |
6170 | effectively changing nothing, or enter a number to keep that many minutes. | |
6171 | @item K | |
6172 | If you use the shift key and press @kbd{K}, it will keep however many minutes | |
6173 | you request and then immediately clock out of that task. If you keep all of | |
6174 | the minutes, this is the same as just clocking out of the current task. | |
6175 | @item s | |
6176 | To keep none of the minutes, use @kbd{s} to subtract all the away time from | |
6177 | the clock, and then check back in from the moment you returned. | |
6178 | @item S | |
6179 | To keep none of the minutes and just clock out at the start of the away time, | |
6180 | use the shift key and press @kbd{S}. Remember that using shift will always | |
6181 | leave you clocked out, no matter which option you choose. | |
6182 | @item C | |
6183 | To cancel the clock altogether, use @kbd{C}. Note that if instead of | |
86fbb8ca CD |
6184 | canceling you subtract the away time, and the resulting clock amount is less |
6185 | than a minute, the clock will still be canceled rather than clutter up the | |
a351880d CD |
6186 | log with an empty entry. |
6187 | @end table | |
6188 | ||
6189 | What if you subtracted those away minutes from the current clock, and now | |
6190 | want to apply them to a new clock? Simply clock in to any task immediately | |
6191 | after the subtraction. Org will notice that you have subtracted time ``on | |
6192 | the books'', so to speak, and will ask if you want to apply those minutes to | |
6193 | the next task you clock in on. | |
6194 | ||
6195 | There is one other instance when this clock resolution magic occurs. Say you | |
6196 | were clocked in and hacking away, and suddenly your cat chased a mouse who | |
6197 | scared a hamster that crashed into your UPS's power button! You suddenly | |
6198 | lose all your buffers, but thanks to auto-save you still have your recent Org | |
6199 | mode changes, including your last clock in. | |
6200 | ||
6201 | If you restart Emacs and clock into any task, Org will notice that you have a | |
6202 | dangling clock which was never clocked out from your last session. Using | |
6203 | that clock's starting time as the beginning of the unaccounted-for period, | |
6204 | Org will ask how you want to resolve that time. The logic and behavior is | |
ce57c2fe | 6205 | identical to dealing with away time due to idleness; it is just happening due |
a351880d CD |
6206 | to a recovery event rather than a set amount of idle time. |
6207 | ||
6208 | You can also check all the files visited by your Org agenda for dangling | |
6209 | clocks at any time using @kbd{M-x org-resolve-clocks}. | |
6210 | ||
acedf35c | 6211 | @node Effort estimates, Relative timer, Clocking work time, Dates and Times |
a7808fba | 6212 | @section Effort estimates |
96c8522a | 6213 | @cindex effort estimates |
a7808fba | 6214 | |
c8d0cf5c CD |
6215 | @cindex property, Effort |
6216 | @vindex org-effort-property | |
a7808fba CD |
6217 | If you want to plan your work in a very detailed way, or if you need to |
6218 | produce offers with quotations of the estimated work effort, you may want to | |
6219 | assign effort estimates to entries. If you are also clocking your work, you | |
6220 | may later want to compare the planned effort with the actual working time, a | |
6221 | great way to improve planning estimates. Effort estimates are stored in a | |
6222 | special property @samp{Effort}@footnote{You may change the property being | |
6eb02347 CD |
6223 | used with the variable @code{org-effort-property}.}. You can set the effort |
6224 | for an entry with the following commands: | |
6225 | ||
6226 | @table @kbd | |
acedf35c | 6227 | @orgcmd{C-c C-x e,org-set-effort} |
6eb02347 | 6228 | Set the effort estimate for the current entry. With a numeric prefix |
acedf35c | 6229 | argument, set it to the Nth allowed value (see below). This command is also |
6eb02347 | 6230 | accessible from the agenda with the @kbd{e} key. |
acedf35c | 6231 | @orgcmd{C-c C-x C-e,org-clock-modify-effort-estimate} |
6eb02347 CD |
6232 | Modify the effort estimate of the item currently being clocked. |
6233 | @end table | |
6234 | ||
6235 | Clearly the best way to work with effort estimates is through column view | |
6236 | (@pxref{Column view}). You should start by setting up discrete values for | |
6237 | effort estimates, and a @code{COLUMNS} format that displays these values | |
6238 | together with clock sums (if you want to clock your time). For a specific | |
6239 | buffer you can use | |
a7808fba CD |
6240 | |
6241 | @example | |
ce57c2fe | 6242 | #+PROPERTY: Effort_ALL 0 0:10 0:30 1:00 2:00 3:00 4:00 5:00 6:00 7:00 |
a7808fba CD |
6243 | #+COLUMNS: %40ITEM(Task) %17Effort(Estimated Effort)@{:@} %CLOCKSUM |
6244 | @end example | |
6245 | ||
6246 | @noindent | |
c8d0cf5c CD |
6247 | @vindex org-global-properties |
6248 | @vindex org-columns-default-format | |
71d35b24 CD |
6249 | or, even better, you can set up these values globally by customizing the |
6250 | variables @code{org-global-properties} and @code{org-columns-default-format}. | |
6251 | In particular if you want to use this setup also in the agenda, a global | |
6252 | setup may be advised. | |
a7808fba CD |
6253 | |
6254 | The way to assign estimates to individual items is then to switch to column | |
6255 | mode, and to use @kbd{S-@key{right}} and @kbd{S-@key{left}} to change the | |
6256 | value. The values you enter will immediately be summed up in the hierarchy. | |
6257 | In the column next to it, any clocked time will be displayed. | |
6258 | ||
c8d0cf5c | 6259 | @vindex org-agenda-columns-add-appointments-to-effort-sum |
a7808fba CD |
6260 | If you switch to column view in the daily/weekly agenda, the effort column |
6261 | will summarize the estimated work effort for each day@footnote{Please note | |
6262 | the pitfalls of summing hierarchical data in a flat list (@pxref{Agenda | |
b349f79f | 6263 | column view}).}, and you can use this to find space in your schedule. To get |
a7808fba CD |
6264 | an overview of the entire part of the day that is committed, you can set the |
6265 | option @code{org-agenda-columns-add-appointments-to-effort-sum}. The | |
6266 | appointments on a day that take place over a specified time interval will | |
6267 | then also be added to the load estimate of the day. | |
6268 | ||
71d35b24 CD |
6269 | Effort estimates can be used in secondary agenda filtering that is triggered |
6270 | with the @kbd{/} key in the agenda (@pxref{Agenda commands}). If you have | |
6271 | these estimates defined consistently, two or three key presses will narrow | |
6272 | down the list to stuff that fits into an available time slot. | |
864c9740 | 6273 | |
afe98dfa | 6274 | @node Relative timer, Countdown timer, Effort estimates, Dates and Times |
96c8522a CD |
6275 | @section Taking notes with a relative timer |
6276 | @cindex relative timer | |
6277 | ||
6278 | When taking notes during, for example, a meeting or a video viewing, it can | |
6279 | be useful to have access to times relative to a starting time. Org provides | |
6280 | such a relative timer and make it easy to create timed notes. | |
6281 | ||
6282 | @table @kbd | |
acedf35c | 6283 | @orgcmd{C-c C-x .,org-timer} |
96c8522a CD |
6284 | Insert a relative time into the buffer. The first time you use this, the |
6285 | timer will be started. When called with a prefix argument, the timer is | |
6286 | restarted. | |
acedf35c | 6287 | @orgcmd{C-c C-x -,org-timer-item} |
96c8522a CD |
6288 | Insert a description list item with the current relative time. With a prefix |
6289 | argument, first reset the timer to 0. | |
acedf35c | 6290 | @orgcmd{M-@key{RET},org-insert-heading} |
377952e0 | 6291 | Once the timer list is started, you can also use @kbd{M-@key{RET}} to insert |
96c8522a | 6292 | new timer items. |
acedf35c | 6293 | @c for key sequences with a comma, command name macros fail :( |
55e0839d CD |
6294 | @kindex C-c C-x , |
6295 | @item C-c C-x , | |
acedf35c CD |
6296 | Pause the timer, or continue it if it is already paused |
6297 | (@command{org-timer-pause-or-continue}). | |
c8d0cf5c | 6298 | @c removed the sentence because it is redundant to the following item |
55e0839d CD |
6299 | @kindex C-u C-c C-x , |
6300 | @item C-u C-c C-x , | |
6301 | Stop the timer. After this, you can only start a new timer, not continue the | |
6302 | old one. This command also removes the timer from the mode line. | |
acedf35c | 6303 | @orgcmd{C-c C-x 0,org-timer-start} |
96c8522a CD |
6304 | Reset the timer without inserting anything into the buffer. By default, the |
6305 | timer is reset to 0. When called with a @kbd{C-u} prefix, reset the timer to | |
6306 | specific starting offset. The user is prompted for the offset, with a | |
6307 | default taken from a timer string at point, if any, So this can be used to | |
6308 | restart taking notes after a break in the process. When called with a double | |
86fbb8ca | 6309 | prefix argument @kbd{C-u C-u}, change all timer strings in the active region |
96c8522a CD |
6310 | by a certain amount. This can be used to fix timer strings if the timer was |
6311 | not started at exactly the right moment. | |
6312 | @end table | |
6313 | ||
afe98dfa CD |
6314 | @node Countdown timer, , Relative timer, Dates and Times |
6315 | @section Countdown timer | |
6316 | @cindex Countdown timer | |
6317 | @kindex C-c C-x ; | |
6318 | @kindex ; | |
6319 | ||
e66ba1df | 6320 | Calling @code{org-timer-set-timer} from an Org mode buffer runs a countdown |
27e428e7 | 6321 | timer. Use @kbd{;} from agenda buffers, @key{C-c C-x ;} everywhere else. |
afe98dfa CD |
6322 | |
6323 | @code{org-timer-set-timer} prompts the user for a duration and displays a | |
6324 | countdown timer in the modeline. @code{org-timer-default-timer} sets the | |
6325 | default countdown value. Giving a prefix numeric argument overrides this | |
6326 | default value. | |
6327 | ||
a351880d CD |
6328 | @node Capture - Refile - Archive, Agenda Views, Dates and Times, Top |
6329 | @chapter Capture - Refile - Archive | |
864c9740 CD |
6330 | @cindex capture |
6331 | ||
6332 | An important part of any organization system is the ability to quickly | |
6333 | capture new ideas and tasks, and to associate reference material with them. | |
86fbb8ca | 6334 | Org does this using a process called @i{capture}. It also can store files |
a351880d CD |
6335 | related to a task (@i{attachments}) in a special directory. Once in the |
6336 | system, tasks and projects need to be moved around. Moving completed project | |
6337 | trees to an archive file keeps the system compact and fast. | |
864c9740 CD |
6338 | |
6339 | @menu | |
c0468714 GM |
6340 | * Capture:: Capturing new stuff |
6341 | * Attachments:: Add files to tasks | |
6342 | * RSS Feeds:: Getting input from RSS feeds | |
ce57c2fe | 6343 | * Protocols:: External (e.g.@: Browser) access to Emacs and Org |
c0468714 GM |
6344 | * Refiling notes:: Moving a tree from one place to another |
6345 | * Archiving:: What to do with finished projects | |
864c9740 CD |
6346 | @end menu |
6347 | ||
86fbb8ca CD |
6348 | @node Capture, Attachments, Capture - Refile - Archive, Capture - Refile - Archive |
6349 | @section Capture | |
6350 | @cindex capture | |
dbc28aaa | 6351 | |
86fbb8ca CD |
6352 | Org's method for capturing new items is heavily inspired by John Wiegley |
6353 | excellent remember package. Up to version 6.36 Org used a special setup | |
e66ba1df | 6354 | for @file{remember.el}. @file{org-remember.el} is still part of Org mode for |
86fbb8ca CD |
6355 | backward compatibility with existing setups. You can find the documentation |
6356 | for org-remember at @url{http://orgmode.org/org-remember.pdf}. | |
6357 | ||
6358 | The new capturing setup described here is preferred and should be used by new | |
6359 | users. To convert your @code{org-remember-templates}, run the command | |
6360 | @example | |
6361 | @kbd{M-x org-capture-import-remember-templates @key{RET}} | |
6362 | @end example | |
6363 | @noindent and then customize the new variable with @kbd{M-x | |
6364 | customize-variable org-capture-templates}, check the result, and save the | |
6365 | customization. You can then use both remember and capture until | |
6366 | you are familiar with the new mechanism. | |
c8d0cf5c | 6367 | |
86fbb8ca CD |
6368 | Capture lets you quickly store notes with little interruption of your work |
6369 | flow. The basic process of capturing is very similar to remember, but Org | |
6370 | does enhance it with templates and more. | |
dbc28aaa CD |
6371 | |
6372 | @menu | |
c0468714 GM |
6373 | * Setting up capture:: Where notes will be stored |
6374 | * Using capture:: Commands to invoke and terminate capture | |
6375 | * Capture templates:: Define the outline of different note types | |
dbc28aaa CD |
6376 | @end menu |
6377 | ||
86fbb8ca CD |
6378 | @node Setting up capture, Using capture, Capture, Capture |
6379 | @subsection Setting up capture | |
dbc28aaa | 6380 | |
86fbb8ca CD |
6381 | The following customization sets a default target file for notes, and defines |
6382 | a global key@footnote{Please select your own key, @kbd{C-c c} is only a | |
6383 | suggestion.} for capturing new material. | |
dbc28aaa | 6384 | |
afe98dfa | 6385 | @vindex org-default-notes-file |
dbc28aaa | 6386 | @example |
dbc28aaa | 6387 | (setq org-default-notes-file (concat org-directory "/notes.org")) |
86fbb8ca | 6388 | (define-key global-map "\C-cc" 'org-capture) |
dbc28aaa CD |
6389 | @end example |
6390 | ||
86fbb8ca CD |
6391 | @node Using capture, Capture templates, Setting up capture, Capture |
6392 | @subsection Using capture | |
28a16a1b | 6393 | |
86fbb8ca | 6394 | @table @kbd |
acedf35c CD |
6395 | @orgcmd{C-c c,org-capture} |
6396 | Call the command @code{org-capture}. Note that this keybinding is global and | |
6397 | not active by default - you need to install it. If you have templates | |
ce57c2fe | 6398 | @cindex date tree |
acedf35c CD |
6399 | defined @pxref{Capture templates}, it will offer these templates for |
6400 | selection or use a new Org outline node as the default template. It will | |
6401 | insert the template into the target file and switch to an indirect buffer | |
6402 | narrowed to this new node. You may then insert the information you want. | |
6403 | ||
6404 | @orgcmd{C-c C-c,org-capture-finalize} | |
6405 | Once you have finished entering information into the capture buffer, @kbd{C-c | |
6406 | C-c} will return you to the window configuration before the capture process, | |
6407 | so that you can resume your work without further distraction. When called | |
6408 | with a prefix arg, finalize and then jump to the captured item. | |
6409 | ||
6410 | @orgcmd{C-c C-w,org-capture-refile} | |
86fbb8ca | 6411 | Finalize the capture process by refiling (@pxref{Refiling notes}) the note to |
afe98dfa | 6412 | a different place. Please realize that this is a normal refiling command |
acedf35c | 6413 | that will be executed---so the cursor position at the moment you run this |
afe98dfa | 6414 | command is important. If you have inserted a tree with a parent and |
acedf35c CD |
6415 | children, first move the cursor back to the parent. Any prefix argument |
6416 | given to this command will be passed on to the @code{org-refile} command. | |
86fbb8ca | 6417 | |
acedf35c | 6418 | @orgcmd{C-c C-k,org-capture-kill} |
86fbb8ca | 6419 | Abort the capture process and return to the previous state. |
acedf35c | 6420 | |
86fbb8ca CD |
6421 | @end table |
6422 | ||
6423 | You can also call @code{org-capture} in a special way from the agenda, using | |
6424 | the @kbd{k c} key combination. With this access, any timestamps inserted by | |
6425 | the selected capture template will default to the cursor date in the agenda, | |
6426 | rather than to the current date. | |
6427 | ||
acedf35c CD |
6428 | To find the locations of the last stored capture, use @code{org-capture} with |
6429 | prefix commands: | |
6430 | ||
6431 | @table @kbd | |
6432 | @orgkey{C-u C-c c} | |
ce57c2fe | 6433 | Visit the target location of a capture template. You get to select the |
acedf35c CD |
6434 | template in the usual way. |
6435 | @orgkey{C-u C-u C-c c} | |
6436 | Visit the last stored capture item in its buffer. | |
6437 | @end table | |
6438 | ||
86fbb8ca CD |
6439 | @node Capture templates, , Using capture, Capture |
6440 | @subsection Capture templates | |
6441 | @cindex templates, for Capture | |
6442 | ||
6443 | You can use templates for different types of capture items, and | |
6444 | for different target locations. The easiest way to create such templates is | |
6445 | through the customize interface. | |
6446 | ||
6447 | @table @kbd | |
acedf35c | 6448 | @orgkey{C-c c C} |
86fbb8ca CD |
6449 | Customize the variable @code{org-capture-templates}. |
6450 | @end table | |
6451 | ||
6452 | Before we give the formal description of template definitions, let's look at | |
6453 | an example. Say you would like to use one template to create general TODO | |
6454 | entries, and you want to put these entries under the heading @samp{Tasks} in | |
6455 | your file @file{~/org/gtd.org}. Also, a date tree in the file | |
6456 | @file{journal.org} should capture journal entries. A possible configuration | |
6457 | would look like: | |
28a16a1b | 6458 | |
86fbb8ca CD |
6459 | @example |
6460 | (setq org-capture-templates | |
6461 | '(("t" "Todo" entry (file+headline "~/org/gtd.org" "Tasks") | |
6462 | "* TODO %?\n %i\n %a") | |
6463 | ("j" "Journal" entry (file+datetree "~/org/journal.org") | |
6464 | "* %?\nEntered on %U\n %i\n %a"))) | |
6465 | @end example | |
6466 | ||
6467 | @noindent If you then press @kbd{C-c c t}, Org will prepare the template | |
6468 | for you like this: | |
dbc28aaa CD |
6469 | @example |
6470 | * TODO | |
86fbb8ca | 6471 | [[file:@var{link to where you initiated capture}]] |
dbc28aaa CD |
6472 | @end example |
6473 | ||
6474 | @noindent | |
86fbb8ca CD |
6475 | During expansion of the template, @code{%a} has been replaced by a link to |
6476 | the location from where you called the capture command. This can be | |
6477 | extremely useful for deriving tasks from emails, for example. You fill in | |
6478 | the task definition, press @code{C-c C-c} and Org returns you to the same | |
6479 | place where you started the capture process. | |
6480 | ||
ce57c2fe BG |
6481 | To define special keys to capture to a particular template without going |
6482 | through the interactive template selection, you can create your key binding | |
6483 | like this: | |
6484 | ||
6485 | @lisp | |
6486 | (define-key global-map "\C-cx" | |
6487 | (lambda () (interactive) (org-capture nil "x"))) | |
6488 | @end lisp | |
86fbb8ca CD |
6489 | |
6490 | @menu | |
c0468714 GM |
6491 | * Template elements:: What is needed for a complete template entry |
6492 | * Template expansion:: Filling in information about time and context | |
86fbb8ca CD |
6493 | @end menu |
6494 | ||
6495 | @node Template elements, Template expansion, Capture templates, Capture templates | |
6496 | @subsubsection Template elements | |
6497 | ||
e66ba1df | 6498 | Now lets look at the elements of a template definition. Each entry in |
ce57c2fe | 6499 | @code{org-capture-templates} is a list with the following items: |
86fbb8ca CD |
6500 | |
6501 | @table @var | |
6502 | @item keys | |
6503 | The keys that will select the template, as a string, characters | |
6504 | only, for example @code{"a"} for a template to be selected with a | |
6505 | single key, or @code{"bt"} for selection with two keys. When using | |
ce57c2fe | 6506 | several keys, keys using the same prefix key must be sequential |
86fbb8ca CD |
6507 | in the list and preceded by a 2-element entry explaining the |
6508 | prefix key, for example | |
dbc28aaa | 6509 | @example |
86fbb8ca CD |
6510 | ("b" "Templates for marking stuff to buy") |
6511 | @end example | |
6512 | @noindent If you do not define a template for the @kbd{C} key, this key will | |
6513 | be used to open the customize buffer for this complex variable. | |
6514 | ||
6515 | @item description | |
6516 | A short string describing the template, which will be shown during | |
6517 | selection. | |
6518 | ||
6519 | @item type | |
6520 | The type of entry, a symbol. Valid values are: | |
6521 | @table @code | |
6522 | @item entry | |
e66ba1df BG |
6523 | An Org mode node, with a headline. Will be filed as the child of the target |
6524 | entry or as a top-level entry. The target file should be an Org mode file. | |
86fbb8ca CD |
6525 | @item item |
6526 | A plain list item, placed in the first plain list at the target | |
6527 | location. Again the target file should be an Org file. | |
6528 | @item checkitem | |
6529 | A checkbox item. This only differs from the plain list item by the | |
6530 | default template. | |
6531 | @item table-line | |
6532 | a new line in the first table at the target location. Where exactly the | |
6533 | line will be inserted depends on the properties @code{:prepend} and | |
6534 | @code{:table-line-pos} (see below). | |
6535 | @item plain | |
6536 | Text to be inserted as it is. | |
6537 | @end table | |
6538 | ||
6539 | @item target | |
afe98dfa | 6540 | @vindex org-default-notes-file |
e66ba1df | 6541 | Specification of where the captured item should be placed. In Org mode |
afe98dfa | 6542 | files, targets usually define a node. Entries will become children of this |
acedf35c | 6543 | node. Other types will be added to the table or list in the body of this |
afe98dfa | 6544 | node. Most target specifications contain a file name. If that file name is |
ce57c2fe BG |
6545 | the empty string, it defaults to @code{org-default-notes-file}. A file can |
6546 | also be given as a variable, function, or Emacs Lisp form. | |
86fbb8ca CD |
6547 | |
6548 | Valid values are: | |
6549 | @table @code | |
6550 | @item (file "path/to/file") | |
6551 | Text will be placed at the beginning or end of that file. | |
6552 | ||
6553 | @item (id "id of existing org entry") | |
6554 | Filing as child of this entry, or in the body of the entry. | |
6555 | ||
6556 | @item (file+headline "path/to/file" "node headline") | |
6557 | Fast configuration if the target heading is unique in the file. | |
6558 | ||
6559 | @item (file+olp "path/to/file" "Level 1 heading" "Level 2" ...) | |
6560 | For non-unique headings, the full path is safer. | |
6561 | ||
6562 | @item (file+regexp "path/to/file" "regexp to find location") | |
6563 | Use a regular expression to position the cursor. | |
6564 | ||
6565 | @item (file+datetree "path/to/file") | |
acedf35c CD |
6566 | Will create a heading in a date tree for today's date. |
6567 | ||
6568 | @item (file+datetree+prompt "path/to/file") | |
6569 | Will create a heading in a date tree, but will prompt for the date. | |
86fbb8ca CD |
6570 | |
6571 | @item (file+function "path/to/file" function-finding-location) | |
6572 | A function to find the right location in the file. | |
6573 | ||
6574 | @item (clock) | |
6575 | File to the entry that is currently being clocked. | |
6576 | ||
6577 | @item (function function-finding-location) | |
6578 | Most general way, write your own function to find both | |
6579 | file and location. | |
6580 | @end table | |
6581 | ||
6582 | @item template | |
6583 | The template for creating the capture item. If you leave this empty, an | |
6584 | appropriate default template will be used. Otherwise this is a string with | |
6585 | escape codes, which will be replaced depending on time and context of the | |
6586 | capture call. The string with escapes may be loaded from a template file, | |
6587 | using the special syntax @code{(file "path/to/template")}. See below for | |
6588 | more details. | |
6589 | ||
6590 | @item properties | |
6591 | The rest of the entry is a property list of additional options. | |
6592 | Recognized properties are: | |
6593 | @table @code | |
6594 | @item :prepend | |
6595 | Normally new captured information will be appended at | |
6596 | the target location (last child, last table line, last list item...). | |
6597 | Setting this property will change that. | |
6598 | ||
6599 | @item :immediate-finish | |
6600 | When set, do not offer to edit the information, just | |
6601 | file it away immediately. This makes sense if the template only needs | |
6602 | information that can be added automatically. | |
6603 | ||
6604 | @item :empty-lines | |
6605 | Set this to the number of lines to insert | |
6606 | before and after the new item. Default 0, only common other value is 1. | |
6607 | ||
6608 | @item :clock-in | |
6609 | Start the clock in this item. | |
6610 | ||
ce57c2fe BG |
6611 | @item :clock-keep |
6612 | Keep the clock running when filing the captured entry. | |
6613 | ||
86fbb8ca CD |
6614 | @item :clock-resume |
6615 | If starting the capture interrupted a clock, restart that clock when finished | |
ce57c2fe BG |
6616 | with the capture. Note that @code{:clock-keep} has precedence over |
6617 | @code{:clock-resume}. When setting both to @code{t}, the current clock will | |
6618 | run and the previous one will not be resumed. | |
86fbb8ca CD |
6619 | |
6620 | @item :unnarrowed | |
6621 | Do not narrow the target buffer, simply show the full buffer. Default is to | |
6622 | narrow it so that you only see the new material. | |
afe98dfa | 6623 | |
ce57c2fe BG |
6624 | @item :table-line-pos |
6625 | Specification of the location in the table where the new line should be | |
6626 | inserted. It should be a string like @code{"II-3"} meaning that the new | |
6627 | line should become the third line before the second horizontal separator | |
6628 | line. | |
6629 | ||
afe98dfa CD |
6630 | @item :kill-buffer |
6631 | If the target file was not yet visited when capture was invoked, kill the | |
6632 | buffer again after capture is completed. | |
86fbb8ca CD |
6633 | @end table |
6634 | @end table | |
6635 | ||
6636 | @node Template expansion, , Template elements, Capture templates | |
6637 | @subsubsection Template expansion | |
6638 | ||
6639 | In the template itself, special @kbd{%}-escapes@footnote{If you need one of | |
6640 | these sequences literally, escape the @kbd{%} with a backslash.} allow | |
e66ba1df | 6641 | dynamic insertion of content. The templates are expanded in the order given here: |
86fbb8ca | 6642 | |
86fbb8ca | 6643 | @smallexample |
ce57c2fe BG |
6644 | %[@var{file}] @r{insert the contents of the file given by @var{file}.} |
6645 | %(@var{sexp}) @r{evaluate Elisp @var{sexp} and replace with the result.} | |
6646 | %<...> @r{the result of format-time-string on the ... format specification.} | |
6647 | %t @r{timestamp, date only.} | |
6648 | %T @r{timestamp with date and time.} | |
6649 | %u, %U @r{like the above, but inactive timestamps.} | |
6650 | %a @r{annotation, normally the link created with @code{org-store-link}.} | |
86fbb8ca CD |
6651 | %i @r{initial content, the region when capture is called while the} |
6652 | @r{region is active.} | |
b349f79f | 6653 | @r{The entire text will be indented like @code{%i} itself.} |
ce57c2fe | 6654 | %A @r{like @code{%a}, but prompt for the description part.} |
a7808fba CD |
6655 | %c @r{Current kill ring head.} |
6656 | %x @r{Content of the X clipboard.} | |
ce57c2fe BG |
6657 | %k @r{title of the currently clocked task.} |
6658 | %K @r{link to the currently clocked task.} | |
6659 | %n @r{user name (taken from @code{user-full-name}).} | |
6660 | %f @r{file visited by current buffer when org-capture was called.} | |
6661 | %F @r{full path of the file or directory visited by current buffer.} | |
6662 | %:keyword @r{specific information for certain link types, see below.} | |
dbc28aaa CD |
6663 | %^g @r{prompt for tags, with completion on tags in target file.} |
6664 | %^G @r{prompt for tags, with completion all tags in all agenda files.} | |
ce57c2fe BG |
6665 | %^t @r{like @code{%t}, but prompt for date. Similarly @code{%^T}, @code{%^u}, @code{%^U}.} |
6666 | @r{You may define a prompt like @code{%^@{Birthday@}t}.} | |
6667 | %^C @r{Interactive selection of which kill or clip to use.} | |
6668 | %^L @r{Like @code{%^C}, but insert as link.} | |
6669 | %^@{@var{prop}@}p @r{Prompt the user for a value for property @var{prop}.} | |
6670 | %^@{@var{prompt}@} @r{prompt the user for a string and replace this sequence with it.} | |
6671 | @r{You may specify a default value and a completion table with} | |
6672 | @r{%^@{prompt|default|completion2|completion3...@}.} | |
6673 | @r{The arrow keys access a prompt-specific history.} | |
86fbb8ca | 6674 | @end smallexample |
dbc28aaa CD |
6675 | |
6676 | @noindent | |
6677 | For specific link types, the following keywords will be | |
6678 | defined@footnote{If you define your own link types (@pxref{Adding | |
6679 | hyperlink types}), any property you store with | |
86fbb8ca | 6680 | @code{org-store-link-props} can be accessed in capture templates in a |
dbc28aaa CD |
6681 | similar way.}: |
6682 | ||
c8d0cf5c | 6683 | @vindex org-from-is-user-regexp |
86fbb8ca | 6684 | @smallexample |
ce57c2fe BG |
6685 | Link type | Available keywords |
6686 | ------------------------+---------------------------------------------- | |
afe98dfa CD |
6687 | bbdb | %:name %:company |
6688 | irc | %:server %:port %:nick | |
6689 | vm, wl, mh, mew, rmail | %:type %:subject %:message-id | |
6690 | | %:from %:fromname %:fromaddress | |
6691 | | %:to %:toname %:toaddress | |
6692 | | %:date @r{(message date header field)} | |
6693 | | %:date-timestamp @r{(date as active timestamp)} | |
6694 | | %:date-timestamp-inactive @r{(date as inactive timestamp)} | |
6695 | | %: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}.}} | |
6696 | gnus | %:group, @r{for messages also all email fields} | |
6697 | w3, w3m | %:url | |
6698 | info | %:file %:node | |
6699 | calendar | %:date | |
86fbb8ca | 6700 | @end smallexample |
dbc28aaa CD |
6701 | |
6702 | @noindent | |
6703 | To place the cursor after template expansion use: | |
6704 | ||
86fbb8ca | 6705 | @smallexample |
dbc28aaa | 6706 | %? @r{After completing the template, position cursor here.} |
86fbb8ca | 6707 | @end smallexample |
dbc28aaa | 6708 | |
c8d0cf5c | 6709 | |
86fbb8ca | 6710 | @node Attachments, RSS Feeds, Capture, Capture - Refile - Archive |
864c9740 CD |
6711 | @section Attachments |
6712 | @cindex attachments | |
6713 | ||
c8d0cf5c | 6714 | @vindex org-attach-directory |
864c9740 CD |
6715 | It is often useful to associate reference material with an outline node/task. |
6716 | Small chunks of plain text can simply be stored in the subtree of a project. | |
86fbb8ca | 6717 | Hyperlinks (@pxref{Hyperlinks}) can establish associations with |
864c9740 CD |
6718 | files that live elsewhere on your computer or in the cloud, like emails or |
6719 | source code files belonging to a project. Another method is @i{attachments}, | |
6720 | which are files located in a directory belonging to an outline node. Org | |
6721 | uses directories named by the unique ID of each entry. These directories are | |
6722 | located in the @file{data} directory which lives in the same directory where | |
c8d0cf5c CD |
6723 | your Org file lives@footnote{If you move entries or Org files from one |
6724 | directory to another, you may want to configure @code{org-attach-directory} | |
864c9740 | 6725 | to contain an absolute path.}. If you initialize this directory with |
c8d0cf5c | 6726 | @code{git init}, Org will automatically commit changes when it sees them. |
864c9740 CD |
6727 | The attachment system has been contributed to Org by John Wiegley. |
6728 | ||
c8d0cf5c | 6729 | In cases where it seems better to do so, you can also attach a directory of your |
55e0839d CD |
6730 | choice to an entry. You can also make children inherit the attachment |
6731 | directory from a parent, so that an entire subtree uses the same attached | |
6732 | directory. | |
6733 | ||
86fbb8ca | 6734 | @noindent The following commands deal with attachments: |
864c9740 CD |
6735 | |
6736 | @table @kbd | |
6737 | ||
acedf35c | 6738 | @orgcmd{C-c C-a,org-attach} |
864c9740 | 6739 | The dispatcher for commands related to the attachment system. After these |
86fbb8ca | 6740 | keys, a list of commands is displayed and you must press an additional key |
864c9740 CD |
6741 | to select a command: |
6742 | ||
6743 | @table @kbd | |
acedf35c | 6744 | @orgcmdtkc{a,C-c C-a a,org-attach-attach} |
c8d0cf5c | 6745 | @vindex org-attach-method |
864c9740 CD |
6746 | Select a file and move it into the task's attachment directory. The file |
6747 | will be copied, moved, or linked, depending on @code{org-attach-method}. | |
6748 | Note that hard links are not supported on all systems. | |
6749 | ||
6750 | @kindex C-c C-a c | |
96c8522a CD |
6751 | @kindex C-c C-a m |
6752 | @kindex C-c C-a l | |
864c9740 CD |
6753 | @item c/m/l |
6754 | Attach a file using the copy/move/link method. | |
6755 | Note that hard links are not supported on all systems. | |
6756 | ||
acedf35c | 6757 | @orgcmdtkc{n,C-c C-a n,org-attach-new} |
864c9740 CD |
6758 | Create a new attachment as an Emacs buffer. |
6759 | ||
acedf35c | 6760 | @orgcmdtkc{z,C-c C-a z,org-attach-sync} |
864c9740 CD |
6761 | Synchronize the current task with its attachment directory, in case you added |
6762 | attachments yourself. | |
6763 | ||
ce57c2fe | 6764 | @orgcmdtkc{o,C-c C-a o,org-attach-open} |
c8d0cf5c | 6765 | @vindex org-file-apps |
86fbb8ca | 6766 | Open current task's attachment. If there is more than one, prompt for a |
864c9740 | 6767 | file name first. Opening will follow the rules set by @code{org-file-apps}. |
a50253cc | 6768 | For more details, see the information on following hyperlinks |
864c9740 CD |
6769 | (@pxref{Handling links}). |
6770 | ||
acedf35c | 6771 | @orgcmdtkc{O,C-c C-a O,org-attach-open-in-emacs} |
864c9740 CD |
6772 | Also open the attachment, but force opening the file in Emacs. |
6773 | ||
acedf35c | 6774 | @orgcmdtkc{f,C-c C-a f,org-attach-reveal} |
864c9740 CD |
6775 | Open the current task's attachment directory. |
6776 | ||
acedf35c | 6777 | @orgcmdtkc{F,C-c C-a F,org-attach-reveal-in-emacs} |
c8d0cf5c | 6778 | Also open the directory, but force using @command{dired} in Emacs. |
864c9740 | 6779 | |
acedf35c | 6780 | @orgcmdtkc{d,C-c C-a d,org-attach-delete-one} |
864c9740 CD |
6781 | Select and delete a single attachment. |
6782 | ||
acedf35c | 6783 | @orgcmdtkc{D,C-c C-a D,org-attach-delete-all} |
864c9740 | 6784 | Delete all of a task's attachments. A safer way is to open the directory in |
c8d0cf5c | 6785 | @command{dired} and delete from there. |
55e0839d | 6786 | |
acedf35c | 6787 | @orgcmdtkc{s,C-c C-a s,org-attach-set-directory} |
c8d0cf5c | 6788 | @cindex property, ATTACH_DIR |
55e0839d CD |
6789 | Set a specific directory as the entry's attachment directory. This works by |
6790 | putting the directory path into the @code{ATTACH_DIR} property. | |
6791 | ||
acedf35c | 6792 | @orgcmdtkc{i,C-c C-a i,org-attach-set-inherit} |
c8d0cf5c | 6793 | @cindex property, ATTACH_DIR_INHERIT |
55e0839d | 6794 | Set the @code{ATTACH_DIR_INHERIT} property, so that children will use the |
c8d0cf5c | 6795 | same directory for attachments as the parent does. |
864c9740 CD |
6796 | @end table |
6797 | @end table | |
6798 | ||
a351880d | 6799 | @node RSS Feeds, Protocols, Attachments, Capture - Refile - Archive |
c8d0cf5c CD |
6800 | @section RSS feeds |
6801 | @cindex RSS feeds | |
86fbb8ca | 6802 | @cindex Atom feeds |
c8d0cf5c | 6803 | |
86fbb8ca CD |
6804 | Org can add and change entries based on information found in RSS feeds and |
6805 | Atom feeds. You could use this to make a task out of each new podcast in a | |
c8d0cf5c | 6806 | podcast feed. Or you could use a phone-based note-creating service on the |
86fbb8ca CD |
6807 | web to import tasks into Org. To access feeds, configure the variable |
6808 | @code{org-feed-alist}. The docstring of this variable has detailed | |
c8d0cf5c CD |
6809 | information. Here is just an example: |
6810 | ||
6811 | @example | |
6812 | (setq org-feed-alist | |
86fbb8ca | 6813 | '(("Slashdot" |
c0468714 GM |
6814 | "http://rss.slashdot.org/Slashdot/slashdot" |
6815 | "~/txt/org/feeds.org" "Slashdot Entries"))) | |
c8d0cf5c | 6816 | @end example |
86fbb8ca | 6817 | |
c8d0cf5c | 6818 | @noindent |
86fbb8ca CD |
6819 | will configure that new items from the feed provided by |
6820 | @code{rss.slashdot.org} will result in new entries in the file | |
6821 | @file{~/org/feeds.org} under the heading @samp{Slashdot Entries}, whenever | |
6822 | the following command is used: | |
c8d0cf5c CD |
6823 | |
6824 | @table @kbd | |
acedf35c | 6825 | @orgcmd{C-c C-x g,org-feed-update-all} |
c8d0cf5c CD |
6826 | @item C-c C-x g |
6827 | Collect items from the feeds configured in @code{org-feed-alist} and act upon | |
6828 | them. | |
acedf35c | 6829 | @orgcmd{C-c C-x G,org-feed-goto-inbox} |
c8d0cf5c CD |
6830 | Prompt for a feed name and go to the inbox configured for this feed. |
6831 | @end table | |
6832 | ||
6833 | Under the same headline, Org will create a drawer @samp{FEEDSTATUS} in which | |
6834 | it will store information about the status of items in the feed, to avoid | |
6835 | adding the same item several times. You should add @samp{FEEDSTATUS} to the | |
6836 | list of drawers in that file: | |
6837 | ||
6838 | @example | |
6839 | #+DRAWERS: LOGBOOK PROPERTIES FEEDSTATUS | |
6840 | @end example | |
6841 | ||
86fbb8ca CD |
6842 | For more information, including how to read atom feeds, see |
6843 | @file{org-feed.el} and the docstring of @code{org-feed-alist}. | |
c8d0cf5c | 6844 | |
a351880d | 6845 | @node Protocols, Refiling notes, RSS Feeds, Capture - Refile - Archive |
c8d0cf5c CD |
6846 | @section Protocols for external access |
6847 | @cindex protocols, for external access | |
6848 | @cindex emacsserver | |
6849 | ||
6850 | You can set up Org for handling protocol calls from outside applications that | |
6851 | are passed to Emacs through the @file{emacsserver}. For example, you can | |
6852 | configure bookmarks in your web browser to send a link to the current page to | |
86fbb8ca | 6853 | Org and create a note from it using capture (@pxref{Capture}). Or you |
c8d0cf5c CD |
6854 | could create a bookmark that will tell Emacs to open the local source file of |
6855 | a remote website you are looking at with the browser. See | |
6856 | @uref{http://orgmode.org/worg/org-contrib/org-protocol.php} for detailed | |
6857 | documentation and setup instructions. | |
6858 | ||
a351880d CD |
6859 | @node Refiling notes, Archiving, Protocols, Capture - Refile - Archive |
6860 | @section Refiling notes | |
6861 | @cindex refiling notes | |
c8d0cf5c | 6862 | |
a351880d CD |
6863 | When reviewing the captured data, you may want to refile some of the entries |
6864 | into a different list, for example into a project. Cutting, finding the | |
6865 | right location, and then pasting the note is cumbersome. To simplify this | |
6866 | process, you can use the following special command: | |
4009494e | 6867 | |
a351880d | 6868 | @table @kbd |
acedf35c | 6869 | @orgcmd{C-c C-w,org-refile} |
a351880d CD |
6870 | @vindex org-reverse-note-order |
6871 | @vindex org-refile-targets | |
6872 | @vindex org-refile-use-outline-path | |
6873 | @vindex org-outline-path-complete-in-steps | |
6874 | @vindex org-refile-allow-creating-parent-nodes | |
ed21c5c8 | 6875 | @vindex org-log-refile |
86fbb8ca | 6876 | @vindex org-refile-use-cache |
a351880d CD |
6877 | Refile the entry or region at point. This command offers possible locations |
6878 | for refiling the entry and lets you select one with completion. The item (or | |
6879 | all items in the region) is filed below the target heading as a subitem. | |
6880 | Depending on @code{org-reverse-note-order}, it will be either the first or | |
6881 | last subitem.@* | |
6882 | By default, all level 1 headlines in the current buffer are considered to be | |
6883 | targets, but you can have more complex definitions across a number of files. | |
6884 | See the variable @code{org-refile-targets} for details. If you would like to | |
6885 | select a location via a file-path-like completion along the outline path, see | |
6886 | the variables @code{org-refile-use-outline-path} and | |
6887 | @code{org-outline-path-complete-in-steps}. If you would like to be able to | |
045b9da7 | 6888 | create new nodes as new parents for refiling on the fly, check the |
a351880d | 6889 | variable @code{org-refile-allow-creating-parent-nodes}. |
ed21c5c8 CD |
6890 | When the variable @code{org-log-refile}@footnote{with corresponding |
6891 | @code{#+STARTUP} keywords @code{logrefile}, @code{lognoterefile}, | |
ce57c2fe | 6892 | and @code{nologrefile}} is set, a timestamp or a note will be |
ed21c5c8 | 6893 | recorded when an entry has been refiled. |
acedf35c | 6894 | @orgkey{C-u C-c C-w} |
a351880d | 6895 | Use the refile interface to jump to a heading. |
acedf35c | 6896 | @orgcmd{C-u C-u C-c C-w,org-refile-goto-last-stored} |
a351880d CD |
6897 | Jump to the location where @code{org-refile} last moved a tree to. |
6898 | @item C-2 C-c C-w | |
6899 | Refile as the child of the item currently being clocked. | |
acedf35c | 6900 | @orgcmdtkc{C-0 C-c C-w @ @r{or} @ C-u C-u C-u C-c C-w,C-0 C-c C-w,org-refile-cache-clear} |
86fbb8ca | 6901 | Clear the target cache. Caching of refile targets can be turned on by |
acedf35c | 6902 | setting @code{org-refile-use-cache}. To make the command see new possible |
86fbb8ca | 6903 | targets, you have to clear the cache with this command. |
a351880d | 6904 | @end table |
4009494e | 6905 | |
a351880d CD |
6906 | @node Archiving, , Refiling notes, Capture - Refile - Archive |
6907 | @section Archiving | |
6908 | @cindex archiving | |
4009494e | 6909 | |
a351880d CD |
6910 | When a project represented by a (sub)tree is finished, you may want |
6911 | to move the tree out of the way and to stop it from contributing to the | |
6912 | agenda. Archiving is important to keep your working files compact and global | |
6913 | searches like the construction of agenda views fast. | |
6914 | ||
6915 | @table @kbd | |
acedf35c | 6916 | @orgcmd{C-c C-x C-a,org-archive-subtree-default} |
a351880d CD |
6917 | @vindex org-archive-default-command |
6918 | Archive the current entry using the command specified in the variable | |
6919 | @code{org-archive-default-command}. | |
6920 | @end table | |
6921 | ||
6922 | @menu | |
c0468714 GM |
6923 | * Moving subtrees:: Moving a tree to an archive file |
6924 | * Internal archiving:: Switch off a tree but keep it in the file | |
a351880d CD |
6925 | @end menu |
6926 | ||
6927 | @node Moving subtrees, Internal archiving, Archiving, Archiving | |
6928 | @subsection Moving a tree to the archive file | |
6929 | @cindex external archiving | |
6930 | ||
6931 | The most common archiving action is to move a project tree to another file, | |
6932 | the archive file. | |
6933 | ||
6934 | @table @kbd | |
acedf35c | 6935 | @orgcmdkskc{C-c C-x C-s,C-c $,org-archive-subtree} |
a351880d CD |
6936 | @vindex org-archive-location |
6937 | Archive the subtree starting at the cursor position to the location | |
6938 | given by @code{org-archive-location}. | |
acedf35c | 6939 | @orgkey{C-u C-c C-x C-s} |
a351880d CD |
6940 | Check if any direct children of the current headline could be moved to |
6941 | the archive. To do this, each subtree is checked for open TODO entries. | |
6942 | If none are found, the command offers to move it to the archive | |
6943 | location. If the cursor is @emph{not} on a headline when this command | |
6944 | is invoked, the level 1 trees will be checked. | |
6945 | @end table | |
6946 | ||
6947 | @cindex archive locations | |
6948 | The default archive location is a file in the same directory as the | |
6949 | current file, with the name derived by appending @file{_archive} to the | |
6950 | current file name. For information and examples on how to change this, | |
6951 | see the documentation string of the variable | |
6952 | @code{org-archive-location}. There is also an in-buffer option for | |
6953 | setting this variable, for example@footnote{For backward compatibility, | |
6954 | the following also works: If there are several such lines in a file, | |
6955 | each specifies the archive location for the text below it. The first | |
6956 | such line also applies to any text before its definition. However, | |
6957 | using this method is @emph{strongly} deprecated as it is incompatible | |
6958 | with the outline structure of the document. The correct method for | |
6959 | setting multiple archive locations in a buffer is using properties.}: | |
6960 | ||
6961 | @cindex #+ARCHIVE | |
6962 | @example | |
6963 | #+ARCHIVE: %s_done:: | |
6964 | @end example | |
6965 | ||
6966 | @cindex property, ARCHIVE | |
6967 | @noindent | |
6968 | If you would like to have a special ARCHIVE location for a single entry | |
6969 | or a (sub)tree, give the entry an @code{:ARCHIVE:} property with the | |
6970 | location as the value (@pxref{Properties and Columns}). | |
6971 | ||
6972 | @vindex org-archive-save-context-info | |
6973 | When a subtree is moved, it receives a number of special properties that | |
6974 | record context information like the file from where the entry came, its | |
6975 | outline path the archiving time etc. Configure the variable | |
6976 | @code{org-archive-save-context-info} to adjust the amount of information | |
6977 | added. | |
6978 | ||
6979 | ||
6980 | @node Internal archiving, , Moving subtrees, Archiving | |
6981 | @subsection Internal archiving | |
6982 | ||
6983 | If you want to just switch off (for agenda views) certain subtrees without | |
6984 | moving them to a different file, you can use the @code{ARCHIVE tag}. | |
6985 | ||
6986 | A headline that is marked with the ARCHIVE tag (@pxref{Tags}) stays at | |
6987 | its location in the outline tree, but behaves in the following way: | |
6988 | @itemize @minus | |
6989 | @item | |
6990 | @vindex org-cycle-open-archived-trees | |
6991 | It does not open when you attempt to do so with a visibility cycling | |
6992 | command (@pxref{Visibility cycling}). You can force cycling archived | |
6993 | subtrees with @kbd{C-@key{TAB}}, or by setting the option | |
6994 | @code{org-cycle-open-archived-trees}. Also normal outline commands like | |
6995 | @code{show-all} will open archived subtrees. | |
6996 | @item | |
6997 | @vindex org-sparse-tree-open-archived-trees | |
6998 | During sparse tree construction (@pxref{Sparse trees}), matches in | |
6999 | archived subtrees are not exposed, unless you configure the option | |
7000 | @code{org-sparse-tree-open-archived-trees}. | |
7001 | @item | |
7002 | @vindex org-agenda-skip-archived-trees | |
7003 | During agenda view construction (@pxref{Agenda Views}), the content of | |
7004 | archived trees is ignored unless you configure the option | |
7005 | @code{org-agenda-skip-archived-trees}, in which case these trees will always | |
7006 | be included. In the agenda you can press @kbd{v a} to get archives | |
7007 | temporarily included. | |
7008 | @item | |
7009 | @vindex org-export-with-archived-trees | |
7010 | Archived trees are not exported (@pxref{Exporting}), only the headline | |
7011 | is. Configure the details using the variable | |
7012 | @code{org-export-with-archived-trees}. | |
7013 | @item | |
86fbb8ca | 7014 | @vindex org-columns-skip-archived-trees |
a351880d | 7015 | Archived trees are excluded from column view unless the variable |
86fbb8ca | 7016 | @code{org-columns-skip-archived-trees} is configured to @code{nil}. |
a351880d CD |
7017 | @end itemize |
7018 | ||
86fbb8ca | 7019 | The following commands help manage the ARCHIVE tag: |
a351880d CD |
7020 | |
7021 | @table @kbd | |
acedf35c | 7022 | @orgcmd{C-c C-x a,org-toggle-archive-tag} |
a351880d CD |
7023 | Toggle the ARCHIVE tag for the current headline. When the tag is set, |
7024 | the headline changes to a shadowed face, and the subtree below it is | |
7025 | hidden. | |
acedf35c | 7026 | @orgkey{C-u C-c C-x a} |
a351880d CD |
7027 | Check if any direct children of the current headline should be archived. |
7028 | To do this, each subtree is checked for open TODO entries. If none are | |
7029 | found, the command offers to set the ARCHIVE tag for the child. If the | |
7030 | cursor is @emph{not} on a headline when this command is invoked, the | |
7031 | level 1 trees will be checked. | |
acedf35c | 7032 | @orgcmd{C-@kbd{TAB},org-force-cycle-archived} |
a351880d | 7033 | Cycle a tree even if it is tagged with ARCHIVE. |
acedf35c | 7034 | @orgcmd{C-c C-x A,org-archive-to-archive-sibling} |
a351880d CD |
7035 | Move the current entry to the @emph{Archive Sibling}. This is a sibling of |
7036 | the entry with the heading @samp{Archive} and the tag @samp{ARCHIVE}. The | |
7037 | entry becomes a child of that sibling and in this way retains a lot of its | |
7038 | original context, including inherited tags and approximate position in the | |
7039 | outline. | |
7040 | @end table | |
7041 | ||
7042 | ||
7043 | @node Agenda Views, Markup, Capture - Refile - Archive, Top | |
86fbb8ca | 7044 | @chapter Agenda views |
a351880d CD |
7045 | @cindex agenda views |
7046 | ||
7047 | Due to the way Org works, TODO items, time-stamped items, and | |
7048 | tagged headlines can be scattered throughout a file or even a number of | |
7049 | files. To get an overview of open action items, or of events that are | |
7050 | important for a particular date, this information must be collected, | |
7051 | sorted and displayed in an organized way. | |
7052 | ||
7053 | Org can select items based on various criteria and display them | |
7054 | in a separate buffer. Seven different view types are provided: | |
7055 | ||
7056 | @itemize @bullet | |
7057 | @item | |
7058 | an @emph{agenda} that is like a calendar and shows information | |
7059 | for specific dates, | |
7060 | @item | |
7061 | a @emph{TODO list} that covers all unfinished | |
7062 | action items, | |
7063 | @item | |
7064 | a @emph{match view}, showings headlines based on the tags, properties, and | |
7065 | TODO state associated with them, | |
7066 | @item | |
7067 | a @emph{timeline view} that shows all events in a single Org file, | |
7068 | in time-sorted view, | |
7069 | @item | |
7070 | a @emph{text search view} that shows all entries from multiple files | |
7071 | that contain specified keywords, | |
7072 | @item | |
7073 | a @emph{stuck projects view} showing projects that currently don't move | |
7074 | along, and | |
7075 | @item | |
7076 | @emph{custom views} that are special searches and combinations of different | |
7077 | views. | |
4009494e GM |
7078 | @end itemize |
7079 | ||
7080 | @noindent | |
7081 | The extracted information is displayed in a special @emph{agenda | |
7082 | buffer}. This buffer is read-only, but provides commands to visit the | |
a7808fba | 7083 | corresponding locations in the original Org files, and even to |
28a16a1b | 7084 | edit these files remotely. |
4009494e | 7085 | |
c8d0cf5c CD |
7086 | @vindex org-agenda-window-setup |
7087 | @vindex org-agenda-restore-windows-after-quit | |
4009494e GM |
7088 | Two variables control how the agenda buffer is displayed and whether the |
7089 | window configuration is restored when the agenda exits: | |
7090 | @code{org-agenda-window-setup} and | |
7091 | @code{org-agenda-restore-windows-after-quit}. | |
7092 | ||
7093 | @menu | |
c0468714 GM |
7094 | * Agenda files:: Files being searched for agenda information |
7095 | * Agenda dispatcher:: Keyboard access to agenda views | |
7096 | * Built-in agenda views:: What is available out of the box? | |
7097 | * Presentation and sorting:: How agenda items are prepared for display | |
7098 | * Agenda commands:: Remote editing of Org trees | |
7099 | * Custom agenda views:: Defining special searches and views | |
7100 | * Exporting Agenda Views:: Writing a view to a file | |
7101 | * Agenda column view:: Using column view for collected entries | |
4009494e GM |
7102 | @end menu |
7103 | ||
a7808fba | 7104 | @node Agenda files, Agenda dispatcher, Agenda Views, Agenda Views |
4009494e GM |
7105 | @section Agenda files |
7106 | @cindex agenda files | |
7107 | @cindex files for agenda | |
7108 | ||
c8d0cf5c | 7109 | @vindex org-agenda-files |
dbc28aaa CD |
7110 | The information to be shown is normally collected from all @emph{agenda |
7111 | files}, the files listed in the variable | |
7112 | @code{org-agenda-files}@footnote{If the value of that variable is not a | |
7113 | list, but a single file name, then the list of agenda files will be | |
ce57c2fe | 7114 | maintained in that external file.}. If a directory is part of this list, |
dbc28aaa CD |
7115 | all files with the extension @file{.org} in this directory will be part |
7116 | of the list. | |
7117 | ||
c8d0cf5c CD |
7118 | Thus, even if you only work with a single Org file, that file should |
7119 | be put into the list@footnote{When using the dispatcher, pressing | |
dbc28aaa CD |
7120 | @kbd{<} before selecting a command will actually limit the command to |
7121 | the current file, and ignore @code{org-agenda-files} until the next | |
4009494e GM |
7122 | dispatcher command.}. You can customize @code{org-agenda-files}, but |
7123 | the easiest way to maintain it is through the following commands | |
7124 | ||
7125 | @cindex files, adding to agenda list | |
7126 | @table @kbd | |
ce57c2fe | 7127 | @orgcmd{C-c [,org-agenda-file-to-front} |
4009494e GM |
7128 | Add current file to the list of agenda files. The file is added to |
7129 | the front of the list. If it was already in the list, it is moved to | |
a7808fba | 7130 | the front. With a prefix argument, file is added/moved to the end. |
acedf35c | 7131 | @orgcmd{C-c ],org-remove-file} |
4009494e GM |
7132 | Remove current file from the list of agenda files. |
7133 | @kindex C-, | |
e66ba1df | 7134 | @cindex cycling, of agenda files |
acedf35c CD |
7135 | @orgcmd{C-',org-cycle-agenda-files} |
7136 | @itemx C-, | |
4009494e | 7137 | Cycle through agenda file list, visiting one file after the other. |
a7808fba CD |
7138 | @kindex M-x org-iswitchb |
7139 | @item M-x org-iswitchb | |
7140 | Command to use an @code{iswitchb}-like interface to switch to and between Org | |
7141 | buffers. | |
4009494e GM |
7142 | @end table |
7143 | ||
7144 | @noindent | |
7145 | The Org menu contains the current list of files and can be used | |
7146 | to visit any of them. | |
7147 | ||
c8d0cf5c CD |
7148 | If you would like to focus the agenda temporarily on a file not in |
7149 | this list, or on just one file in the list, or even on only a subtree in a | |
7150 | file, then this can be done in different ways. For a single agenda command, | |
dbc28aaa CD |
7151 | you may press @kbd{<} once or several times in the dispatcher |
7152 | (@pxref{Agenda dispatcher}). To restrict the agenda scope for an | |
7153 | extended period, use the following commands: | |
7154 | ||
7155 | @table @kbd | |
acedf35c | 7156 | @orgcmd{C-c C-x <,org-agenda-set-restriction-lock} |
dbc28aaa CD |
7157 | Permanently restrict the agenda to the current subtree. When with a |
7158 | prefix argument, or with the cursor before the first headline in a file, | |
7159 | the agenda scope is set to the entire file. This restriction remains in | |
7160 | effect until removed with @kbd{C-c C-x >}, or by typing either @kbd{<} | |
7161 | or @kbd{>} in the agenda dispatcher. If there is a window displaying an | |
7162 | agenda view, the new restriction takes effect immediately. | |
acedf35c | 7163 | @orgcmd{C-c C-x >,org-agenda-remove-restriction-lock} |
dbc28aaa CD |
7164 | Remove the permanent restriction created by @kbd{C-c C-x <}. |
7165 | @end table | |
7166 | ||
7167 | @noindent | |
c8d0cf5c | 7168 | When working with @file{speedbar.el}, you can use the following commands in |
a7808fba | 7169 | the Speedbar frame: |
dbc28aaa | 7170 | @table @kbd |
acedf35c | 7171 | @orgcmdtkc{< @r{in the speedbar frame},<,org-speedbar-set-agenda-restriction} |
c8d0cf5c CD |
7172 | Permanently restrict the agenda to the item---either an Org file or a subtree |
7173 | in such a file---at the cursor in the Speedbar frame. | |
dbc28aaa CD |
7174 | If there is a window displaying an agenda view, the new restriction takes |
7175 | effect immediately. | |
acedf35c | 7176 | @orgcmdtkc{> @r{in the speedbar frame},>,org-agenda-remove-restriction-lock} |
c8d0cf5c | 7177 | Lift the restriction. |
dbc28aaa CD |
7178 | @end table |
7179 | ||
a7808fba | 7180 | @node Agenda dispatcher, Built-in agenda views, Agenda files, Agenda Views |
4009494e GM |
7181 | @section The agenda dispatcher |
7182 | @cindex agenda dispatcher | |
7183 | @cindex dispatching agenda commands | |
c8d0cf5c | 7184 | The views are created through a dispatcher, which should be bound to a |
ce57c2fe | 7185 | global key---for example @kbd{C-c a} (@pxref{Activation}). In the |
4009494e GM |
7186 | following we will assume that @kbd{C-c a} is indeed how the dispatcher |
7187 | is accessed and list keyboard access to commands accordingly. After | |
7188 | pressing @kbd{C-c a}, an additional letter is required to execute a | |
7189 | command. The dispatcher offers the following default commands: | |
7190 | @table @kbd | |
7191 | @item a | |
a7808fba | 7192 | Create the calendar-like agenda (@pxref{Weekly/daily agenda}). |
4009494e GM |
7193 | @item t @r{/} T |
7194 | Create a list of all TODO items (@pxref{Global TODO list}). | |
7195 | @item m @r{/} M | |
7196 | Create a list of headlines matching a TAGS expression (@pxref{Matching | |
7197 | tags and properties}). | |
7198 | @item L | |
7199 | Create the timeline view for the current buffer (@pxref{Timeline}). | |
28a16a1b CD |
7200 | @item s |
7201 | Create a list of entries selected by a boolean expression of keywords | |
7202 | and/or regular expressions that must or must not occur in the entry. | |
dbc28aaa | 7203 | @item / |
c8d0cf5c | 7204 | @vindex org-agenda-text-search-extra-files |
dbc28aaa | 7205 | Search for a regular expression in all agenda files and additionally in |
c8d0cf5c | 7206 | the files listed in @code{org-agenda-text-search-extra-files}. This |
dbc28aaa CD |
7207 | uses the Emacs command @code{multi-occur}. A prefix argument can be |
7208 | used to specify the number of context lines for each match, default is | |
7209 | 1. | |
28a16a1b CD |
7210 | @item # @r{/} ! |
7211 | Create a list of stuck projects (@pxref{Stuck projects}). | |
dbc28aaa CD |
7212 | @item < |
7213 | Restrict an agenda command to the current buffer@footnote{For backward | |
7214 | compatibility, you can also press @kbd{1} to restrict to the current | |
7215 | buffer.}. After pressing @kbd{<}, you still need to press the character | |
7216 | selecting the command. | |
7217 | @item < < | |
4009494e | 7218 | If there is an active region, restrict the following agenda command to |
dbc28aaa CD |
7219 | the region. Otherwise, restrict it to the current subtree@footnote{For |
7220 | backward compatibility, you can also press @kbd{0} to restrict to the | |
c8d0cf5c | 7221 | current region/subtree.}. After pressing @kbd{< <}, you still need to press the |
dbc28aaa | 7222 | character selecting the command. |
4009494e GM |
7223 | @end table |
7224 | ||
7225 | You can also define custom commands that will be accessible through the | |
7226 | dispatcher, just like the default commands. This includes the | |
7227 | possibility to create extended agenda buffers that contain several | |
7228 | blocks together, for example the weekly agenda, the global TODO list and | |
7229 | a number of special tags matches. @xref{Custom agenda views}. | |
7230 | ||
a7808fba | 7231 | @node Built-in agenda views, Presentation and sorting, Agenda dispatcher, Agenda Views |
4009494e GM |
7232 | @section The built-in agenda views |
7233 | ||
7234 | In this section we describe the built-in views. | |
7235 | ||
7236 | @menu | |
c0468714 GM |
7237 | * Weekly/daily agenda:: The calendar page with current tasks |
7238 | * Global TODO list:: All unfinished action items | |
4009494e | 7239 | * Matching tags and properties:: Structured information with fine-tuned search |
c0468714 GM |
7240 | * Timeline:: Time-sorted view for single file |
7241 | * Search view:: Find entries by searching for text | |
7242 | * Stuck projects:: Find projects you need to review | |
4009494e GM |
7243 | @end menu |
7244 | ||
a7808fba | 7245 | @node Weekly/daily agenda, Global TODO list, Built-in agenda views, Built-in agenda views |
4009494e GM |
7246 | @subsection The weekly/daily agenda |
7247 | @cindex agenda | |
7248 | @cindex weekly agenda | |
7249 | @cindex daily agenda | |
7250 | ||
7251 | The purpose of the weekly/daily @emph{agenda} is to act like a page of a | |
7252 | paper agenda, showing all the tasks for the current week or day. | |
7253 | ||
7254 | @table @kbd | |
7255 | @cindex org-agenda, command | |
acedf35c | 7256 | @orgcmd{C-c a a,org-agenda-list} |
c8d0cf5c | 7257 | Compile an agenda for the current week from a list of Org files. The agenda |
864c9740 CD |
7258 | shows the entries for each day. With a numeric prefix@footnote{For backward |
7259 | compatibility, the universal prefix @kbd{C-u} causes all TODO entries to be | |
7260 | listed before the agenda. This feature is deprecated, use the dedicated TODO | |
7261 | list, or a block agenda instead (@pxref{Block agenda}).} (like @kbd{C-u 2 1 | |
acedf35c | 7262 | C-c a a}) you may set the number of days to be displayed. |
4009494e GM |
7263 | @end table |
7264 | ||
acedf35c CD |
7265 | @vindex org-agenda-span |
7266 | @vindex org-agenda-ndays | |
7267 | The default number of days displayed in the agenda is set by the variable | |
7268 | @code{org-agenda-span} (or the obsolete @code{org-agenda-ndays}). This | |
7269 | variable can be set to any number of days you want to see by default in the | |
7270 | agenda, or to a span name, such a @code{day}, @code{week}, @code{month} or | |
7271 | @code{year}. | |
7272 | ||
4009494e GM |
7273 | Remote editing from the agenda buffer means, for example, that you can |
7274 | change the dates of deadlines and appointments from the agenda buffer. | |
7275 | The commands available in the Agenda buffer are listed in @ref{Agenda | |
7276 | commands}. | |
7277 | ||
7278 | @subsubheading Calendar/Diary integration | |
7279 | @cindex calendar integration | |
7280 | @cindex diary integration | |
7281 | ||
7282 | Emacs contains the calendar and diary by Edward M. Reingold. The | |
7283 | calendar displays a three-month calendar with holidays from different | |
7284 | countries and cultures. The diary allows you to keep track of | |
7285 | anniversaries, lunar phases, sunrise/set, recurrent appointments | |
7286 | (weekly, monthly) and more. In this way, it is quite complementary to | |
a7808fba | 7287 | Org. It can be very useful to combine output from Org with |
4009494e GM |
7288 | the diary. |
7289 | ||
e66ba1df | 7290 | In order to include entries from the Emacs diary into Org mode's |
4009494e GM |
7291 | agenda, you only need to customize the variable |
7292 | ||
7293 | @lisp | |
7294 | (setq org-agenda-include-diary t) | |
7295 | @end lisp | |
7296 | ||
7297 | @noindent After that, everything will happen automatically. All diary | |
c8d0cf5c | 7298 | entries including holidays, anniversaries, etc., will be included in the |
e66ba1df | 7299 | agenda buffer created by Org mode. @key{SPC}, @key{TAB}, and |
4009494e GM |
7300 | @key{RET} can be used from the agenda buffer to jump to the diary |
7301 | file in order to edit existing diary entries. The @kbd{i} command to | |
7302 | insert new entries for the current date works in the agenda buffer, as | |
7303 | well as the commands @kbd{S}, @kbd{M}, and @kbd{C} to display | |
7304 | Sunrise/Sunset times, show lunar phases and to convert to other | |
7305 | calendars, respectively. @kbd{c} can be used to switch back and forth | |
7306 | between calendar and agenda. | |
7307 | ||
7308 | If you are using the diary only for sexp entries and holidays, it is | |
7309 | faster to not use the above setting, but instead to copy or even move | |
e66ba1df | 7310 | the entries into an Org file. Org mode evaluates diary-style sexp |
4009494e GM |
7311 | entries, and does it faster because there is no overhead for first |
7312 | creating the diary display. Note that the sexp entries must start at | |
c8d0cf5c | 7313 | the left margin, no whitespace is allowed before them. For example, |
a7808fba | 7314 | the following segment of an Org file will be processed and entries |
4009494e GM |
7315 | will be made in the agenda: |
7316 | ||
7317 | @example | |
7318 | * Birthdays and similar stuff | |
7319 | #+CATEGORY: Holiday | |
7320 | %%(org-calendar-holiday) ; special function for holiday names | |
7321 | #+CATEGORY: Ann | |
e4920bc9 | 7322 | %%(org-anniversary 1956 5 14)@footnote{@code{org-anniversary} is just like @code{diary-anniversary}, but the argument order is always according to ISO and therefore independent of the value of @code{calendar-date-style}.} Arthur Dent is %d years old |
ce57c2fe | 7323 | %%(org-anniversary 1869 10 2) Mahatma Gandhi would be %d years old |
4009494e GM |
7324 | @end example |
7325 | ||
c8d0cf5c CD |
7326 | @subsubheading Anniversaries from BBDB |
7327 | @cindex BBDB, anniversaries | |
7328 | @cindex anniversaries, from BBDB | |
7329 | ||
7330 | If you are using the Big Brothers Database to store your contacts, you will | |
7331 | very likely prefer to store anniversaries in BBDB rather than in a | |
7332 | separate Org or diary file. Org supports this and will show BBDB | |
7333 | anniversaries as part of the agenda. All you need to do is to add the | |
5a5fa834 | 7334 | following to one of your agenda files: |
c8d0cf5c CD |
7335 | |
7336 | @example | |
7337 | * Anniversaries | |
7338 | :PROPERTIES: | |
7339 | :CATEGORY: Anniv | |
86fbb8ca | 7340 | :END: |
c8d0cf5c CD |
7341 | %%(org-bbdb-anniversaries) |
7342 | @end example | |
7343 | ||
7344 | You can then go ahead and define anniversaries for a BBDB record. Basically, | |
7345 | you need to press @kbd{C-o anniversary @key{RET}} with the cursor in a BBDB | |
ce57c2fe BG |
7346 | record and then add the date in the format @code{YYYY-MM-DD} or @code{MM-DD}, |
7347 | followed by a space and the class of the anniversary (@samp{birthday} or | |
7348 | @samp{wedding}, or a format string). If you omit the class, it will default to | |
7349 | @samp{birthday}. Here are a few examples, the header for the file | |
7350 | @file{org-bbdb.el} contains more detailed information. | |
c8d0cf5c CD |
7351 | |
7352 | @example | |
7353 | 1973-06-22 | |
ce57c2fe | 7354 | 06-22 |
c8d0cf5c | 7355 | 1955-08-02 wedding |
e66ba1df | 7356 | 2008-04-14 %s released version 6.01 of org mode, %d years ago |
c8d0cf5c CD |
7357 | @end example |
7358 | ||
7359 | After a change to BBDB, or for the first agenda display during an Emacs | |
7360 | session, the agenda display will suffer a short delay as Org updates its | |
7361 | hash with anniversaries. However, from then on things will be very fast---much | |
7362 | faster in fact than a long list of @samp{%%(diary-anniversary)} entries | |
7363 | in an Org or Diary file. | |
7364 | ||
dbc28aaa CD |
7365 | @subsubheading Appointment reminders |
7366 | @cindex @file{appt.el} | |
7367 | @cindex appointment reminders | |
e66ba1df BG |
7368 | @cindex appointment |
7369 | @cindex reminders | |
dbc28aaa | 7370 | |
c8d0cf5c CD |
7371 | Org can interact with Emacs appointments notification facility. To add all |
7372 | the appointments of your agenda files, use the command | |
7373 | @code{org-agenda-to-appt}. This command also lets you filter through the | |
7374 | list of your appointments and add only those belonging to a specific category | |
ce57c2fe | 7375 | or matching a regular expression. See the docstring for details. |
dbc28aaa | 7376 | |
a7808fba | 7377 | @node Global TODO list, Matching tags and properties, Weekly/daily agenda, Built-in agenda views |
4009494e GM |
7378 | @subsection The global TODO list |
7379 | @cindex global TODO list | |
7380 | @cindex TODO list, global | |
7381 | ||
c8d0cf5c | 7382 | The global TODO list contains all unfinished TODO items formatted and |
4009494e GM |
7383 | collected into a single place. |
7384 | ||
7385 | @table @kbd | |
acedf35c | 7386 | @orgcmd{C-c a t,org-todo-list} |
86fbb8ca CD |
7387 | Show the global TODO list. This collects the TODO items from all agenda |
7388 | files (@pxref{Agenda Views}) into a single buffer. By default, this lists | |
7389 | items with a state the is not a DONE state. The buffer is in | |
7390 | @code{agenda-mode}, so there are commands to examine and manipulate the TODO | |
7391 | entries directly from that buffer (@pxref{Agenda commands}). | |
acedf35c | 7392 | @orgcmd{C-c a T,org-todo-list} |
4009494e | 7393 | @cindex TODO keyword matching |
c8d0cf5c | 7394 | @vindex org-todo-keywords |
86fbb8ca CD |
7395 | Like the above, but allows selection of a specific TODO keyword. You can |
7396 | also do this by specifying a prefix argument to @kbd{C-c a t}. You are | |
7397 | prompted for a keyword, and you may also specify several keywords by | |
7398 | separating them with @samp{|} as the boolean OR operator. With a numeric | |
acedf35c | 7399 | prefix, the Nth keyword in @code{org-todo-keywords} is selected. |
4009494e GM |
7400 | @kindex r |
7401 | The @kbd{r} key in the agenda buffer regenerates it, and you can give | |
7402 | a prefix argument to this command to change the selected TODO keyword, | |
7403 | for example @kbd{3 r}. If you often need a search for a specific | |
7404 | keyword, define a custom command for it (@pxref{Agenda dispatcher}).@* | |
7405 | Matching specific TODO keywords can also be done as part of a tags | |
7406 | search (@pxref{Tag searches}). | |
7407 | @end table | |
7408 | ||
7409 | Remote editing of TODO items means that you can change the state of a | |
7410 | TODO entry with a single key press. The commands available in the | |
7411 | TODO list are described in @ref{Agenda commands}. | |
7412 | ||
a7808fba CD |
7413 | @cindex sublevels, inclusion into TODO list |
7414 | Normally the global TODO list simply shows all headlines with TODO | |
4009494e GM |
7415 | keywords. This list can become very long. There are two ways to keep |
7416 | it more compact: | |
7417 | @itemize @minus | |
7418 | @item | |
c8d0cf5c CD |
7419 | @vindex org-agenda-todo-ignore-scheduled |
7420 | @vindex org-agenda-todo-ignore-deadlines | |
acedf35c | 7421 | @vindex org-agenda-todo-ignore-timestamp |
c8d0cf5c CD |
7422 | @vindex org-agenda-todo-ignore-with-date |
7423 | Some people view a TODO item that has been @emph{scheduled} for execution or | |
7424 | have a @emph{deadline} (@pxref{Timestamps}) as no longer @emph{open}. | |
7425 | Configure the variables @code{org-agenda-todo-ignore-scheduled}, | |
acedf35c CD |
7426 | @code{org-agenda-todo-ignore-deadlines}, |
7427 | @code{org-agenda-todo-ignore-timestamp} and/or | |
7428 | @code{org-agenda-todo-ignore-with-date} to exclude such items from the global | |
7429 | TODO list. | |
c8d0cf5c CD |
7430 | @item |
7431 | @vindex org-agenda-todo-list-sublevels | |
4009494e GM |
7432 | TODO items may have sublevels to break up the task into subtasks. In |
7433 | such cases it may be enough to list only the highest level TODO headline | |
7434 | and omit the sublevels from the global list. Configure the variable | |
7435 | @code{org-agenda-todo-list-sublevels} to get this behavior. | |
7436 | @end itemize | |
7437 | ||
7438 | @node Matching tags and properties, Timeline, Global TODO list, Built-in agenda views | |
a7808fba | 7439 | @subsection Matching tags and properties |
4009494e GM |
7440 | @cindex matching, of tags |
7441 | @cindex matching, of properties | |
7442 | @cindex tags view | |
864c9740 | 7443 | @cindex match view |
4009494e | 7444 | |
c8d0cf5c CD |
7445 | If headlines in the agenda files are marked with @emph{tags} (@pxref{Tags}), |
7446 | or have properties (@pxref{Properties and Columns}), you can select headlines | |
7447 | based on this metadata and collect them into an agenda buffer. The match | |
7448 | syntax described here also applies when creating sparse trees with @kbd{C-c / | |
7449 | m}. | |
4009494e GM |
7450 | |
7451 | @table @kbd | |
acedf35c | 7452 | @orgcmd{C-c a m,org-tags-view} |
4009494e GM |
7453 | Produce a list of all headlines that match a given set of tags. The |
7454 | command prompts for a selection criterion, which is a boolean logic | |
dbc28aaa CD |
7455 | expression with tags, like @samp{+work+urgent-withboss} or |
7456 | @samp{work|home} (@pxref{Tags}). If you often need a specific search, | |
4009494e | 7457 | define a custom command for it (@pxref{Agenda dispatcher}). |
acedf35c | 7458 | @orgcmd{C-c a M,org-tags-view} |
c8d0cf5c CD |
7459 | @vindex org-tags-match-list-sublevels |
7460 | @vindex org-agenda-tags-todo-honor-ignore-options | |
86fbb8ca CD |
7461 | Like @kbd{C-c a m}, but only select headlines that are also TODO items in a |
7462 | not-DONE state and force checking subitems (see variable | |
7463 | @code{org-tags-match-list-sublevels}). To exclude scheduled/deadline items, | |
7464 | see the variable @code{org-agenda-tags-todo-honor-ignore-options}. Matching | |
7465 | specific TODO keywords together with a tags match is also possible, see | |
7466 | @ref{Tag searches}. | |
4009494e GM |
7467 | @end table |
7468 | ||
7469 | The commands available in the tags list are described in @ref{Agenda | |
7470 | commands}. | |
7471 | ||
c8d0cf5c | 7472 | @subsubheading Match syntax |
4009494e | 7473 | |
c8d0cf5c CD |
7474 | @cindex Boolean logic, for tag/property searches |
7475 | A search string can use Boolean operators @samp{&} for AND and @samp{|} for | |
7476 | OR. @samp{&} binds more strongly than @samp{|}. Parentheses are currently | |
7477 | not implemented. Each element in the search is either a tag, a regular | |
7478 | expression matching tags, or an expression like @code{PROPERTY OPERATOR | |
7479 | VALUE} with a comparison operator, accessing a property value. Each element | |
7480 | may be preceded by @samp{-}, to select against it, and @samp{+} is syntactic | |
7481 | sugar for positive selection. The AND operator @samp{&} is optional when | |
7482 | @samp{+} or @samp{-} is present. Here are some examples, using only tags. | |
4009494e | 7483 | |
c8d0cf5c CD |
7484 | @table @samp |
7485 | @item +work-boss | |
7486 | Select headlines tagged @samp{:work:}, but discard those also tagged | |
7487 | @samp{:boss:}. | |
7488 | @item work|laptop | |
7489 | Selects lines tagged @samp{:work:} or @samp{:laptop:}. | |
7490 | @item work|laptop+night | |
7491 | Like before, but require the @samp{:laptop:} lines to be tagged also | |
7492 | @samp{:night:}. | |
4009494e GM |
7493 | @end table |
7494 | ||
c8d0cf5c CD |
7495 | @cindex regular expressions, with tags search |
7496 | Instead of a tag, you may also specify a regular expression enclosed in curly | |
7497 | braces. For example, | |
7498 | @samp{work+@{^boss.*@}} matches headlines that contain the tag | |
7499 | @samp{:work:} and any tag @i{starting} with @samp{boss}. | |
7500 | ||
7501 | @cindex TODO keyword matching, with tags search | |
7502 | @cindex level, require for tags/property match | |
7503 | @cindex category, require for tags/property match | |
7504 | @vindex org-odd-levels-only | |
7505 | You may also test for properties (@pxref{Properties and Columns}) at the same | |
7506 | time as matching tags. The properties may be real properties, or special | |
7507 | properties that represent other metadata (@pxref{Special properties}). For | |
7508 | example, the ``property'' @code{TODO} represents the TODO keyword of the | |
7509 | entry. Or, the ``property'' @code{LEVEL} represents the level of an entry. | |
7510 | So a search @samp{+LEVEL=3+boss-TODO="DONE"} lists all level three headlines | |
7511 | that have the tag @samp{boss} and are @emph{not} marked with the TODO keyword | |
7512 | DONE. In buffers with @code{org-odd-levels-only} set, @samp{LEVEL} does not | |
7513 | count the number of stars, but @samp{LEVEL=2} will correspond to 3 stars etc. | |
7514 | ||
7515 | Here are more examples: | |
7516 | @table @samp | |
7517 | @item work+TODO="WAITING" | |
7518 | Select @samp{:work:}-tagged TODO lines with the specific TODO | |
7519 | keyword @samp{WAITING}. | |
7520 | @item work+TODO="WAITING"|home+TODO="WAITING" | |
7521 | Waiting tasks both at work and at home. | |
7522 | @end table | |
7523 | ||
7524 | When matching properties, a number of different operators can be used to test | |
7525 | the value of a property. Here is a complex example: | |
7526 | ||
7527 | @example | |
7528 | +work-boss+PRIORITY="A"+Coffee="unlimited"+Effort<2 \ | |
7529 | +With=@{Sarah\|Denny@}+SCHEDULED>="<2008-10-11>" | |
7530 | @end example | |
7531 | ||
7532 | @noindent | |
7533 | The type of comparison will depend on how the comparison value is written: | |
7534 | @itemize @minus | |
7535 | @item | |
7536 | If the comparison value is a plain number, a numerical comparison is done, | |
7537 | and the allowed operators are @samp{<}, @samp{=}, @samp{>}, @samp{<=}, | |
7538 | @samp{>=}, and @samp{<>}. | |
7539 | @item | |
7540 | If the comparison value is enclosed in double-quotes, | |
7541 | a string comparison is done, and the same operators are allowed. | |
7542 | @item | |
7543 | If the comparison value is enclosed in double-quotes @emph{and} angular | |
7544 | brackets (like @samp{DEADLINE<="<2008-12-24 18:30>"}), both values are | |
7545 | assumed to be date/time specifications in the standard Org way, and the | |
7546 | comparison will be done accordingly. Special values that will be recognized | |
7547 | are @code{"<now>"} for now (including time), and @code{"<today>"}, and | |
ce57c2fe | 7548 | @code{"<tomorrow>"} for these days at 0:00 hours, i.e.@: without a time |
c8d0cf5c CD |
7549 | specification. Also strings like @code{"<+5d>"} or @code{"<-2m>"} with units |
7550 | @code{d}, @code{w}, @code{m}, and @code{y} for day, week, month, and year, | |
7551 | respectively, can be used. | |
7552 | @item | |
7553 | If the comparison value is enclosed | |
7554 | in curly braces, a regexp match is performed, with @samp{=} meaning that the | |
7555 | regexp matches the property value, and @samp{<>} meaning that it does not | |
7556 | match. | |
7557 | @end itemize | |
7558 | ||
7559 | So the search string in the example finds entries tagged @samp{:work:} but | |
7560 | not @samp{:boss:}, which also have a priority value @samp{A}, a | |
7561 | @samp{:Coffee:} property with the value @samp{unlimited}, an @samp{Effort} | |
7562 | property that is numerically smaller than 2, a @samp{:With:} property that is | |
7563 | matched by the regular expression @samp{Sarah\|Denny}, and that are scheduled | |
7564 | on or after October 11, 2008. | |
7565 | ||
7566 | Accessing TODO, LEVEL, and CATEGORY during a search is fast. Accessing any | |
7567 | other properties will slow down the search. However, once you have paid the | |
7568 | price by accessing one property, testing additional properties is cheap | |
7569 | again. | |
7570 | ||
e66ba1df | 7571 | You can configure Org mode to use property inheritance during a search, but |
c8d0cf5c CD |
7572 | beware that this can slow down searches considerably. See @ref{Property |
7573 | inheritance}, for details. | |
7574 | ||
7575 | For backward compatibility, and also for typing speed, there is also a | |
7576 | different way to test TODO states in a search. For this, terminate the | |
7577 | tags/property part of the search string (which may include several terms | |
7578 | connected with @samp{|}) with a @samp{/} and then specify a Boolean | |
7579 | expression just for TODO keywords. The syntax is then similar to that for | |
86fbb8ca CD |
7580 | tags, but should be applied with care: for example, a positive selection on |
7581 | several TODO keywords cannot meaningfully be combined with boolean AND. | |
7582 | However, @emph{negative selection} combined with AND can be meaningful. To | |
7583 | make sure that only lines are checked that actually have any TODO keyword | |
7584 | (resulting in a speed-up), use @kbd{C-c a M}, or equivalently start the TODO | |
7585 | part after the slash with @samp{!}. Using @kbd{C-c a M} or @samp{/!} will | |
7586 | not match TODO keywords in a DONE state. Examples: | |
c8d0cf5c CD |
7587 | |
7588 | @table @samp | |
7589 | @item work/WAITING | |
7590 | Same as @samp{work+TODO="WAITING"} | |
7591 | @item work/!-WAITING-NEXT | |
7592 | Select @samp{:work:}-tagged TODO lines that are neither @samp{WAITING} | |
7593 | nor @samp{NEXT} | |
7594 | @item work/!+WAITING|+NEXT | |
7595 | Select @samp{:work:}-tagged TODO lines that are either @samp{WAITING} or | |
7596 | @samp{NEXT}. | |
7597 | @end table | |
7598 | ||
a351880d | 7599 | @node Timeline, Search view, Matching tags and properties, Built-in agenda views |
c8d0cf5c CD |
7600 | @subsection Timeline for a single file |
7601 | @cindex timeline, single file | |
7602 | @cindex time-sorted view | |
7603 | ||
e66ba1df | 7604 | The timeline summarizes all time-stamped items from a single Org mode |
c8d0cf5c CD |
7605 | file in a @emph{time-sorted view}. The main purpose of this command is |
7606 | to give an overview over events in a project. | |
7607 | ||
7608 | @table @kbd | |
acedf35c | 7609 | @orgcmd{C-c a L,org-timeline} |
c8d0cf5c CD |
7610 | Show a time-sorted view of the Org file, with all time-stamped items. |
7611 | When called with a @kbd{C-u} prefix, all unfinished TODO entries | |
7612 | (scheduled or not) are also listed under the current date. | |
7613 | @end table | |
7614 | ||
7615 | @noindent | |
7616 | The commands available in the timeline buffer are listed in | |
7617 | @ref{Agenda commands}. | |
7618 | ||
a351880d CD |
7619 | @node Search view, Stuck projects, Timeline, Built-in agenda views |
7620 | @subsection Search view | |
7621 | @cindex search view | |
7622 | @cindex text search | |
7623 | @cindex searching, for text | |
c8d0cf5c | 7624 | |
e66ba1df | 7625 | This agenda view is a general text search facility for Org mode entries. |
c8d0cf5c | 7626 | It is particularly useful to find notes. |
28a16a1b CD |
7627 | |
7628 | @table @kbd | |
acedf35c | 7629 | @orgcmd{C-c a s,org-search-view} |
a351880d CD |
7630 | This is a special search that lets you select entries by matching a substring |
7631 | or specific words using a boolean logic. | |
7632 | @end table | |
7633 | For example, the search string @samp{computer equipment} will find entries | |
7634 | that contain @samp{computer equipment} as a substring. If the two words are | |
7635 | separated by more space or a line break, the search will still match. | |
7636 | Search view can also search for specific keywords in the entry, using Boolean | |
7637 | logic. The search string @samp{+computer +wifi -ethernet -@{8\.11[bg]@}} | |
28a16a1b CD |
7638 | will search for note entries that contain the keywords @code{computer} |
7639 | and @code{wifi}, but not the keyword @code{ethernet}, and which are also | |
7640 | not matched by the regular expression @code{8\.11[bg]}, meaning to | |
ed21c5c8 CD |
7641 | exclude both 8.11b and 8.11g. The first @samp{+} is necessary to turn on |
7642 | word search, other @samp{+} characters are optional. For more details, see | |
7643 | the docstring of the command @code{org-search-view}. | |
28a16a1b | 7644 | |
c8d0cf5c | 7645 | @vindex org-agenda-text-search-extra-files |
28a16a1b CD |
7646 | Note that in addition to the agenda files, this command will also search |
7647 | the files listed in @code{org-agenda-text-search-extra-files}. | |
28a16a1b | 7648 | |
a351880d | 7649 | @node Stuck projects, , Search view, Built-in agenda views |
4009494e | 7650 | @subsection Stuck projects |
ce57c2fe | 7651 | @pindex GTD, Getting Things Done |
4009494e GM |
7652 | |
7653 | If you are following a system like David Allen's GTD to organize your | |
7654 | work, one of the ``duties'' you have is a regular review to make sure | |
7655 | that all projects move along. A @emph{stuck} project is a project that | |
7656 | has no defined next actions, so it will never show up in the TODO lists | |
e66ba1df | 7657 | Org mode produces. During the review, you need to identify such |
4009494e GM |
7658 | projects and define next actions for them. |
7659 | ||
7660 | @table @kbd | |
acedf35c | 7661 | @orgcmd{C-c a #,org-agenda-list-stuck-projects} |
4009494e GM |
7662 | List projects that are stuck. |
7663 | @kindex C-c a ! | |
7664 | @item C-c a ! | |
c8d0cf5c | 7665 | @vindex org-stuck-projects |
4009494e GM |
7666 | Customize the variable @code{org-stuck-projects} to define what a stuck |
7667 | project is and how to find it. | |
7668 | @end table | |
7669 | ||
7670 | You almost certainly will have to configure this view before it will | |
7671 | work for you. The built-in default assumes that all your projects are | |
7672 | level-2 headlines, and that a project is not stuck if it has at least | |
a7808fba | 7673 | one entry marked with a TODO keyword TODO or NEXT or NEXTACTION. |
4009494e | 7674 | |
e66ba1df | 7675 | Let's assume that you, in your own way of using Org mode, identify |
a7808fba | 7676 | projects with a tag PROJECT, and that you use a TODO keyword MAYBE to |
864c9740 | 7677 | indicate a project that should not be considered yet. Let's further |
a7808fba | 7678 | assume that the TODO keyword DONE marks finished projects, and that NEXT |
4009494e GM |
7679 | and TODO indicate next actions. The tag @@SHOP indicates shopping and |
7680 | is a next action even without the NEXT tag. Finally, if the project | |
7681 | contains the special word IGNORE anywhere, it should not be listed | |
7682 | either. In this case you would start by identifying eligible projects | |
c8d0cf5c CD |
7683 | with a tags/todo match@footnote{@xref{Tag searches}.} |
7684 | @samp{+PROJECT/-MAYBE-DONE}, and then check for TODO, NEXT, @@SHOP, and | |
7685 | IGNORE in the subtree to identify projects that are not stuck. The | |
7686 | correct customization for this is | |
4009494e GM |
7687 | |
7688 | @lisp | |
7689 | (setq org-stuck-projects | |
7690 | '("+PROJECT/-MAYBE-DONE" ("NEXT" "TODO") ("@@SHOP") | |
7691 | "\\<IGNORE\\>")) | |
7692 | @end lisp | |
7693 | ||
c8d0cf5c CD |
7694 | Note that if a project is identified as non-stuck, the subtree of this entry |
7695 | will still be searched for stuck projects. | |
4009494e | 7696 | |
a7808fba | 7697 | @node Presentation and sorting, Agenda commands, Built-in agenda views, Agenda Views |
4009494e GM |
7698 | @section Presentation and sorting |
7699 | @cindex presentation, of agenda items | |
7700 | ||
c8d0cf5c | 7701 | @vindex org-agenda-prefix-format |
ce57c2fe | 7702 | @vindex org-agenda-tags-column |
e66ba1df | 7703 | Before displaying items in an agenda view, Org mode visually prepares the |
ce57c2fe BG |
7704 | items and sorts them. Each item occupies a single line. The line starts |
7705 | with a @emph{prefix} that contains the @emph{category} (@pxref{Categories}) | |
7706 | of the item and other important information. You can customize in which | |
7707 | column tags will be displayed through @code{org-agenda-tags-column}. You can | |
7708 | also customize the prefix using the option @code{org-agenda-prefix-format}. | |
7709 | This prefix is followed by a cleaned-up version of the outline headline | |
4009494e GM |
7710 | associated with the item. |
7711 | ||
7712 | @menu | |
c0468714 GM |
7713 | * Categories:: Not all tasks are equal |
7714 | * Time-of-day specifications:: How the agenda knows the time | |
7715 | * Sorting of agenda items:: The order of things | |
4009494e GM |
7716 | @end menu |
7717 | ||
7718 | @node Categories, Time-of-day specifications, Presentation and sorting, Presentation and sorting | |
7719 | @subsection Categories | |
7720 | ||
7721 | @cindex category | |
afe98dfa | 7722 | @cindex #+CATEGORY |
4009494e GM |
7723 | The category is a broad label assigned to each agenda item. By default, |
7724 | the category is simply derived from the file name, but you can also | |
dbc28aaa | 7725 | specify it with a special line in the buffer, like this@footnote{For |
c8d0cf5c | 7726 | backward compatibility, the following also works: if there are several |
dbc28aaa CD |
7727 | such lines in a file, each specifies the category for the text below it. |
7728 | The first category also applies to any text before the first CATEGORY | |
7729 | line. However, using this method is @emph{strongly} deprecated as it is | |
7730 | incompatible with the outline structure of the document. The correct | |
7731 | method for setting multiple categories in a buffer is using a | |
7732 | property.}: | |
4009494e GM |
7733 | |
7734 | @example | |
7735 | #+CATEGORY: Thesis | |
7736 | @end example | |
7737 | ||
dbc28aaa | 7738 | @noindent |
c8d0cf5c | 7739 | @cindex property, CATEGORY |
dbc28aaa | 7740 | If you would like to have a special CATEGORY for a single entry or a |
55e0839d CD |
7741 | (sub)tree, give the entry a @code{:CATEGORY:} property with the |
7742 | special category you want to apply as the value. | |
dbc28aaa CD |
7743 | |
7744 | @noindent | |
7745 | The display in the agenda buffer looks best if the category is not | |
7746 | longer than 10 characters. | |
4009494e | 7747 | |
acedf35c CD |
7748 | @noindent |
7749 | You can set up icons for category by customizing the | |
7750 | @code{org-agenda-category-icon-alist} variable. | |
7751 | ||
4009494e | 7752 | @node Time-of-day specifications, Sorting of agenda items, Categories, Presentation and sorting |
a7808fba | 7753 | @subsection Time-of-day specifications |
4009494e GM |
7754 | @cindex time-of-day specification |
7755 | ||
e66ba1df | 7756 | Org mode checks each agenda item for a time-of-day specification. The |
c8d0cf5c | 7757 | time can be part of the timestamp that triggered inclusion into the |
4009494e | 7758 | agenda, for example as in @w{@samp{<2005-05-10 Tue 19:00>}}. Time |
c8d0cf5c | 7759 | ranges can be specified with two timestamps, like |
4009494e GM |
7760 | @c |
7761 | @w{@samp{<2005-05-10 Tue 20:30>--<2005-05-10 Tue 22:15>}}. | |
7762 | ||
7763 | In the headline of the entry itself, a time(range) may also appear as | |
44ce9197 | 7764 | plain text (like @samp{12:45} or a @samp{8:30-1pm}). If the agenda |
a7808fba | 7765 | integrates the Emacs diary (@pxref{Weekly/daily agenda}), time |
4009494e GM |
7766 | specifications in diary entries are recognized as well. |
7767 | ||
e66ba1df | 7768 | For agenda display, Org mode extracts the time and displays it in a |
4009494e GM |
7769 | standard 24 hour format as part of the prefix. The example times in |
7770 | the previous paragraphs would end up in the agenda like this: | |
7771 | ||
7772 | @example | |
7773 | 8:30-13:00 Arthur Dent lies in front of the bulldozer | |
7774 | 12:45...... Ford Prefect arrives and takes Arthur to the pub | |
7775 | 19:00...... The Vogon reads his poem | |
a50253cc | 7776 | 20:30-22:15 Marvin escorts the Hitchhikers to the bridge |
4009494e GM |
7777 | @end example |
7778 | ||
7779 | @cindex time grid | |
7780 | If the agenda is in single-day mode, or for the display of today, the | |
7781 | timed entries are embedded in a time grid, like | |
7782 | ||
7783 | @example | |
7784 | 8:00...... ------------------ | |
7785 | 8:30-13:00 Arthur Dent lies in front of the bulldozer | |
7786 | 10:00...... ------------------ | |
7787 | 12:00...... ------------------ | |
7788 | 12:45...... Ford Prefect arrives and takes Arthur to the pub | |
7789 | 14:00...... ------------------ | |
7790 | 16:00...... ------------------ | |
7791 | 18:00...... ------------------ | |
7792 | 19:00...... The Vogon reads his poem | |
7793 | 20:00...... ------------------ | |
2096a1b6 | 7794 | 20:30-22:15 Marvin escorts the Hitchhikers to the bridge |
4009494e GM |
7795 | @end example |
7796 | ||
c8d0cf5c CD |
7797 | @vindex org-agenda-use-time-grid |
7798 | @vindex org-agenda-time-grid | |
4009494e GM |
7799 | The time grid can be turned on and off with the variable |
7800 | @code{org-agenda-use-time-grid}, and can be configured with | |
7801 | @code{org-agenda-time-grid}. | |
7802 | ||
7803 | @node Sorting of agenda items, , Time-of-day specifications, Presentation and sorting | |
7804 | @subsection Sorting of agenda items | |
7805 | @cindex sorting, of agenda items | |
7806 | @cindex priorities, of agenda items | |
7807 | Before being inserted into a view, the items are sorted. How this is | |
7808 | done depends on the type of view. | |
7809 | @itemize @bullet | |
7810 | @item | |
c8d0cf5c | 7811 | @vindex org-agenda-files |
4009494e GM |
7812 | For the daily/weekly agenda, the items for each day are sorted. The |
7813 | default order is to first collect all items containing an explicit | |
7814 | time-of-day specification. These entries will be shown at the beginning | |
7815 | of the list, as a @emph{schedule} for the day. After that, items remain | |
7816 | grouped in categories, in the sequence given by @code{org-agenda-files}. | |
7817 | Within each category, items are sorted by priority (@pxref{Priorities}), | |
7818 | which is composed of the base priority (2000 for priority @samp{A}, 1000 | |
7819 | for @samp{B}, and 0 for @samp{C}), plus additional increments for | |
7820 | overdue scheduled or deadline items. | |
28a16a1b | 7821 | @item |
4009494e GM |
7822 | For the TODO list, items remain in the order of categories, but within |
7823 | each category, sorting takes place according to priority | |
c8d0cf5c CD |
7824 | (@pxref{Priorities}). The priority used for sorting derives from the |
7825 | priority cookie, with additions depending on how close an item is to its due | |
7826 | or scheduled date. | |
4009494e GM |
7827 | @item |
7828 | For tags matches, items are not sorted at all, but just appear in the | |
7829 | sequence in which they are found in the agenda files. | |
7830 | @end itemize | |
7831 | ||
c8d0cf5c | 7832 | @vindex org-agenda-sorting-strategy |
4009494e | 7833 | Sorting can be customized using the variable |
a7808fba | 7834 | @code{org-agenda-sorting-strategy}, and may also include criteria based on |
71d35b24 | 7835 | the estimated effort of an entry (@pxref{Effort estimates}). |
4009494e | 7836 | |
a7808fba | 7837 | @node Agenda commands, Custom agenda views, Presentation and sorting, Agenda Views |
4009494e GM |
7838 | @section Commands in the agenda buffer |
7839 | @cindex commands, in agenda buffer | |
7840 | ||
c8d0cf5c | 7841 | Entries in the agenda buffer are linked back to the Org file or diary |
4009494e GM |
7842 | file where they originate. You are not allowed to edit the agenda |
7843 | buffer itself, but commands are provided to show and jump to the | |
c8d0cf5c | 7844 | original entry location, and to edit the Org files ``remotely'' from |
4009494e GM |
7845 | the agenda buffer. In this way, all information is stored only once, |
7846 | removing the risk that your agenda and note files may diverge. | |
7847 | ||
7848 | Some commands can be executed with mouse clicks on agenda lines. For | |
7849 | the other commands, the cursor needs to be in the desired line. | |
7850 | ||
7851 | @table @kbd | |
7852 | @tsubheading{Motion} | |
7853 | @cindex motion commands in agenda | |
acedf35c | 7854 | @orgcmd{n,org-agenda-next-line} |
801a68c8 | 7855 | Next line (same as @key{down} and @kbd{C-n}). |
acedf35c | 7856 | @orgcmd{p,org-agenda-previous-line} |
801a68c8 | 7857 | Previous line (same as @key{up} and @kbd{C-p}). |
c8d0cf5c | 7858 | @tsubheading{View/Go to Org file} |
acedf35c | 7859 | @orgcmdkkc{@key{SPC},mouse-3,org-agenda-show-and-scroll-up} |
4009494e | 7860 | Display the original location of the item in another window. |
b6cb4cd5 CD |
7861 | With prefix arg, make sure that the entire entry is made visible in the |
7862 | outline, not only the heading. | |
4009494e | 7863 | @c |
acedf35c | 7864 | @orgcmd{L,org-agenda-recenter} |
4009494e GM |
7865 | Display original location and recenter that window. |
7866 | @c | |
acedf35c CD |
7867 | @orgcmdkkc{@key{TAB},mouse-2,org-agenda-goto} |
7868 | Go to the original location of the item in another window. | |
4009494e | 7869 | @c |
acedf35c | 7870 | @orgcmd{@key{RET},org-agenda-switch-to} |
4009494e GM |
7871 | Go to the original location of the item and delete other windows. |
7872 | @c | |
acedf35c | 7873 | @orgcmd{F,org-agenda-follow-mode} |
c8d0cf5c | 7874 | @vindex org-agenda-start-with-follow-mode |
4009494e GM |
7875 | Toggle Follow mode. In Follow mode, as you move the cursor through |
7876 | the agenda buffer, the other window always shows the corresponding | |
c8d0cf5c | 7877 | location in the Org file. The initial setting for this mode in new |
4009494e GM |
7878 | agenda buffers can be set with the variable |
7879 | @code{org-agenda-start-with-follow-mode}. | |
7880 | @c | |
acedf35c | 7881 | @orgcmd{C-c C-x b,org-agenda-tree-to-indirect-buffer} |
a7808fba CD |
7882 | Display the entire subtree of the current item in an indirect buffer. With a |
7883 | numeric prefix argument N, go up to level N and then take that tree. If N is | |
7884 | negative, go up that many levels. With a @kbd{C-u} prefix, do not remove the | |
7885 | previously used indirect buffer. | |
6eb02347 | 7886 | |
acedf35c | 7887 | @orgcmd{C-c C-o,org-agenda-open-link} |
6eb02347 CD |
7888 | Follow a link in the entry. This will offer a selection of any links in the |
7889 | text belonging to the referenced Org node. If there is only one link, it | |
7890 | will be followed without a selection prompt. | |
4009494e GM |
7891 | |
7892 | @tsubheading{Change display} | |
7893 | @cindex display changing, in agenda | |
ce57c2fe BG |
7894 | @kindex A |
7895 | @item A | |
7896 | Interactively select another agenda view and append it to the current view. | |
7897 | @c | |
4009494e GM |
7898 | @kindex o |
7899 | @item o | |
7900 | Delete other windows. | |
7901 | @c | |
e4920bc9 PE |
7902 | @orgcmdkskc{v d,d,org-agenda-day-view} |
7903 | @xorgcmdkskc{v w,w,org-agenda-day-view} | |
acedf35c CD |
7904 | @xorgcmd{v m,org-agenda-month-view} |
7905 | @xorgcmd{v y,org-agenda-month-year} | |
ce57c2fe BG |
7906 | @xorgcmd{v SPC,org-agenda-reset-view} |
7907 | @vindex org-agenda-span | |
7908 | Switch to day/week/month/year view. When switching to day or week view, this | |
7909 | setting becomes the default for subsequent agenda refreshes. Since month and | |
7910 | year views are slow to create, they do not become the default. A numeric | |
7911 | prefix argument may be used to jump directly to a specific day of the year, | |
7912 | ISO week, month, or year, respectively. For example, @kbd{32 d} jumps to | |
7913 | February 1st, @kbd{9 w} to ISO week number 9. When setting day, week, or | |
7914 | month view, a year may be encoded in the prefix argument as well. For | |
7915 | example, @kbd{200712 w} will jump to week 12 in 2007. If such a year | |
7916 | specification has only one or two digits, it will be mapped to the interval | |
7917 | 1938-2037. @kbd{v @key{SPC}} will reset to what is set in | |
7918 | @code{org-agenda-span}. | |
4009494e | 7919 | @c |
acedf35c CD |
7920 | @orgcmd{f,org-agenda-later} |
7921 | Go forward in time to display the following @code{org-agenda-current-span} days. | |
6eb02347 | 7922 | For example, if the display covers a week, switch to the following week. |
acedf35c | 7923 | With prefix arg, go forward that many times @code{org-agenda-current-span} days. |
6eb02347 | 7924 | @c |
acedf35c | 7925 | @orgcmd{b,org-agenda-earlier} |
6eb02347 CD |
7926 | Go backward in time to display earlier dates. |
7927 | @c | |
acedf35c | 7928 | @orgcmd{.,org-agenda-goto-today} |
6eb02347 CD |
7929 | Go to today. |
7930 | @c | |
acedf35c | 7931 | @orgcmd{j,org-agenda-goto-date} |
6eb02347 CD |
7932 | Prompt for a date and go there. |
7933 | @c | |
acedf35c CD |
7934 | @orgcmd{J,org-agenda-clock-goto} |
7935 | Go to the currently clocked-in task @i{in the agenda buffer}. | |
afe98dfa | 7936 | @c |
acedf35c | 7937 | @orgcmd{D,org-agenda-toggle-diary} |
a7808fba | 7938 | Toggle the inclusion of diary entries. See @ref{Weekly/daily agenda}. |
4009494e | 7939 | @c |
acedf35c | 7940 | @orgcmdkskc{v l,l,org-agenda-log-mode} |
ed21c5c8 | 7941 | @kindex v L |
6eb02347 CD |
7942 | @vindex org-log-done |
7943 | @vindex org-agenda-log-mode-items | |
7944 | Toggle Logbook mode. In Logbook mode, entries that were marked DONE while | |
7945 | logging was on (variable @code{org-log-done}) are shown in the agenda, as are | |
7946 | entries that have been clocked on that day. You can configure the entry | |
7947 | types that should be included in log mode using the variable | |
7948 | @code{org-agenda-log-mode-items}. When called with a @kbd{C-u} prefix, show | |
7949 | all possible logbook entries, including state changes. When called with two | |
7950 | prefix args @kbd{C-u C-u}, show only logging information, nothing else. | |
ed21c5c8 | 7951 | @kbd{v L} is equivalent to @kbd{C-u v l}. |
6eb02347 | 7952 | @c |
acedf35c | 7953 | @orgcmdkskc{v [,[,org-agenda-manipulate-query-add} |
6eb02347 CD |
7954 | Include inactive timestamps into the current view. Only for weekly/daily |
7955 | agenda and timeline views. | |
7956 | @c | |
acedf35c CD |
7957 | @orgcmd{v a,org-agenda-archives-mode} |
7958 | @xorgcmd{v A,org-agenda-archives-mode 'files} | |
6eb02347 CD |
7959 | Toggle Archives mode. In Archives mode, trees that are marked |
7960 | @code{ARCHIVED} are also scanned when producing the agenda. When you use the | |
7961 | capital @kbd{A}, even all archive files are included. To exit archives mode, | |
7962 | press @kbd{v a} again. | |
7963 | @c | |
acedf35c | 7964 | @orgcmdkskc{v R,R,org-agenda-clockreport-mode} |
6eb02347 | 7965 | @vindex org-agenda-start-with-clockreport-mode |
e66ba1df | 7966 | @vindex org-clock-report-include-clocking-task |
6eb02347 CD |
7967 | Toggle Clockreport mode. In Clockreport mode, the daily/weekly agenda will |
7968 | always show a table with the clocked times for the timespan and file scope | |
7969 | covered by the current agenda view. The initial setting for this mode in new | |
7970 | agenda buffers can be set with the variable | |
acedf35c | 7971 | @code{org-agenda-start-with-clockreport-mode}. By using a prefix argument |
ce57c2fe | 7972 | when toggling this mode (i.e.@: @kbd{C-u R}), the clock table will not show |
acedf35c | 7973 | contributions from entries that are hidden by agenda filtering@footnote{Only |
e66ba1df BG |
7974 | tags filtering will be respected here, effort filtering is ignored.}. See |
7975 | also the variable @code{org-clock-report-include-clocking-task}. | |
6eb02347 | 7976 | @c |
ce57c2fe BG |
7977 | @orgkey{v c} |
7978 | @vindex org-agenda-clock-consistency-checks | |
7979 | Show overlapping clock entries, clocking gaps, and other clocking problems in | |
7980 | the current agenda range. You can then visit clocking lines and fix them | |
7981 | manually. See the variable @code{org-agenda-clock-consistency-checks} for | |
7982 | information on how to customize the definition of what constituted a clocking | |
7983 | problem. To return to normal agenda display, press @kbd{l} to exit Logbook | |
7984 | mode. | |
7985 | @c | |
acedf35c | 7986 | @orgcmdkskc{v E,E,org-agenda-entry-text-mode} |
6eb02347 CD |
7987 | @vindex org-agenda-start-with-entry-text-mode |
7988 | @vindex org-agenda-entry-text-maxlines | |
7989 | Toggle entry text mode. In entry text mode, a number of lines from the Org | |
7990 | outline node referenced by an agenda line will be displayed below the line. | |
7991 | The maximum number of lines is given by the variable | |
7992 | @code{org-agenda-entry-text-maxlines}. Calling this command with a numeric | |
7993 | prefix argument will temporarily modify that number to the prefix value. | |
7994 | @c | |
acedf35c | 7995 | @orgcmd{G,org-agenda-toggle-time-grid} |
c8d0cf5c CD |
7996 | @vindex org-agenda-use-time-grid |
7997 | @vindex org-agenda-time-grid | |
4009494e GM |
7998 | Toggle the time grid on and off. See also the variables |
7999 | @code{org-agenda-use-time-grid} and @code{org-agenda-time-grid}. | |
8000 | @c | |
ce57c2fe | 8001 | @orgcmd{r,org-agenda-redo} |
560bb6ea | 8002 | Recreate the agenda buffer, for example to reflect the changes after |
3bcfba17 | 8003 | modification of the timestamps of items with @kbd{S-@key{left}} and |
560bb6ea | 8004 | @kbd{S-@key{right}}. When the buffer is the global TODO list, a prefix |
4009494e GM |
8005 | argument is interpreted to create a selective list for a specific TODO |
8006 | keyword. | |
ce57c2fe | 8007 | @orgcmd{g,org-agenda-redo} |
28a16a1b | 8008 | Same as @kbd{r}. |
4009494e | 8009 | @c |
acedf35c | 8010 | @orgcmdkskc{C-x C-s,s,org-save-all-org-buffers} |
c8d0cf5c CD |
8011 | Save all Org buffers in the current Emacs session, and also the locations of |
8012 | IDs. | |
4009494e | 8013 | @c |
acedf35c | 8014 | @orgcmd{C-c C-x C-c,org-agenda-columns} |
c8d0cf5c | 8015 | @vindex org-columns-default-format |
a7808fba CD |
8016 | Invoke column view (@pxref{Column view}) in the agenda buffer. The column |
8017 | view format is taken from the entry at point, or (if there is no entry at | |
8018 | point), from the first entry in the agenda view. So whatever the format for | |
8019 | that entry would be in the original buffer (taken from a property, from a | |
8020 | @code{#+COLUMNS} line, or from the default variable | |
8021 | @code{org-columns-default-format}), will be used in the agenda. | |
4009494e | 8022 | |
acedf35c | 8023 | @orgcmd{C-c C-x >,org-agenda-remove-restriction-lock} |
c8d0cf5c CD |
8024 | Remove the restriction lock on the agenda, if it is currently restricted to a |
8025 | file or subtree (@pxref{Agenda files}). | |
8026 | ||
864c9740 | 8027 | @tsubheading{Secondary filtering and query editing} |
e66ba1df | 8028 | @cindex filtering, by tag category and effort, in agenda |
71d35b24 | 8029 | @cindex tag filtering, in agenda |
e66ba1df | 8030 | @cindex category filtering, in agenda |
71d35b24 | 8031 | @cindex effort filtering, in agenda |
28a16a1b CD |
8032 | @cindex query editing, in agenda |
8033 | ||
e66ba1df BG |
8034 | @orgcmd{<,org-agenda-filter-by-category} |
8035 | @vindex org-agenda-category-filter-preset | |
8036 | ||
8037 | Filter the current agenda view with respect to the category of the item at | |
8038 | point. Pressing @code{<} another time will remove this filter. You can add | |
8039 | a filter preset through the option @code{org-agenda-category-filter-preset} | |
8040 | (see below.) | |
8041 | ||
acedf35c | 8042 | @orgcmd{/,org-agenda-filter-by-tag} |
e66ba1df | 8043 | @vindex org-agenda-tag-filter-preset |
71d35b24 | 8044 | Filter the current agenda view with respect to a tag and/or effort estimates. |
c8d0cf5c | 8045 | The difference between this and a custom agenda command is that filtering is |
71d35b24 | 8046 | very fast, so that you can switch quickly between different filters without |
acedf35c | 8047 | having to recreate the agenda.@footnote{Custom commands can preset a filter by |
e66ba1df | 8048 | binding the variable @code{org-agenda-tag-filter-preset} as an option. This |
c8d0cf5c | 8049 | filter will then be applied to the view and persist as a basic filter through |
afe98dfa | 8050 | refreshes and more secondary filtering. The filter is a global property of |
acedf35c | 8051 | the entire agenda view---in a block agenda, you should only set this in the |
afe98dfa | 8052 | global options section, not in the section of an individual block.} |
71d35b24 | 8053 | |
acedf35c | 8054 | You will be prompted for a tag selection letter; @key{SPC} will mean any tag at |
a351880d CD |
8055 | all. Pressing @key{TAB} at that prompt will offer use completion to select a |
8056 | tag (including any tags that do not have a selection character). The command | |
8057 | then hides all entries that do not contain or inherit this tag. When called | |
8058 | with prefix arg, remove the entries that @emph{do} have the tag. A second | |
8059 | @kbd{/} at the prompt will turn off the filter and unhide any hidden entries. | |
8060 | If the first key you press is either @kbd{+} or @kbd{-}, the previous filter | |
8061 | will be narrowed by requiring or forbidding the selected additional tag. | |
8062 | Instead of pressing @kbd{+} or @kbd{-} after @kbd{/}, you can also | |
8063 | immediately use the @kbd{\} command. | |
71d35b24 | 8064 | |
c8d0cf5c | 8065 | @vindex org-sort-agenda-noeffort-is-high |
acedf35c | 8066 | In order to filter for effort estimates, you should set up allowed |
71d35b24 CD |
8067 | efforts globally, for example |
8068 | @lisp | |
8069 | (setq org-global-properties | |
8070 | '(("Effort_ALL". "0 0:10 0:30 1:00 2:00 3:00 4:00"))) | |
8071 | @end lisp | |
c8d0cf5c CD |
8072 | You can then filter for an effort by first typing an operator, one of |
8073 | @kbd{<}, @kbd{>}, and @kbd{=}, and then the one-digit index of an effort | |
8074 | estimate in your array of allowed values, where @kbd{0} means the 10th value. | |
8075 | The filter will then restrict to entries with effort smaller-or-equal, equal, | |
8076 | or larger-or-equal than the selected value. If the digits 0-9 are not used | |
8077 | as fast access keys to tags, you can also simply press the index digit | |
8078 | directly without an operator. In this case, @kbd{<} will be assumed. For | |
8079 | application of the operator, entries without a defined effort will be treated | |
8080 | according to the value of @code{org-sort-agenda-noeffort-is-high}. To filter | |
8081 | for tasks without effort definition, press @kbd{?} as the operator. | |
71d35b24 | 8082 | |
a351880d CD |
8083 | Org also supports automatic, context-aware tag filtering. If the variable |
8084 | @code{org-agenda-auto-exclude-function} is set to a user-defined function, | |
8085 | that function can decide which tags should be excluded from the agenda | |
8086 | automatically. Once this is set, the @kbd{/} command then accepts @kbd{RET} | |
8087 | as a sub-option key and runs the auto exclusion logic. For example, let's | |
8088 | say you use a @code{Net} tag to identify tasks which need network access, an | |
8089 | @code{Errand} tag for errands in town, and a @code{Call} tag for making phone | |
8090 | calls. You could auto-exclude these tags based on the availability of the | |
8091 | Internet, and outside of business hours, with something like this: | |
8092 | ||
8093 | @lisp | |
8094 | @group | |
8095 | (defun org-my-auto-exclude-function (tag) | |
8096 | (and (cond | |
c0468714 GM |
8097 | ((string= tag "Net") |
8098 | (/= 0 (call-process "/sbin/ping" nil nil nil | |
8099 | "-c1" "-q" "-t1" "mail.gnu.org"))) | |
8100 | ((or (string= tag "Errand") (string= tag "Call")) | |
8101 | (let ((hour (nth 2 (decode-time)))) | |
8102 | (or (< hour 8) (> hour 21))))) | |
a351880d CD |
8103 | (concat "-" tag))) |
8104 | ||
8105 | (setq org-agenda-auto-exclude-function 'org-my-auto-exclude-function) | |
8106 | @end group | |
8107 | @end lisp | |
8108 | ||
ce57c2fe | 8109 | @orgcmd{\\,org-agenda-filter-by-tag-refine} |
71d35b24 CD |
8110 | Narrow the current agenda filter by an additional condition. When called with |
8111 | prefix arg, remove the entries that @emph{do} have the tag, or that do match | |
8112 | the effort criterion. You can achieve the same effect by pressing @kbd{+} or | |
8113 | @kbd{-} as the first key after the @kbd{/} command. | |
864c9740 | 8114 | |
acedf35c | 8115 | @c |
28a16a1b CD |
8116 | @kindex [ |
8117 | @kindex ] | |
8118 | @kindex @{ | |
8119 | @kindex @} | |
8120 | @item [ ] @{ @} | |
6eb02347 CD |
8121 | @table @i |
8122 | @item @r{in} search view | |
8123 | add new search words (@kbd{[} and @kbd{]}) or new regular expressions | |
8124 | (@kbd{@{} and @kbd{@}}) to the query string. The opening bracket/brace will | |
8125 | add a positive search term prefixed by @samp{+}, indicating that this search | |
8126 | term @i{must} occur/match in the entry. The closing bracket/brace will add a | |
8127 | negative search term which @i{must not} occur/match in the entry for it to be | |
864c9740 | 8128 | selected. |
6eb02347 | 8129 | @end table |
28a16a1b | 8130 | |
4009494e GM |
8131 | @tsubheading{Remote editing} |
8132 | @cindex remote editing, from agenda | |
8133 | ||
8134 | @item 0-9 | |
8135 | Digit argument. | |
8136 | @c | |
8137 | @cindex undoing remote-editing events | |
8138 | @cindex remote editing, undo | |
acedf35c | 8139 | @orgcmd{C-_,org-agenda-undo} |
4009494e GM |
8140 | Undo a change due to a remote editing command. The change is undone |
8141 | both in the agenda buffer and in the remote buffer. | |
8142 | @c | |
acedf35c | 8143 | @orgcmd{t,org-agenda-todo} |
4009494e GM |
8144 | Change the TODO state of the item, both in the agenda and in the |
8145 | original org file. | |
8146 | @c | |
acedf35c CD |
8147 | @orgcmd{C-S-@key{right},org-agenda-todo-nextset} |
8148 | @orgcmd{C-S-@key{left},org-agenda-todo-previousset} | |
a351880d CD |
8149 | Switch to the next/previous set of TODO keywords. |
8150 | @c | |
acedf35c | 8151 | @orgcmd{C-k,org-agenda-kill} |
c8d0cf5c | 8152 | @vindex org-agenda-confirm-kill |
4009494e | 8153 | Delete the current agenda item along with the entire subtree belonging |
a7808fba | 8154 | to it in the original Org file. If the text to be deleted remotely |
4009494e GM |
8155 | is longer than one line, the kill needs to be confirmed by the user. See |
8156 | variable @code{org-agenda-confirm-kill}. | |
8157 | @c | |
acedf35c | 8158 | @orgcmd{C-c C-w,org-agenda-refile} |
c8d0cf5c CD |
8159 | Refile the entry at point. |
8160 | @c | |
acedf35c | 8161 | @orgcmdkskc{C-c C-x C-a,a,org-agenda-archive-default-with-confirmation} |
a351880d CD |
8162 | @vindex org-archive-default-command |
8163 | Archive the subtree corresponding to the entry at point using the default | |
8164 | archiving command set in @code{org-archive-default-command}. When using the | |
8165 | @code{a} key, confirmation will be required. | |
8166 | @c | |
acedf35c | 8167 | @orgcmd{C-c C-x a,org-agenda-toggle-archive-tag} |
a7808fba CD |
8168 | Toggle the ARCHIVE tag for the current headline. |
8169 | @c | |
acedf35c | 8170 | @orgcmd{C-c C-x A,org-agenda-archive-to-archive-sibling} |
c8d0cf5c CD |
8171 | Move the subtree corresponding to the current entry to its @emph{archive |
8172 | sibling}. | |
a7808fba | 8173 | @c |
acedf35c | 8174 | @orgcmdkskc{C-c C-x C-s,$,org-agenda-archive} |
a7808fba | 8175 | Archive the subtree corresponding to the current headline. This means the |
b349f79f | 8176 | entry will be moved to the configured archive location, most likely a |
a7808fba | 8177 | different file. |
4009494e | 8178 | @c |
acedf35c | 8179 | @orgcmd{T,org-agenda-show-tags} |
c8d0cf5c | 8180 | @vindex org-agenda-show-inherited-tags |
96c8522a CD |
8181 | Show all tags associated with the current item. This is useful if you have |
8182 | turned off @code{org-agenda-show-inherited-tags}, but still want to see all | |
8183 | tags of a headline occasionally. | |
4009494e | 8184 | @c |
acedf35c | 8185 | @orgcmd{:,org-agenda-set-tags} |
dbc28aaa CD |
8186 | Set tags for the current headline. If there is an active region in the |
8187 | agenda, change a tag for all headings in the region. | |
4009494e | 8188 | @c |
4009494e GM |
8189 | @kindex , |
8190 | @item , | |
acedf35c | 8191 | Set the priority for the current item (@command{org-agenda-priority}). |
e66ba1df | 8192 | Org mode prompts for the priority character. If you reply with @key{SPC}, |
ce57c2fe | 8193 | the priority cookie is removed from the entry. |
4009494e | 8194 | @c |
acedf35c | 8195 | @orgcmd{P,org-agenda-show-priority} |
4009494e GM |
8196 | Display weighted priority of current item. |
8197 | @c | |
acedf35c | 8198 | @orgcmdkkc{+,S-@key{up},org-agenda-priority-up} |
4009494e GM |
8199 | Increase the priority of the current item. The priority is changed in |
8200 | the original buffer, but the agenda is not resorted. Use the @kbd{r} | |
8201 | key for this. | |
8202 | @c | |
acedf35c | 8203 | @orgcmdkkc{-,S-@key{down},org-agenda-priority-down} |
4009494e GM |
8204 | Decrease the priority of the current item. |
8205 | @c | |
acedf35c | 8206 | @orgcmdkkc{z,C-c C-z,org-agenda-add-note} |
c8d0cf5c | 8207 | @vindex org-log-into-drawer |
acedf35c | 8208 | Add a note to the entry. This note will be recorded, and then filed to the |
c8d0cf5c | 8209 | same location where state change notes are put. Depending on |
acedf35c | 8210 | @code{org-log-into-drawer}, this may be inside a drawer. |
c8d0cf5c | 8211 | @c |
acedf35c | 8212 | @orgcmd{C-c C-a,org-attach} |
864c9740 CD |
8213 | Dispatcher for all command related to attachments. |
8214 | @c | |
acedf35c CD |
8215 | @orgcmd{C-c C-s,org-agenda-schedule} |
8216 | Schedule this item. With prefix arg remove the scheduling timestamp | |
4009494e | 8217 | @c |
acedf35c CD |
8218 | @orgcmd{C-c C-d,org-agenda-deadline} |
8219 | Set a deadline for this item. With prefix arg remove the deadline. | |
4009494e | 8220 | @c |
acedf35c | 8221 | @orgcmd{k,org-agenda-action} |
b349f79f CD |
8222 | Agenda actions, to set dates for selected items to the cursor date. |
8223 | This command also works in the calendar! The command prompts for an | |
a50253cc | 8224 | additional key: |
b349f79f CD |
8225 | @example |
8226 | m @r{Mark the entry at point for action. You can also make entries} | |
8227 | @r{in Org files with @kbd{C-c C-x C-k}.} | |
8228 | d @r{Set the deadline of the marked entry to the date at point.} | |
8229 | s @r{Schedule the marked entry at the date at point.} | |
86fbb8ca | 8230 | r @r{Call @code{org-capture} with the cursor date as default date.} |
b349f79f | 8231 | @end example |
c8d0cf5c | 8232 | @noindent |
a50253cc | 8233 | Press @kbd{r} afterward to refresh the agenda and see the effect of the |
b349f79f CD |
8234 | command. |
8235 | @c | |
acedf35c | 8236 | @orgcmd{S-@key{right},org-agenda-do-date-later} |
c8d0cf5c | 8237 | Change the timestamp associated with the current line by one day into the |
e66ba1df BG |
8238 | future. If the date is in the past, the first call to this command will move |
8239 | it to today.@* | |
8240 | With a numeric prefix argument, change it by that many days. For example, | |
8241 | @kbd{3 6 5 S-@key{right}} will change it by a year. With a @kbd{C-u} prefix, | |
8242 | change the time by one hour. If you immediately repeat the command, it will | |
8243 | continue to change hours even without the prefix arg. With a double @kbd{C-u | |
8244 | C-u} prefix, do the same for changing minutes.@* | |
8245 | The stamp is changed in the original Org file, but the change is not directly | |
8246 | reflected in the agenda buffer. Use @kbd{r} or @kbd{g} to update the buffer. | |
4009494e | 8247 | @c |
acedf35c | 8248 | @orgcmd{S-@key{left},org-agenda-do-date-earlier} |
c8d0cf5c | 8249 | Change the timestamp associated with the current line by one day |
4009494e GM |
8250 | into the past. |
8251 | @c | |
acedf35c | 8252 | @orgcmd{>,org-agenda-date-prompt} |
ed21c5c8 CD |
8253 | Change the timestamp associated with the current line. The key @kbd{>} has |
8254 | been chosen, because it is the same as @kbd{S-.} on my keyboard. | |
4009494e | 8255 | @c |
acedf35c | 8256 | @orgcmd{I,org-agenda-clock-in} |
4009494e GM |
8257 | Start the clock on the current item. If a clock is running already, it |
8258 | is stopped first. | |
8259 | @c | |
acedf35c | 8260 | @orgcmd{O,org-agenda-clock-out} |
4009494e GM |
8261 | Stop the previously started clock. |
8262 | @c | |
acedf35c | 8263 | @orgcmd{X,org-agenda-clock-cancel} |
4009494e | 8264 | Cancel the currently running clock. |
acedf35c CD |
8265 | @c |
8266 | @orgcmd{J,org-agenda-clock-goto} | |
dbc28aaa CD |
8267 | Jump to the running clock in another window. |
8268 | ||
c8d0cf5c CD |
8269 | @tsubheading{Bulk remote editing selected entries} |
8270 | @cindex remote editing, bulk, from agenda | |
8271 | ||
acedf35c CD |
8272 | @orgcmd{m,org-agenda-bulk-mark} |
8273 | Mark the entry at point for bulk action. With prefix arg, mark that many | |
8274 | successive entries. | |
8275 | @c | |
ce57c2fe BG |
8276 | @orgcmd{%,org-agenda-bulk-mark-regexp} |
8277 | Mark entries matching a regular expression for bulk action. | |
8278 | @c | |
acedf35c | 8279 | @orgcmd{u,org-agenda-bulk-unmark} |
c8d0cf5c | 8280 | Unmark entry for bulk action. |
acedf35c CD |
8281 | @c |
8282 | @orgcmd{U,org-agenda-bulk-remove-all-marks} | |
c8d0cf5c | 8283 | Unmark all marked entries for bulk action. |
acedf35c CD |
8284 | @c |
8285 | @orgcmd{B,org-agenda-bulk-action} | |
c8d0cf5c | 8286 | Bulk action: act on all marked entries in the agenda. This will prompt for |
ed21c5c8 CD |
8287 | another key to select the action to be applied. The prefix arg to @kbd{B} |
8288 | will be passed through to the @kbd{s} and @kbd{d} commands, to bulk-remove | |
8289 | these special timestamps. | |
c8d0cf5c CD |
8290 | @example |
8291 | r @r{Prompt for a single refile target and move all entries. The entries} | |
acedf35c | 8292 | @r{will no longer be in the agenda; refresh (@kbd{g}) to bring them back.} |
c8d0cf5c CD |
8293 | $ @r{Archive all selected entries.} |
8294 | A @r{Archive entries by moving them to their respective archive siblings.} | |
8295 | t @r{Change TODO state. This prompts for a single TODO keyword and} | |
8296 | @r{changes the state of all selected entries, bypassing blocking and} | |
ce57c2fe | 8297 | @r{suppressing logging notes (but not timestamps).} |
c8d0cf5c CD |
8298 | + @r{Add a tag to all selected entries.} |
8299 | - @r{Remove a tag from all selected entries.} | |
8300 | s @r{Schedule all items to a new date. To shift existing schedule dates} | |
8301 | @r{by a fixed number of days, use something starting with double plus} | |
8302 | @r{at the prompt, for example @samp{++8d} or @samp{++2w}.} | |
ce57c2fe BG |
8303 | S @r{Reschedule randomly into the coming N days. N will be prompted for.} |
8304 | @r{With prefix arg (@kbd{C-u B S}), scatter only across weekdays.} | |
c8d0cf5c | 8305 | d @r{Set deadline to a specific date.} |
ce57c2fe BG |
8306 | f @r{Apply a function to marked entries.} |
8307 | @r{For example, the function below sets the CATEGORY property of the} | |
8308 | @r{entries to web.} | |
8309 | @r{(defun set-category ()} | |
8310 | @r{ (interactive "P")} | |
8311 | @r{ (let* ((marker (or (org-get-at-bol 'org-hd-marker)} | |
8312 | @r{ (org-agenda-error)))} | |
8313 | @r{ (buffer (marker-buffer marker)))} | |
8314 | @r{ (with-current-buffer buffer} | |
8315 | @r{ (save-excursion} | |
8316 | @r{ (save-restriction} | |
8317 | @r{ (widen)} | |
8318 | @r{ (goto-char marker)} | |
8319 | @r{ (org-back-to-heading t)} | |
8320 | @r{ (org-set-property "CATEGORY" "web"))))))} | |
c8d0cf5c CD |
8321 | @end example |
8322 | ||
8323 | ||
4009494e GM |
8324 | @tsubheading{Calendar commands} |
8325 | @cindex calendar commands, from agenda | |
acedf35c CD |
8326 | |
8327 | @orgcmd{c,org-agenda-goto-calendar} | |
4009494e GM |
8328 | Open the Emacs calendar and move to the date at the agenda cursor. |
8329 | @c | |
acedf35c | 8330 | @orgcmd{c,org-calendar-goto-agenda} |
e66ba1df | 8331 | When in the calendar, compute and show the Org mode agenda for the |
4009494e GM |
8332 | date at the cursor. |
8333 | @c | |
8334 | @cindex diary entries, creating from agenda | |
acedf35c | 8335 | @orgcmd{i,org-agenda-diary-entry} |
a351880d CD |
8336 | @vindex org-agenda-diary-file |
8337 | Insert a new entry into the diary, using the date at the cursor and (for | |
8338 | block entries) the date at the mark. This will add to the Emacs diary | |
8339 | file@footnote{This file is parsed for the agenda when | |
8340 | @code{org-agenda-include-diary} is set.}, in a way similar to the @kbd{i} | |
8341 | command in the calendar. The diary file will pop up in another window, where | |
8342 | you can add the entry. | |
8343 | ||
e66ba1df BG |
8344 | If you configure @code{org-agenda-diary-file} to point to an Org mode file, |
8345 | Org will create entries (in Org mode syntax) in that file instead. Most | |
a351880d CD |
8346 | entries will be stored in a date-based outline tree that will later make it |
8347 | easy to archive appointments from previous months/years. The tree will be | |
86fbb8ca | 8348 | built under an entry with a @code{DATE_TREE} property, or else with years as |
acedf35c | 8349 | top-level entries. Emacs will prompt you for the entry text---if you specify |
a351880d CD |
8350 | it, the entry will be created in @code{org-agenda-diary-file} without further |
8351 | interaction. If you directly press @key{RET} at the prompt without typing | |
8352 | text, the target file will be shown in another window for you to finish the | |
8353 | entry there. See also the @kbd{k r} command. | |
4009494e | 8354 | @c |
acedf35c | 8355 | @orgcmd{M,org-agenda-phases-of-moon} |
4009494e GM |
8356 | Show the phases of the moon for the three months around current date. |
8357 | @c | |
acedf35c | 8358 | @orgcmd{S,org-agenda-sunrise-sunset} |
4009494e | 8359 | Show sunrise and sunset times. The geographical location must be set |
c8d0cf5c | 8360 | with calendar variables, see the documentation for the Emacs calendar. |
4009494e | 8361 | @c |
acedf35c | 8362 | @orgcmd{C,org-agenda-convert-date} |
4009494e GM |
8363 | Convert the date at cursor into many other cultural and historic |
8364 | calendars. | |
8365 | @c | |
acedf35c | 8366 | @orgcmd{H,org-agenda-holidays} |
c8d0cf5c | 8367 | Show holidays for three months around the cursor date. |
a7808fba CD |
8368 | |
8369 | @item M-x org-export-icalendar-combine-agenda-files | |
4009494e | 8370 | Export a single iCalendar file containing entries from all agenda files. |
a7808fba | 8371 | This is a globally available command, and also available in the agenda menu. |
4009494e GM |
8372 | |
8373 | @tsubheading{Exporting to a file} | |
acedf35c | 8374 | @orgcmd{C-x C-w,org-write-agenda} |
4009494e GM |
8375 | @cindex exporting agenda views |
8376 | @cindex agenda views, exporting | |
c8d0cf5c CD |
8377 | @vindex org-agenda-exporter-settings |
8378 | Write the agenda view to a file. Depending on the extension of the selected | |
8379 | file name, the view will be exported as HTML (extension @file{.html} or | |
e66ba1df | 8380 | @file{.htm}), Postscript (extension @file{.ps}), PDF (extension @file{.pdf}), |
a351880d CD |
8381 | and plain text (any other extension). When called with a @kbd{C-u} prefix |
8382 | argument, immediately open the newly created file. Use the variable | |
8383 | @code{org-agenda-exporter-settings} to set options for @file{ps-print} and | |
8384 | for @file{htmlize} to be used during export. | |
4009494e GM |
8385 | |
8386 | @tsubheading{Quit and Exit} | |
acedf35c | 8387 | @orgcmd{q,org-agenda-quit} |
4009494e GM |
8388 | Quit agenda, remove the agenda buffer. |
8389 | @c | |
4009494e | 8390 | @cindex agenda files, removing buffers |
acedf35c | 8391 | @orgcmd{x,org-agenda-exit} |
4009494e GM |
8392 | Exit agenda, remove the agenda buffer and all buffers loaded by Emacs |
8393 | for the compilation of the agenda. Buffers created by the user to | |
c8d0cf5c | 8394 | visit Org files will not be removed. |
4009494e GM |
8395 | @end table |
8396 | ||
8397 | ||
c8d0cf5c | 8398 | @node Custom agenda views, Exporting Agenda Views, Agenda commands, Agenda Views |
4009494e GM |
8399 | @section Custom agenda views |
8400 | @cindex custom agenda views | |
8401 | @cindex agenda views, custom | |
8402 | ||
8403 | Custom agenda commands serve two purposes: to store and quickly access | |
8404 | frequently used TODO and tags searches, and to create special composite | |
8405 | agenda buffers. Custom agenda commands will be accessible through the | |
8406 | dispatcher (@pxref{Agenda dispatcher}), just like the default commands. | |
8407 | ||
8408 | @menu | |
c0468714 GM |
8409 | * Storing searches:: Type once, use often |
8410 | * Block agenda:: All the stuff you need in a single buffer | |
8411 | * Setting Options:: Changing the rules | |
4009494e GM |
8412 | @end menu |
8413 | ||
8414 | @node Storing searches, Block agenda, Custom agenda views, Custom agenda views | |
8415 | @subsection Storing searches | |
8416 | ||
8417 | The first application of custom searches is the definition of keyboard | |
8418 | shortcuts for frequently used searches, either creating an agenda | |
8419 | buffer, or a sparse tree (the latter covering of course only the current | |
8420 | buffer). | |
8421 | @kindex C-c a C | |
c8d0cf5c | 8422 | @vindex org-agenda-custom-commands |
4009494e GM |
8423 | Custom commands are configured in the variable |
8424 | @code{org-agenda-custom-commands}. You can customize this variable, for | |
8425 | example by pressing @kbd{C-c a C}. You can also directly set it with | |
8426 | Emacs Lisp in @file{.emacs}. The following example contains all valid | |
8427 | search types: | |
8428 | ||
8429 | @lisp | |
8430 | @group | |
8431 | (setq org-agenda-custom-commands | |
8432 | '(("w" todo "WAITING") | |
8433 | ("W" todo-tree "WAITING") | |
dbc28aaa CD |
8434 | ("u" tags "+boss-urgent") |
8435 | ("v" tags-todo "+boss-urgent") | |
8436 | ("U" tags-tree "+boss-urgent") | |
8437 | ("f" occur-tree "\\<FIXME\\>") | |
8438 | ("h" . "HOME+Name tags searches") ; description for "h" prefix | |
8439 | ("hl" tags "+home+Lisa") | |
8440 | ("hp" tags "+home+Peter") | |
8441 | ("hk" tags "+home+Kim"))) | |
4009494e GM |
8442 | @end group |
8443 | @end lisp | |
8444 | ||
8445 | @noindent | |
dbc28aaa CD |
8446 | The initial string in each entry defines the keys you have to press |
8447 | after the dispatcher command @kbd{C-c a} in order to access the command. | |
8448 | Usually this will be just a single character, but if you have many | |
8449 | similar commands, you can also define two-letter combinations where the | |
8450 | first character is the same in several combinations and serves as a | |
8451 | prefix key@footnote{You can provide a description for a prefix key by | |
8452 | inserting a cons cell with the prefix and the description.}. The second | |
8453 | parameter is the search type, followed by the string or regular | |
8454 | expression to be used for the matching. The example above will | |
8455 | therefore define: | |
4009494e GM |
8456 | |
8457 | @table @kbd | |
8458 | @item C-c a w | |
8459 | as a global search for TODO entries with @samp{WAITING} as the TODO | |
8460 | keyword | |
8461 | @item C-c a W | |
8462 | as the same search, but only in the current buffer and displaying the | |
8463 | results as a sparse tree | |
8464 | @item C-c a u | |
dbc28aaa CD |
8465 | as a global tags search for headlines marked @samp{:boss:} but not |
8466 | @samp{:urgent:} | |
4009494e GM |
8467 | @item C-c a v |
8468 | as the same search as @kbd{C-c a u}, but limiting the search to | |
8469 | headlines that are also TODO items | |
8470 | @item C-c a U | |
8471 | as the same search as @kbd{C-c a u}, but only in the current buffer and | |
8472 | displaying the result as a sparse tree | |
8473 | @item C-c a f | |
8474 | to create a sparse tree (again: current buffer only) with all entries | |
dbc28aaa CD |
8475 | containing the word @samp{FIXME} |
8476 | @item C-c a h | |
8477 | as a prefix command for a HOME tags search where you have to press an | |
8478 | additional key (@kbd{l}, @kbd{p} or @kbd{k}) to select a name (Lisa, | |
8479 | Peter, or Kim) as additional tag to match. | |
4009494e GM |
8480 | @end table |
8481 | ||
8482 | @node Block agenda, Setting Options, Storing searches, Custom agenda views | |
8483 | @subsection Block agenda | |
8484 | @cindex block agenda | |
8485 | @cindex agenda, with block views | |
8486 | ||
8487 | Another possibility is the construction of agenda views that comprise | |
8488 | the results of @emph{several} commands, each of which creates a block in | |
8489 | the agenda buffer. The available commands include @code{agenda} for the | |
8490 | daily or weekly agenda (as created with @kbd{C-c a a}), @code{alltodo} | |
a7808fba | 8491 | for the global TODO list (as constructed with @kbd{C-c a t}), and the |
4009494e GM |
8492 | matching commands discussed above: @code{todo}, @code{tags}, and |
8493 | @code{tags-todo}. Here are two examples: | |
8494 | ||
8495 | @lisp | |
8496 | @group | |
8497 | (setq org-agenda-custom-commands | |
8498 | '(("h" "Agenda and Home-related tasks" | |
28a16a1b | 8499 | ((agenda "") |
dbc28aaa CD |
8500 | (tags-todo "home") |
8501 | (tags "garden"))) | |
4009494e | 8502 | ("o" "Agenda and Office-related tasks" |
28a16a1b | 8503 | ((agenda "") |
dbc28aaa CD |
8504 | (tags-todo "work") |
8505 | (tags "office"))))) | |
4009494e GM |
8506 | @end group |
8507 | @end lisp | |
8508 | ||
8509 | @noindent | |
8510 | This will define @kbd{C-c a h} to create a multi-block view for stuff | |
8511 | you need to attend to at home. The resulting agenda buffer will contain | |
8512 | your agenda for the current week, all TODO items that carry the tag | |
dbc28aaa | 8513 | @samp{home}, and also all lines tagged with @samp{garden}. Finally the |
4009494e GM |
8514 | command @kbd{C-c a o} provides a similar view for office tasks. |
8515 | ||
c8d0cf5c | 8516 | @node Setting Options, , Block agenda, Custom agenda views |
a7808fba | 8517 | @subsection Setting options for custom commands |
4009494e GM |
8518 | @cindex options, for custom agenda views |
8519 | ||
c8d0cf5c | 8520 | @vindex org-agenda-custom-commands |
e66ba1df | 8521 | Org mode contains a number of variables regulating agenda construction |
4009494e GM |
8522 | and display. The global variables define the behavior for all agenda |
8523 | commands, including the custom commands. However, if you want to change | |
8524 | some settings just for a single custom view, you can do so. Setting | |
8525 | options requires inserting a list of variable names and values at the | |
8526 | right spot in @code{org-agenda-custom-commands}. For example: | |
8527 | ||
8528 | @lisp | |
8529 | @group | |
8530 | (setq org-agenda-custom-commands | |
8531 | '(("w" todo "WAITING" | |
8532 | ((org-agenda-sorting-strategy '(priority-down)) | |
8533 | (org-agenda-prefix-format " Mixed: "))) | |
dbc28aaa | 8534 | ("U" tags-tree "+boss-urgent" |
4009494e | 8535 | ((org-show-following-heading nil) |
28a16a1b CD |
8536 | (org-show-hierarchy-above nil))) |
8537 | ("N" search "" | |
8538 | ((org-agenda-files '("~org/notes.org")) | |
8539 | (org-agenda-text-search-extra-files nil))))) | |
4009494e GM |
8540 | @end group |
8541 | @end lisp | |
8542 | ||
8543 | @noindent | |
8544 | Now the @kbd{C-c a w} command will sort the collected entries only by | |
dbc28aaa | 8545 | priority, and the prefix format is modified to just say @samp{ Mixed: } |
4009494e GM |
8546 | instead of giving the category of the entry. The sparse tags tree of |
8547 | @kbd{C-c a U} will now turn out ultra-compact, because neither the | |
8548 | headline hierarchy above the match, nor the headline following the match | |
28a16a1b CD |
8549 | will be shown. The command @kbd{C-c a N} will do a text search limited |
8550 | to only a single file. | |
4009494e | 8551 | |
c8d0cf5c | 8552 | @vindex org-agenda-custom-commands |
4009494e GM |
8553 | For command sets creating a block agenda, |
8554 | @code{org-agenda-custom-commands} has two separate spots for setting | |
8555 | options. You can add options that should be valid for just a single | |
8556 | command in the set, and options that should be valid for all commands in | |
acedf35c | 8557 | the set. The former are just added to the command entry; the latter |
4009494e GM |
8558 | must come after the list of command entries. Going back to the block |
8559 | agenda example (@pxref{Block agenda}), let's change the sorting strategy | |
8560 | for the @kbd{C-c a h} commands to @code{priority-down}, but let's sort | |
8561 | the results for GARDEN tags query in the opposite order, | |
8562 | @code{priority-up}. This would look like this: | |
8563 | ||
8564 | @lisp | |
8565 | @group | |
8566 | (setq org-agenda-custom-commands | |
8567 | '(("h" "Agenda and Home-related tasks" | |
8568 | ((agenda) | |
dbc28aaa CD |
8569 | (tags-todo "home") |
8570 | (tags "garden" | |
4009494e GM |
8571 | ((org-agenda-sorting-strategy '(priority-up))))) |
8572 | ((org-agenda-sorting-strategy '(priority-down)))) | |
8573 | ("o" "Agenda and Office-related tasks" | |
8574 | ((agenda) | |
dbc28aaa CD |
8575 | (tags-todo "work") |
8576 | (tags "office"))))) | |
4009494e GM |
8577 | @end group |
8578 | @end lisp | |
8579 | ||
c8d0cf5c CD |
8580 | As you see, the values and parentheses setting is a little complex. |
8581 | When in doubt, use the customize interface to set this variable---it | |
8582 | fully supports its structure. Just one caveat: when setting options in | |
8583 | this interface, the @emph{values} are just Lisp expressions. So if the | |
8584 | value is a string, you need to add the double-quotes around the value | |
4009494e GM |
8585 | yourself. |
8586 | ||
8587 | ||
c8d0cf5c CD |
8588 | @node Exporting Agenda Views, Agenda column view, Custom agenda views, Agenda Views |
8589 | @section Exporting Agenda Views | |
4009494e GM |
8590 | @cindex agenda views, exporting |
8591 | ||
3da3282e | 8592 | If you are away from your computer, it can be very useful to have a printed |
e66ba1df | 8593 | version of some agenda views to carry around. Org mode can export custom |
3da3282e | 8594 | agenda views as plain text, HTML@footnote{You need to install Hrvoje Niksic's |
e66ba1df | 8595 | @file{htmlize.el}.}, Postscript, PDF@footnote{To create PDF output, the |
c8d0cf5c | 8596 | ghostscript @file{ps2pdf} utility must be installed on the system. Selecting |
e66ba1df | 8597 | a PDF file will also create the postscript file.}, and iCalendar files. If |
c8d0cf5c | 8598 | you want to do this only occasionally, use the command |
4009494e GM |
8599 | |
8600 | @table @kbd | |
acedf35c | 8601 | @orgcmd{C-x C-w,org-write-agenda} |
4009494e GM |
8602 | @cindex exporting agenda views |
8603 | @cindex agenda views, exporting | |
c8d0cf5c | 8604 | @vindex org-agenda-exporter-settings |
7006d207 CD |
8605 | Write the agenda view to a file. Depending on the extension of the selected |
8606 | file name, the view will be exported as HTML (extension @file{.html} or | |
e66ba1df | 8607 | @file{.htm}), Postscript (extension @file{.ps}), iCalendar (extension |
a351880d CD |
8608 | @file{.ics}), or plain text (any other extension). Use the variable |
8609 | @code{org-agenda-exporter-settings} to set options for @file{ps-print} and | |
8610 | for @file{htmlize} to be used during export, for example | |
28a16a1b | 8611 | |
c8d0cf5c CD |
8612 | @vindex org-agenda-add-entry-text-maxlines |
8613 | @vindex htmlize-output-type | |
8614 | @vindex ps-number-of-columns | |
8615 | @vindex ps-landscape-mode | |
4009494e GM |
8616 | @lisp |
8617 | (setq org-agenda-exporter-settings | |
8618 | '((ps-number-of-columns 2) | |
8619 | (ps-landscape-mode t) | |
c8d0cf5c | 8620 | (org-agenda-add-entry-text-maxlines 5) |
4009494e GM |
8621 | (htmlize-output-type 'css))) |
8622 | @end lisp | |
8623 | @end table | |
8624 | ||
8625 | If you need to export certain agenda views frequently, you can associate | |
8626 | any custom agenda command with a list of output file names | |
8627 | @footnote{If you want to store standard views like the weekly agenda | |
8628 | or the global TODO list as well, you need to define custom commands for | |
28a16a1b | 8629 | them in order to be able to specify file names.}. Here is an example |
c8d0cf5c CD |
8630 | that first defines custom commands for the agenda and the global |
8631 | TODO list, together with a number of files to which to export them. | |
28a16a1b | 8632 | Then we define two block agenda commands and specify file names for them |
4009494e GM |
8633 | as well. File names can be relative to the current working directory, |
8634 | or absolute. | |
8635 | ||
8636 | @lisp | |
8637 | @group | |
8638 | (setq org-agenda-custom-commands | |
8639 | '(("X" agenda "" nil ("agenda.html" "agenda.ps")) | |
8640 | ("Y" alltodo "" nil ("todo.html" "todo.txt" "todo.ps")) | |
8641 | ("h" "Agenda and Home-related tasks" | |
28a16a1b | 8642 | ((agenda "") |
dbc28aaa CD |
8643 | (tags-todo "home") |
8644 | (tags "garden")) | |
4009494e GM |
8645 | nil |
8646 | ("~/views/home.html")) | |
8647 | ("o" "Agenda and Office-related tasks" | |
8648 | ((agenda) | |
dbc28aaa CD |
8649 | (tags-todo "work") |
8650 | (tags "office")) | |
4009494e | 8651 | nil |
28a16a1b | 8652 | ("~/views/office.ps" "~/calendars/office.ics")))) |
4009494e GM |
8653 | @end group |
8654 | @end lisp | |
8655 | ||
8656 | The extension of the file name determines the type of export. If it is | |
e66ba1df | 8657 | @file{.html}, Org mode will use the @file{htmlize.el} package to convert |
4009494e GM |
8658 | the buffer to HTML and save it to this file name. If the extension is |
8659 | @file{.ps}, @code{ps-print-buffer-with-faces} is used to produce | |
e66ba1df | 8660 | Postscript output. If the extension is @file{.ics}, iCalendar export is |
28a16a1b | 8661 | run export over all files that were used to construct the agenda, and |
c8d0cf5c | 8662 | limit the export to entries listed in the agenda. Any other |
28a16a1b | 8663 | extension produces a plain ASCII file. |
4009494e GM |
8664 | |
8665 | The export files are @emph{not} created when you use one of those | |
28a16a1b CD |
8666 | commands interactively because this might use too much overhead. |
8667 | Instead, there is a special command to produce @emph{all} specified | |
8668 | files in one step: | |
4009494e GM |
8669 | |
8670 | @table @kbd | |
acedf35c | 8671 | @orgcmd{C-c a e,org-store-agenda-views} |
28a16a1b | 8672 | Export all agenda views that have export file names associated with |
4009494e GM |
8673 | them. |
8674 | @end table | |
8675 | ||
8676 | You can use the options section of the custom agenda commands to also | |
8677 | set options for the export commands. For example: | |
8678 | ||
8679 | @lisp | |
8680 | (setq org-agenda-custom-commands | |
8681 | '(("X" agenda "" | |
8682 | ((ps-number-of-columns 2) | |
8683 | (ps-landscape-mode t) | |
8684 | (org-agenda-prefix-format " [ ] ") | |
8685 | (org-agenda-with-colors nil) | |
8686 | (org-agenda-remove-tags t)) | |
8687 | ("theagenda.ps")))) | |
8688 | @end lisp | |
8689 | ||
8690 | @noindent | |
e66ba1df | 8691 | This command sets two options for the Postscript exporter, to make it |
c8d0cf5c | 8692 | print in two columns in landscape format---the resulting page can be cut |
4009494e GM |
8693 | in two and then used in a paper agenda. The remaining settings modify |
8694 | the agenda prefix to omit category and scheduling information, and | |
8695 | instead include a checkbox to check off items. We also remove the tags | |
8696 | to make the lines compact, and we don't want to use colors for the | |
8697 | black-and-white printer. Settings specified in | |
8698 | @code{org-agenda-exporter-settings} will also apply, but the settings | |
8699 | in @code{org-agenda-custom-commands} take precedence. | |
8700 | ||
8701 | @noindent | |
8702 | From the command line you may also use | |
8703 | @example | |
e66ba1df | 8704 | emacs -eval (org-batch-store-agenda-views) -kill |
4009494e GM |
8705 | @end example |
8706 | @noindent | |
c8d0cf5c CD |
8707 | or, if you need to modify some parameters@footnote{Quoting depends on the |
8708 | system you use, please check the FAQ for examples.} | |
4009494e GM |
8709 | @example |
8710 | emacs -eval '(org-batch-store-agenda-views \ | |
e66ba1df | 8711 | org-agenda-span (quote month) \ |
dbc28aaa | 8712 | org-agenda-start-day "2007-11-01" \ |
4009494e GM |
8713 | org-agenda-include-diary nil \ |
8714 | org-agenda-files (quote ("~/org/project.org")))' \ | |
8715 | -kill | |
8716 | @end example | |
8717 | @noindent | |
8718 | which will create the agenda views restricted to the file | |
c8d0cf5c | 8719 | @file{~/org/project.org}, without diary entries and with a 30-day |
28a16a1b | 8720 | extent. |
4009494e | 8721 | |
c8d0cf5c CD |
8722 | You can also extract agenda information in a way that allows further |
8723 | processing by other programs. See @ref{Extracting agenda information}, for | |
8724 | more information. | |
4009494e | 8725 | |
4009494e | 8726 | |
c8d0cf5c | 8727 | @node Agenda column view, , Exporting Agenda Views, Agenda Views |
a7808fba CD |
8728 | @section Using column view in the agenda |
8729 | @cindex column view, in agenda | |
8730 | @cindex agenda, column view | |
8731 | ||
8732 | Column view (@pxref{Column view}) is normally used to view and edit | |
8733 | properties embedded in the hierarchical structure of an Org file. It can be | |
8734 | quite useful to use column view also from the agenda, where entries are | |
8735 | collected by certain criteria. | |
8736 | ||
8737 | @table @kbd | |
acedf35c | 8738 | @orgcmd{C-c C-x C-c,org-agenda-columns} |
a7808fba CD |
8739 | Turn on column view in the agenda. |
8740 | @end table | |
8741 | ||
8742 | To understand how to use this properly, it is important to realize that the | |
8743 | entries in the agenda are no longer in their proper outline environment. | |
8744 | This causes the following issues: | |
8745 | ||
8746 | @enumerate | |
8747 | @item | |
c8d0cf5c CD |
8748 | @vindex org-columns-default-format |
8749 | @vindex org-overriding-columns-format | |
a7808fba CD |
8750 | Org needs to make a decision which @code{COLUMNS} format to use. Since the |
8751 | entries in the agenda are collected from different files, and different files | |
8752 | may have different @code{COLUMNS} formats, this is a non-trivial problem. | |
ce57c2fe | 8753 | Org first checks if the variable @code{org-agenda-overriding-columns-format} is |
c8d0cf5c | 8754 | currently set, and if so, takes the format from there. Otherwise it takes |
a7808fba | 8755 | the format associated with the first item in the agenda, or, if that item |
c8d0cf5c | 8756 | does not have a specific format (defined in a property, or in its file), it |
a7808fba CD |
8757 | uses @code{org-columns-default-format}. |
8758 | @item | |
c8d0cf5c | 8759 | @cindex property, special, CLOCKSUM |
a7808fba CD |
8760 | If any of the columns has a summary type defined (@pxref{Column attributes}), |
8761 | turning on column view in the agenda will visit all relevant agenda files and | |
8762 | make sure that the computations of this property are up to date. This is | |
8763 | also true for the special @code{CLOCKSUM} property. Org will then sum the | |
8764 | values displayed in the agenda. In the daily/weekly agenda, the sums will | |
acedf35c | 8765 | cover a single day; in all other views they cover the entire block. It is |
a7808fba CD |
8766 | vital to realize that the agenda may show the same entry @emph{twice} (for |
8767 | example as scheduled and as a deadline), and it may show two entries from the | |
c8d0cf5c | 8768 | same hierarchy (for example a @emph{parent} and its @emph{child}). In these |
a7808fba CD |
8769 | cases, the summation in the agenda will lead to incorrect results because |
8770 | some values will count double. | |
8771 | @item | |
8772 | When the column view in the agenda shows the @code{CLOCKSUM}, that is always | |
8773 | the entire clocked time for this item. So even in the daily/weekly agenda, | |
8774 | the clocksum listed in column view may originate from times outside the | |
8775 | current view. This has the advantage that you can compare these values with | |
c8d0cf5c | 8776 | a column listing the planned total effort for a task---one of the major |
a7808fba CD |
8777 | applications for column view in the agenda. If you want information about |
8778 | clocked time in the displayed period use clock table mode (press @kbd{R} in | |
8779 | the agenda). | |
8780 | @end enumerate | |
8781 | ||
8782 | ||
a351880d CD |
8783 | @node Markup, Exporting, Agenda Views, Top |
8784 | @chapter Markup for rich export | |
4009494e | 8785 | |
e66ba1df | 8786 | When exporting Org mode documents, the exporter tries to reflect the |
a351880d | 8787 | structure of the document as accurately as possible in the backend. Since |
acedf35c | 8788 | export targets like HTML, @LaTeX{}, or DocBook allow much richer formatting, |
e66ba1df BG |
8789 | Org mode has rules on how to prepare text for rich export. This section |
8790 | summarizes the markup rules used in an Org mode buffer. | |
4009494e | 8791 | |
a351880d | 8792 | @menu |
c0468714 GM |
8793 | * Structural markup elements:: The basic structure as seen by the exporter |
8794 | * Images and tables:: Tables and Images will be included | |
8795 | * Literal examples:: Source code examples with special formatting | |
8796 | * Include files:: Include additional files into a document | |
8797 | * Index entries:: Making an index | |
8798 | * Macro replacement:: Use macros to create complex output | |
e66ba1df | 8799 | * Embedded @LaTeX{}:: LaTeX can be freely used inside Org documents |
a351880d CD |
8800 | @end menu |
8801 | ||
8802 | @node Structural markup elements, Images and tables, Markup, Markup | |
8803 | @section Structural markup elements | |
4009494e GM |
8804 | |
8805 | @menu | |
c0468714 GM |
8806 | * Document title:: Where the title is taken from |
8807 | * Headings and sections:: The document structure as seen by the exporter | |
8808 | * Table of contents:: The if and where of the table of contents | |
8809 | * Initial text:: Text before the first heading? | |
8810 | * Lists:: Lists | |
8811 | * Paragraphs:: Paragraphs | |
8812 | * Footnote markup:: Footnotes | |
8813 | * Emphasis and monospace:: Bold, italic, etc. | |
8814 | * Horizontal rules:: Make a line | |
8815 | * Comment lines:: What will *not* be exported | |
4009494e GM |
8816 | @end menu |
8817 | ||
a351880d CD |
8818 | @node Document title, Headings and sections, Structural markup elements, Structural markup elements |
8819 | @subheading Document title | |
8820 | @cindex document title, markup rules | |
4009494e | 8821 | |
a351880d CD |
8822 | @noindent |
8823 | The title of the exported document is taken from the special line | |
4009494e | 8824 | |
a351880d | 8825 | @cindex #+TITLE |
4009494e | 8826 | @example |
a351880d | 8827 | #+TITLE: This is the title of the document |
4009494e | 8828 | @end example |
a351880d | 8829 | |
c8d0cf5c | 8830 | @noindent |
a351880d CD |
8831 | If this line does not exist, the title is derived from the first non-empty, |
8832 | non-comment line in the buffer. If no such line exists, or if you have | |
8833 | turned off exporting of the text before the first headline (see below), the | |
8834 | title will be the file name without extension. | |
4009494e | 8835 | |
a351880d CD |
8836 | @cindex property, EXPORT_TITLE |
8837 | If you are exporting only a subtree by marking is as the region, the heading | |
8838 | of the subtree will become the title of the document. If the subtree has a | |
8839 | property @code{EXPORT_TITLE}, that will take precedence. | |
4009494e | 8840 | |
a351880d CD |
8841 | @node Headings and sections, Table of contents, Document title, Structural markup elements |
8842 | @subheading Headings and sections | |
8843 | @cindex headings and sections, markup rules | |
8844 | ||
8845 | @vindex org-export-headline-levels | |
8846 | The outline structure of the document as described in @ref{Document | |
8847 | Structure}, forms the basis for defining sections of the exported document. | |
8848 | However, since the outline structure is also used for (for example) lists of | |
8849 | tasks, only the first three outline levels will be used as headings. Deeper | |
8850 | levels will become itemized lists. You can change the location of this | |
8851 | switch globally by setting the variable @code{org-export-headline-levels}, or on a | |
8852 | per-file basis with a line | |
4009494e | 8853 | |
a351880d | 8854 | @cindex #+OPTIONS |
4009494e | 8855 | @example |
a351880d | 8856 | #+OPTIONS: H:4 |
4009494e GM |
8857 | @end example |
8858 | ||
a351880d CD |
8859 | @node Table of contents, Initial text, Headings and sections, Structural markup elements |
8860 | @subheading Table of contents | |
8861 | @cindex table of contents, markup rules | |
4009494e | 8862 | |
a351880d CD |
8863 | @vindex org-export-with-toc |
8864 | The table of contents is normally inserted directly before the first headline | |
8865 | of the file. If you would like to get it to a different location, insert the | |
8866 | string @code{[TABLE-OF-CONTENTS]} on a line by itself at the desired | |
8867 | location. The depth of the table of contents is by default the same as the | |
8868 | number of headline levels, but you can choose a smaller number, or turn off | |
8869 | the table of contents entirely, by configuring the variable | |
8870 | @code{org-export-with-toc}, or on a per-file basis with a line like | |
b349f79f CD |
8871 | |
8872 | @example | |
8873 | #+OPTIONS: toc:2 (only to two levels in TOC) | |
8874 | #+OPTIONS: toc:nil (no TOC at all) | |
8875 | @end example | |
8876 | ||
a351880d | 8877 | @node Initial text, Lists, Table of contents, Structural markup elements |
b349f79f CD |
8878 | @subheading Text before the first headline |
8879 | @cindex text before first headline, markup rules | |
8880 | @cindex #+TEXT | |
8881 | ||
e66ba1df | 8882 | Org mode normally exports the text before the first headline, and even uses |
b349f79f | 8883 | the first line as the document title. The text will be fully marked up. If |
acedf35c | 8884 | you need to include literal HTML, @LaTeX{}, or DocBook code, use the special |
c8d0cf5c | 8885 | constructs described below in the sections for the individual exporters. |
b349f79f | 8886 | |
c8d0cf5c | 8887 | @vindex org-export-skip-text-before-1st-heading |
b349f79f CD |
8888 | Some people like to use the space before the first headline for setup and |
8889 | internal links and therefore would like to control the exported text before | |
8890 | the first headline in a different way. You can do so by setting the variable | |
8891 | @code{org-export-skip-text-before-1st-heading} to @code{t}. On a per-file | |
8892 | basis, you can get the same effect with @samp{#+OPTIONS: skip:t}. | |
8893 | ||
8894 | @noindent | |
8895 | If you still want to have some text before the first headline, use the | |
8896 | @code{#+TEXT} construct: | |
8897 | ||
8898 | @example | |
8899 | #+OPTIONS: skip:t | |
8900 | #+TEXT: This text will go before the *first* headline. | |
8901 | #+TEXT: [TABLE-OF-CONTENTS] | |
ce57c2fe | 8902 | #+TEXT: This goes between the table of contents and the *first* headline |
b349f79f CD |
8903 | @end example |
8904 | ||
a351880d | 8905 | @node Lists, Paragraphs, Initial text, Structural markup elements |
b349f79f CD |
8906 | @subheading Lists |
8907 | @cindex lists, markup rules | |
8908 | ||
c8d0cf5c CD |
8909 | Plain lists as described in @ref{Plain lists}, are translated to the backend's |
8910 | syntax for such lists. Most backends support unordered, ordered, and | |
b349f79f CD |
8911 | description lists. |
8912 | ||
a351880d | 8913 | @node Paragraphs, Footnote markup, Lists, Structural markup elements |
b349f79f CD |
8914 | @subheading Paragraphs, line breaks, and quoting |
8915 | @cindex paragraphs, markup rules | |
8916 | ||
8917 | Paragraphs are separated by at least one empty line. If you need to enforce | |
8918 | a line break within a paragraph, use @samp{\\} at the end of a line. | |
8919 | ||
8920 | To keep the line breaks in a region, but otherwise use normal formatting, you | |
8921 | can use this construct, which can also be used to format poetry. | |
8922 | ||
c8d0cf5c | 8923 | @cindex #+BEGIN_VERSE |
b349f79f CD |
8924 | @example |
8925 | #+BEGIN_VERSE | |
864c9740 CD |
8926 | Great clouds overhead |
8927 | Tiny black birds rise and fall | |
8928 | Snow covers Emacs | |
96c8522a | 8929 | |
864c9740 | 8930 | -- AlexSchroeder |
b349f79f CD |
8931 | #+END_VERSE |
8932 | @end example | |
8933 | ||
8934 | When quoting a passage from another document, it is customary to format this | |
8935 | as a paragraph that is indented on both the left and the right margin. You | |
e66ba1df | 8936 | can include quotations in Org mode documents like this: |
b349f79f | 8937 | |
c8d0cf5c | 8938 | @cindex #+BEGIN_QUOTE |
b349f79f CD |
8939 | @example |
8940 | #+BEGIN_QUOTE | |
8941 | Everything should be made as simple as possible, | |
8942 | but not any simpler -- Albert Einstein | |
8943 | #+END_QUOTE | |
8944 | @end example | |
8945 | ||
c8d0cf5c CD |
8946 | If you would like to center some text, do it like this: |
8947 | @cindex #+BEGIN_CENTER | |
8948 | @example | |
8949 | #+BEGIN_CENTER | |
8950 | Everything should be made as simple as possible, \\ | |
8951 | but not any simpler | |
8952 | #+END_CENTER | |
8953 | @end example | |
b349f79f | 8954 | |
a351880d CD |
8955 | |
8956 | @node Footnote markup, Emphasis and monospace, Paragraphs, Structural markup elements | |
8957 | @subheading Footnote markup | |
8958 | @cindex footnotes, markup rules | |
8959 | @cindex @file{footnote.el} | |
8960 | ||
ce57c2fe BG |
8961 | Footnotes defined in the way described in @ref{Footnotes}, will be exported |
8962 | by all backends. Org allows multiple references to the same note, and | |
8963 | multiple footnotes side by side. | |
a351880d CD |
8964 | |
8965 | @node Emphasis and monospace, Horizontal rules, Footnote markup, Structural markup elements | |
8966 | @subheading Emphasis and monospace | |
8967 | ||
8968 | @cindex underlined text, markup rules | |
8969 | @cindex bold text, markup rules | |
8970 | @cindex italic text, markup rules | |
8971 | @cindex verbatim text, markup rules | |
8972 | @cindex code text, markup rules | |
8973 | @cindex strike-through text, markup rules | |
8974 | You can make words @b{*bold*}, @i{/italic/}, _underlined_, @code{=code=} | |
8975 | and @code{~verbatim~}, and, if you must, @samp{+strike-through+}. Text | |
e66ba1df | 8976 | in the code and verbatim string is not processed for Org mode specific |
acedf35c | 8977 | syntax; it is exported verbatim. |
a351880d CD |
8978 | |
8979 | @node Horizontal rules, Comment lines, Emphasis and monospace, Structural markup elements | |
8980 | @subheading Horizontal rules | |
8981 | @cindex horizontal rules, markup rules | |
ce57c2fe BG |
8982 | A line consisting of only dashes, and at least 5 of them, will be exported as |
8983 | a horizontal line (@samp{<hr/>} in HTML and @code{\hrule} in @LaTeX{}). | |
a351880d CD |
8984 | |
8985 | @node Comment lines, , Horizontal rules, Structural markup elements | |
8986 | @subheading Comment lines | |
8987 | @cindex comment lines | |
8988 | @cindex exporting, not | |
8989 | @cindex #+BEGIN_COMMENT | |
8990 | ||
8991 | Lines starting with @samp{#} in column zero are treated as comments and will | |
ce57c2fe | 8992 | never be exported. If you want an indented line to be treated as a comment, |
a351880d CD |
8993 | start it with @samp{#+ }. Also entire subtrees starting with the word |
8994 | @samp{COMMENT} will never be exported. Finally, regions surrounded by | |
8995 | @samp{#+BEGIN_COMMENT} ... @samp{#+END_COMMENT} will not be exported. | |
8996 | ||
8997 | @table @kbd | |
8998 | @kindex C-c ; | |
8999 | @item C-c ; | |
9000 | Toggle the COMMENT keyword at the beginning of an entry. | |
9001 | @end table | |
9002 | ||
9003 | ||
9004 | @node Images and tables, Literal examples, Structural markup elements, Markup | |
9005 | @section Images and Tables | |
9006 | ||
9007 | @cindex tables, markup rules | |
9008 | @cindex #+CAPTION | |
9009 | @cindex #+LABEL | |
e66ba1df BG |
9010 | Both the native Org mode tables (@pxref{Tables}) and tables formatted with |
9011 | the @file{table.el} package will be exported properly. For Org mode tables, | |
a351880d CD |
9012 | the lines before the first horizontal separator line will become table header |
9013 | lines. You can use the following lines somewhere before the table to assign | |
ed21c5c8 CD |
9014 | a caption and a label for cross references, and in the text you can refer to |
9015 | the object with @code{\ref@{tab:basic-data@}}: | |
a351880d CD |
9016 | |
9017 | @example | |
9018 | #+CAPTION: This is the caption for the next table (or link) | |
9019 | #+LABEL: tbl:basic-data | |
9020 | | ... | ...| | |
9021 | |-----|----| | |
9022 | @end example | |
9023 | ||
ce57c2fe BG |
9024 | Optionally, the caption can take the form: |
9025 | @example | |
9026 | #+CAPTION: [Caption for list of figures]@{Caption for table (or link).@} | |
9027 | @end example | |
9028 | ||
a351880d | 9029 | @cindex inlined images, markup rules |
acedf35c | 9030 | Some backends (HTML, @LaTeX{}, and DocBook) allow you to directly include |
a351880d CD |
9031 | images into the exported document. Org does this, if a link to an image |
9032 | files does not have a description part, for example @code{[[./img/a.jpg]]}. | |
9033 | If you wish to define a caption for the image and maybe a label for internal | |
86fbb8ca CD |
9034 | cross references, make sure that the link is on a line by itself and precede |
9035 | it with @code{#+CAPTION} and @code{#+LABEL} as follows: | |
a351880d CD |
9036 | |
9037 | @example | |
9038 | #+CAPTION: This is the caption for the next figure link (or table) | |
9039 | #+LABEL: fig:SED-HR4049 | |
9040 | [[./img/a.jpg]] | |
9041 | @end example | |
9042 | ||
9043 | You may also define additional attributes for the figure. As this is | |
9044 | backend-specific, see the sections about the individual backends for more | |
9045 | information. | |
9046 | ||
afe98dfa | 9047 | @xref{Handling links,the discussion of image links}. |
a351880d CD |
9048 | |
9049 | @node Literal examples, Include files, Images and tables, Markup | |
9050 | @section Literal examples | |
b349f79f | 9051 | @cindex literal examples, markup rules |
c8d0cf5c | 9052 | @cindex code line references, markup rules |
b349f79f CD |
9053 | |
9054 | You can include literal examples that should not be subjected to | |
9055 | markup. Such examples will be typeset in monospace, so this is well suited | |
9056 | for source code and similar examples. | |
9057 | @cindex #+BEGIN_EXAMPLE | |
9058 | ||
9059 | @example | |
9060 | #+BEGIN_EXAMPLE | |
9061 | Some example from a text file. | |
9062 | #+END_EXAMPLE | |
9063 | @end example | |
9064 | ||
c8d0cf5c CD |
9065 | Note that such blocks may be @i{indented} in order to align nicely with |
9066 | indented text and in particular with plain list structure (@pxref{Plain | |
9067 | lists}). For simplicity when using small examples, you can also start the | |
9068 | example lines with a colon followed by a space. There may also be additional | |
55e0839d | 9069 | whitespace before the colon: |
b349f79f CD |
9070 | |
9071 | @example | |
55e0839d CD |
9072 | Here is an example |
9073 | : Some example from a text file. | |
b349f79f CD |
9074 | @end example |
9075 | ||
9076 | @cindex formatting source code, markup rules | |
9077 | If the example is source code from a programming language, or any other text | |
9078 | that can be marked up by font-lock in Emacs, you can ask for the example to | |
afe98dfa CD |
9079 | look like the fontified Emacs buffer@footnote{This works automatically for |
9080 | the HTML backend (it requires version 1.34 of the @file{htmlize.el} package, | |
e66ba1df | 9081 | which is distributed with Org). Fontified code chunks in @LaTeX{} can be |
afe98dfa | 9082 | achieved using either the listings or the |
ce57c2fe | 9083 | @url{http://code.google.com/p/minted, minted,} package. To use listings, turn |
afe98dfa | 9084 | on the variable @code{org-export-latex-listings} and ensure that the listings |
e66ba1df | 9085 | package is included by the @LaTeX{} header (e.g.@: by configuring |
ce57c2fe | 9086 | @code{org-export-latex-packages-alist}). See the listings documentation for |
afe98dfa CD |
9087 | configuration options, including obtaining colored output. For minted it is |
9088 | necessary to install the program @url{http://pygments.org, pygments}, in | |
9089 | addition to setting @code{org-export-latex-minted}, ensuring that the minted | |
e66ba1df | 9090 | package is included by the @LaTeX{} header, and ensuring that the |
afe98dfa | 9091 | @code{-shell-escape} option is passed to @file{pdflatex} (see |
ce57c2fe | 9092 | @code{org-latex-to-pdf-process}). See the documentation of the variables |
afe98dfa CD |
9093 | @code{org-export-latex-listings} and @code{org-export-latex-minted} for |
9094 | further details.}. This is done with the @samp{src} block, where you also | |
9095 | need to specify the name of the major mode that should be used to fontify the | |
ce57c2fe BG |
9096 | example@footnote{Code in @samp{src} blocks may also be evaluated either |
9097 | interactively or on export. See @pxref{Working With Source Code} for more | |
e66ba1df BG |
9098 | information on evaluating code blocks.}, see @ref{Easy Templates} for |
9099 | shortcuts to easily insert code blocks. | |
b349f79f CD |
9100 | @cindex #+BEGIN_SRC |
9101 | ||
9102 | @example | |
9103 | #+BEGIN_SRC emacs-lisp | |
86fbb8ca CD |
9104 | (defun org-xor (a b) |
9105 | "Exclusive or." | |
9106 | (if a (not b) b)) | |
b349f79f CD |
9107 | #+END_SRC |
9108 | @end example | |
9109 | ||
55e0839d CD |
9110 | Both in @code{example} and in @code{src} snippets, you can add a @code{-n} |
9111 | switch to the end of the @code{BEGIN} line, to get the lines of the example | |
9112 | numbered. If you use a @code{+n} switch, the numbering from the previous | |
9113 | numbered snippet will be continued in the current one. In literal examples, | |
9114 | Org will interpret strings like @samp{(ref:name)} as labels, and use them as | |
ce57c2fe | 9115 | targets for special hyperlinks like @code{[[(name)]]} (i.e.@: the reference name |
c8d0cf5c CD |
9116 | enclosed in single parenthesis). In HTML, hovering the mouse over such a |
9117 | link will remote-highlight the corresponding code line, which is kind of | |
9118 | cool. | |
9119 | ||
9120 | You can also add a @code{-r} switch which @i{removes} the labels from the | |
9121 | source code@footnote{Adding @code{-k} to @code{-n -r} will @i{keep} the | |
9122 | labels in the source code while using line numbers for the links, which might | |
e66ba1df | 9123 | be useful to explain those in an Org mode example code.}. With the @code{-n} |
c8d0cf5c CD |
9124 | switch, links to these references will be labeled by the line numbers from |
9125 | the code listing, otherwise links will use the labels with no parentheses. | |
9126 | Here is an example: | |
55e0839d CD |
9127 | |
9128 | @example | |
9129 | #+BEGIN_SRC emacs-lisp -n -r | |
9130 | (save-excursion (ref:sc) | |
9131 | (goto-char (point-min)) (ref:jump) | |
c8d0cf5c CD |
9132 | #+END_SRC |
9133 | In line [[(sc)]] we remember the current position. [[(jump)][Line (jump)]] | |
55e0839d CD |
9134 | jumps to point-min. |
9135 | @end example | |
9136 | ||
c8d0cf5c | 9137 | @vindex org-coderef-label-format |
55e0839d CD |
9138 | If the syntax for the label format conflicts with the language syntax, use a |
9139 | @code{-l} switch to change the format, for example @samp{#+BEGIN_SRC pascal | |
9140 | -n -r -l "((%s))"}. See also the variable @code{org-coderef-label-format}. | |
9141 | ||
ce57c2fe BG |
9142 | HTML export also allows examples to be published as text areas (@pxref{Text |
9143 | areas in HTML export}). | |
9144 | ||
9145 | Because the @code{#+BEGIN_...} and @code{#+END_...} patterns need to be added | |
9146 | so often, shortcuts are provided using the Easy Templates facility | |
9147 | (@pxref{Easy Templates}). | |
55e0839d | 9148 | |
b349f79f CD |
9149 | @table @kbd |
9150 | @kindex C-c ' | |
9151 | @item C-c ' | |
9152 | Edit the source code example at point in its native mode. This works by | |
c8d0cf5c CD |
9153 | switching to a temporary buffer with the source code. You need to exit by |
9154 | pressing @kbd{C-c '} again@footnote{Upon exit, lines starting with @samp{*} | |
9155 | or @samp{#} will get a comma prepended, to keep them from being interpreted | |
86fbb8ca | 9156 | by Org as outline nodes or special comments. These commas will be stripped |
acedf35c | 9157 | for editing with @kbd{C-c '}, and also for export.}. The edited version will |
c8d0cf5c CD |
9158 | then replace the old version in the Org buffer. Fixed-width regions |
9159 | (where each line starts with a colon followed by a space) will be edited | |
9160 | using @code{artist-mode}@footnote{You may select a different-mode with the | |
9161 | variable @code{org-edit-fixed-width-region-mode}.} to allow creating ASCII | |
9162 | drawings easily. Using this command in an empty line will create a new | |
864c9740 | 9163 | fixed-width region. |
55e0839d CD |
9164 | @kindex C-c l |
9165 | @item C-c l | |
9166 | Calling @code{org-store-link} while editing a source code example in a | |
acedf35c | 9167 | temporary buffer created with @kbd{C-c '} will prompt for a label. Make sure |
55e0839d CD |
9168 | that it is unique in the current buffer, and insert it with the proper |
9169 | formatting like @samp{(ref:label)} at the end of the current line. Then the | |
9170 | label is stored as a link @samp{(label)}, for retrieval with @kbd{C-c C-l}. | |
b349f79f CD |
9171 | @end table |
9172 | ||
9173 | ||
ed21c5c8 | 9174 | @node Include files, Index entries, Literal examples, Markup |
a351880d | 9175 | @section Include files |
b349f79f CD |
9176 | @cindex include files, markup rules |
9177 | ||
9178 | During export, you can include the content of another file. For example, to | |
c8d0cf5c | 9179 | include your @file{.emacs} file, you could use: |
b349f79f CD |
9180 | @cindex #+INCLUDE |
9181 | ||
9182 | @example | |
9183 | #+INCLUDE: "~/.emacs" src emacs-lisp | |
9184 | @end example | |
c8d0cf5c | 9185 | @noindent |
ce57c2fe | 9186 | The optional second and third parameter are the markup (e.g.@: @samp{quote}, |
b349f79f | 9187 | @samp{example}, or @samp{src}), and, if the markup is @samp{src}, the |
acedf35c | 9188 | language for formatting the contents. The markup is optional; if it is not |
e66ba1df | 9189 | given, the text will be assumed to be in Org mode format and will be |
44ce9197 CD |
9190 | processed normally. The include line will also allow additional keyword |
9191 | parameters @code{:prefix1} and @code{:prefix} to specify prefixes for the | |
acedf35c | 9192 | first line and for each following line, @code{:minlevel} in order to get |
e66ba1df | 9193 | Org mode content demoted to a specified level, as well as any options |
acedf35c CD |
9194 | accepted by the selected markup. For example, to include a file as an item, |
9195 | use | |
44ce9197 CD |
9196 | |
9197 | @example | |
9198 | #+INCLUDE: "~/snippets/xx" :prefix1 " + " :prefix " " | |
9199 | @end example | |
b349f79f | 9200 | |
ce57c2fe BG |
9201 | You can also include a portion of a file by specifying a lines range using |
9202 | the @code{:lines} parameter. The line at the upper end of the range will not | |
9203 | be included. The start and/or the end of the range may be omitted to use the | |
9204 | obvious defaults. | |
9205 | ||
9206 | @example | |
9207 | #+INCLUDE: "~/.emacs" :lines "5-10" @r{Include lines 5 to 10, 10 excluded} | |
9208 | #+INCLUDE: "~/.emacs" :lines "-10" @r{Include lines 1 to 10, 10 excluded} | |
9209 | #+INCLUDE: "~/.emacs" :lines "10-" @r{Include lines from 10 to EOF} | |
9210 | @end example | |
9211 | ||
b349f79f CD |
9212 | @table @kbd |
9213 | @kindex C-c ' | |
9214 | @item C-c ' | |
9215 | Visit the include file at point. | |
9216 | @end table | |
9217 | ||
ed21c5c8 | 9218 | @node Index entries, Macro replacement, Include files, Markup |
86fbb8ca | 9219 | @section Index entries |
ed21c5c8 CD |
9220 | @cindex index entries, for publishing |
9221 | ||
9222 | You can specify entries that will be used for generating an index during | |
9223 | publishing. This is done by lines starting with @code{#+INDEX}. An entry | |
9224 | the contains an exclamation mark will create a sub item. See @ref{Generating | |
9225 | an index} for more information. | |
9226 | ||
9227 | @example | |
86fbb8ca | 9228 | * Curriculum Vitae |
ed21c5c8 CD |
9229 | #+INDEX: CV |
9230 | #+INDEX: Application!CV | |
9231 | @end example | |
9232 | ||
9233 | ||
b349f79f | 9234 | |
ed21c5c8 | 9235 | |
e66ba1df | 9236 | @node Macro replacement, Embedded @LaTeX{}, Index entries, Markup |
a351880d CD |
9237 | @section Macro replacement |
9238 | @cindex macro replacement, during export | |
9239 | @cindex #+MACRO | |
9240 | ||
9241 | You can define text snippets with | |
9242 | ||
9243 | @example | |
9244 | #+MACRO: name replacement text $1, $2 are arguments | |
9245 | @end example | |
9246 | ||
9247 | @noindent which can be referenced anywhere in the document (even in | |
9248 | code examples) with @code{@{@{@{name(arg1,arg2)@}@}@}}. In addition to | |
9249 | defined macros, @code{@{@{@{title@}@}@}}, @code{@{@{@{author@}@}@}}, etc., | |
9250 | will reference information set by the @code{#+TITLE:}, @code{#+AUTHOR:}, and | |
9251 | similar lines. Also, @code{@{@{@{date(@var{FORMAT})@}@}@}} and | |
9252 | @code{@{@{@{modification-time(@var{FORMAT})@}@}@}} refer to current date time | |
9253 | and to the modification time of the file being exported, respectively. | |
9254 | @var{FORMAT} should be a format string understood by | |
9255 | @code{format-time-string}. | |
9256 | ||
9257 | Macro expansion takes place during export, and some people use it to | |
9258 | construct complex HTML code. | |
9259 | ||
9260 | ||
e66ba1df | 9261 | @node Embedded @LaTeX{}, , Macro replacement, Markup |
acedf35c | 9262 | @section Embedded @LaTeX{} |
a351880d | 9263 | @cindex @TeX{} interpretation |
acedf35c CD |
9264 | @cindex @LaTeX{} interpretation |
9265 | ||
9266 | Plain ASCII is normally sufficient for almost all note taking. Exceptions | |
9267 | include scientific notes, which often require mathematical symbols and the | |
9268 | occasional formula. @LaTeX{}@footnote{@LaTeX{} is a macro system based on | |
9269 | Donald E. Knuth's @TeX{} system. Many of the features described here as | |
9270 | ``@LaTeX{}'' are really from @TeX{}, but for simplicity I am blurring this | |
e66ba1df | 9271 | distinction.} is widely used to typeset scientific documents. Org mode |
acedf35c CD |
9272 | supports embedding @LaTeX{} code into its files, because many academics are |
9273 | used to writing and reading @LaTeX{} source code, and because it can be | |
9274 | readily processed to produce pretty output for a number of export backends. | |
a351880d CD |
9275 | |
9276 | @menu | |
c0468714 GM |
9277 | * Special symbols:: Greek letters and other symbols |
9278 | * Subscripts and superscripts:: Simple syntax for raising/lowering text | |
e66ba1df BG |
9279 | * @LaTeX{} fragments:: Complex formulas made easy |
9280 | * Previewing @LaTeX{} fragments:: What will this snippet look like? | |
c0468714 | 9281 | * CDLaTeX mode:: Speed up entering of formulas |
a351880d CD |
9282 | @end menu |
9283 | ||
e66ba1df | 9284 | @node Special symbols, Subscripts and superscripts, Embedded @LaTeX{}, Embedded @LaTeX{} |
a351880d CD |
9285 | @subsection Special symbols |
9286 | @cindex math symbols | |
9287 | @cindex special symbols | |
9288 | @cindex @TeX{} macros | |
acedf35c | 9289 | @cindex @LaTeX{} fragments, markup rules |
a351880d | 9290 | @cindex HTML entities |
acedf35c | 9291 | @cindex @LaTeX{} entities |
a351880d | 9292 | |
acedf35c | 9293 | You can use @LaTeX{} macros to insert special symbols like @samp{\alpha} to |
a351880d CD |
9294 | indicate the Greek letter, or @samp{\to} to indicate an arrow. Completion |
9295 | for these macros is available, just type @samp{\} and maybe a few letters, | |
acedf35c | 9296 | and press @kbd{M-@key{TAB}} to see possible completions. Unlike @LaTeX{} |
e66ba1df | 9297 | code, Org mode allows these macros to be present without surrounding math |
a351880d CD |
9298 | delimiters, for example: |
9299 | ||
9300 | @example | |
9301 | Angles are written as Greek letters \alpha, \beta and \gamma. | |
9302 | @end example | |
9303 | ||
86fbb8ca | 9304 | @vindex org-entities |
a351880d CD |
9305 | During export, these symbols will be transformed into the native format of |
9306 | the exporter backend. Strings like @code{\alpha} will be exported as | |
acedf35c | 9307 | @code{α} in the HTML output, and as @code{$\alpha$} in the @LaTeX{} |
a351880d | 9308 | output. Similarly, @code{\nbsp} will become @code{ } in HTML and |
acedf35c | 9309 | @code{~} in @LaTeX{}. If you need such a symbol inside a word, terminate it |
a351880d CD |
9310 | like this: @samp{\Aacute@{@}stor}. |
9311 | ||
9312 | A large number of entities is provided, with names taken from both HTML and | |
acedf35c | 9313 | @LaTeX{}; see the variable @code{org-entities} for the complete list. |
a351880d CD |
9314 | @samp{\-} is treated as a shy hyphen, and @samp{--}, @samp{---}, and |
9315 | @samp{...} are all converted into special commands creating hyphens of | |
9316 | different lengths or a compact set of dots. | |
9317 | ||
afe98dfa | 9318 | If you would like to see entities displayed as UTF8 characters, use the |
86fbb8ca CD |
9319 | following command@footnote{You can turn this on by default by setting the |
9320 | variable @code{org-pretty-entities}, or on a per-file base with the | |
9321 | @code{#+STARTUP} option @code{entitiespretty}.}: | |
9322 | ||
9323 | @table @kbd | |
9324 | @kindex C-c C-x \ | |
9325 | @item C-c C-x \ | |
acedf35c CD |
9326 | Toggle display of entities as UTF-8 characters. This does not change the |
9327 | buffer content which remains plain ASCII, but it overlays the UTF-8 character | |
86fbb8ca CD |
9328 | for display purposes only. |
9329 | @end table | |
9330 | ||
e66ba1df | 9331 | @node Subscripts and superscripts, @LaTeX{} fragments, Special symbols, Embedded @LaTeX{} |
a351880d CD |
9332 | @subsection Subscripts and superscripts |
9333 | @cindex subscript | |
9334 | @cindex superscript | |
9335 | ||
acedf35c | 9336 | Just like in @LaTeX{}, @samp{^} and @samp{_} are used to indicate super- |
a351880d CD |
9337 | and subscripts. Again, these can be used without embedding them in |
9338 | math-mode delimiters. To increase the readability of ASCII text, it is | |
9339 | not necessary (but OK) to surround multi-character sub- and superscripts | |
9340 | with curly braces. For example | |
67df9cfb CD |
9341 | |
9342 | @example | |
acedf35c | 9343 | The mass of the sun is M_sun = 1.989 x 10^30 kg. The radius of |
a351880d | 9344 | the sun is R_@{sun@} = 6.96 x 10^8 m. |
67df9cfb CD |
9345 | @end example |
9346 | ||
a351880d CD |
9347 | @vindex org-export-with-sub-superscripts |
9348 | To avoid interpretation as raised or lowered text, you can quote @samp{^} and | |
9349 | @samp{_} with a backslash: @samp{\^} and @samp{\_}. If you write a text | |
9350 | where the underscore is often used in a different context, Org's convention | |
9351 | to always interpret these as subscripts can get in your way. Configure the | |
9352 | variable @code{org-export-with-sub-superscripts} to globally change this | |
9353 | convention, or use, on a per-file basis: | |
67df9cfb CD |
9354 | |
9355 | @example | |
a351880d | 9356 | #+OPTIONS: ^:@{@} |
67df9cfb | 9357 | @end example |
b349f79f | 9358 | |
afe98dfa CD |
9359 | @noindent With this setting, @samp{a_b} will not be interpreted as a |
9360 | subscript, but @samp{a_@{b@}} will. | |
9361 | ||
86fbb8ca CD |
9362 | @table @kbd |
9363 | @kindex C-c C-x \ | |
9364 | @item C-c C-x \ | |
acedf35c | 9365 | In addition to showing entities as UTF-8 characters, this command will also |
86fbb8ca CD |
9366 | format sub- and superscripts in a WYSIWYM way. |
9367 | @end table | |
67df9cfb | 9368 | |
e66ba1df | 9369 | @node @LaTeX{} fragments, Previewing @LaTeX{} fragments, Subscripts and superscripts, Embedded @LaTeX{} |
acedf35c CD |
9370 | @subsection @LaTeX{} fragments |
9371 | @cindex @LaTeX{} fragments | |
b349f79f | 9372 | |
a351880d | 9373 | @vindex org-format-latex-header |
afe98dfa | 9374 | Going beyond symbols and sub- and superscripts, a full formula language is |
e66ba1df | 9375 | needed. Org mode can contain @LaTeX{} math fragments, and it supports ways |
acedf35c | 9376 | to process these for several export backends. When exporting to @LaTeX{}, |
afe98dfa CD |
9377 | the code is obviously left as it is. When exporting to HTML, Org invokes the |
9378 | @uref{http://www.mathjax.org, MathJax library} (@pxref{Math formatting in | |
9379 | HTML export}) to process and display the math@footnote{If you plan to use | |
9380 | this regularly or on pages with significant page views, you should install | |
acedf35c CD |
9381 | @file{MathJax} on your own |
9382 | server in order to limit the load of our server.}. Finally, it can also | |
9383 | process the mathematical expressions into images@footnote{For this to work | |
ce57c2fe | 9384 | you need to be on a system with a working @LaTeX{} installation. You also |
acedf35c CD |
9385 | need the @file{dvipng} program, available at |
9386 | @url{http://sourceforge.net/projects/dvipng/}. The @LaTeX{} header that will | |
afe98dfa CD |
9387 | be used when processing a fragment can be configured with the variable |
9388 | @code{org-format-latex-header}.} that can be displayed in a browser or in | |
9389 | DocBook documents. | |
b349f79f | 9390 | |
acedf35c CD |
9391 | @LaTeX{} fragments don't need any special marking at all. The following |
9392 | snippets will be identified as @LaTeX{} source code: | |
a351880d CD |
9393 | @itemize @bullet |
9394 | @item | |
afe98dfa | 9395 | Environments of any kind@footnote{When @file{MathJax} is used, only the |
acedf35c CD |
9396 | environment recognized by @file{MathJax} will be processed. When |
9397 | @file{dvipng} is used to create images, any @LaTeX{} environments will be | |
9398 | handled.}. The only requirement is that the @code{\begin} statement appears | |
9399 | on a new line, preceded by only whitespace. | |
a351880d | 9400 | @item |
acedf35c | 9401 | Text within the usual @LaTeX{} math delimiters. To avoid conflicts with |
a351880d CD |
9402 | currency specifications, single @samp{$} characters are only recognized as |
9403 | math delimiters if the enclosed text contains at most two line breaks, is | |
9404 | directly attached to the @samp{$} characters with no whitespace in between, | |
9405 | and if the closing @samp{$} is followed by whitespace, punctuation or a dash. | |
9406 | For the other delimiters, there is no such restriction, so when in doubt, use | |
9407 | @samp{\(...\)} as inline math delimiters. | |
9408 | @end itemize | |
b349f79f | 9409 | |
a351880d | 9410 | @noindent For example: |
b349f79f | 9411 | |
a351880d CD |
9412 | @example |
9413 | \begin@{equation@} % arbitrary environments, | |
9414 | x=\sqrt@{b@} % even tables, figures | |
9415 | \end@{equation@} % etc | |
b349f79f | 9416 | |
a351880d CD |
9417 | If $a^2=b$ and \( b=2 \), then the solution must be |
9418 | either $$ a=+\sqrt@{2@} $$ or \[ a=-\sqrt@{2@} \]. | |
9419 | @end example | |
b349f79f | 9420 | |
a351880d CD |
9421 | @noindent |
9422 | @vindex org-format-latex-options | |
9423 | If you need any of the delimiter ASCII sequences for other purposes, you | |
9424 | can configure the option @code{org-format-latex-options} to deselect the | |
acedf35c | 9425 | ones you do not wish to have interpreted by the @LaTeX{} converter. |
b349f79f | 9426 | |
afe98dfa | 9427 | @vindex org-export-with-LaTeX-fragments |
e66ba1df | 9428 | @LaTeX{} processing can be configured with the variable |
afe98dfa CD |
9429 | @code{org-export-with-LaTeX-fragments}. The default setting is @code{t} |
9430 | which means @file{MathJax} for HTML, and no processing for DocBook, ASCII and | |
e66ba1df | 9431 | @LaTeX{} backends. You can also set this variable on a per-file basis using one |
afe98dfa CD |
9432 | of these lines: |
9433 | ||
9434 | @example | |
9435 | #+OPTIONS: LaTeX:t @r{Do the right thing automatically (MathJax)} | |
9436 | #+OPTIONS: LaTeX:dvipng @r{Force using dvipng images} | |
acedf35c | 9437 | #+OPTIONS: LaTeX:nil @r{Do not process @LaTeX{} fragments at all} |
afe98dfa CD |
9438 | #+OPTIONS: LaTeX:verbatim @r{Verbatim export, for jsMath or so} |
9439 | @end example | |
9440 | ||
e66ba1df BG |
9441 | @node Previewing @LaTeX{} fragments, CDLaTeX mode, @LaTeX{} fragments, Embedded @LaTeX{} |
9442 | @subsection Previewing @LaTeX{} fragments | |
9443 | @cindex @LaTeX{} fragments, preview | |
b349f79f | 9444 | |
acedf35c | 9445 | If you have @file{dvipng} installed, @LaTeX{} fragments can be processed to |
afe98dfa | 9446 | produce preview images of the typeset expressions: |
b349f79f CD |
9447 | |
9448 | @table @kbd | |
a351880d CD |
9449 | @kindex C-c C-x C-l |
9450 | @item C-c C-x C-l | |
acedf35c | 9451 | Produce a preview image of the @LaTeX{} fragment at point and overlay it |
a351880d CD |
9452 | over the source code. If there is no fragment at point, process all |
9453 | fragments in the current entry (between two headlines). When called | |
9454 | with a prefix argument, process the entire subtree. When called with | |
9455 | two prefix arguments, or when the cursor is before the first headline, | |
9456 | process the entire buffer. | |
9457 | @kindex C-c C-c | |
9458 | @item C-c C-c | |
9459 | Remove the overlay preview images. | |
b349f79f CD |
9460 | @end table |
9461 | ||
a351880d CD |
9462 | @vindex org-format-latex-options |
9463 | You can customize the variable @code{org-format-latex-options} to influence | |
ce57c2fe | 9464 | some aspects of the preview. In particular, the @code{:scale} (and for HTML |
a351880d CD |
9465 | export, @code{:html-scale}) property can be used to adjust the size of the |
9466 | preview images. | |
c8d0cf5c | 9467 | |
e66ba1df BG |
9468 | @node CDLaTeX mode, , Previewing @LaTeX{} fragments, Embedded @LaTeX{} |
9469 | @subsection Using CD@LaTeX{} to enter math | |
9470 | @cindex CD@LaTeX{} | |
a351880d | 9471 | |
e66ba1df | 9472 | CD@LaTeX{} mode is a minor mode that is normally used in combination with a |
acedf35c | 9473 | major @LaTeX{} mode like AUC@TeX{} in order to speed-up insertion of |
e66ba1df BG |
9474 | environments and math templates. Inside Org mode, you can make use of |
9475 | some of the features of CD@LaTeX{} mode. You need to install | |
a351880d CD |
9476 | @file{cdlatex.el} and @file{texmathp.el} (the latter comes also with |
9477 | AUC@TeX{}) from @url{http://www.astro.uva.nl/~dominik/Tools/cdlatex}. | |
e66ba1df BG |
9478 | Don't use CD@LaTeX{} mode itself under Org mode, but use the light |
9479 | version @code{org-cdlatex-mode} that comes as part of Org mode. Turn it | |
a351880d CD |
9480 | on for the current buffer with @code{M-x org-cdlatex-mode}, or for all |
9481 | Org files with | |
9482 | ||
9483 | @lisp | |
9484 | (add-hook 'org-mode-hook 'turn-on-org-cdlatex) | |
9485 | @end lisp | |
9486 | ||
9487 | When this mode is enabled, the following features are present (for more | |
e66ba1df | 9488 | details see the documentation of CD@LaTeX{} mode): |
a351880d CD |
9489 | @itemize @bullet |
9490 | @kindex C-c @{ | |
9491 | @item | |
9492 | Environment templates can be inserted with @kbd{C-c @{}. | |
9493 | @item | |
9494 | @kindex @key{TAB} | |
9495 | The @key{TAB} key will do template expansion if the cursor is inside a | |
e66ba1df | 9496 | @LaTeX{} fragment@footnote{Org mode has a method to test if the cursor is |
a351880d CD |
9497 | inside such a fragment, see the documentation of the function |
9498 | @code{org-inside-LaTeX-fragment-p}.}. For example, @key{TAB} will | |
9499 | expand @code{fr} to @code{\frac@{@}@{@}} and position the cursor | |
9500 | correctly inside the first brace. Another @key{TAB} will get you into | |
9501 | the second brace. Even outside fragments, @key{TAB} will expand | |
9502 | environment abbreviations at the beginning of a line. For example, if | |
9503 | you write @samp{equ} at the beginning of a line and press @key{TAB}, | |
9504 | this abbreviation will be expanded to an @code{equation} environment. | |
9505 | To get a list of all abbreviations, type @kbd{M-x cdlatex-command-help}. | |
9506 | @item | |
9507 | @kindex _ | |
9508 | @kindex ^ | |
9509 | @vindex cdlatex-simplify-sub-super-scripts | |
acedf35c | 9510 | Pressing @kbd{_} and @kbd{^} inside a @LaTeX{} fragment will insert these |
a351880d CD |
9511 | characters together with a pair of braces. If you use @key{TAB} to move |
9512 | out of the braces, and if the braces surround only a single character or | |
9513 | macro, they are removed again (depending on the variable | |
9514 | @code{cdlatex-simplify-sub-super-scripts}). | |
9515 | @item | |
9516 | @kindex ` | |
9517 | Pressing the backquote @kbd{`} followed by a character inserts math | |
acedf35c | 9518 | macros, also outside @LaTeX{} fragments. If you wait more than 1.5 seconds |
a351880d CD |
9519 | after the backquote, a help window will pop up. |
9520 | @item | |
9521 | @kindex ' | |
9522 | Pressing the single-quote @kbd{'} followed by another character modifies | |
9523 | the symbol before point with an accent or a font. If you wait more than | |
acedf35c CD |
9524 | 1.5 seconds after the single-quote, a help window will pop up. Character |
9525 | modification will work only inside @LaTeX{} fragments; outside the quote | |
a351880d CD |
9526 | is normal. |
9527 | @end itemize | |
9528 | ||
9529 | @node Exporting, Publishing, Markup, Top | |
9530 | @chapter Exporting | |
9531 | @cindex exporting | |
9532 | ||
e66ba1df | 9533 | Org mode documents can be exported into a variety of other formats. For |
a351880d CD |
9534 | printing and sharing of notes, ASCII export produces a readable and simple |
9535 | version of an Org file. HTML export allows you to publish a notes file on | |
9536 | the web, while the XOXO format provides a solid base for exchange with a | |
e66ba1df | 9537 | broad range of other applications. @LaTeX{} export lets you use Org mode and |
acedf35c | 9538 | its structured editing functions to easily create @LaTeX{} files. DocBook |
a351880d | 9539 | export makes it possible to convert Org files to many other formats using |
801a68c8 | 9540 | DocBook tools. OpenDocument Text (ODT) export allows seamless |
27e428e7 | 9541 | collaboration across organizational boundaries. For project management you |
e66ba1df BG |
9542 | can create gantt and resource charts by using TaskJuggler export. To |
9543 | incorporate entries with associated times like deadlines or appointments into | |
9544 | a desktop calendar program like iCal, Org mode can also produce extracts in | |
801a68c8 | 9545 | the iCalendar format. Currently, Org mode only supports export, not import of |
e66ba1df | 9546 | these different formats. |
a351880d CD |
9547 | |
9548 | Org supports export of selected regions when @code{transient-mark-mode} is | |
9549 | enabled (default in Emacs 23). | |
9550 | ||
9551 | @menu | |
c0468714 GM |
9552 | * Selective export:: Using tags to select and exclude trees |
9553 | * Export options:: Per-file export settings | |
9554 | * The export dispatcher:: How to access exporter commands | |
9555 | * ASCII/Latin-1/UTF-8 export:: Exporting to flat files with encoding | |
9556 | * HTML export:: Exporting to HTML | |
e66ba1df | 9557 | * @LaTeX{} and PDF export:: Exporting to @LaTeX{}, and processing to PDF |
c0468714 | 9558 | * DocBook export:: Exporting to DocBook |
e66ba1df | 9559 | * OpenDocument Text export:: Exporting to OpenDocument Text |
c0468714 GM |
9560 | * TaskJuggler export:: Exporting to TaskJuggler |
9561 | * Freemind export:: Exporting to Freemind mind maps | |
9562 | * XOXO export:: Exporting to XOXO | |
9563 | * iCalendar export:: Exporting in iCalendar format | |
a351880d | 9564 | @end menu |
c8d0cf5c | 9565 | |
a351880d | 9566 | @node Selective export, Export options, Exporting, Exporting |
864c9740 | 9567 | @section Selective export |
ce57c2fe | 9568 | @cindex export, selective by tags or TODO keyword |
864c9740 | 9569 | |
c8d0cf5c CD |
9570 | @vindex org-export-select-tags |
9571 | @vindex org-export-exclude-tags | |
ce57c2fe | 9572 | @cindex org-export-with-tasks |
864c9740 CD |
9573 | You may use tags to select the parts of a document that should be exported, |
9574 | or to exclude parts from export. This behavior is governed by two variables: | |
e66ba1df BG |
9575 | @code{org-export-select-tags} and @code{org-export-exclude-tags}, |
9576 | respectively defaulting to @code{'(:export:)} and @code{'(:noexport:)}. | |
864c9740 | 9577 | |
ce57c2fe BG |
9578 | @enumerate |
9579 | @item | |
9580 | Org first checks if any of the @emph{select} tags is present in the | |
9581 | buffer. If yes, all trees that do not carry one of these tags will be | |
9582 | excluded. If a selected tree is a subtree, the heading hierarchy above it | |
9583 | will also be selected for export, but not the text below those headings. | |
864c9740 | 9584 | |
ce57c2fe | 9585 | @item |
864c9740 CD |
9586 | If none of the select tags is found, the whole buffer will be selected for |
9587 | export. | |
9588 | ||
ce57c2fe | 9589 | @item |
864c9740 CD |
9590 | Finally, all subtrees that are marked by any of the @emph{exclude} tags will |
9591 | be removed from the export buffer. | |
ce57c2fe BG |
9592 | @end enumerate |
9593 | ||
9594 | The variable @code{org-export-with-tasks} can be configured to select which | |
9595 | kind of tasks should be included for export. See the docstring of the | |
9596 | variable for more information. | |
864c9740 CD |
9597 | |
9598 | @node Export options, The export dispatcher, Selective export, Exporting | |
b349f79f CD |
9599 | @section Export options |
9600 | @cindex options, for export | |
9601 | ||
9602 | @cindex completion, of option keywords | |
9603 | The exporter recognizes special lines in the buffer which provide | |
9604 | additional information. These lines may be put anywhere in the file. | |
9605 | The whole set of lines can be inserted into the buffer with @kbd{C-c | |
9606 | C-e t}. For individual lines, a good way to make sure the keyword is | |
9607 | correct is to type @samp{#+} and then use @kbd{M-@key{TAB}} completion | |
c8d0cf5c CD |
9608 | (@pxref{Completion}). For a summary of other in-buffer settings not |
9609 | specifically related to export, see @ref{In-buffer settings}. | |
9610 | In particular, note that you can place commonly-used (export) options in | |
9611 | a separate file which can be included using @code{#+SETUPFILE}. | |
b349f79f CD |
9612 | |
9613 | @table @kbd | |
acedf35c | 9614 | @orgcmd{C-c C-e t,org-insert-export-options-template} |
b349f79f CD |
9615 | Insert template with export options, see example below. |
9616 | @end table | |
9617 | ||
c8d0cf5c CD |
9618 | @cindex #+TITLE |
9619 | @cindex #+AUTHOR | |
9620 | @cindex #+DATE | |
9621 | @cindex #+EMAIL | |
9622 | @cindex #+DESCRIPTION | |
9623 | @cindex #+KEYWORDS | |
9624 | @cindex #+LANGUAGE | |
9625 | @cindex #+TEXT | |
9626 | @cindex #+OPTIONS | |
9627 | @cindex #+BIND | |
9628 | @cindex #+LINK_UP | |
9629 | @cindex #+LINK_HOME | |
9630 | @cindex #+EXPORT_SELECT_TAGS | |
9631 | @cindex #+EXPORT_EXCLUDE_TAGS | |
86fbb8ca | 9632 | @cindex #+XSLT |
c8d0cf5c CD |
9633 | @cindex #+LATEX_HEADER |
9634 | @vindex user-full-name | |
9635 | @vindex user-mail-address | |
9636 | @vindex org-export-default-language | |
e66ba1df | 9637 | @vindex org-export-date-timestamp-format |
c8d0cf5c CD |
9638 | @example |
9639 | #+TITLE: the title to be shown (default is the buffer name) | |
9640 | #+AUTHOR: the author (default taken from @code{user-full-name}) | |
e66ba1df | 9641 | #+DATE: a date, an Org timestamp@footnote{@code{org-export-date-timestamp-format} defines how this timestamp will be exported.}, or a format string for @code{format-time-string} |
c8d0cf5c | 9642 | #+EMAIL: his/her email address (default from @code{user-mail-address}) |
ce57c2fe BG |
9643 | #+DESCRIPTION: the page description, e.g.@: for the XHTML meta tag |
9644 | #+KEYWORDS: the page keywords, e.g.@: for the XHTML meta tag | |
9645 | #+LANGUAGE: language for HTML, e.g.@: @samp{en} (@code{org-export-default-language}) | |
c8d0cf5c CD |
9646 | #+TEXT: Some descriptive text to be inserted at the beginning. |
9647 | #+TEXT: Several lines may be given. | |
9648 | #+OPTIONS: H:2 num:t toc:t \n:nil @@:t ::t |:t ^:t f:t TeX:t ... | |
e66ba1df | 9649 | #+BIND: lisp-var lisp-val, e.g.@:: @code{org-export-latex-low-levels itemize} |
c8d0cf5c CD |
9650 | @r{You need to confirm using these, or configure @code{org-export-allow-BIND}} |
9651 | #+LINK_UP: the ``up'' link of an exported page | |
9652 | #+LINK_HOME: the ``home'' link of an exported page | |
e66ba1df | 9653 | #+LATEX_HEADER: extra line(s) for the @LaTeX{} header, like \usepackage@{xyz@} |
864c9740 CD |
9654 | #+EXPORT_SELECT_TAGS: Tags that select a tree for export |
9655 | #+EXPORT_EXCLUDE_TAGS: Tags that exclude a tree from export | |
86fbb8ca | 9656 | #+XSLT: the XSLT stylesheet used by DocBook exporter to generate FO file |
b349f79f CD |
9657 | @end example |
9658 | ||
9659 | @noindent | |
e66ba1df BG |
9660 | The @code{#+OPTIONS} line is a compact@footnote{If you want to configure many options |
9661 | this way, you can use several @code{#+OPTIONS} lines.} form to specify export | |
acedf35c | 9662 | settings. Here you can: |
b349f79f CD |
9663 | @cindex headline levels |
9664 | @cindex section-numbers | |
9665 | @cindex table of contents | |
9666 | @cindex line-break preservation | |
9667 | @cindex quoted HTML tags | |
9668 | @cindex fixed-width sections | |
9669 | @cindex tables | |
9670 | @cindex @TeX{}-like syntax for sub- and superscripts | |
9671 | @cindex footnotes | |
9672 | @cindex special strings | |
9673 | @cindex emphasized text | |
9674 | @cindex @TeX{} macros | |
acedf35c | 9675 | @cindex @LaTeX{} fragments |
b349f79f CD |
9676 | @cindex author info, in export |
9677 | @cindex time info, in export | |
ce57c2fe BG |
9678 | @vindex org-export-plist-vars |
9679 | @vindex org-export-author-info | |
9680 | @vindex org-export-creator-info | |
9681 | @vindex org-export-email-info | |
9682 | @vindex org-export-time-stamp-file | |
b349f79f CD |
9683 | @example |
9684 | H: @r{set the number of headline levels for export} | |
9685 | num: @r{turn on/off section-numbers} | |
9686 | toc: @r{turn on/off table of contents, or set level limit (integer)} | |
ed21c5c8 | 9687 | \n: @r{turn on/off line-break-preservation (DOES NOT WORK)} |
b349f79f CD |
9688 | @@: @r{turn on/off quoted HTML tags} |
9689 | :: @r{turn on/off fixed-width sections} | |
9690 | |: @r{turn on/off tables} | |
9691 | ^: @r{turn on/off @TeX{}-like syntax for sub- and superscripts. If} | |
9692 | @r{you write "^:@{@}", @code{a_@{b@}} will be interpreted, but} | |
9693 | @r{the simple @code{a_b} will be left as it is.} | |
9694 | -: @r{turn on/off conversion of special strings.} | |
9695 | f: @r{turn on/off footnotes like this[1].} | |
96c8522a | 9696 | todo: @r{turn on/off inclusion of TODO keywords into exported text} |
ce57c2fe BG |
9697 | tasks: @r{turn on/off inclusion of tasks (TODO items), can be nil to remove} |
9698 | @r{all tasks, @code{todo} to remove DONE tasks, or list of kwds to keep} | |
96c8522a CD |
9699 | pri: @r{turn on/off priority cookies} |
9700 | tags: @r{turn on/off inclusion of tags, may also be @code{not-in-toc}} | |
9701 | <: @r{turn on/off inclusion of any time/date stamps like DEADLINES} | |
b349f79f CD |
9702 | *: @r{turn on/off emphasized text (bold, italic, underlined)} |
9703 | TeX: @r{turn on/off simple @TeX{} macros in plain text} | |
acedf35c | 9704 | LaTeX: @r{configure export of @LaTeX{} fragments. Default @code{auto}} |
b349f79f CD |
9705 | skip: @r{turn on/off skipping the text before the first heading} |
9706 | author: @r{turn on/off inclusion of author name/email into exported file} | |
ed21c5c8 | 9707 | email: @r{turn on/off inclusion of author email into exported file} |
dd12e1c6 | 9708 | creator: @r{turn on/off inclusion of creator info into exported file} |
b349f79f CD |
9709 | timestamp: @r{turn on/off inclusion creation time into exported file} |
9710 | d: @r{turn on/off inclusion of drawers} | |
9711 | @end example | |
c8d0cf5c | 9712 | @noindent |
acedf35c | 9713 | These options take effect in both the HTML and @LaTeX{} export, except for |
ce57c2fe BG |
9714 | @code{TeX} and @code{LaTeX} options, which are respectively @code{t} and |
9715 | @code{nil} for the @LaTeX{} export. | |
9716 | ||
9717 | The default values for these and many other options are given by a set of | |
9718 | variables. For a list of such variables, the corresponding OPTIONS keys and | |
9719 | also the publishing keys (@pxref{Project alist}), see the constant | |
9720 | @code{org-export-plist-vars}. | |
b349f79f CD |
9721 | |
9722 | When exporting only a single subtree by selecting it with @kbd{C-c @@} before | |
9723 | calling an export command, the subtree can overrule some of the file's export | |
9724 | settings with properties @code{EXPORT_FILE_NAME}, @code{EXPORT_TITLE}, | |
c8d0cf5c CD |
9725 | @code{EXPORT_TEXT}, @code{EXPORT_AUTHOR}, @code{EXPORT_DATE}, and |
9726 | @code{EXPORT_OPTIONS}. | |
b349f79f | 9727 | |
ed21c5c8 | 9728 | @node The export dispatcher, ASCII/Latin-1/UTF-8 export, Export options, Exporting |
b349f79f CD |
9729 | @section The export dispatcher |
9730 | @cindex dispatcher, for export commands | |
9731 | ||
9732 | All export commands can be reached using the export dispatcher, which is a | |
9733 | prefix key that prompts for an additional key specifying the command. | |
9734 | Normally the entire file is exported, but if there is an active region that | |
9735 | contains one outline tree, the first heading is used as document title and | |
9736 | the subtrees are exported. | |
4009494e GM |
9737 | |
9738 | @table @kbd | |
acedf35c | 9739 | @orgcmd{C-c C-e,org-export} |
c8d0cf5c | 9740 | @vindex org-export-run-in-background |
4009494e GM |
9741 | Dispatcher for export and publishing commands. Displays a help-window |
9742 | listing the additional key(s) needed to launch an export or publishing | |
64fb801f CD |
9743 | command. The prefix arg is passed through to the exporter. A double prefix |
9744 | @kbd{C-u C-u} causes most commands to be executed in the background, in a | |
c8d0cf5c | 9745 | separate Emacs process@footnote{To make this behavior the default, customize |
64fb801f | 9746 | the variable @code{org-export-run-in-background}.}. |
acedf35c | 9747 | @orgcmd{C-c C-e v,org-export-visible} |
b349f79f | 9748 | Like @kbd{C-c C-e}, but only export the text that is currently visible |
ce57c2fe | 9749 | (i.e.@: not hidden by outline visibility). |
acedf35c | 9750 | @orgcmd{C-u C-u C-c C-e,org-export} |
c8d0cf5c | 9751 | @vindex org-export-run-in-background |
acedf35c | 9752 | Call the exporter, but reverse the setting of |
ce57c2fe | 9753 | @code{org-export-run-in-background}, i.e.@: request background processing if |
c8d0cf5c | 9754 | not set, or force processing in the current Emacs process if set. |
4009494e GM |
9755 | @end table |
9756 | ||
ed21c5c8 CD |
9757 | @node ASCII/Latin-1/UTF-8 export, HTML export, The export dispatcher, Exporting |
9758 | @section ASCII/Latin-1/UTF-8 export | |
4009494e | 9759 | @cindex ASCII export |
ed21c5c8 CD |
9760 | @cindex Latin-1 export |
9761 | @cindex UTF-8 export | |
4009494e | 9762 | |
e66ba1df | 9763 | ASCII export produces a simple and very readable version of an Org mode |
ed21c5c8 CD |
9764 | file, containing only plain ASCII. Latin-1 and UTF-8 export augment the file |
9765 | with special characters and symbols available in these encodings. | |
4009494e GM |
9766 | |
9767 | @cindex region, active | |
9768 | @cindex active region | |
b6cb4cd5 | 9769 | @cindex transient-mark-mode |
4009494e | 9770 | @table @kbd |
acedf35c | 9771 | @orgcmd{C-c C-e a,org-export-as-ascii} |
c8d0cf5c CD |
9772 | @cindex property, EXPORT_FILE_NAME |
9773 | Export as ASCII file. For an Org file, @file{myfile.org}, the ASCII file | |
4009494e | 9774 | will be @file{myfile.txt}. The file will be overwritten without |
c8d0cf5c CD |
9775 | warning. If there is an active region@footnote{This requires |
9776 | @code{transient-mark-mode} be turned on.}, only the region will be | |
ce57c2fe | 9777 | exported. If the selected region is a single tree@footnote{To select the |
b349f79f | 9778 | current subtree, use @kbd{C-c @@}.}, the tree head will |
4009494e | 9779 | become the document title. If the tree head entry has or inherits an |
b349f79f | 9780 | @code{EXPORT_FILE_NAME} property, that name will be used for the |
28a16a1b | 9781 | export. |
acedf35c CD |
9782 | @orgcmd{C-c C-e A,org-export-as-ascii-to-buffer} |
9783 | Export to a temporary buffer. Do not create a file. | |
9784 | @orgcmd{C-c C-e n,org-export-as-latin1} | |
9785 | @xorgcmd{C-c C-e N,org-export-as-latin1-to-buffer} | |
ed21c5c8 | 9786 | Like the above commands, but use Latin-1 encoding. |
acedf35c CD |
9787 | @orgcmd{C-c C-e u,org-export-as-utf8} |
9788 | @xorgcmd{C-c C-e U,org-export-as-utf8-to-buffer} | |
ed21c5c8 | 9789 | Like the above commands, but use UTF-8 encoding. |
acedf35c | 9790 | @item C-c C-e v a/n/u |
4009494e GM |
9791 | Export only the visible part of the document. |
9792 | @end table | |
9793 | ||
9794 | @cindex headline levels, for exporting | |
9795 | In the exported version, the first 3 outline levels will become | |
9796 | headlines, defining a general document structure. Additional levels | |
9797 | will be exported as itemized lists. If you want that transition to occur | |
9798 | at a different level, specify it with a prefix argument. For example, | |
9799 | ||
9800 | @example | |
9801 | @kbd{C-1 C-c C-e a} | |
9802 | @end example | |
9803 | ||
9804 | @noindent | |
9805 | creates only top level headlines and does the rest as items. When | |
9806 | headlines are converted to items, the indentation of the text following | |
9807 | the headline is changed to fit nicely under the item. This is done with | |
a7808fba | 9808 | the assumption that the first body line indicates the base indentation of |
4009494e GM |
9809 | the body text. Any indentation larger than this is adjusted to preserve |
9810 | the layout relative to the first line. Should there be lines with less | |
9811 | indentation than the first, these are left alone. | |
9812 | ||
c8d0cf5c CD |
9813 | @vindex org-export-ascii-links-to-notes |
9814 | Links will be exported in a footnote-like style, with the descriptive part in | |
9815 | the text and the link in a note before the next heading. See the variable | |
9816 | @code{org-export-ascii-links-to-notes} for details and other options. | |
9817 | ||
e66ba1df | 9818 | @node HTML export, @LaTeX{} and PDF export, ASCII/Latin-1/UTF-8 export, Exporting |
4009494e GM |
9819 | @section HTML export |
9820 | @cindex HTML export | |
9821 | ||
e66ba1df | 9822 | Org mode contains an HTML (XHTML 1.0 strict) exporter with extensive |
b6cb4cd5 | 9823 | HTML formatting, in ways similar to John Gruber's @emph{markdown} |
4009494e GM |
9824 | language, but with additional support for tables. |
9825 | ||
9826 | @menu | |
c0468714 | 9827 | * HTML Export commands:: How to invoke HTML export |
ce57c2fe | 9828 | * HTML preamble and postamble:: How to insert a preamble and a postamble |
e66ba1df | 9829 | * Quoting HTML tags:: Using direct HTML in Org mode |
c0468714 GM |
9830 | * Links in HTML export:: How links will be interpreted and formatted |
9831 | * Tables in HTML export:: How to modify the formatting of tables | |
9832 | * Images in HTML export:: How to insert figures into HTML output | |
afe98dfa | 9833 | * Math formatting in HTML export:: Beautiful math also on the web |
c0468714 GM |
9834 | * Text areas in HTML export:: An alternative way to show an example |
9835 | * CSS support:: Changing the appearance of the output | |
9836 | * JavaScript support:: Info and Folding in a web browser | |
4009494e GM |
9837 | @end menu |
9838 | ||
ce57c2fe | 9839 | @node HTML Export commands, HTML preamble and postamble, HTML export, HTML export |
4009494e GM |
9840 | @subsection HTML export commands |
9841 | ||
9842 | @cindex region, active | |
9843 | @cindex active region | |
b6cb4cd5 | 9844 | @cindex transient-mark-mode |
4009494e | 9845 | @table @kbd |
acedf35c | 9846 | @orgcmd{C-c C-e h,org-export-as-html} |
c8d0cf5c | 9847 | @cindex property, EXPORT_FILE_NAME |
ce57c2fe BG |
9848 | Export as HTML file. For an Org file @file{myfile.org}, |
9849 | the HTML file will be @file{myfile.html}. The file will be overwritten | |
c8d0cf5c CD |
9850 | without warning. If there is an active region@footnote{This requires |
9851 | @code{transient-mark-mode} be turned on.}, only the region will be | |
ce57c2fe | 9852 | exported. If the selected region is a single tree@footnote{To select the |
b349f79f | 9853 | current subtree, use @kbd{C-c @@}.}, the tree head will become the document |
b6cb4cd5 | 9854 | title. If the tree head entry has, or inherits, an @code{EXPORT_FILE_NAME} |
b349f79f | 9855 | property, that name will be used for the export. |
acedf35c | 9856 | @orgcmd{C-c C-e b,org-export-as-html-and-open} |
4009494e | 9857 | Export as HTML file and immediately open it with a browser. |
acedf35c CD |
9858 | @orgcmd{C-c C-e H,org-export-as-html-to-buffer} |
9859 | Export to a temporary buffer. Do not create a file. | |
9860 | @orgcmd{C-c C-e R,org-export-region-as-html} | |
a7808fba CD |
9861 | Export the active region to a temporary buffer. With a prefix argument, do |
9862 | not produce the file header and footer, but just the plain HTML section for | |
9863 | the region. This is good for cut-and-paste operations. | |
acedf35c | 9864 | @item C-c C-e v h/b/H/R |
4009494e GM |
9865 | Export only the visible part of the document. |
9866 | @item M-x org-export-region-as-html | |
e66ba1df | 9867 | Convert the region to HTML under the assumption that it was Org mode |
4009494e GM |
9868 | syntax before. This is a global command that can be invoked in any |
9869 | buffer. | |
9870 | @item M-x org-replace-region-by-HTML | |
e66ba1df | 9871 | Replace the active region (assumed to be in Org mode syntax) by HTML |
4009494e GM |
9872 | code. |
9873 | @end table | |
9874 | ||
9875 | @cindex headline levels, for exporting | |
a7808fba CD |
9876 | In the exported version, the first 3 outline levels will become headlines, |
9877 | defining a general document structure. Additional levels will be exported as | |
9878 | itemized lists. If you want that transition to occur at a different level, | |
9879 | specify it with a numeric prefix argument. For example, | |
4009494e GM |
9880 | |
9881 | @example | |
9882 | @kbd{C-2 C-c C-e b} | |
9883 | @end example | |
9884 | ||
9885 | @noindent | |
9886 | creates two levels of headings and does the rest as items. | |
9887 | ||
ce57c2fe BG |
9888 | |
9889 | @node HTML preamble and postamble, Quoting HTML tags, HTML Export commands, HTML export | |
9890 | @subsection HTML preamble and postamble | |
9891 | @vindex org-export-html-preamble | |
9892 | @vindex org-export-html-postamble | |
9893 | @vindex org-export-html-preamble-format | |
9894 | @vindex org-export-html-postamble-format | |
9895 | @vindex org-export-html-validation-link | |
9896 | @vindex org-export-author-info | |
9897 | @vindex org-export-email-info | |
9898 | @vindex org-export-creator-info | |
9899 | @vindex org-export-time-stamp-file | |
9900 | ||
9901 | The HTML exporter lets you define a preamble and a postamble. | |
9902 | ||
9903 | The default value for @code{org-export-html-preamble} is @code{t}, which | |
9904 | means that the preamble is inserted depending on the relevant formatting | |
9905 | string in @code{org-export-html-preamble-format}. | |
9906 | ||
9907 | Setting @code{org-export-html-preamble} to a string will override the default | |
9908 | formatting string. Setting it to a function, will insert the output of the | |
9909 | function, which must be a string; such a function takes no argument but you | |
9910 | can check against the value of @code{opt-plist}, which contains the list of | |
9911 | publishing properties for the current file. Setting to @code{nil} will not | |
9912 | insert any preamble. | |
9913 | ||
9914 | The default value for @code{org-export-html-postamble} is @code{'auto}, which | |
9915 | means that the HTML exporter will look for the value of | |
9916 | @code{org-export-author-info}, @code{org-export-email-info}, | |
9917 | @code{org-export-creator-info} and @code{org-export-time-stamp-file}, | |
9918 | @code{org-export-html-validation-link} and build the postamble from these | |
9919 | values. Setting @code{org-export-html-postamble} to @code{t} will insert the | |
9920 | postamble from the relevant formatting string found in | |
9921 | @code{org-export-html-postamble-format}. Setting it to @code{nil} will not | |
9922 | insert any postamble. | |
9923 | ||
9924 | @node Quoting HTML tags, Links in HTML export, HTML preamble and postamble, HTML export | |
4009494e GM |
9925 | @subsection Quoting HTML tags |
9926 | ||
9927 | Plain @samp{<} and @samp{>} are always transformed to @samp{<} and | |
9928 | @samp{>} in HTML export. If you want to include simple HTML tags | |
9929 | which should be interpreted as such, mark them with @samp{@@} as in | |
9930 | @samp{@@<b>bold text@@</b>}. Note that this really works only for | |
9931 | simple tags. For more extensive HTML that should be copied verbatim to | |
9932 | the exported file use either | |
9933 | ||
c8d0cf5c CD |
9934 | @cindex #+HTML |
9935 | @cindex #+BEGIN_HTML | |
4009494e GM |
9936 | @example |
9937 | #+HTML: Literal HTML code for export | |
9938 | @end example | |
9939 | ||
9940 | @noindent or | |
b349f79f | 9941 | @cindex #+BEGIN_HTML |
4009494e GM |
9942 | |
9943 | @example | |
9944 | #+BEGIN_HTML | |
9945 | All lines between these markers are exported literally | |
9946 | #+END_HTML | |
9947 | @end example | |
9948 | ||
9949 | ||
a351880d CD |
9950 | @node Links in HTML export, Tables in HTML export, Quoting HTML tags, HTML export |
9951 | @subsection Links in HTML export | |
4009494e GM |
9952 | |
9953 | @cindex links, in HTML export | |
9954 | @cindex internal links, in HTML export | |
9955 | @cindex external links, in HTML export | |
55e0839d | 9956 | Internal links (@pxref{Internal links}) will continue to work in HTML. This |
c8d0cf5c | 9957 | includes automatic links created by radio targets (@pxref{Radio |
55e0839d CD |
9958 | targets}). Links to external files will still work if the target file is on |
9959 | the same @i{relative} path as the published Org file. Links to other | |
9960 | @file{.org} files will be translated into HTML links under the assumption | |
9961 | that an HTML version also exists of the linked file, at the same relative | |
9962 | path. @samp{id:} links can then be used to jump to specific entries across | |
9963 | files. For information related to linking files while publishing them to a | |
9964 | publishing directory see @ref{Publishing links}. | |
4009494e | 9965 | |
44ce9197 | 9966 | If you want to specify attributes for links, you can do so using a special |
a50253cc | 9967 | @code{#+ATTR_HTML} line to define attributes that will be added to the |
c8d0cf5c CD |
9968 | @code{<a>} or @code{<img>} tags. Here is an example that sets @code{title} |
9969 | and @code{style} attributes for a link: | |
44ce9197 | 9970 | |
c8d0cf5c | 9971 | @cindex #+ATTR_HTML |
44ce9197 | 9972 | @example |
e66ba1df | 9973 | #+ATTR_HTML: title="The Org mode homepage" style="color:red;" |
c8d0cf5c CD |
9974 | [[http://orgmode.org]] |
9975 | @end example | |
9976 | ||
a351880d | 9977 | @node Tables in HTML export, Images in HTML export, Links in HTML export, HTML export |
c8d0cf5c CD |
9978 | @subsection Tables |
9979 | @cindex tables, in HTML | |
9980 | @vindex org-export-html-table-tag | |
9981 | ||
e66ba1df | 9982 | Org mode tables are exported to HTML using the table tag defined in |
c8d0cf5c CD |
9983 | @code{org-export-html-table-tag}. The default setting makes tables without |
9984 | cell borders and frame. If you would like to change this for individual | |
86fbb8ca | 9985 | tables, place something like the following before the table: |
c8d0cf5c CD |
9986 | |
9987 | @cindex #+CAPTION | |
a351880d | 9988 | @cindex #+ATTR_HTML |
c8d0cf5c CD |
9989 | @example |
9990 | #+CAPTION: This is a table with lines around and between cells | |
e66ba1df | 9991 | #+ATTR_HTML: border="2" rules="all" frame="border" |
44ce9197 CD |
9992 | @end example |
9993 | ||
afe98dfa | 9994 | @node Images in HTML export, Math formatting in HTML export, Tables in HTML export, HTML export |
a351880d | 9995 | @subsection Images in HTML export |
4009494e GM |
9996 | |
9997 | @cindex images, inline in HTML | |
9998 | @cindex inlining images in HTML | |
c8d0cf5c | 9999 | @vindex org-export-html-inline-images |
a7808fba | 10000 | HTML export can inline images given as links in the Org file, and |
4009494e | 10001 | it can make an image the clickable part of a link. By |
c8d0cf5c CD |
10002 | default@footnote{But see the variable |
10003 | @code{org-export-html-inline-images}.}, images are inlined if a link does | |
4009494e GM |
10004 | not have a description. So @samp{[[file:myimg.jpg]]} will be inlined, |
10005 | while @samp{[[file:myimg.jpg][the image]]} will just produce a link | |
10006 | @samp{the image} that points to the image. If the description part | |
10007 | itself is a @code{file:} link or a @code{http:} URL pointing to an | |
10008 | image, this image will be inlined and activated so that clicking on the | |
10009 | image will activate the link. For example, to include a thumbnail that | |
10010 | will link to a high resolution version of the image, you could use: | |
10011 | ||
10012 | @example | |
10013 | [[file:highres.jpg][file:thumb.jpg]] | |
10014 | @end example | |
10015 | ||
86fbb8ca | 10016 | If you need to add attributes to an inlined image, use a @code{#+ATTR_HTML}. |
a351880d CD |
10017 | In the example below we specify the @code{alt} and @code{title} attributes to |
10018 | support text viewers and accessibility, and align it to the right. | |
c8d0cf5c CD |
10019 | |
10020 | @cindex #+CAPTION | |
a351880d | 10021 | @cindex #+ATTR_HTML |
c8d0cf5c CD |
10022 | @example |
10023 | #+CAPTION: A black cat stalking a spider | |
a351880d | 10024 | #+ATTR_HTML: alt="cat/spider image" title="Action!" align="right" |
c8d0cf5c CD |
10025 | [[./img/a.jpg]] |
10026 | @end example | |
10027 | ||
4009494e | 10028 | @noindent |
ce57c2fe | 10029 | You could use @code{http} addresses just as well. |
4009494e | 10030 | |
afe98dfa CD |
10031 | @node Math formatting in HTML export, Text areas in HTML export, Images in HTML export, HTML export |
10032 | @subsection Math formatting in HTML export | |
10033 | @cindex MathJax | |
10034 | @cindex dvipng | |
10035 | ||
e66ba1df | 10036 | @LaTeX{} math snippets (@pxref{@LaTeX{} fragments}) can be displayed in two |
afe98dfa CD |
10037 | different ways on HTML pages. The default is to use the |
10038 | @uref{http://www.mathjax.org, MathJax system} which should work out of the | |
10039 | box with Org mode installation because @code{http://orgmode.org} serves | |
e66ba1df | 10040 | @file{MathJax} for Org mode users for small applications and for testing |
afe98dfa | 10041 | purposes. @b{If you plan to use this regularly or on pages with significant |
acedf35c CD |
10042 | page views, you should install@footnote{Installation instructions can be |
10043 | found on the MathJax website, see | |
10044 | @uref{http://www.mathjax.org/resources/docs/?installation.html}.} MathJax on | |
10045 | your own server in order to limit the load of our server.} To configure | |
10046 | @file{MathJax}, use the variable @code{org-export-html-mathjax-options} or | |
10047 | insert something like the following into the buffer: | |
afe98dfa CD |
10048 | |
10049 | @example | |
10050 | #+MATHJAX: align:"left" mathml:t path:"/MathJax/MathJax.js" | |
10051 | @end example | |
10052 | ||
10053 | @noindent See the docstring of the variable | |
10054 | @code{org-export-html-mathjax-options} for the meaning of the parameters in | |
10055 | this line. | |
10056 | ||
acedf35c CD |
10057 | If you prefer, you can also request that @LaTeX{} fragments are processed |
10058 | into small images that will be inserted into the browser page. Before the | |
10059 | availability of MathJax, this was the default method for Org files. This | |
10060 | method requires that the @file{dvipng} program is available on your system. | |
10061 | You can still get this processing with | |
afe98dfa CD |
10062 | |
10063 | @example | |
10064 | #+OPTIONS: LaTeX:dvipng | |
10065 | @end example | |
10066 | ||
10067 | @node Text areas in HTML export, CSS support, Math formatting in HTML export, HTML export | |
a351880d | 10068 | @subsection Text areas in HTML export |
55e0839d CD |
10069 | |
10070 | @cindex text areas, in HTML | |
10071 | An alternative way to publish literal code examples in HTML is to use text | |
10072 | areas, where the example can even be edited before pasting it into an | |
10073 | application. It is triggered by a @code{-t} switch at an @code{example} or | |
10074 | @code{src} block. Using this switch disables any options for syntax and | |
10075 | label highlighting, and line numbering, which may be present. You may also | |
10076 | use @code{-h} and @code{-w} switches to specify the height and width of the | |
10077 | text area, which default to the number of lines in the example, and 80, | |
10078 | respectively. For example | |
10079 | ||
10080 | @example | |
10081 | #+BEGIN_EXAMPLE -t -w 40 | |
86fbb8ca CD |
10082 | (defun org-xor (a b) |
10083 | "Exclusive or." | |
10084 | (if a (not b) b)) | |
55e0839d CD |
10085 | #+END_EXAMPLE |
10086 | @end example | |
10087 | ||
10088 | ||
86fbb8ca | 10089 | @node CSS support, JavaScript support, Text areas in HTML export, HTML export |
4009494e | 10090 | @subsection CSS support |
a7808fba CD |
10091 | @cindex CSS, for HTML export |
10092 | @cindex HTML export, CSS | |
4009494e | 10093 | |
c8d0cf5c CD |
10094 | @vindex org-export-html-todo-kwd-class-prefix |
10095 | @vindex org-export-html-tag-class-prefix | |
55e0839d | 10096 | You can also give style information for the exported file. The HTML exporter |
c8d0cf5c CD |
10097 | assigns the following special CSS classes@footnote{If the classes on TODO |
10098 | keywords and tags lead to conflicts, use the variables | |
10099 | @code{org-export-html-todo-kwd-class-prefix} and | |
10100 | @code{org-export-html-tag-class-prefix} to make them unique.} to appropriate | |
10101 | parts of the document---your style specifications may change these, in | |
10102 | addition to any of the standard classes like for headlines, tables, etc. | |
10103 | @example | |
10104 | p.author @r{author information, including email} | |
10105 | p.date @r{publishing date} | |
e66ba1df | 10106 | p.creator @r{creator info, about org mode version} |
c8d0cf5c CD |
10107 | .title @r{document title} |
10108 | .todo @r{TODO keywords, all not-done states} | |
ce57c2fe | 10109 | .done @r{the DONE keywords, all states that count as done} |
c8d0cf5c CD |
10110 | .WAITING @r{each TODO keyword also uses a class named after itself} |
10111 | .timestamp @r{timestamp} | |
10112 | .timestamp-kwd @r{keyword associated with a timestamp, like SCHEDULED} | |
10113 | .timestamp-wrapper @r{span around keyword plus timestamp} | |
10114 | .tag @r{tag in a headline} | |
10115 | ._HOME @r{each tag uses itself as a class, "@@" replaced by "_"} | |
10116 | .target @r{target for links} | |
10117 | .linenr @r{the line number in a code example} | |
10118 | .code-highlighted @r{for highlighting referenced code lines} | |
10119 | div.outline-N @r{div for outline level N (headline plus text))} | |
10120 | div.outline-text-N @r{extra div for text at outline level N} | |
10121 | .section-number-N @r{section number in headlines, different for each level} | |
10122 | div.figure @r{how to format an inlined image} | |
10123 | pre.src @r{formatted source code} | |
10124 | pre.example @r{normal example} | |
10125 | p.verse @r{verse paragraph} | |
10126 | div.footnotes @r{footnote section headline} | |
10127 | p.footnote @r{footnote definition paragraph, containing a footnote} | |
10128 | .footref @r{a footnote reference number (always a <sup>)} | |
10129 | .footnum @r{footnote number in footnote definition (always <sup>)} | |
10130 | @end example | |
10131 | ||
10132 | @vindex org-export-html-style-default | |
10133 | @vindex org-export-html-style-include-default | |
10134 | @vindex org-export-html-style | |
10135 | @vindex org-export-html-extra | |
10136 | @vindex org-export-html-style-default | |
10137 | Each exported file contains a compact default style that defines these | |
e45e3595 CD |
10138 | classes in a basic way@footnote{This style is defined in the constant |
10139 | @code{org-export-html-style-default}, which you should not modify. To turn | |
10140 | inclusion of these defaults off, customize | |
10141 | @code{org-export-html-style-include-default}}. You may overwrite these | |
10142 | settings, or add to them by using the variables @code{org-export-html-style} | |
10143 | (for Org-wide settings) and @code{org-export-html-style-extra} (for more | |
acedf35c | 10144 | fine-grained settings, like file-local settings). To set the latter variable |
e45e3595 | 10145 | individually for each file, you can use |
4009494e | 10146 | |
c8d0cf5c | 10147 | @cindex #+STYLE |
4009494e | 10148 | @example |
864c9740 | 10149 | #+STYLE: <link rel="stylesheet" type="text/css" href="stylesheet.css" /> |
4009494e GM |
10150 | @end example |
10151 | ||
864c9740 | 10152 | @noindent |
e45e3595 CD |
10153 | For longer style definitions, you can use several such lines. You could also |
10154 | directly write a @code{<style>} @code{</style>} section in this way, without | |
10155 | referring to an external file. | |
4009494e | 10156 | |
afe98dfa CD |
10157 | In order to add styles to a subtree, use the @code{:HTML_CONTAINER_CLASS:} |
10158 | property to assign a class to the tree. In order to specify CSS styles for a | |
10159 | particular headline, you can use the id specified in a @code{:CUSTOM_ID:} | |
10160 | property. | |
10161 | ||
4009494e GM |
10162 | @c FIXME: More about header and footer styles |
10163 | @c FIXME: Talk about links and targets. | |
10164 | ||
86fbb8ca CD |
10165 | @node JavaScript support, , CSS support, HTML export |
10166 | @subsection JavaScript supported display of web pages | |
a7808fba | 10167 | |
c8d0cf5c CD |
10168 | @cindex Rose, Sebastian |
10169 | Sebastian Rose has written a JavaScript program especially designed to | |
a7808fba | 10170 | enhance the web viewing experience of HTML files created with Org. This |
55e0839d CD |
10171 | program allows you to view large files in two different ways. The first one |
10172 | is an @emph{Info}-like mode where each section is displayed separately and | |
a7808fba CD |
10173 | navigation can be done with the @kbd{n} and @kbd{p} keys (and some other keys |
10174 | as well, press @kbd{?} for an overview of the available keys). The second | |
55e0839d CD |
10175 | view type is a @emph{folding} view much like Org provides inside Emacs. The |
10176 | script is available at @url{http://orgmode.org/org-info.js} and you can find | |
10177 | the documentation for it at @url{http://orgmode.org/worg/code/org-info-js/}. | |
c8d0cf5c | 10178 | We host the script at our site, but if you use it a lot, you might |
55e0839d CD |
10179 | not want to be dependent on @url{orgmode.org} and prefer to install a local |
10180 | copy on your own web server. | |
a7808fba | 10181 | |
b349f79f | 10182 | To use the script, you need to make sure that the @file{org-jsinfo.el} module |
b6cb4cd5 CD |
10183 | gets loaded. It should be loaded by default, but you can try @kbd{M-x |
10184 | customize-variable @key{RET} org-modules @key{RET}} to convince yourself that | |
10185 | this is indeed the case. All it then takes to make use of the program is | |
10186 | adding a single line to the Org file: | |
a7808fba | 10187 | |
c8d0cf5c | 10188 | @cindex #+INFOJS_OPT |
a7808fba | 10189 | @example |
b349f79f | 10190 | #+INFOJS_OPT: view:info toc:nil |
a7808fba CD |
10191 | @end example |
10192 | ||
10193 | @noindent | |
10194 | If this line is found, the HTML header will automatically contain the code | |
10195 | needed to invoke the script. Using the line above, you can set the following | |
10196 | viewing options: | |
10197 | ||
10198 | @example | |
10199 | path: @r{The path to the script. The default is to grab the script from} | |
10200 | @r{@url{http://orgmode.org/org-info.js}, but you might want to have} | |
10201 | @r{a local copy and use a path like @samp{../scripts/org-info.js}.} | |
b349f79f | 10202 | view: @r{Initial view when website is first shown. Possible values are:} |
a7808fba CD |
10203 | info @r{Info-like interface with one section per page.} |
10204 | overview @r{Folding interface, initially showing only top-level.} | |
10205 | content @r{Folding interface, starting with all headlines visible.} | |
10206 | showall @r{Folding interface, all headlines and text visible.} | |
10207 | sdepth: @r{Maximum headline level that will still become an independent} | |
10208 | @r{section for info and folding modes. The default is taken from} | |
7006d207 CD |
10209 | @r{@code{org-export-headline-levels} (= the @code{H} switch in @code{#+OPTIONS}).} |
10210 | @r{If this is smaller than in @code{org-export-headline-levels}, each} | |
c8d0cf5c | 10211 | @r{info/folding section can still contain child headlines.} |
acedf35c | 10212 | toc: @r{Should the table of contents @emph{initially} be visible?} |
c8d0cf5c | 10213 | @r{Even when @code{nil}, you can always get to the "toc" with @kbd{i}.} |
a7808fba | 10214 | tdepth: @r{The depth of the table of contents. The defaults are taken from} |
7006d207 | 10215 | @r{the variables @code{org-export-headline-levels} and @code{org-export-with-toc}.} |
acedf35c | 10216 | ftoc: @r{Does the CSS of the page specify a fixed position for the "toc"?} |
b349f79f | 10217 | @r{If yes, the toc will never be displayed as a section.} |
a7808fba | 10218 | ltoc: @r{Should there be short contents (children) in each section?} |
c8d0cf5c | 10219 | @r{Make this @code{above} if the section should be above initial text.} |
a7808fba CD |
10220 | mouse: @r{Headings are highlighted when the mouse is over them. Should be} |
10221 | @r{@samp{underline} (default) or a background color like @samp{#cccccc}.} | |
10222 | buttons: @r{Should view-toggle buttons be everywhere? When @code{nil} (the} | |
10223 | @r{default), only one such button will be present.} | |
10224 | @end example | |
c8d0cf5c CD |
10225 | @noindent |
10226 | @vindex org-infojs-options | |
10227 | @vindex org-export-html-use-infojs | |
a7808fba CD |
10228 | You can choose default values for these options by customizing the variable |
10229 | @code{org-infojs-options}. If you always want to apply the script to your | |
10230 | pages, configure the variable @code{org-export-html-use-infojs}. | |
10231 | ||
e66ba1df | 10232 | @node @LaTeX{} and PDF export, DocBook export, HTML export, Exporting |
acedf35c CD |
10233 | @section @LaTeX{} and PDF export |
10234 | @cindex @LaTeX{} export | |
71d35b24 | 10235 | @cindex PDF export |
72d803ad | 10236 | @cindex Guerry, Bastien |
4009494e | 10237 | |
e66ba1df BG |
10238 | Org mode contains a @LaTeX{} exporter written by Bastien Guerry. With |
10239 | further processing@footnote{The default @LaTeX{} output is designed for | |
10240 | processing with @code{pdftex} or @LaTeX{}. It includes packages that are not | |
10241 | compatible with @code{xetex} and possibly @code{luatex}. See the variables | |
ed21c5c8 CD |
10242 | @code{org-export-latex-default-packages-alist} and |
10243 | @code{org-export-latex-packages-alist}.}, this backend is also used to | |
acedf35c | 10244 | produce PDF output. Since the @LaTeX{} output uses @file{hyperref} to |
ed21c5c8 | 10245 | implement links and cross references, the PDF output file will be fully |
ce57c2fe BG |
10246 | linked. Beware of the fact that your @code{org} file has to be properly |
10247 | structured in order to be correctly exported: respect the hierarchy of | |
10248 | sections. | |
4009494e GM |
10249 | |
10250 | @menu | |
e66ba1df | 10251 | * @LaTeX{}/PDF export commands:: |
c0468714 | 10252 | * Header and sectioning:: Setting up the export file structure |
e66ba1df BG |
10253 | * Quoting @LaTeX{} code:: Incorporating literal @LaTeX{} code |
10254 | * Tables in @LaTeX{} export:: Options for exporting tables to @LaTeX{} | |
10255 | * Images in @LaTeX{} export:: How to insert figures into @LaTeX{} output | |
c0468714 | 10256 | * Beamer class export:: Turning the file into a presentation |
4009494e GM |
10257 | @end menu |
10258 | ||
e66ba1df | 10259 | @node @LaTeX{}/PDF export commands, Header and sectioning, @LaTeX{} and PDF export, @LaTeX{} and PDF export |
acedf35c | 10260 | @subsection @LaTeX{} export commands |
4009494e | 10261 | |
b6cb4cd5 CD |
10262 | @cindex region, active |
10263 | @cindex active region | |
10264 | @cindex transient-mark-mode | |
4009494e | 10265 | @table @kbd |
acedf35c | 10266 | @orgcmd{C-c C-e l,org-export-as-latex} |
c8d0cf5c | 10267 | @cindex property EXPORT_FILE_NAME |
ce57c2fe BG |
10268 | Export as @LaTeX{} file. For an Org file |
10269 | @file{myfile.org}, the @LaTeX{} file will be @file{myfile.tex}. The file will | |
c8d0cf5c CD |
10270 | be overwritten without warning. If there is an active region@footnote{This |
10271 | requires @code{transient-mark-mode} be turned on.}, only the region will be | |
ce57c2fe | 10272 | exported. If the selected region is a single tree@footnote{To select the |
b6cb4cd5 CD |
10273 | current subtree, use @kbd{C-c @@}.}, the tree head will become the document |
10274 | title. If the tree head entry has or inherits an @code{EXPORT_FILE_NAME} | |
10275 | property, that name will be used for the export. | |
acedf35c CD |
10276 | @orgcmd{C-c C-e L,org-export-as-latex-to-buffer} |
10277 | Export to a temporary buffer. Do not create a file. | |
ce57c2fe | 10278 | @item C-c C-e v l/L |
4009494e GM |
10279 | Export only the visible part of the document. |
10280 | @item M-x org-export-region-as-latex | |
e66ba1df | 10281 | Convert the region to @LaTeX{} under the assumption that it was Org mode |
4009494e GM |
10282 | syntax before. This is a global command that can be invoked in any |
10283 | buffer. | |
10284 | @item M-x org-replace-region-by-latex | |
e66ba1df | 10285 | Replace the active region (assumed to be in Org mode syntax) by @LaTeX{} |
4009494e | 10286 | code. |
acedf35c CD |
10287 | @orgcmd{C-c C-e p,org-export-as-pdf} |
10288 | Export as @LaTeX{} and then process to PDF. | |
10289 | @orgcmd{C-c C-e d,org-export-as-pdf-and-open} | |
10290 | Export as @LaTeX{} and then process to PDF, then open the resulting PDF file. | |
4009494e GM |
10291 | @end table |
10292 | ||
10293 | @cindex headline levels, for exporting | |
c8d0cf5c | 10294 | @vindex org-latex-low-levels |
4009494e GM |
10295 | In the exported version, the first 3 outline levels will become |
10296 | headlines, defining a general document structure. Additional levels | |
10297 | will be exported as description lists. The exporter can ignore them or | |
10298 | convert them to a custom string depending on | |
10299 | @code{org-latex-low-levels}. | |
10300 | ||
10301 | If you want that transition to occur at a different level, specify it | |
ce57c2fe | 10302 | with a numeric prefix argument. For example, |
4009494e GM |
10303 | |
10304 | @example | |
10305 | @kbd{C-2 C-c C-e l} | |
10306 | @end example | |
10307 | ||
10308 | @noindent | |
10309 | creates two levels of headings and does the rest as items. | |
10310 | ||
e66ba1df | 10311 | @node Header and sectioning, Quoting @LaTeX{} code, @LaTeX{}/PDF export commands, @LaTeX{} and PDF export |
ed21c5c8 | 10312 | @subsection Header and sectioning structure |
acedf35c CD |
10313 | @cindex @LaTeX{} class |
10314 | @cindex @LaTeX{} sectioning structure | |
10315 | @cindex @LaTeX{} header | |
e66ba1df BG |
10316 | @cindex header, for @LaTeX{} files |
10317 | @cindex sectioning structure, for @LaTeX{} export | |
ed21c5c8 | 10318 | |
acedf35c | 10319 | By default, the @LaTeX{} output uses the class @code{article}. |
ed21c5c8 CD |
10320 | |
10321 | @vindex org-export-latex-default-class | |
10322 | @vindex org-export-latex-classes | |
10323 | @vindex org-export-latex-default-packages-alist | |
10324 | @vindex org-export-latex-packages-alist | |
10325 | @cindex #+LATEX_HEADER | |
10326 | @cindex #+LATEX_CLASS | |
10327 | @cindex #+LATEX_CLASS_OPTIONS | |
10328 | @cindex property, LATEX_CLASS | |
10329 | @cindex property, LATEX_CLASS_OPTIONS | |
10330 | You can change this globally by setting a different value for | |
10331 | @code{org-export-latex-default-class} or locally by adding an option like | |
10332 | @code{#+LaTeX_CLASS: myclass} in your file, or with a @code{:LaTeX_CLASS:} | |
10333 | property that applies when exporting a region containing only this (sub)tree. | |
10334 | The class must be listed in @code{org-export-latex-classes}. This variable | |
10335 | defines a header template for each class@footnote{Into which the values of | |
10336 | @code{org-export-latex-default-packages-alist} and | |
10337 | @code{org-export-latex-packages-alist} are spliced.}, and allows you to | |
10338 | define the sectioning structure for each class. You can also define your own | |
10339 | classes there. @code{#+LaTeX_CLASS_OPTIONS} or a @code{LaTeX_CLASS_OPTIONS} | |
10340 | property can specify the options for the @code{\documentclass} macro. You | |
10341 | can also use @code{#+LATEX_HEADER: \usepackage@{xyz@}} to add lines to the | |
10342 | header. See the docstring of @code{org-export-latex-classes} for more | |
10343 | information. | |
10344 | ||
e66ba1df | 10345 | @node Quoting @LaTeX{} code, Tables in @LaTeX{} export, Header and sectioning, @LaTeX{} and PDF export |
acedf35c | 10346 | @subsection Quoting @LaTeX{} code |
4009494e | 10347 | |
e66ba1df | 10348 | Embedded @LaTeX{} as described in @ref{Embedded @LaTeX{}}, will be correctly |
acedf35c | 10349 | inserted into the @LaTeX{} file. This includes simple macros like |
55e0839d | 10350 | @samp{\ref@{LABEL@}} to create a cross reference to a figure. Furthermore, |
acedf35c | 10351 | you can add special code that should only be present in @LaTeX{} export with |
55e0839d | 10352 | the following constructs: |
4009494e | 10353 | |
c8d0cf5c CD |
10354 | @cindex #+LaTeX |
10355 | @cindex #+BEGIN_LaTeX | |
4009494e | 10356 | @example |
e66ba1df | 10357 | #+LaTeX: Literal @LaTeX{} code for export |
4009494e GM |
10358 | @end example |
10359 | ||
10360 | @noindent or | |
b349f79f | 10361 | @cindex #+BEGIN_LaTeX |
4009494e GM |
10362 | |
10363 | @example | |
10364 | #+BEGIN_LaTeX | |
10365 | All lines between these markers are exported literally | |
10366 | #+END_LaTeX | |
10367 | @end example | |
dbc28aaa | 10368 | |
dbc28aaa | 10369 | |
e66ba1df | 10370 | @node Tables in @LaTeX{} export, Images in @LaTeX{} export, Quoting @LaTeX{} code, @LaTeX{} and PDF export |
acedf35c CD |
10371 | @subsection Tables in @LaTeX{} export |
10372 | @cindex tables, in @LaTeX{} export | |
67df9cfb | 10373 | |
ce57c2fe BG |
10374 | For @LaTeX{} export of a table, you can specify a label, a caption and |
10375 | placement options (@pxref{Images and tables}). You can also use the | |
10376 | @code{ATTR_LaTeX} line to request a @code{longtable} environment for the | |
10377 | table, so that it may span several pages, or to change the default table | |
10378 | environment from @code{table} to @code{table*} or to change the default inner | |
10379 | tabular environment to @code{tabularx} or @code{tabulary}. Finally, you can | |
10380 | set the alignment string, and (with @code{tabularx} or @code{tabulary}) the | |
10381 | width: | |
67df9cfb | 10382 | |
c8d0cf5c CD |
10383 | @cindex #+CAPTION |
10384 | @cindex #+LABEL | |
10385 | @cindex #+ATTR_LaTeX | |
67df9cfb CD |
10386 | @example |
10387 | #+CAPTION: A long table | |
10388 | #+LABEL: tbl:long | |
c8d0cf5c | 10389 | #+ATTR_LaTeX: longtable align=l|lp@{3cm@}r|l |
67df9cfb CD |
10390 | | ..... | ..... | |
10391 | | ..... | ..... | | |
10392 | @end example | |
10393 | ||
ce57c2fe BG |
10394 | or to specify a multicolumn table with @code{tabulary} |
10395 | ||
10396 | @cindex #+CAPTION | |
10397 | @cindex #+LABEL | |
10398 | @cindex #+ATTR_LaTeX | |
10399 | @example | |
10400 | #+CAPTION: A wide table with tabulary | |
10401 | #+LABEL: tbl:wide | |
10402 | #+ATTR_LaTeX: table* tabulary width=\textwidth | |
10403 | | ..... | ..... | | |
10404 | | ..... | ..... | | |
10405 | @end example | |
67df9cfb | 10406 | |
e66ba1df | 10407 | @node Images in @LaTeX{} export, Beamer class export, Tables in @LaTeX{} export, @LaTeX{} and PDF export |
acedf35c CD |
10408 | @subsection Images in @LaTeX{} export |
10409 | @cindex images, inline in @LaTeX{} | |
10410 | @cindex inlining images in @LaTeX{} | |
67df9cfb CD |
10411 | |
10412 | Images that are linked to without a description part in the link, like | |
10413 | @samp{[[file:img.jpg]]} or @samp{[[./img.jpg]]} will be inserted into the PDF | |
acedf35c | 10414 | output file resulting from @LaTeX{} processing. Org will use an |
67df9cfb | 10415 | @code{\includegraphics} macro to insert the image. If you have specified a |
a351880d CD |
10416 | caption and/or a label as described in @ref{Images and tables}, the figure |
10417 | will be wrapped into a @code{figure} environment and thus become a floating | |
ce57c2fe BG |
10418 | element. You can use an @code{#+ATTR_LaTeX:} line to specify various other |
10419 | options. You can ask org to export an image as a float without specifying | |
10420 | a label or a caption by using the keyword @code{float} in this line. Various | |
10421 | optional arguments to the @code{\includegraphics} macro can also be specified | |
10422 | in this fashion. To modify the placement option of the floating environment, | |
10423 | add something like @samp{placement=[h!]} to the attributes. It is to be noted | |
10424 | this option can be used with tables as well@footnote{One can also take | |
10425 | advantage of this option to pass other, unrelated options into the figure or | |
10426 | table environment. For an example see the section ``Exporting org files'' in | |
10427 | @url{http://orgmode.org/worg/org-hacks.html}}. For example the | |
10428 | @code{#+ATTR_LaTeX:} line below is exported as the @code{figure} environment | |
10429 | below it. | |
a351880d | 10430 | |
86fbb8ca CD |
10431 | If you would like to let text flow around the image, add the word @samp{wrap} |
10432 | to the @code{#+ATTR_LaTeX:} line, which will make the figure occupy the left | |
10433 | half of the page. To fine-tune, the @code{placement} field will be the set | |
10434 | of additional arguments needed by the @code{wrapfigure} environment. Note | |
10435 | that if you change the size of the image, you need to use compatible settings | |
10436 | for @code{\includegraphics} and @code{wrapfigure}. | |
67df9cfb | 10437 | |
c8d0cf5c CD |
10438 | @cindex #+CAPTION |
10439 | @cindex #+LABEL | |
10440 | @cindex #+ATTR_LaTeX | |
67df9cfb CD |
10441 | @example |
10442 | #+CAPTION: The black-body emission of the disk around HR 4049 | |
10443 | #+LABEL: fig:SED-HR4049 | |
10444 | #+ATTR_LaTeX: width=5cm,angle=90 | |
10445 | [[./img/sed-hr4049.pdf]] | |
a351880d CD |
10446 | |
10447 | #+ATTR_LaTeX: width=0.38\textwidth wrap placement=@{r@}@{0.4\textwidth@} | |
10448 | [[./img/hst.png]] | |
67df9cfb CD |
10449 | @end example |
10450 | ||
ce57c2fe BG |
10451 | If you wish to include an image which spans multiple columns in a page, you |
10452 | can use the keyword @code{multicolumn} in the @code{#+ATTR_LaTeX} line. This | |
10453 | will export the image wrapped in a @code{figure*} environment. | |
10454 | ||
55e0839d | 10455 | If you need references to a label created in this way, write |
acedf35c | 10456 | @samp{\ref@{fig:SED-HR4049@}} just like in @LaTeX{}. |
67df9cfb | 10457 | |
e66ba1df | 10458 | @node Beamer class export, , Images in @LaTeX{} export, @LaTeX{} and PDF export |
ed21c5c8 CD |
10459 | @subsection Beamer class export |
10460 | ||
e66ba1df BG |
10461 | The @LaTeX{} class @file{beamer} allows production of high quality presentations |
10462 | using @LaTeX{} and pdf processing. Org mode has special support for turning an | |
10463 | Org mode file or tree into a @file{beamer} presentation. | |
ed21c5c8 | 10464 | |
e66ba1df | 10465 | When the @LaTeX{} class for the current buffer (as set with @code{#+LaTeX_CLASS: |
ed21c5c8 CD |
10466 | beamer}) or subtree (set with a @code{LaTeX_CLASS} property) is |
10467 | @code{beamer}, a special export mode will turn the file or tree into a beamer | |
86fbb8ca | 10468 | presentation. Any tree with not-too-deep level nesting should in principle be |
ed21c5c8 CD |
10469 | exportable as a beamer presentation. By default, the top-level entries (or |
10470 | the first level below the selected subtree heading) will be turned into | |
10471 | frames, and the outline structure below this level will become itemize lists. | |
10472 | You can also configure the variable @code{org-beamer-frame-level} to a | |
acedf35c | 10473 | different level---then the hierarchy above frames will produce the sectioning |
ed21c5c8 CD |
10474 | structure of the presentation. |
10475 | ||
10476 | A template for useful in-buffer settings or properties can be inserted into | |
afe98dfa CD |
10477 | the buffer with @kbd{M-x org-insert-beamer-options-template}. Among other |
10478 | things, this will install a column view format which is very handy for | |
10479 | editing special properties used by beamer. | |
ed21c5c8 CD |
10480 | |
10481 | You can influence the structure of the presentation using the following | |
10482 | properties: | |
10483 | ||
10484 | @table @code | |
10485 | @item BEAMER_env | |
10486 | The environment that should be used to format this entry. Valid environments | |
10487 | are defined in the constant @code{org-beamer-environments-default}, and you | |
10488 | can define more in @code{org-beamer-environments-extra}. If this property is | |
10489 | set, the entry will also get a @code{:B_environment:} tag to make this | |
10490 | visible. This tag has no semantic meaning, it is only a visual aid. | |
10491 | @item BEAMER_envargs | |
10492 | The beamer-special arguments that should be used for the environment, like | |
10493 | @code{[t]} or @code{[<+->]} of @code{<2-3>}. If the @code{BEAMER_col} | |
10494 | property is also set, something like @code{C[t]} can be added here as well to | |
10495 | set an options argument for the implied @code{columns} environment. | |
acedf35c CD |
10496 | @code{c[t]} or @code{c<2->} will set an options for the implied @code{column} |
10497 | environment. | |
ed21c5c8 CD |
10498 | @item BEAMER_col |
10499 | The width of a column that should start with this entry. If this property is | |
10500 | set, the entry will also get a @code{:BMCOL:} property to make this visible. | |
86fbb8ca | 10501 | Also this tag is only a visual aid. When this is a plain number, it will be |
ed21c5c8 CD |
10502 | interpreted as a fraction of @code{\textwidth}. Otherwise it will be assumed |
10503 | that you have specified the units, like @samp{3cm}. The first such property | |
10504 | in a frame will start a @code{columns} environment to surround the columns. | |
10505 | This environment is closed when an entry has a @code{BEAMER_col} property | |
10506 | with value 0 or 1, or automatically at the end of the frame. | |
10507 | @item BEAMER_extra | |
10508 | Additional commands that should be inserted after the environment has been | |
10509 | opened. For example, when creating a frame, this can be used to specify | |
10510 | transitions. | |
10511 | @end table | |
10512 | ||
10513 | Frames will automatically receive a @code{fragile} option if they contain | |
10514 | source code that uses the verbatim environment. Special @file{beamer} | |
10515 | specific code can be inserted using @code{#+BEAMER:} and | |
10516 | @code{#+BEGIN_beamer...#+end_beamer} constructs, similar to other export | |
10517 | backends, but with the difference that @code{#+LaTeX:} stuff will be included | |
10518 | in the presentation as well. | |
10519 | ||
10520 | Outline nodes with @code{BEAMER_env} property value @samp{note} or | |
10521 | @samp{noteNH} will be formatted as beamer notes, i,e, they will be wrapped | |
10522 | into @code{\note@{...@}}. The former will include the heading as part of the | |
10523 | note text, the latter will ignore the heading of that node. To simplify note | |
10524 | generation, it is actually enough to mark the note with a @emph{tag} (either | |
10525 | @code{:B_note:} or @code{:B_noteNH:}) instead of creating the | |
10526 | @code{BEAMER_env} property. | |
10527 | ||
10528 | You can turn on a special minor mode @code{org-beamer-mode} for editing | |
10529 | support with | |
10530 | ||
10531 | @example | |
10532 | #+STARTUP: beamer | |
10533 | @end example | |
10534 | ||
10535 | @table @kbd | |
acedf35c | 10536 | @orgcmd{C-c C-b,org-beamer-select-environment} |
ed21c5c8 CD |
10537 | In @code{org-beamer-mode}, this key offers fast selection of a beamer |
10538 | environment or the @code{BEAMER_col} property. | |
10539 | @end table | |
10540 | ||
10541 | Column view provides a great way to set the environment of a node and other | |
10542 | important parameters. Make sure you are using a COLUMN format that is geared | |
10543 | toward this special purpose. The command @kbd{M-x | |
afe98dfa | 10544 | org-insert-beamer-options-template} defines such a format. |
ed21c5c8 CD |
10545 | |
10546 | Here is a simple example Org document that is intended for beamer export. | |
10547 | ||
10548 | @smallexample | |
10549 | #+LaTeX_CLASS: beamer | |
10550 | #+TITLE: Example Presentation | |
10551 | #+AUTHOR: Carsten Dominik | |
10552 | #+LaTeX_CLASS_OPTIONS: [presentation] | |
10553 | #+BEAMER_FRAME_LEVEL: 2 | |
10554 | #+BEAMER_HEADER_EXTRA: \usetheme@{Madrid@}\usecolortheme@{default@} | |
10555 | #+COLUMNS: %35ITEM %10BEAMER_env(Env) %10BEAMER_envargs(Args) %4BEAMER_col(Col) %8BEAMER_extra(Ex) | |
10556 | ||
10557 | * This is the first structural section | |
86fbb8ca | 10558 | |
ed21c5c8 CD |
10559 | ** Frame 1 \\ with a subtitle |
10560 | *** Thanks to Eric Fraga :BMCOL:B_block: | |
10561 | :PROPERTIES: | |
10562 | :BEAMER_env: block | |
10563 | :BEAMER_envargs: C[t] | |
10564 | :BEAMER_col: 0.5 | |
10565 | :END: | |
10566 | for the first viable beamer setup in Org | |
10567 | *** Thanks to everyone else :BMCOL:B_block: | |
10568 | :PROPERTIES: | |
10569 | :BEAMER_col: 0.5 | |
10570 | :BEAMER_env: block | |
10571 | :BEAMER_envargs: <2-> | |
10572 | :END: | |
10573 | for contributing to the discussion | |
10574 | **** This will be formatted as a beamer note :B_note: | |
10575 | ** Frame 2 \\ where we will not use columns | |
10576 | *** Request :B_block: | |
10577 | Please test this stuff! | |
10578 | :PROPERTIES: | |
10579 | :BEAMER_env: block | |
10580 | :END: | |
10581 | @end smallexample | |
10582 | ||
10583 | For more information, see the documentation on Worg. | |
10584 | ||
e66ba1df | 10585 | @node DocBook export, OpenDocument Text export, @LaTeX{} and PDF export, Exporting |
c8d0cf5c CD |
10586 | @section DocBook export |
10587 | @cindex DocBook export | |
10588 | @cindex PDF export | |
86fbb8ca | 10589 | @cindex Cui, Baoqiu |
c8d0cf5c CD |
10590 | |
10591 | Org contains a DocBook exporter written by Baoqiu Cui. Once an Org file is | |
10592 | exported to DocBook format, it can be further processed to produce other | |
10593 | formats, including PDF, HTML, man pages, etc., using many available DocBook | |
10594 | tools and stylesheets. | |
10595 | ||
10596 | Currently DocBook exporter only supports DocBook V5.0. | |
10597 | ||
10598 | @menu | |
c0468714 GM |
10599 | * DocBook export commands:: How to invoke DocBook export |
10600 | * Quoting DocBook code:: Incorporating DocBook code in Org files | |
10601 | * Recursive sections:: Recursive sections in DocBook | |
10602 | * Tables in DocBook export:: Tables are exported as HTML tables | |
10603 | * Images in DocBook export:: How to insert figures into DocBook output | |
10604 | * Special characters:: How to handle special characters | |
c8d0cf5c CD |
10605 | @end menu |
10606 | ||
10607 | @node DocBook export commands, Quoting DocBook code, DocBook export, DocBook export | |
10608 | @subsection DocBook export commands | |
10609 | ||
10610 | @cindex region, active | |
10611 | @cindex active region | |
10612 | @cindex transient-mark-mode | |
10613 | @table @kbd | |
acedf35c | 10614 | @orgcmd{C-c C-e D,org-export-as-docbook} |
c8d0cf5c CD |
10615 | @cindex property EXPORT_FILE_NAME |
10616 | Export as DocBook file. For an Org file, @file{myfile.org}, the DocBook XML | |
10617 | file will be @file{myfile.xml}. The file will be overwritten without | |
10618 | warning. If there is an active region@footnote{This requires | |
10619 | @code{transient-mark-mode} to be turned on}, only the region will be | |
10620 | exported. If the selected region is a single tree@footnote{To select the | |
10621 | current subtree, use @kbd{C-c @@}.}, the tree head will become the document | |
10622 | title. If the tree head entry has, or inherits, an @code{EXPORT_FILE_NAME} | |
10623 | property, that name will be used for the export. | |
acedf35c | 10624 | @orgcmd{C-c C-e V,org-export-as-docbook-pdf-and-open} |
c8d0cf5c CD |
10625 | Export as DocBook file, process to PDF, then open the resulting PDF file. |
10626 | ||
10627 | @vindex org-export-docbook-xslt-proc-command | |
10628 | @vindex org-export-docbook-xsl-fo-proc-command | |
10629 | Note that, in order to produce PDF output based on exported DocBook file, you | |
10630 | need to have XSLT processor and XSL-FO processor software installed on your | |
10631 | system. Check variables @code{org-export-docbook-xslt-proc-command} and | |
10632 | @code{org-export-docbook-xsl-fo-proc-command}. | |
10633 | ||
86fbb8ca CD |
10634 | @vindex org-export-docbook-xslt-stylesheet |
10635 | The stylesheet argument @code{%s} in variable | |
10636 | @code{org-export-docbook-xslt-proc-command} is replaced by the value of | |
10637 | variable @code{org-export-docbook-xslt-stylesheet}, which needs to be set by | |
10638 | the user. You can also overrule this global setting on a per-file basis by | |
10639 | adding an in-buffer setting @code{#+XSLT:} to the Org file. | |
10640 | ||
acedf35c | 10641 | @orgkey{C-c C-e v D} |
c8d0cf5c CD |
10642 | Export only the visible part of the document. |
10643 | @end table | |
10644 | ||
10645 | @node Quoting DocBook code, Recursive sections, DocBook export commands, DocBook export | |
10646 | @subsection Quoting DocBook code | |
10647 | ||
10648 | You can quote DocBook code in Org files and copy it verbatim into exported | |
10649 | DocBook file with the following constructs: | |
10650 | ||
10651 | @cindex #+DOCBOOK | |
10652 | @cindex #+BEGIN_DOCBOOK | |
10653 | @example | |
10654 | #+DOCBOOK: Literal DocBook code for export | |
10655 | @end example | |
10656 | ||
10657 | @noindent or | |
10658 | @cindex #+BEGIN_DOCBOOK | |
10659 | ||
10660 | @example | |
10661 | #+BEGIN_DOCBOOK | |
10662 | All lines between these markers are exported by DocBook exporter | |
10663 | literally. | |
10664 | #+END_DOCBOOK | |
10665 | @end example | |
10666 | ||
10667 | For example, you can use the following lines to include a DocBook warning | |
10668 | admonition. As to what this warning says, you should pay attention to the | |
10669 | document context when quoting DocBook code in Org files. You may make | |
10670 | exported DocBook XML files invalid by not quoting DocBook code correctly. | |
10671 | ||
10672 | @example | |
10673 | #+BEGIN_DOCBOOK | |
10674 | <warning> | |
10675 | <para>You should know what you are doing when quoting DocBook XML code | |
acedf35c | 10676 | in your Org file. Invalid DocBook XML may be generated by |
c8d0cf5c CD |
10677 | DocBook exporter if you are not careful!</para> |
10678 | </warning> | |
10679 | #+END_DOCBOOK | |
10680 | @end example | |
10681 | ||
10682 | @node Recursive sections, Tables in DocBook export, Quoting DocBook code, DocBook export | |
10683 | @subsection Recursive sections | |
10684 | @cindex DocBook recursive sections | |
10685 | ||
10686 | DocBook exporter exports Org files as articles using the @code{article} | |
ce57c2fe | 10687 | element in DocBook. Recursive sections, i.e.@: @code{section} elements, are |
c8d0cf5c CD |
10688 | used in exported articles. Top level headlines in Org files are exported as |
10689 | top level sections, and lower level headlines are exported as nested | |
10690 | sections. The entire structure of Org files will be exported completely, no | |
10691 | matter how many nested levels of headlines there are. | |
10692 | ||
10693 | Using recursive sections makes it easy to port and reuse exported DocBook | |
10694 | code in other DocBook document types like @code{book} or @code{set}. | |
10695 | ||
10696 | @node Tables in DocBook export, Images in DocBook export, Recursive sections, DocBook export | |
10697 | @subsection Tables in DocBook export | |
10698 | @cindex tables, in DocBook export | |
10699 | ||
10700 | Tables in Org files are exported as HTML tables, which have been supported since | |
10701 | DocBook V4.3. | |
10702 | ||
10703 | If a table does not have a caption, an informal table is generated using the | |
10704 | @code{informaltable} element; otherwise, a formal table will be generated | |
10705 | using the @code{table} element. | |
10706 | ||
10707 | @node Images in DocBook export, Special characters, Tables in DocBook export, DocBook export | |
10708 | @subsection Images in DocBook export | |
10709 | @cindex images, inline in DocBook | |
10710 | @cindex inlining images in DocBook | |
10711 | ||
10712 | Images that are linked to without a description part in the link, like | |
10713 | @samp{[[file:img.jpg]]} or @samp{[[./img.jpg]]}, will be exported to DocBook | |
10714 | using @code{mediaobject} elements. Each @code{mediaobject} element contains | |
10715 | an @code{imageobject} that wraps an @code{imagedata} element. If you have | |
a351880d | 10716 | specified a caption for an image as described in @ref{Images and tables}, a |
c8d0cf5c CD |
10717 | @code{caption} element will be added in @code{mediaobject}. If a label is |
10718 | also specified, it will be exported as an @code{xml:id} attribute of the | |
10719 | @code{mediaobject} element. | |
10720 | ||
10721 | @vindex org-export-docbook-default-image-attributes | |
10722 | Image attributes supported by the @code{imagedata} element, like @code{align} | |
10723 | or @code{width}, can be specified in two ways: you can either customize | |
10724 | variable @code{org-export-docbook-default-image-attributes} or use the | |
10725 | @code{#+ATTR_DOCBOOK:} line. Attributes specified in variable | |
10726 | @code{org-export-docbook-default-image-attributes} are applied to all inline | |
86fbb8ca | 10727 | images in the Org file to be exported (unless they are overridden by image |
c8d0cf5c CD |
10728 | attributes specified in @code{#+ATTR_DOCBOOK:} lines). |
10729 | ||
10730 | The @code{#+ATTR_DOCBOOK:} line can be used to specify additional image | |
86fbb8ca | 10731 | attributes or override default image attributes for individual images. If |
c8d0cf5c CD |
10732 | the same attribute appears in both the @code{#+ATTR_DOCBOOK:} line and |
10733 | variable @code{org-export-docbook-default-image-attributes}, the former | |
86fbb8ca | 10734 | takes precedence. Here is an example about how image attributes can be |
c8d0cf5c CD |
10735 | set: |
10736 | ||
10737 | @cindex #+CAPTION | |
10738 | @cindex #+LABEL | |
10739 | @cindex #+ATTR_DOCBOOK | |
10740 | @example | |
e66ba1df | 10741 | #+CAPTION: The logo of Org mode |
c8d0cf5c CD |
10742 | #+LABEL: unicorn-svg |
10743 | #+ATTR_DOCBOOK: scalefit="1" width="100%" depth="100%" | |
10744 | [[./img/org-mode-unicorn.svg]] | |
10745 | @end example | |
10746 | ||
10747 | @vindex org-export-docbook-inline-image-extensions | |
10748 | By default, DocBook exporter recognizes the following image file types: | |
10749 | @file{jpeg}, @file{jpg}, @file{png}, @file{gif}, and @file{svg}. You can | |
10750 | customize variable @code{org-export-docbook-inline-image-extensions} to add | |
10751 | more types to this list as long as DocBook supports them. | |
10752 | ||
10753 | @node Special characters, , Images in DocBook export, DocBook export | |
10754 | @subsection Special characters in DocBook export | |
10755 | @cindex Special characters in DocBook export | |
10756 | ||
10757 | @vindex org-export-docbook-doctype | |
86fbb8ca | 10758 | @vindex org-entities |
c8d0cf5c CD |
10759 | Special characters that are written in @TeX{}-like syntax, such as @code{\alpha}, |
10760 | @code{\Gamma}, and @code{\Zeta}, are supported by DocBook exporter. These | |
10761 | characters are rewritten to XML entities, like @code{α}, | |
10762 | @code{Γ}, and @code{Ζ}, based on the list saved in variable | |
86fbb8ca | 10763 | @code{org-entities}. As long as the generated DocBook file includes the |
c8d0cf5c CD |
10764 | corresponding entities, these special characters are recognized. |
10765 | ||
10766 | You can customize variable @code{org-export-docbook-doctype} to include the | |
10767 | entities you need. For example, you can set variable | |
10768 | @code{org-export-docbook-doctype} to the following value to recognize all | |
10769 | special characters included in XHTML entities: | |
10770 | ||
10771 | @example | |
10772 | "<!DOCTYPE article [ | |
10773 | <!ENTITY % xhtml1-symbol PUBLIC | |
10774 | \"-//W3C//ENTITIES Symbol for HTML//EN//XML\" | |
10775 | \"http://www.w3.org/2003/entities/2007/xhtml1-symbol.ent\" | |
10776 | > | |
10777 | %xhtml1-symbol; | |
10778 | ]> | |
10779 | " | |
10780 | @end example | |
10781 | ||
ce57c2fe BG |
10782 | @c begin opendocument |
10783 | ||
e66ba1df BG |
10784 | @node OpenDocument Text export, TaskJuggler export, DocBook export, Exporting |
10785 | @section OpenDocument Text export | |
ce57c2fe | 10786 | @cindex K, Jambunathan |
e66ba1df BG |
10787 | @cindex ODT |
10788 | @cindex OpenDocument | |
10789 | @cindex export, OpenDocument | |
10790 | @cindex LibreOffice | |
10791 | @cindex org-odt.el | |
10792 | @cindex org-modules | |
10793 | ||
10794 | Orgmode@footnote{Versions 7.8 or later} supports export to OpenDocument Text | |
153ae947 | 10795 | (ODT) format using the @file{org-odt.el} module. Documents created |
e66ba1df BG |
10796 | by this exporter use the @cite{OpenDocument-v1.2 |
10797 | specification}@footnote{@url{http://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2.html, | |
10798 | Open Document Format for Office Applications (OpenDocument) Version 1.2}} and | |
10799 | are compatible with LibreOffice 3.4. | |
ce57c2fe BG |
10800 | |
10801 | @menu | |
153ae947 BG |
10802 | * Pre-requisites for ODT export:: What packages ODT exporter relies on |
10803 | * ODT export commands:: How to invoke ODT export | |
10804 | * Extending ODT export:: How to produce @samp{doc}, @samp{pdf} files | |
e66ba1df | 10805 | * Applying custom styles:: How to apply custom styles to the output |
153ae947 BG |
10806 | * Links in ODT export:: How links will be interpreted and formatted |
10807 | * Tables in ODT export:: How Tables are exported | |
10808 | * Images in ODT export:: How to insert images | |
10809 | * Math formatting in ODT export:: How @LaTeX{} fragments are formatted | |
10810 | * Labels and captions in ODT export:: How captions are rendered | |
10811 | * Literal examples in ODT export:: How source and example blocks are formatted | |
10812 | * Advanced topics in ODT export:: Read this if you are a power user | |
ce57c2fe BG |
10813 | @end menu |
10814 | ||
153ae947 BG |
10815 | @node Pre-requisites for ODT export, ODT export commands, OpenDocument Text export, OpenDocument Text export |
10816 | @subsection Pre-requisites for ODT export | |
e66ba1df | 10817 | @cindex zip |
153ae947 | 10818 | The ODT exporter relies on the @file{zip} program to create the final |
e66ba1df BG |
10819 | output. Check the availability of this program before proceeding further. |
10820 | ||
153ae947 BG |
10821 | @node ODT export commands, Extending ODT export, Pre-requisites for ODT export, OpenDocument Text export |
10822 | @subsection ODT export commands | |
e66ba1df | 10823 | |
153ae947 | 10824 | @subsubheading Exporting to ODT |
e66ba1df | 10825 | @anchor{x-export-to-odt} |
ce57c2fe BG |
10826 | |
10827 | @cindex region, active | |
10828 | @cindex active region | |
10829 | @cindex transient-mark-mode | |
10830 | @table @kbd | |
10831 | @orgcmd{C-c C-e o,org-export-as-odt} | |
10832 | @cindex property EXPORT_FILE_NAME | |
e66ba1df BG |
10833 | |
10834 | Export as OpenDocument Text file. | |
153ae947 | 10835 | |
e66ba1df BG |
10836 | @vindex org-export-odt-preferred-output-format |
10837 | If @code{org-export-odt-preferred-output-format} is specified, automatically | |
153ae947 BG |
10838 | convert the exported file to that format. @xref{x-export-to-other-formats, , |
10839 | Automatically exporting to other formats}. | |
e66ba1df | 10840 | |
153ae947 | 10841 | For an Org file @file{myfile.org}, the ODT file will be |
e66ba1df BG |
10842 | @file{myfile.odt}. The file will be overwritten without warning. If there |
10843 | is an active region,@footnote{This requires @code{transient-mark-mode} to be | |
10844 | turned on} only the region will be exported. If the selected region is a | |
10845 | single tree,@footnote{To select the current subtree, use @kbd{C-c @@}} the | |
10846 | tree head will become the document title. If the tree head entry has, or | |
10847 | inherits, an @code{EXPORT_FILE_NAME} property, that name will be used for the | |
10848 | export. | |
10849 | ||
ce57c2fe | 10850 | @orgcmd{C-c C-e O,org-export-as-odt-and-open} |
e66ba1df | 10851 | Export as OpenDocument Text file and open the resulting file. |
153ae947 | 10852 | |
e66ba1df BG |
10853 | @vindex org-export-odt-preferred-output-format |
10854 | If @code{org-export-odt-preferred-output-format} is specified, open the | |
153ae947 BG |
10855 | converted file instead. @xref{x-export-to-other-formats, , Automatically |
10856 | exporting to other formats}. | |
ce57c2fe BG |
10857 | @end table |
10858 | ||
153ae947 BG |
10859 | @node Extending ODT export, Applying custom styles, ODT export commands, OpenDocument Text export |
10860 | @subsection Extending ODT export | |
10861 | ||
10862 | The ODT exporter can interface with a variety of document | |
10863 | converters and supports popular converters out of the box. As a result, you | |
10864 | can use it to export to formats like @samp{doc} or convert a document from | |
10865 | one format (say @samp{csv}) to another format (say @samp{ods} or @samp{xls}). | |
10866 | ||
10867 | @cindex @file{unoconv} | |
10868 | @cindex LibreOffice | |
10869 | If you have a working installation of LibreOffice, a document converter is | |
10870 | pre-configured for you and you can use it right away. If you would like to | |
10871 | use @file{unoconv} as your preferred converter, customize the variable | |
801a68c8 BG |
10872 | @code{org-export-odt-convert-process} to point to @code{unoconv}. You can |
10873 | also use your own favorite converter or tweak the default settings of the | |
10874 | @file{LibreOffice} and @samp{unoconv} converters. @xref{Configuring a | |
10875 | document converter}. | |
153ae947 BG |
10876 | |
10877 | @subsubsection Automatically exporting to other formats | |
e66ba1df | 10878 | @anchor{x-export-to-other-formats} |
153ae947 | 10879 | |
e66ba1df | 10880 | @vindex org-export-odt-preferred-output-format |
153ae947 BG |
10881 | Very often, you will find yourself exporting to ODT format, only to |
10882 | immediately save the exported document to other formats like @samp{doc}, | |
10883 | @samp{docx}, @samp{rtf}, @samp{pdf} etc. In such cases, you can specify your | |
e66ba1df BG |
10884 | preferred output format by customizing the variable |
10885 | @code{org-export-odt-preferred-output-format}. This way, the export commands | |
153ae947 BG |
10886 | (@pxref{x-export-to-odt,,Exporting to ODT}) can be extended to export to a |
10887 | format that is of immediate interest to you. | |
10888 | ||
10889 | @subsubsection Converting between document formats | |
10890 | @anchor{x-convert-to-other-formats} | |
10891 | ||
10892 | There are many document converters in the wild which support conversion to | |
10893 | and from various file formats, including, but not limited to the | |
10894 | ODT format. LibreOffice converter, mentioned above, is one such | |
10895 | converter. Once a converter is configured, you can interact with it using | |
10896 | the following command. | |
e66ba1df | 10897 | |
153ae947 BG |
10898 | @vindex org-export-odt-convert |
10899 | @table @kbd | |
10900 | ||
10901 | @item M-x org-export-odt-convert | |
10902 | Convert an existing document from one format to another. With a prefix | |
10903 | argument, also open the newly produced file. | |
10904 | @end table | |
10905 | ||
10906 | @node Applying custom styles, Links in ODT export, Extending ODT export, OpenDocument Text export | |
e66ba1df | 10907 | @subsection Applying custom styles |
ce57c2fe BG |
10908 | @cindex styles, custom |
10909 | @cindex template, custom | |
10910 | ||
153ae947 | 10911 | The ODT exporter ships with a set of OpenDocument styles |
e66ba1df BG |
10912 | (@pxref{Working with OpenDocument style files}) that ensure a well-formatted |
10913 | output. These factory styles, however, may not cater to your specific | |
10914 | tastes. To customize the output, you can either modify the above styles | |
10915 | files directly, or generate the required styles using an application like | |
10916 | LibreOffice. The latter method is suitable for expert and non-expert | |
10917 | users alike, and is described here. | |
ce57c2fe | 10918 | |
e66ba1df | 10919 | @subsubsection Applying custom styles - the easy way |
ce57c2fe BG |
10920 | |
10921 | @enumerate | |
10922 | @item | |
e66ba1df | 10923 | Create a sample @file{example.org} file with the below settings and export it |
153ae947 | 10924 | to ODT format. |
e66ba1df BG |
10925 | |
10926 | @example | |
10927 | #+OPTIONS: H:10 num:t | |
10928 | @end example | |
10929 | ||
10930 | @item | |
10931 | Open the above @file{example.odt} using LibreOffice. Use the @file{Stylist} | |
10932 | to locate the target styles - these typically have the @samp{Org} prefix - | |
10933 | and modify those to your taste. Save the modified file either as an | |
10934 | OpenDocument Text (@file{.odt}) or OpenDocument Template (@file{.ott}) file. | |
10935 | ||
ce57c2fe | 10936 | @item |
e66ba1df BG |
10937 | @cindex #+ODT_STYLES_FILE |
10938 | @vindex org-export-odt-styles-file | |
10939 | Customize the variable @code{org-export-odt-styles-file} and point it to the | |
10940 | newly created file. For additional configuration options | |
10941 | @pxref{x-overriding-factory-styles,,Overriding factory styles}. | |
10942 | ||
10943 | If you would like to choose a style on a per-file basis, you can use the | |
10944 | @code{#+ODT_STYLES_FILE} option. A typical setting will look like | |
10945 | ||
10946 | @example | |
10947 | #+ODT_STYLES_FILE: "/path/to/example.ott" | |
10948 | @end example | |
10949 | ||
10950 | or | |
10951 | ||
10952 | @example | |
10953 | #+ODT_STYLES_FILE: ("/path/to/file.ott" ("styles.xml" "image/hdr.png")) | |
10954 | @end example | |
10955 | ||
ce57c2fe BG |
10956 | @end enumerate |
10957 | ||
e66ba1df BG |
10958 | @subsubsection Using third-party styles and templates |
10959 | ||
10960 | You can use third-party styles and templates for customizing your output. | |
10961 | This will produce the desired output only if the template provides all | |
10962 | style names that the @samp{ODT} exporter relies on. Unless this condition is | |
10963 | met, the output is going to be less than satisfactory. So it is highly | |
10964 | recommended that you only work with templates that are directly derived from | |
10965 | the factory settings. | |
10966 | ||
153ae947 BG |
10967 | @node Links in ODT export, Tables in ODT export, Applying custom styles, OpenDocument Text export |
10968 | @subsection Links in ODT export | |
e66ba1df BG |
10969 | @cindex tables, in DocBook export |
10970 | ||
153ae947 BG |
10971 | ODT exporter creates native cross-references for internal links. It creates |
10972 | Internet-style links for all other links. | |
10973 | ||
10974 | A link with no description and destined to a regular (un-itemized) outline | |
10975 | heading is replaced with a cross-reference and section number of the heading. | |
e66ba1df | 10976 | |
153ae947 | 10977 | A @samp{\ref@{label@}}-style reference to an image, table etc. is replaced |
7bd20f91 | 10978 | with a cross-reference and sequence number of the labeled entity. |
153ae947 BG |
10979 | @xref{Labels and captions in ODT export}. |
10980 | ||
10981 | @node Tables in ODT export, Images in ODT export, Links in ODT export, OpenDocument Text export | |
10982 | @subsection Tables in ODT export | |
e66ba1df | 10983 | @cindex tables, in DocBook export |
ce57c2fe | 10984 | |
e66ba1df BG |
10985 | Export of native Org mode tables (@pxref{Tables}) and simple @file{table.el} |
10986 | tables is supported. However, export of complex @file{table.el} tables - | |
10987 | tables that have column or row spans - is not supported. Such tables are | |
10988 | stripped from the exported document. | |
ce57c2fe | 10989 | |
153ae947 BG |
10990 | By default, a table is exported with top and bottom frames and with rules |
10991 | separating row and column groups (@pxref{Column groups}). Furthermore, all | |
10992 | tables are typeset to occupy the same width. If the table specifies | |
10993 | alignment and relative width for its columns (@pxref{Column width and | |
10994 | alignment}) then these are honored on export.@footnote{The column widths are | |
10995 | interpreted as weighted ratios with the default weight being 1} | |
e66ba1df BG |
10996 | |
10997 | @cindex #+ATTR_ODT | |
153ae947 BG |
10998 | You can control the width of the table by specifying @code{:rel-width} |
10999 | property using an @code{#+ATTR_ODT} line. | |
11000 | ||
11001 | For example, consider the following table which makes use of all the rules | |
7bd20f91 | 11002 | mentioned above. |
153ae947 BG |
11003 | |
11004 | @example | |
11005 | #+ATTR_ODT: :rel-width 50 | |
11006 | | Area/Month | Jan | Feb | Mar | Sum | | |
11007 | |---------------+-------+-------+-------+-------| | |
11008 | | / | < | | | < | | |
11009 | | <l13> | <r5> | <r5> | <r5> | <r6> | | |
11010 | | North America | 1 | 21 | 926 | 948 | | |
11011 | | Middle East | 6 | 75 | 844 | 925 | | |
11012 | | Asia Pacific | 9 | 27 | 790 | 826 | | |
11013 | |---------------+-------+-------+-------+-------| | |
11014 | | Sum | 16 | 123 | 2560 | 2699 | | |
11015 | @end example | |
11016 | ||
11017 | On export, the table will occupy 50% of text area. The columns will be sized | |
11018 | (roughly) in the ratio of 13:5:5:5:6. The first column will be left-aligned | |
11019 | and rest of the columns will be right-aligned. There will be vertical rules | |
11020 | after separating the header and last columns from other columns. There will | |
11021 | be horizontal rules separating the header and last rows from other rows. | |
11022 | ||
11023 | If you are not satisfied with the above formatting options, you can create | |
11024 | custom table styles and associate them with a table using the | |
11025 | @code{#+ATTR_ODT} line. @xref{Customizing tables in ODT export}. | |
e66ba1df | 11026 | |
153ae947 BG |
11027 | @node Images in ODT export, Math formatting in ODT export, Tables in ODT export, OpenDocument Text export |
11028 | @subsection Images in ODT export | |
11029 | @cindex images, embedding in ODT | |
11030 | @cindex embedding images in ODT | |
e66ba1df BG |
11031 | |
11032 | @subsubheading Embedding images | |
11033 | You can embed images within the exported document by providing a link to the | |
11034 | desired image file with no link description. For example, to embed | |
11035 | @samp{img.png} do either of the following: | |
11036 | ||
11037 | @example | |
11038 | [[file:img.png]] | |
11039 | @end example | |
11040 | ||
11041 | @example | |
11042 | [[./img.png]] | |
11043 | @end example | |
11044 | ||
11045 | @subsubheading Embedding clickable images | |
11046 | You can create clickable images by providing a link whose description is a | |
11047 | link to an image file. For example, to embed a image | |
11048 | @file{org-mode-unicorn.png} which when clicked jumps to | |
11049 | @uref{http://Orgmode.org} website, do the following | |
11050 | ||
11051 | @example | |
11052 | [[http://orgmode.org][./org-mode-unicorn.png]] | |
11053 | @end example | |
11054 | ||
11055 | @subsubheading Sizing and scaling of embedded images | |
11056 | ||
153ae947 | 11057 | @cindex #+ATTR_ODT |
e66ba1df BG |
11058 | You can control the size and scale of the embedded images using the |
11059 | @code{#+ATTR_ODT} attribute. | |
11060 | ||
153ae947 | 11061 | @cindex identify, ImageMagick |
e66ba1df | 11062 | @vindex org-export-odt-pixels-per-inch |
153ae947 BG |
11063 | The exporter specifies the desired size of the image in the final document in |
11064 | units of centimeters. In order to scale the embedded images, the exporter | |
11065 | queries for pixel dimensions of the images using one of a) ImageMagick's | |
11066 | @file{identify} program or b) Emacs `create-image' and `image-size' | |
11067 | APIs.@footnote{Use of @file{ImageMagick} is only desirable. However, if you | |
11068 | routinely produce documents that have large images or you export your Org | |
11069 | files that has images using a Emacs batch script, then the use of | |
11070 | @file{ImageMagick} is mandatory.} The pixel dimensions are subsequently | |
11071 | converted in to units of centimeters using | |
e66ba1df BG |
11072 | @code{org-export-odt-pixels-per-inch}. The default value of this variable is |
11073 | set to @code{display-pixels-per-inch}. You can tweak this variable to | |
11074 | achieve the best results. | |
11075 | ||
11076 | The examples below illustrate the various possibilities. | |
11077 | ||
11078 | @table @asis | |
e66ba1df BG |
11079 | @item Explicitly size the image |
11080 | To embed @file{img.png} as a 10 cm x 10 cm image, do the following: | |
11081 | ||
11082 | @example | |
11083 | #+ATTR_ODT: :width 10 :height 10 | |
11084 | [[./img.png]] | |
11085 | @end example | |
11086 | ||
11087 | @item Scale the image | |
11088 | To embed @file{img.png} at half its size, do the following: | |
11089 | ||
11090 | @example | |
11091 | #+ATTR_ODT: :scale 0.5 | |
11092 | [[./img.png]] | |
11093 | @end example | |
11094 | ||
11095 | @item Scale the image to a specific width | |
11096 | To embed @file{img.png} with a width of 10 cm while retaining the original | |
11097 | height:width ratio, do the following: | |
11098 | ||
11099 | @example | |
11100 | #+ATTR_ODT: :width 10 | |
11101 | [[./img.png]] | |
11102 | @end example | |
11103 | ||
11104 | @item Scale the image to a specific height | |
11105 | To embed @file{img.png} with a height of 10 cm while retaining the original | |
11106 | height:width ratio, do the following | |
11107 | ||
11108 | @example | |
11109 | #+ATTR_ODT: :height 10 | |
11110 | [[./img.png]] | |
11111 | @end example | |
11112 | @end table | |
11113 | ||
153ae947 BG |
11114 | @subsubheading Anchoring of images |
11115 | ||
11116 | @cindex #+ATTR_ODT | |
11117 | You can control the manner in which an image is anchored by setting the | |
11118 | @code{:anchor} property of it's @code{#+ATTR_ODT} line. You can specify one | |
11119 | of the the following three values for the @code{:anchor} property - | |
11120 | @samp{"as-char"}, @samp{"paragraph"} and @samp{"page"}. | |
11121 | ||
11122 | To create an image that is anchored to a page, do the following: | |
11123 | @example | |
11124 | #+ATTR_ODT: :anchor "page" | |
11125 | [[./img.png]] | |
11126 | @end example | |
11127 | ||
11128 | @node Math formatting in ODT export, Labels and captions in ODT export, Images in ODT export, OpenDocument Text export | |
11129 | @subsection Math formatting in ODT export | |
e66ba1df | 11130 | |
153ae947 | 11131 | The ODT exporter has special support for handling math. |
e66ba1df BG |
11132 | |
11133 | @menu | |
11134 | * Working with @LaTeX{} math snippets:: How to embed @LaTeX{} math fragments | |
11135 | * Working with MathML or OpenDocument formula files:: How to embed equations in native format | |
11136 | @end menu | |
11137 | ||
153ae947 | 11138 | @node Working with @LaTeX{} math snippets, Working with MathML or OpenDocument formula files, Math formatting in ODT export, Math formatting in ODT export |
e66ba1df BG |
11139 | @subsubsection Working with @LaTeX{} math snippets |
11140 | ||
11141 | @LaTeX{} math snippets (@pxref{@LaTeX{} fragments}) can be embedded in the ODT | |
11142 | document in one of the following ways: | |
11143 | ||
11144 | @cindex MathML | |
11145 | @enumerate | |
11146 | @item MathML | |
11147 | ||
11148 | This option is activated on a per-file basis with | |
11149 | ||
11150 | @example | |
11151 | #+OPTIONS: LaTeX:t | |
11152 | @end example | |
11153 | ||
11154 | With this option, @LaTeX{} fragments are first converted into MathML | |
11155 | fragments using an external @LaTeX{}-to-MathML converter program. The | |
11156 | resulting MathML fragments are then embedded as an OpenDocument Formula in | |
11157 | the exported document. | |
11158 | ||
11159 | @vindex org-latex-to-mathml-convert-command | |
11160 | @vindex org-latex-to-mathml-jar-file | |
11161 | ||
11162 | You can specify the @LaTeX{}-to-MathML converter by customizing the variables | |
11163 | @code{org-latex-to-mathml-convert-command} and | |
11164 | @code{org-latex-to-mathml-jar-file}. | |
11165 | ||
11166 | If you prefer to use @file{MathToWeb}@footnote{See | |
11167 | @uref{http://www.mathtoweb.com/cgi-bin/mathtoweb_home.pl, MathToWeb}} as your | |
11168 | converter, you can configure the above variables as shown below. | |
11169 | ||
11170 | @lisp | |
11171 | (setq org-latex-to-mathml-convert-command | |
11172 | "java -jar %j -unicode -force -df %o %I" | |
11173 | org-latex-to-mathml-jar-file | |
11174 | "/path/to/mathtoweb.jar") | |
11175 | @end lisp | |
11176 | ||
11177 | You can use the following commands to quickly verify the reliability of | |
11178 | the @LaTeX{}-to-MathML converter. | |
11179 | ||
11180 | @table @kbd | |
11181 | ||
11182 | @item M-x org-export-as-odf | |
11183 | Convert a @LaTeX{} math snippet to OpenDocument formula (@file{.odf}) file. | |
11184 | ||
11185 | @item M-x org-export-as-odf-and-open | |
11186 | Convert a @LaTeX{} math snippet to OpenDocument formula (@file{.odf}) file and | |
11187 | open the formula file with the system-registered application. | |
11188 | @end table | |
11189 | ||
11190 | @cindex dvipng | |
11191 | @item PNG images | |
11192 | ||
11193 | This option is activated on a per-file basis with | |
11194 | ||
11195 | @example | |
11196 | #+OPTIONS: LaTeX:dvipng | |
11197 | @end example | |
11198 | ||
11199 | With this option, @LaTeX{} fragments are processed into PNG images and the | |
11200 | resulting images are embedded in the exported document. This method requires | |
11201 | that the @file{dvipng} program be available on your system. | |
11202 | @end enumerate | |
11203 | ||
153ae947 | 11204 | @node Working with MathML or OpenDocument formula files, , Working with @LaTeX{} math snippets, Math formatting in ODT export |
e66ba1df BG |
11205 | @subsubsection Working with MathML or OpenDocument formula files |
11206 | ||
11207 | For various reasons, you may find embedding @LaTeX{} math snippets in an | |
153ae947 | 11208 | ODT document less than reliable. In that case, you can embed a |
801a68c8 | 11209 | math equation by linking to its MathML (@file{.mml}) source or its |
e66ba1df BG |
11210 | OpenDocument formula (@file{.odf}) file as shown below: |
11211 | ||
11212 | @example | |
11213 | [[./equation.mml]] | |
11214 | @end example | |
11215 | ||
11216 | or | |
11217 | ||
11218 | @example | |
11219 | [[./equation.odf]] | |
11220 | @end example | |
11221 | ||
153ae947 BG |
11222 | @node Labels and captions in ODT export, Literal examples in ODT export, Math formatting in ODT export, OpenDocument Text export |
11223 | @subsection Labels and captions in ODT export | |
e66ba1df | 11224 | |
153ae947 BG |
11225 | You can label and caption various category of objects - an inline image, a |
11226 | table, a @LaTeX{} fragment or a Math formula - using @code{#+LABEL} and | |
11227 | @code{#+CAPTION} lines. @xref{Images and tables}. ODT exporter enumerates | |
7bd20f91 | 11228 | each labeled or captioned object of a given category separately. As a |
153ae947 BG |
11229 | result, each such object is assigned a sequence number based on order of it's |
11230 | appearance in the Org file. | |
e66ba1df | 11231 | |
153ae947 BG |
11232 | In the exported document, a user-provided caption is augmented with the |
11233 | category and sequence number. Consider the following inline image in an Org | |
11234 | file. | |
11235 | ||
11236 | @example | |
11237 | #+CAPTION: Bell curve | |
11238 | #+LABEL: fig:SED-HR4049 | |
11239 | [[./img/a.png]] | |
11240 | @end example | |
e66ba1df | 11241 | |
153ae947 | 11242 | It could be rendered as shown below in the exported document. |
e66ba1df | 11243 | |
153ae947 BG |
11244 | @example |
11245 | Figure 2: Bell curve | |
11246 | @end example | |
11247 | ||
11248 | @vindex org-export-odt-category-strings | |
11249 | You can modify the category component of the caption by customizing the | |
11250 | variable @code{org-export-odt-category-strings}. For example, to tag all | |
11251 | embedded images with the string @samp{Illustration} (instead of the default | |
11252 | @samp{Figure}) use the following setting. | |
11253 | ||
11254 | @lisp | |
11255 | (setq org-export-odt-category-strings | |
11256 | '(("en" "Table" "Illustration" "Equation" "Equation"))) | |
11257 | @end lisp | |
e66ba1df | 11258 | |
153ae947 BG |
11259 | With this, previous image will be captioned as below in the exported |
11260 | document. | |
e66ba1df | 11261 | |
153ae947 BG |
11262 | @example |
11263 | Illustration 2: Bell curve | |
11264 | @end example | |
11265 | ||
11266 | @node Literal examples in ODT export, Advanced topics in ODT export, Labels and captions in ODT export, OpenDocument Text export | |
11267 | @subsection Literal examples in ODT export | |
e66ba1df | 11268 | |
153ae947 BG |
11269 | Export of literal examples (@pxref{Literal examples}) with full fontification |
11270 | is supported. Internally, the exporter relies on @file{htmlfontify.el} to | |
11271 | generate all style definitions needed for a fancy listing.@footnote{Your | |
801a68c8 | 11272 | @file{htmlfontify.el} library must at least be at Emacs 24.1 levels for |
153ae947 BG |
11273 | fontification to be turned on.} The auto-generated styles have @samp{OrgSrc} |
11274 | as prefix and inherit their color from the faces used by Emacs | |
11275 | @code{font-lock} library for the source language. | |
e66ba1df | 11276 | |
153ae947 BG |
11277 | @vindex org-export-odt-fontify-srcblocks |
11278 | If you prefer to use your own custom styles for fontification, you can do so | |
11279 | by customizing the variable | |
11280 | @code{org-export-odt-create-custom-styles-for-srcblocks}. | |
11281 | ||
11282 | @vindex org-export-odt-create-custom-styles-for-srcblocks | |
11283 | You can turn off fontification of literal examples by customizing the | |
11284 | variable @code{org-export-odt-fontify-srcblocks}. | |
11285 | ||
11286 | @node Advanced topics in ODT export, , Literal examples in ODT export, OpenDocument Text export | |
11287 | @subsection Advanced topics in ODT export | |
11288 | ||
11289 | If you rely heavily on ODT export, you may want to exploit the full | |
e66ba1df BG |
11290 | set of features that the exporter offers. This section describes features |
11291 | that would be of interest to power users. | |
11292 | ||
11293 | @menu | |
153ae947 | 11294 | * Configuring a document converter:: How to register a document converter |
e66ba1df BG |
11295 | * Working with OpenDocument style files:: Explore the internals |
11296 | * Creating one-off styles:: How to produce custom highlighting etc | |
153ae947 | 11297 | * Customizing tables in ODT export:: How to define and use Table templates |
e66ba1df BG |
11298 | * Validating OpenDocument XML:: How to debug corrupt OpenDocument files |
11299 | @end menu | |
11300 | ||
153ae947 BG |
11301 | @node Configuring a document converter, Working with OpenDocument style files, Advanced topics in ODT export, Advanced topics in ODT export |
11302 | @subsubsection Configuring a document converter | |
ce57c2fe | 11303 | @cindex convert |
153ae947 | 11304 | @cindex doc, docx, rtf |
e66ba1df | 11305 | @cindex converter |
ce57c2fe | 11306 | |
153ae947 BG |
11307 | The ODT exporter can work with popular converters with little or no |
11308 | extra configuration from your side. @xref{Extending ODT export}. | |
11309 | If you are using a converter that is not supported by default or if you would | |
11310 | like to tweak the default converter settings, proceed as below. | |
e66ba1df BG |
11311 | |
11312 | @enumerate | |
11313 | @item Register the converter | |
11314 | ||
11315 | @vindex org-export-odt-convert-processes | |
11316 | Name your converter and add it to the list of known converters by customizing | |
11317 | the variable @code{org-export-odt-convert-processes}. Also specify how the | |
11318 | converter can be invoked via command-line to effect the conversion. | |
11319 | ||
11320 | @item Configure its capabilities | |
ce57c2fe | 11321 | |
801a68c8 | 11322 | @vindex org-export-odt-convert-capabilities |
e66ba1df | 11323 | @anchor{x-odt-converter-capabilities} |
e66ba1df BG |
11324 | Specify the set of formats the converter can handle by customizing the |
11325 | variable @code{org-export-odt-convert-capabilities}. Use the default value | |
11326 | for this variable as a guide for configuring your converter. As suggested by | |
11327 | the default setting, you can specify the full set of formats supported by the | |
11328 | converter and not limit yourself to specifying formats that are related to | |
11329 | just the OpenDocument Text format. | |
11330 | ||
11331 | @item Choose the converter | |
11332 | ||
11333 | @vindex org-export-odt-convert-process | |
11334 | Select the newly added converter as the preferred one by customizing the | |
11335 | variable @code{org-export-odt-convert-process}. | |
11336 | @end enumerate | |
11337 | ||
153ae947 | 11338 | @node Working with OpenDocument style files, Creating one-off styles, Configuring a document converter, Advanced topics in ODT export |
e66ba1df BG |
11339 | @subsubsection Working with OpenDocument style files |
11340 | @cindex styles, custom | |
11341 | @cindex template, custom | |
ce57c2fe | 11342 | |
153ae947 | 11343 | This section explores the internals of the ODT exporter and the |
e66ba1df BG |
11344 | means by which it produces styled documents. Read this section if you are |
11345 | interested in exploring the automatic and custom OpenDocument styles used by | |
11346 | the exporter. | |
11347 | ||
11348 | @anchor{x-factory-styles} | |
11349 | @subsubheading Factory styles | |
11350 | ||
153ae947 | 11351 | The ODT exporter relies on two files for generating its output. |
e66ba1df BG |
11352 | These files are bundled with the distribution under the directory pointed to |
11353 | by the variable @code{org-odt-styles-dir}. The two files are: | |
11354 | ||
11355 | @itemize | |
11356 | @anchor{x-orgodtstyles-xml} | |
11357 | @item | |
11358 | @file{OrgOdtStyles.xml} | |
11359 | ||
11360 | This file contributes to the @file{styles.xml} file of the final @samp{ODT} | |
11361 | document. This file gets modified for the following purposes: | |
11362 | @enumerate | |
11363 | ||
11364 | @item | |
11365 | To control outline numbering based on user settings. | |
11366 | ||
11367 | @item | |
11368 | To add styles generated by @file{htmlfontify.el} for fontification of code | |
11369 | blocks. | |
11370 | @end enumerate | |
11371 | ||
11372 | @anchor{x-orgodtcontenttemplate-xml} | |
11373 | @item | |
11374 | @file{OrgOdtContentTemplate.xml} | |
11375 | ||
11376 | This file contributes to the @file{content.xml} file of the final @samp{ODT} | |
11377 | document. The contents of the Org outline are inserted between the | |
11378 | @samp{<office:text>}@dots{}@samp{</office:text>} elements of this file. | |
11379 | ||
11380 | Apart from serving as a template file for the final @file{content.xml}, the | |
11381 | file serves the following purposes: | |
11382 | @enumerate | |
11383 | ||
11384 | @item | |
11385 | It contains automatic styles for formatting of tables which are referenced by | |
11386 | the exporter. | |
11387 | ||
11388 | @item | |
11389 | It contains @samp{<text:sequence-decl>}@dots{}@samp{</text:sequence-decl>} | |
11390 | elements that control how various entities - tables, images, equations etc - | |
11391 | are numbered. | |
11392 | @end enumerate | |
11393 | @end itemize | |
11394 | ||
11395 | @anchor{x-overriding-factory-styles} | |
11396 | @subsubheading Overriding factory styles | |
153ae947 | 11397 | The following two variables control the location from which the ODT |
e66ba1df BG |
11398 | exporter picks up the custom styles and content template files. You can |
11399 | customize these variables to override the factory styles used by the | |
11400 | exporter. | |
11401 | ||
11402 | @itemize | |
11403 | @anchor{x-org-export-odt-styles-file} | |
11404 | @item | |
11405 | @code{org-export-odt-styles-file} | |
11406 | ||
11407 | Use this variable to specify the @file{styles.xml} that will be used in the | |
11408 | final output. You can specify one of the following values: | |
11409 | ||
11410 | @enumerate | |
11411 | @item A @file{styles.xml} file | |
11412 | ||
11413 | Use this file instead of the default @file{styles.xml} | |
11414 | ||
11415 | @item A @file{.odt} or @file{.ott} file | |
11416 | ||
11417 | Use the @file{styles.xml} contained in the specified OpenDocument Text or | |
11418 | Template file | |
11419 | ||
11420 | @item A @file{.odt} or @file{.ott} file and a subset of files contained within them | |
11421 | ||
11422 | Use the @file{styles.xml} contained in the specified OpenDocument Text or | |
11423 | Template file. Additionally extract the specified member files and embed | |
11424 | those within the final @samp{ODT} document. | |
11425 | ||
11426 | Use this option if the @file{styles.xml} file references additional files | |
11427 | like header and footer images. | |
11428 | ||
11429 | @item @code{nil} | |
11430 | ||
11431 | Use the default @file{styles.xml} | |
11432 | @end enumerate | |
11433 | ||
11434 | @anchor{x-org-export-odt-content-template-file} | |
11435 | @item | |
11436 | @code{org-export-odt-content-template-file} | |
11437 | ||
11438 | Use this variable to specify the blank @file{content.xml} that will be used | |
11439 | in the final output. | |
11440 | @end itemize | |
11441 | ||
153ae947 | 11442 | @node Creating one-off styles, Customizing tables in ODT export, Working with OpenDocument style files, Advanced topics in ODT export |
e66ba1df BG |
11443 | @subsubsection Creating one-off styles |
11444 | ||
11445 | There are times when you would want one-off formatting in the exported | |
11446 | document. You can achieve this by embedding raw OpenDocument XML in the Org | |
11447 | file. The use of this feature is better illustrated with couple of examples. | |
11448 | ||
11449 | @enumerate | |
11450 | @item Embedding ODT tags as part of regular text | |
11451 | ||
11452 | You can include simple OpenDocument tags by prefixing them with | |
11453 | @samp{@@}. For example, to highlight a region of text do the following: | |
11454 | ||
11455 | @example | |
11456 | @@<text:span text:style-name="Highlight">This is a | |
11457 | highlighted text@@</text:span>. But this is a | |
11458 | regular text. | |
11459 | @end example | |
11460 | ||
11461 | @strong{Hint:} To see the above example in action, edit your | |
801a68c8 | 11462 | @file{styles.xml} (@pxref{x-orgodtstyles-xml,,Factory styles}) and add a |
e66ba1df BG |
11463 | custom @samp{Highlight} style as shown below. |
11464 | ||
11465 | @example | |
11466 | <style:style style:name="Highlight" style:family="text"> | |
11467 | <style:text-properties fo:background-color="#ff0000"/> | |
11468 | </style:style> | |
11469 | @end example | |
11470 | ||
11471 | @item Embedding a one-line OpenDocument XML | |
11472 | ||
11473 | You can add a simple OpenDocument one-liner using the @code{#+ODT:} | |
11474 | directive. For example, to force a page break do the following: | |
11475 | ||
11476 | @example | |
11477 | #+ODT: <text:p text:style-name="PageBreak"/> | |
11478 | @end example | |
11479 | ||
11480 | @strong{Hint:} To see the above example in action, edit your | |
801a68c8 | 11481 | @file{styles.xml} (@pxref{x-orgodtstyles-xml,,Factory styles}) and add a |
e66ba1df BG |
11482 | custom @samp{PageBreak} style as shown below. |
11483 | ||
11484 | @example | |
11485 | <style:style style:name="PageBreak" style:family="paragraph" | |
11486 | style:parent-style-name="Text_20_body"> | |
11487 | <style:paragraph-properties fo:break-before="page"/> | |
11488 | </style:style> | |
11489 | @end example | |
11490 | ||
11491 | @item Embedding a block of OpenDocument XML | |
11492 | ||
11493 | You can add a large block of OpenDocument XML using the | |
11494 | @code{#+BEGIN_ODT}@dots{}@code{#+END_ODT} construct. | |
11495 | ||
11496 | For example, to create a one-off paragraph that uses bold text, do the | |
11497 | following: | |
11498 | ||
11499 | @example | |
11500 | #+BEGIN_ODT | |
11501 | <text:p text:style-name="Text_20_body_20_bold"> | |
11502 | This paragraph is specially formatted and uses bold text. | |
11503 | </text:p> | |
11504 | #+END_ODT | |
11505 | @end example | |
11506 | ||
11507 | @end enumerate | |
11508 | ||
153ae947 BG |
11509 | @node Customizing tables in ODT export, Validating OpenDocument XML, Creating one-off styles, Advanced topics in ODT export |
11510 | @subsubsection Customizing tables in ODT export | |
e66ba1df BG |
11511 | @cindex tables, in ODT export |
11512 | ||
11513 | @cindex #+ATTR_ODT | |
11514 | You can override the default formatting of the table by specifying a custom | |
11515 | table style with the @code{#+ATTR_ODT} line. For a discussion on default | |
153ae947 | 11516 | formatting of tables @pxref{Tables in ODT export}. |
e66ba1df BG |
11517 | |
11518 | This feature closely mimics the way table templates are defined in the | |
11519 | OpenDocument-v1.2 | |
11520 | specification.@footnote{@url{http://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2.html, | |
11521 | OpenDocument-v1.2 Specification}} | |
11522 | ||
11523 | ||
11524 | ||
11525 | @subsubheading Custom table styles - an illustration | |
11526 | ||
11527 | To have a quick preview of this feature, install the below setting and export | |
11528 | the table that follows. | |
11529 | ||
11530 | @lisp | |
11531 | (setq org-export-odt-table-styles | |
11532 | (append org-export-odt-table-styles | |
11533 | '(("TableWithHeaderRowAndColumn" "Custom" | |
11534 | ((use-first-row-styles . t) | |
11535 | (use-first-column-styles . t))) | |
11536 | ("TableWithFirstRowandLastRow" "Custom" | |
11537 | ((use-first-row-styles . t) | |
11538 | (use-last-row-styles . t)))))) | |
11539 | @end lisp | |
11540 | ||
11541 | @example | |
153ae947 | 11542 | #+ATTR_ODT: :style "TableWithHeaderRowAndColumn" |
e66ba1df BG |
11543 | | Name | Phone | Age | |
11544 | | Peter | 1234 | 17 | | |
11545 | | Anna | 4321 | 25 | | |
11546 | @end example | |
11547 | ||
11548 | In the above example, you used a template named @samp{Custom} and installed | |
11549 | two table styles with the names @samp{TableWithHeaderRowAndColumn} and | |
11550 | @samp{TableWithFirstRowandLastRow}. (@strong{Important:} The OpenDocument | |
11551 | styles needed for producing the above template have been pre-defined for you. | |
11552 | These styles are available under the section marked @samp{Custom Table | |
11553 | Template} in @file{OrgOdtContentTemplate.xml} | |
11554 | (@pxref{x-orgodtcontenttemplate-xml,,Factory styles}). If you need | |
11555 | additional templates you have to define these styles yourselves. | |
11556 | ||
11557 | @subsubheading Custom table styles - the nitty-gritty | |
11558 | To use this feature proceed as follows: | |
11559 | ||
11560 | @enumerate | |
11561 | @item | |
11562 | Create a table template@footnote{See the @code{<table:table-template>} | |
11563 | element of the OpenDocument-v1.2 specification} | |
11564 | ||
11565 | A table template is nothing but a set of @samp{table-cell} and | |
11566 | @samp{paragraph} styles for each of the following table cell categories: | |
11567 | ||
11568 | @itemize @minus | |
11569 | @item Body | |
11570 | @item First column | |
11571 | @item Last column | |
11572 | @item First row | |
11573 | @item Last row | |
11574 | @item Even row | |
11575 | @item Odd row | |
11576 | @item Even column | |
11577 | @item Odd Column | |
11578 | @end itemize | |
11579 | ||
11580 | The names for the above styles must be chosen based on the name of the table | |
11581 | template using a well-defined convention. | |
11582 | ||
11583 | The naming convention is better illustrated with an example. For a table | |
11584 | template with the name @samp{Custom}, the needed style names are listed in | |
11585 | the following table. | |
11586 | ||
11587 | @multitable {Table cell type} {CustomEvenColumnTableCell} {CustomEvenColumnTableParagraph} | |
11588 | @headitem Table cell type | |
11589 | @tab @code{table-cell} style | |
11590 | @tab @code{paragraph} style | |
11591 | @item | |
11592 | @tab | |
11593 | @tab | |
11594 | @item Body | |
11595 | @tab @samp{CustomTableCell} | |
11596 | @tab @samp{CustomTableParagraph} | |
11597 | @item First column | |
11598 | @tab @samp{CustomFirstColumnTableCell} | |
11599 | @tab @samp{CustomFirstColumnTableParagraph} | |
11600 | @item Last column | |
11601 | @tab @samp{CustomLastColumnTableCell} | |
11602 | @tab @samp{CustomLastColumnTableParagraph} | |
11603 | @item First row | |
11604 | @tab @samp{CustomFirstRowTableCell} | |
11605 | @tab @samp{CustomFirstRowTableParagraph} | |
11606 | @item Last row | |
11607 | @tab @samp{CustomLastRowTableCell} | |
11608 | @tab @samp{CustomLastRowTableParagraph} | |
11609 | @item Even row | |
11610 | @tab @samp{CustomEvenRowTableCell} | |
11611 | @tab @samp{CustomEvenRowTableParagraph} | |
11612 | @item Odd row | |
11613 | @tab @samp{CustomOddRowTableCell} | |
11614 | @tab @samp{CustomOddRowTableParagraph} | |
11615 | @item Even column | |
11616 | @tab @samp{CustomEvenColumnTableCell} | |
11617 | @tab @samp{CustomEvenColumnTableParagraph} | |
11618 | @item Odd column | |
11619 | @tab @samp{CustomOddColumnTableCell} | |
11620 | @tab @samp{CustomOddColumnTableParagraph} | |
11621 | @end multitable | |
11622 | ||
11623 | To create a table template with the name @samp{Custom}, define the above | |
11624 | styles in the | |
11625 | @code{<office:automatic-styles>}...@code{</office:automatic-styles>} element | |
11626 | of the content template file (@pxref{x-orgodtcontenttemplate-xml,,Factory | |
11627 | styles}). | |
11628 | ||
11629 | @item | |
11630 | Define a table style@footnote{See the attributes @code{table:template-name}, | |
11631 | @code{table:use-first-row-styles}, @code{table:use-last-row-styles}, | |
11632 | @code{table:use-first-column-styles}, @code{table:use-last-column-styles}, | |
11633 | @code{table:use-banding-rows-styles}, and | |
11634 | @code{table:use-banding-column-styles} of the @code{<table:table>} element in | |
11635 | the OpenDocument-v1.2 specification} | |
11636 | ||
11637 | @vindex org-export-odt-table-styles | |
11638 | To define a table style, create an entry for the style in the variable | |
11639 | @code{org-export-odt-table-styles} and specify the following: | |
11640 | ||
11641 | @itemize @minus | |
11642 | @item the name of the table template created in step (1) | |
11643 | @item the set of cell styles in that template that are to be activated | |
11644 | @end itemize | |
11645 | ||
11646 | For example, the entry below defines two different table styles | |
153ae947 BG |
11647 | @samp{TableWithHeaderRowAndColumn} and @samp{TableWithFirstRowandLastRow} |
11648 | based on the same template @samp{Custom}. The styles achieve their intended | |
11649 | effect by selectively activating the individual cell styles in that template. | |
e66ba1df BG |
11650 | |
11651 | @lisp | |
11652 | (setq org-export-odt-table-styles | |
11653 | (append org-export-odt-table-styles | |
11654 | '(("TableWithHeaderRowAndColumn" "Custom" | |
11655 | ((use-first-row-styles . t) | |
11656 | (use-first-column-styles . t))) | |
11657 | ("TableWithFirstRowandLastRow" "Custom" | |
11658 | ((use-first-row-styles . t) | |
11659 | (use-last-row-styles . t)))))) | |
11660 | @end lisp | |
11661 | ||
11662 | @item | |
11663 | Associate a table with the table style | |
11664 | ||
11665 | To do this, specify the table style created in step (2) as part of | |
11666 | the @code{ATTR_ODT} line as shown below. | |
11667 | ||
11668 | @example | |
153ae947 | 11669 | #+ATTR_ODT: :style "TableWithHeaderRowAndColumn" |
e66ba1df BG |
11670 | | Name | Phone | Age | |
11671 | | Peter | 1234 | 17 | | |
11672 | | Anna | 4321 | 25 | | |
11673 | @end example | |
11674 | @end enumerate | |
11675 | ||
153ae947 | 11676 | @node Validating OpenDocument XML, , Customizing tables in ODT export, Advanced topics in ODT export |
e66ba1df BG |
11677 | @subsubsection Validating OpenDocument XML |
11678 | ||
11679 | Occasionally, you will discover that the document created by the | |
153ae947 | 11680 | ODT exporter cannot be opened by your favorite application. One of |
e66ba1df BG |
11681 | the common reasons for this is that the @file{.odt} file is corrupt. In such |
11682 | cases, you may want to validate the document against the OpenDocument RELAX | |
11683 | NG Compact Syntax (RNC) schema. | |
11684 | ||
11685 | For de-compressing the @file{.odt} file@footnote{@file{.odt} files are | |
11686 | nothing but @samp{zip} archives}: @inforef{File Archives,,emacs}. For | |
11687 | general help with validation (and schema-sensitive editing) of XML files: | |
11688 | @inforef{Introduction,,nxml-mode}. | |
11689 | ||
11690 | @vindex org-export-odt-schema-dir | |
11691 | If you have ready access to OpenDocument @file{.rnc} files and the needed | |
11692 | schema-locating rules in a single folder, you can customize the variable | |
11693 | @code{org-export-odt-schema-dir} to point to that directory. The | |
153ae947 | 11694 | ODT exporter will take care of updating the |
e66ba1df | 11695 | @code{rng-schema-locating-files} for you. |
ce57c2fe BG |
11696 | |
11697 | @c end opendocument | |
11698 | ||
e66ba1df | 11699 | @node TaskJuggler export, Freemind export, OpenDocument Text export, Exporting |
86fbb8ca CD |
11700 | @section TaskJuggler export |
11701 | @cindex TaskJuggler export | |
11702 | @cindex Project management | |
11703 | ||
11704 | @uref{http://www.taskjuggler.org/, TaskJuggler} is a project management tool. | |
11705 | It provides an optimizing scheduler that computes your project time lines and | |
11706 | resource assignments based on the project outline and the constraints that | |
11707 | you have provided. | |
11708 | ||
11709 | The TaskJuggler exporter is a bit different from other exporters, such as the | |
e66ba1df | 11710 | @code{HTML} and @LaTeX{} exporters for example, in that it does not export all the |
86fbb8ca CD |
11711 | nodes of a document or strictly follow the order of the nodes in the |
11712 | document. | |
11713 | ||
11714 | Instead the TaskJuggler exporter looks for a tree that defines the tasks and | |
ce57c2fe | 11715 | a optionally tree that defines the resources for this project. It then |
86fbb8ca CD |
11716 | creates a TaskJuggler file based on these trees and the attributes defined in |
11717 | all the nodes. | |
11718 | ||
11719 | @subsection TaskJuggler export commands | |
11720 | ||
11721 | @table @kbd | |
acedf35c | 11722 | @orgcmd{C-c C-e j,org-export-as-taskjuggler} |
86fbb8ca CD |
11723 | Export as TaskJuggler file. |
11724 | ||
acedf35c | 11725 | @orgcmd{C-c C-e J,org-export-as-taskjuggler-and-open} |
86fbb8ca CD |
11726 | Export as TaskJuggler file and then open the file with TaskJugglerUI. |
11727 | @end table | |
11728 | ||
11729 | @subsection Tasks | |
11730 | ||
11731 | @vindex org-export-taskjuggler-project-tag | |
e66ba1df | 11732 | Create your tasks as you usually do with Org mode. Assign efforts to each |
ce57c2fe | 11733 | task using properties (it is easiest to do this in the column view). You |
86fbb8ca CD |
11734 | should end up with something similar to the example by Peter Jones in |
11735 | @url{http://www.contextualdevelopment.com/static/artifacts/articles/2008/project-planning/project-planning.org}. | |
11736 | Now mark the top node of your tasks with a tag named | |
11737 | @code{:taskjuggler_project:} (or whatever you customized | |
ce57c2fe | 11738 | @code{org-export-taskjuggler-project-tag} to). You are now ready to export |
86fbb8ca CD |
11739 | the project plan with @kbd{C-c C-e J} which will export the project plan and |
11740 | open a gantt chart in TaskJugglerUI. | |
11741 | ||
11742 | @subsection Resources | |
11743 | ||
11744 | @vindex org-export-taskjuggler-resource-tag | |
ce57c2fe BG |
11745 | Next you can define resources and assign those to work on specific tasks. You |
11746 | can group your resources hierarchically. Tag the top node of the resources | |
86fbb8ca | 11747 | with @code{:taskjuggler_resource:} (or whatever you customized |
ce57c2fe | 11748 | @code{org-export-taskjuggler-resource-tag} to). You can optionally assign an |
86fbb8ca CD |
11749 | identifier (named @samp{resource_id}) to the resources (using the standard |
11750 | Org properties commands, @pxref{Property syntax}) or you can let the exporter | |
11751 | generate identifiers automatically (the exporter picks the first word of the | |
acedf35c | 11752 | headline as the identifier as long as it is unique---see the documentation of |
ce57c2fe BG |
11753 | @code{org-taskjuggler-get-unique-id}). Using that identifier you can then |
11754 | allocate resources to tasks. This is again done with the @samp{allocate} | |
11755 | property on the tasks. Do this in column view or when on the task type | |
86fbb8ca CD |
11756 | @kbd{C-c C-x p allocate @key{RET} <resource_id> @key{RET}}. |
11757 | ||
11758 | Once the allocations are done you can again export to TaskJuggler and check | |
11759 | in the Resource Allocation Graph which person is working on what task at what | |
11760 | time. | |
11761 | ||
11762 | @subsection Export of properties | |
11763 | ||
ce57c2fe | 11764 | The exporter also takes TODO state information into consideration, i.e.@: if a |
86fbb8ca | 11765 | task is marked as done it will have the corresponding attribute in |
ce57c2fe | 11766 | TaskJuggler (@samp{complete 100}). Also it will export any property on a task |
86fbb8ca CD |
11767 | resource or resource node which is known to TaskJuggler, such as |
11768 | @samp{limits}, @samp{vacation}, @samp{shift}, @samp{booking}, | |
11769 | @samp{efficiency}, @samp{journalentry}, @samp{rate} for resources or | |
11770 | @samp{account}, @samp{start}, @samp{note}, @samp{duration}, @samp{end}, | |
11771 | @samp{journalentry}, @samp{milestone}, @samp{reference}, @samp{responsible}, | |
11772 | @samp{scheduling}, etc for tasks. | |
11773 | ||
11774 | @subsection Dependencies | |
11775 | ||
11776 | The exporter will handle dependencies that are defined in the tasks either | |
11777 | with the @samp{ORDERED} attribute (@pxref{TODO dependencies}), with the | |
acedf35c | 11778 | @samp{BLOCKER} attribute (see @file{org-depend.el}) or alternatively with a |
ce57c2fe | 11779 | @samp{depends} attribute. Both the @samp{BLOCKER} and the @samp{depends} |
86fbb8ca CD |
11780 | attribute can be either @samp{previous-sibling} or a reference to an |
11781 | identifier (named @samp{task_id}) which is defined for another task in the | |
ce57c2fe BG |
11782 | project. @samp{BLOCKER} and the @samp{depends} attribute can define multiple |
11783 | dependencies separated by either space or comma. You can also specify | |
11784 | optional attributes on the dependency by simply appending it. The following | |
86fbb8ca CD |
11785 | examples should illustrate this: |
11786 | ||
11787 | @example | |
11788 | * Preparation | |
11789 | :PROPERTIES: | |
11790 | :task_id: preparation | |
11791 | :ORDERED: t | |
11792 | :END: | |
11793 | * Training material | |
11794 | :PROPERTIES: | |
11795 | :task_id: training_material | |
11796 | :ORDERED: t | |
11797 | :END: | |
11798 | ** Markup Guidelines | |
11799 | :PROPERTIES: | |
ce57c2fe | 11800 | :Effort: 2d |
86fbb8ca CD |
11801 | :END: |
11802 | ** Workflow Guidelines | |
11803 | :PROPERTIES: | |
ce57c2fe | 11804 | :Effort: 2d |
86fbb8ca CD |
11805 | :END: |
11806 | * Presentation | |
11807 | :PROPERTIES: | |
ce57c2fe | 11808 | :Effort: 2d |
86fbb8ca CD |
11809 | :BLOCKER: training_material @{ gapduration 1d @} preparation |
11810 | :END: | |
11811 | @end example | |
11812 | ||
11813 | @subsection Reports | |
11814 | ||
11815 | @vindex org-export-taskjuggler-default-reports | |
ce57c2fe BG |
11816 | TaskJuggler can produce many kinds of reports (e.g.@: gantt chart, resource |
11817 | allocation, etc). The user defines what kind of reports should be generated | |
11818 | for a project in the TaskJuggler file. The exporter will automatically insert | |
11819 | some default reports in the file. These defaults are defined in | |
11820 | @code{org-export-taskjuggler-default-reports}. They can be modified using | |
11821 | customize along with a number of other options. For a more complete list, see | |
86fbb8ca CD |
11822 | @kbd{M-x customize-group @key{RET} org-export-taskjuggler @key{RET}}. |
11823 | ||
11824 | For more information and examples see the Org-taskjuggler tutorial at | |
ce57c2fe | 11825 | @uref{http://orgmode.org/worg/org-tutorials/org-taskjuggler.html}. |
86fbb8ca CD |
11826 | |
11827 | @node Freemind export, XOXO export, TaskJuggler export, Exporting | |
a351880d CD |
11828 | @section Freemind export |
11829 | @cindex Freemind export | |
11830 | @cindex mind map | |
11831 | ||
86fbb8ca | 11832 | The Freemind exporter was written by Lennart Borgman. |
a351880d CD |
11833 | |
11834 | @table @kbd | |
acedf35c | 11835 | @orgcmd{C-c C-e m,org-export-as-freemind} |
ce57c2fe BG |
11836 | Export as Freemind mind map. For an Org file @file{myfile.org}, the Freemind |
11837 | file will be @file{myfile.mm}. | |
a351880d CD |
11838 | @end table |
11839 | ||
11840 | @node XOXO export, iCalendar export, Freemind export, Exporting | |
4009494e GM |
11841 | @section XOXO export |
11842 | @cindex XOXO export | |
11843 | ||
e66ba1df | 11844 | Org mode contains an exporter that produces XOXO-style output. |
4009494e | 11845 | Currently, this exporter only handles the general outline structure and |
e66ba1df | 11846 | does not interpret any additional Org mode features. |
4009494e GM |
11847 | |
11848 | @table @kbd | |
acedf35c | 11849 | @orgcmd{C-c C-e x,org-export-as-xoxo} |
ce57c2fe BG |
11850 | Export as XOXO file. For an Org file @file{myfile.org}, the XOXO file will be |
11851 | @file{myfile.html}. | |
acedf35c | 11852 | @orgkey{C-c C-e v x} |
4009494e GM |
11853 | Export only the visible part of the document. |
11854 | @end table | |
11855 | ||
b349f79f | 11856 | @node iCalendar export, , XOXO export, Exporting |
4009494e GM |
11857 | @section iCalendar export |
11858 | @cindex iCalendar export | |
11859 | ||
c8d0cf5c CD |
11860 | @vindex org-icalendar-include-todo |
11861 | @vindex org-icalendar-use-deadline | |
11862 | @vindex org-icalendar-use-scheduled | |
11863 | @vindex org-icalendar-categories | |
afe98dfa | 11864 | @vindex org-icalendar-alarm-time |
e66ba1df | 11865 | Some people use Org mode for keeping track of projects, but still prefer a |
c8d0cf5c CD |
11866 | standard calendar application for anniversaries and appointments. In this |
11867 | case it can be useful to show deadlines and other time-stamped items in Org | |
e66ba1df | 11868 | files in the calendar application. Org mode can export calendar information |
c8d0cf5c CD |
11869 | in the standard iCalendar format. If you also want to have TODO entries |
11870 | included in the export, configure the variable | |
11871 | @code{org-icalendar-include-todo}. Plain timestamps are exported as VEVENT, | |
11872 | and TODO items as VTODO. It will also create events from deadlines that are | |
11873 | in non-TODO items. Deadlines and scheduling dates in TODO items will be used | |
11874 | to set the start and due dates for the TODO entry@footnote{See the variables | |
11875 | @code{org-icalendar-use-deadline} and @code{org-icalendar-use-scheduled}.}. | |
11876 | As categories, it will use the tags locally defined in the heading, and the | |
11877 | file/tree category@footnote{To add inherited tags or the TODO state, | |
afe98dfa CD |
11878 | configure the variable @code{org-icalendar-categories}.}. See the variable |
11879 | @code{org-icalendar-alarm-time} for a way to assign alarms to entries with a | |
11880 | time. | |
c8d0cf5c CD |
11881 | |
11882 | @vindex org-icalendar-store-UID | |
11883 | @cindex property, ID | |
b349f79f CD |
11884 | The iCalendar standard requires each entry to have a globally unique |
11885 | identifier (UID). Org creates these identifiers during export. If you set | |
11886 | the variable @code{org-icalendar-store-UID}, the UID will be stored in the | |
11887 | @code{:ID:} property of the entry and re-used next time you report this | |
11888 | entry. Since a single entry can give rise to multiple iCalendar entries (as | |
11889 | a timestamp, a deadline, a scheduled item, and as a TODO item), Org adds | |
11890 | prefixes to the UID, depending on what triggered the inclusion of the entry. | |
11891 | In this way the UID remains unique, but a synchronization program can still | |
11892 | figure out from which entry all the different instances originate. | |
11893 | ||
4009494e | 11894 | @table @kbd |
acedf35c | 11895 | @orgcmd{C-c C-e i,org-export-icalendar-this-file} |
4009494e GM |
11896 | Create iCalendar entries for the current file and store them in the same |
11897 | directory, using a file extension @file{.ics}. | |
acedf35c | 11898 | @orgcmd{C-c C-e I, org-export-icalendar-all-agenda-files} |
c8d0cf5c | 11899 | @vindex org-agenda-files |
4009494e GM |
11900 | Like @kbd{C-c C-e i}, but do this for all files in |
11901 | @code{org-agenda-files}. For each of these files, a separate iCalendar | |
11902 | file will be written. | |
acedf35c | 11903 | @orgcmd{C-c C-e c,org-export-icalendar-combine-agenda-files} |
c8d0cf5c | 11904 | @vindex org-combined-agenda-icalendar-file |
4009494e GM |
11905 | Create a single large iCalendar file from all files in |
11906 | @code{org-agenda-files} and write it to the file given by | |
11907 | @code{org-combined-agenda-icalendar-file}. | |
11908 | @end table | |
11909 | ||
c8d0cf5c CD |
11910 | @vindex org-use-property-inheritance |
11911 | @vindex org-icalendar-include-body | |
11912 | @cindex property, SUMMARY | |
11913 | @cindex property, DESCRIPTION | |
11914 | @cindex property, LOCATION | |
96c8522a CD |
11915 | The export will honor SUMMARY, DESCRIPTION and LOCATION@footnote{The LOCATION |
11916 | property can be inherited from higher in the hierarchy if you configure | |
11917 | @code{org-use-property-inheritance} accordingly.} properties if the selected | |
11918 | entries have them. If not, the summary will be derived from the headline, | |
11919 | and the description from the body (limited to | |
28a16a1b | 11920 | @code{org-icalendar-include-body} characters). |
dbc28aaa | 11921 | |
c8d0cf5c | 11922 | How this calendar is best read and updated, depends on the application |
4009494e GM |
11923 | you are using. The FAQ covers this issue. |
11924 | ||
86fbb8ca | 11925 | @node Publishing, Working With Source Code, Exporting, Top |
4009494e GM |
11926 | @chapter Publishing |
11927 | @cindex publishing | |
11928 | ||
c8d0cf5c CD |
11929 | Org includes a publishing management system that allows you to configure |
11930 | automatic HTML conversion of @emph{projects} composed of interlinked org | |
11931 | files. You can also configure Org to automatically upload your exported HTML | |
11932 | pages and related attachments, such as images and source code files, to a web | |
11933 | server. | |
4009494e | 11934 | |
c8d0cf5c CD |
11935 | You can also use Org to convert files into PDF, or even combine HTML and PDF |
11936 | conversion so that files are available in both formats on the server. | |
4009494e | 11937 | |
c8d0cf5c | 11938 | Publishing has been contributed to Org by David O'Toole. |
4009494e GM |
11939 | |
11940 | @menu | |
c0468714 GM |
11941 | * Configuration:: Defining projects |
11942 | * Uploading files:: How to get files up on the server | |
11943 | * Sample configuration:: Example projects | |
11944 | * Triggering publication:: Publication commands | |
4009494e GM |
11945 | @end menu |
11946 | ||
c8d0cf5c | 11947 | @node Configuration, Uploading files, Publishing, Publishing |
4009494e GM |
11948 | @section Configuration |
11949 | ||
11950 | Publishing needs significant configuration to specify files, destination | |
11951 | and many other properties of a project. | |
11952 | ||
11953 | @menu | |
c0468714 GM |
11954 | * Project alist:: The central configuration variable |
11955 | * Sources and destinations:: From here to there | |
11956 | * Selecting files:: What files are part of the project? | |
11957 | * Publishing action:: Setting the function doing the publishing | |
ce57c2fe | 11958 | * Publishing options:: Tweaking HTML/@LaTeX{} export |
c0468714 GM |
11959 | * Publishing links:: Which links keep working after publishing? |
11960 | * Sitemap:: Generating a list of all pages | |
11961 | * Generating an index:: An index that reaches across pages | |
4009494e GM |
11962 | @end menu |
11963 | ||
11964 | @node Project alist, Sources and destinations, Configuration, Configuration | |
11965 | @subsection The variable @code{org-publish-project-alist} | |
11966 | @cindex org-publish-project-alist | |
11967 | @cindex projects, for publishing | |
11968 | ||
c8d0cf5c CD |
11969 | @vindex org-publish-project-alist |
11970 | Publishing is configured almost entirely through setting the value of one | |
11971 | variable, called @code{org-publish-project-alist}. Each element of the list | |
11972 | configures one project, and may be in one of the two following forms: | |
4009494e GM |
11973 | |
11974 | @lisp | |
ce57c2fe BG |
11975 | ("project-name" :property value :property value ...) |
11976 | @r{i.e.@: a well-formed property list with alternating keys and values} | |
28a16a1b | 11977 | @r{or} |
c8d0cf5c | 11978 | ("project-name" :components ("project-name" "project-name" ...)) |
4009494e GM |
11979 | |
11980 | @end lisp | |
11981 | ||
c8d0cf5c CD |
11982 | In both cases, projects are configured by specifying property values. A |
11983 | project defines the set of files that will be published, as well as the | |
11984 | publishing configuration to use when publishing those files. When a project | |
11985 | takes the second form listed above, the individual members of the | |
11986 | @code{:components} property are taken to be sub-projects, which group | |
11987 | together files requiring different publishing options. When you publish such | |
11988 | a ``meta-project'', all the components will also be published, in the | |
11989 | sequence given. | |
4009494e GM |
11990 | |
11991 | @node Sources and destinations, Selecting files, Project alist, Configuration | |
11992 | @subsection Sources and destinations for files | |
11993 | @cindex directories, for publishing | |
11994 | ||
c8d0cf5c CD |
11995 | Most properties are optional, but some should always be set. In |
11996 | particular, Org needs to know where to look for source files, | |
4009494e GM |
11997 | and where to put published files. |
11998 | ||
11999 | @multitable @columnfractions 0.3 0.7 | |
12000 | @item @code{:base-directory} | |
12001 | @tab Directory containing publishing source files | |
12002 | @item @code{:publishing-directory} | |
c8d0cf5c CD |
12003 | @tab Directory where output files will be published. You can directly |
12004 | publish to a webserver using a file name syntax appropriate for | |
12005 | the Emacs @file{tramp} package. Or you can publish to a local directory and | |
12006 | use external tools to upload your website (@pxref{Uploading files}). | |
4009494e | 12007 | @item @code{:preparation-function} |
ed21c5c8 CD |
12008 | @tab Function or list of functions to be called before starting the |
12009 | publishing process, for example, to run @code{make} for updating files to be | |
12010 | published. The project property list is scoped into this call as the | |
12011 | variable @code{project-plist}. | |
b349f79f | 12012 | @item @code{:completion-function} |
ed21c5c8 CD |
12013 | @tab Function or list of functions called after finishing the publishing |
12014 | process, for example, to change permissions of the resulting files. The | |
12015 | project property list is scoped into this call as the variable | |
12016 | @code{project-plist}. | |
4009494e GM |
12017 | @end multitable |
12018 | @noindent | |
12019 | ||
12020 | @node Selecting files, Publishing action, Sources and destinations, Configuration | |
12021 | @subsection Selecting files | |
12022 | @cindex files, selecting for publishing | |
12023 | ||
12024 | By default, all files with extension @file{.org} in the base directory | |
12025 | are considered part of the project. This can be modified by setting the | |
28a16a1b | 12026 | properties |
4009494e GM |
12027 | @multitable @columnfractions 0.25 0.75 |
12028 | @item @code{:base-extension} | |
12029 | @tab Extension (without the dot!) of source files. This actually is a | |
c8d0cf5c CD |
12030 | regular expression. Set this to the symbol @code{any} if you want to get all |
12031 | files in @code{:base-directory}, even without extension. | |
4009494e | 12032 | |
28a16a1b | 12033 | @item @code{:exclude} |
4009494e GM |
12034 | @tab Regular expression to match file names that should not be |
12035 | published, even though they have been selected on the basis of their | |
12036 | extension. | |
12037 | ||
12038 | @item @code{:include} | |
12039 | @tab List of files to be included regardless of @code{:base-extension} | |
12040 | and @code{:exclude}. | |
acedf35c CD |
12041 | |
12042 | @item @code{:recursive} | |
12043 | @tab Non-nil means, check base-directory recursively for files to publish. | |
4009494e GM |
12044 | @end multitable |
12045 | ||
12046 | @node Publishing action, Publishing options, Selecting files, Configuration | |
a7808fba | 12047 | @subsection Publishing action |
4009494e GM |
12048 | @cindex action, for publishing |
12049 | ||
12050 | Publishing means that a file is copied to the destination directory and | |
71d35b24 CD |
12051 | possibly transformed in the process. The default transformation is to export |
12052 | Org files as HTML files, and this is done by the function | |
12053 | @code{org-publish-org-to-html} which calls the HTML exporter (@pxref{HTML | |
c8d0cf5c | 12054 | export}). But you also can publish your content as PDF files using |
afe98dfa CD |
12055 | @code{org-publish-org-to-pdf}, or as @code{ascii}, @code{latin1} or |
12056 | @code{utf8} encoded files using the corresponding functions. If you want to | |
12057 | publish the Org file itself, but with @i{archived}, @i{commented}, and | |
12058 | @i{tag-excluded} trees removed, use @code{org-publish-org-to-org} and set the | |
12059 | parameters @code{:plain-source} and/or @code{:htmlized-source}. This will | |
12060 | produce @file{file.org} and @file{file.org.html} in the publishing | |
c8d0cf5c CD |
12061 | directory@footnote{@file{file-source.org} and @file{file-source.org.html} if |
12062 | source and publishing directories are equal. Note that with this kind of | |
12063 | setup, you need to add @code{:exclude "-source\\.org"} to the project | |
acedf35c CD |
12064 | definition in @code{org-publish-project-alist} to prevent the published |
12065 | source files from being considered as new org files the next time the project | |
12066 | is published.}. Other files like images only need to be copied to the | |
12067 | publishing destination; for this you may use @code{org-publish-attachment}. | |
afe98dfa | 12068 | For non-Org files, you always need to specify the publishing function: |
4009494e GM |
12069 | |
12070 | @multitable @columnfractions 0.3 0.7 | |
12071 | @item @code{:publishing-function} | |
12072 | @tab Function executing the publication of a file. This may also be a | |
12073 | list of functions, which will all be called in turn. | |
c8d0cf5c CD |
12074 | @item @code{:plain-source} |
12075 | @tab Non-nil means, publish plain source. | |
12076 | @item @code{:htmlized-source} | |
12077 | @tab Non-nil means, publish htmlized source. | |
4009494e GM |
12078 | @end multitable |
12079 | ||
ed21c5c8 CD |
12080 | The function must accept three arguments: a property list containing at least |
12081 | a @code{:publishing-directory} property, the name of the file to be | |
12082 | published, and the path to the publishing directory of the output file. It | |
12083 | should take the specified file, make the necessary transformation (if any) | |
12084 | and place the result into the destination folder. | |
4009494e GM |
12085 | |
12086 | @node Publishing options, Publishing links, Publishing action, Configuration | |
acedf35c | 12087 | @subsection Options for the HTML/@LaTeX{} exporters |
4009494e GM |
12088 | @cindex options, for publishing |
12089 | ||
12090 | The property list can be used to set many export options for the HTML | |
acedf35c | 12091 | and @LaTeX{} exporters. In most cases, these properties correspond to user |
a7808fba | 12092 | variables in Org. The table below lists these properties along |
4009494e GM |
12093 | with the variable they belong to. See the documentation string for the |
12094 | respective variable for details. | |
12095 | ||
c8d0cf5c CD |
12096 | @vindex org-export-html-link-up |
12097 | @vindex org-export-html-link-home | |
12098 | @vindex org-export-default-language | |
12099 | @vindex org-display-custom-times | |
12100 | @vindex org-export-headline-levels | |
12101 | @vindex org-export-with-section-numbers | |
12102 | @vindex org-export-section-number-format | |
12103 | @vindex org-export-with-toc | |
12104 | @vindex org-export-preserve-breaks | |
12105 | @vindex org-export-with-archived-trees | |
12106 | @vindex org-export-with-emphasize | |
12107 | @vindex org-export-with-sub-superscripts | |
12108 | @vindex org-export-with-special-strings | |
12109 | @vindex org-export-with-footnotes | |
12110 | @vindex org-export-with-drawers | |
12111 | @vindex org-export-with-tags | |
12112 | @vindex org-export-with-todo-keywords | |
ce57c2fe BG |
12113 | @vindex org-export-with-tasks |
12114 | @vindex org-export-with-done-tasks | |
c8d0cf5c CD |
12115 | @vindex org-export-with-priority |
12116 | @vindex org-export-with-TeX-macros | |
12117 | @vindex org-export-with-LaTeX-fragments | |
12118 | @vindex org-export-skip-text-before-1st-heading | |
12119 | @vindex org-export-with-fixed-width | |
12120 | @vindex org-export-with-timestamps | |
12121 | @vindex org-export-author-info | |
ce57c2fe | 12122 | @vindex org-export-email-info |
c8d0cf5c | 12123 | @vindex org-export-creator-info |
ce57c2fe | 12124 | @vindex org-export-time-stamp-file |
c8d0cf5c CD |
12125 | @vindex org-export-with-tables |
12126 | @vindex org-export-highlight-first-table-line | |
12127 | @vindex org-export-html-style-include-default | |
ce57c2fe | 12128 | @vindex org-export-html-style-include-scripts |
c8d0cf5c CD |
12129 | @vindex org-export-html-style |
12130 | @vindex org-export-html-style-extra | |
12131 | @vindex org-export-html-link-org-files-as-html | |
12132 | @vindex org-export-html-inline-images | |
12133 | @vindex org-export-html-extension | |
12134 | @vindex org-export-html-table-tag | |
12135 | @vindex org-export-html-expand | |
12136 | @vindex org-export-html-with-timestamp | |
12137 | @vindex org-export-publishing-directory | |
12138 | @vindex org-export-html-preamble | |
12139 | @vindex org-export-html-postamble | |
c8d0cf5c CD |
12140 | @vindex user-full-name |
12141 | @vindex user-mail-address | |
12142 | @vindex org-export-select-tags | |
12143 | @vindex org-export-exclude-tags | |
12144 | ||
96c8522a CD |
12145 | @multitable @columnfractions 0.32 0.68 |
12146 | @item @code{:link-up} @tab @code{org-export-html-link-up} | |
12147 | @item @code{:link-home} @tab @code{org-export-html-link-home} | |
4009494e | 12148 | @item @code{:language} @tab @code{org-export-default-language} |
96c8522a | 12149 | @item @code{:customtime} @tab @code{org-display-custom-times} |
4009494e GM |
12150 | @item @code{:headline-levels} @tab @code{org-export-headline-levels} |
12151 | @item @code{:section-numbers} @tab @code{org-export-with-section-numbers} | |
96c8522a | 12152 | @item @code{:section-number-format} @tab @code{org-export-section-number-format} |
4009494e | 12153 | @item @code{:table-of-contents} @tab @code{org-export-with-toc} |
96c8522a | 12154 | @item @code{:preserve-breaks} @tab @code{org-export-preserve-breaks} |
4009494e GM |
12155 | @item @code{:archived-trees} @tab @code{org-export-with-archived-trees} |
12156 | @item @code{:emphasize} @tab @code{org-export-with-emphasize} | |
12157 | @item @code{:sub-superscript} @tab @code{org-export-with-sub-superscripts} | |
dbc28aaa | 12158 | @item @code{:special-strings} @tab @code{org-export-with-special-strings} |
96c8522a CD |
12159 | @item @code{:footnotes} @tab @code{org-export-with-footnotes} |
12160 | @item @code{:drawers} @tab @code{org-export-with-drawers} | |
12161 | @item @code{:tags} @tab @code{org-export-with-tags} | |
12162 | @item @code{:todo-keywords} @tab @code{org-export-with-todo-keywords} | |
ce57c2fe | 12163 | @item @code{:tasks} @tab @code{org-export-with-tasks} |
96c8522a | 12164 | @item @code{:priority} @tab @code{org-export-with-priority} |
4009494e GM |
12165 | @item @code{:TeX-macros} @tab @code{org-export-with-TeX-macros} |
12166 | @item @code{:LaTeX-fragments} @tab @code{org-export-with-LaTeX-fragments} | |
6eb02347 | 12167 | @item @code{:latex-listings} @tab @code{org-export-latex-listings} |
96c8522a | 12168 | @item @code{:skip-before-1st-heading} @tab @code{org-export-skip-text-before-1st-heading} |
4009494e | 12169 | @item @code{:fixed-width} @tab @code{org-export-with-fixed-width} |
44ce9197 | 12170 | @item @code{:timestamps} @tab @code{org-export-with-timestamps} |
ce57c2fe BG |
12171 | @item @code{:author} @tab @code{user-full-name} |
12172 | @item @code{:email} @tab @code{user-mail-address} : @code{addr;addr;..} | |
44ce9197 | 12173 | @item @code{:author-info} @tab @code{org-export-author-info} |
ed21c5c8 | 12174 | @item @code{:email-info} @tab @code{org-export-email-info} |
44ce9197 | 12175 | @item @code{:creator-info} @tab @code{org-export-creator-info} |
4009494e GM |
12176 | @item @code{:tables} @tab @code{org-export-with-tables} |
12177 | @item @code{:table-auto-headline} @tab @code{org-export-highlight-first-table-line} | |
e45e3595 | 12178 | @item @code{:style-include-default} @tab @code{org-export-html-style-include-default} |
ce57c2fe | 12179 | @item @code{:style-include-scripts} @tab @code{org-export-html-style-include-scripts} |
4009494e | 12180 | @item @code{:style} @tab @code{org-export-html-style} |
44ce9197 | 12181 | @item @code{:style-extra} @tab @code{org-export-html-style-extra} |
4009494e GM |
12182 | @item @code{:convert-org-links} @tab @code{org-export-html-link-org-files-as-html} |
12183 | @item @code{:inline-images} @tab @code{org-export-html-inline-images} | |
96c8522a | 12184 | @item @code{:html-extension} @tab @code{org-export-html-extension} |
ce57c2fe BG |
12185 | @item @code{:html-preamble} @tab @code{org-export-html-preamble} |
12186 | @item @code{:html-postamble} @tab @code{org-export-html-postamble} | |
c8d0cf5c | 12187 | @item @code{:xml-declaration} @tab @code{org-export-html-xml-declaration} |
96c8522a | 12188 | @item @code{:html-table-tag} @tab @code{org-export-html-table-tag} |
4009494e GM |
12189 | @item @code{:expand-quoted-html} @tab @code{org-export-html-expand} |
12190 | @item @code{:timestamp} @tab @code{org-export-html-with-timestamp} | |
12191 | @item @code{:publishing-directory} @tab @code{org-export-publishing-directory} | |
864c9740 CD |
12192 | @item @code{:select-tags} @tab @code{org-export-select-tags} |
12193 | @item @code{:exclude-tags} @tab @code{org-export-exclude-tags} | |
c8d0cf5c | 12194 | @item @code{:latex-image-options} @tab @code{org-export-latex-image-default-option} |
4009494e GM |
12195 | @end multitable |
12196 | ||
12197 | Most of the @code{org-export-with-*} variables have the same effect in | |
acedf35c | 12198 | both HTML and @LaTeX{} exporters, except for @code{:TeX-macros} and |
ce57c2fe BG |
12199 | @code{:LaTeX-fragments} options, respectively @code{nil} and @code{t} in the |
12200 | @LaTeX{} export. See @code{org-export-plist-vars} to check this list of | |
12201 | options. | |
12202 | ||
12203 | ||
4009494e | 12204 | |
c8d0cf5c | 12205 | @vindex org-publish-project-alist |
dbc28aaa CD |
12206 | When a property is given a value in @code{org-publish-project-alist}, |
12207 | its setting overrides the value of the corresponding user variable (if | |
12208 | any) during publishing. Options set within a file (@pxref{Export | |
4009494e GM |
12209 | options}), however, override everything. |
12210 | ||
ed21c5c8 | 12211 | @node Publishing links, Sitemap, Publishing options, Configuration |
4009494e GM |
12212 | @subsection Links between published files |
12213 | @cindex links, publishing | |
12214 | ||
a7808fba | 12215 | To create a link from one Org file to another, you would use |
4009494e | 12216 | something like @samp{[[file:foo.org][The foo]]} or simply |
c8d0cf5c | 12217 | @samp{file:foo.org.} (@pxref{Hyperlinks}). When published, this link |
4009494e GM |
12218 | becomes a link to @file{foo.html}. In this way, you can interlink the |
12219 | pages of your "org web" project and the links will work as expected when | |
c8d0cf5c CD |
12220 | you publish them to HTML. If you also publish the Org source file and want |
12221 | to link to that, use an @code{http:} link instead of a @code{file:} link, | |
12222 | because @code{file:} links are converted to link to the corresponding | |
12223 | @file{html} file. | |
4009494e | 12224 | |
ce57c2fe | 12225 | You may also link to related files, such as images. Provided you are careful |
c8d0cf5c | 12226 | with relative file names, and provided you have also configured Org to upload |
ce57c2fe | 12227 | the related files, these links will work too. See @ref{Complex example}, for |
c8d0cf5c | 12228 | an example of this usage. |
4009494e | 12229 | |
c8d0cf5c | 12230 | Sometimes an Org file to be published may contain links that are |
4009494e | 12231 | only valid in your production environment, but not in the publishing |
28a16a1b | 12232 | location. In this case, use the property |
4009494e GM |
12233 | |
12234 | @multitable @columnfractions 0.4 0.6 | |
12235 | @item @code{:link-validation-function} | |
12236 | @tab Function to validate links | |
12237 | @end multitable | |
12238 | ||
12239 | @noindent | |
12240 | to define a function for checking link validity. This function must | |
12241 | accept two arguments, the file name and a directory relative to which | |
12242 | the file name is interpreted in the production environment. If this | |
12243 | function returns @code{nil}, then the HTML generator will only insert a | |
12244 | description into the HTML file, but no link. One option for this | |
12245 | function is @code{org-publish-validate-link} which checks if the given | |
12246 | file is part of any project in @code{org-publish-project-alist}. | |
12247 | ||
ed21c5c8 CD |
12248 | @node Sitemap, Generating an index, Publishing links, Configuration |
12249 | @subsection Generating a sitemap | |
12250 | @cindex sitemap, of published pages | |
4009494e | 12251 | |
86fbb8ca | 12252 | The following properties may be used to control publishing of |
ed21c5c8 | 12253 | a map of files for a given project. |
4009494e | 12254 | |
86fbb8ca | 12255 | @multitable @columnfractions 0.35 0.65 |
ed21c5c8 CD |
12256 | @item @code{:auto-sitemap} |
12257 | @tab When non-nil, publish a sitemap during @code{org-publish-current-project} | |
c8d0cf5c | 12258 | or @code{org-publish-all}. |
4009494e | 12259 | |
ed21c5c8 | 12260 | @item @code{:sitemap-filename} |
ce57c2fe | 12261 | @tab Filename for output of sitemap. Defaults to @file{sitemap.org} (which |
c8d0cf5c | 12262 | becomes @file{sitemap.html}). |
4009494e | 12263 | |
ed21c5c8 | 12264 | @item @code{:sitemap-title} |
ce57c2fe | 12265 | @tab Title of sitemap page. Defaults to name of file. |
4009494e | 12266 | |
ed21c5c8 CD |
12267 | @item @code{:sitemap-function} |
12268 | @tab Plug-in function to use for generation of the sitemap. | |
12269 | Defaults to @code{org-publish-org-sitemap}, which generates a plain list | |
4009494e | 12270 | of links to all files in the project. |
86fbb8ca CD |
12271 | |
12272 | @item @code{:sitemap-sort-folders} | |
12273 | @tab Where folders should appear in the sitemap. Set this to @code{first} | |
12274 | (default) or @code{last} to display folders first or last, | |
12275 | respectively. Any other value will mix files and folders. | |
12276 | ||
ce57c2fe BG |
12277 | @item @code{:sitemap-sort-files} |
12278 | @tab How the files are sorted in the site map. Set this to | |
12279 | @code{alphabetically} (default), @code{chronologically} or | |
12280 | @code{anti-chronologically}. @code{chronologically} sorts the files with | |
12281 | older date first while @code{anti-chronologically} sorts the files with newer | |
12282 | date first. @code{alphabetically} sorts the files alphabetically. The date of | |
12283 | a file is retrieved with @code{org-publish-find-date}. | |
86fbb8ca CD |
12284 | |
12285 | @item @code{:sitemap-ignore-case} | |
12286 | @tab Should sorting be case-sensitive? Default @code{nil}. | |
12287 | ||
ce57c2fe | 12288 | @item @code{:sitemap-file-entry-format} |
c80e3b4a | 12289 | @tab With this option one can tell how a sitemap's entry is formatted in the |
ce57c2fe BG |
12290 | sitemap. This is a format string with some escape sequences: @code{%t} stands |
12291 | for the title of the file, @code{%a} stands for the author of the file and | |
12292 | @code{%d} stands for the date of the file. The date is retrieved with the | |
c80e3b4a | 12293 | @code{org-publish-find-date} function and formatted with |
ce57c2fe BG |
12294 | @code{org-publish-sitemap-date-format}. Default @code{%t}. |
12295 | ||
12296 | @item @code{:sitemap-date-format} | |
12297 | @tab Format string for the @code{format-time-string} function that tells how | |
c80e3b4a | 12298 | a sitemap entry's date is to be formatted. This property bypasses |
ce57c2fe BG |
12299 | @code{org-publish-sitemap-date-format} which defaults to @code{%Y-%m-%d}. |
12300 | ||
12301 | @item @code{:sitemap-sans-extension} | |
12302 | @tab When non-nil, remove filenames' extensions from the generated sitemap. | |
12303 | Useful to have cool URIs (see @uref{http://www.w3.org/Provider/Style/URI}). | |
12304 | Defaults to @code{nil}. | |
12305 | ||
4009494e GM |
12306 | @end multitable |
12307 | ||
ed21c5c8 CD |
12308 | @node Generating an index, , Sitemap, Configuration |
12309 | @subsection Generating an index | |
12310 | @cindex index, in a publishing project | |
12311 | ||
e66ba1df | 12312 | Org mode can generate an index across the files of a publishing project. |
ed21c5c8 CD |
12313 | |
12314 | @multitable @columnfractions 0.25 0.75 | |
12315 | @item @code{:makeindex} | |
12316 | @tab When non-nil, generate in index in the file @file{theindex.org} and | |
12317 | publish it as @file{theindex.html}. | |
12318 | @end multitable | |
12319 | ||
ce57c2fe | 12320 | The file will be created when first publishing a project with the |
ed21c5c8 | 12321 | @code{:makeindex} set. The file only contains a statement @code{#+include: |
ce57c2fe BG |
12322 | "theindex.inc"}. You can then build around this include statement by adding |
12323 | a title, style information, etc. | |
ed21c5c8 | 12324 | |
c8d0cf5c CD |
12325 | @node Uploading files, Sample configuration, Configuration, Publishing |
12326 | @section Uploading files | |
12327 | @cindex rsync | |
12328 | @cindex unison | |
12329 | ||
12330 | For those people already utilizing third party sync tools such as | |
12331 | @command{rsync} or @command{unison}, it might be preferable not to use the built in | |
e66ba1df | 12332 | @i{remote} publishing facilities of Org mode which rely heavily on |
c8d0cf5c CD |
12333 | Tramp. Tramp, while very useful and powerful, tends not to be |
12334 | so efficient for multiple file transfer and has been known to cause problems | |
12335 | under heavy usage. | |
12336 | ||
12337 | Specialized synchronization utilities offer several advantages. In addition | |
12338 | to timestamp comparison, they also do content and permissions/attribute | |
12339 | checks. For this reason you might prefer to publish your web to a local | |
12340 | directory (possibly even @i{in place} with your Org files) and then use | |
12341 | @file{unison} or @file{rsync} to do the synchronization with the remote host. | |
12342 | ||
12343 | Since Unison (for example) can be configured as to which files to transfer to | |
12344 | a certain remote destination, it can greatly simplify the project publishing | |
12345 | definition. Simply keep all files in the correct location, process your Org | |
12346 | files with @code{org-publish} and let the synchronization tool do the rest. | |
12347 | You do not need, in this scenario, to include attachments such as @file{jpg}, | |
12348 | @file{css} or @file{gif} files in the project definition since the 3rd party | |
12349 | tool syncs them. | |
12350 | ||
12351 | Publishing to a local directory is also much faster than to a remote one, so | |
12352 | that you can afford more easily to republish entire projects. If you set | |
12353 | @code{org-publish-use-timestamps-flag} to @code{nil}, you gain the main | |
12354 | benefit of re-including any changed external files such as source example | |
12355 | files you might include with @code{#+INCLUDE}. The timestamp mechanism in | |
12356 | Org is not smart enough to detect if included files have been modified. | |
12357 | ||
12358 | @node Sample configuration, Triggering publication, Uploading files, Publishing | |
4009494e GM |
12359 | @section Sample configuration |
12360 | ||
12361 | Below we provide two example configurations. The first one is a simple | |
a7808fba | 12362 | project publishing only a set of Org files. The second example is |
4009494e GM |
12363 | more complex, with a multi-component project. |
12364 | ||
12365 | @menu | |
c0468714 GM |
12366 | * Simple example:: One-component publishing |
12367 | * Complex example:: A multi-component publishing example | |
4009494e GM |
12368 | @end menu |
12369 | ||
12370 | @node Simple example, Complex example, Sample configuration, Sample configuration | |
12371 | @subsection Example: simple publishing configuration | |
12372 | ||
a7808fba | 12373 | This example publishes a set of Org files to the @file{public_html} |
4009494e GM |
12374 | directory on the local machine. |
12375 | ||
12376 | @lisp | |
12377 | (setq org-publish-project-alist | |
28a16a1b | 12378 | '(("org" |
4009494e GM |
12379 | :base-directory "~/org/" |
12380 | :publishing-directory "~/public_html" | |
12381 | :section-numbers nil | |
12382 | :table-of-contents nil | |
e45e3595 | 12383 | :style "<link rel=\"stylesheet\" |
4009494e | 12384 | href=\"../other/mystyle.css\" |
c8d0cf5c | 12385 | type=\"text/css\"/>"))) |
4009494e GM |
12386 | @end lisp |
12387 | ||
12388 | @node Complex example, , Simple example, Sample configuration | |
12389 | @subsection Example: complex publishing configuration | |
12390 | ||
12391 | This more complicated example publishes an entire website, including | |
c8d0cf5c | 12392 | Org files converted to HTML, image files, Emacs Lisp source code, and |
ce57c2fe | 12393 | style sheets. The publishing directory is remote and private files are |
4009494e GM |
12394 | excluded. |
12395 | ||
12396 | To ensure that links are preserved, care should be taken to replicate | |
12397 | your directory structure on the web server, and to use relative file | |
ce57c2fe | 12398 | paths. For example, if your Org files are kept in @file{~/org} and your |
86fbb8ca | 12399 | publishable images in @file{~/images}, you would link to an image with |
4009494e GM |
12400 | @c |
12401 | @example | |
12402 | file:../images/myimage.png | |
12403 | @end example | |
12404 | @c | |
12405 | On the web server, the relative path to the image should be the | |
ce57c2fe | 12406 | same. You can accomplish this by setting up an "images" folder in the |
a7808fba | 12407 | right place on the web server, and publishing images to it. |
4009494e GM |
12408 | |
12409 | @lisp | |
12410 | (setq org-publish-project-alist | |
12411 | '(("orgfiles" | |
12412 | :base-directory "~/org/" | |
12413 | :base-extension "org" | |
12414 | :publishing-directory "/ssh:user@@host:~/html/notebook/" | |
12415 | :publishing-function org-publish-org-to-html | |
12416 | :exclude "PrivatePage.org" ;; regexp | |
12417 | :headline-levels 3 | |
12418 | :section-numbers nil | |
12419 | :table-of-contents nil | |
e45e3595 | 12420 | :style "<link rel=\"stylesheet\" |
c8d0cf5c | 12421 | href=\"../other/mystyle.css\" type=\"text/css\"/>" |
ce57c2fe | 12422 | :html-preamble t) |
28a16a1b | 12423 | |
4009494e GM |
12424 | ("images" |
12425 | :base-directory "~/images/" | |
12426 | :base-extension "jpg\\|gif\\|png" | |
12427 | :publishing-directory "/ssh:user@@host:~/html/images/" | |
12428 | :publishing-function org-publish-attachment) | |
28a16a1b | 12429 | |
4009494e GM |
12430 | ("other" |
12431 | :base-directory "~/other/" | |
12432 | :base-extension "css\\|el" | |
12433 | :publishing-directory "/ssh:user@@host:~/html/other/" | |
12434 | :publishing-function org-publish-attachment) | |
12435 | ("website" :components ("orgfiles" "images" "other")))) | |
12436 | @end lisp | |
12437 | ||
12438 | @node Triggering publication, , Sample configuration, Publishing | |
12439 | @section Triggering publication | |
12440 | ||
c8d0cf5c | 12441 | Once properly configured, Org can publish with the following commands: |
4009494e GM |
12442 | |
12443 | @table @kbd | |
acedf35c | 12444 | @orgcmd{C-c C-e X,org-publish} |
4009494e | 12445 | Prompt for a specific project and publish all files that belong to it. |
acedf35c | 12446 | @orgcmd{C-c C-e P,org-publish-current-project} |
4009494e | 12447 | Publish the project containing the current file. |
acedf35c | 12448 | @orgcmd{C-c C-e F,org-publish-current-file} |
4009494e | 12449 | Publish only the current file. |
acedf35c | 12450 | @orgcmd{C-c C-e E,org-publish-all} |
c8d0cf5c | 12451 | Publish every project. |
4009494e GM |
12452 | @end table |
12453 | ||
c8d0cf5c | 12454 | @vindex org-publish-use-timestamps-flag |
ce57c2fe BG |
12455 | Org uses timestamps to track when a file has changed. The above functions |
12456 | normally only publish changed files. You can override this and force | |
c8d0cf5c CD |
12457 | publishing of all files by giving a prefix argument to any of the commands |
12458 | above, or by customizing the variable @code{org-publish-use-timestamps-flag}. | |
12459 | This may be necessary in particular if files include other files via | |
12460 | @code{#+SETUPFILE:} or @code{#+INCLUDE:}. | |
4009494e | 12461 | |
86fbb8ca CD |
12462 | @comment node-name, next, previous, up |
12463 | @comment Working With Source Code, Miscellaneous, Publishing, Top | |
12464 | ||
12465 | @node Working With Source Code, Miscellaneous, Publishing, Top | |
12466 | @chapter Working with source code | |
12467 | @cindex Schulte, Eric | |
12468 | @cindex Davison, Dan | |
12469 | @cindex source code, working with | |
12470 | ||
e66ba1df | 12471 | Source code can be included in Org mode documents using a @samp{src} block, |
ce57c2fe | 12472 | e.g.@: |
86fbb8ca CD |
12473 | |
12474 | @example | |
12475 | #+BEGIN_SRC emacs-lisp | |
12476 | (defun org-xor (a b) | |
12477 | "Exclusive or." | |
12478 | (if a (not b) b)) | |
12479 | #+END_SRC | |
12480 | @end example | |
12481 | ||
e66ba1df | 12482 | Org mode provides a number of features for working with live source code, |
86fbb8ca | 12483 | including editing of code blocks in their native major-mode, evaluation of |
ce57c2fe BG |
12484 | code blocks, converting code blocks into source files (known as @dfn{tangling} |
12485 | in literate programming), and exporting code blocks and their | |
afe98dfa CD |
12486 | results in several formats. This functionality was contributed by Eric |
12487 | Schulte and Dan Davison, and was originally named Org-babel. | |
86fbb8ca | 12488 | |
e66ba1df | 12489 | The following sections describe Org mode's code block handling facilities. |
4009494e GM |
12490 | |
12491 | @menu | |
c0468714 GM |
12492 | * Structure of code blocks:: Code block syntax described |
12493 | * Editing source code:: Language major-mode editing | |
12494 | * Exporting code blocks:: Export contents and/or results | |
12495 | * Extracting source code:: Create pure source code files | |
e66ba1df | 12496 | * Evaluating code blocks:: Place results of evaluation in the Org mode buffer |
c0468714 GM |
12497 | * Library of Babel:: Use and contribute to a library of useful code blocks |
12498 | * Languages:: List of supported code block languages | |
12499 | * Header arguments:: Configure code block functionality | |
12500 | * Results of evaluation:: How evaluation results are handled | |
e66ba1df | 12501 | * Noweb reference syntax:: Literate programming in Org mode |
86fbb8ca | 12502 | * Key bindings and useful functions:: Work quickly with code blocks |
c0468714 | 12503 | * Batch execution:: Call functions from the command line |
4009494e GM |
12504 | @end menu |
12505 | ||
86fbb8ca CD |
12506 | @comment node-name, next, previous, up |
12507 | @comment Structure of code blocks, Editing source code, Working With Source Code, Working With Source Code | |
c8d0cf5c | 12508 | |
86fbb8ca CD |
12509 | @node Structure of code blocks, Editing source code, Working With Source Code, Working With Source Code |
12510 | @section Structure of code blocks | |
12511 | @cindex code block, structure | |
12512 | @cindex source code, block structure | |
e66ba1df BG |
12513 | @cindex #+NAME |
12514 | @cindex #+BEGIN_SRC | |
4009494e | 12515 | |
e66ba1df BG |
12516 | Live code blocks can be specified with a @samp{src} block or |
12517 | inline.@footnote{Note that @samp{src} blocks may be inserted using Org mode's | |
12518 | @ref{Easy Templates} system} The structure of a @samp{src} block is | |
6eb02347 | 12519 | |
86fbb8ca | 12520 | @example |
e66ba1df BG |
12521 | #+NAME: <name> |
12522 | #+BEGIN_SRC <language> <switches> <header arguments> | |
86fbb8ca | 12523 | <body> |
e66ba1df | 12524 | #+END_SRC |
86fbb8ca | 12525 | @end example |
4009494e | 12526 | |
e66ba1df BG |
12527 | The @code{#+NAME:} line is optional, and can be used to name the code |
12528 | block. Live code blocks require that a language be specified on the | |
12529 | @code{#+BEGIN_SRC} line. Switches and header arguments are optional. | |
12530 | @cindex source code, inline | |
12531 | ||
12532 | Live code blocks can also be specified inline using | |
afe98dfa CD |
12533 | |
12534 | @example | |
12535 | src_<language>@{<body>@} | |
12536 | @end example | |
12537 | ||
12538 | or | |
12539 | ||
12540 | @example | |
12541 | src_<language>[<header arguments>]@{<body>@} | |
12542 | @end example | |
12543 | ||
86fbb8ca | 12544 | @table @code |
e66ba1df BG |
12545 | @item <#+NAME: name> |
12546 | This line associates a name with the code block. This is similar to the | |
12547 | @code{#+TBLNAME: NAME} lines that can be used to name tables in Org mode | |
12548 | files. Referencing the name of a code block makes it possible to evaluate | |
12549 | the block from other places in the file, from other files, or from Org mode | |
12550 | table formulas (see @ref{The spreadsheet}). Names are assumed to be unique | |
12551 | and the behavior of Org mode when two or more blocks share the same name is | |
ce57c2fe | 12552 | undefined. |
e66ba1df | 12553 | @cindex #+NAME |
86fbb8ca | 12554 | @item <language> |
e66ba1df BG |
12555 | The language of the code in the block (see @ref{Languages}). |
12556 | @cindex source code, language | |
86fbb8ca | 12557 | @item <switches> |
e66ba1df | 12558 | Optional switches control code block export (see the discussion of switches in |
86fbb8ca | 12559 | @ref{Literal examples}) |
e66ba1df | 12560 | @cindex source code, switches |
86fbb8ca CD |
12561 | @item <header arguments> |
12562 | Optional header arguments control many aspects of evaluation, export and | |
e66ba1df | 12563 | tangling of code blocks (see @ref{Header arguments}). |
ce57c2fe | 12564 | Header arguments can also be set on a per-buffer or per-subtree |
86fbb8ca | 12565 | basis using properties. |
e66ba1df | 12566 | @item source code, header arguments |
86fbb8ca | 12567 | @item <body> |
e66ba1df | 12568 | Source code in the specified language. |
4009494e GM |
12569 | @end table |
12570 | ||
86fbb8ca CD |
12571 | @comment node-name, next, previous, up |
12572 | @comment Editing source code, Exporting code blocks, Structure of code blocks, Working With Source Code | |
17673adf | 12573 | |
86fbb8ca CD |
12574 | @node Editing source code, Exporting code blocks, Structure of code blocks, Working With Source Code |
12575 | @section Editing source code | |
12576 | @cindex code block, editing | |
12577 | @cindex source code, editing | |
17673adf | 12578 | |
86fbb8ca | 12579 | @kindex C-c ' |
ce57c2fe | 12580 | Use @kbd{C-c '} to edit the current code block. This brings up |
86fbb8ca | 12581 | a language major-mode edit buffer containing the body of the code |
ce57c2fe BG |
12582 | block. Saving this buffer will write the new contents back to the Org |
12583 | buffer. Use @kbd{C-c '} again to exit. | |
4009494e | 12584 | |
ce57c2fe | 12585 | The @code{org-src-mode} minor mode will be active in the edit buffer. The |
86fbb8ca | 12586 | following variables can be used to configure the behavior of the edit |
ce57c2fe | 12587 | buffer. See also the customization group @code{org-edit-structure} for |
86fbb8ca CD |
12588 | further configuration options. |
12589 | ||
12590 | @table @code | |
12591 | @item org-src-lang-modes | |
12592 | If an Emacs major-mode named @code{<lang>-mode} exists, where | |
12593 | @code{<lang>} is the language named in the header line of the code block, | |
ce57c2fe | 12594 | then the edit buffer will be placed in that major-mode. This variable |
86fbb8ca CD |
12595 | can be used to map arbitrary language names to existing major modes. |
12596 | @item org-src-window-setup | |
12597 | Controls the way Emacs windows are rearranged when the edit buffer is created. | |
12598 | @item org-src-preserve-indentation | |
12599 | This variable is especially useful for tangling languages such as | |
acedf35c | 12600 | Python, in which whitespace indentation in the output is critical. |
86fbb8ca | 12601 | @item org-src-ask-before-returning-to-edit-buffer |
ce57c2fe BG |
12602 | By default, Org will ask before returning to an open edit buffer. Set this |
12603 | variable to nil to switch without asking. | |
86fbb8ca CD |
12604 | @end table |
12605 | ||
ce57c2fe BG |
12606 | To turn on native code fontification in the @emph{Org} buffer, configure the |
12607 | variable @code{org-src-fontify-natively}. | |
12608 | ||
86fbb8ca CD |
12609 | @comment node-name, next, previous, up |
12610 | @comment Exporting code blocks, Extracting source code, Editing source code, Working With Source Code | |
12611 | ||
12612 | @node Exporting code blocks, Extracting source code, Editing source code, Working With Source Code | |
12613 | @section Exporting code blocks | |
12614 | @cindex code block, exporting | |
12615 | @cindex source code, exporting | |
12616 | ||
e66ba1df BG |
12617 | It is possible to export the @emph{code} of code blocks, the @emph{results} |
12618 | of code block evaluation, @emph{both} the code and the results of code block | |
12619 | evaluation, or @emph{none}. For most languages, the default exports code. | |
12620 | However, for some languages (e.g.@: @code{ditaa}) the default exports the | |
12621 | results of code block evaluation. For information on exporting code block | |
12622 | bodies, see @ref{Literal examples}. | |
86fbb8ca CD |
12623 | |
12624 | The @code{:exports} header argument can be used to specify export | |
12625 | behavior: | |
12626 | ||
12627 | @subsubheading Header arguments: | |
12628 | @table @code | |
12629 | @item :exports code | |
ce57c2fe | 12630 | The default in most languages. The body of the code block is exported, as |
86fbb8ca CD |
12631 | described in @ref{Literal examples}. |
12632 | @item :exports results | |
12633 | The code block will be evaluated and the results will be placed in the | |
e66ba1df | 12634 | Org mode buffer for export, either updating previous results of the code |
86fbb8ca CD |
12635 | block located anywhere in the buffer or, if no previous results exist, |
12636 | placing the results immediately after the code block. The body of the code | |
12637 | block will not be exported. | |
12638 | @item :exports both | |
12639 | Both the code block and its results will be exported. | |
12640 | @item :exports none | |
12641 | Neither the code block nor its results will be exported. | |
12642 | @end table | |
12643 | ||
12644 | It is possible to inhibit the evaluation of code blocks during export. | |
acedf35c | 12645 | Setting the @code{org-export-babel-evaluate} variable to @code{nil} will |
86fbb8ca | 12646 | ensure that no code blocks are evaluated as part of the export process. This |
e66ba1df BG |
12647 | can be useful in situations where potentially untrusted Org mode files are |
12648 | exported in an automated fashion, for example when Org mode is used as the | |
86fbb8ca CD |
12649 | markup language for a wiki. |
12650 | ||
12651 | @comment node-name, next, previous, up | |
12652 | @comment Extracting source code, Evaluating code blocks, Exporting code blocks, Working With Source Code | |
12653 | @node Extracting source code, Evaluating code blocks, Exporting code blocks, Working With Source Code | |
12654 | @section Extracting source code | |
ce57c2fe | 12655 | @cindex tangling |
86fbb8ca CD |
12656 | @cindex source code, extracting |
12657 | @cindex code block, extracting source code | |
12658 | ||
12659 | Creating pure source code files by extracting code from source blocks is | |
12660 | referred to as ``tangling''---a term adopted from the literate programming | |
12661 | community. During ``tangling'' of code blocks their bodies are expanded | |
12662 | using @code{org-babel-expand-src-block} which can expand both variable and | |
12663 | ``noweb'' style references (see @ref{Noweb reference syntax}). | |
12664 | ||
12665 | @subsubheading Header arguments | |
12666 | @table @code | |
12667 | @item :tangle no | |
12668 | The default. The code block is not included in the tangled output. | |
12669 | @item :tangle yes | |
ce57c2fe | 12670 | Include the code block in the tangled output. The output file name is the |
86fbb8ca CD |
12671 | name of the org file with the extension @samp{.org} replaced by the extension |
12672 | for the block language. | |
12673 | @item :tangle filename | |
12674 | Include the code block in the tangled output to file @samp{filename}. | |
12675 | @end table | |
12676 | ||
12677 | @kindex C-c C-v t | |
12678 | @subsubheading Functions | |
12679 | @table @code | |
ce57c2fe | 12680 | @item org-babel-tangle |
afe98dfa | 12681 | Tangle the current file. Bound to @kbd{C-c C-v t}. |
86fbb8ca | 12682 | @item org-babel-tangle-file |
ce57c2fe | 12683 | Choose a file to tangle. Bound to @kbd{C-c C-v f}. |
86fbb8ca CD |
12684 | @end table |
12685 | ||
12686 | @subsubheading Hooks | |
12687 | @table @code | |
12688 | @item org-babel-post-tangle-hook | |
12689 | This hook is run from within code files tangled by @code{org-babel-tangle}. | |
12690 | Example applications could include post-processing, compilation or evaluation | |
12691 | of tangled code files. | |
12692 | @end table | |
12693 | ||
12694 | @node Evaluating code blocks, Library of Babel, Extracting source code, Working With Source Code | |
12695 | @section Evaluating code blocks | |
12696 | @cindex code block, evaluating | |
12697 | @cindex source code, evaluating | |
153ae947 | 12698 | @cindex #+RESULTS |
86fbb8ca CD |
12699 | |
12700 | Code blocks can be evaluated@footnote{Whenever code is evaluated there is a | |
e66ba1df BG |
12701 | potential for that code to do harm. Org mode provides safeguards to ensure |
12702 | that code is only evaluated after explicit confirmation from the user. For | |
12703 | information on these safeguards (and on how to disable them) see @ref{Code | |
12704 | evaluation security}.} and the results of evaluation optionally placed in the | |
153ae947 BG |
12705 | Org mode buffer. The results of evaluation are placed following a line that |
12706 | begins by default with @code{#+RESULTS} and optionally a cache identifier | |
12707 | and/or the name of the evaluated code block. The default value of | |
12708 | @code{#+RESULTS} can be changed with the customizable variable | |
12709 | @code{org-babel-results-keyword}. | |
12710 | ||
12711 | By default, the evaluation facility is only enabled for Lisp code blocks | |
12712 | specified as @code{emacs-lisp}. However, source code blocks in many languages | |
12713 | can be evaluated within Org mode (see @ref{Languages} for a list of supported | |
12714 | languages and @ref{Structure of code blocks} for information on the syntax | |
12715 | used to define a code block). | |
86fbb8ca CD |
12716 | |
12717 | @kindex C-c C-c | |
12718 | There are a number of ways to evaluate code blocks. The simplest is to press | |
12719 | @kbd{C-c C-c} or @kbd{C-c C-v e} with the point on a code block@footnote{The | |
12720 | @code{org-babel-no-eval-on-ctrl-c-ctrl-c} variable can be used to remove code | |
12721 | evaluation from the @kbd{C-c C-c} key binding.}. This will call the | |
12722 | @code{org-babel-execute-src-block} function to evaluate the block and insert | |
e66ba1df BG |
12723 | its results into the Org mode buffer. |
12724 | @cindex #+CALL | |
86fbb8ca CD |
12725 | |
12726 | It is also possible to evaluate named code blocks from anywhere in an | |
e66ba1df BG |
12727 | Org mode buffer or an Org mode table. Live code blocks located in the current |
12728 | Org mode buffer or in the ``Library of Babel'' (see @ref{Library of Babel}) | |
12729 | can be executed. Named code blocks can be executed with a separate | |
12730 | @code{#+CALL:} line or inline within a block of text. | |
12731 | ||
12732 | The syntax of the @code{#+CALL:} line is | |
86fbb8ca CD |
12733 | |
12734 | @example | |
e66ba1df BG |
12735 | #+CALL: <name>(<arguments>) |
12736 | #+CALL: <name>[<inside header arguments>](<arguments>) <end header arguments> | |
ce57c2fe BG |
12737 | @end example |
12738 | ||
e66ba1df | 12739 | The syntax for inline evaluation of named code blocks is |
ce57c2fe BG |
12740 | |
12741 | @example | |
e66ba1df BG |
12742 | ... call_<name>(<arguments>) ... |
12743 | ... call_<name>[<inside header arguments>](<arguments>)[<end header arguments>] ... | |
86fbb8ca CD |
12744 | @end example |
12745 | ||
12746 | @table @code | |
12747 | @item <name> | |
e66ba1df | 12748 | The name of the code block to be evaluated (see @ref{Structure of code blocks}). |
86fbb8ca | 12749 | @item <arguments> |
ce57c2fe | 12750 | Arguments specified in this section will be passed to the code block. These |
e66ba1df BG |
12751 | arguments use standard function call syntax, rather than |
12752 | header argument syntax. For example, a @code{#+CALL:} line that passes the | |
12753 | number four to a code block named @code{double}, which declares the header | |
12754 | argument @code{:var n=2}, would be written as @code{#+CALL: double(n=4)}. | |
12755 | @item <inside header arguments> | |
12756 | Inside header arguments are passed through and applied to the named code | |
12757 | block. These arguments use header argument syntax rather than standard | |
12758 | function call syntax. Inside header arguments affect how the code block is | |
12759 | evaluated. For example, @code{[:results output]} will collect the results of | |
12760 | everything printed to @code{STDOUT} during execution of the code block. | |
12761 | @item <end header arguments> | |
12762 | End header arguments are applied to the calling instance and do not affect | |
12763 | evaluation of the named code block. They affect how the results are | |
12764 | incorporated into the Org mode buffer and how the call line is exported. For | |
12765 | example, @code{:results html} will insert the results of the call line | |
12766 | evaluation in the Org buffer, wrapped in a @code{BEGIN_HTML:} block. | |
12767 | ||
12768 | For more examples of passing header arguments to @code{#+CALL:} lines see | |
ce57c2fe BG |
12769 | @ref{Header arguments in function calls}. |
12770 | @end table | |
86fbb8ca CD |
12771 | |
12772 | @node Library of Babel, Languages, Evaluating code blocks, Working With Source Code | |
12773 | @section Library of Babel | |
12774 | @cindex babel, library of | |
12775 | @cindex source code, library | |
12776 | @cindex code block, library | |
12777 | ||
e66ba1df BG |
12778 | The ``Library of Babel'' consists of code blocks that can be called from any |
12779 | Org mode file. Code blocks defined in the ``Library of Babel'' can be called | |
12780 | remotely as if they were in the current Org mode buffer (see @ref{Evaluating | |
12781 | code blocks} for information on the syntax of remote code block evaluation). | |
12782 | ||
12783 | ||
12784 | The central repository of code blocks in the ``Library of Babel'' is housed | |
12785 | in an Org mode file located in the @samp{contrib} directory of Org mode. | |
12786 | ||
12787 | Users can add code blocks they believe to be generally useful to their | |
12788 | ``Library of Babel.'' The code blocks can be stored in any Org mode file and | |
12789 | then loaded into the library with @code{org-babel-lob-ingest}. | |
86fbb8ca | 12790 | |
86fbb8ca | 12791 | |
afe98dfa | 12792 | @kindex C-c C-v i |
e66ba1df | 12793 | Code blocks located in any Org mode file can be loaded into the ``Library of |
86fbb8ca | 12794 | Babel'' with the @code{org-babel-lob-ingest} function, bound to @kbd{C-c C-v |
afe98dfa | 12795 | i}. |
86fbb8ca CD |
12796 | |
12797 | @node Languages, Header arguments, Library of Babel, Working With Source Code | |
12798 | @section Languages | |
12799 | @cindex babel, languages | |
12800 | @cindex source code, languages | |
12801 | @cindex code block, languages | |
12802 | ||
12803 | Code blocks in the following languages are supported. | |
12804 | ||
12805 | @multitable @columnfractions 0.28 0.3 0.22 0.2 | |
12806 | @item @b{Language} @tab @b{Identifier} @tab @b{Language} @tab @b{Identifier} | |
ce57c2fe BG |
12807 | @item Asymptote @tab asymptote @tab Awk @tab awk |
12808 | @item Emacs Calc @tab calc @tab C @tab C | |
86fbb8ca | 12809 | @item C++ @tab C++ @tab Clojure @tab clojure |
acedf35c | 12810 | @item CSS @tab css @tab ditaa @tab ditaa |
86fbb8ca CD |
12811 | @item Graphviz @tab dot @tab Emacs Lisp @tab emacs-lisp |
12812 | @item gnuplot @tab gnuplot @tab Haskell @tab haskell | |
ce57c2fe BG |
12813 | @item Java @tab java @tab @tab |
12814 | @item Javascript @tab js @tab LaTeX @tab latex | |
12815 | @item Ledger @tab ledger @tab Lisp @tab lisp | |
12816 | @item Lilypond @tab lilypond @tab MATLAB @tab matlab | |
86fbb8ca | 12817 | @item Mscgen @tab mscgen @tab Objective Caml @tab ocaml |
e66ba1df | 12818 | @item Octave @tab octave @tab Org mode @tab org |
ce57c2fe BG |
12819 | @item Oz @tab oz @tab Perl @tab perl |
12820 | @item Plantuml @tab plantuml @tab Python @tab python | |
86fbb8ca | 12821 | @item R @tab R @tab Ruby @tab ruby |
ce57c2fe BG |
12822 | @item Sass @tab sass @tab Scheme @tab scheme |
12823 | @item GNU Screen @tab screen @tab shell @tab sh | |
12824 | @item SQL @tab sql @tab SQLite @tab sqlite | |
86fbb8ca CD |
12825 | @end multitable |
12826 | ||
12827 | Language-specific documentation is available for some languages. If | |
12828 | available, it can be found at | |
12829 | @uref{http://orgmode.org/worg/org-contrib/babel/languages}. | |
12830 | ||
12831 | The @code{org-babel-load-languages} controls which languages are enabled for | |
12832 | evaluation (by default only @code{emacs-lisp} is enabled). This variable can | |
12833 | be set using the customization interface or by adding code like the following | |
12834 | to your emacs configuration. | |
12835 | ||
12836 | @quotation | |
12837 | The following disables @code{emacs-lisp} evaluation and enables evaluation of | |
12838 | @code{R} code blocks. | |
12839 | @end quotation | |
12840 | ||
12841 | @lisp | |
12842 | (org-babel-do-load-languages | |
12843 | 'org-babel-load-languages | |
12844 | '((emacs-lisp . nil) | |
12845 | (R . t))) | |
12846 | @end lisp | |
12847 | ||
12848 | It is also possible to enable support for a language by loading the related | |
12849 | elisp file with @code{require}. | |
12850 | ||
12851 | @quotation | |
12852 | The following adds support for evaluating @code{clojure} code blocks. | |
12853 | @end quotation | |
12854 | ||
12855 | @lisp | |
12856 | (require 'ob-clojure) | |
12857 | @end lisp | |
12858 | ||
12859 | @node Header arguments, Results of evaluation, Languages, Working With Source Code | |
12860 | @section Header arguments | |
12861 | @cindex code block, header arguments | |
12862 | @cindex source code, block header arguments | |
12863 | ||
12864 | Code block functionality can be configured with header arguments. This | |
12865 | section provides an overview of the use of header arguments, and then | |
12866 | describes each header argument in detail. | |
12867 | ||
12868 | @menu | |
c0468714 GM |
12869 | * Using header arguments:: Different ways to set header arguments |
12870 | * Specific header arguments:: List of header arguments | |
86fbb8ca CD |
12871 | @end menu |
12872 | ||
12873 | @node Using header arguments, Specific header arguments, Header arguments, Header arguments | |
12874 | @subsection Using header arguments | |
12875 | ||
afe98dfa | 12876 | The values of header arguments can be set in six different ways, each more |
86fbb8ca CD |
12877 | specific (and having higher priority) than the last. |
12878 | @menu | |
12879 | * System-wide header arguments:: Set global default values | |
c0468714 | 12880 | * Language-specific header arguments:: Set default values by language |
86fbb8ca | 12881 | * Buffer-wide header arguments:: Set default values for a specific buffer |
e66ba1df | 12882 | * Header arguments in Org mode properties:: Set default values for a buffer or heading |
86fbb8ca | 12883 | * Code block specific header arguments:: The most common way to set values |
afe98dfa | 12884 | * Header arguments in function calls:: The most specific level |
86fbb8ca CD |
12885 | @end menu |
12886 | ||
12887 | ||
12888 | @node System-wide header arguments, Language-specific header arguments, Using header arguments, Using header arguments | |
12889 | @subsubheading System-wide header arguments | |
12890 | @vindex org-babel-default-header-args | |
12891 | System-wide values of header arguments can be specified by customizing the | |
12892 | @code{org-babel-default-header-args} variable: | |
12893 | ||
12894 | @example | |
12895 | :session => "none" | |
12896 | :results => "replace" | |
12897 | :exports => "code" | |
12898 | :cache => "no" | |
12899 | :noweb => "no" | |
12900 | @end example | |
12901 | ||
12902 | @c @example | |
12903 | @c org-babel-default-header-args is a variable defined in `org-babel.el'. | |
12904 | @c Its value is | |
12905 | @c ((:session . "none") | |
12906 | @c (:results . "replace") | |
12907 | @c (:exports . "code") | |
12908 | @c (:cache . "no") | |
12909 | @c (:noweb . "no")) | |
12910 | ||
12911 | ||
12912 | @c Documentation: | |
12913 | @c Default arguments to use when evaluating a code block. | |
12914 | @c @end example | |
12915 | ||
12916 | For example, the following example could be used to set the default value of | |
12917 | @code{:noweb} header arguments to @code{yes}. This would have the effect of | |
12918 | expanding @code{:noweb} references by default when evaluating source code | |
12919 | blocks. | |
12920 | ||
12921 | @lisp | |
12922 | (setq org-babel-default-header-args | |
12923 | (cons '(:noweb . "yes") | |
12924 | (assq-delete-all :noweb org-babel-default-header-args))) | |
12925 | @end lisp | |
12926 | ||
12927 | @node Language-specific header arguments, Buffer-wide header arguments, System-wide header arguments, Using header arguments | |
12928 | @subsubheading Language-specific header arguments | |
12929 | Each language can define its own set of default header arguments. See the | |
12930 | language-specific documentation available online at | |
12931 | @uref{http://orgmode.org/worg/org-contrib/babel}. | |
12932 | ||
e66ba1df | 12933 | @node Buffer-wide header arguments, Header arguments in Org mode properties, Language-specific header arguments, Using header arguments |
86fbb8ca | 12934 | @subsubheading Buffer-wide header arguments |
e66ba1df BG |
12935 | Buffer-wide header arguments may be specified as properties through the use |
12936 | of @code{#+PROPERTY:} lines placed anywhere in an Org mode file (see | |
12937 | @ref{Property syntax}). | |
86fbb8ca CD |
12938 | |
12939 | For example the following would set @code{session} to @code{*R*}, and | |
12940 | @code{results} to @code{silent} for every code block in the buffer, ensuring | |
12941 | that all execution took place in the same session, and no results would be | |
12942 | inserted into the buffer. | |
12943 | ||
12944 | @example | |
e66ba1df BG |
12945 | #+PROPERTY: session *R* |
12946 | #+PROPERTY: results silent | |
86fbb8ca CD |
12947 | @end example |
12948 | ||
e66ba1df BG |
12949 | @node Header arguments in Org mode properties, Code block specific header arguments, Buffer-wide header arguments, Using header arguments |
12950 | @subsubheading Header arguments in Org mode properties | |
86fbb8ca | 12951 | |
e66ba1df | 12952 | Header arguments are also read from Org mode properties (see @ref{Property |
ce57c2fe | 12953 | syntax}), which can be set on a buffer-wide or per-heading basis. An example |
86fbb8ca CD |
12954 | of setting a header argument for all code blocks in a buffer is |
12955 | ||
12956 | @example | |
e66ba1df | 12957 | #+PROPERTY: tangle yes |
86fbb8ca CD |
12958 | @end example |
12959 | ||
e66ba1df | 12960 | @vindex org-use-property-inheritance |
86fbb8ca | 12961 | When properties are used to set default header arguments, they are looked up |
e66ba1df BG |
12962 | with inheritance, regardless of the value of |
12963 | @code{org-use-property-inheritance}. In the following example the value of | |
12964 | the @code{:cache} header argument will default to @code{yes} in all code | |
12965 | blocks in the subtree rooted at the following heading: | |
86fbb8ca CD |
12966 | |
12967 | @example | |
12968 | * outline header | |
12969 | :PROPERTIES: | |
12970 | :cache: yes | |
12971 | :END: | |
12972 | @end example | |
12973 | ||
12974 | @kindex C-c C-x p | |
12975 | @vindex org-babel-default-header-args | |
12976 | Properties defined in this way override the properties set in | |
12977 | @code{org-babel-default-header-args}. It is convenient to use the | |
12978 | @code{org-set-property} function bound to @kbd{C-c C-x p} to set properties | |
e66ba1df | 12979 | in Org mode documents. |
86fbb8ca | 12980 | |
e66ba1df | 12981 | @node Code block specific header arguments, Header arguments in function calls, Header arguments in Org mode properties, Using header arguments |
86fbb8ca CD |
12982 | @subsubheading Code block specific header arguments |
12983 | ||
12984 | The most common way to assign values to header arguments is at the | |
12985 | code block level. This can be done by listing a sequence of header | |
e66ba1df | 12986 | arguments and their values as part of the @code{#+BEGIN_SRC} line. |
86fbb8ca CD |
12987 | Properties set in this way override both the values of |
12988 | @code{org-babel-default-header-args} and header arguments specified as | |
12989 | properties. In the following example, the @code{:results} header argument | |
12990 | is set to @code{silent}, meaning the results of execution will not be | |
12991 | inserted in the buffer, and the @code{:exports} header argument is set to | |
12992 | @code{code}, meaning only the body of the code block will be | |
e66ba1df | 12993 | preserved on export to HTML or @LaTeX{}. |
86fbb8ca CD |
12994 | |
12995 | @example | |
e66ba1df BG |
12996 | #+NAME: factorial |
12997 | #+BEGIN_SRC haskell :results silent :exports code :var n=0 | |
86fbb8ca CD |
12998 | fac 0 = 1 |
12999 | fac n = n * fac (n-1) | |
e66ba1df | 13000 | #+END_SRC |
86fbb8ca | 13001 | @end example |
e66ba1df | 13002 | Similarly, it is possible to set header arguments for inline code blocks |
86fbb8ca CD |
13003 | |
13004 | @example | |
13005 | src_haskell[:exports both]@{fac 5@} | |
13006 | @end example | |
13007 | ||
e66ba1df BG |
13008 | Code block header arguments can span multiple lines using @code{#+HEADER:} or |
13009 | @code{#+HEADERS:} lines preceding a code block or nested between the | |
13010 | @code{#+NAME:} line and the @code{#+BEGIN_SRC} line of a named code block. | |
13011 | @cindex #+HEADER: | |
13012 | @cindex #+HEADERS: | |
ce57c2fe BG |
13013 | |
13014 | Multi-line header arguments on an un-named code block: | |
13015 | @example | |
e66ba1df BG |
13016 | #+HEADERS: :var data1=1 |
13017 | #+BEGIN_SRC emacs-lisp :var data2=2 | |
ce57c2fe | 13018 | (message "data1:%S, data2:%S" data1 data2) |
e66ba1df | 13019 | #+END_SRC |
ce57c2fe BG |
13020 | |
13021 | #+results: | |
13022 | : data1:1, data2:2 | |
13023 | @end example | |
13024 | ||
13025 | Multi-line header arguments on a named code block: | |
13026 | @example | |
e66ba1df BG |
13027 | #+NAME: named-block |
13028 | #+HEADER: :var data=2 | |
13029 | #+BEGIN_SRC emacs-lisp | |
ce57c2fe | 13030 | (message "data:%S" data) |
e66ba1df | 13031 | #+END_SRC |
ce57c2fe BG |
13032 | |
13033 | #+results: named-block | |
13034 | : data:2 | |
13035 | @end example | |
13036 | ||
afe98dfa CD |
13037 | @node Header arguments in function calls, , Code block specific header arguments, Using header arguments |
13038 | @comment node-name, next, previous, up | |
13039 | @subsubheading Header arguments in function calls | |
13040 | ||
13041 | At the most specific level, header arguments for ``Library of Babel'' or | |
e66ba1df BG |
13042 | @code{#+CALL:} lines can be set as shown in the two examples below. For more |
13043 | information on the structure of @code{#+CALL:} lines see @ref{Evaluating code | |
ce57c2fe | 13044 | blocks}. |
86fbb8ca | 13045 | |
ce57c2fe | 13046 | The following will apply the @code{:exports results} header argument to the |
e66ba1df | 13047 | evaluation of the @code{#+CALL:} line. |
86fbb8ca | 13048 | @example |
e66ba1df | 13049 | #+CALL: factorial(n=5) :exports results |
86fbb8ca CD |
13050 | @end example |
13051 | ||
ce57c2fe BG |
13052 | The following will apply the @code{:session special} header argument to the |
13053 | evaluation of the @code{factorial} code block. | |
13054 | @example | |
e66ba1df | 13055 | #+CALL: factorial[:session special](n=5) |
ce57c2fe BG |
13056 | @end example |
13057 | ||
86fbb8ca CD |
13058 | @node Specific header arguments, , Using header arguments, Header arguments |
13059 | @subsection Specific header arguments | |
e66ba1df BG |
13060 | Header arguments consist of an initial colon followed by the name of the |
13061 | argument in lowercase letters. The following header arguments are defined: | |
86fbb8ca CD |
13062 | |
13063 | @menu | |
c0468714 GM |
13064 | * var:: Pass arguments to code blocks |
13065 | * results:: Specify the type of results and how they will | |
86fbb8ca | 13066 | be collected and handled |
c0468714 GM |
13067 | * file:: Specify a path for file output |
13068 | * dir:: Specify the default (possibly remote) | |
86fbb8ca | 13069 | directory for code block execution |
c0468714 GM |
13070 | * exports:: Export code and/or results |
13071 | * tangle:: Toggle tangling and specify file name | |
ce57c2fe BG |
13072 | * mkdirp:: Toggle creation of parent directories of target |
13073 | files during tangling | |
86fbb8ca CD |
13074 | * comments:: Toggle insertion of comments in tangled |
13075 | code files | |
ce57c2fe BG |
13076 | * padline:: Control insertion of padding lines in tangled |
13077 | code files | |
afe98dfa CD |
13078 | * no-expand:: Turn off variable assignment and noweb |
13079 | expansion during tangling | |
c0468714 GM |
13080 | * session:: Preserve the state of code evaluation |
13081 | * noweb:: Toggle expansion of noweb references | |
ce57c2fe | 13082 | * noweb-ref:: Specify block's noweb reference resolution target |
153ae947 | 13083 | * noweb-sep:: String used to separate noweb references |
c0468714 | 13084 | * cache:: Avoid re-evaluating unchanged code blocks |
ce57c2fe | 13085 | * sep:: Delimiter for writing tabular results outside Org |
c0468714 GM |
13086 | * hlines:: Handle horizontal lines in tables |
13087 | * colnames:: Handle column names in tables | |
13088 | * rownames:: Handle row names in tables | |
13089 | * shebang:: Make tangled files executable | |
86fbb8ca CD |
13090 | * eval:: Limit evaluation of specific code blocks |
13091 | @end menu | |
13092 | ||
ce57c2fe BG |
13093 | Additional header arguments are defined on a language-specific basis, see |
13094 | @ref{Languages}. | |
13095 | ||
86fbb8ca CD |
13096 | @node var, results, Specific header arguments, Specific header arguments |
13097 | @subsubsection @code{:var} | |
13098 | The @code{:var} header argument is used to pass arguments to code blocks. | |
13099 | The specifics of how arguments are included in a code block vary by language; | |
ce57c2fe | 13100 | these are addressed in the language-specific documentation. However, the |
e66ba1df BG |
13101 | syntax used to specify arguments is the same across all languages. In every |
13102 | case, variables require a default value when they are declared. | |
13103 | ||
13104 | The values passed to arguments can either be literal values, references, or | |
13105 | Emacs Lisp code (see @ref{var, Emacs Lisp evaluation of variables}). References | |
13106 | include anything in the Org mode file that takes a @code{#+NAME:}, | |
13107 | @code{#+TBLNAME:}, or @code{#+RESULTS:} line. This includes tables, lists, | |
13108 | @code{#+BEGIN_EXAMPLE} blocks, other code blocks, and the results of other | |
13109 | code blocks. | |
86fbb8ca | 13110 | |
e66ba1df BG |
13111 | Argument values can be indexed in a manner similar to arrays (see @ref{var, |
13112 | Indexable variable values}). | |
86fbb8ca CD |
13113 | |
13114 | The following syntax is used to pass arguments to code blocks using the | |
13115 | @code{:var} header argument. | |
13116 | ||
13117 | @example | |
13118 | :var name=assign | |
13119 | @end example | |
13120 | ||
e66ba1df BG |
13121 | The argument, @code{assign}, can either be a literal value, such as a string |
13122 | @samp{"string"} or a number @samp{9}, or a reference to a table, a list, a | |
13123 | literal example, another code block (with or without arguments), or the | |
13124 | results of evaluating another code block. | |
86fbb8ca | 13125 | |
e66ba1df BG |
13126 | Here are examples of passing values by reference: |
13127 | ||
13128 | @table @dfn | |
86fbb8ca | 13129 | |
e66ba1df BG |
13130 | @item table |
13131 | an Org mode table named with either a @code{#+NAME:} or @code{#+TBLNAME:} line | |
86fbb8ca | 13132 | @example |
e66ba1df | 13133 | #+TBLNAME: example-table |
86fbb8ca CD |
13134 | | 1 | |
13135 | | 2 | | |
13136 | | 3 | | |
13137 | | 4 | | |
13138 | ||
e66ba1df BG |
13139 | #+NAME: table-length |
13140 | #+BEGIN_SRC emacs-lisp :var table=example-table | |
86fbb8ca | 13141 | (length table) |
e66ba1df | 13142 | #+END_SRC |
86fbb8ca CD |
13143 | |
13144 | #+results: table-length | |
13145 | : 4 | |
13146 | @end example | |
13147 | ||
e66ba1df BG |
13148 | @item list |
13149 | a simple list named with a @code{#+NAME:} line (note that nesting is not | |
13150 | carried through to the source code block) | |
86fbb8ca CD |
13151 | |
13152 | @example | |
e66ba1df BG |
13153 | #+NAME: example-list |
13154 | - simple | |
13155 | - not | |
13156 | - nested | |
13157 | - list | |
13158 | ||
13159 | #+BEGIN_SRC emacs-lisp :var x=example-list | |
13160 | (print x) | |
13161 | #+END_SRC | |
13162 | ||
13163 | #+results: | |
13164 | | simple | list | | |
13165 | @end example | |
13166 | ||
13167 | @item code block without arguments | |
13168 | a code block name (from the example above), as assigned by @code{#+NAME:}, | |
13169 | optionally followed by parentheses | |
13170 | ||
13171 | @example | |
13172 | #+BEGIN_SRC emacs-lisp :var length=table-length() | |
86fbb8ca | 13173 | (* 2 length) |
e66ba1df | 13174 | #+END_SRC |
86fbb8ca CD |
13175 | |
13176 | #+results: | |
13177 | : 8 | |
13178 | @end example | |
13179 | ||
e66ba1df BG |
13180 | @item code block with arguments |
13181 | a code block name, as assigned by @code{#+NAME:}, followed by parentheses and | |
13182 | optional arguments passed within the parentheses following the | |
13183 | code block name using standard function call syntax | |
86fbb8ca CD |
13184 | |
13185 | @example | |
e66ba1df BG |
13186 | #+NAME: double |
13187 | #+BEGIN_SRC emacs-lisp :var input=8 | |
86fbb8ca | 13188 | (* 2 input) |
e66ba1df | 13189 | #+END_SRC |
86fbb8ca CD |
13190 | |
13191 | #+results: double | |
13192 | : 16 | |
13193 | ||
e66ba1df BG |
13194 | #+NAME: squared |
13195 | #+BEGIN_SRC emacs-lisp :var input=double(input=1) | |
86fbb8ca | 13196 | (* input input) |
e66ba1df | 13197 | #+END_SRC |
86fbb8ca CD |
13198 | |
13199 | #+results: squared | |
13200 | : 4 | |
13201 | @end example | |
e66ba1df BG |
13202 | |
13203 | @item literal example | |
13204 | a literal example block named with a @code{#+NAME:} line | |
13205 | ||
13206 | @example | |
13207 | #+NAME: literal-example | |
13208 | #+BEGIN_EXAMPLE | |
13209 | A literal example | |
13210 | on two lines | |
13211 | #+END_EXAMPLE | |
13212 | ||
13213 | #+NAME: read-literal-example | |
13214 | #+BEGIN_SRC emacs-lisp :var x=literal-example | |
13215 | (concatenate 'string x " for you.") | |
13216 | #+END_SRC | |
13217 | ||
13218 | #+results: read-literal-example | |
13219 | : A literal example | |
13220 | : on two lines for you. | |
13221 | ||
13222 | @end example | |
13223 | ||
13224 | @end table | |
86fbb8ca CD |
13225 | |
13226 | @subsubheading Alternate argument syntax | |
13227 | It is also possible to specify arguments in a potentially more natural way | |
e66ba1df BG |
13228 | using the @code{#+NAME:} line of a code block. As in the following |
13229 | example, arguments can be packed inside of parentheses, separated by commas, | |
86fbb8ca CD |
13230 | following the source name. |
13231 | ||
13232 | @example | |
e66ba1df BG |
13233 | #+NAME: double(input=0, x=2) |
13234 | #+BEGIN_SRC emacs-lisp | |
86fbb8ca | 13235 | (* 2 (+ input x)) |
e66ba1df | 13236 | #+END_SRC |
86fbb8ca CD |
13237 | @end example |
13238 | ||
13239 | @subsubheading Indexable variable values | |
13240 | It is possible to reference portions of variable values by ``indexing'' into | |
13241 | the variables. Indexes are 0 based with negative values counting back from | |
13242 | the end. If an index is separated by @code{,}s then each subsequent section | |
ce57c2fe BG |
13243 | will index into the next deepest nesting or dimension of the value. Note |
13244 | that this indexing occurs @emph{before} other table related header arguments | |
13245 | like @code{:hlines}, @code{:colnames} and @code{:rownames} are applied. The | |
86fbb8ca CD |
13246 | following example assigns the last cell of the first row the table |
13247 | @code{example-table} to the variable @code{data}: | |
13248 | ||
13249 | @example | |
e66ba1df | 13250 | #+NAME: example-table |
86fbb8ca CD |
13251 | | 1 | a | |
13252 | | 2 | b | | |
13253 | | 3 | c | | |
13254 | | 4 | d | | |
13255 | ||
e66ba1df | 13256 | #+BEGIN_SRC emacs-lisp :var data=example-table[0,-1] |
86fbb8ca | 13257 | data |
e66ba1df | 13258 | #+END_SRC |
86fbb8ca CD |
13259 | |
13260 | #+results: | |
13261 | : a | |
13262 | @end example | |
13263 | ||
13264 | Ranges of variable values can be referenced using two integers separated by a | |
13265 | @code{:}, in which case the entire inclusive range is referenced. For | |
13266 | example the following assigns the middle three rows of @code{example-table} | |
13267 | to @code{data}. | |
13268 | ||
13269 | @example | |
e66ba1df | 13270 | #+NAME: example-table |
86fbb8ca CD |
13271 | | 1 | a | |
13272 | | 2 | b | | |
13273 | | 3 | c | | |
13274 | | 4 | d | | |
13275 | | 5 | 3 | | |
13276 | ||
e66ba1df | 13277 | #+BEGIN_SRC emacs-lisp :var data=example-table[1:3] |
86fbb8ca | 13278 | data |
e66ba1df | 13279 | #+END_SRC |
86fbb8ca CD |
13280 | |
13281 | #+results: | |
13282 | | 2 | b | | |
13283 | | 3 | c | | |
13284 | | 4 | d | | |
13285 | @end example | |
13286 | ||
13287 | Additionally, an empty index, or the single character @code{*}, are both | |
13288 | interpreted to mean the entire range and as such are equivalent to | |
13289 | @code{0:-1}, as shown in the following example in which the entire first | |
13290 | column is referenced. | |
13291 | ||
13292 | @example | |
e66ba1df | 13293 | #+NAME: example-table |
86fbb8ca CD |
13294 | | 1 | a | |
13295 | | 2 | b | | |
13296 | | 3 | c | | |
13297 | | 4 | d | | |
13298 | ||
e66ba1df | 13299 | #+BEGIN_SRC emacs-lisp :var data=example-table[,0] |
86fbb8ca | 13300 | data |
e66ba1df | 13301 | #+END_SRC |
86fbb8ca CD |
13302 | |
13303 | #+results: | |
13304 | | 1 | 2 | 3 | 4 | | |
13305 | @end example | |
13306 | ||
13307 | It is possible to index into the results of code blocks as well as tables. | |
13308 | Any number of dimensions can be indexed. Dimensions are separated from one | |
13309 | another by commas, as shown in the following example. | |
13310 | ||
13311 | @example | |
e66ba1df BG |
13312 | #+NAME: 3D |
13313 | #+BEGIN_SRC emacs-lisp | |
86fbb8ca CD |
13314 | '(((1 2 3) (4 5 6) (7 8 9)) |
13315 | ((10 11 12) (13 14 15) (16 17 18)) | |
13316 | ((19 20 21) (22 23 24) (25 26 27))) | |
e66ba1df | 13317 | #+END_SRC |
86fbb8ca | 13318 | |
e66ba1df | 13319 | #+BEGIN_SRC emacs-lisp :var data=3D[1,,1] |
86fbb8ca | 13320 | data |
e66ba1df | 13321 | #+END_SRC |
86fbb8ca CD |
13322 | |
13323 | #+results: | |
13324 | | 11 | 14 | 17 | | |
13325 | @end example | |
13326 | ||
ce57c2fe BG |
13327 | @subsubheading Emacs Lisp evaluation of variables |
13328 | ||
13329 | Emacs lisp code can be used to initialize variable values. When a variable | |
e66ba1df BG |
13330 | value starts with @code{(}, @code{[}, @code{'} or @code{`} it will be |
13331 | evaluated as Emacs Lisp and the result of the evaluation will be assigned as | |
13332 | the variable value. The following example demonstrates use of this | |
13333 | evaluation to reliably pass the file-name of the Org mode buffer to a code | |
13334 | block---note that evaluation of header arguments is guaranteed to take place | |
13335 | in the original Org mode file, while there is no such guarantee for | |
13336 | evaluation of the code block body. | |
ce57c2fe BG |
13337 | |
13338 | @example | |
e66ba1df | 13339 | #+BEGIN_SRC sh :var filename=(buffer-file-name) :exports both |
ce57c2fe | 13340 | wc -w $filename |
e66ba1df | 13341 | #+END_SRC |
ce57c2fe BG |
13342 | @end example |
13343 | ||
13344 | Note that values read from tables and lists will not be evaluated as | |
13345 | Emacs Lisp, as shown in the following example. | |
13346 | ||
13347 | @example | |
e66ba1df | 13348 | #+NAME: table |
ce57c2fe BG |
13349 | | (a b c) | |
13350 | ||
e66ba1df BG |
13351 | #+HEADERS: :var data=table[0,0] |
13352 | #+BEGIN_SRC perl | |
ce57c2fe | 13353 | $data |
e66ba1df | 13354 | #+END_SRC |
ce57c2fe BG |
13355 | |
13356 | #+results: | |
13357 | : (a b c) | |
13358 | @end example | |
13359 | ||
86fbb8ca CD |
13360 | @node results, file, var, Specific header arguments |
13361 | @subsubsection @code{:results} | |
13362 | ||
acedf35c CD |
13363 | There are three classes of @code{:results} header argument. Only one option |
13364 | per class may be supplied per code block. | |
86fbb8ca CD |
13365 | |
13366 | @itemize @bullet | |
13367 | @item | |
13368 | @b{collection} header arguments specify how the results should be collected | |
13369 | from the code block | |
13370 | @item | |
13371 | @b{type} header arguments specify what type of result the code block will | |
13372 | return---which has implications for how they will be inserted into the | |
e66ba1df | 13373 | Org mode buffer |
86fbb8ca CD |
13374 | @item |
13375 | @b{handling} header arguments specify how the results of evaluating the code | |
13376 | block should be handled. | |
13377 | @end itemize | |
13378 | ||
13379 | @subsubheading Collection | |
13380 | The following options are mutually exclusive, and specify how the results | |
13381 | should be collected from the code block. | |
13382 | ||
13383 | @itemize @bullet | |
13384 | @item @code{value} | |
13385 | This is the default. The result is the value of the last statement in the | |
13386 | code block. This header argument places the evaluation in functional | |
acedf35c | 13387 | mode. Note that in some languages, e.g., Python, use of this result type |
86fbb8ca | 13388 | requires that a @code{return} statement be included in the body of the source |
ce57c2fe | 13389 | code block. E.g., @code{:results value}. |
86fbb8ca CD |
13390 | @item @code{output} |
13391 | The result is the collection of everything printed to STDOUT during the | |
13392 | execution of the code block. This header argument places the | |
13393 | evaluation in scripting mode. E.g., @code{:results output}. | |
13394 | @end itemize | |
13395 | ||
13396 | @subsubheading Type | |
13397 | ||
13398 | The following options are mutually exclusive and specify what type of results | |
13399 | the code block will return. By default, results are inserted as either a | |
13400 | table or scalar depending on their value. | |
13401 | ||
13402 | @itemize @bullet | |
13403 | @item @code{table}, @code{vector} | |
e66ba1df | 13404 | The results should be interpreted as an Org mode table. If a single value is |
86fbb8ca CD |
13405 | returned, it will be converted into a table with one row and one column. |
13406 | E.g., @code{:results value table}. | |
acedf35c | 13407 | @item @code{list} |
e66ba1df | 13408 | The results should be interpreted as an Org mode list. If a single scalar |
acedf35c | 13409 | value is returned it will be converted into a list with only one element. |
86fbb8ca CD |
13410 | @item @code{scalar}, @code{verbatim} |
13411 | The results should be interpreted literally---they will not be | |
e66ba1df | 13412 | converted into a table. The results will be inserted into the Org mode |
86fbb8ca CD |
13413 | buffer as quoted text. E.g., @code{:results value verbatim}. |
13414 | @item @code{file} | |
13415 | The results will be interpreted as the path to a file, and will be inserted | |
e66ba1df | 13416 | into the Org mode buffer as a file link. E.g., @code{:results value file}. |
86fbb8ca | 13417 | @item @code{raw}, @code{org} |
e66ba1df | 13418 | The results are interpreted as raw Org mode code and are inserted directly |
86fbb8ca | 13419 | into the buffer. If the results look like a table they will be aligned as |
e66ba1df | 13420 | such by Org mode. E.g., @code{:results value raw}. |
86fbb8ca CD |
13421 | @item @code{html} |
13422 | Results are assumed to be HTML and will be enclosed in a @code{begin_html} | |
13423 | block. E.g., @code{:results value html}. | |
13424 | @item @code{latex} | |
e66ba1df | 13425 | Results assumed to be @LaTeX{} and are enclosed in a @code{begin_latex} block. |
86fbb8ca CD |
13426 | E.g., @code{:results value latex}. |
13427 | @item @code{code} | |
fac916bf | 13428 | Result are assumed to be parsable code and are enclosed in a code block. |
86fbb8ca CD |
13429 | E.g., @code{:results value code}. |
13430 | @item @code{pp} | |
13431 | The result is converted to pretty-printed code and is enclosed in a code | |
acedf35c | 13432 | block. This option currently supports Emacs Lisp, Python, and Ruby. E.g., |
86fbb8ca | 13433 | @code{:results value pp}. |
ce57c2fe | 13434 | @item @code{wrap} |
153ae947 | 13435 | The result is wrapped in a RESULTS drawer. This can be useful for |
ce57c2fe | 13436 | inserting @code{raw} or @code{org} syntax results in such a way that their |
153ae947 | 13437 | extent is known and they can be automatically removed or replaced. |
86fbb8ca CD |
13438 | @end itemize |
13439 | ||
13440 | @subsubheading Handling | |
13441 | The following results options indicate what happens with the | |
13442 | results once they are collected. | |
13443 | ||
13444 | @itemize @bullet | |
13445 | @item @code{silent} | |
13446 | The results will be echoed in the minibuffer but will not be inserted into | |
e66ba1df | 13447 | the Org mode buffer. E.g., @code{:results output silent}. |
86fbb8ca CD |
13448 | @item @code{replace} |
13449 | The default value. Any existing results will be removed, and the new results | |
e66ba1df | 13450 | will be inserted into the Org mode buffer in their place. E.g., |
86fbb8ca CD |
13451 | @code{:results output replace}. |
13452 | @item @code{append} | |
13453 | If there are pre-existing results of the code block then the new results will | |
13454 | be appended to the existing results. Otherwise the new results will be | |
13455 | inserted as with @code{replace}. | |
13456 | @item @code{prepend} | |
13457 | If there are pre-existing results of the code block then the new results will | |
13458 | be prepended to the existing results. Otherwise the new results will be | |
13459 | inserted as with @code{replace}. | |
13460 | @end itemize | |
13461 | ||
13462 | @node file, dir, results, Specific header arguments | |
13463 | @subsubsection @code{:file} | |
13464 | ||
ce57c2fe | 13465 | The header argument @code{:file} is used to specify an external file in which |
e66ba1df | 13466 | to save code block results. After code block evaluation an Org mode style |
ce57c2fe | 13467 | @code{[[file:]]} link (see @ref{Link format}) to the file will be inserted |
e66ba1df | 13468 | into the Org mode buffer. Some languages including R, gnuplot, dot, and |
ce57c2fe BG |
13469 | ditaa provide special handling of the @code{:file} header argument |
13470 | automatically wrapping the code block body in the boilerplate code required | |
13471 | to save output to the specified file. This is often useful for saving | |
13472 | graphical output of a code block to the specified file. | |
86fbb8ca | 13473 | |
ce57c2fe BG |
13474 | The argument to @code{:file} should be either a string specifying the path to |
13475 | a file, or a list of two strings in which case the first element of the list | |
13476 | should be the path to a file and the second a description for the link. | |
86fbb8ca CD |
13477 | |
13478 | @node dir, exports, file, Specific header arguments | |
13479 | @subsubsection @code{:dir} and remote execution | |
13480 | ||
13481 | While the @code{:file} header argument can be used to specify the path to the | |
13482 | output file, @code{:dir} specifies the default directory during code block | |
ce57c2fe BG |
13483 | execution. If it is absent, then the directory associated with the current |
13484 | buffer is used. In other words, supplying @code{:dir path} temporarily has | |
86fbb8ca | 13485 | the same effect as changing the current directory with @kbd{M-x cd path}, and |
ce57c2fe | 13486 | then not supplying @code{:dir}. Under the surface, @code{:dir} simply sets |
86fbb8ca CD |
13487 | the value of the Emacs variable @code{default-directory}. |
13488 | ||
13489 | When using @code{:dir}, you should supply a relative path for file output | |
ce57c2fe | 13490 | (e.g.@: @code{:file myfile.jpg} or @code{:file results/myfile.jpg}) in which |
86fbb8ca CD |
13491 | case that path will be interpreted relative to the default directory. |
13492 | ||
acedf35c CD |
13493 | In other words, if you want your plot to go into a folder called @file{Work} |
13494 | in your home directory, you could use | |
86fbb8ca CD |
13495 | |
13496 | @example | |
e66ba1df | 13497 | #+BEGIN_SRC R :file myplot.png :dir ~/Work |
86fbb8ca | 13498 | matplot(matrix(rnorm(100), 10), type="l") |
e66ba1df | 13499 | #+END_SRC |
86fbb8ca CD |
13500 | @end example |
13501 | ||
13502 | @subsubheading Remote execution | |
13503 | A directory on a remote machine can be specified using tramp file syntax, in | |
ce57c2fe | 13504 | which case the code will be evaluated on the remote machine. An example is |
86fbb8ca CD |
13505 | |
13506 | @example | |
e66ba1df | 13507 | #+BEGIN_SRC R :file plot.png :dir /dand@@yakuba.princeton.edu: |
86fbb8ca | 13508 | plot(1:10, main=system("hostname", intern=TRUE)) |
e66ba1df | 13509 | #+END_SRC |
86fbb8ca CD |
13510 | @end example |
13511 | ||
e66ba1df | 13512 | Text results will be returned to the local Org mode buffer as usual, and file |
86fbb8ca | 13513 | output will be created on the remote machine with relative paths interpreted |
e66ba1df | 13514 | relative to the remote directory. An Org mode link to the remote file will be |
86fbb8ca CD |
13515 | created. |
13516 | ||
13517 | So, in the above example a plot will be created on the remote machine, | |
13518 | and a link of the following form will be inserted in the org buffer: | |
13519 | ||
13520 | @example | |
13521 | [[file:/scp:dand@@yakuba.princeton.edu:/home/dand/plot.png][plot.png]] | |
13522 | @end example | |
13523 | ||
13524 | Most of this functionality follows immediately from the fact that @code{:dir} | |
13525 | sets the value of the Emacs variable @code{default-directory}, thanks to | |
ce57c2fe | 13526 | tramp. Those using XEmacs, or GNU Emacs prior to version 23 may need to |
acedf35c | 13527 | install tramp separately in order for these features to work correctly. |
86fbb8ca CD |
13528 | |
13529 | @subsubheading Further points | |
13530 | ||
13531 | @itemize @bullet | |
13532 | @item | |
13533 | If @code{:dir} is used in conjunction with @code{:session}, although it will | |
13534 | determine the starting directory for a new session as expected, no attempt is | |
13535 | currently made to alter the directory associated with an existing session. | |
13536 | @item | |
13537 | @code{:dir} should typically not be used to create files during export with | |
ce57c2fe | 13538 | @code{:exports results} or @code{:exports both}. The reason is that, in order |
86fbb8ca | 13539 | to retain portability of exported material between machines, during export |
e66ba1df | 13540 | links inserted into the buffer will @emph{not} be expanded against @code{default |
ce57c2fe | 13541 | directory}. Therefore, if @code{default-directory} is altered using |
86fbb8ca CD |
13542 | @code{:dir}, it is probable that the file will be created in a location to |
13543 | which the link does not point. | |
13544 | @end itemize | |
13545 | ||
13546 | @node exports, tangle, dir, Specific header arguments | |
13547 | @subsubsection @code{:exports} | |
13548 | ||
13549 | The @code{:exports} header argument specifies what should be included in HTML | |
e66ba1df | 13550 | or @LaTeX{} exports of the Org mode file. |
86fbb8ca CD |
13551 | |
13552 | @itemize @bullet | |
13553 | @item @code{code} | |
13554 | The default. The body of code is included into the exported file. E.g., | |
13555 | @code{:exports code}. | |
13556 | @item @code{results} | |
ce57c2fe | 13557 | The result of evaluating the code is included in the exported file. E.g., |
86fbb8ca CD |
13558 | @code{:exports results}. |
13559 | @item @code{both} | |
ce57c2fe | 13560 | Both the code and results are included in the exported file. E.g., |
86fbb8ca CD |
13561 | @code{:exports both}. |
13562 | @item @code{none} | |
13563 | Nothing is included in the exported file. E.g., @code{:exports none}. | |
13564 | @end itemize | |
13565 | ||
ce57c2fe | 13566 | @node tangle, mkdirp, exports, Specific header arguments |
86fbb8ca CD |
13567 | @subsubsection @code{:tangle} |
13568 | ||
13569 | The @code{:tangle} header argument specifies whether or not the code | |
13570 | block should be included in tangled extraction of source code files. | |
13571 | ||
13572 | @itemize @bullet | |
acedf35c | 13573 | @item @code{tangle} |
ce57c2fe | 13574 | The code block is exported to a source code file named after the full path |
e66ba1df | 13575 | (including the directory) and file name (w/o extension) of the Org mode file. |
ce57c2fe | 13576 | E.g., @code{:tangle yes}. |
86fbb8ca CD |
13577 | @item @code{no} |
13578 | The default. The code block is not exported to a source code file. | |
13579 | E.g., @code{:tangle no}. | |
13580 | @item other | |
13581 | Any other string passed to the @code{:tangle} header argument is interpreted | |
e66ba1df | 13582 | as a path (directory and file name relative to the directory of the Org mode |
ce57c2fe | 13583 | file) to which the block will be exported. E.g., @code{:tangle path}. |
86fbb8ca CD |
13584 | @end itemize |
13585 | ||
ce57c2fe BG |
13586 | @node mkdirp, comments, tangle, Specific header arguments |
13587 | @subsubsection @code{:mkdirp} | |
13588 | ||
13589 | The @code{:mkdirp} header argument can be used to create parent directories | |
13590 | of tangled files when missing. This can be set to @code{yes} to enable | |
13591 | directory creation or to @code{no} to inhibit directory creation. | |
13592 | ||
13593 | @node comments, padline, mkdirp, Specific header arguments | |
86fbb8ca CD |
13594 | @subsubsection @code{:comments} |
13595 | By default code blocks are tangled to source-code files without any insertion | |
13596 | of comments beyond those which may already exist in the body of the code | |
afe98dfa CD |
13597 | block. The @code{:comments} header argument can be set as follows to control |
13598 | the insertion of extra comments into the tangled code file. | |
13599 | ||
13600 | @itemize @bullet | |
13601 | @item @code{no} | |
13602 | The default. No extra comments are inserted during tangling. | |
13603 | @item @code{link} | |
13604 | The code block is wrapped in comments which contain pointers back to the | |
13605 | original Org file from which the code was tangled. | |
13606 | @item @code{yes} | |
13607 | A synonym for ``link'' to maintain backwards compatibility. | |
13608 | @item @code{org} | |
e66ba1df | 13609 | Include text from the Org mode file as a comment. |
afe98dfa CD |
13610 | |
13611 | The text is picked from the leading context of the tangled code and is | |
13612 | limited by the nearest headline or source block as the case may be. | |
13613 | @item @code{both} | |
13614 | Turns on both the ``link'' and ``org'' comment options. | |
ce57c2fe BG |
13615 | @item @code{noweb} |
13616 | Turns on the ``link'' comment option, and additionally wraps expanded noweb | |
13617 | references in the code block body in link comments. | |
afe98dfa | 13618 | @end itemize |
86fbb8ca | 13619 | |
ce57c2fe BG |
13620 | @node padline, no-expand, comments, Specific header arguments |
13621 | @subsubsection @code{:padline} | |
13622 | Control in insertion of padding lines around code block bodies in tangled | |
13623 | code files. The default value is @code{yes} which results in insertion of | |
13624 | newlines before and after each tangled code block. The following arguments | |
13625 | are accepted. | |
13626 | ||
13627 | @itemize @bullet | |
13628 | @item @code{yes} | |
13629 | Insert newlines before and after each code block body in tangled code files. | |
13630 | @item @code{no} | |
13631 | Do not insert any newline padding in tangled output. | |
13632 | @end itemize | |
13633 | ||
13634 | @node no-expand, session, padline, Specific header arguments | |
86fbb8ca CD |
13635 | @subsubsection @code{:no-expand} |
13636 | ||
13637 | By default, code blocks are expanded with @code{org-babel-expand-src-block} | |
13638 | during tangling. This has the effect of assigning values to variables | |
13639 | specified with @code{:var} (see @ref{var}), and of replacing ``noweb'' | |
13640 | references (see @ref{Noweb reference syntax}) with their targets. The | |
13641 | @code{:no-expand} header argument can be used to turn off this behavior. | |
13642 | ||
13643 | @node session, noweb, no-expand, Specific header arguments | |
13644 | @subsubsection @code{:session} | |
13645 | ||
13646 | The @code{:session} header argument starts a session for an interpreted | |
13647 | language where state is preserved. | |
13648 | ||
13649 | By default, a session is not started. | |
13650 | ||
13651 | A string passed to the @code{:session} header argument will give the session | |
13652 | a name. This makes it possible to run concurrent sessions for each | |
13653 | interpreted language. | |
13654 | ||
ce57c2fe | 13655 | @node noweb, noweb-ref, session, Specific header arguments |
86fbb8ca CD |
13656 | @subsubsection @code{:noweb} |
13657 | ||
13658 | The @code{:noweb} header argument controls expansion of ``noweb'' style (see | |
13659 | @ref{Noweb reference syntax}) references in a code block. This header | |
ce57c2fe | 13660 | argument can have one of three values: @code{yes}, @code{no}, or @code{tangle}. |
86fbb8ca CD |
13661 | |
13662 | @itemize @bullet | |
afe98dfa CD |
13663 | @item @code{yes} |
13664 | All ``noweb'' syntax references in the body of the code block will be | |
13665 | expanded before the block is evaluated, tangled or exported. | |
86fbb8ca | 13666 | @item @code{no} |
153ae947 BG |
13667 | The default. No ``noweb'' syntax specific action is taken when the code |
13668 | block is evaluated, tangled or exported. | |
acedf35c | 13669 | @item @code{tangle} |
86fbb8ca | 13670 | All ``noweb'' syntax references in the body of the code block will be |
afe98dfa CD |
13671 | expanded before the block is tangled, however ``noweb'' references will not |
13672 | be expanded when the block is evaluated or exported. | |
86fbb8ca CD |
13673 | @end itemize |
13674 | ||
13675 | @subsubheading Noweb prefix lines | |
13676 | Noweb insertions are now placed behind the line prefix of the | |
13677 | @code{<<reference>>}. | |
13678 | This behavior is illustrated in the following example. Because the | |
13679 | @code{<<example>>} noweb reference appears behind the SQL comment syntax, | |
13680 | each line of the expanded noweb reference will be commented. | |
13681 | ||
13682 | This code block: | |
13683 | ||
13684 | @example | |
13685 | -- <<example>> | |
13686 | @end example | |
13687 | ||
13688 | ||
13689 | expands to: | |
13690 | ||
13691 | @example | |
13692 | -- this is the | |
13693 | -- multi-line body of example | |
13694 | @end example | |
13695 | ||
13696 | Note that noweb replacement text that does not contain any newlines will not | |
13697 | be affected by this change, so it is still possible to use inline noweb | |
13698 | references. | |
13699 | ||
153ae947 | 13700 | @node noweb-ref, noweb-sep, noweb, Specific header arguments |
ce57c2fe BG |
13701 | @subsubsection @code{:noweb-ref} |
13702 | When expanding ``noweb'' style references the bodies of all code block with | |
13703 | @emph{either} a block name matching the reference name @emph{or} a | |
13704 | @code{:noweb-ref} header argument matching the reference name will be | |
13705 | concatenated together to form the replacement text. | |
13706 | ||
13707 | By setting this header argument at the sub-tree or file level, simple code | |
13708 | block concatenation may be achieved. For example, when tangling the | |
e66ba1df BG |
13709 | following Org mode file, the bodies of code blocks will be concatenated into |
13710 | the resulting pure code file@footnote{(The example needs property inheritance | |
13711 | to be turned on for the @code{noweb-ref} property, see @ref{Property | |
13712 | inheritance}).}. | |
ce57c2fe BG |
13713 | |
13714 | @example | |
e66ba1df | 13715 | #+BEGIN_SRC sh :tangle yes :noweb yes :shebang #!/bin/sh |
ce57c2fe | 13716 | <<fullest-disk>> |
e66ba1df | 13717 | #+END_SRC |
ce57c2fe BG |
13718 | * the mount point of the fullest disk |
13719 | :PROPERTIES: | |
13720 | :noweb-ref: fullest-disk | |
13721 | :END: | |
13722 | ||
13723 | ** query all mounted disks | |
e66ba1df | 13724 | #+BEGIN_SRC sh |
ce57c2fe | 13725 | df \ |
e66ba1df | 13726 | #+END_SRC |
ce57c2fe BG |
13727 | |
13728 | ** strip the header row | |
e66ba1df | 13729 | #+BEGIN_SRC sh |
ce57c2fe | 13730 | |sed '1d' \ |
e66ba1df | 13731 | #+END_SRC |
ce57c2fe BG |
13732 | |
13733 | ** sort by the percent full | |
e66ba1df | 13734 | #+BEGIN_SRC sh |
ce57c2fe | 13735 | |awk '@{print $5 " " $6@}'|sort -n |tail -1 \ |
e66ba1df | 13736 | #+END_SRC |
ce57c2fe BG |
13737 | |
13738 | ** extract the mount point | |
e66ba1df | 13739 | #+BEGIN_SRC sh |
ce57c2fe | 13740 | |awk '@{print $2@}' |
e66ba1df | 13741 | #+END_SRC |
ce57c2fe BG |
13742 | @end example |
13743 | ||
153ae947 BG |
13744 | The @code{:noweb-sep} (see @ref{noweb-sep}) header argument holds the string |
13745 | used to separate accumulate noweb references like those above. By default a | |
13746 | newline is used. | |
13747 | ||
13748 | @node noweb-sep, cache, noweb-ref, Specific header arguments | |
13749 | @subsubsection @code{:noweb-sep} | |
13750 | ||
13751 | The @code{:noweb-sep} header argument holds the string used to separate | |
13752 | accumulate noweb references (see @ref{noweb-ref}). By default a newline is | |
13753 | used. | |
13754 | ||
13755 | @node cache, sep, noweb-sep, Specific header arguments | |
86fbb8ca CD |
13756 | @subsubsection @code{:cache} |
13757 | ||
13758 | The @code{:cache} header argument controls the use of in-buffer caching of | |
13759 | the results of evaluating code blocks. It can be used to avoid re-evaluating | |
153ae947 BG |
13760 | unchanged code blocks. Note that the @code{:cache} header argument will not |
13761 | attempt to cache results when the @code{:session} header argument is used, | |
13762 | because the results of the code block execution may be stored in the session | |
13763 | outside of the Org-mode buffer. The @code{:cache} header argument can have | |
13764 | one of two values: @code{yes} or @code{no}. | |
86fbb8ca CD |
13765 | |
13766 | @itemize @bullet | |
13767 | @item @code{no} | |
13768 | The default. No caching takes place, and the code block will be evaluated | |
13769 | every time it is called. | |
13770 | @item @code{yes} | |
acedf35c | 13771 | Every time the code block is run a SHA1 hash of the code and arguments |
86fbb8ca CD |
13772 | passed to the block will be generated. This hash is packed into the |
13773 | @code{#+results:} line and will be checked on subsequent | |
13774 | executions of the code block. If the code block has not | |
13775 | changed since the last time it was evaluated, it will not be re-evaluated. | |
13776 | @end itemize | |
13777 | ||
ce57c2fe BG |
13778 | Code block caches notice if the value of a variable argument |
13779 | to the code block has changed. If this is the case, the cache is | |
13780 | invalidated and the code block is re-run. In the following example, | |
13781 | @code{caller} will not be re-run unless the results of @code{random} have | |
13782 | changed since it was last run. | |
13783 | ||
13784 | @example | |
e66ba1df BG |
13785 | #+NAME: random |
13786 | #+BEGIN_SRC R :cache yes | |
ce57c2fe | 13787 | runif(1) |
e66ba1df | 13788 | #+END_SRC |
ce57c2fe BG |
13789 | |
13790 | #+results[a2a72cd647ad44515fab62e144796432793d68e1]: random | |
13791 | 0.4659510825295 | |
13792 | ||
e66ba1df BG |
13793 | #+NAME: caller |
13794 | #+BEGIN_SRC emacs-lisp :var x=random :cache yes | |
ce57c2fe | 13795 | x |
e66ba1df | 13796 | #+END_SRC |
ce57c2fe BG |
13797 | |
13798 | #+results[bec9c8724e397d5df3b696502df3ed7892fc4f5f]: caller | |
13799 | 0.254227238707244 | |
13800 | @end example | |
13801 | ||
13802 | @node sep, hlines, cache, Specific header arguments | |
13803 | @subsubsection @code{:sep} | |
13804 | ||
13805 | The @code{:sep} header argument can be used to control the delimiter used | |
e66ba1df | 13806 | when writing tabular results out to files external to Org mode. This is used |
ce57c2fe BG |
13807 | either when opening tabular results of a code block by calling the |
13808 | @code{org-open-at-point} function bound to @kbd{C-c C-o} on the code block, | |
13809 | or when writing code block results to an external file (see @ref{file}) | |
13810 | header argument. | |
13811 | ||
13812 | By default, when @code{:sep} is not specified output tables are tab | |
13813 | delimited. | |
13814 | ||
13815 | @node hlines, colnames, sep, Specific header arguments | |
86fbb8ca CD |
13816 | @subsubsection @code{:hlines} |
13817 | ||
13818 | Tables are frequently represented with one or more horizontal lines, or | |
13819 | hlines. The @code{:hlines} argument to a code block accepts the | |
13820 | values @code{yes} or @code{no}, with a default value of @code{no}. | |
13821 | ||
13822 | @itemize @bullet | |
13823 | @item @code{no} | |
13824 | Strips horizontal lines from the input table. In most languages this is the | |
13825 | desired effect because an @code{hline} symbol is interpreted as an unbound | |
13826 | variable and raises an error. Setting @code{:hlines no} or relying on the | |
13827 | default value yields the following results. | |
13828 | ||
13829 | @example | |
e66ba1df | 13830 | #+TBLNAME: many-cols |
86fbb8ca CD |
13831 | | a | b | c | |
13832 | |---+---+---| | |
13833 | | d | e | f | | |
13834 | |---+---+---| | |
13835 | | g | h | i | | |
13836 | ||
e66ba1df BG |
13837 | #+NAME: echo-table |
13838 | #+BEGIN_SRC python :var tab=many-cols | |
86fbb8ca | 13839 | return tab |
e66ba1df | 13840 | #+END_SRC |
86fbb8ca CD |
13841 | |
13842 | #+results: echo-table | |
13843 | | a | b | c | | |
13844 | | d | e | f | | |
13845 | | g | h | i | | |
13846 | @end example | |
13847 | ||
13848 | @item @code{yes} | |
ce57c2fe | 13849 | Leaves hlines in the table. Setting @code{:hlines yes} has this effect. |
86fbb8ca CD |
13850 | |
13851 | @example | |
e66ba1df | 13852 | #+TBLNAME: many-cols |
86fbb8ca CD |
13853 | | a | b | c | |
13854 | |---+---+---| | |
13855 | | d | e | f | | |
13856 | |---+---+---| | |
13857 | | g | h | i | | |
13858 | ||
e66ba1df BG |
13859 | #+NAME: echo-table |
13860 | #+BEGIN_SRC python :var tab=many-cols :hlines yes | |
86fbb8ca | 13861 | return tab |
e66ba1df | 13862 | #+END_SRC |
86fbb8ca CD |
13863 | |
13864 | #+results: echo-table | |
13865 | | a | b | c | | |
13866 | |---+---+---| | |
13867 | | d | e | f | | |
13868 | |---+---+---| | |
13869 | | g | h | i | | |
13870 | @end example | |
13871 | @end itemize | |
13872 | ||
13873 | @node colnames, rownames, hlines, Specific header arguments | |
13874 | @subsubsection @code{:colnames} | |
13875 | ||
13876 | The @code{:colnames} header argument accepts the values @code{yes}, | |
13877 | @code{no}, or @code{nil} for unassigned. The default value is @code{nil}. | |
e66ba1df BG |
13878 | Note that the behavior of the @code{:colnames} header argument may differ |
13879 | across languages. For example Emacs Lisp code blocks ignore the | |
13880 | @code{:colnames} header argument entirely given the ease with which tables | |
13881 | with column names may be handled directly in Emacs Lisp. | |
86fbb8ca CD |
13882 | |
13883 | @itemize @bullet | |
13884 | @item @code{nil} | |
13885 | If an input table looks like it has column names | |
13886 | (because its second row is an hline), then the column | |
13887 | names will be removed from the table before | |
13888 | processing, then reapplied to the results. | |
13889 | ||
13890 | @example | |
e66ba1df | 13891 | #+TBLNAME: less-cols |
86fbb8ca CD |
13892 | | a | |
13893 | |---| | |
13894 | | b | | |
13895 | | c | | |
13896 | ||
e66ba1df BG |
13897 | #+NAME: echo-table-again |
13898 | #+BEGIN_SRC python :var tab=less-cols | |
86fbb8ca | 13899 | return [[val + '*' for val in row] for row in tab] |
e66ba1df | 13900 | #+END_SRC |
86fbb8ca CD |
13901 | |
13902 | #+results: echo-table-again | |
13903 | | a | | |
13904 | |----| | |
13905 | | b* | | |
13906 | | c* | | |
13907 | @end example | |
13908 | ||
ce57c2fe BG |
13909 | Please note that column names are not removed before the table is indexed |
13910 | using variable indexing @xref{var, Indexable variable values}. | |
13911 | ||
86fbb8ca CD |
13912 | @item @code{no} |
13913 | No column name pre-processing takes place | |
13914 | ||
13915 | @item @code{yes} | |
13916 | Column names are removed and reapplied as with @code{nil} even if the table | |
ce57c2fe | 13917 | does not ``look like'' it has column names (i.e.@: the second row is not an |
86fbb8ca CD |
13918 | hline) |
13919 | @end itemize | |
13920 | ||
13921 | @node rownames, shebang, colnames, Specific header arguments | |
13922 | @subsubsection @code{:rownames} | |
13923 | ||
13924 | The @code{:rownames} header argument can take on the values @code{yes} | |
13925 | or @code{no}, with a default value of @code{no}. | |
13926 | ||
13927 | @itemize @bullet | |
13928 | @item @code{no} | |
13929 | No row name pre-processing will take place. | |
13930 | ||
13931 | @item @code{yes} | |
13932 | The first column of the table is removed from the table before processing, | |
13933 | and is then reapplied to the results. | |
13934 | ||
13935 | @example | |
e66ba1df | 13936 | #+TBLNAME: with-rownames |
86fbb8ca CD |
13937 | | one | 1 | 2 | 3 | 4 | 5 | |
13938 | | two | 6 | 7 | 8 | 9 | 10 | | |
13939 | ||
e66ba1df BG |
13940 | #+NAME: echo-table-once-again |
13941 | #+BEGIN_SRC python :var tab=with-rownames :rownames yes | |
86fbb8ca | 13942 | return [[val + 10 for val in row] for row in tab] |
e66ba1df | 13943 | #+END_SRC |
86fbb8ca CD |
13944 | |
13945 | #+results: echo-table-once-again | |
13946 | | one | 11 | 12 | 13 | 14 | 15 | | |
13947 | | two | 16 | 17 | 18 | 19 | 20 | | |
13948 | @end example | |
ce57c2fe BG |
13949 | |
13950 | Please note that row names are not removed before the table is indexed using | |
13951 | variable indexing @xref{var, Indexable variable values}. | |
13952 | ||
86fbb8ca CD |
13953 | @end itemize |
13954 | ||
13955 | @node shebang, eval, rownames, Specific header arguments | |
13956 | @subsubsection @code{:shebang} | |
13957 | ||
13958 | Setting the @code{:shebang} header argument to a string value | |
ce57c2fe | 13959 | (e.g.@: @code{:shebang "#!/bin/bash"}) causes the string to be inserted as the |
86fbb8ca CD |
13960 | first line of any tangled file holding the code block, and the file |
13961 | permissions of the tangled file are set to make it executable. | |
13962 | ||
afe98dfa | 13963 | @node eval, , shebang, Specific header arguments |
86fbb8ca CD |
13964 | @subsubsection @code{:eval} |
13965 | The @code{:eval} header argument can be used to limit the evaluation of | |
e66ba1df BG |
13966 | specific code blocks. The @code{:eval} header argument can be useful for |
13967 | protecting against the evaluation of dangerous code blocks or to ensure that | |
13968 | evaluation will require a query regardless of the value of the | |
13969 | @code{org-confirm-babel-evaluate} variable. The possible values of | |
13970 | @code{:eval} and their effects are shown below. | |
13971 | ||
13972 | @table @code | |
13973 | @item never or no | |
13974 | The code block will not be evaluated under any circumstances. | |
13975 | @item query | |
13976 | Evaluation of the code block will require a query. | |
13977 | @item never-export or no-export | |
13978 | The code block will not be evaluated during export but may still be called | |
13979 | interactively. | |
13980 | @item query-export | |
13981 | Evaluation of the code block during export will require a query. | |
13982 | @end table | |
86fbb8ca | 13983 | |
ce57c2fe BG |
13984 | If this header argument is not set then evaluation is determined by the value |
13985 | of the @code{org-confirm-babel-evaluate} variable see @ref{Code evaluation | |
13986 | security}. | |
13987 | ||
86fbb8ca CD |
13988 | @node Results of evaluation, Noweb reference syntax, Header arguments, Working With Source Code |
13989 | @section Results of evaluation | |
13990 | @cindex code block, results of evaluation | |
13991 | @cindex source code, results of evaluation | |
13992 | ||
13993 | The way in which results are handled depends on whether a session is invoked, | |
13994 | as well as on whether @code{:results value} or @code{:results output} is | |
ce57c2fe BG |
13995 | used. The following table shows the table possibilities. For a full listing |
13996 | of the possible results header arguments see @ref{results}. | |
86fbb8ca CD |
13997 | |
13998 | @multitable @columnfractions 0.26 0.33 0.41 | |
13999 | @item @tab @b{Non-session} @tab @b{Session} | |
14000 | @item @code{:results value} @tab value of last expression @tab value of last expression | |
14001 | @item @code{:results output} @tab contents of STDOUT @tab concatenation of interpreter output | |
14002 | @end multitable | |
14003 | ||
14004 | Note: With @code{:results value}, the result in both @code{:session} and | |
e66ba1df | 14005 | non-session is returned to Org mode as a table (a one- or two-dimensional |
86fbb8ca CD |
14006 | vector of strings or numbers) when appropriate. |
14007 | ||
14008 | @subsection Non-session | |
14009 | @subsubsection @code{:results value} | |
ce57c2fe | 14010 | This is the default. Internally, the value is obtained by wrapping the code |
86fbb8ca | 14011 | in a function definition in the external language, and evaluating that |
ce57c2fe BG |
14012 | function. Therefore, code should be written as if it were the body of such a |
14013 | function. In particular, note that Python does not automatically return a | |
86fbb8ca | 14014 | value from a function unless a @code{return} statement is present, and so a |
acedf35c | 14015 | @samp{return} statement will usually be required in Python. |
86fbb8ca CD |
14016 | |
14017 | This is the only one of the four evaluation contexts in which the code is | |
14018 | automatically wrapped in a function definition. | |
14019 | ||
14020 | @subsubsection @code{:results output} | |
14021 | The code is passed to the interpreter as an external process, and the | |
ce57c2fe | 14022 | contents of the standard output stream are returned as text. (In certain |
86fbb8ca CD |
14023 | languages this also contains the error output stream; this is an area for |
14024 | future work.) | |
14025 | ||
acedf35c | 14026 | @subsection Session |
86fbb8ca | 14027 | @subsubsection @code{:results value} |
ce57c2fe BG |
14028 | The code is passed to an interpreter running as an interactive Emacs inferior |
14029 | process. Only languages which provide tools for interactive evaluation of | |
14030 | code have session support, so some language (e.g., C and ditaa) do not | |
14031 | support the @code{:session} header argument, and in other languages (e.g., | |
14032 | Python and Haskell) which have limitations on the code which may be entered | |
14033 | into interactive sessions, those limitations apply to the code in code blocks | |
14034 | using the @code{:session} header argument as well. | |
14035 | ||
14036 | Unless the @code{:results output} option is supplied (see below) the result | |
14037 | returned is the result of the last evaluation performed by the | |
14038 | interpreter. (This is obtained in a language-specific manner: the value of | |
14039 | the variable @code{_} in Python and Ruby, and the value of @code{.Last.value} | |
14040 | in R). | |
86fbb8ca CD |
14041 | |
14042 | @subsubsection @code{:results output} | |
14043 | The code is passed to the interpreter running as an interactive Emacs | |
ce57c2fe BG |
14044 | inferior process. The result returned is the concatenation of the sequence of |
14045 | (text) output from the interactive interpreter. Notice that this is not | |
86fbb8ca CD |
14046 | necessarily the same as what would be sent to @code{STDOUT} if the same code |
14047 | were passed to a non-interactive interpreter running as an external | |
ce57c2fe | 14048 | process. For example, compare the following two blocks: |
86fbb8ca CD |
14049 | |
14050 | @example | |
e66ba1df | 14051 | #+BEGIN_SRC python :results output |
86fbb8ca CD |
14052 | print "hello" |
14053 | 2 | |
14054 | print "bye" | |
e66ba1df | 14055 | #+END_SRC |
86fbb8ca | 14056 | |
e66ba1df | 14057 | #+results: |
86fbb8ca CD |
14058 | : hello |
14059 | : bye | |
14060 | @end example | |
14061 | ||
acedf35c | 14062 | In non-session mode, the `2' is not printed and does not appear. |
86fbb8ca | 14063 | @example |
e66ba1df | 14064 | #+BEGIN_SRC python :results output :session |
86fbb8ca CD |
14065 | print "hello" |
14066 | 2 | |
14067 | print "bye" | |
e66ba1df | 14068 | #+END_SRC |
86fbb8ca | 14069 | |
e66ba1df | 14070 | #+results: |
86fbb8ca CD |
14071 | : hello |
14072 | : 2 | |
14073 | : bye | |
14074 | @end example | |
14075 | ||
acedf35c | 14076 | But in @code{:session} mode, the interactive interpreter receives input `2' |
ce57c2fe | 14077 | and prints out its value, `2'. (Indeed, the other print statements are |
86fbb8ca CD |
14078 | unnecessary here). |
14079 | ||
14080 | @node Noweb reference syntax, Key bindings and useful functions, Results of evaluation, Working With Source Code | |
14081 | @section Noweb reference syntax | |
14082 | @cindex code block, noweb reference | |
14083 | @cindex syntax, noweb | |
14084 | @cindex source code, noweb reference | |
14085 | ||
14086 | The ``noweb'' (see @uref{http://www.cs.tufts.edu/~nr/noweb/}) Literate | |
14087 | Programming system allows named blocks of code to be referenced by using the | |
14088 | familiar Noweb syntax: | |
14089 | ||
14090 | @example | |
14091 | <<code-block-name>> | |
14092 | @end example | |
14093 | ||
14094 | When a code block is tangled or evaluated, whether or not ``noweb'' | |
14095 | references are expanded depends upon the value of the @code{:noweb} header | |
14096 | argument. If @code{:noweb yes}, then a Noweb reference is expanded before | |
14097 | evaluation. If @code{:noweb no}, the default, then the reference is not | |
e66ba1df BG |
14098 | expanded before evaluation. See the @ref{noweb-ref} header argument for |
14099 | a more flexible way to resolve noweb references. | |
86fbb8ca | 14100 | |
153ae947 BG |
14101 | It is possible to include the @emph{results} of a code block rather than the |
14102 | body. This is done by appending parenthesis to the code block name which may | |
14103 | optionally contain arguments to the code block as shown below. | |
14104 | ||
14105 | @example | |
14106 | <<code-block-name(optional arguments)>> | |
14107 | @end example | |
14108 | ||
86fbb8ca CD |
14109 | Note: the default value, @code{:noweb no}, was chosen to ensure that |
14110 | correct code is not broken in a language, such as Ruby, where | |
14111 | @code{<<arg>>} is a syntactically valid construct. If @code{<<arg>>} is not | |
14112 | syntactically valid in languages that you use, then please consider setting | |
14113 | the default value. | |
14114 | ||
e66ba1df BG |
14115 | Note: if noweb tangling is slow in large Org-mode files consider setting the |
14116 | @code{*org-babel-use-quick-and-dirty-noweb-expansion*} variable to true. | |
14117 | This will result in faster noweb reference resolution at the expense of not | |
14118 | correctly resolving inherited values of the @code{:noweb-ref} header | |
14119 | argument. | |
14120 | ||
86fbb8ca CD |
14121 | @node Key bindings and useful functions, Batch execution, Noweb reference syntax, Working With Source Code |
14122 | @section Key bindings and useful functions | |
14123 | @cindex code block, key bindings | |
14124 | ||
e66ba1df | 14125 | Many common Org mode key sequences are re-bound depending on |
86fbb8ca CD |
14126 | the context. |
14127 | ||
14128 | Within a code block, the following key bindings | |
14129 | are active: | |
14130 | ||
14131 | @multitable @columnfractions 0.25 0.75 | |
14132 | @kindex C-c C-c | |
ce57c2fe | 14133 | @item @kbd{C-c C-c} @tab @code{org-babel-execute-src-block} |
86fbb8ca | 14134 | @kindex C-c C-o |
ce57c2fe | 14135 | @item @kbd{C-c C-o} @tab @code{org-babel-open-src-block-result} |
86fbb8ca | 14136 | @kindex C-up |
ce57c2fe | 14137 | @item @kbd{C-@key{up}} @tab @code{org-babel-load-in-session} |
86fbb8ca | 14138 | @kindex M-down |
ce57c2fe | 14139 | @item @kbd{M-@key{down}} @tab @code{org-babel-pop-to-session} |
86fbb8ca CD |
14140 | @end multitable |
14141 | ||
e66ba1df | 14142 | In an Org mode buffer, the following key bindings are active: |
86fbb8ca CD |
14143 | |
14144 | @multitable @columnfractions 0.45 0.55 | |
153ae947 BG |
14145 | @kindex C-c C-v p |
14146 | @kindex C-c C-v C-p | |
14147 | @item @kbd{C-c C-v p} @ @ @r{or} @ @ @kbd{C-c C-v C-p} @tab @code{org-babel-previous-src-block} | |
14148 | @kindex C-c C-v n | |
14149 | @kindex C-c C-v C-n | |
14150 | @item @kbd{C-c C-v n} @ @ @r{or} @ @ @kbd{C-c C-v C-n} @tab @code{org-babel-next-src-block} | |
14151 | @kindex C-c C-v e | |
14152 | @kindex C-c C-v C-e | |
14153 | @item @kbd{C-c C-v e} @ @ @r{or} @ @ @kbd{C-c C-v C-e} @tab @code{org-babel-execute-maybe} | |
14154 | @kindex C-c C-v o | |
14155 | @kindex C-c C-v C-o | |
14156 | @item @kbd{C-c C-v o} @ @ @r{or} @ @ @kbd{C-c C-v C-o} @tab @code{org-babel-open-src-block-result} | |
14157 | @kindex C-c C-v v | |
14158 | @kindex C-c C-v C-v | |
14159 | @item @kbd{C-c C-v v} @ @ @r{or} @ @ @kbd{C-c C-v C-v} @tab @code{org-babel-expand-src-block} | |
14160 | @kindex C-c C-v u | |
14161 | @kindex C-c C-v C-u | |
14162 | @item @kbd{C-c C-v u} @ @ @r{or} @ @ @kbd{C-c C-v C-u} @tab @code{org-babel-goto-src-block-head} | |
14163 | @kindex C-c C-v g | |
14164 | @kindex C-c C-v C-g | |
14165 | @item @kbd{C-c C-v g} @ @ @r{or} @ @ @kbd{C-c C-v C-g} @tab @code{org-babel-goto-named-src-block} | |
14166 | @kindex C-c C-v r | |
14167 | @kindex C-c C-v C-r | |
14168 | @item @kbd{C-c C-v r} @ @ @r{or} @ @ @kbd{C-c C-v C-r} @tab @code{org-babel-goto-named-result} | |
86fbb8ca CD |
14169 | @kindex C-c C-v b |
14170 | @kindex C-c C-v C-b | |
ce57c2fe | 14171 | @item @kbd{C-c C-v b} @ @ @r{or} @ @ @kbd{C-c C-v C-b} @tab @code{org-babel-execute-buffer} |
86fbb8ca CD |
14172 | @kindex C-c C-v s |
14173 | @kindex C-c C-v C-s | |
ce57c2fe | 14174 | @item @kbd{C-c C-v s} @ @ @r{or} @ @ @kbd{C-c C-v C-s} @tab @code{org-babel-execute-subtree} |
153ae947 BG |
14175 | @kindex C-c C-v d |
14176 | @kindex C-c C-v C-d | |
14177 | @item @kbd{C-c C-v d} @ @ @r{or} @ @ @kbd{C-c C-v C-d} @tab @code{org-babel-demarcate-block} | |
86fbb8ca CD |
14178 | @kindex C-c C-v t |
14179 | @kindex C-c C-v C-t | |
ce57c2fe | 14180 | @item @kbd{C-c C-v t} @ @ @r{or} @ @ @kbd{C-c C-v C-t} @tab @code{org-babel-tangle} |
153ae947 BG |
14181 | @kindex C-c C-v f |
14182 | @kindex C-c C-v C-f | |
14183 | @item @kbd{C-c C-v f} @ @ @r{or} @ @ @kbd{C-c C-v C-f} @tab @code{org-babel-tangle-file} | |
14184 | @kindex C-c C-v c | |
14185 | @kindex C-c C-v C-c | |
14186 | @item @kbd{C-c C-v c} @ @ @r{or} @ @ @kbd{C-c C-v C-c} @tab @code{org-babel-check-src-block} | |
14187 | @kindex C-c C-v j | |
14188 | @kindex C-c C-v C-j | |
14189 | @item @kbd{C-c C-v j} @ @ @r{or} @ @ @kbd{C-c C-v C-j} @tab @code{org-babel-insert-header-arg} | |
14190 | @kindex C-c C-v l | |
14191 | @kindex C-c C-v C-l | |
14192 | @item @kbd{C-c C-v l} @ @ @r{or} @ @ @kbd{C-c C-v C-l} @tab @code{org-babel-load-in-session} | |
14193 | @kindex C-c C-v i | |
14194 | @kindex C-c C-v C-i | |
14195 | @item @kbd{C-c C-v i} @ @ @r{or} @ @ @kbd{C-c C-v C-i} @tab @code{org-babel-lob-ingest} | |
14196 | @kindex C-c C-v I | |
14197 | @kindex C-c C-v C-I | |
14198 | @item @kbd{C-c C-v I} @ @ @r{or} @ @ @kbd{C-c C-v C-I} @tab @code{org-babel-view-src-block-info} | |
86fbb8ca CD |
14199 | @kindex C-c C-v z |
14200 | @kindex C-c C-v C-z | |
153ae947 BG |
14201 | @item @kbd{C-c C-v z} @ @ @r{or} @ @ @kbd{C-c C-v C-z} @tab @code{org-babel-switch-to-session-with-code} |
14202 | @kindex C-c C-v a | |
14203 | @kindex C-c C-v C-a | |
14204 | @item @kbd{C-c C-v a} @ @ @r{or} @ @ @kbd{C-c C-v C-a} @tab @code{org-babel-sha1-hash} | |
14205 | @kindex C-c C-v h | |
14206 | @kindex C-c C-v C-h | |
14207 | @item @kbd{C-c C-v h} @ @ @r{or} @ @ @kbd{C-c C-v C-h} @tab @code{org-babel-describe-bindings} | |
14208 | @kindex C-c C-v x | |
14209 | @kindex C-c C-v C-x | |
14210 | @item @kbd{C-c C-v x} @ @ @r{or} @ @ @kbd{C-c C-v C-x} @tab @code{org-babel-do-key-sequence-in-edit-buffer} | |
86fbb8ca CD |
14211 | @end multitable |
14212 | ||
14213 | @c When possible these keybindings were extended to work when the control key is | |
14214 | @c kept pressed, resulting in the following additional keybindings. | |
14215 | ||
14216 | @c @multitable @columnfractions 0.25 0.75 | |
ce57c2fe BG |
14217 | @c @item @kbd{C-c C-v C-a} @tab @code{org-babel-sha1-hash} |
14218 | @c @item @kbd{C-c C-v C-b} @tab @code{org-babel-execute-buffer} | |
14219 | @c @item @kbd{C-c C-v C-f} @tab @code{org-babel-tangle-file} | |
14220 | @c @item @kbd{C-c C-v C-l} @tab @code{org-babel-lob-ingest} | |
14221 | @c @item @kbd{C-c C-v C-p} @tab @code{org-babel-expand-src-block} | |
14222 | @c @item @kbd{C-c C-v C-s} @tab @code{org-babel-execute-subtree} | |
14223 | @c @item @kbd{C-c C-v C-t} @tab @code{org-babel-tangle} | |
14224 | @c @item @kbd{C-c C-v C-z} @tab @code{org-babel-switch-to-session} | |
86fbb8ca CD |
14225 | @c @end multitable |
14226 | ||
14227 | @node Batch execution, , Key bindings and useful functions, Working With Source Code | |
14228 | @section Batch execution | |
14229 | @cindex code block, batch execution | |
14230 | @cindex source code, batch execution | |
14231 | ||
14232 | It is possible to call functions from the command line. This shell | |
14233 | script calls @code{org-babel-tangle} on every one of its arguments. | |
14234 | ||
14235 | Be sure to adjust the paths to fit your system. | |
14236 | ||
14237 | @example | |
14238 | #!/bin/sh | |
14239 | # -*- mode: shell-script -*- | |
14240 | # | |
afe98dfa | 14241 | # tangle files with org-mode |
86fbb8ca CD |
14242 | # |
14243 | DIR=`pwd` | |
14244 | FILES="" | |
afe98dfa | 14245 | ORGINSTALL="~/src/org/lisp/org-install.el" |
86fbb8ca CD |
14246 | |
14247 | # wrap each argument in the code required to call tangle on it | |
14248 | for i in $@@; do | |
afe98dfa | 14249 | FILES="$FILES \"$i\"" |
86fbb8ca CD |
14250 | done |
14251 | ||
afe98dfa | 14252 | emacs -Q --batch -l $ORGINSTALL \ |
86fbb8ca CD |
14253 | --eval "(progn |
14254 | (add-to-list 'load-path (expand-file-name \"~/src/org/lisp/\")) | |
14255 | (add-to-list 'load-path (expand-file-name \"~/src/org/contrib/lisp/\")) | |
14256 | (require 'org)(require 'org-exp)(require 'ob)(require 'ob-tangle) | |
14257 | (mapc (lambda (file) | |
14258 | (find-file (expand-file-name file \"$DIR\")) | |
14259 | (org-babel-tangle) | |
afe98dfa | 14260 | (kill-buffer)) '($FILES)))" 2>&1 |grep tangled |
86fbb8ca CD |
14261 | @end example |
14262 | ||
14263 | @node Miscellaneous, Hacking, Working With Source Code, Top | |
14264 | @chapter Miscellaneous | |
14265 | ||
14266 | @menu | |
c0468714 | 14267 | * Completion:: M-TAB knows what you need |
afe98dfa | 14268 | * Easy Templates:: Quick insertion of structural elements |
c0468714 GM |
14269 | * Speed keys:: Electric commands at the beginning of a headline |
14270 | * Code evaluation security:: Org mode files evaluate inline code | |
14271 | * Customization:: Adapting Org to your taste | |
14272 | * In-buffer settings:: Overview of the #+KEYWORDS | |
14273 | * The very busy C-c C-c key:: When in doubt, press C-c C-c | |
14274 | * Clean view:: Getting rid of leading stars in the outline | |
14275 | * TTY keys:: Using Org on a tty | |
14276 | * Interaction:: Other Emacs packages | |
ce57c2fe | 14277 | * org-crypt.el:: Encrypting Org files |
86fbb8ca CD |
14278 | @end menu |
14279 | ||
14280 | ||
afe98dfa | 14281 | @node Completion, Easy Templates, Miscellaneous, Miscellaneous |
86fbb8ca CD |
14282 | @section Completion |
14283 | @cindex completion, of @TeX{} symbols | |
14284 | @cindex completion, of TODO keywords | |
14285 | @cindex completion, of dictionary words | |
14286 | @cindex completion, of option keywords | |
14287 | @cindex completion, of tags | |
14288 | @cindex completion, of property keys | |
14289 | @cindex completion, of link abbreviations | |
14290 | @cindex @TeX{} symbol completion | |
14291 | @cindex TODO keywords completion | |
14292 | @cindex dictionary word completion | |
14293 | @cindex option keyword completion | |
14294 | @cindex tag completion | |
14295 | @cindex link abbreviations, completion of | |
14296 | ||
e66ba1df | 14297 | Emacs would not be Emacs without completion, and Org mode uses it whenever it |
86fbb8ca CD |
14298 | makes sense. If you prefer an @i{iswitchb}- or @i{ido}-like interface for |
14299 | some of the completion prompts, you can specify your preference by setting at | |
14300 | most one of the variables @code{org-completion-use-iswitchb} | |
14301 | @code{org-completion-use-ido}. | |
14302 | ||
14303 | Org supports in-buffer completion. This type of completion does | |
14304 | not make use of the minibuffer. You simply type a few letters into | |
14305 | the buffer and use the key to complete text right there. | |
14306 | ||
14307 | @table @kbd | |
14308 | @kindex M-@key{TAB} | |
14309 | @item M-@key{TAB} | |
14310 | Complete word at point | |
14311 | @itemize @bullet | |
14312 | @item | |
14313 | At the beginning of a headline, complete TODO keywords. | |
14314 | @item | |
14315 | After @samp{\}, complete @TeX{} symbols supported by the exporter. | |
14316 | @item | |
14317 | After @samp{*}, complete headlines in the current buffer so that they | |
14318 | can be used in search links like @samp{[[*find this headline]]}. | |
14319 | @item | |
14320 | After @samp{:} in a headline, complete tags. The list of tags is taken | |
14321 | from the variable @code{org-tag-alist} (possibly set through the | |
14322 | @samp{#+TAGS} in-buffer option, @pxref{Setting tags}), or it is created | |
14323 | dynamically from all tags used in the current buffer. | |
14324 | @item | |
14325 | After @samp{:} and not in a headline, complete property keys. The list | |
14326 | of keys is constructed dynamically from all keys used in the current | |
14327 | buffer. | |
14328 | @item | |
14329 | After @samp{[}, complete link abbreviations (@pxref{Link abbreviations}). | |
14330 | @item | |
14331 | After @samp{#+}, complete the special keywords like @samp{TYP_TODO} or | |
e66ba1df | 14332 | @samp{OPTIONS} which set file-specific options for Org mode. When the |
86fbb8ca CD |
14333 | option keyword is already complete, pressing @kbd{M-@key{TAB}} again |
14334 | will insert example settings for this keyword. | |
14335 | @item | |
14336 | In the line after @samp{#+STARTUP: }, complete startup keywords, | |
ce57c2fe | 14337 | i.e.@: valid keys for this line. |
86fbb8ca CD |
14338 | @item |
14339 | Elsewhere, complete dictionary words using Ispell. | |
14340 | @end itemize | |
14341 | @end table | |
14342 | ||
afe98dfa CD |
14343 | @node Easy Templates, Speed keys, Completion, Miscellaneous |
14344 | @section Easy Templates | |
14345 | @cindex template insertion | |
14346 | @cindex insertion, of templates | |
14347 | ||
e66ba1df | 14348 | Org mode supports insertion of empty structural elements (like |
afe98dfa CD |
14349 | @code{#+BEGIN_SRC} and @code{#+END_SRC} pairs) with just a few key |
14350 | strokes. This is achieved through a native template expansion mechanism. | |
14351 | Note that Emacs has several other template mechanisms which could be used in | |
14352 | a similar way, for example @file{yasnippet}. | |
14353 | ||
14354 | To insert a structural element, type a @samp{<}, followed by a template | |
14355 | selector and @kbd{@key{TAB}}. Completion takes effect only when the above | |
14356 | keystrokes are typed on a line by itself. | |
14357 | ||
14358 | The following template selectors are currently supported. | |
14359 | ||
14360 | @multitable @columnfractions 0.1 0.9 | |
14361 | @item @kbd{s} @tab @code{#+begin_src ... #+end_src} | |
14362 | @item @kbd{e} @tab @code{#+begin_example ... #+end_example} | |
14363 | @item @kbd{q} @tab @code{#+begin_quote ... #+end_quote} | |
14364 | @item @kbd{v} @tab @code{#+begin_verse ... #+end_verse} | |
14365 | @item @kbd{c} @tab @code{#+begin_center ... #+end_center} | |
14366 | @item @kbd{l} @tab @code{#+begin_latex ... #+end_latex} | |
14367 | @item @kbd{L} @tab @code{#+latex:} | |
14368 | @item @kbd{h} @tab @code{#+begin_html ... #+end_html} | |
14369 | @item @kbd{H} @tab @code{#+html:} | |
14370 | @item @kbd{a} @tab @code{#+begin_ascii ... #+end_ascii} | |
14371 | @item @kbd{A} @tab @code{#+ascii:} | |
ce57c2fe BG |
14372 | @item @kbd{i} @tab @code{#+index:} line |
14373 | @item @kbd{I} @tab @code{#+include:} line | |
afe98dfa CD |
14374 | @end multitable |
14375 | ||
14376 | For example, on an empty line, typing "<e" and then pressing TAB, will expand | |
14377 | into a complete EXAMPLE template. | |
14378 | ||
14379 | You can install additional templates by customizing the variable | |
ce57c2fe | 14380 | @code{org-structure-template-alist}. See the docstring of the variable for |
afe98dfa CD |
14381 | additional details. |
14382 | ||
14383 | @node Speed keys, Code evaluation security, Easy Templates, Miscellaneous | |
86fbb8ca CD |
14384 | @section Speed keys |
14385 | @cindex speed keys | |
14386 | @vindex org-use-speed-commands | |
14387 | @vindex org-speed-commands-user | |
14388 | ||
14389 | Single keys can be made to execute commands when the cursor is at the | |
ce57c2fe | 14390 | beginning of a headline, i.e.@: before the first star. Configure the variable |
86fbb8ca CD |
14391 | @code{org-use-speed-commands} to activate this feature. There is a |
14392 | pre-defined list of commands, and you can add more such commands using the | |
14393 | variable @code{org-speed-commands-user}. Speed keys do not only speed up | |
14394 | navigation and other commands, but they also provide an alternative way to | |
acedf35c | 14395 | execute commands bound to keys that are not or not easily available on a TTY, |
86fbb8ca CD |
14396 | or on a small mobile device with a limited keyboard. |
14397 | ||
14398 | To see which commands are available, activate the feature and press @kbd{?} | |
14399 | with the cursor at the beginning of a headline. | |
14400 | ||
14401 | @node Code evaluation security, Customization, Speed keys, Miscellaneous | |
14402 | @section Code evaluation and security issues | |
14403 | ||
afe98dfa | 14404 | Org provides tools to work with the code snippets, including evaluating them. |
86fbb8ca CD |
14405 | |
14406 | Running code on your machine always comes with a security risk. Badly | |
14407 | written or malicious code can be executed on purpose or by accident. Org has | |
14408 | default settings which will only evaluate such code if you give explicit | |
14409 | permission to do so, and as a casual user of these features you should leave | |
14410 | these precautions intact. | |
14411 | ||
14412 | For people who regularly work with such code, the confirmation prompts can | |
14413 | become annoying, and you might want to turn them off. This can be done, but | |
14414 | you must be aware of the risks that are involved. | |
14415 | ||
14416 | Code evaluation can happen under the following circumstances: | |
14417 | ||
14418 | @table @i | |
14419 | @item Source code blocks | |
14420 | Source code blocks can be evaluated during export, or when pressing @kbd{C-c | |
14421 | C-c} in the block. The most important thing to realize here is that Org mode | |
afe98dfa | 14422 | files which contain code snippets are, in a certain sense, like executable |
86fbb8ca | 14423 | files. So you should accept them and load them into Emacs only from trusted |
acedf35c | 14424 | sources---just like you would do with a program you install on your computer. |
86fbb8ca CD |
14425 | |
14426 | Make sure you know what you are doing before customizing the variables | |
afe98dfa | 14427 | which take off the default security brakes. |
86fbb8ca CD |
14428 | |
14429 | @defopt org-confirm-babel-evaluate | |
ce57c2fe BG |
14430 | When t (the default), the user is asked before every code block evaluation. |
14431 | When nil, the user is not asked. When set to a function, it is called with | |
14432 | two arguments (language and body of the code block) and should return t to | |
14433 | ask and nil not to ask. | |
86fbb8ca CD |
14434 | @end defopt |
14435 | ||
ce57c2fe BG |
14436 | For example, here is how to execute "ditaa" code (which is considered safe) |
14437 | without asking: | |
14438 | @example | |
14439 | (defun my-org-confirm-babel-evaluate (lang body) | |
14440 | (not (string= lang "ditaa"))) ; don't ask for ditaa | |
14441 | (setq org-confirm-babel-evaluate 'my-org-confirm-babel-evaluate) | |
14442 | @end example | |
14443 | ||
86fbb8ca CD |
14444 | @item Following @code{shell} and @code{elisp} links |
14445 | Org has two link types that can directly evaluate code (@pxref{External | |
afe98dfa | 14446 | links}). These links can be problematic because the code to be evaluated is |
86fbb8ca CD |
14447 | not visible. |
14448 | ||
14449 | @defopt org-confirm-shell-link-function | |
14450 | Function to queries user about shell link execution. | |
14451 | @end defopt | |
14452 | @defopt org-confirm-elisp-link-function | |
14453 | Functions to query user for Emacs Lisp link execution. | |
14454 | @end defopt | |
14455 | ||
86fbb8ca CD |
14456 | @item Formulas in tables |
14457 | Formulas in tables (@pxref{The spreadsheet}) are code that is evaluated | |
14458 | either by the @i{calc} interpreter, or by the @i{Emacs Lisp} interpreter. | |
14459 | @end table | |
14460 | ||
14461 | @node Customization, In-buffer settings, Code evaluation security, Miscellaneous | |
14462 | @section Customization | |
14463 | @cindex customization | |
14464 | @cindex options, for customization | |
14465 | @cindex variables, for customization | |
14466 | ||
14467 | There are more than 180 variables that can be used to customize | |
14468 | Org. For the sake of compactness of the manual, I am not | |
14469 | describing the variables here. A structured overview of customization | |
14470 | variables is available with @kbd{M-x org-customize}. Or select | |
14471 | @code{Browse Org Group} from the @code{Org->Customization} menu. Many | |
14472 | settings can also be activated on a per-file basis, by putting special | |
14473 | lines into the buffer (@pxref{In-buffer settings}). | |
4009494e GM |
14474 | |
14475 | @node In-buffer settings, The very busy C-c C-c key, Customization, Miscellaneous | |
14476 | @section Summary of in-buffer settings | |
14477 | @cindex in-buffer settings | |
14478 | @cindex special keywords | |
14479 | ||
e66ba1df | 14480 | Org mode uses special lines in the buffer to define settings on a |
4009494e GM |
14481 | per-file basis. These lines start with a @samp{#+} followed by a |
14482 | keyword, a colon, and then individual words defining a setting. Several | |
14483 | setting words can be in the same line, but you can also have multiple | |
14484 | lines for the keyword. While these settings are described throughout | |
14485 | the manual, here is a summary. After changing any of those lines in the | |
14486 | buffer, press @kbd{C-c C-c} with the cursor still in the line to | |
14487 | activate the changes immediately. Otherwise they become effective only | |
14488 | when the file is visited again in a new Emacs session. | |
14489 | ||
c8d0cf5c | 14490 | @vindex org-archive-location |
4009494e GM |
14491 | @table @kbd |
14492 | @item #+ARCHIVE: %s_done:: | |
14493 | This line sets the archive location for the agenda file. It applies for | |
14494 | all subsequent lines until the next @samp{#+ARCHIVE} line, or the end | |
14495 | of the file. The first such line also applies to any entries before it. | |
14496 | The corresponding variable is @code{org-archive-location}. | |
14497 | @item #+CATEGORY: | |
14498 | This line sets the category for the agenda file. The category applies | |
14499 | for all subsequent lines until the next @samp{#+CATEGORY} line, or the | |
14500 | end of the file. The first such line also applies to any entries before it. | |
14501 | @item #+COLUMNS: %25ITEM ..... | |
c8d0cf5c | 14502 | @cindex property, COLUMNS |
4009494e | 14503 | Set the default format for columns view. This format applies when |
c8d0cf5c | 14504 | columns view is invoked in locations where no @code{COLUMNS} property |
dbc28aaa | 14505 | applies. |
4009494e | 14506 | @item #+CONSTANTS: name1=value1 ... |
c8d0cf5c CD |
14507 | @vindex org-table-formula-constants |
14508 | @vindex org-table-formula | |
4009494e | 14509 | Set file-local values for constants to be used in table formulas. This |
acedf35c | 14510 | line sets the local variable @code{org-table-formula-constants-local}. |
dbc28aaa | 14511 | The global version of this variable is |
4009494e | 14512 | @code{org-table-formula-constants}. |
b349f79f CD |
14513 | @item #+FILETAGS: :tag1:tag2:tag3: |
14514 | Set tags that can be inherited by any entry in the file, including the | |
14515 | top-level entries. | |
dbc28aaa | 14516 | @item #+DRAWERS: NAME1 ..... |
c8d0cf5c | 14517 | @vindex org-drawers |
dbc28aaa CD |
14518 | Set the file-local set of drawers. The corresponding global variable is |
14519 | @code{org-drawers}. | |
4009494e | 14520 | @item #+LINK: linkword replace |
c8d0cf5c | 14521 | @vindex org-link-abbrev-alist |
4009494e GM |
14522 | These lines (several are allowed) specify link abbreviations. |
14523 | @xref{Link abbreviations}. The corresponding variable is | |
14524 | @code{org-link-abbrev-alist}. | |
14525 | @item #+PRIORITIES: highest lowest default | |
c8d0cf5c CD |
14526 | @vindex org-highest-priority |
14527 | @vindex org-lowest-priority | |
14528 | @vindex org-default-priority | |
4009494e GM |
14529 | This line sets the limits and the default for the priorities. All three |
14530 | must be either letters A-Z or numbers 0-9. The highest priority must | |
acedf35c | 14531 | have a lower ASCII number than the lowest priority. |
4009494e GM |
14532 | @item #+PROPERTY: Property_Name Value |
14533 | This line sets a default inheritance value for entries in the current | |
14534 | buffer, most useful for specifying the allowed values of a property. | |
c8d0cf5c | 14535 | @cindex #+SETUPFILE |
b349f79f CD |
14536 | @item #+SETUPFILE: file |
14537 | This line defines a file that holds more in-buffer setup. Normally this is | |
14538 | entirely ignored. Only when the buffer is parsed for option-setting lines | |
e66ba1df | 14539 | (i.e.@: when starting Org mode for a file, when pressing @kbd{C-c C-c} in a |
b349f79f | 14540 | settings line, or when exporting), then the contents of this file are parsed |
a50253cc | 14541 | as if they had been included in the buffer. In particular, the file can be |
e66ba1df | 14542 | any other Org mode file with internal setup. You can visit the file the |
b349f79f | 14543 | cursor is in the line with @kbd{C-c '}. |
4009494e | 14544 | @item #+STARTUP: |
c8d0cf5c | 14545 | @cindex #+STARTUP: |
e66ba1df | 14546 | This line sets options to be used at startup of Org mode, when an |
c8d0cf5c CD |
14547 | Org file is being visited. |
14548 | ||
14549 | The first set of options deals with the initial visibility of the outline | |
14550 | tree. The corresponding variable for global default settings is | |
14551 | @code{org-startup-folded}, with a default value @code{t}, which means | |
14552 | @code{overview}. | |
14553 | @vindex org-startup-folded | |
4009494e GM |
14554 | @cindex @code{overview}, STARTUP keyword |
14555 | @cindex @code{content}, STARTUP keyword | |
14556 | @cindex @code{showall}, STARTUP keyword | |
7006d207 | 14557 | @cindex @code{showeverything}, STARTUP keyword |
4009494e | 14558 | @example |
7006d207 CD |
14559 | overview @r{top-level headlines only} |
14560 | content @r{all headlines} | |
14561 | showall @r{no folding of any entries} | |
14562 | showeverything @r{show even drawer contents} | |
4009494e | 14563 | @end example |
c8d0cf5c CD |
14564 | |
14565 | @vindex org-startup-indented | |
14566 | @cindex @code{indent}, STARTUP keyword | |
14567 | @cindex @code{noindent}, STARTUP keyword | |
14568 | Dynamic virtual indentation is controlled by the variable | |
e66ba1df | 14569 | @code{org-startup-indented}@footnote{Emacs 23 and Org mode 6.29 are required} |
c8d0cf5c CD |
14570 | @example |
14571 | indent @r{start with @code{org-indent-mode} turned on} | |
14572 | noindent @r{start with @code{org-indent-mode} turned off} | |
14573 | @end example | |
14574 | ||
14575 | @vindex org-startup-align-all-tables | |
4009494e GM |
14576 | Then there are options for aligning tables upon visiting a file. This |
14577 | is useful in files containing narrowed table columns. The corresponding | |
14578 | variable is @code{org-startup-align-all-tables}, with a default value | |
28a16a1b | 14579 | @code{nil}. |
4009494e GM |
14580 | @cindex @code{align}, STARTUP keyword |
14581 | @cindex @code{noalign}, STARTUP keyword | |
14582 | @example | |
14583 | align @r{align all tables} | |
14584 | noalign @r{don't align tables on startup} | |
14585 | @end example | |
afe98dfa CD |
14586 | |
14587 | @vindex org-startup-with-inline-images | |
14588 | When visiting a file, inline images can be automatically displayed. The | |
14589 | corresponding variable is @code{org-startup-with-inline-images}, with a | |
14590 | default value @code{nil} to avoid delays when visiting a file. | |
14591 | @cindex @code{inlineimages}, STARTUP keyword | |
14592 | @cindex @code{noinlineimages}, STARTUP keyword | |
14593 | @example | |
14594 | inlineimages @r{show inline images} | |
14595 | noinlineimages @r{don't show inline images on startup} | |
14596 | @end example | |
14597 | ||
c8d0cf5c CD |
14598 | @vindex org-log-done |
14599 | @vindex org-log-note-clock-out | |
14600 | @vindex org-log-repeat | |
14601 | Logging the closing and reopening of TODO items and clock intervals can be | |
14602 | configured using these options (see variables @code{org-log-done}, | |
14603 | @code{org-log-note-clock-out} and @code{org-log-repeat}) | |
4009494e | 14604 | @cindex @code{logdone}, STARTUP keyword |
4009494e | 14605 | @cindex @code{lognotedone}, STARTUP keyword |
28a16a1b | 14606 | @cindex @code{nologdone}, STARTUP keyword |
4009494e | 14607 | @cindex @code{lognoteclock-out}, STARTUP keyword |
28a16a1b | 14608 | @cindex @code{nolognoteclock-out}, STARTUP keyword |
4009494e | 14609 | @cindex @code{logrepeat}, STARTUP keyword |
28a16a1b | 14610 | @cindex @code{lognoterepeat}, STARTUP keyword |
4009494e | 14611 | @cindex @code{nologrepeat}, STARTUP keyword |
a351880d CD |
14612 | @cindex @code{logreschedule}, STARTUP keyword |
14613 | @cindex @code{lognotereschedule}, STARTUP keyword | |
14614 | @cindex @code{nologreschedule}, STARTUP keyword | |
14615 | @cindex @code{logredeadline}, STARTUP keyword | |
14616 | @cindex @code{lognoteredeadline}, STARTUP keyword | |
14617 | @cindex @code{nologredeadline}, STARTUP keyword | |
ed21c5c8 CD |
14618 | @cindex @code{logrefile}, STARTUP keyword |
14619 | @cindex @code{lognoterefile}, STARTUP keyword | |
14620 | @cindex @code{nologrefile}, STARTUP keyword | |
4009494e | 14621 | @example |
28a16a1b CD |
14622 | logdone @r{record a timestamp when an item is marked DONE} |
14623 | lognotedone @r{record timestamp and a note when DONE} | |
14624 | nologdone @r{don't record when items are marked DONE} | |
14625 | logrepeat @r{record a time when reinstating a repeating item} | |
14626 | lognoterepeat @r{record a note when reinstating a repeating item} | |
14627 | nologrepeat @r{do not record when reinstating repeating item} | |
14628 | lognoteclock-out @r{record a note when clocking out} | |
14629 | nolognoteclock-out @r{don't record a note when clocking out} | |
a351880d CD |
14630 | logreschedule @r{record a timestamp when scheduling time changes} |
14631 | lognotereschedule @r{record a note when scheduling time changes} | |
14632 | nologreschedule @r{do not record when a scheduling date changes} | |
14633 | logredeadline @r{record a timestamp when deadline changes} | |
14634 | lognoteredeadline @r{record a note when deadline changes} | |
14635 | nologredeadline @r{do not record when a deadline date changes} | |
ed21c5c8 CD |
14636 | logrefile @r{record a timestamp when refiling} |
14637 | lognoterefile @r{record a note when refiling} | |
14638 | nologrefile @r{do not record when refiling} | |
4009494e | 14639 | @end example |
c8d0cf5c CD |
14640 | @vindex org-hide-leading-stars |
14641 | @vindex org-odd-levels-only | |
b349f79f CD |
14642 | Here are the options for hiding leading stars in outline headings, and for |
14643 | indenting outlines. The corresponding variables are | |
14644 | @code{org-hide-leading-stars} and @code{org-odd-levels-only}, both with a | |
14645 | default setting @code{nil} (meaning @code{showstars} and @code{oddeven}). | |
4009494e GM |
14646 | @cindex @code{hidestars}, STARTUP keyword |
14647 | @cindex @code{showstars}, STARTUP keyword | |
14648 | @cindex @code{odd}, STARTUP keyword | |
14649 | @cindex @code{even}, STARTUP keyword | |
14650 | @example | |
14651 | hidestars @r{make all but one of the stars starting a headline invisible.} | |
14652 | showstars @r{show all stars starting a headline} | |
b349f79f CD |
14653 | indent @r{virtual indentation according to outline level} |
14654 | noindent @r{no virtual indentation according to outline level} | |
4009494e GM |
14655 | odd @r{allow only odd outline levels (1,3,...)} |
14656 | oddeven @r{allow all outline levels} | |
14657 | @end example | |
c8d0cf5c CD |
14658 | @vindex org-put-time-stamp-overlays |
14659 | @vindex org-time-stamp-overlay-formats | |
14660 | To turn on custom format overlays over timestamps (variables | |
4009494e GM |
14661 | @code{org-put-time-stamp-overlays} and |
14662 | @code{org-time-stamp-overlay-formats}), use | |
14663 | @cindex @code{customtime}, STARTUP keyword | |
14664 | @example | |
14665 | customtime @r{overlay custom time format} | |
14666 | @end example | |
c8d0cf5c | 14667 | @vindex constants-unit-system |
4009494e GM |
14668 | The following options influence the table spreadsheet (variable |
14669 | @code{constants-unit-system}). | |
14670 | @cindex @code{constcgs}, STARTUP keyword | |
14671 | @cindex @code{constSI}, STARTUP keyword | |
14672 | @example | |
14673 | constcgs @r{@file{constants.el} should use the c-g-s unit system} | |
14674 | constSI @r{@file{constants.el} should use the SI unit system} | |
14675 | @end example | |
c8d0cf5c CD |
14676 | @vindex org-footnote-define-inline |
14677 | @vindex org-footnote-auto-label | |
14678 | @vindex org-footnote-auto-adjust | |
55e0839d | 14679 | To influence footnote settings, use the following keywords. The |
c8d0cf5c CD |
14680 | corresponding variables are @code{org-footnote-define-inline}, |
14681 | @code{org-footnote-auto-label}, and @code{org-footnote-auto-adjust}. | |
55e0839d | 14682 | @cindex @code{fninline}, STARTUP keyword |
c8d0cf5c | 14683 | @cindex @code{nofninline}, STARTUP keyword |
55e0839d CD |
14684 | @cindex @code{fnlocal}, STARTUP keyword |
14685 | @cindex @code{fnprompt}, STARTUP keyword | |
14686 | @cindex @code{fnauto}, STARTUP keyword | |
14687 | @cindex @code{fnconfirm}, STARTUP keyword | |
14688 | @cindex @code{fnplain}, STARTUP keyword | |
c8d0cf5c CD |
14689 | @cindex @code{fnadjust}, STARTUP keyword |
14690 | @cindex @code{nofnadjust}, STARTUP keyword | |
55e0839d CD |
14691 | @example |
14692 | fninline @r{define footnotes inline} | |
14693 | fnnoinline @r{define footnotes in separate section} | |
14694 | fnlocal @r{define footnotes near first reference, but not inline} | |
14695 | fnprompt @r{prompt for footnote labels} | |
ce57c2fe | 14696 | fnauto @r{create @code{[fn:1]}-like labels automatically (default)} |
55e0839d | 14697 | fnconfirm @r{offer automatic label for editing or confirmation} |
ce57c2fe | 14698 | fnplain @r{create @code{[1]}-like labels automatically} |
c8d0cf5c CD |
14699 | fnadjust @r{automatically renumber and sort footnotes} |
14700 | nofnadjust @r{do not renumber and sort automatically} | |
14701 | @end example | |
14702 | @cindex org-hide-block-startup | |
ce57c2fe | 14703 | To hide blocks on startup, use these keywords. The corresponding variable is |
c8d0cf5c CD |
14704 | @code{org-hide-block-startup}. |
14705 | @cindex @code{hideblocks}, STARTUP keyword | |
14706 | @cindex @code{nohideblocks}, STARTUP keyword | |
14707 | @example | |
14708 | hideblocks @r{Hide all begin/end blocks on startup} | |
14709 | nohideblocks @r{Do not hide blocks on startup} | |
55e0839d | 14710 | @end example |
86fbb8ca | 14711 | @cindex org-pretty-entities |
acedf35c | 14712 | The display of entities as UTF-8 characters is governed by the variable |
86fbb8ca CD |
14713 | @code{org-pretty-entities} and the keywords |
14714 | @cindex @code{entitiespretty}, STARTUP keyword | |
14715 | @cindex @code{entitiesplain}, STARTUP keyword | |
14716 | @example | |
acedf35c | 14717 | entitiespretty @r{Show entities as UTF-8 characters where possible} |
86fbb8ca CD |
14718 | entitiesplain @r{Leave entities plain} |
14719 | @end example | |
4009494e | 14720 | @item #+TAGS: TAG1(c1) TAG2(c2) |
c8d0cf5c | 14721 | @vindex org-tag-alist |
cad1d376 | 14722 | These lines (several such lines are allowed) specify the valid tags in |
4009494e GM |
14723 | this file, and (potentially) the corresponding @emph{fast tag selection} |
14724 | keys. The corresponding variable is @code{org-tag-alist}. | |
14725 | @item #+TBLFM: | |
14726 | This line contains the formulas for the table directly above the line. | |
c8d0cf5c | 14727 | @item #+TITLE:, #+AUTHOR:, #+EMAIL:, #+LANGUAGE:, #+TEXT:, #+DATE:, |
86fbb8ca CD |
14728 | @itemx #+OPTIONS:, #+BIND:, #+XSLT:, |
14729 | @itemx #+DESCRIPTION:, #+KEYWORDS:, | |
c8d0cf5c CD |
14730 | @itemx #+LATEX_HEADER:, #+STYLE:, #+LINK_UP:, #+LINK_HOME:, |
14731 | @itemx #+EXPORT_SELECT_TAGS:, #+EXPORT_EXCLUDE_TAGS: | |
4009494e GM |
14732 | These lines provide settings for exporting files. For more details see |
14733 | @ref{Export options}. | |
c8d0cf5c CD |
14734 | @item #+TODO: #+SEQ_TODO: #+TYP_TODO: |
14735 | @vindex org-todo-keywords | |
4009494e | 14736 | These lines set the TODO keywords and their interpretation in the |
c8d0cf5c | 14737 | current file. The corresponding variable is @code{org-todo-keywords}. |
4009494e GM |
14738 | @end table |
14739 | ||
14740 | @node The very busy C-c C-c key, Clean view, In-buffer settings, Miscellaneous | |
14741 | @section The very busy C-c C-c key | |
14742 | @kindex C-c C-c | |
14743 | @cindex C-c C-c, overview | |
14744 | ||
a7808fba | 14745 | The key @kbd{C-c C-c} has many purposes in Org, which are all |
4009494e GM |
14746 | mentioned scattered throughout this manual. One specific function of |
14747 | this key is to add @emph{tags} to a headline (@pxref{Tags}). In many | |
c8d0cf5c CD |
14748 | other circumstances it means something like @emph{``Hey Org, look |
14749 | here and update according to what you see here''}. Here is a summary of | |
4009494e GM |
14750 | what this means in different contexts. |
14751 | ||
14752 | @itemize @minus | |
14753 | @item | |
14754 | If there are highlights in the buffer from the creation of a sparse | |
14755 | tree, or from clock display, remove these highlights. | |
14756 | @item | |
14757 | If the cursor is in one of the special @code{#+KEYWORD} lines, this | |
14758 | triggers scanning the buffer for these lines and updating the | |
28a16a1b | 14759 | information. |
4009494e GM |
14760 | @item |
14761 | If the cursor is inside a table, realign the table. This command | |
14762 | works even if the automatic table editor has been turned off. | |
14763 | @item | |
14764 | If the cursor is on a @code{#+TBLFM} line, re-apply the formulas to | |
14765 | the entire table. | |
14766 | @item | |
86fbb8ca | 14767 | If the current buffer is a capture buffer, close the note and file it. |
4009494e GM |
14768 | With a prefix argument, file it, without further interaction, to the |
14769 | default location. | |
14770 | @item | |
14771 | If the cursor is on a @code{<<<target>>>}, update radio targets and | |
14772 | corresponding links in this buffer. | |
14773 | @item | |
14774 | If the cursor is in a property line or at the start or end of a property | |
14775 | drawer, offer property commands. | |
14776 | @item | |
55e0839d CD |
14777 | If the cursor is at a footnote reference, go to the corresponding |
14778 | definition, and vice versa. | |
14779 | @item | |
6eb02347 CD |
14780 | If the cursor is on a statistics cookie, update it. |
14781 | @item | |
4009494e GM |
14782 | If the cursor is in a plain list item with a checkbox, toggle the status |
14783 | of the checkbox. | |
14784 | @item | |
14785 | If the cursor is on a numbered item in a plain list, renumber the | |
14786 | ordered list. | |
dbc28aaa | 14787 | @item |
c8d0cf5c | 14788 | If the cursor is on the @code{#+BEGIN} line of a dynamic block, the |
dbc28aaa | 14789 | block is updated. |
e66ba1df BG |
14790 | @item |
14791 | If the cursor is at a timestamp, fix the day name in the timestamp. | |
4009494e GM |
14792 | @end itemize |
14793 | ||
14794 | @node Clean view, TTY keys, The very busy C-c C-c key, Miscellaneous | |
14795 | @section A cleaner outline view | |
14796 | @cindex hiding leading stars | |
b349f79f CD |
14797 | @cindex dynamic indentation |
14798 | @cindex odd-levels-only outlines | |
4009494e GM |
14799 | @cindex clean outline view |
14800 | ||
c8d0cf5c CD |
14801 | Some people find it noisy and distracting that the Org headlines start with a |
14802 | potentially large number of stars, and that text below the headlines is not | |
6eb02347 CD |
14803 | indented. While this is no problem when writing a @emph{book-like} document |
14804 | where the outline headings are really section headings, in a more | |
14805 | @emph{list-oriented} outline, indented structure is a lot cleaner: | |
4009494e GM |
14806 | |
14807 | @example | |
b349f79f CD |
14808 | @group |
14809 | * Top level headline | * Top level headline | |
14810 | ** Second level | * Second level | |
14811 | *** 3rd level | * 3rd level | |
14812 | some text | some text | |
14813 | *** 3rd level | * 3rd level | |
14814 | more text | more text | |
14815 | * Another top level headline | * Another top level headline | |
14816 | @end group | |
4009494e GM |
14817 | @end example |
14818 | ||
14819 | @noindent | |
86fbb8ca CD |
14820 | |
14821 | If you are using at least Emacs 23.2@footnote{Emacs 23.1 can actually crash | |
14822 | with @code{org-indent-mode}} and version 6.29 of Org, this kind of view can | |
14823 | be achieved dynamically at display time using @code{org-indent-mode}. In | |
14824 | this minor mode, all lines are prefixed for display with the necessary amount | |
14825 | of space@footnote{@code{org-indent-mode} also sets the @code{wrap-prefix} | |
14826 | property, such that @code{visual-line-mode} (or purely setting | |
14827 | @code{word-wrap}) wraps long lines (including headlines) correctly indented. | |
14828 | }. Also headlines are prefixed with additional stars, so that the amount of | |
14829 | indentation shifts by two@footnote{See the variable | |
ed21c5c8 CD |
14830 | @code{org-indent-indentation-per-level}.} spaces per level. All headline |
14831 | stars but the last one are made invisible using the @code{org-hide} | |
14832 | face@footnote{Turning on @code{org-indent-mode} sets | |
14833 | @code{org-hide-leading-stars} to @code{t} and @code{org-adapt-indentation} to | |
14834 | @code{nil}.} - see below under @samp{2.} for more information on how this | |
14835 | works. You can turn on @code{org-indent-mode} for all files by customizing | |
14836 | the variable @code{org-startup-indented}, or you can turn it on for | |
14837 | individual files using | |
c8d0cf5c CD |
14838 | |
14839 | @example | |
14840 | #+STARTUP: indent | |
14841 | @end example | |
14842 | ||
acedf35c | 14843 | If you want a similar effect in an earlier version of Emacs and/or Org, or if |
c8d0cf5c CD |
14844 | you want the indentation to be hard space characters so that the plain text |
14845 | file looks as similar as possible to the Emacs display, Org supports you in | |
14846 | the following way: | |
4009494e | 14847 | |
b349f79f | 14848 | @enumerate |
96c8522a | 14849 | @item |
b349f79f CD |
14850 | @emph{Indentation of text below headlines}@* |
14851 | You may indent text below each headline to make the left boundary line up | |
14852 | with the headline, like | |
4009494e | 14853 | |
b349f79f CD |
14854 | @example |
14855 | *** 3rd level | |
14856 | more text, now indented | |
14857 | @end example | |
14858 | ||
c8d0cf5c CD |
14859 | @vindex org-adapt-indentation |
14860 | Org supports this with paragraph filling, line wrapping, and structure | |
14861 | editing@footnote{See also the variable @code{org-adapt-indentation}.}, | |
14862 | preserving or adapting the indentation as appropriate. | |
b349f79f CD |
14863 | |
14864 | @item | |
c8d0cf5c | 14865 | @vindex org-hide-leading-stars |
b349f79f CD |
14866 | @emph{Hiding leading stars}@* You can modify the display in such a way that |
14867 | all leading stars become invisible. To do this in a global way, configure | |
14868 | the variable @code{org-hide-leading-stars} or change this on a per-file basis | |
14869 | with | |
4009494e GM |
14870 | |
14871 | @example | |
4009494e | 14872 | #+STARTUP: hidestars |
c8d0cf5c | 14873 | #+STARTUP: showstars |
4009494e GM |
14874 | @end example |
14875 | ||
b349f79f | 14876 | With hidden stars, the tree becomes: |
4009494e GM |
14877 | |
14878 | @example | |
b349f79f | 14879 | @group |
4009494e GM |
14880 | * Top level headline |
14881 | * Second level | |
14882 | * 3rd level | |
b349f79f CD |
14883 | ... |
14884 | @end group | |
4009494e GM |
14885 | @end example |
14886 | ||
14887 | @noindent | |
c8d0cf5c CD |
14888 | @vindex org-hide @r{(face)} |
14889 | The leading stars are not truly replaced by whitespace, they are only | |
14890 | fontified with the face @code{org-hide} that uses the background color as | |
14891 | font color. If you are not using either white or black background, you may | |
14892 | have to customize this face to get the wanted effect. Another possibility is | |
14893 | to set this font such that the extra stars are @i{almost} invisible, for | |
14894 | example using the color @code{grey90} on a white background. | |
4009494e | 14895 | |
b349f79f | 14896 | @item |
c8d0cf5c | 14897 | @vindex org-odd-levels-only |
b349f79f CD |
14898 | Things become cleaner still if you skip all the even levels and use only odd |
14899 | levels 1, 3, 5..., effectively adding two stars to go from one outline level | |
c8d0cf5c CD |
14900 | to the next@footnote{When you need to specify a level for a property search |
14901 | or refile targets, @samp{LEVEL=2} will correspond to 3 stars, etc@.}. In this | |
14902 | way we get the outline view shown at the beginning of this section. In order | |
14903 | to make the structure editing and export commands handle this convention | |
14904 | correctly, configure the variable @code{org-odd-levels-only}, or set this on | |
14905 | a per-file basis with one of the following lines: | |
4009494e GM |
14906 | |
14907 | @example | |
14908 | #+STARTUP: odd | |
14909 | #+STARTUP: oddeven | |
14910 | @end example | |
14911 | ||
a7808fba | 14912 | You can convert an Org file from single-star-per-level to the |
4009494e GM |
14913 | double-star-per-level convention with @kbd{M-x org-convert-to-odd-levels |
14914 | RET} in that file. The reverse operation is @kbd{M-x | |
14915 | org-convert-to-oddeven-levels}. | |
b349f79f | 14916 | @end enumerate |
4009494e GM |
14917 | |
14918 | @node TTY keys, Interaction, Clean view, Miscellaneous | |
a7808fba CD |
14919 | @section Using Org on a tty |
14920 | @cindex tty key bindings | |
4009494e | 14921 | |
c8d0cf5c | 14922 | Because Org contains a large number of commands, by default many of |
a7808fba | 14923 | Org's core commands are bound to keys that are generally not |
dbc28aaa CD |
14924 | accessible on a tty, such as the cursor keys (@key{left}, @key{right}, |
14925 | @key{up}, @key{down}), @key{TAB} and @key{RET}, in particular when used | |
14926 | together with modifiers like @key{Meta} and/or @key{Shift}. To access | |
14927 | these commands on a tty when special keys are unavailable, the following | |
14928 | alternative bindings can be used. The tty bindings below will likely be | |
14929 | more cumbersome; you may find for some of the bindings below that a | |
c8d0cf5c CD |
14930 | customized workaround suits you better. For example, changing a timestamp |
14931 | is really only fun with @kbd{S-@key{cursor}} keys, whereas on a | |
dbc28aaa | 14932 | tty you would rather use @kbd{C-c .} to re-insert the timestamp. |
4009494e | 14933 | |
17673adf | 14934 | @multitable @columnfractions 0.15 0.2 0.1 0.2 |
86fbb8ca CD |
14935 | @item @b{Default} @tab @b{Alternative 1} @tab @b{Speed key} @tab @b{Alternative 2} |
14936 | @item @kbd{S-@key{TAB}} @tab @kbd{C-u @key{TAB}} @tab @kbd{C} @tab | |
14937 | @item @kbd{M-@key{left}} @tab @kbd{C-c C-x l} @tab @kbd{l} @tab @kbd{@key{Esc} @key{left}} | |
14938 | @item @kbd{M-S-@key{left}} @tab @kbd{C-c C-x L} @tab @kbd{L} @tab | |
17673adf | 14939 | @item @kbd{M-@key{right}} @tab @kbd{C-c C-x r} @tab @kbd{r} @tab @kbd{@key{Esc} @key{right}} |
86fbb8ca CD |
14940 | @item @kbd{M-S-@key{right}} @tab @kbd{C-c C-x R} @tab @kbd{R} @tab |
14941 | @item @kbd{M-@key{up}} @tab @kbd{C-c C-x u} @tab @kbd{ } @tab @kbd{@key{Esc} @key{up}} | |
14942 | @item @kbd{M-S-@key{up}} @tab @kbd{C-c C-x U} @tab @kbd{U} @tab | |
17673adf | 14943 | @item @kbd{M-@key{down}} @tab @kbd{C-c C-x d} @tab @kbd{ } @tab @kbd{@key{Esc} @key{down}} |
86fbb8ca | 14944 | @item @kbd{M-S-@key{down}} @tab @kbd{C-c C-x D} @tab @kbd{D} @tab |
17673adf CD |
14945 | @item @kbd{S-@key{RET}} @tab @kbd{C-c C-x c} @tab @kbd{ } @tab |
14946 | @item @kbd{M-@key{RET}} @tab @kbd{C-c C-x m} @tab @kbd{ } @tab @kbd{@key{Esc} @key{RET}} | |
14947 | @item @kbd{M-S-@key{RET}} @tab @kbd{C-c C-x M} @tab @kbd{ } @tab | |
14948 | @item @kbd{S-@key{left}} @tab @kbd{C-c @key{left}} @tab @kbd{ } @tab | |
14949 | @item @kbd{S-@key{right}} @tab @kbd{C-c @key{right}} @tab @kbd{ } @tab | |
14950 | @item @kbd{S-@key{up}} @tab @kbd{C-c @key{up}} @tab @kbd{ } @tab | |
14951 | @item @kbd{S-@key{down}} @tab @kbd{C-c @key{down}} @tab @kbd{ } @tab | |
14952 | @item @kbd{C-S-@key{left}} @tab @kbd{C-c C-x @key{left}} @tab @kbd{ } @tab | |
14953 | @item @kbd{C-S-@key{right}} @tab @kbd{C-c C-x @key{right}} @tab @kbd{ } @tab | |
4009494e GM |
14954 | @end multitable |
14955 | ||
c8d0cf5c | 14956 | |
ce57c2fe | 14957 | @node Interaction, org-crypt.el, TTY keys, Miscellaneous |
4009494e GM |
14958 | @section Interaction with other packages |
14959 | @cindex packages, interaction with other | |
a7808fba | 14960 | Org lives in the world of GNU Emacs and interacts in various ways |
4009494e GM |
14961 | with other code out there. |
14962 | ||
14963 | @menu | |
c0468714 GM |
14964 | * Cooperation:: Packages Org cooperates with |
14965 | * Conflicts:: Packages that lead to conflicts | |
4009494e GM |
14966 | @end menu |
14967 | ||
14968 | @node Cooperation, Conflicts, Interaction, Interaction | |
a7808fba | 14969 | @subsection Packages that Org cooperates with |
4009494e GM |
14970 | |
14971 | @table @asis | |
14972 | @cindex @file{calc.el} | |
c8d0cf5c | 14973 | @cindex Gillespie, Dave |
4009494e | 14974 | @item @file{calc.el} by Dave Gillespie |
a7808fba CD |
14975 | Org uses the Calc package for implementing spreadsheet |
14976 | functionality in its tables (@pxref{The spreadsheet}). Org | |
14977 | checks for the availability of Calc by looking for the function | |
c8d0cf5c | 14978 | @code{calc-eval} which will have been autoloaded during setup if Calc has |
a7808fba | 14979 | been installed properly. As of Emacs 22, Calc is part of the Emacs |
4009494e | 14980 | distribution. Another possibility for interaction between the two |
ce57c2fe | 14981 | packages is using Calc for embedded calculations. @xref{Embedded Mode, |
153ae947 | 14982 | , Embedded Mode, calc, GNU Emacs Calc Manual}. |
4009494e | 14983 | @item @file{constants.el} by Carsten Dominik |
c8d0cf5c CD |
14984 | @cindex @file{constants.el} |
14985 | @cindex Dominik, Carsten | |
14986 | @vindex org-table-formula-constants | |
4009494e GM |
14987 | In a table formula (@pxref{The spreadsheet}), it is possible to use |
14988 | names for natural constants or units. Instead of defining your own | |
14989 | constants in the variable @code{org-table-formula-constants}, install | |
14990 | the @file{constants} package which defines a large number of constants | |
14991 | and units, and lets you use unit prefixes like @samp{M} for | |
c8d0cf5c | 14992 | @samp{Mega}, etc@. You will need version 2.0 of this package, available |
ce57c2fe | 14993 | at @url{http://www.astro.uva.nl/~dominik/Tools}. Org checks for |
4009494e GM |
14994 | the function @code{constants-get}, which has to be autoloaded in your |
14995 | setup. See the installation instructions in the file | |
14996 | @file{constants.el}. | |
14997 | @item @file{cdlatex.el} by Carsten Dominik | |
14998 | @cindex @file{cdlatex.el} | |
c8d0cf5c | 14999 | @cindex Dominik, Carsten |
e66ba1df | 15000 | Org mode can make use of the CD@LaTeX{} package to efficiently enter |
acedf35c | 15001 | @LaTeX{} fragments into Org files. See @ref{CDLaTeX mode}. |
dbc28aaa CD |
15002 | @item @file{imenu.el} by Ake Stenhoff and Lars Lindberg |
15003 | @cindex @file{imenu.el} | |
e66ba1df | 15004 | Imenu allows menu access to an index of items in a file. Org mode |
c8d0cf5c | 15005 | supports Imenu---all you need to do to get the index is the following: |
dbc28aaa | 15006 | @lisp |
28a16a1b | 15007 | (add-hook 'org-mode-hook |
a7808fba | 15008 | (lambda () (imenu-add-to-menubar "Imenu"))) |
dbc28aaa | 15009 | @end lisp |
c8d0cf5c CD |
15010 | @vindex org-imenu-depth |
15011 | By default the index is two levels deep---you can modify the depth using | |
dbc28aaa | 15012 | the option @code{org-imenu-depth}. |
4009494e GM |
15013 | @item @file{remember.el} by John Wiegley |
15014 | @cindex @file{remember.el} | |
c8d0cf5c | 15015 | @cindex Wiegley, John |
86fbb8ca | 15016 | Org used to use this package for capture, but no longer does. |
dbc28aaa CD |
15017 | @item @file{speedbar.el} by Eric M. Ludlam |
15018 | @cindex @file{speedbar.el} | |
c8d0cf5c | 15019 | @cindex Ludlam, Eric M. |
dbc28aaa | 15020 | Speedbar is a package that creates a special frame displaying files and |
e66ba1df | 15021 | index items in files. Org mode supports Speedbar and allows you to |
c8d0cf5c | 15022 | drill into Org files directly from the Speedbar. It also allows you to |
dbc28aaa | 15023 | restrict the scope of agenda commands to a file or a subtree by using |
a7808fba | 15024 | the command @kbd{<} in the Speedbar frame. |
4009494e GM |
15025 | @cindex @file{table.el} |
15026 | @item @file{table.el} by Takaaki Ota | |
15027 | @kindex C-c C-c | |
15028 | @cindex table editor, @file{table.el} | |
15029 | @cindex @file{table.el} | |
c8d0cf5c | 15030 | @cindex Ota, Takaaki |
4009494e | 15031 | |
ed21c5c8 CD |
15032 | Complex ASCII tables with automatic line wrapping, column- and row-spanning, |
15033 | and alignment can be created using the Emacs table package by Takaaki Ota | |
15034 | (@uref{http://sourceforge.net/projects/table}, and also part of Emacs 22). | |
e66ba1df BG |
15035 | Org mode will recognize these tables and export them properly. Because of |
15036 | interference with other Org mode functionality, you unfortunately cannot edit | |
ed21c5c8 CD |
15037 | these tables directly in the buffer. Instead, you need to use the command |
15038 | @kbd{C-c '} to edit them, similar to source code snippets. | |
4009494e GM |
15039 | |
15040 | @table @kbd | |
acedf35c | 15041 | @orgcmd{C-c ',org-edit-special} |
ed21c5c8 | 15042 | Edit a @file{table.el} table. Works when the cursor is in a table.el table. |
4009494e | 15043 | @c |
acedf35c | 15044 | @orgcmd{C-c ~,org-table-create-with-table.el} |
c8d0cf5c | 15045 | Insert a @file{table.el} table. If there is already a table at point, this |
e66ba1df | 15046 | command converts it between the @file{table.el} format and the Org mode |
4009494e GM |
15047 | format. See the documentation string of the command |
15048 | @code{org-convert-table} for the restrictions under which this is | |
15049 | possible. | |
15050 | @end table | |
ed21c5c8 | 15051 | @file{table.el} is part of Emacs since Emacs 22. |
4009494e | 15052 | @item @file{footnote.el} by Steven L. Baur |
c8d0cf5c CD |
15053 | @cindex @file{footnote.el} |
15054 | @cindex Baur, Steven L. | |
e66ba1df BG |
15055 | Org mode recognizes numerical footnotes as provided by this package. |
15056 | However, Org mode also has its own footnote support (@pxref{Footnotes}), | |
55e0839d | 15057 | which makes using @file{footnote.el} unnecessary. |
4009494e GM |
15058 | @end table |
15059 | ||
15060 | @node Conflicts, , Cooperation, Interaction | |
e66ba1df | 15061 | @subsection Packages that lead to conflicts with Org mode |
4009494e GM |
15062 | |
15063 | @table @asis | |
15064 | ||
3da3282e | 15065 | @cindex @code{shift-selection-mode} |
c8d0cf5c | 15066 | @vindex org-support-shift-select |
3da3282e CD |
15067 | In Emacs 23, @code{shift-selection-mode} is on by default, meaning that |
15068 | cursor motions combined with the shift key should start or enlarge regions. | |
15069 | This conflicts with the use of @kbd{S-@key{cursor}} commands in Org to change | |
15070 | timestamps, TODO keywords, priorities, and item bullet types if the cursor is | |
15071 | at such a location. By default, @kbd{S-@key{cursor}} commands outside | |
15072 | special contexts don't do anything, but you can customize the variable | |
e66ba1df | 15073 | @code{org-support-shift-select}. Org mode then tries to accommodate shift |
3da3282e CD |
15074 | selection by (i) using it outside of the special contexts where special |
15075 | commands apply, and by (ii) extending an existing active region even if the | |
15076 | cursor moves across a special context. | |
4009494e | 15077 | |
4009494e | 15078 | @item @file{CUA.el} by Kim. F. Storm |
c8d0cf5c CD |
15079 | @cindex @file{CUA.el} |
15080 | @cindex Storm, Kim. F. | |
15081 | @vindex org-replace-disputed-keys | |
3da3282e | 15082 | Key bindings in Org conflict with the @kbd{S-<cursor>} keys used by CUA mode |
c8d0cf5c | 15083 | (as well as @code{pc-select-mode} and @code{s-region-mode}) to select and extend the |
3da3282e CD |
15084 | region. In fact, Emacs 23 has this built-in in the form of |
15085 | @code{shift-selection-mode}, see previous paragraph. If you are using Emacs | |
c8d0cf5c | 15086 | 23, you probably don't want to use another package for this purpose. However, |
3da3282e | 15087 | if you prefer to leave these keys to a different package while working in |
e66ba1df | 15088 | Org mode, configure the variable @code{org-replace-disputed-keys}. When set, |
3da3282e CD |
15089 | Org will move the following key bindings in Org files, and in the agenda |
15090 | buffer (but not during date selection). | |
4009494e GM |
15091 | |
15092 | @example | |
ce57c2fe BG |
15093 | S-UP @result{} M-p S-DOWN @result{} M-n |
15094 | S-LEFT @result{} M-- S-RIGHT @result{} M-+ | |
15095 | C-S-LEFT @result{} M-S-- C-S-RIGHT @result{} M-S-+ | |
4009494e GM |
15096 | @end example |
15097 | ||
c8d0cf5c | 15098 | @vindex org-disputed-keys |
4009494e GM |
15099 | Yes, these are unfortunately more difficult to remember. If you want |
15100 | to have other replacement keys, look at the variable | |
15101 | @code{org-disputed-keys}. | |
3da3282e | 15102 | |
c8d0cf5c CD |
15103 | @item @file{yasnippet.el} |
15104 | @cindex @file{yasnippet.el} | |
ce57c2fe | 15105 | The way Org mode binds the TAB key (binding to @code{[tab]} instead of |
acedf35c | 15106 | @code{"\t"}) overrules YASnippet's access to this key. The following code |
c8d0cf5c CD |
15107 | fixed this problem: |
15108 | ||
15109 | @lisp | |
15110 | (add-hook 'org-mode-hook | |
c0468714 GM |
15111 | (lambda () |
15112 | (org-set-local 'yas/trigger-key [tab]) | |
e66ba1df | 15113 | (define-key yas/keymap [tab] 'yas/next-field-or-maybe-expand))) |
c8d0cf5c CD |
15114 | @end lisp |
15115 | ||
ce57c2fe BG |
15116 | The latest version of yasnippet doesn't play well with Org mode. If the |
15117 | above code does not fix the conflict, start by defining the following | |
15118 | function: | |
15119 | ||
15120 | @lisp | |
15121 | (defun yas/org-very-safe-expand () | |
15122 | (let ((yas/fallback-behavior 'return-nil)) (yas/expand))) | |
15123 | @end lisp | |
15124 | ||
15125 | Then, tell Org mode what to do with the new function: | |
15126 | ||
15127 | @lisp | |
15128 | (add-hook 'org-mode-hook | |
15129 | (lambda () | |
15130 | (make-variable-buffer-local 'yas/trigger-key) | |
15131 | (setq yas/trigger-key [tab]) | |
15132 | (add-to-list 'org-tab-first-hook 'yas/org-very-safe-expand) | |
15133 | (define-key yas/keymap [tab] 'yas/next-field))) | |
15134 | @end lisp | |
15135 | ||
4009494e GM |
15136 | @item @file{windmove.el} by Hovav Shacham |
15137 | @cindex @file{windmove.el} | |
c8d0cf5c | 15138 | This package also uses the @kbd{S-<cursor>} keys, so everything written |
86fbb8ca | 15139 | in the paragraph above about CUA mode also applies here. If you want make |
e66ba1df | 15140 | the windmove function active in locations where Org mode does not have |
86fbb8ca CD |
15141 | special functionality on @kbd{S-@key{cursor}}, add this to your |
15142 | configuration: | |
15143 | ||
15144 | @lisp | |
15145 | ;; Make windmove work in org-mode: | |
15146 | (add-hook 'org-shiftup-final-hook 'windmove-up) | |
15147 | (add-hook 'org-shiftleft-final-hook 'windmove-left) | |
15148 | (add-hook 'org-shiftdown-final-hook 'windmove-down) | |
15149 | (add-hook 'org-shiftright-final-hook 'windmove-right) | |
15150 | @end lisp | |
4009494e | 15151 | |
a351880d CD |
15152 | @item @file{viper.el} by Michael Kifer |
15153 | @cindex @file{viper.el} | |
15154 | @kindex C-c / | |
15155 | Viper uses @kbd{C-c /} and therefore makes this key not access the | |
e66ba1df | 15156 | corresponding Org mode command @code{org-sparse-tree}. You need to find |
a351880d CD |
15157 | another key for this command, or override the key in |
15158 | @code{viper-vi-global-user-map} with | |
15159 | ||
15160 | @lisp | |
15161 | (define-key viper-vi-global-user-map "C-c /" 'org-sparse-tree) | |
15162 | @end lisp | |
15163 | ||
4009494e GM |
15164 | @end table |
15165 | ||
ce57c2fe BG |
15166 | @node org-crypt.el, , Interaction, Miscellaneous |
15167 | @section org-crypt.el | |
15168 | @cindex @file{org-crypt.el} | |
15169 | @cindex @code{org-decrypt-entry} | |
15170 | ||
15171 | Org-crypt will encrypt the text of an entry, but not the headline, or | |
15172 | properties. Org-crypt uses the Emacs EasyPG library to encrypt and decrypt | |
15173 | files. | |
15174 | ||
15175 | Any text below a headline that has a @samp{:crypt:} tag will be automatically | |
15176 | be encrypted when the file is saved. If you want to use a different tag just | |
15177 | customize the @code{org-crypt-tag-matcher} setting. | |
15178 | ||
15179 | To use org-crypt it is suggested that you have the following in your | |
15180 | @file{.emacs}: | |
15181 | ||
15182 | @example | |
15183 | (require 'org-crypt) | |
15184 | (org-crypt-use-before-save-magic) | |
15185 | (setq org-tags-exclude-from-inheritance (quote ("crypt"))) | |
15186 | ||
15187 | (setq org-crypt-key nil) | |
15188 | ;; GPG key to use for encryption | |
15189 | ;; Either the Key ID or set to nil to use symmetric encryption. | |
15190 | ||
15191 | (setq auto-save-default nil) | |
15192 | ;; Auto-saving does not cooperate with org-crypt.el: so you need | |
15193 | ;; to turn it off if you plan to use org-crypt.el quite often. | |
15194 | ;; Otherwise, you'll get an (annoying) message each time you | |
15195 | ;; start Org. | |
15196 | ||
15197 | ;; To turn it off only locally, you can insert this: | |
15198 | ;; | |
15199 | ;; # -*- buffer-auto-save-file-name: nil; -*- | |
15200 | @end example | |
15201 | ||
15202 | Excluding the crypt tag from inheritance prevents already encrypted text | |
15203 | being encrypted again. | |
7006d207 CD |
15204 | |
15205 | @node Hacking, MobileOrg, Miscellaneous, Top | |
b349f79f | 15206 | @appendix Hacking |
c8d0cf5c | 15207 | @cindex hacking |
b349f79f CD |
15208 | |
15209 | This appendix covers some aspects where users can extend the functionality of | |
a7808fba | 15210 | Org. |
4009494e GM |
15211 | |
15212 | @menu | |
c0468714 GM |
15213 | * Hooks:: Who to reach into Org's internals |
15214 | * Add-on packages:: Available extensions | |
15215 | * Adding hyperlink types:: New custom link types | |
15216 | * Context-sensitive commands:: How to add functionality to such commands | |
acedf35c | 15217 | * Tables in arbitrary syntax:: Orgtbl for @LaTeX{} and other programs |
c0468714 GM |
15218 | * Dynamic blocks:: Automatically filled blocks |
15219 | * Special agenda views:: Customized views | |
c8d0cf5c | 15220 | * Extracting agenda information:: Postprocessing of agenda information |
c0468714 GM |
15221 | * Using the property API:: Writing programs that use entry properties |
15222 | * Using the mapping API:: Mapping over all or selected entries | |
4009494e GM |
15223 | @end menu |
15224 | ||
c8d0cf5c CD |
15225 | @node Hooks, Add-on packages, Hacking, Hacking |
15226 | @section Hooks | |
15227 | @cindex hooks | |
15228 | ||
15229 | Org has a large number of hook variables that can be used to add | |
15230 | functionality. This appendix about hacking is going to illustrate the | |
15231 | use of some of them. A complete list of all hooks with documentation is | |
15232 | maintained by the Worg project and can be found at | |
15233 | @uref{http://orgmode.org/worg/org-configs/org-hooks.php}. | |
15234 | ||
15235 | @node Add-on packages, Adding hyperlink types, Hooks, Hacking | |
15236 | @section Add-on packages | |
15237 | @cindex add-on packages | |
15238 | ||
15239 | A large number of add-on packages have been written by various authors. | |
15240 | These packages are not part of Emacs, but they are distributed as contributed | |
e66ba1df | 15241 | packages with the separate release available at the Org mode home page at |
c8d0cf5c CD |
15242 | @uref{http://orgmode.org}. The list of contributed packages, along with |
15243 | documentation about each package, is maintained by the Worg project at | |
15244 | @uref{http://orgmode.org/worg/org-contrib/}. | |
15245 | ||
15246 | ||
15247 | ||
15248 | @node Adding hyperlink types, Context-sensitive commands, Add-on packages, Hacking | |
4009494e GM |
15249 | @section Adding hyperlink types |
15250 | @cindex hyperlinks, adding new types | |
15251 | ||
a7808fba | 15252 | Org has a large number of hyperlink types built-in |
c8d0cf5c CD |
15253 | (@pxref{Hyperlinks}). If you would like to add new link types, Org |
15254 | provides an interface for doing so. Let's look at an example file, | |
15255 | @file{org-man.el}, that will add support for creating links like | |
a7808fba | 15256 | @samp{[[man:printf][The printf manpage]]} to show Unix manual pages inside |
c8d0cf5c | 15257 | Emacs: |
4009494e GM |
15258 | |
15259 | @lisp | |
a7808fba | 15260 | ;;; org-man.el - Support for links to manpages in Org |
4009494e GM |
15261 | |
15262 | (require 'org) | |
15263 | ||
15264 | (org-add-link-type "man" 'org-man-open) | |
15265 | (add-hook 'org-store-link-functions 'org-man-store-link) | |
15266 | ||
15267 | (defcustom org-man-command 'man | |
15268 | "The Emacs command to be used to display a man page." | |
15269 | :group 'org-link | |
15270 | :type '(choice (const man) (const woman))) | |
15271 | ||
15272 | (defun org-man-open (path) | |
15273 | "Visit the manpage on PATH. | |
15274 | PATH should be a topic that can be thrown at the man command." | |
15275 | (funcall org-man-command path)) | |
15276 | ||
15277 | (defun org-man-store-link () | |
15278 | "Store a link to a manpage." | |
15279 | (when (memq major-mode '(Man-mode woman-mode)) | |
15280 | ;; This is a man page, we do make this link | |
15281 | (let* ((page (org-man-get-page-name)) | |
15282 | (link (concat "man:" page)) | |
15283 | (description (format "Manpage for %s" page))) | |
15284 | (org-store-link-props | |
15285 | :type "man" | |
15286 | :link link | |
15287 | :description description)))) | |
15288 | ||
15289 | (defun org-man-get-page-name () | |
15290 | "Extract the page name from the buffer name." | |
15291 | ;; This works for both `Man-mode' and `woman-mode'. | |
15292 | (if (string-match " \\(\\S-+\\)\\*" (buffer-name)) | |
15293 | (match-string 1 (buffer-name)) | |
15294 | (error "Cannot create link to this man page"))) | |
15295 | ||
15296 | (provide 'org-man) | |
15297 | ||
15298 | ;;; org-man.el ends here | |
15299 | @end lisp | |
15300 | ||
15301 | @noindent | |
15302 | You would activate this new link type in @file{.emacs} with | |
15303 | ||
15304 | @lisp | |
15305 | (require 'org-man) | |
15306 | @end lisp | |
15307 | ||
15308 | @noindent | |
864c9740 | 15309 | Let's go through the file and see what it does. |
4009494e | 15310 | @enumerate |
28a16a1b | 15311 | @item |
4009494e GM |
15312 | It does @code{(require 'org)} to make sure that @file{org.el} has been |
15313 | loaded. | |
15314 | @item | |
15315 | The next line calls @code{org-add-link-type} to define a new link type | |
15316 | with prefix @samp{man}. The call also contains the name of a function | |
15317 | that will be called to follow such a link. | |
15318 | @item | |
c8d0cf5c | 15319 | @vindex org-store-link-functions |
4009494e GM |
15320 | The next line adds a function to @code{org-store-link-functions}, in |
15321 | order to allow the command @kbd{C-c l} to record a useful link in a | |
15322 | buffer displaying a man page. | |
15323 | @end enumerate | |
15324 | ||
15325 | The rest of the file defines the necessary variables and functions. | |
c8d0cf5c | 15326 | First there is a customization variable that determines which Emacs |
a7808fba | 15327 | command should be used to display man pages. There are two options, |
4009494e | 15328 | @code{man} and @code{woman}. Then the function to follow a link is |
c8d0cf5c | 15329 | defined. It gets the link path as an argument---in this case the link |
4009494e GM |
15330 | path is just a topic for the manual command. The function calls the |
15331 | value of @code{org-man-command} to display the man page. | |
15332 | ||
15333 | Finally the function @code{org-man-store-link} is defined. When you try | |
c8d0cf5c | 15334 | to store a link with @kbd{C-c l}, this function will be called to |
4009494e | 15335 | try to make a link. The function must first decide if it is supposed to |
c8d0cf5c | 15336 | create the link for this buffer type; we do this by checking the value |
4009494e | 15337 | of the variable @code{major-mode}. If not, the function must exit and |
a7808fba CD |
15338 | return the value @code{nil}. If yes, the link is created by getting the |
15339 | manual topic from the buffer name and prefixing it with the string | |
4009494e GM |
15340 | @samp{man:}. Then it must call the command @code{org-store-link-props} |
15341 | and set the @code{:type} and @code{:link} properties. Optionally you | |
15342 | can also set the @code{:description} property to provide a default for | |
a7808fba | 15343 | the link description when the link is later inserted into an Org |
4009494e GM |
15344 | buffer with @kbd{C-c C-l}. |
15345 | ||
acedf35c | 15346 | When it makes sense for your new link type, you may also define a function |
ce57c2fe | 15347 | @code{org-PREFIX-complete-link} that implements special (e.g.@: completion) |
c8d0cf5c CD |
15348 | support for inserting such a link with @kbd{C-c C-l}. Such a function should |
15349 | not accept any arguments, and return the full link with prefix. | |
15350 | ||
15351 | @node Context-sensitive commands, Tables in arbitrary syntax, Adding hyperlink types, Hacking | |
15352 | @section Context-sensitive commands | |
15353 | @cindex context-sensitive commands, hooks | |
15354 | @cindex add-ons, context-sensitive commands | |
15355 | @vindex org-ctrl-c-ctrl-c-hook | |
15356 | ||
15357 | Org has several commands that act differently depending on context. The most | |
153ae947 | 15358 | important example is the @kbd{C-c C-c} (@pxref{The very busy C-c C-c key}). |
c8d0cf5c CD |
15359 | Also the @kbd{M-cursor} and @kbd{M-S-cursor} keys have this property. |
15360 | ||
15361 | Add-ons can tap into this functionality by providing a function that detects | |
15362 | special context for that add-on and executes functionality appropriate for | |
15363 | the context. Here is an example from Dan Davison's @file{org-R.el} which | |
afe98dfa | 15364 | allows you to evaluate commands based on the @file{R} programming language |
e66ba1df | 15365 | @footnote{@file{org-R.el} has been replaced by the Org mode functionality |
afe98dfa CD |
15366 | described in @ref{Working With Source Code} and is now obsolete.}. For this |
15367 | package, special contexts are lines that start with @code{#+R:} or | |
c8d0cf5c CD |
15368 | @code{#+RR:}. |
15369 | ||
15370 | @lisp | |
15371 | (defun org-R-apply-maybe () | |
15372 | "Detect if this is context for org-R and execute R commands." | |
15373 | (if (save-excursion | |
15374 | (beginning-of-line 1) | |
15375 | (looking-at "#\\+RR?:")) | |
15376 | (progn (call-interactively 'org-R-apply) | |
15377 | t) ;; to signal that we took action | |
15378 | nil)) ;; to signal that we did not | |
15379 | ||
15380 | (add-hook 'org-ctrl-c-ctrl-c-hook 'org-R-apply-maybe) | |
15381 | @end lisp | |
15382 | ||
15383 | The function first checks if the cursor is in such a line. If that is the | |
15384 | case, @code{org-R-apply} is called and the function returns @code{t} to | |
15385 | signal that action was taken, and @kbd{C-c C-c} will stop looking for other | |
ce57c2fe BG |
15386 | contexts. If the function finds it should do nothing locally, it returns |
15387 | @code{nil} so that other, similar functions can have a try. | |
c8d0cf5c CD |
15388 | |
15389 | ||
15390 | @node Tables in arbitrary syntax, Dynamic blocks, Context-sensitive commands, Hacking | |
a7808fba | 15391 | @section Tables and lists in arbitrary syntax |
4009494e | 15392 | @cindex tables, in other modes |
dbc28aaa | 15393 | @cindex lists, in other modes |
a7808fba | 15394 | @cindex Orgtbl mode |
4009494e | 15395 | |
a7808fba | 15396 | Since Orgtbl mode can be used as a minor mode in arbitrary buffers, a |
4009494e | 15397 | frequent feature request has been to make it work with native tables in |
acedf35c | 15398 | specific languages, for example @LaTeX{}. However, this is extremely |
dbc28aaa | 15399 | hard to do in a general way, would lead to a customization nightmare, |
ce57c2fe | 15400 | and would take away much of the simplicity of the Orgtbl mode table |
dbc28aaa CD |
15401 | editor. |
15402 | ||
a7808fba | 15403 | This appendix describes a different approach. We keep the Orgtbl mode |
4009494e GM |
15404 | table in its native format (the @i{source table}), and use a custom |
15405 | function to @i{translate} the table to the correct syntax, and to | |
15406 | @i{install} it in the right location (the @i{target table}). This puts | |
15407 | the burden of writing conversion functions on the user, but it allows | |
15408 | for a very flexible system. | |
15409 | ||
86fbb8ca CD |
15410 | Bastien added the ability to do the same with lists, in Orgstruct mode. You |
15411 | can use Org's facilities to edit and structure lists by turning | |
15412 | @code{orgstruct-mode} on, then locally exporting such lists in another format | |
acedf35c | 15413 | (HTML, @LaTeX{} or Texinfo.) |
dbc28aaa CD |
15414 | |
15415 | ||
4009494e | 15416 | @menu |
c0468714 | 15417 | * Radio tables:: Sending and receiving radio tables |
e66ba1df | 15418 | * A @LaTeX{} example:: Step by step, almost a tutorial |
c0468714 GM |
15419 | * Translator functions:: Copy and modify |
15420 | * Radio lists:: Doing the same for lists | |
4009494e GM |
15421 | @end menu |
15422 | ||
e66ba1df | 15423 | @node Radio tables, A @LaTeX{} example, Tables in arbitrary syntax, Tables in arbitrary syntax |
4009494e GM |
15424 | @subsection Radio tables |
15425 | @cindex radio tables | |
15426 | ||
15427 | To define the location of the target table, you first need to create two | |
15428 | lines that are comments in the current mode, but contain magic words for | |
a7808fba | 15429 | Orgtbl mode to find. Orgtbl mode will insert the translated table |
4009494e GM |
15430 | between these lines, replacing whatever was there before. For example: |
15431 | ||
15432 | @example | |
15433 | /* BEGIN RECEIVE ORGTBL table_name */ | |
15434 | /* END RECEIVE ORGTBL table_name */ | |
15435 | @end example | |
15436 | ||
15437 | @noindent | |
15438 | Just above the source table, we put a special line that tells | |
a7808fba | 15439 | Orgtbl mode how to translate this table and where to install it. For |
4009494e | 15440 | example: |
c8d0cf5c | 15441 | @cindex #+ORGTBL |
4009494e GM |
15442 | @example |
15443 | #+ORGTBL: SEND table_name translation_function arguments.... | |
15444 | @end example | |
15445 | ||
15446 | @noindent | |
15447 | @code{table_name} is the reference name for the table that is also used | |
ce57c2fe | 15448 | in the receiver lines. @code{translation_function} is the Lisp function |
4009494e GM |
15449 | that does the translation. Furthermore, the line can contain a list of |
15450 | arguments (alternating key and value) at the end. The arguments will be | |
15451 | passed as a property list to the translation function for | |
15452 | interpretation. A few standard parameters are already recognized and | |
15453 | acted upon before the translation function is called: | |
15454 | ||
15455 | @table @code | |
15456 | @item :skip N | |
b349f79f CD |
15457 | Skip the first N lines of the table. Hlines do count as separate lines for |
15458 | this parameter! | |
15459 | ||
4009494e GM |
15460 | @item :skipcols (n1 n2 ...) |
15461 | List of columns that should be skipped. If the table has a column with | |
15462 | calculation marks, that column is automatically discarded as well. | |
15463 | Please note that the translator function sees the table @emph{after} the | |
15464 | removal of these columns, the function never knows that there have been | |
15465 | additional columns. | |
15466 | @end table | |
15467 | ||
15468 | @noindent | |
15469 | The one problem remaining is how to keep the source table in the buffer | |
15470 | without disturbing the normal workings of the file, for example during | |
acedf35c | 15471 | compilation of a C file or processing of a @LaTeX{} file. There are a |
4009494e GM |
15472 | number of different solutions: |
15473 | ||
15474 | @itemize @bullet | |
15475 | @item | |
15476 | The table could be placed in a block comment if that is supported by the | |
a7808fba | 15477 | language. For example, in C mode you could wrap the table between |
4009494e | 15478 | @samp{/*} and @samp{*/} lines. |
28a16a1b | 15479 | @item |
4009494e | 15480 | Sometimes it is possible to put the table after some kind of @i{END} |
c8d0cf5c | 15481 | statement, for example @samp{\bye} in @TeX{} and @samp{\end@{document@}} |
acedf35c | 15482 | in @LaTeX{}. |
4009494e | 15483 | @item |
c8d0cf5c | 15484 | You can just comment the table line-by-line whenever you want to process |
4009494e | 15485 | the file, and uncomment it whenever you need to edit the table. This |
c8d0cf5c CD |
15486 | only sounds tedious---the command @kbd{M-x orgtbl-toggle-comment} |
15487 | makes this comment-toggling very easy, in particular if you bind it to a | |
4009494e GM |
15488 | key. |
15489 | @end itemize | |
15490 | ||
e66ba1df | 15491 | @node A @LaTeX{} example, Translator functions, Radio tables, Tables in arbitrary syntax |
acedf35c CD |
15492 | @subsection A @LaTeX{} example of radio tables |
15493 | @cindex @LaTeX{}, and Orgtbl mode | |
4009494e | 15494 | |
acedf35c | 15495 | The best way to wrap the source table in @LaTeX{} is to use the |
4009494e GM |
15496 | @code{comment} environment provided by @file{comment.sty}. It has to be |
15497 | activated by placing @code{\usepackage@{comment@}} into the document | |
a7808fba | 15498 | header. Orgtbl mode can insert a radio table skeleton@footnote{By |
acedf35c | 15499 | default this works only for @LaTeX{}, HTML, and Texinfo. Configure the |
4009494e GM |
15500 | variable @code{orgtbl-radio-tables} to install templates for other |
15501 | modes.} with the command @kbd{M-x orgtbl-insert-radio-table}. You will | |
55e0839d | 15502 | be prompted for a table name, let's say we use @samp{salesfigures}. You |
4009494e GM |
15503 | will then get the following template: |
15504 | ||
c8d0cf5c | 15505 | @cindex #+ORGTBL, SEND |
4009494e GM |
15506 | @example |
15507 | % BEGIN RECEIVE ORGTBL salesfigures | |
15508 | % END RECEIVE ORGTBL salesfigures | |
15509 | \begin@{comment@} | |
15510 | #+ORGTBL: SEND salesfigures orgtbl-to-latex | |
15511 | | | | | |
15512 | \end@{comment@} | |
15513 | @end example | |
15514 | ||
15515 | @noindent | |
acedf35c | 15516 | @vindex @LaTeX{}-verbatim-environments |
a7808fba | 15517 | The @code{#+ORGTBL: SEND} line tells Orgtbl mode to use the function |
acedf35c | 15518 | @code{orgtbl-to-latex} to convert the table into @LaTeX{} and to put it |
4009494e | 15519 | into the receiver location with name @code{salesfigures}. You may now |
acedf35c | 15520 | fill in the table---feel free to use the spreadsheet features@footnote{If |
4009494e | 15521 | the @samp{#+TBLFM} line contains an odd number of dollar characters, |
acedf35c | 15522 | this may cause problems with font-lock in @LaTeX{} mode. As shown in the |
4009494e GM |
15523 | example you can fix this by adding an extra line inside the |
15524 | @code{comment} environment that is used to balance the dollar | |
c8d0cf5c | 15525 | expressions. If you are using AUC@TeX{} with the font-latex library, a |
4009494e GM |
15526 | much better solution is to add the @code{comment} environment to the |
15527 | variable @code{LaTeX-verbatim-environments}.}: | |
15528 | ||
15529 | @example | |
15530 | % BEGIN RECEIVE ORGTBL salesfigures | |
15531 | % END RECEIVE ORGTBL salesfigures | |
15532 | \begin@{comment@} | |
15533 | #+ORGTBL: SEND salesfigures orgtbl-to-latex | |
15534 | | Month | Days | Nr sold | per day | | |
15535 | |-------+------+---------+---------| | |
15536 | | Jan | 23 | 55 | 2.4 | | |
15537 | | Feb | 21 | 16 | 0.8 | | |
15538 | | March | 22 | 278 | 12.6 | | |
15539 | #+TBLFM: $4=$3/$2;%.1f | |
15540 | % $ (optional extra dollar to keep font-lock happy, see footnote) | |
15541 | \end@{comment@} | |
15542 | @end example | |
15543 | ||
15544 | @noindent | |
15545 | When you are done, press @kbd{C-c C-c} in the table to get the converted | |
15546 | table inserted between the two marker lines. | |
15547 | ||
55e0839d | 15548 | Now let's assume you want to make the table header by hand, because you |
c8d0cf5c CD |
15549 | want to control how columns are aligned, etc@. In this case we make sure |
15550 | that the table translator skips the first 2 lines of the source | |
ce57c2fe | 15551 | table, and tell the command to work as a @i{splice}, i.e.@: to not produce |
4009494e GM |
15552 | header and footer commands of the target table: |
15553 | ||
15554 | @example | |
15555 | \begin@{tabular@}@{lrrr@} | |
15556 | Month & \multicolumn@{1@}@{c@}@{Days@} & Nr.\ sold & per day\\ | |
15557 | % BEGIN RECEIVE ORGTBL salesfigures | |
15558 | % END RECEIVE ORGTBL salesfigures | |
15559 | \end@{tabular@} | |
15560 | % | |
15561 | \begin@{comment@} | |
15562 | #+ORGTBL: SEND salesfigures orgtbl-to-latex :splice t :skip 2 | |
15563 | | Month | Days | Nr sold | per day | | |
15564 | |-------+------+---------+---------| | |
15565 | | Jan | 23 | 55 | 2.4 | | |
15566 | | Feb | 21 | 16 | 0.8 | | |
15567 | | March | 22 | 278 | 12.6 | | |
15568 | #+TBLFM: $4=$3/$2;%.1f | |
15569 | \end@{comment@} | |
15570 | @end example | |
15571 | ||
acedf35c | 15572 | The @LaTeX{} translator function @code{orgtbl-to-latex} is already part of |
a7808fba | 15573 | Orgtbl mode. It uses a @code{tabular} environment to typeset the table |
4009494e | 15574 | and marks horizontal lines with @code{\hline}. Furthermore, it |
c8d0cf5c | 15575 | interprets the following parameters (see also @pxref{Translator functions}): |
4009494e GM |
15576 | |
15577 | @table @code | |
15578 | @item :splice nil/t | |
15579 | When set to t, return only table body lines, don't wrap them into a | |
15580 | tabular environment. Default is nil. | |
15581 | ||
15582 | @item :fmt fmt | |
c8d0cf5c | 15583 | A format to be used to wrap each field, it should contain @code{%s} for the |
4009494e GM |
15584 | original field value. For example, to wrap each field value in dollars, |
15585 | you could use @code{:fmt "$%s$"}. This may also be a property list with | |
ce57c2fe | 15586 | column numbers and formats, for example @code{:fmt (2 "$%s$" 4 "%s\\%%")}. |
a7808fba CD |
15587 | A function of one argument can be used in place of the strings; the |
15588 | function must return a formatted string. | |
4009494e GM |
15589 | |
15590 | @item :efmt efmt | |
15591 | Use this format to print numbers with exponentials. The format should | |
15592 | have @code{%s} twice for inserting mantissa and exponent, for example | |
15593 | @code{"%s\\times10^@{%s@}"}. The default is @code{"%s\\,(%s)"}. This | |
15594 | may also be a property list with column numbers and formats, for example | |
15595 | @code{:efmt (2 "$%s\\times10^@{%s@}$" 4 "$%s\\cdot10^@{%s@}$")}. After | |
15596 | @code{efmt} has been applied to a value, @code{fmt} will also be | |
a7808fba CD |
15597 | applied. Similar to @code{fmt}, functions of two arguments can be |
15598 | supplied instead of strings. | |
4009494e GM |
15599 | @end table |
15600 | ||
e66ba1df | 15601 | @node Translator functions, Radio lists, A @LaTeX{} example, Tables in arbitrary syntax |
4009494e | 15602 | @subsection Translator functions |
a7808fba | 15603 | @cindex HTML, and Orgtbl mode |
4009494e GM |
15604 | @cindex translator function |
15605 | ||
b349f79f CD |
15606 | Orgtbl mode has several translator functions built-in: @code{orgtbl-to-csv} |
15607 | (comma-separated values), @code{orgtbl-to-tsv} (TAB-separated values) | |
15608 | @code{orgtbl-to-latex}, @code{orgtbl-to-html}, and @code{orgtbl-to-texinfo}. | |
15609 | Except for @code{orgtbl-to-html}@footnote{The HTML translator uses the same | |
15610 | code that produces tables during HTML export.}, these all use a generic | |
15611 | translator, @code{orgtbl-to-generic}. For example, @code{orgtbl-to-latex} | |
15612 | itself is a very short function that computes the column definitions for the | |
15613 | @code{tabular} environment, defines a few field and line separators and then | |
c8d0cf5c | 15614 | hands processing over to the generic translator. Here is the entire code: |
4009494e GM |
15615 | |
15616 | @lisp | |
15617 | @group | |
15618 | (defun orgtbl-to-latex (table params) | |
a7808fba | 15619 | "Convert the Orgtbl mode TABLE to LaTeX." |
4009494e GM |
15620 | (let* ((alignment (mapconcat (lambda (x) (if x "r" "l")) |
15621 | org-table-last-alignment "")) | |
15622 | (params2 | |
15623 | (list | |
15624 | :tstart (concat "\\begin@{tabular@}@{" alignment "@}") | |
15625 | :tend "\\end@{tabular@}" | |
15626 | :lstart "" :lend " \\\\" :sep " & " | |
15627 | :efmt "%s\\,(%s)" :hline "\\hline"))) | |
15628 | (orgtbl-to-generic table (org-combine-plists params2 params)))) | |
15629 | @end group | |
15630 | @end lisp | |
15631 | ||
15632 | As you can see, the properties passed into the function (variable | |
15633 | @var{PARAMS}) are combined with the ones newly defined in the function | |
ce57c2fe | 15634 | (variable @var{PARAMS2}). The ones passed into the function (i.e.@: the |
4009494e | 15635 | ones set by the @samp{ORGTBL SEND} line) take precedence. So if you |
acedf35c | 15636 | would like to use the @LaTeX{} translator, but wanted the line endings to |
4009494e GM |
15637 | be @samp{\\[2mm]} instead of the default @samp{\\}, you could just |
15638 | overrule the default with | |
15639 | ||
15640 | @example | |
15641 | #+ORGTBL: SEND test orgtbl-to-latex :lend " \\\\[2mm]" | |
15642 | @end example | |
15643 | ||
15644 | For a new language, you can either write your own converter function in | |
acedf35c | 15645 | analogy with the @LaTeX{} translator, or you can use the generic function |
4009494e GM |
15646 | directly. For example, if you have a language where a table is started |
15647 | with @samp{!BTBL!}, ended with @samp{!ETBL!}, and where table lines are | |
c8d0cf5c | 15648 | started with @samp{!BL!}, ended with @samp{!EL!}, and where the field |
4009494e GM |
15649 | separator is a TAB, you could call the generic translator like this (on |
15650 | a single line!): | |
15651 | ||
15652 | @example | |
15653 | #+ORGTBL: SEND test orgtbl-to-generic :tstart "!BTBL!" :tend "!ETBL!" | |
15654 | :lstart "!BL! " :lend " !EL!" :sep "\t" | |
15655 | @end example | |
15656 | ||
15657 | @noindent | |
15658 | Please check the documentation string of the function | |
15659 | @code{orgtbl-to-generic} for a full list of parameters understood by | |
c8d0cf5c | 15660 | that function, and remember that you can pass each of them into |
4009494e GM |
15661 | @code{orgtbl-to-latex}, @code{orgtbl-to-texinfo}, and any other function |
15662 | using the generic function. | |
15663 | ||
15664 | Of course you can also write a completely new function doing complicated | |
15665 | things the generic translator cannot do. A translator function takes | |
15666 | two arguments. The first argument is the table, a list of lines, each | |
15667 | line either the symbol @code{hline} or a list of fields. The second | |
15668 | argument is the property list containing all parameters specified in the | |
15669 | @samp{#+ORGTBL: SEND} line. The function must return a single string | |
15670 | containing the formatted table. If you write a generally useful | |
c8d0cf5c | 15671 | translator, please post it on @email{emacs-orgmode@@gnu.org} so that |
4009494e GM |
15672 | others can benefit from your work. |
15673 | ||
86fbb8ca | 15674 | @node Radio lists, , Translator functions, Tables in arbitrary syntax |
dbc28aaa CD |
15675 | @subsection Radio lists |
15676 | @cindex radio lists | |
15677 | @cindex org-list-insert-radio-list | |
15678 | ||
acedf35c | 15679 | Sending and receiving radio lists works exactly the same way as sending and |
6eb02347 | 15680 | receiving radio tables (@pxref{Radio tables}). As for radio tables, you can |
acedf35c | 15681 | insert radio list templates in HTML, @LaTeX{} and Texinfo modes by calling |
6eb02347 | 15682 | @code{org-list-insert-radio-list}. |
dbc28aaa CD |
15683 | |
15684 | Here are the differences with radio tables: | |
15685 | ||
15686 | @itemize @minus | |
15687 | @item | |
86fbb8ca CD |
15688 | Orgstruct mode must be active. |
15689 | @item | |
15690 | Use the @code{ORGLST} keyword instead of @code{ORGTBL}. | |
dbc28aaa CD |
15691 | @item |
15692 | The available translation functions for radio lists don't take | |
15693 | parameters. | |
28a16a1b | 15694 | @item |
c8d0cf5c | 15695 | @kbd{C-c C-c} will work when pressed on the first item of the list. |
dbc28aaa CD |
15696 | @end itemize |
15697 | ||
acedf35c CD |
15698 | Here is a @LaTeX{} example. Let's say that you have this in your |
15699 | @LaTeX{} file: | |
dbc28aaa | 15700 | |
86fbb8ca | 15701 | @cindex #+ORGLST |
dbc28aaa CD |
15702 | @example |
15703 | % BEGIN RECEIVE ORGLST to-buy | |
15704 | % END RECEIVE ORGLST to-buy | |
15705 | \begin@{comment@} | |
86fbb8ca | 15706 | #+ORGLST: SEND to-buy org-list-to-latex |
dbc28aaa CD |
15707 | - a new house |
15708 | - a new computer | |
15709 | + a new keyboard | |
15710 | + a new mouse | |
15711 | - a new life | |
15712 | \end@{comment@} | |
15713 | @end example | |
15714 | ||
15715 | Pressing `C-c C-c' on @code{a new house} and will insert the converted | |
acedf35c | 15716 | @LaTeX{} list between the two marker lines. |
dbc28aaa | 15717 | |
b349f79f | 15718 | @node Dynamic blocks, Special agenda views, Tables in arbitrary syntax, Hacking |
4009494e GM |
15719 | @section Dynamic blocks |
15720 | @cindex dynamic blocks | |
15721 | ||
a7808fba | 15722 | Org documents can contain @emph{dynamic blocks}. These are |
4009494e GM |
15723 | specially marked regions that are updated by some user-written function. |
15724 | A good example for such a block is the clock table inserted by the | |
15725 | command @kbd{C-c C-x C-r} (@pxref{Clocking work time}). | |
15726 | ||
acedf35c | 15727 | Dynamic blocks are enclosed by a BEGIN-END structure that assigns a name |
4009494e GM |
15728 | to the block and can also specify parameters for the function producing |
15729 | the content of the block. | |
15730 | ||
acedf35c | 15731 | @cindex #+BEGIN:dynamic block |
4009494e GM |
15732 | @example |
15733 | #+BEGIN: myblock :parameter1 value1 :parameter2 value2 ... | |
15734 | ||
15735 | #+END: | |
15736 | @end example | |
15737 | ||
15738 | Dynamic blocks are updated with the following commands | |
15739 | ||
15740 | @table @kbd | |
acedf35c | 15741 | @orgcmd{C-c C-x C-u,org-dblock-update} |
4009494e | 15742 | Update dynamic block at point. |
acedf35c | 15743 | @orgkey{C-u C-c C-x C-u} |
4009494e GM |
15744 | Update all dynamic blocks in the current file. |
15745 | @end table | |
15746 | ||
15747 | Updating a dynamic block means to remove all the text between BEGIN and | |
15748 | END, parse the BEGIN line for parameters and then call the specific | |
28a16a1b CD |
15749 | writer function for this block to insert the new content. If you want |
15750 | to use the original content in the writer function, you can use the | |
15751 | extra parameter @code{:content}. | |
15752 | ||
15753 | For a block with name @code{myblock}, the writer function is | |
4009494e GM |
15754 | @code{org-dblock-write:myblock} with as only parameter a property list |
15755 | with the parameters given in the begin line. Here is a trivial example | |
15756 | of a block that keeps track of when the block update function was last | |
15757 | run: | |
15758 | ||
15759 | @example | |
15760 | #+BEGIN: block-update-time :format "on %m/%d/%Y at %H:%M" | |
15761 | ||
15762 | #+END: | |
15763 | @end example | |
15764 | ||
15765 | @noindent | |
15766 | The corresponding block writer function could look like this: | |
15767 | ||
15768 | @lisp | |
15769 | (defun org-dblock-write:block-update-time (params) | |
15770 | (let ((fmt (or (plist-get params :format) "%d. %m. %Y"))) | |
15771 | (insert "Last block update at: " | |
15772 | (format-time-string fmt (current-time))))) | |
15773 | @end lisp | |
15774 | ||
15775 | If you want to make sure that all dynamic blocks are always up-to-date, | |
15776 | you could add the function @code{org-update-all-dblocks} to a hook, for | |
15777 | example @code{before-save-hook}. @code{org-update-all-dblocks} is | |
c8d0cf5c | 15778 | written in a way such that it does nothing in buffers that are not in |
a7808fba | 15779 | @code{org-mode}. |
4009494e | 15780 | |
ce57c2fe BG |
15781 | You can narrow the current buffer to the current dynamic block (like any |
15782 | other block) with @code{org-narrow-to-block}. | |
15783 | ||
c8d0cf5c | 15784 | @node Special agenda views, Extracting agenda information, Dynamic blocks, Hacking |
a7808fba | 15785 | @section Special agenda views |
4009494e GM |
15786 | @cindex agenda views, user-defined |
15787 | ||
ce57c2fe BG |
15788 | @vindex org-agenda-skip-function |
15789 | @vindex org-agenda-skip-function-global | |
afe98dfa | 15790 | Org provides a special hook that can be used to narrow down the selection |
ce57c2fe BG |
15791 | made by these agenda views: @code{agenda}, @code{todo}, @code{alltodo}, |
15792 | @code{tags}, @code{tags-todo}, @code{tags-tree}. You may specify a function | |
15793 | that is used at each match to verify if the match should indeed be part of | |
15794 | the agenda view, and if not, how much should be skipped. You can specify a | |
15795 | global condition that will be applied to all agenda views, this condition | |
15796 | would be stored in the variable @code{org-agenda-skip-function-global}. More | |
15797 | commonly, such a definition is applied only to specific custom searches, | |
15798 | using @code{org-agenda-skip-function}. | |
4009494e GM |
15799 | |
15800 | Let's say you want to produce a list of projects that contain a WAITING | |
15801 | tag anywhere in the project tree. Let's further assume that you have | |
a7808fba CD |
15802 | marked all tree headings that define a project with the TODO keyword |
15803 | PROJECT. In this case you would run a TODO search for the keyword | |
4009494e GM |
15804 | PROJECT, but skip the match unless there is a WAITING tag anywhere in |
15805 | the subtree belonging to the project line. | |
15806 | ||
15807 | To achieve this, you must write a function that searches the subtree for | |
15808 | the tag. If the tag is found, the function must return @code{nil} to | |
15809 | indicate that this match should not be skipped. If there is no such | |
15810 | tag, return the location of the end of the subtree, to indicate that | |
15811 | search should continue from there. | |
15812 | ||
15813 | @lisp | |
15814 | (defun my-skip-unless-waiting () | |
15815 | "Skip trees that are not waiting" | |
15816 | (let ((subtree-end (save-excursion (org-end-of-subtree t)))) | |
dbc28aaa | 15817 | (if (re-search-forward ":waiting:" subtree-end t) |
4009494e GM |
15818 | nil ; tag found, do not skip |
15819 | subtree-end))) ; tag not found, continue after end of subtree | |
15820 | @end lisp | |
15821 | ||
15822 | Now you may use this function in an agenda custom command, for example | |
15823 | like this: | |
15824 | ||
15825 | @lisp | |
15826 | (org-add-agenda-custom-command | |
15827 | '("b" todo "PROJECT" | |
e45e3595 | 15828 | ((org-agenda-skip-function 'my-skip-unless-waiting) |
4009494e GM |
15829 | (org-agenda-overriding-header "Projects waiting for something: ")))) |
15830 | @end lisp | |
15831 | ||
c8d0cf5c | 15832 | @vindex org-agenda-overriding-header |
4009494e GM |
15833 | Note that this also binds @code{org-agenda-overriding-header} to get a |
15834 | meaningful header in the agenda view. | |
15835 | ||
c8d0cf5c CD |
15836 | @vindex org-odd-levels-only |
15837 | @vindex org-agenda-skip-function | |
a7808fba CD |
15838 | A general way to create custom searches is to base them on a search for |
15839 | entries with a certain level limit. If you want to study all entries with | |
c8d0cf5c CD |
15840 | your custom search function, simply do a search for |
15841 | @samp{LEVEL>0}@footnote{Note that, when using @code{org-odd-levels-only}, a | |
15842 | level number corresponds to order in the hierarchy, not to the number of | |
15843 | stars.}, and then use @code{org-agenda-skip-function} to select the entries | |
15844 | you really want to have. | |
a7808fba | 15845 | |
4009494e GM |
15846 | You may also put a Lisp form into @code{org-agenda-skip-function}. In |
15847 | particular, you may use the functions @code{org-agenda-skip-entry-if} | |
15848 | and @code{org-agenda-skip-subtree-if} in this form, for example: | |
15849 | ||
15850 | @table @code | |
6d72f719 | 15851 | @item (org-agenda-skip-entry-if 'scheduled) |
4009494e | 15852 | Skip current entry if it has been scheduled. |
6d72f719 | 15853 | @item (org-agenda-skip-entry-if 'notscheduled) |
4009494e | 15854 | Skip current entry if it has not been scheduled. |
6d72f719 | 15855 | @item (org-agenda-skip-entry-if 'deadline) |
4009494e | 15856 | Skip current entry if it has a deadline. |
6d72f719 | 15857 | @item (org-agenda-skip-entry-if 'scheduled 'deadline) |
4009494e | 15858 | Skip current entry if it has a deadline, or if it is scheduled. |
6d72f719 | 15859 | @item (org-agenda-skip-entry-if 'todo '("TODO" "WAITING")) |
ed21c5c8 | 15860 | Skip current entry if the TODO keyword is TODO or WAITING. |
6d72f719 | 15861 | @item (org-agenda-skip-entry-if 'todo 'done) |
ed21c5c8 | 15862 | Skip current entry if the TODO keyword marks a DONE state. |
6d72f719 | 15863 | @item (org-agenda-skip-entry-if 'timestamp) |
c8d0cf5c | 15864 | Skip current entry if it has any timestamp, may also be deadline or scheduled. |
6d72f719 | 15865 | @item (org-agenda-skip-entry 'regexp "regular expression") |
dbc28aaa | 15866 | Skip current entry if the regular expression matches in the entry. |
6d72f719 | 15867 | @item (org-agenda-skip-entry 'notregexp "regular expression") |
dbc28aaa | 15868 | Skip current entry unless the regular expression matches. |
6d72f719 | 15869 | @item (org-agenda-skip-subtree-if 'regexp "regular expression") |
4009494e GM |
15870 | Same as above, but check and skip the entire subtree. |
15871 | @end table | |
15872 | ||
15873 | Therefore we could also have written the search for WAITING projects | |
15874 | like this, even without defining a special function: | |
15875 | ||
15876 | @lisp | |
15877 | (org-add-agenda-custom-command | |
15878 | '("b" todo "PROJECT" | |
15879 | ((org-agenda-skip-function '(org-agenda-skip-subtree-if | |
dbc28aaa | 15880 | 'regexp ":waiting:")) |
4009494e GM |
15881 | (org-agenda-overriding-header "Projects waiting for something: ")))) |
15882 | @end lisp | |
15883 | ||
c8d0cf5c CD |
15884 | @node Extracting agenda information, Using the property API, Special agenda views, Hacking |
15885 | @section Extracting agenda information | |
15886 | @cindex agenda, pipe | |
15887 | @cindex Scripts, for agenda processing | |
15888 | ||
15889 | @vindex org-agenda-custom-commands | |
15890 | Org provides commands to access agenda information for the command | |
15891 | line in Emacs batch mode. This extracted information can be sent | |
15892 | directly to a printer, or it can be read by a program that does further | |
15893 | processing of the data. The first of these commands is the function | |
15894 | @code{org-batch-agenda}, that produces an agenda view and sends it as | |
15895 | ASCII text to STDOUT. The command takes a single string as parameter. | |
15896 | If the string has length 1, it is used as a key to one of the commands | |
15897 | you have configured in @code{org-agenda-custom-commands}, basically any | |
15898 | key you can use after @kbd{C-c a}. For example, to directly print the | |
15899 | current TODO list, you could use | |
15900 | ||
15901 | @example | |
15902 | emacs -batch -l ~/.emacs -eval '(org-batch-agenda "t")' | lpr | |
15903 | @end example | |
15904 | ||
15905 | If the parameter is a string with 2 or more characters, it is used as a | |
15906 | tags/TODO match string. For example, to print your local shopping list | |
15907 | (all items with the tag @samp{shop}, but excluding the tag | |
15908 | @samp{NewYork}), you could use | |
15909 | ||
15910 | @example | |
15911 | emacs -batch -l ~/.emacs \ | |
15912 | -eval '(org-batch-agenda "+shop-NewYork")' | lpr | |
15913 | @end example | |
15914 | ||
15915 | @noindent | |
15916 | You may also modify parameters on the fly like this: | |
15917 | ||
15918 | @example | |
15919 | emacs -batch -l ~/.emacs \ | |
15920 | -eval '(org-batch-agenda "a" \ | |
e66ba1df | 15921 | org-agenda-span (quote month) \ |
c8d0cf5c CD |
15922 | org-agenda-include-diary nil \ |
15923 | org-agenda-files (quote ("~/org/project.org")))' \ | |
15924 | | lpr | |
15925 | @end example | |
15926 | ||
15927 | @noindent | |
15928 | which will produce a 30-day agenda, fully restricted to the Org file | |
15929 | @file{~/org/projects.org}, not even including the diary. | |
15930 | ||
15931 | If you want to process the agenda data in more sophisticated ways, you | |
15932 | can use the command @code{org-batch-agenda-csv} to get a comma-separated | |
15933 | list of values for each agenda item. Each line in the output will | |
15934 | contain a number of fields separated by commas. The fields in a line | |
15935 | are: | |
15936 | ||
15937 | @example | |
15938 | category @r{The category of the item} | |
15939 | head @r{The headline, without TODO keyword, TAGS and PRIORITY} | |
15940 | type @r{The type of the agenda entry, can be} | |
15941 | todo @r{selected in TODO match} | |
15942 | tagsmatch @r{selected in tags match} | |
15943 | diary @r{imported from diary} | |
15944 | deadline @r{a deadline} | |
15945 | scheduled @r{scheduled} | |
15946 | timestamp @r{appointment, selected by timestamp} | |
15947 | closed @r{entry was closed on date} | |
15948 | upcoming-deadline @r{warning about nearing deadline} | |
15949 | past-scheduled @r{forwarded scheduled item} | |
15950 | block @r{entry has date block including date} | |
15951 | todo @r{The TODO keyword, if any} | |
15952 | tags @r{All tags including inherited ones, separated by colons} | |
15953 | date @r{The relevant date, like 2007-2-14} | |
15954 | time @r{The time, like 15:00-16:50} | |
15955 | extra @r{String with extra planning info} | |
15956 | priority-l @r{The priority letter if any was given} | |
15957 | priority-n @r{The computed numerical priority} | |
15958 | @end example | |
15959 | ||
15960 | @noindent | |
15961 | Time and date will only be given if a timestamp (or deadline/scheduled) | |
15962 | led to the selection of the item. | |
15963 | ||
15964 | A CSV list like this is very easy to use in a post-processing script. | |
15965 | For example, here is a Perl program that gets the TODO list from | |
15966 | Emacs/Org and prints all the items, preceded by a checkbox: | |
15967 | ||
15968 | @example | |
15969 | #!/usr/bin/perl | |
15970 | ||
15971 | # define the Emacs command to run | |
15972 | $cmd = "emacs -batch -l ~/.emacs -eval '(org-batch-agenda-csv \"t\")'"; | |
15973 | ||
15974 | # run it and capture the output | |
15975 | $agenda = qx@{$cmd 2>/dev/null@}; | |
15976 | ||
15977 | # loop over all lines | |
15978 | foreach $line (split(/\n/,$agenda)) @{ | |
15979 | # get the individual values | |
15980 | ($category,$head,$type,$todo,$tags,$date,$time,$extra, | |
15981 | $priority_l,$priority_n) = split(/,/,$line); | |
15982 | # process and print | |
15983 | print "[ ] $head\n"; | |
15984 | @} | |
15985 | @end example | |
15986 | ||
c8d0cf5c | 15987 | @node Using the property API, Using the mapping API, Extracting agenda information, Hacking |
4009494e GM |
15988 | @section Using the property API |
15989 | @cindex API, for properties | |
15990 | @cindex properties, API | |
15991 | ||
15992 | Here is a description of the functions that can be used to work with | |
15993 | properties. | |
15994 | ||
15995 | @defun org-entry-properties &optional pom which | |
c8d0cf5c | 15996 | Get all properties of the entry at point-or-marker POM.@* |
4009494e GM |
15997 | This includes the TODO keyword, the tags, time strings for deadline, |
15998 | scheduled, and clocking, and any additional properties defined in the | |
acedf35c | 15999 | entry. The return value is an alist. Keys may occur multiple times |
c8d0cf5c | 16000 | if the property key was used several times.@* |
4009494e GM |
16001 | POM may also be nil, in which case the current entry is used. |
16002 | If WHICH is nil or `all', get all properties. If WHICH is | |
16003 | `special' or `standard', only get that subclass. | |
16004 | @end defun | |
c8d0cf5c | 16005 | @vindex org-use-property-inheritance |
4009494e | 16006 | @defun org-entry-get pom property &optional inherit |
a7808fba CD |
16007 | Get value of PROPERTY for entry at point-or-marker POM. By default, |
16008 | this only looks at properties defined locally in the entry. If INHERIT | |
16009 | is non-nil and the entry does not have the property, then also check | |
16010 | higher levels of the hierarchy. If INHERIT is the symbol | |
16011 | @code{selective}, use inheritance if and only if the setting of | |
16012 | @code{org-use-property-inheritance} selects PROPERTY for inheritance. | |
4009494e GM |
16013 | @end defun |
16014 | ||
16015 | @defun org-entry-delete pom property | |
16016 | Delete the property PROPERTY from entry at point-or-marker POM. | |
16017 | @end defun | |
16018 | ||
16019 | @defun org-entry-put pom property value | |
16020 | Set PROPERTY to VALUE for entry at point-or-marker POM. | |
16021 | @end defun | |
16022 | ||
16023 | @defun org-buffer-property-keys &optional include-specials | |
16024 | Get all property keys in the current buffer. | |
16025 | @end defun | |
16026 | ||
16027 | @defun org-insert-property-drawer | |
16028 | Insert a property drawer at point. | |
16029 | @end defun | |
16030 | ||
864c9740 CD |
16031 | @defun org-entry-put-multivalued-property pom property &rest values |
16032 | Set PROPERTY at point-or-marker POM to VALUES. VALUES should be a list of | |
16033 | strings. They will be concatenated, with spaces as separators. | |
16034 | @end defun | |
16035 | ||
16036 | @defun org-entry-get-multivalued-property pom property | |
16037 | Treat the value of the property PROPERTY as a whitespace-separated list of | |
16038 | values and return the values as a list of strings. | |
16039 | @end defun | |
16040 | ||
a7808fba CD |
16041 | @defun org-entry-add-to-multivalued-property pom property value |
16042 | Treat the value of the property PROPERTY as a whitespace-separated list of | |
16043 | values and make sure that VALUE is in this list. | |
16044 | @end defun | |
16045 | ||
16046 | @defun org-entry-remove-from-multivalued-property pom property value | |
16047 | Treat the value of the property PROPERTY as a whitespace-separated list of | |
16048 | values and make sure that VALUE is @emph{not} in this list. | |
16049 | @end defun | |
16050 | ||
16051 | @defun org-entry-member-in-multivalued-property pom property value | |
16052 | Treat the value of the property PROPERTY as a whitespace-separated list of | |
16053 | values and check if VALUE is in this list. | |
16054 | @end defun | |
16055 | ||
ed21c5c8 | 16056 | @defopt org-property-allowed-value-functions |
acedf35c | 16057 | Hook for functions supplying allowed values for a specific property. |
ed21c5c8 CD |
16058 | The functions must take a single argument, the name of the property, and |
16059 | return a flat list of allowed values. If @samp{:ETC} is one of | |
16060 | the values, use the values as completion help, but allow also other values | |
16061 | to be entered. The functions must return @code{nil} if they are not | |
16062 | responsible for this property. | |
16063 | @end defopt | |
16064 | ||
b349f79f CD |
16065 | @node Using the mapping API, , Using the property API, Hacking |
16066 | @section Using the mapping API | |
16067 | @cindex API, for mapping | |
16068 | @cindex mapping entries, API | |
16069 | ||
16070 | Org has sophisticated mapping capabilities to find all entries satisfying | |
16071 | certain criteria. Internally, this functionality is used to produce agenda | |
16072 | views, but there is also an API that can be used to execute arbitrary | |
16073 | functions for each or selected entries. The main entry point for this API | |
96c8522a | 16074 | is: |
b349f79f CD |
16075 | |
16076 | @defun org-map-entries func &optional match scope &rest skip | |
16077 | Call FUNC at each headline selected by MATCH in SCOPE. | |
16078 | ||
c8d0cf5c | 16079 | FUNC is a function or a Lisp form. The function will be called without |
b349f79f CD |
16080 | arguments, with the cursor positioned at the beginning of the headline. |
16081 | The return values of all calls to the function will be collected and | |
16082 | returned as a list. | |
16083 | ||
c8d0cf5c CD |
16084 | The call to FUNC will be wrapped into a save-excursion form, so FUNC |
16085 | does not need to preserve point. After evaluation, the cursor will be | |
16086 | moved to the end of the line (presumably of the headline of the | |
16087 | processed entry) and search continues from there. Under some | |
16088 | circumstances, this may not produce the wanted results. For example, | |
ce57c2fe | 16089 | if you have removed (e.g.@: archived) the current (sub)tree it could |
c8d0cf5c CD |
16090 | mean that the next entry will be skipped entirely. In such cases, you |
16091 | can specify the position from where search should continue by making | |
16092 | FUNC set the variable `org-map-continue-from' to the desired buffer | |
16093 | position. | |
16094 | ||
864c9740 | 16095 | MATCH is a tags/property/todo match as it is used in the agenda match view. |
b349f79f CD |
16096 | Only headlines that are matched by this query will be considered during |
16097 | the iteration. When MATCH is nil or t, all headlines will be | |
16098 | visited by the iteration. | |
16099 | ||
16100 | SCOPE determines the scope of this command. It can be any of: | |
16101 | ||
16102 | @example | |
16103 | nil @r{the current buffer, respecting the restriction if any} | |
16104 | tree @r{the subtree started with the entry at point} | |
ce57c2fe | 16105 | region @r{The entries within the active region, if any} |
b349f79f CD |
16106 | file @r{the current buffer, without restriction} |
16107 | file-with-archives | |
16108 | @r{the current buffer, and any archives associated with it} | |
16109 | agenda @r{all agenda files} | |
16110 | agenda-with-archives | |
16111 | @r{all agenda files with any archive files associated with them} | |
16112 | (file1 file2 ...) | |
16113 | @r{if this is a list, all files in the list will be scanned} | |
16114 | @end example | |
c8d0cf5c | 16115 | @noindent |
b349f79f CD |
16116 | The remaining args are treated as settings for the skipping facilities of |
16117 | the scanner. The following items can be given here: | |
16118 | ||
c8d0cf5c | 16119 | @vindex org-agenda-skip-function |
b349f79f CD |
16120 | @example |
16121 | archive @r{skip trees with the archive tag} | |
16122 | comment @r{skip trees with the COMMENT keyword} | |
16123 | function or Lisp form | |
16124 | @r{will be used as value for @code{org-agenda-skip-function},} | |
867d4bb3 | 16125 | @r{so whenever the function returns t, FUNC} |
b349f79f CD |
16126 | @r{will not be called for that entry and search will} |
16127 | @r{continue from the point where the function leaves it} | |
16128 | @end example | |
16129 | @end defun | |
16130 | ||
16131 | The function given to that mapping routine can really do anything you like. | |
a50253cc GM |
16132 | It can use the property API (@pxref{Using the property API}) to gather more |
16133 | information about the entry, or in order to change metadata in the entry. | |
b349f79f | 16134 | Here are a couple of functions that might be handy: |
96c8522a | 16135 | |
b349f79f | 16136 | @defun org-todo &optional arg |
acedf35c | 16137 | Change the TODO state of the entry. See the docstring of the functions for |
b349f79f CD |
16138 | the many possible values for the argument ARG. |
16139 | @end defun | |
16140 | ||
16141 | @defun org-priority &optional action | |
acedf35c | 16142 | Change the priority of the entry. See the docstring of this function for the |
b349f79f CD |
16143 | possible values for ACTION. |
16144 | @end defun | |
16145 | ||
16146 | @defun org-toggle-tag tag &optional onoff | |
16147 | Toggle the tag TAG in the current entry. Setting ONOFF to either @code{on} | |
16148 | or @code{off} will not toggle tag, but ensure that it is either on or off. | |
16149 | @end defun | |
16150 | ||
16151 | @defun org-promote | |
16152 | Promote the current entry. | |
16153 | @end defun | |
16154 | ||
16155 | @defun org-demote | |
16156 | Demote the current entry. | |
16157 | @end defun | |
16158 | ||
16159 | Here is a simple example that will turn all entries in the current file with | |
16160 | a tag @code{TOMORROW} into TODO entries with the keyword @code{UPCOMING}. | |
16161 | Entries in comment trees and in archive trees will be ignored. | |
16162 | ||
16163 | @lisp | |
16164 | (org-map-entries | |
16165 | '(org-todo "UPCOMING") | |
16166 | "+TOMORROW" 'file 'archive 'comment) | |
16167 | @end lisp | |
16168 | ||
16169 | The following example counts the number of entries with TODO keyword | |
16170 | @code{WAITING}, in all agenda files. | |
16171 | ||
16172 | @lisp | |
96c8522a | 16173 | (length (org-map-entries t "/+WAITING" 'agenda)) |
b349f79f CD |
16174 | @end lisp |
16175 | ||
7006d207 CD |
16176 | @node MobileOrg, History and Acknowledgments, Hacking, Top |
16177 | @appendix MobileOrg | |
16178 | @cindex iPhone | |
16179 | @cindex MobileOrg | |
16180 | ||
86fbb8ca CD |
16181 | @uref{http://mobileorg.ncogni.to/, MobileOrg} is an application for the |
16182 | @i{iPhone/iPod Touch} series of devices, developed by Richard Moreland. | |
e66ba1df | 16183 | @i{MobileOrg} offers offline viewing and capture support for an Org mode |
86fbb8ca CD |
16184 | system rooted on a ``real'' computer. It does also allow you to record |
16185 | changes to existing entries. Android users should check out | |
16186 | @uref{http://wiki.github.com/matburt/mobileorg-android/, MobileOrg Android} | |
16187 | by Matt Jones. | |
7006d207 CD |
16188 | |
16189 | This appendix describes the support Org has for creating agenda views in a | |
16190 | format that can be displayed by @i{MobileOrg}, and for integrating notes | |
a351880d CD |
16191 | captured and changes made by @i{MobileOrg} into the main system. |
16192 | ||
16193 | For changing tags and TODO states in MobileOrg, you should have set up the | |
16194 | customization variables @code{org-todo-keywords} and @code{org-tags-alist} to | |
86fbb8ca | 16195 | cover all important tags and TODO keywords, even if individual files use only |
a351880d | 16196 | part of these. MobileOrg will also offer you states and tags set up with |
86fbb8ca | 16197 | in-buffer settings, but it will understand the logistics of TODO state |
a351880d CD |
16198 | @i{sets} (@pxref{Per-file keywords}) and @i{mutually exclusive} tags |
16199 | (@pxref{Setting tags}) only for those set in these variables. | |
7006d207 CD |
16200 | |
16201 | @menu | |
c0468714 GM |
16202 | * Setting up the staging area:: Where to interact with the mobile device |
16203 | * Pushing to MobileOrg:: Uploading Org files and agendas | |
16204 | * Pulling from MobileOrg:: Integrating captured and flagged items | |
7006d207 CD |
16205 | @end menu |
16206 | ||
16207 | @node Setting up the staging area, Pushing to MobileOrg, MobileOrg, MobileOrg | |
16208 | @section Setting up the staging area | |
16209 | ||
acedf35c | 16210 | MobileOrg needs to interact with Emacs through a directory on a server. If you |
afe98dfa | 16211 | are using a public server, you should consider to encrypt the files that are |
e66ba1df | 16212 | uploaded to the server. This can be done with Org mode 7.02 and with |
afe98dfa CD |
16213 | @i{MobileOrg 1.5} (iPhone version), and you need an @file{openssl} |
16214 | installation on your system. To turn on encryption, set a password in | |
16215 | @i{MobileOrg} and, on the Emacs side, configure the variable | |
16216 | @code{org-mobile-use-encryption}@footnote{If you can safely store the | |
16217 | password in your Emacs setup, you might also want to configure | |
16218 | @code{org-mobile-encryption-password}. Please read the docstring of that | |
16219 | variable. Note that encryption will apply only to the contents of the | |
16220 | @file{.org} files. The file names themselves will remain visible.}. | |
16221 | ||
16222 | The easiest way to create that directory is to use a free | |
16223 | @uref{http://dropbox.com,Dropbox.com} account@footnote{If you cannot use | |
16224 | Dropbox, or if your version of MobileOrg does not support it, you can use a | |
acedf35c | 16225 | webdav server. For more information, check out the documentation of MobileOrg and also this |
ce57c2fe | 16226 | @uref{http://orgmode.org/worg/org-faq.html#mobileorg_webdav, FAQ entry}.}. |
86fbb8ca CD |
16227 | When MobileOrg first connects to your Dropbox, it will create a directory |
16228 | @i{MobileOrg} inside the Dropbox. After the directory has been created, tell | |
16229 | Emacs about it: | |
a351880d | 16230 | |
86fbb8ca CD |
16231 | @lisp |
16232 | (setq org-mobile-directory "~/Dropbox/MobileOrg") | |
16233 | @end lisp | |
a351880d | 16234 | |
e66ba1df | 16235 | Org mode has commands to put files for @i{MobileOrg} into that directory, |
86fbb8ca | 16236 | and to read captured notes from there. |
7006d207 CD |
16237 | |
16238 | @node Pushing to MobileOrg, Pulling from MobileOrg, Setting up the staging area, MobileOrg | |
16239 | @section Pushing to MobileOrg | |
16240 | ||
16241 | This operation copies all files currently listed in @code{org-mobile-files} | |
16242 | to the directory @code{org-mobile-directory}. By default this list contains | |
16243 | all agenda files (as listed in @code{org-agenda-files}), but additional files | |
ce57c2fe | 16244 | can be included by customizing @code{org-mobile-files}. File names will be |
acedf35c | 16245 | staged with paths relative to @code{org-directory}, so all files should be |
86fbb8ca CD |
16246 | inside this directory. The push operation also creates a special Org file |
16247 | @file{agendas.org} with all custom agenda view defined by the | |
e66ba1df | 16248 | user@footnote{While creating the agendas, Org mode will force ID properties |
afe98dfa CD |
16249 | on all referenced entries, so that these entries can be uniquely identified |
16250 | if @i{MobileOrg} flags them for further action. If you do not want to get | |
16251 | these properties in so many entries, you can set the variable | |
16252 | @code{org-mobile-force-id-on-agenda-items} to @code{nil}. Org mode will then | |
16253 | rely on outline paths, in the hope that these will be unique enough.}. | |
16254 | Finally, Org writes the file @file{index.org}, containing links to all other | |
16255 | files. @i{MobileOrg} first reads this file from the server, and then | |
16256 | downloads all agendas and Org files listed in it. To speed up the download, | |
16257 | MobileOrg will only read files whose checksums@footnote{stored automatically | |
16258 | in the file @file{checksums.dat}} have changed. | |
7006d207 CD |
16259 | |
16260 | @node Pulling from MobileOrg, , Pushing to MobileOrg, MobileOrg | |
16261 | @section Pulling from MobileOrg | |
16262 | ||
86fbb8ca CD |
16263 | When @i{MobileOrg} synchronizes with the server, it not only pulls the Org |
16264 | files for viewing. It also appends captured entries and pointers to flagged | |
16265 | and changed entries to the file @file{mobileorg.org} on the server. Org has | |
16266 | a @emph{pull} operation that integrates this information into an inbox file | |
16267 | and operates on the pointers to flagged entries. Here is how it works: | |
7006d207 CD |
16268 | |
16269 | @enumerate | |
16270 | @item | |
16271 | Org moves all entries found in | |
16272 | @file{mobileorg.org}@footnote{@file{mobileorg.org} will be empty after this | |
16273 | operation.} and appends them to the file pointed to by the variable | |
a351880d CD |
16274 | @code{org-mobile-inbox-for-pull}. Each captured entry and each editing event |
16275 | will be a top-level entry in the inbox file. | |
16276 | @item | |
16277 | After moving the entries, Org will attempt to implement the changes made in | |
16278 | @i{MobileOrg}. Some changes are applied directly and without user | |
16279 | interaction. Examples are all changes to tags, TODO state, headline and body | |
16280 | text that can be cleanly applied. Entries that have been flagged for further | |
16281 | action will receive a tag @code{:FLAGGED:}, so that they can be easily found | |
16282 | again. When there is a problem finding an entry or applying the change, the | |
16283 | pointer entry will remain in the inbox and will be marked with an error | |
16284 | message. You need to later resolve these issues by hand. | |
7006d207 CD |
16285 | @item |
16286 | Org will then generate an agenda view with all flagged entries. The user | |
16287 | should then go through these entries and do whatever actions are necessary. | |
16288 | If a note has been stored while flagging an entry in @i{MobileOrg}, that note | |
16289 | will be displayed in the echo area when the cursor is on the corresponding | |
16290 | agenda line. | |
16291 | @table @kbd | |
16292 | @kindex ? | |
16293 | @item ? | |
16294 | Pressing @kbd{?} in that special agenda will display the full flagging note in | |
16295 | another window and also push it onto the kill ring. So you could use @kbd{? | |
16296 | z C-y C-c C-c} to store that flagging note as a normal note in the entry. | |
16297 | Pressing @kbd{?} twice in succession will offer to remove the | |
16298 | @code{:FLAGGED:} tag along with the recorded flagging note (which is stored | |
acedf35c | 16299 | in a property). In this way you indicate that the intended processing for |
a351880d | 16300 | this flagged entry is finished. |
7006d207 CD |
16301 | @end table |
16302 | @end enumerate | |
16303 | ||
16304 | @kindex C-c a ? | |
16305 | If you are not able to process all flagged entries directly, you can always | |
afe98dfa CD |
16306 | return to this agenda view@footnote{Note, however, that there is a subtle |
16307 | difference. The view created automatically by @kbd{M-x org-mobile-pull | |
16308 | @key{RET}} is guaranteed to search all files that have been addressed by the | |
16309 | last pull. This might include a file that is not currently in your list of | |
16310 | agenda files. If you later use @kbd{C-c a ?} to regenerate the view, only | |
16311 | the current agenda files will be searched.} using @kbd{C-c a ?}. | |
7006d207 CD |
16312 | |
16313 | @node History and Acknowledgments, Main Index, MobileOrg, Top | |
86fbb8ca CD |
16314 | @appendix History and acknowledgments |
16315 | @cindex acknowledgments | |
4009494e GM |
16316 | @cindex history |
16317 | @cindex thanks | |
16318 | ||
86fbb8ca CD |
16319 | Org was born in 2003, out of frustration over the user interface of the Emacs |
16320 | Outline mode. I was trying to organize my notes and projects, and using | |
16321 | Emacs seemed to be the natural way to go. However, having to remember eleven | |
16322 | different commands with two or three keys per command, only to hide and show | |
16323 | parts of the outline tree, that seemed entirely unacceptable to me. Also, | |
16324 | when using outlines to take notes, I constantly wanted to restructure the | |
16325 | tree, organizing it parallel to my thoughts and plans. @emph{Visibility | |
16326 | cycling} and @emph{structure editing} were originally implemented in the | |
16327 | package @file{outline-magic.el}, but quickly moved to the more general | |
16328 | @file{org.el}. As this environment became comfortable for project planning, | |
16329 | the next step was adding @emph{TODO entries}, basic @emph{timestamps}, and | |
16330 | @emph{table support}. These areas highlighted the two main goals that Org | |
16331 | still has today: to be a new, outline-based, plain text mode with innovative | |
16332 | and intuitive editing features, and to incorporate project planning | |
16333 | functionality directly into a notes file. | |
a7808fba | 16334 | |
c8d0cf5c CD |
16335 | Since the first release, literally thousands of emails to me or to |
16336 | @email{emacs-orgmode@@gnu.org} have provided a constant stream of bug | |
4009494e GM |
16337 | reports, feedback, new ideas, and sometimes patches and add-on code. |
16338 | Many thanks to everyone who has helped to improve this package. I am | |
16339 | trying to keep here a list of the people who had significant influence | |
a7808fba | 16340 | in shaping one or more aspects of Org. The list may not be |
4009494e GM |
16341 | complete, if I have forgotten someone, please accept my apologies and |
16342 | let me know. | |
16343 | ||
86fbb8ca CD |
16344 | Before I get to this list, a few special mentions are in order: |
16345 | ||
16346 | @table @i | |
16347 | @item Bastien Guerry | |
16348 | Bastien has written a large number of extensions to Org (most of them | |
e66ba1df | 16349 | integrated into the core by now), including the @LaTeX{} exporter and the plain |
86fbb8ca CD |
16350 | list parser. His support during the early days, when he basically acted as |
16351 | co-maintainer, was central to the success of this project. Bastien also | |
16352 | invented Worg, helped establishing the Web presence of Org, and sponsors | |
16353 | hosting costs for the orgmode.org website. | |
16354 | @item Eric Schulte and Dan Davison | |
16355 | Eric and Dan are jointly responsible for the Org-babel system, which turns | |
16356 | Org into a multi-language environment for evaluating code and doing literate | |
16357 | programming and reproducible research. | |
16358 | @item John Wiegley | |
acedf35c CD |
16359 | John has contributed a number of great ideas and patches directly to Org, |
16360 | including the attachment system (@file{org-attach.el}), integration with | |
16361 | Apple Mail (@file{org-mac-message.el}), hierarchical dependencies of TODO | |
16362 | items, habit tracking (@file{org-habits.el}), and encryption | |
16363 | (@file{org-crypt.el}). Also, the capture system is really an extended copy | |
16364 | of his great @file{remember.el}. | |
86fbb8ca CD |
16365 | @item Sebastian Rose |
16366 | Without Sebastian, the HTML/XHTML publishing of Org would be the pitiful work | |
16367 | of an ignorant amateur. Sebastian has pushed this part of Org onto a much | |
16368 | higher level. He also wrote @file{org-info.js}, a Java script for displaying | |
16369 | webpages derived from Org using an Info-like or a folding interface with | |
16370 | single-key navigation. | |
16371 | @end table | |
16372 | ||
16373 | @noindent OK, now to the full list of contributions! Again, please let me | |
16374 | know what I am missing here! | |
16375 | ||
4009494e GM |
16376 | @itemize @bullet |
16377 | ||
16378 | @item | |
16379 | @i{Russel Adams} came up with the idea for drawers. | |
16380 | @item | |
a7808fba | 16381 | @i{Thomas Baumann} wrote @file{org-bbdb.el} and @file{org-mhe.el}. |
4009494e | 16382 | @item |
b349f79f | 16383 | @i{Christophe Bataillon} created the great unicorn logo that we use on the |
e66ba1df | 16384 | Org mode website. |
b349f79f | 16385 | @item |
c8d0cf5c CD |
16386 | @i{Alex Bochannek} provided a patch for rounding timestamps. |
16387 | @item | |
ed21c5c8 CD |
16388 | @i{Jan Böcker} wrote @file{org-docview.el}. |
16389 | @item | |
e66ba1df | 16390 | @i{Brad Bozarth} showed how to pull RSS feed data into Org mode files. |
c8d0cf5c CD |
16391 | @item |
16392 | @i{Tom Breton} wrote @file{org-choose.el}. | |
4009494e GM |
16393 | @item |
16394 | @i{Charles Cave}'s suggestion sparked the implementation of templates | |
86fbb8ca | 16395 | for Remember, which are now templates for capture. |
4009494e GM |
16396 | @item |
16397 | @i{Pavel Chalmoviansky} influenced the agenda treatment of items with | |
16398 | specified time. | |
16399 | @item | |
c8d0cf5c | 16400 | @i{Gregory Chernov} patched support for Lisp forms into table |
4009494e GM |
16401 | calculations and improved XEmacs compatibility, in particular by porting |
16402 | @file{nouline.el} to XEmacs. | |
16403 | @item | |
c8d0cf5c CD |
16404 | @i{Sacha Chua} suggested copying some linking code from Planner. |
16405 | @item | |
16406 | @i{Baoqiu Cui} contributed the DocBook exporter. | |
4009494e | 16407 | @item |
5fbc0f11 | 16408 | @i{Eddward DeVilla} proposed and tested checkbox statistics. He also |
4009494e GM |
16409 | came up with the idea of properties, and that there should be an API for |
16410 | them. | |
16411 | @item | |
c8d0cf5c CD |
16412 | @i{Nick Dokos} tracked down several nasty bugs. |
16413 | @item | |
4009494e GM |
16414 | @i{Kees Dullemond} used to edit projects lists directly in HTML and so |
16415 | inspired some of the early development, including HTML export. He also | |
16416 | asked for a way to narrow wide table columns. | |
16417 | @item | |
86fbb8ca CD |
16418 | @i{Thomas S. Dye} contributed documentation on Worg and helped integrating |
16419 | the Org-Babel documentation into the manual. | |
16420 | @item | |
acedf35c CD |
16421 | @i{Christian Egli} converted the documentation into Texinfo format, inspired |
16422 | the agenda, patched CSS formatting into the HTML exporter, and wrote | |
16423 | @file{org-taskjuggler.el}. | |
4009494e GM |
16424 | @item |
16425 | @i{David Emery} provided a patch for custom CSS support in exported | |
16426 | HTML agendas. | |
16427 | @item | |
16428 | @i{Nic Ferrier} contributed mailcap and XOXO support. | |
16429 | @item | |
28a16a1b CD |
16430 | @i{Miguel A. Figueroa-Villanueva} implemented hierarchical checkboxes. |
16431 | @item | |
4009494e GM |
16432 | @i{John Foerch} figured out how to make incremental search show context |
16433 | around a match in a hidden outline tree. | |
16434 | @item | |
a351880d CD |
16435 | @i{Raimar Finken} wrote @file{org-git-line.el}. |
16436 | @item | |
16437 | @i{Mikael Fornius} works as a mailing list moderator. | |
16438 | @item | |
16439 | @i{Austin Frank} works as a mailing list moderator. | |
16440 | @item | |
acedf35c CD |
16441 | @i{Eric Fraga} drove the development of BEAMER export with ideas and |
16442 | testing. | |
16443 | @item | |
16444 | @i{Barry Gidden} did proofreading the manual in preparation for the book | |
16445 | publication through Network Theory Ltd. | |
16446 | @item | |
dbc28aaa | 16447 | @i{Niels Giesen} had the idea to automatically archive DONE trees. |
4009494e | 16448 | @item |
afe98dfa CD |
16449 | @i{Nicolas Goaziou} rewrote much of the plain list code. |
16450 | @item | |
4009494e GM |
16451 | @i{Kai Grossjohann} pointed out key-binding conflicts with other packages. |
16452 | @item | |
acedf35c CD |
16453 | @i{Brian Gough} of Network Theory Ltd publishes the Org mode manual as a |
16454 | book. | |
16455 | @item | |
a7808fba CD |
16456 | @i{Bernt Hansen} has driven much of the support for auto-repeating tasks, |
16457 | task state change logging, and the clocktable. His clear explanations have | |
c8d0cf5c | 16458 | been critical when we started to adopt the Git version control system. |
a7808fba | 16459 | @item |
c8d0cf5c | 16460 | @i{Manuel Hermenegildo} has contributed various ideas, small fixes and |
864c9740 CD |
16461 | patches. |
16462 | @item | |
a7808fba CD |
16463 | @i{Phil Jackson} wrote @file{org-irc.el}. |
16464 | @item | |
4009494e GM |
16465 | @i{Scott Jaderholm} proposed footnotes, control over whitespace between |
16466 | folded entries, and column view for properties. | |
16467 | @item | |
86fbb8ca CD |
16468 | @i{Matt Jones} wrote @i{MobileOrg Android}. |
16469 | @item | |
a7808fba CD |
16470 | @i{Tokuya Kameshima} wrote @file{org-wl.el} and @file{org-mew.el}. |
16471 | @item | |
acedf35c | 16472 | @i{Shidai Liu} ("Leo") asked for embedded @LaTeX{} and tested it. He also |
4009494e GM |
16473 | provided frequent feedback and some patches. |
16474 | @item | |
55e0839d CD |
16475 | @i{Matt Lundin} has proposed last-row references for table formulas and named |
16476 | invisible anchors. He has also worked a lot on the FAQ. | |
16477 | @item | |
86fbb8ca CD |
16478 | @i{David Maus} wrote @file{org-atom.el}, maintains the issues file for Org, |
16479 | and is a prolific contributor on the mailing list with competent replies, | |
16480 | small fixes and patches. | |
16481 | @item | |
4009494e GM |
16482 | @i{Jason F. McBrayer} suggested agenda export to CSV format. |
16483 | @item | |
dbc28aaa CD |
16484 | @i{Max Mikhanosha} came up with the idea of refiling. |
16485 | @item | |
4009494e GM |
16486 | @i{Dmitri Minaev} sent a patch to set priority limits on a per-file |
16487 | basis. | |
16488 | @item | |
16489 | @i{Stefan Monnier} provided a patch to keep the Emacs-Lisp compiler | |
16490 | happy. | |
16491 | @item | |
7006d207 CD |
16492 | @i{Richard Moreland} wrote @i{MobileOrg} for the iPhone. |
16493 | @item | |
c8d0cf5c CD |
16494 | @i{Rick Moynihan} proposed allowing multiple TODO sequences in a file |
16495 | and being able to quickly restrict the agenda to a subtree. | |
4009494e | 16496 | @item |
c8d0cf5c CD |
16497 | @i{Todd Neal} provided patches for links to Info files and Elisp forms. |
16498 | @item | |
16499 | @i{Greg Newman} refreshed the unicorn logo into its current form. | |
4009494e GM |
16500 | @item |
16501 | @i{Tim O'Callaghan} suggested in-file links, search options for general | |
16502 | file links, and TAGS. | |
16503 | @item | |
acedf35c | 16504 | @i{Osamu Okano} wrote @file{orgcard2ref.pl}, a Perl program to create a text |
86fbb8ca CD |
16505 | version of the reference card. |
16506 | @item | |
4009494e GM |
16507 | @i{Takeshi Okano} translated the manual and David O'Toole's tutorial |
16508 | into Japanese. | |
16509 | @item | |
16510 | @i{Oliver Oppitz} suggested multi-state TODO items. | |
16511 | @item | |
16512 | @i{Scott Otterson} sparked the introduction of descriptive text for | |
16513 | links, among other things. | |
16514 | @item | |
16515 | @i{Pete Phillips} helped during the development of the TAGS feature, and | |
16516 | provided frequent feedback. | |
16517 | @item | |
c8d0cf5c CD |
16518 | @i{Martin Pohlack} provided the code snippet to bundle character insertion |
16519 | into bundles of 20 for undo. | |
16520 | @item | |
4009494e GM |
16521 | @i{T.V. Raman} reported bugs and suggested improvements. |
16522 | @item | |
16523 | @i{Matthias Rempe} (Oelde) provided ideas, Windows support, and quality | |
16524 | control. | |
16525 | @item | |
a351880d CD |
16526 | @i{Paul Rivier} provided the basic implementation of named footnotes. He |
16527 | also acted as mailing list moderator for some time. | |
55e0839d | 16528 | @item |
4009494e GM |
16529 | @i{Kevin Rogers} contributed code to access VM files on remote hosts. |
16530 | @item | |
16531 | @i{Frank Ruell} solved the mystery of the @code{keymapp nil} bug, a | |
16532 | conflict with @file{allout.el}. | |
16533 | @item | |
c8d0cf5c | 16534 | @i{Jason Riedy} generalized the send-receive mechanism for Orgtbl tables with |
b349f79f | 16535 | extensive patches. |
4009494e | 16536 | @item |
b349f79f CD |
16537 | @i{Philip Rooke} created the Org reference card, provided lots |
16538 | of feedback, developed and applied standards to the Org documentation. | |
4009494e GM |
16539 | @item |
16540 | @i{Christian Schlauer} proposed angular brackets around links, among | |
16541 | other things. | |
16542 | @item | |
ed21c5c8 CD |
16543 | @i{Paul Sexton} wrote @file{org-ctags.el}. |
16544 | @item | |
b349f79f | 16545 | Linking to VM/BBDB/Gnus was first inspired by @i{Tom Shannon}'s |
4009494e GM |
16546 | @file{organizer-mode.el}. |
16547 | @item | |
55e0839d CD |
16548 | @i{Ilya Shlyakhter} proposed the Archive Sibling, line numbering in literal |
16549 | examples, and remote highlighting for referenced code lines. | |
a7808fba | 16550 | @item |
64fb801f CD |
16551 | @i{Stathis Sideris} wrote the @file{ditaa.jar} ASCII to PNG converter that is |
16552 | now packaged into Org's @file{contrib} directory. | |
16553 | @item | |
4009494e GM |
16554 | @i{Daniel Sinder} came up with the idea of internal archiving by locking |
16555 | subtrees. | |
16556 | @item | |
16557 | @i{Dale Smith} proposed link abbreviations. | |
16558 | @item | |
864c9740 CD |
16559 | @i{James TD Smith} has contributed a large number of patches for useful |
16560 | tweaks and features. | |
16561 | @item | |
b349f79f CD |
16562 | @i{Adam Spiers} asked for global linking commands, inspired the link |
16563 | extension system, added support for mairix, and proposed the mapping API. | |
4009494e | 16564 | @item |
86fbb8ca | 16565 | @i{Ulf Stegemann} created the table to translate special symbols to HTML, |
e66ba1df | 16566 | @LaTeX{}, UTF-8, Latin-1 and ASCII. |
86fbb8ca | 16567 | @item |
96c8522a CD |
16568 | @i{Andy Stewart} contributed code to @file{org-w3m.el}, to copy HTML content |
16569 | with links transformation to Org syntax. | |
16570 | @item | |
4009494e GM |
16571 | @i{David O'Toole} wrote @file{org-publish.el} and drafted the manual |
16572 | chapter about publishing. | |
16573 | @item | |
153ae947 | 16574 | @i{Jambunathan K} contributed the ODT exporter. |
ce57c2fe | 16575 | @item |
e66ba1df | 16576 | @i{Sebastien Vauban} reported many issues with @LaTeX{} and BEAMER export and |
27e428e7 | 16577 | enabled source code highlighting in Gnus. |
acedf35c | 16578 | @item |
86fbb8ca CD |
16579 | @i{Stefan Vollmar} organized a video-recorded talk at the |
16580 | Max-Planck-Institute for Neurology. He also inspired the creation of a | |
16581 | concept index for HTML export. | |
16582 | @item | |
4009494e GM |
16583 | @i{J@"urgen Vollmer} contributed code generating the table of contents |
16584 | in HTML output. | |
16585 | @item | |
ed21c5c8 CD |
16586 | @i{Samuel Wales} has provided important feedback and bug reports. |
16587 | @item | |
4009494e GM |
16588 | @i{Chris Wallace} provided a patch implementing the @samp{QUOTE} |
16589 | keyword. | |
16590 | @item | |
16591 | @i{David Wainberg} suggested archiving, and improvements to the linking | |
16592 | system. | |
16593 | @item | |
4009494e | 16594 | @i{Carsten Wimmer} suggested some changes and helped fix a bug in |
a7808fba | 16595 | linking to Gnus. |
4009494e | 16596 | @item |
a7808fba | 16597 | @i{Roland Winkler} requested additional key bindings to make Org |
4009494e GM |
16598 | work on a tty. |
16599 | @item | |
16600 | @i{Piotr Zielinski} wrote @file{org-mouse.el}, proposed agenda blocks | |
16601 | and contributed various ideas and code snippets. | |
ce57c2fe | 16602 | @item |
4009494e GM |
16603 | @end itemize |
16604 | ||
16605 | ||
dbc28aaa | 16606 | @node Main Index, Key Index, History and Acknowledgments, Top |
86fbb8ca | 16607 | @unnumbered Concept index |
4009494e GM |
16608 | |
16609 | @printindex cp | |
16610 | ||
afe98dfa | 16611 | @node Key Index, Command and Function Index, Main Index, Top |
86fbb8ca | 16612 | @unnumbered Key index |
4009494e GM |
16613 | |
16614 | @printindex ky | |
16615 | ||
afe98dfa CD |
16616 | @node Command and Function Index, Variable Index, Key Index, Top |
16617 | @unnumbered Command and function index | |
16618 | ||
16619 | @printindex fn | |
16620 | ||
16621 | @node Variable Index, , Command and Function Index, Top | |
86fbb8ca | 16622 | @unnumbered Variable index |
c8d0cf5c CD |
16623 | |
16624 | This is not a complete index of variables and faces, only the ones that are | |
16625 | mentioned in the manual. For a more complete list, use @kbd{M-x | |
a351880d | 16626 | org-customize @key{RET}} and then click yourself through the tree. |
c8d0cf5c CD |
16627 | |
16628 | @printindex vr | |
16629 | ||
4009494e GM |
16630 | @bye |
16631 | ||
a7808fba | 16632 | @c Local variables: |
a7808fba | 16633 | @c fill-column: 77 |
afe98dfa | 16634 | @c indent-tabs-mode: nil |
acedf35c CD |
16635 | @c paragraph-start: "\b\\|^@[a-zA-Z]*[ \n]\\|^@x?org\\(key\\|cmd\\)\\|\f\\|[ ]*$" |
16636 | @c paragraph-separate: "\b\\|^@[a-zA-Z]*[ \n]\\|^@x?org\\(key\\|cmd\\)\\|[ \f]*$" | |
a7808fba | 16637 | @c End: |
44ce9197 | 16638 | |
7006d207 CD |
16639 | |
16640 | @c LocalWords: webdavhost pre |