4 #+TYP_TODO: TODO IDEA WISH QUESTION INCONSISTENCY BUG | DONE DECLINED
6 #+OPTIONS: H:2 num:t toc:t \n:nil @:t ::t |:t ^:t *:t TeX:t
7 #+ARCHIVE: ::** Archived Tasks
8 #+EMAIL: carsten.dominik@gmail.com
9 #+TITLE: The Org-mode TODO list
13 This is a loose collection of ideas and TODO items for the future
14 development of Org-mode. These ideas come from various sources,
15 mostly from emacs-orgmode@gnu.org, from direct emails to me, or from
16 my own day-dreaming. I don't always mention the source of an idea,
17 out of laziness. However, when I implement a good idea, I try to
18 mention the origin of this idea in the /Acknowledgments/ section of
19 the manual - let me know if I forgot to give /you/ credit for
23 On this page, I am using TODO keywords in the following way:
24 |-----------------+----------------------------------------------------|
25 | *Keyword* | Intention |
26 |-----------------+----------------------------------------------------|
27 | *TODO* | A development that is going to happen, once I have time or once I figure out how to do it. |
28 | *IDEA* | A new idea, I have not yet decided what if anything I will do about it. |
29 | *WISH* | A wish, probably voiced by someone on emacs-orgmode@gnu.org. This is less than a new idea, more a change in existing behavior. |
30 | *QUESTION* | A question someone asked, that needs some thinking before it can be answered |
31 | *DECLINED* | 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. |
32 | *INCONSISTENCY* | Some behavior in Org-mode that is not as clean and consistent as I would like it to be. |
33 | *BUG* | This needs to be fixed, as soon as possible. |
34 | *DONE* | Well, done is done. |
35 | /NEW/ | This is a tag, indicating recently added entries |
37 |-----------------+----------------------------------------------------|
43 *** TODO Get rid of all the \r instances, which were used only for XEmacs.
44 *** TODO proper visibility cycling for items
45 Make them not hide the text after the final list item.
46 This is not trivial, we cannot usenormal outline stuff,
47 needs a separate implementaiton.
48 *** WISH Inline TODO entries
49 A way to put a TODO entry without starting a new section.
52 *** WISH Make more modes changeable from the agenda
53 These could be made available for toggling, just like
54 follow-mode. Examples:
55 - org-agenda-todo-list-sublevels
56 - org-tags-match-list-sublevels
57 - org-agenda-todo-ignore-scheduled
58 *** IDEA Sort TODO entries according to type?
59 This would apply for the list collection, not in the day entries.
60 However, I could also have a TODO keyword criterion that could be
61 used in the day entries, as one of the minor criteria.
63 Right now we can already sort an outline tree according to
64 children, this is nice already. However, sorting in the agenda
65 would be nice too. The problem is, that i the agenda we may have
66 todo lists from a number of different buffers, so the sorting
67 relation may not be clear.....
70 *** WISH Variable of standard links for completion with C-c C-l
71 Or something like that, to make standard links fast.
72 *** IDEA Find all links to a specific file
73 *** IDEA Make info HTML links work for links to Info files
74 Info links of course only work inside Emacs. However, many info
75 documents are on the web, so the HTML exporter could try to be
76 smart and convert an Info link into the corresponding link on the
77 web. For example, we could use the GNU software site then
78 Name.HTML. Here is the link to be used:
79 http://www.gnu.org/software/emacs/manual/html_node/ Another
80 question is, is this URL going to be stable so that it makes sense
81 to actually put this into org.el?
83 *** IDEA Make News HTML links work, using Google.
84 I can use Google groups with a message id to find a USENET message,
85 even if the original link points to gnus.
87 *** TODO Remove irretrievable links from /published/ HTML output
88 This is on David's table, and he will hopefully integrate a
89 mechanism for this into org-publish.el. The discussion about this
90 was started by [[http://thread.gmane.org/gmane.emacs.orgmode/281][Austin Frank]]
92 *** TODO Document the character protection in links
93 I don't think this is really covered anywhere.
94 Maybe we also should protect characters in the visible part, to
95 make sure thing will never be on two lines...?
97 *** WISH Radio targets across files
98 I guess each org file could write a .orgtargets.filename file, if
99 it has any radio targets.
103 *** WISH Row formulas
106 *** WISH Make a variable that current line should be recomputed always
107 in each table, skipping headers of course.
109 *** BUG When computing in a narrowed column, this may go wrong.
110 Computing changes fields and does not yet see correctly if the column
111 width has changed, in the case of a narrowed column.
113 ** Compatibility issues
114 *** Emacs 21 compatibility
115 This is being phased out. Almost everything works under Emacs 21,
116 but in the future I will make little effort to support it.
118 *** XEmacs compatibility
121 *** IDEA Convert links to footnotes for ASCII export.
122 But the question is: where should these footnotes be placed?
126 We need to simplify the publishing options. Here are some of the
127 options for publishing projects
129 *** Publishing options
131 :`:base-directory' Directory containing publishing source files
133 :`:publishing-directory' Directory (possibly remote) where output files
136 :`:preparation-function' Function called before starting publishing
137 : process, for example to run `make' for updating
138 : files to be published.
140 :`:base-extension' Extension (without the dot!) of source files. This
141 : actually is a regular expression.
143 :`:exclude' Regular expression to match file names that should
144 : not be published, even though they have been selected
145 : on the basis of their extension.
147 :`:include' List of files to be included regardless of
148 : `:base-extension' and `:exclude'.
150 :`:publishing-function' Function executing the publication of a file.
151 : This may also be a list of functions, which will
152 : all be called in turn.
154 :`:link-validation-function' Function to validate links
156 :`:auto-index' When non-nil, publish an index during
157 : org-publish-current-project or org-publish-all.
159 :`:index-filename' Filename for output of index. Defaults to `index.org'
160 : (which becomes `index.html').
162 :`:index-title' Title of index page. Defaults to name of file.
164 :`:index-function' Plug-in function to use for generation of index.
165 : Defaults to `org-publish-org-index', which generates
166 : a plain list of links to all files in the project.
168 *** TODO Document the :recursive option
169 *** QUESTION Does anyone use the index related options
170 *** QUESTION Remove :base-extension and only use :include
171 *** WISH Simple interaction between :include :exclude :recursive
172 *** QUESTION Use an export-directory option per file?
174 For now we use publishing-directory but this is not consistent with the
175 convention of using "publishing" when there is a /project/ to publish.
177 ** Miscellaneous Stuff
178 *** BUG Comments cannot be filled
179 *** QUESTION Inlining of images in Org-mode files
180 *** TODO Fixup outline-magic.el, so that it can be used.
182 *** TODO Use the new argument of bibtex-url
183 Roland Winkler was kind enough to implement a new argument to the
184 `bibtex-url' command that allows me to retrieve the corresponding
185 URL, whether it is taken from a URL field or constructed in some
186 clever way. Currently I am not using this, because too many
187 people use an old Emacs version which does not have this.
188 however, eventually I will implement this.
190 *** QUESTION Do we need a 43 folders implementation?
191 That could easily be done in an org-mode file. But then, maybe
192 this should really be a paper thing.
195 Here is some information about priorities, which is not yet
196 documented. Actually, I am not sur if the list here is correct
197 **** QUOTE Priorities
198 TODO entries: 1 or 1,2,...
199 DEADLINE is 10-ddays, i.e. it is 10 on the due day
200 i.e. it goes above top todo stuff 7 days
202 SCHEDULED is 5-ddays, i.e. it is 5 on the due date
203 i.e. it goes above top todo on the due day
204 TIMESTAMP is 0 i.e. always at bottom
205 but as a deadline it is 100
206 but if scheduled it is 99
207 TIMERANGE is 0 i.e. always at bottom
208 DIARY is 0 i.e. always at bottom
212 *** INCONSISTENCY: items don't grow/shrink due to promotion.
213 In plain lists, multiple demote/promote commands executed directly
214 after each other don't change the scope of the command - the
215 initially selected text continues to be selected. This is
216 inconsistent with the behavior of outline sections, were the subtree
217 for promotion/demotion is newly defined after each command. Which
218 convention is better? Should this be consistent between trees and
221 *** INCONSISTENCY: M-TAB does not work on plain lists. Why???
223 *** QUESTION grep on directory does not yet work.
224 I am actually not sure, I might have addressed this already, but
225 my memory is failing me. Needs some checking.
227 *** DECLINED Inlining of external files
231 *** DONE Definition lists, like in Muse
233 :ARCHIVE_TIME: 2008-05-29 Thu 17:01
234 :ARCHIVE_FILE: ~/lib/emacs/work/org-mode/ORGWEBPAGE/todo.org
235 :ARCHIVE_OLPATH: Tasks/Structure
236 :ARCHIVE_CATEGORY: todo
240 * COMMENT HTML style specifications
243 # org-export-html-style: "<link rel=stylesheet href=\"freeshell2.css\" type=\"text/css\"> <style type=\"text/css\"> .tag { color: red; font-weight:bold}</style>"