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: Sun, 29 Mar 2009 03:06:16 +0200	[thread overview]
Message-ID: <87eiwh6stz.fsf@kassiopeya.MSHEIMNETZ> (raw)
In-Reply-To: <49CE6BD9.1050100@gmx.de> (Karl Maihofer's message of "Sat, 28 Mar 2009 19:26:33 +0100")

Karl Maihofer <ignoramus@gmx.de> writes:
> Hi,
> thanks for your answer!
> Sebastian Rose schrieb:
>> 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
>>    `org-export-headline-levels'
> OK, I see. But now the text below the TODO-item is still part of the
> list. So it is indented - in html.

Hmmm - true - how are those todo items related to the rest of the text?

Todos in Org-mode are geared for TODO lists, not as annotations or

> Another idea: Why not simply use comments?
> #+HTML: <!--
> #+LaTeX: \begin{comment}
> * TODO Test
> #+LaTeX: \end{comment}
> #+HTML: -->
> I think, this should work for me.
> The only problem now is to exclude the TODO from the HTML-generated
> Table of Contents. Using "#+EXPORT_EXCLUDE_TAGS: exclude" does not work.
> Perhaps a bug in the html-export?



* TODO not exported but in agena                     :noexport:


works here.

> That looks nice. But I think this is not the right solution for me?! For
> me it is important that the TODOs are recognized by Org-Mode so that I
> can jump to the position within my document using the agenda. In the
> exported version of the file it is no problem when the TODOs are missing.

What about using links to those TODO items?


* headline

  This is the text with a [[todo-1][TODO-link]] inline...

 .... more content here, sections, lists, whatever...

# <<todo-1>>
* TODO This is the TODO

  This TODO will show up in the agenda.




* headline

  This is the text with a [[Clean the garage]] inline...

.... more content here, sections, lists, whatever...

* TODO <<Clean the garage>>

  This TODO will show up in the agenda.



This is all I can think of so far. Not exactly what you're looking for,
but maybe some of this or combinations from it might help.

  - Sebastian

  parent reply	other threads:[~2009-03-29  1:03 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
2009-03-28 18:26   ` Karl Maihofer
2009-03-28 19:16     ` Karl Maihofer
2009-03-29  1:06     ` Sebastian Rose [this message]
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=87eiwh6stz.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).