From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9707 invoked by alias); 4 Jan 2018 00:06:37 -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: 42213 Received: (qmail 13636 invoked by uid 1010); 4 Jan 2018 00:06:37 -0000 X-Qmail-Scanner-Diagnostics: from mail-qk0-f182.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.220.182):SA:0(-1.9/5.0):. Processed in 9.712738 secs); 04 Jan 2018 00:06:37 -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,RCVD_IN_DNSWL_NONE, SPF_PASS,T_DKIM_INVALID autolearn=ham autolearn_force=no version=3.4.1 X-Envelope-From: schaefer@brasslantern.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=mrrpjuddkDxgDeQNpr56AUwCu42DYrkvhfOMqBm3fnQ=; b=fPsvF9WBKDlktI86hyftXiux3MEhNHTwBTItKP74DQ5fxWsfAkpSRTf7RIo5Ytn3Ou FRFgz1PuyDfleqo9y5Y+iUqIx41fLolXzj/Z822pB0XDiHDLDHeTVEqrjDEaxqZvl3aL iVcmCK00xWw6cWHZ6q9LSeRoIXxnAWsVlnUQh1TBhe2aX/Wpn+FS0YZWjbBVrJBae2nv TNzX/xzWPRAokTKt4DdoIKzTSV2FQf0b2H11Lrn3c4+F2cAeLHfcMHNEqSBRFpwaK6cB +LShftVTBy3JG5HutQi02+/eGMVcLczy4BlbBc6jqzyh5j3NIZeXiDXDHNVEZ0gLF5o9 1ltQ== 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; bh=mrrpjuddkDxgDeQNpr56AUwCu42DYrkvhfOMqBm3fnQ=; b=KEkZp7ndzP2VNJjlNgXx3e0blULzLF5yf8ffgaAit7OG0VFRbs8NwM60GaawXTM55g p8dRd1hmbAvx0irJO+DReB6cmr0Ip0ij1gEazEQooNL9fjGDjAhi6IFQEIjYlUdxRz1f h74sAxTjA5vqELup2tV4pyUk/bg9RS2kfOdF3Uqx2GeRtzLj7Ynb1TDgm/sX/950ac3Z WltD49OrRh7RtJV2RuuVvgeKB9ddpBcOye6FzH6rDo50ojdQ2RuBIhEO5i8TGbeRf6MW v6RhJtCQEpZmGXj0eUOGCJ1qxm3D6x1hkpx8suY4XIMK5sfwTfiZr37Smj5pPSrVEMR3 4LyA== X-Gm-Message-State: AKGB3mLaw5U+UPJXumK9IIrhUXDa2OTYhMJERxxDiLl1zlI8d+1anf5T +gEsGd3BCDITqGscOo2r1CpzENjo5kH9UTaCtm5bvA== X-Google-Smtp-Source: ACJfBos4cr6MBXcSU41YDZ4AL/0pApOE+LpFDBCfNNVkVhVWFJE4JwfyCJud4ZIY28ZtVDKEP0fjFzmbjK8nHuRAu+c= X-Received: by 10.55.107.197 with SMTP id g188mr3720140qkc.254.1515024383450; Wed, 03 Jan 2018 16:06:23 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <48C5B9DE-16A6-4987-8B1B-1CDD20C50B0C@dana.is> References: <48C5B9DE-16A6-4987-8B1B-1CDD20C50B0C@dana.is> From: Bart Schaefer Date: Wed, 3 Jan 2018 16:06:22 -0800 Message-ID: Subject: Re: [PATCH] Completion batch #3: Break _flags/_modes out of _chflags/_chmod To: "zsh-workers@zsh.org" Content-Type: text/plain; charset="UTF-8" On Wed, Jan 3, 2018 at 2:13 PM, dana wrote: > Moving on to more elaborate stuff: > > 1. Some of the new functions i was adding (to come in a subsequent batch) needed > to re-use the logic for file flags and modes from _chflags and _chmod, > respectively, so i broke those out into separate type functions called _flags > and _modes. I wonder if it might be better to call these _fflags and _fmodes or some such, since theoretically other things than files could have flags and modes?