From: rob@research.att.com
To: sam-fans@hawkwind.utcs.toronto.edu
Date: Sun, 21 Feb 1993 23:48:41 -0500 [thread overview]
Message-ID: <93Feb21.235516est.2758@hawkwind.utcs.toronto.edu> (raw)
How about:
y/^ +/ x/ +/ c/ /
that's using ^ again; i thought the exercise was to avoid it.
at least, that is the exercise i've been working on.
when i made my suggestion
x s2/ +/ /g
i implicitly assumed, as i think did the original poster, that
each line began with white space. as i sit here now, i can't
find a clean-enough-to-use version that doesn't use ^. the
magic thing about ^ is that it works at the beginning of the file;
otherwise i could cheat. the poster said he had whole lines, hence:
-#1,. x/\n?.+/ v/\n/ x/ +/ c/ /
but this is already too silly.
-rob
next reply other threads:[~1993-02-22 4:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-02-22 4:48 rob [this message]
1993-02-23 3:26 ` David Hogan
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=93Feb21.235516est.2758@hawkwind.utcs.toronto.edu \
--to=rob@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).