Org-mode version 5.13

Org-mode version 5.13

[Carsten Dominik]

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.

Re: Org-mode version 5.13

[Adam Spiers]

On Fri, Oct 19, 2007 at 08:25:18AM +0200, Carsten Dominik wrote:
> Hi everyone,
> 
> I am releasing Org-mode version 5.13 at http://orgmode.org
>    - The agenda dispatcher
>      + `<' cycles through restriction states.
>      + Multi-character access codes to commands (= sub-keymaps).

I can't believe you implemented this already; I'm struggling to think
of superlatives to describe this quality of maintainership!  Really
looking forward to testing it out, thanks a lot :-D

Re: Org-mode version 5.13

[Eddward DeVilla]

On 10/19/07, Adam Spiers <orgmode@adamspiers.org> wrote:
> On Fri, Oct 19, 2007 at 08:25:18AM +0200, Carsten Dominik wrote:
> > Hi everyone,
> >
> > I am releasing Org-mode version 5.13 at http://orgmode.org
> >    - The agenda dispatcher
> >      + `<' cycles through restriction states.
> >      + Multi-character access codes to commands (= sub-keymaps).
>
> I can't believe you implemented this already; I'm struggling to think
> of superlatives to describe this quality of maintainership!

Ya.  Carsten is pretty good like that.

Edd

Re: Org-mode version 5.13

[Bastien]

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

Hello all,

Carsten Dominik <dominik@science.uva.nl> writes:

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

This should be "id", not "class", since there is only one instance of
the table of contents - fixed in the proposed patch.

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

Classes are ok here.

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

There was a small typo for the <div> of the postamble, this patch also
fixes it.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: org.el.patch --]
[-- Type: text/x-diff, Size: 879 bytes --]

diff -u /home/guerry/elisp/testing/org/org.el /home/guerry/elisp/testing/bzg/org.el
--- /home/guerry/elisp/testing/org/org.el	2007-10-19 15:44:15.000000000 +0100
+++ /home/guerry/elisp/testing/bzg/org.el	2007-10-20 11:26:28.000000000 +0100
@@ -23830,7 +23830,7 @@
 
       (unless body-only
 	(when (plist-get opt-plist :auto-postamble)
-	  (insert "<div=\"postamble\">")
+	  (insert "<div id=\"postamble\">")
 	  (when (and org-export-author-info author)
 	    (insert "<p class=\"author\"> "
 		    (nth 1 lang-words) ": " author "\n")
@@ -23866,7 +23866,7 @@
 	  (when (looking-at "\\s-*</p>")
 	    (goto-char (match-end 0))
 	    (insert "\n")))
-	(insert "<div class=\"table-of-contents\">\n")
+	(insert "<div id=\"table-of-contents\">\n")
 	(mapc 'insert thetoc)
 	(insert "</div>\n"))
       ;; remove empty paragraphs and lists

Diff finished.  Sat Oct 20 11:29:17 2007

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


-- 
Bastien

[-- Attachment #4: Type: text/plain, Size: 204 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Org-mode version 5.13

[Mike Newman]

On Sat, 20 Oct 2007 11:30:29 +0100
Bastien <bzg@altern.org> wrote:

> Hello all,
> 
> Carsten Dominik <dominik@science.uva.nl> writes:
> 
> >     - The table of context is wrapped into a div with a class
> >       "table-of-contents".
> 
> This should be "id", not "class", since there is only one instance of
> the table of contents - fixed in the proposed patch.

I think that class is the right thing here.  We are saying that this is
a "table-of-contents" rather than this is the "table-of-contents".  I
believe at present there is no mechanism to give more than one table of
contents, but someone, sometime might want tables of contents for
individual sections of a document.

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

This appears to be logical, but is in fact (I think) redundant.  We can
specify the style to applied at different levels without using
class attributes.  For example:

   div { background-color: lightgray}
   div > div { background-color: peachpuff}
   div > div > div { background-color: green}
   
shows how different styling can be applied to level 1, level 2 and
level 3 (and above).

I think this has advantages (e.g. inheritance of unspecified
characteristics from higher levels) and leaves the class attribute free
to represent styling that is independent of the structure.

-- 
Mike

Re: Org-mode version 5.13

[Nuutti Kotivuori]

Mike Newman wrote:
> This appears to be logical, but is in fact (I think) redundant.  We can
> specify the style to applied at different levels without using
> class attributes.  For example:
>
> div { background-color: lightgray}
> div > div { background-color: peachpuff}
> div > div > div { background-color: green}

...except that it doesn't work with IE < 7.0.

All in all, browser interoperable CSS is the land of kludges, horrible
kludges and dear-god-make-it-stop kludges.

It's best to be as simple as possible to make the life of those poor
souls as easy as possible.

-- Naked

Re: Org-mode version 5.13

[Bastien]

Mike Newman <mike@newmanfamily.me.uk> writes:

> I think that class is the right thing here.  We are saying that this is
> a "table-of-contents" rather than this is the "table-of-contents".  I
> believe at present there is no mechanism to give more than one table of
> contents, but someone, sometime might want tables of contents for
> individual sections of a document.

Fair enough.  Let's say that "id" is okay for now (since the HTML
exporter doesn't know how to export multiple tables of contents), 
but this might become "class" when needed.

> This appears to be logical, but is in fact (I think) redundant.  We can
> specify the style to applied at different levels without using
> class attributes.  For example:
>
>    div { background-color: lightgray}
>    div > div { background-color: peachpuff}
>    div > div > div { background-color: green}
>    
> shows how different styling can be applied to level 1, level 2 and
> level 3 (and above).

So you suggest keeping the <div> tags, but stripping them out of their
"class" attributes? 

> I think this has advantages (e.g. inheritance of unspecified
> characteristics from higher levels) and leaves the class attribute
> free to represent styling that is independent of the structure.

Yes, I feel quite the same.

-- 
Bastien

Re: Org-mode version 5.13

[Carsten Dominik]

So, does everybody agree that I should remove the class from the divs  
again?

- Carsten

On Oct 22, 2007, at 11:38 PM, Mike Newman wrote:

> On Sat, 20 Oct 2007 11:30:29 +0100
> Bastien <bzg@altern.org> wrote:
>
>> Hello all,
>>
>> Carsten Dominik <dominik@science.uva.nl> writes:
>>
>>>     - The table of context is wrapped into a div with a class
>>>       "table-of-contents".
>>
>> This should be "id", not "class", since there is only one instance of
>> the table of contents - fixed in the proposed patch.
>
> I think that class is the right thing here.  We are saying that  
> this is
> a "table-of-contents" rather than this is the "table-of-contents".  I
> believe at present there is no mechanism to give more than one  
> table of
> contents, but someone, sometime might want tables of contents for
> individual sections of a document.
>
>>
>>>     - The outline structure is embedded in <div> elements with
>>>       classes "outline-1", "outline-2" etc.
>>
>> Classes are ok here.
>>
>
> This appears to be logical, but is in fact (I think) redundant.  We  
> can
> specify the style to applied at different levels without using
> class attributes.  For example:
>
>    div { background-color: lightgray}
>    div > div { background-color: peachpuff}
>    div > div > div { background-color: green}
>
> shows how different styling can be applied to level 1, level 2 and
> level 3 (and above).
>
> I think this has advantages (e.g. inheritance of unspecified
> characteristics from higher levels) and leaves the class attribute  
> free
> to represent styling that is independent of the structure.
>
> -- 
> Mike
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Org-mode version 5.13

[Dmitri Minaev]

On 10/24/07, Carsten Dominik <carsten.dominik@gmail.com> wrote:
> So, does everybody agree that I should remove the class from the divs
> again?
>


Wouldn't classes make formatting more flexible? If I understand
correctly, Mike Newman's proposal will require all formatting to be
hardcoded into org.el? I'd rather keep it in a separate .css file, one
for the whole site...


-- 
With best regards,
Dmitri Minaev

Russian history blog: http://minaev.blogspot.com

Re: Org-mode version 5.13

[Mike Newman]

On Thu, 25 Oct 2007 16:12:36 +0500
"Dmitri Minaev" <minaev@gmail.com> wrote:


> Wouldn't classes make formatting more flexible? If I understand
> correctly, Mike Newman's proposal will require all formatting to be
> hardcoded into org.el? I'd rather keep it in a separate .css file, one
> for the whole site...
> 
> 
That is certainly not my intention.  I think keeping style information
in a separate file is a good idea.

-- 
Mike

Re: Org-mode version 5.13

[Nuutti Kotivuori]

Carsten Dominik wrote:
> So, does everybody agree that I should remove the class from the divs
> again?

Not at all. I think there should definitely be classes on the divs
signifying the level. Also, toc should have a class - possibly only in
addition an id, that tells that this is the main front page toc, but
that's already extra.

CSS is a difficult beast to do in a way that is compatible between
browsers - the more ways there are to select an element, the easier
making that CSS is.

Ofcourse, there's no need to go overboard with those, but classes on
divs is hardly that.

-- Naked

Re: Org-mode version 5.13

[Scott Jaderholm]

[-- Attachment #1.1: Type: text/plain, Size: 734 bytes --]

On 10/19/07, Carsten Dominik <dominik@science.uva.nl> wrote:
>
>
> Changes in Version 5.13
> ------------------------
>
>      - 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.
>

In org 5.12 when I do C-c a the Agenda Commands window that comes up is only
as tall as it needs to be. In 5.13 it is half the frame height. I'm not sure
exactly which change caused this. Setting org-agenda-window-frame-fractions
to have a minimum of 0.1 doesn't make the agenda commands window any
smaller, as I think it only affects the Org Agenda window.

Thanks for another great release!

--Scott

[-- Attachment #1.2: Type: text/html, Size: 1234 bytes --]

[-- Attachment #2: Type: text/plain, Size: 204 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Org-mode version 5.13

[Bastien]

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

"Scott Jaderholm" <jaderholm@gmail.com> writes:

>          - 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.
>
> In org 5.12 when I do C-c a the Agenda Commands window that comes up
> is only as tall as it needs to be. In 5.13 it is half the frame
> height. I'm not sure exactly which change caused this.

`org-agenda-window-setup' or `org-agenda-window-frame-fractions' don't
change the way the Agenda Commands window is displayed.

I guess Carsten wanted the default size of windows to be the same for
the Agenda Commands window and for any agenda view.  But I think the
Agenda Commands window should be as small as possible since it's not
likely to change very often.

Here is a patch for this.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: org.el.patch --]
[-- Type: text/x-diff, Size: 664 bytes --]

diff -u /home/guerry/elisp/testing/org/org.el /home/guerry/elisp/testing/bzg/org.el
--- /home/guerry/elisp/testing/org/org.el	2007-10-22 15:04:16.000000000 +0100
+++ /home/guerry/elisp/testing/bzg/org.el	2007-10-24 01:04:27.000000000 +0100
@@ -18339,9 +18339,7 @@
 				   "Prefix key"))))
 		    prefixes))
 	  (goto-char (point-min))
-	  (if (and (fboundp 'fit-window-to-buffer)
-		   (not (pos-visible-in-window-p (point-max))))
-	      (fit-window-to-buffer))
+	  (if (fboundp 'fit-window-to-buffer) (fit-window-to-buffer))
 	  (message "Press key for agenda command%s:"
 		   (if restrict-ok
 		       (if restriction

Diff finished.  Wed Oct 24 01:04:41 2007

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


-- 
Bastien

[-- Attachment #4: Type: text/plain, Size: 204 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Org-mode version 5.13

[Carsten Dominik]

On Oct 24, 2007, at 2:14 AM, Bastien wrote:

> "Scott Jaderholm" <jaderholm@gmail.com> writes:
>
>>          - 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.
>>
>> In org 5.12 when I do C-c a the Agenda Commands window that comes up
>> is only as tall as it needs to be. In 5.13 it is half the frame
>> height. I'm not sure exactly which change caused this.
>
> `org-agenda-window-setup' or `org-agenda-window-frame-fractions' don't
> change the way the Agenda Commands window is displayed.
>
> I guess Carsten wanted the default size of windows to be the same for
> the Agenda Commands window and for any agenda view.  But I think the
> Agenda Commands window should be as small as possible since it's not
> likely to change very often.

No, the reason was that due to the ability to have multiple keys  
leading to
a command, the window is displayed several times, and it is annoying
when it changes during a single command selection.  But I forgot
to get it small on the first key.  Fixed, thanks.

- Carsten

Re: Org-mode version 5.13

[Adam Spiers]

On Fri, Oct 19, 2007 at 08:25:18AM +0200, Carsten Dominik wrote:
> Changes in Version 5.13
> ------------------------
> 
>     - `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.

I finally got around to trying this, and I can't get the variable to
have any effect at all, whether it's set to t or to something like

  ((65 (:bold t :weight bold)))

Any ideas?