all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] doc: Fix 'geiser-guile-load-path' example.
Date: Tue, 17 Nov 2015 22:40:32 +0100	[thread overview]
Message-ID: <87a8qcs3sf.fsf@gnu.org> (raw)
In-Reply-To: <874mgksfqi.fsf@gmail.com> (Alex Kost's message of "Tue, 17 Nov 2015 20:22:29 +0300")

Alex Kost <alezost@gmail.com> 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)

> (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.

Ludo’.

  reply	other threads:[~2015-11-17 21:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-14 18:56 [PATCH] doc: Fix 'geiser-guile-load-path' example Alex Kost
2015-11-15 17:41 ` Ludovic Courtès
2015-11-17  8:04   ` Alex Kost
2015-11-17 16:16     ` Ludovic Courtès
2015-11-17 17:22       ` Alex Kost
2015-11-17 21:40         ` Ludovic Courtès [this message]
2015-11-18 17:26           ` Alex Kost
2015-11-18 21:36             ` Ludovic Courtès

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a8qcs3sf.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=alezost@gmail.com \
    --cc=guix-devel@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.