From: Sam <sah@softcardsystems.com>
To: <9fans@cse.psu.edu>
Subject: [9fans] Pico (again)
Date: Wed, 17 Jul 2002 18:46:14 -0400 [thread overview]
Message-ID: <Pine.LNX.4.30.0207171836110.17275-100000@athena> (raw)
Of course, now that I've thought about it if you're
looking for an editor with the "simplicity" of
pico you can always use the rio window buffer
and snarf it into a file when you're done.
Rob mentions this in his 8 1/2 paper (The editing,
not the snarfing, iirc).
Sam
next reply other threads:[~2002-07-17 22:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-17 22:46 Sam [this message]
2002-07-18 0:28 ` Fariborz (Skip) Tavakkolian
2002-07-17 23:19 ` Sam
2002-07-18 0:35 ` Fariborz (Skip) Tavakkolian
2002-07-18 9:51 ` William Josephson
2002-07-18 8:53 steve.simon
2002-07-18 14:14 anothy
2002-07-18 18:07 ` Fariborz (Skip) Tavakkolian
2002-07-18 23:07 ` Micah Stetson
2002-07-29 15:57 ` Douglas A. Gwyn
2002-07-18 20:04 Dennis Ritchie
2002-07-19 8:19 ` ggm
2002-07-29 15:57 ` Douglas A. Gwyn
2002-07-26 6:03 Byron Rakitzis
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=Pine.LNX.4.30.0207171836110.17275-100000@athena \
--to=sah@softcardsystems.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).