From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2501 invoked by alias); 3 Apr 2017 07:13:11 -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: 22652 Received: (qmail 2479 invoked from network); 3 Apr 2017 07:13:11 -0000 X-Qmail-Scanner-Diagnostics: from mail-qk0-f178.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.178):SA:0(0.5/5.0):. Processed in 3.653742 secs); 03 Apr 2017 07:13:11 -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.5 required=5.0 tests=RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,RCVD_IN_SORBS_SPAM,SPF_PASS, T_DKIM_INVALID autolearn=no 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.220.178 as permitted sender) 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=Tih4zg8D0EHLWiVres0AZ5gZpCxd1XcJKdcD0rIW6cg=; b=awwO2T8d7MBl7l+G5sjNFETR6Rk7wTyI3LTn8WOqLZK8yYCe24bjhM6vFLLNGV6pxv sbaAW7TFpQn7+aACG0aDRpjIdWbrb7Y3UsPTIrkWh1UsDyc0KrKKC6RbP4fU9AfhEH3R EfBaqgwROZNLaVgt/oY1pp5OYM4TwMN7G79ky4fjcxCZLp29Opu8PSe6qYwbV7jhzED0 kMf6HiYJ4XOg9QleQ+bOPEb1r3FU3oYw1bLXVXDjUTMX6Jg31nqdqxhoQfE38HzroM+D Il+e2w0hCcKqXujsuFk2y/D0DUsqAcmoBUQDLgfl/Kfc3c1qYIt4akpJ5tCXAC/wwi86 Sqvg== 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=Tih4zg8D0EHLWiVres0AZ5gZpCxd1XcJKdcD0rIW6cg=; b=tCfDQlATgAa2SSM6H/8dvnQJuwHPXWtRCSle1+5xSMFD/HrZzqz/t0PenzDbH0in4M 4OzPC2O46BJy+l1jW3XioYE7mNTiiVyk7csmR4PCinJ8DL+1cxlvEUPkd0r3XA3w/yaZ mRk9I6ACKphUSeDG89OgewAE4Gl2BDHHjbaME1T+nTw75CGGkX/VukxyoV3Rsl7DfWQM tfpUv90PmPHaGloLFI/ZxapBq0nyzBdO/xR50h9ljnZ938dyeEuVtOiokoqBrYY06csC QlbcfgLBAuFizHdVf9Iz8bXEEh8B70S7ggnL4wjr5n1Mi4Grd0p5xdzggs7MQ36q4hIn B6Kg== X-Gm-Message-State: AFeK/H023MMc5ZJhPRVr0r2F4lmy9lYlWDcNioQGZPU9tO+x8nRC0yDSrdfeU5fxYa0xdkCqideyYQeYuV/8aQ== X-Received: by 10.55.97.67 with SMTP id v64mr15398414qkb.80.1491203580724; Mon, 03 Apr 2017 00:13:00 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20170403011159.GA64116@tower.spodhuis.org> References: <27c2026c-f760-32b0-e0d5-8c6909346979@gmx.com> <170401145348.ZM30308@torch.brasslantern.com> <20170403011159.GA64116@tower.spodhuis.org> From: Bart Schaefer Date: Mon, 3 Apr 2017 00:13:00 -0700 Message-ID: Subject: Re: REMATCH_PCRE with zsh built without pcre support To: Zsh Users Content-Type: text/plain; charset=UTF-8 On Sun, Apr 2, 2017 at 6:12 PM, Phil Pennock wrote: > On 2017-04-01 at 14:53 -0700, Bart Schaefer wrote: >> 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. > > That's a shame. To clarify, I'm not advocating any such demotion of PCRE. However, *IF* the presence of the option when the module is not available is really a serious problem, then I think the right thing is to remove the option, rather than to expand the special case. >> 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. > > I'll have to hunt down that thread and see what I can do about that. It's the recent "zregexparse" thread where this came up. I'm not sure there is anything to be done about it; the zsh/regex module would have to become part of the default static build, which might have licensing consequences.