From: Rainer Stengele <rainer.stengele@diplan.de>
To: emacs-orgmode@gnu.org
Subject: Re: Org-mode version 5.05
Date: Wed, 22 Aug 2007 23:14:29 +0200 [thread overview]
Message-ID: <fai8vf$nlo$3@sea.gmane.org> (raw)
In-Reply-To: <cca79cc56985a83ad792580f5c2669b1@science.uva.nl>
Carsten Dominik schrieb:
> I am releasing version 5.05 of Org-mode. As usual, it is
> in the Emacs CVS trunk, and at my website
>
> http://www.astro.uva.nl/~dominik/Tools/org/
>
> Lots of changes again, make sure to carefully read the stuff below.
>
> Enjoy!
>
> - Carsten
>
>
> Changes in Version 5.05
> -----------------------
>
> * Overview
>
> - LaTeX export, finally, thanks to Bastien.
>
> - Extension mechanism for the hyperlink system.
>
> - Global access to commands the insert and follow links.
>
> - Individual lead-times for deadlines.
>
> - Option to show only the next instance of repeating timestamp.
>
> - Store remember notes with only 2 keys
>
> - Appointment reminders from Org-mode.
>
> - Global values for selected properties.
>
> - Bug fixes.
>
>
> * Details
>
> - 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.
>
> - 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
> *you* 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.
>
> - New *global* 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.
>
> - 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
>
> DEADLINE: <2007-08-13 Mon -5d>
>
> When combined with a repeater, the repeater has to come
> first:
>
> DEADLINE: <2007-08-13 Mon +2w -5d>
>
> 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'.
>
> Thanks to Pavel Chalmoviansky and John Wiegley for
> proposals in this direction.
>
> - 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.
>
> - 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.
>
> - 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.
>
> - 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:
>
> (setq org-global-properties '(("NAME" "This is the value")))
>
> Buffer-local values are set like this:
>
> #+PROPERTY: NAME This is the value
>
> 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.
>
> - Bug fixes.
Thank you Carsten for the excellent work.
I can confirm that the "r"-eload for custom agenda views now stays with
the custom settings!
Rainer
next prev parent reply other threads:[~2007-08-22 21:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 12:02 Org-mode version 5.05 Carsten Dominik
2007-08-22 13:20 ` GPL3 (was: Org-mode version 5.05) Leo
2007-08-23 10:18 ` Carsten Dominik
2007-08-23 11:10 ` GPL3 Leo
2007-08-23 12:01 ` Re: GPL3 (was: Org-mode version 5.05) Giovanni Ridolfi
2007-08-23 12:09 ` GPL3 Leo
2007-08-22 15:46 ` Org-mode version 5.05 Giovanni Ridolfi
2007-08-22 17:39 ` Carsten Dominik
2007-08-25 13:51 ` Bastien
2007-08-22 21:14 ` Rainer Stengele [this message]
2007-08-25 17:55 ` Bastien
2007-08-26 18:53 ` Carsten Dominik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='fai8vf$nlo$3@sea.gmane.org' \
--to=rainer.stengele@diplan.de \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).