From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
Subject: Re: [RFC] Syntax for macros
Date: Thu, 30 Jan 2014 15:56:58 +0100
Message-ID: <86zjmdfrgl.fsf@somewhere.org>
References: <86ha8n6ulq.fsf@somewhere.org> <87y51zta1a.fsf@bzg.ath.cx>
	<867g9hiwzy.fsf@somewhere.org> <87sis592gg.fsf@bzg.ath.cx>
	<8638k5iw3i.fsf@somewhere.org> <8738k57ebi.fsf@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org>
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-mXXj517/zsQ@public.gmane.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode-mXXj517/zsQ@public.gmane.org>
List-Help: <mailto:emacs-orgmode-request-mXXj517/zsQ@public.gmane.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request-mXXj517/zsQ@public.gmane.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org

Hello Nick,

Nick Dokos wrote:
> "Sebastien Vauban" writes:
>> Bastien wrote:
>>> "Sebastien Vauban" writes:
>>>> Bastien wrote:
>>>>
>>>>> Reducing to {{...}} could be better, but I'm not sure this is
>>>>> what will make your friends happy :)
>>>>
>>>> Not entirely, no!  But I think that'd be already a good
>>>> simplification.
>>>
>>> Added to my "will-silently-see-if-this-makes-progress" list :)
>>
>> Isn't it just changing those occurrences?
>>
>> ./org-element.el:3177: (looking-at
>> "{{{\\([a-zA-Z][-a-zA-Z0-9_]*\\)\\(([ \t\n]*\\([^\000]*?\\))\\)?}}}")
>> ./org-element.el:3217:
>> "{{{\\([a-zA-Z][-a-zA-Z0-9_]*\\)\\(([ \t\n]*\\([^\000]*?\\))\\)?}}}"
>> ./org-macro.el:35:;; {{{time(format-string)}}}, {{{property(node-property)}}},
>> ./org-macro.el:36:;; {{{input-file}}} and {{{modification-time(format-string)}}}.
>> ./org-macro.el:38:;; Upon exporting, "ox.el" will also provide {{{author}}}, {{{date}}},
>> ./org-macro.el:39:;; {{{email}}} and {{{title}}} macros.
>> ./org-macro.el:165:      (while (re-search-forward "{{{[-A-Za-z0-9_]" nil t)
>> ./org.el:6263:	   '("{{{.+?}}}" (0 'org-macro t))
>> ./ox.el:3092:	 ;; Expand export-specific set of macros: {{{author}}},
>> ./ox.el:3093:	 ;; {{{date}}}, {{{email}}} and {{{title}}}.  It must be done
>
> 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.

As a reminder, some of the changes:

  #+STYLE: ...                             ->  #+HTML_HEAD: ...
  #+BEAMER_HEADER_EXTRA: \usetheme{Madrid} ->  #+BEAMER_THEME: Madrid
  #+ATTR_LaTeX: width=1.1cm                ->  #+ATTR_LaTeX: :width 1.1cm
  #+ATTR_LaTeX: align=lrrrr                ->  #+ATTR_LaTeX: :align lrrrr

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.

Best regards,
  Seb

-- 
Sebastien Vauban