emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kaushal Modi <kaushal.modi@gmail.com>
To: Christopher Miles <numbchild@gmail.com>
Cc: emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: compatible issue between MELPA org and source code org
Date: Tue, 23 Jan 2018 12:26:50 +0000	[thread overview]
Message-ID: <CAFyQvY23xEqNomekGd4uXnGBbEMoxO90pMi=BciacWNMED7muQ@mail.gmail.com> (raw)
In-Reply-To: <CAL1eYuLiWuku_Z4ChCMgn8BK+YhGfcHy7oSruknRpBKejwJXKQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 946 bytes --]

On Mon, Jan 22, 2018, 4:41 AM numbchild@gmail.com <numbchild@gmail.com>
wrote:

>
> Does anybody have a perfect solution to use latest source code Org in
> Emacs way?
>

I've been using a solution that's working perfectly for me. Unfortunately,
the only way is to:

1. Uninstall all the Org installations that you don't want to use (example:
delete the Org Elpa installed version if you plan to use the git cloned
version).
2. Advice a package.el function that never auto-installs Org as dependency.
3. Another advice to never update Org using the package manager (as you
would be managing the updates yourself using git).

Basically the update/dependency-check should not install Org.

A while back, I did a detailed write-up on this setup:
https://scripter.co/building-org-development-version/. With that setup, and
modi/org-version-select set to 'dev, I don't have to worry about other Org
versions getting auto-installed.

> --

Kaushal Modi

[-- Attachment #2: Type: text/html, Size: 1866 bytes --]

  reply	other threads:[~2018-01-23 12:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-22  9:39 compatible issue between MELPA org and source code org numbchild
2018-01-23 12:26 ` Kaushal Modi [this message]
2018-01-23 16:08   ` numbchild
2018-01-23 16:15     ` Kaushal Modi
2018-01-24  0:14       ` numbchild

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='CAFyQvY23xEqNomekGd4uXnGBbEMoxO90pMi=BciacWNMED7muQ@mail.gmail.com' \
    --to=kaushal.modi@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=numbchild@gmail.com \
    /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).