Installing is easy just add:
alias updog="sudo apt update && sudo apt upgrade -y"
to your .bashrc or .zshrc
You must log in or register to comment.
This would go perfectly with the alias I did because I kept forgetting the original command:
$ alias whats=type $ whats updog updog is aliased to 'sudo apt update && sudo apt upgrade -y'It’s all coming together now!
Is this a meme I’m too crontab to understand?
So you mean “what’s updog” hahhahahha
Don’t be such a chrony. I’m sure you’ll be in symc sooner or later.
Someone wrote about there being a cat and a bat command in linux (plus another animal name I forgot), but no dog command. Someone commented that there’s updog.
alias yay="sudo apt update && sudo apt upgrade -y"These are my aliases:
alias dog=catAnd this one really improves my performance:
alias got=gitWait until you see the one I showed off the other day:
alias gl='git log --graph --abbrev-commit --no-decorate --date=format:'\''%Y-%m-%d %H:%M:%S'\'' --format=format:'\''%C(8)%>|(16)%h %C(7)%ad %C(8)%<(16,trunc)%an %C(auto)%d %>|(1)%s'\'' --all'I present my
ll:exa --all --long --header --group --time-style=long-iso --group-directories-first --git.
what’s updog?
Not much, hbu?
Not much, what’s up with you?
Isn’t “dist-upgrade” a better practice, particularly when using the “-y” argument?
What does -y do in apt?
Forces “yes” so you don’t get the “continue?” prompt after hitting enter
I see. For some reason my apt manpage don’t list it, but my apt-get manpage does.
Wait… what? I didn’t even consider this could be an option. Is anyone willing to point me at some accurate information about how to get started? Like… where do I put a bash file, and how is it structured? How can I automate it? So many questions. I’m only sort of familiar with bash, as in I’ve seen the term and watched my coworker do some wizardry once.
I think this is an easier way to do it:
add this to a file called .bash_aliases instead (it should be a file right next to .bashrc, if not just create it)
You can add aliases to .bashrc with this, but I personally perfer to have aliases in their own file
Another thing, if you have a console window open while adding it, restart it so that the console is aware of the aliases. Alternatively, google something like “sourcing bashrc” or “sourcing aliases” and apply the commands you find
If you wish to add aliases to a bash script (for later automation), you add these two lines
shopt -s expand_aliases
source ~/.bash_aliases
but of course add this to the top of your bash scripts, so that your script knows to use the bash shell:
#!/bin/bash
This is so great. Thank you.
