unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Nala Ginrut <nalaginrut@gmail.com>
To: Matt Wette <matt.wette@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: FOSDEM 2019
Date: Wed, 6 Feb 2019 08:56:19 +0800	[thread overview]
Message-ID: <CAPjoZoeO5A5ne-85wgKyjdLWVKbGzc5XV5QkDX8xFcoF=47q1Q@mail.gmail.com> (raw)
In-Reply-To: <037725de-428a-596f-8f39-c987b7553495@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1372 bytes --]

This patche provide #lang tag like Racket does. If so then it's reasonable
and doable. Thanks for that! :-)

Matt Wette <matt.wette@gmail.com> 于 2019年2月6日周三 08:38写道:

>
>
> On 2/5/19 8:58 AM, Ludovic Courtès wrote:
> > Hi,
> >
> > Amirouche Boubekki <amirouche.boubekki@gmail.com> skribis:
> >
> >> What does it mean in practice? What are the tasks that must dealt with?
> > Like I wrote, an immediate task is to write a Racket importer for Guix¹
> > and to actually package things.
> >
> > Next, we could ensure the subset of these packages that use #r6rs can
> > also be used as Guile packages.  However Chris noted that there are few
> > of them; most use #lang racket.
> >
> > Thus, the next idea is to have #lang racket in Guile, which is quite a
> > bit of work but probably doable.  And the converse: #lang guile in
> > Racket.
> >
> > There are probably other things that could be done, or variants on this
> > theme.
> >
> > Is that clearer?
> >
> > Thanks,
> > Ludo’.
> >
> > ¹
> https://gnu.org/software/guix/manual/en/html_node/Invoking-guix-import.html
> >
> >
> I assume that means a  language/racket/spec.scm file.
>
> A patch to 2.2.4 for maping #lang foo" in a file to
> langauge/foo/spec.scm is in
>
> https://github.com/mwette/guile-contrib/blob/master/patch-2.2.4/load.patch
>
>
>
>

[-- Attachment #2: Type: text/html, Size: 2142 bytes --]

  reply	other threads:[~2019-02-06  0:56 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-03 21:34 FOSDEM 2019 Mikael Djurfeldt
2019-02-03 23:13 ` Arne Babenhauserheide
2019-02-04  5:21   ` Nala Ginrut
2019-02-05 21:25   ` Christopher Lemmer Webber
2019-02-06 13:46     ` Alex Sassmannshausen
2019-02-06 15:22       ` Amirouche Boubekki
2019-02-06 15:33         ` Amirouche Boubekki
2019-02-06 15:42         ` Alex Sassmannshausen
2019-02-06 21:03           ` Ricardo Wurmus
2019-02-06 22:09             ` Alex Sassmannshausen
2019-02-26  8:57             ` swedebugia
2019-02-06 20:40         ` Arne Babenhauserheide
2019-02-05 21:26   ` Christopher Lemmer Webber
2019-02-04 13:06 ` Amirouche Boubekki
2019-02-04 14:44 ` Ludovic Courtès
2019-02-04 18:01   ` Jan Nieuwenhuizen
2019-02-05 11:09   ` Amirouche Boubekki
2019-02-05 16:58     ` Ludovic Courtès
2019-02-06  0:31       ` Nala Ginrut
2019-02-06 12:59         ` Ludovic Courtès
2019-02-06 19:09           ` Amirouche Boubekki
2019-02-06  0:37       ` Matt Wette
2019-02-06  0:56         ` Nala Ginrut [this message]
2019-02-06  1:40       ` Amirouche Boubekki
2019-02-05  2:30 ` Matt Wette
  -- strict thread matches above, loose matches on Subject: below --
2018-08-21 13:33 Manolis Ragkousis
2018-08-21 17:57 ` Ricardo Wurmus
2018-08-22 16:27   ` Andy Wingo
2018-08-22  2:33 ` Mike Gran
2018-08-23  0:08 ` Mike Gran
2018-08-24 12:23 ` Christopher Lemmer Webber
2018-08-29 21:08   ` Ludovic Courtès

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='CAPjoZoeO5A5ne-85wgKyjdLWVKbGzc5XV5QkDX8xFcoF=47q1Q@mail.gmail.com' \
    --to=nalaginrut@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=matt.wette@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).