From: John Hendy <jw.hendy@gmail.com>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: mixed orgmode installation
Date: Sun, 8 Sep 2013 09:31:57 -0500 [thread overview]
Message-ID: <CA+M2ft9h3Bhd7offb8LbztGeht4b3Lv=bR9Rhw_Mbx_XWUBixQ@mail.gmail.com> (raw)
In-Reply-To: <8761ugs8as.fsf@Rainer.invalid>
On Wed, Sep 4, 2013 at 2:20 PM, Achim Gratz <Stromeko@nexgo.de> wrote:
> Johannes Rainer writes:
>> is there a "clean" way to disable the built in org from emacs?
>
> Short answer: no.
>
>> I'm loading org mode from git externally, but newer emacs always come
>> with org mode included.
>
> That's not a problem as long as you set up the load-path to point to the
> install made via Git before loading Org. I don't recommend working from
> a Git tree directly because it's just too easy to mess up with the
> autoloads or have stale byte-compiled files somewhere that you forgot
> about.
>
Could you elaborate on this? I'd always thought the exact opposite due
to being burned in the past by stale junk littered around /usr/lib,
/usr/bin, /usr/local/[bin/sbin]. Thus, for some things, I prefer to
run them from the git repository since I know where they'll be vs.
where `make install` might desire to put them.
What happens, for example, in this situation:
- git clone
- make && make install
- some file.el gets moved from org.git/contrib/lisp to org.git/lisp in master
- git pull
- make && make install
Are there now two copies of file.el somewhere in the system?
Anyway, if there's more to read on some of your situations, I'd love
to know as I've been doing exactly that and want to stop if it's
recommended against! Thanks for mentioning the potential risk, as I
had no idea!
Best regards,
John
>> would just deleting the org folder in the emacs (am using Emacs.app on
>> mac) installation help?
>
> No. Leave your Emacs installation alone, unless you fancy compiling
> your own Emacs. Install Org into site-lisp, whereever that is on Mac.
>
>
> Regards,
> Achim.
> --
> +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
>
> SD adaptation for Waldorf microQ V2.22R2:
> http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
>
>
next prev parent reply other threads:[~2013-09-08 14:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 13:52 mixed orgmode installation Johannes Rainer
2013-09-04 14:19 ` Thorsten Jolitz
2013-09-04 14:52 ` Johannes Rainer
2013-09-04 15:07 ` Suvayu Ali
2013-09-08 5:40 ` adam
2013-09-08 14:37 ` John Hendy
2013-09-08 15:10 ` Suvayu Ali
2013-09-08 15:26 ` John Hendy
2013-09-08 16:52 ` Achim Gratz
2014-01-02 8:06 ` Justin Gordon
2014-01-03 8:43 ` Sharon Kimble
2014-01-03 18:08 ` Justin Gordon
2014-01-03 18:49 ` John Hendy
2013-09-04 19:20 ` Achim Gratz
2013-09-08 14:31 ` John Hendy [this message]
2013-09-08 16:41 ` Achim Gratz
2013-09-08 17:52 ` John Hendy
2013-09-08 18:39 ` 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='CA+M2ft9h3Bhd7offb8LbztGeht4b3Lv=bR9Rhw_Mbx_XWUBixQ@mail.gmail.com' \
--to=jw.hendy@gmail.com \
--cc=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).