Re: [O] compatible issue between MELPA org and source code org

After check your source code, I finally and with your theory: > Org doesn't load automatically.. it autoloads only if you open an Org file or call an org-loading function. After emacs -Q, if you do M-: (featurep 'org), you will get nil. So the user does get a change to set the load path as they

Re: [O] compatible issue between MELPA org and source code org

On Tue, Jan 23, 2018 at 11:09 AM numbch...@gmail.com wrote: > Thanks for your advice. After your code inspiration. I got an idea. After > test, it works fine. I try to load `use-package` and `(use-package org :pin > manaul ..)` ahead of `(package-initialize)`. Half of the

Re: [O] compatible issue between MELPA org and source code org

Thanks for your advice. After your code inspiration. I got an idea. After test, it works fine. I try to load `use-package` and `(use-package org :pin manaul ..)` ahead of `(package-initialize)`. Half of the problem is solved. The another half of the problem is that Emacs still will load built-in

Re: [O] compatible issue between MELPA org and source code org

On Mon, Jan 22, 2018, 4:41 AM numbch...@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

[O] compatible issue between MELPA org and source code org

Because some MELPA package requires `org`. So Emacs will **force** install `org` package from MELPA. But it is delay with source code Org. I use source code org with use-package like this: ``` (use-package org :load-path "~/Code/Emacs/org-mode/lisp/" :pin manual ;; :mode (("\\.org$" .