From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: naming: Re: Experimental public branch for inline special blocks
Date: Thu, 7 Mar 2024 17:34:38 +0700 [thread overview]
Message-ID: <usc57v$nfo$1@ciao.gmane.io> (raw)
In-Reply-To: <87frx339yl.fsf@localhost>
On 06/03/2024 17:56, Ihor Radchenko wrote:
> Max Nikulin writes:
>
>>> Custom inline markup.
>>
>> "Markup" is something abstract to my taste. I would prefer something
>> related to concrete instances of such objects.
>
> 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.
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.
>> 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.
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.
P.S. I am neutral in respect to "span".
next prev parent reply other threads:[~2024-03-07 10:35 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 20:34 Experimental public branch for inline special blocks Juan Manuel Macías
2024-03-02 8:29 ` Stefan Nobis
2024-03-02 10:57 ` Juan Manuel Macías
2024-03-03 20:29 ` Juan Manuel Macías
2024-03-10 2:08 ` `:export' attribute?: " Juan Manuel Macías
2024-03-10 13:54 ` Juan Manuel Macías
2024-03-11 10:27 ` Max Nikulin
2024-03-11 13:59 ` Juan Manuel Macías
2024-03-11 17:01 ` Max Nikulin
2024-03-11 20:19 ` Juan Manuel Macías
2024-03-12 8:32 ` Stefan Nobis
2024-03-12 13:45 ` Juan Manuel Macías
2024-03-12 16:20 ` Max Nikulin
2024-03-12 17:41 ` Juan Manuel Macías
2024-03-13 16:08 ` Max Nikulin
2024-03-13 16:48 ` Juan Manuel Macías
2024-03-13 17:16 ` Juan Manuel Macías
2024-03-15 2:19 ` Juan Manuel Macías
2024-03-15 10:52 ` Max Nikulin
2024-03-15 13:10 ` Juan Manuel Macías
2024-03-15 17:21 ` Max Nikulin
2024-03-15 14:00 ` Ihor Radchenko
2024-03-15 11:11 ` Max Nikulin
2024-03-15 14:19 ` Ihor Radchenko
2024-03-15 16:26 ` Juan Manuel Macías
2024-03-16 14:07 ` Max Nikulin
2024-03-18 19:42 ` Juan Manuel Macías
2024-03-19 14:54 ` Max Nikulin
2024-03-19 17:47 ` Juan Manuel Macías
2024-03-21 10:26 ` inline-special-block: export rules (was: `:export' attribute?: Re: Experimental public branch for inline special blocks) Juan Manuel Macías
2024-03-26 16:56 ` inline-special-block: export rules Max Nikulin
2024-03-04 17:13 ` naming: Re: Experimental public branch for inline special blocks Max Nikulin
2024-03-04 17:29 ` Ihor Radchenko
2024-03-04 17:49 ` Juan Manuel Macías
2024-03-05 10:53 ` Max Nikulin
2024-03-05 11:04 ` Ihor Radchenko
2024-03-05 15:16 ` Suhail Singh
2024-03-05 15:23 ` Suhail Singh
2024-03-05 15:16 ` Juan Manuel Macías
2024-03-06 10:42 ` Max Nikulin
2024-03-06 10:56 ` Ihor Radchenko
2024-03-07 10:34 ` Max Nikulin [this message]
2024-03-07 14:12 ` Ihor Radchenko
2024-03-08 5:26 ` Samuel Wales
2024-03-08 16:32 ` Max Nikulin
2024-03-08 16:41 ` Ihor Radchenko
2024-03-04 18:07 ` Juan Manuel Macías
2024-03-04 22:17 ` Samuel Wales
2024-03-04 22:18 ` Samuel Wales
2024-03-05 16:47 ` smallcaps: " Max Nikulin
2024-03-05 17:28 ` Juan Manuel Macías
2024-03-06 10:55 ` Max Nikulin
2024-03-06 15:21 ` Juan Manuel Macías
2024-03-06 16:53 ` To avoid zero width space: " Max Nikulin
2024-03-06 18:27 ` Juan Manuel Macías
2024-03-06 21:13 ` Juan Manuel Macías
2024-03-07 10:57 ` false positives: " Max Nikulin
2024-03-07 11:06 ` Juan Manuel Macías
2024-03-07 11:18 ` Ihor Radchenko
2024-03-07 11:19 ` Juan Manuel Macías
2024-03-07 15:53 ` Juan Manuel Macías
2024-03-07 16:09 ` Ihor Radchenko
2024-03-07 16:57 ` Juan Manuel Macías
2024-03-07 18:21 ` Juan Manuel Macías
2024-03-08 13:58 ` Max Nikulin
2024-03-08 15:44 ` Juan Manuel Macías
2024-03-08 16:04 ` Max Nikulin
2024-03-08 16:15 ` Ihor Radchenko
2024-03-08 18:44 ` Juan Manuel Macías
2024-03-08 18:57 ` Juan Manuel Macías
2024-03-09 11:10 ` Max Nikulin
2024-03-09 11:48 ` Juan Manuel Macías
2024-03-09 15:24 ` Juan Manuel Macías
2024-03-10 7:11 ` Max Nikulin
2024-04-09 8:52 ` Ihor Radchenko
2024-04-09 10:51 ` Max Nikulin
2024-04-09 14:05 ` Ihor Radchenko
2024-04-10 23:00 ` Juan Manuel Macías
2024-04-11 12:26 ` Ihor Radchenko
2024-04-11 13:47 ` Juan Manuel Macías
2024-04-14 15:59 ` Attributes on images (was:: Experimental public branch for inline special blocks) Rick Lupton
2024-04-14 19:26 ` Ihor Radchenko
2024-04-11 11:06 ` Experimental public branch for inline special blocks Max Nikulin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='usc57v$nfo$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).