From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1.migadu.com ([2001:41d0:403:4876::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms8.migadu.com with LMTPS id OIIsBShDvmX5/AAA62LTzQ:P1 (envelope-from ) for ; Sat, 03 Feb 2024 14:44:08 +0100 Received: from aspmx1.migadu.com ([2001:41d0:403:4876::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1.migadu.com with LMTPS id OIIsBShDvmX5/AAA62LTzQ (envelope-from ) for ; Sat, 03 Feb 2024 14:44:08 +0100 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20230601 header.b=RPI9KqAt; dmarc=pass (policy=none) header.from=gmail.com; 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" ARC-Seal: i=1; s=key1; d=yhetil.org; t=1706967847; a=rsa-sha256; cv=none; b=KqYNu4WxM85PsJKwGuK6m06QljbGnPfkTvyoD4jU/tqHJ56/uQS6tB0Xf6zB8JO4fEAJLe 5x9vNjPIM0eZBT1M219nbjindeRRa5wBuAC8//7nIkzp3+vFDGTDavJcvF23O3NwDdo6Qi B2X9Wro+dWsatzgznHGJ85sxLG4CzpolXH1ZZHgqgnujxXsIdQgU0DDtwbTL+s8S4dhBR9 m14agDEAbb6yVGI0aVQFH5NU3N6ilUrVsKR8aYrgy2ZryevQZ/MRgM4T6jpwv8Lv8sEUvg rCXyW1/tBckiXbP2X4F4u1wxLkqNhdCITpGQ4q9Qjn1q4OhZS145yS0P+Lw77g== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20230601 header.b=RPI9KqAt; dmarc=pass (policy=none) header.from=gmail.com; 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" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1706967847; 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=R9/Sd1BcZKnDNfoz5MPsQAfjNFKOwJNAllh9GN70O2Q=; b=LKMJ1tViN6k2T6NT15L4zwfa3hYPCaOa4Ldy+Y4LI0bGHIJd3ci8iPhRBKmkhhQ6KZimoJ bSMy+elyTI3L+9/5VRK+sQUTarnLUtzJBTRDL/NYaTYt72MxpfBCQkiawrRZUl9j3tbfz3 M3iA9Gt6oQA8bArp6BeufgF46o3AiN4rjb/AjR4fP08uehv6807p20Z70vreG2ro6SIr3A zEwKZEzv/7z505ouWxCVgTZXXfjGxl/Y781xNXuwqqQO52xLG4spBLdD6wbv6F9B4vdm7s 9l7fP7lHEHdBF5WrkY3s9b6X2QaBHwVZas+EWMEVBsw4oloRsql1v8R7fHuwmg== 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 B19E876713 for ; Sat, 3 Feb 2024 14:44:07 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rWGId-000163-9O; Sat, 03 Feb 2024 08:43:15 -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 1rWGIb-00015t-RS for emacs-orgmode@gnu.org; Sat, 03 Feb 2024 08:43:13 -0500 Received: from mail-yb1-xb2c.google.com ([2607:f8b0:4864:20::b2c]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1rWGIa-0004Ip-BS for emacs-orgmode@gnu.org; Sat, 03 Feb 2024 08:43:13 -0500 Received: by mail-yb1-xb2c.google.com with SMTP id 3f1490d57ef6-dc6d8f31930so1353392276.0 for ; Sat, 03 Feb 2024 05:43:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1706967791; x=1707572591; darn=gnu.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=R9/Sd1BcZKnDNfoz5MPsQAfjNFKOwJNAllh9GN70O2Q=; b=RPI9KqAt8lYWn9G3/rnJbj/BdY49/bdl9HHU4PQDzHR0Fw8DgA7A3lMlmPKabWnFM9 9Y7kjDsuFNgokK322xqCdwJ4ozeSiA2Va6NWZxlxvWSpx6URxxchTc5JTHHAbqqQkmry MXop3PWlSTvbh4ouZld4r+JIjs9q3C37/29fjuYu5MfltkFua4rN5yMkvpwXOovLnOZg RSa1WwARlCcRKTZ40/53/TbDkFTkWf2ioH/n/nyh7pRS/SPX/1JdWN9eGmgzJsC8suvB gT2aWGp17iZWYPvJtEHvfs1PNzJ+z8UM18beaZDnDV3WE54cQ9U9teNF9APXMmrf5AEZ mt7Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1706967791; x=1707572591; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=R9/Sd1BcZKnDNfoz5MPsQAfjNFKOwJNAllh9GN70O2Q=; b=iKOGVUOOy4V1CJb3fUfTesbCYQ4dpzCiZSfE6P9lIWt0RWBAgr7Ea13aHH43PEAJah qzMpJTuIlt50PvMEQxsRUZwdTnBxyeiZzd9WqRp4qOBZxrO6kJw3cX9+QLPEpC+filUb FOWQ5oX8u1j83Ww4PoVMhkv+CnAYonrGXNYDca/ayf9ulhX7qf2egU16eSf0hQvOSCOI IyB6jgbLYOkkFibeYQWwBG9BZuYy4tq7pLXG6PoNPA7kPCmlfci2JDlyIn/DaL64JEmx DOhaVvxX8Wt/kzX0Eceob9yw5HuB2svPa4eNtsA4AquALhbuS8YtDubNf71OtZuUuPVv TfWQ== X-Gm-Message-State: AOJu0YxklcUO+UC6i6Dc+lWIkdBJcFmbBgJ+Q3moiC/ckKpAGSnVYQmz d/LmtP8EjU/+1iqWbMee68pM8dgT95yTfdOXCJ267NhIZ5yuDM/dZGtt1uzzmC31kZAwqcEagHl 6njgpxl1sQDxd+oBlhMOIj+Gh7Xo= X-Google-Smtp-Source: AGHT+IEwHnemogK1Ss7f0ynTWH3fmEYnRGT1PdY2yn1m1sh01Q9APa/3zZTssKCtfBJqF545AOEHKgelLfbztIAv5w8= X-Received: by 2002:a05:6902:240f:b0:dc6:ca3a:31da with SMTP id dr15-20020a056902240f00b00dc6ca3a31damr1045556ybb.16.1706967790773; Sat, 03 Feb 2024 05:43:10 -0800 (PST) MIME-Version: 1.0 References: <877cjl67z6.fsf@localhost> In-Reply-To: From: gusbrs Date: Sat, 3 Feb 2024 10:42:59 -0300 Message-ID: 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/)] To: Ihor Radchenko Cc: org-mode list Content-Type: text/plain; charset="UTF-8" Received-SPF: pass client-ip=2607:f8b0:4864:20::b2c; envelope-from=gtvbrs@gmail.com; helo=mail-yb1-xb2c.google.com X-Spam_score_int: -10 X-Spam_score: -1.1 X-Spam_bar: - X-Spam_report: (-1.1 / 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, FREEMAIL_FROM=0.001, HK_RANDOM_ENVFROM=0.998, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no 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-Scanner: mx10.migadu.com X-Spam-Score: -7.01 X-Migadu-Queue-Id: B19E876713 X-Migadu-Spam-Score: -7.01 X-TUID: 43sDAPERR4oO Hi, On Sat, 3 Feb 2024 at 10:27, gusbrs wrote: > On Sat, 3 Feb 2024 at 09:32, Ihor Radchenko wrote: > > 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? > > Looking from the perspective of C-RET alone, I'd be inclined to > restate my suggestion of treating the issue that motivated that commit > as a "visibility / folding" problem. However, including M-RET into the > mix, I think you have a good point, and something like > `org-blank-after-new-entry' would possibly help improve blank line > consistency in general. A couple of further comments about this. First, I think exposing a `org-blank-after-new-entry' is a good idea also on the grounds that it becomes a commitment to a desired/desirable behavior. And would offer more control. Also, something like `(setq org-blank-after-new-entry '((heading . auto)))' would arguably have to keep the number of lines existing at the end of the current entry. In other words, implement (by other means) the behavior which used to prevail before the commit in discussion. Best, gusbrs