Org mode for Emacs – Old Release notes

From now on, Org expects at least Emacs 24.3, although Emacs 24.4 or above is suggested.

Incomplete compatibility layer with XEmacs has been removed. If you want to take over maintainance of this compatibility, please contact our mailing list.

Export blocks are explicitly marked as such at the syntax level to disambiguate their parsing from special blocks. The new syntax is

#+BEGIN_EXPORT backend
...
#+END_EXPORT

instead of

#+BEGIN_backend
...
#+END_backend

As a consequence, INCLUDE keywords syntax is modified, e.g.,

#+INCLUDE: "file.org" HTML

becomes

#+INCLUDE: "file.org" export html

The following function repairs export blocks and INCLUDE keywords using previous syntax:

(defun org-repair-export-blocks ()
  "Repair export blocks and INCLUDE keywords in current buffer."
  (interactive)
  (when (eq major-mode 'org-mode)
    (let ((case-fold-search t)
          (back-end-re (regexp-opt
                        '("HTML" "ASCII" "LATEX" "ODT" "MARKDOWN" "MD" "ORG"
                          "MAN" "BEAMER" "TEXINFO" "GROFF" "KOMA-LETTER")
                        t)))
      (org-with-wide-buffer
       (goto-char (point-min))
       (let ((block-re (concat "^[ \t]*#\\+BEGIN_" back-end-re)))
         (save-excursion
           (while (re-search-forward block-re nil t)
             (let ((element (save-match-data (org-element-at-point))))
               (when (eq (org-element-type element) 'special-block)
                 (save-excursion
                   (goto-char (org-element-property :end element))
                   (save-match-data (search-backward "_"))
                   (forward-char)
                   (insert "EXPORT")
                   (delete-region (point) (line-end-position)))
                 (replace-match "EXPORT \\1" nil nil nil 1))))))
       (let ((include-re
              (format "^[ \t]*#\\+INCLUDE: .*?%s[ \t]*$" back-end-re)))
         (while (re-search-forward include-re nil t)
           (let ((element (save-match-data (org-element-at-point))))
             (when (and (eq (org-element-type element) 'keyword)
                        (string= (org-element-property :key element) "INCLUDE"))
               (replace-match "EXPORT \\1" nil nil nil 1)))))))))

Moreover, :export-block keyword used in org-export-define-backend and org-export-define-derived-backend is no longer used and needs to be removed.

The variable now accepts functions of two arguments instead of plain S-expressions. Replacing a S-expresion with an appropriate function is straightforward. For example

("pdf" . (foo))

becomes

("pdf" . (lambda (file link) (foo)))

The modification time will be determined via vc.el if the second argument is non-nil. See the manual for details.

Preparation and completion functions are now called with an argument, which is the project property list. It used to be dynamically scoped through the project-plist variable.

Using header arguments as property names is no longer possible. As such, the following

* Headline
:PROPERTIES:
:exports: code
:var: a=1 b=2
:var+: c=3
:END:

should be written instead

* Headline
:PROPERTIES:
:header-args: :exports code
:header-args: :var a=1 b=2
:header-args+: :var c=3
:END:

Please note that, however, old properties were defined at the source block definition. Current ones are defined where the block is called.

Org-protocol can now handle query-style parameters such as:

org-protocol://store-link?url=http:%2F%2Flocalhost%2Findex.html&title=The%20title
org-protocol://capture?template=x&title=Hello&body=World&url=http:%2F%2Fexample.com

Old-style links such as

org-protocol://store-link:/http:%2F%2Flocalhost%2Findex.html/The%20title

continue to be supported.

If you have defined your own handler functions for org-protocol-protocol-alist, change them to accept either a property list (for new-style links) or a string (for old-style links). Use org-protocol-parse-parameters to convert old-style links into property lists.

org-lint can check syntax and report common issues in Org documents.

When org-agenda-insert-diary-strategy is set to date-tree-last, diary entries are added to last in the date tree.

\vbar or \vbar{} will be exported unconditionnally as a |, unlike to existing \vert, which is expanded as | when using a HTML derived export back-end.

Radio lists, i.e, Org plain lists in foreign buffers, have been rewritten to be on par with Radio tables. You can use a large set of parameters to control how a given list should be rendered. See manual for details.

Used like org-bbdb-anniversaries, it provides a few days warning for upcoming anniversaries (default: 7 days).

If the task is repeated, and therefore done at least one, scheduling information is no longer relevant. It is therefore removed.

See commit message for more information.

ISO week trees are an alternative date tree format that orders entries by ISO week and not by month.

For example:

* 2015
** 2015-W35
** 2015-W36
*** 2015-08-31 Monday

They are supported in org-capture via file+weektree and file+weektree+prompt target specifications.

When defining a "columnview" dynamic block, it is now possible to add an :indent parameter, much like the one in the clock table.

On the other hand, stars no longer appear in an ITEM field.

When non-nil, commit attachments with git, assuming the document is in a git repository.

When set to smart, the new variable org-occur-case-fold-search allows to mimic isearch.el: if the regexp searched contains any upper case character (or character class), the search is case sensitive. Otherwise, it is case insensitive.

Repeated footnotes are now numbered by referring to a label in the first footnote.

This works also when org-src-fontify-natively is non-nil. It is also possible to specify per-languages faces. See org-src-block-faces and the manual for details.

Links can now have custom colors, tooltips, keymaps, display behavior, etc. Links are now centralized in org-link-parameters.

It replaces the deprecated next argument to org-previous-line-empty-p.

It is a faster implementation of outline-show-children.

Use org-agenda-filter-by-tag instead.

Use org-agenda-today-p instead.

Use org-babel--get-vars or assq instead, as applicable.

Use org-trim instead.

Use org-remove-indentation instead.

Use image-file-name-regexp instead. The never-used-in-core extensions argument has been dropped.

Use org-list-to-lisp instead.

A comment to this effect was in the source code since 7.8.03, but now a byte-compiler warning will be generated as well.

Use org-at-table-p instead.

It was not called by any org code since 2010.

The affected functions are:

• org-count
• org-remove-if
• org-remove-if-not
• org-reduce
• org-every
• org-some

Additionally, org-sublist is deprecated in favor of cl-subseq. Note the differences in indexing conventions: org-sublist is 1-based and end-inclusive; cl-subseq is 0-based and end-exclusive.

This includes org-completion-use-iswitchb and org-completion-use-ido. Instead Org uses regular functions, e.g., completion-read so as to let those libraries operate.

Two consecutive blank lines always terminate all levels of current plain list.

fixltx2e is obsolete, see LaTeX News 22.

It is now allowed to write, e.g., [[http:orgmode.org][<file:unicorn.png>]] as an equivalent to [[http:orgmode.org][file:unicorn.png]]. The advantage of the former is that spaces are allowed within the path.

Functions in this list are called before any file is associated to the current projet. Thus, they can be used to generate to be published Org files.

The new algorithm doesn't remove TAB characters not used for indentation.

Placeholders in capture templates are no longer expanded recursively. However, %(...) constructs are expanded very late, so you can fill the contents of the S-exp with the replacement text of non-interactive placeholders. As before, interactive ones are still expanded as the very last step, so the previous statement doesn't apply to them.

Note that only %(...) placeholders initially present in the template, or introduced using a file placeholder, i.e., %[...] are expanded. This prevents evaluating potentially malicious code when another placeholder, e.g., %i expands to a S-exp.

Since gnus nnir groups are temporary, org-gnus-store-link now refers to the article's original group.

The calling convention has changed.

Variable org-html-table-row-tags has been split into org-html-table-row-open-tag and org-html-table-row-close-tag. Both new variables can be either a string or a function which will be called with 6 parameters.

The previous name is, for the time being, kept as an obsolete alias.

When setting a new optional argument to a non-nil value, org-trim preserves leading indentation while removing blank lines at the beginning of the string. The behavior is identical for white space at the end of the string.

HTML links created from certain info links now point to gnu.org URL's rather than just to local files. For example info links such as info:emacs#List Buffers used to be converted to HTML links like this:

<a href="emacs.html#List-Buffers">emacs#List Buffers</a>

where local file emacs.html is referenced. For most folks this file does not exist. Thus the new behavior is to generate this HTML link instead:

<a href="http://www.gnu.org/software/emacs/manual/html_mono/emacs.html#List-Buffers">emacs#List Buffers</a>

All emacs related info links are similarly translated plus few other gnu.org manuals.

Previously, if a recurring task had a timestamp of <2016-01-01 Fri 20:00 ++1d> and was completed on 2016-01-02 at 08:00, the task would skip 2016-01-02 and would be rescheduled for 2016-01-03. Timestamps with ++ cookies and a specific time will now shift to the first possible future occurrence, even if the occurrence is later the same day the task is completed. (Timestamps already in the future are still shifted one time further into the future.)

It used to be a defcustom, with a warning that it shouldn't be modified anyway.

They are still supported in Org 9.0 but will eventually be removed in a later release. Use file link type along with universal arguments to force opening it in either Emacs or with system application.

Allows J source blocks be indicated by letter j. Previously the indication letter was solely J.

When org-special-ctrl-o is non-nil, it is impractical to create a blank line above a table at the beginning of the document. Now, as a special case, org-open-line behaves normally in this situation.

The experimental variable used to be more or less confidential, as a defvar.

It defines the format of the original link. Possible values are: plain, bracket and angle.

Properties drawers are now required to be located right after a headline and its planning line, when applicable.

It will break some documents as TODO states changes were sometimes logged before the property drawer.

The following function will repair them:

(defun org-repair-property-drawers ()
  "Fix properties drawers in current buffer.
 Ignore non Org buffers."
  (when (eq major-mode 'org-mode)
    (org-with-wide-buffer
     (goto-char (point-min))
     (let ((case-fold-search t)
           (inline-re (and (featurep 'org-inlinetask)
                           (concat (org-inlinetask-outline-regexp)
                                   "END[ \t]*$"))))
       (org-map-entries
        (lambda ()
          (unless (and inline-re (org-looking-at-p inline-re))
            (save-excursion
              (let ((end (save-excursion (outline-next-heading) (point))))
                (forward-line)
                (when (org-looking-at-p org-planning-line-re) (forward-line))
                (when (and (< (point) end)
                           (not (org-looking-at-p org-property-drawer-re))
                           (save-excursion
                             (and (re-search-forward org-property-drawer-re end t)
                                  (eq (org-element-type
                                       (save-match-data (org-element-at-point)))
                                      'drawer))))
                  (insert (delete-and-extract-region
                           (match-beginning 0)
                           (min (1+ (match-end 0)) end)))
                  (unless (bolp) (insert "\n"))))))))))))

It was possible to use several such keywords and have them apply to the text below until the next one, but strongly deprecated since Org 5.14 (2008).

#+CATEGORY keywords are now global to the document. You can use node properties to set category for a subtree, e.g.,

* Headline
   :PROPERTIES:
   :CATEGORY: some category
   :END:

org-show-following-heading, org-show-siblings, org-show-entry-below and org-show-hierarchy-above no longer exist. Instead, visibility is controlled through a single variable: org-show-context-detail, which see.

org-replace-disputed-keys has been ignored when reading date since version 8.1, but the former behavior is restored again.

Keybinding for reading date can be customized with a new variable org-read-date-minibuffer-local-map.

Skipping TITLE keyword no longer provides the current file name, or buffer name, as the title. Instead, simply ignore the title.

The following functions require an additional argument. See their docstring for more information.

• org-export-collect-footnote-definitions
• org-html-format-headline-function
• org-html-format-inlinetask-function
• org-latex-format-headline-function
• org-latex-format-inlinetask-function
• org-link-search

The key sequences C-c C-n and C-c C-p are now bound to org-next-visible-heading and org-next-visible-heading respectively, rather than the outline-mode versions of these functions. The Org version of these functions skips over inline tasks (and even-level headlines when org-odd-levels-only is set).

org-element-context used to return objects on some keywords, i.e., TITLE, DATE and AUTHOR. It now returns only the keyword.

If point is before or after the headline title, insert a new line without changing the headline.

If you have, in your configuration, something like (setq org-timer-default-timer 10) replace it with (setq org-timer-default-timer "10").

The functionality of nesting tags in hierarchies is added to org-mode. This is the generalization of what was previously called "Tag groups" in the manual. That term is now changed to "Tag hierarchy".

The following in-buffer definition:

#+TAGS: [ Group : SubOne SubTwo ]
#+TAGS: [ SubOne : SubOne1 SubOne2 ]
#+TAGS: [ SubTwo : SubTwo1 SubTwo2 ]

Should be seen as the following tree of tags:

• Group
  • SubOne
    • SubOne1
    • SubOne2
  • SubTwo
    • SubTwo1
    • SubTwo2

Searching for "Group" should return all tags defined above. Filtering on SubOne filters also it's sub-tags. Etc.

There is no limit on the depth for the tag hierarchy.

Additional syntax is defined for grouptags if the tags in the group don't have to be distinct on a heading.

Grouptags had to previously be defined with { }. This syntax is already used for exclusive tags and Grouptags need their own, non-exclusive syntax. This behaviour is achieved with [ ]. Note: { } can still be used also for Grouptags but then only one of the given tags can be used on the headline at the same time. Example:

[ group : sub1 sub2 ]

* Test                                                            :sub1:sub2:

This is a more general case than the already existing syntax for grouptags; { }.

Tags can be defined as grouptags with regular expressions as "sub-tags".

The regular expressions in the group must be marked up within { }. Example use:

#+TAGS: [ Project : {P@.+} ]

Searching for the tag Project will now list all tags also including regular expression matches for P@.+. Good for example if tags for a certain project is tagged with a common project-identifier, i.e. P@2014_OrgTags.

Filtering in the agenda on grouptags filter all of the related tags. Exception if filter is applied with a (double) prefix-argument.

Filtering in the agenda on subcategories does not filter the "above" levels anymore.

If a grouptag contains a regular expression the regular expression is also used as a filter.

Now uses the argument arg and optional argument exclude instead of strip and narrow. ARG because the argument has multiple purposes and makes more sense than strip now. The term narrowing is changed to exclude.

The main purpose is for the function to make more logical sense when filtering on tags now when tags can be structured in hierarchies.

Thanks to Bjarte Johansen for this feature.

New ob-processing.el library.

This library implements necessary functions for implementing editing of Processing code blocks, viewing the resulting sketches in an external viewer, and HTML export of the sketches.

Check the documentation for more.

Thanks to Jarmo Hurri for this feature.

The new behaviour is the following:

• With a double prefix argument or with a single prefix argument when point is before the first headline, toggle overlays in the whole buffer;
• With a single prefix argument, toggle overlays in the current subtree;
• On latex code, toggle overlay at point;
• Otherwise, toggle overlays in the current section.

The content of the included file can now be optionally marked up, for instance as HTML. See the documentation for details.

Objects can be extracted via #+INCLUDE using file links. It is possible to include only the contents of the object. See manual for more information.

One can use a drawer without listing it in the #+DRAWERS keyword, which is now obsolete. As a consequence, this change also deprecates org-drawers variable.

Using C-c ' on an export block now opens a sub-editing buffer. Major mode in that buffer is determined by export backend name (e.g., "latex" → "latex-mode"). You can define exceptions to this rule by configuring org-src-lang-modes, which see.

If the argument :hlines yes is present in a babel call, an optional argument :hlines-string can be used to define a string to use as a representation for the lisp symbol 'hline in the shell program. The default is hline.

For example, it is now possible to number lines using the -n switch in a source block.

Plain lists can have an extra margin by setting org-ascii-list-margin variable to an appopriate integer.

ASCII export now supports #+BEGIN_JUSTIFYRIGHT and #+BEGIN_JUSTIFYLEFT blocks. See documentation for details.

The number of publishing options specific to each back-end has been increased. See manual for details.

Inline source code was used to be removed upon exporting. They are now handled as standard code blocks, i.e., the source code can appear in the output, depending on the parameters.

These functions now support any element or object, not only headlines.

This function deprecates org-export-get-genealogy. It also provides more features. See docstring for details.

Functions in this filter are applied on the body of the exported document, befor wrapping it within the template.

Radio tables feature now relies on Org's export framework ("ox.el"). :no-escape parameter no longer exists, but additional global parameters are now supported: :raw, :backend. Moreover, there are new parameters specific to some pre-defined translators, e.g., :environment and :booktabs for orgtbl-to-latex. See translators docstrings (including orgtbl-to-generic) for details.

It is not possible to specify #+attr_latex: :float nil in conjunction with source blocks exported by the minted package.

Previously, evaluating formulas that referenced out-of-bounds columns would throw an error. A new variable org-table-formula-create-columns was added to adjust this behavior. It is now possible to silently add new columns, to do so with a warning or to explicitly ask the user each time.

Ability to plot values in a column through ASCII-art bars. See manual for details.

This hook is called after successfully archiving a subtree, with point on the original subtree, not yet deleted.

When non-nil, attachments from archived subtrees are removed.

This variable generalizes org-latex-table-caption-above, which is now deprecated. In addition to tables, it applies to source blocks, special blocks and images. See docstring for more information.

See docstring for more information.

Headlines, for which the property UNNUMBERED is non-nil, are now exported without section numbers irrespective of their levels. The property is inherited by children.

It is now possible to specify a function, both programatically, through a new optional argument, and interactively with f or F keys, to sort a table.

The TOC keywords now accepts an optional local parameter. See manual for details.

org-timer-pause-time now pauses and restarts both relative and countdown timers.

When org-agenda-window-setup is set to only-window, the agenda is displayed as the sole window of the current frame.

It is now possible to supply and optional formatting argument to {{{date}}}. See manual for details.

It is now possible to supply an optional search option to {{{property}}} in order to retrieve remote properties optional. See manual for details.

It is possible to suppress the title insertion with #+OPTIONS: title:nil or globally using the variable org-export-with-title.

" " are used to insert up to 20 contiguous spaces in various back-ends. In particular, this family can be used to introduce leading spaces within table cells.

Org uses the MathJax CDN by default. See the manual and the docstring of org-html-mathjax-options for details.

When defining a back-end, it is now possible to specify to give `parse' behaviour on a keyword. It is equivalent to call `org-element-parse-secondary-string' on the value.

However, parsed KEYWORD is automatically associated to an :EXPORT_KEYWORD: property, which can be used to override the keyword value during a subtree export. Moreover, macros are expanded in such keywords and properties.

Viewport for mobile-optimized website is now automatically inserted when exporting to html. See org-html-viewport for details.

Org can typeset a subtitle in some export backends. See the manual for details.

Calling org-edit-footnote-reference (C-c ') on a footnote reference allows to edit its definition, as long as it is not anonymous, in a dedicated buffer. It works even if buffer is currently narrowed.

Work as delete-indentation unless at heading, in which case text is added to headline text.

Texinfo back-end now handles images. See manual for details.

Tables and source blocks can now have captions. Additionally, lists of tables and lists of listings can be inserted in the document with #+TOC keyword.

In addition to setting countdown timers in minutes, they can also be set using the hh:mm:ss format.

org-clone-subtree-with-time-shift now accepts 0 as an argument for the number of clones, which removes the repeater from the original subtree and creates one shifted, repeating clone.

It encompasses all past closed clocks.

See the docstring of org-latex-classes and org-latex-guess-polyglossia-language for details.

Use org-timestamp-translate instead.

This function inserted a Beamer specific template at point or in current subtree. Use org-export-insert-default-template instead, as it provides more features and covers all export back-ends. It is also accessible from the export dispatcher.

org-timer-stop now stops both relative and countdown timers.

This function, being non-bijective, introduced bug in internal references. Use org-export-get-reference instead.

The function is superseded by org-end-of-meta-data, called with an optional argument.

These functions were left-over from pre 8.0 era. They are not correct anymore. Since they are not needed, they have no replacement.

It will be kept in code base until next release, for backward compatibility.

If you need to separate consecutive lists with blank lines, always use two of them, as if this option was nil (default value).

Special comment value is no longer allowed. It is possible to use a body filter to add comments about the creator at the end of the document instead.

This undocumented option defaulted to the value of shell-file-name at the time of loading ob-shell. The new behaviour is to use the value of shell-file-name directly when the shell langage is shell. To chose a different shell, either customize shell-file-name or bind this variable locally.

This undocumented option was supposed to provide different quoting styles when changing the shell type. Changing the shell type can now be done directly from the source block and the quoting style has to be compatible across all shells, so a customization doesn't make sense anymore. The chosen hard coded quoting style conforms to POSIX.

Setting this option to anything else that the default value (nil) would create invalid planning info. This dangerous option is now removed.

Use org-export-with-title instead. See also below.

This variable has no effect since Org 8.0.

This variable has no effect since August 2009.

MathJax automatically chooses the best display technology based on the end-users browser. You may force initial usage of MathML via org-html-mathjax-template or by setting the path property of org-html-mathjax-options.

org-export-filter-comment-functions and org-export-filter-comment-block-functions variables do not exist anymore.

ITEM special property does not contain TODO, priority or tags anymore.

Absolute file names can now start with /// in addition to /. E.g., [[file:///home/me/unicorn.jpg]].

As a consequence, it is possible to include multiple Org files with footnotes in a master document without being concerned about footnote labels colliding.

This change deprecates old Org syntax for mailto links: mailto:user@domain::Subject.

QUOTE keywords have been deprecated since Org 8.2.

The build system has been enhanced to allow test selection with a regular expression by defining BTEST_RE during the test invocation. This is especially useful during bisection to find just when a particular test failure was introduced.

Exact heading search for links now ignore spaces and cookies. This is the case for links of the form file:projects.org::*task title, as well as links of the form file:projects.org::some words when org-link-search-must-match-exact-headline is not nil.

New formatting keys are supported. See the respective docstrings. Note, org-latex-hyperref-template has a new default value.

If you require any of these package add them to your preamble via org-latex-packages-alist. Org also uses default LaTeX \tolerance now.

This helps spotting wrong links.

This did not work properly in some environments as xdg-open is desktop specific.

You can now have searches like SOMEPROP="aaa/bbb". Until now, this would break because the slash would be interpreted as the separator starting a TOTO match string.

• rotating is now a default package, to support sideways tables.
• amsmath is a default package
• eucal package removed, no longer needed since amsmath is present

Furthermore, the manual now specifically notes if an additional package is needed for one of the documented attributes.

Thanks to Marc McLean for this patch.

When following a link that has an id: prefix, org-id.el will now automatically be loaded.

Thanks to Oleh for this patch

The commands C-down and C-up now invoke special commands that use knowledge from the org-elements parser to move the cursor in a paragraph-like way.

Thanks to Nicolas Goaziou for the implementation.

The agenda has now, in addition to day, week, month, and year views, also a fortnight view covering 14 days.

Thanks to Michael Gauland for the implementation.

This variable can be used to turn off the special behavior of C-o in tables.

Please remove calls to (require 'org-mac-message) and (require 'org-mac-link-grabber) in your .emacs initialization file. All you need now is (require 'org-mac-link).

Additionally, replace any calls to ogml-grab-link to org-mac-grab-link. For example, replace this line:

(define-key org-mode-map (kbd "C-c g") 'omgl-grab-link)

with this:

(define-key org-mode-map (kbd "C-c g") 'org-mac-grab-link)

Some of the HTML specific export options in Org <8.1 are either nil or t, like #+HTML_INCLUDE_STYLE. We replaced these binary options with option keywords like :html-include-style.

So you need to replace

#+HTML_INCLUDE_STYLE: t

by

#+OPTIONS: :html-include-style t

Options affected by this change: HTML5_FANCY, HTML_INCLUDE_SCRIPTS and HTML_INCLUDE_STYLE.

See org-sort-list: hitting C-c ^ x will put checked items at the end of the list.

• Support SVG images
• Support for .pgf files
• LaTeX Babel blocks can now be exported as .tikz files
• Allow latexmk as an option for org-latex-pdf-process
• When using \usepackage[AUTO]{inputenc}, AUTO will automatically be replaced with a coding system derived from buffer-file-coding-system.
• The dependency on the latexsym LaTeX package has been removed, we now use amssymb symbols by default instead.

forward-paragraph and backward-paragraph are now remapped to org-forward-element and org-backward-element respectively. E.g. hitting C-<down> on a headline will move to the next headline.

Add support for ell, imath, jmath, varphi, varpi, aleph, gimel, beth, dalet, cdots, S (§), dag, ddag, colon, therefore, because, triangleq, leq, geq, lessgtr, lesseqgtr, ll, lll, gg, ggg, prec, preceq, preccurleyeq, succ, succeq, succurleyeq, setminus, nexist(s), mho, check, frown, diamond. Changes loz, vert, checkmark, smile and tilde.

This allows to specify the names of automatic bookmarks.

This allows more flexibility when optimizing the agenda generation. See https://orgmode.org/worg/agenda-optimization.html for details.

This is an export/publishing option, and should be used either within the #+OPTIONS line(s) or within a org-publish-project-alist.

Setting this option to t is needed when the HTML output does not allow relative URLs. For example, the contrib/lisp/ox-rss.el library produces a RSS feed, and RSS feeds need to use absolute URLs, so a combination of :html-link-home "..." and :html-link-use-abs-url t is required—see the configuration example in the comment section of ox-rss.el.

This makes java executable configurable for ditaa blocks.

This enables SVG generation from latex code blocks.

See this message from Max Mikhanosha.

If you set this to the following

(setq org-babel-inline-result-wrap "$%s$")

then inline code snippets will be wrapped into the formatting string.

ob-makefile.el implements Org Babel support for Makefile tangling.

ox-man.el allows you to export Org files to man pages.

ox-md.el allows you to export Org files to Markdown files, using the vanilla Markdown syntax.

ox-texinfo.el allows you to export Org files to Texinfo files.

Julia is a new programming language.

ob-julia.el provides Org Babel support for evaluating Julia source code.

mathomatic a portable, command-line, educational CAS and calculator software, written entirely in the C programming language.

ob-mathomatic.el provides Org Babel support for evaluating mathomatic entries.

ob-tcl.el provides Org Babel support for evaluating Tcl source code.

Display bullets instead of stars for headlines.

Also see this updated FAQ on how to display another character than "*" for starting headlines.

ox-confluence.el lets you convert Org files to Confluence Wiki files.

deck.js is a javascript library for displaying HTML ages as presentations. ox-deck.el exports Org files to HTML presentations using deck.js.

s5 is a set of scripts which also allows to display HTML pages as presentations. ox-s5.el exports Org files to HTML presentations using s5.

The groff (GNU troff) software is a typesetting package which reads plain text mixed with formatting commands and produces formatted output.

Luis Anaya and Nicolas Goaziou implemented ox-groff.el to allow conversion from Org files to groff.

This back-end allow to export Org pages to the KOMA Scrlttr2 format.

This back-end lets you export Org pages to RSS 2.0 feeds. Combined with the HTML publishing feature, this allows you to build a blog entirely with Org.

Using #+TAGS: { Tag1 : Tag2 Tag3 } will define Tag1 as a group tag (note the colon after Tag1). If you search for Tag1, it will return headlines containing either Tag1, Tag2 or Tag3 (or any combination of those tags.)

You can use group tags for sparse tree in an Org buffer, for creating agenda views, and for filtering.

See https://orgmode.org/org.html#Tag-groups for details.

These new startup keywords are now available:

• Org now fontifies radio link targets by default
• In the agenda, use org-todo-keyword-faces to highlight selected TODO keywords
• New face org-priority, enhanced fontification of priority cookies in agenda
• New face org-tag-group for group tags

David (and others) translated the Org compact guide in Spanish:

You can read the PDF guide.

Two new libraries (poporg.el by François Pinard and outorg.el by Thorsten Jolitz) now enable editing of comment-sections from source-code buffers in temporary Org-mode buffers, making the full editing power of Org-mode available. outorg.el comes together with outshine.el and navi-mode.el, two more libraries by Thorsten Jolitz with the goal to give source-code buffers the look & feel of Org-mode buffers while greatly improving navigation and structure editing. A detailed description can be found here: https://orgmode.org/worg/org-tutorials/org-outside-org.html

Here are two screencasts demonstrating Thorsten's tools:

• "Modern conventions for Emacs Lisp files"
• Exploring Bernt Hansen's Org-mode tutorial with 'navi-mode'

MobileOrg for iOS back in the App Store The 1.6.0 release was focused on the new Dropbox API and minor bug fixes but also includes a new ability to launch in Capture mode. Track development and contribute on github.

Achim implemented a new build system.

The basic method for installing Org is the same:

1. Download or clone Org.
2. run `make install' from the Org directory.
3. Add (require 'org-install) in your .emacs.el.

But the build system is now more flexible and can be more easily adapted to suit your needs.

See https://orgmode.org/worg/dev/org-build-system.html for details.

Note: The EXPERIMENTAL/ directory has been deleted. The files have been moved to the contrib/lisp/ directory.

Nicolas export engine org-export.el lives in the contrib/lisp/ directory. To use it:

Make sure contrib/lisp/ is in your load-path
M-: (require 'org-export) RET
M-: (require 'org-e-latex) RET ; or any other library
M-x org-export-dispatch RET

These are the currently available exporters:

• org-e-ascii.el by Nicolas
• org-e-beamer.el by Nicolas
• org-e-groff.el by Luis Anaya
• org-e-html.el by Jambunathan
• org-e-latex.el by Nicolas
• org-e-man.el by Luis Anaya
• org-e-odt.el by Jambunathan
• org-e-texinfo.el by Jonathan Leech-Pepin
• org-md.el by Nicolas

If we have enough testers, the new export engine is very likely to replace the current one for the next major release. Please report any problem on the mailing list!

If you want to write a new export backend based on this export engine, please check the online documentation.

org-element.el is a toolbox for parsing and analysing "elements" in an Org-mode buffer. This has been written by Nicolas Goaziou and has been tested for quite some time. It is now part of Org's core and many core functions rely on this package.

Two functions might be particularily handy for users: org-element-at-point and org-element-context. See the docstrings for more details.

Below is a list of editing and navigating commands that now rely on org-element.el.

If you hit M-TAB on keywords like #+TITLE, Org will try to perform completion with meaningful values.

Embedded javascript code produced when exporting an Org file to HTML is now licensed under GPLv3 (or later), and the copyright is owned by the Free Software Foundation, Inc.

The javascript code for embedding MathJax in the browser mentions the MathJax copyright and the Apache 2.0 license.

The javascript code for embedding org-injo.js in the browser mentions the copyright of Sebastian Rose and the GPLv3 (or later) license.

org-export-html-scripts is now a variable, so that you can adapt the code and the license to your needs.

See http://www.gnu.org/philosophy/javascript-trap.html for explanations on why these changes were necessary.

Do not use Org mode 7.xx with Emacs 21, use version 6.36c instead.

To use Org mode 7.xx with XEmacs, you need to run the developer version of XEmacs. We were about to drop XEmacs support entirely, but Michael Sperber stepped in and made changes to XEmacs that made it easier to keep the support. Thanks to Michael for this last-minute save.

The key C-c C-v is now reserved for Org Babel action. TODO sparse trees can still be made with C-c / t (all not-done states) and C-c / T (specific states).

The variable org-agenda-ndays is obsolete - please use org-agenda-span instead.

Thanks to Julien Danjou for this.

So far this variable has been used to specify the complete header of the LaTeX document, including all the \usepackage calls necessary for the document. This setup makes it difficult to maintain the list of packages that Org itself would like to call, for example for the special symbol support it needs.

First of all, you can opt out of this change in the following way: You can say: I want to have full control over headers, and I will take responsibility to include the packages Org needs. If that is what you want, add this to your configuration and skip the rest of this section (except maybe for the description of the [EXTRA] place holder):

(setq org-export-latex-default-packages-alist nil
      org-export-latex-packages-alist nil)

Continue to read here if you want to go along with the modified setup.

There are now two variables that should be used to list the LaTeX packages that need to be included in all classes. The header definition in org-export-latex-classes should then not contain the corresponding \usepackage calls (see below).

The two new variables are:

1. org-export-latex-default-packages-alist :: This is the variable where Org-mode itself puts the packages it needs. Normally you should not change this variable. The only reason to change it anyway is when one of these packages causes a conflict with another package you want to use. Then you can remove that packages and hope that you are not using Org-mode functionality that needs it.
2. org-export-latex-packages-alist :: This is the variable where you can put the packages that you'd like to use across all classes.

The sequence how these customizations will show up in the LaTeX document are:

1. Header from org-export-latex-classes
2. org-export-latex-default-packages-alist
3. org-export-latex-packages-alist
4. Buffer-specific things set with #+LaTeX_HEADER:

If you want more control about which segment is placed where, or if you want, for a specific class, have full control over the header and exclude some of the automatic building blocks, you can put the following macro-like place holders into the header:

[DEFAULT-PACKAGES]      \usepackage statements for default packages
[NO-DEFAULT-PACKAGES]   do not include any of the default packages
[PACKAGES]              \usepackage statements for packages
[NO-PACKAGES]           do not include the packages
[EXTRA]                 the stuff from #+LaTeX_HEADER
[NO-EXTRA]              do not include #+LaTeX_HEADER stuff

If you have currently customized org-export-latex-classes, you should revise that customization and remove any package calls that are covered by org-export-latex-default-packages-alist. This applies to the following packages:

• inputenc
• fontenc
• fixltx2e
• graphicx
• longtable
• float
• wrapfig
• soul
• t1enc
• textcomp
• marvosym
• wasysym
• latexsym
• amssymb
• hyperref

If one of these packages creates a conflict with another package you are using, you can remove it from org-export-latex-default-packages-alist. But then you risk that some of the advertised export features of Org will not work properly.

You can also consider moving packages that you use in all classes to org-export-latex-packages-alist. If necessary, put the place holders so that the packages get loaded in the right sequence. As said above, for backward compatibility, if you omit the place holders, all the variables will dump their content at the end of the header.

Its content is now part of the new constant org-entities, which is defined in the file org-entities.el. org-html-entities was an internal variable, but it is possible that some users did write code using it.

Please check the docstring and update your settings accordingly.

This function has been deleted: please update your code.

Jambunathan's Org to ODT exporter is now part of Org.

To use it, it `C-c C-e o' in an Org file. See the documentation for more information on how to customize it.

This replaces the earlier system org-remember. The manual only describes org-capture, but for people who prefer to continue to use org-remember, we keep a static copy of the former manual section chapter about remember.

The new system has a technically cleaner implementation and more possibilities for capturing different types of data. See Carsten's announcement for more details.

To switch over to the new system:

1. Run

   M-x org-capture-import-remember-templates RET
   
   

   to get a translated version of your remember templates into the new variable org-capture-templates. This will "mostly" work, but maybe not for all cases. At least it will give you a good place to modify your templates. After running this command, enter the customize buffer for this variable with

   M-x customize-variable RET org-capture-templates RET
   
   

   and convince yourself that everything is OK. Then save the customization.

2. Bind the command org-capture to a key, similar to what you did with org-remember:

   (define-key global-map "\C-cc" 'org-capture)
   
   

   If your fingers prefer C-c r, you can also use this key once you have decided to move over completely to the new implementation. During a test time, there is nothing wrong with using both system in parallel.

• ob-picolisp.el (Thorsten Jolitz)
• ob-fortran.el (Sergey Litvinov)
• ob-shen.el (Eric Schulte)
• ob-maxima.el (Eric S Fraga)
• ob-java.el (Eric Schulte)
• ob-lilypond.el (Martyn Jago)
• ob-awk.el (Eric Schulte)

Images can now be displayed inline. The key C-c C-x C-v does toggle the display of such images. Note that only image links that have no description part will be inlined.

If you want to start an ordered plain list with a number different from 1, you can now do it like this:

1. [@start:12] will star a lit a number 12

In org-babel, code is "expanded" prior to evaluation. I.e. the code that is actually evaluated comprises the code block contents, augmented with the extra code which assigns the referenced data to variables. It is now possible to preview expanded contents, and also to expand code during during tangling. This expansion takes into account all header arguments, and variables.

A new keybinding `C-c M-b p' bound to `org-babel-expand-src-block' can be used from inside of a source code block to preview its expanded contents (which can be very useful for debugging). tangling

The expanded body can now be tangled, this includes variable values which may be the results of other source-code blocks, or stored in headline properties or tables. One possible use for this is to allow those using org-babel for their emacs initialization to store values (e.g. usernames, passwords, etc…) in headline properties or in tables.

Org-babel now supports three new header arguments, and new default behavior for handling horizontal lines in tables (hlines), column names, and rownames across all languages.

Following a round of on-list discussion, many code block synonyms have been removed. You can safely move forward the following syntax:

• call lines are specified with #+call:
• code blocks are named with #+name:
• results are named with #+name:, however results generated by a code block may still be labeled with #+results:, and tables named with #+tblname: will be considered to be named results

The following function may be used to update an existing Org mode buffer to the new syntax:

(defun update-org-buffer ()
  "Update an Org mode buffer to the new data, code block and call line syntax."
  (interactive)
  (save-excursion
    (flet ((to-re (lst) (concat "^[ \t]*#\\+" (regexp-opt lst t)
                                "\\(\\[\\([[:alnum:]]+\\)\\]\\)?\\:[ \t]*"))
           (update (re new)
                   (goto-char (point-min))
                   (while (re-search-forward re nil t)
                     (replace-match new nil nil nil 1))))
      (let ((old-re (to-re '("RESULTS" "DATA" "SRCNAME" "SOURCE")))
            (lob-re (to-re '("LOB")))
            (case-fold-search t))
        (update old-re "name")
        (update lob-re "call")))))

Note: If an old version of Org mode (e.g., the one shipped with Emacs) is installed on your system, many of the important variables will be pre-defined with a defvar and will not have their values automatically updated – these include the following:

• org-babel-data-names
• org-babel-result-regexp
• org-babel-src-block-regexp
• org-babel-src-name-regexp
• org-babel-src-name-w-name-regexp

It may be necessary to either remove the source code of older versions of Org mode or to explicitly evaluate the ob.el file.

Code block header arguments may now be specified using the standard #+Property: keyword. See Property names ending in + accumulate for more information on the extended property syntax.

This function has been deleted: please update your hacks if you relied on it.

You can type "<2011-12-12 Mon>" or [2011-12-12 Mon] and modify this timestamps with S-<right> like other timestamps. Thanks to Carsten for implementing this.

The new function allows the user to refine the scope of entries to pass to org-agenda-get-day-entries and allows to filter out entries using a function.

Thanks to Peter Münster for raising a related issue and to Tassilo Horn for this idea. Also thanks to Peter Münster for fixing a small bug in the final implementation.

The command org-agenda-date-later (<S-right> in the Agenda Mode) directly jumps to today. Thanks to Carsten for implementing this.

See Carsten's comment: "Sometimes I want to quickly make a few TODOs done in the agenda and I want to bypass the note taking I have normally set up. With this change, I can press `0 t d' in the agenda to do this."

Thanks to Carsten for implementing this.

Nicolas Goaziou worked on refactoring and improving org-indent.el, which should now be faster. It also better combines with visual-line-mode.

This results in the following behavior.

#+property: var  foo=1
#+property: var+ bar=2

#+begin_src emacs-lisp
,  (+ foo bar)
#+end_src

#+results:
,: 3

#+begin_src emacs-lisp
,  (org-entry-get (point) "var" t)
#+end_src

#+results:
,: foo=1 bar=2

* overwriting a file-wide property
,  :PROPERTIES:
,  :var:      foo=7
,  :END:

#+begin_src emacs-lisp
,  foo
#+end_src

#+results:
,: 7

#+begin_src emacs-lisp
,  (org-entry-get (point) "var" t)
#+end_src

#+results:
,: foo=7

* appending to a file-wide property
,  :PROPERTIES:
,  :var+:      baz=3
,  :END:

#+begin_src emacs-lisp
,  (+ foo bar baz)
#+end_src

#+results:
,: 6

#+begin_src emacs-lisp
,  (org-entry-get (point) "var" t)
#+end_src

#+results:
,: foo=1 bar=2 baz=3

This option used to be `nil' by default. This now has a default value, displaying an agenda and all TODOs. See the docstring for details. Thanks to Carsten for this.

Users who use this outline commands in outline-mode will want them to behave the Org way in Org. Thanks to Michael Brand for the suggestion.

The option org-log-note-headings now supports %d and %D for inactive and active timestamps. This affect the behavior of the command org-store-log-note. Thanks to John J Foerch for a patch for this.

See the docstring. This hack from Juan Pechiar is now part of Org's core. Thanks to Juan!

You can now use the command C-c ! (org-time-stamp-inactive) when prompted e.g. for a link name. This is because the central function org-completing-read now support recursive edit. Only C-c ! is available at the moment, but if you can think of a useful command to use, please let me know.

Thanks to Skip Collins for the idea and to Nick Dokos for the implementation.

Thanks to Kai Tetzlaff for adding this.

In the file+datetree+promt target type, the user is being asked for a date, where to file an entry. In the template, he can use the escape placeholders for active and inactive time stamps. So far, these were filled with todays date. This behavior changed so that, also at %t and %u, the date to use is the one entered at the prompt.

Reported by Erik Hetzner and fixed by Carsten.

Carsten wrote org-sudoku.el, a little sudoku solver, which lives in the contrib/ directory.

From his message: "my daughter got stuck with a couple of SUDOKU puzzles during the vacation (where wh had no internet connection), so I hacked a small SUDOKU solver that reads a 9x9 Org table and solves it as a sudoku puzzle. A little silly, but maybe fun for someone - I have pushed it into the contrib/lisp directory."

Thanks to Thorsten Jolitz Pico Lisp code blocks are now supported. See ob-picolisp.el for more information.

The eval code block header argument now accepts four (six) possible values the meaning of which is shown in the table below.

When set to t, the new org-babel-update-intermediate variable will update in-buffer results for code blocks which are evaluated in the resolution of a variable reference. This can be used to ensure that the latest returned results are always shown in buffer.

Thanks to Sergey Litvinov for contributing this support.

If first variable is a string and not a cons cell, then interpret it as a string of header arguments to be passed to the code block.

See http://www.shenlanguage.org/ for information on Shen.

A major mode for shen code blocks is available through the GNU ELPA.

Format for anchors in HTML headlines.

It requires to %s: both will be replaced by the anchor referring to the headline (e.g. "sec-2"). When set to `nil', don't insert HTML anchors in headlines.

This was requested by Alan L Tyree.

Format for fields which contain the result of a formula. For example, using \"%s\" will display the result within tilde characters. Beware that modifying the display can prevent the field from being used in another formula.

Thanks to Dov Grobgeld for this idea.

When set to `t', some commands will loop over the active region. Currently, org-schedule and org-deadline uses this option: pressing C-c C-s or C-c C-d when the region is active will let you schedule/deadline all the visible headlines in the region.

Thanks a lot to David Maus for implementing this.

This option makes it possible to check what is the right thing to do before editing invisible regions. Here are the possible values of this option:

+nil              Do not check, so just do invisible edits.
+error            Throw an error and do nothing.
+show             Make point visible, and do the requested edit.
+show-and-error   Make point visible, then throw an error and abort the edit.
+smart            Make point visible, and do insertion/deletion if it is
                  adjacent to visible text and the change feels predictable.

See the docstring for more details.

Thanks to Carsten for implementing this.

Let the user place a caption above its table in LaTeX. Thanks to Thomas Dye for a patch to this effect.

By setting `org-agenda-follow-indirect' to a non-nil value, `org-agenda-follow-mode' will use an indirect buffer to display only the current item, rather than the whole agenda file in which it lives.

Thanks to Dave Abrahams for implementing this.

Non-nil means also refile active region within a subtree.

By default org-refile doesn't allow refiling regions if they don't contain a set of subtrees, but it might be convenient to do so sometimes: in that case, the first line of the region is converted to a headline before refiling.

Thanks to Jeff Horn for raising the issue of refiling a list item, and to Nicolas Goaziou, Nick Dokos and Suvayu Ali for discussing them patiently.

This option lets you specify a way to convert LaTeX fragments to MathML. See also org-latex-to-mathml-jar-file and the docstring of org-create-math-formula.

Thanks to Jambunathan K for implementing this.

See its docstring:

Alist of properties and functions to adjust inserted values.
Elements of this alist must be of the form

  ([string] [function])

where [string] must be a property name and [function] must be a
lambda expression: this lambda expression must take one argument,
the value to adjust, and return the new value as a string.

For example, this element will allow the property "Remaining"
to be updated wrt the relation between the "Effort" property
and the clock summary:

 (("Remaining" 
     (lambda(value)
       (let ((clocksum (org-clock-sum-current-item))
             (effort (org-duration-string-to-minutes
                     (org-entry-get (point) "Effort"))))
         (org-minutes-to-hh:mm-string (- effort clocksum))))))

This is inspired by a request from Pascal Mattia.

This gives you control over the character used for displaying today (default is `!') and days on which a task has been completed (default is `*'). Thanks to John Wiegley for this.

Configurable property name for bibtex entry types. Thanks to Eric Schulte for this.

This face is used for highlighting the tag(s) filter in the modeline. Thanks to Sébastien Vauban for this idea and its implementation.

org-agenda-calendar-event is the face used to show events and appointments in the agenda, and org-agenda-calendar-sexp the one used to show events computed from a S-expression.

Thanks to Sébastien Vauban for this addition.

Thanks to Suvayu Ali for spotting this problem and fixing it.

Thanks to Michael Sperber for this fix.

This command will copy the visible text in the region into the kill ring.

Thanks to Florian Beck for this function and to Carsten for adding it to org.el and documenting it!

This hook will be called when nothing special can be performed by the busy C-c C-c key. Thanks to Paul Sexton for this idea!

(git commit)

You can now use relative duration strings like "-2d" or "++3w" when calling org-schedule or org-deadline: it will schedule (or set the deadline for) the item respectively two days before today and three weeks after the current timestamp, if any.

You can use this programmatically: (org-schedule nil "+2d") will work on the current entry.

You can also use this while (bulk-)rescheduling and (bulk-)resetting the deadline of (several) items from the agenda.

Thanks to Memnon Anon for a heads up about this!

(git commit)

This is useful when you need to mark things done yesterday.

Thanks to Max Mikhanosha for this patch.

(git commit)

When setting a property with C-c C-x p, it will offered the last interactively modified property as a default choice. If this command is called on a property line, the property in this line will take precedence over the last set property.

(git commit)

Using S-M-<up/down> on CLOCK log timestamps will increase/decrease the two timestamps on this line so that duration will keep the same. Note that duration can still be slightly modified in case a timestamp needs some rounding.

Thanks to Rainer Stengele for this idea.

(git commit)

This function removes empty CLOCK drawers and has been added to org-clock-out-hook: when clocking out, if no CLOCK log has been inserted and the drawer is empty, the drawer will be removed.

(git commit)

Using %F in capture templates will insert the full path of the file or the directory the capture mechanism was called from (whereas %f only insert the filename.)

Thanks to Nicolas Goaziou for this change.

(git commit)

When using org-agenda-bulk-action in agenda view, the user could already call custom functions by pressing f and entering the function's name.

This variable lets the user add custom choices and reach them more quickly. Set the variable to an alist of keys (chars) and functions, and these keys will be accessible through the org-agenda-bulk-action interface.

If there is a conflict between custom keys and hardcoded choices, the latter ones take precedence.

Thanks to Julien Cubizolles for triggering this idea.

(git commit)

When refiling from an org-mode buffer, the current heading and its subheadings will be excluded from the list of possible targets.

This only works when org-refile-use-cache is nil and in org-mode buffers, not in agenda buffers.

Thanks to Jason Dunsmore for this idea!

This variable allows some commands to consider lists as cyclic structures. For example, when non-nil, moving past the last item of a list with S-down will bring you back to the first one.

This variable helps improving readability of sub-items by increasing their indentation. E.g., if org-list-indent-offset is set to 2, you may see the following list:

- First item
	  - Sub-item 1
	  - Sub-item 2
- Second item

See the new variable org-table-duration-custom-format and the updated example from the manual:

In this example, 0.92 is a fraction of hour, the default for org-table-duration-custom-format.

Thanks to Daniel E. Doherty for discussions about this.

(git commit)

When editing a field with C-c `, the field's coordinate will the displayed in the buffer.

Thanks to Michael Brand for a patch to this effect.

(git commit)

Evaluation of blocks of Java code is now possible. Currently only external evaluation of Java code is supported (i.e., no session evaluation) and only the :results output results are collected. Code blocks are compiled to a Java class file which are then evaluated and the values printed to STDOUT are returned.

Java code blocks required a :classname header argument which is used by the compiler to name .java and .class files.

Example Java code block:

#+begin_src java :classname myfirstjavaprog
,  class myfirstjavaprog
,  {
,      public static void main(String args[])
,      {
,          System.out.println("Hello World!");
,      }
,  }
#+end_src

#+results:
,: Hello World!

The contrib/babel/langs/ contains the new library ob-fortran.el by Sergey Litvinov.

Thanks to him for this addition.

(git commit)

ob-fomus.el has been added to contrib/babel/langs/.

Thanks to Torsten Anders for contributing this functionality.

(git commit)

When :makeindex is `non-nil' in the publishing options, Org will export an index. It populates the directory with .orgx files: those files are now hidden (.file.orgx). Also the index is directly stored in the file theindex.org, not in the file theindex.inc (which you can delete).

Thanks to Nathan Neff and Carsten for pointing at the problems and solutions.

(git commit)

The default value of org-export-html-divs is ("preamble" "content" "postamble") and is used to define the <div "%s"> for the main structure of the exported HTML file.

Note that modifying the default value will break compatibility with the org-info.js script.

Also note that the variable org-export-html-content-div will still be checked for compatibility reasons but is not a custom variable anymore.

Thanks to Sébastian Vauban for a preliminary version of this patch.

(git commit)

This allows users to define what quotes they want to use as a replacement of english double-quotes while exporting to LaTeX.

In particular, if you use the csquote package, you can configure Org to output something like \endquote{some quoted text} instead of "some quoted text".

Thanks to Frederik for bringing this issue up, and to Thomas S. Dye, Nick Dokos and Stefan Nobis for elaborating this solution.

(git commit)

Thanks to Christian Moe for signaling this problem.

Thanks to Stefan Vollmar for mentioning this problem.

(git commit)

Thanks to David Maus for suggesting related improvements to org-map-entries. This one prepares the possibility of letting some commands to loop over the active region.

(git commit)

See the updated docstring of this file.

Thanks a lot to Max Mikhanosha for this!

(git commit)

The EXPERIMENTAL/ directory contains a new file org-mm.el that allows you to export an Org file to a MoinMoin file.

Thanks to Puneeth Chaganti for this addition.

(git commit)

The default value included the title. It now defaults to the empty string, as the title is hardcoded and included in the "content" div. Including the title here is necessary to let org-info.js find it and display the page properly.

Flashy and verbose warnings while exporting to ODT have been disabled. Set this to t if you want it back.

This used to be width=10em and this is now width=.9\linewidth, which makes more sense.

Thanks to Sebastien Vauban for this suggestion.

(git commit)

This is useful when you want to use \url{link} instead of the default \href{link}{path}.

Thanks to Henri-Paul Indiogine for bringing this up.

For example, using the hungarian version of the table of contents, as defined in org-export-language-setup, the ODT exporter will complain about a problem with the translated string.

The workaround is to customize org-export-language-setup and to use accents directly.

ob-lilypond - an org-babel language, provided to allow LilyPond music score generation, complete with optional auditioning via midi, whilst leveraging the full power of org mode, and literate programming. See https://github.com/mjago/ob-lilypond for more documentation.

Thanks to Martyn Jago for this addition.

Provides support for managing bibtex bibliographical references data in headline properties. Each headline corresponds to a single reference and the relevant bibliographic meta-data is stored in headline properties, leaving the body of the headline free to hold notes and comments. Org-bibtex is aware of all standard bibtex reference types and fields.

The key new functions are

org-bibtex-check

queries the user to flesh out all required (and with prefix argument optional) bibtex fields available for the specific reference type of the current headline.

org-bibtex-create

Create a new entry at the given level, using org-bibtex-check to flesh out the relevant fields.

org-bibtex-yank

Yank a bibtex entry on the kill ring as a formatted Org mode headline into the current buffer

org-bibtex-export-to-kill-ring

Export the current headline to the kill ring as a formatted bibtex entry.

If you want to compute time values use the T flag, either in Calc formulas or Elisp formulas:

Values must be of the form [HH:]MM:SS, where hours are optional.

Thanks to Martin Halder, Eric Schulte and Carsten for code and feedback on this.

It as also possible to have footnotes side-by-side correctly exported. New variables org-export-latex-footnote-separator, org-export-html-footnote-separator and org-export-docbook-footnote-separator are used to separate them in that case.

Fontification of footnotes is also more accurate.

Non-nil means include TODO items for export.

This may have the following values:

• t include tasks independent of state.
• todo include only tasks that are not yet done.
• done include only tasks that are already done.
• nil remove all tasks before export
• list of TODO kwds keep only tasks with these keywords

Thanks to Carsten for implementing this!

This variable allows the user to define the LaTeX markup for inactive timestamps. It defaults to the same markup than active timestamps. Thanks to Eric S Fraga for this patch.

M-x customize-face RET org-default RET will let you define the default face for org-mode buffers.

The tests/ directory has been extensively updated.

During export pre-processing org-exp-blocks will now ensure that all matched blocks contain a proper balanced number of recursively nested blocks.

Before this fix nested blocks such as the following would break during export.

#+begin_src org
,  ,#+begin_example
,  ,  nested example
,  ,#+end_example
#+end_src

Fix an infinite loop when a list has an end of block string without the corresponding beginning.

Auto-filling cannot happen at a location where it would otherwise insert a new item.

• properly ignore footnotes in comments,
• export calls to previously defined footnotes in LaTeX using \footnotemark,
• export footnotes before first heading (LaTeX),
• export footnotes when selecting a subtree not holding their definition (LaTeX).

• fix `org-timer-item',
• fix insertion of a new item with a non-nil `indent-tabs-mode',
• fix use of `fill-region' in an item,
• correct export lists within footnotes and footnotes within lists,
• correctly export lists containing macros,
• don't ignore with-case specification when sorting a list,
• better indentation handling when changing an item to an headline or the other way,
• fix check-boxes' cookies updating.

It is no longer possible to assign code block variables using executable Emacs Lisp statements contained in tables or lists. As per the following example.

$data

(a b c)

Thanks to Vladimir Alexiev for raising this issue.

Please check the docstring and update your settings accordingly.

Carsten implemented this field-ranges formulas.

A frequently requested feature for tables has been to be able to define
row formulas in a way similar to column formulas.  The patch below allows
things like

@3=
@2$2..@5$7=
@I$2..@II$4=

as the left hand side for table formulas in order to write a formula that
is valid for an entire column or for a rectangular section in a
table.

Thanks a lot to Carsten for this.

Nicolas Goaziou extended and improved the way Org handles lists.

1. Indentation of text determines again end of items in lists. So, some text less indented than the previous item doesn't close the whole list anymore, only all items more indented than it.
2. Alphabetical bullets are implemented, through the use of the variable `org-alphabetical-lists'. This also adds alphabetical counters like [@c] or [@W].
3. Lists can now safely contain drawers, inline tasks, or various blocks, themselves containing lists. Two variables are controlling this: `org-list-forbidden-blocks', and `org-list-export-context'.
4. Improve `newline-and-indent' (C-j): used in an item, it will keep text from moving at column 0. This allows to split text and make paragraphs and still not break the list.
5. Improve `org-toggle-item' (C-c -): used on a region with standard text, it will change the region into one item. With a prefix argument, it will fallback to the previous behavior and make every line in region an item. It permits to easily integrate paragraphs inside a list.
6. `fill-paragraph' (M-q) now understands lists. It can freely be used inside items, or on text just after a list, even with no blank line around, without breaking list structure.

Thanks a lot to Nicolas for all this!

David Maus worked on `org-link-escape'. See his message:

Percent escaping is used in Org mode to escape certain characters
in links that would either break the parser (e.g. square brackets
in link target oder description) or are not allowed to appear in
a particular link type (e.g. non-ascii characters in a http:
link).

With this change in place Org will apply percent escaping and
unescaping more consistently especially for non-ascii characters.
Additionally some of the outstanding bugs or glitches concerning
percent escaped links are solved.

Thanks a lot to David for this work.

When set to `t', export the preamble/postamble as usual, honoring the org-export-email/author/creator-info variables.

When set to a formatting string, insert this string. See the docstring of these variable for details about available %-sequences.

You can set :html-preamble in publishing project in the same way: `t' means to honor :email/creator/author-info, and a formatting string will insert a string.

You can now use `org-agenda-append-agenda' to dynamically add new agendas views to the current one. It is particularily useful to compare multiple small agendas.

Clock tables now support a new new :lang parameter, allowing the user to customize the localization of the table headers. See the variable org-clock-clocktable-language-setup which controls available translated strings.

The :sitemap-sort-file option now allows sorting the sitemap file (anti-)alphabetically and (anti-)chronogically. Thanks a lot to Manuel Giraud for a patch to this effet.

Martyn Jago added new tests to testing/ - thanks to him!

Org is now distributed with org-notmuch.el, by Matthieu Lemerre. See explanations in the header of org-notmuch.el:

=org-notmuch.el= implements links to notmuch messages and
"searchs". A search is a query to be performed by notmuch; it is
the equivalent to folders in other mail clients. Similarly, mails
are refered to by a query, so both a link can refer to several
mails.

You can now create links from messages. This is particularily useful when the user wants to stored messages that he sends, for later check. Thanks to Ulf Stegemann for the patch.

You can now safely capture entries to narrowed buffers. Thanks a lot to Memnon Anon for bringing this up.

Agendas were a bit confused by the introduction of this variable, in particular block agendas. This is now fixed.

Thanks to Julien and Carsten for helping find the right fix for this issue, and to Michael Brand and Matt Lundin for their patient testing and reporting.

To prevent Emacs from auto-saving encrypted entries in clear text, the user should not use auto-save with org-crypt.el. We now send a warning when users are both using auto-saving and org-crypt.el. Thanks to Peter Jones for bringing this up.

In case you were manually loading org-complete.el (which is not necessary anyway), please be aware that the name of this library was changed to org-pcomplete.el.

New variables `org-export-latex-listings-options' and `org-export-latex-minted-options' allow package options to be controlled; `org-export-latex-custom-lang-environments' allows arbitrary configuration on a per-language basis.

Effort duration can now be set as 2h (for 2 hours), etc. This will be converted to minutes automatically when clocking in an entry with an effort property. See the org-effort-durations variable.

Thanks a lot to Lawrence Mitchell for this patch.

A capture template with :clock-keep t will prevent the refiling process from clocking out the entry. If :clock-resume is also `t', :clock-keep will take precedence and :clock-resume will be ignored.

So now :immediate-finish t :clock-in t :clock-keep t makes sense: it will capture a new task and clock it.

The variable org-agenda-ndays is obsolete - please use org-agenda-span instead.

Thanks to Julien Danjou for this.

There is now a configurable way on how to export inline tasks. See the new variable org-inlinetask-export-templates.

Thanks to Nicolas Goaziou for coding these changes.

B S in the agenda buffer will cause tasks to be rescheduled a random number of days into the future, with 7 as the default. This is useful if you've got a ton of tasks scheduled for today, you realize you'll never deal with them all, and you just want them to be distributed across the next N days. When called with a prefix arg, rescheduling will avoid weekend days.

Thanks to John Wiegley for this.

Thanks to John Wiegley for much of this code.

Org radio tables can no also be sent inside Org buffers. Also, there is a new hook which get called after a table has been sent.

Thanks to Seweryn Kokot.

The reference manual now lists command names for most commands. Thanks to Andreas Röhler who started this project.

Times in the agenda can now be displayed in am/pm format. See the new variable org-agenda-timegrid-use-ampm. Thanks to C. A. Webber for a patch to this effect.

The entire clocktable code has been rewritten to add more options and to make hacking time reports easier.

Thanks to Erwin Vrolijk for a patch introducing clock tables for quarters.

Due to changes in the code resolving code block header arguments hashing of code block results should now re-run a code block when an argument to the code block has changed. As a result of this change all code blocks with cached results will be re-run after upgrading to the latest version.

Anyone using the org-mode test suite will need to update the jump repository for test navigation by executing the following from the root of the org-mode repository.

git submodule update

Failure to update this repository will cause loading of org-test.el to throw errors.

All Org-babel commands (behind the C-c C-v key prefix) are now available as speed commands when the point is on the first line of a code block. This uses the existing Org mode speed key mechanisms.

Thanks to Jambunathan K for implementation this new feature.

Source code in code blocks can now be fontified. Please customize the varable org-src-fontify-natively. For very large blocks (several hundreds of lines) there can be delays in editing such fontified blocks, in which case C-c ' should be used to bring up a dedicated edit buffer.

Thanks to Dan Davison for this.

The most general machinery for doing this is the macro `org-babel-do-in-edit-buffer'. There is also the convenience function `org-babel-do-key-sequence-in-edit-buffer' which makes use of this macro, and is bound to C-c C-v C-x and C-c C-v x. If there is an active region contained within the code block, then this is inherited by the edit buffer. Some examples of the sorts of usage this permits are

C-c C-v C-x M-; comment region according to language C-c C-v C-x C-M-\ indent region according to language

Users can make these more convenient, e.g.

(defun my/org-comment-dwim (&optional arg) (interactive "P") (or (org-babel-do-key-sequence-in-edit-buffer "\M-;") (comment-dwim arg)))

(define-key org-mode-map "\M-;" 'my/org-comment-dwim)

A common instance of this general pattern is built in to Org mode, controlled by the variable `org-src-tab-acts-natively': if this variable is set, then TAB in a code block has the effect that it would have in the language major mode buffer.

Mirroring the language-native commands in Org buffers above, a new macro `org-src-do-at-code-block' and convenience function `org-src-do-key-sequence-at-code-block' provide the converse. When used in a language major-mode edit buffer (i.e. a buffer generated by C-c '), `org-src-do-key-sequence-at-code-block' executes a key sequence at the code block in the source Org buffer. The command bound to the key sequence in the Org-babel key map is executed remotely with point temporarily at the start of the code block in the Org buffer.

The command is not bound to a key by default, to avoid conflicts with language major mode bindings. To bind it to C-c @ in all language major modes, you could use

(add-hook 'org-src-mode-hook (lambda () (define-key org-src-mode-map "\C-c@" 'org-src-do-key-sequence-at-code-block)))

In that case, for example, C-c @ t issued in code edit buffers would tangle the current Org code block, C-c @ e would execute the block and C-c @ h would display the other available Org-babel commands.

Code block header arguments can now span multiple lines using the new #+header: or #+headers: lines preceding a code block or nested in between the name and body of a named code block. Examples are given below.

• multi-line header arguments on an un-named code block

  #+headers: :var data1=1
  #+begin_src emacs-lisp :var data2=2
    (message "data1:%S, data2:%S" data1 data2)
  #+end_src
  
  #+results:
  : data1:1, data2:2
  
  

• multi-line header arguments on a named code block

  #+source: named-block
  #+header: :var data=2
  #+begin_src emacs-lisp
    (message "data:%S" data)
  #+end_src
  
  #+results: named-block
  : data:2
  
  

The code used to resolve variable references in code block header arguments has now been consolidated. This both simplifies the code base (especially the language-specific files), and ensures that the arguments to a code block will not be evaluated multiple times. This change should not be externally visible to the Org mode user.

Code block caches now notice if the value of a variable argument to the code block has changed, if this is the case the cache is invalidated and the code block is re-run. The following example can provide intuition for the new behavior.

#+srcname: random
#+begin_src R :cache yes
,runif(1)
#+end_src

#+results[a2a72cd647ad44515fab62e144796432793d68e1]: random
,: 0.4659510825295

#+srcname: caller
#+begin_src emacs-lisp :var x=random :cache yes
,x
#+end_src

#+results[bec9c8724e397d5df3b696502df3ed7892fc4f5f]: caller
,: 0.254227238707244

This makes it possible to set LaTeX options which must take place in the document pre-amble for LaTeX code blocks. This header argument accepts either a single string or a list, e.g.

#+begin_src latex :headers \usepackage{lmodern} :file name1.pdf
,  latex body
#+end_src

#+begin_src latex :headers '("\\usepackage{mathpazo}" "\\usepackage{fullpage}") :file name2.pdf
,  latex body
#+end_src

Allows exporting directly from a string to the specified export format.

Only expands syntax references when tangling, not during export (weaving).

C-c C-v z (`org-babel-switch-to-session-with-code') is a variant of C-c C-v C-z (`org-babel-switch-to-session'): instead of switching to the session buffer, it splits the window between (a) the session buffer and (b) a language major-mode edit buffer for the code block in question. This can be convenient for using language major mode for interacting with the session buffer.

R now uses standard ESS code evaluation machinery in the :results value case, which avoids unnecessary output to the comint buffer. In addition, the R command responsible for writing the result to file is hidden from the user. Finally, the R code edit buffer generated by C-c ' is automatically linked to the ESS session if the current code block is using :session.

All babel temporary files are now kept in a single sub-directory in the /tmp directory and are cleaned up when Emacs exits.

Can be called to wrap the region in a block, or to split the block around point, bound to (C-c C-v d).

Bound to C-M-h in the babel key map (i.e. C-c C-v C-M-h by default). This can be useful in conjunction with `org-babel-do-in-edit-buffer', for example for language-native commenting or indenting of the whole block.

When several anniversaries are defined in the bbdb anniversaries field (separated by semicolon), this is now handled nicely by the agenda.

Thanks to Łukasz Stelmach for a patch to this effect.

In HTML export, table fields are now properly aligned in accord with automatic alignment in org, or as set by the <r>, <l>, and <c> cookies. The <c> cookie is new and has no effect in Org, but it does do the right thing in HTML export. A LaTeX export implementation will follow, but is currently still missing.

The freemind exporter now incorporates body text into the mind map.

Thanks to Lennard Borgman for this patch.

The footnotes code now searches for message-signature-separator (which is "– " by default) in order to place footnotes before the signature. Thanks to Tassilo Horn for this patch.

Org mode 7.02 now runs again in 21.4.22 if the new XEmacs base package is installed.

Thanks to Uwe Bauer, Volker Ziegler, Michael Sperber and others for a discussion that lead to this nice result.

When jumping to a date from the agenda using the j key, you may or may not like the property of Org's date reader to prefer the future when you enter incomplete dates. This can now be configured using the variable =org-agenda-jump-prefer-future'.

There are now publishing functions org-publish-org-to-ascii, org-publish-org-to-latin1, and org-publish-org-to-utf8.

Thanks to Matthias Danzl for showing how to do this.

Indentation in inline tasks, and headline insertion after inline tasks now behave as expected.

As soon as MobilOrg 1.5 hits the Apple's AppStore, you can encrypt your org files on public servers. Please see the documentation of MobileOrg and Appendix B of the manual for more details.

If you dislike the property of MobileOrg to insert ID properties for in all entries being part of an agenda view, you can now turn this off using the variable org-mobile-force-id-on-agenda-items. When this variable is set to nil, MobileOrg will use outline paths to identify entries. Note that this may fail if several entries have identical outline paths.

Patch by Dan Davison.

A non-nil value of `org-export-latex-minted' means to export source code using the minted package, which will fontify source code with color. If you want to use this, you need to make LaTeX use the minted package. Add minted to `org-export-latex-packages-alist', for example using customize, or with something like

(require 'org-latex) (add-to-list 'org-export-latex-packages-alist '("" "minted"))

In addition, it is neccessary to install pygments (http://pygments.org), and to configure `org-latex-to-pdf-process' so that the -shell-escape option is passed to pdflatex.

Please see the variable org-export-latex-to-pdf-process for more information.

Thanks to Olivier Schwander for the rubber part.

If you want to inline images whenever you visit an Org file, use

#+STARTUP: inlineimages

There is a new hook org-speed-command-hook. Thanks to Jambunathan for a patch to this effect.

you can use {{{property{NAME}}}} to insert the value of a property upon export.

Thanks to David Maus for a patch to this effect.

We updated the list of default packages loaded by LaTeX exported files.

Tags can now also contain the characters # and %, in addition to @ and letters.

Andreas Röhler is adding command names to keys in the manual. This will take a while to complete, but a start has been made.

When entering a tags/property query, "-" is a logical operator. However, "-" is also allowed in property names. So you can now write "SOME­NAME" to work around this issue.

This was a request by Ilya Shlyakhter.

Org mode has a built-in template mechanism for inserting block templates. This was undocumented until now.

Thanks to Jambunathan K for the patch.

Org mode now uses MathJax to display math on web pages. We serve MathJax from the orgmode.org server, at least for the time being (thanks Bastien!). If you are going to use this for pages which are viewed often, please install MathJax on your own webserver.

To return to the old way of creating images and inserting them into web pages, you would have to set

(setq org-export-with-LaTeX-fragments 'dvipng)

or on a per-file basis

#+OPTIONS: LaTeX:dvipng

If you have many custom agenda commands, you can have the display in the dispatcher use two columns with the following settings

(setq org-agenda-menu-show-match nil
      org-agenda-menu-two-column t)

This was a request by John Wiegley.

One frequent request has been to be able to use CamelCase words for automatic cross links in a Wiki created by Org. THis is now possible with org-wikinodes.el, which is available in the contrib directory. We also have some documentation for this feature up on Worg.

org-timer-set-timer displays a countdown timer in the modeline. From the agenda, `J' invokes org-agenda-clock-goto.

Do not use Org mode 7.xx with Emacs 21, use version 6.36c instead.

To use Org mode 7.xx with XEmacs, you need to run the developer version of XEmacs. I was about to drop XEmacs support entirely, but Michael Sperber stepped in and made changes to XEmacs that made it easier to keep the support. Thanks to Michael for this last-minute save. I had hoped to be able to remove xemacs/noutline.el from release 7 by moving it into XEmacs, but this is not yet done.

Babel took the integration into Org mode as an opportunity to do some much needed house cleaning. Most importantly we have simplified the enabling of language support, and cleared out unnecessary configuration variables – which is great unless you already have a working configuration under the old model.

The most important changes regard the location and enabling of Babel (both core functionality and language specific support).

Babel

Babel is now part of the core of Org mode, so it is now loaded along with the rest of Org mode. That means that there is no configuration required to enable the main Babel functionality. For current users, this means that statements like

(require 'org-babel)

or

(require 'org-babel-init)

that may by lying around in your configuration must now be removed.

load path

Babel (including all language specific files – aside from those which are located in the contrib/ directory for reasons of licencing) now lives in the base of the Org mode lisp directory, so no additional directories need to be added to your load path to use babel. For Babel users this means that statements adding babel-specific directories to your load-path should now be removed from your config.

language support

It is no longer necessary to require language specific support on a language-by-language basis. Specific language support should now be managed through the `org-babel-load-languages' variable. This variable can be customized using the Emacs customization interface, or through the addition of something like the following to your configuration (note: any language not mentioned will not be enabled, aside from emacs-lisp which is enabled by default)

(org-babel-do-load-languages
 'org-babel-load-languages
 '((R . t)
   (ditaa . t)
   (dot . t)
   (emacs-lisp . t)
   (gnuplot . t)
   (haskell . nil)
   (ocaml . nil)
   (python . t)
   (ruby . t)
   (screen . nil)
   (sh . t)
   (sql . nil)
   (sqlite . t)))

Despite this change it is still possible to add language support through the use of require statements, however to conform to Emacs file-name regulations all Babel language files have changed prefix from org-babel-* to ob-*, so the require lines must also change e.g.

(require 'org-babel-R)

should be changed to

(require 'ob-R)

We have eliminated the org-babel-tangle-w-comments variable as well as the two main internal lists of languages, namely

• org-babel-interpreters and
• org-babel-tangle-langs

so any config lines which mention those variables, can/should be stripped out in their entirety. This includes any calls to the org-babel-add-interpreter function, whose sole purpose was to add languages to the org-babel-interpreters variable.

With those calls stripped out, we may still in some cases want to associate a file name extension with certain languages, for example we want all of our emacs-lisp files to end in a .el, we can do this will the org-babel-tangle-lang-exts variable. In general you shouldn't need to touch this as it already has defaults for most common languages, and if a language is not present in org-babel-tangle-langs, then babel will just use the language name, so for example a file of c code will have a .c extension by default, shell-scripts (identified with sh) will have a .sh extension etc…

The configuration of shebang lines now lives in header arguments. So the shebang for a single file can be set at the code block level, e.g.

#+begin_src clojure :shebang #!/usr/bin/env clj
,  (println "with a shebang line, I can be run as a script!")
#+end_src

Note that whenever a file is tangled which includes a shebang line, Babel will make the file executable, so there is good reason to only add shebangs at the source-code block level. However if you're sure that you want all of your code in some language (say shell scripts) to tangle out with shebang lines, then you can customize the default header arguments for that language, e.g.

;; ensure this variable is defined defined
(unless (boundp 'org-babel-default-header-args:sh)
  (setq org-babel-default-header-args:sh '()))

;; add a default shebang header argument
(add-to-list 'org-babel-default-header-args:sh
             '(:shebang . "#!/bin/bash"))

The final important change included in this release is the addition of new security measures into Babel. These measures are in place to protect users from the accidental or uninformed execution of code. Along these lines every execution of a code block will now require an explicit confirmation from the user. These confirmations can be stifled through customization of the `org-confirm-babel-evaluate' variable, e.g.

;; I don't want to be prompted on every code block evaluation
(setq org-confirm-babel-evaluate nil)

In addition, it is now possible to remove code block evaluation form the C-c C-c keybinding. This can be done by setting the org-babel-no-eval-on-ctrl-c-ctrl-c variable to a non-nil value, e.g.

;; I don't want to execute code blocks with C-c C-c
(setq org-babel-no-eval-on-ctrl-c-ctrl-c t)

An additional keybinding has been added for code block evaluation, namely C-c C-v e.

Whew! that seems like a lot of effort for a simplification of configuration.

The key C-c C-v is now reserved for Org Babel action. TODO sparse trees can still be made with C-c / t (all not-done states) and C-c / T (specific states).

To make it more flexible for users to provide DocBook exporter related commands, we start to use format-spec to format the commands in this release. If you use DocBook exporter and use it to export Org files to PDF and/or FO format, the settings of the following two customizable variables need to be changed:

• org-export-docbook-xslt-proc-command
• org-export-docbook-xsl-fo-proc-command

Instead of using %s in the format control string for all arguments, now we use three different format spec characters:

• %i: input file argument
• %o: output file argument
• %s: XSLT stylesheet argument

For example, if you set org-export-docbook-xslt-proc-command to

java com.icl.saxon.StyleSheet -o %s %s /path/to/docbook.xsl

in the past, now you need to change it to

java com.icl.saxon.StyleSheet -o %o %i %s

and set a new customizable variable called org-export-docbook-xslt-stylesheet to /path/to/docbook.xsl.

Please check the documentation of these two variables for more details and other examples.

Along with the introduction of variable org-export-docbook-xslt-stylesheet, we also added a new in-buffer setting called #+XSLT:. You can use this setting to specify the XSLT stylesheet that you want to use on a per-file basis. This setting overrides org-export-docbook-xslt-stylesheet.

See Org-babel configuration changes for instructions on how to update your babel configuration.

The most significant result of this change is that Babel now has documentation! It is part of Org mode's documentation, see Chapter 14 Working With Source Code. The Babel keybindings are now listed in the refcard, and can be viewed from any Org mode buffer by pressing C-c C-v h. In addition this integration has included a number of bug fixes, and a significant amount of internal code cleanup.

This replaces the earlier system org-remember. The manual only describes org-capture, but for people who prefer to continue to use org-remember, we keep a static copy of the former manual section chapter about remember.

The new system has a technically cleaner implementation and more possibilities for capturing different types of data. See Carsten's announcement for more details.

To switch over to the new system:

1. Run

   M-x org-capture-import-remember-templates RET
   
   

   to get a translated version of your remember templates into the new variable org-capture-templates. This will "mostly" work, but maybe not for all cases. At least it will give you a good place to modify your templates. After running this command, enter the customize buffer for this variable with

   M-x customize-variable RET org-capture-templates RET
   
   

   and convince yourself that everything is OK. Then save the customization.

2. Bind the command org-capture to a key, similar to what you did with org-remember:

   (define-key global-map "\C-cc" 'org-capture)
   
   

   If your fingers prefer C-c r, you can also use this key once you have decided to move over completely to the new implementation. During a test time, there is nothing wrong with using both system in parallel.

The command C-c C-x \ toggles the display of Org's special entities like \alpha as pretty unicode characters. Also, sub and superscripts are displayed in a pretty way (raised/lower display, in a smaller font). If you want to exclude sub- and superscripts, see the variable org-pretty-entities-include-sub-superscripts.

Thanks to Eric Schulte and Ulf Stegeman for making this possible.

The new command M-x org-entities-help creates a structured buffer that lists all entities available in Org. Thanks to Ulf Stegeman for adding the necessary structure to the internal entity list.

Christian Egli's org-taskjuggler.el module is now part of Org. He also wrote a tutorial for it.

You can turn on caching of refile targets by setting the variable org-refile-use-cache. This should speed up refiling if you have many eligible targets in many files. If you need to update the cache because Org misses a newly created entry or still offers a deleted one, press C-0 C-c C-w.

Here are the new options for the clock resolver:

i/q/C-g  Ignore this question; the same as keeping all the idle time.

k/K      Keep X minutes of the idle time (default is all).  If this
         amount is less than the default, you will be clocked out
         that many minutes after the time that idling began, and then
         clocked back in at the present time.
g/G      Indicate that you \"got back\" X minutes ago.  This is quite
         different from 'k': it clocks you out from the beginning of
         the idle period and clock you back in X minutes ago.
s/S      Subtract the idle time from the current clock.  This is the
         same as keeping 0 minutes.
C        Cancel the open timer altogether.  It will be as though you
         never clocked in.
j/J      Jump to the current clock, to make manual adjustments.

For all these options, using uppercase makes your final state to be CLOCKED OUT. Thanks to John Wiegley for making these changes.

This can be useful in particular with property inheritance, if some upper level has the property, and some grandchild of it would like to have the default settings (i.e. not overruled by a property) back.

Thanks to Robert Goldman and Bernt Hansen for suggesting this change.

Thanks to Leo who has been on a year-long quest to get this fixed and finally found the right way to do it.

This was a request by Scott Otterson. See the new variable org-ctrl-k-protect-subtree.

This module allows to grab links to all kinds of applications on a mac. It is available in the contrib directory.

Thanks to Anthony Lander for this contribution.

Thanks to Chris Gray for a patch to this effect.

Thanks to David Maus for this change.

Images can now be displayed inline. The key C-c C-x C-v does toggle the display of such images. Note that only image links that have no description part will be inlined.

If you want to start an ordered plain list with a number different from 1, you can now do it like this:

1. [@start:12] will star a lit a number 12

• Remove filter conditions for messages in a filter folder

  If customization variable `org-wl-link-remove-filter' is non-nil, filter conditions are stripped of the folder name.

• Create web links for messages in a Shimbun folder

  If customization variable `org-wl-shimbun-prefer-web-links' is non-nil, calling `org-store-link' on a Shimbun message creates a web link to the messages source, indicated in the Xref: header field.

• Create web links for messages in a nntp folder

  If customization variable `org-wl-nntp-prefer-web-links' is non-nil, calling `org-store-link' on a nntp message creates a web link either to gmane.org if the group can be read trough gmane or to googlegroups otherwise. In both cases the message-id is used as reference.

• Open links in namazu search folder

  If `org-wl-open' is called with one prefix, WL opens a namazu search folder for message's message-id using `org-wl-namazu-default-index' as search index. If this variable is nil or `org-wl-open' is called with two prefixes Org asks for the search index to use.

Thanks to David Maus for these changes.

In org-babel, code is "expanded" prior to evaluation. I.e. the code that is actually evaluated comprises the code block contents, augmented with the extra code which assigns the referenced data to variables. It is now possible to preview expanded contents, and also to expand code during during tangling. This expansion takes into account all header arguments, and variables.

A new key-binding C-c M-b p bound to `org-babel-expand-src-block' can be used from inside of a source code block to preview its expanded contents (which can be very useful for debugging). tangling

The expanded body can now be tangled, this includes variable values which may be the results of other source-code blocks, or stored in headline properties or tables. One possible use for this is to allow those using org-babel for their emacs initialization to store values (e.g. usernames, passwords, etc…) in headline properties or in tables.

Org-babel now supports three new header arguments, and new default behavior for handling horizontal lines in tables (hlines), column names, and rownames across all languages.

So far this variable has been used to specify the complete header of the LaTeX document, including all the \usepackage calls necessary for the document. This setup makes it difficult to maintain the list of packages that Org itself would like to call, for example for the special symbol support it needs. Each time I have to add a package, I have to ask people to revise the configuration of this variable. In this release, I have tried to fix this.

First of all, you can opt out of this change in the following way: You can say: I want to have full control over headers, and I will take responsibility to include the packages Org needs. If that is what you want, add this to your configuration and skip the rest of this section (except maybe for the description of the [EXTRA] place holder):

(setq org-export-latex-default-packages-alist nil
      org-export-latex-packages-alist nil)

Continue to read here if you want to go along with the modified setup.

There are now two variables that should be used to list the LaTeX packages that need to be included in all classes. The header definition in org-export-latex-classes should then not contain the corresponding \usepackage calls (see below).

The two new variables are:

1. org-export-latex-default-packages-alist :: This is the variable where Org mode itself puts the packages it needs. Normally you should not change this variable. The only reason to change it anyway is when one of these packages causes a conflict with another package you want to use. Then you can remove that packages and hope that you are not using Org mode functionality that needs it.
2. org-export-latex-packages-alist :: This is the variable where you can put the packages that you'd like to use across all classes. For example, I am putting amsmath and tikz here, because I always want to have them.

The sequence how these customizations will show up in the LaTeX document are:

1. Header from org-export-latex-classes
2. org-export-latex-default-packages-alist
3. org-export-latex-packages-alist
4. Buffer-specific things set with #+LaTeX_HEADER:

If you want more control about which segment is placed where, or if you want, for a specific class, have full control over the header and exclude some of the automatic building blocks, you can put the following macro-like place holders into the header:

[DEFAULT-PACKAGES]      \usepackage statements for default packages
[NO-DEFAULT-PACKAGES]   do not include any of the default packages
[PACKAGES]              \usepackage statements for packages
[NO-PACKAGES]           do not include the packages
[EXTRA]                 the stuff from #+LaTeX_HEADER
[NO-EXTRA]              do not include #+LaTeX_HEADER stuff

If you have currently customized org-export-latex-classes, you should revise that customization and remove any package calls that are covered by org-export-latex-default-packages-alist. This applies to the following packages:

• inputenc
• fontenc
• fixltx2e
• graphicx
• longtable
• float
• wrapfig
• soul
• t1enc
• textcomp
• marvosym
• wasysym
• latexsym
• amssymb
• hyperref

If one of these packages creates a conflict with another package you are using, you can remove it from org-export-latex-default-packages-alist. But then you risk that some of the advertised export features of Org will not work properly.

You can also consider moving packages that you use in all classes to org-export-latex-packages-alist. If necessary, put the place holders so that the packages get loaded in the right sequence. As said above, for backward compatibility, if you omit the place holders, all the variables will dump their content at the end of the header.

Damn, this has become more complex than I wanted it to be. I hope that in practice, this will not be complicated at all.

Its content is now part of the new constant org-entities, which is defined in the file org-entities.el. org-html-entities was an internal variable, but it is possible that some users did write code using it - this is why I am mentioning it here.

The keywords in these lines are now dimmed out, and the title is displayed in a larger font, and a special font is also used for author, date, and email information. This is implemented by the following new faces:

org-document-title org-document-info org-document-info-keyword

In addition, the variable org-hidden-keywords can be used to make the corresponding keywords disappear.

Thanks to Dan Davison for this feature.

The variables org-todo-keyword-faces, org-tag-faces, and org-priority-faces now accept simple color names as specifications. The colors will be used as either foreground or background color for the corresponding keyword. See also the variable org-faces-easy-properties, which governs which face property is affected by this setting.

This is really a great simplification for setting keyword faces. The change is based on an idea and patch by Ryan Thompson.

Requested by Michael Brand.

TAB in an empty headline cycles the level of that headline through likely states. Ryan Thompson implemented an improved version of this function, which does not depend upon when exactly this command is used. Thanks to Ryan for this improvement.

For paragraph text, org-adaptive-fill-function did not handle the base case of regular text which needed to be filled. This is now fixed. Among other things, it allows email-style ">" comments to be filled correctly.

Thanks to Dan Hackney for this patch.

Thanks to Richard Riley for triggering this change.

When all first letters of keywords have been used, Org now assigns more meaningful characters based on the keywords.

Thanks to Mikael Fornius for this patch.

Special entities like \therefore and \alpha now know if they need to be in LaTeX math mode and are formatted accordingly.

Thanks to Ulf Stegemann for the tedious work to make this possible.

The coding system of the LaTeX class will now be set to the value corresponding to the buffer's file coding system. This happens if your setup sets up the file to have a line \usepackage[AUTO]{inputenc} (the default setup does this).

While Ulf Stegemann was going through the entities list to improve the LaTeX export, he had the great idea to provide representations for many of the entities in Latin-1, and for all of them in UTF-8. This means that we can now export files rich in special symbols to Latin-1 and to UTF-8 files. These new exporters can be reached with the commands C-c C-e n and C-c C-e u, respectively.

When there is no representation for a given symbol in the targeted coding system, you can choose to keep the TeX-macro-like representation, or to get an "explanatory" representation. For example, \simeq could be represented as "[approx. equal to]". Please use the variable org-entities-ascii-explanatory to state your preference.

#+LABEL definitions for tables and figures are now fully implemented in the LaTeX, Docbook, and HTML interfaces. \ref{xxx} is expanded to a valid link in all backends.

The new option org-outline-frame-title allows to set the title for outline frames in Beamer presentations.

Patch by Łukasz Stelmach.

A lstlisting environment now also triggers the fragile option in a beamer frame, just like verbatim environments do.

Thanks to Eric Schulte for this patch.

Macros for the BEAMER package can have arguments in angular brackets. These are now protected just like normal arguments.

Requested by Bill Jackson.

The HTML_CONTAINER_CLASS property can now be used to add a class name to the outline container of a node in HTML export.