I have made a decision not to merge org-lparse, org-xhtml org-odt in
to Orgmode core. It is a very difficult decision for me to take
considering that I had put all my heart in to it. (Btw, this decision
has nothing to with me not having enough time at hand.)
I leave it up to the
Try M-x org-toc-show in your active org buffer.
You may have to activate org-toc in your org modules.
Cheers,
Thomas
@ Bastien, Jason
thank you for your response!
I made a proposal to stackexchange.com for a dedicated Org-mode site but
they rejected it as a duplicate of stackoverflow. So this option is out.
Nevertheless, I still think it would be nice to have something like this for
Org-mode only.
We could
Hello list,
after reading the responses to my initial suggestion yesterday
(http://thread.gmane.org/gmane.emacs.orgmode/44582) I've set up a
proposal on are51.stackexchange.com for a SE-site that is dedicated to
Org-mode only.
Think something like http://tex.stackexchange.com solely for
Hello,
I have been using Orgmode for the last two years. In fact, I started learning
Emacs only to use orgmode (btw: a huge thank you to Carsten and the other
contributors!).
I noticed that - as more people with a diverse range of background knowledge
start to use orgmode - the mailing list is
Jambunathan K kjambunathan at gmail.com writes:
The biggest diasadvantage would be fragmentation of information.
All information needs to have authoritative sources and archives. I
believe the info manual, GNU mailing list and the Orgmode.org domain (of
which Worg is but a part) are the
However, I started noticing I was getting lost in my own system. This
is partly because I still don't have the habit of reviewing it all
very often, but I also found out that my main gtd.org file (the one
that has projects and next actions/tasks) was getting really long. I
know I could
Richard Lawrence richard.lawrence at berkeley.edu writes:
Hi all,
I just came across this site, which looks really interesting:
http://beeminder.com/about
They provide a service for tracking progress toward (quanitifiable)
goals, and they show you a graph that includes:
-
on bugs and patches via the answers-interface.
By this, maybe at least some of the maintenance tasks can be distributed
more evenly among people who would occasionaly check out a few lines of
code but who don't feel familiar enough with lisp an a large scale.
Just a thought...
Cheers,
Thomas Renkert
