Max Nikulin writes:
> Ihor, I see you intention, however I reserve my vote for some new unique
> word, preferably a single one.
That's fine. I do not insist on my preferences about naming. Rather see
it as a minor issue that can be resolved at any moment after we
implement the functionality. Ma
On 08/03/2024 12:26, Samuel Wales wrote:
cannot follow discussion but is the role and scope of the proposed
semantics settled and agreed upon by those who do?
I think, there are enough issues with the proposed feature to discuss.
Notice "naming" added to the message subject with hope to facili
cannot follow discussion but is the role and scope of the proposed
semantics settled and agreed upon by those who do?
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
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-purpo
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.
> Decorators sometimes stressed a
On 05/03/2024 00:29, Ihor Radchenko wrote:
Max Nikulin writes:
Does anybody have an idea of a better name for a feature? Maybe
something like inline custom objects, snippets. "Objects" are used to
describe syntax, but not used in the manual though.
Custom inline markup.
"Markup" is somethin
Suhail Singh writes:
> ... due to the similarity with "inline code blocks" (cf. "code
> blocks") as well as "special blocks".
.. due to the /relation/ with "inline code blocks" (cf. "code blocks")
as well as "special blocks".
> But if it were to, I do hope the names of other similar syntactic
>
Ihor Radchenko writes:
> In my mind, "fragment" implies no nesting.
FWIW, in the mind of this Org mode user as well.
> But the point of the "inline special blocks" is to allow nesting as
> needed.
Yes, exactly! As "inline code blocks" are to "code blocks" so too are
"inline special blocks" to
Max Nikulin writes:
> Special blocks are really block-level elements. I see similarity,
> however with a better term we could avoid "inline" specifier. I think,
> the new beast may serve in some cases currently handled by macros.
> LaTeX snippets are named "fragments" in the manual.
>
> Custom fra
Max Nikulin writes:
> Special blocks are really block-level elements. I see similarity,
> however with a better term we could avoid "inline" specifier. I think,
> the new beast may serve in some cases currently handled by macros. LaTeX
> snippets are named "fragments" in the manual.
>
> Custom
On 05/03/2024 00:49, Juan Manuel Macías wrote:
Ihor Radchenko writes:
Max Nikulin writes:
Does anybody have an idea of a better name for a feature? Maybe
something like inline custom objects, snippets. "Objects" are used to
describe syntax, but not used in the manual though.
Custom inline ma
[i did not aim that at any particular person!]
On 3/4/24, Samuel Wales wrote:
> If language is not correct, then what is said is
> not what is meant; if what is said is not what is meant,
> then what must be done remains undone; if this remains
> undone, morals and art will deteriorate; if justic
If language is not correct, then what is said is
not what is meant; if what is said is not what is meant,
then what must be done remains undone; if this remains
undone, morals and art will deteriorate; if justice goes
astray, the people will stand about in helpless
confusion. Hence there must be no
Max Nikulin writes:
> In Org syntax, "elements" are paragraphs and larger parts, while parts
> within paragraphs are named objects. I admit that for org-element
> everything is element.
In my initial message I used 'element' loosely. Note that
inline-special-block is included in org-element-all-o
Ihor Radchenko writes:
> Max Nikulin writes:
>
>> Does anybody have an idea of a better name for a feature? Maybe
>> something like inline custom objects, snippets. "Objects" are used to
>> describe syntax, but not used in the manual though.
>
> Custom inline markup.
Custom span?
I chose "inl
Max Nikulin writes:
> Does anybody have an idea of a better name for a feature? Maybe
> something like inline custom objects, snippets. "Objects" are used to
> describe syntax, but not used in the manual though.
Custom inline markup.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn
On 02/03/2024 03:34, Juan Manuel Macías wrote:
Finally, I have made public on GitLab my experimental branch for the new
(possible) inline-special-block element:
I find the feature name confusing, however I am unsure if others share
my opinion.
In Org syntax, "elements" are paragraphs and la
18 matches
Mail list logo
