[tahoe-lafs-trac-stream] [tahoe-lafs] #166: command line order is problematic

[tahoe-lafs]

#166: command line order is problematic
-------------------------+-------------------------------------------------
     Reporter:  zandr    |      Owner:  zooko
         Type:  defect   |     Status:  new
     Priority:  major    |  Milestone:  1.10.0
    Component:  code-    |    Version:  0.6.1
  frontend-cli           |   Keywords:  security usability unix mac error
   Resolution:           |  review-needed zookos-opinion-needed
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by zooko):

 Replying to [comment:26 davidsarah]:
 > After discussing this on IRC we ended up with the following unresolved
 issues:
 >  - {{{--help}}} for subcommands no longer mentions the global options

 This seems like an important issue to me. Users have a hard enough time
 that if they ask for help we should really give it.

 >  - because the new version accepts {{{-d}}}/{{{--node-directory}}} only
 before the command, and the old version accepted it only after the command
 (and ignored it if before), there is no way to write a script that works
 with both.
 >
 > We considered allowing {{{-d}}} both before and after but could not
 decide whether that was worth the complexity. Zooko?

 Hm... I'm not sure if there are any script-writers who are going to care
 about this. I guess since I don't have any evidence either way, I'd like
 to err on the side of ease-of-development on this. Especially since I'm
 reviewing this patch right now for inclusion in Tahoe-LAFS v1.10. So I
 think we should not worry about this compatibility-break.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/166#comment:34>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage