zsh-users
 help / color / mirror / code / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: completion within a function
Date: Sat, 2 Jan 2021 18:07:38 -0600	[thread overview]
Message-ID: <CAMP44s3NufsNkdC5qkcGuGz5D5oQhvAfnT2jS-5gCRtgtjG1+g@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7bZXGvVqeftVn4FnPd+G9Y5tm+YU6yV9wkgE1vXTEVLKw@mail.gmail.com>

On Fri, Jan 1, 2021 at 6:27 PM Bart Schaefer <schaefer@brasslantern.com> wrote:
>
> On Thu, Dec 31, 2020 at 1:25 PM Bart Schaefer <schaefer@brasslantern.com> wrote:
> >
> > On Wed, Dec 30, 2020 at 5:04 PM Felipe Contreras
> > <felipe.contreras@gmail.com> wrote:
> > >
> > > With that I do see the output. There's some garbage in it, but it works.
> >
> > I'm curious what the garbage is?  Maybe something needs redirection.
>
> Ahh ... because it's zpty, the cursor movements get captured along
> with everything else.

Yes, that's what happens.

> That's a bit of a monkey wrench unless all you want to do is display
> the result.  Hmm.

In my particular use-case I just need the list of completions in some
format. I use one per line because it's easier on my tests:

  test_completion "git checkout " <<-\EOF
  HEAD Z
  branch-in-other Z
  main Z
  main-in-other Z
  matching-branch Z
  matching-tag Z
  other/branch-in-other Z
  other/main-in-other Z
  EOF

That way I can test the zsh completion system of git-completion the
same way the git project tests the bash completion (I initially wrote
the tests for that too):

https://travis-ci.org/github/felipec/git-completion

-- 
Felipe Contreras


  parent reply	other threads:[~2021-01-03  0:08 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
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 [this message]
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=CAMP44s3NufsNkdC5qkcGuGz5D5oQhvAfnT2jS-5gCRtgtjG1+g@mail.gmail.com \
    --to=felipe.contreras@gmail.com \
    --cc=schaefer@brasslantern.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).