> 1. "./runltp -h" will scroll up and will not show on a single > screen, > 2. It will be difficult for users to remember all options and their > usage as no. of options increase manifold, which is already too > much.
Well many applications do that, and something that cannot be avoided, you could spend some time and remove least useful options if you want to trim the output a little. I think your other option is to use /etc/bash_completion and create a CLI for runltp. something like this: ./runltp option option option=value for example: ./runltp <tab-tab> prints something like: ./runltp verbose prettyprint iostress ...<more options>... logfile=<enter filename> ./runltp ver<tab-tab> expands to ./runltp verbose ./runltp verbose lo<tab-tab> expands to ./runltp verbose logfile= and the user enters the filename. etc. I think you get the drift. So the user can build the command line on the fly and dont have to hit -h then remember options etc. You could also write the entire CLI in perl which I think offers more flexibility to do command complition & CLI. You can then parse those options & arguments do construct your command line for runltp. > to hear from you on how it can be done best. I would like to see just > the following command execute LTP as desired by the user: > > ./runltp > > And the remaining choice of providing more options to 'runltp' hidden > somewhere. have you polled to see what options consumers of LTP are using? my guess is they are just running with the options that the help command prints at the end. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
