Re: option hint for all commands?

[Hartmut Goebel]

Am 25.02.21 um 00:47 schrieb zimoun:

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?


+1

--
Schönen Gruß
Hartmut Goebel
Dipl.-Informatiker (univ), CISSP, CSSLP, ISO 27001 Lead Implementer
Information Security Management, Security Governance, Secure Software 
Development


Goebel Consult, Landshut
http://www.goebel-consult.de 

Blog: https://www.goe-con.de/blog/alternative-android-betriebssystem 

Kolumne: 
https://www.goe-con.de/hartmut-goebel/cissp-gefluester/2011-09-kommerz-uber-recht-fdp-die-gefaellt-mir-partei 
 

option hint for all commands?

[zimoun]

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: 
2: 
3: 


All the best,
simon