argparse issues

program_name can be problematic

1

`program_name` is taken from the zeroth argument. If the program is called with a full (or partial) path, then this ends up in `program_name`, and then into the help text...

rowlesmr

Some improvements

1

I would like to suggest some improvements to the argparse project: - introduction of count limits for multi-value args - providing result collections for parse errors instead of writing to...

friefi

Support for wchar_t* strings.

Onnxruntime session requires const `wchar_t*` string as input and sometimes it has to be read from command line arguments. It would be nice if `argparse` could be used to directly...

chaihahaha

Alternative implementation for subparsers

2

Sorry this came late, but I recently (in Feb!) also made an implementation for subparsers, so I thought I'd share it still. It's at https://github.com/limwz01/argparse_mf/tree/with_subparsers with the commit https://github.com/limwz01/argparse_mf/commit/fccc2102e605d0c34f2d1ca2f8ed9c606c6694e4 ....

limwz01

Bugfix/Escape CSI sequences correctly

1

I could not use the library on my Linux machine until I escaped the CSI sequences correctly: `\e` -> `\\e` This PR should fix it for any unixoid system.

lightr4in

raise_on_error doesn't work as expected.

1

Hello, First, this is a nice library! very clean API. Some suggestions for improvement: 1. I would expect raise_on_error to throw when unrecognized argument is provided. (Similar to how python...

asaff1

Error: '<function-style-cast>': cannot convert from 'const std::string' to 'T'

2

```cpp struct MyArgs : public argparse::Args { size_t& test = kwarg("-t", "test"); }; ``` What's wrong with this? Why am I forced to use int or unsigned int instead of...

a2nath