From: John (Most modern computers would break if you stood on them) Mackin <john@ civil.su.oz.au>
To: Sam Fans <sam-fans@hawkwind.utcs.toronto.edu>
Subject: ^ and $
Date: Sun, 21 Feb 1993 05:02:04 -0500 [thread overview]
Message-ID: <199302212102.8405.sam.badak@civil.su.oz.au> (raw)
Unfortunately,
x/\n? +/ v/\n/ c/ /
doesn't mean the same thing as
x/ +/ v/^/ c/ /
as long as the selection consists of whole lines, as I posited. I
thought along those paths before sending my first mail. The suggested
command chews up the indentation of the first line, since there is no
\n inside the selection for the x command to match there.
I think there may be no way to express this without a way to match the null
string at the beginning of a line, the current meaning of `^'.
OK,
John.
reply other threads:[~1993-02-21 10:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=199302212102.8405.sam.badak@civil.su.oz.au \
--to=john@civil.su.oz.au \
--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).