emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Sebastian Rose <sebastian_rose@gmx.de>
To: Karl Maihofer <ignoramus@gmx.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: How to define TODOs within continuous text the best way?
Date: Sat, 28 Mar 2009 18:16:33 +0100	[thread overview]
Message-ID: <873acx8t5a.fsf@kassiopeya.MSHEIMNETZ> (raw)
In-Reply-To: <49CE32EC.5060508@gmx.de> (Karl Maihofer's message of "Sat, 28 Mar 2009 15:23:40 +0100")

Karl Maihofer <ignoramus@gmx.de> writes:
> 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?

Yes, this is possible. By default only the first three levels are
exported as headlines. Any headline that is deeper nested, is exported
as a list item.

The variable in question is


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

Those list items are not displayed inline, but produce no entry in the

I have several commands like that defined (\rzidea, ...) and some
produce a box with an icon and frame, that does not use the margin.

Here's the inline version:

=> --->8----------------------------->8----------------------------->8---

\newcommand { \rztodoinline }

<= ---8<-----------------------------8<-----------------------------8<---

For things I need to fix in the document itself, I prefer a more visible
presentation of TODOs. For LaTeX/PDF I even use this here:

=> --->8----------------------------->8----------------------------->8---
* Headline

  some text here...

  \rztodo{Description of todo.}

  more text here...

<= ---8<-----------------------------8<-----------------------------8<---

\rztodo is command defined in an LaTeX include file:

=> --->8----------------------------->8----------------------------->8---

\newcommand { \rztodo }

<= ---8<-----------------------------8<-----------------------------8<---

This creates a _very_ visible box in the margin and the result looks
like this (TODO is white on red):

=> --->8----------------------------->8----------------------------->8---

1 Headline

  some text here...

  ------------------------------------------------------  +------+
  Description of todo.                                    | TODO |
  ------------------------------------------------------  +------+

  more text here...

<= ---8<-----------------------------8<-----------------------------8<---

Best Regards,


  reply	other threads:[~2009-03-28 17:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-28 14:23 How to define TODOs within continuous text the best way? Karl Maihofer
2009-03-28 17:16 ` Sebastian Rose [this message]
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:

  List information: https://www.orgmode.org/

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

  git send-email \
    --in-reply-to=873acx8t5a.fsf@kassiopeya.MSHEIMNETZ \
    --to=sebastian_rose@gmx.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=ignoramus@gmx.de \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).