Correct Way to Create Sibling Headings

Correct Way to Create Sibling Headings

[Peter Jones]

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

Re: Correct Way to Create Sibling Headings

[Daniel Clemente]

Peter Jones <mlists@pmade.com> writes:

> 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)
>
  There's also:
    3. C-c return (org-ctrl-c-ret)

Re: Correct Way to Create Sibling Headings

[Carsten Dominik]

[-- Attachment #1.1: Type: text/plain, Size: 2838 bytes --]

Hi Peter,

thank you for your thoughtful post.  I tend to agree that there is  
some consistency missing in this area.  Following your post, I am  
changing the interface like this:

M-RET and M-S-RET will remain the same, i.e. they will insert the  
heading directly after the current line, therefore making any content  
of the entry part of the new entry.  I believe this still makes sense,  
because it feels more like direct editing of the text file.  In this  
case, the idea is that if you want to insert the new heading after all  
the content, you would first move the cursor to after the content.

I am redefining C-RET and C-S-RET in the way you propose.  The will  
now also insert a new heading *before* the current if the cursor is at  
the beginning of the line.  And they will achieve the insertion  
without folding siblings.

Finally, I am introducing a new option `org-insert-heading-respect- 
content', default nil.  If you set this to t, M-RET and M-S-RET will  
behave just like C-RET and C-S-RET, respectively, so in this way you  
can make this behavior the default.

I hope this will work for everyone, let me know if not.

- Carsten



On Sep 11, 2008, at 11:08 PM, Peter Jones wrote:

> 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
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode


[-- Attachment #1.2: Type: text/html, Size: 3452 bytes --]

[-- Attachment #2: Type: text/plain, Size: 204 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Correct Way to Create Sibling Headings

[Peter Jones]

Carsten Dominik <dominik@science.uva.nl> writes:
> M-RET and M-S-RET will remain the same, i.e. they will insert the
> heading directly after the current line, therefore making any content
> of the entry part of the new entry.  I believe this still makes sense,
> because it feels more like direct editing of the text file.  In this
> case, the idea is that if you want to insert the new heading after all
> the content, you would first move the cursor to after the content.
>
> I am redefining C-RET and C-S-RET in the way you propose.  The will
> now also insert a new heading *before* the current if the cursor is at
> the beginning of the line.  And they will achieve the insertion
> without folding siblings.
>
> Finally, I am introducing a new option `org-insert-heading-respect-
> content', default nil.  If you set this to t, M-RET and M-S-RET will
> behave just like C-RET and C-S-RET, respectively, so in this way you
> can make this behavior the default.

Great!  I can't wait to update and try this out.

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