6355 lines
140 KiB
HTML
6355 lines
140 KiB
HTML
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
|
|
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
|
<html xmlns="http://www.w3.org/1999/xhtml"
|
|
lang="en" xml:lang="en">
|
|
<head>
|
|
<title>Org-mode list of User-visible changes</title>
|
|
<meta http-equiv="Content-Type" content="text/html;charset=iso-8859-1"/>
|
|
<meta name="generator" content="Org-mode"/>
|
|
<meta name="generated" content="2008/01/25 14:14:58"/>
|
|
<meta name="author" content="Carsten Dominik"/>
|
|
<style type="text/css">
|
|
html {
|
|
font-family: Times, serif;
|
|
font-size: 12pt;
|
|
}
|
|
.title { text-align: center; }
|
|
.todo { color: red; }
|
|
.done { color: green; }
|
|
.timestamp { color: grey }
|
|
.timestamp-kwd { color: CadetBlue }
|
|
.tag { background-color:lightblue; font-weight:normal }
|
|
.target { background-color: lavender; }
|
|
pre {
|
|
border: 1pt solid #AEBDCC;
|
|
background-color: #F3F5F7;
|
|
padding: 5pt;
|
|
font-family: courier, monospace;
|
|
}
|
|
table { border-collapse: collapse; }
|
|
td, th {
|
|
vertical-align: top;
|
|
<!--border: 1pt solid #ADB9CC;-->
|
|
}
|
|
</style>
|
|
</head><body>
|
|
<h1 class="title">Org-mode list of User-visible changes</h1>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 5.20</h2>
|
|
|
|
|
|
|
|
<div class="outline-3">
|
|
<h3>Overview</h3>
|
|
|
|
|
|
</div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Incompatible Changes</h3>
|
|
|
|
|
|
</div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Details</h3>
|
|
|
|
|
|
<p>
|
|
+————+–——————+-——————+-————+
|
|
+————+–——————+-——————+-————+
|
|
+————+–——————+-——————+-————+
|
|
+————+–——————+-——————+-————+
|
|
+————+–——————+-——————+-————+
|
|
</p>
|
|
<ul>
|
|
<li>
|
|
The variable `org-remember-use-refile-when-interactive'
|
|
introduced only in 5.19 is obsolete. Please use
|
|
`org-remember-interactive-interface' instead. This new
|
|
variable does select the interface that is used to select
|
|
the target for a remember note. Possible values are:
|
|
FIXME:
|
|
|
|
</li>
|
|
<li>
|
|
You can now also have a plain (as opposed to deadline or
|
|
scheduled) repeater timestamp in a task. Switching the task
|
|
to DONE will now also shift a plain time stamp. This was a
|
|
request by Austin Frank.
|
|
|
|
</li>
|
|
<li>
|
|
It is no longer necessary to update the refiling targets -
|
|
they are always current.
|
|
|
|
</li>
|
|
<li>
|
|
`C-u C-c C-w' allows you to jump to a refiling location.
|
|
|
|
</li>
|
|
<li>
|
|
`C-u C-u C-c C-w' uses the refile interface to jum to any
|
|
headline in the current file.
|
|
|
|
</li>
|
|
<li>
|
|
In `org-goto', typing characters now automatically starts
|
|
isearch from the beginning of the buffer. The isearch is
|
|
special also because it only matches in headline. This goes
|
|
some way toward saving org-goto from being removed from
|
|
Org-mode. Thanks to Piotr Zielinski for the code, and sorry
|
|
that it took me o long to ut it in. If you prefer to use
|
|
single letters n,p,f,b,u,q for navigation as before,
|
|
configure the variable `org-goto-auto-isearch'.
|
|
|
|
</li>
|
|
<li>
|
|
The clock table accepts a new parameter <code>:step</code>. This
|
|
parameter can be `day' or `week' and will result in separate
|
|
tables for each day or week in the requested time interval.
|
|
This was triggered by a proposal by Sacha Chua in her <a href="http://sachachua.com/wp/2007/12/30/clocking-time-with-emacs-org/">blog</a>.
|
|
|
|
</li>
|
|
<li>
|
|
A time-stamp with a repeater now no longer refers to the
|
|
date <b>closest</b> to the current day. Instead, it means either
|
|
today or the most recent match. This change makes sure that
|
|
overdue scheduled or deadline items never disappear from the
|
|
agenda. With the previous convention, an overdue sheduled
|
|
item would disappear. For example, a weekly item scheduled
|
|
for Sunday would appear as overdue until Wednesday, and the
|
|
suddenly disappear until next Sunday. Now the item will
|
|
show up as "Sched 7x" on Saturday. From Sunday on it will
|
|
be in the list as "Scheduled", i.e. old sins will be
|
|
forgiven. This follows a request by Warong, Dennis and
|
|
Bernt.
|
|
|
|
</li>
|
|
<li>
|
|
Archving a subtree now creates an additional property,
|
|
<code>ARCHIVE_OLPATH</code>. This property contains the "path" in the
|
|
outline tree to the archived entry, as it was in the
|
|
original file. For example, archiving <code>Fix the door</code> in the
|
|
following hierarchy
|
|
|
|
<p>
|
|
<pre>
|
|
* Tasks
|
|
** HOME
|
|
*** Garage
|
|
**** Fix the door
|
|
</pre>
|
|
</p>
|
|
<p>
|
|
will file is with the following property
|
|
</p>
|
|
<p>
|
|
<pre>
|
|
:ARCHIVE_PATH: Task/HOME/Garage
|
|
</pre>
|
|
</p>
|
|
<p>
|
|
Note that you can configure (i.e. limit) the information
|
|
that gets stored upon archiving with the variable
|
|
`org-archive-save-context-info'.
|
|
</p>
|
|
</li>
|
|
</ul></div>
|
|
</div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 5.19</h2>
|
|
|
|
|
|
|
|
<div class="outline-3">
|
|
<h3>Overview</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
Column view can list the clocked times of a subtree.
|
|
|
|
</li>
|
|
<li>
|
|
Storing remember notes can use the `org-refile' interface.
|
|
|
|
</li>
|
|
<li>
|
|
Storing remember notes no longer produced empty lines.
|
|
|
|
</li>
|
|
<li>
|
|
Moving subtrees now folds all siblings of the subtree.
|
|
|
|
</li>
|
|
<li>
|
|
New variable `org-agenda-todo-keyword-format'.
|
|
|
|
</li>
|
|
<li>
|
|
Hack to allow brackets in link descriptions.
|
|
|
|
</li>
|
|
<li>
|
|
Clocking into an entry can enforce a specific TODO state.
|
|
|
|
</li>
|
|
<li>
|
|
EXPORT_FILE_NAME may be an absolute file name with "~".
|
|
|
|
</li>
|
|
<li>
|
|
Bug fixes, lots of them.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Details</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
A new special column definition lists the sum of all CLOCK
|
|
entries in a subtree. For example
|
|
|
|
<p>
|
|
<pre>
|
|
#+COLUMNS: %20ITEM %10Time_Estimate{:} %CLOCKSUM
|
|
</pre>
|
|
</p>
|
|
<p>
|
|
will allow you to compare estimated times (as given in the
|
|
Time_Estimate property) with the clocked times. This was a
|
|
request by Bernt Hansen.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
Storing remember notes can now use the `org-refile'
|
|
interface instead of the `org-goto' interface (see the
|
|
variable `org-remember-use-refile-when-interactive').
|
|
Nothing will change if the note is stored immediately after
|
|
pressing `C-c C-c' in the <code>*Remember*</code> buffer. But if you
|
|
have chosen (e.g. by pressing `C-u C-c C-c') to
|
|
interactively select the filing location (file and
|
|
headline), the refile interface will be used instead. I am
|
|
excited about this change, because the `org-goto' interface
|
|
is basically a failure, at least for this application. Note
|
|
that in any case the refile interface has to be configured
|
|
first by customizing `org-refile-targets'.
|
|
|
|
</li>
|
|
<li>
|
|
Notes inserted with remember now remove any whitespace
|
|
before and after the note before being pasted, so that there
|
|
will be no empty lines inserted together with the note. We
|
|
could invent special syntax in remember templates to allow
|
|
creating empty lines before a note - is there anyone who'd
|
|
want this?
|
|
|
|
</li>
|
|
<li>
|
|
Moving subtrees now folds all siblings of the subtree. This
|
|
is the only reasonably simple way I could find to avoid the
|
|
reported inconsistencies in the folding state of the outline
|
|
tree after moving entries. There are reasons to like this
|
|
new behavior, because it easily visualizes where the tree is
|
|
located after the move. Still, not everyone might be happy
|
|
with this. Massive complaining would be needed to make me
|
|
fix this.
|
|
|
|
</li>
|
|
<li>
|
|
New variable `org-agenda-todo-keyword-format' to specify the
|
|
width of the TODO keyword field in the agenda display. Use
|
|
it to get things to line up better. This was a proposal by
|
|
Rainer Stengele.
|
|
|
|
</li>
|
|
<li>
|
|
If a link description inserted with `C-c C-l' contains
|
|
brackets, the brackets will now be converted into curly
|
|
braces. This looks similar enough. Supporting brackets in
|
|
link descriptions is, for technical reasons too long to
|
|
explain here, complex.
|
|
|
|
</li>
|
|
<li>
|
|
The new option `org-clock-in-switch-to-state' can be set to
|
|
a TODO state that will be enforced when the clock is started
|
|
on an entry. This follows an idea by Sacha Chua.
|
|
|
|
</li>
|
|
<li>
|
|
The EXPORT_FILE_NAME property may now also be an absolute
|
|
file name, and it may contain abbreviations like "~" for the
|
|
users home directory. This was requested by Adam Spiers.
|
|
|
|
</li>
|
|
<li>
|
|
Bug fixes, lots of them.
|
|
|
|
</li>
|
|
</ul></div>
|
|
</div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 5.18</h2>
|
|
|
|
|
|
<p>
|
|
Minor fixes.
|
|
</p>
|
|
</div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 5.17</h2>
|
|
|
|
|
|
|
|
<div class="outline-3">
|
|
<h3>Details</h3>
|
|
|
|
|
|
|
|
<div class="outline-4">
|
|
<h4>Whitespace</h4>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
When cutting, pasting, or moving subtrees and items, the
|
|
empty lines <b>before</b> the subtree/item now belong to the
|
|
part and will be moved with it. There is one exception to
|
|
this rule: If the first child is moved down (or,
|
|
equivalently, the second is moved up), the amount of empty
|
|
lines <b>above</b> the first child to be moved along with it is
|
|
limited by the number of empty lines <b>below</b> it. This
|
|
sounds complicated, but it allows to have extra empty space
|
|
before the first child and still have good behavior of the
|
|
subtree motion commands.
|
|
|
|
</li>
|
|
<li>
|
|
Plain lists items work the same.
|
|
|
|
</li>
|
|
</ul>
|
|
<p>I believe we have finally nailed this one. Thanks to Daniel
|
|
Pittman for bring this up again and to Eric Schulte for
|
|
pointing out that it is the empty lines <b>before</b> an entry
|
|
that really count.
|
|
</p>
|
|
<p>
|
|
This change was non-trivial, please give it a good test and
|
|
let me know about any problems.
|
|
</p>
|
|
</div>
|
|
|
|
<div class="outline-4">
|
|
<h4>Remember</h4>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
The new command `org-remember-goto-last-stored' will jump
|
|
to the location of the remember note stored most recently.
|
|
If you have `org-remember' on a key like `C-c r', then you
|
|
can go to the location with a double prefix arg: `C-u C-u
|
|
C-c r'. This was a proposal by Rainer Stengele.
|
|
|
|
</li>
|
|
<li>
|
|
Template items that are being prompted for can now specify
|
|
a default value and a completion table. Furthermore,
|
|
previous inputs at a specific prompt are captured in a
|
|
history variable. For example:
|
|
|
|
<p>
|
|
<pre>
|
|
%^{Author|Roald Dahl|Thomas Mann|Larry Niven}
|
|
</pre>
|
|
</p>
|
|
<p>
|
|
will prompt for an author name. Pressing RET without
|
|
typing anything will select "Roald Dahl". Completion will
|
|
give you any of the three names. And a history will be
|
|
kept, so you can use the arrow keys to get to previous
|
|
input. The history is tied to the prompt. By using the
|
|
same prompt in different templates, you can build a history
|
|
across templates. The ideas for this came from proposals
|
|
by Bastien and Adam.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
When a remember template contains the string `%!', the note
|
|
will be stored immediately after all template parts have
|
|
been filled in, so you don't even have to press `C-c
|
|
C-c'. The was a proposal by Adam Spiers.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-4">
|
|
<h4>Refile</h4>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
`org-refile-targets' has a new parameter to specify a
|
|
maximum level for target selection. Thanks to Wanrong Lin
|
|
for this proposal.
|
|
|
|
</li>
|
|
<li>
|
|
When the new option `org-refile-use-outline-path' is set,
|
|
refile targets will be presented like a file path to the
|
|
completion interface: "level 1/level 2/level 3". This
|
|
may be the fastest interface yet to get to a certain
|
|
outline entry. Do we need to use this interface in other
|
|
places? Thanks to Jose Ruiz for this proposal.
|
|
|
|
</li>
|
|
</ul></div>
|
|
</div>
|
|
</div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 5.16</h2>
|
|
|
|
|
|
|
|
<div class="outline-3">
|
|
<h3>Details</h3>
|
|
|
|
|
|
|
|
<div class="outline-4">
|
|
<h4>Restriction lock on agenda scope</h4>
|
|
|
|
|
|
<p>
|
|
You can now permanently lock the agenda construction to a
|
|
certain scope, like a file or a subtree. So instead of
|
|
pressing "<" for each command in the agenda dispatcher, you
|
|
only once select a restriction scope. All subsequent agenda
|
|
commands will than respect this restriction. For example,
|
|
you can use this at work, to limit agendas to your work file
|
|
or tree, and at home to limit to the home file or tree. Or
|
|
you can use it during the day in order to focus in on certain
|
|
projects.
|
|
</p>
|
|
<p>
|
|
You select a scope with the command `C-c C-x <', which
|
|
restricts to the current subtree. When called with a `C-u'
|
|
prefix, the restriction is to the current file. You can also
|
|
make restrictions from the speedbar frame, see below.
|
|
</p>
|
|
<p>
|
|
When making a new restriction and an agenda window is
|
|
currently visible, it will immediately be updated to reflect
|
|
the new scope. TO if you like you can display an agenda view
|
|
and then watch it change in various scopes.
|
|
</p>
|
|
<p>
|
|
To get rid of the restriction, use the command "C-c C-x >".
|
|
Or press ">" in the agenda dispatcher. Also, and use of "<"
|
|
in the dispatcher will disable the restriction lock and
|
|
select a new restriction.
|
|
</p>
|
|
<p>
|
|
Thanks to Rick Moynihan for triggering this development.
|
|
</p>
|
|
</div>
|
|
|
|
<div class="outline-4">
|
|
<h4>Imenu and Speedbar support</h4>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
Org-mode now supports Imenu. For example, with the setting
|
|
|
|
<p>
|
|
<pre>
|
|
(add-hook 'org-mode-hook
|
|
(lambda () 'imenu-add-to-menubar "Imenu"))
|
|
</pre>
|
|
</p>
|
|
<p>
|
|
a menu will be created in each Org-mode buffer that
|
|
provides access to all level 1 and level 2 headings. The
|
|
depth of the menu can be set with the variable
|
|
`org-imenu-depth'.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
org-mode now supports Speedbar. This means that you can
|
|
drill into the first and second level headlines of an
|
|
Org-mode file right from the speedbar frame.
|
|
|
|
</li>
|
|
<li>
|
|
You can set a restriction lock for the Org-mode agenda to a
|
|
file or a subtree directly from the speedbar frame. Just
|
|
press "<" with the cursor on an Org-mode file or subtree to
|
|
set the lock and immediately update the agenda if it is
|
|
visible. Use ">" to get rid of the lock again.
|
|
|
|
</li>
|
|
</ul></div>
|
|
</div>
|
|
</div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 5.15</h2>
|
|
|
|
|
|
|
|
<div class="outline-3">
|
|
<h3>Details</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
There are new special properties TIMESTAMP and TIMESTAMP_IA.
|
|
These can be used to access the first keyword-less active
|
|
and inactive timestamp in an entry, respectively.
|
|
|
|
</li>
|
|
<li>
|
|
New variable `org-clock-heading-function'. It can be set to
|
|
a function that creates the string shown in the mode line
|
|
when a clock is running. Thanks to Tom Weissmann for this
|
|
idea.
|
|
|
|
</li>
|
|
<li>
|
|
Bug fixes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
</div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 5.14</h2>
|
|
|
|
|
|
|
|
<div class="outline-3">
|
|
<h3>Overview</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
Remember and related stuff
|
|
<ul>
|
|
<li>
|
|
New command `org-refile' to quickly move a note.
|
|
</li>
|
|
<li>
|
|
Easy way to jump to the target location of remember template.
|
|
</li>
|
|
<li>
|
|
New %-escapes in remember templates: %c %(…) and %[…]
|
|
</li>
|
|
<li>
|
|
`org-remember-insinuate' simplifies remember setup
|
|
|
|
</li>
|
|
</ul></li>
|
|
<li>
|
|
Emphasis and Font-lock stuff
|
|
<ul>
|
|
<li>
|
|
Stacked emphasis is no longer allowed.
|
|
</li>
|
|
<li>
|
|
You may finally emphasize a single character like *a*.
|
|
</li>
|
|
<li>
|
|
Font-lock now can hide the emphasis markers
|
|
</li>
|
|
<li>
|
|
Text in the "=" emphasis is exported verbatim
|
|
</li>
|
|
<li>
|
|
There is a new emphasis marker "~" for verbatim text
|
|
</li>
|
|
<li>
|
|
Constructs treated specially by the exporters can be highlighted
|
|
|
|
</li>
|
|
</ul></li>
|
|
<li>
|
|
Properties and Column view
|
|
<ul>
|
|
<li>
|
|
More control over which properties use inheritance
|
|
</li>
|
|
<li>
|
|
CATEGORY="work" can now be used in a tags/property search
|
|
</li>
|
|
<li>
|
|
the {+} summary type can specify a printf-style output format
|
|
</li>
|
|
<li>
|
|
New currency summary type {$}
|
|
|
|
</li>
|
|
</ul></li>
|
|
<li>
|
|
The date/time prompt
|
|
<ul>
|
|
<li>
|
|
While entering data, watch live the current interpretation.
|
|
</li>
|
|
<li>
|
|
The date prompt now prefers to select the future
|
|
</li>
|
|
<li>
|
|
Easier modification of time in an existing time stamp.
|
|
|
|
</li>
|
|
</ul></li>
|
|
<li>
|
|
Export
|
|
<ul>
|
|
<li>
|
|
You can now export some special strings in HTML, like "…"
|
|
</li>
|
|
<li>
|
|
#+EMAIL: may contain several email addresses
|
|
|
|
</li>
|
|
</ul></li>
|
|
<li>
|
|
Agenda
|
|
<ul>
|
|
<li>
|
|
In the agenda, a few keys have changed: `g', `G', and `e'.
|
|
|
|
</li>
|
|
</ul></li>
|
|
<li>
|
|
Miscellaneous
|
|
<ul>
|
|
<li>
|
|
Class-dependent sectioning structures in LaTeX export.
|
|
</li>
|
|
<li>
|
|
Radio-lists modeled after the radio tables.
|
|
</li>
|
|
<li>
|
|
The default for `org-ellipsis' is back to nil
|
|
</li>
|
|
<li>
|
|
Support for pabbrev-mode
|
|
</li>
|
|
<li>
|
|
New variable `org-show-entry-below'.
|
|
|
|
</li>
|
|
</ul></li>
|
|
</ul></div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Incompatible changes</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
If you have customized the variable `org-emphasis-alist' or
|
|
org-export-emphasis-alist', you need to do it again by first
|
|
canceling your customization and then adding it again.
|
|
|
|
</li>
|
|
<li>
|
|
I know that some people have defined their own private helper
|
|
functions to select a specific remember template, without being
|
|
prompted, like this:
|
|
|
|
<p>
|
|
<pre>
|
|
(defun my-remember-template-n ()
|
|
(interactive)
|
|
(org-remember ?n))
|
|
</pre>
|
|
</p>
|
|
<p>
|
|
You need to modify this. The character selecting the template
|
|
must now be the <i>second</i> argument to `org-remember':
|
|
</p>
|
|
<p>
|
|
<pre>
|
|
(defun my-remember-template-n ()
|
|
(interactive)
|
|
(org-remember nil ?n))
|
|
</pre>
|
|
</p>
|
|
</li>
|
|
<li>
|
|
`C-c C-w' now refiles an entry. To get a sparse tree of
|
|
deadlines, use `C-c / d' instead.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Details</h3>
|
|
|
|
|
|
|
|
<div class="outline-4">
|
|
<h4>Remember and related stuff</h4>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
New command `org-refile' to quickly move a note to a
|
|
different place. It is bound to `C-c C-w'. The foremost
|
|
application might be to put a note or task captured with
|
|
`remember' into the proper list or project. The command
|
|
offers a list of possible refiling targets for completion.
|
|
These are headings under which the entry will be inserted
|
|
as a subitem. By default, this will offer all top-level
|
|
headings in the current buffer, but you can configure the
|
|
variable `org-refile-targets' to get more complex
|
|
definitions. For example:
|
|
|
|
<p>
|
|
<pre>
|
|
(setq org-refile-targets '((nil . (:level . 2))))
|
|
</pre>
|
|
</p>
|
|
<p>
|
|
selects all level 2 headlines in the current buffer as
|
|
targets. And
|
|
</p>
|
|
<p>
|
|
<pre>
|
|
(setq org-refile-targets
|
|
'((org-agenda-files . (:tag . "refile"))))
|
|
</pre>
|
|
</p>
|
|
<p>
|
|
searches all agenda files and selects headlines that are
|
|
explicitly marked with the tag :refile: . Note that the
|
|
list of targets is built upon first use only, to rebuilt
|
|
it, call the command `C-c C-w' with a double prefix
|
|
argument.
|
|
</p>
|
|
<p>
|
|
This is based on an idea and example implementation by Max
|
|
Mikhanosha. Many thanks Max.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
You can now use a C-u prefix on `org-remember' to jump to
|
|
the location where a specific templates stores its notes.
|
|
For example, if you have `org-remember' bound to `C-c r',
|
|
then `C-u C-c r n' will get you to the file and headline
|
|
given in the template associated with the letter "n".
|
|
|
|
<p>
|
|
This was proposed by someone, but I have lost track who.
|
|
Sorry, and thanks anyway.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
New %-escapes in remember templates:
|
|
|
|
<p>
|
|
<pre>
|
|
%c insert the current clipboard, like C-y would do
|
|
%(..) evaluate Lisp expression and insert the result
|
|
%[..] include file
|
|
</pre>
|
|
</p>
|
|
<p>
|
|
Thanks to Adam Spiers and Tim O'Callaghan.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
New function `org-remember-insinuate' that makes is easier
|
|
to set Org-mode specific values for remember variables.
|
|
Thanks to Michael Olson for this proposal. It is
|
|
equivalent to:
|
|
|
|
<p>
|
|
<pre>
|
|
(require 'remember)
|
|
(setq remember-annotation-functions '(org-remember-annotation))
|
|
(setq remember-handler-functions '(org-remember-handler))
|
|
(add-hook 'remember-mode-hook 'org-remember-apply-template))
|
|
</pre>
|
|
</p>
|
|
<p>
|
|
You might still want to set `org-default-notes-file' to
|
|
provide a default for templates without a file, and
|
|
`org-directory' to show where to find other org files.
|
|
</p>
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-4">
|
|
<h4>Emphasis and Font-lock stuff</h4>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
Stacked emphasis like */bold italic/* is no longer allowed.
|
|
|
|
</li>
|
|
<li>
|
|
You may finally emphasize a single character like *a*.
|
|
|
|
</li>
|
|
<li>
|
|
Font-lock now can hide the emphasis markers, just like Muse
|
|
does. Configure the variable `org-hide-emphasis-markers'
|
|
if you want this. Showing the characters continues to be
|
|
the default in Org-mode.
|
|
|
|
</li>
|
|
<li>
|
|
Text in the "=" emphasis is now exported verbatim, i.e. no
|
|
further parsing and interpretation of this text takes place. So
|
|
you can write =quoted *xxx* a_x = b=. This and the following
|
|
point implement a request by Daniel Clemente.
|
|
|
|
</li>
|
|
<li>
|
|
There is a new emphasis marker "~" which marks text to be
|
|
exported verbatim, without special formatting. Inside an
|
|
org-mode file, this text is highlighted with the org-verbatim
|
|
face. I am not happy with the face yet (currently is is like
|
|
org-code, but underlined), please suggest a better one.
|
|
|
|
</li>
|
|
<li>
|
|
Whether an emphasis environment is verbatim or not is now an
|
|
extra flag in the variable `org-emphasis-alist'. If you have
|
|
configured this variable, do it again by first canceling your
|
|
customization to revert to the default, and then adding it
|
|
again.
|
|
|
|
</li>
|
|
<li>
|
|
New variable `org-highlight-latex-fragments-and-specials'.
|
|
When turned on, Org-mode will highlight all strings that
|
|
are treated in a special way by the exporters. This is
|
|
great for export-oriented writing, but maybe a bit noisy
|
|
for note taking, so this feature is off by default.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-4">
|
|
<h4>Properties and Column view</h4>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
`org-use-property-inheritance' may now also be a list of
|
|
property names that should be treated with inheritance
|
|
during searches.
|
|
|
|
</li>
|
|
<li>
|
|
CATEGORY="work" can now be used in a tags/property search,
|
|
even if the category is not specified as a property in the
|
|
entry, but rather is inherited or derived from #+CATEGORY.
|
|
Thanks to Adam, Tim, and Bastien for an interesting
|
|
discussion around this issue.
|
|
|
|
</li>
|
|
<li>
|
|
Summary type improvements in column view.
|
|
<ul>
|
|
<li>
|
|
The {+} summary type can specify a printf-style output
|
|
format for computed values like this: {+;%5.2f}
|
|
This was triggered by a report by Levin.
|
|
</li>
|
|
<li>
|
|
New currency summary type {$}, which so far is just a
|
|
shorthand for {+;%.2f}. Do we need to have a currency
|
|
symbol in front of each value. Scott Jaderholm asked for
|
|
this, but I am not sure if this is already what he meant.
|
|
|
|
</li>
|
|
</ul></li>
|
|
</ul></div>
|
|
|
|
<div class="outline-4">
|
|
<h4>The date/time prompt</h4>
|
|
|
|
|
|
<p>
|
|
There have been several small but <b>very</b> useful additions to
|
|
the date prompt.
|
|
</p>
|
|
<ul>
|
|
<li>
|
|
While entering data at the date prompt, the current
|
|
interpretation of your input is shown next to your input in
|
|
the minibuffer. I find this great to understand how the
|
|
input works. If you find the extra stuff in the minibuffer
|
|
annoying, turn it off with `org-read-date-display-live'.
|
|
|
|
</li>
|
|
<li>
|
|
The date prompt now prefers to select the future. If you
|
|
enter a date without a month, and the day number is before
|
|
today (for example, on the 16th of the month you enter
|
|
"9"), Org-mode will assume next month. Similarly, if you
|
|
enter a month and no year, next year will be assumed if the
|
|
entered month is before the current, for example if you
|
|
enter "May" in September. Thanks to John Rakestraw for
|
|
this great suggestion. If you find it confusing, turn it
|
|
off with `org-read-date-prefer-future'.
|
|
|
|
</li>
|
|
<li>
|
|
When modifying an existing date using `C-c .' at the stamp,
|
|
the time or time range in the stamp are now offered as
|
|
default input at the prompt. This goes a long way to
|
|
simplifying the modification of an existing date. Thanks
|
|
to Adam Spiers for this proposal.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-4">
|
|
<h4>Export (all implemented by Bastien…)</h4>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
You can now export special strings in HTML. Here is the
|
|
list of newly performed conversions:
|
|
|
|
<table border="2" cellspacing="0" cellpadding="6" rules="groups" frame="hsides">
|
|
<col align="left"></col><col align="left"></col><col align="left"></col><col align="left"></col>
|
|
<thead>
|
|
<tr><th>Command</th><th></th><th>C-u</th><th>C-u C-u</th></tr>
|
|
<tr><th>org-remember</th><th>select template and</th><th>select template and</th><th>goto location</th></tr>
|
|
<tr><th></th><th>store a note</th><th>go to its default</th><th>last used by</th></tr>
|
|
<tr><th></th><th></th><th>target</th><th>remember</th></tr>
|
|
<tr><th>org-refile</th><th>select a targer and</th><th>goto a target</th><th>goto location</th></tr>
|
|
<tr><th></th><th>refile subtree</th><th></th><th>last used by</th></tr>
|
|
<tr><th></th><th></th><th></th><th>refile</th></tr>
|
|
<tr><th>org-goto</th><th>go to a headline</th><th>Use outline-path-</th><th></th></tr>
|
|
<tr><th></th><th>selected from</th><th>completion to</th><th></th></tr>
|
|
<tr><th></th><th>outline f current</th><th>select the</th><th></th></tr>
|
|
<tr><th></th><th>buffer.</th><th>headline</th><th></th></tr>
|
|
<tr><th>Org</th><th>Description</th><th>HTML</th></tr>
|
|
</thead>
|
|
<tbody>
|
|
<tr><td>\\-</td><td>double backslash followed by minus</td><td>&shy;</td></tr>
|
|
<tr><td>--</td><td>two dashes (minuses)</td><td>&ndash;</td></tr>
|
|
<tr><td>---</td><td>three dashes (minuses)</td><td>&mdash;</td></tr>
|
|
<tr><td>...</td><td>three dots</td><td>&hellip;</td></tr>
|
|
</tbody>
|
|
</table>
|
|
|
|
|
|
<p>
|
|
You can turn this globally on or off with
|
|
`org-export-with-special-strings' or locally with "-:t" or
|
|
"-:nil" in the #+OPTIONS line. Thanks to Adam Spiers for
|
|
starting the discussion, and thanks to Daniel Clemente and
|
|
William Henney for relevant inputs.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
Comma-separated emails in #+EMAIL: are correctly exported.
|
|
Thanks to Raman for pointing out this omission.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-4">
|
|
<h4>Agenda</h4>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
In the agenda, a few keys have changed
|
|
<pre>
|
|
g does now the same a "r", refresh current display,
|
|
because "g" is the Emacs standard for "refresh"
|
|
G toggle the time grid, used to be "g"
|
|
e Execute another agenda command, pretty much the same as
|
|
`C-c a', but shorter and keep the same agenda window.
|
|
</pre>
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-4">
|
|
<h4>Miscellaneous (much of it from Bastien)</h4>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
You can now select the sectioning structure of your LaTeX
|
|
export by setting it either globally
|
|
(`org-export-latex-default-class') or locally in each Org
|
|
file (with #+LaTeX_CLASS: myclass). You can also customize
|
|
the list of available classes and their sectioning
|
|
structures through the new `org-export-latex-classes'
|
|
option. Thanks to Daniel for discussions and suggestion on
|
|
this issue.
|
|
|
|
</li>
|
|
<li>
|
|
You can send and receive radio lists in HTML,
|
|
LaTeX or TeXInfo, just as you send and receive radio
|
|
tables. Check the documentation for details and examples.
|
|
|
|
</li>
|
|
<li>
|
|
The default for `org-ellipsis' is back to nil, some people
|
|
seem to have had problems with the face as a default.
|
|
|
|
</li>
|
|
<li>
|
|
Support for pabbrev-mode, needs pabbrev version 1.1. Thanks
|
|
to Phillip Lord for adapting his package to make this
|
|
possible.
|
|
|
|
</li>
|
|
<li>
|
|
New variable `org-show-entry-below' to force context-showing
|
|
commands to expose the body of a headline that is being
|
|
shown. Thanks to Harald Weis for pointing out this omission.
|
|
|
|
|
|
</li>
|
|
</ul></div>
|
|
</div>
|
|
</div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 5.13i</h2>
|
|
|
|
|
|
|
|
<div class="outline-3">
|
|
<h3>Details</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
On the date/time prompt, you can now also answer with
|
|
something like +2tue to pick the second tuesday from today.
|
|
This was a proposal by Sacha Chua.
|
|
|
|
</li>
|
|
<li>
|
|
When interpopating into Lisp formulas in the spreadsheet,
|
|
the values of constants and properties are no longer
|
|
enclosed into parenthesis. When interpolating for calc,
|
|
this still happens in order to allow expressions in
|
|
constants. This problem was reported by Eddward DeVilla.
|
|
|
|
</li>
|
|
<li>
|
|
When a directory is listed in `org-agenda-files', all files
|
|
with extension matched by the new variable
|
|
`org-agenda-file-regexp' in that directory will be agenda
|
|
files.
|
|
|
|
</li>
|
|
<li>
|
|
Bug fixes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
</div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 5.13</h2>
|
|
|
|
|
|
|
|
<div class="outline-3">
|
|
<h3>Overview</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
Bug fixes and improvements in column view
|
|
<ul>
|
|
<li>
|
|
All known bugs fixed.
|
|
</li>
|
|
<li>
|
|
A Column view can be captured into a dynamic block.
|
|
</li>
|
|
<li>
|
|
The ITEM column is formatted core compactly.
|
|
</li>
|
|
<li>
|
|
Also ITEM can be edited with `e'
|
|
|
|
</li>
|
|
</ul></li>
|
|
<li>
|
|
The agenda dispatcher
|
|
<ul>
|
|
<li>
|
|
`<' cycles through restriction states.
|
|
</li>
|
|
<li>
|
|
Multi-character access codes to commands (= sub-keymaps).
|
|
|
|
</li>
|
|
</ul></li>
|
|
<li>
|
|
Sorting improvements
|
|
<ul>
|
|
<li>
|
|
User-defined sorting keys.
|
|
</li>
|
|
<li>
|
|
Sorting by properties.
|
|
</li>
|
|
<li>
|
|
Sorting of plain lists.
|
|
|
|
</li>
|
|
</ul></li>
|
|
<li>
|
|
HTML <div> structure
|
|
|
|
</li>
|
|
<li>
|
|
Other stuff
|
|
<ul>
|
|
<li>
|
|
New variables, several of them.
|
|
</li>
|
|
<li>
|
|
Drawers can be set on a per-file basis.
|
|
</li>
|
|
<li>
|
|
Better control over priority fontification in agenda.
|
|
</li>
|
|
<li>
|
|
M-up and M-down now move the current line up and down.
|
|
</li>
|
|
<li>
|
|
Abort remember template selection with C-g.
|
|
|
|
</li>
|
|
</ul></li>
|
|
</ul></div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Details</h3>
|
|
|
|
|
|
|
|
<div class="outline-4">
|
|
<h4>Bug fixes and improvements in column view</h4>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
All the bugs described by Scott Jaderholm have been fixed
|
|
(at least I hope so…).
|
|
|
|
</li>
|
|
<li>
|
|
You can now capture a column view into a dynamic block, for
|
|
exporting or printing it. The column view can be
|
|
|
|
<ul>
|
|
<li>
|
|
global, i.e. for the entire file
|
|
</li>
|
|
<li>
|
|
local, i.e. for the subtree where the dynamic block is
|
|
</li>
|
|
<li>
|
|
from an entry with a specific :ID: property.
|
|
|
|
</li>
|
|
</ul>
|
|
<p>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:
|
|
</p>
|
|
<p>
|
|
<pre>
|
|
* Planning
|
|
:PROPERTIES:
|
|
:ID: planning-overview
|
|
:END:
|
|
|
|
[...]
|
|
|
|
* The column view
|
|
#+BEGIN: columnview :hlines 1 :id "planning-overview"
|
|
|
|
#+END:
|
|
</pre>
|
|
</p>
|
|
<p>
|
|
Use `C-c C-x r' to insert such a dynamic block, and you will
|
|
be prompted for the ID.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
When the current column format displays 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.
|
|
|
|
</li>
|
|
<li>
|
|
You can now also edit the ITEM column with `e'.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-4">
|
|
<h4>The agenda dispatcher</h4>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
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.
|
|
|
|
</li>
|
|
<li>
|
|
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:
|
|
|
|
<p>
|
|
<pre>
|
|
(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")))
|
|
</pre>
|
|
</p>
|
|
</li>
|
|
<li>
|
|
The user function option in org-agenda-custom-commands may
|
|
now also be a lambda expression, following a request by
|
|
Adam Spiers.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-4">
|
|
<h4>Sorting improvements</h4>
|
|
|
|
|
|
<p>
|
|
We are using a new routine for sorting entries, courtesy of
|
|
John Wiegley. Many thanks to John.
|
|
</p>
|
|
<ul>
|
|
<li>
|
|
You can define your own function to extract a sorting key
|
|
and in this way sort entries by anything you like.
|
|
|
|
</li>
|
|
<li>
|
|
Entries can now be sorted according to the value of a
|
|
property.
|
|
|
|
</li>
|
|
<li>
|
|
Plain lists can be sorted.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-4">
|
|
<h4>HTML <div> structure</h4>
|
|
|
|
|
|
<p>
|
|
There is now a <div>-based structure in exported HTML.
|
|
</p>
|
|
<ul>
|
|
<li>
|
|
The table of context is wrapped into a div with a class
|
|
"table-of-contents".
|
|
|
|
</li>
|
|
<li>
|
|
The outline structure is embedded in <div> elements with
|
|
classes "outline-1", "outline-2" etc.
|
|
|
|
</li>
|
|
<li>
|
|
The postamble, containing the author information and the
|
|
date is wrapped into a div with class "postamble".
|
|
|
|
</li>
|
|
</ul>
|
|
<p>I am not sure if the class names are the best choice, let me
|
|
know if there are more "canonical" choices.
|
|
</p>
|
|
<p>
|
|
Thanks to Mike Newman and Cezar for input, and in particular
|
|
to Mike for his clearly formulated specification.
|
|
</p>
|
|
</div>
|
|
|
|
<div class="outline-4">
|
|
<h4>Other stuff</h4>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
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.
|
|
|
|
</li>
|
|
<li>
|
|
Drawers can be set on a per-file basis using
|
|
|
|
<p>
|
|
<pre>
|
|
#+DRAWERS: HIDDEN STATE PROPERTIES
|
|
</pre>
|
|
</p>
|
|
<p>
|
|
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.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
`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.
|
|
|
|
</li>
|
|
<li>
|
|
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.
|
|
|
|
</li>
|
|
<li>
|
|
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.
|
|
|
|
</li>
|
|
<li>
|
|
New variable `org-agenda-todo-ignore-with-date', based on a
|
|
request by Wanrong Lin.
|
|
|
|
</li>
|
|
<li>
|
|
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.
|
|
|
|
</li>
|
|
</ul></div>
|
|
</div>
|
|
</div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 5.12</h2>
|
|
|
|
|
|
|
|
<div class="outline-3">
|
|
<h3>Overview</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
Remember templates can now have name.
|
|
</li>
|
|
<li>
|
|
`C-c C-k' will abort taking a note (remember of log)
|
|
</li>
|
|
<li>
|
|
`C-c C-x C-w' and `C-c C-x M-w' now accept a prefix arg.
|
|
</li>
|
|
<li>
|
|
Lines in the agenda can be fontified according to priority.
|
|
</li>
|
|
<li>
|
|
New variable `org-scheduled-past-days'.
|
|
</li>
|
|
<li>
|
|
New variables `org-agenda-deadline-leaders' and
|
|
`org-agenda-scheduled-leaders'.
|
|
</li>
|
|
<li>
|
|
New sparse tree function `org-sparse-tree'.
|
|
</li>
|
|
<li>
|
|
The variable `org-ellipsis' now defaults to `org-link'.
|
|
</li>
|
|
<li>
|
|
The #+OPTIONS line has a new option "tags".
|
|
</li>
|
|
<li>
|
|
New variable `org-use-property-inheritance'.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Incompatible Changes</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
`C-c /' now calls `org-sparse-tree'.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Details</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
Remember templates can now have a template name as the first
|
|
element. The name will be listed along with the selection
|
|
character when prompting for a template. It is best to have
|
|
the name start with the selection character, for example if
|
|
you use ("Note" "n"), you will be prompted like "[n]ote".
|
|
Thanks to Matiyam for this proposal.
|
|
|
|
</li>
|
|
<li>
|
|
`C-c C-k' will abort taking a note. You can use this in remember
|
|
buffers and when taking a logging note (e.g. for a state
|
|
change). Thanks to Bastien.
|
|
|
|
</li>
|
|
<li>
|
|
`C-c C-x C-w' and `C-c C-x M-w' now accept a prefix arg to
|
|
cut N sequential subtrees. This was a proposal by John.
|
|
|
|
</li>
|
|
<li>
|
|
Lines in the agenda are now bold if they have priority A and
|
|
italic if they have priority C. You can turn this off using
|
|
the variable `org-agenda-fontify-priorities'. Thanks to
|
|
John Wiegley for the idea and code.
|
|
|
|
</li>
|
|
<li>
|
|
New variable `org-scheduled-past-days' to set the number a
|
|
scheduled item will be listed after its date has passed.
|
|
Default is 10000, i.e. indefinitely.
|
|
|
|
</li>
|
|
<li>
|
|
New variables `org-agenda-deadline-leaders' and
|
|
`org-agenda-scheduled-leaders' to adjust the leading text o
|
|
scheduled items and deadline in the agenda. Thanks to John
|
|
Wiegley for a patch.
|
|
|
|
</li>
|
|
<li>
|
|
New sparse tree function `org-sparse-tree'. This is now the
|
|
default binding for `C-c /'. It requires one additional
|
|
keypress to select a command, but in return is provides a
|
|
single interface to all the different sparse tree commands,
|
|
with full completion support.
|
|
|
|
</li>
|
|
<li>
|
|
The variable `org-ellipsis' now defaults to the face
|
|
`org-link' because the visibility of the dots is really bad
|
|
and I have found this change very useful indeed.
|
|
|
|
</li>
|
|
<li>
|
|
The #+OPTIONS line has a new option "tags" which can be used
|
|
to set `org-export-with-tags'. Thanks to Wanrong Lin for
|
|
this proposal.
|
|
|
|
</li>
|
|
<li>
|
|
New variable `org-use-property-inheritance'. Configure it
|
|
to `t' if you want that searching for entries with certain
|
|
properties always should assume inheritance. This is not
|
|
well tested yet, please check it out.
|
|
|
|
</li>
|
|
<li>
|
|
Bug fixes
|
|
|
|
</li>
|
|
</ul></div>
|
|
</div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 5.11</h2>
|
|
|
|
|
|
|
|
<div class="outline-3">
|
|
<h3>Overview</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
SUMMARY, DESCRIPTION, LOCATION properties for iCalendar
|
|
</li>
|
|
<li>
|
|
Command to jump to the running clock
|
|
</li>
|
|
<li>
|
|
Clock entries can now have their own drawer
|
|
</li>
|
|
<li>
|
|
`C-c C-x C-r' only updates a clocktable at point
|
|
</li>
|
|
<li>
|
|
New way to assign a remember template to a single key
|
|
</li>
|
|
<li>
|
|
`C-n' and `C-p' are back to their default binding
|
|
</li>
|
|
<li>
|
|
`C-x C-s' in agenda buffer saves all org-mode buffers
|
|
</li>
|
|
<li>
|
|
Schedule/deadline leaves note in agenda buffer
|
|
</li>
|
|
<li>
|
|
Prefix argument for `C-c C-d/s' will remove date
|
|
</li>
|
|
<li>
|
|
New variable to make block aranda more compact
|
|
</li>
|
|
<li>
|
|
Better tag alignment in agenda
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Incompatible changes</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
If you have customized `org-drawers', you need to add
|
|
"CLOCK" to the list of drawers.
|
|
|
|
</li>
|
|
<li>
|
|
The variable `org-agenda-align-tags-to-column' has been
|
|
renamed to `org-agenda-tags-column'. The old name is still
|
|
an alias, in Emacs 22 and in XEmacs, but not in Emacs 21.
|
|
|
|
</li>
|
|
<li>
|
|
The default value for both `org-tags-column' and
|
|
`org-agenda-tags-column' is now -80.
|
|
|
|
</li>
|
|
<li>
|
|
The variable
|
|
`org-insert-labeled-timestamps-before-properties-drawer'
|
|
is now obsolete.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Details</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
The LOGGING property allows to modify the settings for
|
|
progress logging for a single entry. For example:
|
|
|
|
<p>
|
|
<pre>
|
|
:PROPERTIES:
|
|
:LOGGING: nologging nologrepeat
|
|
:END:
|
|
</pre>
|
|
</p>
|
|
<p>
|
|
turns off all progress logging for the current entry and its
|
|
children.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
The properties SUMMARY, DESCRIPTION and LOCATION have
|
|
special meaning during iCalendar export, when they translate
|
|
to the corresponding VEVENT and VTODO fields. If not given,
|
|
Org-ode continues to use cleaned-up version of the headline
|
|
and body as the summary and the description, respectively.
|
|
|
|
</li>
|
|
<li>
|
|
New function to go to the entry with the currently running
|
|
clock. Bound to `C-c C-x C-j', in agenda also to "J". If
|
|
you use this often, you might even want to assign a global
|
|
key. Thanks to Bernt and Bastien.
|
|
|
|
</li>
|
|
<li>
|
|
Clock entries can now have their own drawer, the :CLOCK:
|
|
drawer. Check out the variable `org-clock-into-drawer' for
|
|
configuration of this feature. The default is to create a
|
|
drawer when the second clocking line gets added to an entry.
|
|
Note that "CLOCK" has been added to the default value of
|
|
`org-drawers', but if you have configured that variable, you
|
|
must go back and add "CLOCK" yourself to get this drawer
|
|
folded away. Thanks to Tom Weissman for pointing out that
|
|
too many clock entries are visually annoying.
|
|
|
|
</li>
|
|
<li>
|
|
`C-c C-x C-r' no longer tries to find the first clocktable
|
|
in a buffer and then updates it. Instead, it will update
|
|
the clocktable at point if there is one (same as C-c C-c
|
|
will do if the cursor is in the "#+BEGIN" line of the
|
|
table). If there is none at point, a new one will be
|
|
inserted. This change was necessary because the new :scope
|
|
parameter allows to have several clocktables in a buffer.
|
|
Thanks to Bastien for pointing this out.
|
|
To update all dynamic blocks in a file, use `C-u C-c C-x C-u'.
|
|
|
|
</li>
|
|
<li>
|
|
The function `org-remember' can now be called with a
|
|
template selection key as argument. This helps to make key
|
|
bindings that go directly to a specific template without
|
|
being prompted for a template, like this:
|
|
|
|
<p>
|
|
<pre>
|
|
(global-set-key [f5] (lambda () (interactive) (org-remember "j")))
|
|
</pre>
|
|
</p>
|
|
<p>
|
|
Thanks to Richard G Riley for bringing this up.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
`C-n' and `C-p' are back to their default binding
|
|
(next/previous line) in the agenda buffer. Enough people,
|
|
including recently Denis Bueno, have complained about this,
|
|
and I agree it is not good to break habits like that.
|
|
|
|
</li>
|
|
<li>
|
|
`C-x C-s' in an agenda buffer now saves all org-mode buffers
|
|
(also `s' does this).
|
|
|
|
</li>
|
|
<li>
|
|
Setting schedule or deadline dates from the agenda now
|
|
produces a note in the agenda, similarly to what happens
|
|
with S-left/right.
|
|
|
|
</li>
|
|
<li>
|
|
Using a prefix argument for `C-c C-d' or `C-c C-s' will
|
|
remove the deadline or scheduling date from an item. Thanks
|
|
to Wanrong Lin for this proposal.
|
|
|
|
</li>
|
|
<li>
|
|
New variable `org-agenda-compact-blocks'. When set, the
|
|
space between blocks in a block agenda is reduced as much as
|
|
possible, to show more items on a single screen.
|
|
|
|
</li>
|
|
<li>
|
|
The variable `org-agenda-tags-column' (renamed from
|
|
`org-agenda-align-tags-to-column') can now also be negative,
|
|
to mean alignment to the left. The new default is -80, just
|
|
like it is now for `org-tags-column'.
|
|
|
|
</li>
|
|
<li>
|
|
Bug fixes
|
|
|
|
</li>
|
|
</ul></div>
|
|
</div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 5.10</h2>
|
|
|
|
|
|
|
|
<div class="outline-3">
|
|
<h3>Overview</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
Category and the archive location can be properties.
|
|
</li>
|
|
<li>
|
|
The clocktable has a new <code>:scope</code> parameter.
|
|
</li>
|
|
<li>
|
|
CSV support when importing a table.
|
|
</li>
|
|
<li>
|
|
Better defaults when modifying a time stamp.
|
|
</li>
|
|
<li>
|
|
New way to specify the duration of an appointment.
|
|
</li>
|
|
<li>
|
|
More aggressive version of orgstruct-mode improved wrapping.
|
|
</li>
|
|
<li>
|
|
Modifications to priority cycling.
|
|
</li>
|
|
<li>
|
|
Modifications to computations in column view.
|
|
</li>
|
|
<li>
|
|
New command `org-occur-in-agenda-files'.
|
|
</li>
|
|
<li>
|
|
Bug fixes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Details</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
Both the category and the archive location in a (sub)tree of
|
|
the buffer can now be specified using a property, for
|
|
example:
|
|
|
|
<p>
|
|
<pre>
|
|
* Tree with special properties
|
|
:PROPERTIES:
|
|
:CATEGORY: Examples
|
|
:ARCHIVE: /some/special/file::
|
|
:END:
|
|
</pre>
|
|
</p>
|
|
<p>
|
|
This is a much cleaner way of dealing with multiple
|
|
categories and archives in a single file. The preferred use
|
|
of the <code>#+CATEGORY</code> and <code>#+ARCHIVE</code> lines is now to set a
|
|
<b>single</b> default for the file which is then locally
|
|
overruled by properties. This was a proposal from Bastien
|
|
if I remember correctly. Multiple <code>#+</code> lines still work
|
|
and I don't plan to remove this support soon, but I
|
|
encourage you to stop using them.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
The clocktable has a new <code>:scope</code> parameter that determines
|
|
the range in the file from which clock entries should be
|
|
taken. This can be anything from the local subtree to the
|
|
entire buffer to even the full list of agenda files. Legal
|
|
values are:
|
|
|
|
<table border="2" cellspacing="0" cellpadding="6" rules="groups" frame="hsides">
|
|
<col align="left"></col><col align="left"></col>
|
|
<thead>
|
|
<tr><th>value</th><th>scope</th></tr>
|
|
</thead>
|
|
<tbody>
|
|
<tr><td>nil</td><td>the current buffer or narrowed region</td></tr>
|
|
<tr><td>file</td><td>the full current buffer</td></tr>
|
|
<tr><td>subtree</td><td>the subtree where the clocktable is located</td></tr>
|
|
<tr><td>treeN</td><td>the surrounding level N tree, for example tree3</td></tr>
|
|
<tr><td>tree</td><td>the surrounding level 1 tree</td></tr>
|
|
<tr><td>agenda</td><td>all agenda files</td></tr>
|
|
</tbody>
|
|
</table>
|
|
|
|
|
|
<p>
|
|
Thanks to Jason F. McBrayer and Bernt Hansen for
|
|
inspiration. Thanks to cranreuch (what is you full name?)
|
|
for mentioning, at the right moment, that the clocktable is
|
|
not so bad - that remark made it seem worthwhile to add
|
|
features.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
The commands to import a table and to convert a region to a
|
|
table can now handle comma-separated values (CSV). The
|
|
algorithm does not yet treat quoting correctly, but for
|
|
basic input it works.
|
|
|
|
</li>
|
|
<li>
|
|
When modifying an existing time stamp, or when entering the
|
|
second stamp of a range, the date prompt will now
|
|
consistently default to the date/time in the existing stamp.
|
|
This was triggered by Nuutti Kotivuori's request.
|
|
|
|
</li>
|
|
<li>
|
|
At the date/time prompt, there is a new way to specify a
|
|
range of hours, by using "+DURATION" after the time. For
|
|
example:
|
|
|
|
<p>
|
|
<pre>
|
|
14:00+2 means 14:00-16:00
|
|
2pm+2:30 means 14:00-16:30
|
|
</pre>
|
|
</p>
|
|
<p>
|
|
Again, Nuutti Kotivuori's request.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
When you use the function `turn-on-orgstruct++' to turn on
|
|
orgstruct-mode, the special org-mode settings for
|
|
auto-filling, indentation and paragraphs are exported into
|
|
the buffer, so that typing list items with indentation works
|
|
better. This was Bastien's idea and request.
|
|
|
|
</li>
|
|
<li>
|
|
New variable `org-priority-start-cycle-with-default'. When
|
|
t (the default), priority cycling will initially set the
|
|
default priority and then increase or decrease. When nil,
|
|
the first priority set by cycling is already 1 different
|
|
from the default priority. This was mostly driven by
|
|
Bastien.
|
|
|
|
</li>
|
|
<li>
|
|
In column view: When an entry has a property for a summary
|
|
column defined, its value is normally overwritten by the sum
|
|
of all the children's values each time you enter column
|
|
view. Now there is an exception to this rule: If none of
|
|
the children has that particular property defined, the
|
|
parent's value stays. In this way you can still place TODO
|
|
items under such an entry without getting the property value
|
|
changed. Thanks to Russel Adams for pointing out that this
|
|
is a better way of doing things.
|
|
|
|
</li>
|
|
<li>
|
|
In column view, computed values are now bold face, and
|
|
trying to edit them is an error. I think this works, but
|
|
testing is appreciated.
|
|
|
|
</li>
|
|
<li>
|
|
New command `org-occur-in-agenda-files', this is basically
|
|
the quick command John Wiegley proposed the other day, but
|
|
it also works when the agenda files are not yet in buffers.
|
|
The key is `C-c C-x /', any better proposals?
|
|
|
|
</li>
|
|
<li>
|
|
Links containing a space will now be handled correctly when
|
|
calling the browser. Note that you need to enclose such
|
|
links in square or angular brackets.
|
|
|
|
</li>
|
|
<li>
|
|
Bug fixes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
</div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 5.09</h2>
|
|
|
|
|
|
|
|
<div class="outline-3">
|
|
<h3>Overview</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
Taking a note upon TODO state changes can be restricted to
|
|
selected states.
|
|
|
|
</li>
|
|
<li>
|
|
The format in which dates are shown in the daily/weekly
|
|
agenda can be configured.
|
|
|
|
</li>
|
|
<li>
|
|
The default for `org-remember-store-without-prompt' is now t.
|
|
|
|
</li>
|
|
<li>
|
|
`org-goto' has been made into a general lookup command.
|
|
|
|
</li>
|
|
<li>
|
|
Priority cycling goes back to the nil state.
|
|
|
|
</li>
|
|
<li>
|
|
You can store a remember note to the <b>last used</b> location.
|
|
|
|
</li>
|
|
<li>
|
|
On Emacs 23, the headline faces for org-mode are now
|
|
inherited from the outline faces.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Incompatible Changes</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
The default for `org-remember-store-without-prompt' is now
|
|
t, in order to better match the original intent of
|
|
remember.el (storing a note with minimum interruption of
|
|
work flow). I expect that many people will be hit by this
|
|
incompatible change - nevertheless I believe it is the right
|
|
thing to do.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Details</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
You can now select specific states for recording a note when
|
|
switching to that state. With the setting
|
|
|
|
<p>
|
|
<pre>
|
|
#+SEQ_TODO: TODO(t) ORDERED(o@) INVOICE(i@) PAYED(p) | RECEIVED(r)
|
|
#+STARTUP: lognotestate
|
|
</pre>
|
|
</p>
|
|
<p>
|
|
only the states ORDERED and INVOICE will record a timestamp
|
|
and a note.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
You can now set the format of the string for each day in the
|
|
agenda and timeline buffers. You can use a format string
|
|
interpreted by `format-time-string', or you can write your
|
|
own function. Configure the new variable
|
|
`org-agenda-format-date'. Thanks to Levin for triggering
|
|
this development with a patch.
|
|
|
|
</li>
|
|
<li>
|
|
The default for `org-remember-store-without-prompt' is now
|
|
t, in order to better match the original intent of
|
|
remember.el (storing a note with minimum interruption of
|
|
work flow). Since we can assign files and headlines to
|
|
templates, I guess this takes care of selecting a filing
|
|
location in most cases. For interactive filing, you now
|
|
need a prefix command when exiting `remember'.
|
|
|
|
</li>
|
|
<li>
|
|
`org-goto' (bound to `C-c C-j') now uses an indirect buffer
|
|
and has additional commands enabled: Org-occur with `C-c /'
|
|
or even faster with `/', and the commands needed to select
|
|
and copy a region. This make `org-goto' a more general
|
|
lookup command instead of only a jumping command. Remember
|
|
that you can exit with `Q' to go back to the original
|
|
location. Thanks to William Henney for this idea.
|
|
|
|
</li>
|
|
<li>
|
|
Setting the priority with S-up/down now cycles back to a
|
|
state where no priority is specified. This was requested by
|
|
Rick Moynihan.
|
|
|
|
</li>
|
|
<li>
|
|
You can store a remember note to the <b>last used</b> location.
|
|
So if you select a location interactively once, you can
|
|
re-use it without having to find it again. For this, exit
|
|
the remember buffer with `C-u C-u C-c C-c'. The leading
|
|
comment in the remember buffer will tell exactly where the
|
|
note goes if you exit with a particular command.
|
|
Thanks to Maxim Loginov for this idea.
|
|
|
|
</li>
|
|
<li>
|
|
On Emacs 23, the headline faces for org-mode are now
|
|
inherited from the outline faces. This is just a
|
|
convenience, so that you only have to configure one set of
|
|
faces, and that will then be outline-1 .. outline-8. You
|
|
will actually not see any difference in org-mode, because
|
|
Stefan Monnier has made the outline faces in Emacs 23 to
|
|
match the current org-mode faces.
|
|
|
|
<p>
|
|
This change does not effect XEmacs, nor Emacs 21 and 22.
|
|
</p>
|
|
</li>
|
|
</ul></div>
|
|
</div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 5.08</h2>
|
|
|
|
|
|
|
|
<div class="outline-3">
|
|
<h3>Incompatible changes</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
The default for `org-deadline-warning-days' is now 14.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Details</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
There is now a separate interface for fast and directly
|
|
setting a TODO keyword. This interface kicks in when you
|
|
have configured keys for TODO keywords like
|
|
|
|
<p>
|
|
<pre>
|
|
#+SEQ_TODO: TODO(t) WAITING(w) | DONE(d) CANCELED(c)
|
|
</pre>
|
|
</p>
|
|
<p>
|
|
C-c C-t still does the cycling thing, you need to use a
|
|
prefix argument to get to the fast interface. Or configure
|
|
the variable `org-use-fast-todo-selection' to t, then this
|
|
will be the default and the prefix argument will make the
|
|
command fall back to cycling.
|
|
</p>
|
|
<p>
|
|
The tag selection no longer does include TODO keywords -
|
|
Leo's arguments have convinced me that this is not a good
|
|
idea. If you'd like to see the TODO keywords in the tags
|
|
interface anyway, set the variable
|
|
`org-fast-tag-selection-include-todo'. Thanks to Leo and
|
|
others for input on this issue.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
New variable `org-edit-timestamp-down-means-later'. When
|
|
set, `S-down' on a timestamp will change the timestamp to
|
|
later. Thanks to Raman for this idea.
|
|
|
|
</li>
|
|
<li>
|
|
Property names can now contain non-ascii word characters.
|
|
This follows a request from Daniel Clemente.
|
|
|
|
</li>
|
|
<li>
|
|
For export, the date that should be given in the exported
|
|
file can now be set to a specific value with a line like
|
|
|
|
<p>
|
|
<pre>
|
|
#+DATE: 15 November 2003
|
|
</pre>
|
|
</p>
|
|
<p>
|
|
If you want to use the date/time when the file was created,
|
|
use a format string that will be interpreted by
|
|
`format-time-string', for example:
|
|
</p>
|
|
<p>
|
|
<pre>
|
|
#+DATE: %Y/%m/%d %X
|
|
</pre>
|
|
</p>
|
|
</li>
|
|
<li>
|
|
The default of `org-deadline-warning-days' has changed to 14
|
|
days. 30 was really too much, I suspect most people (me
|
|
included) have changed this.
|
|
|
|
</li>
|
|
<li>
|
|
When a deadline has an individual lead time, this lead time
|
|
obviously overrules `org-deadline-warning-days'. However,
|
|
if you bind `org-deadline-warning-days' to a number <=0, for
|
|
example during a custom agenda command, then the absolute
|
|
value of this number will be enforced also when a different
|
|
lead time has been specified. This is useful to get a list
|
|
of all deadlines coming up in the next N days.
|
|
|
|
</li>
|
|
</ul></div>
|
|
</div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 5.07</h2>
|
|
|
|
|
|
|
|
<div class="outline-3">
|
|
<h3>Overview</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
Different faces for different TODO keywords.
|
|
|
|
</li>
|
|
<li>
|
|
Setting TODO states through the TAG setting interface.
|
|
|
|
</li>
|
|
<li>
|
|
Context information is stored when moving a tree to the archive.
|
|
|
|
</li>
|
|
<li>
|
|
Sorting can be done by priority.
|
|
|
|
</li>
|
|
<li>
|
|
`Org-ellipsis' can now also be a face.
|
|
|
|
</li>
|
|
<li>
|
|
Scheduling info is no longer removed entry is marked CLOSED.
|
|
|
|
</li>
|
|
<li>
|
|
Unavailable files in `org-agenda-files' can be skipped.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Incompatible changes</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
The time of archiving is now stored as a property.
|
|
ARCHIVED is no longer a special time keyword.
|
|
|
|
</li>
|
|
<li>
|
|
Scheduling info is no longer removed entry is marked CLOSED.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Details</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
You can now define different faces for different TODO
|
|
keywords. This request has come up frequently, so here it
|
|
is: Use the variable `org-todo-keyword-faces'.
|
|
|
|
<p>
|
|
A Here is a configuration example:
|
|
</p>
|
|
<p>
|
|
<pre>
|
|
(setq org-todo-keyword-faces
|
|
'(("TODO" . org-warning)
|
|
("DEFERRED" . shadow)
|
|
("CANCELED" . (:foreground "blue" :weight bold
|
|
:underline t))))
|
|
</pre>
|
|
</p>
|
|
<p>
|
|
Org-mode continue still use `org-todo' and `org-done' for
|
|
keywords that have no specific face assigned.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
Some People use TODO states more like tags. For them the
|
|
TODO keywords mark special states and they like to quickly
|
|
switch between states in arbitrary sequence. The standard
|
|
TODO interface is not perfect for this, because it assumes
|
|
that the states are reached in sequence. However, the fast
|
|
tag setting interface is in fact perfect for this. You can
|
|
now "misuse" the TAG selection interface to also set TODO
|
|
states. All you need to do is to assign keys to the TODO
|
|
states, just like you also do for tags.
|
|
|
|
<p>
|
|
<pre>
|
|
#+SEQ_TODO: TODO(t) WAITING(w) | CANCELED(c) DONE(d)
|
|
#+TAGS: @HOME(h) @OFFICE(o) @SHOP(s)
|
|
</pre>
|
|
</p>
|
|
<p>
|
|
Next time you try to set tags with C-c C-c, the todo states
|
|
will be offered as well, and the corresponding key will
|
|
switch the entry to that state.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
New variable `org-archive-save-context-info' governs if
|
|
information that would be lost by moving a subtree to the
|
|
archive file, should be stored as special properties. For
|
|
example,
|
|
|
|
<p>
|
|
<pre>
|
|
(setq org-archive-save-context-info '(itags category))
|
|
</pre>
|
|
</p>
|
|
<p>
|
|
will store the inherited tags and the category in properties
|
|
ARCHIVE_ITAGS and ARCHIVE_CATEGORY, respectively. The
|
|
default setting for this variable is to save everything that
|
|
could be lost. This was a proposal by John Wiegley.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
Sorting (`C-c ^') can use the use the priority to sort. Use
|
|
the "p" and "P" keys at the prompt. John Wiegley, again.
|
|
|
|
</li>
|
|
<li>
|
|
`Org-ellipsis' can now also be a face to make the folding
|
|
ellipsis more visible. This is based on a post by Tassilo
|
|
Horn. Since `org-ellipsis' only works in Org-mode, you
|
|
might want to use Tassilo Horn's hack directly in order to
|
|
affect the folding ellipsis globally.
|
|
|
|
</li>
|
|
<li>
|
|
Scheduling info is no longer removed when an entry is marked
|
|
CLOSED. This was a request by Brian van den Broek. Let me
|
|
know if this breaks anything for you - then it will become
|
|
an option.
|
|
|
|
</li>
|
|
<li>
|
|
New option `org-agenda-skip-unavailable-files'. Currently,
|
|
if a file does not exist, it will be removed from
|
|
`org-agenda-files' after a query. When this option is set,
|
|
the file will simply be skipped.
|
|
|
|
</li>
|
|
<li>
|
|
Bug fixes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
</div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 5.06</h2>
|
|
|
|
|
|
|
|
<div class="outline-3">
|
|
<h3>Overview</h3>
|
|
|
|
|
|
</div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Details</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
When exporting only a region and this region is a single
|
|
(sub)tree (for example selected with `C-c @'), the title for
|
|
the exported document is taken to be the heading of the
|
|
subtree. The sublevels become top-level entries in the
|
|
export. Furthermore, if the head entry of the tree has or
|
|
inherits an EXPORT_FILE_NAME property, that file name (with
|
|
appropriately substituted extension) will be used for the
|
|
exported tree. Thanks to Patrick Drechsler and Jost Burkart
|
|
for these ideas.
|
|
|
|
</li>
|
|
<li>
|
|
org-special-ctrl-a/e has a third allowed value, `reversed'.
|
|
When it is set to this value, the first C-a or C-e command
|
|
behaves normally, i.e. it goes to the true beginning or end
|
|
of the line. Only when you press C-a or C-e immediately
|
|
again, the the "special" position will be found. Additional
|
|
presses of the same key jump between the two positions. I
|
|
like this a lot better than the `t' setting, because now the
|
|
keys behave more predictable and still give easy access to
|
|
the special locations.
|
|
|
|
</li>
|
|
<li>
|
|
New command to set or remove a tag from all headlines in a
|
|
region.
|
|
|
|
</li>
|
|
<li>
|
|
When Org-mode visits a file, it will initially hide all
|
|
drawers.
|
|
|
|
</li>
|
|
<li>
|
|
The default of the variable `org-cycle-global-at-bob' is now
|
|
nil, meaning that TAB no longer does global visibility
|
|
cycling at the beginning of the buffer.
|
|
|
|
</li>
|
|
<li>
|
|
Bug fixes, in particular the problems with scheduling and
|
|
deadlines introduced in 5.05. Please check carefully if
|
|
this works correctly again, and complain if not.
|
|
|
|
</li>
|
|
</ul></div>
|
|
</div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 5.05</h2>
|
|
|
|
|
|
|
|
<div class="outline-3">
|
|
<h3>Overview</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
LaTeX export, finally, thanks to Bastien.
|
|
|
|
</li>
|
|
<li>
|
|
Extension mechanism for the hyperlink system.
|
|
|
|
</li>
|
|
<li>
|
|
Global access to commands inserting and following links.
|
|
|
|
</li>
|
|
<li>
|
|
Individual lead-times for deadlines.
|
|
|
|
</li>
|
|
<li>
|
|
Option to show only the next instance of repeating timestamp.
|
|
|
|
</li>
|
|
<li>
|
|
Store remember notes with only 2 keys: C-c C-c
|
|
|
|
</li>
|
|
<li>
|
|
Appointment reminders from Org-mode.
|
|
|
|
</li>
|
|
<li>
|
|
Global values for selected properties.
|
|
|
|
</li>
|
|
<li>
|
|
Bug fixes.
|
|
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Details</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
Bastien's `org-export-latex.el' is now part of the org-mode
|
|
distribution. You can export an Org-mode document to a
|
|
LaTeX file with `C-c C-e l'. For more options, see the
|
|
manual, and the commentary in the Lisp file. Kudos to
|
|
Bastien for contributing this frequently requested feature.
|
|
I am sure this has been tough because of the many different
|
|
ways I have been allowing LaTeX snippets and environments to
|
|
be incorporated in lazy free-format ways.
|
|
|
|
</li>
|
|
<li>
|
|
Org-mode has now an extension mechanism for the hyperlink
|
|
system. This should clear the road for all those mairix and
|
|
other ideas that have been floating around. Now it is on
|
|
<b>you</b> to write and share new link types for Org-mode. The
|
|
interface for adding a new link type is described in the
|
|
appendix of the manual, section A2. The unsolved problem is
|
|
currently how to handle the new link types for
|
|
export/publishing.
|
|
|
|
</li>
|
|
<li>
|
|
New <b>global</b> commands `org-open-at-point-global' and
|
|
`org-insert-link-global'. You can bind these commands to
|
|
global keys and use them to insert and follow Org-mode-like
|
|
links anywhere in Emacs. Thanks to Adam Spiers for this
|
|
excellent idea.
|
|
|
|
</li>
|
|
<li>
|
|
Each deadline timestamp may now specify its own interval of
|
|
lead-time display, given in days, weeks, months or years.
|
|
The syntax is like this
|
|
|
|
<p>
|
|
<pre>
|
|
DEADLINE: <2007-08-13 Mon -5d>
|
|
</pre>
|
|
</p>
|
|
<p>
|
|
When combined with a repeater, the repeater has to come
|
|
first:
|
|
</p>
|
|
<p>
|
|
<pre>
|
|
DEADLINE: <2007-08-13 Mon +2w -5d>
|
|
</pre>
|
|
</p>
|
|
<p>
|
|
You may now also customize the faces that are used in the
|
|
agenda to indicate the distance of an approaching deadline.
|
|
See the new option `org-agenda-deadline-faces'.
|
|
</p>
|
|
<p>
|
|
Thanks to Pavel Chalmoviansky and John Wiegley proposals in
|
|
this direction.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
New option `org-agenda-repeating-timestamp-show-all'. When
|
|
set to nil, repeating time stamps will only show up once in
|
|
the agenda, either today or in the near future. Other
|
|
matches will be ignored. Thanks to John Wiegley for this
|
|
proposal.
|
|
|
|
</li>
|
|
<li>
|
|
New variable `org-remember-store-without-prompt'. When set,
|
|
exiting the remember buffer with C-c C-c will store the note
|
|
without further prompts to the default location, and `C-u
|
|
C-c C-c' will get the prompts for file and location. So
|
|
this variable reverses the prefix-argument functionality for
|
|
storing remember notes. This follows a request from John
|
|
Wiegley.
|
|
|
|
</li>
|
|
<li>
|
|
A new function `org-agenda-to-appt' activates all
|
|
appointments for the current day so that Emacs will display
|
|
reminders. This uses appt.el. Thanks to Bastien for this
|
|
function.
|
|
|
|
</li>
|
|
<li>
|
|
You can now set default values for properties that can be
|
|
inherited by all entries in a buffer, or by all entries
|
|
globally. Global properties are set in the variable
|
|
`org-global-properties', like this:
|
|
|
|
<p>
|
|
(setq org-global-properties '(("NAME" "This is the value")))
|
|
</p>
|
|
<p>
|
|
Buffer-local values are set like this:
|
|
</p>
|
|
<p>
|
|
#+PROPERTY: NAME This is the value
|
|
</p>
|
|
<p>
|
|
When using org-entry-get to get the value of a property with
|
|
the `inherit' flag and the hierarchy above the entry does
|
|
not contain this property, the buffer-local and global lists
|
|
are checked as well. This is mostly useful (I think) to set
|
|
the list of allowed values for a property. Thanks to Bernt
|
|
Hansen and Bastien for these ideas.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
Bug fixes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
</div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 5.04</h2>
|
|
|
|
|
|
|
|
<div class="outline-3">
|
|
<h3>Details</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
New variables `org-export-author-info' and
|
|
`org-export-time-stamp-file' to turn off inclusion of author
|
|
and time information into exported files. Thank to Patrick
|
|
Drechsler for pointing out that this would be useful.
|
|
|
|
</li>
|
|
<li>
|
|
New variable to avoid moving DEADLINE and SCHEDULED info
|
|
into the property drawer. The default is now to not move
|
|
this stuff into the drawer.
|
|
`org-insert-labeled-timestamps-before-properties-drawer'
|
|
|
|
</li>
|
|
<li>
|
|
`org-archive-mark-done' can be a string now, to select a
|
|
specific keyword that should be used for archived entries.
|
|
|
|
</li>
|
|
<li>
|
|
New command "j" in agenda to jump to an arbitrary date.
|
|
Thanks to Bernt Hansen for the patch.
|
|
|
|
</li>
|
|
<li>
|
|
Lots of minor fixes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
</div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 5.03</h2>
|
|
|
|
|
|
|
|
<div class="outline-3">
|
|
<h3>Incompatible Changes</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
The variable `org-special-ctrl-a' has been renamed to
|
|
`org-special-ctrl-a/e'. The old one is still an alias (but
|
|
not on Emacs 21 where variable aliases cannot be defined).
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Details</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
When the variable `org-special-ctrl-a/e' is set, C-e in a
|
|
headline first goes to the end of the headline ignoring the
|
|
tags. A second C-e then goes to after the tags.
|
|
|
|
</li>
|
|
<li>
|
|
Typing and removing single characters in a headline now
|
|
keeps the tags in the headline aligned. This could have a
|
|
little impact on performance while deleting stuff - let me
|
|
know if we need to make this customizable.
|
|
|
|
</li>
|
|
<li>
|
|
New option `org-n-level-faces' can be used to set the number
|
|
of different faces that are used for headlines. Default is
|
|
all 8 faces Org-mode defines for this purpose, level 9 uses
|
|
again the level-1 face. However, you can use fewer, and then
|
|
the level-1 face will be reused already for level N+1, etc.
|
|
|
|
</li>
|
|
<li>
|
|
Column View and hidestars now work together.
|
|
|
|
</li>
|
|
<li>
|
|
Bug fixes.
|
|
|
|
|
|
</li>
|
|
</ul></div>
|
|
</div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 5.02</h2>
|
|
|
|
|
|
|
|
<div class="outline-3">
|
|
<h3>Overview</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
The interfaces for properties and column view are finished
|
|
now and work well.
|
|
|
|
</li>
|
|
<li>
|
|
Properties can be summaries, i.e. the parent nodes can
|
|
compute their value from the children's values.
|
|
|
|
</li>
|
|
<li>
|
|
Headlines finally require a space ofter the star(s). The
|
|
conflict with bold text at the beginning of the line is no
|
|
longer there.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Incompatible Changes</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
Bad news. It looks like it is going to be really hard to
|
|
make column view work on XEmacs and on Emacs 21. Emacs 22
|
|
is currently the only Emacs where this works. If you are
|
|
using Emacs 21 or XEmacs, you can still use properties, but
|
|
not column view.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Details</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
Improvements for properties:
|
|
|
|
<ul>
|
|
<li>
|
|
There are interactive commands to insert and delete
|
|
properties. Read the manual chapter 7 for details.
|
|
|
|
</li>
|
|
<li>
|
|
You can define <i>allowed values</i> for a property. When
|
|
these are defined, you can change the value of a property
|
|
with S-left and S-right. And you may use completion when
|
|
inserting the property. This goes a long way to prevent
|
|
typos when entering properties.
|
|
|
|
</li>
|
|
</ul></li>
|
|
<li>
|
|
Improvements for column view.
|
|
|
|
<ul>
|
|
<li>
|
|
In column view, you may use the keys S-left/right (and
|
|
also the keys `n' and `p') to switch from one allowed
|
|
value to the next.
|
|
|
|
</li>
|
|
<li>
|
|
You can define summaries for columns. For example,
|
|
parents can contain the sum of all children values of a
|
|
property, or the parent node can have a check box property
|
|
that is automatically checked when all children's boxes are
|
|
checked.
|
|
|
|
</li>
|
|
<li>
|
|
There are interactive commands to add and remove columns,
|
|
and to change the attributes of a column like the summary
|
|
type.
|
|
|
|
</li>
|
|
</ul>
|
|
<p>These additions lead to the exciting fact that the example
|
|
from <a href="http://www.omnigroup.com/images/applications/omnioutliner/features/multicolumn.jpg">omni outliner</a> posted by Scott Jaderholm can now be
|
|
accurately <a href="omni-org.jpg">reproduced by Org-mode</a>.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
The space after the stars is now required in a headline, in
|
|
order to remove the conflict with bold words at the
|
|
beginning of a line. So
|
|
|
|
<p>
|
|
<pre>
|
|
* This is a level 1 headline
|
|
*this is bold text*
|
|
</pre>
|
|
</p>
|
|
</li>
|
|
<li>
|
|
S-up and S-down to navigate plain item lists are now also
|
|
available in orgstruct-mode.
|
|
|
|
</li>
|
|
</ul></div>
|
|
</div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 5.01</h2>
|
|
|
|
|
|
|
|
<div class="outline-3">
|
|
<h3>Overview</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
A new minor mode, orgstruct-mode, exports the Org-mode
|
|
structure editing commands into any other mode.
|
|
|
|
</li>
|
|
<li>
|
|
DRAWERS are a new level off folding for special sections
|
|
that should stay closed during visibility cycling and only
|
|
open if explicitly asked.
|
|
|
|
</li>
|
|
<li>
|
|
Entries can now have PROPERTIES.
|
|
|
|
</li>
|
|
<li>
|
|
A COLUMN VIEW implementation allows to easily view and edit
|
|
the properties of a hierarchy of entries (Emacs only, for
|
|
now).
|
|
|
|
</li>
|
|
<li>
|
|
Formula evaluation in the spreadsheet is more consistent
|
|
now. Properties and per-file constants can be used during
|
|
evaluation.
|
|
|
|
</li>
|
|
<li>
|
|
Bug fixes and minor changes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Incompatible changes</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
When using LEVEL=N in a tags search, things have changed if
|
|
you are also using `org-odd-levels-only'. If you are using
|
|
only odd levels (i.e. 1 or 3 or 5… stars), LEVEL=2 will
|
|
now refer to 3 stars, LEVEL=3 to 5 stars etc. Many thanks
|
|
to Leo (or blame on him if you must) who has convinced me
|
|
that this is the better convention.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Details</h3>
|
|
|
|
|
|
|
|
<div class="outline-4">
|
|
<h4>Orgstruct minor mode</h4>
|
|
|
|
|
|
<p>
|
|
There is a new minor mode, orgstruct-mode. This modes works
|
|
in a similar way as Orgtbl-mode. It can be used to export
|
|
the Org-mode structure-editing commands into arbitrary major
|
|
modes in Emacs. For example, you can use it in Mail-mode to
|
|
easily create lists.
|
|
</p>
|
|
<p>
|
|
The functionality in Orgstruct mode is only active, if the
|
|
cursor is in a line that looks either like a headline, or
|
|
like the first line of a plain list item. Then the commands
|
|
`TAB', `M-cursor', `M-S-cursor', `M-RET', `M-S-RET', `C-c ^',
|
|
`C-c C-c', and `C-c -' will do structure-related editing just
|
|
like in Org-mode. If the cursor is not in such a line, all
|
|
these keys will do whatever the major mode or other active
|
|
minor modes have assigned to them.
|
|
</p>
|
|
<p>
|
|
Orgstruct-mode is the result of a proposal by Raman, quite
|
|
some time ago. It has taken a long time, but here is finally
|
|
the promised implementation.
|
|
</p>
|
|
</div>
|
|
|
|
<div class="outline-4">
|
|
<h4>Drawers</h4>
|
|
|
|
|
|
<p>
|
|
The new concept of <i>drawers</i> allows to create sections
|
|
that remain folded during visibility cycling. Drawers need
|
|
to be configured using the variable `org-drawers'. A drawer
|
|
starts with a line containing only the name of the drawer
|
|
bracketed by colons. It ends with :END:. For example,
|
|
after setting
|
|
</p>
|
|
<p>
|
|
<pre>
|
|
(setq org-drawers '("PROPERTIES" "HIDDEN"))
|
|
</pre>
|
|
</p>
|
|
<p>
|
|
you can then create drawers like this:
|
|
</p>
|
|
<p>
|
|
<pre>
|
|
:HIDDEN:
|
|
here is some stuff that remains hidden
|
|
unless TAB is pressed directly in that line
|
|
:END:
|
|
</pre>
|
|
</p>
|
|
<p>
|
|
The PROPERTIES drawer has special meaning for ORG-mode, it
|
|
contains properties of an entry (see below).
|
|
</p>
|
|
</div>
|
|
|
|
<div class="outline-4">
|
|
<h4>Properties and Column View</h4>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
Entries in Org-mode can now have arbitrary <i>properties</i>
|
|
associated with them. Org-mode handles some default
|
|
properties like the TODO state, the priority, the local
|
|
tags, and planning information like DEADLINE and SCHEDULED.
|
|
In addition, you can assign arbitrary properties by creating
|
|
a property drawer and inserting a line like
|
|
|
|
<p>
|
|
<pre>
|
|
:PROPNAME: This is the value of the property
|
|
</pre>
|
|
</p>
|
|
<p>
|
|
Org-mode has an API for properties, if you want to write a
|
|
program using properties, use the functions
|
|
`org-entry-properties', `org-entry-get', `org-entry-put',
|
|
and `org-entry-delete'.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
Planning information like DEADLINE can be hidden in the
|
|
properties drawer.
|
|
|
|
<p>
|
|
If the PROPERTIES drawer starts in the first line after a
|
|
headline, also the DEADLINE, SCHEDULED and CLOCK information
|
|
will be inserted inside the drawer. If no PROPERTIES drawer
|
|
is present, or if it does not start in the line right after
|
|
the headline, this information remains in the lines directly
|
|
after the headline, outside the drawer.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
TAGS searches can now also query properties. For example,
|
|
the search
|
|
|
|
<p>
|
|
<pre>
|
|
LEVEL=3+BOSS+ASSIGNED="Hans"/WAITING
|
|
</pre>
|
|
</p>
|
|
<p>
|
|
will find entries that
|
|
</p><ul>
|
|
<li>
|
|
are level 3
|
|
</li>
|
|
<li>
|
|
have the tag BOSS
|
|
</li>
|
|
<li>
|
|
have an ASSIGNED property with the value "Hans"
|
|
</li>
|
|
<li>
|
|
are TODO status WAITING.
|
|
|
|
<p>
|
|
So here is an entry that will match:
|
|
</p>
|
|
<p>
|
|
<pre>
|
|
*** WAITING Clean up the factory :BOSS:
|
|
:PROPERTIES:
|
|
:ASSIGNED: Hans
|
|
:END:
|
|
</pre>
|
|
</p>
|
|
<p>
|
|
You may also use a regular expression to match against a
|
|
property value. For example, to find stuff assigned to Hans
|
|
or Sarah, use
|
|
</p>
|
|
<p>
|
|
<pre>
|
|
ASSIGNED={^\(Hans\|Sarah\)$}
|
|
</pre>
|
|
</p>
|
|
</li>
|
|
</ul></li>
|
|
<li>
|
|
Column View is a special way to look at property values in
|
|
tabular form. Column View can be used in any org-mode
|
|
file, and also in any agenda buffer. It works by placing
|
|
an overlay over each headline (or agenda line) that shows a
|
|
table of selected properties. You can look at and edit
|
|
properties from this view. Which properties are shown in
|
|
the table must be set up using the COLUMNS property. You
|
|
can set up different property columns on different levels
|
|
of an outline tree. For example:
|
|
|
|
<p>
|
|
<pre>
|
|
* People
|
|
:PROPERTIES:
|
|
:COLUMNS: %25ITEM %Name
|
|
:END:
|
|
** Family
|
|
:PROPERTIES:
|
|
:COLUMNS: %25ITEM %Name %3Age
|
|
:END:
|
|
*** Sam
|
|
Info about Sam, including a property list with Name and Age.
|
|
*** Sarah
|
|
Info about Sarah, including a property list with Name and Age.
|
|
** Office
|
|
:PROPERTIES:
|
|
:COLUMNS: %25ITEM %Name %Function %Salary
|
|
:END:
|
|
*** Boss
|
|
Info about the Boss, including a property list with Name,
|
|
Function and Salary (if only we knew....).
|
|
</pre>
|
|
</p>
|
|
<p>
|
|
Now we have defined three different sets of columns. If
|
|
you switch to column view in the <i>Family</i> section, you
|
|
will get a different table than if you do it in the
|
|
<i>Office</i> section. However, if you switch to column
|
|
view with the cursor on the <i>People</i> section, the
|
|
table will cover all entries, but contain only the
|
|
<i>Name</i>.
|
|
</p>
|
|
<p>
|
|
Column view does, for the time being, only work on Emacs.
|
|
The XEmacs implementation needs a bit of work.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
Properties can be used in table formulas. To access the
|
|
value of the property :XYZ:, use $PROP_XYZ. The property
|
|
needs to be defined in the hierarchy above the table, not
|
|
necessarily in the same entry as the table. This was a
|
|
request by Eddward. File-wide constants can be defined with
|
|
#+CONSTANTS, see below.
|
|
|
|
</li>
|
|
<li>
|
|
Things that still need to be sorted out about drawers,
|
|
properties and column view - comments and suggestions
|
|
welcome!
|
|
|
|
<ul>
|
|
<li>
|
|
How to deal with drawers and properties in HTML and ASCII
|
|
export?
|
|
</li>
|
|
<li>
|
|
What key could be used to insert an empty property drawer
|
|
into an entry?
|
|
</li>
|
|
<li>
|
|
Right now column view is invoked through the command C-c
|
|
C-x C-c. It is too easy to type C-x C-c by mistake, and
|
|
that causes Emacs to quit. Suggestions for a different
|
|
key?
|
|
</li>
|
|
<li>
|
|
Fontification of drawers and properties is not good yet.
|
|
Any suggestions for better defaults?
|
|
</li>
|
|
<li>
|
|
Mouse support for editing properties in column view would
|
|
be nice - maybe Piotr is interested to add this to
|
|
org-mouse.el?
|
|
|
|
</li>
|
|
</ul></li>
|
|
</ul></div>
|
|
|
|
<div class="outline-4">
|
|
<h4>Spreadsheet</h4>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
In the spreadsheet, the evaluation of formulas has changed.
|
|
Previously, first the column formulas would be evaluated
|
|
everywhere, and then the field formulas would kick in, and
|
|
in some cases overwrite the results of column formulas in
|
|
the appropriate fields. This had the side effect that some
|
|
formulas might always use the wrong, intermediate content of
|
|
a field that is computed both by a column and a field
|
|
formula.
|
|
|
|
<p>
|
|
From now on, column formulas will no longer temporarily
|
|
overwrite field formulas. This gives much more consistent
|
|
results. For example you can now finally have a column of
|
|
increasing numbers by setting the first field to a fixed
|
|
number, and let the rest follow from a column formula.
|
|
</p>
|
|
<p>
|
|
Here is an example
|
|
</p>
|
|
<p>
|
|
<pre>
|
|
| 1 |
|
|
| 2 |
|
|
| 3 |
|
|
#+TBLFM: $1=@-1+1::@1$1=1
|
|
</pre>
|
|
</p>
|
|
</li>
|
|
<li>
|
|
Constants for formulas in spreadsheets are globally defined
|
|
with the variable `org-table-formula-constants'. File-local
|
|
constants can now be set with a line like:
|
|
|
|
<p>
|
|
<pre>
|
|
#+CONSTANTS: c=299792458. pi=3.14 eps=2.4e-6
|
|
</pre>
|
|
</p>
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-4">
|
|
<h4>Minor changes</h4>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
When entries are archived, a timestamp for the moment of
|
|
archiving is added to the line with planning information.
|
|
It looks like this:
|
|
|
|
<p>
|
|
<pre>
|
|
ARCHIVED: [2007-07-02 Mon 11:34]
|
|
</pre>
|
|
</p>
|
|
<p>
|
|
Thanks to J. David Boyd for constructive comments.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
Bug fixes
|
|
|
|
<p>
|
|
Many bugs are fixed, as usually all the ones where I replied
|
|
"fixed" on emacs-orgmode. If you reported one of these
|
|
bugs, please check if it really has disappeared in the new
|
|
version, and complain if not. Thanks!
|
|
</p>
|
|
|
|
</li>
|
|
</ul></div>
|
|
</div>
|
|
</div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.79</h2>
|
|
|
|
|
|
|
|
<div class="outline-3">
|
|
<h3>Details</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
We are back to a single file org.el that works both on Emacs
|
|
and on XEmacs. Merging comes at a speed penalty for you as
|
|
an XEmacs user, but <b>only if you do not compile</b> org.el.
|
|
Compilation completely removes the penalty.
|
|
|
|
</li>
|
|
<li>
|
|
New L flag for literal interpolation in Lisp formulas.
|
|
See manual section 3.5.3.
|
|
|
|
</li>
|
|
<li>
|
|
New options for turning off footnotes.
|
|
This was a request from Ignotus.
|
|
See the option `org-export-with-footnotes'.
|
|
|
|
</li>
|
|
<li>
|
|
Default length for Agenda entries, but this is off by
|
|
default. This was a request from Micheal.
|
|
See the option `org-agenda-default-appointment-duration'.
|
|
|
|
</li>
|
|
<li>
|
|
Bug fixes:
|
|
|
|
<ul>
|
|
<li>
|
|
org-agenda-date-later (Juraj Kubelka)
|
|
</li>
|
|
<li>
|
|
letters off margin in orgcard.ps (Charles Cave)
|
|
</li>
|
|
<li>
|
|
TODO export problems on XEmacs (ignotus@freemail.hu)
|
|
</li>
|
|
<li>
|
|
args-out-of-range with table formulas (Cecil Westerhof)
|
|
</li>
|
|
<li>
|
|
problem with org-file without a heading (Tim O'Callaghan)
|
|
|
|
</li>
|
|
</ul></li>
|
|
</ul></div>
|
|
</div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.78</h2>
|
|
|
|
|
|
|
|
<div class="outline-3">
|
|
<h3>Overview</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
Time stamps with a time range <b>included</b>, like
|
|
<pre>
|
|
<2007-06-18 Mon 17:33-18:23>
|
|
</pre>
|
|
|
|
</li>
|
|
<li>
|
|
Clock times without clocking in/out: CLOCK: => 2:00
|
|
|
|
</li>
|
|
<li>
|
|
Language-specific characters allowed in TAGS (Emacs only).
|
|
|
|
</li>
|
|
<li>
|
|
Promotion and demotion of items gets the indentation right.
|
|
|
|
</li>
|
|
<li>
|
|
Indenting lines with TAB is more intelligent.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Incompatible changes</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
There is now a special version of `org.el' for XEmacs.
|
|
Before installation, as an XEmacs user you must rename the
|
|
file org_xemacs.el to org.el, i.e. you must overwrite org.el
|
|
with the xemacs version. For example:
|
|
|
|
<p>
|
|
<pre>
|
|
mv org_xemacs.el org.el
|
|
</pre>
|
|
</p>
|
|
<p>
|
|
This is necessary so that I can make use of some features
|
|
that would be cumbersome to support in a single file. The
|
|
XEmacs version is derived from the Emacs version with a
|
|
program, so no reason to fear that I might be dropping
|
|
XEmacs support any time soon. Sorry for the trouble.
|
|
</p>
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Details</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
A time stamp may now contain a range of times. So you no
|
|
longer need to use two separate stamps to indicate a time
|
|
interval on a single day. For example
|
|
|
|
<p>
|
|
<pre>
|
|
<2007-06-18 Mon 17:30-18:20>
|
|
</pre>
|
|
</p>
|
|
<p>
|
|
This is now fully supported, including changing the time
|
|
with S-up/down while the cursor is on the end time. Also,
|
|
da the date/time prompt, you can simply write your time like
|
|
12:00-14:00 and the range will be inserted.
|
|
</p>
|
|
<p>
|
|
This was proposed by Leo some time ago, and recently by
|
|
Michael.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
You may specify clocking times by hand (i.e. without
|
|
clocking in and out) using this syntax.
|
|
|
|
<p>
|
|
<pre>
|
|
CLOCK: => 2:00
|
|
</pre>
|
|
</p>
|
|
<p>
|
|
Thanks to Scott Jaderholm for this proposal.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
TAGS may now contain language-specific word characters, as
|
|
long as they are matched by the "[:alnum:]" regexp syntax.
|
|
This is for Emacs only, the XEmacs version continues to use
|
|
the character class "a-zA-Z0-9_@" for tag names. Thanks to
|
|
David Smith for a patch to this effect (a modified version
|
|
of that patch was applied). I am considering to make the
|
|
same change for TODO keywords, but not yet. Note that files
|
|
using localization features may not work correctly in the
|
|
Emacs configuration of another user, so if you are sharing
|
|
org-mode files with other users, it might still be best to
|
|
stick to the ASCII characters.
|
|
|
|
</li>
|
|
<li>
|
|
Promotion and demotion of plain list items (commands M-left,
|
|
M-right) no longer changes the indentation by just one
|
|
space. Instead, it uses intelligence gathered from the
|
|
surrounding list structure to do the right thing. Thanks to
|
|
William Henney for starting the discussion about this.
|
|
|
|
</li>
|
|
<li>
|
|
TAB does now a better job of indenting lines.
|
|
|
|
<ul>
|
|
<li>
|
|
After tables and code segments (lines starting with ":"),
|
|
indentation goes back to what it was before (thanks to
|
|
William Henney for suggesting this behavior).
|
|
|
|
</li>
|
|
<li>
|
|
When plain lists items are involved, we had a long
|
|
discussion on emacs-orgmode where I tried to show that a
|
|
too-sophisticated implementation will still be easily
|
|
fooled. Here is what I have implemented now - lets see
|
|
if we can agree on this:
|
|
|
|
<p>
|
|
Indentation will flatten lists with the same bullet type,
|
|
but indent another bullet type further. The time when
|
|
this fails is in a nested list, when you want to get back
|
|
out to a previous level. For example
|
|
</p>
|
|
<p>
|
|
<pre>
|
|
- item 1
|
|
- item 2
|
|
+ item 2a
|
|
+ item 2b
|
|
- item 3
|
|
</pre>
|
|
</p>
|
|
<p>
|
|
When using TAB on every line in this list, the structure
|
|
will change to
|
|
</p>
|
|
<p>
|
|
<pre>
|
|
- item 1
|
|
- item 2
|
|
+ item 2a
|
|
+ item 2b
|
|
- item 3
|
|
</pre>
|
|
</p>
|
|
<p>
|
|
So you need to change the level of the last line by hand,
|
|
using promotion and demotion functions.
|
|
</p>
|
|
</li>
|
|
</ul></li>
|
|
</ul></div>
|
|
</div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.77</h2>
|
|
|
|
|
|
|
|
<div class="outline-3">
|
|
<h3>Overview</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
Vertical lines in exported tables.
|
|
</li>
|
|
<li>
|
|
New default for `org-show-following-heading'.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Incompatible changes</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
The default for `org-show-following-heading' is now nil.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Details</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
You can now specify column groups in tables, to the effect
|
|
that the groups will be separated by vertical lines in HTML
|
|
and ASCII output. Column groups are specified by the
|
|
characters "<" and ">" in a special table row. "<" starts a
|
|
group, ">" ends a group (in each case including the the
|
|
column where the character is specified). You may also use
|
|
"<>" to make a group a single column wide. For example:
|
|
|
|
<p>
|
|
<pre>
|
|
| | N | N^2 | N^3 | N^4 | sqrt(n) | sqrt[4](N) |
|
|
|---+----+-----+-----+-----+---------+------------|
|
|
| / | <> | < | | > | < | > |
|
|
| # | 1 | 1 | 1 | 1 | 1 | 1 |
|
|
| # | 2 | 4 | 8 | 16 | 1.4142 | 1.1892 |
|
|
| # | 3 | 9 | 27 | 81 | 1.7321 | 1.3161 |
|
|
#+TBLFM: $3=$2^2::$4=$2^3::$5=$2^4::$6=sqrt($2)::$7=sqrt(sqrt(($2))
|
|
</pre>
|
|
</p>
|
|
<p>
|
|
A table row with with nothing but "/" in the first field is
|
|
never exported, but can be used to place column group
|
|
information into the table. In this table, we create a
|
|
group for column 2, one for columns 3-5 and one for columns
|
|
6-7. HTML export will render a vertical line between these
|
|
groups.
|
|
</p>
|
|
<p>
|
|
Because HTML does not require closing <colgroup> tags with
|
|
</colgroup>), you can also simply start a new column
|
|
wherever you want a vertical line:
|
|
</p>
|
|
<p>
|
|
<pre>
|
|
| N | N^2 | N^3 | N^4 | sqrt(n) | sqrt[4](N0 |
|
|
|---+-----+-----+-----+---------+------------|
|
|
| / | < | < | | < | |
|
|
</pre>
|
|
</p>
|
|
</li>
|
|
<li>
|
|
Vertical lines are now also omitted in ASCII export, unless
|
|
grouping explicitly requests these lines.
|
|
|
|
</li>
|
|
<li>
|
|
The default for `org-show-following-heading' is now nil,
|
|
meaning that sparse trees will be more compact. This has
|
|
become possible due to in important remark by Jason Dunsmore
|
|
who pointed out that TAB should behave differently in the
|
|
inconsistent trees produced by the sparse tree commands.
|
|
TAB does now make sure that the heading after a freshly
|
|
unfolded tree is made visible at all, removing the confusing
|
|
behavior we had before.
|
|
|
|
</li>
|
|
<li>
|
|
Several bugs fixed. In particular:
|
|
|
|
<ul>
|
|
<li>
|
|
Strings produced by agenda batch processing with
|
|
`org-batch-agenda' and `org-batch-agenda-csv' are now
|
|
properly encoded, so that you should be able to use
|
|
special characters in other languages as along as your
|
|
post-processing program handles them correctly. At least
|
|
for Emacs this should work now, but have not yet figured
|
|
out how to do this in XEmacs.
|
|
|
|
</li>
|
|
</ul></li>
|
|
</ul></div>
|
|
</div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.76</h2>
|
|
|
|
|
|
|
|
<div class="outline-3">
|
|
<h3>Overview</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
Exporting Footnotes to HTML
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Details</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
Footnotes like<sup><a class="footref" name="fnr.1" href="#fn.1">1</a></sup> are now exported to HTML
|
|
|
|
<p class="footnote"><sup><a class="footnum" name="fn.1" href="#fnr.1">1</a></sup>This is a footnote
|
|
|
|
<p>
|
|
Thanks to Scott Jaderholm for this proposal and a detailed
|
|
HTML example on how the exported text should look like.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
Special version of the reference card, for letter paper.
|
|
|
|
</li>
|
|
<li>
|
|
Switching to OVERVIEW with S-TAB no loner moves the cursor,
|
|
so after three `S-TAB' commands, you will be back where you
|
|
started.
|
|
|
|
</li>
|
|
<li>
|
|
Bug fixes, lots of them again.
|
|
|
|
</li>
|
|
</ul></div>
|
|
</div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.75</h2>
|
|
|
|
|
|
|
|
<div class="outline-3">
|
|
<h3>Overview</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
Cyclic time stamps that repeat after an interval.
|
|
</li>
|
|
<li>
|
|
Special timestamps for appointments like "every 2nd Thursday
|
|
in a month".
|
|
</li>
|
|
<li>
|
|
Completion of link abbreviation prefixes inside `C-c C-l'.
|
|
</li>
|
|
<li>
|
|
Replacing a region of org-mode syntax with HTML.
|
|
</li>
|
|
<li>
|
|
iCalendar export now honors ARCHIVE etc.
|
|
</li>
|
|
<li>
|
|
New command to add/change emphasis markers.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Incompatible Changes</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
The REPEAT(…) cookie is no longer supported, the repeater
|
|
interval now goes directly into the time stamp.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Details</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
Time stamps can contain a repeater code, like +1w for once
|
|
every week, +2d for every two days, etc. For example,
|
|
|
|
</li>
|
|
</ul>
|
|
<p><span class="timestamp">2007-05-16 Wed 12:30 +1w</span><br/>
|
|
</p>
|
|
<p>
|
|
will apply to every Wednesday, starting from the date given.
|
|
I believe this syntax was actually suggested by someone on
|
|
the mailing list, but I cannot find the email back. To
|
|
collect your credit, let me know!
|
|
</p>
|
|
<ul>
|
|
<li>
|
|
You can use an sexp diary entry (with the syntax used by the
|
|
Emacs calendar/diary) in a time stamp, like this:
|
|
|
|
<p>
|
|
*** The nerd club meets on 2nd Thursday of every month
|
|
</p></li>
|
|
</ul>
|
|
<p><span class="timestamp">%%(diary-float t 4 2)</span><br/>
|
|
</p>
|
|
<ul>
|
|
<li>
|
|
You can put diary-style sexp entries directly into an
|
|
org-mode file, where they will be interpreted just like they
|
|
would in the diary. For example
|
|
|
|
<ul>
|
|
<li>
|
|
Birthdays and similar stuff
|
|
</li>
|
|
</ul>
|
|
<p>#+CATEGORY: Holiday
|
|
%%(org-calendar-holiday) ; special function for holiday names
|
|
#+CATEGORY: Ann
|
|
%%(diary-anniversary 14 5 1956) Artur Dent %d is years old
|
|
%%(diary-anniversary 2 10 1869) Mahatma Gandhi
|
|
</p>
|
|
<p>
|
|
These entries must start at column 0 to be evaluated.
|
|
</p>
|
|
<p>
|
|
It turns out that evaluating the entries in an org-mode file
|
|
is actually faster than in the diary itself, because using
|
|
the diary has some overhead (creating fancy diary display,
|
|
then reading and re-interpreting the entries). I have moved
|
|
all the sexp entries from my diary into an org-mode file,
|
|
put in a few categories, and then turned off
|
|
`org-agenda-include-diary'. This has led to a noticeably
|
|
faster agenda display.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
New command `org-replace-region-by-html' that converts the
|
|
current region from org-mode syntax into HTML. For example,
|
|
you might write an itemized list in plain text in an HTML
|
|
buffer, and then invoke this command to convert it. Thanks
|
|
to Raman for this idea.
|
|
|
|
</li>
|
|
<li>
|
|
When inserting a link with `C-c C-l', completion will now
|
|
fill in all valid link prefixes, like http or ftp, but also
|
|
link abbreviation prefixes. This is based on an idea by
|
|
Bastien.
|
|
|
|
</li>
|
|
<li>
|
|
Highest, lowest, and default priority can be set on a
|
|
per-file basis with #+PRIORITIES: H L D
|
|
For example, to use priorities from 1 to 9, you could use
|
|
|
|
<p>
|
|
#+PRIORITIES: 1 9 9
|
|
</p>
|
|
<p>
|
|
Thanks to Dmitri Minaev for a patch to this effect.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
iCalendar export now honors (i.e. skips) subtrees marked as
|
|
ARCHIVE, COMMENT, or QUOTE.
|
|
|
|
</li>
|
|
<li>
|
|
There is a new command to add or change the emphasis (like
|
|
bold or italic) of a piece of text. For lack of better
|
|
available keys the command is at `C-c C-x C-f', but you may
|
|
well want to choose a more convenient key like `C-c f' in
|
|
your private setup:
|
|
|
|
<p>
|
|
(add-hook 'org-load-hook
|
|
(lambda () (define-key org-mode-map "\C-cf" 'org-emphasize)))
|
|
</p>
|
|
<p>
|
|
The command will prompt for an emphasis type, and you may
|
|
reply either with the marker that triggers the emphasis, or
|
|
with the first letter of the corresponding HTML tag. For
|
|
example, to select italic, press either "/" or "i".
|
|
</p>
|
|
<p>
|
|
If there is an active region, the emphasis of this region
|
|
will be set or changed. If there is no region, only the
|
|
emphasis markers will be inserted and the cursor positioned
|
|
between them. Thanks to Bastien for proposing this feature.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
Bug fixes, everything where I have replied "fixed" on the
|
|
mailing list. Thanks to all of you for keeping these reports
|
|
coming.
|
|
|
|
</li>
|
|
</ul></div>
|
|
</div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.74</h2>
|
|
|
|
|
|
|
|
<div class="outline-3">
|
|
<h3>Overview</h3>
|
|
|
|
|
|
<p>
|
|
This release is about exporting agenda views, to HTML, to
|
|
postscript for printing, and to a special format (CSV) for
|
|
further processing in scripts.
|
|
</p>
|
|
</div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Incompatible Changes</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
The variable `org-agenda-remove-tags-when-in-prefix' has
|
|
been renamed to `org-agenda-remove-tags'.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Details</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
Agenda views can be exported as plain text, as HTML, and as
|
|
Postscript(R). This can simply be done from the agenda
|
|
buffer with `C-x C-w' and then specifying a filename like
|
|
`myagenda.html' or `myagenda.ps'. See section 8.6.4 of the
|
|
manual.
|
|
|
|
</li>
|
|
<li>
|
|
Each custom agenda view can specify a list of associated
|
|
files names. The command `C-c a e' then creates all views
|
|
that have associated file names and exports the views to
|
|
these files. This is great for producing paper versions of
|
|
your views, to take with you when you don't have your
|
|
computer. The manual has an example on how to do this, and
|
|
in particular on how to customize the format of the printed
|
|
version. See section 8.6.4 of the manual.
|
|
|
|
</li>
|
|
<li>
|
|
You can produce a CSV format of agenda information with an
|
|
Emacs batch command. This is greate for further processing
|
|
in scipts. Thanks to Jason F. McBrayer for this idea.
|
|
See section 8.6.5 of the manual.
|
|
|
|
</li>
|
|
<li>
|
|
New variable `org-agenda-skip-deadline-if-done'. When set,
|
|
a deadline associated with a DONE item will not be shown in
|
|
the agenda. This is based upon a report by Denis Bueno.
|
|
|
|
</li>
|
|
<li>
|
|
Quite a few bug fixes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
</div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.73</h2>
|
|
|
|
|
|
<p>
|
|
Minor bug fixes.
|
|
</p>
|
|
</div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.72</h2>
|
|
|
|
|
|
|
|
<div class="outline-3">
|
|
<h3>Overview</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
Control over blank lines between trees in collapsed view.
|
|
|
|
</li>
|
|
<li>
|
|
Info about the running clock is shown in the modeline.
|
|
|
|
</li>
|
|
<li>
|
|
C-a can behave specially in headlines.
|
|
|
|
</li>
|
|
<li>
|
|
Better color and scaling defaults for LaTeX fragments.
|
|
|
|
</li>
|
|
<li>
|
|
Customizable list of keys in org-mode to be replaced.
|
|
|
|
</li>
|
|
<li>
|
|
Stuck project descriptions have been extended.
|
|
|
|
</li>
|
|
<li>
|
|
Emphasis code has been modified to fix some issues.
|
|
|
|
</li>
|
|
<li>
|
|
Bug fixes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Incompatible changes</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
The option `org-format-latex-options' has changed. If you
|
|
have customized it, please revert to default and then redo
|
|
your customization.
|
|
|
|
</li>
|
|
<li>
|
|
`org-CUA-compatible' no longer modifies S-RET by default,
|
|
because newer versions of CUA don't use this key anymore.
|
|
If you need this replacement, customize the variable
|
|
`org-disputed-keys'.
|
|
|
|
</li>
|
|
<li>
|
|
The variable `org-CUA-compatible' is obsolete, please use
|
|
`org-replace-disputed-keys' instead. `org-CUA-compatible'
|
|
is still an alias for this new variable, though.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Details</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
Better control over blank lines between trees in collapsed
|
|
view. This has come up several times in the past and most
|
|
recently by Scott Jaderholm. There is now a new variable
|
|
`org-cycle-separator-lines' with default value 2. It says
|
|
how many empty lines there need to be after the end of a
|
|
subtree to get an empty line in collapsed view. So with the
|
|
default, if you leave only one empty line it will disappear
|
|
in collapsed view. If you leave two, one empty line will
|
|
remain so that you can use double empty lines to structure
|
|
the collapsed views of a file. I love it, so many thanks to
|
|
Scott fro bringing this up again.
|
|
|
|
<p>
|
|
One property of the new setup is that you will never get
|
|
more than one blank line in collapsed view. We could do
|
|
something special to allow <b>several</b> empty lines in
|
|
collapsed view, but I think this is counter-productive.
|
|
</p>
|
|
<p>
|
|
In Emacs 22, if you want to make full use of this, make sure
|
|
that you have not set `outline-blank-line'.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
When the clock is running, Org-mode will put info about it
|
|
into the modeline. The info consists of the elapsed time
|
|
and the heading of the clocked item. This was a proposal
|
|
from Bastien who got the idea from Muse.
|
|
|
|
</li>
|
|
<li>
|
|
C-a can behave specially in headlines when you set the
|
|
variable `org-special-ctrl-a'. It will bring the cursor
|
|
first back only to the beginning of the headline <b>text</b>,
|
|
i.e. after the stars and the TODO keyword, if any. A second
|
|
C-a will then move the cursor to the beginning of the line.
|
|
If the cursor is already at the beginning of the line, C-a
|
|
will spring <b>forward</b> to the headline text. This was a
|
|
proposal from Leo, based on a request from Scott Jaderholm.
|
|
|
|
<p>
|
|
I have not turned this turned this on by default, should I?
|
|
</p>
|
|
</li>
|
|
<li>
|
|
When LaTeX fragments are processed into images, there is now
|
|
more control and (hopefully) betters defaults for colors and
|
|
scaling. Special values can be set for HTML export, so that
|
|
these values can differ from what is used for display in an
|
|
emacs buffer. The default foreground and background colors
|
|
for images embedded in emacs are now taken from the default
|
|
emacs face. Thanks to Xiao-Yong Jin for proposing these
|
|
changes.
|
|
|
|
</li>
|
|
<li>
|
|
There is now a much better mechanism to change some keys in
|
|
org-mode if these keys clash with other modes you use. Turn
|
|
this on by setting `org-replace-disputed-keys' (aliased to
|
|
`org-CUA-compatible'). The list of keys to replace is now
|
|
fully customizable, see the option `org-disputed-keys'.
|
|
Many thanks to Meciej Katafiasz for a patch implementing
|
|
this.
|
|
|
|
</li>
|
|
<li>
|
|
Stuck project descriptions have been extended. You can now
|
|
use "*" as a TODO keyword or tag to say that <b>any</b> TODO
|
|
keyword or TAG marks a project as non-stuck. You also can
|
|
give an arbitrary regular expression that, if it matches,
|
|
indicates a non-stuck project.
|
|
|
|
</li>
|
|
<li>
|
|
The code for emphasis like bold, italic etc has been
|
|
modified - I might have broken something in the process,
|
|
please let me know if you find problems.
|
|
|
|
</li>
|
|
<li>
|
|
A number of bugs have been fixed - those where I have
|
|
replied "Fixed" on the mailing list.
|
|
|
|
</li>
|
|
</ul></div>
|
|
</div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.71</h2>
|
|
|
|
|
|
|
|
<div class="outline-3">
|
|
<h3>Overview</h3>
|
|
|
|
|
|
</div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Incompatible changes</h3>
|
|
|
|
|
|
</div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Details</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
New variables to customize the header and data tags in
|
|
exported HTML. These are the variables
|
|
`org-export-table-header-tags' and
|
|
`org-export-table-data-tags'. This follows a request from
|
|
Scott Otterson.
|
|
|
|
</li>
|
|
<li>
|
|
New option `org-format-latex-header' for customizing the
|
|
header of the LaTeX file used to convert embedded LaTeX to
|
|
images. Thanks to `Matthieu Lemerre' for the suggestion.
|
|
|
|
</li>
|
|
<li>
|
|
The prefix version of `org-todo-list' works again. This
|
|
means that `C-1 C-c a t' produces the list of TODO entries
|
|
for the first TODO keyword. If you use different TODO setups
|
|
in different agenda files, be careful: This number now
|
|
refers to the list of <b>all</b> todo keywords used in files
|
|
that are scanned for the agenda.
|
|
|
|
</li>
|
|
<li>
|
|
Many bug fixes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
</div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.70</h2>
|
|
|
|
|
|
|
|
<div class="outline-3">
|
|
<h3>Overview</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
Dust settles after revamp of TODO keyword system.
|
|
</li>
|
|
<li>
|
|
The export title can be taken from the first text line.
|
|
</li>
|
|
<li>
|
|
TTY replacement keys have changed.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Incompatible changes</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
Some TTY replacement keys are changed, see below.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Details</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
Further development concerning TODO keywords.
|
|
|
|
<ul>
|
|
<li>
|
|
You can now have several DONE states in a sequence, like
|
|
|
|
<p>
|
|
#+SEQ_TODO: TODO VERIFY | DONE DELEGATED
|
|
</p>
|
|
<p>
|
|
The difference to the proposal discussed on the mailing
|
|
list (and which is also works!)
|
|
</p>
|
|
<p>
|
|
#+SEQ_TODO: TODO VERIFY | DONE
|
|
#+SEQ_TODO: | CANCELED
|
|
</p>
|
|
<p>
|
|
is that in the first case, the extra DONE states will be
|
|
reached with `C-c C-t' (or with `t' from the agenda), while
|
|
in the second case you need S-<right> to get to the special
|
|
states. I guess both ideas can be useful - I am leaning
|
|
toward using the latter.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
Setting up TODO keywords in Lisp previously used two
|
|
separate variables: `org-todo-keywords' and
|
|
`org-todo-interpretation'. The preferred way is now to use
|
|
only `org-todo-keywords', with a new structure:
|
|
|
|
<p>
|
|
(setq org-todo-keywords
|
|
'((sequence "TODO" "|" "DONE")
|
|
(sequence "BUG" "KNOWNCAUSE" "|" "FIXED" "IGNORED")
|
|
(type "Fred" "Lisa" "Peter" "|" "DONE")
|
|
(sequence "CANCELED") ; for things we decide to not do.
|
|
))
|
|
</p>
|
|
<p>
|
|
If your setting has this new structure,
|
|
`org-todo-interpretation' will be ignored. This change
|
|
does not break backward compatibility. The old way of
|
|
using a flat list in `org-todo-keywords' and taking the
|
|
interpretation from the other variable still works.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
When listing <b>specific</b> TODO entries via a sparse tree
|
|
(`C-u C-c C-v') or via the agenda (`C-c a T' or `C-u C-c a
|
|
t'), you can now specify several keywords to be selected,
|
|
like "TODO|VERIFY|WAITING". This also works for custom
|
|
agenda commands. Thanks to Jason F. McBrayer for pointing
|
|
out this omission.
|
|
|
|
</li>
|
|
</ul></li>
|
|
<li>
|
|
If you have configured Org-mode to export also the text
|
|
before the first headline (this is done by setting the
|
|
variable `org-export-skip-text-before-1st-heading' to nil),
|
|
then the first normal text line in the buffer becomes the
|
|
title of the exported document. A title set with #+TITLE
|
|
overules this default, and the first line then belongs to the
|
|
normal text. Thanks to David House for this proposal.
|
|
|
|
</li>
|
|
<li>
|
|
TTY replacement keys. Some of the key bindings used by
|
|
Org-mode do not work on a tty, so replacement key sequences
|
|
are provided on ttys. In version 4.70, there are some
|
|
changes in the tty replacements. Thanks to Jason F. McBrayer
|
|
for coming up with the idea to use C-c <cursor> keys.
|
|
|
|
<table border="2" cellspacing="0" cellpadding="6" rules="groups" frame="hsides">
|
|
<col align="left"></col><col align="left"></col><col align="left"></col><col align="left"></col>
|
|
<thead>
|
|
<tr><th>Command</th><th></th><th>Old TTY</th><th>New TTY</th></tr>
|
|
<tr><th>org-…..</th><th>Main Key</th><th>Replacement</th><th>Replacement</th></tr>
|
|
</thead>
|
|
<tbody>
|
|
<tr><td>shiftleft</td><td>S-left</td><td>C-c C-x left</td><td>C-c left</td></tr>
|
|
<tr><td>shiftright</td><td>S-right</td><td>C-c C-x right</td><td>C-c right</td></tr>
|
|
<tr><td>shiftup</td><td>S-up</td><td>C-c C-x up</td><td>C-c up</td></tr>
|
|
<tr><td>shiftdown</td><td>S-down</td><td>C-c C-x down</td><td>C-c down</td></tr>
|
|
<tr><td>shiftcontrolleft</td><td>C-S-left</td><td></td><td>C-c C-x left</td></tr>
|
|
<tr><td>shiftcontrolright</td><td>C-s-right</td><td></td><td>C-c C-x right</td></tr>
|
|
</tbody>
|
|
</table>
|
|
|
|
|
|
|
|
</li>
|
|
</ul></div>
|
|
</div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.69</h2>
|
|
|
|
|
|
|
|
<div class="outline-3">
|
|
<h3>Overview</h3>
|
|
|
|
|
|
<p>
|
|
This time the changes affect the following areas:
|
|
</p>
|
|
<ul>
|
|
<li>
|
|
TODO keywords: Multiple sequences in a single file.
|
|
</li>
|
|
<li>
|
|
Export: More control over text before the first heading.
|
|
</li>
|
|
<li>
|
|
Export: More control over sub/superscript interpretation.
|
|
</li>
|
|
<li>
|
|
Plain lists: Option to let empty lines terminate lists.
|
|
</li>
|
|
<li>
|
|
Tables: New command to insert hline and move into line below.
|
|
</li>
|
|
<li>
|
|
REPEATing items: Turn of note taking.
|
|
</li>
|
|
<li>
|
|
Bug fixes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Incompatible changes</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
It used to be possible to spread the list of TODO keywords
|
|
over several lines, like
|
|
|
|
<p>
|
|
#+SEQ_TODO: TODO
|
|
#+SEQ_TODO: PROGRESS
|
|
#+SEQ_TODO: DONE
|
|
</p>
|
|
<p>
|
|
This is no longer possible. Each such line now specifies an
|
|
independent set of TODO keywords, with its own DONE state.
|
|
See below for details.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
The #+TEXT construct has been used to insert unchanged HTML
|
|
into an exported file. This is no longer possible, the TEXT
|
|
lines will be processed like any other lines. However,
|
|
there are now much better ways of getting quoted HTML into
|
|
the exported file.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Details</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
You can now use multiple sets of TODO keywords in the same
|
|
buffer. For example, you may put the following three lines
|
|
into a file:
|
|
|
|
<p>
|
|
#+SEQ_TODO: TODO DONE
|
|
#+SEQ_TODO: REPORT BUG KNOWNCAUSE RESOLVED
|
|
#+TYP_TODO: Fred Laura Peter Me OK
|
|
</p>
|
|
<p>
|
|
Each sub-sequence has its own DONE state. It is best to use
|
|
different keywords in all sequences, to make sure Org-mode
|
|
does not loose track in which specific sequence it is
|
|
working. You could use the same word for all DONE states,
|
|
but then cycling through to a TODO state might not bring you
|
|
where you want to be.
|
|
</p>
|
|
<p>
|
|
After initially setting a keyword, `C-c C-t' cycles through
|
|
a sublist, i.e. is cycles from TODO to DONE or from
|
|
KNOWNCAUSE to RESOLVED and further to (nothing) and back to
|
|
REPORT.
|
|
</p>
|
|
<p>
|
|
S-right and S-left allow to select any keyword, so they move
|
|
from DONE to REPORT and from RESOLVED to Fred.
|
|
</p>
|
|
<p>
|
|
C-S-right and C-S-left jump from one sub-sequence to the
|
|
next, for example from TODO or DONE to REPORT to Fred.
|
|
</p>
|
|
<p>
|
|
Thanks to Rick Moynihan for triggering this development.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
Text before the first headline can now be exported if you
|
|
configure Org-mode accordingly. Either set the variable
|
|
`org-export-skip-text-before-1st-heading' to nil, or use the
|
|
new in-buffer option
|
|
|
|
<p>
|
|
#+OPTION: skip:nil
|
|
</p>
|
|
</li>
|
|
<li>
|
|
Export content specified via the #+TEXT construct is now
|
|
fully processed, i.e. links, emphasis etc. are all
|
|
interpreted. #+TEXT lines may include
|
|
#+BEGIN_HTML…#+END_HTML sections to embed literal HTML.
|
|
|
|
</li>
|
|
<li>
|
|
During HTML export, you can request to have a<sub>b</sub>
|
|
interpreted as a subscript, but to leave a_b as it is. This
|
|
can be done by setting the variable
|
|
org-export-sub-superscript to the symbol `{}' with
|
|
|
|
<p>
|
|
(setq org-export-sub-superscript '{})
|
|
</p>
|
|
<p>
|
|
or by using
|
|
</p>
|
|
<p>
|
|
#+OPTIONS: ^:{}
|
|
</p>
|
|
<p>
|
|
Thanks to Eddward DeVilla for this idea.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
New variable `org-empty-line-terminates-plain-lists'.
|
|
Default is nil, meaning that empty lines are part of the
|
|
previous list item, and that you can have several paragraphs
|
|
in one such item. Set this to t if you want an empty line
|
|
terminate all levels of plain list items.
|
|
|
|
<p>
|
|
Thanks to Mike Newman for triggering this development.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
C-c RET does insert a horizontal separator line and move the
|
|
cursor into the table line below it. Thanks to Bastien for
|
|
this proposal.
|
|
|
|
</li>
|
|
<li>
|
|
Org-mode always offers you to record a note when a TODO item
|
|
automatically repeats, even if you are not logging state
|
|
changes. The new variable `org-log-repeat' allows to turn
|
|
this off, so that notes are really only been taken if you
|
|
are logging all state changes.
|
|
|
|
</li>
|
|
<li>
|
|
Various Bug fixes, thanks to everyone who reported.
|
|
|
|
</li>
|
|
</ul></div>
|
|
</div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.68</h2>
|
|
|
|
|
|
|
|
<div class="outline-3">
|
|
<h3>Overview</h3>
|
|
|
|
<ul>
|
|
<li>
|
|
Priority handling in the tags view
|
|
</li>
|
|
<li>
|
|
Date/time prompt follows the popup calender, and accepts AM/PM times.
|
|
</li>
|
|
<li>
|
|
Standard references like B4 in the spreadsheet.
|
|
</li>
|
|
<li>
|
|
Improvements to the formula editor.
|
|
</li>
|
|
<li>
|
|
C-j does better indentation.
|
|
</li>
|
|
<li>
|
|
Bug fixes
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Details</h3>
|
|
|
|
<ul>
|
|
<li>
|
|
Priority handling in the tags view
|
|
|
|
<ul>
|
|
<li>
|
|
Agenda lists selected by tag are now sorted by priority.
|
|
Thanks to Andrew Korty for reporting this omission.
|
|
|
|
</li>
|
|
</ul></li>
|
|
<li>
|
|
Improvements to the date/time prompt.
|
|
|
|
<ul>
|
|
<li>
|
|
When you move (using S-cursor keys) the cursor in the pop-up
|
|
calendar window while responding to a date/time prompt, the
|
|
prompt is updated with the new default date (Emacs only).
|
|
|
|
</li>
|
|
<li>
|
|
You can now enter AM/PM times at this prompt.
|
|
|
|
</li>
|
|
</ul></li>
|
|
<li>
|
|
Changes in the spreadsheet
|
|
|
|
<ul>
|
|
<li>
|
|
You can now also write B4 instead of @4$2 as a reference in
|
|
formulas. The column references without specified row can be
|
|
written as C& instead of $3. Such references make formulas
|
|
easier to read and are now the default way how references are
|
|
shown when you edit existing formulas. To get the old behavior
|
|
back (i.e. only @row$col references), set the variable
|
|
`org-table-use-standard-references' to nil.
|
|
|
|
<p>
|
|
Relative references like @-3$-2 or @II..III continue to use the
|
|
internal format.
|
|
</p>
|
|
</li>
|
|
</ul></li>
|
|
<li>
|
|
Changes in the formula editor (the one you get with "C-c '")
|
|
|
|
<ul>
|
|
<li>
|
|
The formulas are organized in a more logical way.
|
|
|
|
</li>
|
|
<li>
|
|
There is now a menu with commands.
|
|
|
|
</li>
|
|
<li>
|
|
When starting the formula editor with "C-c '", the cursor
|
|
immediately moves to the formula for the current field.
|
|
|
|
</li>
|
|
<li>
|
|
With the cursor on a reference in the formula, you can use
|
|
S-cursor keys to change the field being referenced.
|
|
|
|
</li>
|
|
</ul></li>
|
|
<li>
|
|
C-j indents the following line correctly whe used in a headline
|
|
or in aplain list item. Thanks to Leo for this suggestion.
|
|
|
|
</li>
|
|
<li>
|
|
Bug fixes
|
|
|
|
<ul>
|
|
<li>
|
|
Flyspell now knows about special org-mode commands.
|
|
Thanks to Vinod Valsalam for reporting this problem, and to
|
|
Andrew Korty for showing how to fix it.
|
|
|
|
</li>
|
|
<li>
|
|
Most other bugs discussed recently on emacs-orgmode@gnu.org
|
|
should be fixed, except the problem with non-ASCII characters
|
|
in tags….
|
|
|
|
</li>
|
|
</ul></li>
|
|
</ul></div>
|
|
</div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.67</h2>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
Expert mode for fast tag selection.
|
|
When org-fast-tag-selection-single-key is `expert', not even
|
|
the selection window is shown, only the prompt. One more C-c
|
|
gets you the window, another one goes to multiple selection mode.
|
|
|
|
</li>
|
|
<li>
|
|
Synchronized with Emacs once more: Emacs CVS has now org-mode
|
|
4.67. At least until it causes a problem, then the Emacs people
|
|
will switch back to 4.56. Lets hope there will be no problem.
|
|
|
|
</li>
|
|
<li>
|
|
Code cleanup
|
|
|
|
</li>
|
|
<li>
|
|
Bug fixes
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.66</h2>
|
|
|
|
|
|
|
|
<div class="outline-3">
|
|
<h3>Overview</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
Sorting of top-level entries works now if the region contains
|
|
top-level entries, or if the cursor is before the first headline.
|
|
Thanks to "redblue" for reporting this bug.
|
|
|
|
</li>
|
|
<li>
|
|
When entering date and time at the prompt, you can now mix
|
|
entering text and selecting something in the calendar. For
|
|
example, enter 22:15 at the prompt without pressing RET, and then
|
|
click on a date in the calendar. Both pieces of information will
|
|
be included in the resulting time stamp. You can also use
|
|
S-curser to move the cursor in the calendar to the desired date
|
|
and then enter 22:15 and press RET at the prompt.
|
|
|
|
</li>
|
|
<li>
|
|
When setting a deadline or a schedule, entering a time now
|
|
automatically selects the time stamp format that includes the
|
|
time. Bug report (by means of a question) from Bastre.
|
|
|
|
</li>
|
|
<li>
|
|
C-c C-l can be used to convert a plain link into a bracket link.
|
|
|
|
</li>
|
|
<li>
|
|
Internal links now match inside (the visible part of) other
|
|
links. Thanks to Scott Otterson for reporting this bug.
|
|
|
|
</li>
|
|
<li>
|
|
iCalendar export of TODO items fixed, see also the variable
|
|
`org-icalendar-include-todo'. Thanks to Philipp Raschdorf.
|
|
|
|
</li>
|
|
<li>
|
|
The number of levels in the table of contents of an exported
|
|
document can now be set independently of the number of headline
|
|
levels. For example:
|
|
|
|
<p>
|
|
#+OPTIONS: H:4 toc:2
|
|
</p>
|
|
</li>
|
|
<li>
|
|
The command `C-c }' toggles the display of row and column numbers
|
|
the the current table, to aid constructing formulas. To try it,
|
|
move the cursor to a table and press `C-c }', or use the menu
|
|
entry.
|
|
|
|
</li>
|
|
<li>
|
|
Orgtbl translation functions (introduced in 4.65) have been
|
|
simplified using a generic function `orgtbl-to-generic' that can
|
|
be used for very general languanges. Writing your own translator
|
|
should be very easy now. More info in the manual.
|
|
|
|
</li>
|
|
<li>
|
|
CONTENTS visibility can be limited to a certain level. The
|
|
command `C-3 S-TAB' will switch to CONTENTS view and show the
|
|
first 3 levels.
|
|
|
|
</li>
|
|
<li>
|
|
Bug fixes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
</div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.65</h2>
|
|
|
|
|
|
|
|
<div class="outline-3">
|
|
<h3>Overview</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
Orgtbl can be used to maintain tables in LaTeX, and in any other mode
|
|
</li>
|
|
<li>
|
|
Editing Lisp formulas for tables improved.
|
|
</li>
|
|
<li>
|
|
Better structure for HTML exported tables.
|
|
</li>
|
|
<li>
|
|
New "calculation" marker "/" to mark lines that should not be exported.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Detailed description of changes</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
You can use orgtbl mode to maintain a LaTeX table, or pretty much
|
|
any table in any mode.
|
|
|
|
<p>
|
|
This does <b>not</b> work by making Orgtbl aware of LaTeX syntax. That
|
|
would be a box of Pandora I am not willing to open. Instead, you
|
|
use a normal Orgtbl-mode table, and a converter program to
|
|
automatically place a LaTeX version of the table into the correct
|
|
spot in the LaTeX file. The orgtbl-mode table can be maintained
|
|
inside the same file, in a block comment.
|
|
</p>
|
|
<p>
|
|
I am providing translators for LaTeX, HTML, and TeXInfo. For
|
|
other applications, you need to write one yourself - but that is
|
|
not hard if you start from the LaTeX version and just modify it.
|
|
Thanks to Thomas Baumann for triggering this development through
|
|
a request for a table-to-LaTeX converter.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
In the special buffer to edit the formulas of a table (created
|
|
with "C-c '"), there is now better support for editing Lisp
|
|
formulas. TAB and M-TAB work like in an Emacs Lisp buffer,
|
|
indenting lines and completing lisp symbols. With the cursor on
|
|
a line defining a complex Lisp formula, a first press on TAB will
|
|
convert the formula into a pretty-printed version with proper
|
|
linebreaks and indentation. A second TAB folds the line back to
|
|
the compact form.
|
|
|
|
</li>
|
|
<li>
|
|
Tables in HTML export have now additional structure elements
|
|
defined. The header (before the first hline) is wrapped into
|
|
<thead>..</thead>, and each part of the body (as separated in
|
|
org-mode by hlines) is wrapped into <tbody>..</tbody> tags. I
|
|
have also changed the CSS style for <td> fields and the value of
|
|
`org-export-html-table-tag' to get cleaner tables. Basically,
|
|
tables now have horizontal lines only where needed, and no
|
|
vertical lines at all, as generally recommended for tables in
|
|
printed text. I like the new look, but I am not sure if this
|
|
change will find general approval, please throw in your view if
|
|
you like. Thanks to Scott for driving this, and to goud-H for
|
|
pointing me to the row grouping in tables.
|
|
|
|
</li>
|
|
<li>
|
|
In a table with calculation markers in the first column, you can
|
|
now also put "/" into the first column. It indicates that this
|
|
line should not be exported. The foremost application for this
|
|
are lines containing only "<N>" markers for narrowing columns.
|
|
|
|
</li>
|
|
</ul></div>
|
|
</div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.64</h2>
|
|
|
|
|
|
|
|
<div class="outline-3">
|
|
<h3>Overview</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
Email links get better, configurable descriptions
|
|
</li>
|
|
<li>
|
|
When inserting a link, selected text becomes the description
|
|
</li>
|
|
<li>
|
|
Easier access to the list of stored links.
|
|
</li>
|
|
<li>
|
|
Horizontal lines in HTML export.
|
|
</li>
|
|
<li>
|
|
Remember templates and storing of notes improved.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-3">
|
|
<h3>Detailed description of changes</h3>
|
|
|
|
|
|
<ul>
|
|
<li>
|
|
The descriptive part of links to email messages can be configured
|
|
using the variable `org-email-link-description-format'. The new
|
|
default is "Email %c: %.30s" and leads to
|
|
|
|
<p>
|
|
Email from NAME: SUBJECT
|
|
</p>
|
|
<p>
|
|
If you configure the variable `org-from-is-user-regexp'
|
|
correctly, then for email you <b>sent</b> this will actually change to
|
|
</p>
|
|
<p>
|
|
Email to NAME: SUBJECT
|
|
</p>
|
|
<p>
|
|
The subject is limited to 30 characters. If you have become
|
|
attached to the previous default (look twice, the new one is
|
|
better), use "%f on: %s" as your format.
|
|
</p>
|
|
</li>
|
|
<li>
|
|
Selecting text before entering a new link with C-c C-l now really
|
|
works, the selected text becomes the description part of the
|
|
link. Requested by Scott, buggy 4.62 implementation is now fixed.
|
|
|
|
</li>
|
|
<li>
|
|
Stored links are part of the history list for C-c C-l, so to
|
|
reach them, you can use up/down rather than completion. Thanks
|
|
to Raman for this excellent idea.
|
|
|
|
</li>
|
|
<li>
|
|
A line consisting only of "-", and at least 5 of them, is
|
|
exported into HTML as <hr/>, as proposed by Giovanni Ridolfi.
|
|
|
|
</li>
|
|
<li>
|
|
Several changes to org <-> remember integration
|
|
|
|
<ul>
|
|
<li>
|
|
You can use `org-remember' as your default command to start
|
|
remember. It will automatically detect if there is an active
|
|
region and use it as initial content (we will probably make
|
|
remember.el work like this as well).
|
|
Also, when calling `org-remember' in a remember buffer that
|
|
was created with a template, you will again be asked to
|
|
select a template. The buffer is then re-created with the
|
|
new template, but the old context information. This is
|
|
useful if you change your mind about the template to use
|
|
(Leo's idea).
|
|
|
|
</li>
|
|
<li>
|
|
Besides specifying a default <b>target</b> file for a note, you
|
|
can also give a default <b>heading</b> of which the note should
|
|
become a subitem. In many cases this avoids or speeds up
|
|
navigating to the right location. Both file and heading can
|
|
be different for each template. Both are non-binding, you
|
|
can change them while storing the note. However, when you
|
|
exit remember with C-u C-c C-c, these defaults will be used
|
|
without interaction.
|
|
|
|
</li>
|
|
<li>
|
|
Templates can specify interactive fields. During expansion
|
|
of the template, you will be prompted for the information in
|
|
that field. For example %^t will pop up a calendar and ask
|
|
you to select a date. This new feature follows a proposal
|
|
from Leo, who in the mean time has said he does not need it
|
|
anymore. But I liked it, so here it is :-)
|
|
|
|
</li>
|
|
<li>
|
|
Templates can access information specific to the link type
|
|
created, for example the author and subject of an email.
|
|
Syntax is %:fromname, %:fromaddress, %:subject etc, details
|
|
in the manual. Proposed by Peder O. Klingenberg.
|
|
|
|
</li>
|
|
<li>
|
|
I have been considering to move, at some stage, the template
|
|
functionality into remember.el itself - which would of course
|
|
require consent of the remember.el maintainers. I am not
|
|
sure how well this would work though, since some things like
|
|
the interactive time stamps are org.el specific, so treating
|
|
them would require special hooks. Comments?
|
|
|
|
</li>
|
|
</ul></li>
|
|
</ul></div>
|
|
</div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.63</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Bug fixes
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.62</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Many changes to the spreadsheet functions in the table editor.
|
|
For details, please re-read the manual section 3.4.
|
|
<ul>
|
|
<li>
|
|
New Features
|
|
<ul>
|
|
<li>
|
|
It is much easier to assign formulas to individual fields.
|
|
</li>
|
|
<li>
|
|
References to arbitrary fields and ranges.
|
|
</li>
|
|
<li>
|
|
Absolute references are modified in row-editing commands.
|
|
</li>
|
|
<li>
|
|
Formula editor that highlights referenced fields.
|
|
</li>
|
|
</ul></li>
|
|
<li>
|
|
Incompatible changes
|
|
<ul>
|
|
<li>
|
|
Empty fields are excluded in range references, see "E" mode flag.
|
|
</li>
|
|
<li>
|
|
&… ranges no longer supported, use new @… ranges.
|
|
</li>
|
|
<li>
|
|
Variable insertion into Lisp formulas work differently.
|
|
</li>
|
|
</ul></li>
|
|
</ul></li>
|
|
<li>
|
|
Selected text becomes the default description for C-c C-l links.(Scott)
|
|
</li>
|
|
<li>
|
|
The date format in the agenda/timeline views is now customizable.
|
|
See the new option `org-agenda-date-format'. (request by Victor)
|
|
</li>
|
|
<li>
|
|
Link abbreviations no longer need a double colon, single colon is fine.
|
|
</li>
|
|
<li>
|
|
Bug fixes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.61</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Avoiding keybinding clashes with flyspell
|
|
<ul>
|
|
<li>
|
|
Archiving is now also on `C-C C-x C-s' (was just `C-c $')
|
|
</li>
|
|
<li>
|
|
Cycling through agenda files is now also on "C-'" (was just "C-,")
|
|
</li>
|
|
</ul></li>
|
|
<li>
|
|
Colon is considered part of number, to align times in clock tables.
|
|
</li>
|
|
<li>
|
|
Fixed bug for list of stuck projects.
|
|
</li>
|
|
<li>
|
|
Fixed several bugs/problems concerning linking to gnus.
|
|
</li>
|
|
<li>
|
|
Block agendas can contain the list of stuck projects.
|
|
</li>
|
|
<li>
|
|
#+ARCHIVE may now appear several times in the buffer.
|
|
</li>
|
|
<li>
|
|
More bug fixes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.60</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
HTML export: inlining images, clickable images (manual 10.2.4).
|
|
</li>
|
|
<li>
|
|
Incremental search now shows proper context when exiting.
|
|
</li>
|
|
<li>
|
|
Tables calculation and Calc package.
|
|
<ul>
|
|
<li>
|
|
Calc is no longer needed when using only elisp formulas.
|
|
</li>
|
|
<li>
|
|
Proper error messages when calc is needed and not available.
|
|
</li>
|
|
</ul></li>
|
|
<li>
|
|
Tracking TODO state changes with time stamps and notes.
|
|
</li>
|
|
<li>
|
|
Empty entries go full circle.
|
|
</li>
|
|
<li>
|
|
Links in iCalendar export cleaned up.
|
|
</li>
|
|
<li>
|
|
Bug fixes.
|
|
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.59</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Cleanup code, bug fixes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.58</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Full undo support in the agenda buffer.
|
|
</li>
|
|
<li>
|
|
Listing stuck GTD projects (projects without any NEXT ACTIONS).
|
|
Configure `org-stuck-projects' before using it.
|
|
</li>
|
|
<li>
|
|
C-c C-x b shows the current subtree in an indirect buffer, in
|
|
another, dedicated frame.
|
|
</li>
|
|
<li>
|
|
Custom agenda commands take precedence over builtin commands.
|
|
</li>
|
|
<li>
|
|
auto-fill for comments works on the Emacs side, XEmacs not yet.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.57</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Sorting of outline items on same level.
|
|
</li>
|
|
<li>
|
|
Sorting tables automatically selects line range between hlines.
|
|
</li>
|
|
<li>
|
|
Changes in Agenda buffer
|
|
<ul>
|
|
<li>
|
|
`C-c C-o' follows a link in the current line.
|
|
</li>
|
|
<li>
|
|
`C-c $' archives the subtree corresponding to the line.
|
|
</li>
|
|
<li>
|
|
Changing dates with S-left and S-right show new date in agenda,
|
|
but still do not move the entry to the new date.
|
|
</li>
|
|
<li>
|
|
new option `org-agenda-skip-scheduled-if-done'.
|
|
</li>
|
|
</ul></li>
|
|
<li>
|
|
Agenda and sparse tree construction using tag matches can now
|
|
use regular expressions.
|
|
</li>
|
|
<li>
|
|
When prompted for a date/time, entering "+7" indicates a date
|
|
7 days from now - but only this is the only thing you give.
|
|
</li>
|
|
<li>
|
|
Custom time formats also apply to exported html and ascii.
|
|
</li>
|
|
<li>
|
|
Bug fixes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.56</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
`C-k' in agenda kills current line and corresponding subtree in file.
|
|
</li>
|
|
<li>
|
|
XEmacs compatibility issues fixed, in particular tag alignment.
|
|
</li>
|
|
<li>
|
|
M-left/right now in/outdents plain list items, no Shift needed.
|
|
</li>
|
|
<li>
|
|
Bug fixes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.55</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Bug fixes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.54</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Improvements to fast tag selection
|
|
<ul>
|
|
<li>
|
|
show status also in target line.
|
|
</li>
|
|
<li>
|
|
option to auto-exit after first change to tags list (see manual).
|
|
</li>
|
|
</ul></li>
|
|
<li>
|
|
Tags sparse trees now also respect the settings in
|
|
`org-show-hierarchy-above' and `org-show-following-heading'.
|
|
</li>
|
|
<li>
|
|
Bug fixes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.53</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Custom time formats can be overlayed over time stamps.
|
|
</li>
|
|
<li>
|
|
New option `org-agenda-todo-ignore-deadlines'.
|
|
</li>
|
|
<li>
|
|
Work-around for flyspell bug (CVS Emacs has this fixed in flyspell.el).
|
|
</li>
|
|
<li>
|
|
Work-around for session.el problem with circular data structures.
|
|
</li>
|
|
<li>
|
|
Bug fixes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.52</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
TAG matches can also specify conditions on TODO keywords.
|
|
</li>
|
|
<li>
|
|
The fast tag interface allows setting tags that are not in the
|
|
predefined list.
|
|
</li>
|
|
<li>
|
|
Bug fixes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.51</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Link abbreviations (manual section 4.5).
|
|
</li>
|
|
<li>
|
|
More control over how agenda is displayed. See the new variables
|
|
`org-agenda-window-setup', `org-agenda-restore-windows-after-quit'.
|
|
</li>
|
|
<li>
|
|
Bug fixes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.50</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Closing a TODO item can record an additional note.
|
|
See variables `org-log-done' and `org-log-note-headings'.
|
|
</li>
|
|
<li>
|
|
Inserting headlines and bullets can leave an extra blank line.
|
|
See variable `org-blank-before-new-entry'. (Ed Hirgelt patch)
|
|
</li>
|
|
<li>
|
|
<a href="#bracket--links">bracket links</a> in the agenda are active just as in org-mode buffers.
|
|
</li>
|
|
<li>
|
|
C-c C-o on a date range displays the agenda for exactly this range.
|
|
</li>
|
|
<li>
|
|
The default for `org-cycle-include-plain-lists' is back to nil.
|
|
</li>
|
|
<li>
|
|
Calls to `org-occur' can be stacked by using a prefix argument.
|
|
</li>
|
|
<li>
|
|
The options `org-show-hierarchy-above' and `org-show-following-heading'
|
|
now always default to `t', but can be customized differently for
|
|
different types of sparse trees or jump commands.
|
|
</li>
|
|
<li>
|
|
Bug fixes.
|
|
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.49</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Agenda views can be made in batch mode from the command line.
|
|
</li>
|
|
<li>
|
|
`org-store-link' does the right thing in dired-mode.
|
|
</li>
|
|
<li>
|
|
File links can contain environment variables.
|
|
</li>
|
|
<li>
|
|
Full Emacs 21 compatibility has been restored.
|
|
</li>
|
|
<li>
|
|
Bug fixes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.47</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Custom commands may produce an agenda which contains several blocks,
|
|
each block created by a different agenda command.
|
|
</li>
|
|
<li>
|
|
Agenda commands can be restricted to the current file, region, subtree.
|
|
</li>
|
|
<li>
|
|
The timeline command must now be called through the agenda
|
|
dispatcher (C-c a L). `C-c C-r' no longer works.
|
|
</li>
|
|
<li>
|
|
Agenda items can be sorted by tag. The <b>last</b> tag is used for this.
|
|
</li>
|
|
<li>
|
|
The prefix and the sorting strategy for agenda items can depend
|
|
upon the agenda type.
|
|
</li>
|
|
<li>
|
|
The handling of `<a href="mailto:'">mailto:'</a> links can be customized, see the new
|
|
variable `org-link-mailto-program'.
|
|
</li>
|
|
<li>
|
|
`mailto' links can specify a subject after a double colon,
|
|
like <a href="mailto:carsten@orgmode.org::Org-mode is buggy">mailto:carsten@orgmode.org::Org-mode is buggy</a>.
|
|
</li>
|
|
<li>
|
|
In the #+STARTUP line, M-TAB completes valid keywords.
|
|
</li>
|
|
<li>
|
|
In the #+TAGS: line, M-TAB after ":" inserts all currently used tags.
|
|
</li>
|
|
<li>
|
|
Again full Emacs 21 support: Checkboxes and publishing are fixed.
|
|
</li>
|
|
<li>
|
|
More minor bug fixes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.45</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Checkbox lists can show statistics about checked items.
|
|
</li>
|
|
<li>
|
|
C-TAB will cycle the visibility of archived subtrees.
|
|
</li>
|
|
<li>
|
|
Documentation about checkboxes has been moved to chapter 5.
|
|
</li>
|
|
<li>
|
|
Bux fixes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.44</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Clock table can be done for a limited time interval.
|
|
</li>
|
|
<li>
|
|
Obsolete support for the old outline mode has been removed.
|
|
</li>
|
|
<li>
|
|
Bug fixes and code cleaning.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.43</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Bug fixes
|
|
</li>
|
|
<li>
|
|
`s' key in the agenda saves all org-mode buffers.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.41</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Shift-curser keys can modify inactive time stamps (inactive time
|
|
stamps are the ones in […] brackets.
|
|
</li>
|
|
<li>
|
|
Toggle all checkboxes in a region/below a headline.
|
|
</li>
|
|
<li>
|
|
Bug fixes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.40</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Bug fixes.
|
|
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.39</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Special tag ARCHIVE keeps a subtree closed and away from agenda lists.
|
|
</li>
|
|
<li>
|
|
LaTeX code in Org-mode files can be converted to images for HTML.
|
|
</li>
|
|
<li>
|
|
Bug fixes.
|
|
</li>
|
|
<li>
|
|
CDLaTeX-mode features can be used in Org-mode to help inserting
|
|
LaTeX environment and math.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.38</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
noutline.el is now required (important for XEmacs users only).
|
|
</li>
|
|
<li>
|
|
Dynamic blocks.
|
|
</li>
|
|
<li>
|
|
Archiving of all level 1 trees without open TODO items.
|
|
</li>
|
|
<li>
|
|
Clock reports can be inserted into the file in a special section.
|
|
</li>
|
|
<li>
|
|
FAQ removed from the manual, now only on the web.
|
|
</li>
|
|
<li>
|
|
Bug fixes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.37</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Clock-feature for measuring time spent on specific items.
|
|
</li>
|
|
<li>
|
|
Improved emphasizing allows configuration and stacking.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.36</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Improved indentation of ASCII export, when headlines become items.
|
|
</li>
|
|
<li>
|
|
Handling of 12am and 12pm fixed. Times beyond 24:00 can be used
|
|
and will not lead to conflicts.
|
|
</li>
|
|
<li>
|
|
Support for mutually exclusive TAGS with the fast tags interface.
|
|
</li>
|
|
<li>
|
|
Bug fixes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.35</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
HTML export is now valid XHTML.
|
|
</li>
|
|
<li>
|
|
Timeline can also show dates without entries. See new option
|
|
`org-timeline-show-empty-dates'.
|
|
</li>
|
|
<li>
|
|
The bullets created by the ASCII exporter can now be configured.
|
|
See the new option `org-export-ascii-bullets'.
|
|
</li>
|
|
<li>
|
|
New face `org-upcoming-deadline' (was `org-scheduled-previously').
|
|
</li>
|
|
<li>
|
|
New function `org-context' to allow testing for local context.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.34</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Bug fixes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.33</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
New commands to move through plain lists: S-up and S-down.
|
|
</li>
|
|
<li>
|
|
Bug fixes and documentation update.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.32</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Fast (single-key-per-tag) interface for setting TAGS.
|
|
</li>
|
|
<li>
|
|
The list of legal tags can be configured globally and locally.
|
|
</li>
|
|
<li>
|
|
Elisp and Info links (thanks to Todd Neal).
|
|
</li>
|
|
<li>
|
|
`org-export-publishing-directory' can be an alist, with different
|
|
directories for different export types.
|
|
</li>
|
|
<li>
|
|
All context-sensitive commands use `call-interactively' to dispatch.
|
|
</li>
|
|
<li>
|
|
`org-confirm-shell-links' renamed to `org-confirm-shell-link-function'.
|
|
</li>
|
|
<li>
|
|
Bug fixes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.31</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Bug fixes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.30</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Modified installation: Autoloads have been collected in org-install.el.
|
|
</li>
|
|
<li>
|
|
Logging (org-log-done) is now a #+STARTUP option.
|
|
</li>
|
|
<li>
|
|
Checkboxes in plain list items, following up on Frank Ruell's idea.
|
|
</li>
|
|
<li>
|
|
File links inserted with C-c C-l will use relative paths if the linked
|
|
file is in the current directory or a subdirectory of it.
|
|
</li>
|
|
<li>
|
|
New variable `org-link-file-path-type' to specify preference for
|
|
relative and absolute paths.
|
|
</li>
|
|
<li>
|
|
New CSS classes for tags, timestamps, timestamp keywords.
|
|
</li>
|
|
<li>
|
|
Bug and typo fixes.
|
|
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.29</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Inlining images in HTML export now depends on wheather the link
|
|
contains a description or not.
|
|
</li>
|
|
<li>
|
|
TODO items can be scheduled from the global TODO list using C-c C-s.
|
|
</li>
|
|
<li>
|
|
TODO items already scheduled can be made to disappear from the global
|
|
todo list, see `org-agenda-todo-ignore-scheduled'.
|
|
</li>
|
|
<li>
|
|
In Tables, formulas may also be Lisp forms.
|
|
</li>
|
|
<li>
|
|
Exporting the visible part of an outline with `C-c C-x v' works now
|
|
for all available exporters.
|
|
</li>
|
|
<li>
|
|
Bug fixes, lots of them :-(
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.28</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Bug fixes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.27</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
HTML exporter generalized to receive external options.
|
|
As part of the process, author, email and date have been moved to the
|
|
end of the HTML file.
|
|
</li>
|
|
<li>
|
|
Support for customizable file search in file links.
|
|
</li>
|
|
<li>
|
|
BibTeX database links as first application of the above.
|
|
</li>
|
|
<li>
|
|
New option `org-agenda-todo-list-sublevels' to turn off listing TODO
|
|
entries that are sublevels of another TODO entry.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.26</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Bug fixes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.25</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Revision of the font-lock faces section, with better tty support.
|
|
</li>
|
|
<li>
|
|
TODO keywords in Agenda buffer are fontified.
|
|
</li>
|
|
<li>
|
|
Export converts links between .org files to links between .html files.
|
|
</li>
|
|
<li>
|
|
Better support for bold/italic/underline emphasis.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.24</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Bug fixes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.23</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Bug fixes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.22</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Bug fixes.
|
|
</li>
|
|
<li>
|
|
In agenda buffer, mouse-1 no longer follows link.
|
|
See `org-agenda-mouse-1-follows-link' and `org-mouse-1-follows-link'.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.20</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Links use now the <a href="#link">description</a> format by default.
|
|
When inserting links, the user is prompted for a description.
|
|
</li>
|
|
<li>
|
|
If a link has a description, only the description is displayed
|
|
the link part is hidden. Use C-c C-l to edit the link part.
|
|
</li>
|
|
<li>
|
|
TAGS are now bold, but in the same color as the headline.
|
|
</li>
|
|
<li>
|
|
The width of a table column can be limited by using a field "<N>".
|
|
</li>
|
|
<li>
|
|
New structure for the customization tree.
|
|
</li>
|
|
<li>
|
|
Bug fixes.
|
|
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.13</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
The list of agenda files can be maintainted in an external file.
|
|
</li>
|
|
<li>
|
|
Bug fixes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 4.12</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Templates for remember buffer. Note that the remember setup changes.
|
|
To set up templates, see `org-remember-templates'.
|
|
</li>
|
|
<li>
|
|
The time in new time stamps can be rounded, see new option
|
|
`org-time-stamp-rounding-minutes'.
|
|
</li>
|
|
<li>
|
|
Bug fixes (there are <b>always</b> more bugs).
|
|
|
|
</li>
|
|
</ul>
|
|
<p>[…]
|
|
</p>
|
|
<p>
|
|
Version 4.00
|
|
</p><ul>
|
|
<li>
|
|
Headlines can contain TAGS, and Org-mode can produced a list
|
|
of matching headlines based on a TAG search expression.
|
|
</li>
|
|
<li>
|
|
`org-agenda' has now become a dispatcher that will produce the agenda
|
|
and other views on org-mode data with an additional keypress.
|
|
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 3.24</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Switching and item to DONE records a time stamp when the variable
|
|
`org-log-done' is turned on. Default is off.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 3.23</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
M-RET makes new items as well as new headings.
|
|
</li>
|
|
<li>
|
|
Various small bug fixes
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 3.22</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
CamelCase words link to other locations in the same file.
|
|
</li>
|
|
<li>
|
|
File links accept search options, to link to specific locations.
|
|
</li>
|
|
<li>
|
|
Plain list items can be folded with `org-cycle'. See new option
|
|
`org-cycle-include-plain-lists'.
|
|
</li>
|
|
<li>
|
|
Sparse trees for specific TODO keywords through numeric prefix
|
|
argument to `C-c C-v'.
|
|
</li>
|
|
<li>
|
|
Global TODO list, also for specific keywords.
|
|
</li>
|
|
<li>
|
|
Matches in sparse trees are highlighted (highlights disappear with
|
|
next buffer change due to editing).
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 3.21</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Improved CSS support for the HTML export. Thanks to Christian Egli.
|
|
</li>
|
|
<li>
|
|
Editing support for hand-formatted lists
|
|
<ul>
|
|
<li>
|
|
M-S-cursor keys handle plain list items
|
|
</li>
|
|
<li>
|
|
C-c C-c renumbers ordered plain lists
|
|
|
|
</li>
|
|
</ul></li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 3.20</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
There is finally an option to make TAB jump over horizontal lines
|
|
in tables instead of creating a new line before that line.
|
|
The option is `org-table-tab-jumps-over-hlines', default nil.
|
|
</li>
|
|
<li>
|
|
New command for sorting tables, on `C-c ^'.
|
|
</li>
|
|
<li>
|
|
Changes to the HTML exporter
|
|
<ul>
|
|
<li>
|
|
hand-formatted lists are exported correctly, similar to
|
|
markdown lists. Nested lists are possible. See the docstring
|
|
of the variable `org-export-plain-list-max-depth'.
|
|
</li>
|
|
<li>
|
|
cleaned up to produce valid HTML 4.0 (transitional).
|
|
</li>
|
|
<li>
|
|
support for cascading style sheets.
|
|
</li>
|
|
</ul></li>
|
|
<li>
|
|
New command to cycle through all agenda files, on C-,
|
|
</li>
|
|
<li>
|
|
C-c [ can now also be used to change the sequence of agenda files.
|
|
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 3.19</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Bug fixes
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 3.18</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Export of calendar information in the standard iCalendar format.
|
|
</li>
|
|
<li>
|
|
Some bug fixes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 3.17</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
HTML export specifies character set depending on coding-system.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 3.16</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
In tables, directly after the field motion commands like TAB and RET,
|
|
typing a character will blank the field. Can be turned off with
|
|
variable `org-table-auto-blank-field'.
|
|
</li>
|
|
<li>
|
|
Inactive timestamps with `C-c !'. These do not trigger the agenda
|
|
and are not linked to the calendar.
|
|
</li>
|
|
<li>
|
|
Additional key bindings to allow Org-mode to function on a tty emacs.
|
|
</li>
|
|
<li>
|
|
`C-c C-h' prefix key replaced by `C-c C-x', and `C-c C-x C-h' replaced
|
|
by `C-c C-x b' (b=Browser). This was necessary to recover the
|
|
standard meaning of C-h after a prefix key (show prefix bindings).
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 3.15</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
QUOTE keyword at the beginning of an entry causes fixed-width export
|
|
of unmodified entry text. `C-c :' toggles this keyword.
|
|
</li>
|
|
<li>
|
|
New face `org-special-keyword' which is used for COMMENT, QUOTE,
|
|
DEADLINE and SCHEDULED, and priority cookies. Default is only a weak
|
|
color, to reduce the amount of aggressive color in the buffer.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 3.14</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Formulas for individual fields in table.
|
|
</li>
|
|
<li>
|
|
Automatic recalculation in calculating tables.
|
|
</li>
|
|
<li>
|
|
Named fields and columns in tables.
|
|
</li>
|
|
<li>
|
|
Fixed bug with calling `org-archive' several times in a row.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 3.13</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Efficiency improvements: Fewer table re-alignments needed.
|
|
</li>
|
|
<li>
|
|
New special lines in tables, for defining names for individual cells.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 3.12</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Tables can store formulas (one per column) and compute fields.
|
|
Not quite like a full spreadsheet, but very powerful.
|
|
</li>
|
|
<li>
|
|
table.el keybinding is now `C-c ~'.
|
|
</li>
|
|
<li>
|
|
Numeric argument to org-cycle does `show-subtree' above on level ARG.
|
|
</li>
|
|
<li>
|
|
Small changes to keys in agenda buffer. Affected keys:
|
|
[w] weekly view; [d] daily view; [D] toggle diary inclusion.
|
|
</li>
|
|
<li>
|
|
Bug fixes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 3.11</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Links inserted with C-c C-l are now by default enclosed in angle
|
|
brackets. See the new variable `org-link-format'.
|
|
</li>
|
|
<li>
|
|
">" terminates a link, this is a way to have several links in a line.
|
|
Both "<" and ">" are no longer allowed as characters in a link.
|
|
</li>
|
|
<li>
|
|
Archiving of finished tasks.
|
|
</li>
|
|
<li>
|
|
C-<up>/<down> bindings removed, to allow access to paragraph commands.
|
|
</li>
|
|
<li>
|
|
Compatibility with CUA-mode (see variable `org-CUA-compatible').
|
|
</li>
|
|
<li>
|
|
Compatibility problems with viper-mode fixed.
|
|
</li>
|
|
<li>
|
|
Improved html export of tables.
|
|
</li>
|
|
<li>
|
|
Various clean-up changes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 3.10</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Using `define-derived-mode' to derive `org-mode' from `outline-mode'.
|
|
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 3.09</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Time-of-day specifications in agenda are extracted and placed
|
|
into the prefix. Timed entries can be placed into a time grid for
|
|
day.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 3.08</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
"|" no longer allowed as part of a link, to allow links in tables.
|
|
</li>
|
|
<li>
|
|
The prefix of items in the agenda buffer can be configured.
|
|
</li>
|
|
<li>
|
|
Cleanup.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 3.07</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Some folding inconsistencies removed.
|
|
</li>
|
|
<li>
|
|
BBDB links to company-only entries.
|
|
</li>
|
|
<li>
|
|
Bug fixes and global cleanup.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 3.06</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
M-S-RET inserts a new TODO heading.
|
|
</li>
|
|
<li>
|
|
New startup option `content'.
|
|
</li>
|
|
<li>
|
|
Better visual response when TODO items in agenda change status.
|
|
</li>
|
|
<li>
|
|
Window positioning after visibility state changes optimized and made
|
|
configurable. See `org-cycle-hook' and `org-occur-hook'.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 3.05</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Agenda entries from the diary are linked to the diary file, so
|
|
adding and editing diary entries can be done directly from the agenda.
|
|
</li>
|
|
<li>
|
|
Many calendar/diary commands available directly from agenda.
|
|
</li>
|
|
<li>
|
|
Field copying in tables with S-RET does increment.
|
|
</li>
|
|
<li>
|
|
C-c C-x C-v extracts the visible part of the buffer for printing.
|
|
</li>
|
|
<li>
|
|
Moving subtrees up and down preserves the whitespace at the tree end.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 3.04</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Table editor optimized to need fewer realignments, and to keep
|
|
table shape when typing in fields.
|
|
</li>
|
|
<li>
|
|
A new minor mode, orgtbl-mode, introduces the Org-mode table editor
|
|
into arbitrary major modes.
|
|
</li>
|
|
<li>
|
|
Fixed bug with realignment in XEmacs.
|
|
</li>
|
|
<li>
|
|
Startup options can be set with special #+STARTUP line.
|
|
</li>
|
|
<li>
|
|
Heading following a match in org-occur can be suppressed.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 3.03</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Copyright transfer to the FSF.
|
|
</li>
|
|
<li>
|
|
Effect of C-u and C-u C-u in org-timeline swapped.
|
|
</li>
|
|
<li>
|
|
Timeline now always contains today, and `.' jumps to it.
|
|
</li>
|
|
<li>
|
|
Table editor:
|
|
<ul>
|
|
<li>
|
|
cut and paste of rectangular regions in tables
|
|
</li>
|
|
<li>
|
|
command to convert org-mode table to table.el table and back
|
|
</li>
|
|
<li>
|
|
command to treat several cells like a paragraph and fill it
|
|
</li>
|
|
<li>
|
|
command to convert a buffer region to a table
|
|
</li>
|
|
<li>
|
|
import/export tables as tab-separated files (exchange with Excel)
|
|
</li>
|
|
</ul></li>
|
|
<li>
|
|
Agenda:
|
|
<ul>
|
|
<li>
|
|
Sorting mechanism for agenda items rewritten from scratch.
|
|
</li>
|
|
<li>
|
|
Sorting fully configurable.
|
|
</li>
|
|
<li>
|
|
Entries specifying a time are sorted together.
|
|
</li>
|
|
</ul></li>
|
|
<li>
|
|
Completion also covers option keywords after `#-'.
|
|
</li>
|
|
<li>
|
|
Bug fixes.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 3.01</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
New reference card, thanks to Philip Rooke for creating it.
|
|
</li>
|
|
<li>
|
|
Single file agenda renamed to "Timeline". It no longer shows
|
|
warnings about upcoming deadlines/overdue scheduled items.
|
|
That functionality is now limited to the (multifile) agenda.
|
|
</li>
|
|
<li>
|
|
When reading a date, the calendar can be manipulated with keys.
|
|
</li>
|
|
<li>
|
|
Link support for RMAIL and Wanderlust (from planner.el, untested).
|
|
</li>
|
|
<li>
|
|
Minor bug fixes and documentation improvements.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 3.00</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Multifile Agenda shows current entries from many different files.
|
|
</li>
|
|
<li>
|
|
TeXInfo documentation (thanks to Christian Egli for the conversion).
|
|
</li>
|
|
<li>
|
|
Additional applications for TODO keywords, see documentation.
|
|
Different files may have different TODO keywords etc.
|
|
</li>
|
|
<li>
|
|
Priorities for TODO items.
|
|
</li>
|
|
<li>
|
|
The browser mode used by `org-remember-handler' is improved.
|
|
</li>
|
|
<li>
|
|
Images get inlined in HTML export (thanks to Carsten Wimmer).
|
|
</li>
|
|
<li>
|
|
File links can contain line numbers, like <a href="/usr/etc/config:255">file:/usr/etc/config:255</a>
|
|
</li>
|
|
<li>
|
|
Minor bug fixes.
|
|
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 2.10</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
TODO entries can have additional states besides TODO and DONE.
|
|
See new variable `org-todo-keywords'.
|
|
</li>
|
|
<li>
|
|
TODO keywords can be interpreted as categories. See variable
|
|
`org-todo-interpretation'.
|
|
</li>
|
|
<li>
|
|
M-TAB completion on TODO keywords, TeX symbols, and normal words.
|
|
</li>
|
|
<li>
|
|
All keywords (like TODO, DEADLINE etc) are configurable.
|
|
</li>
|
|
<li>
|
|
Cursor positioning optimized after pro/demotion and TODO cycling.
|
|
</li>
|
|
<li>
|
|
Emphasizing in HTML works now for <b>bold</b>, <i>italic</i> and <u>underline</u>.
|
|
</li>
|
|
<li>
|
|
New commands to kill, copy and yank entire subtrees. Yanking
|
|
modifies the level of the tree before insertion.
|
|
</li>
|
|
<li>
|
|
New command `org-goto' (C-c C-j) to quickly move to other locations
|
|
in the buffer without affecting outline visibility.
|
|
</li>
|
|
<li>
|
|
Hooks for John Wiegley's remember.el.
|
|
</li>
|
|
<li>
|
|
`org-read-date' pops up calendar for date selection with the mouse.
|
|
See variable `org-popup-calendar-for-date-prompt'.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 2.6</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
TODO items can be SCHEDULED to a certain date.
|
|
</li>
|
|
<li>
|
|
Expired DEADLINEs are ignored if in an entry marked DONE.
|
|
</li>
|
|
<li>
|
|
From the diary or time-sorted view (C-c C-r), C-c C-t can be used to
|
|
change the TODO state of an item remotely.
|
|
</li>
|
|
<li>
|
|
Horizontal computations in table editor. See `org-table-eval-formula'.
|
|
</li>
|
|
<li>
|
|
Fixed bug with summing tables (command `org-table-sum', `C-c +').
|
|
</li>
|
|
<li>
|
|
Calendar window follows the timestamp when a timestamp is changed.
|
|
New variable `org-calendar-follow-timestamp-change'.
|
|
</li>
|
|
<li>
|
|
Time-sorted view (`org-diary-view', C-c C-r) now uses the prefix
|
|
argument to force inclusion of unscheduled TODO items.
|
|
</li>
|
|
<li>
|
|
New variable `org-confirm-shell-links' to turn of safety query.
|
|
</li>
|
|
<li>
|
|
New variable `org-open-non-existing-files'.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 2.4</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
A time-sorted view on all time stamps can be created with C-c C-r.
|
|
</li>
|
|
<li>
|
|
Timestamps and Deadlines can be shown in the Emacs diary.
|
|
</li>
|
|
<li>
|
|
Date ranges introduced.
|
|
</li>
|
|
<li>
|
|
Time-string formats are no longer configurable.
|
|
</li>
|
|
<li>
|
|
Vertical lines in tables can be made invisible with `C-c |'.
|
|
</li>
|
|
<li>
|
|
New "link" type to execute shell commands, like "<i><shell:ls></i> *.org"
|
|
</li>
|
|
<li>
|
|
Upon export, "myfile.org" becomes "myfile.html" or "myfile.txt",
|
|
instead of "myfile.org.html" or "myfile.org.txt".
|
|
</li>
|
|
<li>
|
|
When the cursor is in the white space at the beginning of a line,
|
|
TAB removes the whitespace before indenting again.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 2.0</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Windows (NT/2000) support.
|
|
</li>
|
|
<li>
|
|
Works with both Emacs and XEmacs.
|
|
</li>
|
|
<li>
|
|
Fully automatic table editor.
|
|
</li>
|
|
<li>
|
|
New link types into Gnus, VM and BBDB.
|
|
</li>
|
|
<li>
|
|
Other link system changes
|
|
<ul>
|
|
<li>
|
|
Time stamps are treated as links to the calendar.
|
|
</li>
|
|
<li>
|
|
Easy creation of links with global command `org-store-link'.
|
|
</li>
|
|
<li>
|
|
Insertion of links with `C-c C-l' works differently now.
|
|
</li>
|
|
<li>
|
|
Space characters allowed as part of a link.
|
|
</li>
|
|
<li>
|
|
Options in `org-file-apps' extended. The command may now be
|
|
symbol 'emacs', or a lisp form.
|
|
</li>
|
|
</ul></li>
|
|
</ul>
|
|
<p>Please re-read the manual section about links.
|
|
</p><ul>
|
|
<li>
|
|
Timestamp changes
|
|
<ul>
|
|
<li>
|
|
`org-deadline' now prompts for a date.
|
|
</li>
|
|
<li>
|
|
A line can now contain several timestamps. Updating of a
|
|
timestamp only happens if the cursor is at the timestamp.
|
|
</li>
|
|
<li>
|
|
Changed the time-stamp-format to ISO, to make sure it will
|
|
always work (non-English month names had caused problems
|
|
with `parse-time-string'.). Changing the time stamp format
|
|
is not recommended.
|
|
</li>
|
|
</ul></li>
|
|
<li>
|
|
Picture mode enhancements have been removed from org.el
|
|
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 1.4</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
Some option name changes, not backward compatible.
|
|
</li>
|
|
<li>
|
|
ASCII exporter upgrade: Table of contents.
|
|
</li>
|
|
<li>
|
|
HTML exporter upgrade: fixed-width regions, better
|
|
sub/superscripts, many TeX symbols supported.
|
|
</li>
|
|
<li>
|
|
Calendar support.
|
|
|
|
</li>
|
|
</ul></div>
|
|
|
|
<div class="outline-2">
|
|
<h2>Version 1.3</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
HTML exporter upgrade, in particular table of contents
|
|
|
|
|
|
|
|
</li>
|
|
</ul>
|
|
</div>
|
|
<div id="postamble"><p class="author"> Author: Carsten Dominik
|
|
<a href="mailto:carsten at orgmode dot org"><carsten at orgmode dot org></a>
|
|
</p>
|
|
<p class="date"> Date: 2008/01/25 14:14:58</p>
|
|
</div></body>
|
|
</html>
|