Skip to content
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

Thoughts on adding abbreviated commands to bin? #200

Closed
AndrewSB opened this issue May 4, 2016 · 4 comments
Closed

Thoughts on adding abbreviated commands to bin? #200

AndrewSB opened this issue May 4, 2016 · 4 comments
Labels
question An open question

Comments

@AndrewSB
Copy link

AndrewSB commented May 4, 2016

Adding commands similar to what npm has? i would be shorthand for install, l for list?

Not sure if this has been discussed in the past

@UniqMartin UniqMartin added the question An open question label May 4, 2016
@UniqMartin
Copy link
Contributor

Do you literally mean /usr/local/bin? If so, placing executables with such a short name is likely to be problematic. Or do you talk about abbreviations you can use with brew, e.g. brew i would mean brew install. If that's what you are looking for, there's already a solution: https://github.com/Homebrew/homebrew-aliases

@apjanke
Copy link
Contributor

apjanke commented May 4, 2016

Yeah, I think for either of these, per-user aliases configured in the shell (for standalone commands) or brew alias (for brew subcommands) is the way to go, not something global like adding to /usr/local/bin or making subcommand aliases for everyone.

@AndrewSB
Copy link
Author

AndrewSB commented May 7, 2016

https://github.com/Homebrew/homebrew-aliases is what I was talking about. Thanks @UniqMartin, wasn't able to find that, satisfies my need :)

@apjanke why not add subcommand aliases (like brew i for brew install) for everyone? I feel as if it's a common pattern for package managers now?

@MikeMcQuaid
Copy link
Member

@AndrewSB We may consider that in future but not now.

@Homebrew Homebrew locked and limited conversation to collaborators May 3, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
question An open question
Projects
None yet
Development

No branches or pull requests

4 participants