From: "David Leimbach" <leimy2k@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: Re: Re: [9fans] release -1 of smacme
Date: Thu, 6 Jul 2006 22:07:36 -0700 [thread overview]
Message-ID: <3e1162e60607062207n48c1897dj87c1386bfb345ba9@mail.gmail.com> (raw)
In-Reply-To: <7359f0490607062203u1bcb69bao763a33fb58d1579a@mail.gmail.com>
LOL, totally knew he'd show up if I said that :-)
Hi Rob, don't worry I was kidding.
Dave
On 7/6/06, Rob Pike <robpike@gmail.com> wrote:
> You've lost your way.
>
> -rob
>
>
> On 7/6/06, David Leimbach <leimy2k@gmail.com> wrote:
> > On 7/6/06, Ronald G Minnich <rminnich@lanl.gov> wrote:
> > > OK, people actually want this damned thing.
> > >
> > > So, in the interests of furthering the secret plans of the SP9SSS, I
> > > have put the source to smacme in contrib/rminnich.
> > >
> > > It's called smacme because I expect to have to say: 'don't smacme!' when
> > > I tell people about it. Plus, emacs had one more letter than acme, and
> > > used 5 letters, so now we have evened up the score. 6 letters, 5
> > > different letters.
> > >
> > > What it is: well, just build and start it up, then type stuff like ^D
> > > and ^P and ^N and ^K. What are all the commands? That's secret.
> > >
> > > You don't like it, don't use it. You like it, well, then add more stuff
> > > to it as you see fit, and let me know.
> > >
> > > Bugs? But of course.
> > >
> > > ron
> > >
> >
> > Neat... tempted to make ^K stuff into /dev/snarf... and have ^Y read
> > from /dev/snarf
> >
>
next prev parent reply other threads:[~2006-07-07 5:07 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-06 22:18 Ronald G Minnich
2006-07-07 1:18 ` Federico Benavento
2006-07-07 5:00 ` David Leimbach
2006-07-07 5:03 ` Rob Pike
2006-07-07 5:07 ` David Leimbach [this message]
2006-07-07 14:07 ` Ronald G Minnich
2006-07-07 14:34 ` David Leimbach
2006-07-07 14:51 ` Ronald G Minnich
2006-07-07 14:53 ` John Floren
2006-07-07 15:31 ` David Leimbach
2006-07-07 16:07 ` Jack Johnson
2006-07-07 16:09 ` C H Forsyth
2006-07-07 16:20 ` David Leimbach
2006-07-07 16:00 ` C H Forsyth
2006-07-07 16:27 ` uriel
2006-07-07 16:45 ` jmk
2006-07-07 20:08 ` Brantley Coile
2006-07-07 20:21 ` David Leimbach
2006-07-08 3:00 ` Ronald G Minnich
2006-07-08 2:59 ` Ronald G Minnich
2006-07-07 14:05 ` Ronald G Minnich
2006-07-07 6:16 ` Christoph Lohmann
2006-07-07 14:09 ` Ronald G Minnich
2006-07-07 14:17 ` Christoph Lohmann
2006-07-07 14:27 ` Ronald G Minnich
2006-07-07 19:53 ` uriel
2006-07-07 20:23 ` jmk
2006-07-07 20:35 ` David Leimbach
2006-07-08 2:38 ` uriel
2006-07-08 3:45 ` jmk
2006-07-08 3:39 ` quanstro
2006-07-08 4:26 ` jmk
2006-07-08 12:30 ` quanstro
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=3e1162e60607062207n48c1897dj87c1386bfb345ba9@mail.gmail.com \
--to=leimy2k@gmail.com \
--cc=9fans@cse.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).