From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: Bug in behavior of M-RET with latest Org-mode Date: Mon, 25 Feb 2013 00:13:06 -0500 Message-ID: <14212.1361769186@alphaville> References: Reply-To: nicholas.dokos@hp.com Return-path: Received: from eggs.gnu.org ([208.118.235.92]:33532) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U9qNM-0002xc-Um for emacs-orgmode@gnu.org; Mon, 25 Feb 2013 00:13:30 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1U9qNH-0003wY-Sp for emacs-orgmode@gnu.org; Mon, 25 Feb 2013 00:13:20 -0500 Received: from g1t0029.austin.hp.com ([15.216.28.36]:24463) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U9qNH-0003tc-H8 for emacs-orgmode@gnu.org; Mon, 25 Feb 2013 00:13:15 -0500 Received: from g1t0038.austin.hp.com (g1t0038.austin.hp.com [16.236.32.44]) by g1t0029.austin.hp.com (Postfix) with ESMTP id 8C7E4382C5 for ; Mon, 25 Feb 2013 05:13:07 +0000 (UTC) Received: from alphaville.americas.hpqcorp.net (openvpn.lnx.usa.hp.com [16.125.113.33]) by g1t0038.austin.hp.com (Postfix) with ESMTP id 4B1D73008A for ; Mon, 25 Feb 2013 05:13:07 +0000 (UTC) Received: from alphaville (localhost [127.0.0.1]) by alphaville.americas.hpqcorp.net (Postfix) with ESMTP id 28116471D3 for ; Mon, 25 Feb 2013 00:13:06 -0500 (EST) In-Reply-To: Message from "John Wiegley" of "Sun, 24 Feb 2013 22:25:41 CST." List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org John Wiegley 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 > * Three > > If hit M-RET at the , I'll would get: > > * One > * Two > * > * Three > > With the latest Org, I get: > > * One > * Two > * > > * 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 | 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