I seem to recall that the parsing multiple options code is "wonky" because
it has to deal with a legacy "comma separated string". It may relate to
CLI-306
On Tue, May 28, 2024 at 6:16 PM Gary Gregory wrote:
> What about 'Hello World'?
>
> Gary
>
> On Tue, May 28, 2024, 11:13 AM Eric Pugh
> wro
What about 'Hello World'?
Gary
On Tue, May 28, 2024, 11:13 AM Eric Pugh
wrote:
> I may need to see if there is a unit test I can write, because on my Mac,
> ‘Hello World” get’s turned into “Hello” and “World” as well :-(.
>
>
>
>
>
> > On May 28, 2024, at 10:57 AM, Gary Gregory
> wrote:
> >
>
I may need to see if there is a unit test I can write, because on my Mac,
‘Hello World” get’s turned into “Hello” and “World” as well :-(.
> On May 28, 2024, at 10:57 AM, Gary Gregory wrote:
>
> It depends on the operating system as the OS itself might do different
> things with both single
It depends on the operating system as the OS itself might do different
things with both single-quotes and double-quotes.
For example, on Linux/macOS, single quotes create a string that is not
interpreted IIRC.
Gary
On Tue, May 28, 2024, 10:37 AM Eric Pugh
wrote:
> Hi all, trying to figure out
Hi all, trying to figure out if I found a bug or if it’s user error.
I have a command line:
bin/solr stream -verbose echo.expr "Hello World”
The -verbose is an option, and then the next two parameters I get via
System.out.print(cli.getArgList());.
I would expect to get two parameters: “echo.
