Re: Bug in behavior of M-RET with latest Org-mode

[Nick Dokos <nicholas.dokos@hp.com>]

John Wiegley <johnw@newartisans.com> wrote:

> In Org I've liked that fact that hitting M-RET in a list of headlines which
> have no intervening whitespace, will add a new headline without whitespace.
> Example:
> 
>     * One
>     * Two<cursor>
>     * Three
> 
> If hit M-RET at the <cursor>, I'll would get:
> 
>     * One
>     * Two
>     * <cursor>
>     * Three
> 
> With the latest Org, I get:
> 
>     * One
>     * Two
>     * <cursor>
> 
>     * Three
> 
> Is this just a regression, or has the core behavior been changed to do this?
> Is there a new variable I need to tweak to get the old behavior?
> 

This I think:

,----
| org-blank-before-new-entry is a variable defined in `org.el'.
| Its value is ((heading) (plain-list-item))
| Original value was 
| ((heading . auto)
|  (plain-list-item . auto))
| 
| 
| Documentation:
| Should `org-insert-heading' leave a blank line before new heading/item?
| The value is an alist, with `heading' and `plain-list-item' as CAR,
| and a boolean flag as CDR.  The cdr may also be the symbol `auto', in
| which case Org will look at the surrounding headings/items and try to
| make an intelligent decision whether to insert a blank line or not.
| 
| For plain lists, if the variable `org-empty-line-terminates-plain-lists' is
| set, the setting here is ignored and no empty line is inserted, to avoid
| breaking the list structure.
`----

Given that this was introduced a long time ago however, I'm not sure what
caused the recent change in behavior:

,----
| $ git show 15ad97ac
| commit 15ad97ac3ce0857b92d94cc02d15025fcce05b7d
| Author: Carsten Dominik <carsten.dominik@gmail.com>
| Date:   Thu Jan 8 09:30:55 2009 +0100
| 
|     Editing: Automatic empty lines before new entries.
|     
|     The variable `org-blank-before-new-entry' regulates if Org should
|     insert a blank line before a new entry, when making a new headline or
|     plain list item.  Up to now, the possible values in each case where t
|     or nil, i.e. unconditionally do or don't insert a blank line.
|     
|     Now each setting can also be `auto'.  If this is the case,  Org will
|     look if the current entry, of which the command creates a sibling,
|     does have a blank line before it.  If yes, it will also make a blank
|     line.  If not, it will not.  This seems so useful that I have made
|     this behavior the default.
`----

Nick