zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: completion within a function
Date: Sat, 2 Jan 2021 16:53:51 -0800	[thread overview]
Message-ID: <CAH+w=7ZTxt+XjXxi-xC2MbDL8E5w-G-WEC2NMZAAD39JaJvdEA@mail.gmail.com> (raw)
In-Reply-To: <CAMP44s1zOR_zCOYMi_eWGH6ygsm05CC1WNMtMFxZD_qZxejM7g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 954 bytes --]

On Sat, Jan 2, 2021 at 4:28 PM Felipe Contreras <felipe.contreras@gmail.com>
wrote:

>
> I'm trying it like this:
>
>   ZDOTDIR=/tmp/empty-home zsh /tmp/complete-bart 'git --'
>

Don't pass a single, quoted argument; quote each word separately if needed.

ZDOTDIR=/tmp/empty-home zsh /tmp/complete-bart git --

The symptom I experienced is that the command never ends,
> apparently because the end marker never arrives.
>

I ran into this a couple of times myself.  It seems to have something to do
with the definition of "whole string":

     If a PATTERN is given as well, output is read until the whole
     string read matches the PATTERN, even in the non-blocking case.

If there's anything after the end marker, the "whole string" may not
match.  I had to try several different variations to find one that gave
consistent results.

At a guess, you might try:

zle_complete () {
zle list-choices
BUFFER='print -n "<END-CHOICES>"'
zle .accept-line
}

[-- Attachment #2: Type: text/html, Size: 1784 bytes --]

  reply	other threads:[~2021-01-03  0:54 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-29 15:24 Ray Andrews
2020-12-29 18:52 ` Bart Schaefer
2020-12-29 19:36   ` Felipe Contreras
2020-12-29 19:41     ` Roman Perepelitsa
2020-12-29 21:04   ` Ray Andrews
2020-12-29 21:21     ` Ray Andrews
2020-12-29 22:03       ` Bart Schaefer
2020-12-29 21:48     ` Bart Schaefer
2020-12-30  0:31       ` Ray Andrews
2020-12-30  4:34         ` Roman Perepelitsa
2020-12-30 16:45           ` Ray Andrews
2020-12-30 17:21             ` Felipe Contreras
2020-12-30 20:43               ` Bart Schaefer
2020-12-30 20:46                 ` Bart Schaefer
2020-12-30 20:50                 ` Ray Andrews
2020-12-30 21:31                 ` Roman Perepelitsa
2020-12-30 22:05                   ` Bart Schaefer
2020-12-30 22:18                 ` Felipe Contreras
2020-12-30 23:47                   ` Bart Schaefer
2020-12-31  0:08                     ` Bart Schaefer
2020-12-31  0:12                     ` Felipe Contreras
2020-12-31  0:30                       ` Bart Schaefer
2020-12-31  0:39                         ` Bart Schaefer
2020-12-31  1:04                           ` Felipe Contreras
2020-12-31 21:25                             ` Bart Schaefer
2021-01-01  0:12                               ` Ray Andrews
2021-01-02  0:27                               ` Bart Schaefer
2021-01-02 22:24                                 ` Bart Schaefer
2021-01-03  0:28                                   ` Felipe Contreras
2021-01-03  0:53                                     ` Bart Schaefer [this message]
2021-01-03  1:20                                       ` Felipe Contreras
2021-01-03  2:21                                         ` Bart Schaefer
2021-01-03  2:47                                           ` Felipe Contreras
2021-01-03  3:30                                             ` Bart Schaefer
2021-01-03 23:16                                               ` Felipe Contreras
2021-01-05 19:57                                                 ` Bart Schaefer
2021-01-03 17:50                                             ` Bart Schaefer
2021-01-03  0:07                                 ` Felipe Contreras
2020-12-31  1:03                         ` Felipe Contreras
2020-12-30  6:45         ` 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='CAH+w=7ZTxt+XjXxi-xC2MbDL8E5w-G-WEC2NMZAAD39JaJvdEA@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=felipe.contreras@gmail.com \
    --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).