From: byron@netapp.com (Byron Rakitzis)
To: alan@oldp.astro.wisc.edu, sam-fans@hawkwind.utcs.toronto.edu
Subject: Re: Lines and last lines.
Date: Tue, 1 Dec 1992 02:57:19 -0500 [thread overview]
Message-ID: <9212010757.AA18624@netapp.netapp.com> (raw)
This is a feature, not a bug:
x<space>
is the same thing as
x/.*\n/
(modulo the RE weirdness that's being argued right now which I don't
want to get tied up with --- i.e., in short, x<space> splits the
current selection into lines. This *is* documented in the tutorial if
not in the man page as well.)
BTW, it is a *very* handy shortcut for emulating ed commands:
,x g/foo/d
is the same as ed's
g/foo/d
PS I just checked the man page and it says that
"If the regular expression and its slashes are omitted, /.*\n/
is assumed."
but of course this is not the whole story since sam barfs on
,xg/foo/d
(Another mini-gripe I have with sam: the lexical analyzer, such as it
is, sure is weird. What's the point of having delimiters between one-
letter commands like x and g anyway? Isn't that almost the point of
one-letter commands? I guess, he says sarcastically, the delimiters are
there to disambiguate "c d" and "cd" (the only multicharacter command
in sam that I know of).)
(BTW, to the religious: my negative comments about sam are meant as
constructive criticism. I don't think Rob Pike is God, and I don't
think he achived perfection with sam. He did come fairly close though,
didn't he?)
next reply other threads:[~1992-12-01 7:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1992-12-01 7:57 Byron Rakitzis [this message]
-- strict thread matches above, loose matches on Subject: below --
1992-12-01 19:54 Byron Rakitzis
1992-12-01 19:27 Alan Watson
1992-12-01 7:11 Michael John Haertel
1992-12-01 7:01 Alan Watson
1992-12-01 5:08 Byron Rakitzis
1992-12-01 0:40 Alan Watson
1992-12-01 5:46 ` Chris Siebenmann
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=9212010757.AA18624@netapp.netapp.com \
--to=byron@netapp.com \
--cc=alan@oldp.astro.wisc.edu \
--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).