From mboxrd@z Thu Jan  1 00:00:00 1970
From: Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: org-insert-heading and inline tasks
Date: Fri, 15 Oct 2010 08:48:24 +0200
Message-ID: <76353000-2879-45E2-9E47-24842CAA4ED9@gmail.com>
References: <877hhklk5c.fsf@fastmail.fm>
Mime-Version: 1.0 (Apple Message framework v936)
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from [140.186.70.92] (port=33223 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1P6e5d-0000wv-1W
	for emacs-orgmode@gnu.org; Fri, 15 Oct 2010 02:48:29 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <carsten.dominik@gmail.com>) id 1P6e5c-0000Qy-1E
	for emacs-orgmode@gnu.org; Fri, 15 Oct 2010 02:48:28 -0400
Received: from mail-ew0-f41.google.com ([209.85.215.41]:53541)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <carsten.dominik@gmail.com>) id 1P6e5b-0000Ql-SE
	for emacs-orgmode@gnu.org; Fri, 15 Oct 2010 02:48:27 -0400
Received: by ewy5 with SMTP id 5so249190ewy.0
	for <emacs-orgmode@gnu.org>; Thu, 14 Oct 2010 23:48:27 -0700 (PDT)
In-Reply-To: <877hhklk5c.fsf@fastmail.fm>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=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: Matt Lundin <mdl@imapmail.org>
Cc: Org Mode <emacs-orgmode@gnu.org>


On Oct 14, 2010, at 8:11 PM, Matt Lundin wrote:

> Hi Carsten,
>
> The following commit changes the behavior of org-insert-heading within
> the context of inline tasks:
>
> 19d695ef8fd27ac1b1ef1b675c3960b9b7d6abdc
>
> I find that new headlines are no longer inserted at the same depth as
> inline tasks. A quick skim of the diff suggests that this is the
> intended behavior. While I understand that one would not normally  
> want a
> new headline to derive its depth from an inline task further up in the
> subtree, I often enter a few inline tasks at the same depth in quick
> succession, e.g., when creating a mini project-hierarchy from a single
> inline task.
>
> Take the following example:
>
> --8<---------------cut here---------------start------------->8---
> * My big writing project
>
> Blah blah blah blah blah blah.
>
> *************** PROJECT Add some variety to the above
> **************** TODO Look up synonyms for blah
>
> Blah blah blah blah blah blah blah.
> --8<---------------cut here---------------end--------------->8---
>
> If I hit M-RET at the beginning of the second TODO headline, I get the
> following:
>
> --8<---------------cut here---------------start------------->8---
> * My big writing project
>
> Blah blah blah blah blah blah.
>
> *************** PROJECT Add some variety to the above
> *
>
> **************** TODO Look up synonyms for blah
>
> Blah blah blah blah blah blah blah.
> --8<---------------cut here---------------end--------------->8---
>
> Would it be possible to respect the depth of an inline task if one  
> calls
> org-insert-headline directly on the headline? Normally, if I call M- 
> RET
> from an inline-task headline, I intend to insert another task at the
> same depth. This is especially true if I'd like to add an END headline
> to an inline task.

Okay, fair anough, it now works like this.

- Carsten