From: Tom via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 40549@debbugs.gnu.org
Subject: bug#40549: More usability issues:
Date: Thu, 23 Apr 2020 21:51:36 +0200 [thread overview]
Message-ID: <3827671.e9J7NaK4W3@peach> (raw)
In-Reply-To: <6171889.DvuYhMxLoT@cherry>
To add detail here:
Doing `guix package -d 18 -S 17` actually works.
This gives me the impression that the order of arguments is relevant to the
processing of them.
This sounds like a bad idea because that is quite unlike the normal gnu
command line parsers behavior (and generally any command line parsers, unless
in very rare cases).
The 'package' subcommand should likely always try to do things in-order. First
Switch, reject any second Switch argument.
Then delete (which can be repeated).
Etc.
That would be much more predicable and UX friendly.
Another, similar, example is:
guix package -l --profile=a
this doesn't work. But the most curious thing is that this does:
guix package --list-installed --profile=a
and this too:
guix package --profile=a -l
and this too;
guix package -l --profile=a -l
The things that DONT work are confusingly similar to the things that do, and
the things don't make sense (having -l twice) work just fine without errors.
As said, this is a UX gem to fix. Please take some time to make command line
parting usable by humans!
next prev parent reply other threads:[~2020-04-23 19:52 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 ` Tom via Bug reports for GNU Guix [this message]
2020-04-24 8:28 ` bug#40549: More usability issues: 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
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=3827671.e9J7NaK4W3@peach \
--to=bug-guix@gnu.org \
--cc=40549@debbugs.gnu.org \
--cc=tomz@freedommail.ch \
/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).