From: jbranso@dismail.de
To: "Miguel Ángel Arruga Vivas" <rosen644835@gmail.com>, guix-devel@gnu.org
Subject: Re: Using #true and #false everywhere?
Date: Sat, 17 Oct 2020 00:25:23 +0000 [thread overview]
Message-ID: <3d0ea90a13ff6104ce685c25256c190c@dismail.de> (raw)
In-Reply-To: <878sc5lta5.fsf@gmail.com>
I use "f" for followup. That works for me. :)
October 16, 2020 6:08 PM, "Miguel Ángel Arruga Vivas" <rosen644835@gmail.com> wrote:
> I didn't send this to the list... I must start using S L always instead
> of R and changing the headers manually, sorry. :o)
>
> ---
> Hi Ludo,
>
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Hello Guix!
>>
>> As discussed on IRC recently, several of us think that using “#true” and
>> “#false” instead of “#t” and “#f” throughout or documentation and code
>> would probably make it easier for newcomers to decipher that.
>>
>> WDYT?
>
> I think that it could help to the reader.
>
>> This syntax is supported since Guile 2.0. ‘write’ still uses the
>> abbreviations, but the good thing is that it means we can change all of
>> gnu/packages without triggering a single rebuild.
>
> This is even better. :)
>
>> As for the manual, I’m afraid it’ll make every msgid that contains
>> @code{#t} stale. So maybe now’s not a good time to make this change?
>
> It may be a big issue with a release in one week, but on the other hand
> the msgids would break just after releasing...
>
> Maybe other translators have a say.
>
> Happy hacking!
> Miguel
next prev parent reply other threads:[~2020-10-17 0:25 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 22:06 Using #true and #false everywhere? Miguel Ángel Arruga Vivas
2020-10-17 0:25 ` jbranso [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-10-16 10:38 Ludovic Courtès
2020-10-16 13:19 ` Maxim Cournoyer
2020-10-16 13:36 ` Tobias Geerinckx-Rice
2020-10-18 1:36 ` Maxim Cournoyer
2020-10-18 2:22 ` Bengt Richter
2020-10-19 20:45 ` zimoun
2020-10-21 9:56 ` Ludovic Courtès
2020-10-20 9:57 ` Andreas Enge
2020-10-21 9:59 ` Ludovic Courtès
2020-10-21 11:21 ` Andreas Enge
2020-10-21 15:52 ` Ludovic Courtès
2020-10-21 11:51 ` Roel Janssen
2020-10-16 16:24 ` Vagrant Cascadian
2020-10-16 23:45 ` Danny Milosavljevic
2020-10-20 10:32 ` Andreas Enge
2020-10-20 11:10 ` Ricardo Wurmus
2020-10-20 12:02 ` zimoun
2020-10-20 12:59 ` Tobias Geerinckx-Rice
2020-10-20 13:11 ` zimoun
2020-10-20 13:32 ` Tobias Geerinckx-Rice
2020-10-20 14:26 ` zimoun
2020-10-20 15:48 ` Taylan Kammer
2020-10-21 1:25 ` Mark H Weaver
2020-10-21 6:18 ` Ricardo Wurmus
2020-10-21 10:04 ` Ludovic Courtès
2020-10-20 12:45 ` zimoun
2020-10-20 12:55 ` Andreas Enge
2020-10-21 10:20 ` Ludovic Courtès
2020-10-24 18:29 ` Robin Templeton
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=3d0ea90a13ff6104ce685c25256c190c@dismail.de \
--to=jbranso@dismail.de \
--cc=guix-devel@gnu.org \
--cc=rosen644835@gmail.com \
/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).