From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26003 invoked by alias); 24 May 2017 10:53:21 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 22712 Received: (qmail 3241 invoked from network); 24 May 2017 10:53:21 -0000 X-Qmail-Scanner-Diagnostics: from mail-vk0-f47.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(209.85.213.47):SA:0(-2.8/5.0):. Processed in 1.27589 secs); 24 May 2017 10:53:21 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.8 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_PASS,T_DKIM_INVALID autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: thomas.kupper@gmail.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.213.47 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=5bqbNHVrYqihA9dJ2J4z/bT+p1eDVS9qyd3zLhzH5zk=; b=RttYFgtzlJV9fuse0i4fr7ZHD0K3aODB6PFj4OVyM+hO2PpgFARXcKGV7+7nsa7V+B i3wii74t06uM8YDCP0XWhWA+67knfsTgxiJ7R5mySxPb6gHxSZBRUo7jtk4YcxBO+BFw yM/MxbkuKStZRcNec2pJx4vj5i7w+Wb9HJMxL0rQMELs6TdpCIzlrMPZc5vOAyUaN+27 woG3RkZtrCsVWxAGy0kokjDhdhqWMdAvtjS106/SE0zv1ERVnihXy59i9Ks7IBGCDpq4 MFONnLFEsy3c2w2Li6qQ1rnj85bKDUgKGBv3GQkSTPTJIKgSE8+h/pqnN1LUlMrJFwaz nGjg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=5bqbNHVrYqihA9dJ2J4z/bT+p1eDVS9qyd3zLhzH5zk=; b=JDCSG2n8teVYGosZLMcg4yMrMwr0bhVDre/L2PR2X6X8C9eW8wZwb2dwXt7zt0UrN9 c+pyVj1nuNu+3Lm005uxdLEFn910uptKlgv8NylwotD5jyojxhkfqy+bhztUZTmdgR5y n21nbom9+vrzPIW81B+SJUKgfYRx//R9olHkFX9R5sTJeYbFpsuMhTGI27BVA87vs5AI 5bEDpsVJwdseSJx2ikGmJcYDP8A0aYdoilKhBNsQsxbN9vOlv1ykfSwpe6bHDdvUJxHW jhObMVTKGDCrBiLzmCofYTWEVX5BqL2ri67k2PlNb/jNoIuY4NgbFpwGBusJt7wzekcj 1Row== X-Gm-Message-State: AODbwcDqV4P8bTzJpg4j2jP2gzaW1roZtCdSZMrzQYhfmMcBF1CLzDmn os7AOTnrebtqVe1+vHNiIqWYTdlVYw== X-Received: by 10.31.99.67 with SMTP id x64mr13634134vkb.24.1495623193596; Wed, 24 May 2017 03:53:13 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <170522081324.ZM7724@torch.brasslantern.com> References: <170522081324.ZM7724@torch.brasslantern.com> From: Thomas Kupper Date: Wed, 24 May 2017 12:53:13 +0200 Message-ID: Subject: Re: status of the cssh autocompletion To: Bart Schaefer Cc: zsh-users@zsh.org Content-Type: multipart/alternative; boundary="94eb2c07b1182c193b055042e9a8" --94eb2c07b1182c193b055042e9a8 Content-Type: text/plain; charset="UTF-8" On Mon, May 22, 2017 at 5:13 PM, Bart Schaefer wrote: > On May 22, 3:53pm, Thomas Kupper wrote: > } > } I recently switched to zsh from bash and miss the more complete > } autocompletion for cssh. > > I haven't explicitly tried using _bash_completions for cssh, but I don't > know of any reason it wouldn't work. > > } Is there a specify reason for it? Do I miss the obvious? > > My own usage of cssh is pretty regimented -- I essentially never need to > complete anything, because I'm always running one of the same 3 or 4 > commands that are already in my history. I don't think there's anything > obvious other than lack of need/interest. > > } 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. > > Send it to zsh-workers@zsh.org and we will review and most likely add it > to the distribution. > Thanx Bart, I haven't tried to use the bash completions for _cssh. I'll give it a go. But will work on the extension of the current _cssh ZSH completion anyway and will send it to workers@zsh Have a good day --94eb2c07b1182c193b055042e9a8--