depot - monorepo for the virus lounge

Age	Commit message (Collapse)	Author	Files	Lines
2020-08-31	Lint string, macros.el	William Carroll	1	-1/+2
	More of the same type of linting... basically preferring `namespace-` instead of `namespace/`.
2020-08-31	Lint wpc-golang.el	William Carroll	1	-2/+6
	- change wpc-ocaml.el to wpc-golang.el - Add Version, URL, Package-Requires sections
2020-02-07	Remove assertions that prelude/executable-exists?	William Carroll	1	-3/+0
	I'm in the midst of transitioning onto a few new tools. My previous workflow just used `nix-env` to install some packages. I didn't have a prescribed methodology for which packages I would install using `nix-env` and which ones I would install using `sudo apt-get install`. Sometimes if a package would be available in my aptitude repositories, I'd use that; other times when it wasn't available I'd use `nix-env`. One complication about being on gLinux intead of NixOS is that some packages (e.g. nixpkgs.terminator) is available via `nix-env -iA nixpkgs.terminator`, but the installation won't actually run on my gLinux. In these instances, I would install terminator from the aptitude repositories. Then @tazjin introduced me to his Emacs configuration that he builds using Nix. What appealed to me about his built Emacs is that it worked as expected on either a NixOS machine and on gLinux (and presumably on other non-NixOS machines as well). A setup towards which I'm working is to own one or a few NixOS machines whose configurations are entirely managed with Nix. On devices like my work machines, which cannot run NixOS, I can build as much of the software that I need using Nix and attempt to minimize the ad hoc configuration either with shell scripts, python, golang, or more Nix code... it's clear that I still don't have a clear idea of how that part will work. For now, I'm adopting nix, nix-env, lorri, direnv, and weening off of aptitude as much as I can. Things are a bit messy, but my general trend feels positive. Stay tuned for more updates.
2020-02-05	Temporarily disable initialization code	William Carroll	1	-1/+0
	My Emacs initialization fails for a few reasons, which I haven't prioritized time to investigate yet: - Some OCaml deps are absent - godoc is absent
2020-02-05	Further configure Go tooling	William Carroll	1	-0/+23
	- Prefer goimports to gofmt. goimports calls gofmt; it also adds and removes dependencies. - Assert the presence of goimports, godoc, godef - KBD godef to M-. - Support the M-x compile command for calling `go build -v`
2020-01-31	Support golang	William Carroll	1	-0/+23
	I decided to start writing go code for scripts instead of python. I think this will be a learning opportunity for me and should increase the integrity of my scripts by adding some static type checking.