unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Christopher Allan Webber <cwebber@dustycloud.org>
To: "Luis Felipe López Acevedo" <felipe.lopez@openmailbox.org>
Cc: guile-devel@gnu.org
Subject: Re: Ideas for a Guile tutorial to go with the new site
Date: Fri, 30 Oct 2015 10:41:08 -0500	[thread overview]
Message-ID: <87mvv0fjoi.fsf@dustycloud.org> (raw)
In-Reply-To: <012ecd1a116579c9f312563187bfa475@openmailbox.org>

Luis Felipe López Acevedo writes:

> On 2015-10-20 17:45, BCG wrote:
>> On 10/19/2015 12:29 PM, Christopher Allan Webber wrote:
>>> Amirouche Boubekki writes:
>>> 
>>>> To the contrary I think it's not a good idea to start upfront the
>>>> tutorial with which editor should be used is a good way to loose half 
>>>> of
>>>> the readers, because they will feel more uncomfortable and not up to 
>>>> the
>>>> task. To be useful emacs requires one 'Getting Started' tutorial in
>>>> itself. Or anykind of setup for that matter. The tutorial should go 
>>>> as
>>>> quickly as possible to the matter and start with coding.
>>>> 
>>>> I started a tutorial at http://hypermove.net/. I don't introduce
>>>> readline until the user knows what the REPL is. Part 1 is all done in
>>>> REPL. I subtly introduce emacs as a good choice for an editor in part 
>>>> 2
>>>> which is done in an editor. But doesn't enforce it.
>>> Okay, sorry if I wasn't being clear... my goal in that section would 
>>> be
>>> to encourage everyone who *isn't already an emacs user* to pick up a
>>> simple editor and know how to use that with Guile, but them give them 
>>> a
>>> brief tip that they want to look into Emacs + Geiser once they've 
>>> dived
>>> in a bit more deeply.
>>> 
>>> I don't think this section needs to be too long.  I agree it should 
>>> not
>>> be overwhelming.
>>> 
>> Personally I would appreciate a not-so-brief tip.  Most resources on
>> the web about coding in scheme seem to claim that emacs is the best
>> environment for it, but rarely go into the reasoning about why or
>> provide a focused way to get started with it.  I'd be happy to try out
>> those tools, but it hardly is worth it to me to slog through the emacs
>> tutorial just to see if I like whatever advantages it may have for
>> coding Scheme.
>
> I think a video tutorial to get the user started with Guile + Emacs 
> would be great for that. First video in a "Learn GNU Guile" series 
> hosted in a MediaGoblin instance :)

That would be great, yes!



  reply	other threads:[~2015-10-30 15:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-18 15:41 Ideas for a Guile tutorial to go with the new site Christopher Allan Webber
2015-10-18 16:45 ` Taylan Ulrich Bayırlı/Kammer
2015-10-18 18:44 ` Luis Felipe López Acevedo
2015-10-18 19:26   ` Amirouche Boubekki
2015-10-19 16:29     ` Christopher Allan Webber
2015-10-20 22:45       ` BCG
2015-10-21 15:01         ` Christopher Allan Webber
2015-10-27 15:17         ` Luis Felipe López Acevedo
2015-10-30 15:41           ` Christopher Allan Webber [this message]
2015-11-19 20:24 ` Ludovic Courtès
2015-11-19 21:28   ` Christopher Allan Webber
2015-11-19 21:12 ` Mathieu Lirzin
2015-11-19 21:27   ` Christopher Allan Webber
2015-12-15 20:28 ` Christopher Allan Webber
2015-12-15 20:31   ` Christopher Allan Webber
2015-12-16 10:35   ` Alex Sassmannshausen
2015-12-16 14:33     ` Christopher Allan Webber
2015-12-17  2:41       ` Mike Gerwitz
2015-12-17  6:21         ` Christopher Allan Webber

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=87mvv0fjoi.fsf@dustycloud.org \
    --to=cwebber@dustycloud.org \
    --cc=felipe.lopez@openmailbox.org \
    --cc=guile-devel@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).