From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: LaTeX-export to ACM SIG Proceedings format
Date: Wed, 25 Apr 2012 18:16:18 +0200 [thread overview]
Message-ID: <87ehrbiy7h.fsf@Rainer.invalid> (raw)
In-Reply-To: m1haw8wvhh.fsf@tsdye.com
Thomas S. Dye writes:
> On a practical note, using the new exporter is easy. I have these
> two lines (along with other configuration) in an Org-babel code block
> that I use to setup Org-mode:
>
> (require 'org-export)
> (require 'org-e-latex)
Here's my chance to upsell the new build system to you: to use code from
contrib, just link or copy it into lisp, then do whatever you let make
normally do. You usually don't need any extra requires since the
autoload cookies do their magic. If it turns out you don't want or need
that code from contrib, simply remove the files from lisp and re-make.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2012-04-25 16:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 20:08 LaTeX-export to ACM SIG Proceedings format Karl Voit
2012-04-24 21:26 ` Thomas S. Dye
2012-04-24 22:14 ` Karl Voit
2012-04-24 22:29 ` Jambunathan K
2012-04-24 23:39 ` Thomas S. Dye
2012-04-25 9:06 ` Exporting to ACM format using new LaTeX exporter (was: LaTeX-export to ACM SIG Proceedings format) Karl Voit
2012-04-25 16:19 ` Exporting to ACM format using new LaTeX exporter Thomas S. Dye
2012-04-25 21:16 ` Karl Voit
2012-04-25 21:54 ` Nicolas Goaziou
2012-04-26 8:26 ` Karl Voit
2012-04-26 0:33 ` Thomas S. Dye
2012-04-26 8:33 ` Karl Voit
2012-04-25 16:16 ` Achim Gratz [this message]
2012-04-25 17:30 ` LaTeX-export to ACM SIG Proceedings format Mike McLean
2012-04-25 18:07 ` Achim Gratz
2012-04-25 18:59 ` Mike McLean
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=87ehrbiy7h.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).