Phundrak’s dotfiles Sitemap for project config-website-org

Table of Contents

1. Presentation

This is my collection of dotfiles for my daily GNU/Linux environment, tweaked to my liking. If you wish to get the same setup as mine, follow the instructions below.

For starters, here is the link to all the pages on my website that you might find interesting. I’ll describe them in more details below.

As you can see, I personally use fish as my shell of choice, and Emacs 29.0 as my main text editor.

When it comes to my graphical UI, I do not have any desktop environment. Instead, I have a tiling window managers, StumpWM. I used to use i3-gaps, an i3 fork by Airblader, with which I used Polybar as well as pywal to define my system’s color scheme, and then I used Awesome. But now, as said above, I prefer to use StumpWM. It has a built-in status bar (called a mode-line, like in Emacs) which I use, and I settled on the dark Nord theme for pretty much everything I use.

Finally, you can find my configuration for my ErgodoxEZ keyboard here. It is optimized for usage with the Bépo layout set as a software layout. It has also a layer set to emulate a Qwerty layout when using the Bépo software layout due to some games that do not offer to remap keys (I’m looking at you, Among Us).

2. Features

  • Emacs' configuration perfectly tailored for my own use
  • Beautiful and comfy StumpWM configuration
  • And enough information below to get basically the same distro install as I have on computer.

Most of the org files you will find in this repo are the actual source code of much of my config files. For instance, the bootstrap found in exports almost all of its code snippets to $HOME/.config/yadm/bootstrap thanks to M-x org-babel-tangle from within Emacs. Below I will also present and comment some of my short config files which do not deserve to have a full org file dedicated to them.

2.1. Tiling Window Managers

2.1.1. StumpWM

StumpWM is the tiling window manager I use at the moment. It is written and configured in Common Lisp, which I enjoy a lot since it has a syntax quite close to Elisp, the Lisp dialect used in Emacs. I’m currently still in the process of figuring out my config, so please consider it as a kind of work in progress. You can find the configuration here.

2.1.2. AwesomeWM (Deprecated)

AwesomeWM is the TWM I used for quite some time after switching from i3. This is an automatic tiling window manager written and configured mostly in Lua, with its core written in C (this is originally a dwm fork). My configuration for it is documented in detail in its corresponding document, which you can find here.

2.1.3. i3 configuration (Deprecated)

The i3 configuration is detailed in its corresponding README which you can find here. Be aware I do not use i3 anymore, and I will not update it until I may someday use it again. This was deprecated on August 22nd, 2020. Polybar config (Deprecated)

My annotated polybar config can be found here, if you wish to use it. Be aware I do not use polybar anymore, and I will not update it until I may someday use it again. This was deprecated on August 22nd, 2020.

2.2. Text and source code editing

2.2.1. Emacs configuration

Emacs is my main text editor, which I use for almost everything. Because, you know…

Emacs is a great operating system, it just lacks a good text editor.

My current configuration is a vanilla config, meaning I do not rely on another configuration or framework such as Spacemacs or DoomEmacs to configure Emacs. You can find its configuration here.

I used to use a Spacemacs-based configuration, however I deprecated it on October 20th 2021. You can find it here.

2.2.2. Nano (deprecated)

Although it is a very simple piece of software, nano does offer some customization. Mine can be found in my file. Be aware I do not use nano anymore, and I will not update it until I may someday use it again. This was deprecated on August 28th, 2020.

2.2.3. Rustfmt

You can find my Rustfmt configuration here.

2.3. Custom scripts in PATH

I have written some scripts that help me daily accomplish some simple tasks, like mounting and unmounting a drive or Android device, an emoji picker, a utility to set up my Wacom tablet, and so on. You can find them stored in my file along with their detailed explanation in the README placed in the same folder —which is actually their source code once the org-mode file gets tangled.

2.4. Terminal configuration

2.4.1. Fish configuration with useful abbreviations

You can also find in my Fish shell configuration in my file, which contains my usual abbreviations.

2.4.2. Tmux configuration

You can find my tmux configuration in It depends on the submodule .tmux by Gregory Pakosz.

2.5. And some minor configuration files

2.5.1. Global gitignore

Sometimes, there are some lines that always reappear in gitignores. So, instead of always adding them, let git now that some elements are to be ignored by default, hence the $HOME/.gitignore_global file. First, we don’t want nano’s backup files.


And object files and output binaries generated by gcc and the likes aren’t welcome either.


2.5.2. Paru

paru is an AUR helper for Arch Linux which aims to be a replacement for yay. A couple of the options you will see below aim at restoring the behavior of yay in paru. Sudo loop avoids me having to enter again my password if one package takes too much time to compile and/or compress. I know it can be a security issue if someone ever get access to my computer while paru is running, but if it ever happens it will be already concerning enough they managed to. I also make use of my custom script dired so I can use Emacs’ Dired as the file manager for paru.

DevelSuffixes = -git -cvs -svn -bzr -darcs -always

FileManager = dired

3. Installation

For an installation walkthrough of my Arch Linux installation, check out my bootstrap file where I walk you through the first manual steps and through the bootstrap you can execute to automatically take care of a lot of elements.

4. License

All of my dotfiles (and my dotfiles only) are available under the GNU GPLv3 License. Please consult the license file for more information. In short: you are free to access, edit and redistribute all of my dotfiles under the same license and as allowed by the license, and if you fuck up something, it’s your own responsibility.

Author: Lucien Cartier-Tilet


Created: 2023-11-05 Sun 21:50