-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle which
not installed
#77
Comments
Hey @brandon-leapyear, Thanks for sending this in. I was not aware of the I am having a little bit of a difficult type researching it but I wanted to share what I found. From my findings it seems that maybe Apologies if we are too late here, I realize this issue is quite old now. https://en.wikipedia.org/wiki/Type_(Unix)
https://unix.stackexchange.com/questions/85249/why-not-use-which-what-to-use-then
Here is an interesting point in your favor for POSIX compliant system
Would love to better understand the issues you are facing. |
✨ _**This is an old work account. Please reference @brandonchinn178 for all future communication**_ ✨
<!-- updated by mention_personal_account_in_comments.py -->
…---
I don't remember the exact situation, but I believe type or command would
both work for us.
On Fri, Mar 18, 2022, 2:21 PM Kyle T ***@***.***> wrote:
Hey @brandon-leapyear <https://github.com/brandon-leapyear>,
Thanks for sending this in. I was not aware of the type command! Thank
you for showing it to me.
I am having a little bit of a difficult type researching it but I wanted
to share what I found. From my findings it seems that maybe command -v is
a better generalized command. But I would like to hear more from you and
your use-case.
Apologies if we are too late here, I realize this issue is quite old now.
https://en.wikipedia.org/wiki/Type_(Unix)
The type command was a shell builtin
<https://en.wikipedia.org/wiki/Shell_builtin> for Bourne shell
<https://en.wikipedia.org/wiki/Bourne_shell> that was introduced in AT&T's
System V Release 2 (SVR2) <https://en.wikipedia.org/wiki/SVR2> in 1984,[1]
<https://en.wikipedia.org/wiki/Type_(Unix)#cite_note-1> and continues to
be included in many other POSIX-compatible shells such as Bash
<https://en.wikipedia.org/wiki/Bash_(Unix_shell)>. However, type is not
part of the POSIX standard <https://en.wikipedia.org/wiki/POSIX>. With a
POSIX shell, similar behavior is retrieved with
command -V name
https://unix.stackexchange.com/questions/85249/why-not-use-which-what-to-use-then
The status nowadays is that type and command -v are ubiquitous in all the
Bourne-like shells
Here is an interesting point in your favor for POSIX compliant system
POSIX requires that all shell builtins (like command) be also available as
external commands, but unfortunately, that's not the case for command on
many systems. For instance, it's rare to find a command command on Linux
based operating systems while most of them have a which command (though
different ones with different options and behaviors).
Would love to better understand the issues you are facing.
—
Reply to this email directly, view it on GitHub
<#77 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGUC75OS4LKJUNM3PTTCNATVATXT5ANCNFSM45FJLXDQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
This was resolved with PR #98 |
Use
type
instead, which is a bash built-inThe text was updated successfully, but these errors were encountered: