From: brian via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: Csepp <raingloom@riseup.net>
Cc: guix-devel@gnu.org
Subject: Re: questionable advice about Geiser load path setting
Date: Sat, 26 Aug 2023 07:27:22 -0400 [thread overview]
Message-ID: <87h6om9h7p.fsf@spork.org> (raw)
In-Reply-To: <86jztijvkd.fsf@riseup.net> (Csepp's message of "Sat, 26 Aug 2023 06:03:19 +0200")
Csepp <raingloom@riseup.net> writes:
> The docs contain this recommended Emacs setting:
>
> @lisp
> ;; @r{Assuming the Guix checkout is in ~/src/guix.}
> (with-eval-after-load 'geiser-guile
> (add-to-list 'geiser-guile-load-path "~/src/guix"))
> @end lisp
>
> I haven't been using it for a while because I remember it causing
> trouble whenever I was working on other Guile projects. I have been
> running Emacs inside ./pre-inst-env instead, which seems to work just as
> well, if not better.
>
> I'd like to make an amendment to the relevant docs, but would welcome
> some info on why it was originally written this way, maybe there are use
> cases I'm missing.
I agree that it's bad advice, since it assumes the only reason to use
Guile is to hack on Guix. I also think it's not necessary, since
‘.dir-locals.el’ in the Guix root should be taking care of this for you
already. I don't use the manual addition to ‘load-path’ you quote above,
and Geiser seems to work fine (within the bounds of Geiser's definition
of “fine”, anyway).
The downside of using dir-locals is that Emacs yells quite loudly about
unsafe variables being set. Another option may be direnv or bufenv? I
haven't tried them myself, but have heard good things.
-bjc
next prev parent reply other threads:[~2023-08-31 18:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-26 4:03 questionable advice about Geiser load path setting Csepp
2023-08-26 11:27 ` brian via Development of GNU Guix and the GNU System distribution. [this message]
2023-08-31 19:10 ` wolf
2023-09-05 1:41 ` Maxim Cournoyer
2023-09-05 16:32 ` wolf
2023-09-06 18:46 ` Maxim Cournoyer
2023-08-27 1:42 ` Maxim Cournoyer
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=87h6om9h7p.fsf@spork.org \
--to=guix-devel@gnu.org \
--cc=bjc@spork.org \
--cc=raingloom@riseup.net \
/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.