[Orgmode] Re: Fix Subtle Heading Creation Bugs

[Peter Jones]

Carsten Dominik <address@hidden> writes:
> I am not so sure about forcing headline creation even when in a plain
> list item.  I can see why you would want it like this.  However, the
> reason for the current behavior is that then you can use the respect- 
> content function as a full replacement for M-RET, without the need to
> always switch back and force between the two commands.
>
> Any thought about this?

My position is that I want both features, and I have two key bindings,
so it's a perfect match.

The way I work is that I use C-RET for creating headings, and M-RET for
creating plain lists.  I never use M-RET for creating headings because I
don't like how it creates the heading above the body of the current
item.

I could set org-insert-heading-respect-content to t, but it makes more
sense in my head that M-RET is for plain lists, and C-RET is for
headings.

Before my patch, C-RET and M-RET only differed in where the heading was
created (before or after the body).  But the original behavior of
OrgMode was that M-RET in a plain list created a new plain list item,
while C-RET in a plain list would create a new heading.

However, this could all be chalked up to me being lazy.  I could just as
easily do this in a plain list instead: RET C-RET.  Well, except that
with my patch, C-RET will create a new heading, even if point is in a
drawer or something like a clock line.  In that case I could do C-u
C-RET.  

I just like the path of least resistance for creating new headings,
C-RET.  If this isn't good for OrgMode in general, I can easily bind C-j
to do what I want as well.

Thanks.

-- 
Peter Jones, http://pmade.com
pmade inc.  Louisville, CO US