From: Nick Dokos <nicholas.dokos@hp.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: Achim Gratz <Stromeko@nexgo.de>, emacs-orgmode@gnu.org
Subject: Re: [BUG] `org-load-noerror-mustsuffix´ is not defined, introduced by 5484a33b
Date: Thu, 10 Jan 2013 17:55:11 -0500 [thread overview]
Message-ID: <4908.1357858511@alphaville.americas.hpqcorp.net> (raw)
In-Reply-To: Message from Eric Schulte <schulte.eric@gmail.com> of "Thu\, 10 Jan 2013 15\:30\:20 MST." <87y5g0llhf.fsf@gmail.com>
Eric Schulte <schulte.eric@gmail.com> wrote:
> alright, starting with emacs -Q, evaluate the following in your scratch
> buffer.
>
> (load-file "~/.emacs.d/src/org-mode/lisp/org.el")
>
> it may complain (void-function org-define-obsolete-function-alias), in
> which case evaluate the following in your scratch buffer
>
> (load-file "~/.emacs.d/src/org-mode/lisp/org-compat.el")
> (load-file "~/.emacs.d/src/org-mode/lisp/org.el")
>
> The above works prior to the offending commit, but now it throws an
> error.
>
I doubt that it works in either case: it may not throw an error but you
still have a mixed install where most of the org stuff will come from
the org that's distributed with emacs.
> Can you reproduce this?
>
I don't know what error you get: I get a recursive load
insert-file-contents: Recursive load: "/usr/local/share/emacs/24.3.50/lisp/jka-compr.el.gz",\
"/usr/local/share/emacs/24.3.50/lisp/jka-compr.el.gz",\
"/usr/local/share/emacs/24.3.50/lisp/jka-compr.el.gz",\
"/usr/local/share/emacs/24.3.50/lisp/jka-compr.el.gz",\
"/usr/local/share/emacs/24.3.50/lisp/jka-compr.el.gz",\
"/usr/local/share/emacs/24.3.50/lisp/emacs-lisp/debug.el.gz",\
"/home/nick/src/emacs/org/org-mode/lisp/org.el"
No idea why.
But as I said before, you can not expect this to work.
Nick
next prev parent reply other threads:[~2013-01-10 23:34 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 16:08 [BUG] `org-load-noerror-mustsuffix´ is not defined, introduced by 5484a33b Eric Schulte
2013-01-10 16:29 ` Bastien
2013-01-10 16:38 ` Eric Schulte
2013-01-10 17:09 ` Bastien
2013-01-10 17:29 ` Eric Schulte
2013-01-10 17:44 ` Nick Dokos
2013-01-10 18:13 ` Eric Schulte
2013-01-10 18:44 ` Bastien
2013-01-10 19:28 ` Eric Schulte
2013-01-10 20:05 ` Bastien
2013-01-10 21:12 ` Eric Schulte
2013-01-10 22:24 ` Eric Schulte
2013-01-10 22:45 ` Nick Dokos
2013-01-10 23:05 ` Bastien
2013-01-10 23:44 ` Eric Schulte
2013-01-11 7:04 ` Bastien
2013-01-11 12:28 ` Bastien
2013-01-11 15:41 ` Eric Schulte
2013-01-11 16:31 ` Bastien
2013-01-11 16:50 ` Achim Gratz
2013-01-11 16:40 ` Achim Gratz
2013-01-11 16:58 ` Bastien
2013-01-11 17:04 ` Achim Gratz
2013-01-11 17:23 ` Bastien
2013-01-11 19:30 ` Achim Gratz
2013-01-11 20:19 ` Eric Schulte
2013-01-11 20:48 ` Achim Gratz
2013-01-12 6:57 ` Bastien
2013-01-12 6:56 ` Bastien
2013-01-12 7:44 ` Achim Gratz
2013-01-12 8:40 ` Bastien
2013-01-12 10:27 ` Achim Gratz
2013-01-12 11:03 ` Achim Gratz
2013-01-12 13:35 ` Bastien
2013-01-12 15:49 ` Achim Gratz
2013-01-12 16:06 ` Bastien
2013-01-12 16:17 ` Achim Gratz
2013-01-12 16:12 ` Bastien
2013-01-12 16:24 ` Achim Gratz
2013-01-11 9:12 ` Achim Gratz
2013-01-10 23:27 ` Stelian Iancu
2013-01-10 23:27 ` Stelian Iancu
2013-01-10 20:09 ` Achim Gratz
2013-01-10 22:30 ` Eric Schulte
2013-01-10 22:55 ` Nick Dokos [this message]
2013-01-11 8:58 ` Achim Gratz
2013-01-10 19:37 ` Nick Dokos
2013-01-10 19:47 ` Achim Gratz
2013-01-13 22:08 ` Thorsten Jolitz
2013-01-13 23:06 ` Stelian Iancu
2013-01-13 23:22 ` Thorsten Jolitz
2013-01-14 21:44 ` Eric Schulte
2013-01-15 1:29 ` Thorsten Jolitz
2013-01-15 6:07 ` Eric Schulte
2013-01-15 11:31 ` Thorsten Jolitz
2013-01-15 12:22 ` Nick Dokos
2013-01-15 13:36 ` Thorsten Jolitz
2013-01-15 13:49 ` Nick Dokos
2013-01-15 18:58 ` Achim Gratz
2013-01-15 20:17 ` Thorsten Jolitz
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=4908.1357858511@alphaville.americas.hpqcorp.net \
--to=nicholas.dokos@hp.com \
--cc=Stromeko@nexgo.de \
--cc=emacs-orgmode@gnu.org \
--cc=schulte.eric@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).