Correct Way to Create Sibling Headings

[Peter Jones <mlists@pmade.com>]

I'm aware of two ways to create a sibling heading (a heading directly
after the current heading):

  1. M-return (org-meta-return)
  2. C-return (org-insert-heading-after-current)

They both operate slightly differently, but neither seem to do what I
want.

org-meta-return creates a heading directly after the current heading,
but before the properties and content of the original heading.
org-insert-heading-after-current collapses the current heading before
creating the next heading, keeping properties and content in their
correct location.

I tend to use org-insert-heading-after-current to get around this side
effect of org-meta-return, but org-insert-heading-after-current doesn't
support the same features that org-meta-return does:

 - Using the shift key to make the new heading a TODO item
 - Creating a heading *above* the current heading when used at the BOL

Plus, org-insert-heading-after-current also collapses the open headings
around it, which is often not what I want since it removes context
information.

I guess I have two questions:

  1. Is there a bug in org-meta-return that assigns the properties and
     content of the current heading to the newly created heading?

  2. What is the intended difference between M-return and C-return?

Thanks.

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