Opened at 2010-03-09T06:57:09Z
Last modified at 2020-01-18T00:27:43Z
#986 closed enhancement
'tahoe run' and 'tahoe start' should be one command — at Initial Version
| Reported by: | JeremyVisser | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | undecided |
| Component: | code-frontend-cli | Version: | 1.6.0 |
| Keywords: | usability docs tahoe-run | Cc: | |
| Launchpad Bug: |
Description
Initially, I was slightly confused by the difference between tahoe run and tahoe start. Of course, reading the docs clears it up, but I can foresee getting the two mixed up in future, especially during late nights. :)
Generalising from experience, most applications either fork by default and have a flag to stop it forking, or don't fork by default, and have a flag to fork if the user desires. So it's a switch, rather than separate commands.
I suggest adding either the tahoe start --daemon or tahoe start --foreground switches. The former if you want foreground to be default, or the latter if you want daemonising to be default.
Not sure if it conflicts with any other switches, but -d and -f are choicy short versions of the above.
Any thoughts?
