emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
* Release 8.0
@ 2013-04-18 16:41 Bastien
  2013-04-18 16:58 ` Jambunathan K
                   ` (13 more replies)
  0 siblings, 14 replies; 40+ messages in thread
From: Bastien @ 2013-04-18 16:41 UTC (permalink / raw)
  To: emacs-orgmode

[-- Attachment #1: Type: text/plain, Size: 556 bytes --]

Dear all,

I'm releasing Org 8.0.

See the release notes below or at http://orgmode.org/Changes.html

This release is potentially the most disruptive release since long,
so please don't use it in production before you can carefully review
the release notes and update your configuration -- especially with
respect to export features.

I would like to thank you all again for your patience, and special
thanks to Nicolas who is just great to work with.  I'm happy to see
his code finally widely available for all Org users, not just the
happy few.

Enjoy!


[-- Attachment #2: Changes.txt --]
[-- Type: text/plain, Size: 54062 bytes --]

			    ━━━━━━━━━━━━━━━━
				ORG 8.0
			    ━━━━━━━━━━━━━━━━


Installation
════════════

  Installation instructions have been updated and simplified.

  If you have troubles installing or updating Org, focus on these
  instructions:

  • when updating via a `.zip/.tar.gz' file, you only need to set the
    `load-path' in your `.emacs'.  Set it before any other Org
    customization that would call autoloaded Org functions.

  • when updating by pulling Org's Git repository, make sure to create
    the correct autoloads.  You can do this by running `~$ make
    autoloads' (to only create the autoloads) or by running `~$ make'
    (to also compile the Emacs lisp files.)  `~$ make help' and `~$ make
    helpall' gives you detailed explanations.

  • when updating through ELPA (either from GNU ELPA or from Org ELPA),
    you have to install Org's ELPA package in a session where no Org
    function has been called already.

  When in doubt, run `M-x org-version RET' and see if you have a
  mixed-up installation.

  See [http://orgmode.org/org.html#Installation] for details.


Incompatible changes
════════════════════

  Org 8.0 is the most disruptive major version of Org.

  If you configured export options, you will have to update some of
  them.

  If you used `#+ATTR_*' keywords, the syntax of the attributes changed
  and you will have to update them.

  Below is a list of changes for which you need to take action.

  See [http://orgmode.org/worg/org-8.0.html] for the most recent version
  of this list and for detailed instructions on how to migrate.


New export engine
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  Org 8.0 comes with a new export engine written by Nicolas Goaziou.
  This export engine relies on `org-element.el' (Org's syntax parser),
  which was already in Org's core.  This new export engine triggered the
  rewriting of /all/ export back-ends.

  The most visible change is the export dispatcher, accessible through
  the keybinding `C-c C-e'.  By default, this menu only shows some of
  the built-in export formats, but you can add more formats by loading
  them directly (e.g., `(require 'ox-texinfo)' or by configuring the
  option org-export-backends.

  More contributed back-ends are available from the `contrib/'
  directory, the corresponding files start with the `ox-' prefix.

  If you customized an export back-end (like HTML or LaTeX), you will
  need to rename some options so that your customization is not lost.
  Typically, an option starting with `org-export-html-' is now named
  `org-html-'.  See the manual for details and check [this Worg page]
  for directions.


  [this Worg page] http://orgmode.org/worg/org-8.0.html


New syntax for #+ATTR_HTML/LaTeX/… options
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  ╭────
  │ #+ATTR_HTML width="200px"
  ╰────

  should now be written

  ╭────
  │ #+ATTR_HTML :width 200px
  ╰────

  Keywords like `#+ATTR_HTML' and `#+ATTR_LaTeX' are defined in their
  respective back-ends, and the list of supported parameters depends on
  each backend.  See Org's manual for details.


`org-remember.el' has been removed
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  You cannot use `remember.el' anymore to capture notes.

  Support for remember templates has been obsoleted since long, it is
  now fully removed.

  Use `M-x org-capture-import-remember-templates RET' to import your
  remember templates into capture templates.


`org-jsinfo.el' has been merged into `ox-html.el'
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  If you were requiring `ox-jsinfo.el' in your `.emacs.el' file, you
  will have to remove this requirement from your initialization file.


Note for third-party developers
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  The name of the files for export back-end have changed: we now use the
  prefix `ox-' for those files (like we use the `ob-' prefix for Babel
  files.)  For example `org-html.el' is now `ox-html.el'.

  If your code relies on these files, please update the names in your
  code.


Packages moved from core to contrib
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  Since packages in Org's core are meant to be part of GNU Emacs, we try
  to be minimalist when it comes to adding files into core.  For 8.0, we
  moved some contributions into the `contrib/' directory.

  The rationale for deciding that these files should live in `contrib/'
  is either because they rely on third-part softwares that are not
  included in Emacs, or because they are not targetting a significant
  user-base.

  • org-colview-xemacs.el
  • org-mac-message.el
  • org-mew.el
  • org-wl.el
  • ox-freedmind.el
  • ox-taskjuggler.el

  Note that `ox-freedmind.el' has been rewritten by Jambunathan,
  `org-mew.el' has been enhanced by Tokuya Kameshima and
  `ox-taskjuggler.el' by Nicolas Goaziou and others.

  Also, the Taskjuggler exporter now uses TJ3 by default.  John Hendy
  wrote [a tutorial on Worg] for the TJ3 export.


  [a tutorial on Worg]
  http://orgmode.org/worg/org-tutorials/org-taskjuggler3.html


New packages in core
════════════════════

`ob-makefile.el' by Eric Schulte and Thomas S. Dye
──────────────────────────────────────────────────

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


`ox-man.el' by Luis Anaya
─────────────────────────

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


`ox-md.el' by Nicolas Goaziou
─────────────────────────────

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


  [Markdown syntax] http://daringfireball.net/projects/markdown/


`ox-texinfo.el' by Jonathan Leech-Pepin
───────────────────────────────────────

  `ox-texinfo.el' allows you to export Org files to [Texinfo] files.


  [Texinfo] http://www.gnu.org/software/texinfo/


New packages in contrib
═══════════════════════

`ob-julia.el' by G. Jay Kerns
─────────────────────────────

  [Julia] is a new programming language.

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


  [Julia] http://julialang.org/


`ob-mathomatic.el' by Luis Anaya
────────────────────────────────

  [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.


  [mathomatic] http://www.mathomatic.org/


`ob-tcl.el' by Luis Anaya
─────────────────────────

  `ob-tcl.el' provides Org Babel support for evaluating [Tcl] source
  code.


  [Tcl] http://www.tcl.tk/


`org-bullets.el' by Evgeni Sabof
────────────────────────────────

  Display bullets instead of stars for headlines.

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


  [this updated FAQ] http://orgmode.org/worg/org-faq.html#sec-8-12


`org-favtable.el' by Marc-Oliver Ihm
────────────────────────────────────

  `org-favtable.el' helps you to create and update a table of favorite
  locations in org, keeping the most frequently visited lines right at
  the top.  This table is called "favtable".  See the documentation on
  [Worg].


  [Worg] http://orgmode.org/worg/org-contrib/org-favtable.html


`ox-confluence.el' by Sébastien Delafond
────────────────────────────────────────

  `ox-confluence.el' lets you convert Org files to [Confluence Wiki]
  files.


  [Confluence Wiki]
  https://confluence.atlassian.com/display/DOC/Confluence%2BWiki%2BMarkup


`ox-deck.el' and `ox-s5.el' by Rick Frankel
───────────────────────────────────────────

  [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'.


  [deck.js] http://imakewebthings.com/deck.js/

  [s5] http://meyerweb.com/eric/tools/s5/


`ox-groff.el' by Luis Anaya and Nicolas Goaziou
───────────────────────────────────────────────

  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.


  [groff] http://www.gnu.org/software/groff/


`ox-koma-letter.el' by Nicolas Goaziou and Alan Schmitt
───────────────────────────────────────────────────────

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


`ox-rss.el' by Bastien
──────────────────────

  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.


New features
════════════

Export
──────

New export generic options
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  If you use Org exporter, we advise you to re-read [the manual section
  about it].  It has been updated and includes new options.

  Among the new/updated export options, three are of particular
  importance:

  org-export-allow-bind-keywords: This option replaces the old option
      `org-export-allow-BIND' and the default value is `nil', not
      `confirm'.  You will need to explicitely set this to `t' in your
      initialization file if you want to allow `#+BIND' keywords.

  org-export-with-planning: This new option controls the export of
      `SCHEDULED:, DEADLINE:, CLOSED:' lines, and planning information is
      now skipped by default during export.  This use to be the job of
      org-export-with-timestamps, but this latter option has been given a
      new role: it controls the export of /standalone time-stamps/.  When
      set to `nil', Org will not export active and inactive time-stamps
      standing on a line by themselves or within a paragraph that only
      contains time-stamps.

  To check if an option has been introduced or its default value changed
  in Org 8.0, do `C-h v [option] RET' and check if the documentation
  says that the variable has been introduced (or changed) in version
  24.4 of Emacs.


  [the manual section about it] http://orgmode.org/org.html#Exporting


Enhanced default stylesheet for the HTML exporter
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  See the new default value of org-html-style-default.


New tags, classes and ids for the HTML exporter
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  See the new default value of org-html-divs.


Support for tikz pictures in LaTeX export
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌


`org-man.el': New export function for "man" links
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌


`org-docview.el': New export function for docview links
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌


Structure editing
─────────────────

`C-u C-u M-RET' inserts a heading at the end of the parent subtree
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌


Cycling to the `CONTENTS' view keeps inline tasks folded
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  org-cycle-hook as a new function org-cycle-hide-inline-tasks which
  prevents the display of inline tasks when showing the content of a
  subtree.


`C-c -' in a region makes a list item for each line
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  This is the opposite of the previous behavior, where `C-c -' on a
  region would create one item for the whole region, and where `C-u C-c
  -' would create an item for each line.  Now `C-c -' on the selected
  region creates an item per line, and `C-u C-c -' creates a single item
  for the whole region.


When transposing words, markup characters are now part of the words
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  In Emacs, you can transpose words with `M-t'.  Transposing `*these*
  _words__' will preserve markup.


New command org-set-property-and-value bound to `C-c C-x P'
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  This command allows you to quickly add both the property and its
  value.  It is useful in buffers where there are many properties and
  where `C-c C-x p' can slow down the flow of editing too much.


New commands org-next-block and org-previous-block
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  These commands allow you to go to the previous block (`C-c M-b' or the
  speedy key `B') or to the next block (`C-c M-f' or the speedy key
  `F'.)


New commands org-drag-line-forward and org-drag-line-backward
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  These commands emulate the old behavior of `M-<down>' and `M-<up>' but
  are now bound to `S-M-<down>' and `S-M-<up>' respectively, since
  `M-<down>' and `M-<up>' now drag the whole element at point (a
  paragraph, a table, etc.)  forward and backward.


When a list item has a checkbox, inserting a new item uses a checkbox too
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌


When sorting entries/items, only the description of links is considered
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  Now Org will sort this list

  ╭────
  │ - [[http://abc.org][B]]
  │ - [[http://def.org][A]]
  ╰────

  like this:

  ╭────
  │ - [[http://def.org][A]]
  │ - [[http://abc.org][B]]
  ╰────

  by comparing the descriptions, not the links.  Same when sorting
  headlines instead of list items.


New option `orgstruct-heading-prefix-regexp'
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  For example, setting this option to "^;;; " in Emacs lisp files and
  using `orgstruct-mode' in those files will allow you to cycle through
  visibility states as if lines starting with ";;; *…" where headlines.

  In general, you want to set `orgstruct-heading-prefix-regexp' as a
  file local variable.


New behavior of org-clone-subtree-with-time-shift
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  The default is to only ask for a number of clones.  When called with a
  universal prefix argument `C-u', it will prompt you for a time-shift
  only if there is a time-stamp in the task you want to clone.


New option org-agenda-restriction-lock-highlight-subtree
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  This defaults to `t' so that the whole subtree is highlighted when you
  restrict the agenda view to it with `C-c C-x <' (or the speed command
  `<').  The default setting helps ensuring that you are not adding
  tasks after the restricted region.  If you find this highlighting too
  intrusive, set this option to `nil'.


New option org-closed-keep-when-no-todo
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  When switching back from a `DONE' keyword to a `TODO' keyword, Org now
  removes the `CLOSED' planning information, if any.  It also removes
  this information when going back to a non-TODO state (e.g., with `C-c
  C-t SPC').  If you want to keep the `CLOSED' planning information when
  removing the TODO keyword, set org-closed-keep-when-no-todo to `t'.


New option org-image-actual-width
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  This option allows you to change the width of in-buffer displayed
  images.  The default is to use the actual width of the image, but you
  can use a fixed value for all images, or fall back on an attribute
  like

  ╭────
  │ #+attr_html: :width 300px
  ╰────


Scheduled/deadline
──────────────────

Implement "delay" cookies for scheduled items
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  If you want to delay the display of a scheduled task in the agenda,
  you can now use a delay cookie like this: `SCHEDULED: <2004-12-25 Sat
  -2d>'.  The task is still scheduled on the 25th but will appear in
  your agenda starting from two days later (i.e. from March 27th.)

  Imagine for example that your co-workers are not done in due time and
  tell you "we need two more days".  In that case, you may want to delay
  the display of the task in your agenda by two days, but you still want
  the task to appear as scheduled on March 25th.

  In case the task contains a repeater, the delay is considered to
  affect all occurrences; if you want the delay to only affect the first
  scheduled occurrence of the task, use `--2d' instead.  See
  org-scheduled-delay-days and
  org-agenda-skip-scheduled-delay-if-deadline for details on how to
  control this globally or per agenda.


Use `C-u C-u C-s' will insert a delay cookie for scheduled tasks
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  See the previous section for why delay cookies may be useful.


Use `C-u C-u C-d' will insert a warning delay for deadline tasks
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  `C-u C-u C-d' now inserts a warning delay to deadlines.


Calendar, diary and appts
─────────────────────────

New variable org-read-date-minibuffer-local-map
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  By default, this new local map uses "." to go to today's date, like in
  the normal `M-x calendar RET'.  If you want to deactivate this and to
  reassign the "@" key to `calendar-goto-today', use this:

  ╭────
  │ ;; Unbind "." in Org's calendar:
  │ (define-key org-read-date-minibuffer-local-map (kbd ".") nil)
  │
  │ ;; Bind "@" to `calendar-goto-today':
  │ (define-key org-read-date-minibuffer-local-map
  │             (kbd "@")
  │             (lambda () (interactive) (org-eval-in-calendar '(calendar-goto-today))))
  ╰────


In Org's calendar, `!' displays diary entries of the date at point
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  This is useful when you want to check if you don't already have an
  appointment when setting new ones with `C-c .' or `C-c s'.  `!' will
  call `diary-view-entries' and display the diary in a separate buffer.


org-diary: only keep the descriptions of links
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  org-diary returns diary information from Org files, but it returns it
  in a diary buffer, not in an Org mode buffer.  When links are
  displayed, only show their description, not the full links.


Agenda
──────

New agenda type `agenda*' and entry types `:scheduled* :deadline*'
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  When defining agenda custom commands, you can now use `agenda*': this
  will list entries that have both a date and a time.  This is useful
  when you want to build a list of appointments.

  You can also set org-agenda-entry-types either globally or locally in
  each agenda custom command and use `:timestamp*' and/or `:deadline*'
  there.

  Another place where this is useful is your `.diary' file:

  ╭────
  │ %%(org-diary :scheduled*) ~/org/rdv.org
  ╰────

  This will list only entries from `~/org/rdv.org' that are scheduled
  with a time value (i.e. appointments).


New agenda sorting strategies
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  org-agenda-sorting-strategy allows these new sorting strategies:

  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
   Strategy        Explanations
  ──────────────────────────────────────────────────────────
   timestamp-up    Sort by any timestamp, early first
   timestamp-down  Sort by any timestamp, late first
   scheduled-up    Sort by scheduled timestamp, early first
   scheduled-down  Sort by scheduled timestamp, late first
   deadline-up     Sort by deadline timestamp, early first
   deadline-down   Sort by deadline timestamp, late first
   ts-up           Sort by active timestamp, early first
   ts-down         Sort by active timestamp, late first
   tsia-up         Sort by inactive timestamp, early first
   tsia-down       Sort by inactive timestamp, late first
  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━


New options to limit the number of agenda entries
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  You can now limit the number of entries in an agenda view.  This is
  different from filters: filters only /hide/ the entries in the agenda,
  while limits are set while generating the list of agenda entries.

  These new options are available:

  org-agenda-max-entries: limit by number of entries.
  org-agenda-max-todos: limit by number of TODOs.
  org-agenda-max-tags: limit by number of tagged entries.
  org-agenda-max-effort: limit by effort (minutes).

  For example, if you locally set org-agenda-max-todos to 3 in an agenda
  view, the agenda will be limited to the first three todos.  Other entries
  without a TODO keyword or beyond the third TODO headline will be ignored.

  When setting a limit (e.g. about an effort's sum), the default behavior
  is to exclude entries that cannot be checked against (e.g. entries that
  have no effort property.)  To include other entries too, you can set the
  limit to a negative number.  For example (setq org-agenda-max-tags 3)
  will not show the fourth tagged headline (and beyond), but it will also
  show non-tagged headlines.


`~' in agenda view sets temporary limits
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  You can hit `~' in the agenda to temporarily set limits: this will
  regenerate the agenda as if the limits were set.  This is useful for
  example when you want to only see a list of `N' tasks, or a list of
  tasks that take only `N' minutes.


"=" in agenda view filters by regular expressions
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  You can now filter agenda entries by regular expressions using `='.
  `C-u =' will filter entries out.  Regexp filters are cumulative.  You
  can set org-agenda-regexp-filter-preset to suit your needs in each
  agenda view.


`|' in agenda view resets all filters
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  Since it's common to combine tag filters, category filters, and now
  regexp filters, there is a new command `|' to reset all filters at
  once.


Allow writing an agenda to an `.org' file
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  You can now write an agenda view to an `.org' file.  It copies the
  headlines and their content (but not subheadings) into the new file.

  This is useful when you want to quickly share an agenda containing the
  full list of notes.


New commands to drag an agenda line forward (`M-<down>') or backard (`M-<up>')
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  It sometimes handy to move agenda lines around, just to quickly
  reorganize your tasks, or maybe before saving the agenda to a file.
  Now you can use `M-<down>' and `M-<up>' to move the line forward or
  backward.

  This does not persist after a refresh of the agenda, and this does not
  change the `.org' files who contribute to the agenda.


Use `%s' for displaying "breadcrumbs" in the agenda view
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  org-agenda-prefix-format now allows to use a `%b' formatter to tell
  Org to display "breadcrumbs" in the agenda view.

  This is useful when you want to display the task hierarchy in your
  agenda.


Use `%l' for displaying the headline's level in the agenda view
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  org-agenda-prefix-format allows to use a `%l' formatter to tell Org to
  display entries with additional spaces corresponding to their level in
  the outline tree.


org-agenda-write will ask before overwriting an existing file
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  `M-x org-agenda-write RET' (or `C-c C-w' from an agenda buffer) used
  to overwrite preexisting file with the same name without confirmation.
  It now asks for a confirmation.


New commands `M-m' and `M-*' to toggle (all) mark(s) for bulk action
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  org-agenda-bulk-toggle: this command is bound to `M-m' and toggles the
      mark of the entry at point.

  org-agenda-bulk-toggle-all: this command is bound to `M-*' and toggles
      all the marks in the current agenda.


New option org-agenda-search-view-max-outline-level
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  This option sets the maximum outline level to display in search view.
  E.g. when this is set to 1, the search view will only show headlines
  of level 1.


New option org-agenda-todo-ignore-time-comparison-use-seconds
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  This allows to compare times using seconds instead of days when
  honoring options like `org-agenda-todo-ignore-*' in the agenda
  display.


New option org-agenda-entry-text-leaders
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  This allows you to get rid of the ">" character that gets added in
  front of entries excerpts when hitting `E' in the agenda view.


New formatting string for past deadlines in org-agenda-deadline-leaders
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  The default formatting for past deadlines is `"%2d d. ago: "', which
  makes it explicit that the deadline is in the past.  You can configure
  this via org-agenda-deadline-leaders.  Note that the width of the
  formatting string is important to keep the agenda alignment clean.


New allowed value `repeated-after-deadline' for org-agenda-skip-scheduled-if-deadline-is-shown
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  When org-agenda-skip-scheduled-if-deadline-is-shown is set to
  `repeated-after-deadline', the agenda will skip scheduled items if
  they are repeated beyond the current dealine.


New option for org-agenda-skip-deadline-prewarning-if-scheduled
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  This variable may be set to nil, t, the symbol `pre-scheduled', or a
  number which will then give the number of days before the actual
  deadline when the prewarnings should resume.  The symbol
  `pre-scheduled' eliminates the deadline prewarning only prior to the
  scheduled date.

  Read the full docstring for details.


org-class now supports holiday strings in the skip-weeks parameter
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  For example, this task will now be skipped only on new year's day:

  ╭────
  │ * Task
  │   <%%(org-class 2012 1 1 2013 12 12 2 "New Year's Day")>
  ╰────


Capture
───────

Allow `C-1' as a prefix for org-agenda-capture and org-capture
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  With a `C-1' prefix, the capture mechanism will use the `HH:MM' value
  at point (if any) or the current `HH:MM' time as the default time for
  the capture template.


Expand keywords within %(sexp) placeholder in capture templates
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  If you use a `%:keyword' construct within a `%(sexp)' construct, Org
  will expand the keywords before expanding the `%(sexp)'.


Allow to contextualize capture (and agenda) commands by checking the name of the buffer
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  org-capture-templates-contexts and org-agenda-custom-commands-contexts
  allow you to define what capture templates and what agenda commands
  should be available in various contexts.  It is now possible for the
  context to check against the name of the buffer.


Tag groups
──────────

  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
  combinaison of those tags.)

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

  See [http://orgmode.org/org.html#Tag-groups] for details.


Links
─────

`C-u C-u M-x org-store-link RET' will ignore non-core link functions
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  Org knows how to store links from Org buffers, from info files and
  from other Emacs buffers.  Org can be taught how to store links from
  any buffer through new link protocols (see ["Adding hyperlink types"]
  in the manual.)

  Sometimes you want Org to ignore added link protocols and store the
  link as if the protocol was not known.

  You can now do this with `C-u C-u M-x org-store-link RET'.


  ["Adding hyperlink types"]
  http://orgmode.org/org.html#Adding-hyperlink-types


`C-u C-u C-u M-x org-store-link RET' on an active region will store links for each lines
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  Imagine for example that you want to store a link for every message in
  a Gnus summary buffer.  In that case `C-x h C-u C-u C-u M-x
  org-store-link RET' will store a link for every line (i.e. message) if
  the region is active.


`C-c C-M-l' will add a default description for links which don't have one
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  `C-c C-M-l' inserts all stored links.  If a link does not have a
  description, this command now adds a default one, so that we are not
  mixing with-description and without-description links when inserting
  them.


No curly braces to bracket links within internal links
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  When storing a link to a headline like

  ╭────
  │ * See [[http://orgmode.org][Org website]]
  ╰────

  org-store-link used to convert the square brackets into curly
  brackets.  It does not anymore, taking the link description or the
  link path, when there is no description.


Table
─────

Switching between #+TBLFM lines
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  If you have several `#+TBLFM' lines below a table, `C-c C-c' on a line
  will apply the formulas from this line, and `C-c C-c' on another line
  will apply those other formulas.


You now use "nan" for empty fields in Calc formulas
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  If empty fields are of interest, it is recommended to reread the
  section [3.5.2 Formula syntax for Calc] of the manual because the
  description for the mode strings has been clarified and new examples
  have been added towards the end.


  [3.5.2 Formula syntax for Calc]
  http://orgmode.org/org.html#Formula-syntax-for-Calc


Handle localized time-stamps in formulas evaluation
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  If your `LOCALE' is set so that Org time-stamps use another language
  than english, and if you make time computations in Org's table, it now
  works by internally converting the time-stamps with a temporary
  `LOCALE=C' before doing computation.


New lookup functions
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  There are now three lookup functions:

  • org-loopup-first
  • org-loopup-last
  • org-loopup-all

  See [the manual] for details.


  [the manual] http://orgmode.org/org.html#Lookup-functions


Startup keywords
────────────────

  These new startup keywords are now available:

  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
   Startup keyword                   Option
  ───────────────────────────────────────────────────────────────────────────────
   `#+STARTUP: logdrawer'            `(setq org-log-into-drawer t)'
   `#+STARTUP: nologdrawer'          `(setq org-log-into-drawer nil)'
  ───────────────────────────────────────────────────────────────────────────────
   `#+STARTUP: logstatesreversed'    `(setq org-log-states-order-reversed t)'
   `#+STARTUP: nologstatesreversed'  `(setq org-log-states-order-reversed nil)'
  ───────────────────────────────────────────────────────────────────────────────
   `#+STARTUP: latexpreview'         `(setq org-startup-with-latex-preview t)'
   `#+STARTUP: nolatexpreview'       `(setq org-startup-with-latex-preview nil)'
  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━


Clocking
────────

New option org-clock-rounding-minutes
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  E.g. if org-clock-rounding-minutes is set to 5, time is 14:47 and you
  clock in: then the clock starts at 14:45.  If you clock out within the
  next 5 minutes, the clock line will be removed; if you clock out 8
  minutes after your clocked in, the clock out time will be 14:50.


New option org-time-clocksum-use-effort-durations
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  When non-nil, `C-c C-x C-d' uses effort durations.  E.g., by default,
  one day is considered to be a 8 hours effort, so a task that has been
  clocked for 16 hours will be displayed as during 2 days in the clock
  display or in the clocktable.

  See org-effort-durations on how to set effort durations and
  org-time-clocksum-format for more on time clock formats.


New option org-clock-x11idle-program-name
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  This allows to set the name of the program which prints X11 idle time
  in milliseconds.  The default is to use `x11idle'.


New option org-use-last-clock-out-time-as-effective-time
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  When non-nil, use the last clock out time for org-todo.  Note that
  this option has precedence over the combined use of
  org-use-effective-time and org-extend-today-until.


`S-<left/right>' on a clocksum column will update the sum by updating the last clock
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌


`C-u 3 C-S-<up/down>' will update clock timestamps synchronously by 3 units
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌


New parameter `:wstart' for clocktables to define the week start day
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌


New parameter `:mstart' to state the starting day of the month
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌


Allow relative times in clocktable tstart and tend options
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌


The clocktable summary is now a caption
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌


`:tstart' and `:tend' and friends allow relative times like "<-1w>" or "<now>"
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌


Babel
─────

You can now use `C-c C-k' for org-edit-src-abort
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  This allows you to quickly cancel editing a source block.


`C-u C-u M-x org-babel-tangle RET' tangles by the target file of the block at point
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  This is handy if you want to tangle all source code blocks that have
  the same target than the block at point.


New options for auto-saving the base buffer or the source block editing buffer
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  When org-edit-src-turn-on-auto-save is set to `t', editing a source
  block in a new window will turn on `auto-save-mode' and save the code
  in a new file under the same directory than the base Org file.

  When org-edit-src-auto-save-idle-delay is set to a number of minutes
  `N', the base Org buffer will be saved after this number of minutes of
  idle time.


New `:post' header argument post-processes results
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  This header argument may be used to pass the results of the current
  code block through another code block for post-processing.  See the
  manual for a usage example.


Commented out heading are ignored when collecting blocks for tangling
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  If you comment out a heading (with `C-c ;' anywhere on the heading or
  in the subtree), code blocks from within this heading are now ignored
  when collecting blocks for tangling.


New option org-babel-hash-show-time to show a time-stamp in the result hash
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌


Do not ask for confirmation if cached value is current
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  Do not run org-babel-confirm-evaluate if source block has a cache and
  the cache value is current as there is no evaluation involved in this
  case.


`ob-sql.el' and `ob-python.el' have been improved.
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌


New Babel files only need to `(require 'ob)'
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  When writing a new Babel file, you now only need to use `(require
  'ob)' instead of requiring each Babel library one by one.


Faces
─────

  • 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


Miscellaneous
═════════════

  • New speedy key `s' pour org-narrow-to-subtree
  • Handling of org-html-table-row has been updated (incompatible change)
  • org-export-html-table-tag is replaced by org-html-table-default-attributes
  • Support using `git-annex' with Org attachments
  • org-protocol: Pass optional value using query in url to capture from protocol
  • When the refile history is empty, use the current filename as default
  • When you cannot change the TODO state of a task, Org displays the
    blocking task
  • New option org-mobile-allpriorities
  • org-bibtex.el now use `visual-line-mode' instead of the deprecated
    `longlines-mode'
  • org-format-latex-options allows to set the foreground/background
    colors automatically
  • New option org-archive-file-header-format
  • New "neg" entity in org-entities
  • New function org-docview-export to export docview links
  • New `:eps' header argument for ditaa code blocks
  • New option org-gnus-no-server to start Gnus with `gnus-no-server'
  • Org is now distributed with `htmlize.el' version 1.43
  • `org-drill.el' has been updated to version 2.3.7
  • `org-mac-iCal.el' now supports MacOSX version up to 10.8
  • Various improvements to `org-contacts.el' and `orgpan.el'


Outside Org
═══════════

Spanish translation of the Org guide by David Arroyo Menéndez
─────────────────────────────────────────────────────────────

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

  You can read the [PDF guide].


  [PDF guide] http://orgmode.org/worg/orgguide/orgguide.es.pdf


`poporg.el' and `outorg.el'
───────────────────────────

  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:
  [http://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']


  ["Modern conventions for Emacs Lisp files"]
  http://youtu.be/nqE6YxlY0rw

  [Exploring Bernt Hansen's Org-mode tutorial with 'navi-mode']
  http://www.youtube.com/watch?v%3DII-xYw5VGFM


MobileOrg for iOS
─────────────────

  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].


  [on github] https://github.com/MobileOrg/mobileorg/issues


Thanks you all!
════════=======

Here is a list of people we need to thanks for this release:

Aaron Ecay, Abdó Roig-Maranges, Achim Gratz, Adam Spiers, Alan Schmitt,
Alexander Willand, Andreas Leha, Andreas Röhler, Andrew M. Nuxoll, Arun
Persaud, Bernd Haug, Bernt Hansen, Bill Day, Bill White, Brian van den
Broek, Carsten Dominik, Charles C. Berry, Christian Egli, Christian Moe,
Christophe Junke, Christopher Schmidt, Christopher Witte, Chuck Berry,
Daniel Clemente, Daniel Dehennin, Dave Abrahams, David Kincaid, Derek
Upham, Enda, Eric Abrahamsen, Eric S Fraga, Eric Schulte, Esben Stien,
Fabrice Popineau, Feng Shu, Florian Beck, Francesco Pizzolante, Frank
Fischer, Frank Terbeck, François Pinard, G. Jay Kerns, Gaizka Villate, Gary
Oberbrunner, Greg Minshall, Gregor Kappler, Grégoire Jadi, Henry Atting,
Hiroshi Saito, Hrvoje Nikšić, Ian Barton, Ingo Lohmar, Ippei FURUHASHI,
Ivan Vilata i Balaguer, J. David Boyd, Jae Hee Lee, Jambunathan K, James
Harkins, Jarmo Hurri, John Foerch, John Hendy, John J Foerch, John Wiegley,
Jonas Bernoulli, Jonathan Leech-Pepin, Joost Helberg, Justus Piater, Kalev
Takkis, Ken Williams, Kevin Buchs, Kodi Arfer, Kyle Machulis, Le Wang, Leo
Liu, Luca Sabbatini, Luis Anaya, Marcel van der Boom, Mark Edgington, Matt
Lundin, Max Mikhanosha, Michael Brand, Michael Crouch, Michael Gauland,
Michael Heerdegen, Michael Strey, Mirko Vukovic, Myles English, Nick Dokos,
Nicolas Goaziou, Nicolas Richard, Oliver Večerník, Paul Sexton, Peder
Stray, Peter Münster, Philipp Kroos, Raghavendra D Prabhu, Rainer M. Krug,
Rainer Stengele, Rasmus, Rene, Richard Stanton, Rick Frankel, Rick Hanson,
Robert Goldman, Robert Horn, Robert Klein, Roland Winkler, Ryo TAKAISHI,
Rémi Vanicat, Rüdiger Sonderfeld, Sacha Chua, Samuel Loury, Samuel Wales,
Sean O'Halpin, Sébastien Vauban, Simon Thum, Stefan Monnier, Stefan
Vollmar, Stephen Eglen, Steve Purcell, Suhail Shergill, Suvayu Ali,
T.F. Torrey, Thomas S. Dye, Thorsten Jolitz, Toby S. Cubitt, Tokuya
Kameshima, Tony Day, Viktor Rosenfeld, Vincent Beffara, Vladimir Lomov,
Wanrong Lin, William Lechelle, Xiao-Yong Jin, Xue Fuqiao, Yann Hodique,
Yasushi SHOJI, Zech, sabof, Дядов Васил Стоянов.

[-- Attachment #3: Type: text/plain, Size: 14 bytes --]


-- 
 Bastien

^ permalink raw reply	[flat|nested] 40+ messages in thread

* Re: Release 8.0
  2013-04-18 16:41 Release 8.0 Bastien
@ 2013-04-18 16:58 ` Jambunathan K
  2013-04-18 17:37   ` Bastien
  2013-04-18 17:15 ` Anthony Lander
                   ` (12 subsequent siblings)
  13 siblings, 1 reply; 40+ messages in thread
From: Jambunathan K @ 2013-04-18 16:58 UTC (permalink / raw)
  To: Bastien; +Cc: emacs-orgmode


Bastien

Could you please correct the headers to ox-html.el and ox-odt.el.  I
have not assigned the rights to my changes to FSF.  These files - due to
Emacs project policy - cannot be part of Emacs.

Jambunathan K.

^ permalink raw reply	[flat|nested] 40+ messages in thread

* Re: Release 8.0
  2013-04-18 16:41 Release 8.0 Bastien
  2013-04-18 16:58 ` Jambunathan K
@ 2013-04-18 17:15 ` Anthony Lander
  2013-04-18 17:28 ` Appeal to donors (Re: Release 8.0) Jambunathan K
                   ` (11 subsequent siblings)
  13 siblings, 0 replies; 40+ messages in thread
From: Anthony Lander @ 2013-04-18 17:15 UTC (permalink / raw)
  To: emacs-orgmode

[-- Attachment #1: Type: text/plain, Size: 58172 bytes --]

Bastien & all contributors, thank you!!!




On Thu, Apr 18, 2013 at 12:41 PM, Bastien <bzg@gnu.org> wrote:

> Dear all,
>
> I'm releasing Org 8.0.
>
> See the release notes below or at http://orgmode.org/Changes.html
>
> This release is potentially the most disruptive release since long,
> so please don't use it in production before you can carefully review
> the release notes and update your configuration -- especially with
> respect to export features.
>
> I would like to thank you all again for your patience, and special
> thanks to Nicolas who is just great to work with.  I'm happy to see
> his code finally widely available for all Org users, not just the
> happy few.
>
> Enjoy!
>
>
>                             ━━━━━━━━━━━━━━━━
>                                 ORG 8.0
>                             ━━━━━━━━━━━━━━━━
>
>
> Installation
> ════════════
>
>   Installation instructions have been updated and simplified.
>
>   If you have troubles installing or updating Org, focus on these
>   instructions:
>
>   • when updating via a `.zip/.tar.gz' file, you only need to set the
>     `load-path' in your `.emacs'.  Set it before any other Org
>     customization that would call autoloaded Org functions.
>
>   • when updating by pulling Org's Git repository, make sure to create
>     the correct autoloads.  You can do this by running `~$ make
>     autoloads' (to only create the autoloads) or by running `~$ make'
>     (to also compile the Emacs lisp files.)  `~$ make help' and `~$ make
>     helpall' gives you detailed explanations.
>
>   • when updating through ELPA (either from GNU ELPA or from Org ELPA),
>     you have to install Org's ELPA package in a session where no Org
>     function has been called already.
>
>   When in doubt, run `M-x org-version RET' and see if you have a
>   mixed-up installation.
>
>   See [http://orgmode.org/org.html#Installation] for details.
>
>
> Incompatible changes
> ════════════════════
>
>   Org 8.0 is the most disruptive major version of Org.
>
>   If you configured export options, you will have to update some of
>   them.
>
>   If you used `#+ATTR_*' keywords, the syntax of the attributes changed
>   and you will have to update them.
>
>   Below is a list of changes for which you need to take action.
>
>   See [http://orgmode.org/worg/org-8.0.html] for the most recent version
>   of this list and for detailed instructions on how to migrate.
>
>
> New export engine
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   Org 8.0 comes with a new export engine written by Nicolas Goaziou.
>   This export engine relies on `org-element.el' (Org's syntax parser),
>   which was already in Org's core.  This new export engine triggered the
>   rewriting of /all/ export back-ends.
>
>   The most visible change is the export dispatcher, accessible through
>   the keybinding `C-c C-e'.  By default, this menu only shows some of
>   the built-in export formats, but you can add more formats by loading
>   them directly (e.g., `(require 'ox-texinfo)' or by configuring the
>   option org-export-backends.
>
>   More contributed back-ends are available from the `contrib/'
>   directory, the corresponding files start with the `ox-' prefix.
>
>   If you customized an export back-end (like HTML or LaTeX), you will
>   need to rename some options so that your customization is not lost.
>   Typically, an option starting with `org-export-html-' is now named
>   `org-html-'.  See the manual for details and check [this Worg page]
>   for directions.
>
>
>   [this Worg page] http://orgmode.org/worg/org-8.0.html
>
>
> New syntax for #+ATTR_HTML/LaTeX/… options
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   ╭────
>   │ #+ATTR_HTML width="200px"
>   ╰────
>
>   should now be written
>
>   ╭────
>   │ #+ATTR_HTML :width 200px
>   ╰────
>
>   Keywords like `#+ATTR_HTML' and `#+ATTR_LaTeX' are defined in their
>   respective back-ends, and the list of supported parameters depends on
>   each backend.  See Org's manual for details.
>
>
> `org-remember.el' has been removed
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   You cannot use `remember.el' anymore to capture notes.
>
>   Support for remember templates has been obsoleted since long, it is
>   now fully removed.
>
>   Use `M-x org-capture-import-remember-templates RET' to import your
>   remember templates into capture templates.
>
>
> `org-jsinfo.el' has been merged into `ox-html.el'
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   If you were requiring `ox-jsinfo.el' in your `.emacs.el' file, you
>   will have to remove this requirement from your initialization file.
>
>
> Note for third-party developers
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   The name of the files for export back-end have changed: we now use the
>   prefix `ox-' for those files (like we use the `ob-' prefix for Babel
>   files.)  For example `org-html.el' is now `ox-html.el'.
>
>   If your code relies on these files, please update the names in your
>   code.
>
>
> Packages moved from core to contrib
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   Since packages in Org's core are meant to be part of GNU Emacs, we try
>   to be minimalist when it comes to adding files into core.  For 8.0, we
>   moved some contributions into the `contrib/' directory.
>
>   The rationale for deciding that these files should live in `contrib/'
>   is either because they rely on third-part softwares that are not
>   included in Emacs, or because they are not targetting a significant
>   user-base.
>
>   • org-colview-xemacs.el
>   • org-mac-message.el
>   • org-mew.el
>   • org-wl.el
>   • ox-freedmind.el
>   • ox-taskjuggler.el
>
>   Note that `ox-freedmind.el' has been rewritten by Jambunathan,
>   `org-mew.el' has been enhanced by Tokuya Kameshima and
>   `ox-taskjuggler.el' by Nicolas Goaziou and others.
>
>   Also, the Taskjuggler exporter now uses TJ3 by default.  John Hendy
>   wrote [a tutorial on Worg] for the TJ3 export.
>
>
>   [a tutorial on Worg]
>   http://orgmode.org/worg/org-tutorials/org-taskjuggler3.html
>
>
> New packages in core
> ════════════════════
>
> `ob-makefile.el' by Eric Schulte and Thomas S. Dye
> ──────────────────────────────────────────────────
>
>   `ob-makefile.el' implements Org Babel support for Makefile tangling.
>
>
> `ox-man.el' by Luis Anaya
> ─────────────────────────
>
>   `ox-man.el' allows you to export Org files to `man' pages.
>
>
> `ox-md.el' by Nicolas Goaziou
> ─────────────────────────────
>
>   `ox-md.el' allows you to export Org files to Markdown files, using the
>   vanilla [Markdown syntax].
>
>
>   [Markdown syntax] http://daringfireball.net/projects/markdown/
>
>
> `ox-texinfo.el' by Jonathan Leech-Pepin
> ───────────────────────────────────────
>
>   `ox-texinfo.el' allows you to export Org files to [Texinfo] files.
>
>
>   [Texinfo] http://www.gnu.org/software/texinfo/
>
>
> New packages in contrib
> ═══════════════════════
>
> `ob-julia.el' by G. Jay Kerns
> ─────────────────────────────
>
>   [Julia] is a new programming language.
>
>   `ob-julia.el' provides Org Babel support for evaluating Julia source
>   code.
>
>
>   [Julia] http://julialang.org/
>
>
> `ob-mathomatic.el' by Luis Anaya
> ────────────────────────────────
>
>   [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.
>
>
>   [mathomatic] http://www.mathomatic.org/
>
>
> `ob-tcl.el' by Luis Anaya
> ─────────────────────────
>
>   `ob-tcl.el' provides Org Babel support for evaluating [Tcl] source
>   code.
>
>
>   [Tcl] http://www.tcl.tk/
>
>
> `org-bullets.el' by Evgeni Sabof
> ────────────────────────────────
>
>   Display bullets instead of stars for headlines.
>
>   Also see [this updated FAQ] on how to display another character than
>   "*" for starting headlines.
>
>
>   [this updated FAQ] http://orgmode.org/worg/org-faq.html#sec-8-12
>
>
> `org-favtable.el' by Marc-Oliver Ihm
> ────────────────────────────────────
>
>   `org-favtable.el' helps you to create and update a table of favorite
>   locations in org, keeping the most frequently visited lines right at
>   the top.  This table is called "favtable".  See the documentation on
>   [Worg].
>
>
>   [Worg] http://orgmode.org/worg/org-contrib/org-favtable.html
>
>
> `ox-confluence.el' by Sébastien Delafond
> ────────────────────────────────────────
>
>   `ox-confluence.el' lets you convert Org files to [Confluence Wiki]
>   files.
>
>
>   [Confluence Wiki]
>   https://confluence.atlassian.com/display/DOC/Confluence%2BWiki%2BMarkup
>
>
> `ox-deck.el' and `ox-s5.el' by Rick Frankel
> ───────────────────────────────────────────
>
>   [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'.
>
>
>   [deck.js] http://imakewebthings.com/deck.js/
>
>   [s5] http://meyerweb.com/eric/tools/s5/
>
>
> `ox-groff.el' by Luis Anaya and Nicolas Goaziou
> ───────────────────────────────────────────────
>
>   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.
>
>
>   [groff] http://www.gnu.org/software/groff/
>
>
> `ox-koma-letter.el' by Nicolas Goaziou and Alan Schmitt
> ───────────────────────────────────────────────────────
>
>   This back-end allow to export Org pages to the `KOMA Scrlttr2' format.
>
>
> `ox-rss.el' by Bastien
> ──────────────────────
>
>   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.
>
>
> New features
> ════════════
>
> Export
> ──────
>
> New export generic options
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   If you use Org exporter, we advise you to re-read [the manual section
>   about it].  It has been updated and includes new options.
>
>   Among the new/updated export options, three are of particular
>   importance:
>
>   org-export-allow-bind-keywords: This option replaces the old option
>       `org-export-allow-BIND' and the default value is `nil', not
>       `confirm'.  You will need to explicitely set this to `t' in your
>       initialization file if you want to allow `#+BIND' keywords.
>
>   org-export-with-planning: This new option controls the export of
>       `SCHEDULED:, DEADLINE:, CLOSED:' lines, and planning information is
>       now skipped by default during export.  This use to be the job of
>       org-export-with-timestamps, but this latter option has been given a
>       new role: it controls the export of /standalone time-stamps/.  When
>       set to `nil', Org will not export active and inactive time-stamps
>       standing on a line by themselves or within a paragraph that only
>       contains time-stamps.
>
>   To check if an option has been introduced or its default value changed
>   in Org 8.0, do `C-h v [option] RET' and check if the documentation
>   says that the variable has been introduced (or changed) in version
>   24.4 of Emacs.
>
>
>   [the manual section about it] http://orgmode.org/org.html#Exporting
>
>
> Enhanced default stylesheet for the HTML exporter
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   See the new default value of org-html-style-default.
>
>
> New tags, classes and ids for the HTML exporter
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   See the new default value of org-html-divs.
>
>
> Support for tikz pictures in LaTeX export
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>
> `org-man.el': New export function for "man" links
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>
> `org-docview.el': New export function for docview links
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>
> Structure editing
> ─────────────────
>
> `C-u C-u M-RET' inserts a heading at the end of the parent subtree
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>
> Cycling to the `CONTENTS' view keeps inline tasks folded
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   org-cycle-hook as a new function org-cycle-hide-inline-tasks which
>   prevents the display of inline tasks when showing the content of a
>   subtree.
>
>
> `C-c -' in a region makes a list item for each line
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   This is the opposite of the previous behavior, where `C-c -' on a
>   region would create one item for the whole region, and where `C-u C-c
>   -' would create an item for each line.  Now `C-c -' on the selected
>   region creates an item per line, and `C-u C-c -' creates a single item
>   for the whole region.
>
>
> When transposing words, markup characters are now part of the words
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   In Emacs, you can transpose words with `M-t'.  Transposing `*these*
>   _words__' will preserve markup.
>
>
> New command org-set-property-and-value bound to `C-c C-x P'
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   This command allows you to quickly add both the property and its
>   value.  It is useful in buffers where there are many properties and
>   where `C-c C-x p' can slow down the flow of editing too much.
>
>
> New commands org-next-block and org-previous-block
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   These commands allow you to go to the previous block (`C-c M-b' or the
>   speedy key `B') or to the next block (`C-c M-f' or the speedy key
>   `F'.)
>
>
> New commands org-drag-line-forward and org-drag-line-backward
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   These commands emulate the old behavior of `M-<down>' and `M-<up>' but
>   are now bound to `S-M-<down>' and `S-M-<up>' respectively, since
>   `M-<down>' and `M-<up>' now drag the whole element at point (a
>   paragraph, a table, etc.)  forward and backward.
>
>
> When a list item has a checkbox, inserting a new item uses a checkbox too
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>
> When sorting entries/items, only the description of links is considered
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   Now Org will sort this list
>
>   ╭────
>   │ - [[http://abc.org][B]]
>   │ - [[http://def.org][A]]
>   ╰────
>
>   like this:
>
>   ╭────
>   │ - [[http://def.org][A]]
>   │ - [[http://abc.org][B]]
>   ╰────
>
>   by comparing the descriptions, not the links.  Same when sorting
>   headlines instead of list items.
>
>
> New option `orgstruct-heading-prefix-regexp'
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   For example, setting this option to "^;;; " in Emacs lisp files and
>   using `orgstruct-mode' in those files will allow you to cycle through
>   visibility states as if lines starting with ";;; *…" where headlines.
>
>   In general, you want to set `orgstruct-heading-prefix-regexp' as a
>   file local variable.
>
>
> New behavior of org-clone-subtree-with-time-shift
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   The default is to only ask for a number of clones.  When called with a
>   universal prefix argument `C-u', it will prompt you for a time-shift
>   only if there is a time-stamp in the task you want to clone.
>
>
> New option org-agenda-restriction-lock-highlight-subtree
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   This defaults to `t' so that the whole subtree is highlighted when you
>   restrict the agenda view to it with `C-c C-x <' (or the speed command
>   `<').  The default setting helps ensuring that you are not adding
>   tasks after the restricted region.  If you find this highlighting too
>   intrusive, set this option to `nil'.
>
>
> New option org-closed-keep-when-no-todo
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   When switching back from a `DONE' keyword to a `TODO' keyword, Org now
>   removes the `CLOSED' planning information, if any.  It also removes
>   this information when going back to a non-TODO state (e.g., with `C-c
>   C-t SPC').  If you want to keep the `CLOSED' planning information when
>   removing the TODO keyword, set org-closed-keep-when-no-todo to `t'.
>
>
> New option org-image-actual-width
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   This option allows you to change the width of in-buffer displayed
>   images.  The default is to use the actual width of the image, but you
>   can use a fixed value for all images, or fall back on an attribute
>   like
>
>   ╭────
>   │ #+attr_html: :width 300px
>   ╰────
>
>
> Scheduled/deadline
> ──────────────────
>
> Implement "delay" cookies for scheduled items
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   If you want to delay the display of a scheduled task in the agenda,
>   you can now use a delay cookie like this: `SCHEDULED: <2004-12-25 Sat
>   -2d>'.  The task is still scheduled on the 25th but will appear in
>   your agenda starting from two days later (i.e. from March 27th.)
>
>   Imagine for example that your co-workers are not done in due time and
>   tell you "we need two more days".  In that case, you may want to delay
>   the display of the task in your agenda by two days, but you still want
>   the task to appear as scheduled on March 25th.
>
>   In case the task contains a repeater, the delay is considered to
>   affect all occurrences; if you want the delay to only affect the first
>   scheduled occurrence of the task, use `--2d' instead.  See
>   org-scheduled-delay-days and
>   org-agenda-skip-scheduled-delay-if-deadline for details on how to
>   control this globally or per agenda.
>
>
> Use `C-u C-u C-s' will insert a delay cookie for scheduled tasks
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   See the previous section for why delay cookies may be useful.
>
>
> Use `C-u C-u C-d' will insert a warning delay for deadline tasks
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   `C-u C-u C-d' now inserts a warning delay to deadlines.
>
>
> Calendar, diary and appts
> ─────────────────────────
>
> New variable org-read-date-minibuffer-local-map
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   By default, this new local map uses "." to go to today's date, like in
>   the normal `M-x calendar RET'.  If you want to deactivate this and to
>   reassign the "@" key to `calendar-goto-today', use this:
>
>   ╭────
>   │ ;; Unbind "." in Org's calendar:
>   │ (define-key org-read-date-minibuffer-local-map (kbd ".") nil)
>   │
>   │ ;; Bind "@" to `calendar-goto-today':
>   │ (define-key org-read-date-minibuffer-local-map
>   │             (kbd "@")
>   │             (lambda () (interactive) (org-eval-in-calendar
> '(calendar-goto-today))))
>   ╰────
>
>
> In Org's calendar, `!' displays diary entries of the date at point
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   This is useful when you want to check if you don't already have an
>   appointment when setting new ones with `C-c .' or `C-c s'.  `!' will
>   call `diary-view-entries' and display the diary in a separate buffer.
>
>
> org-diary: only keep the descriptions of links
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   org-diary returns diary information from Org files, but it returns it
>   in a diary buffer, not in an Org mode buffer.  When links are
>   displayed, only show their description, not the full links.
>
>
> Agenda
> ──────
>
> New agenda type `agenda*' and entry types `:scheduled* :deadline*'
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   When defining agenda custom commands, you can now use `agenda*': this
>   will list entries that have both a date and a time.  This is useful
>   when you want to build a list of appointments.
>
>   You can also set org-agenda-entry-types either globally or locally in
>   each agenda custom command and use `:timestamp*' and/or `:deadline*'
>   there.
>
>   Another place where this is useful is your `.diary' file:
>
>   ╭────
>   │ %%(org-diary :scheduled*) ~/org/rdv.org
>   ╰────
>
>   This will list only entries from `~/org/rdv.org' that are scheduled
>   with a time value (i.e. appointments).
>
>
> New agenda sorting strategies
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   org-agenda-sorting-strategy allows these new sorting strategies:
>
>   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
>    Strategy        Explanations
>   ──────────────────────────────────────────────────────────
>    timestamp-up    Sort by any timestamp, early first
>    timestamp-down  Sort by any timestamp, late first
>    scheduled-up    Sort by scheduled timestamp, early first
>    scheduled-down  Sort by scheduled timestamp, late first
>    deadline-up     Sort by deadline timestamp, early first
>    deadline-down   Sort by deadline timestamp, late first
>    ts-up           Sort by active timestamp, early first
>    ts-down         Sort by active timestamp, late first
>    tsia-up         Sort by inactive timestamp, early first
>    tsia-down       Sort by inactive timestamp, late first
>   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
>
>
> New options to limit the number of agenda entries
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   You can now limit the number of entries in an agenda view.  This is
>   different from filters: filters only /hide/ the entries in the agenda,
>   while limits are set while generating the list of agenda entries.
>
>   These new options are available:
>
>   org-agenda-max-entries: limit by number of entries.
>   org-agenda-max-todos: limit by number of TODOs.
>   org-agenda-max-tags: limit by number of tagged entries.
>   org-agenda-max-effort: limit by effort (minutes).
>
>   For example, if you locally set org-agenda-max-todos to 3 in an agenda
>   view, the agenda will be limited to the first three todos.  Other entries
>   without a TODO keyword or beyond the third TODO headline will be ignored.
>
>   When setting a limit (e.g. about an effort's sum), the default behavior
>   is to exclude entries that cannot be checked against (e.g. entries that
>   have no effort property.)  To include other entries too, you can set the
>   limit to a negative number.  For example (setq org-agenda-max-tags 3)
>   will not show the fourth tagged headline (and beyond), but it will also
>   show non-tagged headlines.
>
>
> `~' in agenda view sets temporary limits
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   You can hit `~' in the agenda to temporarily set limits: this will
>   regenerate the agenda as if the limits were set.  This is useful for
>   example when you want to only see a list of `N' tasks, or a list of
>   tasks that take only `N' minutes.
>
>
> "=" in agenda view filters by regular expressions
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   You can now filter agenda entries by regular expressions using `='.
>   `C-u =' will filter entries out.  Regexp filters are cumulative.  You
>   can set org-agenda-regexp-filter-preset to suit your needs in each
>   agenda view.
>
>
> `|' in agenda view resets all filters
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   Since it's common to combine tag filters, category filters, and now
>   regexp filters, there is a new command `|' to reset all filters at
>   once.
>
>
> Allow writing an agenda to an `.org' file
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   You can now write an agenda view to an `.org' file.  It copies the
>   headlines and their content (but not subheadings) into the new file.
>
>   This is useful when you want to quickly share an agenda containing the
>   full list of notes.
>
>
> New commands to drag an agenda line forward (`M-<down>') or backard
> (`M-<up>')
>
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   It sometimes handy to move agenda lines around, just to quickly
>   reorganize your tasks, or maybe before saving the agenda to a file.
>   Now you can use `M-<down>' and `M-<up>' to move the line forward or
>   backward.
>
>   This does not persist after a refresh of the agenda, and this does not
>   change the `.org' files who contribute to the agenda.
>
>
> Use `%s' for displaying "breadcrumbs" in the agenda view
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   org-agenda-prefix-format now allows to use a `%b' formatter to tell
>   Org to display "breadcrumbs" in the agenda view.
>
>   This is useful when you want to display the task hierarchy in your
>   agenda.
>
>
> Use `%l' for displaying the headline's level in the agenda view
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   org-agenda-prefix-format allows to use a `%l' formatter to tell Org to
>   display entries with additional spaces corresponding to their level in
>   the outline tree.
>
>
> org-agenda-write will ask before overwriting an existing file
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   `M-x org-agenda-write RET' (or `C-c C-w' from an agenda buffer) used
>   to overwrite preexisting file with the same name without confirmation.
>   It now asks for a confirmation.
>
>
> New commands `M-m' and `M-*' to toggle (all) mark(s) for bulk action
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   org-agenda-bulk-toggle: this command is bound to `M-m' and toggles the
>       mark of the entry at point.
>
>   org-agenda-bulk-toggle-all: this command is bound to `M-*' and toggles
>       all the marks in the current agenda.
>
>
> New option org-agenda-search-view-max-outline-level
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   This option sets the maximum outline level to display in search view.
>   E.g. when this is set to 1, the search view will only show headlines
>   of level 1.
>
>
> New option org-agenda-todo-ignore-time-comparison-use-seconds
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   This allows to compare times using seconds instead of days when
>   honoring options like `org-agenda-todo-ignore-*' in the agenda
>   display.
>
>
> New option org-agenda-entry-text-leaders
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   This allows you to get rid of the ">" character that gets added in
>   front of entries excerpts when hitting `E' in the agenda view.
>
>
> New formatting string for past deadlines in org-agenda-deadline-leaders
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   The default formatting for past deadlines is `"%2d d. ago: "', which
>   makes it explicit that the deadline is in the past.  You can configure
>   this via org-agenda-deadline-leaders.  Note that the width of the
>   formatting string is important to keep the agenda alignment clean.
>
>
> New allowed value `repeated-after-deadline' for
> org-agenda-skip-scheduled-if-deadline-is-shown
>
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   When org-agenda-skip-scheduled-if-deadline-is-shown is set to
>   `repeated-after-deadline', the agenda will skip scheduled items if
>   they are repeated beyond the current dealine.
>
>
> New option for org-agenda-skip-deadline-prewarning-if-scheduled
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   This variable may be set to nil, t, the symbol `pre-scheduled', or a
>   number which will then give the number of days before the actual
>   deadline when the prewarnings should resume.  The symbol
>   `pre-scheduled' eliminates the deadline prewarning only prior to the
>   scheduled date.
>
>   Read the full docstring for details.
>
>
> org-class now supports holiday strings in the skip-weeks parameter
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   For example, this task will now be skipped only on new year's day:
>
>   ╭────
>   │ * Task
>   │   <%%(org-class 2012 1 1 2013 12 12 2 "New Year's Day")>
>   ╰────
>
>
> Capture
> ───────
>
> Allow `C-1' as a prefix for org-agenda-capture and org-capture
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   With a `C-1' prefix, the capture mechanism will use the `HH:MM' value
>   at point (if any) or the current `HH:MM' time as the default time for
>   the capture template.
>
>
> Expand keywords within %(sexp) placeholder in capture templates
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   If you use a `%:keyword' construct within a `%(sexp)' construct, Org
>   will expand the keywords before expanding the `%(sexp)'.
>
>
> Allow to contextualize capture (and agenda) commands by checking the name
> of the buffer
>
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   org-capture-templates-contexts and org-agenda-custom-commands-contexts
>   allow you to define what capture templates and what agenda commands
>   should be available in various contexts.  It is now possible for the
>   context to check against the name of the buffer.
>
>
> Tag groups
> ──────────
>
>   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
>   combinaison of those tags.)
>
>   You can use group tags for sparse tree in an Org buffer, for creating
>   agenda views, and for filtering.
>
>   See [http://orgmode.org/org.html#Tag-groups] for details.
>
>
> Links
> ─────
>
> `C-u C-u M-x org-store-link RET' will ignore non-core link functions
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   Org knows how to store links from Org buffers, from info files and
>   from other Emacs buffers.  Org can be taught how to store links from
>   any buffer through new link protocols (see ["Adding hyperlink types"]
>   in the manual.)
>
>   Sometimes you want Org to ignore added link protocols and store the
>   link as if the protocol was not known.
>
>   You can now do this with `C-u C-u M-x org-store-link RET'.
>
>
>   ["Adding hyperlink types"]
>   http://orgmode.org/org.html#Adding-hyperlink-types
>
>
> `C-u C-u C-u M-x org-store-link RET' on an active region will store links
> for each lines
>
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   Imagine for example that you want to store a link for every message in
>   a Gnus summary buffer.  In that case `C-x h C-u C-u C-u M-x
>   org-store-link RET' will store a link for every line (i.e. message) if
>   the region is active.
>
>
> `C-c C-M-l' will add a default description for links which don't have one
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   `C-c C-M-l' inserts all stored links.  If a link does not have a
>   description, this command now adds a default one, so that we are not
>   mixing with-description and without-description links when inserting
>   them.
>
>
> No curly braces to bracket links within internal links
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   When storing a link to a headline like
>
>   ╭────
>   │ * See [[http://orgmode.org][Org website]]
>   ╰────
>
>   org-store-link used to convert the square brackets into curly
>   brackets.  It does not anymore, taking the link description or the
>   link path, when there is no description.
>
>
> Table
> ─────
>
> Switching between #+TBLFM lines
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   If you have several `#+TBLFM' lines below a table, `C-c C-c' on a line
>   will apply the formulas from this line, and `C-c C-c' on another line
>   will apply those other formulas.
>
>
> You now use "nan" for empty fields in Calc formulas
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   If empty fields are of interest, it is recommended to reread the
>   section [3.5.2 Formula syntax for Calc] of the manual because the
>   description for the mode strings has been clarified and new examples
>   have been added towards the end.
>
>
>   [3.5.2 Formula syntax for Calc]
>   http://orgmode.org/org.html#Formula-syntax-for-Calc
>
>
> Handle localized time-stamps in formulas evaluation
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   If your `LOCALE' is set so that Org time-stamps use another language
>   than english, and if you make time computations in Org's table, it now
>   works by internally converting the time-stamps with a temporary
>   `LOCALE=C' before doing computation.
>
>
> New lookup functions
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   There are now three lookup functions:
>
>   • org-loopup-first
>   • org-loopup-last
>   • org-loopup-all
>
>   See [the manual] for details.
>
>
>   [the manual] http://orgmode.org/org.html#Lookup-functions
>
>
> Startup keywords
> ────────────────
>
>   These new startup keywords are now available:
>
>
> ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
>    Startup keyword                   Option
>
> ───────────────────────────────────────────────────────────────────────────────
>    `#+STARTUP: logdrawer'            `(setq org-log-into-drawer t)'
>    `#+STARTUP: nologdrawer'          `(setq org-log-into-drawer nil)'
>
> ───────────────────────────────────────────────────────────────────────────────
>    `#+STARTUP: logstatesreversed'    `(setq org-log-states-order-reversed
> t)'
>    `#+STARTUP: nologstatesreversed'  `(setq org-log-states-order-reversed
> nil)'
>
> ───────────────────────────────────────────────────────────────────────────────
>    `#+STARTUP: latexpreview'         `(setq org-startup-with-latex-preview
> t)'
>    `#+STARTUP: nolatexpreview'       `(setq org-startup-with-latex-preview
> nil)'
>
> ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
>
>
> Clocking
> ────────
>
> New option org-clock-rounding-minutes
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   E.g. if org-clock-rounding-minutes is set to 5, time is 14:47 and you
>   clock in: then the clock starts at 14:45.  If you clock out within the
>   next 5 minutes, the clock line will be removed; if you clock out 8
>   minutes after your clocked in, the clock out time will be 14:50.
>
>
> New option org-time-clocksum-use-effort-durations
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   When non-nil, `C-c C-x C-d' uses effort durations.  E.g., by default,
>   one day is considered to be a 8 hours effort, so a task that has been
>   clocked for 16 hours will be displayed as during 2 days in the clock
>   display or in the clocktable.
>
>   See org-effort-durations on how to set effort durations and
>   org-time-clocksum-format for more on time clock formats.
>
>
> New option org-clock-x11idle-program-name
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   This allows to set the name of the program which prints X11 idle time
>   in milliseconds.  The default is to use `x11idle'.
>
>
> New option org-use-last-clock-out-time-as-effective-time
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   When non-nil, use the last clock out time for org-todo.  Note that
>   this option has precedence over the combined use of
>   org-use-effective-time and org-extend-today-until.
>
>
> `S-<left/right>' on a clocksum column will update the sum by updating the
> last clock
>
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>
> `C-u 3 C-S-<up/down>' will update clock timestamps synchronously by 3 units
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>
> New parameter `:wstart' for clocktables to define the week start day
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>
> New parameter `:mstart' to state the starting day of the month
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>
> Allow relative times in clocktable tstart and tend options
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>
> The clocktable summary is now a caption
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>
> `:tstart' and `:tend' and friends allow relative times like "<-1w>" or
> "<now>"
>
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>
> Babel
> ─────
>
> You can now use `C-c C-k' for org-edit-src-abort
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   This allows you to quickly cancel editing a source block.
>
>
> `C-u C-u M-x org-babel-tangle RET' tangles by the target file of the block
> at point
>
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   This is handy if you want to tangle all source code blocks that have
>   the same target than the block at point.
>
>
> New options for auto-saving the base buffer or the source block editing
> buffer
>
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   When org-edit-src-turn-on-auto-save is set to `t', editing a source
>   block in a new window will turn on `auto-save-mode' and save the code
>   in a new file under the same directory than the base Org file.
>
>   When org-edit-src-auto-save-idle-delay is set to a number of minutes
>   `N', the base Org buffer will be saved after this number of minutes of
>   idle time.
>
>
> New `:post' header argument post-processes results
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   This header argument may be used to pass the results of the current
>   code block through another code block for post-processing.  See the
>   manual for a usage example.
>
>
> Commented out heading are ignored when collecting blocks for tangling
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   If you comment out a heading (with `C-c ;' anywhere on the heading or
>   in the subtree), code blocks from within this heading are now ignored
>   when collecting blocks for tangling.
>
>
> New option org-babel-hash-show-time to show a time-stamp in the result hash
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>
> Do not ask for confirmation if cached value is current
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   Do not run org-babel-confirm-evaluate if source block has a cache and
>   the cache value is current as there is no evaluation involved in this
>   case.
>
>
> `ob-sql.el' and `ob-python.el' have been improved.
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>
> New Babel files only need to `(require 'ob)'
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>
>   When writing a new Babel file, you now only need to use `(require
>   'ob)' instead of requiring each Babel library one by one.
>
>
> Faces
> ─────
>
>   • 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
>
>
> Miscellaneous
> ═════════════
>
>   • New speedy key `s' pour org-narrow-to-subtree
>   • Handling of org-html-table-row has been updated (incompatible change)
>   • org-export-html-table-tag is replaced by
> org-html-table-default-attributes
>   • Support using `git-annex' with Org attachments
>   • org-protocol: Pass optional value using query in url to capture from
> protocol
>   • When the refile history is empty, use the current filename as default
>   • When you cannot change the TODO state of a task, Org displays the
>     blocking task
>   • New option org-mobile-allpriorities
>   • org-bibtex.el now use `visual-line-mode' instead of the deprecated
>     `longlines-mode'
>   • org-format-latex-options allows to set the foreground/background
>     colors automatically
>   • New option org-archive-file-header-format
>   • New "neg" entity in org-entities
>   • New function org-docview-export to export docview links
>   • New `:eps' header argument for ditaa code blocks
>   • New option org-gnus-no-server to start Gnus with `gnus-no-server'
>   • Org is now distributed with `htmlize.el' version 1.43
>   • `org-drill.el' has been updated to version 2.3.7
>   • `org-mac-iCal.el' now supports MacOSX version up to 10.8
>   • Various improvements to `org-contacts.el' and `orgpan.el'
>
>
> Outside Org
> ═══════════
>
> Spanish translation of the Org guide by David Arroyo Menéndez
> ─────────────────────────────────────────────────────────────
>
>   David (and others) translated the Org compact guide in spanish:
>
>   You can read the [PDF guide].
>
>
>   [PDF guide] http://orgmode.org/worg/orgguide/orgguide.es.pdf
>
>
> `poporg.el' and `outorg.el'
> ───────────────────────────
>
>   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:
>   [http://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']
>
>
>   ["Modern conventions for Emacs Lisp files"]
>   http://youtu.be/nqE6YxlY0rw
>
>   [Exploring Bernt Hansen's Org-mode tutorial with 'navi-mode']
>   http://www.youtube.com/watch?v%3DII-xYw5VGFM
>
>
> MobileOrg for iOS
> ─────────────────
>
>   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].
>
>
>   [on github] https://github.com/MobileOrg/mobileorg/issues
>
>
> Thanks you all!
> ════════=======
>
> Here is a list of people we need to thanks for this release:
>
> Aaron Ecay, Abdó Roig-Maranges, Achim Gratz, Adam Spiers, Alan Schmitt,
> Alexander Willand, Andreas Leha, Andreas Röhler, Andrew M. Nuxoll, Arun
> Persaud, Bernd Haug, Bernt Hansen, Bill Day, Bill White, Brian van den
> Broek, Carsten Dominik, Charles C. Berry, Christian Egli, Christian Moe,
> Christophe Junke, Christopher Schmidt, Christopher Witte, Chuck Berry,
> Daniel Clemente, Daniel Dehennin, Dave Abrahams, David Kincaid, Derek
> Upham, Enda, Eric Abrahamsen, Eric S Fraga, Eric Schulte, Esben Stien,
> Fabrice Popineau, Feng Shu, Florian Beck, Francesco Pizzolante, Frank
> Fischer, Frank Terbeck, François Pinard, G. Jay Kerns, Gaizka Villate, Gary
> Oberbrunner, Greg Minshall, Gregor Kappler, Grégoire Jadi, Henry Atting,
> Hiroshi Saito, Hrvoje Nikšić, Ian Barton, Ingo Lohmar, Ippei FURUHASHI,
> Ivan Vilata i Balaguer, J. David Boyd, Jae Hee Lee, Jambunathan K, James
> Harkins, Jarmo Hurri, John Foerch, John Hendy, John J Foerch, John Wiegley,
> Jonas Bernoulli, Jonathan Leech-Pepin, Joost Helberg, Justus Piater, Kalev
> Takkis, Ken Williams, Kevin Buchs, Kodi Arfer, Kyle Machulis, Le Wang, Leo
> Liu, Luca Sabbatini, Luis Anaya, Marcel van der Boom, Mark Edgington, Matt
> Lundin, Max Mikhanosha, Michael Brand, Michael Crouch, Michael Gauland,
> Michael Heerdegen, Michael Strey, Mirko Vukovic, Myles English, Nick Dokos,
> Nicolas Goaziou, Nicolas Richard, Oliver Večerník, Paul Sexton, Peder
> Stray, Peter Münster, Philipp Kroos, Raghavendra D Prabhu, Rainer M. Krug,
> Rainer Stengele, Rasmus, Rene, Richard Stanton, Rick Frankel, Rick Hanson,
> Robert Goldman, Robert Horn, Robert Klein, Roland Winkler, Ryo TAKAISHI,
> Rémi Vanicat, Rüdiger Sonderfeld, Sacha Chua, Samuel Loury, Samuel Wales,
> Sean O'Halpin, Sébastien Vauban, Simon Thum, Stefan Monnier, Stefan
> Vollmar, Stephen Eglen, Steve Purcell, Suhail Shergill, Suvayu Ali,
> T.F. Torrey, Thomas S. Dye, Thorsten Jolitz, Toby S. Cubitt, Tokuya
> Kameshima, Tony Day, Viktor Rosenfeld, Vincent Beffara, Vladimir Lomov,
> Wanrong Lin, William Lechelle, Xiao-Yong Jin, Xue Fuqiao, Yann Hodique,
> Yasushi SHOJI, Zech, sabof, Дядов Васил Стоянов.
>
>
> --
>  Bastien
>
>

[-- Attachment #2: Type: text/html, Size: 65715 bytes --]

^ permalink raw reply	[flat|nested] 40+ messages in thread

* Appeal to donors (Re: Release 8.0)
  2013-04-18 16:41 Release 8.0 Bastien
  2013-04-18 16:58 ` Jambunathan K
  2013-04-18 17:15 ` Anthony Lander
@ 2013-04-18 17:28 ` Jambunathan K
  2013-04-19 15:42   ` OAppeal " Wes Hardaker
  2013-04-18 17:41 ` Release 8.0 Neuwirth Erich
                   ` (10 subsequent siblings)
  13 siblings, 1 reply; 40+ messages in thread
From: Jambunathan K @ 2013-04-18 17:28 UTC (permalink / raw)
  To: emacs-orgmode


> I'm releasing Org 8.0.

Donors, please pause before you make any donations.  

Before apportioning all of your donations to a single individual, just
pause for a moment.  

Is Orgmode work of a single individual or a community effort.

1. Split your donation in proportion to the contribution of each
   contributor.  

   a) Do you want to bear a part of hosting charges of Orgmode.org
      webservers?

   b) Do you want to support a specific individual developer.

   c) Do you want to show your appreciation of one of the many regulars
      in this list whose help and response you can take it for granted.

   d) Which portions of Orgmode you rely on - Outlining/Core Org,
      Agenda, Clocking, Exporter, Babel.  Do you know the authors of
      these modules.

   e) How about people who update official and unofficial documentation
      and write Worg tutorials.

2. Make a targeted donation right and approach the contributor directly
   on how the funds can be transfer funds to him.  If this not possible
   and you want to make an umbrella donation to the project, insist
   upfront on how you would like your donation to be split.

Jambunathan K.

^ permalink raw reply	[flat|nested] 40+ messages in thread

* Re: Release 8.0
  2013-04-18 16:58 ` Jambunathan K
@ 2013-04-18 17:37   ` Bastien
  2013-04-18 18:06     ` Jambunathan K
  0 siblings, 1 reply; 40+ messages in thread
From: Bastien @ 2013-04-18 17:37 UTC (permalink / raw)
  To: Jambunathan K; +Cc: emacs-orgmode

Hi Jambunathan,

Jambunathan K <kjambunathan@gmail.com> writes:

> Could you please correct the headers to ox-html.el and ox-odt.el.

I corrected the header for ox-html.el: the header said you were the
only author while it's clear half of the code was simply copied from
Carsten.  I added Carsten as the author.

> I have not assigned the rights to my changes to FSF.  These files -
> due to Emacs project policy - cannot be part of Emacs.

RMS confirmed that you changes were assigned in a private email that
we both received this morning.  It's your right to disagree, but first
solve this dispute with the FSF before asking me to obey to you.  I'm
following the advice of the FSF for now.

-- 
 Bastien

^ permalink raw reply	[flat|nested] 40+ messages in thread

* Re: Release 8.0
  2013-04-18 16:41 Release 8.0 Bastien
                   ` (2 preceding siblings ...)
  2013-04-18 17:28 ` Appeal to donors (Re: Release 8.0) Jambunathan K
@ 2013-04-18 17:41 ` Neuwirth Erich
  2013-04-18 18:01   ` Achim Gratz
  2013-04-18 17:43 ` François Pinard
                   ` (9 subsequent siblings)
  13 siblings, 1 reply; 40+ messages in thread
From: Neuwirth Erich @ 2013-04-18 17:41 UTC (permalink / raw)
  To: Bastien, emacs-orgmode@gnu.org Mode

I compiled from the repository after the announcement.
On my Mac (OSX 10.8.3, Emacs 24.3.1) the test for maxima still fail.
I reported this a few weeks ago.


Ran 443 tests, 436 results as expected, 7 unexpected (2013-04-18 19:38:30+0200)
5 expected failures

7 unexpected results:
   FAILED  ob-maxima/integer-input
   FAILED  ob-maxima/list-input
   FAILED  ob-maxima/matrix-output
   FAILED  ob-maxima/simple-list-input
   FAILED  ob-maxima/string-input
   FAILED  ob-maxima/table-input1
   FAILED  ob-maxima/table-input2

make[1]: *** [test-dirty] Error 1

On Apr 18, 2013, at 6:41 PM, Bastien <bzg@gnu.org> wrote:

> Dear all,
> 
> I'm releasing Org 8.0.
> 
> See the release notes below or at http://orgmode.org/Changes.html
> 
> This release is potentially the most disruptive release since long,
> so please don't use it in production before you can carefully review
> the release notes and update your configuration -- especially with
> respect to export features.
> 
> I would like to thank you all again for your patience, and special
> thanks to Nicolas who is just great to work with.  I'm happy to see
> his code finally widely available for all Org users, not just the
> happy few.
> 
> Enjoy!
> 
> 			    ━━━━━━━━━━━━━━━━
> 				ORG 8.0
> 			    ━━━━━━━━━━━━━━━━
> 
> 
> Installation
> ════════════
> 
>  Installation instructions have been updated and simplified.
> 
>  If you have troubles installing or updating Org, focus on these
>  instructions:
> 
>  • when updating via a `.zip/.tar.gz' file, you only need to set the
>    `load-path' in your `.emacs'.  Set it before any other Org
>    customization that would call autoloaded Org functions.
> 
>  • when updating by pulling Org's Git repository, make sure to create
>    the correct autoloads.  You can do this by running `~$ make
>    autoloads' (to only create the autoloads) or by running `~$ make'
>    (to also compile the Emacs lisp files.)  `~$ make help' and `~$ make
>    helpall' gives you detailed explanations.
> 
>  • when updating through ELPA (either from GNU ELPA or from Org ELPA),
>    you have to install Org's ELPA package in a session where no Org
>    function has been called already.
> 
>  When in doubt, run `M-x org-version RET' and see if you have a
>  mixed-up installation.
> 
>  See [http://orgmode.org/org.html#Installation] for details.
> 
> 
> Incompatible changes
> ════════════════════
> 
>  Org 8.0 is the most disruptive major version of Org.
> 
>  If you configured export options, you will have to update some of
>  them.
> 
>  If you used `#+ATTR_*' keywords, the syntax of the attributes changed
>  and you will have to update them.
> 
>  Below is a list of changes for which you need to take action.
> 
>  See [http://orgmode.org/worg/org-8.0.html] for the most recent version
>  of this list and for detailed instructions on how to migrate.
> 
> 
> New export engine
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  Org 8.0 comes with a new export engine written by Nicolas Goaziou.
>  This export engine relies on `org-element.el' (Org's syntax parser),
>  which was already in Org's core.  This new export engine triggered the
>  rewriting of /all/ export back-ends.
> 
>  The most visible change is the export dispatcher, accessible through
>  the keybinding `C-c C-e'.  By default, this menu only shows some of
>  the built-in export formats, but you can add more formats by loading
>  them directly (e.g., `(require 'ox-texinfo)' or by configuring the
>  option org-export-backends.
> 
>  More contributed back-ends are available from the `contrib/'
>  directory, the corresponding files start with the `ox-' prefix.
> 
>  If you customized an export back-end (like HTML or LaTeX), you will
>  need to rename some options so that your customization is not lost.
>  Typically, an option starting with `org-export-html-' is now named
>  `org-html-'.  See the manual for details and check [this Worg page]
>  for directions.
> 
> 
>  [this Worg page] http://orgmode.org/worg/org-8.0.html
> 
> 
> New syntax for #+ATTR_HTML/LaTeX/… options
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  ╭────
>  │ #+ATTR_HTML width="200px"
>  ╰────
> 
>  should now be written
> 
>  ╭────
>  │ #+ATTR_HTML :width 200px
>  ╰────
> 
>  Keywords like `#+ATTR_HTML' and `#+ATTR_LaTeX' are defined in their
>  respective back-ends, and the list of supported parameters depends on
>  each backend.  See Org's manual for details.
> 
> 
> `org-remember.el' has been removed
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  You cannot use `remember.el' anymore to capture notes.
> 
>  Support for remember templates has been obsoleted since long, it is
>  now fully removed.
> 
>  Use `M-x org-capture-import-remember-templates RET' to import your
>  remember templates into capture templates.
> 
> 
> `org-jsinfo.el' has been merged into `ox-html.el'
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  If you were requiring `ox-jsinfo.el' in your `.emacs.el' file, you
>  will have to remove this requirement from your initialization file.
> 
> 
> Note for third-party developers
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  The name of the files for export back-end have changed: we now use the
>  prefix `ox-' for those files (like we use the `ob-' prefix for Babel
>  files.)  For example `org-html.el' is now `ox-html.el'.
> 
>  If your code relies on these files, please update the names in your
>  code.
> 
> 
> Packages moved from core to contrib
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  Since packages in Org's core are meant to be part of GNU Emacs, we try
>  to be minimalist when it comes to adding files into core.  For 8.0, we
>  moved some contributions into the `contrib/' directory.
> 
>  The rationale for deciding that these files should live in `contrib/'
>  is either because they rely on third-part softwares that are not
>  included in Emacs, or because they are not targetting a significant
>  user-base.
> 
>  • org-colview-xemacs.el
>  • org-mac-message.el
>  • org-mew.el
>  • org-wl.el
>  • ox-freedmind.el
>  • ox-taskjuggler.el
> 
>  Note that `ox-freedmind.el' has been rewritten by Jambunathan,
>  `org-mew.el' has been enhanced by Tokuya Kameshima and
>  `ox-taskjuggler.el' by Nicolas Goaziou and others.
> 
>  Also, the Taskjuggler exporter now uses TJ3 by default.  John Hendy
>  wrote [a tutorial on Worg] for the TJ3 export.
> 
> 
>  [a tutorial on Worg]
>  http://orgmode.org/worg/org-tutorials/org-taskjuggler3.html
> 
> 
> New packages in core
> ════════════════════
> 
> `ob-makefile.el' by Eric Schulte and Thomas S. Dye
> ──────────────────────────────────────────────────
> 
>  `ob-makefile.el' implements Org Babel support for Makefile tangling.
> 
> 
> `ox-man.el' by Luis Anaya
> ─────────────────────────
> 
>  `ox-man.el' allows you to export Org files to `man' pages.
> 
> 
> `ox-md.el' by Nicolas Goaziou
> ─────────────────────────────
> 
>  `ox-md.el' allows you to export Org files to Markdown files, using the
>  vanilla [Markdown syntax].
> 
> 
>  [Markdown syntax] http://daringfireball.net/projects/markdown/
> 
> 
> `ox-texinfo.el' by Jonathan Leech-Pepin
> ───────────────────────────────────────
> 
>  `ox-texinfo.el' allows you to export Org files to [Texinfo] files.
> 
> 
>  [Texinfo] http://www.gnu.org/software/texinfo/
> 
> 
> New packages in contrib
> ═══════════════════════
> 
> `ob-julia.el' by G. Jay Kerns
> ─────────────────────────────
> 
>  [Julia] is a new programming language.
> 
>  `ob-julia.el' provides Org Babel support for evaluating Julia source
>  code.
> 
> 
>  [Julia] http://julialang.org/
> 
> 
> `ob-mathomatic.el' by Luis Anaya
> ────────────────────────────────
> 
>  [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.
> 
> 
>  [mathomatic] http://www.mathomatic.org/
> 
> 
> `ob-tcl.el' by Luis Anaya
> ─────────────────────────
> 
>  `ob-tcl.el' provides Org Babel support for evaluating [Tcl] source
>  code.
> 
> 
>  [Tcl] http://www.tcl.tk/
> 
> 
> `org-bullets.el' by Evgeni Sabof
> ────────────────────────────────
> 
>  Display bullets instead of stars for headlines.
> 
>  Also see [this updated FAQ] on how to display another character than
>  "*" for starting headlines.
> 
> 
>  [this updated FAQ] http://orgmode.org/worg/org-faq.html#sec-8-12
> 
> 
> `org-favtable.el' by Marc-Oliver Ihm
> ────────────────────────────────────
> 
>  `org-favtable.el' helps you to create and update a table of favorite
>  locations in org, keeping the most frequently visited lines right at
>  the top.  This table is called "favtable".  See the documentation on
>  [Worg].
> 
> 
>  [Worg] http://orgmode.org/worg/org-contrib/org-favtable.html
> 
> 
> `ox-confluence.el' by Sébastien Delafond
> ────────────────────────────────────────
> 
>  `ox-confluence.el' lets you convert Org files to [Confluence Wiki]
>  files.
> 
> 
>  [Confluence Wiki]
>  https://confluence.atlassian.com/display/DOC/Confluence%2BWiki%2BMarkup
> 
> 
> `ox-deck.el' and `ox-s5.el' by Rick Frankel
> ───────────────────────────────────────────
> 
>  [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'.
> 
> 
>  [deck.js] http://imakewebthings.com/deck.js/
> 
>  [s5] http://meyerweb.com/eric/tools/s5/
> 
> 
> `ox-groff.el' by Luis Anaya and Nicolas Goaziou
> ───────────────────────────────────────────────
> 
>  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.
> 
> 
>  [groff] http://www.gnu.org/software/groff/
> 
> 
> `ox-koma-letter.el' by Nicolas Goaziou and Alan Schmitt
> ───────────────────────────────────────────────────────
> 
>  This back-end allow to export Org pages to the `KOMA Scrlttr2' format.
> 
> 
> `ox-rss.el' by Bastien
> ──────────────────────
> 
>  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.
> 
> 
> New features
> ════════════
> 
> Export
> ──────
> 
> New export generic options
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  If you use Org exporter, we advise you to re-read [the manual section
>  about it].  It has been updated and includes new options.
> 
>  Among the new/updated export options, three are of particular
>  importance:
> 
>  org-export-allow-bind-keywords: This option replaces the old option
>      `org-export-allow-BIND' and the default value is `nil', not
>      `confirm'.  You will need to explicitely set this to `t' in your
>      initialization file if you want to allow `#+BIND' keywords.
> 
>  org-export-with-planning: This new option controls the export of
>      `SCHEDULED:, DEADLINE:, CLOSED:' lines, and planning information is
>      now skipped by default during export.  This use to be the job of
>      org-export-with-timestamps, but this latter option has been given a
>      new role: it controls the export of /standalone time-stamps/.  When
>      set to `nil', Org will not export active and inactive time-stamps
>      standing on a line by themselves or within a paragraph that only
>      contains time-stamps.
> 
>  To check if an option has been introduced or its default value changed
>  in Org 8.0, do `C-h v [option] RET' and check if the documentation
>  says that the variable has been introduced (or changed) in version
>  24.4 of Emacs.
> 
> 
>  [the manual section about it] http://orgmode.org/org.html#Exporting
> 
> 
> Enhanced default stylesheet for the HTML exporter
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  See the new default value of org-html-style-default.
> 
> 
> New tags, classes and ids for the HTML exporter
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  See the new default value of org-html-divs.
> 
> 
> Support for tikz pictures in LaTeX export
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
> 
> `org-man.el': New export function for "man" links
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
> 
> `org-docview.el': New export function for docview links
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
> 
> Structure editing
> ─────────────────
> 
> `C-u C-u M-RET' inserts a heading at the end of the parent subtree
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
> 
> Cycling to the `CONTENTS' view keeps inline tasks folded
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  org-cycle-hook as a new function org-cycle-hide-inline-tasks which
>  prevents the display of inline tasks when showing the content of a
>  subtree.
> 
> 
> `C-c -' in a region makes a list item for each line
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  This is the opposite of the previous behavior, where `C-c -' on a
>  region would create one item for the whole region, and where `C-u C-c
>  -' would create an item for each line.  Now `C-c -' on the selected
>  region creates an item per line, and `C-u C-c -' creates a single item
>  for the whole region.
> 
> 
> When transposing words, markup characters are now part of the words
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  In Emacs, you can transpose words with `M-t'.  Transposing `*these*
>  _words__' will preserve markup.
> 
> 
> New command org-set-property-and-value bound to `C-c C-x P'
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  This command allows you to quickly add both the property and its
>  value.  It is useful in buffers where there are many properties and
>  where `C-c C-x p' can slow down the flow of editing too much.
> 
> 
> New commands org-next-block and org-previous-block
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  These commands allow you to go to the previous block (`C-c M-b' or the
>  speedy key `B') or to the next block (`C-c M-f' or the speedy key
>  `F'.)
> 
> 
> New commands org-drag-line-forward and org-drag-line-backward
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  These commands emulate the old behavior of `M-<down>' and `M-<up>' but
>  are now bound to `S-M-<down>' and `S-M-<up>' respectively, since
>  `M-<down>' and `M-<up>' now drag the whole element at point (a
>  paragraph, a table, etc.)  forward and backward.
> 
> 
> When a list item has a checkbox, inserting a new item uses a checkbox too
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
> 
> When sorting entries/items, only the description of links is considered
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  Now Org will sort this list
> 
>  ╭────
>  │ - [[http://abc.org][B]]
>  │ - [[http://def.org][A]]
>  ╰────
> 
>  like this:
> 
>  ╭────
>  │ - [[http://def.org][A]]
>  │ - [[http://abc.org][B]]
>  ╰────
> 
>  by comparing the descriptions, not the links.  Same when sorting
>  headlines instead of list items.
> 
> 
> New option `orgstruct-heading-prefix-regexp'
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  For example, setting this option to "^;;; " in Emacs lisp files and
>  using `orgstruct-mode' in those files will allow you to cycle through
>  visibility states as if lines starting with ";;; *…" where headlines.
> 
>  In general, you want to set `orgstruct-heading-prefix-regexp' as a
>  file local variable.
> 
> 
> New behavior of org-clone-subtree-with-time-shift
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  The default is to only ask for a number of clones.  When called with a
>  universal prefix argument `C-u', it will prompt you for a time-shift
>  only if there is a time-stamp in the task you want to clone.
> 
> 
> New option org-agenda-restriction-lock-highlight-subtree
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  This defaults to `t' so that the whole subtree is highlighted when you
>  restrict the agenda view to it with `C-c C-x <' (or the speed command
>  `<').  The default setting helps ensuring that you are not adding
>  tasks after the restricted region.  If you find this highlighting too
>  intrusive, set this option to `nil'.
> 
> 
> New option org-closed-keep-when-no-todo
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  When switching back from a `DONE' keyword to a `TODO' keyword, Org now
>  removes the `CLOSED' planning information, if any.  It also removes
>  this information when going back to a non-TODO state (e.g., with `C-c
>  C-t SPC').  If you want to keep the `CLOSED' planning information when
>  removing the TODO keyword, set org-closed-keep-when-no-todo to `t'.
> 
> 
> New option org-image-actual-width
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  This option allows you to change the width of in-buffer displayed
>  images.  The default is to use the actual width of the image, but you
>  can use a fixed value for all images, or fall back on an attribute
>  like
> 
>  ╭────
>  │ #+attr_html: :width 300px
>  ╰────
> 
> 
> Scheduled/deadline
> ──────────────────
> 
> Implement "delay" cookies for scheduled items
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  If you want to delay the display of a scheduled task in the agenda,
>  you can now use a delay cookie like this: `SCHEDULED: <2004-12-25 Sat
>  -2d>'.  The task is still scheduled on the 25th but will appear in
>  your agenda starting from two days later (i.e. from March 27th.)
> 
>  Imagine for example that your co-workers are not done in due time and
>  tell you "we need two more days".  In that case, you may want to delay
>  the display of the task in your agenda by two days, but you still want
>  the task to appear as scheduled on March 25th.
> 
>  In case the task contains a repeater, the delay is considered to
>  affect all occurrences; if you want the delay to only affect the first
>  scheduled occurrence of the task, use `--2d' instead.  See
>  org-scheduled-delay-days and
>  org-agenda-skip-scheduled-delay-if-deadline for details on how to
>  control this globally or per agenda.
> 
> 
> Use `C-u C-u C-s' will insert a delay cookie for scheduled tasks
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  See the previous section for why delay cookies may be useful.
> 
> 
> Use `C-u C-u C-d' will insert a warning delay for deadline tasks
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  `C-u C-u C-d' now inserts a warning delay to deadlines.
> 
> 
> Calendar, diary and appts
> ─────────────────────────
> 
> New variable org-read-date-minibuffer-local-map
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  By default, this new local map uses "." to go to today's date, like in
>  the normal `M-x calendar RET'.  If you want to deactivate this and to
>  reassign the "@" key to `calendar-goto-today', use this:
> 
>  ╭────
>  │ ;; Unbind "." in Org's calendar:
>  │ (define-key org-read-date-minibuffer-local-map (kbd ".") nil)
>  │
>  │ ;; Bind "@" to `calendar-goto-today':
>  │ (define-key org-read-date-minibuffer-local-map
>  │             (kbd "@")
>  │             (lambda () (interactive) (org-eval-in-calendar '(calendar-goto-today))))
>  ╰────
> 
> 
> In Org's calendar, `!' displays diary entries of the date at point
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  This is useful when you want to check if you don't already have an
>  appointment when setting new ones with `C-c .' or `C-c s'.  `!' will
>  call `diary-view-entries' and display the diary in a separate buffer.
> 
> 
> org-diary: only keep the descriptions of links
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  org-diary returns diary information from Org files, but it returns it
>  in a diary buffer, not in an Org mode buffer.  When links are
>  displayed, only show their description, not the full links.
> 
> 
> Agenda
> ──────
> 
> New agenda type `agenda*' and entry types `:scheduled* :deadline*'
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  When defining agenda custom commands, you can now use `agenda*': this
>  will list entries that have both a date and a time.  This is useful
>  when you want to build a list of appointments.
> 
>  You can also set org-agenda-entry-types either globally or locally in
>  each agenda custom command and use `:timestamp*' and/or `:deadline*'
>  there.
> 
>  Another place where this is useful is your `.diary' file:
> 
>  ╭────
>  │ %%(org-diary :scheduled*) ~/org/rdv.org
>  ╰────
> 
>  This will list only entries from `~/org/rdv.org' that are scheduled
>  with a time value (i.e. appointments).
> 
> 
> New agenda sorting strategies
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  org-agenda-sorting-strategy allows these new sorting strategies:
> 
>  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
>   Strategy        Explanations
>  ──────────────────────────────────────────────────────────
>   timestamp-up    Sort by any timestamp, early first
>   timestamp-down  Sort by any timestamp, late first
>   scheduled-up    Sort by scheduled timestamp, early first
>   scheduled-down  Sort by scheduled timestamp, late first
>   deadline-up     Sort by deadline timestamp, early first
>   deadline-down   Sort by deadline timestamp, late first
>   ts-up           Sort by active timestamp, early first
>   ts-down         Sort by active timestamp, late first
>   tsia-up         Sort by inactive timestamp, early first
>   tsia-down       Sort by inactive timestamp, late first
>  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
> 
> 
> New options to limit the number of agenda entries
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  You can now limit the number of entries in an agenda view.  This is
>  different from filters: filters only /hide/ the entries in the agenda,
>  while limits are set while generating the list of agenda entries.
> 
>  These new options are available:
> 
>  org-agenda-max-entries: limit by number of entries.
>  org-agenda-max-todos: limit by number of TODOs.
>  org-agenda-max-tags: limit by number of tagged entries.
>  org-agenda-max-effort: limit by effort (minutes).
> 
>  For example, if you locally set org-agenda-max-todos to 3 in an agenda
>  view, the agenda will be limited to the first three todos.  Other entries
>  without a TODO keyword or beyond the third TODO headline will be ignored.
> 
>  When setting a limit (e.g. about an effort's sum), the default behavior
>  is to exclude entries that cannot be checked against (e.g. entries that
>  have no effort property.)  To include other entries too, you can set the
>  limit to a negative number.  For example (setq org-agenda-max-tags 3)
>  will not show the fourth tagged headline (and beyond), but it will also
>  show non-tagged headlines.
> 
> 
> `~' in agenda view sets temporary limits
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  You can hit `~' in the agenda to temporarily set limits: this will
>  regenerate the agenda as if the limits were set.  This is useful for
>  example when you want to only see a list of `N' tasks, or a list of
>  tasks that take only `N' minutes.
> 
> 
> "=" in agenda view filters by regular expressions
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  You can now filter agenda entries by regular expressions using `='.
>  `C-u =' will filter entries out.  Regexp filters are cumulative.  You
>  can set org-agenda-regexp-filter-preset to suit your needs in each
>  agenda view.
> 
> 
> `|' in agenda view resets all filters
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  Since it's common to combine tag filters, category filters, and now
>  regexp filters, there is a new command `|' to reset all filters at
>  once.
> 
> 
> Allow writing an agenda to an `.org' file
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  You can now write an agenda view to an `.org' file.  It copies the
>  headlines and their content (but not subheadings) into the new file.
> 
>  This is useful when you want to quickly share an agenda containing the
>  full list of notes.
> 
> 
> New commands to drag an agenda line forward (`M-<down>') or backard (`M-<up>')
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  It sometimes handy to move agenda lines around, just to quickly
>  reorganize your tasks, or maybe before saving the agenda to a file.
>  Now you can use `M-<down>' and `M-<up>' to move the line forward or
>  backward.
> 
>  This does not persist after a refresh of the agenda, and this does not
>  change the `.org' files who contribute to the agenda.
> 
> 
> Use `%s' for displaying "breadcrumbs" in the agenda view
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  org-agenda-prefix-format now allows to use a `%b' formatter to tell
>  Org to display "breadcrumbs" in the agenda view.
> 
>  This is useful when you want to display the task hierarchy in your
>  agenda.
> 
> 
> Use `%l' for displaying the headline's level in the agenda view
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  org-agenda-prefix-format allows to use a `%l' formatter to tell Org to
>  display entries with additional spaces corresponding to their level in
>  the outline tree.
> 
> 
> org-agenda-write will ask before overwriting an existing file
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  `M-x org-agenda-write RET' (or `C-c C-w' from an agenda buffer) used
>  to overwrite preexisting file with the same name without confirmation.
>  It now asks for a confirmation.
> 
> 
> New commands `M-m' and `M-*' to toggle (all) mark(s) for bulk action
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  org-agenda-bulk-toggle: this command is bound to `M-m' and toggles the
>      mark of the entry at point.
> 
>  org-agenda-bulk-toggle-all: this command is bound to `M-*' and toggles
>      all the marks in the current agenda.
> 
> 
> New option org-agenda-search-view-max-outline-level
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  This option sets the maximum outline level to display in search view.
>  E.g. when this is set to 1, the search view will only show headlines
>  of level 1.
> 
> 
> New option org-agenda-todo-ignore-time-comparison-use-seconds
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  This allows to compare times using seconds instead of days when
>  honoring options like `org-agenda-todo-ignore-*' in the agenda
>  display.
> 
> 
> New option org-agenda-entry-text-leaders
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  This allows you to get rid of the ">" character that gets added in
>  front of entries excerpts when hitting `E' in the agenda view.
> 
> 
> New formatting string for past deadlines in org-agenda-deadline-leaders
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  The default formatting for past deadlines is `"%2d d. ago: "', which
>  makes it explicit that the deadline is in the past.  You can configure
>  this via org-agenda-deadline-leaders.  Note that the width of the
>  formatting string is important to keep the agenda alignment clean.
> 
> 
> New allowed value `repeated-after-deadline' for org-agenda-skip-scheduled-if-deadline-is-shown
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  When org-agenda-skip-scheduled-if-deadline-is-shown is set to
>  `repeated-after-deadline', the agenda will skip scheduled items if
>  they are repeated beyond the current dealine.
> 
> 
> New option for org-agenda-skip-deadline-prewarning-if-scheduled
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  This variable may be set to nil, t, the symbol `pre-scheduled', or a
>  number which will then give the number of days before the actual
>  deadline when the prewarnings should resume.  The symbol
>  `pre-scheduled' eliminates the deadline prewarning only prior to the
>  scheduled date.
> 
>  Read the full docstring for details.
> 
> 
> org-class now supports holiday strings in the skip-weeks parameter
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  For example, this task will now be skipped only on new year's day:
> 
>  ╭────
>  │ * Task
>  │   <%%(org-class 2012 1 1 2013 12 12 2 "New Year's Day")>
>  ╰────
> 
> 
> Capture
> ───────
> 
> Allow `C-1' as a prefix for org-agenda-capture and org-capture
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  With a `C-1' prefix, the capture mechanism will use the `HH:MM' value
>  at point (if any) or the current `HH:MM' time as the default time for
>  the capture template.
> 
> 
> Expand keywords within %(sexp) placeholder in capture templates
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  If you use a `%:keyword' construct within a `%(sexp)' construct, Org
>  will expand the keywords before expanding the `%(sexp)'.
> 
> 
> Allow to contextualize capture (and agenda) commands by checking the name of the buffer
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  org-capture-templates-contexts and org-agenda-custom-commands-contexts
>  allow you to define what capture templates and what agenda commands
>  should be available in various contexts.  It is now possible for the
>  context to check against the name of the buffer.
> 
> 
> Tag groups
> ──────────
> 
>  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
>  combinaison of those tags.)
> 
>  You can use group tags for sparse tree in an Org buffer, for creating
>  agenda views, and for filtering.
> 
>  See [http://orgmode.org/org.html#Tag-groups] for details.
> 
> 
> Links
> ─────
> 
> `C-u C-u M-x org-store-link RET' will ignore non-core link functions
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  Org knows how to store links from Org buffers, from info files and
>  from other Emacs buffers.  Org can be taught how to store links from
>  any buffer through new link protocols (see ["Adding hyperlink types"]
>  in the manual.)
> 
>  Sometimes you want Org to ignore added link protocols and store the
>  link as if the protocol was not known.
> 
>  You can now do this with `C-u C-u M-x org-store-link RET'.
> 
> 
>  ["Adding hyperlink types"]
>  http://orgmode.org/org.html#Adding-hyperlink-types
> 
> 
> `C-u C-u C-u M-x org-store-link RET' on an active region will store links for each lines
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  Imagine for example that you want to store a link for every message in
>  a Gnus summary buffer.  In that case `C-x h C-u C-u C-u M-x
>  org-store-link RET' will store a link for every line (i.e. message) if
>  the region is active.
> 
> 
> `C-c C-M-l' will add a default description for links which don't have one
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  `C-c C-M-l' inserts all stored links.  If a link does not have a
>  description, this command now adds a default one, so that we are not
>  mixing with-description and without-description links when inserting
>  them.
> 
> 
> No curly braces to bracket links within internal links
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  When storing a link to a headline like
> 
>  ╭────
>  │ * See [[http://orgmode.org][Org website]]
>  ╰────
> 
>  org-store-link used to convert the square brackets into curly
>  brackets.  It does not anymore, taking the link description or the
>  link path, when there is no description.
> 
> 
> Table
> ─────
> 
> Switching between #+TBLFM lines
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  If you have several `#+TBLFM' lines below a table, `C-c C-c' on a line
>  will apply the formulas from this line, and `C-c C-c' on another line
>  will apply those other formulas.
> 
> 
> You now use "nan" for empty fields in Calc formulas
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  If empty fields are of interest, it is recommended to reread the
>  section [3.5.2 Formula syntax for Calc] of the manual because the
>  description for the mode strings has been clarified and new examples
>  have been added towards the end.
> 
> 
>  [3.5.2 Formula syntax for Calc]
>  http://orgmode.org/org.html#Formula-syntax-for-Calc
> 
> 
> Handle localized time-stamps in formulas evaluation
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  If your `LOCALE' is set so that Org time-stamps use another language
>  than english, and if you make time computations in Org's table, it now
>  works by internally converting the time-stamps with a temporary
>  `LOCALE=C' before doing computation.
> 
> 
> New lookup functions
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  There are now three lookup functions:
> 
>  • org-loopup-first
>  • org-loopup-last
>  • org-loopup-all
> 
>  See [the manual] for details.
> 
> 
>  [the manual] http://orgmode.org/org.html#Lookup-functions
> 
> 
> Startup keywords
> ────────────────
> 
>  These new startup keywords are now available:
> 
>  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
>   Startup keyword                   Option
>  ───────────────────────────────────────────────────────────────────────────────
>   `#+STARTUP: logdrawer'            `(setq org-log-into-drawer t)'
>   `#+STARTUP: nologdrawer'          `(setq org-log-into-drawer nil)'
>  ───────────────────────────────────────────────────────────────────────────────
>   `#+STARTUP: logstatesreversed'    `(setq org-log-states-order-reversed t)'
>   `#+STARTUP: nologstatesreversed'  `(setq org-log-states-order-reversed nil)'
>  ───────────────────────────────────────────────────────────────────────────────
>   `#+STARTUP: latexpreview'         `(setq org-startup-with-latex-preview t)'
>   `#+STARTUP: nolatexpreview'       `(setq org-startup-with-latex-preview nil)'
>  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
> 
> 
> Clocking
> ────────
> 
> New option org-clock-rounding-minutes
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  E.g. if org-clock-rounding-minutes is set to 5, time is 14:47 and you
>  clock in: then the clock starts at 14:45.  If you clock out within the
>  next 5 minutes, the clock line will be removed; if you clock out 8
>  minutes after your clocked in, the clock out time will be 14:50.
> 
> 
> New option org-time-clocksum-use-effort-durations
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  When non-nil, `C-c C-x C-d' uses effort durations.  E.g., by default,
>  one day is considered to be a 8 hours effort, so a task that has been
>  clocked for 16 hours will be displayed as during 2 days in the clock
>  display or in the clocktable.
> 
>  See org-effort-durations on how to set effort durations and
>  org-time-clocksum-format for more on time clock formats.
> 
> 
> New option org-clock-x11idle-program-name
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  This allows to set the name of the program which prints X11 idle time
>  in milliseconds.  The default is to use `x11idle'.
> 
> 
> New option org-use-last-clock-out-time-as-effective-time
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  When non-nil, use the last clock out time for org-todo.  Note that
>  this option has precedence over the combined use of
>  org-use-effective-time and org-extend-today-until.
> 
> 
> `S-<left/right>' on a clocksum column will update the sum by updating the last clock
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
> 
> `C-u 3 C-S-<up/down>' will update clock timestamps synchronously by 3 units
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
> 
> New parameter `:wstart' for clocktables to define the week start day
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
> 
> New parameter `:mstart' to state the starting day of the month
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
> 
> Allow relative times in clocktable tstart and tend options
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
> 
> The clocktable summary is now a caption
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
> 
> `:tstart' and `:tend' and friends allow relative times like "<-1w>" or "<now>"
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
> 
> Babel
> ─────
> 
> You can now use `C-c C-k' for org-edit-src-abort
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  This allows you to quickly cancel editing a source block.
> 
> 
> `C-u C-u M-x org-babel-tangle RET' tangles by the target file of the block at point
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  This is handy if you want to tangle all source code blocks that have
>  the same target than the block at point.
> 
> 
> New options for auto-saving the base buffer or the source block editing buffer
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  When org-edit-src-turn-on-auto-save is set to `t', editing a source
>  block in a new window will turn on `auto-save-mode' and save the code
>  in a new file under the same directory than the base Org file.
> 
>  When org-edit-src-auto-save-idle-delay is set to a number of minutes
>  `N', the base Org buffer will be saved after this number of minutes of
>  idle time.
> 
> 
> New `:post' header argument post-processes results
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  This header argument may be used to pass the results of the current
>  code block through another code block for post-processing.  See the
>  manual for a usage example.
> 
> 
> Commented out heading are ignored when collecting blocks for tangling
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  If you comment out a heading (with `C-c ;' anywhere on the heading or
>  in the subtree), code blocks from within this heading are now ignored
>  when collecting blocks for tangling.
> 
> 
> New option org-babel-hash-show-time to show a time-stamp in the result hash
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
> 
> Do not ask for confirmation if cached value is current
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  Do not run org-babel-confirm-evaluate if source block has a cache and
>  the cache value is current as there is no evaluation involved in this
>  case.
> 
> 
> `ob-sql.el' and `ob-python.el' have been improved.
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
> 
> New Babel files only need to `(require 'ob)'
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
> 
>  When writing a new Babel file, you now only need to use `(require
>  'ob)' instead of requiring each Babel library one by one.
> 
> 
> Faces
> ─────
> 
>  • 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
> 
> 
> Miscellaneous
> ═════════════
> 
>  • New speedy key `s' pour org-narrow-to-subtree
>  • Handling of org-html-table-row has been updated (incompatible change)
>  • org-export-html-table-tag is replaced by org-html-table-default-attributes
>  • Support using `git-annex' with Org attachments
>  • org-protocol: Pass optional value using query in url to capture from protocol
>  • When the refile history is empty, use the current filename as default
>  • When you cannot change the TODO state of a task, Org displays the
>    blocking task
>  • New option org-mobile-allpriorities
>  • org-bibtex.el now use `visual-line-mode' instead of the deprecated
>    `longlines-mode'
>  • org-format-latex-options allows to set the foreground/background
>    colors automatically
>  • New option org-archive-file-header-format
>  • New "neg" entity in org-entities
>  • New function org-docview-export to export docview links
>  • New `:eps' header argument for ditaa code blocks
>  • New option org-gnus-no-server to start Gnus with `gnus-no-server'
>  • Org is now distributed with `htmlize.el' version 1.43
>  • `org-drill.el' has been updated to version 2.3.7
>  • `org-mac-iCal.el' now supports MacOSX version up to 10.8
>  • Various improvements to `org-contacts.el' and `orgpan.el'
> 
> 
> Outside Org
> ═══════════
> 
> Spanish translation of the Org guide by David Arroyo Menéndez
> ─────────────────────────────────────────────────────────────
> 
>  David (and others) translated the Org compact guide in spanish:
> 
>  You can read the [PDF guide].
> 
> 
>  [PDF guide] http://orgmode.org/worg/orgguide/orgguide.es.pdf
> 
> 
> `poporg.el' and `outorg.el'
> ───────────────────────────
> 
>  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:
>  [http://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']
> 
> 
>  ["Modern conventions for Emacs Lisp files"]
>  http://youtu.be/nqE6YxlY0rw
> 
>  [Exploring Bernt Hansen's Org-mode tutorial with 'navi-mode']
>  http://www.youtube.com/watch?v%3DII-xYw5VGFM
> 
> 
> MobileOrg for iOS
> ─────────────────
> 
>  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].
> 
> 
>  [on github] https://github.com/MobileOrg/mobileorg/issues
> 
> 
> Thanks you all!
> ════════=======
> 
> Here is a list of people we need to thanks for this release:
> 
> Aaron Ecay, Abdó Roig-Maranges, Achim Gratz, Adam Spiers, Alan Schmitt,
> Alexander Willand, Andreas Leha, Andreas Röhler, Andrew M. Nuxoll, Arun
> Persaud, Bernd Haug, Bernt Hansen, Bill Day, Bill White, Brian van den
> Broek, Carsten Dominik, Charles C. Berry, Christian Egli, Christian Moe,
> Christophe Junke, Christopher Schmidt, Christopher Witte, Chuck Berry,
> Daniel Clemente, Daniel Dehennin, Dave Abrahams, David Kincaid, Derek
> Upham, Enda, Eric Abrahamsen, Eric S Fraga, Eric Schulte, Esben Stien,
> Fabrice Popineau, Feng Shu, Florian Beck, Francesco Pizzolante, Frank
> Fischer, Frank Terbeck, François Pinard, G. Jay Kerns, Gaizka Villate, Gary
> Oberbrunner, Greg Minshall, Gregor Kappler, Grégoire Jadi, Henry Atting,
> Hiroshi Saito, Hrvoje Nikšić, Ian Barton, Ingo Lohmar, Ippei FURUHASHI,
> Ivan Vilata i Balaguer, J. David Boyd, Jae Hee Lee, Jambunathan K, James
> Harkins, Jarmo Hurri, John Foerch, John Hendy, John J Foerch, John Wiegley,
> Jonas Bernoulli, Jonathan Leech-Pepin, Joost Helberg, Justus Piater, Kalev
> Takkis, Ken Williams, Kevin Buchs, Kodi Arfer, Kyle Machulis, Le Wang, Leo
> Liu, Luca Sabbatini, Luis Anaya, Marcel van der Boom, Mark Edgington, Matt
> Lundin, Max Mikhanosha, Michael Brand, Michael Crouch, Michael Gauland,
> Michael Heerdegen, Michael Strey, Mirko Vukovic, Myles English, Nick Dokos,
> Nicolas Goaziou, Nicolas Richard, Oliver Večerník, Paul Sexton, Peder
> Stray, Peter Münster, Philipp Kroos, Raghavendra D Prabhu, Rainer M. Krug,
> Rainer Stengele, Rasmus, Rene, Richard Stanton, Rick Frankel, Rick Hanson,
> Robert Goldman, Robert Horn, Robert Klein, Roland Winkler, Ryo TAKAISHI,
> Rémi Vanicat, Rüdiger Sonderfeld, Sacha Chua, Samuel Loury, Samuel Wales,
> Sean O'Halpin, Sébastien Vauban, Simon Thum, Stefan Monnier, Stefan
> Vollmar, Stephen Eglen, Steve Purcell, Suhail Shergill, Suvayu Ali,
> T.F. Torrey, Thomas S. Dye, Thorsten Jolitz, Toby S. Cubitt, Tokuya
> Kameshima, Tony Day, Viktor Rosenfeld, Vincent Beffara, Vladimir Lomov,
> Wanrong Lin, William Lechelle, Xiao-Yong Jin, Xue Fuqiao, Yann Hodique,
> Yasushi SHOJI, Zech, sabof, Дядов Васил Стоянов.
> 
> -- 
> Bastien

^ permalink raw reply	[flat|nested] 40+ messages in thread

* Re: Release 8.0
  2013-04-18 16:41 Release 8.0 Bastien
                   ` (3 preceding siblings ...)
  2013-04-18 17:41 ` Release 8.0 Neuwirth Erich
@ 2013-04-18 17:43 ` François Pinard
  2013-04-18 17:57   ` Glyn Millington
  2013-04-18 18:24   ` Jambunathan K
  2013-04-18 18:00 ` John Hendy
                   ` (8 subsequent siblings)
  13 siblings, 2 replies; 40+ messages in thread
From: François Pinard @ 2013-04-18 17:43 UTC (permalink / raw)
  To: emacs-orgmode

Bastien <bzg@gnu.org> writes:

> I'm releasing Org 8.0.

Fantastic work.  Warm congratulations to all those involved!

François

^ permalink raw reply	[flat|nested] 40+ messages in thread

* Re: Release 8.0
  2013-04-18 17:43 ` François Pinard
@ 2013-04-18 17:57   ` Glyn Millington
  2013-04-18 18:24   ` Jambunathan K
  1 sibling, 0 replies; 40+ messages in thread
From: Glyn Millington @ 2013-04-18 17:57 UTC (permalink / raw)
  To: emacs-orgmode

François Pinard <pinard@iro.umontreal.ca> writes:

> Bastien <bzg@gnu.org> writes:
>
>> I'm releasing Org 8.0.
>
> Fantastic work.  Warm congratulations to all those involved!
>


Seconded!! The new exporter is terrific :-)

atb


Glyn

^ permalink raw reply	[flat|nested] 40+ messages in thread

* Re: Release 8.0
  2013-04-18 16:41 Release 8.0 Bastien
                   ` (4 preceding siblings ...)
  2013-04-18 17:43 ` François Pinard
@ 2013-04-18 18:00 ` John Hendy
  2013-04-18 18:10 ` Aaron Ecay
                   ` (7 subsequent siblings)
  13 siblings, 0 replies; 40+ messages in thread
From: John Hendy @ 2013-04-18 18:00 UTC (permalink / raw)
  To: Bastien; +Cc: emacs-orgmode

On Thu, Apr 18, 2013 at 11:41 AM, Bastien <bzg@gnu.org> wrote:
> Dear all,
>
> I'm releasing Org 8.0.

Simply fantastic. Many thanks and great work on such a detailed list
of changes. Just mind-blowing how awesome this project is. Thanks to
all the contributors for this great piece of software -- I use it
everyday with outstanding benefits compared to not having it.


John

^ permalink raw reply	[flat|nested] 40+ messages in thread

* Re: Release 8.0
  2013-04-18 17:41 ` Release 8.0 Neuwirth Erich
@ 2013-04-18 18:01   ` Achim Gratz
  2013-05-09  7:55     ` Neuwirth Erich
  0 siblings, 1 reply; 40+ messages in thread
From: Achim Gratz @ 2013-04-18 18:01 UTC (permalink / raw)
  To: emacs-orgmode

Neuwirth Erich writes:
> I compiled from the repository after the announcement.
> On my Mac (OSX 10.8.3, Emacs 24.3.1) the test for maxima still fail.
> I reported this a few weeks ago.

I can't find any post from you on this mailing list that fits that
description and your last post mentioning maxima is from March last
year.

> Ran 443 tests, 436 results as expected, 7 unexpected (2013-04-18 19:38:30+0200)
> 5 expected failures
>
> 7 unexpected results:
>    FAILED  ob-maxima/integer-input
>    FAILED  ob-maxima/list-input
>    FAILED  ob-maxima/matrix-output
>    FAILED  ob-maxima/simple-list-input
>    FAILED  ob-maxima/string-input
>    FAILED  ob-maxima/table-input1
>    FAILED  ob-maxima/table-input2
>
> make[1]: *** [test-dirty] Error 1

Well this looks like all maxima tests have failed, so you might want to
check if it's correctly configured on your system and/or if there's some
extra definition you'll have to give so that the test will find it (it
runs from 'emacs -Q', so you'll have to add any extra setup to the
config variables that make uses).

Also, please trim your quotes.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada

^ permalink raw reply	[flat|nested] 40+ messages in thread

* Re: Release 8.0
  2013-04-18 17:37   ` Bastien
@ 2013-04-18 18:06     ` Jambunathan K
  0 siblings, 0 replies; 40+ messages in thread
From: Jambunathan K @ 2013-04-18 18:06 UTC (permalink / raw)
  To: Bastien; +Cc: emacs-orgmode


> I added Carsten as the author.

I have no problem with that.  You can even add N other authors as long
as my name stays there.

> I'm following the advice of the FSF for now.

FSF position is ambivalent.  They have made a decision (to suit their
convenience) and shifting the burden on me.  Their response is simply
not consistent with Emacs project policy or the most ethical one.

Both FSF and you [1] are "robbing Peter and paying Paul". 

For the serious observers, I have posted a response here.  

        http://lwn.net/Articles/547737/

I also cite the specific term of my future assignment based on which I
claim that I have the right to report on changes that is "not covered by
contract".

[1] You didn't take my permission to move the files from contrib/lisp to
    lisp.  

Jambunathan K.

^ permalink raw reply	[flat|nested] 40+ messages in thread

* Re: Release 8.0
  2013-04-18 16:41 Release 8.0 Bastien
                   ` (5 preceding siblings ...)
  2013-04-18 18:00 ` John Hendy
@ 2013-04-18 18:10 ` Aaron Ecay
  2013-04-18 18:18   ` Jambunathan K
  2013-04-18 18:17 ` Rasmus
                   ` (6 subsequent siblings)
  13 siblings, 1 reply; 40+ messages in thread
From: Aaron Ecay @ 2013-04-18 18:10 UTC (permalink / raw)
  To: Bastien; +Cc: emacs-orgmode

Excellent news!  Thanks to you Bastien and to all the other people who
have helped make this possible.

-- 
Aaron Ecay

^ permalink raw reply	[flat|nested] 40+ messages in thread

* Re: Release 8.0
  2013-04-18 16:41 Release 8.0 Bastien
                   ` (6 preceding siblings ...)
  2013-04-18 18:10 ` Aaron Ecay
@ 2013-04-18 18:17 ` Rasmus
  2013-04-18 19:28 ` Samuel Wales
                   ` (5 subsequent siblings)
  13 siblings, 0 replies; 40+ messages in thread
From: Rasmus @ 2013-04-18 18:17 UTC (permalink / raw)
  To: emacs-orgmode

Bastien <bzg@gnu.org> writes:

> I would like to thank you all again for your patience, and special
> thanks to Nicolas who is just great to work with.  I'm happy to see
> his code finally widely available for all Org users, not just the
> happy few.

I would also like to thank Nicolas for this impressive archivement!
Thanks a lot!  It is much appreciated! 


> 			    ━━━━━━━━━━━━━━━━
> 				ORG 8.0
> 			    ━━━━━━━━━━━━━━━━

Congrats Bastien!  It's looks like a nice release (and indeed based on
the git version it is!)

–Rasmus

-- 
When the facts change, I change my mind. What do you do, sir?

^ permalink raw reply	[flat|nested] 40+ messages in thread

* Re: Release 8.0
  2013-04-18 18:10 ` Aaron Ecay
@ 2013-04-18 18:18   ` Jambunathan K
  2013-04-18 18:22     ` Bastien
  0 siblings, 1 reply; 40+ messages in thread
From: Jambunathan K @ 2013-04-18 18:18 UTC (permalink / raw)
  To: Aaron Ecay; +Cc: emacs-orgmode

Aaron Ecay <aaronecay@gmail.com> writes:

> Excellent news!  Thanks to you Bastien and to all the other people who
> have helped make this possible.

You speak as though "other people" don't exist or matter.  IMO, you are
doing a disservice to other contributors by *not* naming them.

Is it really difficult for you to read the soruce code or changelog and
educate yourself on who these "other people" are.

Please name the people who are thanking.  It's just basic courtesy.
Stop saying "other people" and "all contributors".

Jambunathan K.

^ permalink raw reply	[flat|nested] 40+ messages in thread

* Re: Release 8.0
  2013-04-18 18:18   ` Jambunathan K
@ 2013-04-18 18:22     ` Bastien
  2013-04-18 19:09       ` Jambunathan K
  0 siblings, 1 reply; 40+ messages in thread
From: Bastien @ 2013-04-18 18:22 UTC (permalink / raw)
  To: Jambunathan K; +Cc: Aaron Ecay, emacs-orgmode

Jambunathan K <kjambunathan@gmail.com> writes:

> You speak as though "other people" don't exist or matter.  IMO, you are
> doing a disservice to other contributors by *not* naming them.

All contributors, including you, have been thanked in the release
notes I attached with the original announcement.

We don't want everybody to copy-past this section in their reply :)

-- 
 Bastien

^ permalink raw reply	[flat|nested] 40+ messages in thread

* Re: Release 8.0
  2013-04-18 17:43 ` François Pinard
  2013-04-18 17:57   ` Glyn Millington
@ 2013-04-18 18:24   ` Jambunathan K
  1 sibling, 0 replies; 40+ messages in thread
From: Jambunathan K @ 2013-04-18 18:24 UTC (permalink / raw)
  To: François Pinard; +Cc: emacs-orgmode

François Pinard <pinard@iro.umontreal.ca> writes:

> Fantastic work.  Warm congratulations to all those involved!

You are a regular.  Is it really difficult for you to spell out the
names explicitly?  

"All those involved" is politically correct but it is a disservice to
few individuals whose efforts have been nothing short of Herculean.

Jambunathan K.

^ permalink raw reply	[flat|nested] 40+ messages in thread

* Re: Release 8.0
  2013-04-18 18:22     ` Bastien
@ 2013-04-18 19:09       ` Jambunathan K
  2013-04-18 19:16         ` Jambunathan K
  2013-04-18 19:28         ` Billy O'Connor
  0 siblings, 2 replies; 40+ messages in thread
From: Jambunathan K @ 2013-04-18 19:09 UTC (permalink / raw)
  To: Bastien; +Cc: Aaron Ecay, emacs-orgmode

Bastien <bzg@gnu.org> writes:

> Jambunathan K <kjambunathan@gmail.com> writes:
>
>> You speak as though "other people" don't exist or matter.  IMO, you are
>> doing a disservice to other contributors by *not* naming them.
>
> All contributors, including you, have been thanked in the release
> notes I attached with the original announcement.
>
> We don't want everybody to copy-past this section in their reply :)

Perceptions matter.  A name that is repeated gets remembered.  All
credits go to that name while other names fade.  Politicians know that
perception matter.

I am just educating users on how warped their perceptions could be when
they thank just a single person for what is essentially the work of many
hands.

Users of Free Software should be appreciative of and show respect to all
hands that did the grunt work.

Jambunathan K.

^ permalink raw reply	[flat|nested] 40+ messages in thread

* Re: Release 8.0
  2013-04-18 19:09       ` Jambunathan K
@ 2013-04-18 19:16         ` Jambunathan K
  2013-04-18 19:28         ` Billy O'Connor
  1 sibling, 0 replies; 40+ messages in thread
From: Jambunathan K @ 2013-04-18 19:16 UTC (permalink / raw)
  To: Bastien; +Cc: Aaron Ecay, emacs-orgmode

Jambunathan K <kjambunathan@gmail.com> writes:

> Perceptions matter.  A name that is repeated gets remembered.  All
> credits go to that name while other names fade.

See this post: http://lwn.net/Articles/501751/

People still continue to thank RMS for new Emacs releases.  IIRC, it is
good 5-6 years since RMS retired from daily Emacs work.

There is a gap between what people hold to be true and what the reality
is.  Some perceptions are wrong and it is important that these be
corrected.

Jambunathan K.

^ permalink raw reply	[flat|nested] 40+ messages in thread

* Re: Release 8.0
  2013-04-18 19:09       ` Jambunathan K
  2013-04-18 19:16         ` Jambunathan K
@ 2013-04-18 19:28         ` Billy O'Connor
  2013-04-18 19:50           ` Jambunathan K
  1 sibling, 1 reply; 40+ messages in thread
From: Billy O'Connor @ 2013-04-18 19:28 UTC (permalink / raw)
  To: Jambunathan K; +Cc: Bastien, Aaron Ecay, emacs-orgmode

Jambunathan K <kjambunathan@gmail.com> writes:

> Bastien <bzg@gnu.org> writes:
>
>> Jambunathan K <kjambunathan@gmail.com> writes:
>>
>>> You speak as though "other people" don't exist or matter.  IMO, you are
>>> doing a disservice to other contributors by *not* naming them.
>>
>> All contributors, including you, have been thanked in the release
>> notes I attached with the original announcement.
>>
>> We don't want everybody to copy-past this section in their reply :)
>
> Perceptions matter.  A name that is repeated gets remembered.

There is very little danger that your name will not be remembered.

^ permalink raw reply	[flat|nested] 40+ messages in thread

* Re: Release 8.0
  2013-04-18 16:41 Release 8.0 Bastien
                   ` (7 preceding siblings ...)
  2013-04-18 18:17 ` Rasmus
@ 2013-04-18 19:28 ` Samuel Wales
  2013-04-18 22:05 ` Carsten Dominik
                   ` (4 subsequent siblings)
  13 siblings, 0 replies; 40+ messages in thread
From: Samuel Wales @ 2013-04-18 19:28 UTC (permalink / raw)
  To: Bastien; +Cc: emacs-orgmode

Thanks to everybody who made this release possible.

^ permalink raw reply	[flat|nested] 40+ messages in thread

* Re: Release 8.0
  2013-04-18 19:28         ` Billy O'Connor
@ 2013-04-18 19:50           ` Jambunathan K
  2013-04-18 20:15             ` Bastien
  2013-04-18 20:20             ` Glyn Millington
  0 siblings, 2 replies; 40+ messages in thread
From: Jambunathan K @ 2013-04-18 19:50 UTC (permalink / raw)
  To: Billy O'Connor; +Cc: emacs-orgmode


> There is very little danger that your name will not be remembered.

Let me be clear, it's not about me.  I am a nobody who likes to troll.

It is about others (as well) who deserve a explicit word of thanks.

Can you name the person who funds http://Orgmode.org website?  How many
people have thanked that fellow.  Do people know that such a person or
server actually exists.

Why cannot people thank Nicolas Goaziou for the parser and exporter
framework and also for most of the exporters.  

People are under the mistaken notion that it is the maintainer who does
the "most" or "important" work.  It is this mistake I am endeavouring to
correct.  Obviously I am failing.

Jambunathan K.

^ permalink raw reply	[flat|nested] 40+ messages in thread

* Re: Release 8.0
  2013-04-18 19:50           ` Jambunathan K
@ 2013-04-18 20:15             ` Bastien
  2013-04-18 20:20             ` Glyn Millington
  1 sibling, 0 replies; 40+ messages in thread
From: Bastien @ 2013-04-18 20:15 UTC (permalink / raw)
  To: Jambunathan K; +Cc: Billy O'Connor, emacs-orgmode

Jambunathan K <kjambunathan@gmail.com> writes:

> Can you name the person who funds http://orgmode.org website?

Indeed, I forget to add Jason Dunsmore in the list of people to thank.
Sorry for that.  Jason is still helping with anything regarding the
server, we are lucky to have him!

-- 
 Bastien

^ permalink raw reply	[flat|nested] 40+ messages in thread

* Re: Release 8.0
  2013-04-18 19:50           ` Jambunathan K
  2013-04-18 20:15             ` Bastien
@ 2013-04-18 20:20             ` Glyn Millington
  1 sibling, 0 replies; 40+ messages in thread
From: Glyn Millington @ 2013-04-18 20:20 UTC (permalink / raw)
  To: emacs-orgmode

Jambunathan K <kjambunathan@gmail.com> writes:

>> There is very little danger that your name will not be remembered.
>
> Let me be clear, it's not about me.  I am a nobody who likes to troll.

Confession noted.  In which case it IS all about you. 

> It is about others (as well) who deserve a explicit word of thanks.

So far you have totally failed to offer any word of thanks - either to
Bastien or to any one else. [1]

> Why cannot people thank Nicolas Goaziou for the parser and exporter
> framework and also for most of the exporters.

Why can't you?

> People are under the mistaken notion that it is the maintainer who
> does the "most" or "important" work.  It is this mistake I am
> endeavouring to correct.  Obviously I am failing.

You are failing because the 'mistaken notion' you are trying to correct
does not exist.  


Glyn

Footnotes: 
[1]  "Anyone else"? Lots of attributions here -
http://orgmode.org/Changes.html - you are all wonderful 
and I love you!

^ permalink raw reply	[flat|nested] 40+ messages in thread

* Re: Release 8.0
  2013-04-18 16:41 Release 8.0 Bastien
                   ` (8 preceding siblings ...)
  2013-04-18 19:28 ` Samuel Wales
@ 2013-04-18 22:05 ` Carsten Dominik
  2013-04-19  4:53   ` Brian van den Broek
  2013-04-19  0:20 ` Bernt Hansen
                   ` (3 subsequent siblings)
  13 siblings, 1 reply; 40+ messages in thread
From: Carsten Dominik @ 2013-04-18 22:05 UTC (permalink / raw)
  To: Bastien; +Cc: emacs-orgmode


On 18.4.2013, at 18:41, Bastien <bzg@gnu.org> wrote:

> Dear all,
> 
> I'm releasing Org 8.0.
> 
> See the release notes below or at http://orgmode.org/Changes.html

This is a beautiful release.  Just reading the list of changes wets
my appetite to try it all out.  A looong list con contributors.

Thanks to you all for your contributions!

- Carsten

^ permalink raw reply	[flat|nested] 40+ messages in thread

* Re: Release 8.0
  2013-04-18 16:41 Release 8.0 Bastien
                   ` (9 preceding siblings ...)
  2013-04-18 22:05 ` Carsten Dominik
@ 2013-04-19  0:20 ` Bernt Hansen
  2013-04-19  6:58 ` Christian Moe
                   ` (2 subsequent siblings)
  13 siblings, 0 replies; 40+ messages in thread
From: Bernt Hansen @ 2013-04-19  0:20 UTC (permalink / raw)
  To: Bastien; +Cc: emacs-orgmode

Bastien <bzg@gnu.org> writes:

> I'm releasing Org 8.0.
>

Great work!  Wow what a huge list of new things to try :)

I'm looking forward to experimenting with it.

Thanks!!
Bernt

^ permalink raw reply	[flat|nested] 40+ messages in thread

* Re: Release 8.0
  2013-04-18 22:05 ` Carsten Dominik
@ 2013-04-19  4:53   ` Brian van den Broek
  2013-04-20  8:15     ` Xiao-Yong Jin
  0 siblings, 1 reply; 40+ messages in thread
From: Brian van den Broek @ 2013-04-19  4:53 UTC (permalink / raw)
  To: Carsten Dominik; +Cc: Bastien, emacs-orgmode

[-- Attachment #1: Type: text/plain, Size: 940 bytes --]

On 18 Apr 2013 18:05, "Carsten Dominik" <carsten.dominik@gmail.com> wrote:
>
> On 18.4.2013, at 18:41, Bastien <bzg@gnu.org> wrote:
>
> > Dear all,
> >
> > I'm releasing Org 8.0.
>
> This is a beautiful release.  Just reading the list of changes wets
> my appetite to try it all out.  A looong list con contributors.
>
> Thanks to you all for your contributions!

An intimidatingly long list of changes, actually. :-)

For what it is worth, I think if Bastien erred in the list of contributors
he thanked, it was on the side of over-inclusion, rather than under. In the
last year or so, I think I've contributed a tiny change doc patch, a bug
report or two, and a few "Please, could someone magically make it work like
this?" messages, yet I find myself included.

Congrats and thanks to all who helped in whatever way. The efforts from the
heroic and steady to minor and irregular have all helped to make my life
better.

Best,

Brian vdB

[-- Attachment #2: Type: text/html, Size: 1203 bytes --]

^ permalink raw reply	[flat|nested] 40+ messages in thread

* Re: Release 8.0
  2013-04-18 16:41 Release 8.0 Bastien
                   ` (10 preceding siblings ...)
  2013-04-19  0:20 ` Bernt Hansen
@ 2013-04-19  6:58 ` Christian Moe
  2013-04-19  8:02 ` Stefan Vollmar
  2013-04-21 12:07 ` Memnon Anon
  13 siblings, 0 replies; 40+ messages in thread
From: Christian Moe @ 2013-04-19  6:58 UTC (permalink / raw)
  To: Bastien; +Cc: emacs-orgmode


Great! Thanks, everybody.

Yours,
Christian

^ permalink raw reply	[flat|nested] 40+ messages in thread

* Re: Release 8.0
  2013-04-18 16:41 Release 8.0 Bastien
                   ` (11 preceding siblings ...)
  2013-04-19  6:58 ` Christian Moe
@ 2013-04-19  8:02 ` Stefan Vollmar
  2013-04-21 12:07 ` Memnon Anon
  13 siblings, 0 replies; 40+ messages in thread
From: Stefan Vollmar @ 2013-04-19  8:02 UTC (permalink / raw)
  To: Bastien; +Cc: Org-mode Mailing List

[-- Attachment #1: Type: text/plain, Size: 2654 bytes --]


On 18.04.2013, at 18:41, Bastien wrote:

> I'm releasing Org 8.0.

EXCELLENT - thank you for the hard work and the patience!

Aaron Ecay, Abdó Roig-Maranges, Achim Gratz, Adam Spiers, Alan Schmitt,
Alexander Willand, Andreas Leha, Andreas Röhler, Andrew M. Nuxoll, Arun
Persaud, Bernd Haug, Bernt Hansen, Bill Day, Bill White, Brian van den
Broek, Carsten Dominik, Charles C. Berry, Christian Egli, Christian Moe,
Christophe Junke, Christopher Schmidt, Christopher Witte, Chuck Berry,
Daniel Clemente, Daniel Dehennin, Dave Abrahams, David Kincaid, Derek
Upham, Enda, Eric Abrahamsen, Eric S Fraga, Eric Schulte, Esben Stien,
Fabrice Popineau, Feng Shu, Florian Beck, Francesco Pizzolante, Frank
Fischer, Frank Terbeck, François Pinard, G. Jay Kerns, Gaizka Villate, Gary
Oberbrunner, Greg Minshall, Gregor Kappler, Grégoire Jadi, Henry Atting,
Hiroshi Saito, Hrvoje Nikšić, Ian Barton, Ingo Lohmar, Ippei FURUHASHI,
Ivan Vilata i Balaguer, J. David Boyd, Jae Hee Lee, Jambunathan K, James
Harkins, Jarmo Hurri, John Foerch, John Hendy, John J Foerch, John Wiegley,
Jonas Bernoulli, Jonathan Leech-Pepin, Joost Helberg, Justus Piater, Kalev
Takkis, Ken Williams, Kevin Buchs, Kodi Arfer, Kyle Machulis, Le Wang, Leo
Liu, Luca Sabbatini, Luis Anaya, Marcel van der Boom, Mark Edgington, Matt
Lundin, Max Mikhanosha, Michael Brand, Michael Crouch, Michael Gauland,
Michael Heerdegen, Michael Strey, Mirko Vukovic, Myles English, Nick Dokos,
Nicolas Goaziou, Nicolas Richard, Oliver Večerník, Paul Sexton, Peder
Stray, Peter Münster, Philipp Kroos, Raghavendra D Prabhu, Rainer M. Krug,
Rainer Stengele, Rasmus, Rene, Richard Stanton, Rick Frankel, Rick Hanson,
Robert Goldman, Robert Horn, Robert Klein, Roland Winkler, Ryo TAKAISHI,
Rémi Vanicat, Rüdiger Sonderfeld, Sacha Chua, Samuel Loury, Samuel Wales,
Sean O'Halpin, Sébastien Vauban, Simon Thum, Stefan Monnier, Stefan
Vollmar, Stephen Eglen, Steve Purcell, Suhail Shergill, Suvayu Ali,
T.F. Torrey, Thomas S. Dye, Thorsten Jolitz, Toby S. Cubitt, Tokuya
Kameshima, Tony Day, Viktor Rosenfeld, Vincent Beffara, Vladimir Lomov,
Wanrong Lin, William Lechelle, Xiao-Yong Jin, Xue Fuqiao, Yann Hodique,
Yasushi SHOJI, Zech, sabof, Дядов Васил Стоянов.

Thanks to everybody who made Orgmode such a great tool! 

Warm regards,
 Stefan
-- 
Dr. Stefan Vollmar, Dipl.-Phys.
Head of IT group
Max-Planck-Institut für neurologische Forschung
Gleuelerstr. 50, 50931 Köln, Germany
Tel.: +49-221-4726-213  FAX +49-221-4726-298
Tel.: +49-221-478-5713  Mobile: 0160-93874279
Email: vollmar@nf.mpg.de   http://www.nf.mpg.de







[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 4490 bytes --]

^ permalink raw reply	[flat|nested] 40+ messages in thread

* Re: OAppeal to donors (Re: Release 8.0)
  2013-04-18 17:28 ` Appeal to donors (Re: Release 8.0) Jambunathan K
@ 2013-04-19 15:42   ` Wes Hardaker
  2013-04-19 16:38     ` Russell Adams
  0 siblings, 1 reply; 40+ messages in thread
From: Wes Hardaker @ 2013-04-19 15:42 UTC (permalink / raw)
  To: Jambunathan K; +Cc: emacs-orgmode

Jambunathan K <kjambunathan@gmail.com> writes:

> Donors, please pause before you make any donations.

Thanks for making me pause.  I probably would have thought "I'll do that
tomorrow" and "tomorrow" would have never come.  Now I've done it now.

Maintaining a popular software component takes a huge amount of work.  I
know that.  It's certainly not more important, I agree.  It is, however,
much more stressful.  Especially to be a mediator in difficult
conversations, the stress of packaging something incorrectly, getting
things out on time and complete.  It's not easy.  Writing code isn't
easy either, but I've always found it far far less stressful than
overseeing an entire system.  I'd be more than happy to donate money to
others that have made such huge contributions of personal time toward a
system that has truly turned my life around in the last few years.
Kudos to everyone.
-- 
Wes Hardaker                                     
My Pictures:  http://capturedonearth.com/
My Thoughts:  http://pontifications.hardakers.net/

^ permalink raw reply	[flat|nested] 40+ messages in thread

* Re: OAppeal to donors (Re: Release 8.0)
  2013-04-19 15:42   ` OAppeal " Wes Hardaker
@ 2013-04-19 16:38     ` Russell Adams
  0 siblings, 0 replies; 40+ messages in thread
From: Russell Adams @ 2013-04-19 16:38 UTC (permalink / raw)
  To: emacs-orgmode

On Fri, Apr 19, 2013 at 08:42:53AM -0700, Wes Hardaker wrote:
> Maintaining a popular software component takes a huge amount of work.  I
> know that.  It's certainly not more important, I agree.  It is, however,
> much more stressful.  Especially to be a mediator in difficult
> conversations, the stress of packaging something incorrectly, getting
> things out on time and complete.  It's not easy.  Writing code isn't
> easy either, but I've always found it far far less stressful than
> overseeing an entire system.  I'd be more than happy to donate money to
> others that have made such huge contributions of personal time toward a
> system that has truly turned my life around in the last few years.
> Kudos to everyone.

I'll also point out that while we understand many people make
contributions to Org, we have to trust the maintainer in not only
packaging and project management but in using any funds donated to
the project in an appropriate manner.

I've repeatedly donated to Org, and whether the money goes to server
hosting, bonuses to specific contributors, or just a nice dinner out
with his spouse, it's his choice.

Thanks.


------------------------------------------------------------------
Russell Adams                            RLAdams@AdamsInfoServ.com

PGP Key ID:     0x1160DCB3           http://www.adamsinfoserv.com/

Fingerprint:    1723 D8CA 4280 1EC9 557F  66E8 1154 E018 1160 DCB3

^ permalink raw reply	[flat|nested] 40+ messages in thread

* Re: Release 8.0
  2013-04-19  4:53   ` Brian van den Broek
@ 2013-04-20  8:15     ` Xiao-Yong Jin
  0 siblings, 0 replies; 40+ messages in thread
From: Xiao-Yong Jin @ 2013-04-20  8:15 UTC (permalink / raw)
  To: Brian van den Broek; +Cc: Bastien, emacs-orgmode, Carsten Dominik

[-- Attachment #1: Type: text/plain, Size: 1630 bytes --]


On Apr 19, 2013, at 1:53 PM, Brian van den Broek <brian.van.den.broek@gmail.com> wrote:

> On 18 Apr 2013 18:05, "Carsten Dominik" <carsten.dominik@gmail.com> wrote:
> >
> > On 18.4.2013, at 18:41, Bastien <bzg@gnu.org> wrote:
> >
> > > Dear all,
> > >
> > > I'm releasing Org 8.0.
> >
> > This is a beautiful release.  Just reading the list of changes wets
> > my appetite to try it all out.  A looong list con contributors.
> >
> > Thanks to you all for your contributions!
> 
> An intimidatingly long list of changes, actually. :-)
> 
> For what it is worth, I think if Bastien erred in the list of contributors he thanked, it was on the side of over-inclusion, rather than under. In the last year or so, I think I've contributed a tiny change doc patch, a bug report or two, and a few "Please, could someone magically make it work like this?" messages, yet I find myself included.
> 
Yes, indeed!  Honestly, I didn't read the long list of contributors that carefully at first.  I decided to take another read after through your message, and ... Wow... I really didn't expect my name be in the list, since I have only sent a few messages to the list.
> Congrats and thanks to all who helped in whatever way. The efforts from the heroic and steady to minor and irregular have all helped to make my life better.
> 
Congratulations to all the orgmode users!  Please allow me to take this chance to express my sincere gratitude to everyone subscribed to this orgmode mailing list and also people who contributed in other ways!  It is you who have made orgmode so fantastic!

Best Regards,
Xiao-Yong



[-- Attachment #2: Type: text/html, Size: 2259 bytes --]

^ permalink raw reply	[flat|nested] 40+ messages in thread

* Re: Release 8.0
  2013-04-18 16:41 Release 8.0 Bastien
                   ` (12 preceding siblings ...)
  2013-04-19  8:02 ` Stefan Vollmar
@ 2013-04-21 12:07 ` Memnon Anon
  2013-04-21 13:25   ` Bastien
  13 siblings, 1 reply; 40+ messages in thread
From: Memnon Anon @ 2013-04-21 12:07 UTC (permalink / raw)
  To: emacs-orgmode

Bastien <bzg@gnu.org> writes:

> I'm releasing Org 8.0.

Excellent.

> To include other entries too, you can set the
> limit to a negative number.  For example (setq org-agenda-max-tags 3)
(setq org-agenda-max-tags -3) ?                                 
> will not show the fourth tagged headline (and beyond), but it will also
> show non-tagged headlines.


> Use `%s' for displaying "breadcrumbs" in the agenda view
> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
       ^%b

>   • New speedy key `s' pour org-narrow-to-subtree

Memnon

^ permalink raw reply	[flat|nested] 40+ messages in thread

* Re: Release 8.0
  2013-04-21 12:07 ` Memnon Anon
@ 2013-04-21 13:25   ` Bastien
  2013-04-22 16:56     ` Jay Kerns
  0 siblings, 1 reply; 40+ messages in thread
From: Bastien @ 2013-04-21 13:25 UTC (permalink / raw)
  To: Memnon Anon; +Cc: emacs-orgmode

Hi Memnon,

Memnon Anon <gegendosenfleisch@googlemail.com> writes:

>> To include other entries too, you can set the
>> limit to a negative number.  For example (setq org-agenda-max-tags 3)
> (setq org-agenda-max-tags -3) ?                                 

Indeed.

>> will not show the fourth tagged headline (and beyond), but it will also
>> show non-tagged headlines.
>
>
>> Use `%s' for displaying "breadcrumbs" in the agenda view
>> ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
>        ^%b

Ditto.

Fixed, thanks!

-- 
 Bastien

^ permalink raw reply	[flat|nested] 40+ messages in thread

* Re: Release 8.0
  2013-04-21 13:25   ` Bastien
@ 2013-04-22 16:56     ` Jay Kerns
  2013-04-22 17:17       ` Bastien
  0 siblings, 1 reply; 40+ messages in thread
From: Jay Kerns @ 2013-04-22 16:56 UTC (permalink / raw)
  To: Bastien; +Cc: Memnon Anon, emacs-orgmode

On Sun, Apr 21, 2013 at 9:25 AM, Bastien <bzg@gnu.org> wrote:
> Hi Memnon,
>
> Memnon Anon <gegendosenfleisch@googlemail.com> writes:

[ snip ]

Quick question: is it true, now that Org 8.0 has been released, that
the engine which publishes Worg is now Org 8.0, too?  In other words,
is it now safe to publish to Worg all of that stuff which was written
compatible with the new exporter, without breaking Worg in the
process?

Cheers,

-- 
Jay

^ permalink raw reply	[flat|nested] 40+ messages in thread

* Re: Release 8.0
  2013-04-22 16:56     ` Jay Kerns
@ 2013-04-22 17:17       ` Bastien
  2013-04-22 18:32         ` Carsten Dominik
  0 siblings, 1 reply; 40+ messages in thread
From: Bastien @ 2013-04-22 17:17 UTC (permalink / raw)
  To: Jay Kerns; +Cc: Memnon Anon, emacs-orgmode

Hi Jay,

Jay Kerns <gjkernsysu@gmail.com> writes:

> On Sun, Apr 21, 2013 at 9:25 AM, Bastien <bzg@gnu.org> wrote:
>> Hi Memnon,
>>
>> Memnon Anon <gegendosenfleisch@googlemail.com> writes:
>
> [ snip ]
>
> Quick question: is it true, now that Org 8.0 has been released, that
> the engine which publishes Worg is now Org 8.0, too?

No, not yet.

> In other words, is it now safe to publish to Worg all of that stuff
> which was written compatible with the new exporter, without breaking
> Worg in the process?

No.  Someone needs to carefully check he can exports his local clone
of worg.git with the new exporter, fix the wrong syntax, then commit
it.  This surely deserves a public branch of Worg, which people can
hack together.

-- 
 Bastien

^ permalink raw reply	[flat|nested] 40+ messages in thread

* Re: Release 8.0
  2013-04-22 17:17       ` Bastien
@ 2013-04-22 18:32         ` Carsten Dominik
  2013-04-22 19:46           ` John Hendy
  0 siblings, 1 reply; 40+ messages in thread
From: Carsten Dominik @ 2013-04-22 18:32 UTC (permalink / raw)
  To: Bastien; +Cc: emacs-orgmode, Memnon Anon, Jay Kerns


On 22.4.2013, at 19:17, Bastien <bzg@gnu.org> wrote:

> Hi Jay,
> 
> Jay Kerns <gjkernsysu@gmail.com> writes:
> 
>> On Sun, Apr 21, 2013 at 9:25 AM, Bastien <bzg@gnu.org> wrote:
>>> Hi Memnon,
>>> 
>>> Memnon Anon <gegendosenfleisch@googlemail.com> writes:
>> 
>> [ snip ]
>> 
>> Quick question: is it true, now that Org 8.0 has been released, that
>> the engine which publishes Worg is now Org 8.0, too?
> 
> No, not yet.
> 
>> In other words, is it now safe to publish to Worg all of that stuff
>> which was written compatible with the new exporter, without breaking
>> Worg in the process?
> 
> No.  Someone needs to carefully check he can exports his local clone
> of worg.git with the new exporter, fix the wrong syntax, then commit
> it.  This surely deserves a public branch of Worg, which people can
> hack together.


Thanks Bastien, I was about to write about this.

We need a volunteer who is willing to coordinate the conversion
of Worg to the new exporter.  This is an important task.  Dogfooding
Worg to the new exporter will be a good way to find remaining bugs
in the parser/exporter setup.

This task would entail:

1. Creating a public branch of Worg for this work.
2. Creating and maintaining a file that contains a site map of Worg,
   with all files that need publishing
3. Organizing contributors who will look at one page after the other
   and implementing any changes needed to make the page export (not yet
   publish) cleanly with the new exporter.  In this way we need to walk
   through all Worg files, and someone needs to keep the tabs on this.
4. When all this is done, see what changes have to be made to the
   publishing setup to fix the automatic publishing.

Any takers?

Once we are done with this, we also need the orgmode.org website, but
that contains fewer pages, so it should be a lot simpler.

- Carsten  

^ permalink raw reply	[flat|nested] 40+ messages in thread

* Re: Release 8.0
  2013-04-22 18:32         ` Carsten Dominik
@ 2013-04-22 19:46           ` John Hendy
  2013-04-22 20:06             ` Carsten Dominik
  2013-04-22 20:17             ` Thorsten Jolitz
  0 siblings, 2 replies; 40+ messages in thread
From: John Hendy @ 2013-04-22 19:46 UTC (permalink / raw)
  To: Carsten Dominik; +Cc: Bastien, Jay Kerns, Memnon Anon, emacs-orgmode

On Mon, Apr 22, 2013 at 1:32 PM, Carsten Dominik
<carsten.dominik@gmail.com> wrote:
>
> On 22.4.2013, at 19:17, Bastien <bzg@gnu.org> wrote:
>
>> Hi Jay,
>>
>> Jay Kerns <gjkernsysu@gmail.com> writes:
>>
>>> On Sun, Apr 21, 2013 at 9:25 AM, Bastien <bzg@gnu.org> wrote:
>>>> Hi Memnon,
>>>>
>>>> Memnon Anon <gegendosenfleisch@googlemail.com> writes:
>>>
>>> [ snip ]
>>>
>>> Quick question: is it true, now that Org 8.0 has been released, that
>>> the engine which publishes Worg is now Org 8.0, too?
>>
>> No, not yet.
>>
>>> In other words, is it now safe to publish to Worg all of that stuff
>>> which was written compatible with the new exporter, without breaking
>>> Worg in the process?
>>
>> No.  Someone needs to carefully check he can exports his local clone
>> of worg.git with the new exporter, fix the wrong syntax, then commit
>> it.  This surely deserves a public branch of Worg, which people can
>> hack together.
>
>
> Thanks Bastien, I was about to write about this.
>
> We need a volunteer who is willing to coordinate the conversion
> of Worg to the new exporter.  This is an important task.  Dogfooding
> Worg to the new exporter will be a good way to find remaining bugs
> in the parser/exporter setup.
>
> This task would entail:
>
> 1. Creating a public branch of Worg for this work.

Can I just update my clone and push to github? If so, sure. I'd just
use my own github account (unpaid). If there's a better location,
suggest it or someone else can volunteer to host/create the clone if
they have better tools/access for this.

> 2. Creating and maintaining a file that contains a site map of Worg,
>    with all files that need publishing

I could take a stab at this, but it won't be instantaneous. If someone
has the time and energy to do this in the short term (< 1 week),
they'd be better. If a week or so is acceptable, I can take this one
as well, at least the creation part. I'm assuming it will be a big
todo list? From there, it would be much easier if editors updated it
themselves.

> 3. Organizing contributors who will look at one page after the other
>    and implementing any changes needed to make the page export (not yet
>    publish) cleanly with the new exporter.  In this way we need to walk
>    through all Worg files, and someone needs to keep the tabs on this.

Not sure we totally need to organize this. I'm wondering about
something like an "editor" property in the file from #2. Contributors
could self-assign by adding their name to that property in the tracker
file and then push. Perhaps an agenda view or simply column view could
quickly show who is assigned to what file?

> 4. When all this is done, see what changes have to be made to the
>    publishing setup to fix the automatic publishing.

I'd be really bad at this as I've never actually set up publishing. I
can definitely help with some of the #+attr_backend and general syntax
stuff, but I never got heavy into the site publishing features and
have never even looked at Worg's setup for this.

If this is the process... how does the public Worg get updated in the
mean time? I'm pretty new to git and only do basic stuff. Diffs have
always been intimidating (and I've found them to really stink even for
really, really small changes I've had). How will we maintain the
public site and then re-combine with the public one down the road?
Editing on the public one needs to happen in old syntax; public repo
for upgrade hacking needs to be in the new syntax.

Should we freeze Worg for the time being and direct editing to happen
at the other one?


Best regards,
John

>
> Any takers?
>
> Once we are done with this, we also need the orgmode.org website, but
> that contains fewer pages, so it should be a lot simpler.
>
> - Carsten
>
>

^ permalink raw reply	[flat|nested] 40+ messages in thread

* Re: Release 8.0
  2013-04-22 19:46           ` John Hendy
@ 2013-04-22 20:06             ` Carsten Dominik
  2013-04-22 20:17             ` Thorsten Jolitz
  1 sibling, 0 replies; 40+ messages in thread
From: Carsten Dominik @ 2013-04-22 20:06 UTC (permalink / raw)
  To: John Hendy; +Cc: Bastien, Jay Kerns, Memnon Anon, emacs-orgmode


On 22.4.2013, at 21:46, John Hendy <jw.hendy@gmail.com> wrote:

> On Mon, Apr 22, 2013 at 1:32 PM, Carsten Dominik
> <carsten.dominik@gmail.com> wrote:
>> 
>> On 22.4.2013, at 19:17, Bastien <bzg@gnu.org> wrote:
>> 
>>> Hi Jay,
>>> 
>>> Jay Kerns <gjkernsysu@gmail.com> writes:
>>> 
>>>> On Sun, Apr 21, 2013 at 9:25 AM, Bastien <bzg@gnu.org> wrote:
>>>>> Hi Memnon,
>>>>> 
>>>>> Memnon Anon <gegendosenfleisch@googlemail.com> writes:
>>>> 
>>>> [ snip ]
>>>> 
>>>> Quick question: is it true, now that Org 8.0 has been released, that
>>>> the engine which publishes Worg is now Org 8.0, too?
>>> 
>>> No, not yet.
>>> 
>>>> In other words, is it now safe to publish to Worg all of that stuff
>>>> which was written compatible with the new exporter, without breaking
>>>> Worg in the process?
>>> 
>>> No.  Someone needs to carefully check he can exports his local clone
>>> of worg.git with the new exporter, fix the wrong syntax, then commit
>>> it.  This surely deserves a public branch of Worg, which people can
>>> hack together.
>> 
>> 
>> Thanks Bastien, I was about to write about this.
>> 
>> We need a volunteer who is willing to coordinate the conversion
>> of Worg to the new exporter.  This is an important task.  Dogfooding
>> Worg to the new exporter will be a good way to find remaining bugs
>> in the parser/exporter setup.
>> 
>> This task would entail:
>> 
>> 1. Creating a public branch of Worg for this work.
> 
> Can I just update my clone and push to github? If so, sure. I'd just
> use my own github account (unpaid). If there's a better location,
> suggest it or someone else can volunteer to host/create the clone if
> they have better tools/access for this.


Do you have commit access at the worg repository at orgmode.org?
Then it would be easiest to set it up there.  I could do it, but maybe you want to?

Basically:

You create a new branch in your repository:

$ git checkout -b worg-new-exporter

Then you push this new branch to the remote repository:

$ git push -u origin worg-new-exporter

Then you can work in this new branch and just push from this branch
whenever you want:

$ git push

Everybody else can hook onto this branch with

$ git checkout --track -b worg-new-exporter origin/worg-new-exporter

and then work in this branch and push it whenever they want.

> 
>> 2. Creating and maintaining a file that contains a site map of Worg,
>>   with all files that need publishing
> 
> I could take a stab at this, but it won't be instantaneous. If someone
> has the time and energy to do this in the short term (< 1 week),
> they'd be better. If a week or so is acceptable, I can take this one
> as well, at least the creation part. I'm assuming it will be a big
> todo list? From there, it would be much easier if editors updated it
> themselves.

I agree, this would be easiest.  Organizing this would then mean
to announce to precise procedure on the mailing list and hope that people
hack away.

> 
>> 3. Organizing contributors who will look at one page after the other
>>   and implementing any changes needed to make the page export (not yet
>>   publish) cleanly with the new exporter.  In this way we need to walk
>>   through all Worg files, and someone needs to keep the tabs on this.
> 
> Not sure we totally need to organize this. I'm wondering about
> something like an "editor" property in the file from #2. Contributors
> could self-assign by adding their name to that property in the tracker
> file and then push.

Yes this is a good way.  Organizing then means to check for files
that have not been done and do them yourself or encourage other
directly to do it.

> Perhaps an agenda view or simply column view could
> quickly show who is assigned to what file?
> 
>> 4. When all this is done, see what changes have to be made to the
>>   publishing setup to fix the automatic publishing.
> 
> I'd be really bad at this as I've never actually set up publishing. I
> can definitely help with some of the #+attr_backend and general syntax
> stuff, but I never got heavy into the site publishing features and
> have never even looked at Worg's setup for this.

Well, if you get everything working with the new exporter, we
will find a way to fix publishing if necessary.

> 
> If this is the process... how does the public Worg get updated in the
> mean time? I'm pretty new to git and only do basic stuff. Diffs have
> always been intimidating (and I've found them to really stink even for
> really, really small changes I've had). How will we maintain the
> public site and then re-combine with the public one down the road?
> Editing on the public one needs to happen in old syntax; public repo
> for upgrade hacking needs to be in the new syntax.

We definitely do NOT stop to edit Worg in the mean time.  The master
branch can be edited in parallel.  This is git, so we can merge both
branches when the time comes.

It would be great if you can take a stab at this, John.

- Carsten

> 
> Should we freeze Worg for the time being and direct editing to happen
> at the other one?
> 
> 
> Best regards,
> John
> 
>> 
>> Any takers?
>> 
>> Once we are done with this, we also need the orgmode.org website, but
>> that contains fewer pages, so it should be a lot simpler.
>> 
>> - Carsten
>> 
>> 

^ permalink raw reply	[flat|nested] 40+ messages in thread

* Re: Release 8.0
  2013-04-22 19:46           ` John Hendy
  2013-04-22 20:06             ` Carsten Dominik
@ 2013-04-22 20:17             ` Thorsten Jolitz
  1 sibling, 0 replies; 40+ messages in thread
From: Thorsten Jolitz @ 2013-04-22 20:17 UTC (permalink / raw)
  To: emacs-orgmode

John Hendy <jw.hendy@gmail.com> writes:

>>> No.  Someone needs to carefully check he can exports his local clone
>>> of worg.git with the new exporter, fix the wrong syntax, then commit
>>> it.  This surely deserves a public branch of Worg, which people can
>>> hack together.

>> We need a volunteer who is willing to coordinate the conversion
>> of Worg to the new exporter.  This is an important task.  Dogfooding
>> Worg to the new exporter will be a good way to find remaining bugs
>> in the parser/exporter setup.
>>
>> This task would entail:

[...]

>> 3. Organizing contributors who will look at one page after the other
>>    and implementing any changes needed to make the page export (not yet
>>    publish) cleanly with the new exporter.  In this way we need to walk
>>    through all Worg files, and someone needs to keep the tabs on this.
>
> Not sure we totally need to organize this. I'm wondering about
> something like an "editor" property in the file from #2. Contributors
> could self-assign by adding their name to that property in the tracker
> file and then push. Perhaps an agenda view or simply column view could
> quickly show who is assigned to what file?

>> Any takers?

I don't know if this would put a huge work load on somebody who
contributed *much* content to Worg, but otherwise I would propose for
this step that all authors of Worg articles/pages take care of their own
pages. In my case that would be e.g. half a dozen of pages, not that
much of a problem.

Once most Worg authors have fixed their own pages, another round of
fixing the (few?) remaining pages by some volunteers could be started.

Just my 2cents

-- 
cheers,
Thorsten

^ permalink raw reply	[flat|nested] 40+ messages in thread

* Re: Release 8.0
  2013-04-18 18:01   ` Achim Gratz
@ 2013-05-09  7:55     ` Neuwirth Erich
  0 siblings, 0 replies; 40+ messages in thread
From: Neuwirth Erich @ 2013-05-09  7:55 UTC (permalink / raw)
  To: Achim Gratz; +Cc: emacs-orgmode

I wanted to report that the problem seems to be solved in the latest release.
I just compiled and ran all the tests (including the maxima ones) without a hitch
on my Mac (OSX 10.8.3, Emacs 24.3.1)

On Apr 18, 2013, at 8:01 PM, Achim Gratz <Stromeko@nexgo.de> wrote:

> Neuwirth Erich writes:
>> I compiled from the repository after the announcement.
>> On my Mac (OSX 10.8.3, Emacs 24.3.1) the test for maxima still fail.
>> I reported this a few weeks ago.
> 
> I can't find any post from you on this mailing list that fits that
> description and your last post mentioning maxima is from March last
> year.
> 
>> Ran 443 tests, 436 results as expected, 7 unexpected (2013-04-18 19:38:30+0200)
>> 5 expected failures
>> 
>> 7 unexpected results:
>>   FAILED  ob-maxima/integer-input
>>   FAILED  ob-maxima/list-input
>>   FAILED  ob-maxima/matrix-output
>>   FAILED  ob-maxima/simple-list-input
>>   FAILED  ob-maxima/string-input
>>   FAILED  ob-maxima/table-input1
>>   FAILED  ob-maxima/table-input2
>> 
>> make[1]: *** [test-dirty] Error 1
> 
> Well this looks like all maxima tests have failed, so you might want to
> check if it's correctly configured on your system and/or if there's some
> extra definition you'll have to give so that the test will find it (it
> runs from 'emacs -Q', so you'll have to add any extra setup to the
> config variables that make uses).
> 
> Also, please trim your quotes.
> 
> 
> Regards,
> Achim.
> -- 
> +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
> 
> SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
> http://Synth.Stromeko.net/Downloads.html#KorgSDada
> 
> 

^ permalink raw reply	[flat|nested] 40+ messages in thread

end of thread, other threads:[~2013-05-09  7:55 UTC | newest]

Thread overview: 40+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-04-18 16:41 Release 8.0 Bastien
2013-04-18 16:58 ` Jambunathan K
2013-04-18 17:37   ` Bastien
2013-04-18 18:06     ` Jambunathan K
2013-04-18 17:15 ` Anthony Lander
2013-04-18 17:28 ` Appeal to donors (Re: Release 8.0) Jambunathan K
2013-04-19 15:42   ` OAppeal " Wes Hardaker
2013-04-19 16:38     ` Russell Adams
2013-04-18 17:41 ` Release 8.0 Neuwirth Erich
2013-04-18 18:01   ` Achim Gratz
2013-05-09  7:55     ` Neuwirth Erich
2013-04-18 17:43 ` François Pinard
2013-04-18 17:57   ` Glyn Millington
2013-04-18 18:24   ` Jambunathan K
2013-04-18 18:00 ` John Hendy
2013-04-18 18:10 ` Aaron Ecay
2013-04-18 18:18   ` Jambunathan K
2013-04-18 18:22     ` Bastien
2013-04-18 19:09       ` Jambunathan K
2013-04-18 19:16         ` Jambunathan K
2013-04-18 19:28         ` Billy O'Connor
2013-04-18 19:50           ` Jambunathan K
2013-04-18 20:15             ` Bastien
2013-04-18 20:20             ` Glyn Millington
2013-04-18 18:17 ` Rasmus
2013-04-18 19:28 ` Samuel Wales
2013-04-18 22:05 ` Carsten Dominik
2013-04-19  4:53   ` Brian van den Broek
2013-04-20  8:15     ` Xiao-Yong Jin
2013-04-19  0:20 ` Bernt Hansen
2013-04-19  6:58 ` Christian Moe
2013-04-19  8:02 ` Stefan Vollmar
2013-04-21 12:07 ` Memnon Anon
2013-04-21 13:25   ` Bastien
2013-04-22 16:56     ` Jay Kerns
2013-04-22 17:17       ` Bastien
2013-04-22 18:32         ` Carsten Dominik
2013-04-22 19:46           ` John Hendy
2013-04-22 20:06             ` Carsten Dominik
2013-04-22 20:17             ` Thorsten Jolitz

Code repositories for project(s) associated with this inbox:

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).