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
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
Emacs software by Carsten Dominik
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_QUOTE Everything should be made as simple as possible, but not any simpler -- Albert Einstein #+BEGIN_QUOTE
which will render as
Everything should be made as simple as possible, but not any simpler – Albert Einstein
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 emacs-lisp (defun org-xor (a b) "Exclusive or." (if a (not b) b)) #+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 http://orgmode.org/Changes.html).
(defun org-xor (a b) "Exclusive or." (if a (not b) b))
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 "<e" and then pressing TAB, on
an otherwise empty line. "<e" will expand into a complete
EXAMPLE template, with the cursor positioned in the middle.
Currently supported templates are:
<s #+begin_src <e #+begin_example <q #+begin_quote <v #+begin_verse <l #+begin_latex <L #+latex: <h #+begin_html <H #+html: <a #+begin_ascii <i #+include
This is an experimental feature, please comment! See also below under org-mtags.el.
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 a VISIBILITY 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:
* Version 6.03 :PROPERTIES: :VISIBILITY: content :END: ** Overview
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) will
clock into that task and mark it as current default task.
C-u C-c C-x C-i (or C-u I from the agenda) will offer a
list of recently clocked tasks, including the default task,
for selection. d selects the default task, i selects
the task that was interrupted by the task that is currently
being clocked. 1,… selects a recent task. When you
select a task, you will be clocked into it.
C-u C-c C-x C-j to jump to any of these
tasks.
When 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?
<lisp> tag
of Emacs Wiki and Muse.
#+BEGIN_EXAMPLE ... #+END_EXAMPLEyou can write
<example> ... </example>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 file commentary in the file org-mtags.el.
If you load this module and use the "<i" etc completion described above, the Muse form will automatically be inserted.
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
http://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.
org-agenda-start-with-clock report-mode. To modify the
properties of the table, in particular the :maxlevel
depth, configure org-agenda-clockreport-parameter-plist.
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.
org-use-tag-inheritance. This
variable may now be a regular expression or a list to
select the inherited tags. Thanks to Michael Ekstrand for
this excellent proposal.
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 set
to the symbol selective. If this is the case, then the
value of the property will be retrieved using inheritance
if and only if the setting in
org-use-property-inheritance selects the property for
inheritance.
org-agenda-date and
org-agenda-date-weekend. Both these faces are initially
similar to the org-agenda-structure face, but you can
customize them freely.
This was an omission in the earlier implementation, spotted by Wanrong Lin. Thanks!
org-directory.
%c - Now always insert the head of the kill ring, never
the X clipboard.
%x - Insert the content of the X clipboard. This is the
first non-empty value from the PRIMARY, SECONDARY and
CLIPBOARD X clipboards.
%^C - This allows the user to choose between any of the
clipboard values available, the kill ring head, and the
initial region if set.
%^L - Like %^C, but this inserts an org link using the
selected value.
Thanks to James TD Smith for this patch.
org-table-export-default-format. You can use properties
TABLE_EXPORT_FILE and TABLE_EXPORT_FORMAT to specify the
file name to which the export should go, and a local
format. For example:
: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.
org-todo-keywords, or in the #+TODO line. Use
the "o" key when sorting with C-c ^.
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)))
t or nil. If it is a list of major-mode, the
template will be available only when org-remember is
called from a buffer in one of these modes. If it is a
function, the template will be offered only if the function
returns `t' when called in the current buffer. A value of
t or nil for this element means select this template in
any context.
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.
(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))))
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 list of two values. The first applies when creating a new
time stamp. The second applies when modifying a timestamp
with S-up/down. The default for this new task is 5 minutes,
but 15 may also be a very good value for many people. If
S-up/down is used on a time stamp where the minute part is
not compatible with this granularity it will be made so.
You can bypass this by using a prefix argument to exactly
specify the number of minutes to shift.
This 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, the headlines listed in the table will be links to the
original headlines.
:content parameter that is passed to the
writer function of the dynamic block. Use this parameter
to pass the previous content of the block to the writer
function, in case you want to make the outcome dependent on
the previous content.
This was a request by Kyle Sexton.
M-RET can again be used to split a line so that the rest
of the line becomes the new heading. However, if you do
this in a heading containing tags, the tags will stay in the
old line.
Customize 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
parameter can be `day' or `week' and will result in separate
tables for each day or week in the requested time interval.
This was triggered by a proposal by Sacha Chua in her blog.
ARCHIVE_OLPATH. This property contains the "path" in the
outline tree to the archived entry, as it was in the
original file. For example, archiving Fix the door in the
following hierarchy
* Tasks ** HOME *** Garage **** Fix the door
will file is with the following property
:ARCHIVE_PATH: Task/HOME/Garage
Note that you can configure (i.e. limit) the information that gets stored upon archiving with the variable `org-archive-save-context-info'.
#+COLUMNS: %20ITEM %10Time_Estimate{:} %CLOCKSUM
will allow you to compare estimated times (as given in the Time_Estimate property) with the clocked times. This was a request by Bernt Hansen.
*Remember* buffer. But if you
have chosen (e.g. by pressing `C-u C-c C-c') to
interactively select the filing location (file and
headline), the refile interface will be used instead. I am
excited about this change, because the `org-goto' interface
is basically a failure, at least for this application. Note
that in any case the refile interface has to be configured
first by customizing `org-refile-targets'.
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'.
(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.
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.
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 <div>-based structure in exported HTML.
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 PROPERTIES
This will define the drawers :HIDDEN: and :STATE:. The :PROPERTY: drawer should always be part of this list, or your properties will not be folded away. Thanks to Richard G. Riley for this proposal.
: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
the range in the file from which clock entries should be
taken. This can be anything from the local subtree to the
entire buffer to even the full list of agenda files. Legal
values are:
| 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 2003
If you want to use the date/time when the file was created, use a format string that will be interpreted by `format-time-string', for example:
#+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.