From: Paul Haahr <haahr@mv.us.adobe.com>
To: schwartz@groucho.cs.psu.edu
Cc: sam-fans@hawkwind.utcs.toronto.edu
Subject: Re: regexps
Date: Wed, 9 Dec 1992 01:15:45 -0500 [thread overview]
Message-ID: <9212090615.AA09031@utopia.mv.us.adobe.com> (raw)
as i remember, the rules in sam for where the selection goes after an
x command that modified data were pretty vague. the justification that
i came up with for this (which may or may not have anything to do with
the code) was the way in which all modifications which are supposed to
happen under an x// are batched and happen in a second pass.
next reply other threads:[~1992-12-09 6:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1992-12-09 6:15 Paul Haahr [this message]
-- strict thread matches above, loose matches on Subject: below --
1992-12-09 4:54 regexps Scott Schwartz
1992-12-09 4:28 regexps Paul Haahr
1992-12-09 4:38 ` 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=9212090615.AA09031@utopia.mv.us.adobe.com \
--to=haahr@mv.us.adobe.com \
--cc=sam-fans@hawkwind.utcs.toronto.edu \
--cc=schwartz@groucho.cs.psu.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).