rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: quanstro@epsilon.eecs.nwu.edu (Erik Quanstrom)
To: <rc@hawkwind.utcs.toronto.edu>
Subject: re:  lazy auto-loading of functions
Date: Wed, 19 May 1993 13:39:28 -0400	[thread overview]
Message-ID: <9305191739.AA24302@canaan.eecs.nwu.edu> (raw)

Alan Watson <alan@oldp.astro.wisc.edu> writes:
  Jealous of Paul Haahr's beautiful implementation of lazy auto-loading of
  functions in es, I tried to do something similar in rc . . .
  This is just what you need for those rarely used but sometimes essential
  functions.

I'm just curious. If it's seldom used, then speed shouldn't matter that
much. Why not just use a shell script if you are concerned about env bloat?


             reply	other threads:[~1993-05-19 17:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1993-05-19 17:39 Erik Quanstrom [this message]
  -- strict thread matches above, loose matches on Subject: below --
1993-05-19 18:05 Alan Watson
1993-05-19  4:40 Alan Watson

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=9305191739.AA24302@canaan.eecs.nwu.edu \
    --to=quanstro@epsilon.eecs.nwu.edu \
    --cc=rc@hawkwind.utcs.toronto.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).