For your consideration, `updog`
Installing is easy just add:
alias updog="sudo apt update && sudo apt upgrade -y"
to your .bashrc or .zshrc
Installing is easy just add:
alias updog="sudo apt update && sudo apt upgrade -y"
to your .bashrc or .zshrc
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'
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.
I'd just like to interject for a moment. What you’re referring to as Linux, is in fact, GNU/Linux, or as I’ve recently taken to calling it, GNU plus Linux. Linux is not an operating system unto itself, but rather another free component of a fully functioning GNU system made useful by the GNU corelibs, shell utilities and vital system components comprising a full OS as defined by POSIX.
Many computer users run a modified version of the GNU system every day, without realizing it. Through a peculiar turn of events, the version of GNU which is widely used today is often called “Linux”, and many of its users are not aware that it is basically the GNU system, developed by the GNU Project. There really is a Linux, and these people are using it, but it is just a part of the system they use.
Linux is the kernel: the program in the system that allocates the machine’s resources to the other programs that you run. The kernel is an essential part of an operating system, but useless by itself; it can only function in the context of a complete operating system. Linux is normally used in combination with the GNU operating system: the whole system is basically GNU with Linux added, or GNU/Linux. All the so-called “Linux” distributions are really distributions of GNU/Linux.
No, Richard, it's Arch + GNU + Linux - GNU because I stripped it of all GNU utils and replaced them with cuck BaSeD licensed software to spite those so called "enlightened" free software advocates.
Ha! What are you gonna do about it? Make GCC 2? No? Didn't think so (๑•ᴗ•๑)
and just like that, with a sickly wheeze, the last of the man's life is ejected from his body. He lies on the floor, cold and limp. I've womansplained him to death
Wait 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.
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