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.0 required=5.0 tests=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 5aee52cf for ; Fri, 10 Jan 2020 10:25:33 +0000 (UTC) Received: (qmail 8055 invoked by alias); 10 Jan 2020 10:25:28 -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: 45279 Received: (qmail 15005 invoked by uid 1010); 10 Jan 2020 10:25:28 -0000 X-Qmail-Scanner-Diagnostics: from rcpt-expgw.biglobe.ne.jp by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.102.1/25684. spamassassin: 3.4.2. Clear:RC:0(133.208.98.2):SA:0(-2.6/5.0):. Processed in 3.377356 secs); 10 Jan 2020 10:25:28 -0000 X-Envelope-From: takimoto-j@kba.biglobe.ne.jp X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at spf01.biglobe.ne.jp designates 133.208.98.2 as permitted sender) X-Biglobe-Sender: From: Jun T Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: [PATCH] find RLIM_NLIMITS correctly on Cygwin Date: Fri, 10 Jan 2020 19:24:49 +0900 References: <82F8CDE0-C95C-4D31-ABFC-EBB3C97799F3@kba.biglobe.ne.jp> <1B509B1C-A670-482F-9D88-2145E15D03A1@kba.biglobe.ne.jp> <20200109131553.hqetnd45sc43z6xb@tarpaulin.shahaf.local2> To: zsh-workers@zsh.org In-Reply-To: <20200109131553.hqetnd45sc43z6xb@tarpaulin.shahaf.local2> Message-Id: <087AE8B9-35B0-4258-9626-AACA85471A07@kba.biglobe.ne.jp> X-Mailer: Apple Mail (2.3445.104.11) X-Biglobe-Spnum: 19381 > 2020/01/09 22:15, Daniel Shahaf wrote: >=20 > Yeah, the C preprocessor can't discover RLIMIT_* macros we don't know = about in > advance, I agree. For that we'd need awk(1) or similar (maybe just = =C2=ABgrep -o > 'RLIMIT_[^ ]*'=C2=BB). Maybe something along these lines: Thanks. But I've started thinking that we can just use a resource name such as "unknown8" (instead of "FOO") for unknown resource. Then rlimits.awk can be removed as you have suggested originally. Of cause there is a chance that the tail part of the macro name ("FOO") = may give some hint for users, but it is far from satisfactory anyway. If users find "unknown8" in the output of the limit builtin, then = *hopefully* they report it to zsh/workers; then we can add it to the list of known resources easily.