unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Stefan Israelsson Tampe <stefan.itampe@gmail.com>
Cc: Guile User <guile-user@gnu.org>, guile-devel <guile-devel@gnu.org>
Subject: Re: Python on guile v1.2.3
Date: Tue, 23 Jun 2020 15:22:58 +0200	[thread overview]
Message-ID: <87d05papcd.fsf@gnu.org> (raw)
In-Reply-To: <CAGua6m2P19zHwWmPdgj1r9dWyQow9Tdz7P8td0NUeN=2D+r54A@mail.gmail.com>

Stefan Israelsson Tampe <stefan.itampe@gmail.com> writes:

> done, all now have tags 1.2.3

Incredible response time, thanks!  :-)

I have not been able to build stis-parser, because slask.scm is missing:

  https://gitlab.com/tampe/stis-parser/-/issues/2

Is it a bug, or am I doing something wrong?

Thanks,
Marius



      reply	other threads:[~2020-06-23 13:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-24 18:11 Python on guile v1.2.3 Stefan Israelsson Tampe
2020-06-23 12:54 ` Marius Bakke
2020-06-23 12:59   ` Stefan Israelsson Tampe
2020-06-23 13:22     ` Marius Bakke [this message]

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=87d05papcd.fsf@gnu.org \
    --to=mbakke@fastmail.com \
    --cc=guile-devel@gnu.org \
    --cc=guile-user@gnu.org \
    --cc=stefan.itampe@gmail.com \
    /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).