zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Marlon Richert <marlon.richert@gmail.com>
Cc: Oliver Kiddle <opk@zsh.org>, Zsh Users <zsh-users@zsh.org>
Subject: Re: Questions about completion matchers
Date: Sat, 9 Oct 2021 09:23:42 -0700	[thread overview]
Message-ID: <CAH+w=7ZpxduSrwZ101JoRJfEkE_xAnNfd_Lo6BUkaQmuxsiu5A@mail.gmail.com> (raw)
In-Reply-To: <CAHLkEDv=+A7BXF6nKADNJDnd-zLW5baZ8xU3erp28it+jAKNrg@mail.gmail.com>

On Fri, Oct 8, 2021 at 3:39 PM Marlon Richert <marlon.richert@gmail.com> wrote:
>
> The way I've understood it, is that, if $word contains the command line string for which completion is attempted, then each matcher should transform $word as follows:
>
> What did I miss?

I think what you've missed is that there are two things being
examined:  The word on the command line, and the "trial completion",
that is, the word passed to compadd that might replace the one on the
command line.  It's not merely (choosing the first of your seeming
duplications)

> *              b:$lpat=$tpat -> ${word/#$~lpat/$~tpat}
> *             l:|$lpat=$tpat -> ${word/#$~lpat/$~tpat}

Rather it's

*              b:$lpat=$tpat -> [[ $trial = ${~lpat}* ]] &&
${word/#$~lpat/$~tpat}
*             l:|$lpat=$tpat -> [[ $trial = *${~lpat}* ]] &&
${word/#$~lpat/$~tpat}

In the cases with r: and R:, $ranchor is only compared to $trial, it
is not used when replacing into $word.


  reply	other threads:[~2021-10-09 16:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-21  9:23 Marlon Richert
2021-09-22 23:25 ` Bart Schaefer
2021-09-26 13:09 ` Oliver Kiddle
2021-10-08 22:38   ` Marlon Richert
2021-10-09 16:23     ` Bart Schaefer [this message]
2021-10-09 22:12       ` Marlon Richert
2021-10-09 22:39         ` Bart Schaefer
2021-10-10 11:17           ` Marlon Richert
2021-10-09 21:59     ` Oliver Kiddle
2021-10-10 12:05       ` Marlon Richert
2021-10-10 20:14         ` Marlon Richert

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='CAH+w=7ZpxduSrwZ101JoRJfEkE_xAnNfd_Lo6BUkaQmuxsiu5A@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=marlon.richert@gmail.com \
    --cc=opk@zsh.org \
    --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).