From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1.migadu.com ([2001:41d0:403:58f0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms8.migadu.com with LMTPS id yDZXIpUyvmUGIQEA62LTzQ:P1 (envelope-from ) for ; Sat, 03 Feb 2024 13:33:25 +0100 Received: from aspmx1.migadu.com ([2001:41d0:403:58f0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1.migadu.com with LMTPS id yDZXIpUyvmUGIQEA62LTzQ (envelope-from ) for ; Sat, 03 Feb 2024 13:33:25 +0100 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=DOBWtEQ4; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=posteo.net ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1706963605; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=JPcW5ipUZHnM1Ydnym0g4w2hLNipSpZI/uGT+PhJE44=; b=Ay9ARjM+jfozD7dOCswkQ/Z6QHmaBwP5YaQk4wJKvHZhxbu3ybontjCfdiE5PJzxfaL60x Q+v2IMgDWu/PudmJAyvyY66oiHAzF1zNQwZSPZagnnMd4KHjjWeF7Oe9/Y4tQMrXM1g9PV xV0Q9MQwD08ubElvPnQ+7lSi+V78RZ0gPmM/4nt1nAidksPzPOaZ7mHhRFqiGzGLqfNxu5 mboUACX6Y88W1XchY8Ch/l3T+z55ss/zaU58wAe+/f5oWi8y4YuYw6wUIADsB0TZvltxO4 vdkl6dCUII6Y4XfgjbpDgp7Oln9X/EVe3s1WsF42Nad8gdjqXSmFKa1K3qlAPQ== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=DOBWtEQ4; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=posteo.net ARC-Seal: i=1; s=key1; d=yhetil.org; t=1706963605; a=rsa-sha256; cv=none; b=t0aONR98qrlXvRuPMbLBEer4cG0LVJlUR4P4FiNk+e/Jf6KoV92HaOH7dNlRJhOALnCovU a+zFZC2aPZe1V+oSiDSjyLlUhQVGqIHHTerb8f3ZtcIY9IwNMos6Ood9KrwzAjCCF2c8Cu fiDGfcz+EALew7/NzH3kF+JjTHiOdnGWSvqleQaTPrux3ZJKbaecwd22AiY9uV4qf/g8/X 0qUND+BhB8QOugSjtW/c3ulh0H29Al9/LWcXYUvUJcwf5mJD9GOmoF3KpLWz15FhYxNnCG EL7d8depIPHLTGhpSskMKypSy6IbW8hplCGbFrRI66GkoNizIfsN4QFZS3sHmw== Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 978DC6CE5D for ; Sat, 3 Feb 2024 13:33:24 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rWFC4-0006xs-Aj; Sat, 03 Feb 2024 07:32:24 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rWFC2-0006xW-ER for emacs-orgmode@gnu.org; Sat, 03 Feb 2024 07:32:22 -0500 Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rWFC0-0002HB-3D for emacs-orgmode@gnu.org; Sat, 03 Feb 2024 07:32:21 -0500 Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id F3769240027 for ; Sat, 3 Feb 2024 13:32:16 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1706963537; bh=Gtbnil+GxvWbe3ngTFlNXWEqvJyf7XiOEEZErc1Jse4=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: From; b=DOBWtEQ4MmYrkAn0sugBr/ozxrLGMD7PXnfhiHdrf6uWKUb7hLUksjynZf5Sg98tk JmFtRW+gsx0yQ65ASlWYkIyrUU8A7H8QSRa6IvW2/OPdenatejarU6FOlA3kgvN9SB qvBzdbv3Ucl7tx0KwMbGst0+cXq1qnEn1cQr394DHXalxdF/qyQtEY8+xL5UweejOv TmBvmv34c8E2Z63g/ZjdOhwXC0VxMJzEQFIYBk8yqAV/euF3DBrd5jmQPVNPGTcLcu TmcLn7uTU7zjQyc55bgDJq4SnlAxWG6ASly5vX4kt0gocOyH12zezhX5iAjbDIlJ1/ 44COttXFFmeqw== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4TRsTq6Fz2z6twC; Sat, 3 Feb 2024 13:32:15 +0100 (CET) From: Ihor Radchenko To: gusbrs Cc: org-mode list Subject: Re: [BUG] org-insert-heading changed behavior with Emacs 29.2 [9.6.15 (release_9.6.15 @ /usr/local/share/emacs/29.2/lisp/org/)] In-Reply-To: References: Date: Sat, 03 Feb 2024 12:35:41 +0000 Message-ID: <877cjl67z6.fsf@localhost> MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=185.67.36.65; envelope-from=yantar92@posteo.net; helo=mout01.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: emacs-orgmode-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US X-Migadu-Spam-Score: -7.26 X-Migadu-Queue-Id: 978DC6CE5D X-Spam-Score: -7.26 X-Migadu-Scanner: mx11.migadu.com X-TUID: lJ85oVe9O3tg gusbrs writes: > I recently upgraded to Emacs 29.2 (from 29.1) and observed that > `org-insert-heading-respect-content' has changed behavior with regard > to how it handles blank lines at the end of the entry at which the > command was called. > > Consider the following document (with "|" representing point): > > ** |SubSec1 > > text > > ** SubSec2 > Calling `org-insert-heading-respect-content' ("C-RET") with Org > version 9.6.6 (built-in Emacs 29.1) would result in: > ... > ** | > > ** SubSec2 > > Now, with Org version 9.6.15 (built-in Emacs 29.2), it results in: > ... > ,** | > ,** SubSec2 > > That is an unfortunate change of behavior since those who like to keep > some breathing space at the end of entries now have to deal with it > manually after the heading is inserted. So the handy "C-RET" becomes > something like "C-RET RET C-b SPC". Plus the cost of having to think > about it, and that of occasionally forgetting it, consistency is just > harder to maintain. The number of blank lines after newly inserted is not defined by Org mode, unlike the number of blank lines before heading that is controlled by `org-blank-before-new-entry'. If you use M- rather then C- and set (setq org-blank-before-new-entry '((heading) (plain-list-item))) , you will get no newlines after the new heading inserted before current: * Sec1 ** SubSec1 M- will yield * Sec1 ** ** SubSec1 Would it make sense to add a new `org-blank-after-new-entry' customization that will provide explicit user control over what Org does when inserting a new heading? -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at