From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 00/14] Enhanced df - followup
Date: Tue, 29 Apr 2014 17:10:31 +0000 (UTC) [thread overview]
Message-ID: <pan$274e8$4b1540e1$e4bc4fe0$2126c4cf@cox.net> (raw)
In-Reply-To: cover.1398786620.git.dsterba@suse.cz
David Sterba posted on Tue, 29 Apr 2014 17:56:47 +0200 as excerpted:
> Changes:
> * btrfs filesystem disk_usage - renamed to usage
Hopefully this isn't rehashing an old discussion, but...
Simpler is good, and getting rid of the _ is good, but...
To users familiar with Unix/POSIX/Linux CLI, "usage" (as --usage) is most
often seen as a rather less common and generally briefer form of --help,
usually with the distinction being that --help may be a screen or more of
output, while --usage is much shorter, perhaps a single line.
While I had seen it listed in manpages and --help output often enough,
once I actually went looking for real examples I had a hard time finding
some, but eventually found some in the grub (grub2) command set.
$ grub-bios-setup --usage
Usage: grub-bios-setup [-afsv?V] [-b FILE] [-c FILE] [-d DIR] [-m FILE]
[--allow-floppy] [--boot-image=FILE] [--core-image=FILE]
[--directory=DIR] [--force] [--device-map=FILE] [--no-rs-
codes]
[--skip-fs-probe] [--verbose] [--help] [--usage] [--version]
DEVICE
(For brevity, just printing the line-count for the following few example
grub-* commands, not the full output.)
$ grub-bios-setup --help | wc -l
30
$ grub-probe --usage | wc -l
3
$ grub-probe --help | wc -l
23
$ grub-editenv --usage | wc -l
2
$ grub-editenv --help | wc -l
23
While --usage does normally appear with the usual long-option double-dash
and the proposal for btrfs does not, I'd still consider a simple
"btrfs filesystem usage" confusing at best, expecting it to print out a
short help/usage for the "btrfs filesystem" command, either due to not
understanding the token and thus printing command usage, or understanding
it as a request to print command usage, NOT the actual filesystem usage.
OTOH, for CLI veterans anyway, standard old "du" (btrfs fi du) should be
as immediately understood as "df".
Given that confusion, I'd suggest either simply making it du, or making
it "device_usage" but with "du" a documented alias printing exactly the
same output, thus giving folks an easy way to avoid the _.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2014-04-29 17:10 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 15:56 [PATCH 00/14] Enhanced df - followup David Sterba
2014-04-29 15:57 ` [PATCH 01/14] btrfs-progs: read global reserve size from space infos David Sterba
2014-04-29 15:57 ` [PATCH 02/14] btrfs-progs: add original 'df' and rename 'disk_usage' to 'usage' David Sterba
2014-04-29 15:58 ` [PATCH 03/14] btrfs-progs: move device usage to cmds-device, more cleanups David Sterba
2014-04-29 15:58 ` [PATCH 04/14] btrfs-progs: check if we can't get info from ioctls due to permissions David Sterba
2014-04-29 16:01 ` [PATCH 05/14] btrfs-progs: zero out structures before calling ioctl David Sterba
2014-04-29 16:02 ` [PATCH 06/14] btrfs-progs: print B for bytes David Sterba
2014-04-29 16:02 ` [PATCH 07/14] btrfs-progs: Print more info about device sizes David Sterba
2014-04-29 19:23 ` Mike Fleetwood
2014-04-30 11:39 ` Goffredo Baroncelli
2014-04-30 12:11 ` David Sterba
2014-04-30 13:31 ` Frank Kingswood
2014-04-30 13:37 ` David Taylor
2014-04-30 17:38 ` Goffredo Baroncelli
2014-05-02 13:13 ` David Sterba
2014-05-02 13:15 ` David Sterba
2014-05-14 18:00 ` David Sterba
2014-04-30 11:52 ` David Sterba
2014-04-29 16:02 ` [PATCH 08/14] btrfs-progs: compare unallocated space against the correct value David Sterba
2014-04-29 16:02 ` [PATCH 09/14] btrfs-progs: add section of overall filesystem usage David Sterba
2014-04-29 16:02 ` [PATCH 10/14] btrfs-progs: cleanup filesystem/device usage code David Sterba
2014-04-29 16:02 ` [PATCH 11/14] btrfs-progs: extend pretty printers with unit mode David Sterba
2014-04-29 16:02 ` [PATCH 12/14] btrfs-progs: replace df_pretty_sizes with pretty_size_mode David Sterba
2014-04-29 16:02 ` [PATCH 13/14] btrfs-progs: clean up return codes and paths David Sterba
2014-04-29 16:03 ` [PATCH 14/14] btrfs-progs: move global reserve to overall summary David Sterba
2014-04-29 17:10 ` Duncan [this message]
2014-04-29 17:17 ` [PATCH 00/14] Enhanced df - followup Marc MERLIN
2014-04-29 17:33 ` Holger Hoffstätte
2014-04-30 0:42 ` Duncan
2014-04-30 8:15 ` Martin Steigerwald
2014-04-30 12:37 ` David Sterba
2014-04-30 13:01 ` David Sterba
2014-04-30 17:25 ` Duncan
2014-04-29 19:14 ` Mike Fleetwood
2014-04-30 12:22 ` David Sterba
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='pan$274e8$4b1540e1$e4bc4fe0$2126c4cf@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.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.
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 NNTP newsgroup(s).