From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Ricardo Wurmus <rekado@elephly.net>, 43477@debbugs.gnu.org
Subject: [bug#43477] Guix aliases?
Date: Fri, 25 Sep 2020 19:00:22 +0200 [thread overview]
Message-ID: <CAJ3okZ3wVYRF7RSUELSEwgb6uaPt6B5zyas1CWaMC8mcMamY=A@mail.gmail.com> (raw)
In-Reply-To: <878scxkfyd.fsf@gnu.org>
On Fri, 25 Sep 2020 at 17:56, Ludovic Courtès <ludo@gnu.org> wrote:
> What I meant to say was that, if we have other use cases, we can write
> new commands or extend existing ones to cater to those needs. That’s
> how ‘guix size’, etc. came to life. “Listing nodes” is not a use case
> per se, but rather an means to an end; let’s focus on the ends. :-)
>
> (Also, let’s avoid Unix arguments; the primary composition level in Guix
> is Scheme, not byte streams on stdout.)
Well, I am not sure yet if I agree or disagree with you. :-)
I understand the arguments and I will not have time to write a v2
which includes your suggestion; I am interested in listing the nodes
for some ends, not by visualizing the graph in a non-X environment.
Therefore, feel free to close this patch submission.
Cheers,
simon
next prev parent reply other threads:[~2020-09-25 17:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 19:39 [bug#43477] [PATCH 0/1] guix: graph: Add 'plain' backend zimoun
2020-09-17 19:40 ` [bug#43477] [PATCH 1/1] " zimoun
2020-09-18 9:35 ` [bug#43477] [PATCH 0/1] " Mathieu Othacehe
2020-09-18 19:59 ` zimoun
2020-09-18 12:34 ` Ricardo Wurmus
2020-09-18 20:04 ` zimoun
2020-09-24 14:44 ` Ludovic Courtès
2020-09-24 15:47 ` zimoun
2020-09-25 9:32 ` Ludovic Courtès
2020-09-25 9:54 ` zimoun
2020-09-25 10:11 ` Ricardo Wurmus
2020-09-25 12:22 ` [bug#43477] Guix aliases? (was: [bug#43477] [PATCH 0/1] guix: graph: Add 'plain' backend.) zimoun
2020-09-25 15:56 ` [bug#43477] Guix aliases? Ludovic Courtès
2020-09-25 17:00 ` zimoun [this message]
2020-10-05 8:03 ` bug#43477: " 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
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='CAJ3okZ3wVYRF7RSUELSEwgb6uaPt6B5zyas1CWaMC8mcMamY=A@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=43477@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=rekado@elephly.net \
/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).