The relative timer is now shown in the mode-line while running.
There is a new command to pause and continue it.
Thanks to Alan Davis for driving this change.
The variable `org-blank-before-new-entry' regulates if Org should
insert a blank line before a new entry, when making a new headline or
plain list item. Up to now, the possible values in each case where t
or nil, i.e. unconditionally do or don't insert a blank line.
Now each setting can also be `auto'. If this is the case, Org will
look if the current entry, of which the command creates a sibling,
does have a blank line before it. If yes, it will also make a blank
line. If not, it will not. This seems so useful that I have made
this behavior the default.
Bernt Hansen writes:
I've been bad and let a couple of my overhead tasks slip past
their deadline dates.
*** TODO Q1 Accounting: October
DEADLINE: <2008-11-30 Mon +1y>
- CLOSING NOTE [2008-01-30 Wed 12:18]
This task does not show up on my agenda anymore (probably because
the year changed). If I change the deadline entry to this:
DEADLINE: <2008-11-30 Mon>
then it shows up as 37 days late. I'm bringing this up as soon as
I noticed it just so people are aware of this. I have a few of
these tasks that just dropped off my agenda (probably at the
beginning of the year).
This interesting bug seems only to happen when the repeat is yearly,
and after crossing the December 31st year boundary. It was a sorting
issue - Org-mode (in the function `org-closest-date') computes two
dates that are consistent with the repeater, one before and one after
the target date. When the computation is done with a preference for
the past date (as it happens for deadlines), it should use the earlier
date. In fact, it did choose "n1", assuming that it was the earlier
one. This assumption does hold for daily, weekly and monthly
repeaters, but not for yearly ones.
This commits make sure that "n1" always holds the earlier date, so
that the logic at the end of the function works again.
This commit removes some of the stuff that was specific for the LaTeX
exporter, and falls back to the default configuration that works for
all backends.
Here is what the commit does:
- The variable `org-export-latex-remove-from-headlines' is now
obsolete. Instead, also LaTeX export now responds to the settings
in the variables org-export-with-todo-keywords',
`org-export-with-priority', and `org-export-with-tags' and in the
corresponding OPTION settings.
- Removal of time stamps and related keywords now already happens in
the preprocessor, so that it will be perfectly the same for all
backends.
- The list functions have been extended to accept an additional
parameter list, to overrule the default setting for a particular
list function. This is used to make the checkbox appearance in
LaTeX configurable, through the new variable
`org-export-latex-list-parameters'.
Column view could fail when the agenda contains entries from the Diary
which start with a *. This commit fixes this problems by making
`org-entry-properties' check for an org-mode buffer.
An agenda series can have a set of global options. Matt Lundin
reported that these options to not work completely. There reason was
that, when calling `org-finalize-agenda' for a series, the dynamic
binding of those options was already off again. This commit makes
sure that these bindings are available also during this final step.
When using "C-u C-u M-x org-remember RET" in order to jump to the last
storage location, the code failed to show the matching entry. This
commit makes sure that at least the headline of the last remember note
is made visible.
With the "* Footnotes" heading as last line in the buffer, footnote
insertion did not position new definitions correctly. This commit
fixes the problem.
Reported by Matt Lundin.
This commit adds an option to org-w3m, to decide whether the mark
should be deactivated after copying the region.
New version from author Andy Steward.
The new export switches -n, +n, and -r for the BEGIN_EXAMPLE and
BEGIN_SRC constructs are now supported by org-mtags.el.
Also fixes some bugs in org-mtags.el.
Sorting footnotes used to be almost like normalization, in that all
footnotes would be collected into a single location. Now sorting
respects the setting of `org-footnote-section'. If that is nil,
sorting will actually move each footnote into the outline node of its
first reference.
This commit add a new face for footnote labels, and activates footnote
labels for mouse clicks and for `C-c C-o', to jump to the
corresponding reference or definition.
This patch implements fully automatic creation of unique labels for
footnotes, which is also turned on as the default setting. The
automatic labels look like [fn:1], [fn:2], etc, using the first
available unused number.
The commit introduces a new variable, `org-footnote-auto-label' with a
number of different options ranging from no auto creation (prompting
the user for a label) to fully automatic creation.
Also, the commit introduces new #+STARTUP options that can be used to
select these settings on a per-file basis.
There was a bug with documents with more than one anonymous footnotes,
which would all end up to reference the first one only. The patch
fixes this problem.
Setting org-footnote-section to nil now causes definitions to be
inserted at the end of the current outline node, instead of into a
special node names "Footnotes".
A new perl program, list-hooks.pl, now extracts the full list of hook
and function variables in Org, for inclusion into Worg's org-hooks.org.
Also, add a docstring to a few hooks that did not have one.
This patch introduces more hooks for preprocessing the export buffer,
at various strategic moments. See the Changes.org file for a
description of the hooks.
Org-mode allows multiple references to the same footnote. However,
the HTML exporter cannot use the same name for all these references,
because names have to be unique. This patch appends numbers to
footnote reference names, to make sure they remain unique.
The dark side of this patch means that from the footnote definition,
there is only a single link, to the first reference of the note.
However, in a browser you can always press BACK to go back after
jumping to a footnote definition.
Carsten Dominik