From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rick Frankel Subject: Re: [BUG] Inserting new heading Date: Thu, 16 Mar 2017 15:38:41 -0400 Message-ID: <20170316193841.oa2blasqu6hiead6@eyeBook> References: <20170315142432.3md5z6yhdymbryck@eyeBook> <878to5h1ix.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:37537) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cobET-0002w7-Ia for emacs-orgmode@gnu.org; Thu, 16 Mar 2017 15:38:46 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cobER-0000Xm-0m for emacs-orgmode@gnu.org; Thu, 16 Mar 2017 15:38:45 -0400 Received: from mail.cybercode.nyc ([45.55.183.129]:34201) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cobEQ-0000XP-SF for emacs-orgmode@gnu.org; Thu, 16 Mar 2017 15:38:42 -0400 Received: from authenticated-user (mail.cybercode.nyc [45.55.183.129]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.cybercode.nyc (Postfix) with ESMTPSA id F27C51404D8 for ; Thu, 16 Mar 2017 15:38:41 -0400 (EDT) Content-Disposition: inline In-Reply-To: <878to5h1ix.fsf@nicolasgoaziou.fr> 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" To: emacs-orgmode@gnu.org On Thu, Mar 16, 2017 at 01:03:18PM +0100, Nicolas Goaziou wrote: > Hello, > > Rick Frankel writes: > > > There is a bug w/ inserting new headings after a collapsed heading (w/ > > C-return, org-insert-heading-respect-content) if the last content under the > > heading (or a subhead) is a RESULTS: block. This occurs w/ the value of > > org-blank-before-new-entry as either '(heading . auto) or '(heading . nil). > > > > This started a few months ago, but I just figured out what actually causes the > > behavior. > Fixed. I couldn't reproduce it on maint tho, so the commit landed on > master branch. Confirmed in master. Not suprised it wasn't in maint, it's a fairly recent bug. thanx, rick