From: Vincent Legoll <vincent.legoll@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: Newbie packagers
Date: Thu, 21 Jul 2016 20:04:36 +0200 [thread overview]
Message-ID: <CAEwRq=qKf76bRZ3MZv-tEi2rpwOtwjGNPyvvAh7mY9xMXc-6=w@mail.gmail.com> (raw)
In-Reply-To: <CAEwRq=o6moK=FACir4jCRcjrnSmQ+8S+1tcZo=8CFmuJJS0e_w@mail.gmail.com>
> I'll go read it and see what I find missing
quick ideas:
1 - the concept index has those: ! # ( . / maybe add ` ' , ,@ with
their aliases / long names alongside (quote, quasiquote, unquote,
unquote-splicing)
2 - they are well hidden in :
The Guile Reference Manual
API Reference
Reading and Evaluating Scheme Code
Scheme Syntax: Standard and Guile Extensions
Expression Syntax
That's far away, and the title don't help find them...
In the mean time I did a search "guile scheme quote", and indeed the
right doc page is there (16th on duckduckgo), and google is way
better (1st place)...
I forgot that sometimes google gives better answers than ddg...
3 - I'd add the following to (unquote-splicing expr):
`(1 ,x 4) ⇒ (1 (2 3) 4)
to better demonstrate the effect of splicing
and to (unquote expr) :
`(1 2 (* 9 9) 3 4) ⇒ (1 2 (* 9 9) 3 4)
--
Vincent Legoll
next prev parent reply other threads:[~2016-07-21 18:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 13:21 Newbie packagers Vincent Legoll
2016-07-21 15:52 ` Ricardo Wurmus
2016-07-21 17:13 ` Vincent Legoll
2016-07-22 8:30 ` Chris Marusich
2016-07-23 10:21 ` Andreas Enge
2016-07-23 10:36 ` Vincent Legoll
2016-07-21 15:54 ` Ludovic Courtès
2016-07-21 17:19 ` Vincent Legoll
2016-07-21 18:04 ` Vincent Legoll [this message]
2016-07-22 7:13 ` Vincent Legoll
2016-07-22 12:23 ` Ludovic Courtès
2016-07-22 12:43 ` Vincent Legoll
2016-07-22 12:41 ` Ludovic Courtès
2016-07-22 12:46 ` Vincent Legoll
2016-07-22 14:41 ` Ludovic Courtès
2016-07-22 20:01 ` Vincent Legoll
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAEwRq=qKf76bRZ3MZv-tEi2rpwOtwjGNPyvvAh7mY9xMXc-6=w@mail.gmail.com' \
--to=vincent.legoll@gmail.com \
--cc=help-guix@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.