rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: noel@es.su.oz.au
To: rc-owner
Subject: Re: trace in rc
Date: Sat, 19 Jun 1993 20:01:42 -0400	[thread overview]
Message-ID: <199306201001.13129.out.badok@es.su.oz.au> (raw)
In-Reply-To: <9306180731.AA00685@dahlie.techfak.uni-bielefeld.de>

    From:	malte@TechFak.Uni-Bielefeld.DE

    So I'd like to hear what you think about adding a function to rc
    which is called after invocation of any command or builtin, running

NO. Leave rc alone. It isn't broken; don't fix it.


      reply	other threads:[~1993-06-20  0:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1993-06-18  7:31 malte
1993-06-20  0:01 ` noel [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=199306201001.13129.out.badok@es.su.oz.au \
    --to=noel@es.su.oz.au \
    /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).