From: Peter Stephenson <p.stephenson@samsung.com>
To: Pier Paolo Grassi <pierpaolog@gmail.com>, zsh-users@zsh.org
Subject: Re: alias of completion
Date: Fri, 02 Mar 2018 10:51:03 +0000 [thread overview]
Message-ID: <20180302105103.679c7880@camnpupstephen.cam.scsc.local> (raw)
In-Reply-To: <CAP+y1xCmn1bDmajXY39N=TOgdRbjGLdGVMJrUPnpq_--6+3QFA@mail.gmail.com>
From: Peter Stephenson <p.stephenson@samsung.com>
To: Pier Paolo Grassi <pierpaolog@gmail.com>
Cc: zsh-users@zsh.org
Subject: Re: alias of completion
Date: Fri, 2 Mar 2018 10:47:34 +0000
X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.30; x86_64-pc-linux-gnu)
Organization: SCSC
On Fri, 2 Mar 2018 10:31:57 +0100
Pier Paolo Grassi <pierpaolog@gmail.com> wrote:
> One thing I was never been able to accomplish though, is: what if I
> want a custom function, say:
>
> mydockerwrapper(){}
>
> behave, for completion's sake, like, let's say:
>
> docker ls
>
> so that if I try to complete after
>
> mydockerwrapper <TAB>
>
> I get the same suggestion that I would get after docker ls, and if I
> have
>
> mydockerwrapper xx <TAB>
>
> I get the same completion that I would get after docker ls xx, and
> so on.
You need a bit of help from the completion function in
question to do this. The feature in question is "services": I just
looked at the docker completion and it does support this.
You'll need to do something like
compdef _docker mydockerwrapper=docker_service_complete_ls_filters
where the thing on the right of the "=" is an appropriate docker
completion function without the "_" (search for _$service for the code
in _docker supporting this).
pws
next prev parent reply other threads:[~2018-03-02 10:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180302093415epcas3p3d273c63fafad455cca7fec4072aeaea1@epcas3p3.samsung.com>
2018-03-02 9:31 ` Pier Paolo Grassi
2018-03-02 10:51 ` Peter Stephenson [this message]
2018-03-02 12:00 ` Pier Paolo Grassi
2018-03-02 12:08 ` m0viefreak
2018-03-02 12:15 ` Pier Paolo Grassi
2018-03-02 22:23 ` Joey Pabalinas
2018-03-03 6:41 ` Pier Paolo Grassi
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=20180302105103.679c7880@camnpupstephen.cam.scsc.local \
--to=p.stephenson@samsung.com \
--cc=pierpaolog@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).