On 8/24/12, Bastien wrote:
>> Well, if the org-e-* stuff gets renamed to oe-* instead it becomes a
>> non-issue plus it would allow to keep the old exporter around for a
>> while in either contrib/ or obsolete/… otherwise I'm not too enamored
>> with the double dashes.
>
> Yes, that's exactly the
Bastien writes:
> Hi Achim,
>
> Achim Gratz writes:
>
>> Luis Anaya writes:
>> Well, if the org-e-* stuff gets renamed to oe-* instead it becomes a
>
> Yes, that's exactly the plan.
That makes sense then and keeps it consistent with babel (ob-*).
Luis
--
Luis R. Anaya
papo anaya aroba hot
Hi Achim,
Achim Gratz writes:
> Luis Anaya writes:
>> I have no problems. We can rename org-e-groff.el to org-groff-mm.el and
>> consequently, org-groff-man.el ? If I get hold around the MOM macros, I
>> can then name them org-groff-mom.el
>
> Well, if the org-e-* stuff gets renamed to oe-* ins
Luis Anaya writes:
> I have no problems. We can rename org-e-groff.el to org-groff-mm.el and
> consequently, org-groff-man.el ? If I get hold around the MOM macros, I
> can then name them org-groff-mom.el
Well, if the org-e-* stuff gets renamed to oe-* instead it becomes a
non-issue plus it would
Achim Gratz writes:
> I just realised that there's a trainwreck in the making:
Choo choo! :)
> We have org-e-man and org-man in contrib. Now when the exporter moves
> into core, org-e-man supposedly changes its name to org-man as
> well... not good. Since org-man was there first, could org-e-m
I just realised that there's a trainwreck in the making:
We have org-e-man and org-man in contrib. Now when the exporter moves
into core, org-e-man supposedly changes its name to org-man as
well... not good. Since org-man was there first, could org-e-man be
renamed to something that will not co
