Opened at 2015-10-23T18:04:10Z

Last modified at 2015-10-23T18:16:12Z

#2547 new defect

it is too confusing that --basedir works for some commands and not others

Reported by: daira Owned by:
Priority: normal Milestone: undecided
Component: code-frontend-cli Version: 1.10.1
Keywords: usability error cli Cc:
Launchpad Bug:

Description (last modified by daira)

-d/--node-directory works for all commands, and for "stub" node directories containing only node.url and maybe private/aliases.

-C/--basedir only works for commands that create or start/restart/stop nodes.

The positions in which -d and -C are accepted vary, IIRC.

This is too confusing.

Change History (4)

comment:1 Changed at 2015-10-23T18:04:48Z by daira

  • Description modified (diff)

comment:2 Changed at 2015-10-23T18:05:16Z by daira

  • Description modified (diff)

comment:3 Changed at 2015-10-23T18:06:02Z by daira

  • Description modified (diff)

comment:4 Changed at 2015-10-23T18:16:12Z by zooko

I for one frequently get confused by this. I try using --basedir=blah, and when I get a usage error then I try moving the --basedir=blah to a different part of the command, and then daira reminds me that --basedir= doesn't work for the command I'm trying to run.

Note: See TracTickets for help on using tickets.