From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luciano Passuello Subject: Re: Insert heading above current one Date: Fri, 29 Sep 2017 19:58:44 -0300 Message-ID: References: <874lrlmg9u.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50323) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dy4FU-0000xo-AM for emacs-orgmode@gnu.org; Fri, 29 Sep 2017 18:59:13 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dy4FP-0003aD-FV for emacs-orgmode@gnu.org; Fri, 29 Sep 2017 18:59:12 -0400 Received: from vps2.litemind.com ([192.159.65.166]:52410) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dy4FP-0003a3-An for emacs-orgmode@gnu.org; Fri, 29 Sep 2017 18:59:07 -0400 Received: from mail-lf0-f50.google.com ([209.85.215.50]:52906) by vps2.litemind.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89) (envelope-from ) id 1dy4FO-0000iI-15 for emacs-orgmode@gnu.org; Fri, 29 Sep 2017 18:59:06 -0400 Received: by mail-lf0-f50.google.com with SMTP id b127so999706lfe.9 for ; Fri, 29 Sep 2017 15:59:05 -0700 (PDT) In-Reply-To: <874lrlmg9u.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: Nicolas Goaziou Cc: Luciano Passuello , emacs-orgmode@gnu.org, Kaushal Modi Hi, thanks for the replies! >> To add, I also think that the earlier behavior made sense, if the point is >> at bolp, insert before, else insert after. > > I think the current behaviour makes more sense, if the command is called > with an universal argument. Indeed, what would be the point of using an > universal argument if you get the exact same behaviour as without it? I also think the earlier behavior made more sense. The variable org-insert-heading-respect-content (or the universal argument) controls how a new headline is inserted BELOW the current header (either add immediately after the current line or down below). I don't see how this variable should alter the behavior of adding a heading ABOVE the current header (ie. "respecting content" or not has no effect here, above is always above). > Out of curiosity is there any to set this variable to something else > than nil? There are already comfortable keybindings to set this > temporarily (C-RET and C-u M-RET). Why would one have M-RET to behave > exactly as C-RET? And even if there was a good reason to do so, why not > simply re-binding M-RET in that case? You have a good point. Looking this way, the org-insert-heading-respect-content variable is indeed of little use. But since the variable does exist (even though perhaps it should be deprecated?), it should behave correctly. And I just don't see how the behavior of adding a header above the current line should be impacted by it. Thanks! Luciano.