From: matty@cs.su.oz.au (James Matthew Farrow)
To: byron@netapp.com, rc@hawkwind.utcs.toronto.edu
Subject: Re: Interesting things from the Plan 9 rc manpage
Date: Wed, 28 Oct 1992 00:59:43 -0500 [thread overview]
Message-ID: <19921028155943.1634.frobozz@orthanc.cs.su.OZ.AU> (raw)
In-Reply-To: <9210280117.AA25914@netapp.netapp.com>
> Date: Tue, 27 Oct 1992 20:17:47 -0500
> From: byron@netapp.com (Byron Rakitzis)
> Message-Id: <9210280117.AA25914@netapp.netapp.com>
> To: cks@hawkwind.utcs.toronto.edu, rc@hawkwind.utcs.toronto.edu
> Subject: Re: Interesting things from the Plan 9 rc manpage
>
> -s: Print out exit status after any command where the
> status is non-null (false).
>
> This can be done with an appropriate fn prompt in my rc.
Surely this won't work for non-interactive files. On Plan 9's, rc
does print the status when invoked non-interactively, I just checked.
Matty.
--
James Matthew Farrow | "For in that moment I beheld the ruin
matty@cs.su.OZ.AU | of my existence. My world fell dark
Basser Department of Computer Science | and my life became a shallow dream.
Sydney University - FAX: +61 2 692 3838 | `Odi et amo. Excrucior.'" - Tlindah
next prev parent reply other threads:[~1992-10-28 6:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1992-10-28 1:17 Byron Rakitzis
1992-10-28 1:57 ` noel
1992-10-28 1:59 ` noel
1992-10-28 5:59 ` James Matthew Farrow [this message]
-- strict thread matches above, loose matches on Subject: below --
1992-10-28 15:27 Paul Haahr
1992-10-28 5:10 Chris Siebenmann
1992-10-28 4:07 Paul Haahr
1992-10-28 4:20 ` Jeremy Fitzhardinge
1992-10-28 4:27 ` Chris Siebenmann
1992-10-28 3:14 Paul Haahr
1992-10-28 3:39 ` Chris Siebenmann
1992-10-28 4:00 ` Jeremy Fitzhardinge
1992-10-27 10:52 Chris Siebenmann
1992-10-27 16:08 ` Scott Schwartz
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=19921028155943.1634.frobozz@orthanc.cs.su.OZ.AU \
--to=matty@cs.su.oz.au \
--cc=byron@netapp.com \
--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).