From: Alex Sassmannshausen <alex.sassmannshausen@gmail.com>
To: Catonano <catonano@gmail.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>, "Guile User" <guile-user@gnu.org>
Subject: Re: [ANN] Guile Hall Release (v0.1.1)
Date: Tue, 19 Feb 2019 19:05:11 +0000 [thread overview]
Message-ID: <87wolvwqe0.fsf@gmail.com> (raw)
In-Reply-To: <CAJ98PDzN42crrrA_56wQc9J_NcTLCDbJsmYpErhX3OZ7MaF2Jw@mail.gmail.com>
Hi Cato,
Catonano writes:
> Il giorno dom 1 lug 2018 alle ore 22:36 Ludovic Courtès <ludo@gnu.org> ha
> scritto:
>
>> Hello Alex,
>>
>> Alex Sassmannshausen <alex.sassmannshausen@gmail.com> skribis:
>>
>> > Otherwise you can get the code from
>> > https://gitlab.com/a-sassmannshausen/guile-hall/, and build (hopefully)
>> > using the traditional
>> > $ autoreconf -vif && ./configure && make
>> > dance.
>> >
>> > What is Guile Hall?
>> >
>> > From the README:
>> >
>> > Hall is a command-line application and a set of Guile libraries that
>> > allow you to quickly create and publish Guile projects. It allows you
>> > to transparently support the GNU build system, manage a project
>> > hierarchy & provides tight coupling to Guix.
>>
>> This looks really great! There’s this longstanding issue with
>> distributing Guile code, and this seems to be a good approach.
>>
>> In particular, that it’s not a Guix-only solution, while at the same
>> time offering Guix support is really a wise choice.
>>
>> I think we should advertise it widely, it’ll be immensely helpful to
>> newcomers. When the manual is more complete ;-), we could refer to it
>> from guile.texi, too.
>>
>
>
> That'd be great
>
> I have a hard time in trying to fill the manual though
>
> The blank page block !
>
> It doesn't help that I don't fully understand the README file
>
> I could use some help
>
> Alex, Maybe you could edit a skeleton of how you see the manual with
> paragraph titles titles only ?
You're quite right to point this out — I should get at least a draft
manual together now.
I will see if I can get this done this week.
Best wishes,
Alex
>
> That would allow me to try to fill it, to some extent.
next prev parent reply other threads:[~2019-02-19 19:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-01 12:07 [ANN] Guile Hall Release (v0.1.1) Alex Sassmannshausen
2018-07-01 20:35 ` Ludovic Courtès
2018-07-02 9:47 ` Alex Sassmannshausen
2018-07-02 15:09 ` Ludovic Courtès
2018-07-03 7:03 ` alex sassmannshausen
2018-07-03 7:27 ` Aw: " Arne Babenhauserheide
2018-07-03 8:07 ` alex sassmannshausen
2018-07-03 19:59 ` Arne Babenhauserheide
2019-02-19 7:26 ` Catonano
2019-02-19 19:05 ` Alex Sassmannshausen [this message]
2019-02-19 19:44 ` Jérémy Korwin-Zmijowski
2019-02-24 16:10 ` Alex Sassmannshausen
2018-07-01 22:51 ` Amirouche Boubekki
2018-07-02 9:39 ` Alex Sassmannshausen
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=87wolvwqe0.fsf@gmail.com \
--to=alex.sassmannshausen@gmail.com \
--cc=catonano@gmail.com \
--cc=guile-user@gnu.org \
--cc=ludo@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).