StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>When a library contains multiple files one can assume that a single main file will load the others as necessary; but if the directory isn't in the <code>load-path</code> then it won't be able to load them (or at least not those versions), so <code>load-file</code> on its own isn't going to do the trick.</p> <p>I don't make much use of package.el myself, but I'd really have thought that it would manage the load-path such that it took precedence over anything in <code>site-lisp</code> (which is presumably where the debian package is installing things.)</p> <p>Try running <code>emacs --no-site-lisp</code> and check that the correct version of the library is loaded. If you don't want anything from the site libraries, then that might even be your solution.</p> <p>If that works, then check the <code>load-path</code> variable after starting Emacs normally. Unless an absolute path is given, Emacs will look at those directories in sequence, and use the first one which matches. I am guessing that for some reason your site-lisp directory is appearing before the one created by package.el.</p> <p>Or perhaps the package didn't install correctly at all.</p> <p>That all said, in Emacs 24.3 at least <code>(package-initialize)</code> is called automatically and I don't think you should need to manually load anything. Check the <code>package-load-list</code> variable.</p> <p><strong>Edit:</strong></p> <p>On that last note, refer to <a href="https://stackoverflow.com/questions/17512884/cannot-open-load-dired-details/17513285#17513285">cannot open load dired-details</a>.</p> <p>At the time I hadn't noticed that Emacs doesn't initialize packages until <em>after</em> the user init file has loaded, so you generally <em>will</em> need to initialize them manually in your init file.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload