4 #+TYP_TODO: TODO IDEA WISH QUESTION DECLINED INCONSISTENCY BUG DONE
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 Definition lists, like in Muse
44 *** TODO Get rid of all the \r instances, which were used only for XEmacs.
45 *** TODO proper visibility cycling for items
46 Make them not hide the text after the final list item.
47 This is not trivial, we cannot usenormal outline stuff,
48 needs a separate implementaiton.
49 *** WISH Inline TODO entries
50 A way to put a TODO entry without starting a new section.
53 *** WISH Make more modes changeable from the agenda
54 These could be made available for toggling, just like
55 follow-mode. Examples:
56 - org-agenda-todo-list-sublevels
57 - org-tags-match-list-sublevels
58 - org-agenda-todo-ignore-scheduled
59 *** IDEA Sort TODO entries according to type?
60 This would apply for the list collection, not in the day entries.
61 However, I could also have a TODO keyword criterion that could be
62 used in the day entries, as one of the minor criteria.
65 *** WISH Variable of standard links for completion with C-c C-l
66 Or something like that, to make standard links fast.
67 *** IDEA Find all links to a specific file
68 *** IDEA Make info HTML links work for links to Info files
69 Info links of course only work inside Emacs. However, many info
70 documents are on the web, so the HTML exporter could try to be
71 smart and convert an Info link into the corresponding link on the
72 web. For example, we could use the GNU software site then
73 Name.HTML. Here is the link to be used:
74 http://www.gnu.org/software/emacs/manual/html_node/ Another
75 question is, is this URL going to be stable so that it makes sense
76 to actually put this into org.el?
78 *** IDEA Make news HTML links work, using Google.
79 I can use Google groups with a message id to find a USENET message,
80 even if the original link points to gnus.
82 *** TODO Remove irretrievable links from /published/ HTML output
83 This is on David's table, and he will hopefully integrate a
84 mechanism for this into org-publish.el. The discussion about this
85 was started by [[http://thread.gmane.org/gmane.emacs.orgmode/281][Austin Frank]]
87 *** TODO Document the character protection in links
88 I don't think this is really covered anywhere.
89 Maybe we also should protect characters in the visible part, to
90 make sure thing will never be on two lines...?
92 *** WISH Radio targets across files
93 I guess each org file could write a .orgtargets.filename file, if
94 it has any radio targets.
101 *** TODO Write a tutorial
102 Demonstrate running averages.
104 *** WISH Make a variable that current line should be recomputed always
105 in each table, skipping headers of course.
107 *** WISH Interactive way to get a converted table?
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.
117 **** DECLINED Column view does not yet work for Emacs 21s.
118 Declined, because I don't know how to do this. Too many
120 *** XEmacs compatibility
121 **** QUESTION Is there an issue with the coding system of HTML exported files?
122 In the code I used to have a comment saying that
123 : (and (fboundp 'coding-system-get)
124 : (boundp 'buffer-file-coding-system)
125 : buffer-file-coding-system))
126 always returns nil, implicating that setting the coding system for
127 the export buffer would not work correctly. however, I have never
128 followed up on this and never had a bug report - so I am wondering
129 if there is an issue at all.
131 **** DECLINED Column view does not yet work for XEmacs.
132 Declined, because I don't know how to do this. Too many
134 **** DECLINED Rewrite the `format' function
135 To make narrowing work under XEmacs, I would need to write a
136 version of /format/ that does transport text properties, or I
137 would have to rework narrowing entirely. Unlikely that this will
138 happen, mainly because it is working in Emacs and so does not
139 bother me personally so much. Anyway, I don't know if people are
140 actually using narrowing very much at all.
144 *** IDEA Convert links to footnotes for ASCII export.
146 *** INCONSISTENCY Find a better place for formatting checkboxes
147 Right now this is being done as part of `org-html-expand', which
148 does not seem logically correct.
153 We need to simplify the publishing options. Here are some of the
154 options for publishing projects
156 *** Publishing options
158 :`:base-directory' Directory containing publishing source files
160 :`:publishing-directory' Directory (possibly remote) where output files
163 :`:preparation-function' Function called before starting publishing
164 : process, for example to run `make' for updating
165 : files to be published.
167 :`:base-extension' Extension (without the dot!) of source files. This
168 : actually is a regular expression.
170 :`:exclude' Regular expression to match file names that should
171 : not be published, even though they have been selected
172 : on the basis of their extension.
174 :`:include' List of files to be included regardless of
175 : `:base-extension' and `:exclude'.
177 :`:publishing-function' Function executing the publication of a file.
178 : This may also be a list of functions, which will
179 : all be called in turn.
181 :`:link-validation-function' Function to validate links
183 :`:auto-index' When non-nil, publish an index during
184 : org-publish-current-project or org-publish-all.
186 :`:index-filename' Filename for output of index. Defaults to `index.org'
187 : (which becomes `index.html').
189 :`:index-title' Title of index page. Defaults to name of file.
191 :`:index-function' Plug-in function to use for generation of index.
192 : Defaults to `org-publish-org-index', which generates
193 : a plain list of links to all files in the project.
195 *** TODO Document the :recursive option
196 *** QUESTION Does anyone use the index related options
197 *** QUESTION Remove :base-extension and only use :include
198 *** WISH Simple interaction between :include :exclude :recursive
199 *** QUESTION Use an export-directory option per file?
201 For now we use publishing-directory but this is not consistent with the
202 convention of using "publishing" when there is a _project_ to publish.
204 ** Miscellaneous Stuff
205 *** BUG Comments cannot be filled
206 *** QUESTION Inlining of images in Org-mode files
207 *** TODO Fixup outline-magic.el, so that it can be used.
208 *** TODO Use the new argument of bibtex-url
209 Roland Winkler was kind enough to implement a new argument to the
210 `bibtex-url' command that allows me to retrieve the corresponding
211 URL, whether it is taken from a URL field or constructed in some
212 clever way. Currently I am not using this, because too many
213 people use an old Emacs version which does not have this.
214 however, eventually I will implement this.
216 *** QUESTION Do we need a 43 folders implementation?
217 That could easily be done in an org-mode file. But then, maybe
218 this should really be a paper thing.
221 Here is some information about priorities, which is not yet
223 **** QUOTE Priorities
224 TODO entries: 1 or 1,2,...
225 DEADLINE is 10-ddays, i.e. it is 10 on the due day
226 i.e. it goes above top todo stuff 7 days
228 SCHEDULED is 5-ddays, i.e. it is 5 on the due date
229 i.e. it goes above top todo on the due day
230 TIMESTAMP is 0 i.e. always at bottom
231 but as a deadline it is 100
232 but if scheduled it is 99
233 TIMERANGE is 0 i.e. always at bottom
234 DIARY is 0 i.e. always at bottom
238 *** INCONSISTENCY: items don't grow/shrink due to promotion.
239 In plain lists, multiple demote/promote commands executed directly
240 after each other don't change the scope of the command - the
241 initially selected text continues to be selected. This is
242 inconsistent with the behavior of outline sections, were the subtree
243 for promotion/demotion is newly defined after each command. Which
244 convention is better? Should this be consistent between trees and
247 *** INCONSISTENCY: M-TAB does not work on plain lists. Why???
249 *** QUESTION grep on directory does not yet work.
250 I am actually not sure, I might have addressed this already, but
251 my memory is failing me. Needs some checking.
253 *** DECLINED Inlining of external files
258 * COMMENT HTML style specifications
261 # org-export-html-style: "<link rel=stylesheet href=\"freeshell2.css\" type=\"text/css\"> <style type=\"text/css\"> .tag { color: red; font-weight:bold}</style>"