Skip to content

Instantly share code, notes, and snippets.

View FeKoerner's full-sized avatar

Felix Körner FeKoerner

3 followers · 6 following
View GitHub Profile
@FeKoerner
FeKoerner / arch-linux-install.md
Last active October 23, 2021 15:21 — forked from kylemanna/arch-linux-install.md
Minimal instructions for installing arch linux on an UEFI NVMe system with full system encryption using dm-crypt and luks
@FeKoerner
FeKoerner / functionptrdemo.c
Last active May 9, 2019 14:01
#include <stdio.h>
void hackerName(char *string) {
printf("Your hacker name is %s", string);
}
void hackMe(char *string) {
printf("%s has hacked me.\n", string);
}
@FeKoerner
FeKoerner / latexpackages.md
Last active February 26, 2019 13:59
Latex has so many packages
@FeKoerner
FeKoerner / readme.md
Last active December 20, 2020 13:51 — forked from benstr/readme.md
Gist Markdown Cheatsheet

#Heading 1 ##Heading 2 ###Heading 3 ####Heading 4 #####Heading 5 ######Heading 6

Paragraph

@FeKoerner
FeKoerner / VIM_Keybindings.md
Last active December 7, 2019 12:35
A collection of Vim keybindings
@FeKoerner
FeKoerner / lscolors.sh
Created February 17, 2019 13:14
I was wondering why ls entries of external media always had a green background. I found out this is because of the permissions given on mounting. If a file or directory can be written to by others, ls displays it with a green background. This short script demonstrates that. You can deactivate the colors by using ls --color=never
#!/bin/bash
# For LS_COLORS, print type and description in the relevant color.
IFS=:
for ls_color in $LS_COLORS; do
color="${ls_color#*=}"
type="${ls_color%=*}"
# Add descriptions for named types.
case "$type" in