unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Catonano <catonano@gmail.com>
To: Alex Sassmannshausen <alex.sassmannshausen@gmail.com>
Cc: "Guile User" <guile-user@gnu.org>, "Ludovic Courtès" <ludo@gnu.org>
Subject: Re: [ANN] Guile Hall 0.3.0 released
Date: Fri, 22 May 2020 07:16:36 +0200	[thread overview]
Message-ID: <CAJ98PDzNYa_HgGTNTNp4UnNNAtX2HU7Q9ndu2q_NAA7nHLzujw@mail.gmail.com> (raw)
In-Reply-To: <bb95d6480c72c1ace9fb1cd01419b81a7aeab73d.camel@gmail.com>

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

Il giorno gio 21 mag 2020 alle ore 12:03 Alex Sassmannshausen <
alex.sassmannshausen@gmail.com> ha scritto:

> Heya,
>
> On Thu, 2020-05-21 at 12:00 +0200, Catonano wrote:
> >
> >
> > Il giorno mer 20 mag 2020 alle ore 17:58 Catonano <catonano@gmail.com
> > > ha scritto:
> > >
> > > Ok this is the last revision for today
> > > Now I'm gonna do something else, really ! 😀
> > >
> >
> >
> > So, today is another day and I have a new update
> >
> > I'm watching this talk
> >
> https://peertube.social/videos/watch/8f27a614-aa63-4811-af6a-b9e11effc399
> >
> > and it made up my mind that in this patch I'm intermingling reference
> > type content and tutorial type content
> >
> > Guile desperately lacks some good tutorial and how to materials
> >
> > Because, as the person on the video says, programmers tend to assume
> > that what people want is information
> >
> > But the solution is not to spray the reference manual with bit of
> > tutorials here and there
> >
> > Because, according to the person talking, that decreases the quality
> > of both reference and tutorials
> >
> > Today I'm a bit busy but I'll submit a proper patch maybe tomorrow
>
> I think these are very good points.  I think that's where the
> difference between the Guix Manual and the Cookbook come from.
>
> The Guile manual is definitely a reference manual! :-)
>
> I'll await your update tomorrow.
>
> Alex
>
>
here we go

[-- Attachment #2: 0001-added-a-reference-to-guile-hall-in-the-manual.patch --]
[-- Type: text/x-patch, Size: 1498 bytes --]

From b79615f3058225ff086ceef5b3dd6537958b3fcd Mon Sep 17 00:00:00 2001
From: Adriano <catonano@gmail.com>
Date: Mon, 18 May 2020 17:44:15 +0200
Subject: [PATCH] added a reference to guile-hall in the manual

---
 doc/ref/scheme-using.texi | 21 ++++++++++++++++++++-
 1 file changed, 20 insertions(+), 1 deletion(-)

diff --git a/doc/ref/scheme-using.texi b/doc/ref/scheme-using.texi
index ac265fcca..a43ab0364 100644
--- a/doc/ref/scheme-using.texi
+++ b/doc/ref/scheme-using.texi
@@ -282,7 +282,7 @@ Run the optimizer on a piece of code and print the result.
 @deffn {REPL Command} disassemble exp
 Disassemble a compiled procedure.
 @end deffn
-
+  
 @deffn {REPL Command} disassemble-file file
 Disassemble a file.
 @end deffn
@@ -744,6 +744,25 @@ using a CPAN-like system.
 A complete list of guild scripts can be had by invoking @code{guild
 list}, or simply @code{guild}.
 
+@menu
+* guile-hall::
+@end menu
+
+
+@node guile-hall
+@subsection Bootstrapping projects and distributing them
+
+There's a tool that doesn't come bundled with Guile
+and yet it can be very useful in the common experience of using Guile.
+
+It's @uref{https://gitlab.com/a-sassmannshausen/guile-hall, guile-hall}
+
+When you start a new project guile-hall creates a folder
+containing a scaffold of your new project.
+
+In such scaffold the Autotools setup will be already instrumented,
+you don't need to take care of it yourself.
+
 
 @node Installing Site Packages
 @section Installing Site Packages
-- 
2.25.1


  reply	other threads:[~2020-05-22  5:16 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-16 15:41 [ANN] Guile Hall 0.3.0 released Alex Sassmannshausen
2020-05-16 16:14 ` Jack Hill
2020-05-16 16:22 ` Catonano
2020-05-16 20:57   ` Alex Sassmannshausen
2020-05-17  5:13     ` Catonano
2020-05-17 15:35       ` Alex Sassmannshausen
2020-05-17 17:37         ` Catonano
2020-05-17 18:31           ` Arne Babenhauserheide
2020-05-17 20:55             ` Alex Sassmannshausen
2020-05-18  5:43               ` Arne Babenhauserheide
2020-05-17 20:48           ` Alex Sassmannshausen
2020-05-18 16:19             ` Catonano
2020-05-20 11:45               ` Catonano
2020-05-20 11:46                 ` Alex Sassmannshausen
2020-05-20 15:58                   ` Catonano
2020-05-21 10:00                     ` Catonano
2020-05-21 10:03                       ` Alex Sassmannshausen
2020-05-22  5:16                         ` Catonano [this message]
2020-05-24 21:22                           ` Alex Sassmannshausen
2020-05-25  6:31                             ` Catonano
2020-05-25  7:13                               ` Alex Sassmannshausen
2020-05-25  7:51                                 ` Catonano
2020-05-26 14:37                                   ` Catonano
2020-05-27 20:52                             ` Ludovic Courtès
2020-05-28  5:01                               ` Catonano
2020-05-28 12:32                                 ` Ludovic Courtès
2020-05-28 12:35                                   ` Catonano
2020-05-28 15:54                                     ` Ludovic Courtès
2020-05-28 17:26                                       ` Catonano
2020-05-29  8:27                                         ` Ludovic Courtès
2020-05-29  9:09                                           ` Catonano
2020-05-29 10:52                                             ` Alex Sassmannshausen
2020-05-17 16:36       ` Christopher Lemmer Webber
2020-05-17 20:40         ` Alex Sassmannshausen
2020-05-17 20:21 ` Jérémy Korwin-Zmijowski
2020-05-18 15:43 ` Nala Ginrut

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=CAJ98PDzNYa_HgGTNTNp4UnNNAtX2HU7Q9ndu2q_NAA7nHLzujw@mail.gmail.com \
    --to=catonano@gmail.com \
    --cc=alex.sassmannshausen@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).