From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: Correct / best way of loading packages in contrib when using org compiled from git?
Date: Fri, 22 Feb 2013 22:17:34 +0100 [thread overview]
Message-ID: <87ip5knj4h.fsf@Rainer.invalid> (raw)
In-Reply-To: 51277BD1.8080707@gmail.com
Rainer M Krug writes:
> Ok - that makes sense. I just checked in my contrib/lisp and I only have .el there, so none are
> compiled.
Look in lisp, not contrib/lisp.
>> If you set the load-path to include the "contrib/lisp/" directory, then you don't need to
>> install org-notmuch, and (require 'org-notmuch) will find it.
>
> Well - I don't install org, but just specify the load-path, so I have to specify that one as well.
> No problem.
No, you don't want that if you use ORG_ADD_CONTRIB.
> Yes - that is what I am doing as well.
Just curious, what would change for you if you installed Org into a user
directory (besides using "make up2" instead of "make update")?
> Just for clarifications: is there any problem with adding
>
> ORG_ADD_CONTRIB = *
>
> to the local.mk file, apart from slightly longer compilation times?
Yes, you don't want all of contrib (htmlize.el in particular).
>>> PS: I update my git almost daily via the following script:
>>
>> This should be enough
Actually, the "git checkout master" at the beginning should probably
stay there as a defensive measure.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves
next prev parent reply other threads:[~2013-02-22 21:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 11:56 Correct / best way of loading packages in contrib when using org compiled from git? Rainer M Krug
2013-02-22 13:39 ` Bastien
2013-02-22 14:08 ` Rainer M Krug
2013-02-22 14:32 ` Bastien
2013-02-22 15:42 ` Achim Gratz
2013-02-25 10:00 ` Rainer M Krug
2013-02-25 10:19 ` Bastien
2013-02-22 21:17 ` Achim Gratz [this message]
2013-02-25 10:05 ` Rainer M Krug
2013-02-25 17:37 ` Achim Gratz
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=87ip5knj4h.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).