From: Jason Tyler <jason@itntl.bhp.com.au>
To: rc@hawkwind.utcs.toronto.edu
Cc: j@nc.itntl.bhp.com.au
Subject: whatis bug
Date: Sun, 17 Aug 1997 22:30:48 -0400 [thread overview]
Message-ID: <199708180230.MAA13366@nc.itntl.bhp.com.au> (raw)
Instead of printing "$1 not found", whatis says "$1: Permission denied"
if $path($#path)^/$1 exists but is not executable. The obvious fix is:
*** builtins.c.old Tue Jul 8 01:43:52 1997
--- builtins.c Mon Aug 18 12:05:36 1997
***************
*** 342,348 ****
}
if (!f) {
found = FALSE;
! if (errno != ENOENT)
uerror(av[i]);
else
fprint(2, "%s not found\n", av[i]);
--- 342,348 ----
}
if (!f) {
found = FALSE;
! if (errno != ENOENT && errno != EACCES)
uerror(av[i]);
else
fprint(2, "%s not found\n", av[i]);
However, I don't know the source well enough to predict what unwanted
side-effects this might cause; can anyone suggest a better solution?
jason
--
OBrc: fn test-r { >[2=] <$1 } # fails on named pipes
reply other threads:[~1997-08-18 3:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=199708180230.MAA13366@nc.itntl.bhp.com.au \
--to=jason@itntl.bhp.com.au \
--cc=j@nc.itntl.bhp.com.au \
--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).