Remko Popma

The [built-in exit codes](https://picocli.info/#_exception_exit_codes) are as follows: By default, the `execute` method returns `CommandLine.ExitCode.OK` (0) on success, `CommandLine.ExitCode.SOFTWARE` (1) when an exception occurred in the Runnable, Callable or command method,...

Can you provide a test (maybe like what I did above) to demonstrate the 666 vs 154 issue you mention? Quotes in the annotations won’t compile (int value only). And...

@elyograg were you able to reproduce the 666 vs 154 issue you mentioned? Could you provide a program to reproduce it?

Good point! Java can return any int value as exit code, but the OS or shell may truncate it to a single byte…

One idea is to construct and return a new `CommandLine` instance from `getCommand` instead of caching the `CommandLine` instance. Another idea is to define the array option such that it...

Thanks for looking into this! I’ll try to take a closer look when I’m back from traveling. > On Nov 5, 2022, at 16:45, marinier ***@***.***> wrote: > > ...

Indeed, this has been on the todo list for a long time. See #485. Some error messages are dynamically constructed but it should be possible to capture all patterns in...

> I'm not sure what you mean by _"should be possible to capture all patterns in MessageFormat"._ For example, there is some of the current picocli code, showing a method...

I see, interesting! I only anticipated `@Command`-annotated methods that were subcommands of a `@Command`-annotated class, I did not anticipate your use case. 😅 Note that this is not limited to...

@rsenden Apologies for the late reply, this dropped below my inbox horizon... About alternative approaches, one idea is to have a MIXEE spec in every Mixin: ```java public class MyCommand...