From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
Subject: Re: missing autoloads / (void-variable org-version)
Date: Thu, 26 Apr 2012 21:30:56 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
Achim Gratz wrote:
> Sebastien Vauban writes:
>> Here, I would have thought that invoking the function `text-aux' would open
>> the "production" Lisp file (that is, the one in Emacs code base) as you use
>> Emacs loaddefs.el associations, no?
> It could be set up that way, but isn't. You wouldn't be able to move an
> installed emacs tree if that were the case, and it could quite likely
> break in other mysterious ways.
I think you did not understand what I meant, or the opposite. Whatever, this
presentation is not the most important thing. What you're trying to achieve
*is*. First things first...
To come back to what I understood from your text:
1. you have `test.el' in, let's say,
2. the autoload definition for the function `test-aux' is in
3. you have latest Test package (dev version) in, let's say,
`c:/home/sva/src/test-mode', with 2 files in there:
4. you add `c:/home/sva/src/test-mode' *in front of* your `load-path' list
5. you, then, require `test.el' in your Emacs startup file; it loads the dev
version (that is, `c:/home/sva/src/test-mode/test.el')
6. you, then, invoke the command `test-aux'. As the autoload says that, for
getting the definition of that function, you need to load the file
`test-aux.el', Emacs searches for that file, and finds the first occurrence
in version `c:/home/sva/src/test-mode/test-aux.el'
Here, due to a too quick reflexion, I thought that Emacs would load the base
version in `c:/Program Files/Emacs-24.0/lisp/test-mode/test-aux.el'. But
that's _not_ true, as:
- only file names are given in `loaddefs.el', not full paths
- the dev version directory has been placed first in `load-path'.
So, I was wrong about my comment... Sorry for the noise.
However, a problem that has bitten me twice already is that, in the above
case, I would have this in my Emacs startup file:
(require 'xyz-package) ;; this one requires `test.el' but you don't see/know it
(add-to-list 'load-path "c:/home/sva/src/test-mode") ;; before use of Test package
(require 'test) ;; no-op in this case
You end up in mixed versions of the different functions. Typically the case
where Org version looks like:
Org-mode version 7.7 (release_7.8.09-400-g4a0e5b)
But, when having a look at the value of `load-path', everything seems correct:
you dev version is in front of your Emacs core version.
You think that everything related to the Test package would have been loaded
correctly. Not the case, "obviously"...
Are we on the same wavelength?
>> I've experienced enough couple of hours lost in the past, searching for
>> problems due to mixed versions loaded, to know what the correct answer is.
> ...so, I count that as a "yes, fix it please"?
Yep! I consider important that you fix things which you consider as flaws or
next prev parent reply other threads:[~2012-04-26 19:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 5:52 missing autoloads / (void-variable org-version) Achim Gratz
2012-04-26 10:23 ` Sebastien Vauban
2012-04-26 16:06 ` Achim Gratz
2012-04-26 19:30 ` Sebastien Vauban [this message]
2012-04-26 22:03 ` Bastien
2012-04-26 22:04 ` Bastien
2012-04-26 11:55 ` Detlef Steuer
2012-04-26 12:01 ` Martyn Jago
2012-04-26 16:14 ` Achim Gratz
2012-04-26 13:15 ` Bastien
2012-04-26 19:03 ` Achim Gratz
2012-04-26 21:54 ` Bastien
2012-04-29 9:53 ` Michael Sperber
2012-04-29 18:57 ` Achim Gratz
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).