public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrey Repin <anrdaemon@yandex.ru>
To: L A Walsh <cygwin@tlinx.org>, cygwin@cygwin.com
Subject: Re: manpage searches "^\s+keyword\s" vs. ???
Date: Wed, 30 Jan 2019 18:50:00 -0000	[thread overview]
Message-ID: <1210066491.20190130214043@yandex.ru> (raw)
In-Reply-To: <5C4E5F0F.2090403@tlinx.org>

Greetings, L A Walsh!

> I've always used "^\s+keyword\s" as a way to search for some
> keyword starting a section. 

Welcome to the club.

> On linux it still works, but on cygin it doesn't like '\s' as
> symbol for white space.

> Any idea why there might be a difference?

> I note an option that could do similar in less -- '&pattern'
> turns OFF single special characters, I tried that on linux
> and it turned off the '\s' matching space.  That's nice..um
> how about other way?

> Well didn't know if there might be some other op to go the
> other way, but didn't see anything.

> any ideas?

I've been puzzled by this since… forever, it seems.
This is something in less, but all the `man less` says is "regular expression
library provided by your system".
I guess this is down to compilation options at this point.


-- 
With best regards,
Andrey Repin
Wednesday, January 30, 2019 21:36:27

Sorry for my terrible english...
--
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


  reply	other threads:[~2019-01-30 18:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-28  1:47 L A Walsh
2019-01-30 18:50 ` Andrey Repin [this message]
2019-01-30 19:09   ` Eric Blake
2019-01-30 19:34     ` Corinna Vinschen
2019-01-30 19:35     ` Eric Blake
2019-01-30 21:03     ` Wayne Davison
2019-01-31  0:55   ` Brian Inglis

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=1210066491.20190130214043@yandex.ru \
    --to=anrdaemon@yandex.ru \
    --cc=cygwin@cygwin.com \
    --cc=cygwin@tlinx.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.
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).