Jakarta Commons Developers List" <[EMAIL PROTECTED]>
Sent: Tuesday, July 01, 2003 1:46 PM
Subject: Re: [CLI] Do we have the correct model? (was Re: [CLI] Support for CVS style
command line)
> Sounds like a good plan to me.
>
> Rob
>
> - Original Message -
> F
Firstly, it may well be unimportant for now as it is really an
> > implementation detail of my experimental code - there may be other
> > stratergies for processing.
> >
> > The idea is that each option will return the set of string prefixes
> > that this option ca
- Original Message -
From: "John Keyes" <[EMAIL PROTECTED]>
To: "Jakarta Commons Developers List" <[EMAIL PROTECTED]>
Sent: Wednesday, June 18, 2003 10:21 PM
Subject: Re: [CLI] Do we have the correct model? (was Re: [CLI] Support for CVS style
command l
ile.
Rob
----- Original Message -----
From: "John Keyes" <[EMAIL PROTECTED]>
To: "Jakarta Commons Developers List" <[EMAIL PROTECTED]>
Sent: Thursday, June 12, 2003 10:18 AM
Subject: Re: [CLI] Support for CVS style command line
> > The "setDisplayCommandA
> The "setDisplayCommandAlias(boolean)" is purely hypothetical at the moment, it
> illustrates
> the level of control I was planning on offering but is beyond the implementation so
> far.
> I haven't tackled Commands and aliases at all but I guess should put my code
> where my mouth is. I'll
- Original Message -
From: "John Keyes" <[EMAIL PROTECTED]>
To: "Jakarta Commons Developers List" <[EMAIL PROTECTED]>
Cc: "Jakarta Commons Developers List" <[EMAIL PROTECTED]>
Sent: Wednesday, June 11, 2003 1:56 PM
Subject: Re: [CLI] Sup
>Eitherway the implementation should be a simple case of setting a few attributes on
>the HelpFormatter and supplying an alternate
>Options object:
>
>if(commandLine.hasOption("--help-commands")){
>// don't descend into suboptions
>helpFormatter.setDepth(0);
>// make s
- Original Message -
From: "John Keyes" <[EMAIL PROTECTED]>
To: "Jakarta Commons Developers List" <[EMAIL PROTECTED]>
Sent: Wednesday, June 11, 2003 12:24 AM
Subject: Re: [CLI] Support for CVS style command line
...
> >
> >
o do this
and that the position of the global options shouldn't matter but
others may disagree.
I agree with you that its a mistake, but I will spend some time
thinking about
it to see if it is possible to come up with a solution.
Thanks for all that information. I will post whatever I come
The CVS command line is defined as follows:
cvs [options] command [command-options]
Ideally I would like to have CLI support this implicity, i.e.
validate the 'command' value (this was a feature already
recommended by Mike McLean and modified by Max Rydahl Andersen)
and based on this value pars
The CVS command line is defined as follows:
cvs [options] command [command-options]
Ideally I would like to have CLI support this implicity, i.e.
validate the 'command' value (this was a feature already
recommended by Mike McLean and modified by Max Rydahl Andersen)
and based on this value pars
ter
the "checkout" for instance. Do either
proposals allow this? (I don't think mine would). Do we want to support this?
Personally I think it was a mistake of CVS to do this
and that the position of the global options shouldn't matter but others may disagree.
Rob
- Or
The CVS command line is defined as follows:
cvs [options] command [command-options]
Ideally I would like to have CLI support this implicity, i.e.
validate the 'command' value (this was a feature already
recommended by Mike McLean and modified by Max Rydahl Andersen)
and based on this value pars
13 matches
Mail list logo
