On 28/01/2022 20:13, Juan Manuel Macías wrote:
Max Nikulin writes:

I have an idea how to implement *intra*/word/ markup with minimal
change of Org syntax. At first I had a hope that it is enough to
introduce \relax entity that expands to empty string, but it does not
work for second part of words: *intra*\relax{}/word/ is exported to
     <b>intra</b>/word/.
So it is necessary to support consuming spaces after such entity
similar to TeX commands:
     *intra*\relax /word/
In Org "a\_      b" already behaves in the same way.

Maxim, I find the idea of \relax entity interesting. The only (minor)
drawback I find (in normal use, I mean) is the verbosity it adds.

"Relax" is just a name known to TeX users. Certainly another shorter word may be used instead. I am just lazy enough to look through HTML named entities and LaTeX command to avoid conflicts and thus behavior unexpected to some users.

In my case, I have already given up on the problem of marks inside words
:-(. My personal opinion: I think that, unless a completely
'revolutionary' solution emerges, it is better to leave the matter as it
is, and consider this a feature of Org rather than a bug. I suspect that
a single solution could not satisfy all tastes or all possible
scenarios, so maybe it would be nice to put a list of solutions
(including this one and also the zero space thing, and others that have
arisen or may arise) somewhere (perhaps in the manual?).

A day before I posted my current summary why export snippets and macros do not help with intra-word markup (before I expected that they can), only custom links is a workaround (with some limitations, as usual):

[RFC] Creole-style / Support for **emphasis**__within__**a word**
Tue, 25 Jan 2022 23:27:50 +0700.
https://list.orgmode.org/ssp8e7$ah2$1...@ciao.gmane.io/

But at that moment I forgot about entities, Another topic served as a reminder, and I spent some time experimenting with them.


Reply via email to