From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: completion
Date: Thu, 08 Jan 2015 08:52:12 -0800 [thread overview]
Message-ID: <54AEB5BC.4060503@eastlink.ca> (raw)
In-Reply-To: <150108003124.ZM8010@torch.brasslantern.com>
On 01/08/2015 12:31 AM, Bart Schaefer wrote:
> On Jan 7, 3:00pm, Ray Andrews wrote:
> }
> } To put it in English, what I'm reaching for (I think), sounds something
> } like this:
> }
> } If [something-on-command-line] matches [this-pattern] (a filter), then
> } expand that pattern using [this-particular-set-of-rules], and then
> } search (go find) in [this-particular-group-of-objects] for
> } [this-particular-glob-pattern] and put that on my command line.
>
> Incidentally, no, it's not like that at all. In fact its so far from
> that, that I can't even reword the above to give a better sense of it.
> Completion involves several layers of loops-within-loops, it can't be
> described in a single if-then sentence.
Well that's hardly a surprise to hear, because the square peg of what
my preconception is/was definitely does not go through the round hole
of what happens. You know, I was going to give completion a rest and
try again in a year, but since Vincent brought the subject up again, and
there's new food to digest, I'd better reread the docs again in the light
of this new explanation and maybe I will get it. At the moment, my mind
just melts down at the 'asterisk' part, I just can't grok ambiguously
omitted field separators, it ain't humanly decent.
>
> If you ignore a lot of the looping parts and the listing of ambiguous
> matches, then it's sort of like:
>
> Choose a completer and pass it some information about the command line,
> from which it will construct a context which summarizes the meaning of
> the command line in about six words. For each/any configuration option
> that may be useful, use the context to find the best definition among
> the set of zstyle patterns the user has defined. Some of those options
> (called styles) should explain where to look for [this-particular-group-
> of-strings], otherwise use a fallback to find them. Compare whatever
> strings you end up with to the word to the left of or under the cursor
> and put the longest unambiguous common substring that matches on the
> command line, assuming the other styles said that's what you should do.
> If there aren't any matches at all, try again with the next completer
> until something is found or there are no more completers.
I'm lost after 'choose a completer' ;-) ... what does that mean? I expect
that zsh *provides* me with the completer ....
Nevermind! I've got to reread. For now, I'm interested to see how you
respond to Vincent, he already mostly understands this. I don't
understand enough to be even worth talking to.
next prev parent reply other threads:[~2015-01-08 16:52 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 23:15 completion Ray Andrews
2014-12-10 23:31 ` completion Lawrence Velázquez
2014-12-11 0:34 ` completion Oliver Kiddle
2014-12-11 1:17 ` completion Ray Andrews
2014-12-11 5:44 ` completion Bart Schaefer
2014-12-11 16:40 ` completion Ray Andrews
2014-12-11 17:28 ` completion Bart Schaefer
2014-12-11 19:34 ` completion Ray Andrews
2015-01-07 15:01 ` completion Vincent Lefevre
2015-01-07 15:28 ` completion Peter Stephenson
2015-01-07 16:58 ` completion Mikael Magnusson
2015-01-07 17:06 ` completion Peter Stephenson
2015-01-07 18:33 ` completion Ray Andrews
[not found] ` <CAH+w=7Z_B2ghc21QgHxA8FEV7W8uQnjEwtPqK3tL-kjPihjicA@mail.gmail.com>
2015-01-07 19:54 ` completion Bart Schaefer
2015-01-07 18:48 ` completion Bart Schaefer
2015-01-07 19:24 ` completion Ray Andrews
2015-01-07 19:33 ` completion Lawrence Velázquez
2015-01-07 20:06 ` completion Ray Andrews
2015-01-07 19:51 ` completion Bart Schaefer
2015-01-07 20:15 ` completion Ray Andrews
2015-01-07 20:42 ` completion Bart Schaefer
2015-01-07 23:00 ` completion Ray Andrews
2015-01-08 5:09 ` completion Bart Schaefer
2015-01-08 8:31 ` completion Bart Schaefer
2015-01-08 16:52 ` Ray Andrews [this message]
2015-01-08 0:43 ` completion Vincent Lefevre
2015-01-08 0:57 ` completion ZyX
2015-01-08 1:15 ` completion Vincent Lefevre
2015-01-08 6:03 ` completion Bart Schaefer
2015-01-08 5:26 ` completion Bart Schaefer
2015-01-08 12:36 ` completion Vincent Lefevre
2015-01-10 2:12 ` completion Bart Schaefer
2015-01-12 9:09 ` completion Vincent Lefevre
2015-01-12 16:43 ` completion Bart Schaefer
2015-01-13 16:03 ` completion Vincent Lefevre
2015-01-14 2:56 ` completion Bart Schaefer
2015-01-08 17:12 ` completion Ray Andrews
2015-01-09 9:37 ` completion Vincent Lefevre
2015-01-10 5:33 ` completion Bart Schaefer
-- strict thread matches above, loose matches on Subject: below --
2012-12-03 17:44 completion Ray Andrews
2012-12-03 18:31 ` completion Ray Andrews
2007-05-15 15:27 Completion Anonymous bin ich
2007-05-15 16:23 ` Completion Peter Stephenson
2006-02-20 12:54 Completion Etienne Chové
2006-02-20 18:51 ` Completion Clint Adams
2006-02-20 19:47 ` Completion Etienne Chové
2003-12-22 23:15 Completion Seth Kurtzberg
2000-02-22 14:58 Completion Sven Wischnowsky
2000-02-22 14:47 Completion Sven Wischnowsky
2000-02-22 15:01 ` Completion Andy Spiegl
2000-02-22 11:36 Completion Sven Wischnowsky
2000-02-22 14:24 ` Completion Andy Spiegl
2000-02-22 18:01 ` Completion Bart Schaefer
2000-02-15 8:42 Completion Claus Alboege
2000-02-21 22:20 ` Completion Bart Schaefer
2000-02-22 10:37 ` Completion Andy Spiegl
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=54AEB5BC.4060503@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=zsh-users@zsh.org \
/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).