From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Re: Tagging a region of text without creating a branch Date: Fri, 9 Oct 2009 19:45:11 +0200 Message-ID: References: <87r5tc919n.wl@imapmail.org> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MwJWs-0000eA-Aj for emacs-orgmode@gnu.org; Fri, 09 Oct 2009 13:45:22 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MwJWn-0000aF-2C for emacs-orgmode@gnu.org; Fri, 09 Oct 2009 13:45:21 -0400 Received: from [199.232.76.173] (port=45350 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MwJWm-0000Zh-TO for emacs-orgmode@gnu.org; Fri, 09 Oct 2009 13:45:16 -0400 Received: from mail-ew0-f228.google.com ([209.85.219.228]:37570) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MwJWm-0007xB-4v for emacs-orgmode@gnu.org; Fri, 09 Oct 2009 13:45:16 -0400 Received: by ewy28 with SMTP id 28so14041336ewy.42 for ; Fri, 09 Oct 2009 10:45:15 -0700 (PDT) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: bar tomas Cc: Matt Lundin , Org Mode List 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: > > > > general stuff about item1 > about subItem1 > more general stuff about 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