From: Tom Gillespie <tgbugs@gmail.com>
To: Max Nikulin <manikulin@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: [PATCH] Don't fill displayed equations
Date: Sat, 2 Oct 2021 10:51:34 -0700 [thread overview]
Message-ID: <CA+G3_PNcuHY-z9Ui0O2QFGH_Z+4H+eMr3D+3fMSLc2XHZ-Cn0Q@mail.gmail.com> (raw)
In-Reply-To: <sj9psl$17vu$1@ciao.gmane.io>
> do not see a reason for idiosyncrasy that markup intended to add LaTeX
> snippet that looks like exactly as LaTeX commands for this purpose and
> even actually preserved during export to LaTeX should have different
> semantics for Org parser.
The answer is that \[ \] can only occur inside paragraphs. The issues
here are exactly the same as the issues for inline footnotes. Org gives
us a bit more power, but not the full power because Org is Org, not
Latex. Making \[ \] available outside of a paragraph would be a massive
breaking change.
In Timothy's original example he is narrowly skirting the syntax to
allow that all to remain a single paragraph, but stick in a newline
anywhere and boom, no more paragraph, no more equation.
I guess one thing I'm missing/not understanding is when/why people
want to use \[ \] instead of full #+begin_export latex block?
Best,
Tom
next prev parent reply other threads:[~2021-10-02 17:52 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 ` Org syntax: \[ \] as block element instead of inline object Max Nikulin
2021-10-02 10:47 ` 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 [this message]
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=CA+G3_PNcuHY-z9Ui0O2QFGH_Z+4H+eMr3D+3fMSLc2XHZ-Cn0Q@mail.gmail.com \
--to=tgbugs@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@gmail.com \
/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).