From: "Ludovic Courtès" <ludo@gnu.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 36239@debbugs.gnu.org
Subject: [bug#36239] [PATCH] opensmtpd-service-type to extend pam
Date: Thu, 20 Jun 2019 14:49:51 +0200 [thread overview]
Message-ID: <87y31wifps.fsf@gnu.org> (raw)
In-Reply-To: <87r27o30xi.fsf@nckx> (Tobias Geerinckx-Rice's message of "Thu, 20 Jun 2019 14:18:27 +0200")
Tobias Geerinckx-Rice <me@tobias.gr> skribis:
> Ludovic Courtès wrote:
>> I think I’d use it here; that’s consistent with the rest of the file
>> actually, no? To me everything looks OK as it is.
>
> Then I'm not sure I grok % (which is likely as I've never read a
> description, only induced its use).
>
> What's the difference between:
>
> (define (%dovecot-activation config) …
>
> and
>
> (define opensmtpd-activation …
> (define exim-activation …
>
> ? I thought it had something to do with being exports/globals but
> here (%opensmtpd-accounts, etc.) it is used simply to say ‘this is a
> list’.
It’s a long story. :-)
Initially in Guile the ‘%’ prefix was used for “system” bindings, thing
you don’t normally use as a normal user. Then I think I started using
it for things that are meant to be “internal” or variables meant to be
read-only (not procedures). In Guix we sort of follow that but somewhat
extend the meaning.
In the example above, I’d rather write ‘dovecot-activation’ (without
prefix, because it’s a procedure), but I’d probably write
‘%exim-activation’, depending on the phase of the moon.
HTH!
Ludo’.
next prev parent reply other threads:[~2019-06-20 12:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-16 2:45 [bug#36239] [PATCH] opensmtpd-service-type to extend pam Kristofer Buffington
2019-06-19 20:40 ` Ludovic Courtès
2019-06-20 0:52 ` Kristofer Buffington
2019-06-20 9:11 ` Tobias Geerinckx-Rice
2019-06-20 9:23 ` Tobias Geerinckx-Rice
2019-06-20 11:54 ` Ludovic Courtès
2019-06-20 12:18 ` Tobias Geerinckx-Rice
2019-06-20 12:49 ` Ludovic Courtès [this message]
2019-06-20 13:54 ` Tobias Geerinckx-Rice
2019-06-20 11:52 ` Ludovic Courtès
2019-06-20 14:01 ` bug#36239: " Tobias Geerinckx-Rice
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=87y31wifps.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=36239@debbugs.gnu.org \
--cc=me@tobias.gr \
/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).