Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unique short name #41

Open
GregorySchwartz opened this issue Sep 1, 2017 · 1 comment
Open

Unique short name #41

GregorySchwartz opened this issue Sep 1, 2017 · 1 comment

Comments

@GregorySchwartz
Copy link

The auto generation of the short names is fantastic, but it would be nice to have it automatically detect used names and choose the next best thing. So if two options are "--cheese" and "--cherries", it would be "-c" and "-C" respectively, or if that is taken, "-d", etc.

@Gabriella439
Copy link
Owner

One of the goals of the optparse-generic library is that the user should be able to easily predict what command line options the Haskell type will correspond to. Implementing this makes it harder to reason about that translation process

I also think at this level of customization I would recommend using the underlying optparse-applicative library

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants