RELEASE: Org-mode version 6.32

RELEASE: Org-mode version 6.32

[Carsten Dominik]

Hi everyone,

I have uploaded version 6.32 of Org, with lots of good additions and the
usual suite of bug fixes.  Thanks to everyone who contributed to this
release.

Enjoy!

- Carsten

Changes in Version 6.32
=======================


Rewrite of org-mobile.org, for MobileOrg 1.0 (build 20)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

MobileOrg is currently under review at the iPhone App Store.  You
will need Org-mode version 6.32 to interact with it.

Added support for habit consistency tracking
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

/org-habit.el/ contains new code to track habits.  Please
configure the variable org-modules to activate it.  When active,
habits (a special TODO entry) will be displayed in the agenda
together with a "consistency graph".  Habit tracking is described
in a new [manual section].

Thanks to John Wiegley for this contribution.


[manual section]: http://orgmode.org/manual/Tracking-your-habits.html

New context-aware tag auto-exclusion
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

After writing a function relating to location and context
information, you will be able to press `/ RET' in the agenda to
exclude tasks that cannot be done in the current context.
For details, see the information about filtering in the manual.

Thanks to John Wiegley for a patch to this effect.

New clock resolving tools
~~~~~~~~~~~~~~~~~~~~~~~~~~

When clocking into a new task while no clock is running, Org now
checks for orphaned CLOCK lines and offers to repair these before
starting the clock.  You can also configure this feature to check
for idle time and prompt you to subtract that time from the
running timer.

See the new [manual section] for more details.

Thanks to John Wiegley for a patch to this effect.


[manual section]: http://orgmode.org/manual/Resolving-idle-time.html

Mutually exclusive tag groups can now have a name in the tags interface
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The customize interface allows to optionally add a string to the
beginning or end of such a group.

Thanks to James TD Smith for a patch to this effect.

Agenda Search view: Search for substrings
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The default in search view (/C-c a s/)is now that the search
expression is searched for as a /substring/, i.e. the different
words must occur in direct sequence, and it may be only part of
a word.  If you want to look for a number of separate keywords
with Boolean logic, all words must be preceded by `+' or `-'.

This was, more-or-less, requested by John Wiegley.

Make space and backspace scroll the show window in the agenda
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Pressing SPC again after using it to show an agenda item in
another window will make the entire subtree visible, and show
scroll it.  Backspace and DEL will scroll back.

This was a request by Eric Fraga.


File tags are now offered for completion during a tag prompts
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Requested by Matt Lundin.

Make `- SPC' an agenda filter that selects entries without any tags
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Request by John Wiegley.

Better way to edit multi-line macro definitions
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The editing tool key `C-c '= now also edits =#+MACRO'
definitions, including multiline macros.

Restructured Manual
~~~~~~~~~~~~~~~~~~~~

The manual has been slightly reorganized.  The archiving stuff,
which was - somewhat obscurely - hidden in the /Document
Structure/ chapter, has been moved into the new chapter
/Capture-Refile-Archive/.  Also, there is a new chapter /Markup/
which contains both the markup rules (moved there from the Export
chapter) and the documentation for embedded LaTeX.

Improved figure placement in LaTeX and HTML export
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Text can now be wrapped around figures.  See the manual for
details.

Allow date to be shifted into the future if time given is earlier than  
now
~ 
~ 
~ 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

By setting

     (setq org-read-date-prefer-future 'time)

you indicate to Org that, if you only give a time at the
date/time prompt, and if this time is earlier then the current
time, then the date of tomorrow will be assumed to be valid for
this event.  A similar mechanism was already in place for dates,
but now you can make it work for times as well.

Collected changes in org-babel
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- Source blocks can now reference source-blocks in other files
   using `filepath:srcname' syntax.
- Inline code blocks like `src_python{2+2}' are now exported
- Remote source block calls using the `#+lob: srcname(arg=val)'
   syntax can now be exported.
- When `:file' is supplied with an `R' block, graphics are
   automatically sent to file and linked from the org buffer, thus
   appearing on export.  The image format is obtained from the
   filename extension.  Possible values are `.png, .jpg, .jpeg,
   .tiff, .bmp, .pdf, .ps, .postscript', defaulting to `png'.
- Results can be returned as parseable code using `:results code',
   and as pretty-printed code using `:results pp' (emacs-lisp,
   python, ruby).  Thanks to Benny Andresen for the idea and patch
   for emacs-lisp.
- When `:file filename' is supplied, `:exports file' is unnecessary
- Header args are taken from org-file-properties in addition to
   properties active in the subtree.
- `:noweb' header argument now expands noweb references before
   source-block evaluation.
- Tangling honours the new org variable
   org-src-preserve-indentation, so that correct code is output for
   a language like python that depends on indentation.

Changes in org-exp-blocks.el
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- Interblocks export has been simplified.
- Support for R code (`begin_R' blocks and inline `\R{}') has been
   removed.  Please use org-babel instead.

- Carsten

Feature request about habit tracking [was: RELEASE: Org-mode version 6.32]

[Friedrich Delgado Friedrichs]

Hi!

I have a feature request about habit tracking and I bet you can guess
what it is:

Carsten Dominik schrieb:
> Added support for habit consistency tracking
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 
> /org-habit.el/ contains new code to track habits.  Please
> configure the variable org-modules to activate it.  When active,
> habits (a special TODO entry) will be displayed in the agenda
> together with a "consistency graph".  Habit tracking is described
> in a new [manual section].
---Zitatende---

I'd really like habit tracking to be enabled for all TODOs with active
timestamps + repeaters with the property :STYLE: habit.

Those things are rarely part of the hard landscape of the day for me,
things won't blow up if I won't do them on exactly that same day, so I
don't want them scheduled and don't want them on my calendar, but I
want to be reminded in my agenda. But tracking how consistently I've
done things on those days is still very useful.


-- 
        Friedrich Delgado Friedrichs <friedel@nomaden.org>
                             TauPan on Ircnet and Freenode ;)

Re: Feature request about habit tracking [was: RELEASE: Org-mode version 6.32]

[Carsten Dominik]

Hi Friedrich,

John and I are not really clear about exactly what you are
asking for.  Can you try again?  What exactly is the difference
between what we have now and what you are asking for?

- Carsten

On Oct 30, 2009, at 4:13 PM, Friedrich Delgado Friedrichs wrote:

> Hi!
>
> I have a feature request about habit tracking and I bet you can guess
> what it is:
>
> Carsten Dominik schrieb:
>> Added support for habit consistency tracking
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>
>> /org-habit.el/ contains new code to track habits.  Please
>> configure the variable org-modules to activate it.  When active,
>> habits (a special TODO entry) will be displayed in the agenda
>> together with a "consistency graph".  Habit tracking is described
>> in a new [manual section].
> ---Zitatende---
>
> I'd really like habit tracking to be enabled for all TODOs with active
> timestamps + repeaters with the property :STYLE: habit.
>
> Those things are rarely part of the hard landscape of the day for me,
> things won't blow up if I won't do them on exactly that same day, so I
> don't want them scheduled and don't want them on my calendar, but I
> want to be reminded in my agenda. But tracking how consistently I've
> done things on those days is still very useful.
>
>
> -- 
>        Friedrich Delgado Friedrichs <friedel@nomaden.org>
>                             TauPan on Ircnet and Freenode ;)
>
>
> _______________________________________________
> 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

- Carsten

Re: Feature request about habit tracking [was: RELEASE: Org-mode version 6.32]

[Friedrich Delgado Friedrichs]

Hi!

Carsten Dominik schrieb:
> John and I are not really clear about exactly what you are
> asking for.  Can you try again?  What exactly is the difference
> between what we have now and what you are asking for?

You know after I had sent that mail, I had the nagging thought that
maybe I should have explicitely mentioned the difference:

> >I'd really like habit tracking to be enabled for all TODOs with active
> >timestamps + repeaters with the property :STYLE: habit.

That means: Exactly what you have now, but add an option to also match
active timestamps *without* the SCHEDULED or DEADLINE keyword.

(i.e. similar to what you did for me in the icalendar export)

And I hope the next paragraph also makes more sense now:

> >Those things are rarely part of the hard landscape of the day for me,
> >things won't blow up if I won't do them on exactly that same day, so I
> >don't want them scheduled and don't want them on my calendar, but I
> >want to be reminded in my agenda. But tracking how consistently I've
> >done things on those days is still very useful.



-- 
        Friedrich Delgado Friedrichs <friedel@nomaden.org>
                             TauPan on Ircnet and Freenode ;)

Re: Feature request about habit tracking [was: RELEASE: Org-mode version 6.32]

[Carsten Dominik]

Hi Friedrich,

from what I see, John has built the habit tracking
into the routine that looks for scheduling entries.  So it would be
a significant change to do this for normal time stamps.

A solution for you could be to just use the scheduling stuff anyway,
and then use a filter function to make sure these entries do not show up
in the iCalendar export (untested):

(defun my-icalendar-verify ()
    (if (string= (org-entry-get nil "STYLE") "habit") nil t))

(setq org-icalendar-verify-function 'my-icalendar-verify)

HTH

- Carsten
	
On Nov 2, 2009, at 12:06 PM, Friedrich Delgado Friedrichs wrote:

> Hi!
>
> Carsten Dominik schrieb:
>> John and I are not really clear about exactly what you are
>> asking for.  Can you try again?  What exactly is the difference
>> between what we have now and what you are asking for?
>
> You know after I had sent that mail, I had the nagging thought that
> maybe I should have explicitely mentioned the difference:
>
>>> I'd really like habit tracking to be enabled for all TODOs with  
>>> active
>>> timestamps + repeaters with the property :STYLE: habit.
>
> That means: Exactly what you have now, but add an option to also match
> active timestamps *without* the SCHEDULED or DEADLINE keyword.
>
> (i.e. similar to what you did for me in the icalendar export)
>
> And I hope the next paragraph also makes more sense now:
>
>>> Those things are rarely part of the hard landscape of the day for  
>>> me,
>>> things won't blow up if I won't do them on exactly that same day,  
>>> so I
>>> don't want them scheduled and don't want them on my calendar, but I
>>> want to be reminded in my agenda. But tracking how consistently I've
>>> done things on those days is still very useful.
>
>
>
> -- 
>        Friedrich Delgado Friedrichs <friedel@nomaden.org>
>                             TauPan on Ircnet and Freenode ;)
>
>
> _______________________________________________
> 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

- Carsten

Re: Feature request about habit tracking [was: RELEASE: Org-mode version 6.32]

[Friedrich Delgado Friedrichs]

Hi

Carsten Dominik schrieb:
> from what I see, John has built the habit tracking
> into the routine that looks for scheduling entries.  So it would be
> a significant change to do this for normal time stamps.
> 
> A solution for you could be to just use the scheduling stuff anyway,
> and then use a filter function to make sure these entries do not show up
> in the iCalendar export (untested):
---Zitatende---

To schedule those items is a significant semantic difference for me,
which is reflected in a different face in the agenda, so just
filtering them out of the icalendar export is not enough.



-- 
        Friedrich Delgado Friedrichs <friedel@nomaden.org>
                             TauPan on Ircnet and Freenode ;)

Re: Feature request about habit tracking

[Matt Lundin]

Hi Friedrich,

Friedrich Delgado Friedrichs <friedel@nomaden.org> writes:

> Hi
>
> Carsten Dominik schrieb:
>> from what I see, John has built the habit tracking
>> into the routine that looks for scheduling entries.  So it would be
>> a significant change to do this for normal time stamps.
>> 
>> A solution for you could be to just use the scheduling stuff anyway,
>> and then use a filter function to make sure these entries do not show up
>> in the iCalendar export (untested):
> ---Zitatende---
>
> To schedule those items is a significant semantic difference for me,
> which is reflected in a different face in the agenda, so just
> filtering them out of the icalendar export is not enough.

Have you tried using habits? Even though their functionality depends on
SCHEDULED timestamps, they look and behave quite differently than normal
scheduled items.

Granted, habits appear with the org-scheduled-today face. But they do
not have the normal "Scheduled:" or "Sched. 2x" warnings. And they can
easily be filtered out of the agenda by pressing "K".

Best,
Matt

Re: Re: Feature request about habit tracking

[Friedrich Delgado Friedrichs]

Hi

Matt Lundin schrieb:
 > To schedule those items is a significant semantic difference for me,
> > which is reflected in a different face in the agenda, so just
> > filtering them out of the icalendar export is not enough.
> Have you tried using habits? Even though their functionality depends on
> SCHEDULED timestamps, they look and behave quite differently than normal
> scheduled items.

Yes I tried using them.

> Granted, habits appear with the org-scheduled-today face. But they do
> not have the normal "Scheduled:" or "Sched. 2x" warnings. And they can
> easily be filtered out of the agenda by pressing "K".
--Zitatende---

I don't like that they have the same face, even though they can easily be
filtered and are visually set apart by the graph.

I admit I didn't notice that they don't have the "Scheduled:" keyword.
That's a definitive advantage for me.

How hard would it be to give them a different face as well?

-- 
        Friedrich Delgado Friedrichs <friedel@nomaden.org>
                             TauPan on Ircnet and Freenode ;)

Re: Feature request about habit tracking [was: RELEASE: Org-mode version 6.32]

[Friedrich Delgado Friedrichs]

Hi again!

Meanwhile I've experimented a bit more with org-habit.el and I've
grown to like it very much.

Now I've tried to filter the habits out of my icalendar export, as
suggested by Carsten:
Carsten Dominik schrieb:
> A solution for you could be to just use the scheduling stuff anyway,
> and then use a filter function to make sure these entries do not show up
> in the iCalendar export (untested):
> 
> (defun my-icalendar-verify ()
>    (if (string= (org-entry-get nil "STYLE") "habit") nil t))
> 
> (setq org-icalendar-verify-function 'my-icalendar-verify)
---Zitatende---

Unfortunately I can't make this work. I've stepped the
my-icalendar-verify function with edebug and it is simple enough and
returns nil for habits, and t for non-habits. And I can't spot an
error in org-print-icalendar-entries, but I can't say I understand it.


-- 
        Friedrich Delgado Friedrichs <friedel@nomaden.org>
                             TauPan on Ircnet and Freenode ;)

Re: Feature request about habit tracking [was: RELEASE: Org-mode version 6.32]

[Friedrich Delgado Friedrichs]

Sorry!

I think I left out just about every bit of relevant information
here...

I'm using 1029daee030975f086be1d7470533b584b262829, and the problem is
that I get an empty org.ics file after
org-export-icalendar-combine-agenda-files.

(It looks to me like org-print-icalendar-entries has faulty logic, but
that is pure conjecture.)

If you need more information, or example files, please let me know.

> Now I've tried to filter the habits out of my icalendar export, as
> suggested by Carsten:
> Carsten Dominik schrieb:
> > A solution for you could be to just use the scheduling stuff anyway,
> > and then use a filter function to make sure these entries do not show up
> > in the iCalendar export (untested):
> > 
> > (defun my-icalendar-verify ()
> >    (if (string= (org-entry-get nil "STYLE") "habit") nil t))
> > 
> > (setq org-icalendar-verify-function 'my-icalendar-verify)
> 
> Unfortunately I can't make this work. I've stepped the
> my-icalendar-verify function with edebug and it is simple enough and
> returns nil for habits, and t for non-habits. And I can't spot an
> error in org-print-icalendar-entries, but I can't say I understand it.
---Zitatende---

-- 
        Friedrich Delgado Friedrichs <friedel@nomaden.org>
                             TauPan on Ircnet and Freenode ;)

Re: Feature request about habit tracking [was: RELEASE: Org-mode version 6.32]

[Carsten Dominik]

You mean the file is empty only if you set orv-icalendar-verify- 
function????

- Carsten

On Nov 5, 2009, at 1:21 PM, Friedrich Delgado Friedrichs wrote:

> Sorry!
>
> I think I left out just about every bit of relevant information
> here...
>
> I'm using 1029daee030975f086be1d7470533b584b262829, and the problem is
> that I get an empty org.ics file after
> org-export-icalendar-combine-agenda-files.
>
> (It looks to me like org-print-icalendar-entries has faulty logic, but
> that is pure conjecture.)
>
> If you need more information, or example files, please let me know.
>
>> Now I've tried to filter the habits out of my icalendar export, as
>> suggested by Carsten:
>> Carsten Dominik schrieb:
>>> A solution for you could be to just use the scheduling stuff anyway,
>>> and then use a filter function to make sure these entries do not  
>>> show up
>>> in the iCalendar export (untested):
>>>
>>> (defun my-icalendar-verify ()
>>>   (if (string= (org-entry-get nil "STYLE") "habit") nil t))
>>>
>>> (setq org-icalendar-verify-function 'my-icalendar-verify)
>>
>> Unfortunately I can't make this work. I've stepped the
>> my-icalendar-verify function with edebug and it is simple enough and
>> returns nil for habits, and t for non-habits. And I can't spot an
>> error in org-print-icalendar-entries, but I can't say I understand  
>> it.
> ---Zitatende---
>
> -- 
>        Friedrich Delgado Friedrichs <friedel@nomaden.org>
>                             TauPan on Ircnet and Freenode ;)
>
>
> _______________________________________________
> 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

- Carsten

Re: Feature request about habit tracking [was: RELEASE: Org-mode version 6.32]

[Friedrich Delgado Friedrichs]

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

Carsten Dominik schrieb:
> You mean the file is empty only if you set orv-icalendar-verify-
> function????

Yes, exactly. When org-icalendar-verify-function is not bound, I get
the normal entries in the icalendar file, if I set it to the function
you gave me, it's empty.

This may be related to other parts of my setup.

 '(org-icalendar-categories (quote (all-tags category todo-state)))
 '(org-icalendar-include-body 1000)
 '(org-icalendar-include-sexps nil)
 '(org-icalendar-include-todo nil)
 '(org-icalendar-store-UID t)
 '(org-icalendar-timezone "Europe/Berlin")
 '(org-icalendar-use-deadline (quote (event-if-not-todo event-if-todo)))
 '(org-icalendar-use-plain-timestamp nil)
 '(org-icalendar-use-scheduled (quote (event-if-not-todo event-if-todo)))

Anything else that might be relevant?


-- 
        Friedrich Delgado Friedrichs <friedel@nomaden.org>
                             TauPan on Ircnet and Freenode ;)

[-- Attachment #1.2: Type: application/pgp-signature, Size: 198 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: Feature request about habit tracking [was: RELEASE: Org-mode version 6.32]

[Carsten Dominik]

I guess it is not only empty, but export throws an error?

Should be fixed now...

- Carsten


On Nov 5, 2009, at 11:06 PM, Friedrich Delgado Friedrichs wrote:

> Carsten Dominik schrieb:
>> You mean the file is empty only if you set orv-icalendar-verify-
>> function????
>
> Yes, exactly. When org-icalendar-verify-function is not bound, I get
> the normal entries in the icalendar file, if I set it to the function
> you gave me, it's empty.
>
> This may be related to other parts of my setup.
>
> '(org-icalendar-categories (quote (all-tags category todo-state)))
> '(org-icalendar-include-body 1000)
> '(org-icalendar-include-sexps nil)
> '(org-icalendar-include-todo nil)
> '(org-icalendar-store-UID t)
> '(org-icalendar-timezone "Europe/Berlin")
> '(org-icalendar-use-deadline (quote (event-if-not-todo event-if- 
> todo)))
> '(org-icalendar-use-plain-timestamp nil)
> '(org-icalendar-use-scheduled (quote (event-if-not-todo event-if- 
> todo)))
>
> Anything else that might be relevant?
>
>
> -- 
>        Friedrich Delgado Friedrichs <friedel@nomaden.org>
>                             TauPan on Ircnet and Freenode ;)
> _______________________________________________
> 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

- Carsten

Re: Feature request about habit tracking [was: RELEASE: Org-mode version 6.32]

[Friedrich Delgado Friedrichs]

Carsten Dominik schrieb:
> I guess it is not only empty, but export throws an error?
Not sure, I haven't seen one.
> Should be fixed now...

Yup! Thanks a lot! ;)

-- 
        Friedrich Delgado Friedrichs <friedel@nomaden.org>
                             TauPan on Ircnet and Freenode ;)