1 # -*- mode: org; fill-column: 65 -*-
5 #+TITLE: Org-mode list of user-visible changes
6 #+AUTHOR: Carsten Dominik
7 #+EMAIL: carsten at orgmode dot org
8 #+OPTIONS: H:3 num:nil toc:nil \n:nil @:t ::t |:t ^:{} *:t TeX:t LaTeX:nil f:nil
9 #+INFOJS_OPT: view:info toc:1 path:org-info.js tdepth:2 ftoc:t
11 #+LINK_HOME: http://orgmode.org
13 * Version 6.23 (in preparation)
19 ** Incompatible changes
21 - CLOCK lines will now be captured into the LOGBOOK drawer.
22 See below for details.
26 *** Capture state change notes into a drawer
28 State change notes can now be captured into a drawer =LOGBOOK=,
29 to keep the entry tidy. If this is what you want, you will need
32 #+begin_src emacs-lisp
33 (setq org-log-into-drawer "LOGBOOK")
36 Thanks to Wanrong Lin for this proposal.
38 *** Clock lines are now captured into the LOGBOOK drawer as well
40 The =CLOCK= drawer will be abandoned, clock lines will now also
41 end up in a drawer =LOGBOOK=. The reason for this is that it's a
42 bit useless to have two different drawers for state change notes
43 and clock lines. If you wish to keep the old way, use
45 #+begin_src emacs-lisp
46 (setq org-clock-into-drawer "CLOCK")
49 *** Added org-R.el to contrib directory
51 Dan Davison has contributed /org-R.el/ which is now in the
52 contrib directory. Org-R performs numerical computations and
53 generates graphics. Data can come from org tables, or from csv
54 files; numerical output can be stored in the org buffer as org
55 tables, and links are created to files containing graphical
56 output. Although, behind the scenes, it uses R, you do not need
57 to know anything about R. Common operations, such as tabulating
58 discrete values in a column of an org table, are available "off
59 the shelf" by specifying options on lines starting with =#+R:=.
60 However, you can also provide raw R code to be evaluated. The
61 documentation is currently the worg tutorial at
62 http://orgmode.org/worg/org-tutorials/org-R/org-R.php
64 Thanks to Dan for this great contribution.
66 *** Allow individual formatting of each TODO keyword in HTML export
68 TODO keywords in HTML export have the CSS class =todo= or =done=.
69 In addition to this, each keyword has now itself as class, so you
70 could do this in your CSS file:
73 .todo { font-weight:bold; }
74 .done { font-weight:bold; }
76 .WAITING { color:orange; }
77 .DONE { color:green; }
80 Thanks to Wanrong Lin for this request, and to Sebastian Rose for
81 help with the implementation.
83 *** New hooks for add-ons to tap into context-sensitive commands
85 Some commands in Org are context-sensitive, they will execute
86 different functions depending on context. The most important
87 example is of course =C-c C-c=, but also the =M-cursor= keys fall
90 Org has now a system of hooks that can be used by add-on packages
91 to install their own functionality into these keys. See the
92 docstring of =org-ctrl-c-ctrl-c-hook= for details. The other
93 hooks are named like =org-metaleft-hook= or
94 =org-shiftmetaright-hook=.
96 *** Publishing files irrespective of extension
98 If you set the =:base-extension= property for a publishing
99 project to the symbol =any=, all files in the directory will be
100 published, irrespective of extension.
102 Thanks to Richard Klinda for a patch to this effect.
104 *** New variable index in the manual
106 A new index in the manual lists all variables mentioned in the
107 manual, about 200 variables in total.
109 *** The ORDERED property also influences checkboxes
111 When an entry has the ORDERED property set, checkboxes in
112 the entry must be completed in order. This was already the case
113 for children TODO items, now it also applies for checkboxes.
115 Thanks to Rainer Stengele for this proposal.
117 *** The ORDERED property can be tracked with a tag
119 The =ORDERED= property is used to flag an entry so that subtasks
120 (both children TODO items and checkboxes) must be completed in
121 order. This property is most easily toggled with the command
122 =C-c C-x o=. A property was chosen for this functionality,
123 because this should be a behavior local to the current task, not
124 inherited like tags. However, properties are normally
125 invisible. If you would like visual feedback on the state of
126 this property, configure the variable
127 =org-track-ordered-property-with-tag=. If you then use =C-c C-x
128 o= to toggle the property, a tag will be toggled as well, for
131 Note that the tag itself has no meaning for the behavior of TODO
132 items and checkboxes, and that changing the tag with the usual
133 tag commands will not influence the property and therefore the
134 behavior of TODO and checkbox commands.
136 *** You may now specify line breaks in the fast tags interface
138 Up to now, the fast tags interface tried to lump as many tags as
139 possible into a single line, with the exception that groups would
140 always be on a line by themselves.
142 Now, if you use several lines to define your tags, like
145 ,#+TAGS: aa(a) bb(b) cc(c)
146 ,#+TAGS: dd(d) ee(e) ff(f)
149 then there will also be a line break after the "cc" tag in the
150 fast tag selection interface. You may also write
153 ,#+TAGS: aa(a) bb(b) cc(c) \n dd(d) ee(e) ff(f)
156 to achieve the same effect, and you can use =\n= several times in
157 order to produce empty lines. In =org-tag-alist=, newlines are
158 represented as =(:newline)=.
160 Thanks to Christopher Suckling for a patch to this effect.
162 *** When a TODO is blocked by checkboxes, keep it visible in agenda
164 When the variable =org-agenda-dim-blocked-tasks= is set to
165 =invisible=, tasks that are blocked will not be visible in the
166 agenda. If the blocking is due to child TODO entries, this does
167 make sense because the children themselves will show up in the
170 However, as John Rakestraw has [[http://thread.gmane.org/gmane.emacs.orgmode/10939][pointed out]], if the blocking is
171 done by checkboxes, no trace of these subtasks is left.
172 Therefore, when the blocking is done by checkboxes, we now
173 overrule the =invisible= setting and replace it with mere dimming
176 *** LaTeX can import Org's in-buffer definitions for TITLE, EMAIL etc.
178 If you configure =org-export-latex-import-inbuffer-stuff=,
179 in-buffer definitions like #+TITLE will be made available in the
180 LaTeX file as =\orgTITLE=.
182 This was a request by Russel Adams.
187 *** org-choose.el by Tom Breton is now included
189 Org-choose helps documenting a decision-making process by using
190 TODO keywords for different degrees of /chosenness/, and by
191 automatically keeping a set of alternatives in a consistent state.
193 Documentation for /org-choose.el/ is available [[http://orgmode.org/worg/org-contrib/org-choose.php][here]].
195 This package inserts itself into Org using hooks, so if other
196 people would like to do interesting stuff with TODO keywords for
197 special purposes, looking at Tom's code might be a good way to
200 Thanks to Tom for this interesting contribution!
202 *** orgmode.org and Worg css works now better on IE
204 Thanks to Sebastian Rose for making these changes.
206 *** When exporting a subtree, headline levels are now relative to parent
208 This was reported as a bug by William Henney and is fixed now.
210 *** Inactive dates in tables can be used for sorting.
212 When sorting table fields or entries by date, Org first tries to
213 find an active date, and, if none exist, uses a passive date if
216 This was a request by Hsui-Khuen Tang
218 *** The default for =org-return-follows-link= is back to =nil=
220 Setting it to =t= violates Emacs rules to some extent. The
221 internal implementation of this has been improved, so setting it
222 to =t= should now be pretty stable.
224 *** Automatic scheduling of siblings with org-depend.el
226 The sibling of a DONE task can now automatically be scheduled.
228 This was a patch by Andrew Hyatt.
230 *** New skipping conditions
232 The functions =org-agenda-skip-entry-if= and
233 =org-agenda-skip-subtree-if= now accept =timestamp= and
234 =nottimestamp= as additional conditions.
236 This was in response to a request by Saurabh Agrawal.
242 *** Changes to some default values of variables:
244 Here are the new default values:
247 (setq org-return-follows-link t)
249 (setq org-use-fast-todo-selection t)
251 (setq org-yank-adjusted-subtrees nil)
253 (setq org-tags-column -77)
255 (setq org-agenda-sorting-strategy
256 '((agenda time-up priority-down category-keep)
257 (todo time-up priority-down category-keep)
258 (tags time-up priority-down category-keep)
259 (search category-keep)))
262 *** Final cleanup for Emacs 21.1 pretest
268 *** Support for simple TODO dependencies
270 John Wiegley's code for enforcing simple TODO dependencies has
271 been integrated into Org-mode. Thanks John!
273 The structure of Org files (hierarchy and lists) makes it easy to
274 define TODO dependencies. A parent TODO task should not be
275 marked DONE until all subtasks (defined as children tasks) are
276 marked as DONE. And sometimes there is a logical sequence to a
277 number of (sub)tasks, so that one task cannot be acted upon
278 before all siblings above it are done. If you customize the
279 variable =org-enforce-todo-dependencies=, Org will block entries
280 from changing state while they have children that are not DONE.
281 Furthermore, if an entry has a property =ORDERED=, each of its
282 children will be blocked until all earlier siblings are marked
283 DONE. Here is an example:
286 ,* TODO Blocked until (two) is done
295 ,** TODO b, needs to wait for (a)
296 ,** TODO c, needs to wait for (a) and (b)
299 The command =C-c C-x o= toggles the value of the =ORDERED=
302 The variable =org-agenda-dim-blocked-tasks= controls how blocked
303 entries should appear in the agenda, where they can be dimmed or
306 Furthermore, you can use the variable
307 =org-enforce-todo-checkbox-dependencies= to block TODO entries
308 from switching to DONE while any checkboxes are unchecked in the entry.
310 *** Support for shift-selection in Emacs 23
312 Customize the variable =org-support-shift-select= to use S-cursor
313 key for selecting text. Make sure that you carefully read the
314 docstring of that variable first.
316 *** Adding and removing checkboxes from many lines
318 The command =C-c C-x C-b= normally toggles checkbox status in the
319 current line, or in all lines in the region. With prefix
320 argument it now either adds or removes the checkbox.
322 This was a requested by Daniel Clemente.
328 - Improved behavior of conversion commands =C-c -= and =C-c *=
329 - Table formulas may now reference fields in other tables
330 - A final hline is imagined in each table, for the sake of references
331 - A tags-todo search can now ignore timestamped items
332 - =\par= can be used to force a paragraph break, also in footnotes
337 *** Improved behavior of conversion commands =C-c -= and =C-c *=
339 The conversion commands =C-c -= and =C-c *= are now better
340 behaved and therefore more useful, I hope.
342 If there is an active region, these commands will act on the
343 region, otherwise on the current line.
345 - C-c - :: This command turns headings or normal lines into
346 items, or items into normal lines. When there is a
347 region, everything depends on the first line of the
349 - if it is a item, turn all items in the region into
351 - if it is a headline, turn all headlines in the region
353 - if it is a normal line, turn all lines into items.
354 - special case: if there is no active region and the
355 current line is an item, cycle the bullet type of the
357 - C-c * :: This command turns items and normal lines into
358 headings, or headings into normal lines. When there is
359 a region, everything depends on the first line of the
361 - if it is a item, turn all items in the region into
363 - if it is a headline, turn all headlines in the region
365 - if it is a normal line, turn all lines into headlines.
367 *** Table formulas may now reference fields in other tables
369 You may now reference constants, fields and ranges from a
370 different table, either in the current file or even in a
371 different file. The syntax is
373 : remote(NAME-OR-ID,REF)
375 where /NAME/ can be the name of a table in the current file as
376 set by a =#+TBLNAME: NAME= line before the table. It can also be
377 the ID of an entry, even in a different file, and the reference
378 then refers to the first table in that entry. /REF/ is an
379 absolute field or range reference, valid in the referenced table.
380 Note that since there is no "current filed" for the remote table,
381 all row and column references must be absolute, not relative.
383 *** A final hline is imagined in each table, for the sake of references
385 Even if a table does not end with a hline (mine never do because I
386 think it is not pretty), for the sake of references you can
387 assume there is one. So in the following table
396 a reference like =@I$1..@II$2= will now work.
398 *** A tags-todo search can now ignore timestamped items
399 The variables =org-agenda-todo-ignore-with-date=,
400 =org-agenda-todo-ignore-with-date=, and
401 =org-agenda-todo-ignore-with-date= make it possible to
402 exclude TODO entries which have this kind of planning info
403 associated with them. This is most useful for people who
404 schedule everything, and who use the TODO list mainly to find
405 things that are not yet scheduled. Thomas Morgan pointed out
406 that also the tags-todo search may serve exactly this
407 purpose, and that it might be good to have a way to make
408 these variables also apply to the tags-todo search. I can
409 see that, but could not convince myself to make this the
410 default. A new variable must be set to make this happen:
411 =org-agenda-tags-todo-honor-ignore-options=.
413 *** =\par= can be used to force a paragraph break, also in footnotes
415 The LaTeX idiom =\par= will insert a paragraph break at that
416 location. Normally you would simply leave an empty line to get
417 such a break, but this is useful for footnotes whose
418 definitions may not contain empty lines.
421 ** Incompatible changes
423 *** Short examples must have a space after the colon
425 Short literal examples can be created by preceding lines
426 with a colon. Such lines must now have a space after the
427 colon. I believe this is already general practice, but now
428 it must be like this. The only exception are lines what are
429 empty except for the colon.
433 *** Include files can now also process switches
435 The example and src switches like =-n= can now also be added
436 to include file statements:
438 : #+INCLUDE "~/.emacs" src emacs-lisp -n -r
440 Thanks to Manish for pointing out that this was not yet
443 *** Examples can be exported to HTML as text areas
445 You can now specify a =-t= switch to an example or src block,
446 to make it export to HTML as a text area. To change the
447 defaults for height (number of lines in the example) and
448 width of this area (80), use the =-h= and =-w= switches.
450 Thanks to Ulf Stegemann for driving this development.
452 *** LaTeX_CLASS can be given as a property
454 When exporting a single subtree by selecting it as a region
455 before export, the LaTeX class for the export will be taken
456 from the =LaTeX_CLASS= property of the entry if present.
458 Thanks to Robert Goldman for this request.
460 *** Better handling of inlined images in different backends
462 Two new variables govern which kind of files can be inlined
463 during export. These are
464 =org-export-html-inline-image-extensions= and
465 =org-export-latex-inline-image-extensions=. Remember that
466 links are turned into an inline image if they are a pure link
467 with no description. HTML files can inline /.png/, /.jpg/,
468 and /.gif/ files, while LaTeX files, when processed with
469 /pdflatex/, can inline /.png/, /.jpg/, and /.pdf/ files.
470 These also represent the default settings for the new
471 variables. Note that this means that pure links to /.pdf/
472 files will be inlined - to avoid this for a particular link,
473 make sure that the link has a description part which is not
474 equal to the link part.
476 *** Links by ID now continue to work in HTML exported files
478 If you make links by ID, these links will now still work in
479 HTML exported files, provided that you keep the relative path
480 from link to target file the same.
482 Thanks to Friedrich Delgado Friedrichs for pushing this over
485 *** The relative timer can be paused
487 The new command `C-c C-x ,' will pause the relative timer.
488 When the relative timer is running, its value will be shown
489 in the mode line. To get rid of this display, you need to
490 really stop the timer with `C-u C-c C-x ,'.
492 Thanks to Alan Davis for driving this change.
494 *** The attachment directory may now be chosen by the user
496 Instead of using the automatic, unique directory related to
497 the entry ID, you can also use a chosen directory for the
498 attachments of an entry. This directory is specified by the
499 ATTACH_DIR property. You can use `C-c C-a s' to set this
502 Thanks to Jason Jackson for this proposal.
504 *** You can use a single attachment directory for a subtree
506 By setting the property ATTACH_DIR_INHERIT, you can now tell
507 Org that children of the entry should use the same directory
508 for attachments, unless a child explicitly defines its own
509 directory with the ATTACH_DIR property. You can use the
510 command `C-c C-a i' to set this property in an entry.
517 - Line numbers and references in literal examples
518 - New hooks for export preprocessing
519 - Capture column view into a different file
525 Org-mode now directly supports the creation of footnotes. In
526 contrast to the /footnote.el/ package, Org-mode's footnotes are
527 designed for work on a larger document, not only for one-off
528 documents like emails. The basic syntax is similar to the one
529 used by /footnote.el/, i.e. a footnote is defined in a paragraph
530 that is started by a footnote marker in square brackets in column
531 0, no indentation allowed. The footnote reference is simply the
532 marker in square brackets inside text. For example:
535 The Org homepage[fn:1] now looks a lot better than it used to.
537 [fn:1] The link is: http://orgmode.org
540 Org-mode extends the number-based syntax to /named/ footnotes and
541 optional inline definition. Using plain numbers as markers is
542 supported for backward compatibility, but not encouraged because
543 of possible conflicts with LaTeX syntax. Here are the valid
546 - [1] :: A plain numeric footnote marker.
548 - [fn:name] :: A named footnote reference, where `name' is a
549 unique label word or, for simplicity of automatic creation,
552 - [fn:: This is the inline definition of this footnote] :: A
553 LaTeX-like anonymous footnote where the definition is given
554 directly at the reference point.
556 - [fn:name: a definition] :: An inline definition of a footnote,
557 which also specifies a name for the note. Since Org allows
558 multiple references to the same note, you can then use use
559 `[fn:name]' to create additional references.
561 Footnote labels can be created automatically, or you create names
562 yourself. This is handled by the variable
563 =org-footnote-auto-label= and its corresponding =#+STARTUP=
564 keywords, see the docstring of that variable for details.
566 The following command handles footnotes:
568 - C-c C-x f :: The footnote action command. When the cursor is
569 on a footnote reference, jump to the definition. When it is
570 at a definition, jump to the (first) reference. Otherwise,
571 create a new footnote. Depending on the variable
572 `org-footnote-define-inline' (with associated =#+STARTUP=
573 options =fninline= and =nofninline=), the definitions will
574 be placed right into the text as part of the reference, or
575 separately into the location determined by the variable
576 =org-footnote-section=.
577 When this command is called with a prefix argument, a menu
578 of additional options is offered:
579 - s :: Sort the footnote definitions by reference sequence.
580 During editing, Org makes no effort to sort footnote
581 definitions into a particular sequence. If you want
582 them sorted, use this command, which will also move
583 entries according to =org-footnote-section=.
584 - n :: Normalize the footnotes by collecting all
585 definitions (including inline definitions) into a
586 special section, and then numbering them in
587 sequence. The references will then also be
588 numbers. This is meant to be the final step before
589 finishing a document (e.g. sending off an email).
590 The exporters do this automatically, and so could
591 something like `message-send-hook'.
592 - d :: Delete the footnote at point, and all references to it.
594 - C-c C-c :: If the cursor is on a footnote reference, jump to
595 the definition. If it is a the definition, jump back to the
596 reference. When called with a prefix argument at either
597 location, offer the same menu as `C-u C-c C-x f'.
599 - C-c C-o or mouse-1/2 :: Footnote labels are also links to the
600 corresponding definition/reference, and you can use the
601 usual commands to follow these links.
603 Org-mode's footnote support is designed so that it should also
604 work in buffers that are not in Org-mode, for example in email
605 messages. Just bind =org-footnote-action= to a global key like
608 The main trigger for this development came from a hook function
609 written by Paul Rivier, to implement named footnotes and to
610 convert them to numbered ones before export. Thanks, Paul!
612 Thanks also to Scot Becker for a thoughtful post bringing this
613 subject back onto the discussion table, and to Matt Lundin for
614 the idea of named footnotes and his prompt testing of the new
617 *** Line numbers and references in literal examples
619 Literal examples introduced with =#+BEGIN_EXAMPLE= or =#+BEGIN_SRC=
620 do now allow optional line numbering in the example.
621 Furthermore, links to specific code lines are supported, greatly
622 increasing Org-mode's utility for writing tutorials and other
625 Code references use special labels embedded directly into the
626 source code. Such labels look like "(ref:name)" and must be
627 unique within a document. Org-mode links with "(name)" in the
628 link part will be correctly interpreted, both while working with
629 an Org file (internal links), and while exporting to the
630 different backends. Line numbering and code references are
631 supported for all three major backends, HTML, LaTeX, and ASCII.
632 In the HTML backend, hovering the mouse over a link to a source
633 line will remote-highlight the referenced code line.
635 The options for the BEGIN lines are:
637 - -n :: Number the lines in the example
638 - +n :: Like -n, but continue numbering from where the previous
640 - -r :: Remove the coderef cookies from the example, and replace
641 links to this reference with line numbers. This option
642 takes only effect if either -n or +n are given as well.
643 If -r is not given, coderefs simply use the label name.
644 - -l "fmt" :: Define a local format for coderef labels, see the
645 variable =org-coderef-label-format= for details. Use this
646 of the default syntax causes conflicts with the code in the
647 code snippet you are using.
652 #+begin_src emacs-lisp -n -r
653 (defmacro org-unmodified (&rest body) (ref:def)
654 "Execute body without changing `buffer-modified-p'."
655 `(set-buffer-modified-p (ref:back)
656 (prog1 (buffer-modified-p) ,@body)))
658 [[(def)][Line (def)]] contains the macro name. Later at line [[(back)]],
662 When exported, this is translated to:
663 #+begin_src emacs-lisp -n -r
664 (defmacro org-unmodified (&rest body) (ref:def)
665 "Execute body without changing `buffer-modified-p'."
666 `(set-buffer-modified-p (ref:back)
667 (prog1 (buffer-modified-p) ,@body)))
669 [[(def)][Line (def)]] contains the macro name. Later at line [[(back)]],
672 Thanks to Ilya Shlyakhter for proposing this feature set. Thanks
673 to Sebastian Rose for the key Javascript element that made the
674 remote highlighting possible.
676 *** New hooks for export preprocessing
677 The export preprocessor now runs more hooks, to allow
678 better-timed tweaking by user functions:
680 - =org-export-preprocess-hook= ::
681 Pretty much the first thing in the preprocessor. But org-mode
682 is already active in the preprocessing buffer.
684 - =org-export-preprocess-after-include-files-hook= ::
685 This is run after the contents of included files have been inserted.
687 - =org-export-preprocess-after-tree-selection-hook= ::
688 This is run after selection of trees to be exported has
689 happened. This selection includes tags-based selection, as
690 well as removal of commented and archived trees.
692 - =org-export-preprocess-before-backend-specifics-hook= ::
693 Hook run before backend-specific functions are called during preprocessing.
695 - =org-export-preprocess-final-hook= ::
696 Hook for preprocessing an export buffer. This is run as the
697 last thing in the preprocessing buffer, just before returning
698 the buffer string to the backend.
700 *** Capture column view into a different file
702 The :id parameter for the dynamic block capturing column view
703 can now truly be an ID that will also be found in a
704 different file. Also, it can be like =file:path/to/file=, to
705 capture the global column view from a different file.
707 Thanks to Francois Lagarde for his report that IDs outside
708 the current file would not work.
711 Cleanup of many small bugs, and one new feature.
715 *** References to last table row with special names
717 Fields in the last row of a table can now be referenced with
718 $LR1, $LR2, etc. These references can appear both on the
719 left hand side and right hand side of a formula.
723 This version reverses the introduction of @0 as a reference to
724 the last rwo in a table, because of a conflict with the use of
725 @0 for the current row.
730 - All known LaTeX export issues fixed
731 - Captions and attributes for figures and tables.
732 - Better implementation for entry IDs
733 - Spreadsheet references to the last table line.
734 - Old syntax for link attributes abandoned
736 ** Incompatible changes
737 *** Old syntax for link attributes abandoned
739 There used to be a syntax for setting link attributes for
740 HTML export by enclosing the attributes into double braces
741 and adding them to the link itself, like
744 [[./img/a.jpg{{alt="an image"}}] ]
747 This syntax is not longer supported, use instead
750 ,#+ATTR_HTML: alt="an image"
756 *** All known LaTeX export issues fixed
758 All the remaining issues with the LaTeX exporter have hopefully
759 been addressed in this release. In particular, this covers
760 quoting of special characters in tables and problems with
761 exporting files where the headline is in the first line, or with
764 *** Captions and attributes for figures and tables.
766 Tables, and Hyperlinks that represent inlined images, can now be
767 equipped with additional information that will be used during
768 export. The information will be taken from the following special
769 lines in the buffer and apply to the first following table or
772 - #+CAPTION: :: The caption of the image or table. This string
773 should be processed according to the export backend, but
774 this is not yet done.
776 - #+LABEL: :: A label to identify the figure/table for cross
777 references. For HTML export, this string will become the
778 ID for the ~<div class="figure">~ element that encapsulates
779 the image tag and the caption. For LaTeX export, this
780 string will be used as the argument of a ~\label{...}~
781 macro. These labels will be available for internal links
782 like ~[[label][Table] ]~.
784 - #+ATTR_HTML: :: Attributes for HTML export of image, to be
785 added as attributes into the ~<img...>~ tag. This string
786 will not be processed, so it should have immediately the
789 - #+ATTR_LaTeX: :: Attributes for LaTeX export of images and
791 For /images/, this string is directly inserted into
792 the optional argument of the ~\includegraphics[...]{file}~
793 command, to specify scaling, clipping and other options.
794 This string will not be processed, so it should have
795 immediately the right format, like =width=5cm,angle=90=.\\
796 For /tables/, this can currently contain the keyword
797 =longtable=, to request typesetting of the table using the
798 longtable package, which automatically distributes the table
799 over several pages if needed. Also, the attributes line may
800 contain an alignment string for the tabular environment, like
801 =longtable,align=l|lrl=
803 For LaTeX export, if either a caption or a label is given, the element
804 will be exported as a float, i.e. wrapped into a figure or table
807 *** Better implementation for entry IDs
809 Unique identifiers for entries can now be used more efficiently.
810 Internally, a hash array has replaced the alist used so far to
811 keep track of the files in which an ID is defined. This makes it
812 quite fast to find an entry by ID.
814 There is a new link type which looks like this:
817 id:GLOBALLY-UNIQUE-IDENTIFIER
820 This link points to a specific entry. When you move the entry to
821 a different file, for example if you move it to an archive
822 file, the link will continue to work.
824 The file /org-id.el/ contains an API that can be used to write
825 code using these identifiers, including creating IDs and finding
826 them wherever they are.
828 Org has its own method to create unique identifiers, but if the system
829 has /uuidgen/ command installed (Mac's and Linux systems generally
830 do), it will be used by default (a change compared to the earlier
831 implmentation, where you explicitdly had to opt for uuidgen). You can
832 also select the method by hand, using the variable =org-id-method=.
834 If the ID system ever gets confused about where a certain ID is, it
835 initiates a global scan of all agenda files with associated archives,
836 all files previously known containing any IDs, and all currently
837 visited Org-mode files to rebuild the hash. You can also initiate
838 this by hand: =M-x org-id-update-id-locations=. Running this command
839 will also dump into the =*Messages*= buffer information about any
840 duplicate IDs. These should not exist, and Org will never /make/ the
841 same ID twice, but if you /copy/ an entry with its properties,
842 duplicate IDs will inevitably be produced. Unfortunately, this is
843 unavoidable in a plain text system that allows you to edit the text in
844 arbitrary ways, and a portion of care on your side is needed to keep
847 The hash is stored in the file =~/.emacs.d/.org-id-locations=.
848 This is also a change from previous versions where the file was
849 =~/.org=id-locations=. Therefore, you can remove this old file
850 if you have it. I am not sure what will happen if the =.emacs.d=
851 directory does not exists in your setup, but in modern Emacsen, I
852 believe it should exist. If you do not want to use IDs across
853 files, you can avoid the overhead with tracking IDs by
854 customizing the variable =org-id-track-globally=. IDs can then
855 still be used for links inside a single file.
857 IDs will also be used when you create a new link to an Org-mode
858 buffer. If you use =org-store-link= (normally at =C-c l=) inside
859 en entry in an Org-mode buffer, and ID property will be created
860 if it does not exist, and the stored link will be an =id:= link.
861 If you prefer the much less secure linking to headline text, you
862 can configure the variable =org-link-to-org-use-id=. The default
863 setting for this variable is =create-if-interactive=, meaning
864 that an ID will be created when you store a link interactively,
865 but not if you happen to be in an Org-mode file while you create
866 a remember note (which usually has a link to the place where you
867 were when starting remember).
869 *** Spreadsheet references to the last table line.
871 You may now use =@0= to reference the last dataline in a table
872 in a stable way. This is useful in particular for automatically
873 generated tables like the ones using /org-collector.el/ by Eric
879 - New relative timer to support timed notes
880 - Special faces can be set for individual tags
881 - The agenda shows now all tags, including inherited ones.
882 - Exclude some tags from inheritance.
883 - More special values for time comparisons in property searches
884 - Control for exporting meta data
885 - Cut and Paste with hot links from w3m to Org
886 - LOCATION can be inherited for iCalendar export
887 - Relative row references crossing hlines now throw an error
889 ** Incompatible Changes
891 *** Relative row references crossing hlines now throw an error
893 Relative row references in tables look like this: "@-4" which
894 means the forth row above this one. These row references are
895 not allowed to cross horizontal separator lines (hlines). So
896 far, when a row reference violates this policy, Org would
897 silently choose the field just next to the hline.
899 Tassilo Horn pointed out that this kind of hidden magic is
900 actually confusing and may cause incorrect formulas, and I do
901 agree. Therefore, trying to cross a hline with a relative
902 reference will now throw an error.
904 If you need the old behavior, customize the variable
905 `org-table-error-on-row-ref-crossing-hline'.
909 *** New relative timer to support timed notes
911 Org now supports taking timed notes, useful for example while
912 watching a video, or during a meeting which is also recorded.
915 Insert a relative time into the buffer. The first time
916 you use this, the timer will be started. When called
917 with a prefix argument, the timer is reset to 0.
920 Insert a description list item with the current relative
921 time. With a prefix argument, first reset the timer to 0.
924 Once the time list has been initiated, you can also use the
925 normal item-creating command to insert the next timer item.
928 Reset the timer without inserting anything into the buffer.
929 By default, the timer is reset to 0. When called with a
930 =C-u= prefix, reset the timer to specific starting
931 offset. The user is prompted for the offset, with a
932 default taken from a timer string at point, if any, So this
933 can be used to restart taking notes after a break in the
934 process. When called with a double prefix argument
935 =C-c C-u=, change all timer strings in the active
936 region by a certain amount. This can be used to fix timer
937 strings if the timer was not started at exactly the right
940 Thanks to Alan Dove, Adam Spiers, and Alan Davis for
941 contributions to this idea.
943 *** Special faces can be set for individual tags
945 You may now use the variable =org-tag-faces= to define the
946 face used for specific tags, much in the same way as you can
947 do for TODO keywords.
949 Thanks to Samuel Wales for this proposal.
951 *** The agenda shows now all tags, including inherited ones.
953 This request has come up often, most recently it was
954 formulated by Tassilo Horn.
956 If you prefer the old behavior of only showing the local
957 tags, customize the variable =org-agenda-show-inherited-tags=.
959 *** Exclude some tags from inheritance.
961 So far, the only way to select tags for inheritance was to
962 allow it for all tags, or to do a positive selection using
963 one of the more complex settings for
964 `org-use-tag-inheritance'. It may actually be better to
965 allow inheritance for all but a few tags, which was difficult
966 to achieve with this methodology.
968 A new option, `org-tags-exclude-from-inheritance', allows to
969 specify an exclusion list for inherited tags.
971 *** More special values for time comparisons in property searches
973 In addition to =<now>=, =<today>=, =<yesterday>=, and
974 =<tomorrow>=, there are more special values accepted now in
975 time comparisons in property searches: You may use strings
976 like =<+3d>= or =<-2w>=, with units d, w, m, and y for day,
977 week, month, and year, respectively
979 Thanks to Linday Todd for this proposal.
981 *** Control for exporting meta data
983 All the metadata in a headline, i.e. the TODO keyword, the
984 priority cookie, and the tags, can now be excluded from
985 export with appropriate options:
987 | Variable | Publishing property | OPTIONS switch |
988 |-------------------------------+---------------------+----------------|
989 | org-export-with-todo-keywords | :todo-keywords | todo: |
990 | org-export-with-tags | :tags | tags: |
991 | org-export-with-priority | :priority | pri: |
993 *** Cut and Paste with hot links from w3m to Org
995 You can now use the key =C-c C-x M-w= in a w3m buffer with
996 HTML content to copy either the region or the entire file in
997 a special way. When you yank this text back into an Org-mode
998 buffer, all links from the w3m buffer will continue to work
1001 For this to work you need to load the new file /org-w3m.el./
1002 Please check your org-modules variable to make sure that this
1005 Thanks for Richard Riley for the idea and to Andy Stewart for
1008 *** LOCATION can be inherited for iCalendar export
1010 The LOCATION property can now be inherited during iCalendar
1011 export if you configure =org-use-property-inheritance= like
1014 #+begin_src emacs-lisp
1015 (setq org-use-property-inheritance '("LOCATION"))
1022 - Keybindings in Remember buffers can be configured
1023 - Support for ido completion
1024 - New face for date lines in agenda column view
1025 - Invisible targets become now anchors in headlines.
1026 - New contributed file /org-exp-blocks.el/
1027 - New contributed file /org-eval-light.el/
1029 - BBDB links may use regular expressions.
1030 - Link abbreviations can use %h to insert a url-encoded target value
1031 - Improved XHTML compliance
1035 *** Keybindings in Remember buffers can be configured
1037 The remember buffers created with Org's extensions are in
1038 Org-mode, which is nice to prepare snippets that will
1039 actually be stored in Org-mode files. However, this makes it
1040 hard to configure key bindings without modifying the Org-mode
1041 keymap. There is now a minor mode active in these buffers,
1042 `org-remember-mode', and its keymap org-remember-mode-map can
1043 be used for key bindings. By default, this map only contains
1044 the bindings for =C-c C-c= to store the note, and =C-c C-k=
1045 to abort it. Use `org-remember-mode-hook' to define your own
1048 #+begin_src emacs-lisp
1050 'org-remember-mode-hook
1052 (define-key org-remember-mode-map
1053 "\C-x\C-s" 'org-remember-finalize)))
1056 If you wish, you can also use this to free the =C-c C-c=
1057 binding (by binding this key to nil in the minor mode map),
1058 so that you can use =C-c C-c= again to set tags.
1060 This modification is based on a request by Tim O'Callaghan.
1062 *** Support for ido completion
1064 You can now get the completion interface from /ido.el/ for
1065 many of Org's internal completion commands by turning on the
1066 variable =org-completion-use-ido=. =ido-mode= must also be
1067 active before you can use this.
1069 This change is based upon a request by Samuel Wales.
1071 *** New face for date lines in agenda column view
1073 When column view is active in the agenda, and when you have
1074 summarizing properties, the date lines become normal column
1075 lines and the separation between different days becomes
1076 harder to see. If this bothers you, you can now customize
1077 the face =org-agenda-column-dateline=.
1079 This is based on a request by George Pearson.
1081 *** Invisible targets become now anchors in headlines.
1083 These anchors can be used to jump to a directly with an HTML
1084 link, just like the =sec-xxx= IDs. For example, the
1085 following will make a http link
1086 =//domain/path-to-my-file.html#dummy= work:
1093 This is based on a request by Matt Lundin.
1095 *** New contributed file /org-exp-blocks.el/
1097 This new file implements special export behavior of
1098 user-defined blocks. The currently supported blocks are
1100 - comment :: Comment blocks with author-specific markup
1101 - ditaa :: conversion of ASCII art into pretty png files
1102 using Stathis Sideris' /ditaa.jar/ program
1103 - dot :: creation of graphs in the /dot/ language
1104 - R :: Sweave type exporting using the R program
1106 For more details and examples, see the file commentary in
1107 /org-exp-blocks.el/.
1109 Kudos to Eric Schulte for this new functionality, after
1110 /org-plot.el/ already his second major contribution. Thanks
1111 to Stathis for this excellent program, and for allowing us to
1112 bundle it with Org-mode.
1114 *** New contributed file /org-eval-light.el/
1116 This module gives control over execution Emacs Lisp code
1117 blocks included in a file.
1119 Thanks to Eric Schulte also for this file.
1121 *** Link translation
1123 You can now configure Org to understand many links created
1124 with the Emacs Planner package, so you can cut text from
1125 planner pages and paste them into Org-mode files without
1126 having to re-write the links. Among other things, this means
1127 that the command =org-open-at-point-global= which follows
1128 links not only in Org-mode, but in arbitrary files like
1129 source code files etc, will work also with links created by
1130 planner. The following customization is needed to make all of
1133 #+begin_src emacs-lisp
1134 (setq org-link-translation-function
1135 'org-translate-link-from-planner)
1138 I guess an inverse translator could be written and integrated
1141 *** BBDB links may use regular expressions.
1143 This did work all along, but only now I have documented it.
1145 *** =yank-pop= works again after yanking an outline tree
1147 Samuel Wales had noticed that =org-yank= did mess up this
1148 functionality. Now you can use =yank-pop= again, the only
1149 restriction is that the so-yanked text will not be
1150 pro/demoted or folded.
1152 *** Link abbreviations can use %h to insert a url-encoded target value
1154 Thanks to Steve Purcell for a patch to this effect.
1156 *** Improved XHTML compliance
1158 Thanks to Sebastian Rose for pushing this.
1160 *** Many bug fixes again.
1165 - A region of entries can now be refiled with a single command
1166 - Fine-tuning the behavior of `org-yank'
1167 - Formulas for clocktables
1168 - Better implementation of footnotes for HTML export
1169 - More languages for HTML export.
1173 *** A region of entries can now be refiled with a single command
1175 With =transient-make-mode= active (=zmacs-regions= under
1176 XEmacs), you can now select a region of entries and refile
1177 them all with a single =C-c C-w= command.
1179 Thanks to Samuel Wales for this useful proposal.
1181 *** Fine-tuning the behavior of =org-yank=
1183 The behavior of Org's yanking command has been further
1184 fine-tuned in order to avoid some of the small annoyances
1185 this command caused.
1187 - Calling =org-yank= with a prefix arg will stop any special
1188 treatment and directly pass through to the normal =yank=
1189 command. Therefore, you can now force a normal yank with
1192 - Subtrees will only be folded after a yank if doing so will
1193 now swallow any non-white characters after the yanked text.
1194 This is, I think a really important change to make the
1195 command work more sanely.
1197 *** Formulas for clocktables
1199 You can now add formulas to a clock table, either by hand, or
1200 with a =:formula= parameter. These formulas can be used to
1201 create additional columns with further analysis of the
1204 Thanks to Jurgen Defurne for triggering this addition.
1206 *** Better implementation of footnotes for HTML export
1208 The footnote export in 6.11 really was not good enough. Now
1209 it works fine. If you have customized
1210 =footnote-section-tag=, make sure that your customization is
1211 matched by =footnote-section-tag-regexp=.
1213 Thanks to Sebastian Rose for pushing this change.
1215 *** More languages for HTML export.
1217 More languages are supported during HTML export. This is
1218 only relevant for the few special words Org inserts, like
1219 "Table of Contents", or "Footnotes". Also the encoding
1220 issues with this feature seem to be solved now.
1222 Thanks to Sebastian Rose for pushing me to fix the encoding
1229 - Yanking subtree with =C-y= now adjusts the tree level
1230 - State changes can now be shown in the log mode in the agenda
1231 - Footnote in HTML export are now collected at the end of the document
1232 - HTML export now validates again as XHTML
1233 - The clock can now be resumed after exiting and re-starting Emacs
1234 - Clock-related data can be saved and resumed across Emacs sessions
1235 - Following file links can now use C-u C-u to force use of an external app
1236 - Inserting absolute files names now abbreviates links with "~"
1237 - Links to attachment files
1238 - Completed repeated tasks listed briefly in agenda
1239 - Remove buffers created during publishing are removed
1243 *** Yanking subtree with =C-y= now adjusts the tree level
1244 When yanking a cut/copied subtree or a series of trees, the
1245 normal yank key =C-y= now adjusts the level of the tree to
1246 make it fit into the current outline position, without losing
1247 its identity, and without swallowing other subtrees.
1249 This uses the command =org-past-subtree=. An additional
1250 change in that command has been implemented: Normally, this
1251 command picks the right outline level from the surrounding
1252 *visible* headlines, and uses the smaller one. So if the
1253 cursor is between a level 4 and a level 3 headline, the tree
1254 will be pasted as level 3. If the cursor is actually *at*
1255 the beginning of a headline, the level of that headline will
1256 be used. For example, lets say you have a tree like this:
1262 ,(2)* Level one again
1265 with (1) and (2) indicating possible cursor positions for the
1266 insertion. When at (1), the tree will be pasted as level 2.
1267 When at (2), it will be pasted as level 1.
1269 If you do not want =C-y= to behave like this, configure the
1270 variable =org-yank-adjusted-subtrees=.
1272 Thanks to Samuel Wales for this idea and a partial implementation.
1274 *** State changes can now be shown in the log mode in the agenda
1276 If you configure the variable =org-agenda-log-mode-items=,
1277 you can now request that all logged state changes be included
1278 in the agenda when log mode is active. If you find this too
1279 much for normal applications, you can also temporarily
1280 request the inclusion of state changes by pressing =C-u l= in
1283 This was a request by Hsiu-Khuern Tang.
1285 You can also press `C-u C-u l' to get *only* log items in the
1286 agenda, withour any timestamps/deadlines etc.
1288 *** Footnote in HTML export are now collected at the end of the document
1289 Previously, footnotes would be left in the document where
1290 they are defined, now they are all collected and put into a
1291 special =<div>= at the end of the document.
1293 Thanks to Sebastian Rose for this request.
1295 *** HTML export now validates again as XHTML.
1297 Thanks to Sebastian Rose for pushing this cleanup.
1299 *** The clock can now be resumed after exiting and re-starting Emacs
1301 If the option =org-clock-in-resume= is t, and the first clock
1302 line in an entry is unclosed, clocking into that task resumes
1303 the clock from that time.
1305 Thanks to James TD Smith for a patch to this effect.
1307 *** Clock-related data can be saved and resumed across Emacs sessions
1309 The data saved include the contents of =org-clock-history=,
1310 and the running clock, if there is one.
1312 To use this, you will need to add to your .emacs
1314 #+begin_src emacs-lisp
1315 (setq org-clock-persist t)
1316 (setq org-clock-in-resume t)
1317 (org-clock-persistence-insinuate)
1320 Thanks to James TD Smith for a patch to this effect.
1322 *** Following file links can now use C-u C-u to force use of an external app.
1324 So far you could only bypass your setup in `org-file-apps'
1325 and force opening a file link in Emacs by using a =C-u= prefix arg
1326 with =C-c C-o=. Now you can call =C-u C-u C-c C-o= to force
1327 an external application. Which external application depends
1328 on your system. On Mac OS X and Windows, =open= is used. On
1329 a GNU/Linux system, the mailcap settings are used.
1331 This was a proposal by Samuel Wales.
1333 *** Inserting absolute files names now abbreviates links with "~".
1335 Inserting file links with =C-u C-c C-l= was buggy if the
1336 setting of `org-link-file-path-type' was `adaptive' (the
1337 default). Absolute file paths were not abbreviated relative
1338 to the users home directory. This bug has been fixed.
1340 Thanks to Matt Lundin for the report.
1342 *** Links to attachment files
1344 Even though one of the purposes of entry attachments was to
1345 reduce the number of links in an entry, one might still want
1346 to have the occasional link to one of those files. You can
1347 now use link abbreviations to set up a special link type that
1348 points to attachments in the current entry. Note that such
1349 links will only work from within the same entry that has the
1350 attachment, because the directory path is entry specific.
1351 Here is the setup you need:
1353 #+begin_src emacs-lisp
1354 (setq org-link-abbrev-alist '(("att" . org-attach-expand-link)))
1357 After this, a link like this will work
1360 [[att:some-attached-file.txt]]
1362 This was a proposal by Lindsay Todd.
1364 *** Completed repeated tasks listed briefly in agenda
1366 When a repeating task, listed in the daily/weekly agenda under
1367 today's date, is completed from the agenda, it is listed as
1368 DONE in the agenda until the next update happens. After the
1369 next update, the task will have disappeared, of course,
1370 because the new date is no longer today.
1372 *** Remove buffers created during publishing are removed
1374 Buffers that are created during publishing are now deleted
1375 when the publishing is over. At least I hope it works like this.
1381 - Secondary agenda filtering is becoming a killer feature
1382 - Setting tags has now its own binding, =C-c C-q=
1383 - Todo state changes can trigger tag changes
1384 - C-RET will now always insert a new headline, never an item.
1385 - Customize org-mouse.el feature set to free up mouse events
1386 - New commands for export all the way to PDF (through LaTeX)
1387 - Some bug fixed for LaTeX export, more bugs remain.
1391 *** Enhancements to secondary agenda filtering
1393 This is, I believe, becoming a killer feature. It allows you
1394 to define fewer and more general custom agenda commands, and
1395 then to do the final narrowing to specific tasks you are
1396 looking for very quickly, much faster than calling a new
1399 If you have not tries this yet, you should!
1401 **** You can now refining the current filter by an additional criterion
1402 When filtering an existing agenda view with =/=, you can
1403 now narrow down the existing selection by an additional
1404 condition. Do do this, use =\= instead of =/= to add the
1405 additional criterion. You can also press =+= or =-= after
1406 =/= to add a positive or negative condition. A condition
1407 can be a TAG, or an effort estimate limit, see below.
1409 **** It is now possible to filter for effort estimates
1410 This means to filter the agenda for the value of the Effort
1411 property. For this you should best set up global allowed
1412 values for effort estimates, with
1414 #+begin_src emacs-lisp
1415 (setq org-global-properties
1416 '(("Effort_ALL" . "0 0:10 0:30 1:00 2:00 3:00 4:00")))
1419 You may then select effort limits with single keys in the
1420 filter. It works like this: After =/= or =\=, first select
1421 the operator which you want to use to compare effort
1424 : < Select entries with effort smaller than or equal to the limit
1425 : > Select entries with effort larger than or equal to the limit
1426 : = Select entries with effort equal to the limit
1428 After that, you can press a single digit number which is
1429 used as an index to the allowed effort estimates.
1431 If you do not use digits to fast-select tags, you can even
1432 skip the operator, which will then default to
1433 `org-agenda-filter-effort-default-operator', which is by
1436 Thanks to Manish for the great idea to include fast effort
1437 filtering into the agenda filtering process.
1439 **** The mode line will show the active filter
1440 For example, if there is a filter in place that does select
1441 for HOME tags, against EMAIL tags, and for tasks with an
1442 estimated effort smaller than 30 minutes, the mode-line with
1443 show =+HOME-EMAIL+<0:30=
1445 **** The filter now persists when the agenda view is refreshed
1446 All normal refresh commands, including those that move the
1447 weekly agenda from one week to the next, now keep the
1448 current filter in place.
1450 You need to press =/ /= to turn off the filter. However,
1451 when you run a new agenda command, for example going from
1452 the weekly agenda to the TODO list, the filter will be
1455 *** Setting tags has now its own binding, =C-c C-q=
1457 You can still use =C-c C-c= on a headline, but the new
1458 binding should be considered as the main binding for this
1459 command. The reasons for this change are:
1461 - Using =C-c C-c= for tags is really out of line with other
1464 - I hate it in Remember buffers when I try to set tags and I
1465 cannot, because =C-c C-c= exits the buffer :-(
1467 - =C-c C-q= will also work when the cursor is somewhere down
1468 in the entry, it does not have to be on the headline.
1470 *** Todo state changes can trigger tag changes
1472 The new option =org-todo-state-tags-triggers= can be used to
1473 define automatic changes to tags when a TODO state changes.
1474 For example, the setting
1476 : (setq org-todo-state-tags-triggers
1477 : '((done ("Today" . nil) ("NEXT" . nil))
1478 : ("WAITING" ("Today" . t))))
1480 will make sure that any change to any of the DONE states will
1481 remove tags "Today" and "NEXT", while switching to the
1482 "WAITING" state will trigger the tag "Today" to be added.
1484 I use this mostly to get rid of TODAY and NEXT tags which I
1485 apply to select an entry for execution in the near future,
1486 which I often prefer to specific time scheduling.
1488 *** C-RET will now always insert a new headline, never an item.
1489 The new headline is inserted after the current subtree.
1491 Thanks to Peter Jones for patches to fine-tune this behavior.
1493 *** Customize org-mouse.el feature set
1494 There is a new variable =org-mouse-features= which gives you
1495 some control about what features of org-mouse you want to
1496 use. Turning off some of the feature will free up the
1497 corresponding mouse events, or will avoid activating special
1498 regions for mouse clicks. By default I have urned off the
1499 feature to use drag mouse events to move or promote/demote
1500 entries. You can of course turn them back on if you wish.
1502 This variable may still change in the future, allowing more
1503 fine-grained control.
1505 *** New commands for export to PDF
1507 This is using LaTeX export, and then processes it to PDF
1510 : C-c C-e p process to PDF.
1511 : C-c C-e d process to PDF, and open the file.
1514 - \usepackage{graphicx} is now part of the standard class
1516 - Several bugs fixed, but definitely not all of them :-(
1518 *** New option `org-log-state-notes-insert-after-drawers'
1520 Set this to =t= if you want state change notes to be inserted
1521 after any initial drawers, i.e drawers the immediately follow
1522 the headline and the planning line (the one with
1523 DEADLINE/SCHEDULED/CLOSED information).
1527 *** =org-file-apps= now uses regular expressions, see [[*%20org%20file%20apps%20now%20uses%20regular%20repressions%20instead%20of%20extensions][below]]
1531 *** =org-file-apps= now uses regular repressions instead of extensions
1532 Just like in =auto-mode-alist=, car's in the variable
1533 =org-file-apps= that are strings are now interpreted as
1534 regular expressions that are matched against a file name. So
1535 instead of "txt", you should now write "\\.txt\\'" to make
1536 sure the matching is done correctly (even though "txt" will
1537 be recognized and still be interpreted as an extension).
1539 There is now a shortcut to get many file types visited by
1540 Emacs. If org-file-apps contains `(auto-mode . emacs)', then
1541 any files that are matched by `auto-mode-alist' will be
1544 *** Changes to the attachment system
1546 - The default method to attach a file is now to copy it
1547 instead of moving it.
1548 - You can modify the default method using the variable
1549 `org-attach-method'. I believe that most Unix people want
1550 to set it to `ln' to create hard links.
1551 - The keys =c=, =m=, and =l= specifically select =copy=,
1552 =move=, or =link=, respectively, as the attachment method
1553 for a file, overruling `org-attach-method'.
1554 - To create a new attachment as an Emacs buffer, you have not
1555 now use =n= instead of =c=.
1556 - The file list is now always retrieved from the directory
1557 itself, not from the "Attachments" property. We still
1558 keep this property by default, but you can turn it off, by
1559 customizing the variable =org-attach-file-list-property=.
1563 ** Incompatible changes
1565 - Changes in the structure of IDs, see [[*The%20default%20structure%20of%20IDs%20has%20changed][here]] for details.
1567 - C-c C-a has been redefined, see [[*%20C%20c%20C%20a%20no%20longer%20calls%20show%20all][here]] for details.
1571 *** The default structure of IDs has changed
1573 IDs created by Org have changed a bit:
1574 - By default, there is no prefix on the ID. There used to be
1575 an "Org" prefix, but I now think this is not necessary.
1576 - IDs use only lower-case letters, no upper-case letters
1577 anymore. The reason for this is that IDs are now also used
1578 as directory names for org-attach, and some systems do not
1579 distinguish upper and lower case in the file system.
1580 - The ID string derived from the current time is now
1581 /reversed/ to become an ID. This assures that the first
1582 two letters of the ID change fast, so hat it makes sense to
1583 split them off to create subdirectories to balance load.
1584 - You can now set the `org-id-method' to `uuidgen' on systems
1587 *** =C-c C-a= no longer calls `show-all'
1589 The reason for this is that =C-c C-a= is now used for the
1590 attachment system. On the rare occasions that this command
1591 is needed, use =M-x show-all=, or =C-u C-u C-u TAB=.
1593 *** New attachment system
1595 You can now attach files to each node in the outline tree.
1596 This works by creating special directories based on the ID of
1597 an entry, and storing files in these directories. Org can
1598 keep track of changes to the attachments by automatically
1599 committing changes to git. See the manual for more
1602 Thanks to John Wiegley who contributed this fantastic new
1603 concept and wrote org-attach.el to implement it.
1605 *** New remember template escapes
1607 : %^{prop}p to insert a property
1608 : %k the heading of the item currently being clocked
1609 : %K a link to the heading of the item currently being clocked
1611 Also, when you exit remember with =C-2 C-c C-c=, the item
1612 will be filed as a child of the item currently being
1613 clocked. So the idea is, if you are working on something and
1614 think of a new task related to this or a new note to be
1615 added, you can use this to quickly add information to that
1618 Thanks to James TD Smith for a patch to this effect.
1620 *** Clicking with mouse-2 on clock info in mode-line visits the clock.
1622 Thanks to James TD Smith for a patch to this effect.
1624 *** New file in contrib: lisp/org-checklist.el
1626 This module deals with repeated tasks that have checkbox
1629 Thanks to James TD Smith for this contribution.
1631 *** New in-buffer setting #+STYLE
1633 It can be used to locally set the variable
1634 `org-export-html-style-extra'. Several such lines are
1635 allowed-, they will all be concatenated. For an example on
1636 how to use it, see the [[http://orgmode.org/worg/org-tutorials/org-publish-html-tutorial.php][publishing tutorial]].
1642 - Filtering existing agenda views with respect to a tag
1643 - Editing fixed-width regions with picture or artist mode
1644 - /org-plot.el/ is now part of Org
1645 - Tags can be used to select the export part of a document
1646 - Prefix interpretation when storing remember notes
1647 - Yanking inserts folded subtrees
1648 - Column view capture tables can have formulas, plotting info
1649 - In column view, date stamps can be changed with S-cursor keys
1650 - The note buffer for clocking out now mentions the task
1651 - Sorting entries alphabetically ignores TODO keyword and priority
1652 - Agenda views can sort entries by TODO state
1653 - New face =org-scheduled= for entries scheduled in the future.
1654 - Remember templates for gnus links can use the :to escape.
1655 - The file specification in a remember template may be a function
1656 - Categories in iCalendar export include local tags
1657 - It is possible to define filters for column view
1658 - Disabling integer increment during table Field copy
1659 - Capturing column view is on `C-c C-x i'
1660 - And tons of bugs fixed.
1663 ** Incompatible changes
1665 *** Prefix interpretation when storing remember notes has changed
1667 The prefix argument to the `C-c C-c' command that finishes a
1668 remember process is now interpreted differently:
1670 : C-c C-c Store the note to predefined file and headline
1671 : C-u C-c C-c Like C-c C-c, but immediately visit the note
1672 : in its new location.
1673 : C-1 C-c C-c Select the storage location interactively
1674 : C-0 C-c C-c Re-use the last used location
1676 This was requested by John Wiegley.
1678 *** Capturing column view is now on `C-c C-x i'
1680 The reason for this change was that `C-c C-x r' is also used
1681 as a tty key replacement.
1683 *** Categories in iCalendar export now include local tags
1685 The locally defined tags are now listed as categories when
1686 exporting to iCalendar format. Org's traditional file/tree
1687 category is now the last category in this list. Configure
1688 the variable =org-icalendar-categories= to modify or revert
1691 This was a request by Charles Philip Chan.
1695 *** Secondary filtering of agenda views.
1697 You can now easily and interactively filter an existing
1698 agenda view with respect to a tag. This command is executed
1699 with the =/= key in the agenda. You will be prompted for a
1700 tag selection key, and all entries that do not contain or
1701 inherit the corresponding tag will be hidden. With a prefix
1702 argument, the opposite filter is applied: entries that
1703 do have the tag will be hidden.
1705 This operation only /hides/ lines in the agenda buffer, it
1706 does not remove them. Changing the secondary filtering does
1707 not require a new search and is very fast.
1709 If you press TAB at the tag selection prompt, you will be
1710 switched to a completion interface to select a tag. This is
1711 useful when you want to select a tag that does not have a
1712 direct access character.
1714 A double =/ /= will restore the original agenda view by
1715 unhiding any hidden lines.
1717 This functionality was John Wiegley's idea. It is a simpler
1718 implementation of some of the query-editing features proposed
1719 and implemented some time ago by Christopher League (see the
1720 file contrib/lisp/org-interactive-query.el).
1722 *** Editing fixed-width regions with picture or artist mode
1724 The command @<code>C-c '@</code> (that is =C-c= followed by a
1725 single quote) can now also be used to switch to a special
1726 editing mode for fixed-width sections. The default mode is
1727 =artist-mode= which allows you to create ASCII drawings.
1729 It works like this: Enter the editing mode with
1730 @<code>C-c '@</code>. An indirect buffer will be created and
1731 narrowed to the fixed-width region. Edit the drawing, and
1732 press @<code>C-c '@</code> again to exit.
1734 Lines in a fixed-width region should be preceded by a colon
1735 followed by at least one space. These will be removed during
1736 editing, and then added back when you exit the editing mode.
1738 Using the command in an empty line will create a new
1741 This new feature arose from a discussion involving Scott
1742 Otterson, Sebastian Rose and Will Henney.
1744 *** /org-plot.el/ is now part of Org.
1746 You can run it by simple calling org-plot/gnuplot.
1747 Documentation is not yet included with Org, please refer to
1748 http://github.com/eschulte/org-plot/tree/master until we have
1749 moved the docs into Org or Worg.
1751 Thanks to Eric Schulte for this great contribution.
1753 *** Tags can be used to select the export part of a document
1755 You may now use tags to select parts of a document for
1756 inclusion into the export, and to exclude other parts. This
1757 behavior is governed by two new variables:
1758 =org-export-select-tags= and =org-export-exclude-tags=.
1759 These default to =("export")= and =("noexport")=, but can be
1760 changed, even to include a list of several tags.
1762 Org first checks if any of the /select/ tags is present in
1763 the buffer. If yes, all trees that do not carry one of these
1764 tags will be excluded. If a selected tree is a subtree, the
1765 heading hierarchy above it will also be selected for export,
1766 but not the text below those headings. If none of the select
1767 tags is found anywhere in the buffer, the whole buffer will
1768 be selected for export. Finally, all subtrees that are
1769 marked by any of the /exclude/ tags will be removed from the
1772 You may set these tags with in-buffer options
1773 =EXPORT_SELECT_TAGS= and =EXPORT_EXCLUDE_TAGS=.
1775 I love this feature. Thanks to Richard G Riley for coming
1778 *** Prefix interpretation when storing remember notes
1780 The prefix argument to the `C-c C-c' command that finishes a
1781 remember process is now interpreted differently:
1783 : C-c C-c Store the note to predefined file and headline
1784 : C-u C-c C-c Like C-c C-c, but immediately visit the note
1785 : in its new location.
1786 : C-1 C-c C-c Select the storage location interactively
1787 : C-0 C-c C-c Re-use the last used location
1789 This was requested by John Wiegley.
1791 *** Yanking inserts folded subtrees
1793 If the kill is a subtree or a sequence of subtrees, yanking
1794 them with =C-y= will leave all the subtrees in a folded
1795 state. This basically means, that kill and yank are now
1796 much more useful in moving stuff around in your outline. If
1797 you do not like this, customize the variable
1798 =org-yank-folded-subtrees=.
1800 Right now, I am only binding =C-y= to this new function,
1801 should I modify all bindings of yank? Do we need to amend
1804 This feature was requested by John Wiegley.
1806 *** Column view capture tables can have formulas, plotting info
1808 If you attach formulas and plotting instructions to a table
1809 capturing column view, these extra lines will now survive an
1810 update of the column view capture, and any formulas will be
1811 re-applied to the captured table. This works by keeping any
1812 continuous block of comments before and after the actual
1815 *** In column view, date stamps can be changed with S-cursor keys
1817 If a property value is a time stamp, S-left and S-right can
1818 now be used to shift this date around while in column view.
1820 This was a request by Chris Randle.
1822 *** The note buffer for clocking out now mentions the task
1824 This was a request by Peter Frings.
1826 *** Sorting entries alphabetically ignores TODO keyword and priority
1828 Numerical and alphanumerical sorting now skips any TODO
1829 keyword or priority cookie when constructing the comparison
1830 string. This was a request by Wanrong Lin.
1832 *** Agenda views can sort entries by TODO state
1834 You can now define a sorting strategy for agenda entries that
1835 does look at the TODO state of the entries. Sorting by TODO
1836 entry does first separate the non-done from the done states.
1837 Within each class, the entries are sorted not alphabetically,
1838 but in definition order. So if you have a sequence of TODO
1839 entries defined, the entries will be sorted according to the
1840 position of the keyword in this sequence.
1842 This follows an idea and sample implementation by Christian
1845 *** New face =org-scheduled= for entries scheduled in the future.
1847 This was a request by Richard G Riley.
1849 *** Remember templates for gnus links can now use the :to escape.
1851 Thanks to Tommy Lindgren for a patch to this effect.
1852 *** The file specification in a remember template may now be a function
1854 Thanks to Gregory Sullivan for a patch to this effect.
1856 *** Categories in iCalendar export now include local tags
1858 The locally defined tags are now listed as categories when
1859 exporting to iCalendar format. Org's traditional file/tree
1860 category is now the last category in this list. Configure
1861 the variable =org-icalendar-categories= to modify or revert
1864 This was a request by Charles Philip Chan.
1866 *** It is now possible to define filters for column view
1868 The filter can modify the value that will be displayed in a
1869 column, for example it can cut out a part of a time stamp.
1870 For more information, look at the variable
1871 =org-columns-modify-value-for-display-function=.
1873 *** Disabling integer increment during table field copy
1875 Prefix arg 0 to S-RET does the trick.
1877 This was a request by Chris Randle.
1882 For older Changes, see [[file:Changes_old.org]]