-
We need to be able to accept command line args or a config file. Should we use the program options method used in the WindNinja CLI? This will require boost. Is that okay?
-
The command line arguments structure for crust should look like the following:
```
crust [config_opts, ...] [command_opts, ...] ...
[config_opts] := --
[command_opts] := --
# command_opts …
-
# related:
- [x] xxx
- [x] xxx
-
allow toggling the option to run tests and populate the database
-
since qt does not provide a command line parser, we should find one that fits our needs:
- http://gitorious.org/qcommandline
- http://gitorious.org/qcommandline ([documentation](http://xf.iksaif.net/d…
aoloe updated
10 years ago
-
Man page mentions non-existent option `-p/--parser`.
Would be nice to turn parser on/off from command-line instead of config file.
-
- Allen's tool is a command line utility
- add as an integrated parser for 1.0 release?
It will get plenty of use for the ARC01 cruise.
-
```
Add option parser for icereader.py to make it available from command-line. This
would be a shortcut alternative to the ICE Explorer app for
converting/exporting icecache files to ascii.
e.g.
# …
-
### Describe the bug
Updating an existing data collection rule is not working.
```sh
az monitor data-collection rule update --resource-group my-rg --name my-dcr --stream-declarations "columns[{lo…
-
[Realm's command-line parser](https://gitlab.com/StanfordLegion/legion/-/blob/master/runtime/realm/cmdline.h#L30) provides no way for clients to know which of the flags actually present in the command…