Kilka przydatnych aliasów (bash)

Aliasy

Codziennie korzystam z dobrodziejstw konsoli. Wpisuję komendy, zapamiętuję, wpisuję nowe, zapamiętuję nowe, itd. Jeśli korzystam z jakiejś komendy dość często robię sobie z niej alias i wrzucam do pliku .bash_aliases w katalogu użytkownika.

Przedstawię aliasy z których korzystam na co dzień i które znacznie ułatwiają mi pracę. Aliasy będę przedstawiał najpierw w formie kodu, później krótki opis i na końcu obrazek jeżeli będzie to konieczne. Uwaga, zaczynam.

Katalogi/pliki

alias lr='ls -R | grep ":$" | sed -e '\''s/:$//'\'' -e '\''s/[^-][^\/]*\//--/g'\'' -e '\''s/^/   /'\'' -e '\''s/-/|/'\'''
W przyjemny dla oka sposób, wyświetla strukturę katalogów (rekurencyjnie).



alias ..='cd ..'
alias ...='cd ../..'
alias ....='cd ../../..'
alias .....='cd ../../../..'
alias ......='cd ../../../../..'
Zamiast wpisywać "cd ..", wpisujesz "..". Jak raz użyjesz to nie ma odwrotu! 

b() {
    str=""
    count=0
    while [ "$count" -lt "$1" ];
    do
        str=$str"../"
        let count=count+1
    done
    cd $str
}
Służy do tego samego co powyższy alias, z tym, że używasz go w sposób "b <liczba>".

alias l.='ls -d .* --color=auto'
Wyświetla tylko ukryte pliki.

alias lf='ls -Gl | grep ^d'
alias lsd='ls -Gal | grep ^d'
Oba listują wyłącznie katalogi. Drugi pokazuje również ukryte katalogi.

function mcd() {
  mkdir -p "$1" && cd "$1";
}
Tworzy katalog i od razu do niego wchodzi.

Terminal

alias c='clear'
Zamiast wpisywać clear, wpisujesz c.

alias freq='cut -f1 -d" " ~/.bash_history | sort | uniq -c | sort -nr | head -n 30'
Listuje 30 najczęściej wywoływanych przez ciebie poleceń basha.

Ubuntu

alias upgrade='sudo apt-get update && sudo apt-get upgrade && sudo apt-get clean'
Szybki upgrade.

I na koniec

extract () {
    if [ -f $1 ] ; then
      case $1 in
        *.tar.bz2)   tar xjf $1     ;;
        *.tar.gz)    tar xzf $1     ;;
        *.bz2)       bunzip2 $1     ;;
        *.rar)       unrar e $1     ;;
        *.gz)        gunzip $1      ;;
        *.tar)       tar xf $1      ;;
        *.tbz2)      tar xjf $1     ;;
        *.tgz)       tar xzf $1     ;;
        *.zip)       unzip $1       ;;
        *.Z)         uncompress $1  ;;
        *.7z)        7z x $1        ;;
        *)     echo "'$1' cannot be extracted via extract()" ;;
         esac
     else
         echo "'$1' is not a valid file"
     fi
}
Rozpakowywuje najpopularniejsze archiwa, "extract <nazwapliku>"

Więcej aliasów znajdziesz w moim repo na githubie dotfiles. Polecam jeszcze stronę alias.sh, na której nie ma co prawda jeszcze dużej ilości aliasów, ale można znaleźć kilka ciekawych. Oczywiście jak masz własne aliasy to warto się nimi dzielić.

Comments

Post a Comment

Popular posts from this blog

GitLab - extends keyword

Image
In the previous post I had written about the include keyword. Now, let's dive in the extends  keyword. What can you do with this? Here is the definition from GitLab documentation: extends defines entry names that a job that uses extends inherits from. It’s an alternative to using YAML anchors and is a little more flexible and readable. So, when is it useful? It is useful when you want to be DRY and keep your setup cleanly. Let's assume that you want to build a docker image and give developers possibility to deploy the image on dev , staging and prod environments. We are going to do that without the extends keyword, and after that we will think how we can do it better. Example without the extends  keyword: As you can see, there is a lot of code which repeats itself: stage, image, when  and script . We can remove a lot of code! So, let's do that. We are going to create a hidden job .deploy  (you will not see this job in a pipeline) and the rest of the jobs will in
Read more

GitLab - trigger keyword

Image
 We are going to talk about the trigger keyword today. With this feature you can define a downstream pipeline trigger. So, you can trigger a pipeline in any project (you must have access to this project of course). There are two types of downstream pipelines: multi-project pipelines child pipelines  Let's omit child pipelines and have a look at multi-project pipelines. It is very easy to use. You just need to provide a path to the project and that's it. Remember that you only can trigger a pipeline, not a job ! You can also provide more information like environment variables. As always, I am going to provide some examples, so you will understand it better. The first example: you want to trigger a pipeline in another project after the deployment of your service/s. How to do that? Here we want to trigger this pipeline (project my/run-tests ). Let's say that we want to run some tests after each deployment: We need to add the job which will trigger this pipeline in my/run-
Read more

Managing Secrets in GitLab / Git

Image
Let's say that you have to log in via ssh into an instance, and you work with GitLab, so you want to keep the private key in GitLab somewhere. Is it secure? Let's see! Custom environment variables You can use custom environment variables. Here you can read more about them (Developers cannot change them, only Maintainers and Owners can). There are two types of variables: Variable (the runner creates an environment variable that uses the key for the name and the value for the value) File (the runner creates an environment variable that uses the key for the name. For the value, the runner writes the variable value to a temporary file and uses this path) It seems that we can use File type for our purpose. We can set up it via API or UI . So, let's do that! Go to project's Settings > CI/CD . There will be Variables section (btw, you can specify variables also per group and even for all projects (in admin panel)). Click Add Variable button and add a variable: Key:
Read more