unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Arne Babenhauserheide <arne_bab@web.de>
To: alex.sassmannshausen@gmail.com
Cc: Guix-devel <Guix-devel@gnu.org>, guile-user <guile-user@gnu.org>
Subject: Re: FOSDEM 2016 slides
Date: Mon, 01 Feb 2016 16:47:07 +0100	[thread overview]
Message-ID: <871t8wtouc.fsf@web.de> (raw)
In-Reply-To: <87bn80g16p.fsf@gmail.com>

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


Hi Alex,

> And my slides from the FOSDEM devroom (for my Guile Config
> presentation), for anyone interested (copying in Guile User as it isn't
> Guix related…):
>
> http://alex.pompo.co/presentations/fosdem-16-conf.html

These are great — and I hope I can use guile-config. I tend to write
quick commandline tools which sometimes begin to grow wild. Elegant
commandline parsing is still one of the things with which I had problems
in Guile, and I hope that guile-config can fix that. It already shows
what can be gained in expressivity by macros.

Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein
ohne es zu merken

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

  reply	other threads:[~2016-02-01 15:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-30 16:32 FOSDEM 2016 slides Pjotr Prins
2016-01-30 18:49 ` Leo Famulari
2016-01-30 22:40 ` Ricardo Wurmus
2016-02-01 10:44   ` Alex Sassmannshausen
2016-02-01 15:47     ` Arne Babenhauserheide [this message]
2016-02-01 21:45       ` Alex Sassmannshausen
2016-02-01 22:03         ` Ludovic Courtès
2016-02-02  8:56           ` Alex Sassmannshausen
2016-02-03 22:14         ` Arne Babenhauserheide
2016-02-02 11:21     ` Manolis Ragkousis
2016-01-31 10:31 ` Ludovic Courtès
2016-01-31 20:47   ` Leo Famulari
2016-02-07  7:31   ` Pjotr Prins
2016-01-31 11:10 ` 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://guix.gnu.org/

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

  git send-email \
    --in-reply-to=871t8wtouc.fsf@web.de \
    --to=arne_bab@web.de \
    --cc=Guix-devel@gnu.org \
    --cc=alex.sassmannshausen@gmail.com \
    --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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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