From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [PATCH v2] org-faq.org: Inline comments
Date: Mon, 10 Jul 2023 23:09:55 +0700 [thread overview]
Message-ID: <u8hagl$569$1@ciao.gmane.io> (raw)
In-Reply-To: <87ilauagvy.fsf@localhost>
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.
> https://orgmode.org/quickstart.html#text-comments
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.
The section in quickstart was added in
64922ca 2020-10-04 14:28:00 -0400 Tom Gillespie: quickstart add sections
for comments and macros at the end
I am surprises that quickstart is more detailed than the manual. However
I have no idea how to have this section in both documents with proper
balance in respect to details. Literal copy may be distracting for
readers familiar with quickstart.
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>
>> +#+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. https://list.orgmode.org/87fsa7o79c.fsf@localhost
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.
next prev parent reply other threads:[~2023-07-10 16:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 0:04 Inline comments ypuntot
2023-06-22 1:50 ` Max Nikulin
2023-06-28 15:51 ` [PATCH] org-faq.org: " Max Nikulin
2023-06-29 10:47 ` Ihor Radchenko
2023-06-30 10:34 ` Max Nikulin
2023-07-01 10:48 ` Ihor Radchenko
2023-08-06 18:34 ` Bastien Guerry
2023-07-01 15:24 ` Ihor Radchenko
2023-07-02 5:46 ` Org FAQ design (Re: [PATCH] org-faq.org: Inline comments) Max Nikulin
2023-07-08 5:48 ` [PATCH v2] org-faq.org: Inline comments Max Nikulin
2023-07-08 9:31 ` Ihor Radchenko
2023-07-10 16:09 ` Max Nikulin [this message]
2023-09-01 11:28 ` Ihor Radchenko
2024-04-15 12:17 ` Ihor Radchenko
2024-04-17 14:44 ` Max Nikulin
2024-04-20 11:14 ` Trailing whitespace after export snippets without a transcoder (was: [PATCH v2] org-faq.org: Inline comments) Ihor Radchenko
2024-04-20 15:02 ` Trailing whitespace after export snippets without a transcoder Max Nikulin
2024-04-21 13:00 ` Ihor Radchenko
2024-04-22 10:45 ` Max Nikulin
2024-04-22 19:01 ` Ihor Radchenko
2024-04-25 10:54 ` Max Nikulin
2024-04-28 11:19 ` Ihor Radchenko
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='u8hagl$569$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).