unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Adriano Peluso <randomlooser@riseup.net>
To: Olivier Dion <olivier.dion@polymtl.ca>,
	Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>,
	Guile User <guile-user@gnu.org>
Subject: Re: Guile 3.0.7 compile cache messages
Date: Wed, 02 Jun 2021 08:00:02 +0200	[thread overview]
Message-ID: <a1a9157b6ee086f1dd69f762f5fefaa24dba0cc5.camel@riseup.net> (raw)
In-Reply-To: <87im2xzsrk.fsf@clara>

Il giorno mar, 01/06/2021 alle 08.14 -0400, Olivier Dion via General
Guile related discussions ha scritto:
> On Mon, 31 May 2021, Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
> wrote:
> > Hello Guile Users!
> > 
> > It seems my Guile (version 3.0.7, installed via GNU Guile, updated
> > today) is
> > doing something weird, or perhaps something correct but unexpected
> > with regard
> > to informing about it finding compile caches. When I run a program
> > with `guile
> > -L . main.scm`, it displays the following:
> 
> I also find it annoying.  I use Guile as a script language for a
> video game engine in C.  This interferes with the logging system and it
> annoys the hell out of me >:-)

Does this bug help anyone of you ?

https://debbugs.gnu.org/cgi/bugreport.cgi?bug=16364









  reply	other threads:[~2021-06-02  6:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-31 19:46 Guile 3.0.7 compile cache messages Zelphir Kaltstahl
2021-06-01 12:14 ` Olivier Dion via General Guile related discussions
2021-06-02  6:00   ` Adriano Peluso [this message]
2021-06-02  8:52     ` Zelphir Kaltstahl
2021-06-02 10:30       ` Chris Vine
2021-06-02 12:20         ` Zelphir Kaltstahl
2021-06-02 12:38           ` Matt Wette
2021-06-02 16:53           ` Chris Vine
2021-06-02 21:52             ` Zelphir Kaltstahl
2021-06-02 23:09               ` Chris Vine
2021-06-02 20:51           ` Adriano Peluso
2021-06-02 21:45             ` Zelphir Kaltstahl
2021-06-02 22:15               ` Zelphir Kaltstahl

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=a1a9157b6ee086f1dd69f762f5fefaa24dba0cc5.camel@riseup.net \
    --to=randomlooser@riseup.net \
    --cc=guile-user@gnu.org \
    --cc=olivier.dion@polymtl.ca \
    --cc=zelphirkaltstahl@posteo.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).