This only lead to a contributed file, this is neither robust nor fast.
But maybe throwing the existing code into a contrib file
will make someone come up with an idea.
The #+STARTUP etc lines that define settings on a per-file
basis can now be collected in a separate file and included
with a line:
#+SETUPFILE: "/path/to/setup.org"
This has been a frequent request in the past, now it is
finally possible.
These are implemented as part of plain lists, so a leading
"-" or "+" is still needed. Maybe this is not the most pretty
implementation, but it works without rewriting the quite
complex list formatting code. So all the list formatting
continues to work just fine. The description tag
is highlighted in bold, so still easy to spot.
The HTML exporter does export these already, the LaTeX
exporter still needs to be adapted.
Recently clocked tasks are now remembered as well as a default
task and an interrupted task.
There is no automatic clock-in yet.
Also, a number of bug fixes have sneaked into this patch,
sorry for the mess.
So far only internal links that lead to a dedicated target where
converted correctly during HTML export. Now, also heuristic
links create a working jump in a file.
This is a new display mode in the agenda view. It appends a clock
table to the daily/weekly agenda view that covers clocked time
for the time span shown in the agenda, and also limited to the
files that were used to create the current view.
The clocktable can now more easily select the correct time range
that should be considered when summing times. S-right and S-left
in the "#+BEGIN: clocktable" line allow to shift the time block around.
Also some code-cleanup.
Tags can now be selected for inheritance by using a list or a regular
expression.
Also for property inheritance, we now allow a regular
expression (list selection existed before).
The property API can now retrieve the value of a property
with inheritance based on the value of
`org-use-property-inheritance'. Earlier this value was ignored
when querying an entry. It still is ignored by default, but by
passing `selective' as the INHERIT flag, it can now be used.
ISO week dates can now be entered at the date prompt.
The ISO week of each day is displayed in the agenda.
New jumping commands like `43 w' quickly switch the agenda
to a certain week.
This system works by configuring a variable that contains a list of
all available modules. These will automatically be loaded when the
first buffer is turned into org-mode, or when a global command
is run that needs org-mode code available (such are
org-store-link.
Carsten Dominik
Bastien Guerry