From: Arne Babenhauserheide <arne_bab@web.de>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 40549@debbugs.gnu.org, tomz@freedommail.ch
Subject: bug#40549: More usability issues:
Date: Wed, 13 May 2020 20:53:50 +0200 [thread overview]
Message-ID: <87o8qrwts1.fsf@web.de> (raw)
In-Reply-To: <CAJ3okZ0406hPp5437nYePZ1cZW7aw_6+oqdnca2Jq8SqgyT38w@mail.gmail.com>
Dear zimoun,
zimoun <zimon.toutoune@gmail.com> writes:
> It would like it works. And to do so, I accept that "guix package -I
> regexp -p /tmp/profile" does not anymore and would be replaced by
> "guix package -Iregexp -p /tmp/profile" which already works (as
> specified by SRFI-37).
Wow, this surprised me. I expected
guix package -Iregexp
to be equivalent to
guix package -I -r -e -g -e -x -p
which is how getopt long works in the shell.
> Today, the Guix manual is lying because the optional argument for
> short-name is *not* optional depending on its position. And that
> leads to surprise:
>
> guix package -I -p /tmp/profile # fails
> guix package -p /tmp/profile -I # works
>
> And this is really really annoying! It is hard to understand why such
> different behaviour.
Yes, this seems annoying.
> Instead of what I am proposing, what do you suggest?
What I would suggets would break -Iregexp and as such deviate from
SRFI-37, so it wouldn’t be optimal.
It would first need another SRFI so it’s no shortterm fix :-)
The commandline handling I want is this:
https://www.draketo.de/english/free-software/shell-argument-parsing
But I don’t yet have a good way to do it in Guile.
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken
next prev parent reply other threads:[~2020-05-13 18:54 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-11 9:23 bug#40549: [usability] revert last generation Tom Zander via Bug reports for GNU Guix
2020-04-23 19:37 ` Ludovic Courtès
2020-04-23 19:51 ` bug#40549: More usability issues: Tom via Bug reports for GNU Guix
2020-04-24 8:28 ` zimoun
2020-05-12 0:27 ` zimoun
2020-05-12 8:51 ` Ludovic Courtès
2020-05-12 9:54 ` Tom Zander via Bug reports for GNU Guix
2020-05-12 11:35 ` zimoun
2020-05-12 16:23 ` Tom Zander via Bug reports for GNU Guix
2020-05-12 18:08 ` zimoun
2020-05-12 20:19 ` Tom Zander via Bug reports for GNU Guix
2020-05-12 21:38 ` zimoun
2020-05-13 6:22 ` Tom Zander via Bug reports for GNU Guix
2020-05-13 16:32 ` Arne Babenhauserheide
2020-05-13 18:02 ` zimoun
2020-05-13 18:53 ` Arne Babenhauserheide [this message]
2020-05-14 9:08 ` zimoun
2020-05-12 14:10 ` zimoun
2020-05-12 10:38 ` zimoun
2020-05-12 13:58 ` zimoun
2020-05-14 8:15 ` Efraim Flashner
2020-05-14 9:13 ` zimoun
2020-05-14 14:25 ` bug#40549: Fix -p profile -p profile -I zimoun
2020-05-12 13:03 ` bug#40549: proposal for 'process-actions' zimoun
2020-05-12 16:26 ` Tom Zander via Bug reports for GNU Guix
2021-09-08 12:49 ` bug#40549: [usability] revert last generation 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=87o8qrwts1.fsf@web.de \
--to=arne_bab@web.de \
--cc=40549@debbugs.gnu.org \
--cc=tomz@freedommail.ch \
--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).