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

Parametrize lc_len_limit #129

Closed
ahojukka5 opened this issue Mar 9, 2024 · 1 comment · Fixed by #132
Closed

Parametrize lc_len_limit #129

ahojukka5 opened this issue Mar 9, 2024 · 1 comment · Fixed by #132

Comments

@ahojukka5
Copy link

https://github.com/carlobaldassi/ArgParse.jl/blob/master/src/parsing.jl#L140

lc_len_limit is hard coded to 24 which is not necessary enough if optional argument lengths are long enough (the result will not look good). It would be good to parametrize this so that it can be increased if needed.

@carlobaldassi
Copy link
Owner

That setting refers to the indentation of lines after the first in the "usage" output. Like this one:

usage: argparse_example3.jl [--opt1 [OPT1]] [-k] [--version] [-h]
                        arg1 arg1 [arg2...]

Here the arg1 ... part is indented by 24 spaces.

Is this what you were referring to? Or is it rather the overall width of the usage/help display (which is set to 70 at the moment)? I think making that customizable would be more useful.

carlobaldassi added a commit that referenced this issue May 6, 2024
Allow to control the auto-generated help text formatting

Fix #129
carlobaldassi added a commit that referenced this issue May 6, 2024
Allow to control the auto-generated help text formatting

Fix #129
carlobaldassi added a commit that referenced this issue May 6, 2024
Allow to control the auto-generated help text formatting

Fix #129
carlobaldassi added a commit that referenced this issue May 6, 2024
Allow to control the auto-generated help text formatting

Fix #129
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

Successfully merging a pull request may close this issue.

2 participants