command line options together don't work (-hv as opposed to -h -v) about termsaver HOT 6 CLOSED

How did you envision handling this? I have a branch where I'm playing with the idea now and there are multiple ways we could approach it.

Am I correct to assume this would only apply to arguments that were parameterless?

If so, what are the thoughts on modifying the programs core so we had to indicate if an argument needed parameters or not (the same way we indicate what their longname is?). This would allow parsing of each "type" of argument separately and grouping the parameterless arguments together might be easier.

from termsaver.

Yeah the issue now is that I send the parameters to the screen code so it can parse the individual options of each screen, that's why it is not using the standard getopt. Ideally, we would get everything in the 'termsaver' script (the one without .py), and pass the parsed arguments when instantiating the screen class...

from termsaver.

Worked out a solution. It'll take a day or so for me to implement fully. I think you'll like it.

from termsaver.

When you test this, make sure you look at bash_completion functionality as well (you hit TAB and it auto completes the screens or subsequent options)

from termsaver.

When you test this, make sure you look at bash_completion functionality as well (you hit TAB and it auto completes the screens or subsequent options)

Will do.

What are your thoughts on argparse? I've worked out a branch that implements it, however it required some major modifications to ScreenBase and some of the helper bases but it autogens usage for us and gives better control over specific options, handles '-h' on its own, etc.

I'd be happy to start a Draft PR if you're interested in seeing it.

from termsaver.

from termsaver.