On Thu, Aug 8, 2013 at 2:32 PM, Stestagg <stest...@gmail.com> wrote: > I would agree here, it's not at all clear. Even when you know there is a > --user option, then the fossil output isn't clear: >
In Fossil's defense: i've been using Fossil almost daily since Christmas 2007 and haven't every used --user. steves@sapphire ~> f --user foo > fossil: fossil: unknown command: --user > fossil: use "help" for more information > IIRC, only commands which use user details (e.g. a commit or tag) allow/user a user override option. Most locally-run commands don't care who you are. > # So the first argument must be the command? > > steves@sapphire ~> f --user foo ls > fossil: current directory is not within an open checkout > Unfortunately, that depends on the exact command :/. Side effects of the argument resolution process change (potentially) in what order some code must be run. i don't recall off-hand whether the top-level command dispatcher skips over --flags, but i don't see how it could because it cannot generically know if the token after a -flag is the value for the flag or if it is a command (unless it looks up the argument in its command table). i'm not in any way discounting your arguments that the help could be clearer/more intuitive in places, but some of the current behaviours are side effects of old design decisions which cannot simply be swapped out. Feel free to propose new/improved help texts :). -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
