some CLI commands accept "--verbose", other don't #1101

New Issue

Open

opened 2010-06-28 22:11:25 +00:00 by zooko · 1 comment

zooko commented

2010-06-28 22:11:25 +00:00

For example, I can run:

tahoe cp --verbose …

and it works, but then when I run

tahoe mkdir --verbose …

it says:

tahoe:  option --verbose not recognized

For consistency, perhaps all commands should accept --verbose even if some of them (currently) don't change their behavior in the presence of it.

For example, I can run: ``` tahoe cp --verbose … ``` and it works, but then when I run ``` tahoe mkdir --verbose … ``` it says: ``` tahoe: option --verbose not recognized ``` For consistency, perhaps all commands should accept `--verbose` even if some of them (currently) don't change their behavior in the presence of it.

zooko added the

code-frontend-cli

labels 2010-06-28 22:11:25 +00:00

zooko added this to the undecided milestone 2010-06-28 22:11:25 +00:00

zooko commented

2010-06-28 22:11:55 +00:00

Author

(Or actually even better would be to make all commands change their behavior to emit progress indicators and other useful tidbits when --verbose.)

(Or actually even better would be to make all commands change their behavior to emit progress indicators and other useful tidbits when `--verbose`.)

Sign in to join this conversation.

No Label

LeastAuthority.com automation

cannot reproduce

code-frontend-cli

code-frontend-ftp-sftp

code-frontend-magic-folder

code-frontend-web

code-peerselection

dev-infrastructure

somebody else's problem

was already fixed

No Milestone

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#1101

No description provided.