From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2.migadu.com ([2001:41d0:303:e16b::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms8.migadu.com with LMTPS id oIhCA4rK6WWMSAEAe85BDQ:P1 (envelope-from ) for ; Thu, 07 Mar 2024 15:09:14 +0100 Received: from aspmx1.migadu.com ([2001:41d0:303:e16b::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2.migadu.com with LMTPS id oIhCA4rK6WWMSAEAe85BDQ (envelope-from ) for ; Thu, 07 Mar 2024 15:09:14 +0100 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=NHaSA3Lw; 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=1709820554; 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=RvUi08CHhFva9c58ShHUCjp2GQ3MQX52cSOrLy4iu14=; b=FrjKSkFdhbyZiM9vXszjZg4QOG78p/inaVIUECBqojKlQzwQfCnNJeHKrbXBJKlls9c8ay 91A9A/3qgnSqWUcFH0Pj2cR4ECeo0NcN488I6yLdPrA4mOagIXDmehgf5QvLGDPuletUOb E+6ZWzCzK9BpEYAWtswl6OU2NOd0iaMmqmYgKF6wTWz5Fysmv9uH9srI23kyh2aGen50dz sCEuILDo9Ypik348BsMheCdQ5BXzVKalU8oz6sI7vm2yvhJCmWsgJHo68xw90Aia88yE5s 8QiCMzm8d0n4fLqvHfAQ1LOAz5VJFQXWPXURfJbVp02ZR9odzIRClCActJghAA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=NHaSA3Lw; 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=1709820554; a=rsa-sha256; cv=none; b=P0eXpd//zASMvfxdysLFKYU7hty5O8ffeSg5LIoWNQseAww1KhhYXgQQAyGZX2+nk71yyy PFgtQE2RDo9oWLegojTieo469eJy+2XXhWQaJVZ4ZtUpyEsvBy/C1NfQM1jcG3UkZ2+S9c GfeKU255aPDLSNOB4hv0KTyPj8OsbQON0TSVKu6QJgPI0JhRQWymQGou7tARZHHqqN59uu BzFjBNrWCBSD+o74xEcRNq+qf7sAj9UZ/7aNM1lf6MSUPory8nUMM8OhOqqdkXXQ0RRPsa GcvmocVTzqP4K/c1wpvRYmUMv3mzzk5l8nrw3KVTYQ5uRATngZ94mBqVPDlNLQ== 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 EB70A60425 for ; Thu, 7 Mar 2024 15:09:13 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1riEPy-0003GV-K7; Thu, 07 Mar 2024 09:08:18 -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 1riEPw-0003GG-AL for emacs-orgmode@gnu.org; Thu, 07 Mar 2024 09:08:16 -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 1riEPm-0006xe-RQ for emacs-orgmode@gnu.org; Thu, 07 Mar 2024 09:08:10 -0500 Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 9EDEA24002A for ; Thu, 7 Mar 2024 15:08:02 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1709820482; bh=Wt7BhcF0EKH9MSHrKqmejWUwQN48KTM5YGWA+bzcgqg=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: From; b=NHaSA3Lw8Bq/smFKKFVd1M25nGDr8fQdg85GG5wAZQjLj7rESqhR4uo9vKRGHWcq8 rm0D4vlS9DEdGoWmY9gKqTaDXbY5T0ZQT23INg4wsH/xiZ+pxxEAYrA1HAHwfOjFHj 5RxIEvaXnBSSiyuDVvYfVjhUTfdsInsgurARTyR9Yu4rMz/dbrc0lfnLeBB77obUvl c4HvXHXG3qUwp+YlOBWZWnIFK30hk4ZLpRTB5Qnw8teH8pYIZr5byhdJd3s9rQ1pUa 6jmvxmSxPmlE2u4IfVWQM3oKZQwVBvCAcf/8NhAGZyJ9y+sZQt9rIHqVpFgWWuXajD c8fLYhBEAcl3g== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4TrB356Xy3z9rxM; Thu, 7 Mar 2024 15:08:01 +0100 (CET) From: Ihor Radchenko To: Max Nikulin Cc: emacs-orgmode@gnu.org Subject: Re: naming: Re: Experimental public branch for inline special blocks In-Reply-To: References: <87wmql6690.fsf@posteo.net> <875xy1kisj.fsf@localhost> <87frx339yl.fsf@localhost> Date: Thu, 07 Mar 2024 14:12:07 +0000 Message-ID: <87edcmxhag.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_H3=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: -6.47 X-Spam-Score: -6.47 X-Migadu-Queue-Id: EB70A60425 X-Migadu-Scanner: mx13.migadu.com X-TUID: +g5RQlxEr22N Max Nikulin writes: >> IMHO, the whole point of the discussed construct is exactly being abstract >> and multi-purpose. > > Almost everything in Org syntax may be called "markup", so using this > word for a specific object may lead to confusion unless a couple of > extra words are added to make it clear what kind of markup is referred to. Yup. "inline custom markup". I feel that it's enough. Do I miss something? > I had an idea to name new object "markup macro" since its role is close > to existing macro ("substitution macro"), but I discarded it because > "markup" is too general. I do not find "too general" as a big problem. I am not sure if I like macro. "macro" feels like something replaced literally, without extra processing. But the proposed object has little to do with literal replacement. >>> Decorators sometimes stressed as "inline decorators"? >> >> I dislike "decorators" because it is not a term we use anywhere in Org >> mode. I'd prefer to reuse an existing term, if at all possible. > > I had a hope to find a unique word that will be convenient for usage in > discussions, a term that will be uniformly used in the manual and in the > syntax specification. Manual was one of the reasons I chose "markup". Because this word is used in "Markup for Rich Contents" section of the manual. Further, we refer to "markup" when talking about emphasis/monospace in "12.2 Emphasis and Monospace" section. > If others are happy to name "block" instances that are neither solid nor > shaped as blocks then I see no point to continue this discussion. I am slightly in favor of "markup" vs. "block". > P.S. I am neutral in respect to "span". I do not like this for the same reason as "decorators" - unfamiliar terminology. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at