![Twitter Follow][twitter]
A shady game master approaches...
Hey there! You look like you would enjoy a good game of chance.
This is an updated fork of this gist.
Logging functionality that supports:
- If a log message should be printed is determined at comptime, meaning zero overhead for unprinted messages (so just leave the code peppered with debug logs, but when it makes sense scope them; so downstream users can filter them out)
- Scoped log messages
- Different log levels per scope
- Overrideable log output (write to file, database, etc.)
I wanted to be really able to explain to a fair amount of detail how does the program :command:`ls` actually work right from the moment you type the command name and hit ENTER. What goes on in user space and and in kernel space? This is my attempt and what I have learned so far on Linux (Fedora 19, 3.x kernel).
How does the shell find the location of 'ls' ?
JosefJezek
/ how-to-use-pelican.md
Last active
August 24, 2025 22:27
How to use Pelican on GitHub Pages
How to use Pelican on GitHub Pages 
Author: Josef Jezek
sudo apt-get install python-setuptools