From: Wayne Davison <wayne@opencoder.net>
To: cygwin <cygwin@cygwin.com>
Subject: Re: change in pattern matching in pager /usr/bin/less
Date: Mon, 02 Sep 2019 07:25:00 -0000 [thread overview]
Message-ID: <CAHSx_SumgRmLs5RxjwbiyxyNv-c860g00VEZOoFkudzWLE3teg@mail.gmail.com> (raw)
In-Reply-To: <5D6C6749.1080706@tlinx.org>
On Sun, Sep 1, 2019 at 5:50 PM L A Walsh wrote:
> For some reason, the behavior of less has changed recently in regards to how
> it interprets characters like '\s' (whitespace).
Sadly, it's been compiled with POSIX regular expressions on Cygwin for
quite a while now. On Linux it is often compiled with GNU regex or
PCRE.
I started compiling my own version of less on Cygwin back in January
for this very reason. If you snag the source and run "./configure
--with-regex=pcre ; make" then you'll get a version of less.exe that
you can put somewhere early on your path (or in place of the stock
less.exe). You'll need the standard build tools installed (one way to
get those is to install cygport) plus some extra devel libraries, such
as libpcre-devel and libncurses-devel.
It would certainly be nice to have the PCRE regex as the standard in
the Cygwin version, though.
Running the Cygwin version:
$ /usr/bin/less --version
less 530 (POSIX regular expressions)
Copyright (C) 1984-2017 Mark Nudelman
Running my version:
$ less --version
less 530 (PCRE regular expressions)
Copyright (C) 1984-2017 Mark Nudelman
..wayne..
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-09-02 7:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-02 0:50 L A Walsh
2019-09-02 7:25 ` Wayne Davison [this message]
2019-09-02 13:32 ` Steven Penny
2019-09-03 7:05 ` Andrey Repin
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=CAHSx_SumgRmLs5RxjwbiyxyNv-c860g00VEZOoFkudzWLE3teg@mail.gmail.com \
--to=wayne@opencoder.net \
--cc=cygwin@cygwin.com \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).