emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Rainer M Krug <r.m.krug@gmail.com>
To: Suvayu Ali <fatkasuvayu+linux@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: old to new converter transition
Date: Fri, 08 Feb 2013 08:54:38 +0100	[thread overview]
Message-ID: <5114AF3E.9000106@gmail.com> (raw)
In-Reply-To: <20130207150448.GC7028@kuru.dyndns-at-home.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/02/13 16:04, Suvayu Ali wrote:
> On Thu, Feb 07, 2013 at 03:26:10PM +0100, Rainer M Krug wrote:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>> 
>> Hi
>> 
>> Some remarks and questions about transition to new exporter:
>> 
>> 1) org-export-latex-listings -becomes-> org-latex-listings
>> 
> 
> Since Nicolas answered your specific question, I thought I should share some of my notes about
> moving to the new exporter.  I assembled this by reading Nicolas' announcement, grepping
> through the source, and some light testing after the switch.
> 
> 1. Export engine renamed: org-export → ox 2. Backend requires renamed: org-e-* → ox-* 3. All
> backend specific variables and functions renamed: - org-export-* → org-* (e.g.
> org-html-xml-declaration, ..) - org-e-* → org-* (e.g. org-latex-classes, org-ascii-bullets,
> ..) 4. Generic export variables retain the name org-export-* (e.g.
> org-export-dispatch-use-expert-ui, org-export-filter-headline-functions, ..) 5.
> org-latex-to-pdf-process has been renamed to org-latex-pdf-process 7. Guess, export snippets
> and backend symbols renamed: - e-<backend> → <backend>
> 
> Hope this help others going through the switch.

I am sure.

Would it be possible to collect this info on a "quick and dirty" worg page? At the moment, the
info is in several different threads?

Could be a temporarily useful.

Thanks,

Rainer


> 
> :)
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJRFK8+AAoJENvXNx4PUvmCX78H/3Pfq/H5QbxiuIuIIGCankKy
bFnYJaoQxBOOZO/LYv0EPKyrFGfgp6E7OxkuluQkR03WK1C59BtgmRMCzAsZY5u+
bbgW3zNgAgspPiZj6IoyYoTm6zRA0FPXrnM76voxDA8Dtf/LshWMnvrDvSh5Wm6l
1tJxmNHU7sOUGqNSpNwC5BZAhhPLH4jzoU/kpSUGomZa9Xj028dT+ejK8FoQvtsD
I0PsDltL//GRWAxak0MHsnb/F5YV6GXJD/Tlgs3YZtsVLgk0agva+91xkdew8G7U
GILEprBqKpFYG0Ga4F7HkuLVymOmTda1lHd+g3hCVJkCO3XDAlZv6IudBjU0Q+E=
=Z+Ls
-----END PGP SIGNATURE-----

next prev parent reply	other threads:[~2013-02-08  7:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-07 14:26 old to new converter transition Rainer M Krug
2013-02-07 14:29 ` Nicolas Goaziou
2013-02-07 14:31   ` Rainer M Krug
2013-02-07 15:04 ` Suvayu Ali
2013-02-08  7:54   ` Rainer M Krug [this message]
2013-02-08 12:07     ` Thorsten Jolitz
2013-02-08 16:25     ` Bastien
2013-02-08 16:51       ` Suvayu Ali
2013-02-08 18:33         ` Bastien

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=5114AF3E.9000106@gmail.com \
    --to=r.m.krug@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=fatkasuvayu+linux@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

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).