unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: sirgazil <sirgazil@zoho.com>
To: swedebugia@riseup.net, Guile User <guile-user@gnu.org>
Subject: Re: Flattening the learning curve of guile
Date: Tue, 11 Dec 2018 10:09:59 -0500	[thread overview]
Message-ID: <a5974b6c-fb12-5f2d-46d8-076ccbb3110c@zoho.com> (raw)
In-Reply-To: <7001e20ec2418873e9672cb8d91a6269@riseup.net>

Hi, swedebugia :)

There is a lot one could do to make it easier for beginners to start 
using Guile. This topic has been discussed before. This is what I think 
about it:

https://lists.gnu.org/archive/html/guile-user/2017-02/msg00108.html


On 10/12/18 2:07 p. m., swedebugia@riseup.net wrote:
> Hi
> 
> I would like to help improve the manual because the learning curve is
> pretty steep at the moment (to me at least) and there a surely many good
> examples and helpful think-this-way to put into it.


Yes, I've found some places in the manual where examples would be 
useful. If you find the time to write examples, you can clone the 
documentation and send patches to Guile (see 
https://www.gnu.org/software/guile/contribute/).


> We could have a whole new section with:
> i want to do this: x
> in guile this is best done with bla bla, see this project
> i want to do this: y
> in guile this is best done with bla bla, see this example
> ...


Hmm, I don't know about this one. Maybe the tutorials could work for 
this, and I think the tutorials should be independent documents from the 
manual.


> Also the error messages really need an overhaul. Eg. the "wrong
> type"-error is cryptic at best and often you have no idea where it
> originates. (I noticed this in my wikidata library where it would pop up
> from a low level.)


I've seen error messages that I found hard to read too, but I didn't 
take note.


> Also it would be nice to update the guile-webpage with personal stories
> how people use guile and a tutorial about porting bash-scripts and
> making simple scripts in guile. (we really want people to use guile
> instead of bash-scripts don't we?


I think the guile for bash scripting tutorial would be a good addition 
to the currently lonely Tutorials section 
(https://www.gnu.org/software/guile/learn/).

I guess you could write the tutorial, send it to the mailing list for 
review, and patch the website to include it in the tutorials section.


> With simple scripts I mean a script with a main that does something with
> 100 lines max.
> 
> My wikidata library is already way past this so I guess I'm beyond
> simple scripting already! \o/


Now you could package it for Guix ;) (https://www.gnu.org/software/guix/).





      reply	other threads:[~2018-12-11 15:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-10 19:07 Flattening the learning curve of guile swedebugia
2018-12-11 15:09 ` sirgazil [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=a5974b6c-fb12-5f2d-46d8-076ccbb3110c@zoho.com \
    --to=sirgazil@zoho.com \
    --cc=guile-user@gnu.org \
    --cc=swedebugia@riseup.net \
    /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).