From: "Douglas A. Gwyn" <gwyn@arl.army.mil>
To: 9fans@cse.psu.edu
Subject: [9fans] Re: h for sam
Date: Fri, 1 Dec 2000 09:34:31 +0000 [thread overview]
Message-ID: <3A268FA0.810338D6@arl.army.mil> (raw)
In-Reply-To: <t1m9hgck9i6c8d@corp.supernews.com>
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?
Otherwise a lot of the process space is occupied
with an embedded, hard-to-update help file.
next prev parent reply other threads:[~2000-12-01 9:34 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 ` Douglas A. Gwyn [this message]
2000-12-04 9:49 ` [9fans] " cLIeNUX user
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=3A268FA0.810338D6@arl.army.mil \
--to=gwyn@arl.army.mil \
--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).