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

New Issue

tahoe-lafs · 2015-10-23T18:04:10Z

daira commented

2015-10-23 18:04:10 +00:00

-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.

`-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.

tahoe-lafs added the

labels 2015-10-23 18:04:10 +00:00

tahoe-lafs added this to the undecided milestone 2015-10-23 18:04:10 +00:00

zooko commented

2015-10-23 18:16:12 +00:00

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.

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.

Sign in to join this conversation.