rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: jew@rt.sunquest.com
To: cks@hawkwind.utcs.toronto.edu
Cc: rc@archone.tamu.edu
Subject: to imake or not to imake
Date: Fri, 14 Feb 1992 15:37:45 -0600	[thread overview]
Message-ID: <9202142137.AA03158@rt.sunquest.com> (raw)
In-Reply-To: Chris Siebenmann's message of Fri, 14 Feb 1992 15:21:32 -0600 <92Feb14.162134est.2736@hawkwind.utcs.toronto.edu>

On a similar note to the imake question, I haven't compiled the latest
version of rc because I didn't want to go find unproto, download it,
compile it, run it/or get the patch to make it work from the author.
I liked the awk scripts from before.  Do they work in place of
unproto?  (This is for an IBM PC/RT running AIX 2.2.1)


      reply	other threads:[~1992-02-14 21:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1992-02-14 20:26 malte
1992-02-14 20:52 ` schwartz
1992-02-14 21:21 ` Chris Siebenmann
1992-02-14 21:37   ` jew [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=9202142137.AA03158@rt.sunquest.com \
    --to=jew@rt.sunquest.com \
    --cc=cks@hawkwind.utcs.toronto.edu \
    --cc=rc@archone.tamu.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).