unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Jake Shilling <shilling.jake@gmail.com>
To: jgart <jgart@dismail.de>, Guix Help <help-guix@gnu.org>
Subject: Re: geiser-edit-symbol-at-point
Date: Fri, 11 Nov 2022 09:31:40 -0500	[thread overview]
Message-ID: <87sfipd0kz.fsf@gmail.com> (raw)
In-Reply-To: <20221110194440.GB1732@dismail.de>

[-- Attachment #1: Type: text/plain, Size: 1941 bytes --]


I don't really have anything helpful to add, except that I believe
geiser doesn't work the way SLIME or LSP does, where there's some
process parsing a project with semantic awareness. Instead it just
launches guile (or some other repl) and parses the prompt string. As far
as I know it is really just sending text back and forth between a
scheme-mode buffer and a runing repl.

The load path has to be set for each project because the guile repl
isn't aware of any project structure that a particular file is a part
of. It is simply going to parse whatever text it's sent within the
context of whatever %load-path it was initialized with. That %load-path
can either be set with the GUILE_LOAD_PATH env variable or by
geiser-guile-load-path which affects how geiser launches guile.

The way I handle this is by making sure that
${HOME}/.config/guix/current/share/guile/site/3.0 is in my
GUILE_LOAD_PATH so that whatever channels I've pulled in the current
profile are included in any guile repl I start. This gets around needing
to have the guix source cloned down somewhere else. When I'm working on
my configuration files, I have a toplevel script which updates the
%load-path:

```
(when (current-filename)
  (add-to-load-path
   (dirname (current-filename))))
```

So when I load that file into the repl with C-c C-l all the subsequent
use-modules work.

On 2022-11-10 19:44, jgart wrote:

> On Thu, 10 Nov 2022 19:35:27 -0600 jgart <jgart@dismail.de> wrote:
>
>> (with-eval-after-load 'geiser-guile
>>   (add-to-list 'geiser-guile-load-path "~/guix"))
>
> Also, why does geiser want you to set up the load path manually for every project?
>
> I'd like for the experience to be more like a language server/eglot where I
> just enter the guile project and xref just works if the mode is turned on.
>
> Why is this not possible with geiser currently?
>
>

-- 
Best regards,
Jake Shilling

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2022-11-11 15:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11  1:35 geiser-edit-symbol-at-point jgart
2022-11-11  1:39 ` geiser-edit-symbol-at-point jgart
2022-11-11  1:44 ` geiser-edit-symbol-at-point jgart
2022-11-11 14:31   ` Jake Shilling [this message]
2022-11-11 16:17     ` geiser-edit-symbol-at-point Olivier Dion via
2022-11-11 16:47       ` geiser-edit-symbol-at-point Jake Shilling
2022-11-11 17:10         ` geiser-edit-symbol-at-point Olivier Dion via
2022-11-11 18:40     ` geiser-edit-symbol-at-point jgart
2022-11-11 20:43       ` geiser-edit-symbol-at-point Jake Shilling
2022-11-11 21:42         ` geiser-edit-symbol-at-point jgart
2022-11-11 21:45           ` geiser-edit-symbol-at-point jgart
2022-11-11 22:06           ` geiser-edit-symbol-at-point Jake Shilling
2022-11-11 22:15             ` geiser-edit-symbol-at-point jgart
2022-11-12  0:07               ` geiser-edit-symbol-at-point jgart
2022-11-12  0:12                 ` geiser-edit-symbol-at-point jgart
2022-11-12 15:48                   ` geiser-edit-symbol-at-point Jake Shilling
2022-11-14 15:01                     ` geiser-edit-symbol-at-point jgart
2022-11-14 15:16                       ` geiser-edit-symbol-at-point Jake Shilling
2022-11-14 22:38                         ` geiser-edit-symbol-at-point jgart
2022-11-15  1:31                           ` geiser-edit-symbol-at-point Jake Shilling

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=87sfipd0kz.fsf@gmail.com \
    --to=shilling.jake@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=jgart@dismail.de \
    /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.
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).