emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: bar tomas <bartomas@gmail.com>
To: Stephan Schmitt <drmabuse@cs.tu-berlin.de>
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 16:01:07 +0100	[thread overview]
Message-ID: <fdcd75820910090801l2045d233w19da184b7ea64de3@mail.gmail.com> (raw)
In-Reply-To: <4ACF4C21.4040107@cs.tu-berlin.de>

ok. Many Thanks!

On Fri, Oct 9, 2009 at 3:43 PM, Stephan Schmitt
<drmabuse@cs.tu-berlin.de> wrote:
>
> 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:
>>
>> * item1 [#A]
>> ** general stuff item1
>> general stuff  about item1
>> **subItem1
>> about subItem1
>> ** general stuff item1
>> more general stuff about item1
>>
>> So, a container in orgmode can have either subcontainers or text but
>> not a mixture of both? Is this right?
>>
>
> To be exact, a heading (container) can have both text and subheadings
> (subcontainers), but the subheadings have to follow the text.
> You can't close a subheading and go back to the previous outline level
> without a new heading.  I guess, that is a limitation of org-mode (inherited
> from outline-mode) you have to deal with.
>
> Greetings,
>        Stephan
>

  reply	other threads:[~2009-10-09 15:01 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 [this message]
2009-10-09 17:45         ` Carsten Dominik
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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  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=fdcd75820910090801l2045d233w19da184b7ea64de3@mail.gmail.com \
    --to=bartomas@gmail.com \
    --cc=drmabuse@cs.tu-berlin.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=mdl@imapmail.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
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

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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