unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: swedebugia@riseup.net
To: Guile User <guile-user@gnu.org>
Subject: Flattening the learning curve of guile
Date: Mon, 10 Dec 2018 11:07:21 -0800	[thread overview]
Message-ID: <7001e20ec2418873e9672cb8d91a6269@riseup.net> (raw)

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.

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
...

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.)

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?

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/

Any thoughts?

-- 
Cheers 
Swedebugia



             reply	other threads:[~2018-12-10 19:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-10 19:07 swedebugia [this message]
2018-12-11 15:09 ` Flattening the learning curve of guile sirgazil

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=7001e20ec2418873e9672cb8d91a6269@riseup.net \
    --to=swedebugia@riseup.net \
    --cc=guile-user@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).