unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Vili Aapro <vili.aapro@iki.fi>
To: Maxime Devos <maximedevos@telenet.be>
Cc: guile-devel@gnu.org
Subject: Re: Feature request: make Guile compiler always write absolute paths in .go files for Geiser compatiblity
Date: Mon, 25 Sep 2023 12:36:04 +0300	[thread overview]
Message-ID: <20230925123604.57571c02@vilij-ESPRIMO-Q510> (raw)
In-Reply-To: <43058127-5a40-309b-1d82-649e8eb394a2@telenet.be>

On Mon, 25 Sep 2023 11:26:31 +0200
Maxime Devos <maximedevos@telenet.be> wrote:

> Sounds like a very bad idea.  The absolute file name would be somewhere 
> in the build directory, which very likely doesn't exist anymore on a 
> typical installation.

Yes, you are right.

> I suppose that whatever code 
> is responsible for loading .go/.scm can be adjusted to add a prefix 
> turning it in an absolute file name.

Yes, this must be the way. The loader should do the job.

>  > One wrong way to find out the absolute path would be to go through
>  > %load-path, but the semantics of that would break under mutation.
> Can you elaborate?

I was just thinking of a dirty fix on the Emacs side of things, to search for the module through %load-path, that that would break when %load-path was mutated.



  reply	other threads:[~2023-09-25  9:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-01  9:33 Feature request: make Guile compiler always write absolute paths in .go files for Geiser compatiblity Vili Aapro
2023-09-25  9:26 ` Maxime Devos
2023-09-25  9:36   ` Vili Aapro [this message]
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=20230925123604.57571c02@vilij-ESPRIMO-Q510 \
    --to=vili.aapro@iki.fi \
    --cc=guile-devel@gnu.org \
    --cc=maximedevos@telenet.be \
    /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).