From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25664 invoked by alias); 6 Aug 2018 07:28:29 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: List-Unsubscribe: X-Seq: 43235 Received: (qmail 816 invoked by uid 1010); 6 Aug 2018 07:28:29 -0000 X-Qmail-Scanner-Diagnostics: from nl.dwimlabs.net 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(81.4.124.96):SA:0(-1.9/5.0):. Processed in 0.612227 secs); 06 Aug 2018 07:28:29 -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=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_PASS, SPF_PASS,T_DKIM_INVALID autolearn=ham autolearn_force=no version=3.4.1 X-Envelope-From: av6@dwimlabs.net X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dwimlabs.net; s=20171204; t=1533540505; bh=CeRinEm0PuyX/j9wqk4p08D57PwwjLP1jmBTTKhElE8=; h=From:To:Cc:Subject:Date:From; b=cpxy0cZlSAl5gEgdqsx9fN8/Zn0t0ApdnFWACM8bKPDOtnuF9PqTlgaSb7QWGUwvm uGtf3ScSqrjjSd9xbxrw4PubXtah3ictfJ1Zjsu43RH5boeNOEO+gIBpFVvm3sxtc1 3MgV6cOsiDCrCAZs0W1qrZGHM/+cM5XGP0Yrsau4= From: Anton Shestakov To: zsh-workers@zsh.org Cc: Anton Shestakov Subject: [PATCH 0/5] An update for Completion/Unix/Command/_hg Date: Mon, 6 Aug 2018 15:28:08 +0800 Message-Id: <20180806072813.5051-1-av6@dwimlabs.net> X-Mailer: git-send-email 2.11.0 Hey there zsh folks, One day I decided to update completion file for hg (Mercurial), even though I didn't really know how zsh completion system works. A week later, I still don't know how it works, but I believe I have something that's worth sending. So here goes. This update is based on hg 4.0, which is what Debian stable has at the moment. When comparing it to 4.7, which has been released recently, it lacks some newer command line flags (e.g. --dry-run and --interactive for more commands), but let's assume people don't upgrade often and 4.0 is the least they have. I can update the completion file based on 4.7 later, if people think it's a good idea. In general, I can fix errors and things that I missed, but preferably in a follow-up, because I was staring at these diffs for a whole week. Diffs as in plural because I have an update to upstream... downstream? sidestream's completion file: Mercurial's own contrib/zsh_completion, which I'm intending to base on 4.7. My idea is to run things through people who know zsh completion better first, and then send patches to Mercurial. I've split the work into 5 patches for easier reviewing, because they do need reviewing -- I'd rather not have any errors in a file that gets updated once a year. Thanks in advance! Anton Shestakov (5): _hg: rename _hg_style_opts to _hg_template_opts _hg: declare appropriate local parameters for ->string form _hg: add forget, phase, summary _hg: update all options _hg: drop -w, add -S to _arguments Completion/Unix/Command/_hg | 357 ++++++++++++++++++++++++++------------------ 1 file changed, 213 insertions(+), 144 deletions(-) -- 2.11.0