From: ludo@gnu.org (Ludovic Courtès)
To: Nikita Karetnikov <nikita@karetnikov.org>
Cc: bug-guix@gnu.org
Subject: Re: [PATCH] Add 'guix hash'.
Date: Thu, 11 Apr 2013 22:35:23 +0200 [thread overview]
Message-ID: <87txncbyb8.fsf@inria.fr> (raw)
In-Reply-To: 87hajfbrcr.fsf@karetnikov.org
Nikita Karetnikov <nikita@karetnikov.org> skribis:
>> I think it’d be nice to have a ‘warning’ procedure in (guix ui), so
>> things are uniform. Furthermore, ‘guix-main’ could do:
>
>> (parameterize ((current-script-name arg0))
>> ...)
>
>> so that ‘warning’ and similar procedures could pick up the program
>> name from there.
>
> Not sure how to do it. How can I get the result of 'guix-main' from a
> relevant script (e.g., 'guix/scripts/hash.scm')?
>
> I assume that 'parameterize' should be placed inside 'guix-main'. But
> how can 'warning' access its internals? Note that I'm new to
> 'parameterize' and I'm not really comfortable with it. (Yep, I've read
> the manual.)
‘parameterize’ sets dynamically-scoped variables (or “parameters”, in
SRFI-39 terms). So for instance:
(let* ((p (make-parameter 'outside))
(f (lambda () (format #f "i am ~a" (p)))))
(parameterize ((p 'inside))
(f)))
⇒ "i am inside"
It’s like ‘current-input-port’ & co.
>> Would you like to work on this, in a separate patch?
>
> Yes, I'd like to push it prior to 'guix hash'. But it seems that you'll
> do all the work if you answer my questions. So feel free to push if the
> patch is just a couple of lines.
OK, done.
>> I was thinking that it might be enough to list the supported formats
>> in the manual, and not in --help, which should remain concise. WDYT?
>
> Of course, it should be concise but also helpful. I was puzzled when I
> saw it for the first time. So I still think that we should mention the
> formats in the output of '--help'. I'll create a patch for
> 'guix download' if you agree.
OK.
>>>> Also, could you add an entry in the manual (with a couple of
>>>> sentences explaining when users should care about this tool, and
>>>> what it does), as well as a line in po/POTFILES.in?
>
>>> Done. But what is a translatable string? Is it a string that should
>>> be i18n'd?
>
>> Yes, introduced by a call to the ‘gettext’ procedure, of which ‘_’ is
>> an alias.
>
> Why should we keep track of such files?
Because ‘xgettext’ extracts translatable strings from files listed
therein (info "(gettext) po/POTFILES.in").
> Also, what is the purpose of 'let' in 'guix-main'? If I get it right,
> it's used to isolate some functions [1]. But 'option?' is not a
> top-level function. So why bother? (I expect it's not that easy.)
Yeah, I’d have written:
(define (guix-main ...)
(define (option? x) ...)
(initialize-guix)
(match args ...))
But it’s basically equivalent.
Ludo’.
next prev parent reply other threads:[~2013-04-11 20:35 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-01 5:06 [PATCH] Add 'guix hash' Nikita Karetnikov
2013-04-03 8:34 ` Ludovic Courtès
2013-04-05 14:04 ` Nikita Karetnikov
2013-04-05 14:14 ` Nikita Karetnikov
2013-04-05 16:15 ` Ludovic Courtès
2013-04-10 11:48 ` Nikita Karetnikov
2013-04-10 11:54 ` Ludovic Courtès
2013-04-10 12:21 ` Nikita Karetnikov
2013-04-10 17:30 ` Ludovic Courtès
2013-04-05 16:13 ` Ludovic Courtès
2013-04-09 16:28 ` Nikita Karetnikov
2013-04-11 20:35 ` Ludovic Courtès [this message]
2013-04-12 5:24 ` master: FAIL: tests/guix-package.sh (was: [PATCH] Add 'guix hash'.) Nikita Karetnikov
2013-04-12 6:48 ` master: FAIL: tests/guix-package.sh Nikita Karetnikov
2013-04-12 16:24 ` Ludovic Courtès
2013-04-18 5:01 ` Enhanced 'warning' (was: [PATCH] Add 'guix hash'.) Nikita Karetnikov
2013-04-18 5:06 ` Enhanced 'warning' Nikita Karetnikov
2013-04-18 11:55 ` Ludovic Courtès
2013-04-18 19:27 ` Nikita Karetnikov
2013-04-18 20:59 ` Ludovic Courtès
2013-04-19 20:16 ` [PATCH] ui: Add a 'define-diagnostic' macro. (was: Enhanced 'warning') Nikita Karetnikov
2013-04-20 5:48 ` [PATCH] ui: Add a 'define-diagnostic' macro Nikita Karetnikov
2013-04-20 9:10 ` Ludovic Courtès
2013-04-20 17:33 ` Nikita Karetnikov
2013-04-20 19:55 ` Ludovic Courtès
2013-04-20 9:09 ` Ludovic Courtès
2013-04-21 18:14 ` [PATCH] Add 'guix hash' Nikita Karetnikov
2013-04-21 19:02 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87txncbyb8.fsf@inria.fr \
--to=ludo@gnu.org \
--cc=bug-guix@gnu.org \
--cc=nikita@karetnikov.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.