Issue management

[lazysegtree]

@jarro2783, Could you add a label pending on author (example: S-waiting-on-author in rust) or something similar to these issues and PR?

Why? - This really helps potential contributors to filter non-actionable issues and non-reviewable PRs. Good labelling makes project management very easier. ( I use that extensively on this repo- ( https://github.com/yorukot/superfile/issues ) that I maintain)

Issues where pending on author label should be added, but should not be closed.

• options test fails with SIGTRAP on macOS / arm64 #431
• Filtered argc/argv #418

Issues that could be closed or pending on author label could be added. (upto you)

• Unexpected behavior when setting two std::vector values as positional arguments #457
• Feature request: value pairs or tuples #394

Issues that should be closed

• Path with spaces gets broken up at space #439
• feature request/question: support the one dash as argument #393
• Please improve explanation of positional arguments #371

PRs that are pending on author

• Multitoken options #444
• Support external definition of CXXOPTS_ENABLE_INSTALL option #437
• Format custom help message with configured column width #413

Additional suggestions related to project management

• We could have a label platform-specific for issues that are platform specific and not universal
• We could open Github's discussion tab so that this kind of discussion doesn't pollute issues.

[lazysegtree]

I only triaged a few recent issues. I will be traiging all of the open issues soon.

[jarro2783]

I've added the label. Thanks for helping.

[lazysegtree]

@jarro2783 I see that you have defined the label, but it's not applied to the issues that I have pointed out. Will you be doing that? For your information, I cannot do that as only people with Collaborator+ permissions can apply labels or close issues.

[jarro2783]

I thuoght that might be the case. I'll go through and label some of these.

[lazysegtree]

Request 2

@jarro2783 Issue/PR management requests. (Note: Some issues were in the first request too, but looks like you missed adding labels in that case)

Please add "Pending on Author" Label

• Filtered argc/argv #418

Either we can add "Pending on Author" Label , or close the issues

• Unexpected behavior when setting two std::vector values as positional arguments #457
• Feature request: value pairs or tuples #394
• Negative sign being treated as an optional argument in the case of positional arguments #254

Other Issues

A very specific feature ask. You can close the issue, or add won't do label, or just add enhancement label

• Add + as an argument indicator #425

PRs should be closed as author had said he cannot continue working on it. Or we should at least put "Pending on Author" Label (#412 doesn't have the label)

• Print long names in help option #412
• Format custom help message with configured column width #413

Other things require your input

Please let me know if you would accept this feature

• Sub-options support #430

[jarro2783]

Thanks for following up on these for me, I've closed some and labelled some.

[lazysegtree]

Request 3

@jarro2783 Issue/PR management requests.

Please add "Pending on Author" Label

• Filtered argc/argv #418 (This hasn't been labelled yet, despite earlier request, is there are something wrong in this issue?)

Either we can add "Pending on Author" Label , or close these issues

• Optional output file values #279
• Allow insertion of arbitrary top-level text before and after list of options in help text #278
• Conflicts between repeated arguments and vector arguments #262

Other things require your input

Please let me know if you are okay with these feature

• Options without arguments #297 (adding options to mandate the absence of value)
• Support for Windows command-line options #268 (let me know if you would like to add windows support. I feel its will be a lot of commitment, and we shouldn't, at this point )
• Allow disabling vector delimiter based parsing per option #489

Please review these PRs when you get some time.

• fix: Add ci test for options_no_regex, and fix inconsistency between regex pattern and customer parser #487

Optional issues/PRs where your input is useful

• fix: Fix short options parsing with equal sign #488 ( You can just add an initial review about changes and new tests, I will make it merge ready after the dependent PR is merged)
• Print long names in help option #412 Let me know if would like to do these changes on your own or I can put a PR for this.
• Format custom help message with configured column width #413 Let me know if would like to do these changes on your own or I can put a PR for this.
• How to not parse options after positional arguments #259 I don't understand the ask here. If you know what it is, let me know.

[jarro2783]

Sorry I missed 418 somehow. I think I looked at it 3 times and still missed adding the label.

I'll take a look at those PRs and issues at the bottom.

[lazysegtree]

Request 4

@jarro2783 Requests for project management

Please put pending on author on these.

• Negating booleans with short options #120
• Error when setting a long string as the default value #95

Please close these ( They are all fixed )

• Implicit values break value assignment without equals sign #441
• short arg unable to accept argument. #429
• segfault when using undefined options #185
• Operations out of range #106

Review PR ( I know you have already acknowledged. I just wanted to list it down here to for completeness of the request)

• feat: allow arbitrary char in opt name #491