Re: MixedCase or dashed-case for long options in Solr CLI?

2024-03-17 Thread Eric Pugh 
Thanks for chiming in.  

Yes, this would be 10 only change.   

Have you been able to try out the Windows scripts?   

> On Mar 17, 2024, at 3:05 PM, Shawn Heisey  wrote:
> 
> On 3/17/2024 13:01, Shawn Heisey wrote:
>> I like there to be a single character option and a kebab-case option. So -z 
>> and --zk-host.  Long options like find uses, such as -name, can be OK, but 
>> if you're going for standardization, I would just stick with the first two.
> 
> In cases where there might be a conflict for the single-character option, I 
> would opt to use the single character option for the one that is likely to be 
> more commonly used.  For others, I would choose another single character that 
> makes some kind of sense, or in some cases, simply opt to not have a single 
> character option.
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org
> For additional commands, e-mail: dev-h...@solr.apache.org
> 

___
Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467 | 
http://www.opensourceconnections.com  | 
My Free/Busy   
Co-Author: Apache Solr Enterprise Search Server, 3rd Ed 


This e-mail and all contents, including attachments, is considered to be 
Company Confidential unless explicitly stated otherwise, regardless of whether 
attachments are marked as such.

Re: MixedCase or dashed-case for long options in Solr CLI?

2024-03-17 Thread Shawn Heisey 

On 3/17/2024 13:01, Shawn Heisey wrote:
I like there to be a single character option and a kebab-case option. So 
-z and --zk-host.  Long options like find uses, such as -name, can be 
OK, but if you're going for standardization, I would just stick with the 
first two.


In cases where there might be a conflict for the single-character 
option, I would opt to use the single character option for the one that 
is likely to be more commonly used.  For others, I would choose another 
single character that makes some kind of sense, or in some cases, simply 
opt to not have a single character option.



-
To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org
For additional commands, e-mail: dev-h...@solr.apache.org

Re: MixedCase or dashed-case for long options in Solr CLI?

2024-03-17 Thread Shawn Heisey 

On 2/24/2024 09:34, Eric Pugh wrote:

I wanted to get the communities input on formatting of long options for the 
Solr CLI.   I noticed on https://commons.apache.org/proper/commons-cli/ that 
their examples all are —dashed-case.

However, we have —solrUrl or —zkHost as our pattern.   Though in working on the 
PostTool, I used —solr-update-url as the parameter because I had been reading 
the commons-cli docs...

I’d like to get this sorted so that I can get 
https://issues.apache.org/jira/browse/SOLR-16824 over the finish line.   So 
please do speak up with preferences!   (And please let’s not support both!)


I like there to be a single character option and a kebab-case option. 
So -z and --zk-host.  Long options like find uses, such as -name, can be 
OK, but if you're going for standardization, I would just stick with the 
first two.


Some will argue that this is the way gnu does things, not the way that 
the old unix gods did it.  I say this:  By using bash, we are already 
heavily in the gnu world, I see no reason to avoid going all the way in.


I imagine you're only considering this for version 10.  Breaking 
user-created scripts would be a bad thing to do in a minor release.


Thanks,
Shawn


-
To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org
For additional commands, e-mail: dev-h...@solr.apache.org

Re: MixedCase or dashed-case for long options in Solr CLI?

2024-03-04 Thread Eric Pugh 
-z and --zk-host works for me.


> On Mar 4, 2024, at 9:15 AM, Arrieta, Alejandro  
> wrote:
> 
> I prefer
> 
> —zk-host
> 
> Kind Regards,
> Alejandro Arrieta
> 
> On Mon, Mar 4, 2024 at 8:45 AM Eric Pugh  >
> wrote:
> 
>> “zkHost” —> “—zk-host” or “—zkhost” ?
>> 
>> 
>>> On Mar 4, 2024, at 6:34 AM, Eric Pugh 
>> wrote:
>>> 
>>> Kebab!  I love it.
>>> 
>>> 
 On Mar 3, 2024, at 1:14 PM, Arrieta, Alejandro <
>> aarri...@perrinsoftware.com> wrote:
 
 Hello,
 
 dashed-case is called kebab case almost everywhere. One example:
 https://www.theserverside.com/definition/Kebab-case
 I was looking at the meaning of dashed-case, and it always pointed to
 kebab-case.
 
 Having kebab, Kamel, and other cases helps troubleshoot over a
>> conference
 to see command errors faster or to tell where to insert other words.
 For scripts it does not matter imho.
 
 Yes, please go with Kebab case everything. Now you know the most common
 name it will never go away.
 
 Kind Regards,
 Alejandro Arrieta
 
 On Sun, Mar 3, 2024 at 2:10 PM Eric Pugh <
>> ep...@opensourceconnections.com  
>> >
 wrote:
 
> Thanks all for weighing in.   So I’m going to go for —dashed-case for
>> long
> options.   So expect some —solr-url and —zk-host parameters coming!
> 
> 
> 
>> On Feb 26, 2024, at 10:28 AM, Walter Underwood > 
>>> 
> wrote:
>> 
>> Long options are dashed-case, following the GNU convention. POSIX only
> specifies single character options. The “—“ prefix for long options is
>> a
> GNU invention, as far as I know. Older Unix commands with long option
> names, e.g. find, only use a single dash.
>> 
>> 
>> https://www.gnu.org/software/libc/manual/html_node/Argument-Syntax.html
>> 
>> https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap12.html
>> 
>> wunder
>> Walter Underwood
>> wun...@wunderwood.org  
>>  > wun...@wunderwood.org >
>> http://observer.wunderwood.org/  (my blog)
>> 
>>> On Feb 26, 2024, at 5:29 AM, Eric Pugh <
>> ep...@opensourceconnections.com  
>> 
> > wrote:
>>> 
>>> I hear a vote for dashed-case, how about some more votes?
> —solr-update-url versus —solrUpdateUrl ?
>>> 
>>> 
>>> 
 On Feb 26, 2024, at 7:29 AM, Jason Gerlowski >>> 
>> >
> wrote:
 
 My guess is that "dashed-case" is slightly more common -- at least,
 that's my sense from haphazardly checking a few tools I use often
 ("curl", "kubectl", "git", "docker").
 
 But I don't have an opinion as long as we're internally consistent
 about using one convention or the other.
 
 Best,
 
 Jason
 
 On Sat, Feb 24, 2024 at 11:35 AM Eric Pugh
 >>>  > ep...@opensourceconnections.com > 
>>  ep...@opensourceconnections.com  
> > ep...@opensourceconnections.com >> 
>>  wrote:
> 
> Hi all,
> 
> I wanted to get the communities input on formatting of long options
> for the Solr CLI.   I noticed on
> https://commons.apache.org/proper/commons-cli/ that their examples all
> are —dashed-case.
> 
> However, we have —solrUrl or —zkHost as our pattern.   Though in
> working on the PostTool, I used —solr-update-url as the parameter
>> because I
> had been reading the commons-cli docs...
> 
> I’d like to get this sorted so that I can get
> https://issues.apache.org/jira/browse/SOLR-16824 over the finish line.
> So please do speak up with preferences!   (And please let’s not support
> both!)
> 
> 
> The changes to the formatting will be a 10x thing.
> 
> Eric
> 
> ___
> Eric Pugh | Founder & CEO | OpenSource Connections, LLC |
> 434.466.1467 | http://www.opensourceconnections.com 
>  <
>> http://www.opensourceconnections.com/> <
> http://www.opensourceconnections.com/> <
> http://www.opensourceconnections.com/><
> http://www.opensourceconnections.com/> | My Free/Busy <
> http://tinyurl.com/eric-cal>
> Co-Author: Apache Solr Enterprise Search Server, 3rd Ed <
>

Re: MixedCase or dashed-case for long options in Solr CLI?

2024-03-04 Thread Arrieta, Alejandro 
I prefer

—zk-host

Kind Regards,
Alejandro Arrieta

On Mon, Mar 4, 2024 at 8:45 AM Eric Pugh 
wrote:

> “zkHost” —> “—zk-host” or “—zkhost” ?
>
>
> > On Mar 4, 2024, at 6:34 AM, Eric Pugh 
> wrote:
> >
> > Kebab!  I love it.
> >
> >
> >> On Mar 3, 2024, at 1:14 PM, Arrieta, Alejandro <
> aarri...@perrinsoftware.com> wrote:
> >>
> >> Hello,
> >>
> >> dashed-case is called kebab case almost everywhere. One example:
> >> https://www.theserverside.com/definition/Kebab-case
> >> I was looking at the meaning of dashed-case, and it always pointed to
> >> kebab-case.
> >>
> >> Having kebab, Kamel, and other cases helps troubleshoot over a
> conference
> >> to see command errors faster or to tell where to insert other words.
> >> For scripts it does not matter imho.
> >>
> >> Yes, please go with Kebab case everything. Now you know the most common
> >> name it will never go away.
> >>
> >> Kind Regards,
> >> Alejandro Arrieta
> >>
> >> On Sun, Mar 3, 2024 at 2:10 PM Eric Pugh <
> ep...@opensourceconnections.com >
> >> wrote:
> >>
> >>> Thanks all for weighing in.   So I’m going to go for —dashed-case for
> long
> >>> options.   So expect some —solr-url and —zk-host parameters coming!
> >>>
> >>>
> >>>
>  On Feb 26, 2024, at 10:28 AM, Walter Underwood  >
> >>> wrote:
> 
>  Long options are dashed-case, following the GNU convention. POSIX only
> >>> specifies single character options. The “—“ prefix for long options is
> a
> >>> GNU invention, as far as I know. Older Unix commands with long option
> >>> names, e.g. find, only use a single dash.
> 
> 
> https://www.gnu.org/software/libc/manual/html_node/Argument-Syntax.html
> 
> https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap12.html
> 
>  wunder
>  Walter Underwood
>  wun...@wunderwood.org   wun...@wunderwood.org>
>  http://observer.wunderwood.org/  (my blog)
> 
> > On Feb 26, 2024, at 5:29 AM, Eric Pugh <
> ep...@opensourceconnections.com 
> >>> > wrote:
> >
> > I hear a vote for dashed-case, how about some more votes?
> >>> —solr-update-url versus —solrUpdateUrl ?
> >
> >
> >
> >> On Feb 26, 2024, at 7:29 AM, Jason Gerlowski  >
> >>> wrote:
> >>
> >> My guess is that "dashed-case" is slightly more common -- at least,
> >> that's my sense from haphazardly checking a few tools I use often
> >> ("curl", "kubectl", "git", "docker").
> >>
> >> But I don't have an opinion as long as we're internally consistent
> >> about using one convention or the other.
> >>
> >> Best,
> >>
> >> Jason
> >>
> >> On Sat, Feb 24, 2024 at 11:35 AM Eric Pugh
> >>  ep...@opensourceconnections.com>  >>> ep...@opensourceconnections.com  ep...@opensourceconnections.com>>  >>
> >>> wrote:
> >>>
> >>> Hi all,
> >>>
> >>> I wanted to get the communities input on formatting of long options
> >>> for the Solr CLI.   I noticed on
> >>> https://commons.apache.org/proper/commons-cli/ that their examples all
> >>> are —dashed-case.
> >>>
> >>> However, we have —solrUrl or —zkHost as our pattern.   Though in
> >>> working on the PostTool, I used —solr-update-url as the parameter
> because I
> >>> had been reading the commons-cli docs...
> >>>
> >>> I’d like to get this sorted so that I can get
> >>> https://issues.apache.org/jira/browse/SOLR-16824 over the finish line.
> >>> So please do speak up with preferences!   (And please let’s not support
> >>> both!)
> >>>
> >>>
> >>> The changes to the formatting will be a 10x thing.
> >>>
> >>> Eric
> >>>
> >>> ___
> >>> Eric Pugh | Founder & CEO | OpenSource Connections, LLC |
> >>> 434.466.1467 | http://www.opensourceconnections.com <
> http://www.opensourceconnections.com/> <
> >>> http://www.opensourceconnections.com/> <
> >>> http://www.opensourceconnections.com/><
> >>> http://www.opensourceconnections.com/> | My Free/Busy <
> >>> http://tinyurl.com/eric-cal>
> >>> Co-Author: Apache Solr Enterprise Search Server, 3rd Ed <
> >>>
> https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw
> 
> >>> This e-mail and all contents, including attachments, is considered
> to
> >>> be Company Confidential unless explicitly stated otherwise, regardless
> of
> >>> whether attachments are marked as such.
> >>>
> >>
> >>
> -
> >> To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org  dev-unsubscr...@solr.apache.org>  >>> dev-unsubscr...@solr.apache.org  dev-unsubscr...@solr.apache.org>> 
> >> For additional commands, e-mail:

Re: MixedCase or dashed-case for long options in Solr CLI?

2024-03-04 Thread Eric Pugh 
“zkHost” —> “—zk-host” or “—zkhost” ?


> On Mar 4, 2024, at 6:34 AM, Eric Pugh  wrote:
> 
> Kebab!  I love it.
> 
> 
>> On Mar 3, 2024, at 1:14 PM, Arrieta, Alejandro  
>> wrote:
>> 
>> Hello,
>> 
>> dashed-case is called kebab case almost everywhere. One example:
>> https://www.theserverside.com/definition/Kebab-case
>> I was looking at the meaning of dashed-case, and it always pointed to
>> kebab-case.
>> 
>> Having kebab, Kamel, and other cases helps troubleshoot over a conference
>> to see command errors faster or to tell where to insert other words.
>> For scripts it does not matter imho.
>> 
>> Yes, please go with Kebab case everything. Now you know the most common
>> name it will never go away.
>> 
>> Kind Regards,
>> Alejandro Arrieta
>> 
>> On Sun, Mar 3, 2024 at 2:10 PM Eric Pugh > >
>> wrote:
>> 
>>> Thanks all for weighing in.   So I’m going to go for —dashed-case for long
>>> options.   So expect some —solr-url and —zk-host parameters coming!
>>> 
>>> 
>>> 
 On Feb 26, 2024, at 10:28 AM, Walter Underwood 
>>> wrote:
 
 Long options are dashed-case, following the GNU convention. POSIX only
>>> specifies single character options. The “—“ prefix for long options is a
>>> GNU invention, as far as I know. Older Unix commands with long option
>>> names, e.g. find, only use a single dash.
 
 https://www.gnu.org/software/libc/manual/html_node/Argument-Syntax.html
 https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap12.html
 
 wunder
 Walter Underwood
 wun...@wunderwood.org  
 
 http://observer.wunderwood.org/  (my blog)
 
> On Feb 26, 2024, at 5:29 AM, Eric Pugh  
>>> > wrote:
> 
> I hear a vote for dashed-case, how about some more votes?
>>> —solr-update-url versus —solrUpdateUrl ?
> 
> 
> 
>> On Feb 26, 2024, at 7:29 AM, Jason Gerlowski > >
>>> wrote:
>> 
>> My guess is that "dashed-case" is slightly more common -- at least,
>> that's my sense from haphazardly checking a few tools I use often
>> ("curl", "kubectl", "git", "docker").
>> 
>> But I don't have an opinion as long as we're internally consistent
>> about using one convention or the other.
>> 
>> Best,
>> 
>> Jason
>> 
>> On Sat, Feb 24, 2024 at 11:35 AM Eric Pugh
>> >  >> ep...@opensourceconnections.com > 
>>> >
>>> wrote:
>>> 
>>> Hi all,
>>> 
>>> I wanted to get the communities input on formatting of long options
>>> for the Solr CLI.   I noticed on
>>> https://commons.apache.org/proper/commons-cli/ that their examples all
>>> are —dashed-case.
>>> 
>>> However, we have —solrUrl or —zkHost as our pattern.   Though in
>>> working on the PostTool, I used —solr-update-url as the parameter because I
>>> had been reading the commons-cli docs...
>>> 
>>> I’d like to get this sorted so that I can get
>>> https://issues.apache.org/jira/browse/SOLR-16824 over the finish line.
>>> So please do speak up with preferences!   (And please let’s not support
>>> both!)
>>> 
>>> 
>>> The changes to the formatting will be a 10x thing.
>>> 
>>> Eric
>>> 
>>> ___
>>> Eric Pugh | Founder & CEO | OpenSource Connections, LLC |
>>> 434.466.1467 | http://www.opensourceconnections.com 
>>>  <
>>> http://www.opensourceconnections.com/> <
>>> http://www.opensourceconnections.com/><
>>> http://www.opensourceconnections.com/> | My Free/Busy <
>>> http://tinyurl.com/eric-cal>
>>> Co-Author: Apache Solr Enterprise Search Server, 3rd Ed <
>>> https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw
 
>>> This e-mail and all contents, including attachments, is considered to
>>> be Company Confidential unless explicitly stated otherwise, regardless of
>>> whether attachments are marked as such.
>>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org 
>>  >> dev-unsubscr...@solr.apache.org > 
>>> 
>> For additional commands, e-mail: dev-h...@solr.apache.org 
>>  >> dev-h...@solr.apache.org > 
>>> 
> ___
> Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467
>>> | http://www.opensourceconnections.com 
>>>

Re: MixedCase or dashed-case for long options in Solr CLI?

2024-03-04 Thread Eric Pugh 
Kebab!  I love it.


> On Mar 3, 2024, at 1:14 PM, Arrieta, Alejandro  
> wrote:
> 
> Hello,
> 
> dashed-case is called kebab case almost everywhere. One example:
> https://www.theserverside.com/definition/Kebab-case
> I was looking at the meaning of dashed-case, and it always pointed to
> kebab-case.
> 
> Having kebab, Kamel, and other cases helps troubleshoot over a conference
> to see command errors faster or to tell where to insert other words.
> For scripts it does not matter imho.
> 
> Yes, please go with Kebab case everything. Now you know the most common
> name it will never go away.
> 
> Kind Regards,
> Alejandro Arrieta
> 
> On Sun, Mar 3, 2024 at 2:10 PM Eric Pugh  >
> wrote:
> 
>> Thanks all for weighing in.   So I’m going to go for —dashed-case for long
>> options.   So expect some —solr-url and —zk-host parameters coming!
>> 
>> 
>> 
>>> On Feb 26, 2024, at 10:28 AM, Walter Underwood 
>> wrote:
>>> 
>>> Long options are dashed-case, following the GNU convention. POSIX only
>> specifies single character options. The “—“ prefix for long options is a
>> GNU invention, as far as I know. Older Unix commands with long option
>> names, e.g. find, only use a single dash.
>>> 
>>> https://www.gnu.org/software/libc/manual/html_node/Argument-Syntax.html
>>> https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap12.html
>>> 
>>> wunder
>>> Walter Underwood
>>> wun...@wunderwood.org  
>>> 
>>> http://observer.wunderwood.org/  (my blog)
>>> 
 On Feb 26, 2024, at 5:29 AM, Eric Pugh >>> 
>> > wrote:
 
 I hear a vote for dashed-case, how about some more votes?
>> —solr-update-url versus —solrUpdateUrl ?
 
 
 
> On Feb 26, 2024, at 7:29 AM, Jason Gerlowski  >
>> wrote:
> 
> My guess is that "dashed-case" is slightly more common -- at least,
> that's my sense from haphazardly checking a few tools I use often
> ("curl", "kubectl", "git", "docker").
> 
> But I don't have an opinion as long as we're internally consistent
> about using one convention or the other.
> 
> Best,
> 
> Jason
> 
> On Sat, Feb 24, 2024 at 11:35 AM Eric Pugh
> mailto:ep...@opensourceconnections.com> 
> > ep...@opensourceconnections.com > 
>> >
>> wrote:
>> 
>> Hi all,
>> 
>> I wanted to get the communities input on formatting of long options
>> for the Solr CLI.   I noticed on
>> https://commons.apache.org/proper/commons-cli/ that their examples all
>> are —dashed-case.
>> 
>> However, we have —solrUrl or —zkHost as our pattern.   Though in
>> working on the PostTool, I used —solr-update-url as the parameter because I
>> had been reading the commons-cli docs...
>> 
>> I’d like to get this sorted so that I can get
>> https://issues.apache.org/jira/browse/SOLR-16824 over the finish line.
>> So please do speak up with preferences!   (And please let’s not support
>> both!)
>> 
>> 
>> The changes to the formatting will be a 10x thing.
>> 
>> Eric
>> 
>> ___
>> Eric Pugh | Founder & CEO | OpenSource Connections, LLC |
>> 434.466.1467 | http://www.opensourceconnections.com 
>>  <
>> http://www.opensourceconnections.com/> <
>> http://www.opensourceconnections.com/><
>> http://www.opensourceconnections.com/> | My Free/Busy <
>> http://tinyurl.com/eric-cal>
>> Co-Author: Apache Solr Enterprise Search Server, 3rd Ed <
>> https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw
>>> 
>> This e-mail and all contents, including attachments, is considered to
>> be Company Confidential unless explicitly stated otherwise, regardless of
>> whether attachments are marked as such.
>> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org 
>  > dev-unsubscr...@solr.apache.org > 
>> 
> For additional commands, e-mail: dev-h...@solr.apache.org 
>  > dev-h...@solr.apache.org > 
>> 
 ___
 Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467
>> | http://www.opensourceconnections.com 
>>  <
>> http://www.opensourceconnections.com/> <
>> http://www.opensourceconnections.com/> | My Free/Busy <
>> http://tinyurl.com/eric-cal>
 Co-Author: Apache Solr Enterprise Search Server, 3rd Ed <
>>

Re: MixedCase or dashed-case for long options in Solr CLI?

2024-03-03 Thread Arrieta, Alejandro 
 Hello,

dashed-case is called kebab case almost everywhere. One example:
https://www.theserverside.com/definition/Kebab-case
I was looking at the meaning of dashed-case, and it always pointed to
kebab-case.

Having kebab, Kamel, and other cases helps troubleshoot over a conference
to see command errors faster or to tell where to insert other words.
For scripts it does not matter imho.

Yes, please go with Kebab case everything. Now you know the most common
name it will never go away.

Kind Regards,
Alejandro Arrieta

On Sun, Mar 3, 2024 at 2:10 PM Eric Pugh 
wrote:

> Thanks all for weighing in.   So I’m going to go for —dashed-case for long
> options.   So expect some —solr-url and —zk-host parameters coming!
>
>
>
> > On Feb 26, 2024, at 10:28 AM, Walter Underwood 
> wrote:
> >
> > Long options are dashed-case, following the GNU convention. POSIX only
> specifies single character options. The “—“ prefix for long options is a
> GNU invention, as far as I know. Older Unix commands with long option
> names, e.g. find, only use a single dash.
> >
> > https://www.gnu.org/software/libc/manual/html_node/Argument-Syntax.html
> > https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap12.html
> >
> > wunder
> > Walter Underwood
> > wun...@wunderwood.org 
> > http://observer.wunderwood.org/  (my blog)
> >
> >> On Feb 26, 2024, at 5:29 AM, Eric Pugh  > wrote:
> >>
> >> I hear a vote for dashed-case, how about some more votes?
>  —solr-update-url versus —solrUpdateUrl ?
> >>
> >>
> >>
> >>> On Feb 26, 2024, at 7:29 AM, Jason Gerlowski 
> wrote:
> >>>
> >>> My guess is that "dashed-case" is slightly more common -- at least,
> >>> that's my sense from haphazardly checking a few tools I use often
> >>> ("curl", "kubectl", "git", "docker").
> >>>
> >>> But I don't have an opinion as long as we're internally consistent
> >>> about using one convention or the other.
> >>>
> >>> Best,
> >>>
> >>> Jason
> >>>
> >>> On Sat, Feb 24, 2024 at 11:35 AM Eric Pugh
> >>>  ep...@opensourceconnections.com> >
> wrote:
> 
>  Hi all,
> 
>  I wanted to get the communities input on formatting of long options
> for the Solr CLI.   I noticed on
> https://commons.apache.org/proper/commons-cli/ that their examples all
> are —dashed-case.
> 
>  However, we have —solrUrl or —zkHost as our pattern.   Though in
> working on the PostTool, I used —solr-update-url as the parameter because I
> had been reading the commons-cli docs...
> 
>  I’d like to get this sorted so that I can get
> https://issues.apache.org/jira/browse/SOLR-16824 over the finish line.
>  So please do speak up with preferences!   (And please let’s not support
> both!)
> 
> 
>  The changes to the formatting will be a 10x thing.
> 
>  Eric
> 
>  ___
>  Eric Pugh | Founder & CEO | OpenSource Connections, LLC |
> 434.466.1467 | http://www.opensourceconnections.com <
> http://www.opensourceconnections.com/> <
> http://www.opensourceconnections.com/><
> http://www.opensourceconnections.com/> | My Free/Busy <
> http://tinyurl.com/eric-cal>
>  Co-Author: Apache Solr Enterprise Search Server, 3rd Ed <
> https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw
> >
>  This e-mail and all contents, including attachments, is considered to
> be Company Confidential unless explicitly stated otherwise, regardless of
> whether attachments are marked as such.
> 
> >>>
> >>> -
> >>> To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org  dev-unsubscr...@solr.apache.org> 
> >>> For additional commands, e-mail: dev-h...@solr.apache.org  dev-h...@solr.apache.org> 
> >> ___
> >> Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467
> | http://www.opensourceconnections.com <
> http://www.opensourceconnections.com/> <
> http://www.opensourceconnections.com/> | My Free/Busy <
> http://tinyurl.com/eric-cal>
> >> Co-Author: Apache Solr Enterprise Search Server, 3rd Ed <
> https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw>
>
> >> This e-mail and all contents, including attachments, is considered to
> be Company Confidential unless explicitly stated otherwise, regardless of
> whether attachments are marked as such.
>
> ___
> Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467 |
> http://www.opensourceconnections.com <
> http://www.opensourceconnections.com/> | My Free/Busy <
> http://tinyurl.com/eric-cal>
> Co-Author: Apache Solr Enterprise Search Server, 3rd Ed <
>

Re: MixedCase or dashed-case for long options in Solr CLI?

2024-03-03 Thread Eric Pugh 
Thanks all for weighing in.   So I’m going to go for —dashed-case for long 
options.   So expect some —solr-url and —zk-host parameters coming!



> On Feb 26, 2024, at 10:28 AM, Walter Underwood  wrote:
> 
> Long options are dashed-case, following the GNU convention. POSIX only 
> specifies single character options. The “—“ prefix for long options is a GNU 
> invention, as far as I know. Older Unix commands with long option names, e.g. 
> find, only use a single dash.
> 
> https://www.gnu.org/software/libc/manual/html_node/Argument-Syntax.html
> https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap12.html
> 
> wunder
> Walter Underwood
> wun...@wunderwood.org 
> http://observer.wunderwood.org/  (my blog)
> 
>> On Feb 26, 2024, at 5:29 AM, Eric Pugh > > wrote:
>> 
>> I hear a vote for dashed-case, how about some more votes?   —solr-update-url 
>> versus —solrUpdateUrl ?
>> 
>> 
>> 
>>> On Feb 26, 2024, at 7:29 AM, Jason Gerlowski  wrote:
>>> 
>>> My guess is that "dashed-case" is slightly more common -- at least,
>>> that's my sense from haphazardly checking a few tools I use often
>>> ("curl", "kubectl", "git", "docker").
>>> 
>>> But I don't have an opinion as long as we're internally consistent
>>> about using one convention or the other.
>>> 
>>> Best,
>>> 
>>> Jason
>>> 
>>> On Sat, Feb 24, 2024 at 11:35 AM Eric Pugh
>>> mailto:ep...@opensourceconnections.com> 
>>> > wrote:
 
 Hi all,
 
 I wanted to get the communities input on formatting of long options for 
 the Solr CLI.   I noticed on 
 https://commons.apache.org/proper/commons-cli/ that their examples all are 
 —dashed-case.
 
 However, we have —solrUrl or —zkHost as our pattern.   Though in working 
 on the PostTool, I used —solr-update-url as the parameter because I had 
 been reading the commons-cli docs...
 
 I’d like to get this sorted so that I can get 
 https://issues.apache.org/jira/browse/SOLR-16824 over the finish line.   
 So please do speak up with preferences!   (And please let’s not support 
 both!)
 
 
 The changes to the formatting will be a 10x thing.
 
 Eric
 
 ___
 Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467 | 
 http://www.opensourceconnections.com 
  
 
  | My Free/Busy 
 Co-Author: Apache Solr Enterprise Search Server, 3rd Ed 
 
 This e-mail and all contents, including attachments, is considered to be 
 Company Confidential unless explicitly stated otherwise, regardless of 
 whether attachments are marked as such.
 
>>> 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org 
>>>  
>>> 
>>> For additional commands, e-mail: dev-h...@solr.apache.org 
>>>  
>> ___
>> Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467 | 
>> http://www.opensourceconnections.com  
>>  | My Free/Busy 
>>   
>> Co-Author: Apache Solr Enterprise Search Server, 3rd Ed 
>> 
>>  
>> This e-mail and all contents, including attachments, is considered to be 
>> Company Confidential unless explicitly stated otherwise, regardless of 
>> whether attachments are marked as such.

___
Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467 | 
http://www.opensourceconnections.com  | 
My Free/Busy   
Co-Author: Apache Solr Enterprise Search Server, 3rd Ed 


This e-mail and all contents, including attachments, is considered to be 
Company Confidential unless explicitly stated otherwise, regardless of whether 
attachments are marked as such.

Re: MixedCase or dashed-case for long options in Solr CLI?

2024-02-26 Thread Walter Underwood 
Long options are dashed-case, following the GNU convention. POSIX only 
specifies single character options. The “—“ prefix for long options is a GNU 
invention, as far as I know. Older Unix commands with long option names, e.g. 
find, only use a single dash.

https://www.gnu.org/software/libc/manual/html_node/Argument-Syntax.html
https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap12.html

wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/  (my blog)

> On Feb 26, 2024, at 5:29 AM, Eric Pugh  
> wrote:
> 
> I hear a vote for dashed-case, how about some more votes?   —solr-update-url 
> versus —solrUpdateUrl ?
> 
> 
> 
>> On Feb 26, 2024, at 7:29 AM, Jason Gerlowski  wrote:
>> 
>> My guess is that "dashed-case" is slightly more common -- at least,
>> that's my sense from haphazardly checking a few tools I use often
>> ("curl", "kubectl", "git", "docker").
>> 
>> But I don't have an opinion as long as we're internally consistent
>> about using one convention or the other.
>> 
>> Best,
>> 
>> Jason
>> 
>> On Sat, Feb 24, 2024 at 11:35 AM Eric Pugh
>> mailto:ep...@opensourceconnections.com>> 
>> wrote:
>>> 
>>> Hi all,
>>> 
>>> I wanted to get the communities input on formatting of long options for the 
>>> Solr CLI.   I noticed on https://commons.apache.org/proper/commons-cli/ 
>>> that their examples all are —dashed-case.
>>> 
>>> However, we have —solrUrl or —zkHost as our pattern.   Though in working on 
>>> the PostTool, I used —solr-update-url as the parameter because I had been 
>>> reading the commons-cli docs...
>>> 
>>> I’d like to get this sorted so that I can get 
>>> https://issues.apache.org/jira/browse/SOLR-16824 over the finish line.   So 
>>> please do speak up with preferences!   (And please let’s not support both!)
>>> 
>>> 
>>> The changes to the formatting will be a 10x thing.
>>> 
>>> Eric
>>> 
>>> ___
>>> Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467 | 
>>> http://www.opensourceconnections.com 
>>> 
>>>  | My Free/Busy 
>>> Co-Author: Apache Solr Enterprise Search Server, 3rd Ed 
>>> 
>>> This e-mail and all contents, including attachments, is considered to be 
>>> Company Confidential unless explicitly stated otherwise, regardless of 
>>> whether attachments are marked as such.
>>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org 
>> 
>> For additional commands, e-mail: dev-h...@solr.apache.org 
>> 
> ___
> Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467 | 
> http://www.opensourceconnections.com  
> | My Free/Busy   
> Co-Author: Apache Solr Enterprise Search Server, 3rd Ed 
> 
>   
> This e-mail and all contents, including attachments, is considered to be 
> Company Confidential unless explicitly stated otherwise, regardless of 
> whether attachments are marked as such.
>

Re: MixedCase or dashed-case for long options in Solr CLI?

2024-02-26 Thread Eric Pugh 
I hear a vote for dashed-case, how about some more votes?   —solr-update-url 
versus —solrUpdateUrl ?



> On Feb 26, 2024, at 7:29 AM, Jason Gerlowski  wrote:
> 
> My guess is that "dashed-case" is slightly more common -- at least,
> that's my sense from haphazardly checking a few tools I use often
> ("curl", "kubectl", "git", "docker").
> 
> But I don't have an opinion as long as we're internally consistent
> about using one convention or the other.
> 
> Best,
> 
> Jason
> 
> On Sat, Feb 24, 2024 at 11:35 AM Eric Pugh
> mailto:ep...@opensourceconnections.com>> 
> wrote:
>> 
>> Hi all,
>> 
>> I wanted to get the communities input on formatting of long options for the 
>> Solr CLI.   I noticed on https://commons.apache.org/proper/commons-cli/ that 
>> their examples all are —dashed-case.
>> 
>> However, we have —solrUrl or —zkHost as our pattern.   Though in working on 
>> the PostTool, I used —solr-update-url as the parameter because I had been 
>> reading the commons-cli docs...
>> 
>> I’d like to get this sorted so that I can get 
>> https://issues.apache.org/jira/browse/SOLR-16824 over the finish line.   So 
>> please do speak up with preferences!   (And please let’s not support both!)
>> 
>> 
>> The changes to the formatting will be a 10x thing.
>> 
>> Eric
>> 
>> ___
>> Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467 | 
>> http://www.opensourceconnections.com 
>> 
>>  | My Free/Busy 
>> Co-Author: Apache Solr Enterprise Search Server, 3rd Ed 
>> 
>> This e-mail and all contents, including attachments, is considered to be 
>> Company Confidential unless explicitly stated otherwise, regardless of 
>> whether attachments are marked as such.
>> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org 
> 
> For additional commands, e-mail: dev-h...@solr.apache.org 
> 
___
Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467 | 
http://www.opensourceconnections.com  | 
My Free/Busy   
Co-Author: Apache Solr Enterprise Search Server, 3rd Ed 


This e-mail and all contents, including attachments, is considered to be 
Company Confidential unless explicitly stated otherwise, regardless of whether 
attachments are marked as such.

Re: MixedCase or dashed-case for long options in Solr CLI?

2024-02-26 Thread Jason Gerlowski 
My guess is that "dashed-case" is slightly more common -- at least,
that's my sense from haphazardly checking a few tools I use often
("curl", "kubectl", "git", "docker").

But I don't have an opinion as long as we're internally consistent
about using one convention or the other.

Best,

Jason

On Sat, Feb 24, 2024 at 11:35 AM Eric Pugh
 wrote:
>
> Hi all,
>
> I wanted to get the communities input on formatting of long options for the 
> Solr CLI.   I noticed on https://commons.apache.org/proper/commons-cli/ that 
> their examples all are —dashed-case.
>
> However, we have —solrUrl or —zkHost as our pattern.   Though in working on 
> the PostTool, I used —solr-update-url as the parameter because I had been 
> reading the commons-cli docs...
>
> I’d like to get this sorted so that I can get 
> https://issues.apache.org/jira/browse/SOLR-16824 over the finish line.   So 
> please do speak up with preferences!   (And please let’s not support both!)
>
>
> The changes to the formatting will be a 10x thing.
>
> Eric
>
> ___
> Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467 | 
> http://www.opensourceconnections.com  
> | My Free/Busy 
> Co-Author: Apache Solr Enterprise Search Server, 3rd Ed 
> 
> This e-mail and all contents, including attachments, is considered to be 
> Company Confidential unless explicitly stated otherwise, regardless of 
> whether attachments are marked as such.
>

-
To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org
For additional commands, e-mail: dev-h...@solr.apache.org

MixedCase or dashed-case for long options in Solr CLI?

2024-02-24 Thread Eric Pugh 
Hi all,

I wanted to get the communities input on formatting of long options for the 
Solr CLI.   I noticed on https://commons.apache.org/proper/commons-cli/ that 
their examples all are —dashed-case.

However, we have —solrUrl or —zkHost as our pattern.   Though in working on the 
PostTool, I used —solr-update-url as the parameter because I had been reading 
the commons-cli docs...

I’d like to get this sorted so that I can get 
https://issues.apache.org/jira/browse/SOLR-16824 over the finish line.   So 
please do speak up with preferences!   (And please let’s not support both!)


The changes to the formatting will be a 10x thing.

Eric

___
Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467 | 
http://www.opensourceconnections.com  | 
My Free/Busy   
Co-Author: Apache Solr Enterprise Search Server, 3rd Ed 


This e-mail and all contents, including attachments, is considered to be 
Company Confidential unless explicitly stated otherwise, regardless of whether 
attachments are marked as such.