zsh-workers
 help / color / mirror / code / Atom feed
From: Marko Myllynen <myllynen@redhat.com>
To: zsh-workers@zsh.org
Subject: Re: Zsh OpenStack completions
Date: Wed, 7 Sep 2016 10:12:35 +0300	[thread overview]
Message-ID: <544ddbce-b3aa-3a08-0470-79e3e563d405@redhat.com> (raw)
In-Reply-To: <d159d464-60e5-4e0f-aee5-0614c39d9788@gmx.com>

Hi,

On 2016-09-07 02:23, Eric Cook wrote:
> On 09/06/2016 08:39 AM, Marko Myllynen wrote:
>>
>> Below is a patch to add completions for several OpenStack related
>> command line clients, including the new common client, openstack(1).
> 
> Adding shell completion for openstack seems like something that is
> better fit committing to their respective project(s). Since it's a
> very active moving target I would imagine by the completer becoming
> dated fairly quickly. Committing it there would also (possibly) have
> more eyeballs that actually use openstack to help out too.

Yes, it is *very* fast moving target, that's why the implementation is
client/command agnostic - I'm unaware of any client ever switching from
the old style bash-completion command to the new style complete command
so that's the reason I think this should be relatively stable approach;
I'm sure nobody here wants to / can keep track of the each client
supported already (more perhaps to come). Dealing with over dozen
OpenStack projects to get completions included (and then later making
sure downstream packagers include them as well) also sounds like quite a
lot of work.

> _systemd would be the most recent example of this. We had a completer
> distributed with zsh. It wasn't kept up to date and people started to
> maintain completers in the systemd git repo. It actually caused
> confusion in #zsh for a few people when they noticed some commands wasn't
> showing all of the options expected on some systems and not others. Since
> two completers for systemd's utilities were in $fpath where as another
> OS decided to delete _systemd from zsh's source when packaging it.

I think _systemd completions are a good fit for systemd upstream (like
_pcp completions for PCP upstream which I contributed some time earlier
this year). However, given the fact that there's nothing OpenStack
client/command specific here except for the bash-completion vs complete
vs swift divide I think it would be feasible to have _openstack in zsh
upstream.

Thanks,

-- 
Marko Myllynen


  reply	other threads:[~2016-09-07  8:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-06 12:39 Marko Myllynen
2016-09-06 23:23 ` Eric Cook
2016-09-07  7:12   ` Marko Myllynen [this message]
2016-09-06 23:37 ` Daniel Shahaf
2016-09-07  9:31   ` Marko Myllynen
2016-09-09  6:38     ` Marko Myllynen
2016-09-19  6:24       ` Marko Myllynen
2016-09-27  5:43         ` Marko Myllynen

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=544ddbce-b3aa-3a08-0470-79e3e563d405@redhat.com \
    --to=myllynen@redhat.com \
    --cc=zsh-workers@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).