When using `org-complete' on keywords like #+TBLFM, a second call to
`org-complete' would throw an error with no helpful message. It now
fails silently.
I also moved #+DATE to the list of options, since the user might expect
that using `org-complete' twice on it will insert the default date.
Other changes: removed (current-time) from (format-time-string ...)
sexp since it is not necessary. As far as I checked, there is no
compatibility issue with this.
This files are stil all loaded automatically, but the user can turn
individual files off. Also, this makes maintaining the link
stuff easier, because everything related to a specific link type
is in one place.
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.
In particular, this implements default dates for deadlines and
scheduled items, taken from previously existing deadline/scheduled
timestamps in the same entry.
Also we fix two minor bugs.
(org-publish-expand-components): Remove null projects from the list of
components.
(org-publish-attachment): Bugfix: handle the mandatory argument pub-dir.
Removed unused retrieval of the :publishing-directory property.
(org-publish-file): Bugfix: when using a relative directory as the
publishing directory, convert it to a directory filename.
(org-publish-project): New alias for `org-publish'
To save time, we don't re-initialize the list of projects/files each
time a file is published. But if people want to publish a file that
they just created, this file is not part of any project until the
list of project/files has been re-initialized.
If the file is not part of a project and should be, then the user
can tell so.
Throw an error when `org-publish-current-file' is called on a file that
is not part of any project. Publishing a single file that is not part
of a project is already done by simply exporting it, so the user should
be warned about this.
This patch implements a way to limit the iCalendar export to
the entries listed in any agenda view. It is implemented as a way to
export an agenda view (using C-x C-w) in the agenda, but internally
it really is a limited iCalendar export.
(list-diary-entries-hook): Declare for compiler.
(org-get-entries-from-diary): Require diary-lib.
Ref in the emacs-diffs mailing list:
<E1JXpsE-0008A3-19@cvs.savannah.gnu.org>
There mechanisms were asked for by Wanrong Lin and Reiner Stengele and
have the goal to make sure the new deadline/scheduled/time is in
the future, and may be chosen relative to the current date.
Whether a buffer is created or not depends on publishing functions such
as `org-export-as-html' and the like. But not all such functions create
a new buffer (e.g. `org-publish-attachment'), so we need to delete the
buffer if it differs from the last buffer we we're in before export.
Timestamp editing did not work correctly. The deadline warning days
could not be edited, and editing the end of a time range did
not respect the new granularity. Seems to work now.
Moved (eval-after-load "org" '(org-load-default-extensions))
after the definition of org-load-default-extensions.
Bugfix in `org-agenda-schedule': don't display marker type when `nil'.
Bastien Guerry
Carsten Dominik
Phil Jackson