From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Org syntax: \[ \] as block element instead of inline object
Date: Sat, 2 Oct 2021 15:17:18 +0700 [thread overview]
Message-ID: <sj94ig$v6s$1@ciao.gmane.io> (raw)
In-Reply-To: <87ilygo4uh.fsf@nicolasgoaziou.fr>
I like Timothy's idea that \[ \] markup should behave like block-level
element rather than inline object. On the other hand, Nicolas convinced
me that the problem is not only with filling paragraphs in Emacs using
M-q and it requires change of Org grammar. That is why I do not think
that suggested patch should be applied.
Although Org has its own syntax, \[ \] constructs are added for LaTeX
snippets, so unless there is a strong reason, such construct should not
be a surprise for users familiar with LaTeX.
As it pointed out by Nicolas, the following is a compatibility issue
with such change.
The following will be invalid Org structure, however the problem is
hidden in the case of exporting to LaTeX:
A \[
1 \ne 2,
\] B
It should be typed as
A
\[ 1 \ne 2, \]
B
or
A
\[
1 \ne 2,
\]
B
On 02/10/2021 03:41, Nicolas Goaziou wrote:
>
>> I wonder, why it is not a block element. As far as I know, the only
>> difference (even in the context of Org) between \(...\) and \[...\]
>> is, that the former denotes inline math and the latter denotes a math
>> block. And at least exporting to HTML (with MathJax) and LaTeX results
>> in a block equation for \[...\].
>
> That's not true. Only some export back-ends can tell the difference
> between \(...\) and \[...\], so in the context of Org, they are the
> same.
Is there a valid use case for that backends, so they should not consider
\[ \] as a block-level element? Otherwise I would tell that it is a bug
in that backend and in Org parser.
>> Do you have a short summary or a pointer why \[...\] has been choosen
>> to be an inline element?
>
> Yes: habit. Also, I don't think LaTeX treats it as a block element.
> E.g.,
>
> text
> \[1+1=3\]
> text
>
> is a single paragraph in LaTeX.
It is a single LaTeX paragraphs assembled in vertical mode from parts
created in horizontal or math mode. Splitting text into lines (in
horizontal mode) is performed for each part of paragraph independently.
So LaTeX paragraph is more like "greater element" than just "element".
There is no of similar concept in HTML + CSS, there are blocks and
inline parts. Formatting like paragraph indents and vertical spacing
between paragraphs may be achieved with CSS rules.
Visually formatted paragraph may contain several block-level elements.
P.S. Examples of HTML vs. LaTeX paragraphs in Org export that were not
intuitive for me:
https://list.orgmode.org/orgmode/sd9h2q$t9a$1@ciao.gmane.io/T/#u
next prev parent reply other threads:[~2021-10-02 8:19 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-30 17:20 [PATCH] Don't fill displayed equations Timothy
2021-09-30 17:44 ` Timothy
2021-09-30 18:51 ` Nicolas Goaziou
2021-09-30 18:54 ` Timothy
2021-09-30 19:02 ` Nicolas Goaziou
2021-09-30 19:17 ` Colin Baxter
2021-09-30 22:11 ` Nicolas Goaziou
2021-09-30 22:26 ` Tim Cross
2021-09-30 19:28 ` Timothy
2021-09-30 20:45 ` Timothy
2021-09-30 22:55 ` Nicolas Goaziou
2021-10-01 7:38 ` Stefan Nobis
2021-10-01 20:41 ` Nicolas Goaziou
2021-10-02 8:17 ` Max Nikulin [this message]
2021-10-02 10:47 ` Org syntax: \[ \] as block element instead of inline object Stefan Nobis
2021-10-02 9:57 ` [PATCH] Don't fill displayed equations Stefan Nobis
2021-10-02 10:04 ` Eric S Fraga
2021-10-02 10:18 ` Timothy
2021-10-02 11:24 ` Eric S Fraga
2021-10-02 14:21 ` Max Nikulin
2021-10-02 17:51 ` Tom Gillespie
2021-10-02 18:28 ` Timothy
2021-10-02 18:57 ` Tom Gillespie
2021-10-02 20:25 ` org-latex-preview and latex export blocks Timothy
2021-10-03 8:50 ` [PATCH] Don't fill displayed equations Max Nikulin
2021-10-03 10:56 ` Stefan Nobis
2021-10-03 12:04 ` Max Nikulin
2021-10-04 5:57 ` Tom Gillespie
2021-10-04 17:11 ` Max Nikulin
2021-10-03 12:35 ` Ihor Radchenko
2021-10-01 7:43 ` Timothy
2021-10-02 11:06 ` Nicolas Goaziou
2021-10-02 11:24 ` Timothy
2021-10-03 8:49 ` Ihor Radchenko
2021-10-03 8:50 ` Timothy
2021-10-03 9:13 ` Ihor Radchenko
2021-10-03 9:14 ` Timothy
2021-10-03 9:41 ` Ihor Radchenko
2021-10-03 9:42 ` Timothy
2022-06-18 6:00 ` Ihor Radchenko
2021-10-01 14:42 ` Greg Minshall
2021-10-04 6:05 ` Timothy
2021-10-04 7:11 ` Tom Gillespie
2021-10-04 7:15 ` Timothy
2021-10-04 8:11 ` Przemysław Pietrzak
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='sj94ig$v6s$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).