| Anonymous | Login | 2026-03-11 17:57 CDT | ![]() |
| My View | View Issues |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
| 0000200 | Rosetta | [All Projects] Input Handling | public | 2013-03-07 08:39 | 2013-03-26 18:42 | ||||||||
| Reporter | momeara | ||||||||||||
| Assigned To | |||||||||||||
| Priority | normal | Severity | minor | Reproducibility | always | ||||||||
| Status | new | Resolution | open | ||||||||||
| Platform | All platforms | OS | Any | OS Version | Any | ||||||||
| Product Version | |||||||||||||
| Fixed in Version | |||||||||||||
| Summary | 0000200: When given a bad option on the command line print what is usually displayed with -help | ||||||||||||
| Description | When a bad option is given on the command line, currently it comes back with something like: ERROR: Option matching -scale_factor not found in command line top-level context caught exception ERROR: Option matching -scale_factor not found in command line top-level context Wouldn't it be nice it came back with that error and then (formated in fixed with font of course): Usage: ../../../bin/benchmark.postgres.linuxclangrelease [options] Options: [Specify on command line or in @file] Showing only relevant options... Option | Setting |Type| Description -------------------------------------------------------------------------------------- | | | run: | | | benchmark_scale | 1 | R| Amount to scale number of | | | cycles to repeate each | | | test run_one_benchmark | | S| Run just a single | | | performance benchmark benchmark_scale | 1 | R| Amount to scale number of | | | cycles to repeate each | | | test run_one_benchmark | | S| Run just a single | | | performance benchmark | | | in:path: | | | database | | (P)| Database file input search | | | paths. If the database is | | | not found the ROSETTA3_DB | | | environment variable is | | | tried. | ||||||||||||
| Tags | No tags attached. | ||||||||||||
| Application(s) Affected | all | ||||||||||||
| Command Line Used | benchmark.linuxclangrelease -asdflkajsdf | ||||||||||||
| Developer Options | Feature Request | ||||||||||||
| Fixed in SVN Version | |||||||||||||
| Attached Files | |||||||||||||
Relationships |
||||||||||||||||
|
||||||||||||||||
Notes |
|
|
(0000199) smlewis (Administrator) 2013-03-21 09:09 |
There are (at least) two types of bad options: A) Correct but insufficiently specific option (did you mean -packing:repack_only, or -somethingelse:repack_only?) B) Never-correct options (-this_option_does_not_exist) We only want to print help for B; for A it already prints a nice message requesting the user disambiguate their choice (and what the unambiguous choices are). |
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2013-03-07 08:39 | momeara | New Issue | |
| 2013-03-20 11:34 | smlewis | Relationship added | related to 0000168 |
| 2013-03-21 09:07 | smlewis | Relationship added | related to 0000221 |
| 2013-03-21 09:09 | smlewis | Note Added: 0000199 | |
| 2013-03-21 12:16 | smlewis | Relationship added | related to 0000226 |
| Copyright © 2000 - 2012 MantisBT Group |