Re: [BUG] `org-load-noerror-mustsuffix´ is not defined, introduced by 5484a33b

[Eric Schulte <schulte.eric@gmail.com>]

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

Bastien <bzg@altern.org> writes:

> Hi Eric,
>
> Eric Schulte <schulte.eric@gmail.com> writes:
>
>> If this problem is specific to my situation I'm happy to ignore it until
>> I can update my elpa version of Org-mode to a newer one.  Alternately I
>> could just remove my ELPA install of Org-mode, as it was only installed
>> to answer questions on the mailing list, and I don't think side-by-side
>> ELPA and source Org-modes are necessarily something that needs to be
>> supported.
>
> I confirm `org-load-noerror-mustsuffix' is *not* in the ELPA tarball,
> so somehow your initialization (auto)loads recent Org files, and then
> the ELPA load path takes over.
>
> As said in http://orgmode.org/elpa.html:
>
> ,----
> | By default, Emacs loads packages after it loads your Emacs init file.
> | 
> | We recommend intializing packages as early as possible in your Emacs
> | init file so that your Org configuration will be correctly handled:
> | 
> | ;; -*- emacs-lisp -*-
> | (package-initialize)                ;; Initialize & Install Package
> | ;; (setq org-...)                   ;; Your custom settings
> | 
> | The package initialization should happen before you require Org and
> | set any Org options.
> `----
>
> So yes, I'd suggest removing Org ELPA version completely..

This is done I now have no Org packages in my ELPA.  However I *still*
can't use any version of Org-mode post the 5484a33b commit.  For the
simplest possible reproduction instructions, try the following.

1. mv your init.el to a backup locate

2. replace your init.el with the attached (update paths as appropriate)


[-- Attachment #2: init.el --]
[-- Type: application/emacs-lisp, Size: 109 bytes --]

[-- Attachment #3: Type: text/plain, Size: 289 bytes --]


3. start Emacs

For me this minimal setup works with versions of Org-mode prior to
5484a33b, but fails with the current master branch.

As a side note, is it intended that users should have to load
org-compat.el before loading org.el?

Best,

-- 
Eric Schulte
http://cs.unm.edu/~eschulte