From: Efraim Flashner <efraim@flashner.co.il>
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: guix-devel@gnu.org
Subject: Re: Adding wc to Bournish
Date: Wed, 25 May 2016 12:43:09 +0300 [thread overview]
Message-ID: <20160525094309.GA15009@debian-netbook> (raw)
In-Reply-To: <idj37p64ihl.fsf@bimsb-sys02.mdc-berlin.net>
[-- Attachment #1: Type: text/plain, Size: 1953 bytes --]
On Wed, May 25, 2016 at 11:03:34AM +0200, Ricardo Wurmus wrote:
>
> Efraim Flashner <efraim@flashner.co.il> writes:
>
> > +(define (wc-command file)
> > + (if (and (file-exists? file) (access? file 4))
> > + (let* ((wc-l ((@@ (guix build bournish) wc-l-command) file))
> > + (wc-w ((@@ (guix build bournish) wc-w-command) file))
> > + (wc-c ((@@ (guix build bournish) wc-c-command) file)))
> > + (begin
> > + (display wc-l)(display #\space)
> > + (display wc-w)(display #\space)
> > + (display wc-c)(display #\space)
> > + (display file)
> > + (newline)))))
>
> Have you considered using “format” instead of “display”? The last
> “begin” could just be this:
>
> (format #t "~a ~a ~a ~a\n"
> wc-l wc-w wc-c file)
>
> or
>
> (format #t "~{~a ~}\n"
> (list wc-l wc-w wc-c file))
I looked at the manual more and I found for-each which does what I was
looking for before which gave me this:
(for-each display (list wc-l #\space wc-w #\space wc-c #\space file))
but I do like the (format #t "~{~a ~}\n" (list ...)) better. I'm working
on trying to get it to read flags and the variable size of the list
works better with that.
format vs display, I knew I wanted display over write but I hadn't come
across format yet. If I don't need to specify #\space to get a space
then that sounds great.
>
> Why is it necessary to do “(@@ (guix build bournish) ...)”? Can it not
> be imported once?
When you say it out loud then it seems obvious it shouldn't need to be
imported more than once. I've also read more about let vs let* and I've
changed some to let.
>
> ~~ Ricardo
Thanks!
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-05-25 9:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 18:47 Adding wc to Bournish Efraim Flashner
2016-05-25 9:03 ` Ricardo Wurmus
2016-05-25 9:43 ` Efraim Flashner [this message]
2016-05-25 9:26 ` Ricardo Wurmus
2016-05-25 10:05 ` Efraim Flashner
2016-05-26 8:46 ` Ludovic Courtès
2016-05-26 17:50 ` Efraim Flashner
2016-05-26 19:27 ` Efraim Flashner
2016-05-27 13:37 ` Eric Bavier
2016-05-27 15:28 ` Taylan Ulrich Bayırlı/Kammer
2016-05-27 15:32 ` Thompson, David
2016-06-05 12:40 ` Efraim Flashner
2016-06-05 20:37 ` Ludovic Courtès
2016-06-07 7:41 ` Efraim Flashner
2016-06-08 15:43 ` Ludovic Courtès
2016-06-14 9:27 ` Efraim Flashner
2016-06-14 9:57 ` Ricardo Wurmus
2016-06-14 10:20 ` Efraim Flashner
2016-06-14 10:50 ` Efraim Flashner
2016-06-14 11:08 ` Ricardo Wurmus
2016-06-15 13:56 ` Ludovic Courtès
2016-06-15 20:28 ` Efraim Flashner
2016-06-23 8:34 ` Ludovic Courtès
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=20160525094309.GA15009@debian-netbook \
--to=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=ricardo.wurmus@mdc-berlin.de \
/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).