From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10879 invoked by alias); 22 May 2017 13:53:15 -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: 22708 Received: (qmail 15665 invoked from network); 22 May 2017 13:53:15 -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.3/5.0):. Processed in 0.706038 secs); 22 May 2017 13:53:15 -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.3 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,RCVD_IN_SORBS_SPAM,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:from:date:message-id:subject:to; bh=50YgLqPI6qP9O5e8MUvg17c395LSltV7gXA4k+GGyLc=; b=Ki3iWuWJGIpX/8UlrIlVfwz8aImWURdIwUDFjNy+XeOaXldH0QDDG72W3nbMFkC64j Q4phNAmfKUH96WsUq1PUfiH7RN+NeOPNDMOAMxMmkTWSvYcVb//o5rdBFO4yuoTrASyz ONen90uU8LC3CIpbYxjJn5EAbUDKPcHsJLS3ragZa5xL/l6gvpGOKeHIuSApd3aowwJS SDsMhUbxgtaEXuu94gp5xdEkCtgrGgUi79CbkCpMpDYQNsTIYBDe2n5QsvmAJ12QJpPJ 1C7tcdNon3JNxQ3pLRZ3sfOVkykXbiVPxv7kazfzUHSsYuyQr8jnXQ4kMJiUws3CqBqE qg/g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=50YgLqPI6qP9O5e8MUvg17c395LSltV7gXA4k+GGyLc=; b=NkjEqw27+RNbfqpwzKxzzAyP7cbKp9zlVeQQvjNEkMoVcPzRp1g9D63l3vReJTcVd3 DYdYOMg3KhKjw/TZKuKsILQleAlyU9XSdrLYX4vGyZ6/16pKkHD4hQCq41CSMh6HLdip 3QTDX4Ue14515TY2Wf1wg4vuqxNc4J1A+FRd3UjhlCbm5WDmrfKl1C+Zz6/uBY/m0O0b a5uy6MYMvx1c+Cs2AoKVTeIV+gSySn18v7LAupfv+fVxslgzudr/lso4Ewc6a5g2Lxi7 8h5jbU1F1D4V+CXhTXkeKp1L4jprdtXD/NGKZ6Uc9QlSFA8avKsCfXESD4+1EDYS3pwx bvrw== X-Gm-Message-State: AODbwcBX08TLJOn/VaqlKSDHhZcMTHmNp7glD+tsWmyyisg+YAJIut4/ NhCS0ZflZjG10tJ/LHxb3eo37rw7SYiS X-Received: by 10.31.190.75 with SMTP id o72mr7053277vkf.131.1495461190085; Mon, 22 May 2017 06:53:10 -0700 (PDT) MIME-Version: 1.0 From: Thomas Kupper Date: Mon, 22 May 2017 15:53:09 +0200 Message-ID: Subject: status of the cssh autocompletion To: zsh-users@zsh.org Content-Type: multipart/alternative; boundary="001a1143846602b1c605501d31de" --001a1143846602b1c605501d31de Content-Type: text/plain; charset="UTF-8" Hi, 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. Have a good day Thomas --001a1143846602b1c605501d31de--