From: Federico Beffa <beffa@ieee.org>
To: emacs-orgmode@gnu.org, Nicolas Goaziou <mail@nicolasgoaziou.fr>
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: Mon, 28 Jul 2014 13:16:05 +0200 [thread overview]
Message-ID: <CAKrPhPOXbU-cxQmts2XSe-QaSPS4gkzcWTLyYdtjTHA4XfiGkQ@mail.gmail.com> (raw)
In-Reply-To: <87tx6221id.fsf@nicolasgoaziou.fr>
In principle, to avoid breaking existing documents, you could
introduce a variable to set org-mode in legacy mode.
Regards,
Fede
On Sun, Jul 27, 2014 at 6:46 PM, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> Hello,
>
> Federico Beffa <beffa@ieee.org> writes:
>
>> In the end of the day the reason why I started looking into this is
>> the fact that I do not find user friendly that org-mode, when filling
>> a paragraph, interprets \[...\] as any inline snippet and does not
>> keep it on a separate line (as recommended by the LaTeX manual, see
>> attached document). That's it.
>
> As explained previously, I'm not against the idea, but it would break
> existing documents containing "\[...\]" in the middle of a line, even
> though it is valid LaTeX. In any case, you will not get total LaTeX
> conformance.
>
> Anyway, I can't see any technical limitation to your suggestion. So we
> might as well ask the ML. I'll write a consultative poll about it.
>
>
> Regards,
>
> --
> Nicolas Goaziou
next prev parent reply other threads:[~2014-07-28 11:16 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
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 [this message]
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=CAKrPhPOXbU-cxQmts2XSe-QaSPS4gkzcWTLyYdtjTHA4XfiGkQ@mail.gmail.com \
--to=beffa@ieee.org \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).