From: jgart <jgart@dismail.de>
To: Guix Help <help-guix@gnu.org>
Subject: Re: geiser-edit-symbol-at-point
Date: Thu, 10 Nov 2022 19:44:40 -0600 [thread overview]
Message-ID: <20221110194440.GB1732@dismail.de> (raw)
In-Reply-To: <20221110193527.GB571@dismail.de>
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?
next prev parent reply other threads:[~2022-11-11 1:45 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 ` jgart [this message]
2022-11-11 14:31 ` geiser-edit-symbol-at-point Jake Shilling
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=20221110194440.GB1732@dismail.de \
--to=jgart@dismail.de \
--cc=help-guix@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.
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).