From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Rodrigo Morales <moralesrodrigo1100@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Newbie user question: What do the columns shown by "guix package -I" mean?
Date: Sun, 26 Feb 2023 21:31:58 +0100 [thread overview]
Message-ID: <87h6v8up7g.fsf@nckx> (raw)
In-Reply-To: <CAGxMbPYM3=-RtNq3fTFVydrjtmnq+AYYGJ3sOyjj4A1BB5J5bA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1388 bytes --]
Rodrigo Morales 写道:
> Thanks! That's what I was looking for.
I'm glad to hear it!
> A related question: I didn't understand the part "retain
> backwards compatibility with isatty/stderr/etc."
First of all: I worded this poorly, as is my wont. I should have
said ‘by using’ instead of ‘with’. We're not trying to be
compatible with isatty or stderr…
Wat I meant was Guix could use the ‘isatty’ Guile procedure to
show decorate the columns only when the output is a TTY
(‘interactive’), or print a header line to ‘stderr’ so it won't be
captured by a pipe.
I think that any such solution would be fragile, do the wrong
thing in at least one case, and add too much complexity just to
sometimes add a header.
Why not simply always add a header?
Someone might be using ‘guix package -I’ in a script, and parsing
its output. In fact I guarantee you that several people are doing
so behind closed doors right now! Adding a header would break
such scripts.
I, personally, would welcome breaking their scripts—in exchange
for adding a ‘--format=<something machine-readable>’ option like
we already do for ‘guix search’. A real API that's actually
reliable and supportable. I think that's fair.
I just think I'd be outvoted and don't feel like starting a fight
:-)
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2023-02-26 20:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-26 19:49 Newbie user question: What do the columns shown by "guix package -I" mean? Rodrigo Morales
2023-02-26 20:03 ` Tobias Geerinckx-Rice
2023-02-26 20:17 ` Rodrigo Morales
[not found] ` <CAGxMbPYM3=-RtNq3fTFVydrjtmnq+AYYGJ3sOyjj4A1BB5J5bA@mail.gmail.com>
2023-02-26 20:31 ` Tobias Geerinckx-Rice [this message]
2023-02-27 10:53 ` Simon Tournier
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=87h6v8up7g.fsf@nckx \
--to=me@tobias.gr \
--cc=help-guix@gnu.org \
--cc=moralesrodrigo1100@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.
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).