From: Ian Zimmerman <itz@very.loosely.org>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: search patterns in less(1)
Date: Fri, 19 Jul 2019 09:29:37 -0700 [thread overview]
Message-ID: <20190719162937.bbtbnjofvvvy6v7z@matica.foolinux.mooo.com> (raw)
In-Reply-To: <15e96e0c-bc97-3712-eca7-5433ca5fad63@web.de>
On 2019-07-19 06:40, n952162 wrote:
> Anyway, thank you for the (unexpected) tip:
>
> man perlre
>
> That says to use \b instead of the decades-old \<.
I did not expect it either, but I convinced myself running
ldd `which less`
--
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet and on broken lists
which rewrite From, fetch the TXT record for no-use.mooo.com.
prev parent reply other threads:[~2019-07-19 16:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 22:40 [gentoo-user] search patterns in less(1) n952162
2019-07-18 20:55 ` Michael Orlitzky
2019-07-19 6:40 ` n952162
2019-07-19 15:28 ` Michael Orlitzky
2019-07-19 15:44 ` Michael Orlitzky
2019-07-19 16:29 ` Ian Zimmerman [this message]
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=20190719162937.bbtbnjofvvvy6v7z@matica.foolinux.mooo.com \
--to=itz@very.loosely.org \
--cc=gentoo-user@lists.gentoo.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