From: Peter Stephenson <pws@pwstephenson.fsnet.co.uk>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Remainder of compsys.yo
Date: Thu, 24 Apr 2003 17:53:24 +0100 [thread overview]
Message-ID: <20030424165329.423C61B76A@pwstephenson.fsnet.co.uk> (raw)
I've finished rewriting compsys.yo from _description onwards; as before,
it's a lot of large scale changes and the diffs aren't very helpful
(about 1000 lines), so I've simply committed it (old version 1.166, new
version 1.168 since I spotted a typo).
The _regex_arguments entry was unfortunately too difficult to fathom
entirely. I have rewritten it to omit mention of state machines, which
is unnecessary implementation detail; all the user sees is a pattern
syntax with no visibility of states beyond the notion of the current
pattern.
However, I've come a cropper at this bit:
COMMENT(I think I've got this wrong, but I can't think what else it
could mean. Actually, it still doesn't mean very much.)\
A special procedure is applied if no test succeeds but the remaining
command line string contains no null character (implying the remaining
word is the one for which completions are to be generated). The
completion target is restricted to the remaining word and any
var(action)s for the corresponding patterns are executed. In this case,
nothing is stripped from the command line string. The order of
evaluation of the var(action)s can be determined by the tt(tag-order)
style; the various formats supported by tt(_alternative) can be used
in var(action). The var(descr) is used for setting up the array
parameter tt(expl).
which used to be further down (inside the syntax for the first pattern,
although it applied to the syntax as a whole) and say this:
If no test succeeds and the remaining command line string contains no null
character, the completion target is restricted to the remainder of the
command line string and var(action)s for the target are executed.
In this case, nothing is actually removed from the command line string
so that any previous or neighbouring state may also have var(actions)s.
var(actions)s evaluation are ordered by the tt(tag-order) style and specified
var(tag) by tt(_alternative). So, the various formats supported by
tt(_alternative) can be used in var(action). var(descr) is used for
setting up the array parameter tt(expl).
If anybody can shed further light on it, please do. In particular, I
don't understand which actions are being executed if no test succeeds.
I'm also not sure whether the reference to _alternative and tag-order
apply more widely than this particular case (i.e. whether there should
really be a paragraph break in the old text after the fifth line).
--
Peter Stephenson <pws@pwstephenson.fsnet.co.uk>
Work: pws@csr.com
Web: http://www.pwstephenson.fsnet.co.uk
next reply other threads:[~2003-04-24 17:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-24 16:53 Peter Stephenson [this message]
2003-04-25 11:02 ` Oliver Kiddle
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=20030424165329.423C61B76A@pwstephenson.fsnet.co.uk \
--to=pws@pwstephenson.fsnet.co.uk \
--cc=zsh-workers@sunsite.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).