From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: option hint for all commands?
Date: Thu, 25 Feb 2021 00:47:43 +0100 [thread overview]
Message-ID: <86im6hkoyo.fsf@gmail.com> (raw)
In-Reply-To: <CAJ3okZ00p5ADTJUGAwS4dX7SedTURazV+RX_zcgpAmu3XYwn5g@mail.gmail.com>
Hi,
From patch#45893 [1]:
> it works for commands using 'parse-command-line' and
> not 'args-fold*'. For example, one patch of the series replace for
> "guix show" and "guix search". I would like to replace all the
> args-fold* by parse-command-line, I think it makes sense. WDYT?
which means that:
$ guix build --load-pth=/tmp/ hello
guix build: error: load-pth=/tmp/: unrecognized option
hint: Did you mean `load-path'?
$ guix show --load-pth=/tmp/ hello
guix show: error: load-pth=/tmp/: unrecognized option
Other said, all the commands using ’parse-command-line’ enjoy the typo
hinter and all the commands using ’args-parse*’ don’t. I am proposing
to use ’parse-command-line’ for all the commands . Any objection?
In [2]–with the correction passing ’#:build-options? #f’–there is an
example for “guix show” and “guix search”.
(using patch#46308 [3] i.e., commit e68ae7f)
1: <http://issues.guix.gnu.org/issue/45893>
2: <http://issues.guix.gnu.org/issue/45893#4>
3: <http://issues.guix.gnu.org/issue/46308>
All the best,
simon
next parent reply other threads:[~2021-02-24 23:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210115163732.53665-1-zimon.toutoune@gmail.com>
[not found] ` <20210119212810.20681-1-zimon.toutoune@gmail.com>
[not found] ` <87ft2nxumw.fsf_-_@gnu.org>
[not found] ` <86lfcficb7.fsf@gmail.com>
[not found] ` <877dnpbdas.fsf_-_@gnu.org>
[not found] ` <CAJ3okZ00p5ADTJUGAwS4dX7SedTURazV+RX_zcgpAmu3XYwn5g@mail.gmail.com>
2021-02-24 23:47 ` zimoun [this message]
2021-03-01 14:07 ` option hint for all commands? Hartmut Goebel
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=86im6hkoyo.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@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).