https://github.com/seizeop/dots
Personal dotfiles repo
https://github.com/seizeop/dots
bash cava css dotfiles dracula elisp emacs emacs-lisp evil greyscale hyprland jsonc orgmode rofi waybar wayland
Last synced: 6 months ago
JSON representation
Personal dotfiles repo
- Host: GitHub
- URL: https://github.com/seizeop/dots
- Owner: SeizeOP
- License: mit
- Created: 2025-05-16T22:24:42.000Z (10 months ago)
- Default Branch: main
- Last Pushed: 2025-09-11T22:07:52.000Z (6 months ago)
- Last Synced: 2025-09-12T00:27:02.727Z (6 months ago)
- Topics: bash, cava, css, dotfiles, dracula, elisp, emacs, emacs-lisp, evil, greyscale, hyprland, jsonc, orgmode, rofi, waybar, wayland
- Language: Python
- Homepage: https://seizeop.github.io
- Size: 12.3 MB
- Stars: 0
- Watchers: 1
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.org
- License: LICENSE
Awesome Lists containing this project
README
#+author: Henry Davies
#+title: Dotfiles README
Personal Configuration File (Dotfile) Repository.
Files which end in the =org= file extension are orgmode literate configs, and do not contain the actual config files for a given program. Rather these orgmode files contain source code blocks which are tangled or pushed to the proper config files on demand. To reduce confusion, the =org= files in each subdirectory has been named according to the program it relates to.
For example:
- the Hyprland config is named: =hyprland.org=
- the Waybar config is named: =waybar.org=
One notable exeption to this naming convention is, I have named my emacs config ~README.org~ instead of ~emacs.org~. The reason I have named the emacs this way is because Github only automatically expands orgmode or markdown files if they are named README, and given the complexity of my emacs config I wanted the orgmode document to auto expand for better readability.