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.
As you can see, I personally use fish as my shell of choice, and Emacs 27.0.90 (custom build) using Spacemacs (still with Emacs keybinding in Insert mode but with Evil in Normal mode) as my main text editor.
When it comes to my graphical UI, I do not have any desktop environment. Instead, I have two tiling window managers. The historical first on my configuration is i3-gaps, an i3 fork by Airblader with which I use two bars generated by Polybar. My other TWM, and the one I use most often, is AwesomeWM. Both TWMs use pywal to define their color scheme, as well as rofi’s color scheme.
Finally, you can find my configuration for my Ergodox keyboard here. It is optimized for usage with the Bépo layout set as a software layout, and for shortcuts from i3.
Emacs configuration perfectly tailored for my own use
Beautiful and comfy i3 and polybar configuration
And enough information below to get basically the same distro install as I have on my main computer and my travel laptop.
Most of the org files you will find in this repos are the actual source code
of much of my config files. For instance, the bootstrap found in
installation.org exports almost all of its code snippets to
.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.
AwesomeWM is the TWM I use the most on my computer between itself and i3. My configuration for it is documented in detail in its corresponding document, which you can find here.
The i3 configuration is detailed in its corresponding README which you can find here.
Regarding GTK2, I have only one configuration file: the filechooser’s configuration file.
The first option alows me to open the file chooser in the current working directory:
Next, setting the location mode to
path-bar will show the path as buttons
that can be clicked rather than the full path.
With this configuration, by default we won’t see hidden files.
And we'll also see the size of the visible files.
Now, let’s choose the geometry of our file picker. These two first lines set where the file picker appears:
And these two describe the size of the window:
With these two lines, we set how our files are sorted: by name, and in the ascending order.
Our default view mode is a list of files:
And finally, setting our icon view scale to
-1 sets the icon view to the
The following file helps me choosing the aspect of various GTK+ 3 software, including their theme and icons. First, let’s declare the header:
Now, let’s hint to GTK that I prefer dark themes. This can have an influence also on some websites that can detect this preference and therefore set their own theme to dark by themselves.
gtk-application-prefer-dark-theme = true
Next, the icon theme is the Flat Remix Dark icon theme:
gtk-icon-theme-name = Flat-Remix-Dark
Now, the general theme for GTK3 is Arc Dark.
gtk-theme-name = Arc-Dark
gtk-can-change-accels = 1
gtk-xft-antialias=1 gtk-xft-hinting=1 gtk-xft-hintstyle=hintslight # gtk-xft-rgba=rgb
Since window decorations are handled by my WMs, I will leave this variable empty.
Picom is a standalone compositor for Xorg, and the successor to Compton, itself successor to xcompmgr-dana, itself a fork of xcompmgr. You can find my Picom configuration here.
My Xresources file is very short. Indeed, it only contains two lines which
are dedicated to my
st terminal to set its font and shell. The font is set
st.font: Fantasque Sans Mono:size=10:antialias=true
I can also set the transparency of st (my terminal emulator) like so:
I used to have lines dedicated to UXTerm and URxvt, but I cast them out of my system.
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.
Although it is a very simple piece of software, nano does offer some customization. Mine can be found in my nano.org file.
You can find my Rustfmt configuration here.
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 .local/bin 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.
You can also find in my Fish shell configuration in my fish.org file, which contains my usual abbreviations.
This file gets inserted automatically at the end of my emails.
Lucien “Phundrak” Cartier-Tilet https://phundrak.com (Français) https://phundrak.com/en (English) Sent from GNU/Emacs
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 ~/.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
Of course, some dependencies are needed for my dotfiles to work well. Here is a non-exhaustive list of software needed by these configuration files:
GNU/Emacs >= 26.2
Rust (stable and nightly)
And a bunch of other stuff, see below
And some other stuff scattered around in my dotfiles.
BTW, I use Arch.
For an installation walkthrough of my Arch Linux installation, check out my installation.org 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.
All of my dotfiles (and my dotfiles only) are available under the GNU GPLv3 Licence. Please consult /phundrak/dotfiles/src/branch/master/org/config/LICENCE.md for more information. In short: you are free to access, edit and redistribute all of my dotfiles under the same licence and as allowed by the licence, and if you fuck up something, it’s your own responsibility.