emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: bar tomas <bartomas@gmail.com>
Cc: Matt Lundin <mdl@imapmail.org>, Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: Re: Tagging a region of text without creating a branch
Date: Fri, 9 Oct 2009 19:45:11 +0200	[thread overview]
Message-ID: <CDD3584C-806C-479A-9D44-03B4D792FEE1@gmail.com> (raw)
In-Reply-To: <fdcd75820910090705n1f3651e6ka5ae53fd21956a4a@mail.gmail.com>

On Oct 9, 2009, at 4:05 PM, bar tomas wrote:

> Thanks very much for your reply and your help.
> I also think in terms of containers, but I was trying to figure out if
> it is possible to have a container that has both subcontainers and
> content that is not contained in a subcontainer.
> For instance, in XML, this is the notion of an element with 'mixed
> content'(subelements+character content). For example:
> <item1 priority='A' >
> general stuff  about item1
> <subItem1> about subItem1 </subItem1>
> more general stuff about item1
> </item1>
> I suppose, this kind of structure is not possible in orgmode?
> you'd have to create 'artificial' subheadings:

This type of structure is indeed not possible in a strict outline.
However, inline tasks have been created exactly for the purpose
of working around this restriction.

The idea is to make it possible to define a task right
in the middle of a flow of text.  You can actually have some
content in such a container as well:

* a headline item1
general stuff  about item1
****************** subitem1
    Everything in here belongs to subitem one
****************** END
but here we go on about item one again.

You can achieve a similar structure in org with plain lists:

* a headline item1
   general stuff  about item1
    - subitem1
      Everything in here belongs to subitem one
      and another line
   but here we go on about item one again.

So the structure is right.  However, plain list items do not allow
tags, todo states and all that.  Inlinetasks are a hack to make
this possible.

Matt: Inline tasks are now always exported, the variable
       org-inlinetask-export is obsolete.  Export will look like
       a description list item - in fact, the export uses internally
       description lists.

Hope that this, in connection with all the other answers, will
make it clear.

- Carsten

  parent reply	other threads:[~2009-10-09 17:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-08 16:06 Tagging a region of text without creating a branch bar tomas
2009-10-08 18:10 ` Matt Lundin
2009-10-08 20:18   ` Bernt Hansen
     [not found]     ` <1f38ae890910090023h2b5cb320y1d2d778c1037d752@mail.gmail.com>
2009-10-09  7:26       ` Andrew Stribblehill
2009-10-09 13:19         ` Bernt Hansen
     [not found]   ` <fdcd75820910090229v39ec6e47m1037cb46afde19a5@mail.gmail.com>
2009-10-09 12:53     ` Matt Lundin
2009-10-09 14:05       ` bar tomas
2009-10-09 14:43         ` Stephan Schmitt
2009-10-09 15:01           ` bar tomas
2009-10-09 17:45         ` Carsten Dominik [this message]
2009-10-09 17:58           ` Matthew Lundin
2009-10-10 14:56             ` Carsten Dominik
2009-10-10 15:39               ` Matt Lundin
2009-10-12  7:29                 ` Carsten Dominik
2009-10-12 13:14                   ` Matt Lundin
2009-10-12 13:27                     ` Carsten Dominik
2009-10-12 13:40                       ` Matthew Lundin

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=CDD3584C-806C-479A-9D44-03B4D792FEE1@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=bartomas@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mdl@imapmail.org \


* 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).