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.18 (in preparation)
18 ** Incompatible changes
20 *** Short examples must have a space after the colon
22 Short literal examples can be created by preceeding lines
23 with a colon. Such lines must now have a space after the
24 colon. I believe this is already general practice, but now
25 it must be like this. The only exception are lines what are
26 empty except for the colon.
30 *** The relative timer can be paused
32 The new command `C-c C-x ,' will pause the relative timer.
33 When the relative timer is running, its value will be shown
34 in the mode line. To get rid of this display, you need to
35 really stop the timer with `C-u C-c C-x ,'.
37 Thanks to Alan Davis for driving this change.
39 *** Include files can now also process switches
41 The example and src switches like =-n= can now also be added
42 to inlcude file statements:
44 : #+INCLUDE "~/.emacs" src emacs-lisp -n -r
46 *** Links by ID now continue to work in HTML exported files
48 If you make links by ID, these links will now still work in
49 HTML exported files, provided that you keep the relative path
50 from link to target file the same.
57 - Line numbers and references in literal examples
58 - New hooks for export preprocessing
59 - Capture column view into a different file
65 Org-mode now directly supports the creation of footnotes. In
66 contrast to the /footnote.el/ package, Org-mode's footnotes are
67 designed for work on a larger document, not only for one-off
68 documents like emails. The basic syntax is similar to the one
69 used by /footnote.el/, i.e. a footnote is defined in a paragraph
70 that is started by a footnote marker in square brackets in column
71 0, no indentation allowed. The footnote reference is simply the
72 marker in square brackets inside text. For example:
75 The Org homepage[fn:1] now looks a lot better than it used to.
77 [fn:1] The link is: http://orgmode.org
80 Org-mode extends the number-based syntax to /named/ footnotes and
81 optional inline definition. Using plain numbers as markers is
82 supported for backward compatibility, but not encouraged because
83 of possible conflicts with LaTeX syntax. Here are the valid
86 - [1] :: A plain numeric footnote marker.
88 - [fn:name] :: A named footnote reference, where `name' is a
89 unique label word or, for simplicity of automatic creation,
92 - [fn:: This is the inline definition of this footnote] :: A
93 LaTeX-like anonymous footnote where the definition is given
94 directly at the reference point.
96 - [fn:name: a definition] :: An inline definition of a footnote,
97 which also specifies a name for the note. Since Org allows
98 multiple references to the same note, you can then use use
99 `[fn:name]' to create additional references.
101 Footnote labels can be created automatically, or you create names
102 yourself. This is handled by the variable
103 =org-footnote-auto-label= and its corresponding =#+STARTUP=
104 keywords, see the docstring of that variable for details.
106 The following command handles footnotes:
108 - C-c C-x f :: The footnote action command. When the cursor is
109 on a footnote reference, jump to the definition. When it is
110 at a definition, jump to the (first) reference. Otherwise,
111 create a new footnote. Depending on the variable
112 `org-footnote-define-inline' (with associated =#+STARTUP=
113 options =fninline= and =nofninline=), the definitions will
114 be placed right into the text as part of the reference, or
115 separately into the location determined by the variable
116 =org-footnote-section=.
117 When this command is called with a prefix argument, a menu
118 of additional options is offered:
119 - s :: Sort the footnote definitions by reference sequence.
120 During editing, Org makes no effort to sort footnote
121 definitions into a particular sequence. If you want
122 them sorted, use this command, which will also move
123 entries according to =org-footnote-section=.
124 - n :: Normalize the footnotes by collecting all
125 definitions (including inline definitions) into a
126 special section, and then numbering them in
127 sequence. The references will then also be
128 numbers. This is meant to be the final step before
129 finishing a document (e.g. sending off an email).
130 The exporters do this automatically, and so could
131 something like `message-send-hook'.
132 - d :: Delete the footnote at point, and all references to it.
134 - C-c C-c :: If the cursor is on a footnote reference, jump to
135 the definition. If it is a the definition, jump back to the
136 reference. When called with a prefix argument at either
137 location, offer the same menu as `C-u C-c C-x f'.
139 - C-c C-o or mouse-1/2 :: Footnote labels are also links to the
140 corresponding definition/reference, and you can use the
141 usual commands to follow these links.
143 Org-mode's footnote support is designed so that it should also
144 work in buffers that are not in Org-mode, for example in email
145 messages. Just bind =org-footnote-action= to a global key like
148 The main trigger for this development came from a hook function
149 written by Paul Rivier, to implement named footnotes and to
150 convert them to numbered ones before export. Thanks, Paul!
152 Thanks also to Scot Becker for a thoughtful post bringing this
153 subject back onto the discussion table, and to Matt Lundin for
154 the idea of named footnotes and his prompt testing of the new
157 *** Line numbers and references in literal examples
159 Literal examples introduced with =#+BEGIN_EXAMPLE= or =#+BEGIN_SRC=
160 do now allow optional line numbering in the example.
161 Furthermore, links to specific code lines are supported, greatly
162 increasing Org-mode's utility for writing tutorials and other
165 Code references use special labels embedded directly into the
166 source code. Such labels look like "(ref:name)" and must be
167 unique within a document. Org-mode links with "(name)" in the
168 link part will be correctly interpreted, both while working with
169 an Org file (internal links), and while exporting to the
170 different backends. Line numbering and code references are
171 supported for all three major backends, HTML, LaTeX, and ASCII.
172 In the HTML backend, hovering the mouse over a link to a source
173 line will remote-highlight the referenced code line.
175 The options for the BEGIN lines are:
177 - -n :: Number the lines in the example
178 - +n :: Like -n, but continue numbering from where the previous
180 - -r :: Remove the coderef cookies from the example, and replace
181 links to this reference with line numbers. This option
182 takes only effect if either -n or +n are given as well.
183 If -r is not given, coderefs simply use the label name.
184 - -l "fmt" :: Define a local format for coderef labels, see the
185 variable =org-coderef-label-format= for details. Use this
186 of the default syntax causes conflicts with the code in the
187 code snippet you are using.
192 #+begin_src emacs-lisp -n -r
193 (defmacro org-unmodified (&rest body) (ref:def)
194 "Execute body without changing `buffer-modified-p'."
195 `(set-buffer-modified-p (ref:back)
196 (prog1 (buffer-modified-p) ,@body)))
198 [[(def)][Line (def)]] contains the macro name. Later at line [[(back)]],
202 When exported, this is translated to:
203 #+begin_src emacs-lisp -n -r
204 (defmacro org-unmodified (&rest body) (ref:def)
205 "Execute body without changing `buffer-modified-p'."
206 `(set-buffer-modified-p (ref:back)
207 (prog1 (buffer-modified-p) ,@body)))
209 [[(def)][Line (def)]] contains the macro name. Later at line [[(back)]],
212 Thanks to Ilya Shlyakhter for proposing this feature set. Thanks
213 to Sebastian Rose for the key Javascript element that made the
214 remote highlighting possible.
216 *** New hooks for export preprocessing
217 The export preprocessor now runs more hooks, to allow
218 better-timed tweaking by user functions:
220 - =org-export-preprocess-hook= ::
221 Pretty much the first thing in the preprocessor. But org-mode
222 is already active in the preprocessing buffer.
224 - =org-export-preprocess-after-include-files-hook= ::
225 This is run after the contents of included files have been inserted.
227 - =org-export-preprocess-after-tree-selection-hook= ::
228 This is run after selection of trees to be exported has
229 happened. This selection includes tags-based selection, as
230 well as removal of commented and archived trees.
232 - =org-export-preprocess-before-backend-specifics-hook= ::
233 Hook run before backend-specific functions are called during preprocessing.
235 - =org-export-preprocess-final-hook= ::
236 Hook for preprocessing an export buffer. This is run as the
237 last thing in the preprocessing buffer, just before returning
238 the buffer string to the backend.
240 *** Capture column view into a different file
242 The :id parameter for the dynamic block capturing column view
243 can now truly be an ID that will also be found in a
244 different file. Also, it can be like =file:path/to/file=, to
245 capture the global column view from a different file.
247 Thanks to Francois Lagarde for his report that IDs outside
248 the current file would not work.
251 Cleanup of many small bugs, and one new feature.
255 *** References to last table row with special names
257 Fields in the last row of a table can now be referenced with
258 $LR1, $LR2, etc. These references can appear both on the
259 left hand side and right hand side of a formula.
263 This version reverses the introduction of @0 as a reference to
264 the last rwo in a table, because of a conflict with the use of
265 @0 for the current row.
270 - All known LaTeX export issues fixed
271 - Captions and attributes for figures and tables.
272 - Better implementation for entry IDs
273 - Spreadsheet references to the last table line.
274 - Old syntax for link attributes abandoned
276 ** Incompatible changes
277 *** Old syntax for link attributes abandoned
279 There used to be a syntax for setting link attributes for
280 HTML export by enclosing the attributes into double braces
281 and adding them to the link itself, like
284 [[./img/a.jpg{{alt="an image"}}] ]
287 This syntax is not longer supported, use instead
290 ,#+ATTR_HTML: alt="an image"
296 *** All known LaTeX export issues fixed
298 All the remaining issues with the LaTeX exporter have hopefully
299 been addressed in this release. In particular, this covers
300 quoting of special characters in tables and problems with
301 exporting files where the headline is in the first line, or with
304 *** Captions and attributes for figures and tables.
306 Tables, and Hyperlinks that represent inlined images, can now be
307 equipped with additional information that will be used during
308 export. The information will be taken from the following special
309 lines in the buffer and apply to the first following table or
312 - #+CAPTION: :: The caption of the image or table. This string
313 should be processed according to the export backend, but
314 this is not yet done.
316 - #+LABEL: :: A label to identify the figure/table for cross
317 references. For HTML export, this string will become the
318 ID for the ~<div class="figure">~ element that encapsulates
319 the image tag and the caption. For LaTeX export, this
320 string will be used as the argument of a ~\label{...}~
321 macro. These labels will be available for internal links
322 like ~[[label][Table] ]~.
324 - #+ATTR_HTML: :: Attributes for HTML export of image, to be
325 added as attributes into the ~<img...>~ tag. This string
326 will not be processed, so it should have immediately the
329 - #+ATTR_LaTeX: :: Attributes for LaTeX export of images and
331 For /images/, this string is directly inserted into
332 the optional argument of the ~\includegraphics[...]{file}~
333 command, to specify scaling, clipping and other options.
334 This string will not be processed, so it should have
335 immediately the right format, like =width=5cm,angle=90=.\\
336 For /tables/, this can currently contain the keyword
337 =longtable=, to request typesetting of the table using the
338 longtable package, which automatically distributes the table
339 over several pages if needed. Also, the attributes line may
340 contain an alignment string for the tabular environment, like
341 =longtable,align=l|lrl=
343 For LaTeX export, if either a caption or a label is given, the element
344 will be exported as a float, i.e. wrapped into a figure or table
347 *** Better implementation for entry IDs
349 Unique identifiers for entries can now be used more efficiently.
350 Internally, a hash array has replaced the alist used so far to
351 keep track of the files in which an ID is defined. This makes it
352 quite fast to find an entry by ID.
354 There is a new link type which looks like this:
357 id:GLOBALLY-UNIQUE-IDENTIFIER
360 This link points to a specific entry. When you move the entry to
361 a different file, for example if you move it to an archive
362 file, the link will continue to work.
364 The file /org-id.el/ contains an API that can be used to write
365 code using these identifiers, including creating IDs and finding
366 them wherever they are.
368 Org has its own method to create unique identifiers, but if the system
369 has /uuidgen/ command installed (Mac's and Linux systems generally
370 do), it will be used by default (a change compared to the earlier
371 implmentation, where you explicitdly had to opt for uuidgen). You can
372 also select the method by hand, using the variable =org-id-method=.
374 If the ID system ever gets confused about where a certain ID is, it
375 initiates a global scan of all agenda files with associated archives,
376 all files previously known containing any IDs, and all currently
377 visited Org-mode files to rebuild the hash. You can also initiate
378 this by hand: =M-x org-id-update-id-locations=. Running this command
379 will also dump into the =*Messages*= buffer information about any
380 duplicate IDs. These should not exist, and Org will never /make/ the
381 same ID twice, but if you /copy/ an entry with its properties,
382 duplicate IDs will inevitably be produced. Unfortunately, this is
383 unavoidable in a plain text system that allows you to edit the text in
384 arbitrary ways, and a portion of care on your side is needed to keep
387 The hash is stored in the file =~/.emacs.d/.org-id-locations=.
388 This is also a change from previous versions where the file was
389 =~/.org=id-locations=. Therefore, you can remove this old file
390 if you have it. I am not sure what will happen if the =.emacs.d=
391 directory does not exists in your setup, but in modern Emacsen, I
392 believe it should exist. If you do not want to use IDs across
393 files, you can avoid the overhead with tracking IDs by
394 customizing the variable =org-id-track-globally=. IDs can then
395 still be used for links inside a single file.
397 IDs will also be used when you create a new link to an Org-mode
398 buffer. If you use =org-store-link= (normally at =C-c l=) inside
399 en entry in an Org-mode buffer, and ID property will be created
400 if it does not exist, and the stored link will be an =id:= link.
401 If you prefer the much less secure linking to headline text, you
402 can configure the variable =org-link-to-org-use-id=. The default
403 setting for this variable is =create-if-interactive=, meaning
404 that an ID will be created when you store a link interactively,
405 but not if you happen to be in an Org-mode file while you create
406 a remember note (which usually has a link to the place where you
407 were when starting remember).
409 *** Spreadsheet references to the last table line.
411 You may now use =@0= to reference the last dataline in a table
412 in a stable way. This is useful in particular for automatically
413 generated tables like the ones using /org-collector.el/ by Eric
419 - New relative timer to support timed notes
420 - Special faces can be set for individual tags
421 - The agenda shows now all tags, including inherited ones.
422 - Exclude some tags from inheritance.
423 - More special values for time comparisons in property searches
424 - Control for exporting meta data
425 - Cut and Paste with hot links from w3m to Org
426 - LOCATION can be inherited for iCalendar export
427 - Relative row references crossing hlines now throw an error
429 ** Incompatible Changes
431 *** Relative row references crossing hlines now throw an error
433 Relative row references in tables look like this: "@-4" which
434 means the forth row above this one. These row references are
435 not allowed to cross horizontal separator lines (hlines). So
436 far, when a row reference violates this policy, Org would
437 silently choose the field just next to the hline.
439 Tassilo Horn pointed out that this kind of hidden magic is
440 actually confusing and may cause incorrect formulas, and I do
441 agree. Therefore, trying to cross a hline with a relative
442 reference will now throw an error.
444 If you need the old behavior, customize the variable
445 `org-table-error-on-row-ref-crossing-hline'.
449 *** New relative timer to support timed notes
451 Org now supports taking timed notes, useful for example while
452 watching a video, or during a meeting which is also recorded.
455 Insert a relative time into the buffer. The first time
456 you use this, the timer will be started. When called
457 with a prefix argument, the timer is reset to 0.
460 Insert a description list item with the current relative
461 time. With a prefix argument, first reset the timer to 0.
464 Once the time list has been initiated, you can also use the
465 normal item-creating command to insert the next timer item.
468 Reset the timer without inserting anything into the buffer.
469 By default, the timer is reset to 0. When called with a
470 =C-u= prefix, reset the timer to specific starting
471 offset. The user is prompted for the offset, with a
472 default taken from a timer string at point, if any, So this
473 can be used to restart taking notes after a break in the
474 process. When called with a double prefix argument
475 =C-c C-u=, change all timer strings in the active
476 region by a certain amount. This can be used to fix timer
477 strings if the timer was not started at exactly the right
480 Thanks to Alan Dove, Adam Spiers, and Alan Davis for
481 contributions to this idea.
483 *** Special faces can be set for individual tags
485 You may now use the variable =org-tag-faces= to define the
486 face used for specific tags, much in the same way as you can
487 do for TODO keywords.
489 Thanks to Samuel Wales for this proposal.
491 *** The agenda shows now all tags, including inherited ones.
493 This request has come up often, most recently it was
494 formulated by Tassilo Horn.
496 If you prefer the old behavior of only showing the local
497 tags, customize the variable =org-agenda-show-inherited-tags=.
499 *** Exclude some tags from inheritance.
501 So far, the only way to select tags for inheritance was to
502 allow it for all tags, or to do a positive selection using
503 one of the more complex settings for
504 `org-use-tag-inheritance'. It may actually be better to
505 allow inheritance for all but a few tags, which was difficult
506 to achieve with this methodology.
508 A new option, `org-tags-exclude-from-inheritance', allows to
509 specify an exclusion list for inherited tags.
511 *** More special values for time comparisons in property searches
513 In addition to =<now>=, =<today>=, =<yesterday>=, and
514 =<tomorrow>=, there are more special values accepted now in
515 time comparisons in property searches: You may use strings
516 like =<+3d>= or =<-2w>=, with units d, w, m, and y for day,
517 week, month, and year, respectively
519 Thanks to Linday Todd for this proposal.
521 *** Control for exporting meta data
523 All the metadata in a headline, i.e. the TODO keyword, the
524 priority cookie, and the tags, can now be excluded from
525 export with appropriate options:
527 | Variable | Publishing property | OPTIONS switch |
528 |-------------------------------+---------------------+----------------|
529 | org-export-with-todo-keywords | :todo-keywords | todo: |
530 | org-export-with-tags | :tags | tags: |
531 | org-export-with-priority | :priority | pri: |
533 *** Cut and Paste with hot links from w3m to Org
535 You can now use the key =C-c C-x M-w= in a w3m buffer with
536 HTML content to copy either the region or the entire file in
537 a special way. When you yank this text back into an Org-mode
538 buffer, all links from the w3m buffer will continue to work
541 For this to work you need to load the new file /org-w3m.el./
542 Please check your org-modules variable to make sure that this
545 Thanks for Richard Riley for the idea and to Andy Stewart for
548 *** LOCATION can be inherited for iCalendar export
550 The LOCATION property can now be inherited during iCalendar
551 export if you configure =org-use-property-inheritance= like
554 #+begin_src emacs-lisp
555 (setq org-use-property-inheritance '("LOCATION"))
562 - Keybindings in Remember buffers can be configured
563 - Support for ido completion
564 - New face for date lines in agenda column view
565 - Invisible targets become now anchors in headlines.
566 - New contributed file /org-exp-blocks.el/
567 - New contributed file /org-eval-light.el/
569 - BBDB links may use regular expressions.
570 - Link abbreviations can use %h to insert a url-encoded target value
571 - Improved XHTML compliance
575 *** Keybindings in Remember buffers can be configured
577 The remember buffers created with Org's extensions are in
578 Org-mode, which is nice to prepare snippets that will
579 actually be stored in Org-mode files. However, this makes it
580 hard to configure key bindings without modifying the Org-mode
581 keymap. There is now a minor mode active in these buffers,
582 `org-remember-mode', and its keymap org-remember-mode-map can
583 be used for key bindings. By default, this map only contains
584 the bindings for =C-c C-c= to store the note, and =C-c C-k=
585 to abort it. Use `org-remember-mode-hook' to define your own
588 #+begin_src emacs-lisp
590 'org-remember-mode-hook
592 (define-key org-remember-mode-map
593 "\C-x\C-s" 'org-remember-finalize)))
596 If you wish, you can also use this to free the =C-c C-c=
597 binding (by binding this key to nil in the minor mode map),
598 so that you can use =C-c C-c= again to set tags.
600 This modification is based on a request by Tim O'Callaghan.
602 *** Support for ido completion
604 You can now get the completion interface from /ido.el/ for
605 many of Org's internal completion commands by turning on the
606 variable =org-completion-use-ido=. =ido-mode= must also be
607 active before you can use this.
609 This change is based upon a request by Samuel Wales.
611 *** New face for date lines in agenda column view
613 When column view is active in the agenda, and when you have
614 summarizing properties, the date lines become normal column
615 lines and the separation between different days becomes
616 harder to see. If this bothers you, you can now customize
617 the face =org-agenda-column-dateline=.
619 This is based on a request by George Pearson.
621 *** Invisible targets become now anchors in headlines.
623 These anchors can be used to jump to a directly with an HTML
624 link, just like the =sec-xxx= IDs. For example, the
625 following will make a http link
626 =//domain/path-to-my-file.html#dummy= work:
633 This is based on a request by Matt Lundin.
635 *** New contributed file /org-exp-blocks.el/
637 This new file implements special export behavior of
638 user-defined blocks. The currently supported blocks are
640 - comment :: Comment blocks with author-specific markup
641 - ditaa :: conversion of ASCII art into pretty png files
642 using Stathis Sideris' /ditaa.jar/ program
643 - dot :: creation of graphs in the /dot/ language
644 - R :: Sweave type exporting using the R program
646 For more details and examples, see the file commentary in
649 Kudos to Eric Schulte for this new functionality, after
650 /org-plot.el/ already his second major contribution. Thanks
651 to Stathis for this excellent program, and for allowing us to
652 bundle it with Org-mode.
654 *** New contributed file /org-eval-light.el/
656 This module gives control over execution Emacs Lisp code
657 blocks included in a file.
659 Thanks to Eric Schulte also for this file.
663 You can now configure Org to understand many links created
664 with the Emacs Planner package, so you can cut text from
665 planner pages and paste them into Org-mode files without
666 having to re-write the links. Among other things, this means
667 that the command =org-open-at-point-global= which follows
668 links not only in Org-mode, but in arbitrary files like
669 source code files etc, will work also with links created by
670 planner. The following customization is needed to make all of
673 #+begin_src emacs-lisp
674 (setq org-link-translation-function
675 'org-translate-link-from-planner)
678 I guess an inverse translator could be written and integrated
681 *** BBDB links may use regular expressions.
683 This did work all along, but only now I have documented it.
685 *** =yank-pop= works again after yanking an outline tree
687 Samuel Wales had noticed that =org-yank= did mess up this
688 functionality. Now you can use =yank-pop= again, the only
689 restriction is that the so-yanked text will not be
690 pro/demoted or folded.
692 *** Link abbreviations can use %h to insert a url-encoded target value
694 Thanks to Steve Purcell for a patch to this effect.
696 *** Improved XHTML compliance
698 Thanks to Sebastian Rose for pushing this.
700 *** Many bug fixes again.
705 - A region of entries can now be refiled with a single command
706 - Fine-tuning the behavior of `org-yank'
707 - Formulas for clocktables
708 - Better implementation of footnotes for HTML export
709 - More languages for HTML export.
713 *** A region of entries can now be refiled with a single command
715 With =transient-make-mode= active (=zmacs-regions= under
716 XEmacs), you can now select a region of entries and refile
717 them all with a single =C-c C-w= command.
719 Thanks to Samuel Wales for this useful proposal.
721 *** Fine-tuning the behavior of =org-yank=
723 The behavior of Org's yanking command has been further
724 fine-tuned in order to avoid some of the small annoyances
727 - Calling =org-yank= with a prefix arg will stop any special
728 treatment and directly pass through to the normal =yank=
729 command. Therefore, you can now force a normal yank with
732 - Subtrees will only be folded after a yank if doing so will
733 now swallow any non-white characters after the yanked text.
734 This is, I think a really important change to make the
735 command work more sanely.
737 *** Formulas for clocktables
739 You can now add formulas to a clock table, either by hand, or
740 with a =:formula= parameter. These formulas can be used to
741 create additional columns with further analysis of the
744 Thanks to Jurgen Defurne for triggering this addition.
746 *** Better implementation of footnotes for HTML export
748 The footnote export in 6.11 really was not good enough. Now
749 it works fine. If you have customized
750 =footnote-section-tag=, make sure that your customization is
751 matched by =footnote-section-tag-regexp=.
753 Thanks to Sebastian Rose for pushing this change.
755 *** More languages for HTML export.
757 More languages are supported during HTML export. This is
758 only relevant for the few special words Org inserts, like
759 "Table of Contents", or "Footnotes". Also the encoding
760 issues with this feature seem to be solved now.
762 Thanks to Sebastian Rose for pushing me to fix the encoding
769 - Yanking subtree with =C-y= now adjusts the tree level
770 - State changes can now be shown in the log mode in the agenda
771 - Footnote in HTML export are now collected at the end of the document
772 - HTML export now validates again as XHTML
773 - The clock can now be resumed after exiting and re-starting Emacs
774 - Clock-related data can be saved and resumed across Emacs sessions
775 - Following file links can now use C-u C-u to force use of an external app
776 - Inserting absolute files names now abbreviates links with "~"
777 - Links to attachment files
778 - Completed repeated tasks listed briefly in agenda
779 - Remove buffers created during publishing are removed
783 *** Yanking subtree with =C-y= now adjusts the tree level
784 When yanking a cut/copied subtree or a series of trees, the
785 normal yank key =C-y= now adjusts the level of the tree to
786 make it fit into the current outline position, without losing
787 its identity, and without swallowing other subtrees.
789 This uses the command =org-past-subtree=. An additional
790 change in that command has been implemented: Normally, this
791 command picks the right outline level from the surrounding
792 *visible* headlines, and uses the smaller one. So if the
793 cursor is between a level 4 and a level 3 headline, the tree
794 will be pasted as level 3. If the cursor is actually *at*
795 the beginning of a headline, the level of that headline will
796 be used. For example, lets say you have a tree like this:
802 ,(2)* Level one again
805 with (1) and (2) indicating possible cursor positions for the
806 insertion. When at (1), the tree will be pasted as level 2.
807 When at (2), it will be pasted as level 1.
809 If you do not want =C-y= to behave like this, configure the
810 variable =org-yank-adjusted-subtrees=.
812 Thanks to Samuel Wales for this idea and a partial implementation.
814 *** State changes can now be shown in the log mode in the agenda
816 If you configure the variable =org-agenda-log-mode-items=,
817 you can now request that all logged state changes be included
818 in the agenda when log mode is active. If you find this too
819 much for normal applications, you can also temporarily
820 request the inclusion of state changes by pressing =C-u l= in
823 This was a request by Hsiu-Khuern Tang.
825 You can also press `C-u C-u l' to get *only* log items in the
826 agenda, withour any timestamps/deadlines etc.
828 *** Footnote in HTML export are now collected at the end of the document
829 Previously, footnotes would be left in the document where
830 they are defined, now they are all collected and put into a
831 special =<div>= at the end of the document.
833 Thanks to Sebastian Rose for this request.
835 *** HTML export now validates again as XHTML.
837 Thanks to Sebastian Rose for pushing this cleanup.
839 *** The clock can now be resumed after exiting and re-starting Emacs
841 If the option =org-clock-in-resume= is t, and the first clock
842 line in an entry is unclosed, clocking into that task resumes
843 the clock from that time.
845 Thanks to James TD Smith for a patch to this effect.
847 *** Clock-related data can be saved and resumed across Emacs sessions
849 The data saved include the contents of =org-clock-history=,
850 and the running clock, if there is one.
852 To use this, you will need to add to your .emacs
854 #+begin_src emacs-lisp
855 (setq org-clock-persist t)
856 (setq org-clock-in-resume t)
857 (org-clock-persistence-insinuate)
860 Thanks to James TD Smith for a patch to this effect.
862 *** Following file links can now use C-u C-u to force use of an external app.
864 So far you could only bypass your setup in `org-file-apps'
865 and force opening a file link in Emacs by using a =C-u= prefix arg
866 with =C-c C-o=. Now you can call =C-u C-u C-c C-o= to force
867 an external application. Which external application depends
868 on your system. On Mac OS X and Windows, =open= is used. On
869 a GNU/Linux system, the mailcap settings are used.
871 This was a proposal by Samuel Wales.
873 *** Inserting absolute files names now abbreviates links with "~".
875 Inserting file links with =C-u C-c C-l= was buggy if the
876 setting of `org-link-file-path-type' was `adaptive' (the
877 default). Absolute file paths were not abbreviated relative
878 to the users home directory. This bug has been fixed.
880 Thanks to Matt Lundin for the report.
882 *** Links to attachment files
884 Even though one of the purposes of entry attachments was to
885 reduce the number of links in an entry, one might still want
886 to have the occasional link to one of those files. You can
887 now use link abbreviations to set up a special link type that
888 points to attachments in the current entry. Note that such
889 links will only work from within the same entry that has the
890 attachment, because the directory path is entry specific.
891 Here is the setup you need:
893 #+begin_src emacs-lisp
894 (setq org-link-abbrev-alist '(("att" . org-attach-expand-link)))
897 After this, a link like this will work
900 [[att:some-attached-file.txt]]
902 This was a proposal by Lindsay Todd.
904 *** Completed repeated tasks listed briefly in agenda
906 When a repeating task, listed in the daily/weekly agenda under
907 today's date, is completed from the agenda, it is listed as
908 DONE in the agenda until the next update happens. After the
909 next update, the task will have disappeared, of course,
910 because the new date is no longer today.
912 *** Remove buffers created during publishing are removed
914 Buffers that are created during publishing are now deleted
915 when the publishing is over. At least I hope it works like this.
921 - Secondary agenda filtering is becoming a killer feature
922 - Setting tags has now its own binding, =C-c C-q=
923 - Todo state changes can trigger tag changes
924 - C-RET will now always insert a new headline, never an item.
925 - Customize org-mouse.el feature set to free up mouse events
926 - New commands for export all the way to PDF (through LaTeX)
927 - Some bug fixed for LaTeX export, more bugs remain.
931 *** Enhancements to secondary agenda filtering
933 This is, I believe, becoming a killer feature. It allows you
934 to define fewer and more general custom agenda commands, and
935 then to do the final narrowing to specific tasks you are
936 looking for very quickly, much faster than calling a new
939 If you have not tries this yet, you should!
941 **** You can now refining the current filter by an additional criterion
942 When filtering an existing agenda view with =/=, you can
943 now narrow down the existing selection by an additional
944 condition. Do do this, use =\= instead of =/= to add the
945 additional criterion. You can also press =+= or =-= after
946 =/= to add a positive or negative condition. A condition
947 can be a TAG, or an effort estimate limit, see below.
949 **** It is now possible to filter for effort estimates
950 This means to filter the agenda for the value of the Effort
951 property. For this you should best set up global allowed
952 values for effort estimates, with
954 #+begin_src emacs-lisp
955 (setq org-global-properties
956 '(("Effort_ALL" . "0 0:10 0:30 1:00 2:00 3:00 4:00")))
959 You may then select effort limits with single keys in the
960 filter. It works like this: After =/= or =\=, first select
961 the operator which you want to use to compare effort
964 : < Select entries with effort smaller than or equal to the limit
965 : > Select entries with effort larger than or equal to the limit
966 : = Select entries with effort equal to the limit
968 After that, you can press a single digit number which is
969 used as an index to the allowed effort estimates.
971 If you do not use digits to fast-select tags, you can even
972 skip the operator, which will then default to
973 `org-agenda-filter-effort-default-operator', which is by
976 Thanks to Manish for the great idea to include fast effort
977 filtering into the agenda filtering process.
979 **** The mode line will show the active filter
980 For example, if there is a filter in place that does select
981 for HOME tags, against EMAIL tags, and for tasks with an
982 estimated effort smaller than 30 minutes, the mode-line with
983 show =+HOME-EMAIL+<0:30=
985 **** The filter now persists when the agenda view is refreshed
986 All normal refresh commands, including those that move the
987 weekly agenda from one week to the next, now keep the
988 current filter in place.
990 You need to press =/ /= to turn off the filter. However,
991 when you run a new agenda command, for example going from
992 the weekly agenda to the TODO list, the filter will be
995 *** Setting tags has now its own binding, =C-c C-q=
997 You can still use =C-c C-c= on a headline, but the new
998 binding should be considered as the main binding for this
999 command. The reasons for this change are:
1001 - Using =C-c C-c= for tags is really out of line with other
1004 - I hate it in Remember buffers when I try to set tags and I
1005 cannot, because =C-c C-c= exits the buffer :-(
1007 - =C-c C-q= will also work when the cursor is somewhere down
1008 in the entry, it does not have to be on the headline.
1010 *** Todo state changes can trigger tag changes
1012 The new option =org-todo-state-tags-triggers= can be used to
1013 define automatic changes to tags when a TODO state changes.
1014 For example, the setting
1016 : (setq org-todo-state-tags-triggers
1017 : '((done ("Today" . nil) ("NEXT" . nil))
1018 : ("WAITING" ("Today" . t))))
1020 will make sure that any change to any of the DONE states will
1021 remove tags "Today" and "NEXT", while switching to the
1022 "WAITING" state will trigger the tag "Today" to be added.
1024 I use this mostly to get rid of TODAY and NEXT tags which I
1025 apply to select an entry for execution in the near future,
1026 which I often prefer to specific time scheduling.
1028 *** C-RET will now always insert a new headline, never an item.
1029 The new headline is inserted after the current subtree.
1031 Thanks to Peter Jones for patches to fine-tune this behavior.
1033 *** Customize org-mouse.el feature set
1034 There is a new variable =org-mouse-features= which gives you
1035 some control about what features of org-mouse you want to
1036 use. Turning off some of the feature will free up the
1037 corresponding mouse events, or will avoid activating special
1038 regions for mouse clicks. By default I have urned off the
1039 feature to use drag mouse events to move or promote/demote
1040 entries. You can of course turn them back on if you wish.
1042 This variable may still change in the future, allowing more
1043 fine-grained control.
1045 *** New commands for export to PDF
1047 This is using LaTeX export, and then processes it to PDF
1050 : C-c C-e p process to PDF.
1051 : C-c C-e d process to PDF, and open the file.
1054 - \usepackage{graphicx} is now part of the standard class
1056 - Several bugs fixed, but definitely not all of them :-(
1058 *** New option `org-log-state-notes-insert-after-drawers'
1060 Set this to =t= if you want state change notes to be inserted
1061 after any initial drawers, i.e drawers the immediately follow
1062 the headline and the planning line (the one with
1063 DEADLINE/SCHEDULED/CLOSED information).
1067 *** =org-file-apps= now uses regular expressions, see [[*%20org%20file%20apps%20now%20uses%20regular%20repressions%20instead%20of%20extensions][below]]
1071 *** =org-file-apps= now uses regular repressions instead of extensions
1072 Just like in =auto-mode-alist=, car's in the variable
1073 =org-file-apps= that are strings are now interpreted as
1074 regular expressions that are matched against a file name. So
1075 instead of "txt", you should now write "\\.txt\\'" to make
1076 sure the matching is done correctly (even though "txt" will
1077 be recognized and still be interpreted as an extension).
1079 There is now a shortcut to get many file types visited by
1080 Emacs. If org-file-apps contains `(auto-mode . emacs)', then
1081 any files that are matched by `auto-mode-alist' will be
1084 *** Changes to the attachment system
1086 - The default method to attach a file is now to copy it
1087 instead of moving it.
1088 - You can modify the default method using the variable
1089 `org-attach-method'. I believe that most Unix people want
1090 to set it to `ln' to create hard links.
1091 - The keys =c=, =m=, and =l= specifically select =copy=,
1092 =move=, or =link=, respectively, as the attachment method
1093 for a file, overruling `org-attach-method'.
1094 - To create a new attachment as an Emacs buffer, you have not
1095 now use =n= instead of =c=.
1096 - The file list is now always retrieved from the directory
1097 itself, not from the "Attachments" property. We still
1098 keep this property by default, but you can turn it off, by
1099 customizing the variable =org-attach-file-list-property=.
1103 ** Incompatible changes
1105 - Changes in the structure of IDs, see [[*The%20default%20structure%20of%20IDs%20has%20changed][here]] for details.
1107 - C-c C-a has been redefined, see [[*%20C%20c%20C%20a%20no%20longer%20calls%20show%20all][here]] for details.
1111 *** The default structure of IDs has changed
1113 IDs created by Org have changed a bit:
1114 - By default, there is no prefix on the ID. There used to be
1115 an "Org" prefix, but I now think this is not necessary.
1116 - IDs use only lower-case letters, no upper-case letters
1117 anymore. The reason for this is that IDs are now also used
1118 as directory names for org-attach, and some systems do not
1119 distinguish upper and lower case in the file system.
1120 - The ID string derived from the current time is now
1121 /reversed/ to become an ID. This assures that the first
1122 two letters of the ID change fast, so hat it makes sense to
1123 split them off to create subdirectories to balance load.
1124 - You can now set the `org-id-method' to `uuidgen' on systems
1127 *** =C-c C-a= no longer calls `show-all'
1129 The reason for this is that =C-c C-a= is now used for the
1130 attachment system. On the rare occasions that this command
1131 is needed, use =M-x show-all=, or =C-u C-u C-u TAB=.
1133 *** New attachment system
1135 You can now attach files to each node in the outline tree.
1136 This works by creating special directories based on the ID of
1137 an entry, and storing files in these directories. Org can
1138 keep track of changes to the attachments by automatically
1139 committing changes to git. See the manual for more
1142 Thanks to John Wiegley who contributed this fantastic new
1143 concept and wrote org-attach.el to implement it.
1145 *** New remember template escapes
1147 : %^{prop}p to insert a property
1148 : %k the heading of the item currently being clocked
1149 : %K a link to the heading of the item currently being clocked
1151 Also, when you exit remember with =C-2 C-c C-c=, the item
1152 will be filed as a child of the item currently being
1153 clocked. So the idea is, if you are working on something and
1154 think of a new task related to this or a new note to be
1155 added, you can use this to quickly add information to that
1158 Thanks to James TD Smith for a patch to this effect.
1160 *** Clicking with mouse-2 on clock info in mode-line visits the clock.
1162 Thanks to James TD Smith for a patch to this effect.
1164 *** New file in contrib: lisp/org-checklist.el
1166 This module deals with repeated tasks that have checkbox
1169 Thanks to James TD Smith for this contribution.
1171 *** New in-buffer setting #+STYLE
1173 It can be used to locally set the variable
1174 `org-export-html-style-extra'. Several such lines are
1175 allowed-, they will all be concatenated. For an example on
1176 how to use it, see the [[http://orgmode.org/worg/org-tutorials/org-publish-html-tutorial.php][publishing tutorial]].
1182 - Filtering existing agenda views with respect to a tag
1183 - Editing fixed-width regions with picture or artist mode
1184 - /org-plot.el/ is now part of Org
1185 - Tags can be used to select the export part of a document
1186 - Prefix interpretation when storing remember notes
1187 - Yanking inserts folded subtrees
1188 - Column view capture tables can have formulas, plotting info
1189 - In column view, date stamps can be changed with S-cursor keys
1190 - The note buffer for clocking out now mentions the task
1191 - Sorting entries alphabetically ignores TODO keyword and priority
1192 - Agenda views can sort entries by TODO state
1193 - New face =org-scheduled= for entries scheduled in the future.
1194 - Remember templates for gnus links can use the :to escape.
1195 - The file specification in a remember template may be a function
1196 - Categories in iCalendar export include local tags
1197 - It is possible to define filters for column view
1198 - Disabling integer increment during table Field copy
1199 - Capturing column view is on `C-c C-x i'
1200 - And tons of bugs fixed.
1203 ** Incompatible changes
1205 *** Prefix interpretation when storing remember notes has changed
1207 The prefix argument to the `C-c C-c' command that finishes a
1208 remember process is now interpreted differently:
1210 : C-c C-c Store the note to predefined file and headline
1211 : C-u C-c C-c Like C-c C-c, but immediately visit the note
1212 : in its new location.
1213 : C-1 C-c C-c Select the storage location interactively
1214 : C-0 C-c C-c Re-use the last used location
1216 This was requested by John Wiegley.
1218 *** Capturing column view is now on `C-c C-x i'
1220 The reason for this change was that `C-c C-x r' is also used
1221 as a tty key replacement.
1223 *** Categories in iCalendar export now include local tags
1225 The locally defined tags are now listed as categories when
1226 exporting to iCalendar format. Org's traditional file/tree
1227 category is now the last category in this list. Configure
1228 the variable =org-icalendar-categories= to modify or revert
1231 This was a request by Charles Philip Chan.
1235 *** Secondary filtering of agenda views.
1237 You can now easily and interactively filter an existing
1238 agenda view with respect to a tag. This command is executed
1239 with the =/= key in the agenda. You will be prompted for a
1240 tag selection key, and all entries that do not contain or
1241 inherit the corresponding tag will be hidden. With a prefix
1242 argument, the opposite filter is applied: entries that
1243 do have the tag will be hidden.
1245 This operation only /hides/ lines in the agenda buffer, it
1246 does not remove them. Changing the secondary filtering does
1247 not require a new search and is very fast.
1249 If you press TAB at the tag selection prompt, you will be
1250 switched to a completion interface to select a tag. This is
1251 useful when you want to select a tag that does not have a
1252 direct access character.
1254 A double =/ /= will restore the original agenda view by
1255 unhiding any hidden lines.
1257 This functionality was John Wiegley's idea. It is a simpler
1258 implementation of some of the query-editing features proposed
1259 and implemented some time ago by Christopher League (see the
1260 file contrib/lisp/org-interactive-query.el).
1262 *** Editing fixed-width regions with picture or artist mode
1264 The command @<code>C-c '@</code> (that is =C-c= followed by a
1265 single quote) can now also be used to switch to a special
1266 editing mode for fixed-width sections. The default mode is
1267 =artist-mode= which allows you to create ASCII drawings.
1269 It works like this: Enter the editing mode with
1270 @<code>C-c '@</code>. An indirect buffer will be created and
1271 narrowed to the fixed-width region. Edit the drawing, and
1272 press @<code>C-c '@</code> again to exit.
1274 Lines in a fixed-width region should be preceded by a colon
1275 followed by at least one space. These will be removed during
1276 editing, and then added back when you exit the editing mode.
1278 Using the command in an empty line will create a new
1281 This new feature arose from a discussion involving Scott
1282 Otterson, Sebastian Rose and Will Henney.
1284 *** /org-plot.el/ is now part of Org.
1286 You can run it by simple calling org-plot/gnuplot.
1287 Documentation is not yet included with Org, please refer to
1288 http://github.com/eschulte/org-plot/tree/master until we have
1289 moved the docs into Org or Worg.
1291 Thanks to Eric Schulte for this great contribution.
1293 *** Tags can be used to select the export part of a document
1295 You may now use tags to select parts of a document for
1296 inclusion into the export, and to exclude other parts. This
1297 behavior is governed by two new variables:
1298 =org-export-select-tags= and =org-export-exclude-tags=.
1299 These default to =("export")= and =("noexport")=, but can be
1300 changed, even to include a list of several tags.
1302 Org first checks if any of the /select/ tags is present in
1303 the buffer. If yes, all trees that do not carry one of these
1304 tags will be excluded. If a selected tree is a subtree, the
1305 heading hierarchy above it will also be selected for export,
1306 but not the text below those headings. If none of the select
1307 tags is found anywhere in the buffer, the whole buffer will
1308 be selected for export. Finally, all subtrees that are
1309 marked by any of the /exclude/ tags will be removed from the
1312 You may set these tags with in-buffer options
1313 =EXPORT_SELECT_TAGS= and =EXPORT_EXCLUDE_TAGS=.
1315 I love this feature. Thanks to Richard G Riley for coming
1318 *** Prefix interpretation when storing remember notes
1320 The prefix argument to the `C-c C-c' command that finishes a
1321 remember process is now interpreted differently:
1323 : C-c C-c Store the note to predefined file and headline
1324 : C-u C-c C-c Like C-c C-c, but immediately visit the note
1325 : in its new location.
1326 : C-1 C-c C-c Select the storage location interactively
1327 : C-0 C-c C-c Re-use the last used location
1329 This was requested by John Wiegley.
1331 *** Yanking inserts folded subtrees
1333 If the kill is a subtree or a sequence of subtrees, yanking
1334 them with =C-y= will leave all the subtrees in a folded
1335 state. This basically means, that kill and yank are now
1336 much more useful in moving stuff around in your outline. If
1337 you do not like this, customize the variable
1338 =org-yank-folded-subtrees=.
1340 Right now, I am only binding =C-y= to this new function,
1341 should I modify all bindings of yank? Do we need to amend
1344 This feature was requested by John Wiegley.
1346 *** Column view capture tables can have formulas, plotting info
1348 If you attach formulas and plotting instructions to a table
1349 capturing column view, these extra lines will now survive an
1350 update of the column view capture, and any formulas will be
1351 re-applied to the captured table. This works by keeping any
1352 continuous block of comments before and after the actual
1355 *** In column view, date stamps can be changed with S-cursor keys
1357 If a property value is a time stamp, S-left and S-right can
1358 now be used to shift this date around while in column view.
1360 This was a request by Chris Randle.
1362 *** The note buffer for clocking out now mentions the task
1364 This was a request by Peter Frings.
1366 *** Sorting entries alphabetically ignores TODO keyword and priority
1368 Numerical and alphanumerical sorting now skips any TODO
1369 keyword or priority cookie when constructing the comparison
1370 string. This was a request by Wanrong Lin.
1372 *** Agenda views can sort entries by TODO state
1374 You can now define a sorting strategy for agenda entries that
1375 does look at the TODO state of the entries. Sorting by TODO
1376 entry does first separate the non-done from the done states.
1377 Within each class, the entries are sorted not alphabetically,
1378 but in definition order. So if you have a sequence of TODO
1379 entries defined, the entries will be sorted according to the
1380 position of the keyword in this sequence.
1382 This follows an idea and sample implementation by Christian
1385 *** New face =org-scheduled= for entries scheduled in the future.
1387 This was a request by Richard G Riley.
1389 *** Remember templates for gnus links can now use the :to escape.
1391 Thanks to Tommy Lindgren for a patch to this effect.
1392 *** The file specification in a remember template may now be a function
1394 Thanks to Gregory Sullivan for a patch to this effect.
1396 *** Categories in iCalendar export now include local tags
1398 The locally defined tags are now listed as categories when
1399 exporting to iCalendar format. Org's traditional file/tree
1400 category is now the last category in this list. Configure
1401 the variable =org-icalendar-categories= to modify or revert
1404 This was a request by Charles Philip Chan.
1406 *** It is now possible to define filters for column view
1408 The filter can modify the value that will be displayed in a
1409 column, for example it can cut out a part of a time stamp.
1410 For more information, look at the variable
1411 =org-columns-modify-value-for-display-function=.
1413 *** Disabling integer increment during table field copy
1415 Prefix arg 0 to S-RET does the trick.
1417 This was a request by Chris Randle.
1422 For older Changes, see [[file:Changes_old.org]]