52d284f59d
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.
42 lines
1.4 KiB
EmacsLisp
42 lines
1.4 KiB
EmacsLisp
;;; wpc-ocaml.el --- Tooling preferences for Go -*- lexical-binding: t -*-
|
|
;; Author: William Carroll <wpcarro@gmail.com>
|
|
|
|
;;; Commentary:
|
|
;; Tooling support for golang development.
|
|
|
|
;;; Code:
|
|
|
|
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
|
|
;; Dependencies
|
|
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
|
|
|
|
(require 'prelude)
|
|
|
|
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
|
|
;; Configuration
|
|
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
|
|
|
|
;; TODO: Support jumping to go source code for fmt.Println, etc.
|
|
|
|
;; I'm unsure if this belongs in wpc-golang.el because it's a generic setting,
|
|
;; but because go is the first languages I've encountered that enforces tab
|
|
;; usage (I think) I'm configuring it.
|
|
(setq-default tab-width 4)
|
|
|
|
(use-package go-mode
|
|
:config
|
|
(setq gofmt-command "goimports")
|
|
;; TODO: Consider configuring `xref-find-definitions' to use `godef-jump'
|
|
;; instead of shadowing the KBD here.
|
|
(general-define-key
|
|
:states '(normal)
|
|
:keymaps '(go-mode-map)
|
|
"M-." #'godef-jump)
|
|
;; Support calling M-x `compile'.
|
|
(add-hook 'go-mode-hook (lambda ()
|
|
(set (make-local-variable 'compile-command)
|
|
"go build -v")))
|
|
(add-hook-before-save 'go-mode-hook #'gofmt-before-save))
|
|
|
|
(provide 'wpc-golang)
|
|
;;; wpc-ocaml.el ends here
|