<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>
<tr><td></td><td><50></td></tr>
</tbody>
</table>
</div>
</div>
<divclass="outline-2">
<h2id="sec-3">2 Tasks</h2>
<divclass="outline-3">
<h3id="sec-4">2.1 Structure</h3>
<ul>
<li><spanclass="todo">TODO</span> Definition lists, like in Muse<br/>
</li>
<li><spanclass="todo">TODO</span> Get rid of all the \r instances, which were used only for XEmacs.<br/>
</li>
<li><spanclass="todo">IDEA</span> Should we allow #+TODO as an alias for #+SEQ<sub>TODO</sub>?<br/>
</li>
<li><spanclass="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><spanclass="todo">IDEA</span> allow different colors for different TODO keywords/tags.<br/>
</li>
<li><spanclass="todo">TODO</span> Use an indirect buffer for org-goto.<br/>
Is there a problem with the overriding map?
</li>
<li><spanclass="todo">WISH</span> Inline TODO entries<br/>
A way to put a TODO entry without starting a new section.
</li>
<li><spanclass="todo">TODO</span> Speedbar support for agenda.<br/>
Nic Ferrier has been pushing this agenda for a long time, for
example with <ahref="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><spanclass="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><spanclass="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><spanclass="todo">DECLINED</span> CSV import/export of tables?<br/>
I remember this coming up several times, for example in emails
from <ahref="http://thread.gmane.org/gmane.emacs.orgmode/156">Niels Giesen</a> and <ahref="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><spanclass="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>
</div>
<divclass="outline-3">
<h3id="sec-12">2.9 Miscellaneous Stuff</h3>
<ul>
<li><spanclass="todo">TODO</span> reinstating a repeated item: keyword for logging.<br/>
</li>
<li><spanclass="todo">BUG</span> Comments cannot be filled<br/>
</li>
<li><spanclass="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><spanclass="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><spanclass="todo">QUESTION</span> Inlining of images in Org-mode files<br/>
</li>
<li><spanclass="todo">TODO</span> Fixup outline-magic.el, so that it can be used.<br/>
</li>
<li><spanclass="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><spanclass="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 <ahref="http://members.optusnet.com.au/~charles57/GTD/orgmode.html">here</a>
</li>
<li><spanclass="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><spanclass="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><spanclass="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><spanclass="todo">INCONSISTENCY</span>: M-TAB does not work on plain lists. Why???<br/>
</li>
<li><spanclass="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><spanclass="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><spanclass="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><spanclass="todo">DECLINED</span> Inlining of external files<br/>
</li>
<li><spanclass="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><spanclass="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>
</div>
</div>
<divclass="outline-2">
<h2id="sec-13">3 Archive</h2>
<divclass="outline-3">
<h3id="sec-14">3.1 Archived Tasks</h3>
<ul>
<li><spanclass="done">DONE</span>( <spanclass="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><spanclass="done">DONE</span>( <spanclass="timestamp">2006-06-01 Thu 09:16</span>) Force relative links, would this be useful?<br/>
<li><spanclass="done">DONE</span>( <spanclass="timestamp">2006-06-01 Thu 09:16</span>) STARTUP options for logging<br/>
</li>
<li><spanclass="done">DONE</span>( <spanclass="timestamp">2006-06-01 Thu 09:16</span>) Make a variable for Pete, to have SCHEDULED at point<br/>
</li>
<li><spanclass="done">DONE</span>( <spanclass="timestamp">2006-06-01 Thu 09:16</span>) Fix ASCII export of narrowed columns<br/>
</li>
<li><spanclass="done">DONE</span>( <spanclass="timestamp">2006-06-01 Thu 09:16</span>) org-file-apps should allow regular expressions<br/>
</li>
<li><spanclass="done">DONE</span>( <spanclass="timestamp">2006-06-01 Thu 09:16</span>) fix problem with w32- versus mswindows-….<br/>
</li>
<li><spanclass="done">DONE</span>( <spanclass="timestamp">2006-06-01 Thu 09:17</span>) Document that font-lock-mode is needed<br/>
</li>
<li><spanclass="done">DONE</span>( <spanclass="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><spanclass="done">DONE</span>( <spanclass="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><spanclass="done">DONE</span>( <spanclass="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><spanclass="done">DONE</span>( <spanclass="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><spanclass="done">DONE</span>( <spanclass="timestamp">2006-06-01 Thu 09:17</span>) Put title and tags in separate classes<br/>
</li>
<li><spanclass="done">DONE</span>( <spanclass="timestamp">2006-06-01 Thu 09:17</span>) Option to leave out TAGS from export<br/>
</li>
<li><spanclass="done">DONE</span>( <spanclass="timestamp">2006-06-01 Thu 09:17</span>) Option to leave out Timestamps from export<br/>
</li>
<li><spanclass="done">DONE</span>( <spanclass="timestamp">2006-06-01 Thu 09:17</span>) Checkable items like Frank Ruell's proposal<br/>
</li>
<li><spanclass="done">DONE</span>( <spanclass="timestamp">2006-06-01 Thu 09:17</span>) Classify Keywords and time stamps<br/>
<li><spanclass="done">DONE</span>( <spanclass="timestamp">2006-06-01 Thu 09:17</span>) Change default for include-all-todo to nil<br/>
</li>
<li><spanclass="done">DONE</span>( <spanclass="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><spanclass="done">DONE</span>( <spanclass="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><spanclass="done">DONE</span>( <spanclass="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><spanclass="done">DONE</span>( <spanclass="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><spanclass="done">DONE</span>( <spanclass="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><spanclass="done">DONE</span>( <spanclass="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><spanclass="done">DONE</span>( <spanclass="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><spanclass="done">DONE</span>( <spanclass="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><spanclass="done">DONE</span>( <spanclass="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><spanclass="done">DONE</span>( <spanclass="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:
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><spanclass="done">DONE</span>( <spanclass="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><spanclass="done">DONE</span>( <spanclass="timestamp">2006-09-25 Mon 16:12</span>) Create a hook to be run after an agenda buffer has been finalized.<br/>
</li>
<li><spanclass="done">DONE</span>( <spanclass="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><spanclass="done">DONE</span>( <spanclass="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><spanclass="done">DONE</span>( <spanclass="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 <ahref="http://thread.gmane.org/gmane.emacs.orgmode/167/focus=168">Piotr's idea</a>.
</li>
<li><spanclass="done">DONE</span>( <spanclass="timestamp">2006-09-25 Mon 16:12</span>) Make org-store-link do the right thing in dired-mode<br/>
</li>
<li><spanclass="done">DONE</span>( <spanclass="timestamp">2006-11-02 Thu 10:24</span>) Control over windows being used for agenda and related buffers <spanclass="tag">NEW</span><br/>
</li>
<li><spanclass="done">DONE</span>( <spanclass="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><spanclass="done">DONE</span>( <spanclass="timestamp">2007-01-24 Wed 12:59</span>) Allow links to remote images to be inlined.<br/>
</li>
<li><spanclass="done">DONE</span>( <spanclass="timestamp">2007-01-24 Wed 12:59</span>) M-TAB on an already complete tag should add the ":"<br/>
</li>
<li><spanclass="done">DONE</span>( <spanclass="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><spanclass="done">DONE</span>( <spanclass="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><spanclass="done">DONE</span>( <spanclass="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><spanclass="done">DONE</span>( <spanclass="timestamp">2007-02-18 Sun 07:37</span>) GNUS <i><gnus:mail.general#123></i> stuff should be "Email from:…"<br/>
</li>
<li><spanclass="done">DONE</span>( <spanclass="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><spanclass="done">DONE</span>( <spanclass="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><spanclass="done">DONE</span>( <spanclass="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><spanclass="done">DONE</span>( <spanclass="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><spanclass="done">DONE</span>( <spanclass="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
