From: zimoun <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: "Ludovic Courtès" <ludo@gnu.org>, 43477@debbugs.gnu.org
Subject: [bug#43477] Guix aliases? (was: [bug#43477] [PATCH 0/1] guix: graph: Add 'plain' backend.)
Date: Fri, 25 Sep 2020 14:22:25 +0200 [thread overview]
Message-ID: <CAJ3okZ0QAtfH-tXdnG+nywCOny+-USFaacWGckzD8zJW7wo9MA@mail.gmail.com> (raw)
In-Reply-To: <87o8luf9nh.fsf@elephly.net>
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 will never remember that. So it means I would have a script
wrapper, somehow; and in this case, instead a AWK wrapper around the
graphviz backend could already do the job.
Well, it remembers the discussion here [1].
[1] <https://lists.gnu.org/archive/html/guix-devel/2019-07/msg00358.html>
My understanding of this situation:
1- specific "guix graph" case: implement something like Ludo
proposed; "--backend plain" in the meaning of non-graphical or
terminal displayable backend.
2- add a mechanism to have aliases.
The #1 is low priority to me. Let's expand explanations about the #2.
Now with "guix repl", the user can extend Guix by their own scripts.
Therefore, it could be nice:
a) to have a location by default (say ~/.config/guix/scripts)
b) to run them with "guix foo" instead of "guix repl --
~/.config/guix/scripts/foo.scm"
And then, we can all be happy. ;-)
It eases the tests of new experimental command-line tools, I can
locally change the behaviour of "guix environment --ad-hoc", I can
experiment with new output formats for "guix search" instead of
recutils, etc.. Well, the philosophy of custom extensions.
WDYT?
All the best,
simon
next prev parent reply other threads:[~2020-09-25 12:23 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 ` zimoun [this message]
2020-09-25 15:56 ` [bug#43477] Guix aliases? Ludovic Courtès
2020-09-25 17:00 ` 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=CAJ3okZ0QAtfH-tXdnG+nywCOny+-USFaacWGckzD8zJW7wo9MA@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).