From: wolf <wolf@wolfsden.cz>
To: brian <bjc@spork.org>
Cc: Csepp <raingloom@riseup.net>, guix-devel@gnu.org
Subject: Re: questionable advice about Geiser load path setting
Date: Thu, 31 Aug 2023 21:10:58 +0200 [thread overview]
Message-ID: <ZPDlwj5oWeVdw8Rq@ws> (raw)
In-Reply-To: <87h6om9h7p.fsf@spork.org>
[-- Attachment #1: Type: text/plain, Size: 2126 bytes --]
On 2023-08-26 07:27:22 -0400, brian via Development of GNU Guix and the GNU System distribution. wrote:
> 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).
Geiser seems to add the project root (I assume based on the git) into the load
path automatically. geiser-repl-current-project-function seems to be set by
default, and rest is described in the docs: (geiser)Customization and tips, Init
files and load paths.
Maybe it once was necessary to set this, I am not sure it still is the case.
I also use (setq geiser-repl-per-project-p t) and everything seems to just work
out of the box.
>
> The downside of using dir-locals is that Emacs yells quite loudly about unsafe
> variables being set.
In emacs 29 it should be possible to whitelist it, so it will stop being so
annoying.
> Another option may be direnv or bufenv? I haven't tried them myself, but have
> heard good things.
>
> -bjc
>
W.
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-09-01 9:23 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.
2023-08-31 19:10 ` wolf [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZPDlwj5oWeVdw8Rq@ws \
--to=wolf@wolfsden.cz \
--cc=bjc@spork.org \
--cc=guix-devel@gnu.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).