tvl-depot/users/tazjin/emacs/config/init.el

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

263 lines
6.9 KiB
EmacsLisp
Raw Normal View History

;;; init.el --- Package bootstrapping. -*- lexical-binding: t; -*-
;; Disable annoying warnings from native compilation.
(setq native-comp-async-report-warnings-errors nil
warning-suppress-log-types '((comp)))
;; Packages are installed via Nix configuration, this file only
;; initialises the newly loaded packages.
(require 'use-package)
(require 'seq)
(package-initialize)
;; Initialise all packages installed via Nix.
(use-package ace-window
:bind (("C-x o" . ace-window))
:config
(setq aw-keys '(?f ?j ?d ?k ?s ?l ?a)
aw-scope 'frame))
(use-package auth-source-pass :config (auth-source-pass-enable))
(use-package avy
:bind (("M-j" . avy-goto-char)
("M-p" . avy-pop-mark)
("M-g g" . avy-goto-line)))
(use-package browse-kill-ring)
refactor(tazjin/emacs): ivy,swiper,counsel -> vertico,consult vertico and consult are more modern versions of interactive narrowing helpers, as those implemented by ivy and its related packages. The primary differences (and what I care about here) is that they are more focused on integration with the core Emacs primitives, rather than building an ecosystem around them. For example: * vertico enhances `completing-read' and friends, but does not attempt to provide its own ecosystem of functions to *trigger* completions. * vertico integrates with the default `completion-style' system, meaning that I can continue to use things like prescient without extra packages that integrate it with vertico * consult does not rely on vertico or any other specific completion framework (such as counsel/swiper do with ivy), and simply implements its functions using completing-read This reduces the overall amount of code in the dependency closure and leads to a less special setup. Functionality is basically equivalent, except for two things which counsel came with that I will need to substitute: * counsel-notmuch (actually this was a separate package, but I didn't use it much anyways, so just ignoring it for now) * counsel-linux-app (opening desktop shortcuts, this I will need to make) As a side note, consult notes "This package is a part of GNU Emacs", but it doesn't seem to be the case. Change-Id: Ia046b763bf3d401b505e0f6393cfe1ccd6f41293 Reviewed-on: https://cl.tvl.fyi/c/depot/+/9155 Tested-by: BuildkiteCI Reviewed-by: tazjin <tazjin@tvl.su>
2023-08-27 00:12:29 +02:00
(use-package consult
:bind
("C-c r g" . consult-ripgrep)
("C-s" . consult-line))
(use-package dash)
(use-package gruber-darker-theme)
(use-package eglot
:custom
(eglot-autoshutdown t)
(eglot-send-changes-idle-time 0.3))
(use-package ht)
(use-package hydra)
(use-package idle-highlight-mode :hook ((prog-mode . idle-highlight-mode)))
(use-package multiple-cursors)
(use-package notmuch
:custom
(notmuch-search-oldest-first nil)
(notmuch-show-all-tags-list t)
(notmuch-hello-tag-list-make-query "tag:unread"))
2018-06-28 11:01:54 +02:00
(use-package paredit :hook ((lisp-mode . paredit-mode)
(emacs-lisp-mode . paredit-mode)))
(use-package pinentry
:config
(setq epa-pinentry-mode 'loopback)
(pinentry-start))
(use-package prescient
refactor(tazjin/emacs): ivy,swiper,counsel -> vertico,consult vertico and consult are more modern versions of interactive narrowing helpers, as those implemented by ivy and its related packages. The primary differences (and what I care about here) is that they are more focused on integration with the core Emacs primitives, rather than building an ecosystem around them. For example: * vertico enhances `completing-read' and friends, but does not attempt to provide its own ecosystem of functions to *trigger* completions. * vertico integrates with the default `completion-style' system, meaning that I can continue to use things like prescient without extra packages that integrate it with vertico * consult does not rely on vertico or any other specific completion framework (such as counsel/swiper do with ivy), and simply implements its functions using completing-read This reduces the overall amount of code in the dependency closure and leads to a less special setup. Functionality is basically equivalent, except for two things which counsel came with that I will need to substitute: * counsel-notmuch (actually this was a separate package, but I didn't use it much anyways, so just ignoring it for now) * counsel-linux-app (opening desktop shortcuts, this I will need to make) As a side note, consult notes "This package is a part of GNU Emacs", but it doesn't seem to be the case. Change-Id: Ia046b763bf3d401b505e0f6393cfe1ccd6f41293 Reviewed-on: https://cl.tvl.fyi/c/depot/+/9155 Tested-by: BuildkiteCI Reviewed-by: tazjin <tazjin@tvl.su>
2023-08-27 00:12:29 +02:00
:config
(prescient-persist-mode)
(setq completion-styles '(basic prescient)))
(use-package rainbow-delimiters :hook (prog-mode . rainbow-delimiters-mode))
(use-package rainbow-mode)
(use-package s)
(use-package string-edit-at-point)
(use-package term-switcher)
(use-package undo-tree
:config (global-undo-tree-mode)
:custom (undo-tree-auto-save-history nil))
(use-package uuidgen)
(use-package which-key :config (which-key-mode t))
;;
;; Applications in emacs
;;
(use-package magit
:bind ("C-c g" . magit-status)
:config (setq magit-repository-directories '(("/home/tazjin/projects" . 2)
("/home/tazjin" . 1))))
(use-package password-store)
(use-package restclient)
(use-package vterm
:custom
(vterm-shell "fish")
(vterm-kill-buffer-on-exit t))
;; vterm removed the ability to set a custom title generator function
;; via the public API, so this overrides its private title generation
;; function instead
(defun vterm--set-title (title)
(rename-buffer
(generate-new-buffer-name
(format "vterm<%s>"
(s-trim-left
(s-chop-prefix "fish" title))))))
;;
;; Packages providing language-specific functionality
;;
(use-package cargo
:hook ((rust-mode . cargo-minor-mode)
(cargo-process-mode . visual-line-mode))
:bind (:map cargo-mode-map ("C-c C-c C-l" . ignore)))
(use-package dockerfile-ts-mode)
(use-package erlang
:hook ((erlang-mode . (lambda ()
;; Don't indent after '>' while I'm writing
(local-set-key ">" 'self-insert-command)))))
(use-package f)
(use-package go-mode
:bind (:map go-mode-map ("C-c C-r" . recompile))
:hook ((go-mode . (lambda ()
(setq tab-width 2)
(setq-local compile-command
(concat "go build " buffer-file-name))))))
(use-package haskell-mode)
(use-package ielm
:hook ((inferior-emacs-lisp-mode . (lambda ()
(rainbow-delimiters-mode-enable)))))
(use-package jq-mode
:config (add-to-list 'auto-mode-alist '("\\.jq\\'" . jq-mode)))
(use-package kotlin-mode
:hook ((kotlin-mode . (lambda ()
(setq indent-line-function #'indent-relative)))))
(use-package markdown-mode
:config
(add-to-list 'auto-mode-alist '("\\.markdown\\'" . markdown-mode))
(add-to-list 'auto-mode-alist '("\\.md\\'" . markdown-mode)))
(use-package markdown-toc)
(use-package nix-mode
:hook ((nix-mode . (lambda ()
(setq indent-line-function #'nix-indent-line)))))
(use-package nix-util)
(use-package nginx-mode)
(use-package rust-mode)
(use-package sly
:hook ((sly-mrepl-mode . (lambda ()
(paredit-mode)
(rainbow-delimiters-mode-enable))))
:config
(setq common-lisp-hyperspec-root "file:///home/tazjin/docs/lisp/"))
(use-package telega
:bind (:map global-map ("s-c" . (lambda (p) (interactive "P")
(if p (call-interactively #'telega-chat-with)
(telega))))
:map telega-chat-button-map ("a" . ignore))
:config (telega-mode-line-mode 1)
:custom
(telega-emoji-use-images nil)
(telega-completing-read-function #'completing-read))
(use-package terraform-mode)
(use-package toml-ts-mode)
(use-package treecrumbs
:hook ((yaml-ts-mode . treecrumbs-mode)))
(use-package tvl)
refactor(tazjin/emacs): ivy,swiper,counsel -> vertico,consult vertico and consult are more modern versions of interactive narrowing helpers, as those implemented by ivy and its related packages. The primary differences (and what I care about here) is that they are more focused on integration with the core Emacs primitives, rather than building an ecosystem around them. For example: * vertico enhances `completing-read' and friends, but does not attempt to provide its own ecosystem of functions to *trigger* completions. * vertico integrates with the default `completion-style' system, meaning that I can continue to use things like prescient without extra packages that integrate it with vertico * consult does not rely on vertico or any other specific completion framework (such as counsel/swiper do with ivy), and simply implements its functions using completing-read This reduces the overall amount of code in the dependency closure and leads to a less special setup. Functionality is basically equivalent, except for two things which counsel came with that I will need to substitute: * counsel-notmuch (actually this was a separate package, but I didn't use it much anyways, so just ignoring it for now) * counsel-linux-app (opening desktop shortcuts, this I will need to make) As a side note, consult notes "This package is a part of GNU Emacs", but it doesn't seem to be the case. Change-Id: Ia046b763bf3d401b505e0f6393cfe1ccd6f41293 Reviewed-on: https://cl.tvl.fyi/c/depot/+/9155 Tested-by: BuildkiteCI Reviewed-by: tazjin <tazjin@tvl.su>
2023-08-27 00:12:29 +02:00
(use-package vertico
:config
(vertico-mode))
(use-package web-mode)
(use-package yaml-ts-mode)
(use-package zoxide)
(use-package passively
:custom
(passively-store-state "/persist/tazjin/known-russian-words.el"))
;; Note taking configuration for deft.
(use-package deft
:custom
(deft-directory "/persist/tazjin/deft/")
(deft-extensions '("md" "org" "txt"))
(deft-default-extension "md"))
(use-package zetteldeft
:custom
;; Configure for Markdown
(zetteldeft-link-indicator "[[")
(zetteldeft-link-suffix "]]")
(zetteldeft-title-prefix "# ")
(zetteldeft-list-prefix "* "))
;; Initialise midnight.el, which by default automatically cleans up
;; unused buffers at midnight.
(require 'midnight)
(defgroup tazjin nil
"Settings related to my configuration")
(defcustom depot-path "/depot"
"Local path to the depot checkout"
:group 'tazjin)
;; Configuration changes in `customize` can not actually be persisted
;; to the customise file that Emacs is currently using (since it comes
;; from the Nix store).
;;
;; The way this will work for now is that Emacs will *write*
;; configuration to the file tracked in my repository, while not
;; actually *reading* it from there (unless Emacs is rebuilt).
(setq custom-file (f-join depot-path "users" "tazjin" "emacs" "config" "custom.el"))
2019-12-14 18:15:18 +01:00
(load-library "custom")
(defvar home-dir (expand-file-name "~"))
;; Seed RNG
(random t)
;; Load all other Emacs configuration. These configurations are
;; added to `load-path' by Nix.
(mapc 'require '(desktop
mail-setup
look-and-feel
functions
settings
bindings
eshell-setup))
(ace-window-display-mode)
;; If a local configuration library exists, it should be loaded.
;;
;; This can be provided by calling my Emacs derivation with
;; `withLocalConfig'.
(if-let (local-file (locate-library "local"))
(load local-file))
(require 'dottime)
(provide 'init)