emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Federico Beffa <beffa@ieee.org>
To: ndokos@gmail.com, emacs-orgmode@gnu.org
Subject: Re: [POLL] Syntax change: make \[...\] non-inline (+1)
Date: Sun, 3 Aug 2014 18:32:24 +0200	[thread overview]
Message-ID: <CAKrPhPM-X8BwPV0219ZL0WGWWzJKNLYSM=whq8xR3pXxjwvZeA@mail.gmail.com> (raw)

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

next             reply	other threads:[~2014-08-03 16:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-03 16:32 Federico Beffa [this message]
2014-08-03 18:19 ` [POLL] Syntax change: make \[...\] non-inline (+1) Nick Dokos
  -- strict thread matches above, loose matches on Subject: below --
2014-08-03 20:05 Federico Beffa
2014-08-03 20:48 ` Nick Dokos
2014-08-04  8:55 ` Rasmus
2014-08-01  8:22 Federico Beffa
2014-07-30 20:19 Federico Beffa
2014-07-30 16:50 Federico Beffa
2014-07-30 17:17 ` Nick Dokos
2014-07-31  9:03 ` Rasmus
2014-08-02 19:12   ` Nicolas Goaziou

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='CAKrPhPM-X8BwPV0219ZL0WGWWzJKNLYSM=whq8xR3pXxjwvZeA@mail.gmail.com' \
    --to=beffa@ieee.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=ndokos@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

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