It appears that (auto-fill-mode 1) may be buffer-local. Adding a hook to
fundamental-mode to ensure auto-fill-mode is enabled for most buffers. Stay
tuned, because this may need to be setup for prog-mode-hook as well. Or
neither... we'll see what works.
Sometimes just capturing what I want to buy is as satisfying as actually buying
the item. These org-capture templates really alleviate a lot of the anxiety I
associate with trying to remember many things.
This allows configuration for device specific settings - usually or
perhaps exclusively hardware related. Supporting disabling laptop
touchscreen, increasing laptop cursor speed, reversing the scroll
direction of the laptop mouse.
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.
Some of the information herein was useful when I supported OSX, but no
longer necessary. Other information is encoded into the config files
herein and is less useful in written form in the README.
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.
My Emacs installation would fail on new machines because:
* use-package
* evil
* paredit
use-package is needed to install everything else.
evil and paredit were required in functions.el and other places before they were
called like (use-package evil ...). This should improve things but not fix the
entire issue.
Removing more files that clutter my `gst`
This time I ran...
```bash
git rm -r --cached .
```
...which is supposed to help ignore files that `git` already tracks. This may be
the missing piece I've been looking for.
After yet another unpleasant experience starting up GPG on a new system, I
decided to encode my learnings and mistakes as aliases, functions, scripts,
hoping to protect my future me from myself. Fingers crossed!
I've been sloppily managing my fonts for awhile. At this point in time,
it seems reasonable to carry around ttf, otf, and other font files.
These are 4.0K in size anyhow, which doesn't seem burdensome to me for
the convenience I get in return.
Lists the packages installed by `nix-env`. Moving forward, it might be
useful to run something like...
`$ nix_installed >nix-env.txt`
...and commit that to this repository a la the brew.txt file that
previously floated around this repo. For now, I'm unwilling to commit to
that solution, because I'm hoping a better alternative exists.
Perhaps this should be an alias. Still unsure why I write aliases
sometimes and functions other times. It might be worth documenting as a
principle that I can lean on.
Supports ZSH themes based on which device I'm working. This might get
annoying after awhile, but I think the idea of having the prompt reflect
when I'm on a different machine than my own might be useful.
Adds "cloudtop" alias in ssh config.
In the future, this may more to Network FS like Dropbox or x20,
or Google Drive. For now, I'm keeping this here. I'd like to add
a Rofi integration in the future that will allow me to quickly
copy or insert this entries.
I documented my consumption of wpcarro/dotfiles in the README. The dream
is to just clone this repo and run `make install`. We'll get there.
TODO: drop support for OSX
TODO: clean up the rest of this README
I have the (package-initialize) call already in wpc-package.el.
I'm unsure how this removal is ending up in a git status because I'm
pretty sure I've never commited that to this repo. Need to tighten
things up I guess.
This repo's history seems to reflect my difficult wrestling with
Git, GitHub, gitignore files. I'm still not sure I understand
everything that's going on.
