unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Ricardo Wurmus <rekado@elephly.net>, 43477@debbugs.gnu.org
Subject: [bug#43477] Guix aliases?
Date: Fri, 25 Sep 2020 17:56:42 +0200	[thread overview]
Message-ID: <878scxkfyd.fsf@gnu.org> (raw)
In-Reply-To: <CAJ3okZ0QAtfH-tXdnG+nywCOny+-USFaacWGckzD8zJW7wo9MA@mail.gmail.com> (zimoun's message of "Fri, 25 Sep 2020 14:22:25 +0200")

Hi,

zimoun <zimon.toutoune@gmail.com> skribis:

> On Fri, 25 Sep 2020 at 12:10, Ricardo Wurmus <rekado@elephly.net> wrote:
>
>> > There is a "guix graph --path" which is really nice.  Why not "guix
>> > graph --list-nodes"?
>>
>> Wouldn’t the tree view that Ludo proposed match your use case?  You can
>> still grep the output (filtering non-alphanum characters), but it would
>> be more useful by default.
>
> I would say no.  :-) You are proposing:
>
>    guix graph -b ludo-backend | tr -dc '\0-\177'
>
> right?

I don’t think so.  The tree view would be a way to visualize the graph,
first and foremost.

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.)

>  2- add a mechanism to have aliases.

I agree it’d be nice but… we’re drifting off-topic.  :-)

Thanks,
Ludo’.




  reply	other threads:[~2020-09-25 16:14 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                 ` Ludovic Courtès [this message]
2020-09-25 17:00                   ` [bug#43477] Guix aliases? zimoun
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=878scxkfyd.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=43477@debbugs.gnu.org \
    --cc=rekado@elephly.net \
    --cc=zimon.toutoune@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).