sam-fans - fans of the sam editor
 help / color / mirror / Atom feed
From: arnold@skeeve.atl.ga.us
To: rob@plan9.research.att.com, sam-fans@hawkwind.utcs.toronto.edu
Subject: Re: structural regexps just for searching
Date: Fri, 25 Nov 1994 09:17:26 -0500	[thread overview]
Message-ID: <m0rB1Sp-00013wC@skeeve.atl.ga.us> (raw)
In-Reply-To: emory!plan9.research.att.com!rob's 27-line message on Nov 24,  9:38am

> it's easy to get it to scroll to the next match.  follow the command
> by an address, . :
> 
> 	/[a-z0-9_]+ \(/ v/if|for|while|switch|return/
> 	.
> 
> it's just like saying
> 
> 	23
> 
> to have it show you line 23

This works, but suprisingly (to me, anyway), it does not wrap around
the file...

Arnold


             reply	other threads:[~1994-11-25 14:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1994-11-25 14:17 arnold [this message]
  -- strict thread matches above, loose matches on Subject: below --
1994-11-24 14:38 rob
1994-11-24 13:25 Arnold D. Robbins

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=m0rB1Sp-00013wC@skeeve.atl.ga.us \
    --to=arnold@skeeve.atl.ga.us \
    --cc=rob@plan9.research.att.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).