From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00 shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 5D41C1F4B4; Mon, 14 Dec 2020 20:39:38 +0000 (UTC) Date: Mon, 14 Dec 2020 20:39:38 +0000 From: Eric Wong To: meta@public-inbox.org Subject: are Perl regexps well-known enough for command-line use? Message-ID: <20201214203938.GA31896@dcvr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline List-Id: I've been thinking a bit about UI/UX for local command-line tooling, and one thing I've been pondering is exposing Perl5 regexps as a mechanism for filtering mailboxes/newsgroups/URLs/pathnames, etc... It ties the UI to Perl5, though PCRE can get pretty close... NNTP has it's own "wildmat" format in RFC 3977 which we support (though maybe not 100% completely :x). It's pretty close to Bourne shell globbing, I think. Perl's built-in and stdlib glob operators only work on FS paths, and (as usual) I'm trying to avoid dependencies or Inline::C for ease-of-installation and disk/bandwidth considerations.