zsh-workers
 help / color / mirror / code / Atom feed
From: Felix Rosencrantz <f_rosencrantz@yahoo.com>
To: zsh-workers <zsh-workers@sunsite.auc.dk>
Subject: Re: New options & arguments processing system for ZSH
Date: Sun, 19 Aug 2001 23:53:51 -0700 (PDT)	[thread overview]
Message-ID: <20010820065351.70088.qmail@web10406.mail.yahoo.com> (raw)

I think parse_opts is very interesting.  To me, it's exciting since it
attempts to use the same specifications for command line parsing as
it does for completion.  I think whatever format we use for command
descriptions, the format should be able to help the shell understand the
command line from many different angles (e.g. completion, command line
correction, validation, prediction, generation).  I think this is the
first specifications that attempts to cover the issues of the command
line from multiple sides, which a data format can do.

I think this format is complimentary to the XML stuff with which I've
been playing.  I think it would be possible to generate the parse_opts
call from the XML format.  Also, since parse_opts has additional type
and frequency information that could be added to the XML format, to aid
parse_opts generation.

One thing I noticed when trying to complete options to the supplied
"yes" function, was that it didn't provide much help for the options.
It provided type information, but it didn't actually tell me what the
options did.  The format does provide a mechanism to do that.  Though
it seems like that it requires duplicating information that is already
there in the help text.  So it seems if it was somehow possible to reuse
the help text already there that might be useful.

This format also gives the developer a bit of control over where&how
option information is placed variables.  It would be nice if _arguments
had richer control over that.  Though this extra control seems like it
is more for command line parsing that for completion.

-FR.


__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/


             reply	other threads:[~2001-08-20  6:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-20  6:53 Felix Rosencrantz [this message]
2001-08-20  7:06 ` Borsenkow Andrej
  -- strict thread matches above, loose matches on Subject: below --
2001-08-21 14:07 martin.ebourne
2001-08-24  6:13 ` Felix Rosencrantz
2001-08-20 11:17 martin.ebourne
2001-08-20 10:42 martin.ebourne
2001-08-21 13:50 ` Felix Rosencrantz
     [not found] <OF653C664E.8AB47B26-ON80256AAB.004AC761@uk.jpmorgan.com>
2001-08-19  5:40 ` Bart Schaefer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010820065351.70088.qmail@web10406.mail.yahoo.com \
    --to=f_rosencrantz@yahoo.com \
    --cc=zsh-workers@sunsite.auc.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).