Org-mode mailing list
 help / color / Atom feed
From: Karl Maihofer <ignoramus@gmx.de>
To: emacs-orgmode@gnu.org
Subject: How to define TODOs within continuous text the best way?
Date: Sat, 28 Mar 2009 15:23:40 +0100
Message-ID: <49CE32EC.5060508@gmx.de> (raw)

Hi,

I write some articles in Org-Mode and use the html and latex export
function. I'm wondering about how to define TODOs within the text the
best way. I hope my bad english lasts to explain what I mean exactly:

I'd like to define a TODO like in the example below. When there is a
task somewhere in my text (I want to look something up etc.) I want to
define this task at the relevant position in my text. So I can lookup
all TODOs using the agenda-view and jump directly to the position in my
text.

The problem is that a TODO is always a new heading and so it is exported
in my html(latex)-version as a heading. I would prefer to format a TODO
as a text box or at least to exclude it from the html(latex)-export so
that it is only visible in org-mode - not in the exported version. But
when I exclude the TODO so that it isn't exported anymore, not only the
TODO itself but also the text below the TODO isn't exported until there
is a new heading - because the TODO itself is a heading, too.

I know that this is because Org-Mode is an outliner-mode, TODOs always
have to be defined with a beginning "*". But is there any possibility to
solve the problem? How do you define TODOs within the text when you use
Org-Mode as an authoring tool?

Perhaps it is possible to define TODOs as a very deep-level heading,
that isn't needed, like "********** TODO text" and change the export
function that this level isn't exported as a heading but as a
"div"-Container? Or every heading that contains "TODO" is not exported
as a heading but as a div-container?

What is the best way to handle TODOs within continuous text?

Kind regards,
Karl

-----------------------------------------------------------------------
* Heading 1

Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy
eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam
voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet
clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit
amet.

* TODO Check again (or ********** TODO text?)

This paragraph still belongs to heading 1. Lorem ipsum dolor sit amet,
consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut
labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et
accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no
sea takimata sanctus est Lorem ipsum dolor sit amet.

* Heading 2

Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy
eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam
voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet
clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit
amet.

-----------------------------------------------------------------------

             reply index

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-28 14:23 Karl Maihofer [this message]
2009-03-28 17:16 ` Sebastian Rose
2009-03-28 18:26   ` Karl Maihofer
2009-03-28 19:16     ` Karl Maihofer
2009-03-29  1:06     ` Sebastian Rose
2009-03-28 17:42 ` Sebastian Rose
2009-03-30 11:47 ` Carsten Dominik
2009-03-30 20:18   ` Bernt Hansen
2009-03-30 20:53     ` Carsten Dominik
2009-03-30 21:20       ` Bernt Hansen
2009-03-31 15:23   ` Karl Maihofer
2009-03-31 18:14     ` Carsten Dominik
2009-03-31 19:53   ` Daniel Clemente
2009-04-01 10:05     ` Carsten Dominik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://orgmode.org

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49CE32EC.5060508@gmx.de \
    --to=ignoramus@gmx.de \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Org-mode mailing list

Archives are clonable:
	git clone --mirror https://orgmode.org/list/0 list/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 list list/ https://orgmode.org/list \
		emacs-orgmode@gnu.org
	public-inbox-index list

Example config snippet for mirrors

Newsgroups are available over NNTP:
	nntp://news.yhetil.org/yhetil.emacs.orgmode
	nntp://news.gmane.io/gmane.emacs.orgmode


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git