zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@zsh.org
Subject: Re: REMATCH_PCRE with zsh built without pcre support
Date: Sat, 1 Apr 2017 14:53:48 -0700	[thread overview]
Message-ID: <170401145348.ZM30308@torch.brasslantern.com> (raw)
In-Reply-To: <27c2026c-f760-32b0-e0d5-8c6909346979@gmx.com>

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.


  reply	other threads:[~2017-04-01 21:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-01 19:09 Eric Cook
2017-04-01 21:53 ` Bart Schaefer [this message]
2017-04-03  1:12   ` Phil Pennock
2017-04-03  7:13     ` Bart Schaefer
2017-04-03 11:26       ` Daniel Shahaf
2017-04-03 18:00         ` Bart Schaefer
2017-04-04  0:36           ` Daniel Shahaf
2017-04-04  2:43             ` Bart Schaefer
2017-04-04 12:27               ` Eric Cook
2017-04-05 13:08                 ` Daniel Shahaf
2017-04-04 15:22               ` Ray Andrews
2017-04-04 23:00                 ` Bart Schaefer
2017-04-05 13:42               ` Peter Stephenson
2017-04-05 22:28                 ` Bart Schaefer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=170401145348.ZM30308@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-users@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).