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 20:07:28 +0200 [thread overview]
Message-ID: <87wr53hehr.fsf@Rainer.invalid> (raw)
In-Reply-To: CANid5Q7bzqNMNHLXpBKE5v2c8juM8yKdxk9WHs2sV_6Fehh7ng@mail.gmail.com
Mike McLean writes:
> So if I do not copy/move/link code from contrib/lisp/ to lisp/ I could
> still be using old contrib code from my Emacs system directories?
There is no contrib code in Emacs unless you yourself installed it
there. The advantage of copying to lisp is that you don't need to add
contrib to the load-path and mostly don't need any further setup beyond
(require 'org-install). Also, the new files in lisp will be compiled
and installed just like anything else in lisp without further
configuration. The latter of course means that you have to do a "make
cleaninstall" if you later decide you don't want to have them installed
anymore.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
next prev parent reply other threads:[~2012-04-25 18:07 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 ` LaTeX-export to ACM SIG Proceedings format Achim Gratz
2012-04-25 17:30 ` Mike McLean
2012-04-25 18:07 ` Achim Gratz [this message]
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=87wr53hehr.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).