-
Notifications
You must be signed in to change notification settings - Fork 4
Yay aliases #2
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
base: master
Are you sure you want to change the base?
Yay aliases #2
Conversation
*Adds alias for "sudo pacman -D --asexplicit" *Adds alias for "sudo pacman -D --asdeps"
|
Hola @UlisesAlexanderAM. There's already a mechanism in place to source Also some of your yay aliases may clobber existing tools, like yq. I don't use arch, so I can't evaluate your new aliases here. @Eriner, an you check this out? |
|
Hi @ericbn. I modified some aliases to avoid clobbering with existing tools as you suggest. About the |
|
Hola @UlisesAlexanderAM. I think the aliases work better when they have a common prefix and then just one or two letters after that. And "yay" would de a really short prefix for yay (instead of "y"). :- ) Second, I've just pushed commits to the master branch that fix the loading of the helper files. That was a regression introduced by me in one of the last previous commits. I'll leave the final decisions regarding the changes proposed here to @Eriner. |
* Rename yay-aliases.zsh to helper_yay.zsh * Delete manual source of the old file
|
I'm hesitant to accept this PR, only because for 90% of these aliases one could just set the The majority of the aliases, from my brief review, are just |
|
|
|
Hi @Eriner. I did it this way because it is the way I do things but now I realize how inneficient it is. So, I'll delete the alias that are just And thanks for your feedback. |
I add some aliases for yay. I tried to add it as helper_yay but I couldn't source it automatically.
Also include the modifications I add on #1 .