From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [POLL] Syntax change: make \[...\] non-inline (+1)
Date: Wed, 30 Jul 2014 13:17:20 -0400 [thread overview]
Message-ID: <87oaw6ix5r.fsf@alphaville.bos.redhat.com> (raw)
In-Reply-To: CAKrPhPPnO_SGuBuvL7ZoDprHRmHm5HVX+H=29DERU1pTH2BJXw@mail.gmail.com
Federico Beffa <beffa@ieee.org> writes:
> Who is entitled to vote? If I am then here is my vote in favor for the
> following reasons:
>
> 1. the construct \[...\] has been defined in LaTeX for equations which
> must stand out and therefore belong on separate lines. It would
> therefore make sense to conform to the borrowed syntax.
>
I don't quite understand why you are so gung-ho for this but the
following works fine:
--8<---------------cut here---------------start------------->8---
\documentclass{article}
\begin{document}
This is a displayed \[ x = 3 \] equation.
\end{document}
--8<---------------cut here---------------end--------------->8---
So what exactly is the problem?
> 5. Existing documents are very easy to fix.
>
Backwards compatibility is important. It has been broken
before, for very good reasons, and even though it was done very
carefully, it still caused many problems (still does).
So I don't buy the "very easy to fix" part: it will bite somebody
two minutes before he/she has to make a presentation (or even during the
presentation - DAMHIKT).
Nick
next prev parent reply other threads:[~2014-07-30 17:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 16:50 [POLL] Syntax change: make \[...\] non-inline (+1) Federico Beffa
2014-07-30 17:17 ` Nick Dokos [this message]
2014-07-31 9:03 ` Rasmus
2014-08-02 19:12 ` Nicolas Goaziou
-- strict thread matches above, loose matches on Subject: below --
2014-07-30 20:19 Federico Beffa
2014-08-01 8:22 Federico Beffa
2014-08-03 16:32 Federico Beffa
2014-08-03 18:19 ` Nick Dokos
2014-08-03 20:05 Federico Beffa
2014-08-03 20:48 ` Nick Dokos
2014-08-04 8:55 ` Rasmus
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=87oaw6ix5r.fsf@alphaville.bos.redhat.com \
--to=ndokos@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).