From mboxrd@z Thu Jan  1 00:00:00 1970
From: Federico Beffa <beffa@ieee.org>
Subject: Re: [POLL] Syntax change: make \[...\] non-inline (+1)
Date: Sun, 3 Aug 2014 18:32:24 +0200
Message-ID: <CAKrPhPM-X8BwPV0219ZL0WGWWzJKNLYSM=whq8xR3pXxjwvZeA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:33698)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <federico.beffa@gmail.com>) id 1XDyhv-0002JD-Vs
	for emacs-orgmode@gnu.org; Sun, 03 Aug 2014 12:32:28 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <federico.beffa@gmail.com>) id 1XDyhu-0002oo-Uj
	for emacs-orgmode@gnu.org; Sun, 03 Aug 2014 12:32:27 -0400
Received: from mail-la0-x22d.google.com ([2a00:1450:4010:c03::22d]:64266)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <federico.beffa@gmail.com>) id 1XDyhu-0002mM-NO
	for emacs-orgmode@gnu.org; Sun, 03 Aug 2014 12:32:26 -0400
Received: by mail-la0-f45.google.com with SMTP id ty20so4609222lab.4
	for <emacs-orgmode@gnu.org>; Sun, 03 Aug 2014 09:32:25 -0700 (PDT)
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: ndokos@gmail.com, emacs-orgmode@gnu.org

>> 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).

Don't get me wrong, I value backward compatibility.

However, here for the end user the change would amount to something like

 if \[ is not at the beginning of a line, then insert \n before \[
 if \] does not end a line, then insert \n after \]

for the whole document (or something similar). This should obviously
be documented in the release notes where an exact procedure to fix the
document can be detailed (possibly two query-replace expressions).

And if somebody updates just before a presentation and without reading
the release notes, then it's his own fault.

Regards,
Federico