:PROPERTIES: :CUSTOM_ID: v6.32 :END:
MobileOrg is currently under review at the iPhone App Store. You will need Org mode version 6.32 to interact with it.
org-habit.el contains new code to track habits. Please configure the variable org-modules to activate it. When active, habits (a special TODO entry) will be displayed in the agenda together with a "consistency graph". Habit tracking is described in a new manual section.
Thanks to John Wiegley for this contribution.
After writing a function relating to location and context
information, you will be able to press / RET
in the agenda to
exclude tasks that cannot be done in the current context.
For details, see the information about filtering in the manual.
Thanks to John Wiegley for a patch to this effect.
When clocking into a new task while no clock is running, Org now checks for orphaned CLOCK lines and offers to repair these before starting the clock. You can also configure this feature to check for idle time and prompt you to subtract that time from the running timer.
See the new manual section for more details.
Thanks to John Wiegley for a patch to this effect.
The customize interface allows to optionally add a string to the beginning or end of such a group.
Thanks to James TD Smith for a patch to this effect.
The default in search view (C-c a s)is now that the search
expression is searched for as a substring, i.e. the different
words must occur in direct sequence, and it may be only part of
a word. If you want to look for a number of separate keywords
with Boolean logic, all words must be preceded by +
or -
.
This was, more-or-less, requested by John Wiegley.
Pressing SPC again after using it to show an agenda item in another window will make the entire subtree visible, and show scroll it. Backspace and DEL will scroll back.
This was a request by Eric Fraga.
Requested by Matt Lundin.
Request by John Wiegley.
The editing tool key C-c '
now also edits =#+MACRO=
definitions, including multiline macros.
The manual has been slightly reorganized. The archiving stuff, which was - somewhat obscurely - hidden in the Document Structure chapter, has been moved into the new chapter /Capture-Refile-Archive/. Also, there is a new chapter /Markup/ which contains both the markup rules (moved there from the Export chapter) and the documentation for embedded LaTeX.
Text can now be wrapped around figures. See the manual for details.
By setting
(setq org-read-date-prefer-future 'time)
you indicate to Org that, if you only give a time at the date/time prompt, and if this time is earlier then the current time, then the date of tomorrow will be assumed to be valid for this event. A similar mechanism was already in place for dates, but now you can make it work for times as well.
src_python{2+2}
are now exported#+lob: srcname(arg=val)
:file
is supplied with an R
block, graphics are:results code
,:file filename
is supplied, :exports file
is unnecessary:noweb
header argument now expands noweb references beforebegin_R
blocks and inline \R{}
) has been:PROPERTIES: :CUSTOM_ID: v6.31 :END:
Org-babel provides the ability to execute source code in many different languages within org-mode documents. The results of code execution -- text, tables and graphics -- can be integrated into Org mode documents and can be automatically updated during publishing. Since Org-babel allows execution of arbitrary code, the range of tasks that can be addressed from within an Org mode file becomes very large. Examples of ways in which Org-babel might be used include
Additionally, Org-babel provides a programming environment within Org files, in which data can be transmitted between parameterised source code blocks in different languages, as well as between source code blocks and Org mode tables.
A simple API is defined so that users can add support for new "languages" (broadly construed). Languages currently supported are:
Org-babel was designed and implemented Eric Schulte with continued significant help on both accounts from Dan Davison.
Richard Morelands iPhone/iPod Touch program MobileOrg can view Org files, mark entries as DONE, flag entries for later attention, and capture new entries on the road. Org mode has now support to produce a staging area where MobileOrg can download its files, and to integrate changes done on the phone in a half automatic, half interactive way. See the new appendix B in the manual for more information.
To allow comments in plain lists without breaking the list structure, you can now have indented comment lines that start with "#+ ".
This will make even drawer contents visible upon startup. Requested by Jeff Kowalczyk.
This package collects clocking information for billing customers.
Thanks to Peter Jones for this contribution.
org-crypt.el by John Wiegley and Peter Jones allows encryption of individual subtrees in Org mode outlines. Thanks to John and Peter for this contribution.
The category (as specified by an #+CATEGORY line or CATEGORY
property can contain a bracket link. While this sort-of worked
in the past, it now is officially supported and should cause no
problems in agenda display or update. The link can be followed
by clicking on it, or with C-c C-o 0
.
This was a request by Peter Westlake.
:PROPERTIES: :CUSTOM_ID: v6.30 :END:
f
and b
to move through timeUp to now, the Org mode agenda used the cursor keys left
and
=right= to switch the agenda view forward an backward through
time. However, many people found this confusing, and others
wanted to be able to do cursor motion in the agenda, for example
to select text. Therefore, after an extensive discussion on
=emacs-orgmode@gnu.org=, it was decided to use the b
and
=f= keys instead, and to let the cursor keys do cursor motion
again.
F
keyThis was necessary to free up the f
key, see above.
There is now a special command M-x org-submit-bug-report
. This
command will create a mail buffer with lots of useful details.
In particular, it contains complete version information for Emacs
and Org mode. It will also (if you agree to it) contain all
non-standard settings of org-mode and outline-mode related
variables. Even if you do not sent your emails from within
Emacs, please still use this command to generate the information
and then copy it into your mail program.
The command will not generate and include a *Backtrace*
buffer,
please do this yourself if you have hit an error. For more
information, see the feedback section of the manual.
This package allows to keep up-to-date with current Org
development, using only Emacs on-board means. So if you don't
want or cannot use git
, but still want to run the latest and
hottest Org mode, this is for you.
Thanks to Sebastian Rose for this contribution.
f
and b
to move through timeUp to now, the Org mode agenda used the cursor keys left
and
=right= to switch the agenda view forward an backward through
time. However, many people found this confusing, and others
wanted to be able to do cursor motion in the agenda, for example
to select text. Therefore, after an extensive discussion on
=emacs-orgmode@gnu.org=, it was decided to use the b
and
=f= keys instead, and to let the cursor keys do cursor motion
again.
F
keyThis was necessary to free up the f
key, see above.
When the variable org-agenda-window-setup
has the value
=other-frame=, then the new frame created to show the agenda
will now have the window marked as dedicated. As a
consequence, exiting the agenda while the agenda is the only
window on the frame will kill that frame.
This was a request by Henry Atting.
There is now a new agenda sub-mode called
=org-agenda-entry-text-mode=. It is toggled with the E
key.
When active, all entries in the agenda will be accompanied by a
few lines from the outline entry. The amount of text can be
customized with the variable org-agenda-entry-text-maxlines
.
This was a request by Anthony Fairchild, Manish, and others.
C-c C-o
in the agenda will now offer all links in the headline
and text of an entry. If there is only a single link, it will be
followed immediately.
There is a new variable that can be used to avoid some duplicate agenda entries: =org-agenda-skip-scheduled-if-deadline-is-shown= If that is set, it avoids that an entry shows up in the agenda for today for both a scheduling and a deadline entry. See the docstring of the variables for more details.
This partially addresses a request by Samuel Wales.
If the entry currently being clocked is present in the agenda, it
will be highlighted with the face org-agenda-clocking
.
This was a request by Rainer Stengele.
The LaTeX listings
package can now be used for formatting
fontified source code in many programming languages. For more
information, see
https://orgmode.org/list/m2prb6t9lw.fsf@gmail.com and
https://orgmode.org/worg/org-faq.php#fontified_source_code_w_latex
Thanks to Eric Schulte for this patch.
The width and alignment in table columns can be set with a cookie like "<10>" or "" or "". In order to keep Org from exporting such lines, the first column of a line should contain only "/". However, for convenience, there is now a special case: If the entire row contains only such markers, the line will automatically be discarded during export, even is the first column is not "/".
Macro calls may now span several lines, to write several arguments in a cleaner way. The result of a macro call can also span several lines, by inserting the string "\n" (backslash followed by n) into the value in the macro definition.
These were requests by Stefan Vollmar.
If C-c C-o
is called while the cursor is in a headline, but not
directly on a link, then all links in the entry will be offered
in a small menu. If there is only a single link, it will be
followed without a prompt.
org-cycle-separator-lines
can now be set to a negative value,
to indicate that, if the number of empty lines before a visible
entry is greater than the specified number, then all empty
lines should be shown.
This was a request by "PT" whatever this means.
Sometimes a language uses a major mode which can't be guessed from it's name. There is now a new variable =org-src-lang-modes= which can be used to map language names to major modes when this is the case. This is used when editing a source-code block, or when exporting fontified source-code with htmlize.
Thanks to Eric Schulte for a patch to this effect.
This is enabled using org-completion-use-iswitchb
, and follows
the same model of usage as for ido users.
Thanks to John Wiegley for a patch to this effect.
There is now a special command, C-c C-x e
to set the Effort=
property of an entry. From the agenda you can even use =e
.
If you have set up allowed values for the Effort
property, then
using a prefix argument will directly select the nth allowed
value. For example, in the agenda, 5 e
will select the 5th
allowed value.
This was a request by Michael Gilbert
Thanks to Dan Davison for a patch to this effect
:PROPERTIES: :CUSTOM_ID: v6.29 :END:
org-indent-mode
This mode implements outline indentation similar to clean view, but in a dynamic and virtual way, at display time. I have wanted this functionality for years and tried several implementations, all unworkable. Emacs 23 has finally made it possible. So this solution is for Emacs 23 only, and I am not sure yet how stable it really is. Time will tell.
Currently I do not recommend to turn it on globally using the
variable org-startup-indented
. But you can turn it on for a
particular buffer using
,#+STARTUP: indent
Turning on this minor mode automatically turns on =org-hide-leading-stars=, and it turns off =org-adapt-indentation=.
When a subtree does not have any children, visibility cycling now skips the CHILDREN state. You can customize this behavior with the variable =org-cycle-skip-children-state-if-no-children=.
See the variable org-provide-todo-statistics
for details. It can be the
symbol all-headings
, or a list of TODO states to consider.
This was requested by David A. Gershman.
org-list-make-subtree
This function converts the plain list at point into a subtree, preserving
the list structure. The key for this command is C-c C-*
. Thanks to Ilya
Shlyakhter for this suggestion.
Use the variable org-fontify-whole-heading-line
to turn this on. Then
headline fontification will include the final newline. If your setup for
headline faces includes a background different from the default background,
this setup creates a visual line across the window.
The new key C-c C-x t
inserts an inline task including an END
line. Inline tasks play along with (i,e, are ignored by) link creation and
footnotes. Inline tasks with an END
line can be refiled and
archived. During the refile/archive operation, the tasks become normal
tasks and the END
line disappears.
These improvements reflect reports and requests by Peter Westlake and Matt Lundin.
When archiving a task, the cursor now ends up on the next headline, so the repeated application of the archiving command will archive successive tasks.
Thanks to Bernt Hansen for a patch to this effect.
The new footnote action r
will renumber simple fn:N
footnotes in the
current document. The action S
will first do the renumbering and then
sort the footnotes (the s
action).
This was a request by Andreas Röhler.
Customize the new variable org-footnote-auto-adjust
or use the
=#+STARTUP= option fnadjust
to get automatic renumbering and sorting of
footnotes after each insertion/deletion.
This was a request by Andreas Röhler.
TAB now by default cycles visibility in plain lists if the cursor is at a
plain list item. This corresponds to the new default value t
of
=org-cycle-include-plain-lists=. If you want to treat plain list items as
part of the outline hierarchy during cycling of outline headings (this is
what a t
value used to mean), set this variable to integrate
.
We now have a mechanism to force a particular bullet type when demoting a
plain list item. See the variable org-list-demote-modify-bullet
for
details.
This was a request by Rainer Stengele.
A relative row reference like @-1 in a table may now reach across a horizontal separator line. I hope this will not break any important tables out there, but I think it is the right thing to do.
The sole original reason for not allowing such crossing was to implement running averages of one column in the next. This can now be done using field formulas near the beginning and end of the column, and a column formula for the central part.
See the variable org-table-relative-ref-may-cross-hline
for more details.
C-c C-x C-w
and C-c C-x M-w
now act on single table fields if there is
no active region defined.
The new command org-occur-link-in-agenda-files
creates a link like
=org=store-link= would, and then searches all agenda files for this
link. So for example, you could be in a GNUS message, trying to find tasks
that have links to this message.
When inserting a link with C-c C-l
, TAB completion will now not only
access link prefixes, but also the stored links.
Agenda bulk commands on marked entries now can also set the scheduling date or a deadline. Normally, all entries will be set to the specified date. However, when writing the change as "++5d" or "++2w", then each time stamp will independently be shifted by that amount.
For historic reasons, org-tags-match-list-sublevels
was forced to t
in
tags-todo agenda searches. Now we no longer do this and accept the user
setting of this variable.
Thanks to Patrick Bahr for bringing this up.
When publishing the source Org file to the source directory (i.e. if the
publishing directory is the same as the source directory), then the file
name will now look like file-source.org
and file-source.org.html
. Note
that if you do use this kind of setup, you probably want to specify
:exclude "-source\.org"
in your publishing project, to avoid that a new generation of =-source= files is created each time you publish the project.
Using #+TITLE:
without a value makes the LaTeX export ignore the value of
=org-export-latex-title-command=.
org-export-html-footnote-format
This defines the format for footnote references. This string must contain =%s= which will be replaced by the footnote label.
Allow whitespace in code references. Allow the -r
switch to remove the
references in the source code even when the lines are not numbered: the
labels can be explicit enough. Note that -r -k
is the same as no switch
at all.
Thanks to Ulf Stegemann for bring this up.
The user can now define a non-standard environment or macro to handle export of low-level headings to LaTeX.
For details, see the variable org-export-latex-low-levels
.
Some people process LaTeX files not directly to pdf, but go through dvi and then to ps or pdf. In that case, allowed images are ps and eps files, not pdf and jpg.
This commit adds the two extensions, so that export using that alternative path can be supported better. However, it is up to the user to make sure that the images are actually compatible with the backend.
org-export-html-link-up
and org-export-html-link-home
are now also
inserted into normal HTML export, above the page title.
Many different people want to set many different variables in a buffer-local way for export. This cannot be done with file variables, because the Org buffer is not current while the exporter is running.
Lots of variables can be set with the #+OPTIONS
lines, but finding
abbreviations goes only so far.
Therefore we have now a general mechanism that can be used to bind variables during export operations.
A line like:
,#+BIND: variable value
will bind the variable to value. For example, the line
,#+OPTIONS: toc:nil
can now equivalently be written as
,#+BIND: org-export-with-toc nil
When changing the publishing setup, old timestamp files can be left behind. Forcing publishing of all projects with =C-u C-c C-e E= will remove all existing timestamp files.
Separate-frame setup for calendar had caused problems in AquaEmacs.
You can now set a timer related to any headline, like an alarm clock. Three new commands have been defined:
C-c C-x ;
in Org buffers and to ;
inThis functionality was requested by Samuel Wales and emulates that of /tea-time.el/ -- see the emacswiki doc at http://www.emacswiki.org/emacs/tea-time
Using :timetamp t
as an option in a clock report now allows insertion of
the timestamp for the clocked entry. Timestamps are searched for in this
order: SCHEDULING
, TIMESTAMP
, DEADLINE
and TIMESTAMP_IA
.
org-id-uuid-program
On some systems, uuidgen
is named uuid
.
See the variable org-show-notification-handler
.
org-tags-sort-function
.This allows tags to be sorted by string<
, string>
, or a custom
function.
Thanks to James TD Smith for a patch to this effect.
But fixes, and allowing to choose between wget
and curl
.
Thanks to Christopher League for a patch to this effect.
:PROPERTIES: :CUSTOM_ID: v6.28 :END:
The command C-c C-w
can be executed to refile an entry shown in the
agenda. After the command, the entry will no longer be shown in the
agenda. It it is still in an agenda file, refresh the agenda to bring it
up from it's new context.
You can now use the m
key to mark entries in the agenda. u
will unmark
the etry at point, and U
will unmark everything. When one or more
entries have been selected, the B
key will execute an action on all
selected entries. I believe this bulk action makes mainly sense for the
commands that require answering interactive prompts. So far the supported
actions are
We can add more actions, if you convince me they make sense.
To make room for the new Bulk action commands, some keys in the agenda buffer had to move:
There is a new command bound to the v
key, it dispatches various view
mode changes. Month and year view are now only available as v m
and v
y
, respectively. Turning on inclusion of archive trees and files (unsed
to be on v
) is now on v a
and v A
.
#+begin
blocks#+begin_ ... +#end_...
blocks may now be indented along with the
structure of your document. So the #+
lines no longer need to start in
column 0, these lines can be, along with the block contents, indented
arbitrarily. Org supports this during editing with "C-c '", and now
finally treats them consistently during export across all backends. This
makes these blocks work much better with plain list structure editing, and
it also looks better if you like to indent text under outline
headings. For example:
,*** This is some headline , #+begin_example , here we have an example , #+end_example , , - a plain list , - a sublist item , - a second sublist item
, #+begin_center , centering within the plain list item , #+end_center
, #+begin_example , This example does terminate the sublist, , the indentation of the #+begin line counts. , #+end_example
, - but the top level plain lists continues here
From now on, the indentation of such a block decides whether it is part of a plain list item or if it is actually terminating the list. This was so far inconsistent between editing behavior and export, now it is consistent.
The content of the block, i.e. the text between the #+ lines gets an extra indentation of two space characters, which I find visually pleasing. You can change the amount of extra indentation using the variable =org-src-content-indentation=.
This was a pretty complex change, achieved in many small steps over the last couple of weeks. It cleans up one of the more annoying inconsistencies in Org. I hope it will work, but I am sure you will let me know if not.
Also tables can be fully indented now. What is new here is that the
=#+TBLFM= line, and also things like #+caption
, #+label
, =#+attr_...=
etc can be indented along with the table. Again, this makes the look of
the document better and allows for proper plain list structure editing.
Some #+begin_ ... +#end_...
blocks contain text that should not be
processed like normal Org mode text. example
and src
block fall into
this class, and so do ditaa
blocks, for example. The content in such
blocks is now properly fontified in a single face (called
=org-block=). This was a frequently requested feature. The list of blocks
that should be protected from normal Org mode fontification is defined in
the variable org-protecting-blocks
. Modules defining new blocks should
add to this variable when needed. org-exp-blocks.el
does this already.
Blocks can now be folded and unfolded with TAB
. If you want to have all
blocks folded on startup, customize org-hide-block-startup
or use the
=#+STARTUP= options hideblocks
or showblocks
to overrule this variable
on a per-file basis.
Thanks to Eric Schulte for a patch to this effect.
This seems to be getting a lot of use now, so it is now part of the core
and loaded automatically. This package can now also be used to define new
blocks. Customize the variable org-export-blocks
or use the function
=org-export-blocks-add-block=.
This new module allows users to export an Org page to any type of output by
constructing the output using a list of prefixes, format specifications and
suffixes for the various types of org data (headlines, paragraphs, list
bullets, etc). Use the org-set-generic-type
function to define your own
export types and have them bound to a key (use an upper-case letter for
user export definitions).
Thanks to Wes Hardaker for this contribution with a lot of potential.
See the documentation on Worg.
Links to Jira tickets.
org-R.el has been updated, thanks to Dan Davison for this.
[ TABLE-OF-CONTENTS]
is now also used for LaTeX exportThis cookie will mark the location of the =\tableofcontents= macro. Triggered by a report by Yuva.
Clocking out can now switch the task to a particular state.
This was a request by Manish.
Effort
property defined, its value is also shown in theC-c C-x C-e
can be used to change the Effort estimateThanks to Konstantin Antipin for part of the implementation, and thanks to Bernt Hansen for helping to iron out the issues related to repeated tasks.
Similar to the <20>
cookies that allow to specify a maximum width for a
table column, you can now also specify the alignment in order to overrule
the automatic alignment choice based on the dominance of number or
non-number fields in a column. The corresponding cookies are <l>
and
== for left and right side alignment, respectively. These can be
combined with maximum width specification like this: <r15>
.
This was a proposal by Michael Brand.
Sometimes you want to quickly select or change a TODO state of an item, without being bothered by your setup for blocking state changes and logging entries. So in this case, you don't want the change be seen as a true state change.
You can now set the variable
=org-treat-S-cursor-todo-selection-as-state-change= to nil. Then, when you
use S-left
and S-right
to quickly flip through states, blocking and
logging will be temporarily disabled.
See the variable `org-icalendar-include-bbdb-anniversaries'.
This was a request by Richard Riley, thanks to Thomas Baumann for the prompt implementation.
If you want to use many macros in different files, collect the =#+macro= lines into a file and link to them with
#+SETUPFILE: path/to-file
When using the command org-clone-subtree-with-time-shift
, time stamps
will be shifted for each clone. So far, this applied only to active
timestamps, but now it does apply to inactive ones as well.
The new variable org-export-table-row-tags
can now be set up in a way so
that different table lines get special CSS classes assigned. This can be
used for example to choose different background colors for odd and even
lines, respectively. The docstring of the variable contains this example:
(setq org-export-table-row-tags (cons '(if head "
It makes use of the local variables head
and nline
which are used to
check whether the current line is a header line, and whether it is an odd
or an even line. Since this is fully programmable, you can do other things
as well.
This was a request by Xin Shi.
When setting up remember templates, the target headline may now be a function, similarly to what is allowed for the target file. The functions needs to return the headline that should be used.
We now keep flyspell from highlighting non-words in links.
Some new targets in the default Makefile make it easier to update through
git to the latest version: update
and up2
. Here are the definitions.
update: git pull ${MAKE} clean ${MAKE} all
up2: update sudo ${MAKE} install
This was a request by Konstantin Antipin.
:PROPERTIES: :CUSTOM_ID: v6.27 :END:
Macro processing for export has been enhanced:
#+begin_src org ,#+macro hello Greet the $1: Hello $1 #+end_src
which would turn {{{hello(world)}}}
into Greet the world: Hello world
#+begin_src org ,#+macro: datetime (eval (format-time-string "$1")) #+end_src
The new built-in macros have been requested by Daniel Clemente.
Org now has a general mechanism how modules can provide enhanced support
(for example through completion) when adding a link. For example, when
inserting a link with C-c C-l
, you can now type file:
followed by RET=
to get completion support for inserting a file. After entering =bbdb:
and
=RET=, a completion interface will allow to complete names in the BBDB
database. These are the only ones implemented right now, but modules that
add a link type xyz:
can simple define org-xyz-complete-link
that
should return the full link with prefix after aiding the used to create the
link. For example, if you have http
links that you have to insert very
often, you could define a function org-http-complete-link
to help
selecting the most common ones.
It is now easy to publish the Org sources along with, for example, HTML files. In your publishing project, replace
:publishing-function org-publish-org-to-html
with
:publishing-function (org-publish-org-to-html org-publish-org-to-org) :plain-source t :htmlized-source t
to get both the plain org file and an htmlized version that looks like your editing buffer published along with the HTML exported version.
All exporters now push the produced material onto the kill-ring in Emacs, and also to the external clipboard and the primary selection to make it easy to paste this under many circumstances.
Set the variable `org-export-latex-tables-centered' to nil
if you prefer
tables not to be horizontally centered. Note that longtable tables are
always centered.
The markup for TODO keywords in LaTeX export is now configurable using the
variable org-export-latex-todo-keyword-markup
.
ASCII export has now the same command variations as the other export backends, for example exporting to a temporary buffer instead of a file.
The was a request by Samuel Wales.
When exporting tables to HTML, Org now adds scope
attributes to all
header fields, in order to support screen readers. Setting the variable
=org-export-html-table-use-header-tags-for-first-column= will request using
=
<td>
also in the entire first column, so that also row
information can be scoped. This was triggered by a request by Jan Buchal,
and as usually Sebastian Rose came up with the right implementation.The timezone information in iCalendar files is now written in the correct
format, and can be set in the variable org-ical-timezone
. This variable
is initialized from the TZ
environment variable.
The package turns any "undefined" #+begin_...
blocks into LaTeX
environments for LaTeX export, and into <div>
tags for HTML export.
Thanks to Chris Gray for this contribution.
Logging into a drawer can now also be set for individual subtrees using the =LOG_INTO_DRAWER= property.
Requested by Daniel J. Sinder.
Reloading Org has moved to a new key, C-c C-x !
, and is now also
available in the agenda.
Set the new option org-agenda-start-with-log-mode
to have log mode turned
on from the start. Or set this option for specific custom commands.
Thanks to Benjamin Andresen for a patch to this effect.
Depending on circumstances, construction the agenda has become a lot faster.
Triggered by Eric S Fraga's reports about using Org on a slow computer like a netbook.
The date that is today can now be highlighted in the agenda by customizing
the face org-agenda-date-today
.
Thanks to Dmitri Minaev for a patch to this effect.
When an entry has both check boxes and TODO children, it is not clear what kind of statistics a cookie should show You can now use the =COOKIE_DATA= property to disambiguate, by giving it a value "todo" or "checkbox".
Thanks to Ulf Stegeman, who was persistent enough to push this change past my initial resistance.
nil
will make statistics cookies count all checkboxes in the Setting the
variable org-hierarchical-checkbox-statistics
to lit hierarchy below it.
Setting the variable org-hierarchical-todo-statistics
to
=nil= will do the same for TODO items.
To turn on recursive statistics only for a single subtree, add the word
"recursive" to the COOKIE_DATA
property. Note that you can have such a
property containing both "todo" or "checkbox" for disambiguation, and the
word "recursive", separated by a space character.
The change for checkboxes was a patch by Richard Klinda.
Column view has new operators for computing the minimum, maximum, and mean of property values.
Thanks to Mikael Fornius for a patch to this effect.
:PROPERTIES: :CUSTOM_ID: v6.26 :END:
Entries can now define a CUSTOM_ID
property. This property must be a
valid ID according to HTML rules, and it will be used in HTML export as the
main target ID for this entry. That means, both the table of conents and
other internal links will automatically point to this ID instead of the
automatic ID like sec-1.1
. This is useful to create humar-readable
permanent links to these location in a document.
The user is responsible to make sure that custom IDs are unique within a file.
Links written like [[#my-target-name] ]
can be used to target a custom
ID.
When using C-c l
to store a link to a headline that has a custom ID, Org
will now create two links at the same time. One link will be to the custom
ID. The other will be to the globaly unique ID property. When inserting
the line with C-c C-l
, you need to decide which one you want to use. Use
the ID links for entries that are expected to move from one file to the
next. Use custom ID links publishing projects, when you are sure that te
entry will stay in that file. See also the variable
=org-link-to-org-use-id=.
If the target headline part of a remember template definition entry is
=top= or bottom
, the target file may now be a non-Org mode file. In this
case, the content of the remember buffer will be added to that file without
enforcing an Org-like headline. Sorry, Russel, that this took so long.
Setting the property NOBLOCKING
will turn off TODO dependency checking
for this entry.
A new function is called to verify tasks that are about to be selected as remember targets. See the new variable =org-refile-target-verify-function=.
Thanks to Stathis Sideris.
The latest version of htmlize.el is now the in the contrib directory of Org. Thanks to Hrvoje Niksic for allowing this.
:PROPERTIES: :CUSTOM_ID: v6.25 :END:
We now do have a fully functional DocBook exporter, contributed by Baoqiu
Cui. Simple press C-c e D
to export the current file to DocBook
format. You can also get direct conversion to PDF if you have made the
correct setup, please see the manual for details.
Kudos to Baoqiu for this fantastic addition, and my personal thanks for doing this in a such a smooth way that I did not have to do anything myself.
org-protocol.el is a new module that supersedes both /org-annotation-helper.el/ and org-browser.el and replaces them with a more abstracted interface. org-protocol intercepts calls from emacsclient to trigger custom actions without external dependencies. Only one protocol has to be configured with your external applications or the operating system, to trigger an arbitrary number of custom actions. Just register your custom sub-protocol and handler with the new variable =org-protocol-protocol-alist=.
org-protocol comes the with three standard protocol handlers (in parenthesis the name of the sub-protocol):
org-protocol-remember
(remember
)org-protocol-store-link
(store-link
)org-protocol-open-source
(open-source
)Passing data to emacs is now as easy as calling
emacsclient org-protocol://sub-protocol://data
For more information see the online documentation.
Thanks to Sebastian Rose for this really beautiful module.
Inline tasks are tasks that have all the properties of normal outline nodes, including the ability to store meta data like scheduling dates, TODO state, tags and properties. But these tasks are not meant to introduce additional outline structure, at least as far as visibility cycling and export is concerned. They are useful for adding tasks in extensive pieces of text where interruption of the flow or restructuring is unwanted.
This feature is not turned on by default, you need to configure =org-modules= to turn it on, or simply add to you .emacs file:
(require 'org-inlinetask)
After that, tasks with level 15 (30 stars when using org-odd-levels-only) will be treated as inline tasks, and fontification will make obvious which tasks are treated in this way.
Org can now collect tasks from an RSS feed, a great method to get stuff
from online call and note-taking services into your trusted system. You
need to configure the feeds in the variable org-feed-alist
. The manual
contains a short description, more detailed information is available on
Worg.
Full credit goes to Brad Bozarth who really paved the way for this exciting new feature.
The #+ATTR_HTML line can now be used to set attributes for a table. Attributes listed in that line will replace existing attributes in =org-export-html-table-tag=, or will add new ones. For example
#+ATTR_HTML: border="2" rules="all" frame="all" #+CAPTION: Finally a table with lines! | a | b | |---|---| | 1 | 2 |
LaTeX export now treats hierarchy levels 4,5, etc as itemize lists, not as description lists as before. This is more consistent with the behavior of HTML export. You can configure this behavior using the variable =org-export-latex-low-levels=.
Text can be exported centered with
,#+BEGIN_CENTER ,Everything should be made as simple as possible, \\ ,but not any simpler ,#+END_CENTER
Org-publish can produce a list of all files in a project. Previously the file containing this list was called "index.org", really a brain-dead default because during publication it would overwrite the "index.html" file of the website.
The default file name is now "sitemap.org".
If a link is [[#name] [desc]]
, the href produced when exporting the file
will be exactly href="#name". So starting a link target with # will
indicate that there will be an explicit target for this.
If a list contains "- ___" (three underscores) as an item, this terminates the list, ignoring this item. This is an experimental feature, it may disappear again if we find other ways to deal with literal examples right after lists.
See this mailing list thread for context.
We now have a way to change not only the date, but also the start time of an entry from the agenda. The date is normally changed with S-right/left. Now, if you add a C-u prefix, the hour will be changed. If you immediately press S-right/left again, hours will continue to be changed. A double prefix will do the same for minutes. If the entry has a time range like 14:40-16:00, then both times will change, preserving the length of the appointment.
When writing an agenda view to a PDF file, supplying a a prefix argument
(C-u C-x C-w
) will get the new file displayed immediately.
This was a request by Alan E Davis.
During secondary agenda filtering, pressing "?" now will install a filter that selects entries which do not have an effort defined.
This new model was necessary because we needed to stop interpreting entries
with no effort defines as 0 effort. This was inconsistent, because for
normal agenda sorting, the treatment of these entries depends on the
variable org-sort-agenda-noeffort-is-high
. Now this variable is also
respected during filtering.
This new feature resulted from a discussion with Matt Lundin and Bernt Hansen.
The new variable org-agenda-cmp-user-defined
can contain a function to
test how two entries should be compared during sorting. The symbols
=user-defined-up= and user-defined-down
can then be part of any sorting
strategy.
This was a request by Samuel Wales.
When a tags/property match does match an entry and it's sublevels, the sublevels used to be indented by dots, to indicate that the matches likely result from tag inheritance. This is now no longer the default, so the subitems will not get special indentation. You can get this behavior back with
(setq org-tags-match-list-sublevels 'indented)
When, during a stuck-project search, a project tree is identified as not stuck, so far the search would continue after the end of the project tree. From now on, the search continues in the subtree, so that stuck subprojects can still be identified.
RefTeX can now be used to create a citation in Org mode buffers. Setup the buffer with
,#+BIBLIOGRAPHY: bibbase style
and create citations with C-c C-x [
.
Together with org-exp-bibtex.el by Taru Karttunen (available as a contributed package), this provides a great environment for including citations into HTML and LaTeX documents.
When using the S-cursor keys to change the first time in a time range like
<2009-04-01 Wed 14:40-16:40>
then the end time will change along, so that the duration of the event will stay the same.
This was a request by Anupam Sengupta.
A new sparse tree command shows entries with times after a certain
date. Keys are C-c / a
, this command is for symmetry with C-c / b
.
A new command allows to create clone copies of the current entry, with shifted dates in all stamps in the entry. This is useful to create, for example, a series of entries for a limited time period. I am using it to prepare lectures, for example.
Checkboxes now have their own face, org-checkbox
. This can be used
for nice effects, for example choosing a face with a box around it:
(custom-set-faces (org-checkbox ((t (:background "#444444" :foreground "white" :box (:line-width 1 :style released-button)))))
In tables fields, the sentence commands M-a
and M-e
are redefined to
jump to the beginning or end of the field.
This was a request by Bastien Guerry.
Sometimes users report that they lost data when not immediately storing a new remember note, and then later exiting Emacs or starting a new remember process.
Now you can set the variable org-remember-backup-directory
. Each
remember buffer created will then get its own unique file name in that
directory, and the file will be removed only if the storing of the note
to an Org files was successful.
Christopher Suckling has added functionality to /org-mac-message.el/. In particular, you can now select a number of messages and easily get links to all of them with a single command. For details, see the online documentation.
Setting up the minibuffer for reading a date. If can be used to The new
hook org-read-date-minibuffer-setup-hook
is called when install new
keys into the temporary keymap used there.
:PROPERTIES: :CUSTOM_ID: v6.24 :END:
From this release on, tag searches will be case sensitive. While I still think it would be nice to have them case-insensitive, this was both an inconsistency (TODO keyword searches have always been case-sensitive), and trouble for coding some efficient algorithms. So please make sure that you give the tags with correct casing when prompted for a match expression.
The key to produce a sparse tree matching tags and properties is now
=C-c / m= instead of C-c a T
. This is also more consistent with the
=C-c a m= key for the corresponding agenda view. C-c / T
will still
work for now, but it is no longer advertised in the documentation and
may go away at any time in the future.
uuidgen generates IDs that often start with a number, not a latter. However, IDs and names in XHTML must start with a letter. Therefore, IDs in HTML files will now get an "ID-" prefix if they have been generated by uuidgen. This means that id links from one file to another may stop working until all files have been exported again.
So far, an entire task would get a special face when
=org-agenda-fontify-priorities= was set. Now, the default value for
this variable is the symbol cookies
, which means that on the cookie is
fontified. Set it to t
if you want the entire task headline to be
fontified.
Agenda views can now be exported to PDF files by writing them to a file
with extension ".pdf". Internally this works by first producing the
postscript version and then converting that to PDF using the ghostview
utility ps2pdf
. Make sure that this utility is installed on your
system.
The postscript version will not be removed, it will stay around.
When exporting an agenda view to HTML or PDF for printing or remote access, one of the problems can be that information stored in entries below the headline is not accessible in that format.
You can now copy some of that information to the agenda view before exporting it. For this you need to set the variable =org-agenda-add-entry-text-maxlines= to a number greater than 0.
(setq org-agenda-add-entry-text-maxlines 20)
Or you can do this with the settings in a custom agenda view, for example:
("A" "" agenda "" ((org-agenda-ndays 1) (org-agenda-add-entry-text-maxlines 5)) ("agenda-today.pdf"))
ASCII export of links works now much better. If a link has a link and a description part which are different, then the description will remain in the text while the link part will be moved to the end of the current section, before the next heading, as a footnote-like construct.
Configure the variable org-export-ascii-links-to-notes
if you prefer
the links to be shown in the text. In this case, Org will make an
attempt to wrap the line which may have become significantly longer by
showing the link.
Thanks to Samuel Wales for pointing out the bad state of ASCII link export.
If a custom agenda command specifies a value for =org-agenda-filter-preset= in its options, the initial view of the agenda will be filterd by the specified tags. Applying a filter with =/= will then always add to that preset filter, clearing the filter with =/ /= will set it back to the preset. Here is an example of a custom agenda view that will display the agenda, but hide all entries with tags =FLUFF= or =BLUFF=:
("A" "" agenda "" ((org-agenda-filter-preset '("-FLUFF" "-BLUFF"))))
This is in response to a thread on the mailing list, started by Daniel Clemente and with great contributions by Bernt Hansen and Matt Lundin.
Citations can now me made using BibTeX, and will be exported to LaTeX and HTML. This is implemented in a contributed package by Taru Karttunen, org-exp-bibtex.el. Kudos to Taru for this really nice addition.
Use something like
,#+DESCRIPTION: This page is all about .... ,#+KEYWORDS: org-mode, indexing, publishing
To specify the content of the description and keywords meta tags for HTML output.
org-collector.el provides functions to create tables by collecting and processing properties from entries in a specific scope like the current tree or file, or even from all agenda files. General lisp expressions can be used to manipulate the property values before they are inserted into an org-mode table, for example as a dynamic block that is easy to update.
Thanks to Eric Schulte for yet another great contribution to Org.
org2rem.el has been updated significantly and now does a more comprehensive job of exporting Org events to remind.
Thanks to Sharad Pratap for this update.
A new <div id=content>
is wrapped around the entire page, everything
that is inside <body>
.
This means that you need to update org-info.js (if you have a local copy). It will be safe todo so, because the new org-info.js still handles older pages correctly. Thanks to Sebastian Rose for making these changes so quicky.
When typing in Org mode, undo will now remove up to 20 characters at a time with a single undo command. This is how things work normally in Emacs, but the special binding of characters in Org mode made this impossible until now.
Thanks to Martin Pohlack for a patch which mimicks the behavior of the
Emacs command loop for the Org version of self-insert-command
. Note
that this will not work in headlines and tables because typing there
will do a lot of extra work.
There might be a small typing performance hit resulting from this change - please report in the mailing list if this is noticeable and annoying.
The variable org-special-ctrl-a/e
now allows separate settings for
=C-a= and C-e
. For example
(setq org-special-ctrl-a/e '(reversed . t))
Thanks to Alan Davis for this proposal.
In addition to orgstruct-mode
which allows to use some Org mode
structure commands in other major modes, there is a more invasive
version of this mode: orgstruct++-mode
. This mode will import all
paragraph and line wrapping variables into the major mode, so that, for
example, during typing the auto-fill wrapping of items will work just
like in Org mode. This change is not reversible, so turning off
=orgstruct++-mode= will not remove these settings
again. orgstruct++-mode
is most useful in text modes like message-mode
or magit-log-edit-mode
. Furthermore, orgstruct++-mode
will
recognize plain list context not only in the first line of an item, but
also further down, so that M-RET
will correctly insert new items.
Thanks to Austin Frank for requesting some of these changes.
M-right
and M-left
now do demote and promote all headlines in an
active region.
The manual chapters about tags and about properties now only refer to the section about agenda views, where the general syntax of tag/property matches is described.
A string like {{{ title }}}
will be replaced by the title of the
document, {{{ email }}}
by the email setting of the author and
similarly for other export settings given in #+...
lines. In addition
to that, you can define an arbitrary number of macros, for example:
,#+MACRO: myaddress 41 Onestreet, 12345 New York, NY ,... ,my address is {{{myaddress}}}, see you there.
Macro replacement is the very first thing that happens during export, and macros will be replaced even in source code and other protected regions.
There is now a special command to reload all Org Lisp files, so that you
can stay in your Emacs session while pulling and compiling changes to
Org. The command to reload the compiled files (if available) is C-c C-x
r
. If no compiled files are found, uncompiled ones will be loaded. If
you want to force loading of uncompiled code (great for producing
backtraces), use a prefix arg: C-u C-c C-x r
. Both commands are
available in the menu as well.
This new command was inspired by one written earlier by Bernt Hansen.
The new variable org-priority-faces
can be used to set faces for each
priority.
The key to produce a sparse tree matching tags and properties is now C-c /
m
instead of C-c a T
. This is more consistent with the C-c a m
key
for the corresponding agenda view. C-c / T
will still work for now, but
it is no longer advertised in the documentation and may go away at any time
in the future.
uuidgen generates IDs that often start with a number, not a letter. However, IDs and names in XHTML must start with a letter. Therefore, IDs in HTML files will now get an "ID-" prefix if they have been generated by uuidgen. This means that id links from one file to another may stop working until all files have been exported again, so that both links and targets have the new prefix.
So far, an entire task would get a special face when
=org-agenda-fontify-priorities= was set. Now, the default value for this
variable is the symbol cookies
, which means that on the cookie is
fontified. Set it to t
if you want the entire task headline to be
fontified.
Some people like to put a creation time stamp into a headline and then get
confused if the time-of-day found in there shows up as the time-of-day of
the deadline/scheduling entry for this headline. The reason for this is
that Org searches the headline for a free-format time when trying to sort
the entry into the agenda, and that search accidentally finds the time in
the creation time stamp or something else that happens to look like a
time. If this is more painful than useful for you, configure the new
variable org-agenda-search-headline-for-time
.
:PROPERTIES: :CUSTOM_ID: v6.23 :END:
State change notes can now be captured into a drawer LOGBOOK
, to keep the
entry tidy. If this is what you want, you will need this configuration:
(setq org-log-into-drawer "LOGBOOK")
Thanks to Wanrong Lin for this proposal.
The CLOCK
drawer will be abandoned, clock lines will now also end up in a
drawer LOGBOOK
. The reason for this is that it's a bit useless to have
two different drawers for state change notes and clock lines. If you wish
to keep the old way, use
(setq org-clock-into-drawer "CLOCK")
Dan Davison has contributed org-R.el which is now in the contrib
directory. Org-R performs numerical computations and generates
graphics. Data can come from org tables, or from csv files; numerical
output can be stored in the org buffer as org tables, and links are
created to files containing graphical output. Although, behind the
scenes, it uses R, you do not need to know anything about R. Common
operations, such as tabulating discrete values in a column of an org
table, are available "off the shelf" by specifying options on lines
starting with #+R:
. However, you can also provide raw R code to be
evaluated. The documentation is currently the worg tutorial at
https://orgmode.org/worg/org-tutorials/org-R/org-R.php
Thanks to Dan for this great contribution.
TODO keywords in HTML export have the CSS class todo
or done
. Tags
have the CSS class tag
. In addition to this, each keyword has now
itself as class, so you could do this in your CSS file:
.todo { font-weight:bold; } .done { font-weight:bold; } .TODO { color:red; } .WAITING { color:orange; } .DONE { color:green; }
If any of your keywords causes conflicts with CSS classes used for
different purposes (for example a tag "title" would cause a conflict with
the class used for formatting the document title), then you can use the
variables org-export-html-tag-class-prefix
and
=org-export-html-todo-kwd-class-prefix= to define prefixes for the class
names for keywords, for example "kwd-".
Thanks to Wanrong Lin for this request, and to Sebastian Rose for help with the implementation.
Some commands in Org are context-sensitive, they will execute different
functions depending on context. The most important example is of course
=C-c C-c=, but also the M-cursor
keys fall into this category.
Org has now a system of hooks that can be used by add-on packages to
install their own functionality into these keys. See the docstring of
=org-ctrl-c-ctrl-c-hook= for details. The other hooks are named like
=org-metaleft-hook= or org-shiftmetaright-hook
.
If you set the :base-extension
property for a publishing project to the
symbol any
, all files in the directory will be published, irrespective of
extension.
Thanks to Richard Klinda for a patch to this effect.
A new index in the manual lists all variables mentioned in the manual, about 200 variables in total.
When an entry has the ORDERED property set, checkboxes in the entry must be completed in order. This was already the case for children TODO items, now it also applies for checkboxes.
Thanks to Rainer Stengele for this proposal.
The ORDERED
property is used to flag an entry so that subtasks
(both children TODO items and checkboxes) must be completed in
order. This property is most easily toggled with the command
=C-c C-x o=. A property was chosen for this functionality,
because this should be a behavior local to the current task, not
inherited like tags. However, properties are normally
invisible. If you would like visual feedback on the state of
this property, configure the variable
=org-track-ordered-property-with-tag=. If you then use C-c C-x
o
to toggle the property, a tag will be toggled as well, for
visual feedback.
Note that the tag itself has no meaning for the behavior of TODO items and checkboxes, and that changing the tag with the usual tag commands will not influence the property and therefore the behavior of TODO and checkbox commands.
Up to now, the fast tags interface tried to lump as many tags as possible into a single line, with the exception that groups would always be on a line by themselves.
Now, if you use several lines to define your tags, like
,#+TAGS: aa(a) bb(b) cc(c) ,#+TAGS: dd(d) ee(e) ff(f)
then there will also be a line break after the "cc" tag in the fast tag selection interface. You may also write
,#+TAGS: aa(a) bb(b) cc(c) \n dd(d) ee(e) ff(f)
to achieve the same effect, and you can use \n
several times in order
to produce empty lines. In org-tag-alist
, newlines are represented as
=(:newline)=.
Thanks to Christopher Suckling for a patch to this effect.
When the variable org-agenda-dim-blocked-tasks
is set to invisible
,
tasks that are blocked will not be visible in the agenda. If the
blocking is due to child TODO entries, this does make sense because the
children themselves will show up in the TODO list.
However, as John Rakestraw has pointed out, if the blocking is done by
checkboxes, no trace of these subtasks is left. Therefore, when the
blocking is done by checkboxes, we now overrule the invisible
setting
and replace it with mere dimming of the task.
If you configure org-export-latex-import-inbuffer-stuff
, in-buffer
definitions like #+TITLE
will be made available in the LaTeX file as
=\orgTITLE=.
This was a request by Russel Adams.
:PROPERTIES: :CUSTOM_ID: v6.22 :END:
Org-choose helps documenting a decision-making process by using TODO keywords for different degrees of chosenness, and by automatically keeping a set of alternatives in a consistent state.
Documentation for org-choose.el is available here.
This package inserts itself into Org using hooks, so if other people would like to do interesting stuff with TODO keywords for special purposes, looking at Tom's code might be a good way to start.
Thanks to Tom for this interesting contribution!
Thanks to Sebastian Rose for making these changes.
This was reported as a bug by William Henney and is fixed now.
When sorting table fields or entries by date, Org first tries to find an active date, and, if none exist, uses a passive date if present.
This was a request by Hsui-Khuen Tang
org-return-follows-link
is back to nil
Setting it to t
violates Emacs rules to some extent. The internal
implementation of this has been improved, so setting it to t
should
now be pretty stable.
The sibling of a DONE task can now automatically be scheduled.
This was a patch by Andrew Hyatt.
The functions org-agenda-skip-entry-if
and
=org-agenda-skip-subtree-if= now accept timestamp
and =nottimestamp=
as additional conditions.
This was in response to a request by Saurabh Agrawal.
:PROPERTIES: :CUSTOM_ID: v6.21 :END:
Here are the new default values:
(setq org-return-follows-link t)
(setq org-use-fast-todo-selection t)
(setq org-yank-adjusted-subtrees nil)
(setq org-tags-column -77)
(setq org-agenda-sorting-strategy '((agenda time-up priority-down category-keep) (todo time-up priority-down category-keep) (tags time-up priority-down category-keep) (search category-keep)))
:PROPERTIES: :CUSTOM_ID: v6.20 :END:
John Wiegley's code for enforcing simple TODO dependencies has been integrated into Org mode. Thanks John!
The structure of Org files (hierarchy and lists) makes it easy to define
TODO dependencies. A parent TODO task should not be marked DONE until
all subtasks (defined as children tasks) are marked as DONE. And
sometimes there is a logical sequence to a number of (sub)tasks, so that
one task cannot be acted upon before all siblings above it are done. If
you customize the variable org-enforce-todo-dependencies
, Org will
block entries from changing state while they have children that are not
DONE. Furthermore, if an entry has a property ORDERED
, each of its
children will be blocked until all earlier siblings are marked
DONE. Here is an example:
,* TODO Blocked until (two) is done ,** DONE one ,** TODO two
,* Parent , :PROPERTIES: , :ORDERED: t , :END: ,** TODO a ,** TODO b, needs to wait for (a) ,** TODO c, needs to wait for (a) and (b)
The command C-c C-x o
toggles the value of the ORDERED
property.
The variable org-agenda-dim-blocked-tasks
controls how blocked entries
should appear in the agenda, where they can be dimmed or even made
invisible.
Furthermore, you can use the variable =org-enforce-todo-checkbox-dependencies= to block TODO entries from switching to DONE while any checkboxes are unchecked in the entry.
Customize the variable org-support-shift-select
to use S-cursor key
for selecting text. Make sure that you carefully read the docstring of
that variable first.
The command C-c C-x C-b
normally toggles checkbox status in the
current line, or in all lines in the region. With prefix argument it
now either adds or removes the checkbox.
This was a requested by Daniel Clemente.
:PROPERTIES: :CUSTOM_ID: v6.19 :END:
C-c -
and C-c *
\par
can be used to force a paragraph break, also in footnotesC-c -
and C-c *
The conversion commands C-c -
and C-c *
are now better behaved
and therefore more useful, I hope.
If there is an active region, these commands will act on the region, otherwise on the current line.
You may now reference constants, fields and ranges from a different table, either in the current file or even in a different file. The syntax is
remote(NAME-OR-ID,REF)
where NAME can be the name of a table in the current file as set by a =#+TBLNAME: NAME= line before the table. It can also be the ID of an entry, even in a different file, and the reference then refers to the first table in that entry. REF is an absolute field or range reference, valid in the referenced table. Note that since there is no "current filed" for the remote table, all row and column references must be absolute, not relative.
Even if a table does not end with a hline (mine never do because I think it is not pretty), for the sake of references you can assume there is one. So in the following table
a | b |
---|---|
1 | 2 |
3 | 4 |
a reference like @I$1..@II$2
will now work.
The variables org-agenda-todo-ignore-with-date
,
org-agenda-todo-ignore-with-date
, and
org-agenda-todo-ignore-with-date
make it possible to exclude TODO
entries which have this kind of planning info associated with
them. This is most useful for people who schedule everything, and
who use the TODO list mainly to find things that are not yet
scheduled. Thomas Morgan pointed out that also the tags-todo search
may serve exactly this purpose, and that it might be good to have a
way to make these variables also apply to the tags-todo search. I
can see that, but could not convince myself to make this the
default. A new variable must be set to make this happen:
org-agenda-tags-todo-honor-ignore-options
.
\par
can be used to force a paragraph break, also in footnotesThe LaTeX idiom \par
will insert a paragraph break at that
location. Normally you would simply leave an empty line to get such a
break, but this is useful for footnotes whose definitions may not
contain empty lines.
:PROPERTIES: :CUSTOM_ID: v6.18 :END:
Short literal examples can be created by preceding lines with a colon. Such lines must now have a space after the colon. I believe this is already general practice, but now it must be like this. The only exception are lines that are empty except for the colon.
The example and src switches like -n
can now also be added to
include file statements:
#+INCLUDE "~/.emacs" src emacs-lisp -n -r
Thanks to Manish for pointing out that this was not yet supported.
You can now specify a -t
switch to an example or src block, to
make it export to HTML as a text area. To change the defaults for
height (number of lines in the example) and width of this area (80),
use the -h
and -w
switches.
Thanks to Ulf Stegemann for driving this development.
When exporting a single subtree by selecting it as a region before
export, the LaTeX class for the export will be taken from the
LaTeX_CLASS
property of the entry if present.
Thanks to Robert Goldman for this request.
Two new variables govern which kind of files can be inlined during
export. These are org-export-html-inline-image-extensions
and
org-export-latex-inline-image-extensions
. Remember that links are
turned into an inline image if they are a pure link with no
description. HTML files can inline /.png/, /.jpg/, and /.gif/
files, while LaTeX files, when processed with pdflatex, can inline
/.png/, /.jpg/, and /.pdf/ files. These also represent the default
settings for the new variables. Note that this means that pure
links to /.pdf/ files will be inlined - to avoid this for a
particular link, make sure that the link has a description part
which is not equal to the link part.
If you make links by ID, these links will now still work in HTML exported files, provided that you keep the relative path from link to target file the same.
Thanks to Friedrich Delgado Friedrichs for pushing this over the line.
The new command `C-c C-x ,' will pause the relative timer. When the relative timer is running, its value will be shown in the mode line. To get rid of this display, you need to really stop the timer with `C-u C-c C-x ,'.
Thanks to Alan Davis for driving this change.
Instead of using the automatic, unique directory related to the entry ID, you can also use a chosen directory for the attachments of an entry. This directory is specified by the ATTACH_DIR property. You can use `C-c C-a s' to set this property.
Thanks to Jason Jackson for this proposal.
By setting the property ATTACH_DIR_INHERIT, you can now tell Org that children of the entry should use the same directory for attachments, unless a child explicitly defines its own directory with the ATTACH_DIR property. You can use the command `C-c C-a i' to set this property in an entry.
:PROPERTIES: :CUSTOM_ID: v6.17 :END:
Org mode now directly supports the creation of footnotes. In contrast to the footnote.el package, Org mode's footnotes are designed for work on a larger document, not only for one-off documents like emails. The basic syntax is similar to the one used by footnote.el, i.e. a footnote is defined in a paragraph that is started by a footnote marker in square brackets in column 0, no indentation allowed. The footnote reference is simply the marker in square brackets inside text. For example:
The Org homepage1 now looks a lot better than it used to. ...
Org mode extends the number-based syntax to named footnotes and optional inline definition. Using plain numbers as markers is supported for backward compatibility, but not encouraged because of possible conflicts with LaTeX syntax. Here are the valid references:
[1]
[fn:name]
[fn:: This is the inline definition of this footnote]
[fn:name: a definition]
Footnote labels can be created automatically, or you create names
yourself. This is handled by the variable org-footnote-auto-label
and
its corresponding #+STARTUP
keywords, see the docstring of that
variable for details.
The following command handles footnotes:
Org mode's footnote support is designed so that it should also work in
buffers that are not in Org mode, for example in email messages. Just
bind org-footnote-action
to a global key like C-c f
.
The main trigger for this development came from a hook function written by Paul Rivier, to implement named footnotes and to convert them to numbered ones before export. Thanks, Paul!
Thanks also to Scot Becker for a thoughtful post bringing this subject back onto the discussion table, and to Matt Lundin for the idea of named footnotes and his prompt testing of the new features.
Literal examples introduced with #+BEGIN_EXAMPLE
or #+BEGIN_SRC
do
now allow optional line numbering in the example. Furthermore, links to
specific code lines are supported, greatly increasing Org mode's utility
for writing tutorials and other similar documents.
Code references use special labels embedded directly into the source code. Such labels look like "(ref:name)" and must be unique within a document. Org mode links with "(name)" in the link part will be correctly interpreted, both while working with an Org file (internal links), and while exporting to the different backends. Line numbering and code references are supported for all three major backends, HTML, LaTeX, and ASCII. In the HTML backend, hovering the mouse over a link to a source line will remote-highlight the referenced code line.
The options for the BEGIN lines are:
Here is an example:
,#+begin_src emacs-lisp -n -r ,(defmacro org-unmodified (&rest body) (ref:def) , "Execute body without changing `buffer-modified-p'." , `(set-buffer-modified-p (ref:back) , (prog1 (buffer-modified-p) ,@body))) ,#+end_src , ,Line (def) contains the macro name. Later at line ,(back), backquoting is used.
When exported, this is translated to:
(defmacro org-unmodified (&rest body) (ref:def) "Execute body without changing `buffer-modified-p'." `(set-buffer-modified-p (ref:back) (prog1 (buffer-modified-p) ,@body)))
Line (def) contains the macro name. Later at line (back), backquoting is used.
Thanks to Ilya Shlyakhter for proposing this feature set. Thanks to Sebastian Rose for the key Javascript element that made the remote highlighting possible.
The export preprocessor now runs more hooks, to allow better-timed tweaking by user functions:
org-export-preprocess-hook
org-export-preprocess-after-include-files-hook
org-export-preprocess-after-tree-selection-hook
org-export-preprocess-before-backend-specifics-hook
org-export-preprocess-final-hook
The :id
parameter for the dynamic block capturing column view can
now truly be an ID that will also be found in a different
file. Also, it can be like file:path/to/file
, to capture the
global column view from a different file.
Thanks to Francois Lagarde for his report that IDs outside the current file would not work.
:PROPERTIES: :CUSTOM_ID: v6.16 :END:
Cleanup of many small bugs, and one new feature.
Fields in the last row of a table can now be referenced with $LR1, $LR2, etc. These references can appear both on the left hand side and right hand side of a formula.
:PROPERTIES: :CUSTOM_ID: v6.15f :END:
This version reverses the introduction of @0 as a reference to the last rwo in a table, because of a conflict with the use of @0 for the current row.
:PROPERTIES: :CUSTOM_ID: v6.15 :END:
There used to be a syntax for setting link attributes for HTML export by enclosing the attributes into double braces and adding them to the link itself, like
[[./resources/img/a.jpg{{alt="an image"}}]]
This syntax is not longer supported, use instead
#+ATTR_HTML: alt="an image" [[./resources/img/a.jpg]]
All the remaining issues with the LaTeX exporter have hopefully been addressed in this release. In particular, this covers quoting of special characters in tables and problems with exporting files where the headline is in the first line, or with an active region.
Tables, and Hyperlinks that represent inlined images, can now be equipped with additional information that will be used during export. The information will be taken from the following special lines in the buffer and apply to the first following table or link.
For LaTeX export, if either a caption or a label is given, the element will be exported as a float, i.e. wrapped into a figure or table environment.
Unique identifiers for entries can now be used more efficiently. Internally, a hash array has replaced the alist used so far to keep track of the files in which an ID is defined. This makes it quite fast to find an entry by ID.
There is a new link type which looks like this:
id:GLOBALLY-UNIQUE-IDENTIFIER
This link points to a specific entry. When you move the entry to a different file, for example if you move it to an archive file, the link will continue to work.
The file org-id.el contains an API that can be used to write code using these identifiers, including creating IDs and finding them wherever they are.
Org has its own method to create unique identifiers, but if the system
has uuidgen command installed (Mac's and Linux systems generally do),
it will be used by default (a change compared to the earlier
implmentation, where you explicitdly had to opt for uuidgen). You can
also select the method by hand, using the variable org-id-method
.
If the ID system ever gets confused about where a certain ID is, it
initiates a global scan of all agenda files with associated archives,
all files previously known containing any IDs, and all currently visited
Org mode files to rebuild the hash. You can also initiate this by hand:
=M-x org-id-update-id-locations=. Running this command will also dump
into the *Messages*
buffer information about any duplicate IDs. These
should not exist, and Org will never make the same ID twice, but if
you copy an entry with its properties, duplicate IDs will inevitably
be produced. Unfortunately, this is unavoidable in a plain text system
that allows you to edit the text in arbitrary ways, and a portion of
care on your side is needed to keep this system clean.
The hash is stored in the file ~/.emacs.d/.org-id-locations
. This is
also a change from previous versions where the file was
=~/.org=id-locations=. Therefore, you can remove this old file if you
have it. I am not sure what will happen if the =.emacs.d= directory
does not exists in your setup, but in modern Emacsen, I believe it
should exist. If you do not want to use IDs across files, you can avoid
the overhead with tracking IDs by customizing the variable
=org-id-track-globally=. IDs can then still be used for links inside a
single file.
IDs will also be used when you create a new link to an Org mode
buffer. If you use org-store-link
(normally at C-c l
) inside en
entry in an Org mode buffer, and ID property will be created if it does
not exist, and the stored link will be an id:
link. If you prefer the
much less secure linking to headline text, you can configure the
variable org-link-to-org-use-id
. The default setting for this
variable is create-if-interactive
, meaning that an ID will be created
when you store a link interactively, but not if you happen to be in an
Org mode file while you create a remember note (which usually has a link
to the place where you were when starting remember).
You may now use @0
to reference the last dataline in a table in a
stable way. This is useful in particular for automatically generated
tables like the ones using org-collector.el by Eric Schulte.
:PROPERTIES: :CUSTOM_ID: v6.14 :END:
Relative row references in tables look like this: "@-4" which means the forth row above this one. These row references are not allowed to cross horizontal separator lines (hlines). So far, when a row reference violates this policy, Org would silently choose the field just next to the hline.
Tassilo Horn pointed out that this kind of hidden magic is actually confusing and may cause incorrect formulas, and I do agree. Therefore, trying to cross a hline with a relative reference will now throw an error.
If you need the old behavior, customize the variable
org-table-error-on-row-ref-crossing-hline
.
Org now supports taking timed notes, useful for example while watching a video, or during a meeting which is also recorded.
C-c C-x .
C-c C-x -
M-RET
C-c C-x 0
Thanks to Alan Dove, Adam Spiers, and Alan Davis for contributions to this idea.
You may now use the variable org-tag-faces
to define the face used
for specific tags, much in the same way as you can do for TODO
keywords.
Thanks to Samuel Wales for this proposal.
This request has come up often, most recently it was formulated by Tassilo Horn.
If you prefer the old behavior of only showing the local tags,
customize the variable org-agenda-show-inherited-tags
.
So far, the only way to select tags for inheritance was to allow it for all tags, or to do a positive selection using one of the more complex settings for `org-use-tag-inheritance'. It may actually be better to allow inheritance for all but a few tags, which was difficult to achieve with this methodology.
A new option, `org-tags-exclude-from-inheritance', allows to specify an exclusion list for inherited tags.
In addition to <now>
, <today>
, <yesterday>
, and <tomorrow>
,
there are more special values accepted now in time comparisons in
property searches: You may use strings like <+3d>
or <-2w>
, with
units d, w, m, and y for day, week, month, and year, respectively
Thanks to Linday Todd for this proposal.
All the metadata in a headline, i.e. the TODO keyword, the priority cookie, and the tags, can now be excluded from export with appropriate options:
| Variable | Publishing property | OPTIONS switch | |-------------------------------+---------------------+----------------| | org-export-with-todo-keywords | :todo-keywords | todo: | | org-export-with-tags | :tags | tags: | | org-export-with-priority | :priority | pri: |
You can now use the key C-c C-x M-w
in a w3m buffer with HTML
content to copy either the region or the entire file in a special
way. When you yank this text back into an Org mode buffer, all
links from the w3m buffer will continue to work under Org mode.
For this to work you need to load the new file /org-w3m.el./ Please check your org-modules variable to make sure that this is turned on.
Thanks for Richard Riley for the idea and to Andy Stewart for the implementation.
The LOCATION property can now be inherited during iCalendar export
if you configure org-use-property-inheritance
like this:
#+begin_src emacs-lisp (setq org-use-property-inheritance '("LOCATION")) #+end_src
:PROPERTIES: :CUSTOM_ID: v6.13 :END:
The remember buffers created with Org's extensions are in
Org mode, which is nice to prepare snippets that will
actually be stored in Org mode files. However, this makes it
hard to configure key bindings without modifying the Org mode
keymap. There is now a minor mode active in these buffers,
`org-remember-mode', and its keymap org-remember-mode-map can
be used for key bindings. By default, this map only contains
the bindings for C-c C-c
to store the note, and =C-c C-k=
to abort it. Use `org-remember-mode-hook' to define your own
bindings like
#+begin_src emacs-lisp (add-hook 'org-remember-mode-hook (lambda () (define-key org-remember-mode-map "\C-x\C-s" 'org-remember-finalize))) #+end_src
If you wish, you can also use this to free the C-c C-c=
binding (by binding this key to nil in the minor mode map),
so that you can use =C-c C-c
again to set tags.
This modification is based on a request by Tim O'Callaghan.
You can now get the completion interface from ido.el for
many of Org's internal completion commands by turning on the
variable org-completion-use-ido
. ido-mode
must also be
active before you can use this.
This change is based upon a request by Samuel Wales.
When column view is active in the agenda, and when you have
summarizing properties, the date lines become normal column
lines and the separation between different days becomes
harder to see. If this bothers you, you can now customize
the face org-agenda-column-dateline
.
This is based on a request by George Pearson.
These anchors can be used to jump to a directly with an HTML
link, just like the sec-xxx
IDs. For example, the
following will make a http link
//domain/path-to-my-file.html#dummy
work:
#+begin_src org ,# <> ,*** a headline #+end_src
This is based on a request by Matt Lundin.
This new file implements special export behavior of user-defined blocks. The currently supported blocks are
For more details and examples, see the file commentary in org-exp-blocks.el.
Kudos to Eric Schulte for this new functionality, after org-plot.el already his second major contribution. Thanks to Stathis for this excellent program, and for allowing us to bundle it with Org mode.
This module gives control over execution Emacs Lisp code blocks included in a file.
Thanks to Eric Schulte also for this file.
You can now configure Org to understand many links created
with the Emacs Planner package, so you can cut text from
planner pages and paste them into Org mode files without
having to re-write the links. Among other things, this means
that the command org-open-at-point-global
which follows
links not only in Org mode, but in arbitrary files like
source code files etc, will work also with links created by
planner. The following customization is needed to make all of
this work
#+begin_src emacs-lisp (setq org-link-translation-function 'org-translate-link-from-planner) #+end_src
I guess an inverse translator could be written and integrated into Planner.
This did work all along, but only now I have documented it.
yank-pop
works again after yanking an outline treeSamuel Wales had noticed that org-yank
did mess up this
functionality. Now you can use yank-pop
again, the only
restriction is that the so-yanked text will not be pro/demoted or
folded.
Thanks to Steve Purcell for a patch to this effect.
Thanks to Sebastian Rose for pushing this.
:PROPERTIES: :CUSTOM_ID: v6.12 :END:
With transient-make-mode
active (zmacs-regions
under
XEmacs), you can now select a region of entries and refile
them all with a single C-c C-w
command.
Thanks to Samuel Wales for this useful proposal.
org-yank
The behavior of Org's yanking command has been further fine-tuned in order to avoid some of the small annoyances this command caused.
org-yank
with a prefix arg will stop any specialYou can now add formulas to a clock table, either by hand, or with a
:formula
parameter. These formulas can be used to create
additional columns with further analysis of the measured times.
Thanks to Jurgen Defurne for triggering this addition.
The footnote export in 6.11 really was not good enough. Now it
works fine. If you have customized footnote-section-tag
, make
sure that your customization is matched by
footnote-section-tag-regexp
.
Thanks to Sebastian Rose for pushing this change.
More languages are supported during HTML export. This is only relevant for the few special words Org inserts, like "Table of Contents", or "Footnotes". Also the encoding issues with this feature seem to be solved now.
Thanks to Sebastian Rose for pushing me to fix the encoding problems.
:PROPERTIES: :CUSTOM_ID: v6.11 :END:
C-y
now adjusts the tree levelC-y
now adjusts the tree levelWhen yanking a cut/copied subtree or a series of trees, the normal
yank key C-y
now adjusts the level of the tree to make it fit into
the current outline position, without losing its identity, and
without swallowing other subtrees.
This uses the command org-past-subtree
. An additional change in
that command has been implemented: Normally, this command picks the
right outline level from the surrounding visible headlines, and
uses the smaller one. So if the cursor is between a level 4 and a
level 3 headline, the tree will be pasted as level 3. If the cursor
is actually at the beginning of a headline, the level of that
headline will be used. For example, lets say you have a tree like
this:
#+begin_src org ,* Level one ,** Level two ,(1) ,(2)* Level one again #+end_src
with (1) and (2) indicating possible cursor positions for the insertion. When at (1), the tree will be pasted as level 2. When at (2), it will be pasted as level 1.
If you do not want C-y
to behave like this, configure the variable
org-yank-adjusted-subtrees
.
Thanks to Samuel Wales for this idea and a partial implementation.
If you configure the variable org-agenda-log-mode-items
, you can
now request that all logged state changes be included in the agenda
when log mode is active. If you find this too much for normal
applications, you can also temporarily request the inclusion of
state changes by pressing C-u l
in the agenda.
This was a request by Hsiu-Khuern Tang.
You can also press `C-u C-u l' to get only log items in the agenda, withour any timestamps/deadlines etc.
Previously, footnotes would be left in the document where they are defined, now they are all collected and put into a special =
Thanks to Sebastian Rose for this request.
Thanks to Sebastian Rose for pushing this cleanup.
If the option org-clock-in-resume
is t
, and the first clock line
in an entry is unclosed, clocking into that task resumes the clock
from that time.
Thanks to James TD Smith for a patch to this effect.
The data saved include the contents of org-clock-history
, and the
running clock, if there is one.
To use this, you will need to add to your .emacs
#+begin_src emacs-lisp (setq org-clock-persist t) (setq org-clock-in-resume t) (org-clock-persistence-insinuate) #+end_src
Thanks to James TD Smith for a patch to this effect.
So far you could only bypass your setup in `org-file-apps' and force
opening a file link in Emacs by using a C-u
prefix arg with C-c
C-o
. Now you can call C-u C-u C-c C-o
to force an external
application. Which external application depends on your system. On
Mac OS X and Windows, open
is used. On a GNU/Linux system, the
mailcap settings are used.
This was a proposal by Samuel Wales.
Inserting file links with C-u C-c C-l
was buggy if the setting of
`org-link-file-path-type' was `adaptive' (the default). Absolute
file paths were not abbreviated relative to the users home
directory. This bug has been fixed.
Thanks to Matt Lundin for the report.
Even though one of the purposes of entry attachments was to reduce the number of links in an entry, one might still want to have the occasional link to one of those files. You can now use link abbreviations to set up a special link type that points to attachments in the current entry. Note that such links will only work from within the same entry that has the attachment, because the directory path is entry specific. Here is the setup you need:
#+begin_src emacs-lisp (setq org-link-abbrev-alist '(("att" . org-attach-expand-link))) #+end_src
After this, a link like this will work
#+BEGIN_EXAMPLE att:some-attached-file.txt #+END_EXAMPLE
This was a proposal by Lindsay Todd.
When a repeating task, listed in the daily/weekly agenda under today's date, is completed from the agenda, it is listed as DONE in the agenda until the next update happens. After the next update, the task will have disappeared, of course, because the new date is no longer today.
Buffers that are created during publishing are now deleted when the publishing is over. At least I hope it works like this.
:PROPERTIES: :CUSTOM_ID: v6.10 :END:
C-c C-q
This is, I believe, becoming a killer feature. It allows you to define fewer and more general custom agenda commands, and then to do the final narrowing to specific tasks you are looking for very quickly, much faster than calling a new agenda command.
If you have not tries this yet, you should!
When filtering an existing agenda view with /
, you can
now narrow down the existing selection by an additional
condition. Do do this, use \
instead of /
to add the
additional criterion. You can also press +
or -
after
/
to add a positive or negative condition. A condition
can be a TAG, or an effort estimate limit, see below.
This means to filter the agenda for the value of the Effort property. For this you should best set up global allowed values for effort estimates, with
#+begin_src emacs-lisp (setq org-global-properties '(("Effort_ALL" . "0 0:10 0:30 1:00 2:00 3:00 4:00"))) #+end_src
You may then select effort limits with single keys in the
filter. It works like this: After /
or \
, first select the
operator which you want to use to compare effort estimates:
< Select entries with effort smaller than or equal to the limit > Select entries with effort larger than or equal to the limit = Select entries with effort equal to the limit
After that, you can press a single digit number which is used as an index to the allowed effort estimates.
If you do not use digits to fast-select tags, you can even skip the
operator, which will then default to
`org-agenda-filter-effort-default-operator', which is by default
<
.
Thanks to Manish for the great idea to include fast effort filtering into the agenda filtering process.
For example, if there is a filter in place that does select for
HOME tags, against EMAIL tags, and for tasks with an estimated
effort smaller than 30 minutes, the mode-line with show
+HOME-EMAIL+<0:30
All normal refresh commands, including those that move the weekly agenda from one week to the next, now keep the current filter in place.
You need to press / /
to turn off the filter. However, when you
run a new agenda command, for example going from the weekly agenda
to the TODO list, the filter will be switched off.
C-c C-q
You can still use C-c C-c
on a headline, but the new binding
should be considered as the main binding for this command. The
reasons for this change are:
C-c C-c
for tags is really out of line with otherC-c C-q
will also work when the cursor is somewhere downThe new option org-todo-state-tags-triggers
can be used to define
automatic changes to tags when a TODO state changes. For example,
the setting
(setq org-todo-state-tags-triggers '((done ("Today" . nil) ("NEXT" . nil)) ("WAITING" ("Today" . t))))
will make sure that any change to any of the DONE states will remove tags "Today" and "NEXT", while switching to the "WAITING" state will trigger the tag "Today" to be added.
I use this mostly to get rid of TODAY and NEXT tags which I apply to select an entry for execution in the near future, which I often prefer to specific time scheduling.
The new headline is inserted after the current subtree.
Thanks to Peter Jones for patches to fine-tune this behavior.
There is a new variable org-mouse-features
which gives you some
control about what features of org-mouse you want to use. Turning
off some of the feature will free up the corresponding mouse events,
or will avoid activating special regions for mouse clicks. By
default I have urned off the feature to use drag mouse events to
move or promote/demote entries. You can of course turn them back on
if you wish.
This variable may still change in the future, allowing more fine-grained control.
This is using LaTeX export, and then processes it to PDF using pdflatex.
C-c C-e p process to PDF. C-c C-e d process to PDF, and open the file.
Set this to t
if you want state change notes to be inserted after
any initial drawers, i.e drawers the immediately follow the headline
and the planning line (the one with DEADLINE/SCHEDULED/CLOSED
information).
org-file-apps
now uses regular expressions, see below:PROPERTIES: :CUSTOM_ID: v6.09 :END:
org-file-apps
now uses regular repressions instead of extensionsJust like in auto-mode-alist
, car's in the variable
org-file-apps
that are strings are now interpreted as regular
expressions that are matched against a file name. So instead of
"txt", you should now write "\\.txt\\'" to make sure the matching is
done correctly (even though "txt" will be recognized and still be
interpreted as an extension).
There is now a shortcut to get many file types visited by Emacs. If org-file-apps contains `(auto-mode . emacs)', then any files that are matched by `auto-mode-alist' will be visited in emacs.
c
, m
, and l
specifically select copy
,:PROPERTIES: :CUSTOM_ID: v6.08 :END:
C-c C-a
no longer calls `show-all'The reason for this is that C-c C-a
is now used for the attachment
system. On the rare occasions that this command is needed, use M-x
show-all
, or C-u C-u C-u TAB
.
You can now attach files to each node in the outline tree. This works by creating special directories based on the ID of an entry, and storing files in these directories. Org can keep track of changes to the attachments by automatically committing changes to git. See the manual for more information.
Thanks to John Wiegley who contributed this fantastic new concept and wrote org-attach.el to implement it.
%^{prop}p to insert a property %k the heading of the item currently being clocked %K a link to the heading of the item currently being clocked
Also, when you exit remember with C-2 C-c C-c
, the item will be
filed as a child of the item currently being clocked. So the idea
is, if you are working on something and think of a new task related
to this or a new note to be added, you can use this to quickly add
information to that task.
Thanks to James TD Smith for a patch to this effect.
Thanks to James TD Smith for a patch to this effect.
This module deals with repeated tasks that have checkbox lists below them.
Thanks to James TD Smith for this contribution.
It can be used to locally set the variable `org-export-html-style-extra'. Several such lines are allowed-, they will all be concatenated. For an example on how to use it, see the publishing tutorial.
:PROPERTIES: :CUSTOM_ID: v6.07 :END:
org-scheduled
for entries scheduled in the future.The prefix argument to the `C-c C-c' command that finishes a remember process is now interpreted differently:
C-c C-c Store the note to predefined file and headline C-u C-c C-c Like C-c C-c, but immediately visit the note in its new location. C-1 C-c C-c Select the storage location interactively C-0 C-c C-c Re-use the last used location
This was requested by John Wiegley.
The reason for this change was that `C-c C-x r' is also used as a tty key replacement.
The locally defined tags are now listed as categories when exporting
to iCalendar format. Org's traditional file/tree category is now
the last category in this list. Configure the variable
org-icalendar-categories
to modify or revert this behavior.
This was a request by Charles Philip Chan.
You can now easily and interactively filter an existing agenda view
with respect to a tag. This command is executed with the /
key in
the agenda. You will be prompted for a tag selection key, and all
entries that do not contain or inherit the corresponding tag will be
hidden. With a prefix argument, the opposite filter is applied:
entries that do have the tag will be hidden.
This operation only hides lines in the agenda buffer, it does not remove them. Changing the secondary filtering does not require a new search and is very fast.
If you press TAB at the tag selection prompt, you will be switched to a completion interface to select a tag. This is useful when you want to select a tag that does not have a direct access character.
A double / /
will restore the original agenda view by unhiding any
hidden lines.
This functionality was John Wiegley's idea. It is a simpler implementation of some of the query-editing features proposed and implemented some time ago by Christopher League (see the file contrib/lisp/org-interactive-query.el).
The command @C-c '@
(that is C-c
followed by a single
quote) can now also be used to switch to a special editing mode for
fixed-width sections. The default mode is artist-mode
which
allows you to create ASCII drawings.
It works like this: Enter the editing mode with @C-c
'@
. An indirect buffer will be created and narrowed to the
fixed-width region. Edit the drawing, and press @C-c
'@
again to exit.
Lines in a fixed-width region should be preceded by a colon followed by at least one space. These will be removed during editing, and then added back when you exit the editing mode.
Using the command in an empty line will create a new fixed-width region.
This new feature arose from a discussion involving Scott Otterson, Sebastian Rose and Will Henney.
You can run it by simple calling org-plot/gnuplot. Documentation is not yet included with Org, please refer to http://github.com/eschulte/org-plot/tree/master until we have moved the docs into Org or Worg.
Thanks to Eric Schulte for this great contribution.
You may now use tags to select parts of a document for inclusion
into the export, and to exclude other parts. This behavior is
governed by two new variables: org-export-select-tags
and
org-export-exclude-tags
. These default to ("export")
and
("noexport")
, but can be changed, even to include a list of
several tags.
Org first checks if any of the select tags is present in the buffer. If yes, all trees that do not carry one of these tags will be excluded. If a selected tree is a subtree, the heading hierarchy above it will also be selected for export, but not the text below those headings. If none of the select tags is found anywhere in the buffer, the whole buffer will be selected for export. Finally, all subtrees that are marked by any of the exclude tags will be removed from the export buffer.
You may set these tags with in-buffer options EXPORT_SELECT_TAGS=
and =EXPORT_EXCLUDE_TAGS
.
I love this feature. Thanks to Richard G Riley for coming up with the idea.
The prefix argument to the `C-c C-c' command that finishes a remember process is now interpreted differently:
C-c C-c Store the note to predefined file and headline C-u C-c C-c Like C-c C-c, but immediately visit the note in its new location. C-1 C-c C-c Select the storage location interactively C-0 C-c C-c Re-use the last used location
This was requested by John Wiegley.
If the kill is a subtree or a sequence of subtrees, yanking them
with C-y
will leave all the subtrees in a folded state. This
basically means, that kill and yank are now much more useful in
moving stuff around in your outline. If you do not like this,
customize the variable org-yank-folded-subtrees
.
Right now, I am only binding C-y
to this new function, should I
modify all bindings of yank? Do we need to amend yank-pop
as
well?
This feature was requested by John Wiegley.
If you attach formulas and plotting instructions to a table capturing column view, these extra lines will now survive an update of the column view capture, and any formulas will be re-applied to the captured table. This works by keeping any continuous block of comments before and after the actual table.
If a property value is a time stamp, S-left and S-right can now be used to shift this date around while in column view.
This was a request by Chris Randle.
This was a request by Peter Frings.
Numerical and alphanumerical sorting now skips any TODO keyword or priority cookie when constructing the comparison string. This was a request by Wanrong Lin.
You can now define a sorting strategy for agenda entries that does look at the TODO state of the entries. Sorting by TODO entry does first separate the non-done from the done states. Within each class, the entries are sorted not alphabetically, but in definition order. So if you have a sequence of TODO entries defined, the entries will be sorted according to the position of the keyword in this sequence.
This follows an idea and sample implementation by Christian Egli.
org-scheduled
for entries scheduled in the future.This was a request by Richard G Riley.
Thanks to Tommy Lindgren for a patch to this effect.
Thanks to Gregory Sullivan for a patch to this effect.
The locally defined tags are now listed as categories when exporting
to iCalendar format. Org's traditional file/tree category is now
the last category in this list. Configure the variable
org-icalendar-categories
to modify or revert this behavior.
This was a request by Charles Philip Chan.
The filter can modify the value that will be displayed in a column,
for example it can cut out a part of a time stamp. For more
information, look at the variable
org-columns-modify-value-for-display-function
.
Prefix arg 0 to S-RET does the trick.
This was a request by Chris Randle.
The timestamp directory now uses SHA1 hashed versions of the path to each publishing file. This should be a consistent and system-independent way to handle things. The change means that your next publishing command will publish each and every file again, but just once, until new time stamps are in place.
org-export-html-style
is noworg-export-html-style-extra
thatThis follows a proposal by Rustom Mody.
You can now set attributes in hyperlinks that will be used when publishing to HTML. For example, if you want to use the ALT and TITLE attributes of an inlined image, here is who to do this:
[[./resources/img/a.jpg{{alt="This is image A" title="Image with no action"}}]]
Thanks to Charles Chen for this idea.
In a link, you can now leave out the "file:" prefix if you write an
absolute file name like /Users/dominik/.emacs
or ~/.emacs
, or if
you write a relative file name by using =./= or =../= to start the
file path. You cannot write a plain file name, because plain text
is interpreted as an internal link.
So for example, a link to an image A.jpg with a thumbnail B.jpg can now be written like
#+begin_src org ,./B.jpg] #+end_src
Deadline and scheduling time stamps are now treated differently in iCalendar export. The default behavior is now the following:
Of course this would not be Emacs if you could not configure exactly
what you want. Take a look at the variables
org-icalendar-use-deadlines
and org-icalendar-use-scheduled
if
you want to go back to the old behavior or even do something
completely different.
Thanks to Karen Cooke for triggering this change.
If the comparison value in a property search is a string that is enclosed in angular brackets, a time comparison will be done. For example
+DEADLINE>="<2008-12-24 15:20>"
looks for entries with a deadline on or after that time. Special allowed values are "" (with time) and "" (date only).
This is based on a request by Manish.
When set, a link pointing to a directory will actually open the index.org file in that directory. This is a good setting inside a publishing project. When not set, you get a finder/explorer window for that directory, or dired, depending on system and setup.
This follows a request by Richard Riley.
These parameters specify prefixes for each line of included text. :prefix1 is only for the first line, :prefix for all other lines.
This follows a proposal by Richard Riley.
This option can be used to switch the style of the index produced by org-publish. Can be `list' (index is just an itemized list of the titles of the files involved) or `tree' (the directory structure of the source files is reflected in the index). The default is `tree'.
Thanks to Manuel Hermenegildo for the patch.
v
will toggle inclusion of trees with theThis was triggered by a proposal by Manuel Hermenegildo.
If I were to name my releases, this one would be called "Adam". Adam, you definitely owe me a beer :-). And I owe you one, too - thanks for all the great ideas.
It used to call org-cut-special
, but that is also at bound
to the key C-c C-x C-w
.
The date at the cursor in the agenda (and also in the calendar) can now be used to schedule entries, or to set the date in a remember template correctly. It is also designed to make it easier to move an entry to a date picked in the agenda. Thanks to Thomas Baumann for starting the thread that led to this development.
If you want to use the date at the agenda cursor in a
remember template, start remember from the agenda with the
keys k r
. While the template is being filled in, the
default date for all time stamps, and also for all
interactive escapes like %^t
is now the date at the cursor
in the agenda. The exact same command can also be used from
the calendar if you prefer that.
You may now pick the date for scheduling an item or for setting a deadline in the agenda, where you have the best overview over free time slots. This is a two step process.
Org has sophisticated mapping capabilities to find all entries satisfying certain criteria. Internally, this functionality is used to produce agenda views, but there is also an API that can be used to execute arbitrary functions for each or selected entries. The main entry point for this API is:
#+begin_example -- Function: org-map-entries func &optional match scope &rest skip Call FUNC at each headline selected by MATCH in SCOPE.
FUNC is a function or a lisp form. The function will be called without arguments, with the cursor positioned at the beginning of the headline. The return values of all calls to the function will be collected and returned as a list.
MATCH is a tags/property/todo match as it is used in the agenda tags view. Only headlines that are matched by this query will be considered during the iteration. When MATCH is nil or t, all headlines will be visited by the iteration.
SCOPE determines the scope of this command, it can specify a file, all agenda files, the current tree and much more.
The remaining args are treated as settings for the skipping facilities of the scanner. #+end_example
The function given to that mapping routine can really do anything you
like. Here is a simple example that will turn all entries in the
current file with a tag TOMORROW
into TODO entries with the keyword
=UPCOMING=. Entries in comment trees and in archive trees will be
ignored.
(org-map-entries '(org-todo "UPCOMING") "+TOMORROW" 'file 'archive 'comment)
The following example counts the number of entries with TODO keyword =WAITING=, in all agenda files.
(length (org-map-entries t "/+WAITING" nil 'agenda))
Use k r
to start remember from the agenda, with enforcing the
cursor date as default for any time stamps created by the template.
You may now set the heading part of a remember template definition to `top' or `bottom'. The template will then be filed as a level 1 entry to the beginning or end of the target file, respectively. Thanks to Adam Spiers for this proposal.
Just include the %&
escape anywhere in the template. An
interesting combination now is to use %!%&
, which will
immediately file and visit the note, which is equivalent to
generating the note directly in the target location. Thanks to
Adam Spiers for this proposal.
If you are using %%(bbdb-anniversaries)
to list anniversaries in
the agenda, you can now directly access the entry that triggered a
listed anniversary from the agenda. Just click the anniversary - it
is a link now. Thanks to Thomas Baumann for a patch to this effect.
See the new variable
org-agenda-columns-remove-prefix-from-item
. Thanks to Adam Spiers
for this proposal.
See the new variable `org-export-section-number-format'. Thanks to Adam Spiers for this proposal.
In column view, if you press a key 1-9 or 0, the corresponding values from the list of allowed values for that field at point will be directly selected. Thanks to Levin Du for this proposal and a patch to this effect.
The new hook `org-before-save-iCalendar-file-hook' runs just before the buffer with a created iCalendar export is saved. This is what I settled for after a long discussion with Adam Spiers about doing some special filtering automatically.
When turning on log mode in the agenda with l
, clock lines
will now also list the end time, not only the starting time.
Thanks to Tian Qiu for bringing this up again.
Thanks to Manuel Hermenegildo for a patch to this effect.
The [/] and [%] cookies have already provided statistics for checkboxes. Now they do the same also for TODO entries. If a headline contains either cookie, changing the TODO state of any direct child will trigger an update of this cookie. Children that are neither TODO nor DONE are ignored.
There have already been requests to automatically switch the parent headline to DONE when all children are done. I am not making this a default feature, because one needs to make many decisions about which keyword to use, etc. Instead of a complex customization variable, I am providing a hook that can be used. This hook will be called each time a TODO statistics cookie is updated, with the cursor in the corresponding line. Each function in the hook will receive two arguments, the number of done entries, and the number of not-done entries, and you can use the hook to change the state of the headline. Here is an example implementation:
(defun org-summary-todo (n-done n-not-done) "Switch entry to DONE when all sub-entries are done, to TODO otherwise." (let (org-log-done org-log-states) ; turn off logging (org-todo (if (= n-not-done 0) "DONE" "TODO"))))
(add-hook 'org-after-todo-statistics-hook 'org-summary-todo)
If you are writing a document with source code examples, you can include
these examples into a #+BEGIN_SRC lang ... #+END_SRC
or (with the
org-mtags module loaded) a <src...
structure. lang
stands for the
Emacs mode used for editing the language, this could be emacs-lisp
for
Emacs Lisp mode examples, or org
for Org mode examples. You can now
use the key "C-c '" (that is C-c followed by the single quote) to edit
the example in its native mode. This works by creating an indirect
buffer, narrowing it to the example and setting the appropriate
mode. You need to exit editing by pressing "C-c '" again. This is
important, because lines that have syntactic meaning in Org will be
quoted by calling this command.
"C-c '" also edits include files, the setupfile in a #+setufile
line,
and all those little foreign snippets like:
,#+HTML: this code can be edited in html-mode
,#+BEGIN_HTML ,Same here ,#+BEGIN_HTML
,#+LaTeX: this code can be edited in latex-mode
,#+BEGIN_LaTeX ,Same here ,#+BEGIN_LaTeX
,#+BEGIN_SRC fortran ,Here we can edit in fortran-mode ,#+END_SRC
This is necessary for synchronization services. The UIDs are created using the the org-id.el module which is now part of the Org core. If you set the variable
(setq org-icalendar-store-UID t)
then all created UIDs will be stored in the entry as an =:ID:= property. This is off by default because it creates lots of property drawers even if you only play with iCalendar export. But if you plan to use synchronization, you really need to turn this on.
Diary sexp entries do not yet receive proper persistent UIDs, because they are transformed to iCalendar format by icalendar.el which creates fresh UIDs each time, based on the current time.
An interesting aspect of Org is that a single outline node can give rise to multiple iCalendar entries (as a timestamp, a deadline, a scheduled item, and as a TODO item). Therefore, Org adds prefixes "TS-", "DL-" "CS-", and "TD-" to the UID during iCalendar export, depending on what triggered the inclusion of the entry. In this way the UID remains unique, but a synchronization program can still figure out from which entry all the different instances originate.
When exporting a subtree by selecting it before calling the export
command, you can now use the properties EXPORT_TITLE
, EXPORT_TEXT
,
and EXPORT_OPTIONS
to overrule the global #+TITLE
, #+TEXT
, and
=#+OPTIONS= settings. You can also set an export file name with
=EXPORT_FILE_NAME= that will overrule the file name derived from the
buffer's file name. As far as the options are concerned, the global
=#+OPTIONS= will still be read, and only the options you give in the
property will be overwritten. For example:
,#+OPTIONS: skip:nil ,* Computer Tricks , :PROPERTIES: , :EXPORT_FILE_NAME: ct.html , :EXPORT_TITLE: Steve's collected computer tricks , :EXPORT_OPTIONS: h:2 toc:nil , :END:
Tags that are defined in a line like
#+FILETAGS: work urgent
are inherited by all entries in the file.
Thanks to Manuel Hermenegildo for this proposal.
Previously, the default was to not include text in an org-mode
buffer before the first headline. From now on, the default it to
include it. If you like the old default better, customize the
variable org-export-skip-text-before-1st-heading
or set the
value on a per-file basis with
A plain list will be exported as a description list if the first item in the list has a term and the description, separated by " :: ". For example
Emacs software by Carsten Dominik - RefTeX :: Support for LaTeX Labels, References, Citations - CDLaTeX :: more LaTeX functionality for Emacs - TeXmathp :: checking LaTeX buffers for Math mode. - ORG :: An Emacs mode for notes and projet planning. - CONSTANTS :: An Emacs package for inserting the definition of natural constants and units into a buffer. - IDLWAVE :: The Emacs modes for editing and running IDL and WAVE CL files.
will be rendered as
This works now in the HTML exporter, we still need to supoort it with the LaTeX and ASCII exporters.
For quoting an entire paragraph as a citation, use
#+begin_src org ,#+BEGIN_QUOTE: ,Everything should be made as simple as possible, ,but not any simpler -- Albert Einstein ,#+BEGIN_QUOTE: #+end_src
which will render as
#+BEGIN_QUOTE: Everything should be made as simple as possible, but not any simpler -- Albert Einstein #+END_QUOTE:
You can now get code examples fontified like they would be fontified in an Emacs Buffer, and export the result to HTML. To do so, wrap the code examples into the following structure:
#+begin_src org ,#+BEGIN_SRC emacs-lisp , (defun org-xor (a b) , "Exclusive or." , (if a (not b) b)) ,#+END_SRC #+end_src
In the export, this will then look like this (if you are now looking at the ASCII export and do not see anything interesting, go and check out the HTML version at https://orgmode.org/Changes.html).
#+BEGIN_SRC emacs-lisp (defun org-xor (a b) "Exclusive or." (if a (not b) b)) #+END_SRC
The string after the BEGIN_SRC
is the name of the major emacs mode
that should be used to fontify the code example, without the "-mode"
at the end of the mode name. For example, if you are writing an Org
tutorial with Org examples included, you would use "org" as the
language identifier - in fact, I have used just that in the example
above.
Currently this works only for HTML export, and requires the htmlize.el package, version 1.34 or later. For other backends, such structures are simply exported as EXAMPLE.
A line like
#+INCLUDE "file" markup lang
will lead to the inclusion of the contents of FILE at the moment of publishing. FILE should be surrounded by double quotes, this is obligatory if it contains space characters. The parameters MARKUP and LANG are optional. MARKUP can be "example", "quote", or "src". If it is "src", LANG should be the name of the Emacs mode to be used for fontifying the code. For example:
Here is my /.emacs/ file: #+INCLUDE "~/.emacs" src emacs-lisp
Previously, the default was to not include text in an org-mode
buffer before the first headline. From now on, the default it to
include it. If you like the old default better, customize the
variable org-export-skip-text-before-1st-heading
or set the value
on a per-file basis with
#+OPTIONS: skip:t
If you would like to share the Org setup between a number of files, you can now store in-buffer setup in a file and simply point to that file from each file that should read it. If you write in a buffer
#+SETUPFILE: "path/to/setup.org"
then this file will be scanned for in-buffer options like
#+STARTUP
, #+TITLE
, or #+OPTIONS
.
From now on, it makes no difference is you write #+STARTUP
or
#+startup
, to make these lines less imposing. Similarly for all
other in-buffer keywords.
As a new experimental feature, Org now supports completion of
structural elements like #+BEGIN_EXAMPLE
in a special way. It
work by typing, for example "
This is an experimental feature, please comment! See also below under org-mtags.el.
Startup visibility can now be influenced by properties
When Emacs opens an Org mode buffer, the outline visibility is set to a startup value that is taken from the variable
org-startup-folded
, or from a#+STARTUP
setting in the buffer. After this has happened, the buffer will now also be scanned for entries with aVISIBILITY
property. Wherever such a property is found, the corresponding subtree will get its visibility adjusted. Allowed values for the property are:
For example, I am using this for the huge Changes.org file that is the source for the list of visible changes you are reading right now. The top-most entry in this file always describes the changes in my current working version. The start of this section currently looks like this:
#+begin_src org ,* Version 6.03 , :PROPERTIES: , :VISIBILITY: content , :END: ,** Overview #+end_src
This was a proposal by Ben Alexander.
The command C-u C-u TAB
will switch back to the startup visibility
of the buffer.
Org now remembers the last 5 tasks that you clocked into, to make it easier to clock back into a task after interrupting it for another task.
C-u C-u C-c C-x C-i
(or C-u C-u I
from the agenda) willC-u C-c C-x C-i
(or C-u I
from the agenda) will offer aC-u C-c C-x C-j
to jump to any of theseWhen moving an entry using structure editing commands, archiving
commands, or the special subtree cut-and-paste commands C-c C-x
C-w
and C-c C-x C-y
, the running clock marker and all clock
history markers will be moved with the subtree. Now you can start a
clock in a remember buffer and keep the clock running while filing
the note away. See also the variable
`org-remember-clock-out-on-exit'.
bbdb-anniversaries
is now much faster, thanks to a new approach
using a hash for birthdays. Thanks to Thomas Baumann for a patch to
this effect.
Do people think any of these should become core?
#+BEGIN_EXAMPLE ... #+END_EXAMPLE
you can write
...
In fact, I myself find these easier to type and to look at. Also, it will allow you to more easily move text and files back and forth between Org and Muse. For a list of supported structure elements, see the commentary in the org-mtags.el file.
If you load this module and use the "
Many bug fixes again. Will this ever stop?
I had already given up on this, but Greg Chernev (who implemented noutline.el for XEmacs and in this way kept Org alive on XEmacs) has done it again and provided the patches to make column view work under XEmacs. There are still some problems, but the basics work and we will iron out the remaining issues, hopefully soon.
If any of the columns has a summary type defined, turning on column
view in the agenda will show summaries for these columns. Org will
first visit all relevant agenda files and make sure that the
computations of this property are up to date. This is also true for
the special CLOCKSUM
property. Org will then sum the values
displayed in the agenda. In the daily/weekly agenda, the sums will
cover a single day, in all other views they cover the entire
block. It is vital to realize that the agenda may show the same
entry multiple times (for example as scheduled and as a deadline),
and it may show two entries from the same hierarchy (for example a
parent and it's child). In these cases, the summation in the
agenda will lead to incorrect results because some values will count
double.
If you want to plan your work in a very detailed way, or if
you need to produce offers with quotations of the estimated
work effort, you may want to assign effort estimates to
entries. If you are also clocking your work, you may later
want to compare the planned effort with the actual working
time. Effort estimates can now be stored in a special
property Effort
, displayed side-to-side with clock sums,
and also be summed over a day, in order to show the planned
work load of a day. See the manual for more details.
Property searches can now choose a number of different operators for comparing values. These operators are `=', `<>', `<', `<=', `>', and `>='.
When the search term uses the operator with plain number like
+Effort>=2.7
, then the property value is converted to a number and
a numerical comparison takes place.
When the search term uses a string on the right hand side of the
operator, a string comparison is done: +PRIORITY<"C".
Finally, if the right hand side is enclosed in curly braces, a
regexp match is done: aaa={regexp}
. In this case you should use
only the `=' or `<>' operators, meaning "does match" or "does not
match", respectively.
This was a triggered with a request by Dan Davison.
If the value of the customization variable
org-agenda-text-search-extra-files
contains the symbol
agenda-archives
as the first element in the list, all archive
files of all agenda files will be added to the list of files to
search. This is relevant for the search view C-c a s
, as well as
for the agenda files multi-occur command C-c a /
.
There are new values for the :scope
parameter of a clock
table. This can now be file-with-archives
and
agenda-with-archives
, in order to collect information not only
from the current file or all agenda files, but also from all archive
files that are currently used by these files.
The options available for radio tables using orgtbl-mode have been expanded. You may use several reception points and formats for the same table, you may have special formatting in the last line of the table, and many table parameters may be functions, so that more general transformations are possible. Jason Riedy provided a patch for this, and he will hopefully come up with some examples. Thanks!
This is a new major release, mostly because of structural changes in Org. However, since this took a while, there is also a long list of small improvements and some new significant features.
In the distribution files as well as in the GIT repository, the lisp files are now located in a subdirectory "lisp", and the documentation files are located in a subdirectory "doc". If you are running Org directly from the unpacked distribution archive (zip or tar file, or GIT repository), you need to modify your settings for load-path accordingly.
In the distribution files as well as in the GIT repository, the lisp files are now located in a subdirectory "lisp", and the documentation files are located in a subdirectory "doc". If you are running Org directly from the unpacked distribution archive (zip or tar file, or GIT repository), you need to modify your settings for load-path accordingly.
Org mode has now a system for loading modules by simply configuring an option that lists all the modules you want to use. Customize the variable `org-modules'. That variable lists both modules that are part of the Org mode core (and in this way part of Emacs), and modules that are contributed packages. Contributed modules will only be available when you have installed them properly (most likely by downloading the distribution and adding /path/to/orgdir/contrib/lisp to your load path).
There is a new method to archive entries in the current file: By moving it to a sibling called the Archive Sibling. That sibling has the heading "Archive" and also carries the ARCHIVE tag. This can be a great way to do archiving inside a project, to get parts of the project out of the way and to wait with true archiving (moving to another file) until the entire project is done. Archiving to a sibling keeps much of the context, for example inherited tags and approximate tree position in tact.
The key binding for the is "C-c C-x A", and from the agenda buffer you can simply use "A".
Thanks to Ilya Shlyakhter for this rather clever idea.
This fascinating program allows a completely new viewing experience for web pages created from Org files. The same document can be viewed in different ways, and switching between the views as well as navigation uses single-key commands.
One of the view types is an Info-like interface where you can jump through the sections of the document with the `n' and `p' keys (and others). There is also a /folding/ interface where you can fold the document much like you can fold it in org-mode in Emacs, and cycle through the visibility both locally and globally.
To set this up, all you need to do is to make sure that org-infojs.el gets loaded (customize the variable org-modules to check). Then add this line to the buffer:
#+INFOJS_OPT: view:info
In that line, you can configure the initial view and other
settings. Available views are info
for the info-like
interface, and overview
, content
, and showall
for the
folding interface. See the manual for more details. The
JavaScript program is served from
https://orgmode.org/org-info.js, and your exported HTML files
will automatically get it from there. However, you may want
to be independent of the existence and stability of
orgmode.org and install a copy locally. Then you need to
change the path from which the script is loaded, either by
using something like
#+INFOJS_OPT: view:info path:../scripts/org-info.js
or by configuring the variable org-infojs-options
.
For details see the documentation provided by Sebastian Rose together with org-info.js.
Both these are based on requests by Ilya Shlyakhter.
The :block
parameter to the table can now look like any
of these:
| :block | meaning | |--------------+-----------------------| | 2008 | The entire year 2008 | | 2008-04 | The month April 2008 | | 2008-04-02 | The day April 2, 2008 | | 2008-W14 | ISO-Week 14 in 2008 | | today | Today | | today-5 | The day five days ago | | thisweek | The current week | | thisweek-2 | Two weeks ago | | thismonth | The current month | | thismonth-12 | Same month, last year | | lastmonth | Same as thismonth-1 |
What is more, you can now use the S-left
and S-right=
keys to shift the time block around. The cursor needs to
be in the =#+BEGIN: clocktable
line for this to work. If
the current block is today
, S-left
with switch to
yesterday. If the current block is 2008-W14
, =S-right=
will switch to the following week.
The agenda now shows the ISO week for the displayed dates, in
the form W08
for week 8.
The keys d
, w
, m
, and y
in the agenda view now accept
prefix arguments. Remember that in the agenda, you can
directly type a prefix argument by typing a number, no need
to press C-u
first. The prefix argument may be used to
jump directly to a specific day of the year, ISO week, month,
or year, respectively. For example, 32 d
jumps to February
1st, 9 w
to ISO week number 9. When setting day, week, or
month view, a year may be encoded in the prefix argument as
well. For example, 200712 w
will jump to week 12 in the
year 2007. If such a year specification has only one or two
digits, it will be mapped to the interval 1938-2037.
When entering a date at the date prompt, you may now also specify an ISO week. For example
w4 Monday of week 4 fri w4 Friday of week 4 w4-5 Same as above 2012 w4 fri Friday of week 4 in 2012. 2012-W04-5 Same as above
So far I have not implemented the effect of `org-read-date-prefer-future' on this functionality, because it seemed too magic for me. I'd appreciate comments on this issue: Should `org-read-date-prefer-future' also push dates into the next year if the week you are entering has already passed in the current year? For consistency I guess this should be the case, but I cannot quite wrap my head around it.
I hope but am not entirely convinced that this will behave sanely also during the first/last week of a year. Please test extensively and report back.
This was a request by Thomas Baumann.
The regexp option is also implemented for
org-use-property-inheritance
, so that you can now select
properties for inheritance my name.
org-entry-get
can be setThis was an omission in the earlier implementation, spotted by Wanrong Lin. Thanks!
%c
- Now always insert the head of the kill ring, never%x
- Insert the content of the X clipboard. This is the%^C
- This allows the user to choose between any of the%^L
- Like %^C
, but this inserts an org link using theThanks to James TD Smith for this patch.
:PROPERTIES: :TABLE_EXPORT_FILE: ~/xx.txt :TABLE_EXPORT_FORMAT: orgtbl-to-generic :splice t :sep "\t" :END:
Thanks to James TD Smith for this patch.
Thanks to James TD Smith for this patch.
M-RET
splits lines again`C-c a s' now invokes a special agenda view that can be used to search notes by keyword and regular expressions. In particular, it does not require a single regular expression or string to search for, but it can search for a number keywords or regexps that can occur in arbitrary sequence in the entry. The search knows the boundaries of an entry, can use simple Boolean logic and is reasonably fast. For example, the search string
+computer +wifi -ethernet -{8\.11[bg]}
will search for note entries that contain the keywords
computer
and wifi
, but not the keyword ethernet
, and
which are also not matched by the regular expression
"8\.11[bg]", meaning to exclude both 8.11b and 8.11g. If the
first character of the search string is an asterisk, the
search will only look at headlines - otherwise it will look
at the headine and the text below it, up to the next
(possibly sub-) heading.
The command searches all agenda files, and in addition the
files listed in org-agenda-text-search-extra-files
.
I find it very useful to define a custom command to do such a search only in a limited number of files (my notes files), like this:
("N" "Search notes" search "" ((org-agenda-files '("~/org/notes.org" "~/org/computer.org")) (org-agenda-text-search-extra-files nil)))
One possible application for this would be to have several templates all using the same selection letter, and choosing the right one based on context. For example, think of tasks describing a bug in a source code file. With the following configuration we make sure that the bug reports are filed into the appropriate sections of the target file.
#+begin_src emacs-lisp (setq org-remember-templates '(("Elisp" ?b "* %a\n\n%i%?" "~/bugs.org" "Elisp bugs" (emacs-lisp-mode)) ("C Bugs" ?b "* %a\n\n%i%?" "~/bugs.org" "C bugs" (cc-mode)))) #+end_src
See (info "(org)Remember templates") for details.
Based on proposals by Bastien.
Based on proposals by Bastien.
org-time-stamp-rounding-minutes
is now a listThis was a proposal by Adam Spiers.
** TODO Call Father DEADLINE: <2008-02-10 Sun ++1w> Marking this DONE will shift the date by at least one week, but also by as many weeks as it takes to get this date into the future. However, it stays on a Sunday, even if you called and marked it done on Saturday. ** TODO Check the batteries in the smoke detectors DEADLINE: <2005-11-01 Tue .+1m> Marking this DONE will shift the date to one month after today.
Proposed by Wanrong Lin and Rainer Stengle.
:link
parameter for the clocktable. When set,:content
parameter that is passed to the writerThis was a request by Kyle Sexton.
M-RET
canCustomize the variable org-M-RET-may-split-line
if you don't want
this command to split a line in the middle. The same variable also
influences line splitting in items and in tables.
=org-follow-link-hook=: runs after following a link =org-publish-before-export-hook=: runs before export =org-publish-after-export-hook=: runs after export
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:
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.
Bug fixes, in particular the long-hunted bug about wrong window positions after pressing SPACE in the agenda. Hopefully this is really fixed.
:step
for clocktable, to get daily reports.This is following a proposal by Piotr Zielinski.
:step
. This* 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'.
#+COLUMNS: %20ITEM %10Time_Estimate{:} %CLOCKSUMwill allow you to compare estimated times (as given in the Time_Estimate property) with the clocked times. This was a request by Bernt Hansen.
Minor fixes.
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.
%^{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.
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. 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.
(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'.
*a*
.(defun my-remember-template-n () (interactive) (org-remember ?n))
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))
(setq org-refile-targets '((nil . (:level . 2))))selects all level 2 headlines in the current buffer as targets. And
(setq org-refile-targets '((org-agenda-files . (:tag . "refile"))))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.
This is based on an idea and example implementation by Max Mikhanosha. Many thanks Max.
This was proposed by someone, but I have lost track who. Sorry, and thanks anyway.
%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.
(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))
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.
*/bold italic/*
is no longer allowed.*a*
.There have been several small but very useful additions to the date prompt.
| Org | Description | HTML |
|-----+------------------------------------+----------|
| \\
| double backslash followed by minus | |
| --
| two dashes (minuses) | – |
| ---
| three dashes (minuses) | — |
| ~...~ | three dots | … |
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.
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.Miscellaneous (much of it from Bastien)
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:
* Planning :PROPERTIES: :ID: planning-overview :END: [...] * The column view #+BEGIN: columnview :hlines 1 :id "planning-overview" #+END:
Use `C-c C-x r' to insert such a dynamic block, and you will be prompted for the ID.
(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")))
We are using a new routine for sorting entries, courtesy of John Wiegley. Many thanks to John.
There is now a
I am not sure if the class names are the best choice, let me know if there are more "canonical" choices.
Thanks to Mike Newman and Cezar for input, and in particular to Mike for his clearly formulated specification.
#+DRAWERS: HIDDEN STATE PROPERTIESThis 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.
:PROPERTIES: :LOGGING: nologging nologrepeat :END:
turns off all progress logging for the current entry and its children.
(global-set-key [f5] (lambda () (interactive) (org-remember "j")))Thanks to Richard G Riley for bringing this up.
:scope
parameter.* Tree with special properties :PROPERTIES: :CATEGORY: Examples :ARCHIVE: /some/special/file:: :END:
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
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
and I don't plan to remove this support soon, but I
encourage you to stop using them.
:scope
parameter that determines| value | scope | |---------+-------------------------------------------------| | nil | the current buffer or narrowed region | | file | the full current buffer | | subtree | the subtree where the clocktable is located | | treeN | the surrounding level N tree, for example tree3 | | tree | the surrounding level 1 tree | | agenda | all agenda files |
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.
14:00+2 means 14:00-16:00 2pm+2:30 means 14:00-16:30
Again, Nuutti Kotivuori's request.
#+SEQ_TODO: TODO(t) ORDERED(o@) INVOICE(i@) PAYED(p) | RECEIVED(r) #+STARTUP: lognotestate
only the states ORDERED and INVOICE will record a timestamp and a note.
This change does not effect XEmacs, nor Emacs 21 and 22.
#+SEQ_TODO: TODO(t) WAITING(w) | DONE(d) CANCELED(c)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.
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.
#+DATE: 15 November 2003If 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:
#+DATE: %Y/%m/%d %X
A Here is a configuration example:
(setq org-todo-keyword-faces '(("TODO" . org-warning) ("DEFERRED" . shadow) ("CANCELED" . (:foreground "blue" :weight bold :underline t))))
Org mode continue still use `org-todo' and `org-done' for keywords that have no specific face assigned.
#+SEQ_TODO: TODO(t) WAITING(w) | CANCELED(c) DONE(d) #+TAGS: @HOME(h) @OFFICE(o) @SHOP(s)
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.
(setq org-archive-save-context-info '(itags category))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.
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 proposals in this direction.
(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.
These additions lead to the exciting fact that the example from omni outliner posted by Scott Jaderholm can now be accurately reproduced by Org mode.
* This is a level 1 headline *this is bold text*
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.
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.
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.
The new concept of drawers 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
(setq org-drawers '("PROPERTIES" "HIDDEN"))
you can then create drawers like this:
:HIDDEN: here is some stuff that remains hidden unless TAB is pressed directly in that line :END:
The PROPERTIES drawer has special meaning for ORG-mode, it contains properties of an entry (see below).
:PROPNAME: This is the value of the propertyOrg 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'.
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.
LEVEL=3+BOSS+ASSIGNED="Hans"/WAITING
So here is an entry that will match:
*** WAITING Clean up the factory :BOSS: :PROPERTIES: :ASSIGNED: Hans :END:
You may also use a regular expression to match against a property value. For example, to find stuff assigned to Hans or Sarah, use
ASSIGNED={^\(Hans\|Sarah\)$}
* 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....).
Now we have defined three different sets of columns. If you switch to column view in the Family section, you will get a different table than if you do it in the Office section. However, if you switch to column view with the cursor on the People section, the table will cover all entries, but contain only the Name.
Column view does, for the time being, only work on Emacs. The XEmacs implementation needs a bit of work.
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.
Here is an example
| 1 | | 2 | | 3 | #+TBLFM: $1=@-1+1::@1$1=1
#+CONSTANTS: c=299792458. pi=3.14 eps=2.4e-6Minor changes
ARCHIVED: [2007-07-02 Mon 11:34]Thanks to J. David Boyd for constructive comments.
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!
<2007-06-18 Mon 17:33-18:23>
mv org_xemacs.el org.elThis 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.
Details
<2007-06-18 Mon 17:30-18:20>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.
This was proposed by Leo some time ago, and recently by Michael.
CLOCK: => 2:00Thanks to Scott Jaderholm for this proposal.
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
- item 1 - item 2 + item 2a + item 2b - item 3
When using TAB on every line in this list, the structure will change to
- item 1 - item 2 + item 2a + item 2b - item 3
So you need to change the level of the last line by hand, using promotion and demotion functions.
| | 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))
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.
Because HTML does not require closing
| N | N^2 | N^3 | N^4 | sqrt(n) | sqrt[4](N0 | |---+-----+-----+-----+---------+------------| | / | < | < | | < | |
here[1]
are now exported to HTML[1]This is a footnote
Thanks to Scott Jaderholm for this proposal and a detailed HTML example on how the exported text should look like.
<2007-05-16 Wed 12:30 +1w>
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!
*** The nerd club meets on 2nd Thursday of every month <%%(diary-float t 4 2)>
* Birthdays and similar stuff #+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
These entries must start at column 0 to be evaluated.
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.
#+PRIORITIES: 1 9 9Thanks to Dmitri Minaev for a patch to this effect.
#+begin_src emacs-lisp (add-hook 'org-load-hook (lambda () (define-key org-mode-map "\C-cf" 'org-emphasize))) #+end_src
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".
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.
This release is about exporting agenda views, to HTML, to postscript for printing, and to a special format (CSV) for further processing in scripts.
Minor bug fixes.
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 several empty lines in collapsed view, but I think this is counter-productive.
In Emacs 22, if you want to make full use of this, make sure that you have not set `outline-blank-line'.
I have not turned this turned this on by default, should I?
#+SEQ_TODO: TODO VERIFY | DONE DELEGATED
The difference to the proposal discussed on the mailing list (and which is also works!)
#+SEQ_TODO: TODO VERIFY | DONE #+SEQ_TODO: | CANCELED
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- to get to the special states. I guess both ideas can be useful - I am leaning toward using the latter.
#+begin_src emacs-lisp (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. )) #+end_src
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.
| Command | | Old TTY | New TTY | | org-..... | Main Key | Replacement | Replacement | |-------------------+-----------+---------------+---------------| | shiftleft | S-left | C-c C-x left | C-c left | | shiftright | S-right | C-c C-x right | C-c right | | shiftup | S-up | C-c C-x up | C-c up | | shiftdown | S-down | C-c C-x down | C-c down | | shiftcontrolleft | C-S-left | | C-c C-x left | | shiftcontrolright | C-s-right | | C-c C-x right |
This time the changes affect the following areas:
#+SEQ_TODO: TODO #+SEQ_TODO: PROGRESS #+SEQ_TODO: DONE
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.
#+SEQ_TODO: TODO DONE #+SEQ_TODO: REPORT BUG KNOWNCAUSE RESOLVED #+TYP_TODO: Fred Laura Peter Me OK
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.
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.
S-right and S-left allow to select any keyword, so they move from DONE to REPORT and from RESOLVED to Fred.
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.
Thanks to Rick Moynihan for triggering this development.
#+OPTION: skip:nil
(setq org-export-sub-superscript '{})or by using
#+OPTIONS: ^:{}Thanks to Eddward DeVilla for this idea.
Thanks to Mike Newman for triggering this development.
Relative references like @-3$-2 or @II..III continue to use the internal format.
#+OPTIONS: H:4 toc:2
This does not 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.
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.
Email from NAME: SUBJECTIf you configure the variable `org-from-is-user-regexp' correctly, then for email you sent this will actually change to
Email to NAME: SUBJECTThe 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.
[[bracket links]]
in the agenda are active just as in org-mode buffers.[[link][description]]
format by default.[...]