My personal configuration files.
Marty Oehme
6ac552d3d5
Added a simple wayland configuration. Currently set up simple wayland configuration based on river window manager and waybar. Rivercarro is the layout manager, being the same in principle as rivertile, the default layout manager for river, only it comes with smart gaps (gaps turn off if there is only one window open) and monocle mode (give one window all space). Runs `keyd` in the background to replace the old `xcape` capslock switching (capslock is escape and if held control). Uses `swaybg` to set a wallpaper. Added powermenu and lockscreen scripts. Improved lockscreen script to detect and work for wayland. Moved old rofi mode 'powermenu' to more general powermenu script, which works with any rofi-like selector (dmenu, bemenu, wofi, etc.) Loses some of its design quality but since it was wonky anyway, and I rarely see the menu, we could repurpose its functionality for a more general powermenu concept. Currently hardcoded for `bemenu` but can be easily swapped and possibly even extended back to rofi. Fixed file upload link sharing to clipboard. Updated rofi-pass to pass-pick. Made rofi-pass universal and less integrated to rofi - that's also the reason for the name change. `pass-pick` works with rofi (default), bemenu or dmenu. In theory it should also work with any other picker that contains a stdin listing function similar to dmenu. It has been definitely tested both on rofi and bemenu. The best user experience still reigns on rofi, where available keys are displayed on the picker and the keys themselves make the most sense. But all functions can be reached from bemenu as well, though the key mappings are more arbitrary and can not be changed as in rofi. The autofilling tool works with both xdotool and ydotool, so should work both on X11 and on Wayland. Ydotool ideally requires its daemon to be running, otherwise some of the typing may get gut off. Otherwise no change should be necessary. Updated qutebrowser open_download for bemenu. Updated download opening script to work with both rofi and bemenu. Prefers original rofi implementation but works with both, and can be set to use a custom dmenu-like file picker as well. Add brightnessctl and removed custom audio / brightness scripts since they became unnecessary. Updated bootstrap script to include system files: With `keyd` taking its configuration from the `/etc` directory and not home, a second stow stage was necessary. These stow files are in a module called `system-packages` inside the top-level `bootstrap` stow package. They will not be installed by the default dotfile stow invocation but have been integrated as an extra step into the install script. Installing this module requires sudo privileges! Switched vifm überzug to sixel graphics rendering. überzug relies on X11 functionality to work, while sixel does not. Unfortunately, alacritty does not work with sixel graphics yet, only foot does (somewhat). Waybar currently runs the gruvbox dark soft color scheme. Added the old polybar archupdates script to waybar and extended it to output json format with additional metadata that waybar can read. Can still output the old plaintext format that polybar expects. Added a wireguard connection to waybar,shows if currently connected to either a wireguard or tun VPN service. If so, shows an icon in the waybar - that can be hovered over to show the full assigned IP address. Added an upcoming event display to waybar, a simple event indicator to show upcoming events on the calendar, on hovering over it the tooltip lists all upcoming events. Added `screenshot` script to take simple screenshots and rectangle region shots of the current output. Can be invoked through the river shortcut PrintScr: `PrintScr` - Fullscreen screenshot `Mod+PrintScr` - Region screenshot `Shift+PrintScr` - Fullscreen screenshot and file upload `Mod+Shift+PrintScr` - Region screenshot and file upload Extended `sharefile` to take paths through stdin and make use of `fd` if it is found on the system. |
||
|---|---|---|
| .assets | ||
| .githooks | ||
| alacritty/.config/alacritty | ||
| an2linux | ||
| bash | ||
| bibtex | ||
| bootstrap | ||
| disks | ||
| dunst/.config/dunst | ||
| git | ||
| mpv | ||
| nvim/.config/nvim | ||
| pass | ||
| picom/.config/picom | ||
| qutebrowser | ||
| rofi | ||
| rofi-surfraw/.config/rofi-surfraw | ||
| scripts | ||
| services | ||
| sh | ||
| ssh | ||
| styler | ||
| sxhkd | ||
| taskwarrior | ||
| tmux | ||
| vifm/.config/vifm | ||
| wayland | ||
| zathura/.config/zathura | ||
| zsh | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .gitmodules | ||
| .stowrc | ||
| install.sh | ||
| LICENSE | ||
| README.md | ||
~/🌹
What's in these dotfiles
- vim configuration for simple programming tasks (especially go/typescript/python/bash) and prose
- academic workflow tools, to allow quick citation, pdf compilation, and preview
- simple, efficient polybar with package update notification, and spotify (mpris) integration
- tmux session management through
tmandtltools - tmux fuzzy-searching of terminal sessions to switch to with hot-key (
<C-A><C-s>) in addition to normal session switching - system-wide color management (terminals, vim, qutebrowser, polybar, xresources) through
stylercommand using base16 themes - quick theme switching by activating
stylerand fuzzy-searching themes with hot-key (<Super>+F8) - many vim color-schemes with quick light/dark switching (
F8) and individual theme switch (<Space>+F8) - quick directory jumping using z, with fzf integration
- fzf integrations for bibtex citation, vim buffer management, most recently used switching, shell command history, and more
Quick-Start
The dotfiles use GNU stow to link themselves in the home directory. You can clone this repository anywhere (though I have mine in ~/.dotfiles as it seemed most logical for me).
I would recommend doing a git clone --recursive for this repository, since it contains git submodules, which will then automatically get pulled in as well. Of course, you can do it non-recursively and then just pull those modules selectively which you actually want.
Once in the repository directory, when you then run ./install.sh it will install many of the packages I use (though they are probably slightly out-of-date) and link the dotfiles into the home directory.
If you do not want to install any packages, but only link the dotfiles run stow -S */ from the main repository directory.
Since dotfiles management is based on stow, it will not overwrite anything already in the home directory (though you can force it to if you really want, using stow --override='.*' -- I do not recommend this).
After all files are linked and you open a new shell session, the dotlink alias will allow you to re-link all dotfiles from anywhere on the system.1
Both automatic installation paths are presumably somewhat brittle. In any case, I would suggest to manually look through the files for things you want instead of copying and activating everything. Dotfiles are too personal to be standardized like that. They're pets, not cattle. Enjoy!
Main Modules
alacritty- Terminal emulator (GPU accelerated and customizable)i3- Tiling window managerpolybar- Easy to customize statusbarpicom- X11 compositor (maintained fork from compton)git- distributed version control system.pass- Password management suitenvim- Neovim configurationbibtex- LateX/BibteX/pandoc plaintext writing & reference suitequtebrowser- vim-key enabled web browserrofi- Application launcher, dmenu replacementsxhkd- X11 hotkey managertmux- terminal multiplexervifm- vim-like file-manager
Notes
- Generally, most configuration for applications attempts to follow the XDG specifications, keeping configuration in .config directory and supplementary files in .local/share directory. Over time, I am moving more applications to this standard: it keeps the home directory clean, and the separation of configuration, binaries, and data relatively clear.
- The
zshdirectory contains all setup for the z-shell, my daily work environment. It should not be required for working with any other module but will add additional functionality to many (such as command auto-completion and so on).shsets some base functionality for any shell you may wish to work in. It is, for now, the only module that is required for some other modules to work.2 roficontains additional scripts and a simple theming framework for rofi and should probably be reorganized to put the correct files into the correct directories (per xdg) at some point.- Whereas
shmodule scripts are requirements for other scripts,.local/binin thescriptsmodule contains most executable user scripts. Most of these have been migrated to other corresponding modules (e.g. if a script exclusively targets git functionality, it will live there), some useful --- or left-over --- stand-alone scripts remain however. .local/share/pandoccontains configuration for academic latex writing (pandoc, really) and is of interest if you want to use this functionality..xinitrcis used for x initialization and program startup. At some point, some of the consistently running applications may be moved to systemd/runit as supervised services.- Generally, top-level directories starting with a . are only meaningful for the repository not for the functionality of the machine that these dotfiles are deployed on. That means
.gitlab-ci.yml,.assets/,.stowrcand similar files and directories will not show up in the final deployment in any home directory. Perhaps they should be called dotdot-files since they're the dotfiles for my dotfiles. 🙂 (Also, 'dotfiles'.)
-
This alias only works when the dotfiles are cloned into
~/.dotfiles, mirroring my setup. This is due to a hard-coded cd into this directory. If your dotfiles lie in another directory and you want to use the dotlink alias, simply change the corresponding line inbootstrap/.config/sh/alias.d/dotlink.sh] ↩︎ -
I may remove this requirement in the future to make modules more self-contained. However, relying on some base utility scripts makes it easier to avoid duplicating such functionality for each individual script in other modules. ↩︎