From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [RFC] Syntax for macros
Date: Thu, 30 Jan 2014 11:59:08 -0500 [thread overview]
Message-ID: <87y51x8kyr.fsf@alphaville.bos.redhat.com> (raw)
In-Reply-To: 86zjmdfrgl.fsf@somewhere.org
"Sebastien Vauban" <sva-news@mygooglest.com>
writes:
>> There is also backwards compatibility to consider.
>
> How? You know, when many, many, many keywords or options changed
> between Org 7.9 and Org 8.0, there was nothing to support backward
> compatibility: much too complex, I guess.
>
Yes, indeed: OTOH there was widespread recognition that the ad-hoc
nature of certain things and creeping featuritis in org-mode was causing
problems and there was a consensus (at least on the list) that having
the pain concentrated in one (major) release was the way to go. I think
in general org-mode is better because of the changes, but that does not
mean that there have not been problems, as you no doubt have noticed.
That does not mean that we can push changes that break peoples'
workflows (yes, I know: http://xkcd.com/1172/ ) willy nilly. They either
have to come at major releases with plenty of warning, or they have to
be backwards compatible or there has to be widespread consensus that
that is a desirable course of action - and I'd raise the bar very high
on this last case.
Are you advocating that the macro syntax should be changed without
worrying about backwards compatibility? That might work if almost nobody
uses macros currently[fn:1], but my impression is that they are used fairly
widely.
> Add a variable "org-support-old-macro-syntax" seems overkill to me. But,
> yes, I know, that's something that will have to be clearly mentioned in
> the NEWS as something that did change, and as some consequences.
>
No: I'm saying that if this change is implemented, {{{foo}}} should be
deprecated (probably raising a deprecation warning when encountered) and
that both {{foo}} and {{{foo}}} should work identically, at least until
the next major release (we can debate whether that's 8.3 or 8.4 or
9.0). At that point and forever after, the old syntax starts raising
errors instead of warnings.
Footnotes:
[fn:1] E.g. QUOTE was an example of a change that could go through,
precisely because nobody was using it. COMMENT could not go
quietly into oblivion in the same way however: it was used
widely.
--
Nick
next prev parent reply other threads:[~2014-01-30 16:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 8:49 [RFC] Syntax for macros Sebastien Vauban
2014-01-29 9:25 ` Bastien
2014-01-30 10:29 ` Sebastien Vauban
2014-01-30 10:41 ` Bastien
2014-01-30 10:48 ` Sebastien Vauban
2014-01-30 14:08 ` Nick Dokos
2014-01-30 14:56 ` Sebastien Vauban
2014-01-30 16:59 ` Nick Dokos [this message]
2014-01-30 17:22 ` Thorsten Jolitz
2014-01-30 18:03 ` Bastien
2014-01-31 22:13 ` [PATCH] Font-lock: allow hiding of brackets surrounding macros Florian Beck
2014-02-01 0:22 ` Bastien
2014-02-05 10:14 ` Bastien
2014-02-05 13:07 ` Sebastien Vauban
2014-02-05 13:12 ` Bastien
2014-01-30 19:25 ` [RFC] Syntax for macros Florian Beck
2014-01-30 21:11 ` Thomas S. Dye
2014-01-30 18:24 ` Achim Gratz
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=87y51x8kyr.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).