From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp12.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id QG0PJQT+eGOWBAEAbAwnHQ (envelope-from ) for ; Sat, 19 Nov 2022 17:02:12 +0100 Received: from aspmx1.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp12.migadu.com with LMTPS id 4IP5JAT+eGNbcQAAauVa8A (envelope-from ) for ; Sat, 19 Nov 2022 17:02:12 +0100 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 4E39F477E3 for ; Sat, 19 Nov 2022 17:02:12 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1owQHX-0006Fq-3O; Sat, 19 Nov 2022 11:01:27 -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 1owQHV-0006Fh-OX for emacs-orgmode@gnu.org; Sat, 19 Nov 2022 11:01:25 -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 1owQHT-00071c-84 for emacs-orgmode@gnu.org; Sat, 19 Nov 2022 11:01:25 -0500 Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 3BB7D24002A for ; Sat, 19 Nov 2022 17:01:21 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1668873681; bh=aIUruwZlT0prai7OTmcC/ckVka17p+ujkWwhZ1E+Gkc=; h=From:To:Cc:Subject:Date:From; b=NCnQ1PhTAzWt+YJ7U5gV8c3U7BOjPHHKRMVD6SBUC4o+d6yNlHN9IMHIvv40Lbmdm eOkUG/3sIfLAOLJsEimhbvrFAiRE2Ei/9GDwfarfU5m6DCJV9Fy+z0AHXlWk1i1+CH jP689js23e9OLxQDTRJ88sUpr0cSyZe5YJqUfFljJl85ZxMFTU60HuXzLIvgqB6qIq kA291Gu5VtoD45yzu/2zsAit8/kvRpbOzZnfLGZKlx6LmgzCZM/KKbsNar4LZ8zybS JkHga+q+nsC39iwraHdu66l5tZIjjRGEHFs2rnoCHJuJik5jjTVlAgLaNK1mVhhtej TfuRftj4dT8dA== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4NDz0b61P0z9rxM; Sat, 19 Nov 2022 17:01:16 +0100 (CET) From: Ihor Radchenko To: Bastien Cc: =?utf-8?Q?Andr=C3=A9_A=2E_Gomes?= , Timothy , emacs-orgmode@gnu.org Subject: Re: [RFC] Re: Headings and Headlines In-Reply-To: <87a64nc541.fsf@gnu.org> References: <878s1xupey.fsf@gmail.com> <87wn7z730z.fsf@localhost> <87a64nc541.fsf@gnu.org> Date: Sat, 19 Nov 2022 16:01:47 +0000 Message-ID: <87sfifkk5w.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: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 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 ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1668873732; 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=kHWgaVxuqgklIL7DhR6cbyk8+PeHM2m/oQCUFgyTN68=; b=nh7AuAA3Ob5E2UGt0mwSPilCYAVtoEn6Lu2Ch9Af8S1uPnE3sCy4njpCHIbPae7toHQ7/D upWssLFuCBgexNXcxXHzaXb5PnEr7cIFVNlYi97YI3DnTjysDSD7oTuE0GZm7S/GORDAny O3sRl3xi54EkL0FYFXUD6hPsyIKB41aPMt5X0YKdQgDmpVm1/IvffyIlmux/vvKQl0Qbz2 kRFy1QZ8QQvzT1P6nBdWUWa9QK3NjxB5272Kg4qwgdXonRWRC/KbXmHOl3Z9WdeCAt7lO4 3K4t4VVhnap1PFze/88As+P/Rcm7qd8gqeswYWmKn6YZKlC6jzMZ8kQRLG8Uqg== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1668873732; a=rsa-sha256; cv=none; b=d0OjKQSFEB3dL5dfZXqCJAlHEqUyiNvtKVp0L4kseL+oPCPzEicAgS9fdtnaugrvT33Kf/ T3Ax9W3kA3flQoXL+u5mrZiu3SYr2Zz8UjT6kJt0403xvZsxCswclxIV+GHFt90OzLK4hq wy+xAZnMP5If2E3THBF2B5JZtJxU+HgYZyT2TdYovUKS7qBqQmes+++BiwDHipvBixsGWI E4hyNT/uQe/lCZ6uQB1TXzePe1jFFmru+IzE0NZyYh6Zg7UST7mV9XSbLW2VKFfBJS5qfp mhx2O3IUER8N0/WN+XiS0SScIUSnT5kiftT4ITfH8GiJYge4qHjNPjS6cKn8AQ== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=NCnQ1PhT; dmarc=pass (policy=none) header.from=posteo.net; 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" X-Migadu-Spam-Score: -3.51 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=NCnQ1PhT; dmarc=pass (policy=none) header.from=posteo.net; 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" X-Migadu-Queue-Id: 4E39F477E3 X-Spam-Score: -3.51 X-Migadu-Scanner: scn1.migadu.com X-TUID: /9U8DSUGz+Ji Bastien writes: > Ihor Radchenko writes: > >> I know for sure >> that changing `headline' element to `heading' element type will break >> important packages like org-roam. And there is no good way to work >> around this. We cannot make symbol aliases in Elisp in scenarios like >> (memq (org-element-type ...) '(headline inlinetask)). > > We cannot make symbol aliases in Elisp but maybe we can support both > symbols for a transitory period during which we warn third-part devs > about replacing the deprecated 'headline symbol? The best idea I can come up with is the following: 1. We replace headline -> heading where it is safe 2. We introduce a new constant: org-element-heading-type, defaulting to 'headline 3. We use the new constant instead of 'headline element type symbol 4. We announce loudly that 'headline will be deprecated in favour of the new constant 5. Few years later, we change the org-element-heading-type value to 'heading >> I came to the conclusion that it will, in fact, be easier to change all >> things to use "headline" -- all the instances of "heading" in Org code >> are in function names, variable names, and docstrings. All can be >> changed using obsolete aliases. > > Given Vikas and Tim feedback, I would rather move forward by changing > "headline" to "heading" *where it does not break anything* then see if > the proposed scenario above is workable. > > In this case, I believe it's better to be partially correct (heading > where possible) than to be consistently wrong (headline everywhere) :) > > WDYT? I tried, but it will be confusing when we talk about Org elements. Phrases like "Headline element" now make sense as they correspond to the element type. Changing to "Heading element" while keeping the actual element as (headline ...) sounds extremely confusing. That said, we may do what I proposed above and then use "`org-element-heading-type' element". Somewhat cumbersome, but at least less confusing. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at