zsh-workers
 help / color / mirror / code / Atom feed
From: martin.ebourne@arcordia.com
To: Felix Rosencrantz <f_rosencrantz@yahoo.com>
Cc: zsh-workers@sunsite.auc.dk
Subject: Re: New options & arguments processing system for ZSH
Date: Tue, 21 Aug 2001 15:07:33 +0100	[thread overview]
Message-ID: <OFABD9EBE5.11B3DC92-ON80256AAF.004CEAA8@uk.jpmorgan.com> (raw)



> prompt% yes2 -<TAB>
> ---- option
> --escape      -e  -- __Interpret escape characters as for echo (default
unless
> --help        -h  -- __Provide help
> --lines       -l  -- __Output only count times
> --no-escape   -E  -- __Prevent interpretation of escape characters
> --no-newline  -n  -- __Suppress output of automatic newline
> --sleep       -s  -- __Pause for number of seconds between each echo
>
> The way I read your mail, though, is that the yes2 output should be
coming
> from the original "yes" script.  So there might be a problem somewhere,
> or I just didn't understand you.

Aha! Yes, it should do exactly that. I think I know what the problem is as
well. parse_opts detects the difference between the options and the help
text because the latter follows tab characters, and the former is before
any tab characters. The documentation is correct about this, but I wouldn't
expect you to have read all that anyway.

However, I should say that the ever wonderful Lotus *#?! Notes program here
has carefully converted my tabs to spaces and totally stuffed it up. So if
you could put 'yes' into emacs and M-x tabify with the whole thing
selected, or something else similar, it should start working properly.
Sorry about that - just more ammo for my personal vendetta against the
worst email program in the universe.

> If you use a state action, _arguments puts information in the opt_args
> associative array.  I think it could be useful if there was a little
> more control how parsed values are stored like provided by parse_opts.

Ah, ok. I haven't used the state machine facilities yet, but I can see how
that might be handy.

Cheers,

Martin.



             reply	other threads:[~2001-08-21 14:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-21 14:07 martin.ebourne [this message]
2001-08-24  6:13 ` Felix Rosencrantz
  -- strict thread matches above, loose matches on Subject: below --
2001-08-20 11:17 martin.ebourne
2001-08-20 10:42 martin.ebourne
2001-08-21 13:50 ` Felix Rosencrantz
2001-08-20  6:53 Felix Rosencrantz
2001-08-20  7:06 ` Borsenkow Andrej
     [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=OFABD9EBE5.11B3DC92-ON80256AAF.004CEAA8@uk.jpmorgan.com \
    --to=martin.ebourne@arcordia.com \
    --cc=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).