From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Federico Beffa <beffa@ieee.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: wrong interpretation of LaTeX [8.2.6 (8.2.6-47-ge3d2c1-elpa @ c:/Users/beffa/.emacs.d/elpa/org-20140526/)]
Date: Sat, 26 Jul 2014 10:26:48 +0200 [thread overview]
Message-ID: <87vbqkikzb.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAKrPhPOh1tkCtG49s2A3LgHauXVddE7f4+uDbBaZpiy=2zcnrQ@mail.gmail.com> (Federico Beffa's message of "Fri, 25 Jul 2014 22:39:29 +0200")
Federico Beffa <beffa@ieee.org> writes:
> Of course \[ 1+1 \] is valid LaTeX syntax, just as inline
> \begin{displaymath} 1+1 \end{displaymath} is valid.
But \begin{displaymath} 1+1 \end{displaymath} isn't valid in an Org
paragraph.
> In my opinion a construct which will be displayed on a line by itself
> and with some space separating it from the preceding and the following
> text lines such as "\[ ... \]" would be better represented as a
> latex-environment and not an inline latex-fragment. In this way the
> org-mode text representation with proper fill-paragraph handling would
> be much more readable and consistent with the meaning of the syntax
> that it borrowed.
That would prevent \[...\] to be recognized within a paragraph, as in
the example above. I don't think it's worth removing it as long as there
is a latex-environment alternative for it.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2014-07-26 8:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 13:04 Bug: wrong interpretation of LaTeX [8.2.6 (8.2.6-47-ge3d2c1-elpa @ c:/Users/beffa/.emacs.d/elpa/org-20140526/)] Federico Beffa
2014-07-25 18:32 ` Nicolas Goaziou
2014-07-25 20:39 ` Federico Beffa
2014-07-26 8:26 ` Nicolas Goaziou [this message]
2014-07-26 9:20 ` Federico Beffa
2014-07-27 9:27 ` Federico Beffa
2014-07-27 16:46 ` Nicolas Goaziou
2014-07-28 11:16 ` Federico Beffa
2014-07-28 12:03 ` Nicolas Goaziou
2014-07-27 11:36 ` Bastien
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=87vbqkikzb.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=beffa@ieee.org \
--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).