From: tsd@tsdye.com (Thomas S. Dye)
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Bastien <bzg@altern.org>, Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Macro question with new texinfo exporter
Date: Wed, 30 Jan 2013 16:21:48 -1000 [thread overview]
Message-ID: <m1obg6ks77.fsf@poto.westell.com> (raw)
In-Reply-To: <87wquumhqk.fsf@gmail.com> (Nicolas Goaziou's message of "Wed, 30 Jan 2013 23:24:51 +0100")
Nicolas Goaziou <n.goaziou@gmail.com> writes:
> Bastien <bzg@altern.org> writes:
>
>> Nicolas Goaziou <n.goaziou@gmail.com> writes:
>>
>>> Supporting old syntax is a bit tricky. Perhaps something like:
>>>
>>> - Find the first one to appear between comma and quote:
>>> - if it is a comma, use old syntax
>>> - in any other case, use new syntax.
>>
>> Sounds good to me.
>
> OTOH, the change will happen during a major release. Moreover macros
> belong to an export framework which have been totally rewritten. Must we
> cope with backward compatibility in this case ?
Perhaps make macro expansion conditional on old/new exporter, rather
than the form of the macro?
Tom
--
Thomas S. Dye
http://www.tsdye.com
next prev parent reply other threads:[~2013-01-31 2:22 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 20:19 Macro question with new texinfo exporter Thomas S. Dye
2013-01-29 18:21 ` Nicolas Goaziou
2013-01-29 18:49 ` Thomas S. Dye
2013-01-30 9:22 ` Bastien
2013-01-30 12:44 ` Nicolas Goaziou
2013-01-30 16:14 ` Bastien
2013-01-30 22:24 ` Nicolas Goaziou
2013-01-31 2:21 ` Thomas S. Dye [this message]
2013-01-31 13:51 ` Bastien
2013-01-31 13:58 ` Nicolas Goaziou
2013-01-31 21:23 ` Nicolas Goaziou
2013-02-04 15:43 ` Thomas S. Dye
2013-02-04 17:26 ` Bastien
2013-02-04 18:57 ` Achim Gratz
2013-02-16 9:21 ` Bastien
2013-02-16 10:19 ` Achim Gratz
2013-02-16 10:34 ` Bastien
2013-02-16 10:39 ` Achim Gratz
2013-02-16 13:18 ` Eric Abrahamsen
2013-02-16 13:23 ` Reloading uncompiled and testing from several git branches (was: Macro question with new texinfo exporter) Bastien
2013-02-16 14:10 ` Reloading uncompiled and testing from several git branches Achim Gratz
2013-02-16 14:21 ` Bastien
2013-02-16 14:59 ` Eric Abrahamsen
2013-02-17 0:08 ` François Pinard
2013-02-18 12:57 ` Nicolas Richard
2013-02-18 19:17 ` Achim Gratz
2013-02-19 1:17 ` François Pinard
2013-02-16 16:40 ` Macro question with new texinfo exporter Nick Dokos
2013-02-16 16:47 ` Nick Dokos
2013-02-16 16:19 ` Nick Dokos
2013-02-16 17:37 ` Thomas S. Dye
2013-02-04 18:10 ` Nicolas Goaziou
2013-02-04 18:48 ` Thomas S. Dye
2013-02-04 18:38 ` Achim Gratz
2013-02-04 20:21 ` Thomas S. Dye
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=m1obg6ks77.fsf@poto.westell.com \
--to=tsd@tsdye.com \
--cc=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@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
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).