;; Run the compilation for each project in a buffer that contains the project name.
;;
;; This works, but I use direnv, and for some reason all the *compilation*
;; buffers seem to share a common direnv environment. I.e., whenever I switch
;; between *compilation* buffers, I have to `M-x direnv-update-environment`
;; before I can compile in it.
(setq compilation-buffer-name-function
      (lambda (compilation-mode)
	(concat "*" (downcase compilation-mode) "*<" (projectile-project-name) ">")))

;; When compiling, only ask to save buffers for the project getting compiled.
;;
;; This doesn't work at all. The problem is that this gets called like
;;
;;     (with-current-buffer <unsaved-file-buffer>
;;       (funcall compilation-save-buffers-predicate))
;;
;; which means that this always returns `t`, since `(projectile-project-root)`
;; is relative to `(current-buffer)`. To complain about Emacs a bit I wish
;; `(current-buffer)` referred to the *compilation* buffer, and the
;; unsaved-file-buffer was passed as a parameter ... this is a thunk for no good
;; reason, AFAICT.
;;
;; Since the *compilation* buffers are now named based on the project, I don't
;; see how I can find the correct projectile-project-root. E.g.,
;;
;;     (let ((root (with-current-buffer "*compilation*" (projectile-project-root)))) ...)
;;
;; could approximate it if I wasn't trying to distinguish the buffers.
(setq compilation-save-buffers-predicate
      (lambda ()
	(let ((root (projectile-project-root)))
	  (or (not root)
	      (projectile-project-buffer-p (current-buffer) root)))))

(with-current-buffer (window-buffer) (projectile-project-root))