cmdargs
cmdargs copied to clipboard
Haskell library for command line argument processing
From http://code.google.com/p/ndmitchell/issues/detail?id=444: Often programs need command line aliases, for example in HLint --utf8 == --encoding=UTF8, and for Hoogle --all == --count=1000000. These should be supported properly, for example, I could...
From http://code.google.com/p/ndmitchell/issues/detail?id=524 In the Explicit module I should at least say what a mode/flag/argument are, currently mode is entirely undefined.
Originally from http://code.google.com/p/ndmitchell/issues/detail?id=540: `darcs --help` prints out: ``` Use 'darcs COMMAND --help' for help on a single command. ``` CmdArgs should do something similar, explaining how to find the additional...
The cmdargs-browser mode should switch to js-jquery. I should also write a blog post about it, since I don't think anyone knows it exists.
Attempting to run the following minimal example given in the documentation for `enum`: ``` haskell {-#LANGUAGE DeriveDataTypeable#-} import System.Console.CmdArgs data State = On | Off deriving (Data, Show) data Mode...
I tested `cmdargs-0.10.12`. ``` data Foo = Foo { arg :: Bool } deriving (Show, Data, Typeable) foo :: Foo foo = Foo { arg = False &= help "arg...
System.Console.CmdArgs.Explicit.helpText: required arguments are rendered as optional and vice versa
The help text rendering (System.Console.CmdArgs.Explicit.helpText) renders required arguments as optional (with square brackets) and optional arguments as required (without square brackets). ### Example ``` Haskell module CmdArgsExplicit where import System.Console.CmdArgs.Explicit...
Hi, When I compile a modal application with optimizations on (such as is done by default with cabal), the command line parsing doesn't work as expected. Here's a small example...
Currently they don't tie down the type of the annotation, but it would be good if they did.
Sometimes it is useful for one field to be controlled by two flags, for example `--encoding=ENC` or `--utf8` as an alias for `--encoding=utf8`. I should support that somehow.