zsh-users
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.stephenson@samsung.com>
To: Thomas Kupper <thomas.kupper@gmail.com>, zsh-users@zsh.org
Subject: Re: status of the cssh autocompletion
Date: Mon, 22 May 2017 16:06:47 +0100	[thread overview]
Message-ID: <20170522160647.4d11b008@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <CAJaHD+PP7mjszENY18=nk6=Wg1Hc=At7FJQikRTmFmvP5M+39A@mail.gmail.com>

On Mon, 22 May 2017 15:53:09 +0200
Thomas Kupper <thomas.kupper@gmail.com> wrote:
> I recently switched to zsh from bash and miss the more complete
> autocompletion for cssh. Even google didn't show any user which modified
> or extended the _cssh file.
> 
> Is there a specify reason for it? Do I miss the obvious?
> 
> Now I created an extend (but not yet finished) autocompletion. Is there an
> interest to include that into the upstream zsh? What would be the process.

There will almost certainly be no other reason than that nobody else has
produced an update yet.

For a few completions, the developers of the utility supply their own
versions of the completion function in their distribution, which allows
them to match the completion to the version of their firmware.  But this
is a rare case, and usually when that happens the more limited on in the
zsh distribution would be deleted.

For everything else --- simply send a patch to update the function(s) to
the zsh-workers@zsh.org list and we'll gladly add it to the distribution.

pws


  reply	other threads:[~2017-05-22 15:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20170522135423epcas2p33bbcf4954f30e2241b6cee17a9b65fae@epcas2p3.samsung.com>
2017-05-22 13:53 ` Thomas Kupper
2017-05-22 15:06   ` Peter Stephenson [this message]
2017-05-24 10:56     ` Thomas Kupper
2017-05-22 15:13   ` Bart Schaefer
2017-05-24 10:53     ` Thomas Kupper

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=20170522160647.4d11b008@pwslap01u.europe.root.pri \
    --to=p.stephenson@samsung.com \
    --cc=thomas.kupper@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).