From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [POLL] Syntax change: make \[...\] non-inline (+1)
Date: Sun, 03 Aug 2014 14:19:31 -0400 [thread overview]
Message-ID: <8761i977ws.fsf@gmail.com> (raw)
In-Reply-To: CAKrPhPM-X8BwPV0219ZL0WGWWzJKNLYSM=whq8xR3pXxjwvZeA@mail.gmail.com
Federico Beffa <beffa@ieee.org> writes:
>>> 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.
>
It's a bit more complicated than that: one upgrades org at some
opportune moment, then three months/years/centuries later, tries to use
that presentation that worked perfectly before - boom. If you go back
and check all your old presentations each time you upgrade org, you are,
I would guess, the exception, not the rule. I certainly don't do that
Just to be clear: on the whole issue you bring up, I'm more or less
neutral (slightly negative to be sure, mostly because I'm not convinced
that it's a serious problem, but I could live with it either way).
I generally put displays in separate paragraphs, I rarely use
autofill[fn:1] and I'm happy to do M-q on individual paragraphs instead,
but if I happen to do it on the wrong paragraph (backtraces, code
fragments, displayed equations), undo is easy enough.
Footnotes:
[fn:1] I use it in gnus message composition modes by default, and I
often swear at it and turn it off because it does things that I don't
want it to do - mostly mangles backtraces and code fragments; I probably
should turn it off completely.
--
Nick
next prev parent reply other threads:[~2014-08-03 18:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-03 16:32 [POLL] Syntax change: make \[...\] non-inline (+1) Federico Beffa
2014-08-03 18:19 ` Nick Dokos [this message]
-- 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=8761i977ws.fsf@gmail.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).