From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6678 invoked by alias); 1 Apr 2017 21:53:56 -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: 22649 Received: (qmail 13435 invoked from network); 1 Apr 2017 21:53:56 -0000 X-Qmail-Scanner-Diagnostics: from mail-vk0-f50.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.50):SA:0(-0.0/5.0):. Processed in 1.026774 secs); 01 Apr 2017 21:53:56 -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=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_PASS,T_DKIM_INVALID autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: schaefer@brasslantern.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.50 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:date:in-reply-to:comments:references:to:subject :mime-version; bh=UdJT+GybQBYl1ZekmSHJkJkXqBTUw0HafMJ6yO1AKWU=; b=qOOB5pa5Yfer9jMyJXx1x5wxm0bFjJJ0ihq58hlWS206vBUX9dh7P3Uu3dn4LvXe4I cZSyvwDgCVWA8gtvi3ehzw0rB6h1X9uIU2uDObMwG+7iQYt1VvNKAvBXFPRT1/b1ZcV+ eHJWPo/qmNYyIsV2wSBEkH5F6yoG2+ur8h8X18TXUKzsg5APRidcYu9bX3m1uQv3CUQL hdj6uu7MZ6pALOQ6CFv02pAF9xzY4Z/5KqmK3cswvwTEMqHVvTeIXYLoHPDMv+sIMcNv hXR8al7wQxcpr/NlPWi8pup0ulmaSp6eabFz8LnGd/A8zhU6i3C52TpksSP2VSSbN/rK Ioww== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:date:in-reply-to:comments :references:to:subject:mime-version; bh=UdJT+GybQBYl1ZekmSHJkJkXqBTUw0HafMJ6yO1AKWU=; b=nHlbC9eUItTfjDzu9QGF0hGw2DpCdGA9OdWUvYP0njpxoqVXMd14UH8NzDSOzhKsNp rffFuRzCeWPT9ml97dUJ4/vMrejgdGBcnrPZBH/1w0iQY13KKL3J/ZWKciQNItoPQx9L Ukd41iNyPJ7V1LIkdPrH4su0jvsE90epOe1zQugP0s/aP4ZO19zw5T+Tsw3xefHLKSLs sbLeEvQ+TZV/qZ3zQpVnKrdmHvTI0wSEEyitYm3UfgTWlbriUvukUTSLfsKHSKa5NtXA L846nxb731w0D29kz7yY7tzju3yRz2s0baDhiqzatuE9NUAv7JKWt0y5dwjP71UkT+5j U++Q== X-Gm-Message-State: AFeK/H2HoW0Tjl1pCdZxKxbtUwqqsLx4JdAjdM+nUIdcVurqA4bj2mFVzFWQGe67ilUgUA== X-Received: by 10.31.80.69 with SMTP id e66mr2745142vkb.142.1491083627492; Sat, 01 Apr 2017 14:53:47 -0700 (PDT) From: Bart Schaefer Message-Id: <170401145348.ZM30308@torch.brasslantern.com> Date: Sat, 1 Apr 2017 14:53:48 -0700 In-Reply-To: <27c2026c-f760-32b0-e0d5-8c6909346979@gmx.com> Comments: In reply to Eric Cook "REMATCH_PCRE with zsh built without pcre support" (Apr 1, 3:09pm) References: <27c2026c-f760-32b0-e0d5-8c6909346979@gmx.com> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-users@zsh.org Subject: Re: REMATCH_PCRE with zsh built without pcre support MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Apr 1, 3:09pm, Eric Cook wrote: } } Should setting this option be allowed when zsh was built without pcre } support? That might make sense, but it would mean that the option-setting code has to know about modules and add a special case for this one. Presently the only existing module-specific hack that deep in the core shell is the bit in conditionals that implements the =~ operator. I'd personally be more inclined to do away with REMATCH_PCRE and that =~ special-case entirely, and require explicit use of the -pcre-match operator (or a shorter equivalent) when you want those semantics. It's already been pointed out in another thread that =~ doesn't work at all if the shell is built with the default modules and without dynamic linking support.