From: cLIeNUX user <r@your_host.com>
To: 9fans@cse.psu.edu
Subject: [9fans] Re: h for sam
Date: Mon, 4 Dec 2000 09:49:19 +0000 [thread overview]
Message-ID: <t2gni0es1uida@corp.supernews.com> (raw)
In-Reply-To: <3A268FA0.810338D6@arl.army.mil>
gwyn@arl.army.mil...
>Hm, if you *have* to have a "help" command in sam,
>why not have it just open a window attached to the
>appropriate help-document path on the host?
sam doesn't have windows. That's samterm. I built just the sam part for my
Linux distro, which has an X-less "Core" that I basically live in.
>Otherwise a lot of the process space is occupied
>with an embedded, hard-to-update help file.
My tastes for online docs are definitely as presented, in contrast to ed,
sam and so on. My tastes for interdependancies leaves Plan9 interesting
for reasons other than it's distributed-ness. Tastes obviously vary. Even
on Plan9, I'm sure I'd personally go with the simplicity of an h key as
presented as, in addition to whatever.
Rick Hohensee
Forth, unix, cLIeNUX
www.clienux.com
prev parent reply other threads:[~2000-12-04 9:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-23 10:17 [9fans] " cLIeNUX user
2000-12-01 9:34 ` [9fans] " Douglas A. Gwyn
2000-12-04 9:49 ` cLIeNUX user [this message]
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=t2gni0es1uida@corp.supernews.com \
--to=r@your_host.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).