I am somewhat in favor of short options, if only because they allow
for less typing.
May I suggest that they be:
* -h (help)
* -s (is-command-substitution)
* -b (is-block)
* -i (is-interactive)
* -l (is-login)
* -f (current-filename)
* -n (current-line-number)
* -j (job-control)
* -t (print-stack-trace)
Opinions?
- Chris Rebert
On 8/1/07, Axel Liljencrantz <[EMAIL PROTECTED]> wrote:
> On 7/10/07, Chris Rebert <[EMAIL PROTECTED]> wrote:
> > After further testing, the same bug appears to be present in all of
> > status' single-letter switches.
>
> Only the 'h', 'j' and 't' short style switches work. It seems the
> documentation for 'status' is completely out of sync for the status
> command. Here are the long-style switches accepted, hopefully their
> meaning is self explanatory:
>
> {
> L"help", no_argument, 0, 'h'
> }
> ,
> {
> L"is-command-substitution", no_argument,
> &mode, IS_SUBST
> }
> ,
> {
> L"is-block", no_argument, &mode, IS_BLOCK
> }
> ,
> {
> L"is-interactive", no_argument, &mode,
> IS_INTERACTIVE
> }
> ,
> {
> L"is-login", no_argument, &mode, IS_LOGIN
> }
> ,
> {
> L"is-full-job-control", no_argument, &mode,
> IS_FULL_JOB_CONTROL
> }
> ,
> {
> L"is-interactive-job-control", no_argument,
> &mode,
> IS_INTERACTIVE_JOB_CONTROL
> }
> ,
> {
> L"is-no-job-control", no_argument, &mode,
> IS_NO_JOB_CONTROL
> }
> ,
> {
> L"current-filename", no_argument, &mode,
> CURRENT_FILENAME
> }
> ,
> {
> L"current-line-number", no_argument, &mode,
> CURRENT_LINE_NUMBER
> }
> ,
> {
> L"job-control", required_argument, 0, 'j'
> }
> ,
> {
> L"print-stack-trace", no_argument, 0, 't'
> }
> ,
> {
> 0, 0, 0, 0
> }
> }
>
> The main question, then, for me is do we want single letter switches
> for status? What should they be? Suggestions are welcome.
>
> Axel
>
> >
> > - Chris Rebert
> >
> > On 7/9/07, Tassilo Horn <[EMAIL PROTECTED]> wrote:
> > > Chris Rebert <[EMAIL PROTECTED]> writes:
> > >
> > > Hi Chris,
> > >
> > > > It appears that I've found a bug in the 'status' command. The -l
> > > > option doesn't work, contrary to the usage instructions.
> > >
> > > [snip]
> > >
> > > > Does anyone else get this behavior w/ fish version 1.22.3?
> > >
> > > Yes, and with a current darcs checkout, too.
> > >
> > > Bye,
> > > Tassilo
> > > --
> > > No person, no idea, and no religion deserves to be illegal to insult,
> > > not even the Church of Emacs. (Richard M. Stallman)
> > >
> > >
> > > -------------------------------------------------------------------------
> > > This SF.net email is sponsored by DB2 Express
> > > Download DB2 Express C - the FREE version of DB2 express and take
> > > control of your XML. No limits. Just data. Click to get it now.
> > > http://sourceforge.net/powerbar/db2/
> > > _______________________________________________
> > > Fish-users mailing list
> > > [email protected]
> > > https://lists.sourceforge.net/lists/listinfo/fish-users
> > >
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by DB2 Express
> > Download DB2 Express C - the FREE version of DB2 express and take
> > control of your XML. No limits. Just data. Click to get it now.
> > http://sourceforge.net/powerbar/db2/
> > _______________________________________________
> > Fish-users mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/fish-users
> >
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Fish-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fish-users