unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Chris Marusich <cmmarusich@gmail.com>
To: Jone <yeger9@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Simple reconfigure
Date: Sat, 28 Apr 2018 13:11:50 -0700	[thread overview]
Message-ID: <87h8nvks55.fsf@gmail.com> (raw)
In-Reply-To: <87po2juqdz.fsf@gmail.com> (Jone's message of "Sat, 28 Apr 2018 18:39:36 +0000")

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

Jone <yeger9@gmail.com> writes:

> Don't refer to manual, please - it does not answer practical
> questions. Why do you think there are so few packages? - and no one
> knows how to build them! I tried, and of course I did not succeed. For
> example, when I write to elisp, I guess by context how and what I should
> do next. And a powerful contextual help system is also very helpful.
>
> I have many practical questions - I use this distribution on real
> hardware, as the main system. I like Lisp, but I'm just a user, not a
> hacker..

Inside every user is a hacker waiting to be set free!  ;-)

I hear what you're saying about the manual.  It does show examples for
many things, though.  In this case, what sort of example were you hoping
to find?  Maybe we can add or improve an example that would have helped
you (and others who might have the same questions).  Feedback like this
is very important, so thank you for taking the time to bring it up!

> About 'cons' and 'cons*' - okay, let's see in the manual. Examples,
> examples, examples, more examples! ;) That would be great.

There are lots of tutorials to Scheme on the internet.  The Guile manual
is pretty good at introducing concepts, but I have had to look elsewhere
to improve my understanding of some topics.  When in doubt, an Internet
search with "scheme" in the keyword list will probably turn up some
useful articles.

When I was starting out, I began by reading Structure and Interpretation
of Computer Programs, which is a very thoughtful introduction to scheme.
It's also an introduction to some fundamental concepts of computer
programming.  It's worth a try, if you're feeling curious.  Since it's
licensed under a free license, you can even find a copy of it in Guix!

  guix package -i sicp
  # View it with the stand-alone Info reader.
  info sicp
  # Or, view it in a web browser, like icecat.
  icecat $HOME/.guix-profile/share/doc/sicp/html/index.xhtml

I feel your pain, but hang in there!  It gets easier as you become more
familiar with Guix and with scheme.  Happy hacking!

-- 
Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2018-04-28 20:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-27 15:38 Simple reconfigure Jone
2018-04-28  5:01 ` Chris Marusich
2018-04-28 18:39   ` Jone
2018-04-28 20:11     ` Chris Marusich [this message]
2018-04-28 21:35       ` myglc2
2018-04-29  3:23         ` Chris Marusich
2018-04-29  3:27         ` Arun Isaac
2018-04-29  6:39           ` Pierre Neidhardt
2018-04-30 13:05           ` Ludovic Courtès
2018-04-29  6:37       ` Pierre Neidhardt
2018-04-29  6:40         ` Pierre Neidhardt

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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h8nvks55.fsf@gmail.com \
    --to=cmmarusich@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=yeger9@gmail.com \
    /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).