mdebray/tvl-depot
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
tvl-depot/emacs/.emacs.d/wpc/wpc-nix.el

80 lines
3.5 KiB
EmacsLisp
Raw Normal View History

Support nix configuration I suppose it was only a matter of time...
2018-09-04 21:00:18 +02:00
;;; wpc-nix.el --- Nix support -*- lexical-binding: t -*-
;; Author: William Carroll <wpcarro@gmail.com>
;;; Commentary:
;; Configuration to support working with Nix.
Support nix/sly-from-universe This function builds a version of SBCL using `nix.buildLisp` and points `sly` to the built executable. The result is a REPL with access to your project's dependencies, which is quite useful. One drawback at the moment is that if new dependencies are added to the project, I think I need to rebuild SBCL using nix and restart sly.
2020-01-23 23:02:13 +01:00
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Dependencies
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
Rename dotfiles -> briefcase 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-31 16:27:48 +01:00
;; TODO: These may fail at startup. How can I make sure that the .envrc is
;; consulted when Emacs starts?
(prelude/assert (f-exists? (getenv "BRIEFCASE")))
(prelude/assert (f-exists? (getenv "DEPOT")))
Support nix/sly-from-universe This function builds a version of SBCL using `nix.buildLisp` and points `sly` to the built executable. The result is a REPL with access to your project's dependencies, which is quite useful. One drawback at the moment is that if new dependencies are added to the project, I think I need to rebuild SBCL using nix and restart sly.
2020-01-23 23:02:13 +01:00
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Library
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
Support nix configuration I suppose it was only a matter of time...
2018-09-04 21:00:18 +02:00
(use-package nix-mode
:mode "\\.nix\\'")
Consume top-level emacs attribute Refactor `nix/rebuild-emacs` to consume newly defined top-level emacs attribute.
2020-03-04 20:25:13 +01:00
;; TODO(wpcarro): Ensure the sub-process can resolve <briefcase>.
Support emacs fn for rebuilding wpcarros-emacs Call `M-x` `nix/rebuild-emacs` to build and link `wpcarros-emacs`.
2020-02-02 14:45:06 +01:00
(defun nix/rebuild-emacs ()
"Use nix-env to rebuild wpcarros-emacs."
(interactive)
Consume top-level emacs attribute Refactor `nix/rebuild-emacs` to consume newly defined top-level emacs attribute.
2020-03-04 20:25:13 +01:00
(start-process "nix-build/<briefcase/emacs>" "*nix-build/<briefcase/emacs>*"
Include NIX_PATH settings in nix/rebuild-emacs function I'm currently setting NIX_PATH in ~/briefcase/shell.nix. This means when I call `nix/rebuild-emacs` from a buffer that is inside the briefcase directory, the command succeeds because NIX_PATH is properly defined. When I call `nix/rebuild-emacs` from any other location it fails. I'm hard-coding the NIX_PATH in this command so that I can call `nix/rebuild-emacs` from any buffer that is currently active.
2020-03-06 12:23:52 +01:00
"nix-env"
"-I" (format "nixpkgs=%s" (f-expand "~/nixpkgs"))
"-I" (format "depot=%s" (f-expand "~/depot"))
"-I" (format "briefcase=%s" (f-expand "~/briefcase"))
"-f" "<briefcase>" "-iA" "emacs")
Consume top-level emacs attribute Refactor `nix/rebuild-emacs` to consume newly defined top-level emacs attribute.
2020-03-04 20:25:13 +01:00
(display-buffer "*nix-build/<briefcase/emacs>*"))
Support emacs fn for rebuilding wpcarros-emacs Call `M-x` `nix/rebuild-emacs` to build and link `wpcarros-emacs`.
2020-02-02 14:45:06 +01:00
Support nix/home-manager-switch As a part of my plan to reduce my dependence on the shell, I defined an Elisp function to call `home-manager switch` from `M-x`.
2020-03-06 12:22:56 +01:00
(defun nix/home-manager-switch ()
"Use Nix to reconfigure the user environment."
(interactive)
(start-process "nix/home-manager-switch" "*nix/home-manager-switch*"
"home-manager"
"-I" (format "nixpkgs=%s" (f-expand "~/nixpkgs"))
"-I" (format "home-manager=%s" (f-expand "~/home-manager"))
"switch")
(display-buffer "*nix/home-manager-switch*"))
Rename dotfiles -> briefcase 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-31 16:27:48 +01:00
(defun nix/sly-from-briefcase (attribute)
Support nix/sly-from-universe This function builds a version of SBCL using `nix.buildLisp` and points `sly` to the built executable. The result is a REPL with access to your project's dependencies, which is quite useful. One drawback at the moment is that if new dependencies are added to the project, I think I need to rebuild SBCL using nix and restart sly.
2020-01-23 23:02:13 +01:00
"Start a Sly REPL configured with a Lisp matching a derivation
from my monorepo.
This function was taken from @tazjin's depot and adapted for my monorepo.
The derivation invokes nix.buildLisp.sbclWith and is built
asynchronously. The build output is included in the error
thrown on build failures."
(interactive "sAttribute: ")
Rename dotfiles -> briefcase 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-31 16:27:48 +01:00
(lexical-let* ((outbuf (get-buffer-create (format "*briefcase-out/%s*" attribute)))
(errbuf (get-buffer-create (format "*briefcase-errors/%s*" attribute)))
(expression (format "let depot = import <depot> {}; briefcase = import <briefcase> {}; in depot.nix.buildLisp.sbclWith [ briefcase.%s ]" attribute))
Support nix/sly-from-universe This function builds a version of SBCL using `nix.buildLisp` and points `sly` to the built executable. The result is a REPL with access to your project's dependencies, which is quite useful. One drawback at the moment is that if new dependencies are added to the project, I think I need to rebuild SBCL using nix and restart sly.
2020-01-23 23:02:13 +01:00
(command (list "nix-build" "-E" expression)))
Rename dotfiles -> briefcase 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-31 16:27:48 +01:00
(message "Acquiring Lisp for <briefcase>.%s" attribute)
(make-process :name (format "nix-build/%s" attribute)
Support nix/sly-from-universe This function builds a version of SBCL using `nix.buildLisp` and points `sly` to the built executable. The result is a REPL with access to your project's dependencies, which is quite useful. One drawback at the moment is that if new dependencies are added to the project, I think I need to rebuild SBCL using nix and restart sly.
2020-01-23 23:02:13 +01:00
:buffer outbuf
:stderr errbuf
:command command
:sentinel
(lambda (process event)
(unwind-protect
(pcase event
("finished\n"
(let* ((outpath (s-trim (with-current-buffer outbuf (buffer-string))))
(lisp-path (s-concat outpath "/bin/sbcl")))
Rename dotfiles -> briefcase 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-31 16:27:48 +01:00
(message "Acquired Lisp for <briefcase>.%s at %s" attribute lisp-path)
Support nix/sly-from-universe This function builds a version of SBCL using `nix.buildLisp` and points `sly` to the built executable. The result is a REPL with access to your project's dependencies, which is quite useful. One drawback at the moment is that if new dependencies are added to the project, I think I need to rebuild SBCL using nix and restart sly.
2020-01-23 23:02:13 +01:00
(sly lisp-path)))
(_ (with-current-buffer errbuf
(error "Failed to build '%s':\n%s" attribute (buffer-string)))))
(kill-buffer outbuf)
(kill-buffer errbuf))))))
Support nix configuration I suppose it was only a matter of time...
2018-09-04 21:00:18 +02:00
(provide 'wpc-nix)
;;; wpc-nix.el ends here
Reference in a new issue Copy permalink