From: 2QdxY4RzWzUUiLuE@potatochowder.com
To: guile-user@gnu.org
Subject: Re: display path of directory of a file and bug?
Date: Sun, 6 Sep 2020 10:12:37 -0500 [thread overview]
Message-ID: <20200906151237.GC1494@scrozzle> (raw)
In-Reply-To: <a8e6a845-bf1f-6ac8-bbbc-7a06790800db@posteo.de>
On 2020-09-06 at 16:03:17 +0200,
Zelphir Kaltstahl <zelphirkaltstahl@posteo.de> wrote:
> If I move a file using `mv`, a recomplation seems to be not
> required. If I copy the file instead, Guile recompiled it. Does this
> have something to do with inodes or creation date, which is
> differently handled when using `cp` instead of `mv`?
That was my first thought. Renaming a file (using mv) doesn't change
the timestamp, and it's likely that guile tries to use a cached version
but some of the pieces don't fit right. Someone with more knowledge of
guile and its caching will have to provide more details.
Possible solutions? (1) Clean your cache. Mine is somewhere under
$HOME/.cache/guile/ccache. (2) Use GUILE_AUTO_COMPILE=fresh to force
guile to ignore the cache and recompile the source file. (3) Don't do
that. ;-)
HTH,
Dan
next prev parent reply other threads:[~2020-09-06 15:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-06 14:03 display path of directory of a file and bug? Zelphir Kaltstahl
2020-09-06 15:12 ` 2QdxY4RzWzUUiLuE [this message]
2020-09-08 10:32 ` Catonano
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=20200906151237.GC1494@scrozzle \
--to=2qdxy4rzwzuuilue@potatochowder.com \
--cc=guile-user@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).