From: "Ludovic Courtès" <ludo@gnu.org>
To: "(" <paren@disroot.org>
Cc: 57090@debbugs.gnu.org, Christopher Rodriguez <yewscion@gmail.com>,
Maxime Devos <maximedevos@telenet.be>
Subject: bug#57090: [BUG] Default Notation for chmod in guix style?
Date: Tue, 09 Aug 2022 23:12:20 +0200 [thread overview]
Message-ID: <87czd92kaz.fsf@gnu.org> (raw)
In-Reply-To: <CM1SWY80OFEA.YWFI9JJ7KLOC@guix-aspire> (paren@disroot.org's message of "Tue, 09 Aug 2022 22:04:24 +0100")
Hi,
"(" <paren@disroot.org> skribis:
> On Tue Aug 9, 2022 at 9:59 PM BST, Maxime Devos wrote:
>> 'chmod' is not mentioned anywhere in (guix scripts style), so I'd think
>> it's just an oversight. The authority on the matter would be Ludovic
>> Courtès <ludo@gnu.org>
>
> Is it possible that (guix read-print) stores octal numbers directly as
> Scheme numbers, with no way to distinguish them from decimal numbers,
> which means when they are printed they are just treated as base10? I
> poked around a bit in the module but couldn't find the code for number
> reading.
Indeed, the reader is basically a wrapper around ‘read’. It preserves
comments and vertical space, but it doesn’t attempt to preserve the
style of numbers (base, etc.), strings (whether \n & co. are escaped or
literal), and so on. I think that’d be a bit too much honestly.
Now, we could tweak the pretty printer so that it recognizes patterns
where numbers or strings should be printed in a certain way.
Help welcome! :-)
Ludo’.
next prev parent reply other threads:[~2022-08-09 21:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 20:47 bug#57090: [BUG] Default Notation for chmod in guix style? Christopher Rodriguez
2022-08-09 20:59 ` Maxime Devos
2022-08-09 21:04 ` paren--- via Bug reports for GNU Guix
2022-08-09 21:12 ` Ludovic Courtès [this message]
2022-09-01 16:43 ` bug#57090: 'guix style' pretty-printer always renders integers as base10 Ludovic Courtès
2022-08-09 21:01 ` bug#57090: [BUG] Default Notation for chmod in guix style? Csepp
2022-08-09 21:08 ` paren--- via Bug reports for GNU Guix
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=87czd92kaz.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=57090@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
--cc=paren@disroot.org \
--cc=yewscion@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).