mirror of
https://git.savannah.gnu.org/git/emacs/org-mode.git
synced 2025-01-03 11:33:46 +00:00
Update version numbers.
This commit is contained in:
parent
1e1cc09504
commit
d357e9d3ac
@ -1,555 +0,0 @@
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
|
||||
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml"
|
||||
lang="en" xml:lang="en">
|
||||
<head>
|
||||
<title>Org-mode Frequently Asked Questions</title>
|
||||
<meta http-equiv="Content-Type" content="text/html;charset=iso-8859-1"/>
|
||||
<meta name="generator" content="Org-mode"/>
|
||||
<meta name="generated" content="2007/09/10 07:06:01"/>
|
||||
<meta name="author" content="Carsten Dominik"/>
|
||||
<link rel=stylesheet href="freeshell2.css" type="text/css"> <style type="text/css"> .tag { color: red; font-weight:bold}</style>
|
||||
</head><body>
|
||||
<h1 class="title">Org-mode Frequently Asked Questions</h1>
|
||||
<h2>Table of Contents</h2>
|
||||
<ul>
|
||||
<li><a href="#sec-1">1 General</a>
|
||||
<ul>
|
||||
<li><a href="#sec-2">1.1 Use features in other modes</a></li>
|
||||
<li><a href="#sec-3">1.2 Visibility cycling in Outline-mode and Outline-minor-mode</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a href="#sec-4">2 Errors</a>
|
||||
<ul>
|
||||
<li><a href="#sec-5">2.1 <code>(wrong-type-argument keymapp nil)</code></a></li>
|
||||
<li><a href="#sec-6">2.2 CUA mode does not work with Org-mode</a></li>
|
||||
<li><a href="#sec-7">2.3 <code>winddmove.el</code> does not work with Org-mode.</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a href="#sec-8">3 Setup and Structure</a>
|
||||
<ul>
|
||||
<li><a href="#sec-9">3.1 Org-mode as default mode</a></li>
|
||||
<li><a href="#sec-10">3.2 Get rid of extra stars in outline</a></li>
|
||||
<li><a href="#sec-11">3.3 Two windows on same Org-mode file</a></li>
|
||||
<li><a href="#sec-12">3.4 Insert empty lines before new headings and plain list items</a></li>
|
||||
<li><a href="#sec-13">3.5 Amount of context in sparse trees</a></li>
|
||||
<li><a href="#sec-14">3.6 Stacking calls to org-occur</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a href="#sec-15">4 Hyperlinks</a>
|
||||
<ul>
|
||||
<li><a href="#sec-16">4.1 Confirmation for shell and elisp links</a></li>
|
||||
<li><a href="#sec-17">4.2 Use RET or TAB to follow a link</a></li>
|
||||
<li><a href="#sec-18">4.3 Clicking on a link without activating it</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a href="#sec-19">5 Export</a>
|
||||
<ul>
|
||||
<li><a href="#sec-20">5.1 Make TODO entries items, not headlines in HTML export</a></li>
|
||||
<li><a href="#sec-21">5.2 Export only a subtree</a></li>
|
||||
<li><a href="#sec-22">5.3 How to import org-mode calendar data into Mac OSX ical</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a href="#sec-23">6 Tables</a>
|
||||
<ul>
|
||||
<li><a href="#sec-24">6.1 #ERROR fields in tables</a></li>
|
||||
<li><a href="#sec-25">6.2 Unwanted new lines in table</a></li>
|
||||
<li><a href="#sec-26">6.3 Automatic detection of formulas</a></li>
|
||||
<li><a href="#sec-27">6.4 Change indentation of a table</a></li>
|
||||
<li><a href="#sec-28">6.5 Performance issues with table alignment</a></li>
|
||||
<li><a href="#sec-29">6.6 Performance issues with table calculation</a></li>
|
||||
<li><a href="#sec-30">6.7 Incrementing numbers</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a href="#sec-31">7 Agenda</a>
|
||||
<ul>
|
||||
<li><a href="#sec-32">7.1 Include Org-mode agenda into Emacs diary</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<h2 id="sec-1">1 General</h2>
|
||||
|
||||
|
||||
<h3 id="sec-2">1.1 Use features in other modes</h3>
|
||||
|
||||
<p><b>I would like to use editing features of org-mode in other modes, is this possible?</b>
|
||||
</p>
|
||||
<p>
|
||||
Not really. For tables there is <code>orgtbl-mode</code> which implements the
|
||||
table editor as a minor mode. For other features you need to switch to
|
||||
Org-mode temporarily, or prepare text in a different buffer.
|
||||
</p>
|
||||
|
||||
|
||||
<h3 id="sec-3">1.2 Visibility cycling in Outline-mode and Outline-minor-mode</h3>
|
||||
|
||||
|
||||
<p>
|
||||
<b>Can I get the visibility-cycling features in outline-mode and outline-minor-mode?</b>
|
||||
</p>
|
||||
<p>
|
||||
Yes, these functions are written in a way that they are independent of
|
||||
the outline setup. The following setup provides standard Org-mode
|
||||
functionality in outline-mode on <code>TAB</code> and <code>S-TAB</code>. For
|
||||
outline-minor-mode, we use <code>C-TAB</code> instead of <code>TAB</code>,
|
||||
because <code>TAB</code> usually has mode-specific tasks.
|
||||
</p>
|
||||
<p>
|
||||
<pre>
|
||||
(add-hook 'outline-minor-mode-hook
|
||||
(lambda ()
|
||||
(define-key outline-minor-mode-map [(control tab)] 'org-cycle)
|
||||
(define-key outline-minor-mode-map [(shift tab)] 'org-global-cycle)))
|
||||
(add-hook 'outline-mode-hook
|
||||
(lambda ()
|
||||
(define-key outline-mode-map [(tab)] 'org-cycle)
|
||||
(define-key outline-mode-map [(shift tab)] 'org-global-cycle)))
|
||||
</pre>
|
||||
</p>
|
||||
<p>
|
||||
Or check out <i>outline-magic.el</i>, which does this and also provides
|
||||
promotion and demotion functionality. <i>outline-magic.el</i> is
|
||||
available at <a href="http://www.astro.uva.nl/~dominik/Tools/OutlineMagic">Outline Magic</a>.
|
||||
</p>
|
||||
|
||||
<h2 id="sec-4">2 Errors</h2>
|
||||
|
||||
|
||||
<h3 id="sec-5">2.1 <code>(wrong-type-argument keymapp nil)</code></h3>
|
||||
|
||||
<p><b>When I try to use Org-mode, I always get the error message @code{(wrong-type-argument keymapp nil)}</b>
|
||||
</p>
|
||||
<p>
|
||||
This is a conflict with an outdated version of the <i>allout.el</i>, see
|
||||
the <a href="http://staff.science.uva.nl/~dominik/Tools/org/org.html#Conflicts">Conflicts</a> section in the manual
|
||||
</p>
|
||||
|
||||
<h3 id="sec-6">2.2 CUA mode does not work with Org-mode</h3>
|
||||
|
||||
|
||||
<p>
|
||||
<b>Org-mode takes over the S-cursor keys. I also want to use CUA-mode, is there a way to fix this conflict?</b>
|
||||
</p>
|
||||
<p>
|
||||
Yes, see the <a href="http://staff.science.uva.nl/~dominik/Tools/org/org.html#Conflicts">Conflicts</a> section of the manual.
|
||||
</p>
|
||||
|
||||
<h3 id="sec-7">2.3 <code>winddmove.el</code> does not work with Org-mode.</h3>
|
||||
|
||||
|
||||
<p>
|
||||
<b>Org-mode takes over the S-cursor keys. I also want to use windmove.el, is there a way to fix this conflict?</b>
|
||||
</p>
|
||||
<p>
|
||||
Yes, see the <a href="http://staff.science.uva.nl/~dominik/Tools/org/org.html#Conflicts">Conflicts</a> section of the manual.
|
||||
</p>
|
||||
|
||||
<h2 id="sec-8">3 Setup and Structure</h2>
|
||||
|
||||
|
||||
<h3 id="sec-9">3.1 Org-mode as default mode</h3>
|
||||
|
||||
|
||||
<p>
|
||||
<b>Org-mode seems to be a useful default mode for the various README files I have scattered through my directories</b>. <b>How do I turn it on for all README files?</b>
|
||||
</p>
|
||||
<p>
|
||||
Add the following to your .emacs file:
|
||||
</p>
|
||||
<p>
|
||||
<pre>
|
||||
(add-to-list 'auto-mode-alist '("README$" . org-mode))
|
||||
</pre>
|
||||
</p>
|
||||
<p>
|
||||
You can even make it the default mode for any files with unspecified
|
||||
mode using
|
||||
</p>
|
||||
<p>
|
||||
<pre>
|
||||
(setq default-major-mode 'org-mode)
|
||||
</pre>
|
||||
</p>
|
||||
|
||||
<h3 id="sec-10">3.2 Get rid of extra stars in outline</h3>
|
||||
|
||||
|
||||
<p>
|
||||
<b>All these stars are driving me mad, I just find the Emacs outlines unreadable. Can't you just put white space and a single star as a starter for headlines?</b>
|
||||
</p>
|
||||
<p>
|
||||
See the section <a href="http://staff.science.uva.nl/~dominik/Tools/org/org.html#Clean%20outline%20view">Clean outline view</a> in the manual.
|
||||
</p>
|
||||
|
||||
<h3 id="sec-11">3.3 Two windows on same Org-mode file</h3>
|
||||
|
||||
<p><b>I would like to have two windows on the same Org-mode file, but with different outline visibility. Is that possible?</b>
|
||||
</p>
|
||||
<p>
|
||||
You may use <i>indirect buffers</i> which do exactly this. See the
|
||||
documentation on the command <code>make-indirect-buffer</code>.
|
||||
</p>
|
||||
|
||||
<h3 id="sec-12">3.4 Insert empty lines before new headings and plain list items</h3>
|
||||
|
||||
|
||||
<p>
|
||||
<b>I would like to have an empty line before each newly inserted headline, but not before each newly inserted plain-list item</b>.
|
||||
</p>
|
||||
<p>
|
||||
<pre>
|
||||
(setq org-blank-before-new-entry
|
||||
'((heading . t) (plain-list-item . nil))
|
||||
</pre>
|
||||
</p>
|
||||
|
||||
|
||||
<h3 id="sec-13">3.5 Amount of context in sparse trees</h3>
|
||||
|
||||
|
||||
<p>
|
||||
*Sparse tree show the headline hierarchy above each match, and also
|
||||
the headline following a match. I'd like to construct more compact
|
||||
trees, with less context.*
|
||||
</p>
|
||||
<p>
|
||||
Take a look at the variables <code>org-show-hierarchy-above</code> and
|
||||
<code>org-show-following-headline</code>.
|
||||
</p>
|
||||
|
||||
<h3 id="sec-14">3.6 Stacking calls to org-occur</h3>
|
||||
|
||||
|
||||
<p>
|
||||
<b>Each call to org-occur starts again from OVERVIEW and exposes only the matches of the current call. I'd like to combine the effect of several calls</b>.
|
||||
</p>
|
||||
<p>
|
||||
You can construct a regular expression that matches all targets you
|
||||
want. Alternatively, use a <code>C-u</code> prefix with the second and any
|
||||
further calls to <code>org-occur</code> to keep the current visibility and
|
||||
highlighting in addition to the new ones.
|
||||
</p>
|
||||
|
||||
<h2 id="sec-15">4 Hyperlinks</h2>
|
||||
|
||||
|
||||
|
||||
<h3 id="sec-16">4.1 Confirmation for shell and elisp links</h3>
|
||||
|
||||
|
||||
<p>
|
||||
<b>When I am executing shell/elisp links I always get a confirmation prompt and need to type "yes RET", that's 4 key presses! Can I get rid of this?</b>
|
||||
</p>
|
||||
<p>
|
||||
The confirmation is there to protect you from unwantingly execute
|
||||
potentially dangerous commands. For example, imagine a link
|
||||
<pre>
|
||||
[[shell:rm -rf ~/*][ Google Search]]
|
||||
</pre>
|
||||
</p>
|
||||
<p>
|
||||
In an Org-mode buffer, this command would look like <i>Google Search</i>,
|
||||
but really it would remove your home directory. If you wish, you can
|
||||
make it easier to respond to the query by setting
|
||||
</p>
|
||||
<p>
|
||||
<pre>
|
||||
(setq org-confirm-shell-link-function 'y-or-n-p
|
||||
org-confirm-elisp-link-function 'y-or-n-p).
|
||||
</pre>
|
||||
</p>
|
||||
<p>
|
||||
Then a single keypress will be enough to confirm those links. It is
|
||||
also possible to turn off this check entirely, but I strongly recommend
|
||||
against this. Be warned.
|
||||
</p>
|
||||
|
||||
<h3 id="sec-17">4.2 Use RET or TAB to follow a link</h3>
|
||||
|
||||
|
||||
<p>
|
||||
<b>From other packages like Emacs-wiki, I am used to follow links with <code>RET</code> when the cursor is on the link. Is this also possible in org-mode?</b>
|
||||
</p>
|
||||
<p>
|
||||
Yes, and you may also use TAB.
|
||||
</p>
|
||||
<p>
|
||||
<pre>
|
||||
(setq org-return-follows-link t)
|
||||
(setq org-tab-follows-link t)
|
||||
</pre>
|
||||
</p>
|
||||
|
||||
<h3 id="sec-18">4.3 Clicking on a link without activating it</h3>
|
||||
|
||||
|
||||
<p>
|
||||
<b>Each time I click inside a link in order to set point to this location, Org-mode actually follows the link</b>
|
||||
</p>
|
||||
<p>
|
||||
Activating links with <code>mouse-1</code> is a new feature in Emacs 22, to make
|
||||
link behavior similar to other applications like web browsers. If you
|
||||
hold the mouse button down a bit longer, the cursor will be set
|
||||
without following the link. If you cannot get used to this behavior,
|
||||
you can (as in Emacs 21) use <code>mouse-2</code> to follow links and turn off
|
||||
link activation for <code>mouse-1</code> with
|
||||
</p>
|
||||
<p>
|
||||
<pre>
|
||||
(setq org-mouse-1-follows-link nil)
|
||||
</pre>
|
||||
</p>
|
||||
|
||||
|
||||
<h2 id="sec-19">5 Export</h2>
|
||||
|
||||
|
||||
<h3 id="sec-20">5.1 Make TODO entries items, not headlines in HTML export</h3>
|
||||
|
||||
|
||||
<p>
|
||||
<b>When I export my TODO list, every TODO item becomes a separate section. How do I enforce these items to be exported as an itemized list?</b>
|
||||
</p>
|
||||
<p>
|
||||
If you plan to use ASCII or HTML export, make sure things you want to
|
||||
be exported as item lists are level 4 at least, even if that does mean
|
||||
there is a level jump. For example:
|
||||
</p>
|
||||
<p>
|
||||
<pre>
|
||||
* Todays top priorities
|
||||
**** TODO write a letter to xyz
|
||||
**** TODO Finish the paper
|
||||
**** Pick up kids at the school
|
||||
</pre>
|
||||
</p>
|
||||
<p>
|
||||
Alternatively, if you need a specific value for the heading/item
|
||||
transition in a particular file, use the <code>#+OPTIONS</code> line to
|
||||
configure the H switch.
|
||||
</p>
|
||||
<p>
|
||||
<pre>
|
||||
#+OPTIONS: H:2; ...
|
||||
</pre>
|
||||
</p>
|
||||
|
||||
<h3 id="sec-21">5.2 Export only a subtree</h3>
|
||||
|
||||
|
||||
<p>
|
||||
<b>I would like to export only a subtree of my file to HTML. How?</b>
|
||||
</p>
|
||||
<p>
|
||||
If you want to export a subtree, mark the subtree as region and then
|
||||
export. Marking can be done with <code>C-c @ C-x C-x</code>, for example.
|
||||
</p>
|
||||
|
||||
<h3 id="sec-22">5.3 How to import org-mode calendar data into Mac OSX ical</h3>
|
||||
|
||||
|
||||
<p>
|
||||
<b>I would like my iCal program on Mac OSX to import the iCalendar file produced by Org-mode. How?</b>
|
||||
</p>
|
||||
<p>
|
||||
<i>This is for OSX 10.3, see below for 10.4:</i> When using iCal under
|
||||
Apple MacOS X, you can create a new calendar <i>OrgMode</i> (the default
|
||||
name for the calendar created by <code>C-c C-e c</code>, see the variables
|
||||
<code>org-icalendar-combined-name</code> and
|
||||
<code>org-combined-agenda-icalendar-file</code>). Then set Org-mode to overwrite
|
||||
the corresponding file <i>~/Library/Calendars/OrgMode.ics</i>. You may
|
||||
even use AppleScript to make iCal re-read the calendar files each time
|
||||
a new version of <i>OrgMode.ics</i> is produced. Here is the setup needed
|
||||
for this:
|
||||
</p>
|
||||
<p>
|
||||
<pre>
|
||||
(setq org-combined-agenda-icalendar-file
|
||||
"~/Library/Calendars/OrgMode.ics")
|
||||
(add-hook 'org-after-save-iCalendar-file-hook
|
||||
(lambda ()
|
||||
(shell-command
|
||||
"osascript -e 'tell application \"iCal\" to reload calendars'")))
|
||||
</pre>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
For Mac OS X 10.4, you need to write the ics file to
|
||||
<code>/Library/WebServer/Documents/</code> and then subscribe iCalendar to
|
||||
<code>http: //localhost/orgmode.ics</code>
|
||||
</p>
|
||||
|
||||
<h2 id="sec-23">6 Tables</h2>
|
||||
|
||||
|
||||
<h3 id="sec-24">6.1 #ERROR fields in tables</h3>
|
||||
|
||||
|
||||
<p>
|
||||
<b>One of my table columns has started to fill up with <code>#ERROR</code>. What is going on?</b>
|
||||
</p>
|
||||
<p>
|
||||
Org-mode tried to compute the column from other fields using a
|
||||
formula stored in the <code>#+TBLFM:</code> line just below the table, and
|
||||
the evaluation of the formula fails. Fix the fields used in the
|
||||
formula, or fix the formula, or remove it!
|
||||
</p>
|
||||
|
||||
<h3 id="sec-25">6.2 Unwanted new lines in table</h3>
|
||||
|
||||
|
||||
<p>
|
||||
<b>When I am in the last column of a table and just above a horizontal line in the table, pressing TAB creates a new table line before the horizontal line</b>. <b>How can I quickly move to the line below the horizontal line instead?</b>
|
||||
</p>
|
||||
<p>
|
||||
Press <code>down</code> (to get on the separator line) and then <code>TAB</code>.
|
||||
Or configure the variable
|
||||
</p>
|
||||
<p>
|
||||
<pre>
|
||||
(setq org-table-tab-jumps-over-hlines t)
|
||||
</pre>
|
||||
</p>
|
||||
|
||||
<h3 id="sec-26">6.3 Automatic detection of formulas</h3>
|
||||
|
||||
<p><b>I need to use fields in my table that start with "=", and each time I enter such a field, Org-mode thinks this is a formula</b>.
|
||||
</p>
|
||||
<p>
|
||||
With the setting
|
||||
</p>
|
||||
<p>
|
||||
<pre>
|
||||
(setq org-table-formula-evaluate-inline nil)
|
||||
</pre>
|
||||
</p>
|
||||
<p>
|
||||
this will no longer happen. You can still use formulas using the
|
||||
commands <tt>C-c =</tt> and <tt>C-u C-c =</tt>
|
||||
</p>
|
||||
|
||||
|
||||
<h3 id="sec-27">6.4 Change indentation of a table</h3>
|
||||
|
||||
<p><b>How can I change the indentation of an entire table without fixing every line by hand?</b>
|
||||
</p>
|
||||
<p>
|
||||
The indentation of a table is set by the first line. So just fix the
|
||||
indentation of the first line and realign with <code>TAB</code>.
|
||||
</p>
|
||||
|
||||
<h3 id="sec-28">6.5 Performance issues with table alignment</h3>
|
||||
|
||||
<p><b>I have a huge table in a file, and the automatic realign of tables is just taking too long. What can I do?</b>
|
||||
</p>
|
||||
<p>
|
||||
Either split the table into several by inserting an empty line every
|
||||
100 lines or so. Or turn off the automatic re-align with
|
||||
</p>
|
||||
<p>
|
||||
<pre>
|
||||
(setq org-table-automatic-realign nil)
|
||||
</pre>
|
||||
</p>
|
||||
<p>
|
||||
After this the only way to realign a table is to press <code>C-c C-c</code>. It
|
||||
will no longer happen automatically, removing the corresponding delays
|
||||
during editing.
|
||||
</p>
|
||||
|
||||
<h3 id="sec-29">6.6 Performance issues with table calculation</h3>
|
||||
|
||||
<p><b>I have a complex table with lots of formulas, and recomputing the table takes rather long. What can I do?</b>
|
||||
</p>
|
||||
<p>
|
||||
Nothing, really. The spreadsheet in org is mostly done to make
|
||||
calculations possible, not so much to make them fast. Since Org-mode
|
||||
is firmly committed to the ASCII format, nothing is stopping you from
|
||||
editing the table by hand. Therefore, there is no internal
|
||||
representation of the data. Each time Org-mode starts a computation,
|
||||
it must scan the table for special lines, find the fields etc. This
|
||||
is slow. Furthermore, Calc is slow compared to hardware computations.
|
||||
To make this work with normal editing, recalculation is not happening
|
||||
automatically, or only for the current line, so that the long wait for
|
||||
a full table iteration only happens when you ask for it.
|
||||
</p>
|
||||
<p>
|
||||
So for really complex tables, moving to a "real" spreadsheet may still
|
||||
be the best option.
|
||||
</p>
|
||||
<p>
|
||||
That said, there are some ways to optimize things in Org-mode, and I
|
||||
have been thinking about moving a bit further down this line.
|
||||
However, for my applications this has so far not been an issue at all.
|
||||
If you have a good case,you could try to convince me.
|
||||
</p>
|
||||
|
||||
<h3 id="sec-30">6.7 Incrementing numbers</h3>
|
||||
|
||||
<p><b>When I press <code>S-RET</code> in a table field to copy its value down, the content is not copied as is, but it is increased by one. Is that a bug or a feature</b>
|
||||
</p>
|
||||
<p>
|
||||
Well, it is <i>supposed</i> to be a feature, to make it easy to create a
|
||||
column with increasing numbers. If this gets into your way, turn it
|
||||
off with
|
||||
</p>
|
||||
<p>
|
||||
<pre>
|
||||
(setq org-org-table-copy-increment nil)
|
||||
</pre>
|
||||
</p>
|
||||
|
||||
<h2 id="sec-31">7 Agenda</h2>
|
||||
|
||||
|
||||
<h3 id="sec-32">7.1 Include Org-mode agenda into Emacs diary</h3>
|
||||
|
||||
<p><b>Is it possible to include entries from org-mode files into my emacs diary?</b>
|
||||
</p>
|
||||
<p>
|
||||
Since the org-mode agenda is much more powerful and can contain the
|
||||
diary, you should think twice before deciding to do this. If you
|
||||
insist, however, integrating Org-mode information into the diary is
|
||||
possible. You need to turn on <i>fancy diary display</i> by setting in
|
||||
.emacs:
|
||||
</p>
|
||||
<p>
|
||||
<pre>
|
||||
(add-hook 'diary-display-hook 'fancy-diary-display)
|
||||
</pre>
|
||||
</p>
|
||||
<p>
|
||||
Then include the following line into your ~/diary file, in
|
||||
order to get the entries from all files listed in the variable
|
||||
<code>org-agenda-files</code>
|
||||
</p>
|
||||
<p>
|
||||
<pre>
|
||||
&%%(org-diary)
|
||||
</pre>
|
||||
You may also select specific files with
|
||||
</p>
|
||||
<p>
|
||||
<pre>
|
||||
&%%(org-diary) ~/path/to/some/org-file.org
|
||||
&%%(org-diary) ~/path/to/another/org-file.org
|
||||
</pre>
|
||||
</p>
|
||||
<p>
|
||||
If you now launch the calendar and press <tt>d</tt> to display a diary, the
|
||||
headlines of entries containing a timestamp, date range, schedule, or
|
||||
deadline referring to the selected date will be listed. Just like
|
||||
Org-mode's agenda view, the diary for <i>today</i> contains additional
|
||||
entries for overdue deadlines and scheduled items. See also the
|
||||
documentation of the <code>org-diary</code> function. Under XEmacs, it is
|
||||
not possible to jump back from the diary to the org, this works only in
|
||||
the agenda buffer.
|
||||
</p>
|
||||
|
||||
<p class="author"> Author: Carsten Dominik
|
||||
<a href="mailto:carsten.dominik@gmail.com"><carsten.dominik@gmail.com></a>
|
||||
</p>
|
||||
<p class="date"> Date: 2007/09/10 07:06:01</p>
|
||||
</body>
|
||||
</html>
|
@ -1,403 +0,0 @@
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
|
||||
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml"
|
||||
lang="en" xml:lang="en">
|
||||
<head>
|
||||
<title>Org-Mode Homepage</title>
|
||||
<meta http-equiv="Content-Type" content="text/html;charset=iso-8859-1"/>
|
||||
<meta name="generator" content="Org-mode"/>
|
||||
<meta name="generated" content="2008/01/18 12:46:32"/>
|
||||
<meta name="author" content="Carsten Dominik"/>
|
||||
<style type="text/css">
|
||||
html {
|
||||
font-family: Times, serif;
|
||||
font-size: 12pt;
|
||||
}
|
||||
.title { text-align: center; }
|
||||
.todo { color: red; }
|
||||
.done { color: green; }
|
||||
.timestamp { color: grey }
|
||||
.timestamp-kwd { color: CadetBlue }
|
||||
.tag { background-color:lightblue; font-weight:normal }
|
||||
.target { background-color: lavender; }
|
||||
pre {
|
||||
border: 1pt solid #AEBDCC;
|
||||
background-color: #F3F5F7;
|
||||
padding: 5pt;
|
||||
font-family: courier, monospace;
|
||||
}
|
||||
table { border-collapse: collapse; }
|
||||
td, th {
|
||||
vertical-align: top;
|
||||
<!--border: 1pt solid #ADB9CC;-->
|
||||
}
|
||||
</style>
|
||||
</head><body>
|
||||
<h1 class="title">Org-Mode Homepage</h1>
|
||||
<div id="table-of-contents">
|
||||
<h2>Table of Contents</h2>
|
||||
<ul>
|
||||
<li><a href="#sec-1">Org - an Emacs Mode for Notes and Project Planning</a></li>
|
||||
<li><a href="#sec-2">Current Version (5.19) and Compatibility</a></li>
|
||||
<li><a href="#sec-3">Downloads</a></li>
|
||||
<li><a href="#sec-4">Documentation</a>
|
||||
<ul>
|
||||
<li><a href="#sec-5">Manual and Reference card</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a href="#sec-6">Links</a>
|
||||
<ul>
|
||||
<li><a href="#sec-7">Mailing list</a></li>
|
||||
<li><a href="#sec-8">Tutorials</a></li>
|
||||
<li><a href="#sec-9">Org-mode, GTD and other task management systems </a></li>
|
||||
<li><a href="#sec-10">Add-Ons</a></li>
|
||||
<li><a href="#sec-11">Translators</a></li>
|
||||
<li><a href="#sec-15">Alternative distributions</a></li>
|
||||
<li><a href="#sec-16">Contributing to Org-mode</a></li>
|
||||
<li><a href="#sec-17">Future Development</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
|
||||
<div class="outline-2">
|
||||
<h2 id="sec-1">Org - an Emacs Mode for Notes and Project Planning</h2>
|
||||
|
||||
|
||||
|
||||
|
||||
<BASE href="http://orgmode.org/index.html">
|
||||
|
||||
<p>
|
||||
Org-mode is a mode for keeping notes, maintaining ToDo lists, and doing
|
||||
project planning with a fast and effective plain-text system.
|
||||
</p>
|
||||
<p>
|
||||
Org-mode develops organizational tasks around NOTES files that contain
|
||||
information about projects as plain text. Org-mode is implemented on
|
||||
top of outline-mode, which makes it possible to keep the content of
|
||||
large files well structured. Visibility cycling and structure editing
|
||||
help to work with the tree. Tables are easily created with a built-in
|
||||
table editor. Org-mode supports ToDo items, deadlines, time stamps,
|
||||
and scheduling. It dynamically compiles entries into an agenda.
|
||||
Plain text URL-like links connect to websites, emails, Usenet
|
||||
messages, BBDB entries, and any files related to the projects. For
|
||||
printing and sharing of notes, an Org-mode file can be exported as a
|
||||
structured ASCII file, HTML, and LaTeX.
|
||||
</p>
|
||||
</div>
|
||||
|
||||
<div class="outline-2">
|
||||
<h2 id="sec-2">Current Version (5.19) and Compatibility</h2>
|
||||
|
||||
|
||||
<p>
|
||||
The current version is 5.19. To see what has changed in recent
|
||||
releases, check this <a href="Changes.html">list of user-visible changes</a>. These descriptions
|
||||
are extensive, to avoid that people will be printing the manual after
|
||||
each incremental release. If you have an older version of the manual,
|
||||
just check the release notes and you will be up-to-date.
|
||||
</p>
|
||||
<p>
|
||||
This package works on Emacs 22, and (with minor restrictions) on Emacs
|
||||
21 and XEmacs 21 (where you must also use <i>noutline.el</i> shipped with
|
||||
Org-mode). The Emacs 22.1 release ships with Org-mode version 4.67c.
|
||||
The latest CVS emacs trunk usually contains a fairly recent version,
|
||||
but may lag a bit behind the website release.
|
||||
</p>
|
||||
</div>
|
||||
|
||||
<div class="outline-2">
|
||||
<h2 id="sec-3">Downloads</h2>
|
||||
|
||||
|
||||
<ul>
|
||||
<li>Distribution<br/>
|
||||
Download as <a href="org-5.19.zip">zip file</a> or <a href="org-5.19.tar.gz">gzipped tar archive</a>. These archives contain
|
||||
both the Lisp file org.el and the documentation in PDF and (TeX)Info
|
||||
formats. A shell script to simplify upgrading to the newest release
|
||||
has been posted <a href="http://www.philfam.co.uk/pete/GTD/org-mode/update-org.sh">here</a>.
|
||||
|
||||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
|
||||
<div class="outline-2">
|
||||
<h2 id="sec-4">Documentation</h2>
|
||||
|
||||
|
||||
<div class="outline-3">
|
||||
<h3 id="sec-5">Manual and Reference card</h3>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
Read the documentation <a href="manual/index.html">online</a>. This is a version consisting of many
|
||||
small files, to save bandwidth. If you really need it, you can also
|
||||
have the entire manual in a <a href="org.html">single monolithic file</a>.
|
||||
</li>
|
||||
<li>
|
||||
Download the documentation in other formats: <a href="org.pdf">PDF</a>, <a href="org">Info</a>, or <a href="org.texi">TeXInfo</a>.
|
||||
</li>
|
||||
<li>
|
||||
Download the <a href="orgcard.pdf">Refcard</a> for org-mode, and Kyle Sherman hast created a
|
||||
<a href="orgcard.txt">text version</a> of the reference card
|
||||
</li>
|
||||
<li>
|
||||
There is also a <a href="http://hpcgi1.nifty.com/spen/index.cgi?OrgMode%2fManual">Japanese translation</a> of the manual (version 4.60),
|
||||
produced by Takeshi Okano.
|
||||
</li>
|
||||
<li>
|
||||
The <a href="faq.html">FAQ</a> is not very up-to-date, but may still answer some of your
|
||||
questions. Please have a look before posting to emacs-orgmode@gnu.org.
|
||||
|
||||
</li>
|
||||
</ul></div>
|
||||
</div>
|
||||
|
||||
<div class="outline-2">
|
||||
<h2 id="sec-6">Links</h2>
|
||||
|
||||
|
||||
|
||||
<div class="outline-3">
|
||||
<h3 id="sec-7">Mailing list</h3>
|
||||
|
||||
|
||||
<p>
|
||||
There is a mailing list for discussion about org-mode.
|
||||
</p>
|
||||
<ul>
|
||||
<li>
|
||||
Subscribe to it at <a href="http://lists.gnu.org/mailman/listinfo/emacs-orgmode">this webpage</a>.
|
||||
</li>
|
||||
<li>
|
||||
Directly <a href="mailto:emacs-orgmode@gnu.org">send mail to it</a>. If you are not subscribed, a moderator
|
||||
will look at the message before passing it through to the
|
||||
list. If that has happened once, future messages from your email
|
||||
address will get through immediately, even if you remain
|
||||
unsubscribed.
|
||||
</li>
|
||||
<li>
|
||||
Read the list on <a href="http://www.gmane.org">Gmane</a> through a <a href="http://news.gmane.org/gmane.emacs.orgmode">web interface</a> or with a
|
||||
<a href="news://news.gmane.org/gmane.emacs.orgmode">newsreader</a>.
|
||||
<li><form method="get" action="http://search.gmane.org/">
|
||||
<input type="text" name="query">
|
||||
<input type="hidden" name="group" value="gmane.emacs.orgmode">
|
||||
<input type="submit" value="Search gmane.emacs.orgmode">
|
||||
</form>
|
||||
|
||||
</li>
|
||||
</ul></div>
|
||||
|
||||
<div class="outline-3">
|
||||
<h3 id="sec-8">Tutorials</h3>
|
||||
|
||||
|
||||
<p>
|
||||
<a href="tutorials.html">Tutorials and screencasts</a> are listed on a separate page.
|
||||
</p>
|
||||
</div>
|
||||
|
||||
<div class="outline-3">
|
||||
<h3 id="sec-9">Org-mode, GTD and other task management systems </h3>
|
||||
|
||||
<p>Org-mode is flexible enough to implement many different ways of
|
||||
organizing your projects. A frequently discusses scheme is <a href="http://www.davidco.com/">David Allen's</a> strategy for <a href="http://en.wikipedia.org/wiki/GTD">Getting Things Done</a>. But it is clearly not
|
||||
the only way to us Org-mode for planning. Here are a couple of
|
||||
links related to this topic.
|
||||
</p>
|
||||
<ul>
|
||||
<li>
|
||||
<a href="http://johnwiegley.com">John Wiegley</a> has written an excellent document describing his
|
||||
way of using Org-mode as a <a href="http://johnwiegley.com/org.mode.day.planner.html">day planner</a>. See also some later
|
||||
messages for enhancements of his setup:
|
||||
<a href="http://article.gmane.org/gmane.emacs.orgmode/2963">emacs-orgmode-2962</a>, <a href="http://article.gmane.org/gmane.emacs.orgmode/3629">emacs-orgmode-3629</a>
|
||||
|
||||
</li>
|
||||
<li>
|
||||
<a href="http://members.optusnet.com.au/charles57/Creative/">Charles Cave</a> has written an <a href="http://members.optusnet.com.au/~charles57/GTD/orgmode.html">article/tutorial</a> about the basic
|
||||
elements of GTD and how he implements them in Org-mode.
|
||||
|
||||
</li>
|
||||
<li>
|
||||
There have been several threads on emacs-orgmode@gnu.org related
|
||||
to GTD, the most important ones are:
|
||||
<ul>
|
||||
<li>
|
||||
<a href="http://thread.gmane.org/gmane.emacs.orgmode/683">Another GTD question</a>, which contains a discussion about basic
|
||||
GTD aspects. It also contains this
|
||||
</li>
|
||||
<li>
|
||||
<a href="http://article.gmane.org/gmane.emacs.orgmode/715">Post by Carsten</a> summarizing several options for implementing
|
||||
GTD in org-mode.
|
||||
</li>
|
||||
<li>
|
||||
<a href="http://thread.gmane.org/gmane.emacs.orgmode/523">GTD, Projects and Next Actions in org-mode</a> is a thread where
|
||||
several people describe their personal setup is
|
||||
</li>
|
||||
<li>
|
||||
The <a href="http://thread.gmane.org/gmane.emacs.orgmode/4915">SOMEDAY/MAYBE vs. low priorities</a> thread contains a
|
||||
discussion about priorities that is quite instructive.
|
||||
</li>
|
||||
<li>
|
||||
Here is a <a href="http://thread.gmane.org/gmane.emacs.orgmode/4832/focus%3D4854">very instructive post</a> by Pete Phillips explaining
|
||||
why David Allens book is where you should start to learn GTD,
|
||||
and that the Internet and Org-mode only come into the game
|
||||
later, when thinking about the implementation. And since
|
||||
doing GTD the right way will give you lots of free time, don't
|
||||
forget to listen to <a href="http://www.detox-jazz.co.uk/">Pete's music</a>!
|
||||
</li>
|
||||
</ul></li>
|
||||
<li>
|
||||
Also on the web you can find information about how people are
|
||||
setting up Org-mode to fit their habits. A few examples:
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
This <a href="http://www.brool.com/?p=82">blog post</a> shows a very simple and clear GTD setup.
|
||||
|
||||
</li>
|
||||
</ul></li>
|
||||
</ul></div>
|
||||
|
||||
<div class="outline-3">
|
||||
<h3 id="sec-10">Add-Ons</h3>
|
||||
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<a href="http://www.cl.cam.ac.uk/~pz215/">Piotr Zielinski</a> wrote <a href="http://www.cl.cam.ac.uk/~pz215/files/org-mouse.el">org-mouse.el</a> which is now distributed with
|
||||
Org-mode. It implements great mouse support for many functions in
|
||||
org-mode.
|
||||
|
||||
</li>
|
||||
<li>
|
||||
<a href="http://dto.freeshell.org/notebook/">David O'Toole</a> is the author of <a href="http://dto.freeshell.org/e/org-publish.el">org-publish.el</a>. While this is
|
||||
now part of the Org-mode distribution, you might find the newest
|
||||
bug fixes and developments at his <a href="http://dto.freeshell.org/notebook/OrgMode.html">Org-mode page</a>, along with
|
||||
several other projects like <i>org-blog.el</i> and
|
||||
<i>org-publish-escript.el</i>.
|
||||
|
||||
</li>
|
||||
<li>
|
||||
<a href="http://www.cognition.ens.fr/~guerry/">Bastien Guerry</a> has been really prolific in writing interesting
|
||||
add-ons, all available at his <a href="http://www.cognition.ens.fr/~guerry/bastien-org-mode.html">org-mode page</a>:
|
||||
<ul>
|
||||
<li>
|
||||
a package for using Org-mode as the basis for blogging
|
||||
</li>
|
||||
<li>
|
||||
a LaTeX exporter that is now distributed together with
|
||||
org-mode
|
||||
</li>
|
||||
<li>
|
||||
a special table-of-contents buffer that simplifies navigation
|
||||
</li>
|
||||
<li>
|
||||
a registry to find locations that link a specific document.
|
||||
|
||||
</li>
|
||||
</ul></li>
|
||||
<li>
|
||||
George C.F. Greve wrote <a href="http://www.emacswiki.org/emacs/org-mairix.el">org-mairix.el</a> to add links that trigger a
|
||||
mairix search.
|
||||
|
||||
</li>
|
||||
</ul></div>
|
||||
|
||||
<div class="outline-3">
|
||||
<h3 id="sec-11">Translators</h3>
|
||||
|
||||
|
||||
<p>
|
||||
I know about the following attempts to translate from and to
|
||||
Org-mode files:
|
||||
</p>
|
||||
|
||||
<div class="outline-4">
|
||||
<h4 id="sec-12">Org-mode to XXX</h4>
|
||||
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<a href="http://www.cognition.ens.fr/~guerry/u/org2rem.el">From Org-mode to remind</a> by <a href="http://www.cognition.ens.fr/~guerry/">Bastien Guerry</a>.
|
||||
|
||||
</li>
|
||||
<li>
|
||||
<a href="org-export-freemind-0.1.0.tar.gz">From Org-mode to Freemind</a> by Marco Vezzoli.
|
||||
|
||||
</li>
|
||||
</ul></div>
|
||||
|
||||
<div class="outline-4">
|
||||
<h4 id="sec-13">XXX to Org-mode</h4>
|
||||
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<a href="http://www.olafdietsche.de/palm/palm2orgmode.pl">From Palm TODO database to Orgmode</a>. This Translator was
|
||||
written by <a href="http://www.olafdietsche.de/">Olaf Dietsche</a>.
|
||||
|
||||
</li>
|
||||
</ul></div>
|
||||
|
||||
<div class="outline-4">
|
||||
<h4 id="sec-14">Bi-directional</h4>
|
||||
|
||||
|
||||
<p>
|
||||
Unfortunately nothing so far.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="outline-3">
|
||||
<h3 id="sec-15">Alternative distributions</h3>
|
||||
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
Mark A. Hershberger has made some <a href="https://launchpad.net/~hexmode/+archive">Ubuntu packages</a> for org-mode.
|
||||
|
||||
</li>
|
||||
</ul></div>
|
||||
|
||||
<div class="outline-3">
|
||||
<h3 id="sec-16">Contributing to Org-mode</h3>
|
||||
|
||||
|
||||
<p>
|
||||
You can always contribute with ideas and bug reports on the mailing
|
||||
list. If you want to contribute a patch, code snippets, or a full
|
||||
add-on, this is very welcome too! However, I can only make it an
|
||||
official part of Org-mode if you have signed the papers with the
|
||||
Free Software Foundation. Org-mode is distributed as part of Emacs
|
||||
and must therefore adhere to strict rules about the copyright of
|
||||
all included material. If this is what you want to do, <a href="request-assign-future.txt">here</a> is the
|
||||
form that you have to fill in and send to the FSF. After you
|
||||
received the final copy with signatures, please scan it and send
|
||||
the scan to the maintainer.
|
||||
</p>
|
||||
</div>
|
||||
|
||||
<div class="outline-3">
|
||||
<h3 id="sec-17">Future Development</h3>
|
||||
|
||||
|
||||
<p>
|
||||
Org-mode is still developing fast. The best way to stay up-to-date
|
||||
is to join the mailing list where the changes are developed and
|
||||
discusssed.
|
||||
</p>
|
||||
<p>
|
||||
Here is a loose <a href="todo.html">list of ideas</a> that are still to be processed
|
||||
somehow, when I get to it…
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="postamble"><p class="author"> Author: Carsten Dominik
|
||||
<a href="mailto:carsten at orgmode dot org"><carsten at orgmode dot org></a>
|
||||
</p>
|
||||
<p class="date"> Date: 2008/01/18 12:46:32</p>
|
||||
</div></body>
|
||||
</html>
|
@ -22,9 +22,9 @@ messages, BBDB entries, and any files related to the projects. For
|
||||
printing and sharing of notes, an Org-mode file can be exported as a
|
||||
structured ASCII file, HTML, and LaTeX.
|
||||
|
||||
* Current Version (5.22a) and Compatibility
|
||||
* Current Version (5.23a) and Compatibility
|
||||
|
||||
The current version is 5.22a. To see what has changed in recent
|
||||
The current version is 5.23a. To see what has changed in recent
|
||||
releases, check this [[file:Changes.html][list of user-visible changes]]. These descriptions
|
||||
are extensive, to avoid that people will be printing the manual after
|
||||
each incremental release. If you have an older version of the manual,
|
||||
@ -39,7 +39,7 @@ but may lag a bit behind the website release.
|
||||
* Downloads
|
||||
|
||||
**** Distribution
|
||||
Download as [[file:org-5.22a.zip][zip file]] or [[file:org-5.22a.tar.gz][gzipped tar archive]]. These archives contain
|
||||
Download as [[file:org-5.23a.zip][zip file]] or [[file:org-5.23a.tar.gz][gzipped tar archive]]. These archives contain
|
||||
both the Lisp file org.el and the documentation in PDF and (TeX)Info
|
||||
formats. A shell script to simplify upgrading to the newest release
|
||||
has been posted [[http://www.philfam.co.uk/pete/GTD/org-mode/update-org.sh][here]].
|
||||
|
@ -1,151 +0,0 @@
|
||||
Org-Mode Homepage
|
||||
=================
|
||||
|
||||
Author: Carsten Dominik <dominik at science dot uva dot nl>
|
||||
Date: 2007/05/13 09:31:34
|
||||
|
||||
|
||||
Table of Contents
|
||||
=================
|
||||
Org - an Emacs Mode for Notes and Project Planning
|
||||
Current Version
|
||||
Compatibility
|
||||
Downloads
|
||||
Frequently Asked Questions
|
||||
Mailing list
|
||||
Links
|
||||
Tutorials
|
||||
Org-mode and GTD
|
||||
Add-Ons
|
||||
Future Development
|
||||
|
||||
|
||||
Org - an Emacs Mode for Notes and Project Planning
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Org-mode is a mode for keeping notes, maintaining ToDo lists, and doing
|
||||
project planning with a fast and effective plain-text system.
|
||||
|
||||
Org-mode develops organizational tasks around NOTES files that contain
|
||||
information about projects as plain text. Org-mode is implemented on
|
||||
top of outline-mode, which makes it possible to keep the content of
|
||||
large files well structured. Visibility cycling and structure editing
|
||||
help to work with the tree. Tables are easily created with a built-in
|
||||
table editor. Org-mode supports ToDo items, deadlines, time stamps,
|
||||
and scheduling. It dynamically compiles entries into an agenda.
|
||||
Plain text URL-like links connect to websites, emails, Usenet
|
||||
messages, BBDB entries, and any files related to the projects. For
|
||||
printing and sharing of notes, an Org-mode file can be exported as a
|
||||
structured ASCII file, or as HTML.
|
||||
|
||||
Current Version
|
||||
===============
|
||||
|
||||
The current version is 4.74. To see what has changed in recent
|
||||
releases, check this [list of user-visible changes].
|
||||
|
||||
Compatibility
|
||||
=============
|
||||
|
||||
This package works on Emacs 21 and (with minor restrictions) on
|
||||
XEmacs 21. Version 4.67c will be part of the Emacs 22.1 release.
|
||||
|
||||
*Attention XEmacs users*: Starting with Org-mode 4.38, Org-mode will
|
||||
only work correctly with XEmacs if you use [noutline.el], a new
|
||||
implementation of outline-mode. Until this package becomes part of
|
||||
XEmacs, you can find it in the xemacs subdirectory of the Org-mode
|
||||
distribution. Just compile it and place it onto you load path,
|
||||
Org-mode will load it automatically.
|
||||
|
||||
Downloads
|
||||
=========
|
||||
|
||||
* Distribution
|
||||
Download as [zip file] or [gzipped tar archive]. These archives
|
||||
contain both the Lisp file org.el and the documentation in PDF
|
||||
and (TeX)Info formats.
|
||||
|
||||
* Documentation
|
||||
- Read the documentation [online].
|
||||
- Download the documentation in [PDF], [Info], or [TeXInfo] format.
|
||||
- Download the [Refcard] for org-mode.
|
||||
- There is also a [Japanese translation] of the manual (version 4.60), produced by Takeshi Okano.
|
||||
|
||||
|
||||
Frequently Asked Questions
|
||||
==========================
|
||||
|
||||
The [FAQ] used to be part of the manual but this is no longer the case.
|
||||
|
||||
Mailing list
|
||||
============
|
||||
|
||||
There is a mailing list for discussion about org-mode. You can
|
||||
subscribe to it at [this webpage] or directly [send mail to it] (which
|
||||
will make it to the list after the moderator has accepted it.
|
||||
Furthermore you can access the mailing list on [Gmane] through a
|
||||
[web interface] or with a
|
||||
[newsreader].
|
||||
|
||||
Links
|
||||
=====
|
||||
|
||||
Tutorials
|
||||
---------
|
||||
- There is a very nice introductory [OrgMode tutorial] by [David O'Toole] covering the basics of TODO lists and the agenda. It
|
||||
has been translated into [French], [Japanese], [Chinese], and [Korean].
|
||||
|
||||
Org-mode and GTD
|
||||
----------------
|
||||
Org-mode is flexible enough to implement many different ways of
|
||||
organizing your projects. A frequently discusses scheme is [David Allen's] strategy for [Getting Things Done]. Here are a couple of
|
||||
links related to this topic.
|
||||
|
||||
- [Charles Cave] has written an [article/tutorial] about the basic
|
||||
elements of GTD and how he implements them in Org-mode.
|
||||
|
||||
- There have been several threads on emacs-orgmode@gnu.org related
|
||||
to GTD, the most important ones are:
|
||||
- [Another GTD question], which contains a discussion about basic
|
||||
GTD aspects. It also contains this
|
||||
- [Post by Carsten] summarising several options for implementing
|
||||
GTD in org-mode.
|
||||
- [GTD, Projects and Next Actions in org-mode] is a thread where
|
||||
several people describe their personal setup is
|
||||
|
||||
- Also on the web you can find information about how people are
|
||||
setting up Org-mode to fit their habits. A few examples:
|
||||
|
||||
- This [blog post] shows a very simple and clear GTD setup.
|
||||
|
||||
Add-Ons
|
||||
-------
|
||||
|
||||
- [Piotr Zielinski] wrote [org-mouse.el] which is now distributed with
|
||||
Org-mode. It implements very interesting mouse support for many
|
||||
functions in org-mode.
|
||||
|
||||
- [David O'Toole] is the author of [org-publish.el]. While this is
|
||||
now part of the Org-mode distribution, you might find the newest
|
||||
bug fixes and developments at his [Org-mode page], along with
|
||||
several other projects like /org-blog.el/ and
|
||||
/org-publish-escript.el/.
|
||||
|
||||
- [Bastien Guerry] has a package for using Org-mode as the basis for
|
||||
blogging, it is available at [this page].
|
||||
|
||||
+ Translators
|
||||
|
||||
I know about the following attempts to translate from and to
|
||||
Org-mode files:
|
||||
|
||||
- [From Palm TODO database to Orgmode]. This Translator was
|
||||
written by [Olaf Dietsche].
|
||||
|
||||
- [From Org-mode to remind] by [Bastien Guerry].
|
||||
|
||||
|
||||
Future Development
|
||||
------------------
|
||||
- Here is a [list of ideas] that are still to be processed somehow,
|
||||
when I get to it.
|
File diff suppressed because it is too large
Load Diff
@ -1,920 +0,0 @@
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
|
||||
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml"
|
||||
lang="en" xml:lang="en">
|
||||
<head>
|
||||
<title>The Org-mode TODO list</title>
|
||||
<meta http-equiv="Content-Type" content="text/html;charset=iso-8859-1"/>
|
||||
<meta name="generator" content="Org-mode"/>
|
||||
<meta name="generated" content="2007/07/10 10:35:08"/>
|
||||
<meta name="author" content="Carsten Dominik"/>
|
||||
<link rel=stylesheet href="freeshell2.css" type="text/css"> <style type="text/css"> .tag { color: red; font-weight:bold}</style>
|
||||
</head><body>
|
||||
<h1 class="title">The Org-mode TODO list</h1>
|
||||
<h2>Table of Contents</h2>
|
||||
<ul>
|
||||
<li><a href="#sec-1">1 Introduction</a>
|
||||
<ul>
|
||||
<li><a href="#sec-2">1.1 Nomenclature</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a href="#sec-3">2 Tasks</a>
|
||||
<ul>
|
||||
<li><a href="#sec-4">2.1 Structure</a></li>
|
||||
<li><a href="#sec-5">2.2 Agenda issues</a></li>
|
||||
<li><a href="#sec-6">2.3 Links</a></li>
|
||||
<li><a href="#sec-7">2.4 Fast update for external editing</a></li>
|
||||
<li><a href="#sec-8">2.5 Tables</a></li>
|
||||
<li><a href="#sec-9">2.6 Properties and Column View</a></li>
|
||||
<li><a href="#sec-10">2.7 Compatibility issues</a></li>
|
||||
<li><a href="#sec-11">2.8 Exporting</a></li>
|
||||
<li><a href="#sec-12">2.9 Miscellaneous Stuff</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a href="#sec-13">3 Archive</a>
|
||||
<ul>
|
||||
<li><a href="#sec-14">3.1 Archived Tasks</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<h2 id="sec-1">1 Introduction</h2>
|
||||
|
||||
|
||||
<p>
|
||||
This is a loose collection of ideas and TODO items for the future
|
||||
development of Org-mode. These ideas come from various sources,
|
||||
mostly from emacs-orgmode@gnu.org, from direct emails to me, or from
|
||||
my own day-dreaming. I don't always mention the source of an idea,
|
||||
out of laziness. However, when I implement a good idea, I try to
|
||||
mention the origin of this idea in the <i>Acknowledgments</i> section of
|
||||
the manual - let me know if I forgot to give <i>you</i> credit for
|
||||
something.
|
||||
</p>
|
||||
|
||||
<h3 id="sec-2">1.1 Nomenclature</h3>
|
||||
|
||||
<p>On this page, I am using TODO keywords in the following way:
|
||||
</p><table border="2" cellspacing="0" cellpadding="6" rules="groups" frame="hsides">
|
||||
<COL align="left"></COL><COL align="left"></COL>
|
||||
<thead>
|
||||
<tr><th><b>Keyword</b></th><th>Intention</th></tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr><td><b>TODO</b></td><td>A development that is going to happen, once I have time or once I figure out how to do it.</td></tr>
|
||||
<tr><td><b>IDEA</b></td><td>A new idea, I have not yet decided what if anything I will do about it.</td></tr>
|
||||
<tr><td><b>WISH</b></td><td>A wish, probably voiced by someone on emacs-orgmode@gnu.org. This is less than a new idea, more a change in existing behavior.</td></tr>
|
||||
<tr><td><b>QUESTION</b></td><td>A question someone asked, that needs some thinking before it can be answered</td></tr>
|
||||
<tr><td><b>DECLINED</b></td><td>I have decided not to implement this feature, but I am keeping it in the list so that people can see it, complain, or still try to convince me.</td></tr>
|
||||
<tr><td><b>INCONSISTENCY</b></td><td>Some behavior in Org-mode that is not as clean and consistent as I would like it to be.</td></tr>
|
||||
<tr><td><b>BUG</b></td><td>This needs to be fixed, as soon as possible.</td></tr>
|
||||
<tr><td><b>DONE</b></td><td>Well, done is done.</td></tr>
|
||||
<tr><td><i>NEW</i></td><td>This is a tag, indicating recently added entries</td></tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
|
||||
<h2 id="sec-3">2 Tasks</h2>
|
||||
|
||||
|
||||
<h3 id="sec-4">2.1 Structure</h3>
|
||||
|
||||
<ul>
|
||||
<li><span class="todo">TODO</span> Definition lists, like in Muse<br/>
|
||||
</li>
|
||||
<li><span class="todo">TODO</span> Get rid of all the \r instances, which were used only for XEmacs.<br/>
|
||||
</li>
|
||||
<li><span class="todo">IDEA</span> Should we allow #+TODO as an alias for #+SEQ<sub>TODO</sub>?<br/>
|
||||
</li>
|
||||
<li><span class="todo">TODO</span> proper visibility cycling for items<br/>
|
||||
Make them not hide the text after the final list item.
|
||||
This is not trivial, we cannot usenormal outline stuff,
|
||||
needs a separate implementaiton.
|
||||
</li>
|
||||
<li><span class="todo">IDEA</span> allow different colors for different TODO keywords/tags.<br/>
|
||||
</li>
|
||||
<li><span class="todo">TODO</span> Use an indirect buffer for org-goto.<br/>
|
||||
Is there a problem with the overriding map?
|
||||
|
||||
</li>
|
||||
<li><span class="todo">WISH</span> Inline TODO entries<br/>
|
||||
A way to put a TODO entry without starting a new section.
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<h3 id="sec-5">2.2 Agenda issues</h3>
|
||||
|
||||
<ul>
|
||||
<li><span class="todo">QUESTION</span> COLUMN View<br/>
|
||||
is this safe, or could things be messed up with this?
|
||||
</li>
|
||||
<li><span class="todo">TODO</span> Make S-right and S-left change TODO keywords<br/>
|
||||
Right now they change the time stamps. This could be
|
||||
M-left/right, but this could also cause inconsistencies, because
|
||||
when on a time stamp, the same keys do exactly this.
|
||||
</li>
|
||||
<li><span class="todo">WISH</span> Make more modes changeable from the agenda<br/>
|
||||
These could be made available for toggling, just like
|
||||
follow-mode. Examples:
|
||||
<ul>
|
||||
<li>
|
||||
org-agenda-todo-list-sublevels
|
||||
</li>
|
||||
<li>
|
||||
org-tags-match-list-sublevels
|
||||
</li>
|
||||
<li>
|
||||
org-agenda-todo-ignore-scheduled
|
||||
</li>
|
||||
</ul></li>
|
||||
<li><span class="todo">IDEA</span> Sort TODO entries according to type?<br/>
|
||||
This would apply for the list collection, not in the day entries.
|
||||
However, I could also have a TODO keyword criterion that could be
|
||||
used in the day entries, as one of the minor criteria.
|
||||
|
||||
</li>
|
||||
<li><span class="todo">DECLINED</span> Allow separators in the Tag-sorted agenda view<br/>
|
||||
This feature is not going to come, because block agendas can
|
||||
achieve the same thing.
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<h3 id="sec-6">2.3 Links</h3>
|
||||
|
||||
<ul>
|
||||
<li><span class="todo">WISH</span> When editing links, give access to stored links.<br/>
|
||||
Not sure why this is needed.
|
||||
Idea from William Henney.
|
||||
</li>
|
||||
<li><span class="todo">WISH</span> Variable of standard links for completion with C-c C-l<br/>
|
||||
Or something like that, to make standard links fast.
|
||||
</li>
|
||||
<li><span class="todo">WISH</span> Make brackets in links possible<br/>
|
||||
Would require a display property also for the label part of
|
||||
links.
|
||||
</li>
|
||||
<li><span class="todo">IDEA</span> Find all links to a specific file<br/>
|
||||
</li>
|
||||
<li><span class="todo">IDEA</span> Make info HTML links work for links to Info files<br/>
|
||||
Info links of course only work inside Emacs. However, many info
|
||||
documents are on the web, so the HTML exporter could try to be
|
||||
smart and convert an Info link into the corresponding link on the
|
||||
web. For example, we could use the GNU software site then
|
||||
Name.HTML. Here is the link to be used:
|
||||
<a href="http://www.gnu.org/software/emacs/manual/html_node/">http://www.gnu.org/software/emacs/manual/html_node/</a> Another
|
||||
question is, is this URL going to be stable so that it makes sense
|
||||
to actually put this into org.el?
|
||||
|
||||
</li>
|
||||
<li><span class="todo">IDEA</span> Make news HTML links work, using Google.<br/>
|
||||
I can use Google groups with a message id to find a USENET message,
|
||||
even if the original link points to gnus.
|
||||
|
||||
</li>
|
||||
<li><span class="todo">TODO</span> Remove irretrievable links from <i>published</i> HTML output<br/>
|
||||
This is on David's table, and he will hopefully integrate a
|
||||
mechanism for this into org-publish.el. The discussion about this
|
||||
was started by <a href="http://thread.gmane.org/gmane.emacs.orgmode/281">Austin Frank</a>
|
||||
|
||||
</li>
|
||||
<li><span class="todo">DECLINED</span> Agenda collections, based on #+COLLECTION lines.<br/>
|
||||
<a href="http://thread.gmane.org/gmane.emacs.orgmode/139">Tim Callaghan</a> started the discussion on this one.
|
||||
Declined because this would depend on local variables and the
|
||||
agenda commands are global. Also, this can actually be done by
|
||||
specifying the file list in a custom agenda command.
|
||||
|
||||
</li>
|
||||
<li><span class="todo">DECLINED</span> Make CamelCase words link to corresponding org-mode files.<br/>
|
||||
Files in the same directory. Or some other way to easy do that.
|
||||
Would be useful for publishing projects. This would be an
|
||||
incompatible change, but I don't think anyone is using CamelCase
|
||||
anyway?
|
||||
This is marked declined, because link abbreviations now provide an
|
||||
easy way to make links to other files.
|
||||
|
||||
</li>
|
||||
<li><span class="todo">TODO</span> Document the character protection in links<br/>
|
||||
I don't think this is really covered anywhere.
|
||||
Maybe we also should protect characters in the visible part, to
|
||||
make sure thing will never be on two lines...?
|
||||
</li>
|
||||
<li><span class="todo">WISH</span> Radio targets across files<br/>
|
||||
I guess each org file could write a .orgtargets.filename file, if
|
||||
it has any radio targets.
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<h3 id="sec-7">2.4 <span class="todo">DECLINED</span> Fast update for external editing</h3>
|
||||
|
||||
<p>Could I use a dynamic block for this?
|
||||
</p>
|
||||
|
||||
<h3 id="sec-8">2.5 Tables</h3>
|
||||
|
||||
<ul>
|
||||
<li><span class="todo">WISH</span> Row formulas<br/>
|
||||
@4=.....
|
||||
</li>
|
||||
<li><span class="todo">TODO</span> Write a tutorial<br/>
|
||||
Demonstrate running averages.
|
||||
|
||||
</li>
|
||||
<li><span class="todo">WISH</span> Make a variable that current line should be recomputed always<br/>
|
||||
in each table, skipping headers of course.
|
||||
|
||||
</li>
|
||||
<li><span class="todo">TODO</span> Allow a table to locally change the unit system<br/>
|
||||
This is for using constants.el.
|
||||
Well, it is now possible to do this for the file, is this enough???
|
||||
</li>
|
||||
<li><span class="todo">QUESTION</span> Does inserting hlines change references correctly?<br/>
|
||||
</li>
|
||||
<li><span class="todo">WISH</span> Interactive way to get a converted table?<br/>
|
||||
</li>
|
||||
<li><span class="todo">BUG</span> When computing in a narrowed column, this may go wrong.<br/>
|
||||
Computing changes fields and does not yet see correctly if the column
|
||||
width has changed, in the case of a narrowed column.
|
||||
|
||||
</li>
|
||||
<li><span class="todo">DECLINED</span> Alternative for the implementation of orgtbl-minor-mode:<br/>
|
||||
I could use post-command-hook to set the variable orgtbl-mode.
|
||||
I will not do this now and only consider it if problems show up.
|
||||
|
||||
</li>
|
||||
<li><span class="todo">DECLINED</span> Table info lines are not necessarily comments in orgtbl-mode<br/>
|
||||
Should I generalize this? No, because the table itself will not be
|
||||
in the correct syntax for whatever mode.
|
||||
|
||||
</li>
|
||||
<li><span class="todo">DECLINED</span> S-cursor motion to select part of a table, with proper highlighting.<br/>
|
||||
Similar to CUA
|
||||
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<h3 id="sec-9">2.6 Properties and Column View</h3>
|
||||
|
||||
<ul>
|
||||
<li><span class="todo">TODO</span> Mouse support for selecting values<br/>
|
||||
This could/should be part of org-mouse.el.
|
||||
<ul>
|
||||
<li>
|
||||
<b>[<span style="visibility:hidden;">X</span>]</b> tags
|
||||
</li>
|
||||
<li>
|
||||
<b>[<span style="visibility:hidden;">X</span>]</b> todo
|
||||
</li>
|
||||
<li>
|
||||
<b>[<span style="visibility:hidden;">X</span>]</b> priority
|
||||
</li>
|
||||
<li>
|
||||
<b>[<span style="visibility:hidden;">X</span>]</b> allowed values
|
||||
</li>
|
||||
<li>
|
||||
<b>[<span style="visibility:hidden;">X</span>]</b> deadline
|
||||
</li>
|
||||
<li>
|
||||
<b>[<span style="visibility:hidden;">X</span>]</b> scheduled.
|
||||
</li>
|
||||
</ul></li>
|
||||
<li><span class="todo">BUG</span> We have no clear view on what to do with properties upon export.<br/>
|
||||
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<h3 id="sec-10">2.7 Compatibility issues</h3>
|
||||
|
||||
<ul>
|
||||
<li>Emacs 21 compatibility<br/>
|
||||
This is being phased out. Almost everything works under Emacs 21,
|
||||
but in the future I wwill make little effort to support it.
|
||||
<ul>
|
||||
<li><span class="todo">DECLINED</span> Column view does not yet work for Emacs 21s.<br/>
|
||||
Declined, because I don't know how to do this. Too many
|
||||
problems.
|
||||
</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>XEmacs compatibility<br/>
|
||||
<ul>
|
||||
<li><span class="todo">QUESTION</span> Is there an issue with the coding system of HTML exported files?<br/>
|
||||
In the code I used to have a comment saying that
|
||||
<pre>
|
||||
(and (fboundp 'coding-system-get)
|
||||
(boundp 'buffer-file-coding-system)
|
||||
buffer-file-coding-system))
|
||||
</pre>
|
||||
always returns nil, implicating that setting the coding system for
|
||||
the export buffer would not work correctly. however, I have never
|
||||
followed up on this and never had a bug report - so I am wondering
|
||||
if there is an issue at all.
|
||||
|
||||
</li>
|
||||
<li><span class="todo">DECLINED</span> Column view does not yet work for XEmacs.<br/>
|
||||
Declined, because I don't know how to do this. Too many
|
||||
problems.
|
||||
</li>
|
||||
<li><span class="todo">DECLINED</span> Rewrite the `format' function<br/>
|
||||
To make narrowing work under XEmacs, I would need to write a
|
||||
version of <i>format</i> that does transport text properties, or I
|
||||
would have to rework narrowing entirely. Unlikely that this will
|
||||
happen, mainly because it is working in Emacs and so does not
|
||||
bother me personally so much. Anyway, I don't know if people are
|
||||
actually using narrowing very much at all.
|
||||
|
||||
|
||||
</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<h3 id="sec-11">2.8 Exporting</h3>
|
||||
|
||||
<ul>
|
||||
<li><span class="todo">IDEA</span> Convert links to footnotes for ASCII export.<br/>
|
||||
</li>
|
||||
<li><span class="todo">DECLINED</span> Store LaTeX code as HTML comments<br/>
|
||||
Declined because I don't really see the need for this.
|
||||
</li>
|
||||
<li><span class="todo">IDEA</span> Microformats<br/>
|
||||
Nic Ferrier has been pushing this agenda for a long time, for
|
||||
example with <a href="http://thread.gmane.org/gmane.emacs.orgmode/140/">this email</a>. I am not deep enough into the semantic
|
||||
web that I could do this myself. Maybe we can do this by
|
||||
modifying the html exporter step-by-step?
|
||||
</li>
|
||||
<li><span class="todo">INCONSISTENCY</span> Find a better place for formatting checkboxes<br/>
|
||||
Right now this is being done as part of `org-html-expand', which
|
||||
does not seem logically correct.
|
||||
</li>
|
||||
<li><span class="todo">DECLINED</span> Can I make the exporter more efficient?<br/>
|
||||
The line-by-line processing may not be the fastest way to do
|
||||
this. It certainly uses more resources. Right now the exporters
|
||||
do work though, so it is unlikely that I am going to change this.
|
||||
|
||||
</li>
|
||||
<li><span class="todo">DECLINED</span> CSV import/export of tables?<br/>
|
||||
I remember this coming up several times, for example in emails
|
||||
from <a href="http://thread.gmane.org/gmane.emacs.orgmode/156">Niels Giesen</a> and <a href="http://thread.gmane.org/gmane.emacs.orgmode/139">Tim Callaghan</a>. Org-mode does have
|
||||
Tab-separated export of tables, so right now I don't really see
|
||||
the benefit of adding CSV export. Are there applications that do
|
||||
not understand tab-separated files, but do understand
|
||||
comma-separated ones?
|
||||
|
||||
</li>
|
||||
<li><span class="todo">DECLINED</span> In HTML export, make links from the time stamps<br/>
|
||||
Time stamps have their own class now which allows to highlight
|
||||
them etc. But I was wondering if something more useful could be
|
||||
done with them, like a link to some kind of calendar...
|
||||
|
||||
|
||||
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<h3 id="sec-12">2.9 Miscellaneous Stuff</h3>
|
||||
|
||||
<ul>
|
||||
<li><span class="todo">TODO</span> reinstating a repeated item: keyword for logging.<br/>
|
||||
</li>
|
||||
<li><span class="todo">BUG</span> Comments cannot be filled<br/>
|
||||
</li>
|
||||
<li><span class="todo">DECLINED</span> HAVE a TIME 3:55 line collecting CLOCK results<br/>
|
||||
The CLOCK lines could be there in addition, or could even be
|
||||
removed, so that only one line is kept.
|
||||
</li>
|
||||
<li><span class="todo">IDEA</span> New uses for C-c C-c<br/>
|
||||
<ul>
|
||||
<li>
|
||||
Compute time interval on time range
|
||||
</li>
|
||||
<li>
|
||||
Update CLOCK interval
|
||||
</li>
|
||||
</ul></li>
|
||||
<li><span class="todo">QUESTION</span> Fix more beginning-of-line commands<br/>
|
||||
Org-mode re-binds C-a to make this command go to the beginning of
|
||||
a visible line. There are other keys which might invoke C-a.
|
||||
Should these keys be changed as well? one could use
|
||||
`substitute-key-definition' on the global map to find them all.
|
||||
</li>
|
||||
<li><span class="todo">QUESTION</span> Inlining of images in Org-mode files<br/>
|
||||
</li>
|
||||
<li><span class="todo">TODO</span> Fixup outline-magic.el, so that it can be used.<br/>
|
||||
</li>
|
||||
<li><span class="todo">TODO</span> Use the new argument of bibtex-url<br/>
|
||||
Roland Winkler was kind enough to implement a new argument to the
|
||||
`bibtex-url' command that allows me to retrieve the corresponding
|
||||
URL, whether it is taken from a URL field or constructed in some
|
||||
clever way. Currently I am not using this, because too many
|
||||
people use an old Emacs version which does not have this.
|
||||
however, eventually I will implement this.
|
||||
</li>
|
||||
<li><span class="todo">WISH</span> Get people to write articles about how to do GTD with Org-mode.<br/>
|
||||
There is now one by Charles Cave, read it <a href="http://members.optusnet.com.au/~charles57/GTD/orgmode.html">here</a>
|
||||
|
||||
</li>
|
||||
<li><span class="todo">IDEA</span> Tree statistics<br/>
|
||||
A key that can be applied to a tree, showing statistics:
|
||||
<ul>
|
||||
<li>
|
||||
how many headlines
|
||||
</li>
|
||||
<li>
|
||||
how many TODO
|
||||
</li>
|
||||
<li>
|
||||
how many DONE
|
||||
</li>
|
||||
<li>
|
||||
Checkboxes
|
||||
</li>
|
||||
<li>
|
||||
etc....
|
||||
|
||||
</li>
|
||||
</ul></li>
|
||||
<li><span class="todo">QUESTION</span> Do we need a 43 folders implementation?<br/>
|
||||
That could easily be done in an org-mode file. But then, maybe
|
||||
this should really be a paper thing.
|
||||
|
||||
</li>
|
||||
<li>Priorities<br/>
|
||||
Here is some information about priorities, which is not yet
|
||||
documented.
|
||||
<ul>
|
||||
<li> Priorities<br/>
|
||||
<pre> TODO entries: 1 or 1,2,...
|
||||
DEADLINE is 10-ddays, i.e. it is 10 on the due day
|
||||
i.e. it goes above top todo stuff 7 days
|
||||
before due
|
||||
SCHEDULED is 5-ddays, i.e. it is 5 on the due date
|
||||
i.e. it goes above top todo on the due day
|
||||
TIMESTAMP is 0 i.e. always at bottom
|
||||
but as a deadline it is 100
|
||||
but if scheduled it is 99
|
||||
TIMERANGE is 0 i.e. always at bottom
|
||||
DIARY is 0 i.e. always at bottom
|
||||
|
||||
Priority * 1000
|
||||
|
||||
</pre>
|
||||
</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><span class="todo">INCONSISTENCY</span>: items don't grow/shrink due to promotion.<br/>
|
||||
In plain lists, multiple demote/promote commands executed directly
|
||||
after each other don't change the scope of the command - the
|
||||
initially selected text continues to be selected. This is
|
||||
inconsistent with the behavior of outline sections, were the subtree
|
||||
for promotion/demotion is newly defined after each command. Which
|
||||
convention is better? Should this be consistent between trees and
|
||||
plain lists?
|
||||
|
||||
</li>
|
||||
<li><span class="todo">INCONSISTENCY</span>: M-TAB does not work on plain lists. Why???<br/>
|
||||
|
||||
</li>
|
||||
<li><span class="todo">QUESTION</span> grep on directory does not yet work.<br/>
|
||||
I am actually not sure, I might have addressed this already, but
|
||||
my memory is failing me. Needs some checking.
|
||||
|
||||
</li>
|
||||
<li><span class="todo">DECLINED</span> Think about Piotr's idea of treating TODO like a TAG.<br/>
|
||||
The answer is probably NO because the simple part of TODO must
|
||||
still be there and I like the keyword at the beginning of the line,
|
||||
just like a checkbox. Of course you can make a TODO tag yourself
|
||||
at any time.
|
||||
|
||||
</li>
|
||||
<li><span class="todo">DECLINED</span> Inlining of external files<br/>
|
||||
|
||||
</li>
|
||||
<li><span class="todo">DECLINED</span> Should TAB on TODO keyword rotate its state?<br/>
|
||||
Problem: If the keyword disappears, it will suddenly start to fold....
|
||||
So my feeling right now is that the answer should be NO.
|
||||
|
||||
<p>
|
||||
No, because S-left/right does this already pretty well
|
||||
</p>
|
||||
</li>
|
||||
<li><span class="todo">DECLINED</span> Create a DONE counter in the mode line<br/>
|
||||
That counter shows what faction of entries has been marked DONE. I
|
||||
am not yet sure how useful such a thing would be, because of the
|
||||
huge number of entries that can be in a file, and the different
|
||||
weight of such entries.
|
||||
Declined because we do now have counters for checkboxes, and the
|
||||
feeling is that this is not so useful for TODOs.
|
||||
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<h2 id="sec-13">3 Archive</h2>
|
||||
|
||||
|
||||
<h3 id="sec-14">3.1 Archived Tasks</h3>
|
||||
|
||||
|
||||
<ul>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-06-01 Thu 09:15</span>) Commands to move through an item list<br/>
|
||||
next item, previous item. What should happen at the boundaries of
|
||||
the current list?
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-06-01 Thu 09:16</span>) Force relative links, would this be useful?<br/>
|
||||
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-06-01 Thu 09:16</span>) Fix empty search string.<br/>
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-06-01 Thu 09:16</span>) STARTUP options for logging<br/>
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-06-01 Thu 09:16</span>) Make a variable for Pete, to have SCHEDULED at point<br/>
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-06-01 Thu 09:16</span>) Fix ASCII export of narrowed columns<br/>
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-06-01 Thu 09:16</span>) org-file-apps should allow regular expressions<br/>
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-06-01 Thu 09:16</span>) fix problem with w32- versus mswindows-....<br/>
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-06-01 Thu 09:17</span>) Document that font-lock-mode is needed<br/>
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-06-01 Thu 09:17</span>) Add keyboard access and menu commands for org-project.el<br/>
|
||||
C-c C-x C-p or something like that.
|
||||
In the menu, it goes under export, or even its own group.
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-06-01 Thu 09:17</span>) Document those new keys in orgcard.tex<br/>
|
||||
C-c C-x C-p or something like that.
|
||||
In the menu, it goes under export, or even its own group.
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-06-01 Thu 09:17</span>) Remove SCHEDULED keyword when marking it done.<br/>
|
||||
in particular when adding a CLOSED timestamp.
|
||||
Only problem is that when unclosing it, it should be scheduled
|
||||
again
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-06-01 Thu 09:17</span>) Don't show tasks already scheduled for the future, only stuff which<br/>
|
||||
is not yet scheduled.
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-06-01 Thu 09:17</span>) Put title and tags in separate classes<br/>
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-06-01 Thu 09:17</span>) Option to leave out TAGS from export<br/>
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-06-01 Thu 09:17</span>) Option to leave out Timestamps from export<br/>
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-06-01 Thu 09:17</span>) Checkable items like Frank Ruell's proposal<br/>
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-06-01 Thu 09:17</span>) Classify Keywords and time stamps<br/>
|
||||
<span class="keyword">SCHEDULED: </span><span
|
||||
class="timestamp">timestamp goes here</span><br>
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-06-01 Thu 09:17</span>) Change default for include-all-todo to nil<br/>
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-06-01 Thu 09:17</span>) Specify TAGS in a special line instead of collecting them dynamically<br/>
|
||||
The could help to avoid typos and could be faster for very large files.
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-06-01 Thu 09:17</span>) Some much faster interface for setting tags.<br/>
|
||||
Basically, use single keys to add/remove tags from the list. Also
|
||||
for this the idea to define tags in a special line would be good,
|
||||
in order to have a way to define the shortcuts.
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-06-01 Thu 09:17</span>) Remove date stamps from headline if they are not needed.<br/>
|
||||
Bug report from Scott.
|
||||
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-06-01 Thu 09:17</span>) : Maybe s-up/down should change priorities only in headlines<br/>
|
||||
Right now this works wherever the cursor is. If this is changed,
|
||||
should S-up or S-down do something else?
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-06-01 Thu 09:21</span>) Need a command to remove tabulators from a line.<br/>
|
||||
Use this in ASCII export, to make sure we get the indentation
|
||||
right.
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-06-01 Thu 09:24</span>) Improve tab in org-cycle:<br/>
|
||||
<ul>
|
||||
<li>
|
||||
there is a bug when the setting is 'white: It requires a
|
||||
non-empty white line!
|
||||
</li>
|
||||
<li>
|
||||
There should be another setting to have tab be the tabulator in
|
||||
the white space at the beginning of the line.
|
||||
</li>
|
||||
<li>
|
||||
Finally, when TAB closes an entry, maybe it should go beck to the
|
||||
beginning of the entry??? On the other hand, it is good to be
|
||||
able to go back to the old place with just another tab.
|
||||
|
||||
</li>
|
||||
</ul></li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-06-01 Thu 11:48</span>) Include TAGS into sorting.<br/>
|
||||
But what strategy should be used when there are several tags?
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-06-06 Tue 10:15</span>) Archiving an entry in current buffer goes to end of file<br/>
|
||||
Should go to end of subtree.
|
||||
This is done now, and I also control the amount of empty lines
|
||||
created by the archiving process in general.
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-06-06 Tue 10:16</span>) Narrowing agenda to current files does not work as advertized.<br/>
|
||||
C-c a 1 t should make the TODO list for the current file, but does
|
||||
not.
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-06-06 Tue 10:17</span>) Radio TAGS for the fast tag interface.<br/>
|
||||
Make lists of tags that are mutually exclusive. So when I turn on
|
||||
@HOME, @WORK would be turned off automagically. A good syntax for
|
||||
defining these groups in the #+TAGS line would be:
|
||||
<pre>
|
||||
#+TAGS: [@WORK(w) @HOME(h) @CLUB(c)] Laptop(l) PC(p) Car(r)
|
||||
</pre>
|
||||
This could indicate that @WORK, @HOME, @CLUB are mutually exclusive.
|
||||
|
||||
<p>
|
||||
If I do this, I will also need a syntax for the global alist to
|
||||
indicate the same thing.
|
||||
</p>
|
||||
<p>
|
||||
It seems to me that with such grouping of tags, sorting would be
|
||||
useful as it would improve the overview over the current tags. I
|
||||
might even be able to support mutually exclusive tags with
|
||||
fontification in the interface. Or arrange things such that the
|
||||
mutually exclusive ones are all in the same row or column, to
|
||||
optimize the visual feedback.
|
||||
</p>
|
||||
<p>
|
||||
For the internal format, I think best would be something like
|
||||
</p>
|
||||
<p>
|
||||
<pre>
|
||||
'( (:startgroup) ("@work") ("@home") ("@club") (:endgroup)
|
||||
("Laptop") ("PC") ("Car"))
|
||||
</pre>
|
||||
This setup makes sure that assoc and rassoc still do work as
|
||||
expected.
|
||||
</p>
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-06-06 Tue 10:17</span>) Should tags be sorted in a certain way?<br/>
|
||||
Right now, you can either set the tag sequence yourself through
|
||||
the completion interface. If you use the fast tag selection
|
||||
interface, the tag sequence depends on the order in which tags are
|
||||
selected and deselected. maybe a specific roder would be useful
|
||||
for example the same order as the one given in the configuration?
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-06-06 Tue 10:17</span>) Remove narrowing cookies for export<br/>
|
||||
Exported tables should not show narrowing cookies. In fact, if a
|
||||
table line does contain nothing but narrowing cookies, the entire
|
||||
line should be removed.
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-06-11 Sun 07:32</span>) Track working times similar to time-clock.el<br/>
|
||||
This was proposed by David O'Toole in an
|
||||
<a href="http://thread.gmane.org/gmane.emacs.orgmode/387">email to emacs-orgmode@gnu.org</a>. He wants to be able to know the
|
||||
times when he worked at a particular project. Some reporting
|
||||
possibility would be needed to make this useful. Maybe sparse
|
||||
trees with broken-down working times?
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-06-15 Thu 13:35</span>) Make org-store-link do better in image-mode buffers<br/>
|
||||
Just link to the file.
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-06-15 Thu 13:35</span>) Use a ported version of noutline.el<br/>
|
||||
Programming the old outline-mode is really a nightmare - the new
|
||||
outline mode that uses invisibility properties instead of
|
||||
selective display works really much much better. There is now
|
||||
an <a href="http://thread.gmane.org/gmane.emacs.orgmode/214/focus=218">experimental port</a> by Greg Chernov, so when I find time I will
|
||||
try if this works well. If yes, this port should become part of
|
||||
XEmacs. Once that happens, I could remove a large amount of
|
||||
ballast from org.el
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-06-15 Thu 13:35</span>) Verify links during export<br/>
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-09-25 Mon 16:11</span>) Allow counting checkboxes<br/>
|
||||
Then some statistics should be displayed. One idea is for
|
||||
checkboxes, to use a special box [%] which will be updated with
|
||||
percent of done. I could have an alternative [/] that will be
|
||||
updated with something like [19/25] to show progress, and when the
|
||||
two numbers are equal, I could highlight then in DONE face, just
|
||||
like [100%]. All smaller numbers could be highlighted even in
|
||||
TODO face if I wanted. Hmmm, I am beginning to like this.
|
||||
|
||||
<p>
|
||||
Then: how to update this? Each time a checkbox is added or
|
||||
toggled, go up and update all the counts, right up to something
|
||||
which is not an item, or up to the previous header line.
|
||||
</p>
|
||||
<p>
|
||||
Maybe I should also make an option for turning this on, to avoid
|
||||
slowdown. I guess for long lists this could be slow.
|
||||
</p>
|
||||
<p>
|
||||
Also would need a command for global update.
|
||||
</p>
|
||||
<p>
|
||||
An maybe plain list and checkboxes should get their own chapter?
|
||||
In Structure they seem to be a bit hidden.....
|
||||
</p>
|
||||
<p>
|
||||
Also a menu sublist...
|
||||
</p>
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-09-25 Mon 16:11</span>) Allow stacking calls to org-occur<br/>
|
||||
This was a proposal from Piotr. It is now possible, the second
|
||||
and subsequent calls to org-occur need a prefix argument to keep
|
||||
the previous highlights.
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-09-25 Mon 16:12</span>) Create a hook to be run after an agenda buffer has been finalized.<br/>
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-09-25 Mon 16:12</span>) Include TAGS into sorting.<br/>
|
||||
But what strategy should be used when there are several tags?
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-09-25 Mon 16:12</span>) Fixup tag display in agenda buffer.<br/>
|
||||
The tabs mess up everything. Either remove the tabs, or realign
|
||||
the tags to some useful column.
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-09-25 Mon 16:12</span>) Blocks in agenda:<br/>
|
||||
Make a single agenda buffer that contains several sets of items,
|
||||
like the TODO list, a tags list, and a day view. Not a bad idea.
|
||||
This was <a href="http://thread.gmane.org/gmane.emacs.orgmode/167/focus=168">Piotr's idea</a>.
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-09-25 Mon 16:12</span>) Make org-store-link do the right thing in dired-mode<br/>
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2006-11-02 Thu 10:24</span>) Control over windows being used for agenda and related buffers <span class="tag">NEW</span><br/>
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2007-01-24 Wed 12:59</span>) Extend access to table fields<br/>
|
||||
Find a general way to get any rectangular region into a calc
|
||||
vector
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2007-01-24 Wed 12:59</span>) Allow links to remote images to be inlined.<br/>
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2007-01-24 Wed 12:59</span>) M-TAB on an already complete tag should add the ":"<br/>
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2007-01-24 Wed 13:07</span>) Need a command to do show hierarchy after isearch.<br/>
|
||||
Maybe automatically, using isearch-mode-end-hook. But this does
|
||||
not seem to work, because to is called before the overlays are
|
||||
re-installed. I can create a new hook, isearch-exit-hook, run in
|
||||
`isearch-exit'.
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2007-02-18 Sun 07:16</span>) hook for users to do their own agenda lists<br/>
|
||||
New function dumping headline into the agenda buffer, based on regexp
|
||||
and callback, to allow general stuff. For the special tags, we can
|
||||
search for one and check for the others using the callback.
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2007-02-18 Sun 07:37</span>) Make C-c C-l also work on a plain link, converting it into bracket.<br/>
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2007-02-18 Sun 07:37</span>) GNUS <i><gnus:mail.general#123></i> stuff should be "Email from:..."<br/>
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2007-02-18 Sun 07:38</span>) Email/message context: What format?<br/>
|
||||
I can think of two good formats for this:
|
||||
<pre>
|
||||
Email from John Smith (if I an the receiver)
|
||||
Email to John Smith (if I am the author)
|
||||
</pre>
|
||||
or
|
||||
<pre>
|
||||
John Smith on: Some subject (this is the current Org-mode default.)
|
||||
</pre>
|
||||
The first format requires better parsing of the messages (to get
|
||||
both author and receiver names), and also
|
||||
some way to detect if I am the author of this email or not.
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2007-02-21 Wed 12:04</span>) Allow internal links to match inside <b>other</b> link<br/>
|
||||
Only the link itself that actually triggered the search.
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2007-02-21 Wed 12:07</span>) Allow fully protected HTML code that will be exported as is<br/>
|
||||
Currently, <...> works only for simple tags, and I think we
|
||||
should have something better. Idea: Text between <protecthtml>
|
||||
and </protecthtml>, mark it with a text property and then exclude
|
||||
each match in the run preparing the export.
|
||||
I guess I could require these at the beginning of the line, like
|
||||
|
||||
|
||||
|
||||
<p>
|
||||
or something like that.......
|
||||
</p>
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2007-03-13 Tue 05:19</span>) Make it possible to set TOC levels independently of headline levels<br/>
|
||||
The easiest way to do this would obviously be to allow a number
|
||||
setting for the tco switch, not only a simple t/nil switch. This
|
||||
can be nice for webpages: One could have only top-level or level
|
||||
1 and 2 in the toc at the beginning of the page, and then still a
|
||||
more complex structure below.
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2007-03-13 Tue 05:20</span>) Filling is not done in a compatible way.<br/>
|
||||
The current setup used the Emacs variables and machine to get the
|
||||
filling of plain lists and everything lese right. XEmacs uses the
|
||||
filladapt package, which has different ways to do the same
|
||||
things. org.el should be smart about this and setup filling under
|
||||
XEmacs correctly.
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2007-06-06 Wed 17:44</span>) Repeating Schedules?<br/>
|
||||
<a href="http://thread.gmane.org/gmane.emacs.orgmode/149">Dieter Grollman</a> requested this feature, but for now I have decided
|
||||
not to do anything about it. I don't see a good way to implement
|
||||
this, and I believe that cyclic diary entries are good enough for
|
||||
such tasks.
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2007-06-14 Thu 13:16</span>) improve item indentation when promoting and demoting<br/>
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2007-06-14 Thu 13:17</span>) The TODO buffer lists possible TODO keywords<br/>
|
||||
These are taken from the current buffer, so when multiple buffers
|
||||
are involved, this list may not be correct.....
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span>( <span class="timestamp">2007-06-14 Thu 13:20</span>) Conflict between bold emphasis and headlines<br/>
|
||||
At the beginning of a line, Org-mode does not know if <b>bold</b> is a
|
||||
headline or an emphasis. This will not be easy to fix. The way
|
||||
to do ii is to require a space after the star in headlines. This
|
||||
requires to change outline-regexp, outline-level, the many many
|
||||
times when outline regexp is used in the program, and also the
|
||||
countless times when I am simply matching th stars directly.
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span> C-c - for cycling bullet types.<br/>
|
||||
<span class="timestamp-kwd">ARCHIVED: </span> <span class="timestamp">2007-07-02 Mon</span><br/>
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span> improve what TAB does with new item<br/>
|
||||
<span class="timestamp-kwd">ARCHIVED: </span> <span class="timestamp">2007-07-02 Mon</span><br/>
|
||||
same or additional indentation????
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span> Make it easier to do monthly agendas, and agendas for ranges<br/>
|
||||
<span class="timestamp-kwd">ARCHIVED: </span> <span class="timestamp">2007-07-02 Mon</span><br/>
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span> Introduce a LOCATION keyword<br/>
|
||||
<span class="timestamp-kwd">ARCHIVED: </span> <span class="timestamp">2007-07-02 Mon</span><br/>
|
||||
similar to DEADLINE and SCHEDULED
|
||||
Idea from Bastien
|
||||
This could be done now using properties, I don't think we need a
|
||||
special thing for this anymore.
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span> Times/date not always removed in agenda lines<br/>
|
||||
<span class="timestamp-kwd">ARCHIVED: </span> <span class="timestamp">2007-07-02 Mon</span><br/>
|
||||
Even when org-agenda-remove-times-when-in-prefix is set, there
|
||||
seem to be cases where this does not work. I forgot what the
|
||||
example was - does anyone remember?
|
||||
|
||||
</li>
|
||||
<li><span class="done">DONE</span> Links are still highlighted in fixed-width environments.<br/>
|
||||
<span class="timestamp-kwd">ARCHIVED: </span> <span class="timestamp">2007-07-02 Mon</span><br/>
|
||||
This ties in with the problem that there is no way to have
|
||||
protected HTML code in the file.
|
||||
|
||||
</li>
|
||||
</ul>
|
||||
<p class="author"> Author: Carsten Dominik
|
||||
<a href="mailto:carsten.dominik@gmail.com"><carsten.dominik@gmail.com></a>
|
||||
</p>
|
||||
<p class="date"> Date: 2007/07/10 10:35:08</p>
|
||||
</body>
|
||||
</html>
|
@ -1,21 +0,0 @@
|
||||
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
|
||||
<html>
|
||||
<head>
|
||||
<meta HTTP-EQUIV="REFRESH" content="10;url=http://www.legito.net/worg/org-tutorials/index.php">
|
||||
<meta name="Author" content="Carsten Dominik">
|
||||
<meta name="Description" content="Ttorials now on Worg">
|
||||
<meta name="Keywords" content="Emacs,Lisp,Org-mode,XEmacs">
|
||||
<title>Tutorials now listed on Worg</title>
|
||||
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<h1>Org-mode tutorials are now maintained by the Worg project.</h1>
|
||||
|
||||
The page listing Org-mode tutorials and Screencasts is now maintained
|
||||
by the Worg project, please update your book marks to
|
||||
the <a href="http://www.legito.net/worg/org-tutorials/index.php">new
|
||||
page</a>.
|
||||
|
||||
</body>
|
||||
</html>
|
@ -5,7 +5,7 @@
|
||||
;; Author: David O'Toole <dto@gnu.org>
|
||||
;; Maintainer: Bastien Guerry <bzg AT altern DOT org>
|
||||
;; Keywords: hypermedia, outlines, wp
|
||||
;; Version: 5.23
|
||||
;; Version: 5.23a
|
||||
|
||||
;; This file is part of GNU Emacs.
|
||||
;;
|
||||
|
4
org.el
4
org.el
@ -5,7 +5,7 @@
|
||||
;; Author: Carsten Dominik <carsten at orgmode dot org>
|
||||
;; Keywords: outlines, hypermedia, calendar, wp
|
||||
;; Homepage: http://orgmode.org
|
||||
;; Version: 5.23
|
||||
;; Version: 5.23a
|
||||
;;
|
||||
;; This file is part of GNU Emacs.
|
||||
;;
|
||||
@ -84,7 +84,7 @@
|
||||
|
||||
;;; Version
|
||||
|
||||
(defconst org-version "5.23"
|
||||
(defconst org-version "5.23a"
|
||||
"The version number of the file org.el.")
|
||||
|
||||
(defun org-version (&optional here)
|
||||
|
Loading…
Reference in New Issue
Block a user