Max Nikulin <> writes:

> On 08/07/2023 16:31, Ihor Radchenko wrote:
>>>> - it is what we use ourselves in WORG sources.
>> Max Nikulin writes:
>>> I have not found it in the worg repository. There are enough @@html:@@
>>> with a handful of @@latex:@@.
>> Yeah, not in WORG.
> It makes the FAQ entry having no value if your suggestions are taken 
> into account. (I would add a link to annotating that is another sort of 
> comments instead of dropping content further.) So I am giving up and 
> leaving opportunity to propose changes to somebody else.

> Bing rates quickstart reasonably, but Google avoids it and I have no 
> idea why. Some hypotheses:
> - quickstart uses generic metadata for the whole site, not specific for 
> this page
> - <h1> repeating <title> has display:none property
> - invalid markup in index.html (a pitfall with affiliated keywords 
> breaking paragraphs) for the link to quickstart:
> <p>
> <a href="quickstart.html">
> </p>
> <figure id="org490449d">
> <img src="resources/img/quickstart.svg" alt="Running stickfigure" 
> class="org-svg" title="Start using Org. You'll never stop.">
> </figure>
> <p>
> </a>
> I am unsure, but I would expect something like
> <a href="quickstart.html" title="Getting started with Org-mode"
>     ><img src="resources/img/quickstart.svg" alt="Quickstart"
>           class="org-svg"></a>

I have no idea here. I wish somebody more familiar with search engine
optimization chimed in.

>>> +#+begin_src org
>>> +The following line may become a patagraph separator.
>>> +@@comment: might give unexpected effect @@
>>> +Put some text before @@comment: a better variant
>>> +@@ and after instread.
>>> +#+end_src
>> May you please elaborate?
>> If you see inline export block starting a paragraph, it is a bug.
> I failed to convince you that it is a general issue, not a LaTeX 
> specific one.
> Ihor Radchenko to emacs-orgmode… Re: [BUG] No space after footnote with 
> org-export-with-footnotes set to nil [9.6.1 ( @ 
> /Users/test/.emacs.d/elpa/28.0/develop/org-9.6.1/)] Tue, 14 Mar 2023 
> 12:19:11 +0000.
> try to export to MarkDown. Even for LaTeX the fix is in the development 
> branch only. There are enough users of built-in Org that deserve to be 
> warned.

The linked message was talking about macros. I still think that for
macros specifically it was not a bug - macros may be expanded into
multiple paragraphs, which is perfectly fine. We should not force macro
expansion to ensure a single paragraph.

As for comments, I tend to agree that it is indeed a bug.

Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <>.
Support Org development at <>,
or support my work at <>

Reply via email to