On Fri, 2009-11-20 at 15:33 -0700, David Brownell wrote: > On Friday 20 November 2009, Zach Welch wrote: > > I have a new series based on this one that attacks command registration, > > adding a usage field. That said, how do you think the help text should > > be formatted and displayed? > > I'd expect "help" to give one line per command, > and "help <foo>" to give more. > > Though I'd have to see the details of your changes > in action.
It will take a little more work to get to what you want, but that's the general idea behind splitting up the usage and help. Usage will almost always fit onto one line and should skip justification or wrapping; the help text will be longer and may deserve both such treatments, but it should not try to replace the user guide either. Right? > > Personally, I am not averse to the new > > 'cmd_help' formatting that this introduces, and -- with the usage and > > help split -- the two commands will display much more sanely. > > > > Also, any reason to hold off on this present series or the USB series? > > These command patches, didn't see a reason. Okay, I've made a few trivial changes to them after working on the changes to support proper usage function, but I will try to push them along this afternoon. > The USB stuff is still in my look-at-this queue. For the most part, it's fairly straightforward refactoring, and any bugs should be easy to find by someone that has the given interface hardware. Nevertheless, I would appreciate your feedback, if you want to give it. Cheers, Zach _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
