From: arnold@skeeve.atl.ga.us (Arnold D. Robbins)
To: sam-fans@hawkwind.utcs.toronto.edu
Subject: structural regexps just for searching
Date: Thu, 24 Nov 1994 08:25:00 -0500 [thread overview]
Message-ID: <m0rAeAr-000145C@skeeve.atl.ga.us> (raw)
I want to look for function calls where there is a space after the function
name and before the left paren. But I like spaces between my keywords and
the right paren. I try something like this in the command window:
/[a-z0-9_]+ \(/ v/if|for|while|switch|return/
This will find the next match, but the file window does not scroll to show . the
way it would for just a plain search. Is there a way to get it to do this?
I'm a bit leary of just making a sweeping change
, /[a-z0-9_]+ \(/ v/if|for|while|switch|return/ s/ //
Although it would probably work ok.
Please reply by mail, my home address is not on the list.
Thanks,
Arnold
next reply other threads:[~1994-11-24 13:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1994-11-24 13:25 Arnold D. Robbins [this message]
1994-11-24 14:38 rob
1994-11-25 14:17 arnold
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=m0rAeAr-000145C@skeeve.atl.ga.us \
--to=arnold@skeeve.atl.ga.us \
--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).