file-error

file-error

[Jeff Kowalczyk]

I use el-get org-mode recipe, but I see the same behavior with a typical
org-mode config from init.el.

On org-mode git master start with emacs bzr trunk (emacs 24), org errors on load:

File mode specification error: (file-error "Cannot open load file" "lisp/org")
progn: Cannot open load file: lisp/org

Any idea what file mode specification in this context would be? The unix file
mode is normal:

[master]~/.emacs.d/el-get $ ls -al org-mode/lisp/org.el*
-rw-r--r-- 1 myuser users 774897 May 10 16:45 org-mode/lisp/org.el
-rw-r--r-- 1 myuser users 688684 May 10 16:45 org-mode/lisp/org.elc

Thanks for any suggestions,

Jeff

Re: file-error

[Nick Dokos]

Jeff Kowalczyk <jtk@yahoo.com> wrote:

> I use el-get org-mode recipe, but I see the same behavior with a typical
> org-mode config from init.el.
> 
> On org-mode git master start with emacs bzr trunk (emacs 24), org errors on load:
> 
> File mode specification error: (file-error "Cannot open load file" "lisp/org")
> progn: Cannot open load file: lisp/org
> 
> Any idea what file mode specification in this context would be? The unix file
> mode is normal:
> 
> [master]~/.emacs.d/el-get $ ls -al org-mode/lisp/org.el*
> -rw-r--r-- 1 myuser users 774897 May 10 16:45 org-mode/lisp/org.el
> -rw-r--r-- 1 myuser users 688684 May 10 16:45 org-mode/lisp/org.elc
> 
> Thanks for any suggestions,
> 

We need a backtrace: see section 1.4, "Feedback", in the Orgmode manual.
But clearly, this is not an orgmode error: emacs just cannot find the file
to load (for whatever reason - the backtrace will make clear what the reason
is, but it is probably an incorrect load-path or an incorrect file spec).

Nick

Re: file-error

[Jeff Kowalczyk]

Nick Dokos <nicholas.dokos <at> hp.com> writes:
> We need a backtrace: see section 1.4, "Feedback", in the Orgmode manual.
> But clearly, this is not an orgmode error: emacs just cannot find the file
> to load (for whatever reason - the backtrace will make clear what the reason
> is, but it is probably an incorrect load-path or an incorrect file spec).

After several attempts, I have not been able to get a traceback that shows much
useful information:

M-x toggle-debug-on-error, scratch buffer, (org-reload) C-x C-e

Debugger entered--Lisp error: (file-error "Cannot open load file" "lisp/org")
  (org-reload)
  eval((org-reload) nil)
  eval-last-sexp-1(nil)
  eval-last-sexp(nil)
  call-interactively(eval-last-sexp nil nil)

I have relieved el-get from org-mode duties temporarily to debug, and here's the
current section in ~/.emacs.d/init.el, no extra customizations to Org:

;; org-mode install
(add-to-list 'load-path "~/.emacs.d/el-get/org-mode/lisp")
(add-to-list 'load-path "~/.emacs.d/el-get/org-mode/contrib/lisp")
(add-to-list 'auto-mode-alist '("\\.org\\'" . org-mode))
(require 'org-install)

The file path is valid:

$ ls -al ~/.emacs.d/el-get/org-mode/lisp | head
total 6280
drwxr-xr-x  2 myuser users  12288 May 11 06:45 .
drwxr-xr-x 10 myuser users   4096 May 11 06:45 ..
-rw-r--r--  1 myuser users   6439 May 10 22:27 ob-asymptote.el
-rw-r--r--  1 myuser users   4571 May 11 06:44 ob-asymptote.elc
-rw-r--r--  1 myuser users   3352 May 10 22:27 ob-calc.el
-rw-r--r--  1 myuser users   2367 May 11 06:44 ob-calc.elc
-rw-r--r--  1 myuser users   6749 May 10 22:27 ob-C.el
-rw-r--r--  1 myuser users   5987 May 11 06:44 ob-C.elc
-rw-r--r--  1 myuser users   3022 May 10 22:27 ob-clojure.el

I don't know that this is an Org-mode problem, only that the above isn't working
with emacs bzr trunk (emacs 24) as of the last 5 days or so.

Thanks,
Jeff

Re: file-error

[Jeff Kowalczyk]

Nick Dokos <nicholas.dokos@hp.com> wrote:
> Try
> 
> (add-to-list 'load-path "~/.emacs.d/el-get/org-mode")
> 
> It is failing on "lisp/org" so that might fix it: it would
> be nice to know *who* is looking for "lisp/org" however - 
> is it org-reload?
> 
> Nick

Thanks Nick, your suggestion worked. It makes a lot more sense now. I think this
is a recent change, I didn't have that org-mode root directory in load-path
previously, and org git worked fine.

Thanks again,
Jeff