From: rsalz@osf.org
To: cks@hawkwind.utcs.toronto.edu, culliton@srg.srg.af.mil,
rc@hawkwind.utcs.toronto.edu, rsalz@osf.org
Subject: Re: Things I'd like whatis to have:
Date: Thu, 11 Mar 1993 10:49:53 -0500 [thread overview]
Message-ID: <9303111549.AA17928@earth.osf.org> (raw)
>This has a slight bug, to avoid getting caught by directories the test
Pedantically, yes. I like seeing directory name/executable clobbers. It
is normally not an issue for me since I just threw the "&& return 0" on to
what I posted; normally I don't have that -- I want to see all versions.
Chris was concerned about the cost of exec'ing all those test(1)'s.
This version cuts it down to one:
fn mywhat {
@ for (i) {
fn $i
whatis $i
}
}
next reply other threads:[~1993-03-11 15:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-03-11 15:49 rsalz [this message]
-- strict thread matches above, loose matches on Subject: below --
1993-03-10 23:21 Tom Culliton x2278
1993-03-10 22:16 Tom Culliton x2278
1993-03-10 21:36 rsalz
1993-03-10 21:22 Chris Siebenmann
1993-03-10 21:29 ` mycroft
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=9303111549.AA17928@earth.osf.org \
--to=rsalz@osf.org \
--cc=cks@hawkwind.utcs.toronto.edu \
--cc=culliton@srg.srg.af.mil \
--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).