From: Scott Schwartz <schwartz@groucho.cs.psu.edu>
To: Paul Haahr <haahr@mv.us.adobe.com>
Cc: sam-fans@hawkwind.utcs.toronto.edu
Subject: Re: regexps
Date: Tue, 8 Dec 1992 23:38:20 -0500 [thread overview]
Message-ID: <92Dec8.233845est.2541@groucho.cs.psu.edu> (raw)
In-Reply-To: Your message of "Tue, 08 Dec 92 23:28:27 EST." <9212090428.AA08969@utopia.mv.us.adobe.com>
| beginning of word: (^|[^a-zA-Z0-9])
| end of word: ($|[^a-zA-Z0-9])
I lust for \< and \>. In vi, something like
%s/\<foo\>/gnu/
is wonderfully concise.
| 'course, you still have to narrow dot by one then.
Hey, no fair leaving parts out. :-)
next prev parent reply other threads:[~1992-12-09 4:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1992-12-09 4:28 regexps Paul Haahr
1992-12-09 4:38 ` Scott Schwartz [this message]
-- strict thread matches above, loose matches on Subject: below --
1992-12-09 6:15 regexps Paul Haahr
1992-12-09 4:54 regexps Scott Schwartz
1992-12-09 4:15 regexps Scott Schwartz
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=92Dec8.233845est.2541@groucho.cs.psu.edu \
--to=schwartz@groucho.cs.psu.edu \
--cc=haahr@mv.us.adobe.com \
--cc=sam-fans@hawkwind.utcs.toronto.edu \
/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 NNTP newsgroup(s).