emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <dominik@science.uva.nl>
To: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Org-mode version 5.13
Date: Fri, 19 Oct 2007 08:25:18 +0200	[thread overview]
Message-ID: <e1dbc9dd7572b0a7c62210849a9db52e@science.uva.nl> (raw)

Hi everyone,

I am releasing Org-mode version 5.13 at http://orgmode.org

This is a big release.  Except for severe bug fixes, the next
release will probably not be before the end of November.

Enjoy

- Carsten


Changes in Version 5.13
------------------------

Overview
========

    - Bug fixes and improvements in column view
      + All known bugs fixed.
      + A Column view can be captured into a dynamic block.
      + The ITEM column is formatted core compactly.
      + Also ITEM can be edited with `e'

    - The agenda dispatcher
      + `<' cycles through restriction states.
      + Multi-character access codes to commands (= sub-keymaps).

    - Sorting improvements
      + User-defined sorting keys.
      + Sorting by properties.
      + Sorting of plain lists.

    - HTML <div> structure

    - Other stuff
      + New variables, several of them.
      + Drawers can be set on a per-file basis.
      + Better control over priority fontification in agenda.
      + M-up and M-down now move the current line up and down.
      + Abort remember template selection with C-g.

Details
=======

Bug fixes and improvements in column view
-----------------------------------------

     - All the bugs described by Scott Jaderholm have been fixed
       (at least I hope so...).

     - You can now capture a column view into a dynamic block, for
       exporting or printing it.  The column view can be

       + global, i.e. for the entire file
       + local, i.e. for the subtree where the dynamic block is
       + from an entry with a specific :ID: property.

       You can identify the entry whose column view you want to
       capture by assigning an :ID: property, and use that property
       in the dynamic block definition.  For example:

        * Planning
          :PROPERTIES:
            :ID: planning-overview
          :END:

        [...]

        * The column view
        #+BEGIN: columnview :hlines 1 :id "planning-overview"

        #+END:

       Use `C-c C-x r' to insert such a dynamic block, and you will
       be prompted for the ID.

     - When the current column format displays the TODO keyword,
       priority or tags, these parts are stripped from the content
       of the ITEM column, making for more compact and readable
       entries.  When any of these "properties" are not listed in
       the current column format, they are instead retained in the
       ITEM column.

     - You can now also edit the ITEM column with `e'.

The agenda dispatcher
---------------------

     - Instead of pressing `1' to restrict an agenda command to
       the current buffer, or `0' to restrict it to the current
       subtree or region, you can now also press `<' once or
       twice, respectively.  This frees up `1' and `0' for user
       commands, a request by Bastien.  In fact, "<" cycles
       through different restriction states.  "1" and "0" are
       still available for backward compatibility, until you bind
       them to custom commands.

     - The access code to custom agenda commands can now contain
       several characters, effectively allowing to bundle several
       similar commands into a sub-keymap.  This follows an
       excellent proposal by Adam Spiers.  For example:

        (setq org-agenda-custom-commands
          '(("h" . "HOME + Name tag searches") ; describe prefix "h"
            ("hl" tags "+HOME+Lisa")
            ("hp" tags "+HOME+Peter")
            ("hk" tags "+HOME+Kim")))

     - The user function option in org-agenda-custom-commands may
       now also be a lambda expression, following a request by
       Adam Spiers.

Sorting improvements
--------------------

     We are using a new routine for sorting entries, courtesy of
     John Wiegley.  Many thanks to John.

     - You can define your own function to extract a sorting key
       and in this way sort entries by anything you like.

     - Entries can now be sorted according to the value of a
       property.

     - Plain lists can be sorted.

HTML <div> structure
--------------------

     There is now a <div>-based structure in exported HTML.

     - The table of context is wrapped into a div with a class
       "table-of-contents".

     - The outline structure is embedded in <div> elements with
       classes "outline-1", "outline-2" etc.

     - The postamble, containing the author information and the
       date is wrapped into a div with class "postamble".

     I am not sure if the class names are the best choice, let me
     know if there are more "canonical" names we should use instead.

     Thanks to Mike Newman and Cezar for input, and in particular
     to Mike for his clearly formulated specification.

Other stuff
-----------

     - New variable `org-agenda-window-frame-fractions' to
       customize the size limits of the agenda window in the case
       that you display the agenda window by reorganizing the
       frame.

     - Drawers can be set on a per-file basis using

        #+DRAWERS: HIDDEN STATE PROPERTIES

       This will define the drawers :HIDDEN: and :STATE:.
       The :PROPERTY: drawer should always be part of this list, or
       your properties will not be folded away.
       Thanks to Richard G. Riley for this proposal.

     - `org-agenda-fontify-priorities' may now also be an
       association list of priorities and faces, to specify the
       faces of priorities in the agenda individually.

     - The variable `org-export-with-property-drawer' no longer
       exists, please use `org-export-with-drawers' instead.  Also,
       the corresponding switch in the #+OPTIONS line has changed
       from "p" to "d".  Thanks to Bastien for pointing out that we
       needed to handle not only the property drawer.

     - M-up and M-down now move the current line up and down (if
       not at a headline, item or table).  Among other things you
       can use this to re-order properties in the drawer.  This was
       a proposal by Bastien.

     - New variable `org-agenda-todo-ignore-with-date', based on a
       request by Wanrong Lin.

     - Aborting remember template selection with C-g now kills the
       remember buffer and restores the old window configuration.
       This was a request by Nuutti Kotivuori.

             reply	other threads:[~2007-10-19  6:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-19  6:25 Carsten Dominik [this message]
2007-10-19 11:23 ` Org-mode version 5.13 Adam Spiers
2007-10-19 15:11   ` Eddward DeVilla
2007-10-20 10:30 ` Bastien
2007-10-22 21:38   ` Mike Newman
2007-10-22 21:48     ` Nuutti Kotivuori
2007-10-22 22:50     ` Bastien
2007-10-24 16:42     ` Carsten Dominik
2007-10-25 11:12       ` Dmitri Minaev
2007-10-26 16:53         ` Mike Newman
2007-10-25 12:00       ` Nuutti Kotivuori
2007-10-23 19:26 ` Scott Jaderholm
2007-10-24  0:14   ` Bastien
2007-10-24  3:18     ` Carsten Dominik
2007-12-30 12:31 ` Adam Spiers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e1dbc9dd7572b0a7c62210849a9db52e@science.uva.nl \
    --to=dominik@science.uva.nl \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public 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).