6ca65d02eb
Since I figured out how to run both KDE and GTK applications with their proper settings under any lightweight window manager, and since I now know how to configure these programs independent of their desktop environments, this commit removes plasma-desktop, with the possibility of gnome-shell bring removed in a future commit as well. The rationale is that using a desktop environment is counter-intuitive when you already use a window manager. Having multiple desktop environments to start a session with is certainly amusing, but not at all practical, especially when you can accomplish anything that needs to be done with any window manager. Switching between GNOME, Plasma, and bspwm also caused some inconsistent X settings that I assume are non-trivial to fix without a proper restart of the X server. Simply starting the Plasma desktop environment will create quite a few files in ~/.config. These files consist of window coordinates and other non-friendly things, which, IMO, should not belong in the *user's* config directory. Regarding other software, GNOME MPV is arguably easier to use and less buggy than baka-mplayer. Manipulating archives is also much easier with file-roller than it is with ark. Since I got Audacity to look decent on a HiDPI display, I no longer have a use for Kwave, which did not have some of the essential features I used in Audacity anyway. l3afpad functions much more like a notepad than kwrite, which is what I'm looking for since I already use Vim. Using Cantata as a mpd client is simply not the same as using ncmpcpp. zathura and evince are more than enough for document viewing, hence the removal of Okular. |
||
|---|---|---|
| .archlinux | ||
| .fedora | ||
| bspwm | ||
| code | ||
| compton | ||
| dunst | ||
| editorconfig | ||
| feh | ||
| fish | ||
| git | ||
| gnome | ||
| gpg | ||
| gtk | ||
| httpie | ||
| kitty | ||
| mpd | ||
| mpv | ||
| ncmpcpp | ||
| neofetch | ||
| neovim | ||
| polybar | ||
| ranger | ||
| rofi | ||
| rtv | ||
| ssh-agent | ||
| sxhkd | ||
| tig | ||
| tmux | ||
| vim | ||
| wal | ||
| xcursor | ||
| xeventbind | ||
| xinit | ||
| xmodmap | ||
| xresources | ||
| yay | ||
| yt-dl | ||
| zathura | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| CHANGELOG.md | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
~/.files
TODO: Screenshots
Usage
Replicate my Arch Linux setup
On a fresh Arch Linux install, run the bootstrap script.
git clone https://github.com/GloverDonovan/.files --depth 1 && ./.files/.archlinux/bootstrap.sh
Replicate my Fedora setup
On a fresh Fedora install, run the bootstrap script.
git clone https://github.com/GloverDonovan/.files --depth 1 && ./.files/.fedora/bootstrap.sh
Use only the dotfiles you want
Method 1. With stow
First, install stow with your package manager. Then, run the following:
make package=kitty
This will symlink my kitty config to your $XDG_CONFIG_HOME. If you want to install a different package, simply replace kitty with the name of the directory you wish to get dotfiles from.
Since stow will only change what it owns, you do not have to worry about any of your existing dotfiles being changed when you use this method.
To uninstall packages, simply use:
make uninstall package=kitty
This will remove the symlink to my kitty config. If you have other kitty files, stow will not remove them, since stow only changes what it owns.
Method 2. Manually
If you already have dotfiles and want to improve them, you can use this repository as a guide. If you find something that makes your dotfiles better, you're free to use it.
If you don't want to use stow, you can simply copy/paste the dotfiles you want to their relevant directories.
Updating
To update your system with any changes I make, you must first verify that the changes I made are actually changes you want. Eventually I want to consider my dotfiles "stable" (i.e. 1.0.0, 2.0.0, etc.) in which only major version upgrades would significantly alter existing functionality, but right now this simply isn't the case.
Once you've verified that you indeed want my changes, update your local copy of the repository like so:
git pull
If you used the stow method, all of the dotfiles that you use from me will already be updated; you do not have to do anything else. If git tells you that there are conflicts, you probably want to rebase your changes on top of mine, or consider making your own version of those files instead.
Downgrading
If for some reason you updated by accident and want existing functionality back, you can simply checkout a previous version or commit.
For example, if your configuration was last known to work at commit a1b2c3d, you would use:
git checkout a1b2c3d