cli icon indicating copy to clipboard operation
cli copied to clipboard

A language for writing command line interfaces in Racket

Results 8 cli issues
Sort by recently updated
recently updated
newest added

Arguments received at the command line are always strings which usually need to be parsed into the appropriate types for use in the command line script. At the moment, every...

## Summary When using `cli` as the [module language for a `main` submodule](https://docs.racket-lang.org/cli/index.html#%28part._.In_a_main_submodule%29), defining a macro _within_ the submodule causes the following error (scroll to the bottom for a workaround):...

bug
help wanted

These are some examples of the syntax for flags at the moment: ``` (flag (verbose) ("-v" "--verbose" "Show detailed messages.") (verbose #t)) (flag (attempts n) ("-a" "--attempts" "Number of attempts...

enhancement

Ordinary Racket functions accept individually named arguments, but also packed "rest" arguments using the dot notation: ``` (define (func . args) body ...) ``` With `#lang cli`, we'd like to...

help wanted

At the moment, the `cli` forms make extensive use of unhygienic macros as well as mutation of module scope variables to track configuration changes. This is an artefact of the...

Given the following program --help generates help text that doesn't seem to support `--parameter=text` format, but `--parameter text` ```racket #lang cli (flag (file in-file-path) ("-f" "--file" "filepath") (file in-file-path)) (program...

At the moment, constraints validate some attributes of the input, e.g. that flags are provided a certain number of times, and so on. It would be nice to broaden the...

Defining commands in `#lang cli` has similar syntax to defining functions in Racket, and in fact, commands compile down to Racket functions. Since commands are just functions, it should be...