From: Vili Aapro <vili.aapro@iki.fi>
To: guile-devel@gnu.org
Subject: Feature request: make Guile compiler always write absolute paths in .go files for Geiser compatiblity
Date: Fri, 1 Sep 2023 12:33:26 +0300 [thread overview]
Message-ID: <20230901123326.0f0632cb@vilij-LIFEBOOK-E744> (raw)
Dear all,
for Geiser (specifically, `geiser-edit-symbol-at-point') compatibility, we would like the Guile procedure `program-source' always to return absolute paths; for this, we would need compiler co-operation. Specifically, it would be desirable to make Guile compiler always write absolute paths in .go files.
At the moment, this is not the case, and `edit-symbol-at-point' fails for `iota' because `program-source' returns a relative path "ice-9/boot-9.scm".
We discussed this on `geiser-guile'; see https://gitlab.com/emacs-geiser/guile/-/issues/33 .
Thank you,
Vili Aapro
next reply other threads:[~2023-09-01 9:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 9:33 Vili Aapro [this message]
2023-09-25 9:26 ` Feature request: make Guile compiler always write absolute paths in .go files for Geiser compatiblity Maxime Devos
2023-09-25 9:36 ` Vili Aapro
2023-09-25 9:51 ` Maxime Devos
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230901123326.0f0632cb@vilij-LIFEBOOK-E744 \
--to=vili.aapro@iki.fi \
--cc=guile-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.
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).