about summary refs log tree commit diff
path: root/configs/install
AgeCommit message (Collapse)AuthorFilesLines
2020-01-31 Rename dotfiles -> briefcaseWilliam Carroll1-1/+1
Renaming my mono-repo briefcase. I first introduced this commit in master, but it introduced a bug where one of two things would happen: 1. Emacs wouldn't start and would crash X. 2. Emacs would start but my keyboard wouldn't work. I learned some valuable debugging skills in the process. Here are some of them: When my keyboard was broken, I wanted to control my computer using my laptop. Thankfully this is possible by using `x2x`, which forward X events from the SSH client to the SSH host. ```shell > # I'm unsure if this is the *exact* command > ssh -X desktop x2x -west :0.0 ``` Git commit-local bisecting. I didn't need to do a `git bisect` because I knew which commit introduced the bug; it was HEAD, master. But -- as you can see from the size of this commit -- there are many changes involved. I wanted to binary search through the changes, so I did the following workflow using `magit`: - git reset --soft HEAD^ - git stash 1/2 of the files changed - re-run `nix-env -f ~/briefcase/emacs -i` - restart X session - If the problem persists, the bug exists in the non-stashed files. Repeat the process until you find the bug. In my case, the bug was pretty benign. Calling `(exwm/switch "Dotfiles")` at the bottom of `window-manager.el` was failing because "Dotfiles" is the name of a non-existent workspace; it should've been `(exwm/switch "Briefcase")`. There may have been more problems. I changed a few other things along the way, including exposing the env vars BRIEFCASE to `wpcarros-emacs` inside of `emacs/default.nix`. The important part is that this was a valuable learning opportunity, and I'm glad that I'm walking away from the two days of "lost productivity" feeling actually productive.
2020-01-29 Support env vars for {DESK,LAP,CLOUD}TOP devicesWilliam Carroll1-6/+3
I recently changed my hostname for my desktop and laptop from wpcarro.lon.corp.google.com -> zeno.lon.corp.google.com wpcarro2 -> seneca If you're curious, the names Zeno and Seneca come from famous Stoic philosophers. As you can see from this commit, my configuration depends on the values of these hostnames. Immediately impacted: - .profile - device.el Not immediately impacted: - configs/install - configs/uninstall - .ssh/config - .zshrc* * As a side note, I should stop supporting ZSH. Using an .envrc file helps me DRY up some of my configuration. Ideally I should only need to make changes to the .envrc file and then expect everything to work as expected. Let's see how that goes.
2019-12-24 Massive configuration overhaulWilliam Carroll1-5/+8
Currently paying the price of months of non-diligent git usage. Here's what has changed. - Theming support in Gvcci and wpgtk - Dropping support for i3 - Supporting EXWM - Many Elisp modules - Collapsed redundant directories in ./configs
2019-03-18 wpcarro.roam.googlers.com -> wpcarroWilliam Carroll1-1/+1
Until I change my hostname, I'll need to use wpcarro. Internally on Google networks, this laptop is resolvable via wpcarro.roam.* Idea: consider defining in ~/.profile: DESKTOP_NAME=<name> LAPTOP_NAME=<name> CLOUDTOP_NAME=<name> ...and then refer to these environment variables throughout my configuration that depends on them. E.g. - - configs/install - configs/uninstall - .zshrc - .ssh/config For now, I'll stick with the path of least resistance.
2019-03-18 Drop OSX support; support desktop, laptop, cloudtopWilliam Carroll1-5/+11
Dropping support for OSX. Moving forward these dotfiles will depend on Linux systems. Furthermore, since I'm support a ~/bin, the machines that consume these dotfiles depend on i386 architectures. Linux and i386 are two dependencies that I'm okay with since the leverage this assumption provides, makes their existence tolerable. There is some Google leakage herein, which includes aliases, functions, and mentions of cloudtop. For now, this is okay. I may break the Google specific code into its own repository, but for now, this is less maintenance. This also introduces a ~/.profile instead of erroneously defining environment variables in my zshrc file, which was unadvised. This is a large commit and also introduces new aliases, variables, functions that I accumulated over the past week or so while migrating away from OSX and onto my new setup. Hopefully in the future I'll be more precise with my commits.
2019-03-16 Support uninstall; setup -> installWilliam Carroll1-0/+11
- support uninstall in Makefile - change setup script name to install