From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FROM,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from primenet.com.au (ns1.primenet.com.au [203.24.36.2]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id 5a79e178 for ; Mon, 25 Mar 2019 18:58:51 +0000 (UTC) Received: (qmail 8232 invoked by alias); 25 Mar 2019 18:58:32 -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: List-Unsubscribe: X-Seq: 23883 Received: (qmail 29476 invoked by uid 1010); 25 Mar 2019 18:58:31 -0000 X-Qmail-Scanner-Diagnostics: from mail-ed1-f46.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.101.1/25398. spamassassin: 3.4.2. Clear:RC:0(209.85.208.46):SA:0(-2.0/5.0):. Processed in 3.32521 secs); 25 Mar 2019 18:58:31 -0000 X-Envelope-From: matthijstijink@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.208.46 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:subject:date:message-id:mime-version :content-transfer-encoding; bh=HE5HKvhaKgfx+Yfm7EJrpI4C9ChrhG7LYNoP25h0fFc=; b=pqQHhLUt+FS8xV0cC9n7N+knNMdOmUYtntapTXYQ3MKJlMGXIITdptOI1Cj0g5Pqbg gr+Y605Bg5tkBOsphvVgImIUScCv2d3Zfc0nApRmiWhO7bTAJ2+XdcYLAGf2wTf9RIu7 peX7iV4f3whj3PFtgtWS2UMW9Nxz5ZMhzXIrrzr6vmf07kBHtJsxJ65nM9SWKdSB59V6 hdYZ0zkkG298obQMNWAnqSlOeSwrAngEZYMDq32DIWyzEFCAD5DT8HjZf3Ot9j5AHyVG z7eHtTJD7W8wBjS4udmOuZ5WKBeKAnGA5FsVbNNfG7Y7pSRytB+er5c4ezoKiGb3Zowi kYOQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:mime-version :content-transfer-encoding; bh=HE5HKvhaKgfx+Yfm7EJrpI4C9ChrhG7LYNoP25h0fFc=; b=cx4t6xZzyDQ6DqGBASZ+z1d/VbBm38fNr5UvbLZ7P+yiqYdZkdTSX2UaMZAzWHffTe 3GVRkN5tyxF9xXQi3u6/yMKfn4e3Kq37F+ra58LwG3TFpDtK14NEAZJqXw+8lt+kMHax 2mCDGbrTWBy7qScJDBlvv4jMLeNtuW6yac9QJ2et9wScD83KnM/wdq/WDmMgaVv+sqhx p8tn32w6oFONWB48Od9vLPYQmcbsD+fuCBbL1HAeP5JemK1LWs+4tdXKxEQ+MmLPhkkp 3Tb4XF+/bTzok6HeO/li0HUj7+wzHF3JoiIeg/+FQOwSF+WPi3WuV+2vbrmBHMYG/zND HZXw== X-Gm-Message-State: APjAAAUji2raey0lzEdB4rf14dqwDo1gphda8+WXWMa4u86LmNRLw8P5 dvQoVW7ccXm9YUbARgY2PgTFyJjI X-Google-Smtp-Source: APXvYqzIzEbQ57Se8B3CrLC9SLDcQYV5bLOsxDGyb/Y0PIzemhea9gpBeFkJxCS/Au9YwfN8xdfXLw== X-Received: by 2002:a50:b673:: with SMTP id c48mr16593157ede.138.1553540272815; Mon, 25 Mar 2019 11:57:52 -0700 (PDT) From: Matthijs Tijink To: zsh-users@zsh.org Subject: Shipping autocomplete file upstream for KDE Connect? Date: Mon, 25 Mar 2019 19:57:50 +0100 Message-ID: <1750439.SibdPxaLH4@matthijs-msi> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Dear all, We at KDE Connect are in the process of improving our zsh autocomplete file, and were thinking it might be easier to ship the file ourselves. However, I initially submitted an autocomplete file to zsh some months ago, and that's already released. So, I've got a few questions and hope you can answer them: What's your preferred way of shipping autocomplete files? With zsh or with the program itself? In case it's with the program itself, how should we proceed with adding/removing the completion file? Thanks in advance! Kind regards, Matthijs Tijink PS: I'm not subscribe to the mailing list, so please keep me on CC.