From: Chris Siebenmann <cks@hawkwind.utcs.toronto.edu>
To: rc@archone.tamu.edu
Subject: Re: rc + Xwindows
Date: Mon, 26 Aug 1991 22:30:31 -0500 [thread overview]
Message-ID: <91Aug26.233038edt.2699@hawkwind.utcs.toronto.edu> (raw)
In-Reply-To: byron's message of Mon, 26 Aug 91 23:22:50 -0400. <91Aug26.222252cdt.22533@archone.tamu.edu>
By contrast, rc -l for me produces 36 lines of output and takes
4.8 real, 1.2 user, and 2.7 sys. This is too many lines of output, but
it will always produce two or three -- I don't want any. One of the reasons
I switched to rc is so that I wouldn't have to run a fair chunk of my
initialization code over and over again for each window (I have a lot of
functions); I'd hate to have to throw that advantage away.
- cks
next prev parent reply other threads:[~1991-08-27 3:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1991-08-27 3:22 Byron Rakitzis
1991-08-27 3:30 ` Chris Siebenmann [this message]
1991-08-27 10:06 ` Boyd Roberts
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=91Aug26.233038edt.2699@hawkwind.utcs.toronto.edu \
--to=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).