unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Alex Sassmannshausen <alex.sassmannshausen@gmail.com>
To: Catonano <catonano@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: Sun, 17 May 2020 22:48:30 +0200	[thread overview]
Message-ID: <87y2pqcmox.fsf@gmail.com> (raw)
In-Reply-To: <CAJ98PDy6xwLyMX=x6YaqfDJOYP11PtkNf1dWqcrfeF15DeWXGA@mail.gmail.com>

Heya,

Catonano <catonano@gmail.com> writes:

> Il giorno dom 17 mag 2020 alle ore 17:35 Alex Sassmannshausen <alex.sassmannshausen@gmail.com> ha scritto:
>
>  Hey Cato,
>
>  Catonano <catonano@gmail.com> writes:
>
>  > […]
>  >
>  > This is an important step in making the Guile user experience less rough
>  >
>  > Where, in the manual, should such mention be placed ?
>
>  I guess section '4.6 Using Guile Tools' might be a good place to put it?
>
>  4.5 advetises paredit and geiser — but that is specific to Emacs.  4.6
>  is about guile tools more generally.  So I imagine something like the
>  blurbs about paredit and geiser, but then for hall and in 4.6?
>
>  What do you think?
>
> I'm ok with that
>
> I'm somewhat puzzled by 4.7, it's about installing Guile code.
>
> It mentions system controlled locations (on traditional systems) such as usr/lib/...
>
> it seems it assumes that people install guile object files by hand ?

Right.  I think this strengthens my believe it should go in 4.6.  I
would like new users to be able to get started with Hall, which just
does the right thing (hopefully) in terms of installing files in the
right places.  And then, when the user is ready for it, they can dive
deeper with 4.7.  They can start grokking how load paths & compilation
and the module system works etc.

But as it stands — I remember when I first started out with Guile — this
stuff is confounding!  By now I can see, first class modules are
amazing.  The introspective capabilities of Guile are a dream to work
with; and understanding how these data structures map onto the file
system is really useful.  But it's definitely something that should be
able to be a black box in the beginning!

> On another side, if you have some .scm files scattered around, they
> will be autocompiled and the result will be put into some well hidden
> buried folder in your home folder
>
> […]
>
> it took me years to figure out the Guile distribution story and this
> email is a distillate of years of confusion

Thanks for this write-up.  It is a very useful stab at categorising the
different levels and moving parts involved.  I'm taking all the emails
in this discussion and will be thinking about them in the coming days.
Clearly there *is*, not just a project bootstrapping role for Hall, but
also a distribution/installation story.  Something in between autotools
and file-fiddling and the brutalist beauty of Guix.

> I'll try to write a mention of guile-hall for the manual and send a
> patch.
>
> Not right now, though. In the coming days

Absolutely, thanks for offering!  Happy to give your draft a once over
if you want!

Alex



  parent reply	other threads:[~2020-05-17 20:48 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 [this message]
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
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=87y2pqcmox.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).