Re: [PATCH] doc: Fix 'geiser-guile-load-path' example.

[Alex Kost]

Ludovic Courtès (2015-11-18 00:40 +0300) wrote:

> Alex Kost <address@hidden> skribis:
>
>> OK.  Actually I thought that you use 'with-eval-after-load' or
>> 'eval-after-load' or 'use-package', and you just didn't mention it in
>> the manual because it's a common Emacs thing.  But it looks like you use
>> a straightforward (add-to-list ...), which can work only if
>> "geiser-guile.el" is already loaded.  Out of curiosity, do you somehow
>> load the whole geiser in your emacs config?  If so, why?
>>
>> I mean not just (require 'geiser), as it does not load
>> "geiser-guile.el", but maybe (require 'geiser-mode) or something like
>> it.
>
> I have:
>
>   (require 'geiser-install)
>   (require 'geiser)

You don't need (require 'geiser) as (require 'geiser-install) loads it
anyway (look at "M-x find-library geiser-install").

But after this, 'geiser-guile-load-path' shouldn't be available, as it
is placed in "geiser-guile.el" which is not loaded by "geiser.el".  So
if (featurep 'geiser-guile) gives you `t' right after Emacs start, then
there is something else (I would say “something evil” :-)) in your
config that loads the whole Geiser functionality.

>> (I personally don't touch 'geiser-guile-load-path' at all, I just set
>> GUILE_LOAD_PATH in my ".bash_profile" instead)
>
> I touch ‘geiser-guile-load-path’ because I want it to point to a bunch
> of source trees.
>
> Conversely, I don’t want GUILE_LOAD_PATH to point to source trees, so it
> only points to installation directories.

Ah, I see your point, thanks.

-- 
Alex