Skip to content


Folders and files

Last commit message
Last commit date

Latest commit


Repository files navigation


These are the dotfiles referenced in the darnedest thing, and then some.

patch history note

This repo's prior patch history resides with the dotfiles-archive-2023 repo -- which had become quite unwieldly, prompting the generation of this instance. Some folders have been deprecated -- removed with workflow changes and the transition to Alpine Linux.


git clone --depth 1

--depth 1 ensures you do not download the unnecessary patch history which can become extremely large over time. (This repo is re-initialized from time to time to reduce its size).

The root folder name within dotfiles is the application the dotfiles belong to. Below that is the actual home folder path (or subfolders) to the dotfile.

The dotfiles folder is the GNU stow root folder, typically installed in $HOME/dotfiles.


Warning: Backup your configuration files before overwriting!

Create symlinks to application dotfiles with

cd ~/dotfiles
stow <application>


There are several keyboard layouts for the Planck, Splitography, Chimera and Corne keyboards.

BEAKL Wi is the current keyboard in daily use (hence, has the most up-to-date libraries).

What this means is that, while all layouts should compile and flash their appropriate keyboards properly, older source (layouts) libraries -- in particular, the keycode_functions.c and tapdance.c files -- will not incorporate the latest tweaks and fixes to corner case behaviours caught over the course of this site's BEAKL development. This does not mean the older layouts do not work -- they do (with probably the majority of corner cases addressed not likely to be noticed by the user).

See keyboard evaluation for a biased comparison of keyboard layouts!


Many of the configuration files contain custom keybind specifications for various applications and window managers. Note that these are tailored for the Colemake Shift-DH layout -- a custom Colemak variant -- described in the reference url above and use vim mappings (customized) where possible. Redefine these keybinds as required.


  1. Fork it!
  2. Create your feature branch: git checkout -b my-new-feature
  3. Commit your changes: git commit -am 'Add some feature'
  4. Push to the branch: git push origin my-new-feature
  5. Submit a pull request :D


This code is distributed under the terms and conditions of the MIT license.


No description, website, or topics provided.






No releases published