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 14:54:39 -0500 [thread overview]
Message-ID: <9212011954.AA03668@netapp.netapp.com> (raw)
The treatment of whitespace in the sam lexical analyzer is
very idiosynchratic.
Here are the features:
B<space>
means "open a new file".
x<space>
is the RE hack we talked about. This applies to y, X and Y as
well. Also it means that either an RE or a space is *required*
between "x" and any other command. This is why I think the
comment in the man page about omitting the RE reads so poorly.
BTW,
x<nl>
also works, and seems to be equivalent to
x/(\n|.)*/p
Here are some more dubious features:
f<space>
sets the current filename to null.
w<space>
prints
?no file name
which is consistent with "f<space>" setting the filename to
null, at least.
Otherwise, whitespace *seems* to be optional. Did I cover all
the cases?
BTW, reading and writing an octal dump a binary editor does not
make. I can do exactly the same with vi (the editor that the
labs people detest), including the bit about piping the whole
file through an octal dumper & undumper.
next reply other threads:[~1992-12-01 19:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1992-12-01 19:54 Byron Rakitzis [this message]
-- strict thread matches above, loose matches on Subject: below --
1992-12-01 19:27 Alan Watson
1992-12-01 7:57 Byron Rakitzis
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=9212011954.AA03668@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).