From: Rainer M Krug <Rainer@krugs.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Can I share ~/.emacs.d/elpa with two machines?
Date: Mon, 05 Oct 2015 13:34:15 +0200 [thread overview]
Message-ID: <m2io6leeh4.fsf@krugs.de> (raw)
In-Reply-To: <20151005101938.GU15858@chitra.no-ip.org> (Suvayu Ali's message of "Mon, 5 Oct 2015 12:19:38 +0200")
[-- Attachment #1: Type: text/plain, Size: 1264 bytes --]
Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
> On Mon, Oct 05, 2015 at 09:54:24AM +0200, Rainer M Krug wrote:
>>
>> Thanks - makes perfect sense. My only question is the contrib
>> directory. I assume I simply also have to copy the files in the same
>> version specific lisp dir?
>
> Add something like this to local.mk (if non-existent, create one)
>
> ORG_ADD_CONTRIB = org-notmuch ox-groff ox-koma-letter
Thanks - haven't looked at that file yet. So than the specified files
would be compiled and put in the contrib directory or copied in the lisp directory?
>
> Also, I would recommend running uncompiled rather than deal with
> versions.
Makes sense.
>
> $ make autoloads
>
Ok - so the sequence :
make clean
make autoloads
make doc
make info
would build all needed files incl documentation?
At the moment I was using
make update
Would compiling have any advantages over un-compiled, besides of speed?
But as org-mode does not do any exorbitant calculations, I would assume
that the only workflows where the speed issue comes in is tangling and
publishing and org-lint?
Thanks,
Rainer
> and that's it.
>
> Cheers,
--
Rainer M. Krug
email: Rainer<at>krugs<dot>de
PGP: 0x0F52F982
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 454 bytes --]
next prev parent reply other threads:[~2015-10-05 11:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 14:03 Can I share ~/.emacs.d/elpa with two machines? Jorge
2015-10-02 15:54 ` Stefan Monnier
2015-10-02 17:05 ` Kaushal Modi
2015-10-02 19:05 ` Rainer M Krug
2015-10-02 19:23 ` Kaushal Modi
2015-10-05 7:54 ` Rainer M Krug
2015-10-05 10:19 ` Suvayu Ali
2015-10-05 11:34 ` Rainer M Krug [this message]
2015-10-05 13:13 ` Suvayu Ali
2015-10-05 13:45 ` Rainer M Krug
2015-10-05 12:55 ` Kaushal Modi
2015-10-05 12:46 ` Kaushal Modi
2015-10-05 13:16 ` Suvayu Ali
2015-10-05 13:56 ` Kaushal Modi
2015-10-05 15:21 ` Solved: " Rainer M Krug
2015-10-03 20:04 ` Phillip Lord
2015-10-02 19:35 ` Stefan Monnier
2015-10-02 15:59 ` Kaushal Modi
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2io6leeh4.fsf@krugs.de \
--to=rainer@krugs.de \
--cc=help-gnu-emacs@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.
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).