unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 41164@debbugs.gnu.org
Subject: [bug#41164] [PATCH 0/3] Add 'guix graph --path'
Date: Sun, 10 May 2020 18:18:21 +0200	[thread overview]
Message-ID: <CAJ3okZ21kTo_PhTrMbJQ1e+A_aMG09WPEJgW9D30DugGg9K7hQ@mail.gmail.com> (raw)
In-Reply-To: <873687an8u.fsf@gnu.org>

Hi Ludo,

Reproducing the example from the manual leads to this error:

--8<---------------cut here---------------start------------->8---
./pre-inst-env guix graph --path -t references libreoffice llvm
guix graph: error: no path from
'/gnu/store/rd24gl402vy5g5sm3azhq13mwdg5fbi1-libreoffice-6.4.2.2' to
'/gnu/store/bcgnx704v408sr7lcy480wcnbkcixwrw-llvm-10.0.0-opt-viewer'
--8<---------------cut here---------------end--------------->8---


On Sun, 10 May 2020 at 16:16, Ludovic Courtès <ludo@gnu.org> wrote:

> > It appears to me not clear in '--help'.
> >
> > display the shortest path between the given nodes
>
> ‘--help’ is not a substitute for the manual though.  Do you have another

Yes for sure.  '--help' is only a remind.  I mean I use it like that:
I know something but I do not remember the exact details on how to use
it (option name, arguments order, etc.)


> wording proposal in mind that is as concise?

display the shortest path from node1 to node2


> As for ‘--path-to’ instead of ‘--path’: I think a path in common
> language is directed (one follows a path from one place to another).

My english is probably not enough good.  (Note that is the same for me
with the french word "chemin".)
To me, "path" is often ambiguous because sometimes it means oriented
and sometimes not; depending on the context: topology, graph theory,
common life: synonymous of road or track and synonymous of route or
direction.

This ambiguity added to the non positional option '--path' appears to
me confusing from where to where.

My 2 remarks come from this ambiguity of the word "path".
Well, maybe it is only me.


> > The "graph" subcommand fits well.  But for example:
> >
> >   guix show emacs --why libffi
> >   guix search emacs --why libffi
> >
> > make sense too -- at least to me. ;-)
>
> Dunno, I’m not convinced.

The main issue with "search" is that the subcommand accepts an
regxexps and so it breaks consistency.  Therefore, I answer to myself:
it is a bad idea. :-)


> > And bikeshedding again, there is a temptation  to pipe the current CLI:
> >
> >   guix graph --path emacs libffi | guix show
>
> ‘guix graph --path emacs libffi | xargs guix show’
>
> Though ‘guix show’ appears to ignore all but one argument, uh.

Yes.  Because it is a pure alias of "guix package --show='.


Cheers,
simon




  reply	other threads:[~2020-05-10 16:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-09 23:04 [bug#41164] [PATCH 0/3] Add 'guix graph --path' Ludovic Courtès
2020-05-09 23:27 ` [bug#41164] [PATCH 1/3] graph: reference/referrer node types work with graph traversal Ludovic Courtès
2020-05-09 23:27   ` [bug#41164] [PATCH 2/3] graph: Add 'shortest-path' Ludovic Courtès
2020-05-09 23:27   ` [bug#41164] [PATCH 3/3] guix graph: Add '--path' Ludovic Courtès
2020-05-10 10:51 ` [bug#41164] [PATCH 0/3] Add 'guix graph --path' zimoun
2020-05-10 14:16   ` Ludovic Courtès
2020-05-10 16:18     ` zimoun [this message]
2020-05-10 19:27       ` zimoun
2020-05-11 12:33         ` Ludovic Courtès
2020-05-11 12:36       ` Ludovic Courtès
2020-05-11 14:02         ` zimoun
2020-05-11 20:55           ` Ludovic Courtès
2020-05-11 22:13             ` zimoun
2020-05-12  8:41               ` Ludovic Courtès
2020-05-12 11:56                 ` zimoun
2020-05-11 21:36           ` bug#41164: " Ludovic Courtès
2020-05-10 23:45     ` [bug#41164] Fix pipe 'guix show' zimoun

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=CAJ3okZ21kTo_PhTrMbJQ1e+A_aMG09WPEJgW9D30DugGg9K7hQ@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=41164@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    /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).