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 Acknowledgments section of the manual - let me know if I forgot to give you credit for something.
On this page, I am using TODO keywords in the following way:
| Keyword | Intention |
|---|---|
| TODO | A development that is going to happen, once I have time or once I figure out how to do it. |
| IDEA | A new idea, I have not yet decided what if anything I will do about it. |
| 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. |
| QUESTION | A question someone asked, that needs some thinking before it can be answered |
| 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. |
| INCONSISTENCY | Some behavior in Org-mode that is not as clean and consistent as I would like it to be. |
| BUG | This needs to be fixed, as soon as possible. |
| DONE | Well, done is done. |
| NEW | This is a tag, indicating recently added entries |
| <50> |
(and (fboundp 'coding-system-get)
(boundp 'buffer-file-coding-system)
buffer-file-coding-system))
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.
We need to simplify the publishing options. Here are some of the options for publishing projects
`:base-directory' Directory containing publishing source files
`:publishing-directory' Directory (possibly remote) where output files
will be published.
`:preparation-function' Function called before starting publishing
process, for example to run `make' for updating
files to be published.
`:base-extension' Extension (without the dot!) of source files. This
actually is a regular expression.
`:exclude' Regular expression to match file names that should
not be published, even though they have been selected
on the basis of their extension.
`:include' List of files to be included regardless of
`:base-extension' and `:exclude'.
`:publishing-function' Function executing the publication of a file.
This may also be a list of functions, which will
all be called in turn.
`:link-validation-function' Function to validate links
`:auto-index' When non-nil, publish an index during
org-publish-current-project or org-publish-all.
`:index-filename' Filename for output of index. Defaults to `index.org'
(which becomes `index.html').
`:index-title' Title of index page. Defaults to name of file.
`:index-function' Plug-in function to use for generation of index.
Defaults to `org-publish-org-index', which generates
a plain list of links to all files in the project.
For now we use publishing-directory but this is not consistent with the convention of using "publishing" when there is a project to publish.
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