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
20 *** Support for simple TODO dependencies
22 John Wiegley's code for enforcing simple TODO dependencies has
23 been integrated into Org-mode. Thanks John!
25 The structure of Org files (hierarchy and lists) makes it easy to
26 define TODO dependencies. A parent TODO task should not be
27 marked DONE until all subtasks (defined as children tasks) are
28 marked as DONE. And sometimes there is a logical sequence to a
29 number of (sub)tasks, so that one task cannot be acted upon
30 before all siblings above it are done. If you customize the
31 variable =org-enforce-todo-dependencies=, Org will block entries
32 from changing state while they have children that are not DONE.
33 Furthermore, if an entry has a property =ORDERED=, each of its
34 children will be blocked until all earlier siblings are marked
35 DONE. Here is an example:
38 ,* TODO Blocked until (two) is done
47 ,** TODO b, needs to wait for (a)
48 ,** TODO c, needs to wait for (a) and (b)
51 The variable =org-agenda-dim-blocked-tasks= controls how blocked
52 entries should appear in the agenda, where they can be dimmed or
55 *** Support for shift-selection in Emacs 23
57 Customize the variable =org-support-shift-select= to use S-cursor
58 key for selecting text. Make sure that you carefully read the
59 docstring of that variable first.
61 *** Adding and removing checkboxes from many lines
63 The command =C-c C-x C-b= normally toggles checkbox status in the
64 current line, or in all lines in the region. With prefix
65 argument it now either adds or removes the checkbox.
67 This was a requested by Daniel Clemente.
73 - Improved behavior of conversion commands =C-c -= and =C-c *=
74 - Table formulas may now reference fields in other tables
75 - A final hline is imagined in each table, for the sake of references
76 - A tags-todo search can now ignore timestamped items
77 - =\par= can be used to force a paragraph break, also in footnotes
82 *** Improved behavior of conversion commands =C-c -= and =C-c *=
84 The conversion commands =C-c -= and =C-c *= are now better
85 behaved and therefore more useful, I hope.
87 If there is an active region, these commands will act on the
88 region, otherwise on the current line.
90 - C-c - :: This command turns headings or normal lines into
91 items, or items into normal lines. When there is a
92 region, everything depends on the first line of the
94 - if it is a item, turn all items in the region into
96 - if it is a headline, turn all headlines in the region
98 - if it is a normal line, turn all lines into items.
99 - special case: if there is no active region and the
100 current line is an item, cycle the bullet type of the
102 - C-c * :: This command turns items and normal lines into
103 headings, or headings into normal lines. When there is
104 a region, everything depends on the first line of the
106 - if it is a item, turn all items in the region into
108 - if it is a headline, turn all headlines in the region
110 - if it is a normal line, turn all lines into headlines.
112 *** Table formulas may now reference fields in other tables
114 You may now reference constants, fields and ranges from a
115 different table, either in the current file or even in a
116 different file. The syntax is
118 : remote(NAME-OR-ID,REF)
120 where /NAME/ can be the name of a table in the current file as
121 set by a =#+TBLNAME: NAME= line before the table. It can also be
122 the ID of an entry, even in a different file, and the reference
123 then refers to the first table in that entry. /REF/ is an
124 absolute field or range reference, valid in the referenced table.
125 Note that since there is no "current filed" for the remote table,
126 all row and column references must be absolute, not relative.
128 *** A final hline is imagined in each table, for the sake of references
130 Even if a table does not end with a hline (mine never do because I
131 think it is not pretty), for the sake of references you can
132 assume there is one. So in the following table
141 a reference like =@I$1..@II$2= will now work.
143 *** A tags-todo search can now ignore timestamped items
144 The variables =org-agenda-todo-ignore-with-date=,
145 =org-agenda-todo-ignore-with-date=, and
146 =org-agenda-todo-ignore-with-date= make it possible to
147 exclude TODO entries which have this kind of planning info
148 associated with them. This is most useful for people who
149 schedule everything, and who use the TODO list mainly to find
150 things that are not yet scheduled. Thomas Morgan pointed out
151 that also the tags-todo search may serve exactly this
152 purpose, and that it might be good to have a way to make
153 these variables also apply to the tags-todo search. I can
154 see that, but could not convince myself to make this the
155 default. A new variable must be set to make this happen:
156 =org-agenda-tags-todo-honor-ignore-options=.
158 *** =\par= can be used to force a paragraph break, also in footnotes
160 The LaTeX idiom =\par= will insert a paragraph break at that
161 location. Normally you would simply leave an empty line to get
162 such a break, but this is useful for footnotes whose
163 definitions may not contain empty lines.
166 ** Incompatible changes
168 *** Short examples must have a space after the colon
170 Short literal examples can be created by preceding lines
171 with a colon. Such lines must now have a space after the
172 colon. I believe this is already general practice, but now
173 it must be like this. The only exception are lines what are
174 empty except for the colon.
178 *** Include files can now also process switches
180 The example and src switches like =-n= can now also be added
181 to include file statements:
183 : #+INCLUDE "~/.emacs" src emacs-lisp -n -r
185 Thanks to Manish for pointing out that this was not yet
188 *** Examples can be exported to HTML as text areas
190 You can now specify a =-t= switch to an example or src block,
191 to make it export to HTML as a text area. To change the
192 defaults for height (number of lines in the example) and
193 width of this area (80), use the =-h= and =-w= switches.
195 Thanks to Ulf Stegemann for driving this development.
197 *** LaTeX_CLASS can be given as a property
199 When exporting a single subtree by selecting it as a region
200 before export, the LaTeX class for the export will be taken
201 from the =LaTeX_CLASS= property of the entry if present.
203 Thanks to Robert Goldman for this request.
205 *** Better handling of inlined images in different backends
207 Two new variables govern which kind of files can be inlined
208 during export. These are
209 =org-export-html-inline-image-extensions= and
210 =org-export-latex-inline-image-extensions=. Remember that
211 links are turned into an inline image if they are a pure link
212 with no description. HTML files can inline /.png/, /.jpg/,
213 and /.gif/ files, while LaTeX files, when processed with
214 /pdflatex/, can inline /.png/, /.jpg/, and /.pdf/ files.
215 These also represent the default settings for the new
216 variables. Note that this means that pure links to /.pdf/
217 files will be inlined - to avoid this for a particular link,
218 make sure that the link has a description part which is not
219 equal to the link part.
221 *** Links by ID now continue to work in HTML exported files
223 If you make links by ID, these links will now still work in
224 HTML exported files, provided that you keep the relative path
225 from link to target file the same.
227 Thanks to Friedrich Delgado Friedrichs for pushing this over
230 *** The relative timer can be paused
232 The new command `C-c C-x ,' will pause the relative timer.
233 When the relative timer is running, its value will be shown
234 in the mode line. To get rid of this display, you need to
235 really stop the timer with `C-u C-c C-x ,'.
237 Thanks to Alan Davis for driving this change.
239 *** The attachment directory may now be chosen by the user
241 Instead of using the automatic, unique directory related to
242 the entry ID, you can also use a chosen directory for the
243 attachments of an entry. This directory is specified by the
244 ATTACH_DIR property. You can use `C-c C-a s' to set this
247 Thanks to Jason Jackson for this proposal.
249 *** You can use a single attachment directory for a subtree
251 By setting the property ATTACH_DIR_INHERIT, you can now tell
252 Org that children of the entry should use the same directory
253 for attachments, unless a child explicitly defines its own
254 directory with the ATTACH_DIR property. You can use the
255 command `C-c C-a i' to set this property in an entry.
262 - Line numbers and references in literal examples
263 - New hooks for export preprocessing
264 - Capture column view into a different file
270 Org-mode now directly supports the creation of footnotes. In
271 contrast to the /footnote.el/ package, Org-mode's footnotes are
272 designed for work on a larger document, not only for one-off
273 documents like emails. The basic syntax is similar to the one
274 used by /footnote.el/, i.e. a footnote is defined in a paragraph
275 that is started by a footnote marker in square brackets in column
276 0, no indentation allowed. The footnote reference is simply the
277 marker in square brackets inside text. For example:
280 The Org homepage[fn:1] now looks a lot better than it used to.
282 [fn:1] The link is: http://orgmode.org
285 Org-mode extends the number-based syntax to /named/ footnotes and
286 optional inline definition. Using plain numbers as markers is
287 supported for backward compatibility, but not encouraged because
288 of possible conflicts with LaTeX syntax. Here are the valid
291 - [1] :: A plain numeric footnote marker.
293 - [fn:name] :: A named footnote reference, where `name' is a
294 unique label word or, for simplicity of automatic creation,
297 - [fn:: This is the inline definition of this footnote] :: A
298 LaTeX-like anonymous footnote where the definition is given
299 directly at the reference point.
301 - [fn:name: a definition] :: An inline definition of a footnote,
302 which also specifies a name for the note. Since Org allows
303 multiple references to the same note, you can then use use
304 `[fn:name]' to create additional references.
306 Footnote labels can be created automatically, or you create names
307 yourself. This is handled by the variable
308 =org-footnote-auto-label= and its corresponding =#+STARTUP=
309 keywords, see the docstring of that variable for details.
311 The following command handles footnotes:
313 - C-c C-x f :: The footnote action command. When the cursor is
314 on a footnote reference, jump to the definition. When it is
315 at a definition, jump to the (first) reference. Otherwise,
316 create a new footnote. Depending on the variable
317 `org-footnote-define-inline' (with associated =#+STARTUP=
318 options =fninline= and =nofninline=), the definitions will
319 be placed right into the text as part of the reference, or
320 separately into the location determined by the variable
321 =org-footnote-section=.
322 When this command is called with a prefix argument, a menu
323 of additional options is offered:
324 - s :: Sort the footnote definitions by reference sequence.
325 During editing, Org makes no effort to sort footnote
326 definitions into a particular sequence. If you want
327 them sorted, use this command, which will also move
328 entries according to =org-footnote-section=.
329 - n :: Normalize the footnotes by collecting all
330 definitions (including inline definitions) into a
331 special section, and then numbering them in
332 sequence. The references will then also be
333 numbers. This is meant to be the final step before
334 finishing a document (e.g. sending off an email).
335 The exporters do this automatically, and so could
336 something like `message-send-hook'.
337 - d :: Delete the footnote at point, and all references to it.
339 - C-c C-c :: If the cursor is on a footnote reference, jump to
340 the definition. If it is a the definition, jump back to the
341 reference. When called with a prefix argument at either
342 location, offer the same menu as `C-u C-c C-x f'.
344 - C-c C-o or mouse-1/2 :: Footnote labels are also links to the
345 corresponding definition/reference, and you can use the
346 usual commands to follow these links.
348 Org-mode's footnote support is designed so that it should also
349 work in buffers that are not in Org-mode, for example in email
350 messages. Just bind =org-footnote-action= to a global key like
353 The main trigger for this development came from a hook function
354 written by Paul Rivier, to implement named footnotes and to
355 convert them to numbered ones before export. Thanks, Paul!
357 Thanks also to Scot Becker for a thoughtful post bringing this
358 subject back onto the discussion table, and to Matt Lundin for
359 the idea of named footnotes and his prompt testing of the new
362 *** Line numbers and references in literal examples
364 Literal examples introduced with =#+BEGIN_EXAMPLE= or =#+BEGIN_SRC=
365 do now allow optional line numbering in the example.
366 Furthermore, links to specific code lines are supported, greatly
367 increasing Org-mode's utility for writing tutorials and other
370 Code references use special labels embedded directly into the
371 source code. Such labels look like "(ref:name)" and must be
372 unique within a document. Org-mode links with "(name)" in the
373 link part will be correctly interpreted, both while working with
374 an Org file (internal links), and while exporting to the
375 different backends. Line numbering and code references are
376 supported for all three major backends, HTML, LaTeX, and ASCII.
377 In the HTML backend, hovering the mouse over a link to a source
378 line will remote-highlight the referenced code line.
380 The options for the BEGIN lines are:
382 - -n :: Number the lines in the example
383 - +n :: Like -n, but continue numbering from where the previous
385 - -r :: Remove the coderef cookies from the example, and replace
386 links to this reference with line numbers. This option
387 takes only effect if either -n or +n are given as well.
388 If -r is not given, coderefs simply use the label name.
389 - -l "fmt" :: Define a local format for coderef labels, see the
390 variable =org-coderef-label-format= for details. Use this
391 of the default syntax causes conflicts with the code in the
392 code snippet you are using.
397 #+begin_src emacs-lisp -n -r
398 (defmacro org-unmodified (&rest body) (ref:def)
399 "Execute body without changing `buffer-modified-p'."
400 `(set-buffer-modified-p (ref:back)
401 (prog1 (buffer-modified-p) ,@body)))
403 [[(def)][Line (def)]] contains the macro name. Later at line [[(back)]],
407 When exported, this is translated to:
408 #+begin_src emacs-lisp -n -r
409 (defmacro org-unmodified (&rest body) (ref:def)
410 "Execute body without changing `buffer-modified-p'."
411 `(set-buffer-modified-p (ref:back)
412 (prog1 (buffer-modified-p) ,@body)))
414 [[(def)][Line (def)]] contains the macro name. Later at line [[(back)]],
417 Thanks to Ilya Shlyakhter for proposing this feature set. Thanks
418 to Sebastian Rose for the key Javascript element that made the
419 remote highlighting possible.
421 *** New hooks for export preprocessing
422 The export preprocessor now runs more hooks, to allow
423 better-timed tweaking by user functions:
425 - =org-export-preprocess-hook= ::
426 Pretty much the first thing in the preprocessor. But org-mode
427 is already active in the preprocessing buffer.
429 - =org-export-preprocess-after-include-files-hook= ::
430 This is run after the contents of included files have been inserted.
432 - =org-export-preprocess-after-tree-selection-hook= ::
433 This is run after selection of trees to be exported has
434 happened. This selection includes tags-based selection, as
435 well as removal of commented and archived trees.
437 - =org-export-preprocess-before-backend-specifics-hook= ::
438 Hook run before backend-specific functions are called during preprocessing.
440 - =org-export-preprocess-final-hook= ::
441 Hook for preprocessing an export buffer. This is run as the
442 last thing in the preprocessing buffer, just before returning
443 the buffer string to the backend.
445 *** Capture column view into a different file
447 The :id parameter for the dynamic block capturing column view
448 can now truly be an ID that will also be found in a
449 different file. Also, it can be like =file:path/to/file=, to
450 capture the global column view from a different file.
452 Thanks to Francois Lagarde for his report that IDs outside
453 the current file would not work.
456 Cleanup of many small bugs, and one new feature.
460 *** References to last table row with special names
462 Fields in the last row of a table can now be referenced with
463 $LR1, $LR2, etc. These references can appear both on the
464 left hand side and right hand side of a formula.
468 This version reverses the introduction of @0 as a reference to
469 the last rwo in a table, because of a conflict with the use of
470 @0 for the current row.
475 - All known LaTeX export issues fixed
476 - Captions and attributes for figures and tables.
477 - Better implementation for entry IDs
478 - Spreadsheet references to the last table line.
479 - Old syntax for link attributes abandoned
481 ** Incompatible changes
482 *** Old syntax for link attributes abandoned
484 There used to be a syntax for setting link attributes for
485 HTML export by enclosing the attributes into double braces
486 and adding them to the link itself, like
489 [[./img/a.jpg{{alt="an image"}}] ]
492 This syntax is not longer supported, use instead
495 ,#+ATTR_HTML: alt="an image"
501 *** All known LaTeX export issues fixed
503 All the remaining issues with the LaTeX exporter have hopefully
504 been addressed in this release. In particular, this covers
505 quoting of special characters in tables and problems with
506 exporting files where the headline is in the first line, or with
509 *** Captions and attributes for figures and tables.
511 Tables, and Hyperlinks that represent inlined images, can now be
512 equipped with additional information that will be used during
513 export. The information will be taken from the following special
514 lines in the buffer and apply to the first following table or
517 - #+CAPTION: :: The caption of the image or table. This string
518 should be processed according to the export backend, but
519 this is not yet done.
521 - #+LABEL: :: A label to identify the figure/table for cross
522 references. For HTML export, this string will become the
523 ID for the ~<div class="figure">~ element that encapsulates
524 the image tag and the caption. For LaTeX export, this
525 string will be used as the argument of a ~\label{...}~
526 macro. These labels will be available for internal links
527 like ~[[label][Table] ]~.
529 - #+ATTR_HTML: :: Attributes for HTML export of image, to be
530 added as attributes into the ~<img...>~ tag. This string
531 will not be processed, so it should have immediately the
534 - #+ATTR_LaTeX: :: Attributes for LaTeX export of images and
536 For /images/, this string is directly inserted into
537 the optional argument of the ~\includegraphics[...]{file}~
538 command, to specify scaling, clipping and other options.
539 This string will not be processed, so it should have
540 immediately the right format, like =width=5cm,angle=90=.\\
541 For /tables/, this can currently contain the keyword
542 =longtable=, to request typesetting of the table using the
543 longtable package, which automatically distributes the table
544 over several pages if needed. Also, the attributes line may
545 contain an alignment string for the tabular environment, like
546 =longtable,align=l|lrl=
548 For LaTeX export, if either a caption or a label is given, the element
549 will be exported as a float, i.e. wrapped into a figure or table
552 *** Better implementation for entry IDs
554 Unique identifiers for entries can now be used more efficiently.
555 Internally, a hash array has replaced the alist used so far to
556 keep track of the files in which an ID is defined. This makes it
557 quite fast to find an entry by ID.
559 There is a new link type which looks like this:
562 id:GLOBALLY-UNIQUE-IDENTIFIER
565 This link points to a specific entry. When you move the entry to
566 a different file, for example if you move it to an archive
567 file, the link will continue to work.
569 The file /org-id.el/ contains an API that can be used to write
570 code using these identifiers, including creating IDs and finding
571 them wherever they are.
573 Org has its own method to create unique identifiers, but if the system
574 has /uuidgen/ command installed (Mac's and Linux systems generally
575 do), it will be used by default (a change compared to the earlier
576 implmentation, where you explicitdly had to opt for uuidgen). You can
577 also select the method by hand, using the variable =org-id-method=.
579 If the ID system ever gets confused about where a certain ID is, it
580 initiates a global scan of all agenda files with associated archives,
581 all files previously known containing any IDs, and all currently
582 visited Org-mode files to rebuild the hash. You can also initiate
583 this by hand: =M-x org-id-update-id-locations=. Running this command
584 will also dump into the =*Messages*= buffer information about any
585 duplicate IDs. These should not exist, and Org will never /make/ the
586 same ID twice, but if you /copy/ an entry with its properties,
587 duplicate IDs will inevitably be produced. Unfortunately, this is
588 unavoidable in a plain text system that allows you to edit the text in
589 arbitrary ways, and a portion of care on your side is needed to keep
592 The hash is stored in the file =~/.emacs.d/.org-id-locations=.
593 This is also a change from previous versions where the file was
594 =~/.org=id-locations=. Therefore, you can remove this old file
595 if you have it. I am not sure what will happen if the =.emacs.d=
596 directory does not exists in your setup, but in modern Emacsen, I
597 believe it should exist. If you do not want to use IDs across
598 files, you can avoid the overhead with tracking IDs by
599 customizing the variable =org-id-track-globally=. IDs can then
600 still be used for links inside a single file.
602 IDs will also be used when you create a new link to an Org-mode
603 buffer. If you use =org-store-link= (normally at =C-c l=) inside
604 en entry in an Org-mode buffer, and ID property will be created
605 if it does not exist, and the stored link will be an =id:= link.
606 If you prefer the much less secure linking to headline text, you
607 can configure the variable =org-link-to-org-use-id=. The default
608 setting for this variable is =create-if-interactive=, meaning
609 that an ID will be created when you store a link interactively,
610 but not if you happen to be in an Org-mode file while you create
611 a remember note (which usually has a link to the place where you
612 were when starting remember).
614 *** Spreadsheet references to the last table line.
616 You may now use =@0= to reference the last dataline in a table
617 in a stable way. This is useful in particular for automatically
618 generated tables like the ones using /org-collector.el/ by Eric
624 - New relative timer to support timed notes
625 - Special faces can be set for individual tags
626 - The agenda shows now all tags, including inherited ones.
627 - Exclude some tags from inheritance.
628 - More special values for time comparisons in property searches
629 - Control for exporting meta data
630 - Cut and Paste with hot links from w3m to Org
631 - LOCATION can be inherited for iCalendar export
632 - Relative row references crossing hlines now throw an error
634 ** Incompatible Changes
636 *** Relative row references crossing hlines now throw an error
638 Relative row references in tables look like this: "@-4" which
639 means the forth row above this one. These row references are
640 not allowed to cross horizontal separator lines (hlines). So
641 far, when a row reference violates this policy, Org would
642 silently choose the field just next to the hline.
644 Tassilo Horn pointed out that this kind of hidden magic is
645 actually confusing and may cause incorrect formulas, and I do
646 agree. Therefore, trying to cross a hline with a relative
647 reference will now throw an error.
649 If you need the old behavior, customize the variable
650 `org-table-error-on-row-ref-crossing-hline'.
654 *** New relative timer to support timed notes
656 Org now supports taking timed notes, useful for example while
657 watching a video, or during a meeting which is also recorded.
660 Insert a relative time into the buffer. The first time
661 you use this, the timer will be started. When called
662 with a prefix argument, the timer is reset to 0.
665 Insert a description list item with the current relative
666 time. With a prefix argument, first reset the timer to 0.
669 Once the time list has been initiated, you can also use the
670 normal item-creating command to insert the next timer item.
673 Reset the timer without inserting anything into the buffer.
674 By default, the timer is reset to 0. When called with a
675 =C-u= prefix, reset the timer to specific starting
676 offset. The user is prompted for the offset, with a
677 default taken from a timer string at point, if any, So this
678 can be used to restart taking notes after a break in the
679 process. When called with a double prefix argument
680 =C-c C-u=, change all timer strings in the active
681 region by a certain amount. This can be used to fix timer
682 strings if the timer was not started at exactly the right
685 Thanks to Alan Dove, Adam Spiers, and Alan Davis for
686 contributions to this idea.
688 *** Special faces can be set for individual tags
690 You may now use the variable =org-tag-faces= to define the
691 face used for specific tags, much in the same way as you can
692 do for TODO keywords.
694 Thanks to Samuel Wales for this proposal.
696 *** The agenda shows now all tags, including inherited ones.
698 This request has come up often, most recently it was
699 formulated by Tassilo Horn.
701 If you prefer the old behavior of only showing the local
702 tags, customize the variable =org-agenda-show-inherited-tags=.
704 *** Exclude some tags from inheritance.
706 So far, the only way to select tags for inheritance was to
707 allow it for all tags, or to do a positive selection using
708 one of the more complex settings for
709 `org-use-tag-inheritance'. It may actually be better to
710 allow inheritance for all but a few tags, which was difficult
711 to achieve with this methodology.
713 A new option, `org-tags-exclude-from-inheritance', allows to
714 specify an exclusion list for inherited tags.
716 *** More special values for time comparisons in property searches
718 In addition to =<now>=, =<today>=, =<yesterday>=, and
719 =<tomorrow>=, there are more special values accepted now in
720 time comparisons in property searches: You may use strings
721 like =<+3d>= or =<-2w>=, with units d, w, m, and y for day,
722 week, month, and year, respectively
724 Thanks to Linday Todd for this proposal.
726 *** Control for exporting meta data
728 All the metadata in a headline, i.e. the TODO keyword, the
729 priority cookie, and the tags, can now be excluded from
730 export with appropriate options:
732 | Variable | Publishing property | OPTIONS switch |
733 |-------------------------------+---------------------+----------------|
734 | org-export-with-todo-keywords | :todo-keywords | todo: |
735 | org-export-with-tags | :tags | tags: |
736 | org-export-with-priority | :priority | pri: |
738 *** Cut and Paste with hot links from w3m to Org
740 You can now use the key =C-c C-x M-w= in a w3m buffer with
741 HTML content to copy either the region or the entire file in
742 a special way. When you yank this text back into an Org-mode
743 buffer, all links from the w3m buffer will continue to work
746 For this to work you need to load the new file /org-w3m.el./
747 Please check your org-modules variable to make sure that this
750 Thanks for Richard Riley for the idea and to Andy Stewart for
753 *** LOCATION can be inherited for iCalendar export
755 The LOCATION property can now be inherited during iCalendar
756 export if you configure =org-use-property-inheritance= like
759 #+begin_src emacs-lisp
760 (setq org-use-property-inheritance '("LOCATION"))
767 - Keybindings in Remember buffers can be configured
768 - Support for ido completion
769 - New face for date lines in agenda column view
770 - Invisible targets become now anchors in headlines.
771 - New contributed file /org-exp-blocks.el/
772 - New contributed file /org-eval-light.el/
774 - BBDB links may use regular expressions.
775 - Link abbreviations can use %h to insert a url-encoded target value
776 - Improved XHTML compliance
780 *** Keybindings in Remember buffers can be configured
782 The remember buffers created with Org's extensions are in
783 Org-mode, which is nice to prepare snippets that will
784 actually be stored in Org-mode files. However, this makes it
785 hard to configure key bindings without modifying the Org-mode
786 keymap. There is now a minor mode active in these buffers,
787 `org-remember-mode', and its keymap org-remember-mode-map can
788 be used for key bindings. By default, this map only contains
789 the bindings for =C-c C-c= to store the note, and =C-c C-k=
790 to abort it. Use `org-remember-mode-hook' to define your own
793 #+begin_src emacs-lisp
795 'org-remember-mode-hook
797 (define-key org-remember-mode-map
798 "\C-x\C-s" 'org-remember-finalize)))
801 If you wish, you can also use this to free the =C-c C-c=
802 binding (by binding this key to nil in the minor mode map),
803 so that you can use =C-c C-c= again to set tags.
805 This modification is based on a request by Tim O'Callaghan.
807 *** Support for ido completion
809 You can now get the completion interface from /ido.el/ for
810 many of Org's internal completion commands by turning on the
811 variable =org-completion-use-ido=. =ido-mode= must also be
812 active before you can use this.
814 This change is based upon a request by Samuel Wales.
816 *** New face for date lines in agenda column view
818 When column view is active in the agenda, and when you have
819 summarizing properties, the date lines become normal column
820 lines and the separation between different days becomes
821 harder to see. If this bothers you, you can now customize
822 the face =org-agenda-column-dateline=.
824 This is based on a request by George Pearson.
826 *** Invisible targets become now anchors in headlines.
828 These anchors can be used to jump to a directly with an HTML
829 link, just like the =sec-xxx= IDs. For example, the
830 following will make a http link
831 =//domain/path-to-my-file.html#dummy= work:
838 This is based on a request by Matt Lundin.
840 *** New contributed file /org-exp-blocks.el/
842 This new file implements special export behavior of
843 user-defined blocks. The currently supported blocks are
845 - comment :: Comment blocks with author-specific markup
846 - ditaa :: conversion of ASCII art into pretty png files
847 using Stathis Sideris' /ditaa.jar/ program
848 - dot :: creation of graphs in the /dot/ language
849 - R :: Sweave type exporting using the R program
851 For more details and examples, see the file commentary in
854 Kudos to Eric Schulte for this new functionality, after
855 /org-plot.el/ already his second major contribution. Thanks
856 to Stathis for this excellent program, and for allowing us to
857 bundle it with Org-mode.
859 *** New contributed file /org-eval-light.el/
861 This module gives control over execution Emacs Lisp code
862 blocks included in a file.
864 Thanks to Eric Schulte also for this file.
868 You can now configure Org to understand many links created
869 with the Emacs Planner package, so you can cut text from
870 planner pages and paste them into Org-mode files without
871 having to re-write the links. Among other things, this means
872 that the command =org-open-at-point-global= which follows
873 links not only in Org-mode, but in arbitrary files like
874 source code files etc, will work also with links created by
875 planner. The following customization is needed to make all of
878 #+begin_src emacs-lisp
879 (setq org-link-translation-function
880 'org-translate-link-from-planner)
883 I guess an inverse translator could be written and integrated
886 *** BBDB links may use regular expressions.
888 This did work all along, but only now I have documented it.
890 *** =yank-pop= works again after yanking an outline tree
892 Samuel Wales had noticed that =org-yank= did mess up this
893 functionality. Now you can use =yank-pop= again, the only
894 restriction is that the so-yanked text will not be
895 pro/demoted or folded.
897 *** Link abbreviations can use %h to insert a url-encoded target value
899 Thanks to Steve Purcell for a patch to this effect.
901 *** Improved XHTML compliance
903 Thanks to Sebastian Rose for pushing this.
905 *** Many bug fixes again.
910 - A region of entries can now be refiled with a single command
911 - Fine-tuning the behavior of `org-yank'
912 - Formulas for clocktables
913 - Better implementation of footnotes for HTML export
914 - More languages for HTML export.
918 *** A region of entries can now be refiled with a single command
920 With =transient-make-mode= active (=zmacs-regions= under
921 XEmacs), you can now select a region of entries and refile
922 them all with a single =C-c C-w= command.
924 Thanks to Samuel Wales for this useful proposal.
926 *** Fine-tuning the behavior of =org-yank=
928 The behavior of Org's yanking command has been further
929 fine-tuned in order to avoid some of the small annoyances
932 - Calling =org-yank= with a prefix arg will stop any special
933 treatment and directly pass through to the normal =yank=
934 command. Therefore, you can now force a normal yank with
937 - Subtrees will only be folded after a yank if doing so will
938 now swallow any non-white characters after the yanked text.
939 This is, I think a really important change to make the
940 command work more sanely.
942 *** Formulas for clocktables
944 You can now add formulas to a clock table, either by hand, or
945 with a =:formula= parameter. These formulas can be used to
946 create additional columns with further analysis of the
949 Thanks to Jurgen Defurne for triggering this addition.
951 *** Better implementation of footnotes for HTML export
953 The footnote export in 6.11 really was not good enough. Now
954 it works fine. If you have customized
955 =footnote-section-tag=, make sure that your customization is
956 matched by =footnote-section-tag-regexp=.
958 Thanks to Sebastian Rose for pushing this change.
960 *** More languages for HTML export.
962 More languages are supported during HTML export. This is
963 only relevant for the few special words Org inserts, like
964 "Table of Contents", or "Footnotes". Also the encoding
965 issues with this feature seem to be solved now.
967 Thanks to Sebastian Rose for pushing me to fix the encoding
974 - Yanking subtree with =C-y= now adjusts the tree level
975 - State changes can now be shown in the log mode in the agenda
976 - Footnote in HTML export are now collected at the end of the document
977 - HTML export now validates again as XHTML
978 - The clock can now be resumed after exiting and re-starting Emacs
979 - Clock-related data can be saved and resumed across Emacs sessions
980 - Following file links can now use C-u C-u to force use of an external app
981 - Inserting absolute files names now abbreviates links with "~"
982 - Links to attachment files
983 - Completed repeated tasks listed briefly in agenda
984 - Remove buffers created during publishing are removed
988 *** Yanking subtree with =C-y= now adjusts the tree level
989 When yanking a cut/copied subtree or a series of trees, the
990 normal yank key =C-y= now adjusts the level of the tree to
991 make it fit into the current outline position, without losing
992 its identity, and without swallowing other subtrees.
994 This uses the command =org-past-subtree=. An additional
995 change in that command has been implemented: Normally, this
996 command picks the right outline level from the surrounding
997 *visible* headlines, and uses the smaller one. So if the
998 cursor is between a level 4 and a level 3 headline, the tree
999 will be pasted as level 3. If the cursor is actually *at*
1000 the beginning of a headline, the level of that headline will
1001 be used. For example, lets say you have a tree like this:
1007 ,(2)* Level one again
1010 with (1) and (2) indicating possible cursor positions for the
1011 insertion. When at (1), the tree will be pasted as level 2.
1012 When at (2), it will be pasted as level 1.
1014 If you do not want =C-y= to behave like this, configure the
1015 variable =org-yank-adjusted-subtrees=.
1017 Thanks to Samuel Wales for this idea and a partial implementation.
1019 *** State changes can now be shown in the log mode in the agenda
1021 If you configure the variable =org-agenda-log-mode-items=,
1022 you can now request that all logged state changes be included
1023 in the agenda when log mode is active. If you find this too
1024 much for normal applications, you can also temporarily
1025 request the inclusion of state changes by pressing =C-u l= in
1028 This was a request by Hsiu-Khuern Tang.
1030 You can also press `C-u C-u l' to get *only* log items in the
1031 agenda, withour any timestamps/deadlines etc.
1033 *** Footnote in HTML export are now collected at the end of the document
1034 Previously, footnotes would be left in the document where
1035 they are defined, now they are all collected and put into a
1036 special =<div>= at the end of the document.
1038 Thanks to Sebastian Rose for this request.
1040 *** HTML export now validates again as XHTML.
1042 Thanks to Sebastian Rose for pushing this cleanup.
1044 *** The clock can now be resumed after exiting and re-starting Emacs
1046 If the option =org-clock-in-resume= is t, and the first clock
1047 line in an entry is unclosed, clocking into that task resumes
1048 the clock from that time.
1050 Thanks to James TD Smith for a patch to this effect.
1052 *** Clock-related data can be saved and resumed across Emacs sessions
1054 The data saved include the contents of =org-clock-history=,
1055 and the running clock, if there is one.
1057 To use this, you will need to add to your .emacs
1059 #+begin_src emacs-lisp
1060 (setq org-clock-persist t)
1061 (setq org-clock-in-resume t)
1062 (org-clock-persistence-insinuate)
1065 Thanks to James TD Smith for a patch to this effect.
1067 *** Following file links can now use C-u C-u to force use of an external app.
1069 So far you could only bypass your setup in `org-file-apps'
1070 and force opening a file link in Emacs by using a =C-u= prefix arg
1071 with =C-c C-o=. Now you can call =C-u C-u C-c C-o= to force
1072 an external application. Which external application depends
1073 on your system. On Mac OS X and Windows, =open= is used. On
1074 a GNU/Linux system, the mailcap settings are used.
1076 This was a proposal by Samuel Wales.
1078 *** Inserting absolute files names now abbreviates links with "~".
1080 Inserting file links with =C-u C-c C-l= was buggy if the
1081 setting of `org-link-file-path-type' was `adaptive' (the
1082 default). Absolute file paths were not abbreviated relative
1083 to the users home directory. This bug has been fixed.
1085 Thanks to Matt Lundin for the report.
1087 *** Links to attachment files
1089 Even though one of the purposes of entry attachments was to
1090 reduce the number of links in an entry, one might still want
1091 to have the occasional link to one of those files. You can
1092 now use link abbreviations to set up a special link type that
1093 points to attachments in the current entry. Note that such
1094 links will only work from within the same entry that has the
1095 attachment, because the directory path is entry specific.
1096 Here is the setup you need:
1098 #+begin_src emacs-lisp
1099 (setq org-link-abbrev-alist '(("att" . org-attach-expand-link)))
1102 After this, a link like this will work
1105 [[att:some-attached-file.txt]]
1107 This was a proposal by Lindsay Todd.
1109 *** Completed repeated tasks listed briefly in agenda
1111 When a repeating task, listed in the daily/weekly agenda under
1112 today's date, is completed from the agenda, it is listed as
1113 DONE in the agenda until the next update happens. After the
1114 next update, the task will have disappeared, of course,
1115 because the new date is no longer today.
1117 *** Remove buffers created during publishing are removed
1119 Buffers that are created during publishing are now deleted
1120 when the publishing is over. At least I hope it works like this.
1126 - Secondary agenda filtering is becoming a killer feature
1127 - Setting tags has now its own binding, =C-c C-q=
1128 - Todo state changes can trigger tag changes
1129 - C-RET will now always insert a new headline, never an item.
1130 - Customize org-mouse.el feature set to free up mouse events
1131 - New commands for export all the way to PDF (through LaTeX)
1132 - Some bug fixed for LaTeX export, more bugs remain.
1136 *** Enhancements to secondary agenda filtering
1138 This is, I believe, becoming a killer feature. It allows you
1139 to define fewer and more general custom agenda commands, and
1140 then to do the final narrowing to specific tasks you are
1141 looking for very quickly, much faster than calling a new
1144 If you have not tries this yet, you should!
1146 **** You can now refining the current filter by an additional criterion
1147 When filtering an existing agenda view with =/=, you can
1148 now narrow down the existing selection by an additional
1149 condition. Do do this, use =\= instead of =/= to add the
1150 additional criterion. You can also press =+= or =-= after
1151 =/= to add a positive or negative condition. A condition
1152 can be a TAG, or an effort estimate limit, see below.
1154 **** It is now possible to filter for effort estimates
1155 This means to filter the agenda for the value of the Effort
1156 property. For this you should best set up global allowed
1157 values for effort estimates, with
1159 #+begin_src emacs-lisp
1160 (setq org-global-properties
1161 '(("Effort_ALL" . "0 0:10 0:30 1:00 2:00 3:00 4:00")))
1164 You may then select effort limits with single keys in the
1165 filter. It works like this: After =/= or =\=, first select
1166 the operator which you want to use to compare effort
1169 : < Select entries with effort smaller than or equal to the limit
1170 : > Select entries with effort larger than or equal to the limit
1171 : = Select entries with effort equal to the limit
1173 After that, you can press a single digit number which is
1174 used as an index to the allowed effort estimates.
1176 If you do not use digits to fast-select tags, you can even
1177 skip the operator, which will then default to
1178 `org-agenda-filter-effort-default-operator', which is by
1181 Thanks to Manish for the great idea to include fast effort
1182 filtering into the agenda filtering process.
1184 **** The mode line will show the active filter
1185 For example, if there is a filter in place that does select
1186 for HOME tags, against EMAIL tags, and for tasks with an
1187 estimated effort smaller than 30 minutes, the mode-line with
1188 show =+HOME-EMAIL+<0:30=
1190 **** The filter now persists when the agenda view is refreshed
1191 All normal refresh commands, including those that move the
1192 weekly agenda from one week to the next, now keep the
1193 current filter in place.
1195 You need to press =/ /= to turn off the filter. However,
1196 when you run a new agenda command, for example going from
1197 the weekly agenda to the TODO list, the filter will be
1200 *** Setting tags has now its own binding, =C-c C-q=
1202 You can still use =C-c C-c= on a headline, but the new
1203 binding should be considered as the main binding for this
1204 command. The reasons for this change are:
1206 - Using =C-c C-c= for tags is really out of line with other
1209 - I hate it in Remember buffers when I try to set tags and I
1210 cannot, because =C-c C-c= exits the buffer :-(
1212 - =C-c C-q= will also work when the cursor is somewhere down
1213 in the entry, it does not have to be on the headline.
1215 *** Todo state changes can trigger tag changes
1217 The new option =org-todo-state-tags-triggers= can be used to
1218 define automatic changes to tags when a TODO state changes.
1219 For example, the setting
1221 : (setq org-todo-state-tags-triggers
1222 : '((done ("Today" . nil) ("NEXT" . nil))
1223 : ("WAITING" ("Today" . t))))
1225 will make sure that any change to any of the DONE states will
1226 remove tags "Today" and "NEXT", while switching to the
1227 "WAITING" state will trigger the tag "Today" to be added.
1229 I use this mostly to get rid of TODAY and NEXT tags which I
1230 apply to select an entry for execution in the near future,
1231 which I often prefer to specific time scheduling.
1233 *** C-RET will now always insert a new headline, never an item.
1234 The new headline is inserted after the current subtree.
1236 Thanks to Peter Jones for patches to fine-tune this behavior.
1238 *** Customize org-mouse.el feature set
1239 There is a new variable =org-mouse-features= which gives you
1240 some control about what features of org-mouse you want to
1241 use. Turning off some of the feature will free up the
1242 corresponding mouse events, or will avoid activating special
1243 regions for mouse clicks. By default I have urned off the
1244 feature to use drag mouse events to move or promote/demote
1245 entries. You can of course turn them back on if you wish.
1247 This variable may still change in the future, allowing more
1248 fine-grained control.
1250 *** New commands for export to PDF
1252 This is using LaTeX export, and then processes it to PDF
1255 : C-c C-e p process to PDF.
1256 : C-c C-e d process to PDF, and open the file.
1259 - \usepackage{graphicx} is now part of the standard class
1261 - Several bugs fixed, but definitely not all of them :-(
1263 *** New option `org-log-state-notes-insert-after-drawers'
1265 Set this to =t= if you want state change notes to be inserted
1266 after any initial drawers, i.e drawers the immediately follow
1267 the headline and the planning line (the one with
1268 DEADLINE/SCHEDULED/CLOSED information).
1272 *** =org-file-apps= now uses regular expressions, see [[*%20org%20file%20apps%20now%20uses%20regular%20repressions%20instead%20of%20extensions][below]]
1276 *** =org-file-apps= now uses regular repressions instead of extensions
1277 Just like in =auto-mode-alist=, car's in the variable
1278 =org-file-apps= that are strings are now interpreted as
1279 regular expressions that are matched against a file name. So
1280 instead of "txt", you should now write "\\.txt\\'" to make
1281 sure the matching is done correctly (even though "txt" will
1282 be recognized and still be interpreted as an extension).
1284 There is now a shortcut to get many file types visited by
1285 Emacs. If org-file-apps contains `(auto-mode . emacs)', then
1286 any files that are matched by `auto-mode-alist' will be
1289 *** Changes to the attachment system
1291 - The default method to attach a file is now to copy it
1292 instead of moving it.
1293 - You can modify the default method using the variable
1294 `org-attach-method'. I believe that most Unix people want
1295 to set it to `ln' to create hard links.
1296 - The keys =c=, =m=, and =l= specifically select =copy=,
1297 =move=, or =link=, respectively, as the attachment method
1298 for a file, overruling `org-attach-method'.
1299 - To create a new attachment as an Emacs buffer, you have not
1300 now use =n= instead of =c=.
1301 - The file list is now always retrieved from the directory
1302 itself, not from the "Attachments" property. We still
1303 keep this property by default, but you can turn it off, by
1304 customizing the variable =org-attach-file-list-property=.
1308 ** Incompatible changes
1310 - Changes in the structure of IDs, see [[*The%20default%20structure%20of%20IDs%20has%20changed][here]] for details.
1312 - C-c C-a has been redefined, see [[*%20C%20c%20C%20a%20no%20longer%20calls%20show%20all][here]] for details.
1316 *** The default structure of IDs has changed
1318 IDs created by Org have changed a bit:
1319 - By default, there is no prefix on the ID. There used to be
1320 an "Org" prefix, but I now think this is not necessary.
1321 - IDs use only lower-case letters, no upper-case letters
1322 anymore. The reason for this is that IDs are now also used
1323 as directory names for org-attach, and some systems do not
1324 distinguish upper and lower case in the file system.
1325 - The ID string derived from the current time is now
1326 /reversed/ to become an ID. This assures that the first
1327 two letters of the ID change fast, so hat it makes sense to
1328 split them off to create subdirectories to balance load.
1329 - You can now set the `org-id-method' to `uuidgen' on systems
1332 *** =C-c C-a= no longer calls `show-all'
1334 The reason for this is that =C-c C-a= is now used for the
1335 attachment system. On the rare occasions that this command
1336 is needed, use =M-x show-all=, or =C-u C-u C-u TAB=.
1338 *** New attachment system
1340 You can now attach files to each node in the outline tree.
1341 This works by creating special directories based on the ID of
1342 an entry, and storing files in these directories. Org can
1343 keep track of changes to the attachments by automatically
1344 committing changes to git. See the manual for more
1347 Thanks to John Wiegley who contributed this fantastic new
1348 concept and wrote org-attach.el to implement it.
1350 *** New remember template escapes
1352 : %^{prop}p to insert a property
1353 : %k the heading of the item currently being clocked
1354 : %K a link to the heading of the item currently being clocked
1356 Also, when you exit remember with =C-2 C-c C-c=, the item
1357 will be filed as a child of the item currently being
1358 clocked. So the idea is, if you are working on something and
1359 think of a new task related to this or a new note to be
1360 added, you can use this to quickly add information to that
1363 Thanks to James TD Smith for a patch to this effect.
1365 *** Clicking with mouse-2 on clock info in mode-line visits the clock.
1367 Thanks to James TD Smith for a patch to this effect.
1369 *** New file in contrib: lisp/org-checklist.el
1371 This module deals with repeated tasks that have checkbox
1374 Thanks to James TD Smith for this contribution.
1376 *** New in-buffer setting #+STYLE
1378 It can be used to locally set the variable
1379 `org-export-html-style-extra'. Several such lines are
1380 allowed-, they will all be concatenated. For an example on
1381 how to use it, see the [[http://orgmode.org/worg/org-tutorials/org-publish-html-tutorial.php][publishing tutorial]].
1387 - Filtering existing agenda views with respect to a tag
1388 - Editing fixed-width regions with picture or artist mode
1389 - /org-plot.el/ is now part of Org
1390 - Tags can be used to select the export part of a document
1391 - Prefix interpretation when storing remember notes
1392 - Yanking inserts folded subtrees
1393 - Column view capture tables can have formulas, plotting info
1394 - In column view, date stamps can be changed with S-cursor keys
1395 - The note buffer for clocking out now mentions the task
1396 - Sorting entries alphabetically ignores TODO keyword and priority
1397 - Agenda views can sort entries by TODO state
1398 - New face =org-scheduled= for entries scheduled in the future.
1399 - Remember templates for gnus links can use the :to escape.
1400 - The file specification in a remember template may be a function
1401 - Categories in iCalendar export include local tags
1402 - It is possible to define filters for column view
1403 - Disabling integer increment during table Field copy
1404 - Capturing column view is on `C-c C-x i'
1405 - And tons of bugs fixed.
1408 ** Incompatible changes
1410 *** Prefix interpretation when storing remember notes has changed
1412 The prefix argument to the `C-c C-c' command that finishes a
1413 remember process is now interpreted differently:
1415 : C-c C-c Store the note to predefined file and headline
1416 : C-u C-c C-c Like C-c C-c, but immediately visit the note
1417 : in its new location.
1418 : C-1 C-c C-c Select the storage location interactively
1419 : C-0 C-c C-c Re-use the last used location
1421 This was requested by John Wiegley.
1423 *** Capturing column view is now on `C-c C-x i'
1425 The reason for this change was that `C-c C-x r' is also used
1426 as a tty key replacement.
1428 *** Categories in iCalendar export now include local tags
1430 The locally defined tags are now listed as categories when
1431 exporting to iCalendar format. Org's traditional file/tree
1432 category is now the last category in this list. Configure
1433 the variable =org-icalendar-categories= to modify or revert
1436 This was a request by Charles Philip Chan.
1440 *** Secondary filtering of agenda views.
1442 You can now easily and interactively filter an existing
1443 agenda view with respect to a tag. This command is executed
1444 with the =/= key in the agenda. You will be prompted for a
1445 tag selection key, and all entries that do not contain or
1446 inherit the corresponding tag will be hidden. With a prefix
1447 argument, the opposite filter is applied: entries that
1448 do have the tag will be hidden.
1450 This operation only /hides/ lines in the agenda buffer, it
1451 does not remove them. Changing the secondary filtering does
1452 not require a new search and is very fast.
1454 If you press TAB at the tag selection prompt, you will be
1455 switched to a completion interface to select a tag. This is
1456 useful when you want to select a tag that does not have a
1457 direct access character.
1459 A double =/ /= will restore the original agenda view by
1460 unhiding any hidden lines.
1462 This functionality was John Wiegley's idea. It is a simpler
1463 implementation of some of the query-editing features proposed
1464 and implemented some time ago by Christopher League (see the
1465 file contrib/lisp/org-interactive-query.el).
1467 *** Editing fixed-width regions with picture or artist mode
1469 The command @<code>C-c '@</code> (that is =C-c= followed by a
1470 single quote) can now also be used to switch to a special
1471 editing mode for fixed-width sections. The default mode is
1472 =artist-mode= which allows you to create ASCII drawings.
1474 It works like this: Enter the editing mode with
1475 @<code>C-c '@</code>. An indirect buffer will be created and
1476 narrowed to the fixed-width region. Edit the drawing, and
1477 press @<code>C-c '@</code> again to exit.
1479 Lines in a fixed-width region should be preceded by a colon
1480 followed by at least one space. These will be removed during
1481 editing, and then added back when you exit the editing mode.
1483 Using the command in an empty line will create a new
1486 This new feature arose from a discussion involving Scott
1487 Otterson, Sebastian Rose and Will Henney.
1489 *** /org-plot.el/ is now part of Org.
1491 You can run it by simple calling org-plot/gnuplot.
1492 Documentation is not yet included with Org, please refer to
1493 http://github.com/eschulte/org-plot/tree/master until we have
1494 moved the docs into Org or Worg.
1496 Thanks to Eric Schulte for this great contribution.
1498 *** Tags can be used to select the export part of a document
1500 You may now use tags to select parts of a document for
1501 inclusion into the export, and to exclude other parts. This
1502 behavior is governed by two new variables:
1503 =org-export-select-tags= and =org-export-exclude-tags=.
1504 These default to =("export")= and =("noexport")=, but can be
1505 changed, even to include a list of several tags.
1507 Org first checks if any of the /select/ tags is present in
1508 the buffer. If yes, all trees that do not carry one of these
1509 tags will be excluded. If a selected tree is a subtree, the
1510 heading hierarchy above it will also be selected for export,
1511 but not the text below those headings. If none of the select
1512 tags is found anywhere in the buffer, the whole buffer will
1513 be selected for export. Finally, all subtrees that are
1514 marked by any of the /exclude/ tags will be removed from the
1517 You may set these tags with in-buffer options
1518 =EXPORT_SELECT_TAGS= and =EXPORT_EXCLUDE_TAGS=.
1520 I love this feature. Thanks to Richard G Riley for coming
1523 *** Prefix interpretation when storing remember notes
1525 The prefix argument to the `C-c C-c' command that finishes a
1526 remember process is now interpreted differently:
1528 : C-c C-c Store the note to predefined file and headline
1529 : C-u C-c C-c Like C-c C-c, but immediately visit the note
1530 : in its new location.
1531 : C-1 C-c C-c Select the storage location interactively
1532 : C-0 C-c C-c Re-use the last used location
1534 This was requested by John Wiegley.
1536 *** Yanking inserts folded subtrees
1538 If the kill is a subtree or a sequence of subtrees, yanking
1539 them with =C-y= will leave all the subtrees in a folded
1540 state. This basically means, that kill and yank are now
1541 much more useful in moving stuff around in your outline. If
1542 you do not like this, customize the variable
1543 =org-yank-folded-subtrees=.
1545 Right now, I am only binding =C-y= to this new function,
1546 should I modify all bindings of yank? Do we need to amend
1549 This feature was requested by John Wiegley.
1551 *** Column view capture tables can have formulas, plotting info
1553 If you attach formulas and plotting instructions to a table
1554 capturing column view, these extra lines will now survive an
1555 update of the column view capture, and any formulas will be
1556 re-applied to the captured table. This works by keeping any
1557 continuous block of comments before and after the actual
1560 *** In column view, date stamps can be changed with S-cursor keys
1562 If a property value is a time stamp, S-left and S-right can
1563 now be used to shift this date around while in column view.
1565 This was a request by Chris Randle.
1567 *** The note buffer for clocking out now mentions the task
1569 This was a request by Peter Frings.
1571 *** Sorting entries alphabetically ignores TODO keyword and priority
1573 Numerical and alphanumerical sorting now skips any TODO
1574 keyword or priority cookie when constructing the comparison
1575 string. This was a request by Wanrong Lin.
1577 *** Agenda views can sort entries by TODO state
1579 You can now define a sorting strategy for agenda entries that
1580 does look at the TODO state of the entries. Sorting by TODO
1581 entry does first separate the non-done from the done states.
1582 Within each class, the entries are sorted not alphabetically,
1583 but in definition order. So if you have a sequence of TODO
1584 entries defined, the entries will be sorted according to the
1585 position of the keyword in this sequence.
1587 This follows an idea and sample implementation by Christian
1590 *** New face =org-scheduled= for entries scheduled in the future.
1592 This was a request by Richard G Riley.
1594 *** Remember templates for gnus links can now use the :to escape.
1596 Thanks to Tommy Lindgren for a patch to this effect.
1597 *** The file specification in a remember template may now be a function
1599 Thanks to Gregory Sullivan for a patch to this effect.
1601 *** Categories in iCalendar export now include local tags
1603 The locally defined tags are now listed as categories when
1604 exporting to iCalendar format. Org's traditional file/tree
1605 category is now the last category in this list. Configure
1606 the variable =org-icalendar-categories= to modify or revert
1609 This was a request by Charles Philip Chan.
1611 *** It is now possible to define filters for column view
1613 The filter can modify the value that will be displayed in a
1614 column, for example it can cut out a part of a time stamp.
1615 For more information, look at the variable
1616 =org-columns-modify-value-for-display-function=.
1618 *** Disabling integer increment during table field copy
1620 Prefix arg 0 to S-RET does the trick.
1622 This was a request by Chris Randle.
1627 For older Changes, see [[file:Changes_old.org]]