Release 5.22a.
This commit is contained in:
parent
a011ae4ecb
commit
9bca3981f7
2
Makefile
2
Makefile
|
@ -244,5 +244,5 @@ push:
|
|||
git-push git+ssh://repo.or.cz/srv/git/org-mode.git master
|
||||
|
||||
pushtag:
|
||||
git-tag -m "adding tag" -a $(TAG)
|
||||
git-tag -m "Adding tag" -a $(TAG)
|
||||
git-push git+ssh://repo.or.cz/srv/git/org-mode.git $(TAG)
|
|
@ -2,18 +2,548 @@
|
|||
=====================================
|
||||
|
||||
Author: Carsten Dominik <carsten at orgmode dot org>
|
||||
Date: 2007/11/13 12:21:31
|
||||
Date: 2008/02/19 09:16:04
|
||||
|
||||
|
||||
Version 5.14
|
||||
Version 5.22
|
||||
~~~~~~~~~~~~
|
||||
|
||||
Incompatible changes
|
||||
====================
|
||||
|
||||
- If you have customize the variable `org-emphasis-alist', you
|
||||
need to do it again by first canceling your customization and
|
||||
then adding it again.
|
||||
- The variable `org-log-done' is now less complex.
|
||||
- The in-buffer settings for logging have changed. Some
|
||||
options no longer exists, some new ones have been added.
|
||||
|
||||
Details
|
||||
=======
|
||||
|
||||
Changes to logging progress
|
||||
---------------------------
|
||||
|
||||
There is now more control over which state changes are being
|
||||
logged in what way. Please read carefully the corresponding
|
||||
sections in the manual. Basically:
|
||||
|
||||
- The variable `org-log-done' has been simplified, it no
|
||||
longer influences logging state changes and clocking out.
|
||||
- There is a new variable for triggering note-taking when
|
||||
clocking out an item: `org-log-note-clock-out'.
|
||||
- Logging of state changes now has to be configured on a
|
||||
pre-keyword basis, either in `org-todo-keywords' or in the
|
||||
#+TODO in-buffer setting.
|
||||
- These per-keyword settings allow more control. For example
|
||||
|
||||
WAIT(w@) Record a note when entering this state.
|
||||
WAIT(w!) Record a timestamp when entering this state.
|
||||
WAIT(w@/!) Recore a note when entering and timestamp
|
||||
when leaving this state. This is great for
|
||||
getting a record when switching *back* from
|
||||
WAIT to TODO.
|
||||
WAIT(/!) Record a timestamp when leaving this state.
|
||||
Here we not even define a fast access
|
||||
character, but just the logging stuff.
|
||||
|
||||
This was triggered by requests from Wanrong Lin and Bernt Hansen.
|
||||
|
||||
Other
|
||||
-----
|
||||
|
||||
- M-RET no longer brakes a line in the middle, it will make a
|
||||
new line after the current or (if cursor is at the beginning
|
||||
of the line) before the current line.
|
||||
|
||||
- RET, when executed in a headline after the main text and
|
||||
before the tags will leave the tags in the current line and
|
||||
create a new line below the current one.
|
||||
|
||||
Version 5.21
|
||||
~~~~~~~~~~~~
|
||||
|
||||
Bug fixes, in particular the long-hunted bug about wrong window
|
||||
positions after pressing SPACE in the agenda. Hopefully this
|
||||
is really fixed.
|
||||
|
||||
Version 5.20
|
||||
~~~~~~~~~~~~
|
||||
|
||||
Overview
|
||||
========
|
||||
|
||||
Remember/Refile/Goto
|
||||
--------------------
|
||||
|
||||
- The use of prefix arguments for the commands `org-remember'
|
||||
and `org-refile' has been normalized.
|
||||
|
||||
- The clock can now safely be used in a remember buffer.
|
||||
|
||||
- The variable `org-remember-use-refile-when-interactive'
|
||||
introduced only in 5.19 is already obsolete. Please use
|
||||
`org-remember-interactive-interface' instead.
|
||||
|
||||
- It is no longer necessary to update the refiling targets.
|
||||
|
||||
- Automatic isearch in `org-goto'.
|
||||
|
||||
- Outline-path-completion as alternative org-goto interface.
|
||||
|
||||
Misc
|
||||
----
|
||||
|
||||
- Checkboxes now work hierarchically.
|
||||
|
||||
- `C-k' can now behave specially in headlines.
|
||||
|
||||
- Repeater for tasks in plain timestamps.
|
||||
|
||||
- All clock intervals of an item show in agenda/timeline.
|
||||
|
||||
- New parameter `:step' for clocktable, to get daily reports.
|
||||
|
||||
- Never loose a repeaded scheduled item from the agenda.
|
||||
|
||||
- Archiving a subtree now stores the outline path in a property.
|
||||
|
||||
- Links to messages in Apple Mail.
|
||||
|
||||
- Bug fixes.
|
||||
|
||||
Incompatible Changes
|
||||
====================
|
||||
|
||||
- The variable `org-remember-use-refile-when-interactive'
|
||||
introduced only in 5.19 is already obsolete. Please use
|
||||
`org-remember-interactive-interface' instead.
|
||||
|
||||
Details
|
||||
=======
|
||||
|
||||
Remember/Refile/Goto
|
||||
--------------------
|
||||
|
||||
- The use of prefix arguments for the commands `org-remember'
|
||||
and `org-refile' has been normalized:
|
||||
|
||||
+ when called without prefix argument, the command does its
|
||||
normal job, starting a remember note or refiling a tree.
|
||||
|
||||
+ when called with a single C-u prefix, these commands can be
|
||||
used to select a target location and to jump there. In
|
||||
the case of `org-remember', you will be prompted for a
|
||||
template and then Emacs jumps to the default target
|
||||
location or this template. In the case of `org-refile',
|
||||
you select a location from the refile target list and jump
|
||||
there.
|
||||
|
||||
+ when called with two prefixes (`C-u C-u'), the command
|
||||
jumps to the location last used for storing a note or a
|
||||
moved tree.
|
||||
|
||||
- When the clock is running inside an remember buffer, storing
|
||||
the remember buffer with `C-c C-c' will automatically clock
|
||||
out. This was inspired by a request by Rainer Stengle.
|
||||
|
||||
- The variable `org-remember-use-refile-when-interactive'
|
||||
introduced only in 5.19 is already 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 in an interactive way.
|
||||
Possible values are:
|
||||
|
||||
+ `outline': Use an outline of the document to select a
|
||||
location.
|
||||
+ `outline-path-completion': Use completion of an outline
|
||||
path to select a location.
|
||||
+ `refile': Offer the `org-refile-targets' as possible
|
||||
targets.
|
||||
|
||||
- It is no longer necessary to update the refiling targets -
|
||||
they are always current.
|
||||
|
||||
- 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 so long to put 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'.
|
||||
|
||||
- Outline-path-completion is now available as an alternative
|
||||
interface in the command `org-goto'. Please select the
|
||||
default interface you'd like to use with the new variable
|
||||
`org-goto-interface'. You can then select the alternative
|
||||
interface with a prefix argument to `C-c C-j' (org-goto). I
|
||||
am considering to make outline-path-completion the default
|
||||
interface. Comments?
|
||||
|
||||
|
||||
Misc
|
||||
----
|
||||
|
||||
- Checkboxes now work hierarchically. When a plain-list item
|
||||
with a checkbox has children with checkboxes, the status of
|
||||
the item's checkbox is calculated from the children, each
|
||||
time a checkbox is toggled with C-c C-c. Thanks to Miguel
|
||||
A. Figueroa-Villanueva for a patch to this effect.
|
||||
|
||||
- There is a new variable `org-special-ctrl-k'. When set,
|
||||
`C-k' will behave specially in headlines:
|
||||
|
||||
+ When the cursor is at the beginning of a headline, kill
|
||||
the entire line and possible the folded subtree below the
|
||||
line.
|
||||
+ When in the middle of the headline text, kill the
|
||||
headline up to the tags.
|
||||
+ When after the headline text, kill the tags.
|
||||
|
||||
This is following a proposal by Piotr Zielinski.
|
||||
|
||||
- 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.
|
||||
|
||||
- If an entry is clocked multiple times, it will now show up
|
||||
several times in the agenda and timeline buffers, when
|
||||
log-mode is on. This was a proposal by Jurgen Defurne.
|
||||
|
||||
- The clock table accepts a new parameter `:step'. 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 [blog].
|
||||
|
||||
- A time-stamp with a repeater now no longer refers to the
|
||||
date *closest* 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 scheduled
|
||||
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.
|
||||
|
||||
- Archiving a subtree now creates an additional property,
|
||||
`ARCHIVE_OLPATH'. This property contains the "path" in the
|
||||
outline tree to the archived entry, as it was in the
|
||||
original file. For example, archiving `Fix the door' in the
|
||||
following hierarchy
|
||||
|
||||
* Tasks
|
||||
** HOME
|
||||
*** Garage
|
||||
**** Fix the door
|
||||
|
||||
will file is with the following property
|
||||
|
||||
:ARCHIVE_PATH: Task/HOME/Garage
|
||||
|
||||
Note that you can configure (i.e. limit) the information
|
||||
that gets stored upon archiving with the variable
|
||||
`org-archive-save-context-info'.
|
||||
|
||||
- New file `org-mac-message.el' by John Wiegley to create
|
||||
links for messages in Apple Mail, and to follow these
|
||||
links.
|
||||
|
||||
- Bug fixes.
|
||||
|
||||
Version 5.19
|
||||
~~~~~~~~~~~~
|
||||
|
||||
Overview
|
||||
========
|
||||
|
||||
- Column view can list the clocked times of a subtree.
|
||||
|
||||
- Storing remember notes can use the `org-refile' interface.
|
||||
|
||||
- Storing remember notes no longer produced empty lines.
|
||||
|
||||
- Moving subtrees now folds all siblings of the subtree.
|
||||
|
||||
- New variable `org-agenda-todo-keyword-format'.
|
||||
|
||||
- Hack to allow brackets in link descriptions.
|
||||
|
||||
- Clocking into an entry can enforce a specific TODO state.
|
||||
|
||||
- EXPORT_FILE_NAME may be an absolute file name with "~".
|
||||
|
||||
- Bug fixes, lots of them.
|
||||
|
||||
Details
|
||||
=======
|
||||
|
||||
- A new special column definition lists the sum of all CLOCK
|
||||
entries in a subtree. For example
|
||||
|
||||
#+COLUMNS: %20ITEM %10Time_Estimate{:} %CLOCKSUM
|
||||
|
||||
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.
|
||||
|
||||
- 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 `*Remember*' 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'.
|
||||
|
||||
- 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?
|
||||
|
||||
- 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.
|
||||
|
||||
- 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.
|
||||
|
||||
- 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.
|
||||
|
||||
- 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.
|
||||
|
||||
- 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.
|
||||
|
||||
- Bug fixes, lots of them.
|
||||
|
||||
Version 5.18
|
||||
~~~~~~~~~~~~
|
||||
|
||||
Minor fixes.
|
||||
|
||||
Version 5.17
|
||||
~~~~~~~~~~~~
|
||||
|
||||
Details
|
||||
=======
|
||||
|
||||
Whitespace
|
||||
----------
|
||||
|
||||
- When cutting, pasting, or moving subtrees and items, the
|
||||
empty lines *before* 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 *above* the first child to be moved along with it is
|
||||
limited by the number of empty lines *below* 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.
|
||||
|
||||
- Plain lists items work the same.
|
||||
|
||||
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 *before* an entry
|
||||
that really count.
|
||||
|
||||
This change was non-trivial, please give it a good test and
|
||||
let me know about any problems.
|
||||
|
||||
Remember
|
||||
--------
|
||||
|
||||
- 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.
|
||||
|
||||
- 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:
|
||||
|
||||
%^{Author|Roald Dahl|Thomas Mann|Larry Niven}
|
||||
|
||||
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.
|
||||
|
||||
- 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.
|
||||
|
||||
Refile
|
||||
------
|
||||
|
||||
- `org-refile-targets' has a new parameter to specify a
|
||||
maximum level for target selection. Thanks to Wanrong Lin
|
||||
for this proposal.
|
||||
|
||||
- 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.
|
||||
|
||||
Version 5.16
|
||||
~~~~~~~~~~~~
|
||||
|
||||
Details
|
||||
=======
|
||||
|
||||
Restriction lock on agenda scope
|
||||
--------------------------------
|
||||
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
Thanks to Rick Moynihan for triggering this development.
|
||||
|
||||
Imenu and Speedbar support
|
||||
--------------------------
|
||||
|
||||
- Org-mode now supports Imenu. For example, with the setting
|
||||
|
||||
(add-hook 'org-mode-hook
|
||||
(lambda () 'imenu-add-to-menubar "Imenu"))
|
||||
|
||||
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'.
|
||||
|
||||
- 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.
|
||||
|
||||
- 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.
|
||||
|
||||
Version 5.15
|
||||
~~~~~~~~~~~~
|
||||
|
||||
Details
|
||||
=======
|
||||
|
||||
- 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.
|
||||
|
||||
- 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.
|
||||
|
||||
- Bug fixes.
|
||||
|
||||
Version 5.14
|
||||
~~~~~~~~~~~~
|
||||
|
||||
Overview
|
||||
========
|
||||
|
||||
+ Remember and related stuff
|
||||
- New command `org-refile' to quickly move a note.
|
||||
- Easy way to jump to the target location of remember template.
|
||||
- New %-escapes in remember templates: %c %(...) and %[...]
|
||||
- `org-remember-insinuate' simplifies remember setup
|
||||
|
||||
+ Emphasis and Font-lock stuff
|
||||
- Stacked emphasis is no longer allowed.
|
||||
- You may finally emphasize a single character like `*a*'.
|
||||
- Font-lock now can hide the emphasis markers
|
||||
- Text in the "=" emphasis is exported verbatim
|
||||
- There is a new emphasis marker "~" for verbatim text
|
||||
- Constructs treated specially by the exporters can be highlighted
|
||||
|
||||
+ Properties and Column view
|
||||
- More control over which properties use inheritance
|
||||
- CATEGORY="work" can now be used in a tags/property search
|
||||
- the {+} summary type can specify a printf-style output format
|
||||
- New currency summary type {$}
|
||||
|
||||
+ The date/time prompt
|
||||
- While entering data, watch live the current interpretation.
|
||||
- The date prompt now prefers to select the future
|
||||
- Easier modification of time in an existing time stamp.
|
||||
|
||||
+ Export
|
||||
- You can now export some special strings in HTML, like "..."
|
||||
- #+EMAIL: may contain several email addresses
|
||||
|
||||
+ Agenda
|
||||
- In the agenda, a few keys have changed: `g', `G', and `e'.
|
||||
|
||||
+ Miscellaneous
|
||||
- Class-dependent sectioning structures in LaTeX export.
|
||||
- Radio-lists modeled after the radio tables.
|
||||
- The default for `org-ellipsis' is back to nil
|
||||
- Support for pabbrev-mode
|
||||
- New variable `org-show-entry-below'.
|
||||
|
||||
Incompatible changes
|
||||
====================
|
||||
|
||||
- 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.
|
||||
|
||||
- I know that some people have defined their own private helper
|
||||
functions to select a specific remember template, without being
|
||||
|
@ -23,13 +553,16 @@ Incompatible changes
|
|||
(interactive)
|
||||
(org-remember ?n))
|
||||
|
||||
You need to modify this. The character selectiong the template
|
||||
must now be the second argument to `org-remember':
|
||||
You need to modify this. The character selecting the template
|
||||
must now be the /second/ argument to `org-remember':
|
||||
|
||||
(defun my-remember-template-n ()
|
||||
(interactive)
|
||||
(org-remember nil ?n))
|
||||
|
||||
- `C-c C-w' now refiles an entry. To get a sparse tree of
|
||||
deadlines, use `C-c / d' instead.
|
||||
|
||||
Details
|
||||
=======
|
||||
|
||||
|
@ -58,7 +591,8 @@ Remember and related stuff
|
|||
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 prefix argument.
|
||||
it, call the command `C-c C-w' with a double prefix
|
||||
argument.
|
||||
|
||||
This is based on an idea and example implementation by Max
|
||||
Mikhanosha. Many thanks Max.
|
||||
|
@ -76,6 +610,7 @@ Remember and related stuff
|
|||
|
||||
%c insert the current clipboard, like C-y would do
|
||||
%(..) evaluate Lisp expression and insert the result
|
||||
%[..] include file
|
||||
|
||||
Thanks to Adam Spiers and Tim O'Callaghan.
|
||||
|
||||
|
@ -93,19 +628,21 @@ Remember and related stuff
|
|||
provide a default for templates without a file, and
|
||||
`org-directory' to show where to find other org files.
|
||||
|
||||
Emphasis
|
||||
--------
|
||||
Emphasis and Font-lock stuff
|
||||
----------------------------
|
||||
|
||||
- Stacked emphasis like ~*/bold italic/*~ is no longer allowed.
|
||||
- Stacked emphasis like `*/bold italic/*' is no longer allowed.
|
||||
|
||||
- Font-lock now hides the emphasis markers - this makes for a more
|
||||
readable text, and since we are all used to the hiding done by
|
||||
links, I guess this is no problem? If it is for you, configure
|
||||
the variable org-hide-emphasis-markers'.
|
||||
- You may finally emphasize a single character like `*a*'.
|
||||
|
||||
- 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.
|
||||
|
||||
- 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
|
||||
you can write `=quoted *xxx* a_x = b='. This and the following
|
||||
point implement a request by Daniel Clemente.
|
||||
|
||||
- There is a new emphasis marker "~" which marks text to be
|
||||
|
@ -120,6 +657,12 @@ Emphasis
|
|||
customization to revert to the default, and then adding it
|
||||
again.
|
||||
|
||||
- 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.
|
||||
|
||||
Properties and Column view
|
||||
--------------------------
|
||||
|
||||
|
@ -142,18 +685,14 @@ Properties and Column view
|
|||
symbol in front of each value. Scott Jaderholm asked for
|
||||
this, but I am not sure if this is already what he meant.
|
||||
|
||||
|
||||
The date/time prompt
|
||||
--------------------
|
||||
|
||||
There have been several small but *very* useful additions to
|
||||
the date prompt. I happen to think that it has become a very
|
||||
compact and cool way to select or modify a date and a time,
|
||||
better than anything I have seen in any other application -
|
||||
at least if you like to work with the keyboard.
|
||||
the date prompt.
|
||||
|
||||
- While entering data at the date prompt, the current
|
||||
interpretation of you input is shown next to your input in
|
||||
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'.
|
||||
|
@ -174,27 +713,27 @@ The date/time prompt
|
|||
simplifying the modification of an existing date. Thanks
|
||||
to Adam Spiers for this proposal.
|
||||
|
||||
Export
|
||||
------
|
||||
Export (all implemented by Bastien...)
|
||||
--------------------------------------
|
||||
|
||||
- You can now export special strings in HTML. Here is the
|
||||
list of newly performed conversions:
|
||||
|
||||
Org Description HTML
|
||||
-------+------------------------------------+----------
|
||||
\\ - double backslash followed by minus ­
|
||||
- - two dashes (minuses) –
|
||||
- - - three dashes (minuses) —
|
||||
. . . three dots …
|
||||
Org Description HTML
|
||||
-----+------------------------------------+----------
|
||||
`\\-' double backslash followed by minus ­
|
||||
`--' two dashes (minuses) –
|
||||
`---' three dashes (minuses) —
|
||||
`...' three dots …
|
||||
|
||||
You can turn this globally on/off with
|
||||
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.
|
||||
|
||||
- Comma-separated emails in #+EMAIL: are correctly exported.
|
||||
Thanks to Raman for pointing this out.
|
||||
Thanks to Raman for pointing out this omission.
|
||||
|
||||
Agenda
|
||||
------
|
||||
|
@ -206,8 +745,21 @@ Agenda
|
|||
e Execute another agenda command, pretty much the same as
|
||||
`C-c a', but shorter and keep the same agenda window.
|
||||
|
||||
Miscellaneous
|
||||
-------------
|
||||
Miscellaneous (much of it from Bastien)
|
||||
---------------------------------------
|
||||
|
||||
- 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.
|
||||
|
||||
- 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.
|
||||
|
||||
- The default for `org-ellipsis' is back to nil, some people
|
||||
seem to have had problems with the face as a default.
|
||||
|
@ -221,7 +773,7 @@ Miscellaneous
|
|||
shown. Thanks to Harald Weis for pointing out this omission.
|
||||
|
||||
|
||||
Version 5.13g
|
||||
Version 5.13i
|
||||
~~~~~~~~~~~~~
|
||||
|
||||
Details
|
||||
|
@ -615,7 +1167,7 @@ Overview
|
|||
========
|
||||
|
||||
- Category and the archive location can be properties.
|
||||
- The clocktable has a new =:scope= parameter.
|
||||
- The clocktable has a new `:scope' parameter.
|
||||
- CSV support when importing a table.
|
||||
- Better defaults when modifying a time stamp.
|
||||
- New way to specify the duration of an appointment.
|
||||
|
@ -640,14 +1192,14 @@ Details
|
|||
|
||||
This is a much cleaner way of dealing with multiple
|
||||
categories and archives in a single file. The preferred use
|
||||
of the =#+CATEGORY= and =#+ARCHIVE= lines is now to set a
|
||||
of the `#+CATEGORY' and `#+ARCHIVE' lines is now to set a
|
||||
*single* default for the file which is then locally
|
||||
overruled by properties. This was a proposal from Bastien
|
||||
if I remember correctly. Multiple =#+= lines still work
|
||||
if I remember correctly. Multiple `#+' lines still work
|
||||
and I don't plan to remove this support soon, but I
|
||||
encourage you to stop using them.
|
||||
|
||||
- The clocktable has a new =:scope= parameter that determines
|
||||
- The clocktable has a new `:scope' 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
|
||||
|
@ -1479,7 +2031,6 @@ Spreadsheet
|
|||
|
||||
#+CONSTANTS: c=299792458. pi=3.14 eps=2.4e-6
|
||||
|
||||
|
||||
Minor changes
|
||||
-------------
|
||||
|
||||
|
@ -1546,7 +2097,6 @@ Overview
|
|||
|
||||
- Indenting lines with TAB is more intelligent.
|
||||
|
||||
|
||||
Incompatible changes
|
||||
====================
|
||||
|
||||
|
@ -1640,7 +2190,6 @@ Details
|
|||
So you need to change the level of the last line by hand,
|
||||
using promotion and demotion functions.
|
||||
|
||||
|
||||
Version 4.77
|
||||
~~~~~~~~~~~~
|
||||
|
||||
|
@ -2006,11 +2555,9 @@ Version 4.71
|
|||
Overview
|
||||
========
|
||||
|
||||
|
||||
Incompatible changes
|
||||
====================
|
||||
|
||||
|
||||
Details
|
||||
=======
|
||||
|
||||
|
@ -2433,9 +2980,8 @@ Overview
|
|||
- Horizontal lines in HTML export.
|
||||
- Remember templates and storing of notes improved.
|
||||
|
||||
|
||||
Detailed description of changes
|
||||
================================
|
||||
===============================
|
||||
|
||||
- The descriptive part of links to email messages can be configured
|
||||
using the variable `org-email-link-description-format'. The new
|
||||
|
@ -2504,7 +3050,6 @@ Detailed description of changes
|
|||
the interactive time stamps are org.el specific, so treating
|
||||
them would require special hooks. Comments?
|
||||
|
||||
|
||||
Version 4.63
|
||||
~~~~~~~~~~~~
|
||||
- Bug fixes
|
||||
|
@ -2660,7 +3205,7 @@ Version 4.47
|
|||
- Agenda items can be sorted by tag. The *last* tag is used for this.
|
||||
- The prefix and the sorting strategy for agenda items can depend
|
||||
upon the agenda type.
|
||||
- The handling of `[mailto:'] links can be customized, see the new
|
||||
- The handling of `mailto:' links can be customized, see the new
|
||||
variable `org-link-mailto-program'.
|
||||
- `mailto' links can specify a subject after a double colon,
|
||||
like [mailto:carsten@orgmode.org::Org-mode is buggy].
|
||||
|
|
|
@ -22,9 +22,9 @@ messages, BBDB entries, and any files related to the projects. For
|
|||
printing and sharing of notes, an Org-mode file can be exported as a
|
||||
structured ASCII file, HTML, and LaTeX.
|
||||
|
||||
* Current Version (5.22) and Compatibility
|
||||
* Current Version (5.22a) and Compatibility
|
||||
|
||||
The current version is 5.22. To see what has changed in recent
|
||||
The current version is 5.22a. To see what has changed in recent
|
||||
releases, check this [[file:Changes.html][list of user-visible changes]]. These descriptions
|
||||
are extensive, to avoid that people will be printing the manual after
|
||||
each incremental release. If you have an older version of the manual,
|
||||
|
@ -39,7 +39,7 @@ but may lag a bit behind the website release.
|
|||
* Downloads
|
||||
|
||||
**** Distribution
|
||||
Download as [[file:org-5.22.zip][zip file]] or [[file:org-5.22.tar.gz][gzipped tar archive]]. These archives contain
|
||||
Download as [[file:org-5.22a.zip][zip file]] or [[file:org-5.22a.tar.gz][gzipped tar archive]]. These archives contain
|
||||
both the Lisp file org.el and the documentation in PDF and (TeX)Info
|
||||
formats. A shell script to simplify upgrading to the newest release
|
||||
has been posted [[http://www.philfam.co.uk/pete/GTD/org-mode/update-org.sh][here]].
|
||||
|
|
|
@ -6,7 +6,7 @@ lang="en" xml:lang="en">
|
|||
<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/02/12 12:28:13"/>
|
||||
<meta name="generated" content="2008/02/19 09:12:40"/>
|
||||
<meta name="author" content="Carsten Dominik"/>
|
||||
<link rel=stylesheet href="freeshell2.css" type="text/css">
|
||||
</head><body>
|
||||
|
@ -17,14 +17,79 @@ lang="en" xml:lang="en">
|
|||
|
||||
|
||||
|
||||
<div class="outline-3">
|
||||
<h3>Incompatible changes</h3>
|
||||
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
The variable `org-log-done' is now less complex.
|
||||
</li>
|
||||
<li>
|
||||
The in-buffer settings for logging have changed. Some
|
||||
options no longer exists, some new ones have been added.
|
||||
|
||||
</li>
|
||||
</ul></div>
|
||||
|
||||
<div class="outline-3">
|
||||
<h3>Details</h3>
|
||||
|
||||
|
||||
|
||||
<div class="outline-4">
|
||||
<h4>Changes to logging progress</h4>
|
||||
|
||||
|
||||
<p>
|
||||
There is now more control over which state changes are being
|
||||
logged in what way. Please read carefully the corresponding
|
||||
sections in the manual. Basically:
|
||||
</p>
|
||||
<ul>
|
||||
<li>
|
||||
The variable `org-log-done' has been simplified, it no
|
||||
longer influences logging state changes and clocking out.
|
||||
</li>
|
||||
<li>
|
||||
There is a new variable for triggering note-taking when
|
||||
clocking out an item: `org-log-note-clock-out'.
|
||||
</li>
|
||||
<li>
|
||||
Logging of state changes now has to be configured on a
|
||||
pre-keyword basis, either in `org-todo-keywords' or in the
|
||||
#+TODO in-buffer setting.
|
||||
</li>
|
||||
<li>
|
||||
These per-keyword settings allow more control. For example
|
||||
|
||||
<p>
|
||||
<pre>
|
||||
WAIT(w@) Record a note when entering this state.
|
||||
WAIT(w!) Record a timestamp when entering this state.
|
||||
WAIT(w@/!) Recore a note when entering and timestamp
|
||||
when leaving this state. This is great for
|
||||
getting a record when switching *back* from
|
||||
WAIT to TODO.
|
||||
WAIT(/!) Record a timestamp when leaving this state.
|
||||
Here we not even define a fast access
|
||||
character, but just the logging stuff.
|
||||
</pre>
|
||||
</p>
|
||||
</li>
|
||||
</ul>
|
||||
<p>This was triggered by requests from Wanrong Lin and Bernt Hansen.
|
||||
</p>
|
||||
</div>
|
||||
|
||||
<div class="outline-4">
|
||||
<h4>Other</h4>
|
||||
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
M-RET no longer brakes a line in the middle, it will make a
|
||||
new line ofter the current or (if cursor is at the beginning
|
||||
new line after the current or (if cursor is at the beginning
|
||||
of the line) before the current line.
|
||||
|
||||
</li>
|
||||
|
@ -36,6 +101,7 @@ create a new line below the current one.
|
|||
</li>
|
||||
</ul></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="outline-2">
|
||||
<h2>Version 5.21</h2>
|
||||
|
@ -6536,6 +6602,6 @@ HTML exporter upgrade, in particular table of contents
|
|||
<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/02/12 12:28:13</p>
|
||||
<p class="date"> Date: 2008/02/19 09:12:40</p>
|
||||
</div></body>
|
||||
</html>
|
||||
|
|
|
@ -6,7 +6,7 @@ lang="en" xml:lang="en">
|
|||
<title>Org-Mode Homepage</title>
|
||||
<meta http-equiv="Content-Type" content="text/html;charset=iso-8859-1"/>
|
||||
<meta name="generator" content="Org-mode"/>
|
||||
<meta name="generated" content="2008/02/12 12:28:14"/>
|
||||
<meta name="generated" content="2008/02/19 09:14:54"/>
|
||||
<meta name="author" content="Carsten Dominik"/>
|
||||
<link rel=stylesheet href="freeshell2.css" type="text/css">
|
||||
</head><body>
|
||||
|
@ -15,7 +15,7 @@ lang="en" xml:lang="en">
|
|||
<h2>Table of Contents</h2>
|
||||
<ul>
|
||||
<li><a href="#sec-1">Org - an Emacs Mode for Notes and Project Planning</a></li>
|
||||
<li><a href="#sec-2">Current Version (5.21) and Compatibility</a></li>
|
||||
<li><a href="#sec-2">Current Version (5.22a) and Compatibility</a></li>
|
||||
<li><a href="#sec-3">Downloads</a></li>
|
||||
<li><a href="#sec-4">Documentation</a>
|
||||
<ul>
|
||||
|
@ -68,11 +68,11 @@ structured ASCII file, HTML, and LaTeX.
|
|||
</div>
|
||||
|
||||
<div class="outline-2">
|
||||
<h2 id="sec-2">Current Version (5.21) and Compatibility</h2>
|
||||
<h2 id="sec-2">Current Version (5.22a) and Compatibility</h2>
|
||||
|
||||
|
||||
<p>
|
||||
The current version is 5.21. To see what has changed in recent
|
||||
The current version is 5.22a. To see what has changed in recent
|
||||
releases, check this <a href="Changes.html">list of user-visible changes</a>. These descriptions
|
||||
are extensive, to avoid that people will be printing the manual after
|
||||
each incremental release. If you have an older version of the manual,
|
||||
|
@ -93,7 +93,7 @@ but may lag a bit behind the website release.
|
|||
|
||||
<ul>
|
||||
<li>Distribution<br/>
|
||||
Download as <a href="org-5.21.zip">zip file</a> or <a href="org-5.21.tar.gz">gzipped tar archive</a>. These archives contain
|
||||
Download as <a href="org-5.22a.zip">zip file</a> or <a href="org-5.22a.tar.gz">gzipped tar archive</a>. These archives contain
|
||||
both the Lisp file org.el and the documentation in PDF and (TeX)Info
|
||||
formats. A shell script to simplify upgrading to the newest release
|
||||
has been posted <a href="http://www.philfam.co.uk/pete/GTD/org-mode/update-org.sh">here</a>.
|
||||
|
@ -415,6 +415,6 @@ somehow, when I get to it…
|
|||
<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/02/12 12:28:14</p>
|
||||
<p class="date"> Date: 2008/02/19 09:14:54</p>
|
||||
</div></body>
|
||||
</html>
|
||||
|
|
4
org.el
4
org.el
|
@ -5,7 +5,7 @@
|
|||
;; Author: Carsten Dominik <carsten at orgmode dot org>
|
||||
;; Keywords: outlines, hypermedia, calendar, wp
|
||||
;; Homepage: http://orgmode.org
|
||||
;; Version: 5.22
|
||||
;; Version: 5.22a
|
||||
;;
|
||||
;; This file is part of GNU Emacs.
|
||||
;;
|
||||
|
@ -84,7 +84,7 @@
|
|||
|
||||
;;; Version
|
||||
|
||||
(defconst org-version "5.22"
|
||||
(defconst org-version "5.22a"
|
||||
"The version number of the file org.el.")
|
||||
|
||||
(defun org-version (&optional here)
|
||||
|
|
4
org.texi
4
org.texi
|
@ -3,7 +3,7 @@
|
|||
@setfilename ../../info/org
|
||||
@settitle Org Mode Manual
|
||||
|
||||
@set VERSION 5.22
|
||||
@set VERSION 5.22a
|
||||
@set DATE February 2008
|
||||
|
||||
@dircategory Emacs
|
||||
|
@ -2743,7 +2743,7 @@ also use a prefix argument to quickly select a specific state. For
|
|||
example @kbd{C-3 C-c C-t} will change the state immediately to VERIFY.
|
||||
Or you can use @kbd{S-left} to go backward through the sequence. If you
|
||||
define many keywords, you can use in-buffer completion
|
||||
(@pref{Completion}) or even a special one-key selection scheme
|
||||
(@pxref{Completion}) or even a special one-key selection scheme
|
||||
(@pxref{Fast access to TODO states}) to insert these words into the
|
||||
buffer. Changing a todo state can be logged with a timestamp, see
|
||||
@ref{Tracking TODO state changes} for more information.
|
||||
|
|
Loading…
Reference in New Issue