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

23 lines
471 B
EmacsLisp
Raw Normal View History

Massive configuration overhaul Currently paying the price of months of non-diligent git usage. Here's what has changed. - Theming support in Gvcci and wpgtk - Dropping support for i3 - Supporting EXWM - Many Elisp modules - Collapsed redundant directories in ./configs
2019-10-09 13:13:56 +02:00
;; load order is intentional
fix(wpcarro/emacs): Ensure debug-on-error is globally set I'm still a bit confused about the nuances between the myriad of ways to handle variables in Emacs... - `setq` - `setq-default` - `setq-local` - `defvar` - `defcustom` - `defconst` - `customize-set-variable` - `make-local-variable` - `make-variable-buffer-local` - `kill-local-variable` ...but after running some experiments, this triggers the Emacs debugger when an error is encountered (e.g. either *in* `init.el` or another package that is evaluated during `init.el`'s evaluation). Change-Id: I00d543735b1d816462ba18bad23867865d7af80e Reviewed-on: https://cl.tvl.fyi/c/depot/+/4812 Tested-by: BuildkiteCI Reviewed-by: wpcarro <wpcarro@gmail.com> Autosubmit: wpcarro <wpcarro@gmail.com>
2021-11-09 19:43:06 +01:00
(setq-default debug-on-error t)
General Elisp linting TL;DR: - Remove `require` statements from init.el - Remove unused, auto-install KBDs for bookmark.el - Remove unused `require` statements from clipboard - Remove unused, commented-out code I would like for an Elisp linting stage to test for unused `require` statements, but I'm unsure how practical that is to support.
2020-09-02 15:09:15 +02:00
(require 'wpc-package)
Massive configuration overhaul Currently paying the price of months of non-diligent git usage. Here's what has changed. - Theming support in Gvcci and wpgtk - Dropping support for i3 - Supporting EXWM - Many Elisp modules - Collapsed redundant directories in ./configs
2019-10-09 13:13:56 +02:00
(require 'wpc-misc)
Configure ssh preferences Every Tuesday I work from Google's 6PS office instead of BEL. I work from my laptop, which often requires that I ssh into the desktop work station in BEL. I have settled on a locally optimal workflow that I'd like to improve. To help seek higher ground, I'm planning on using ssh.el to configure tramp and define utility functions to lower my cost of exploring new workflows. - Defines a function, `ssh/desktop-cd-home` that helps me quickly open a dired buffer for my work station's home directory. - Documents some variables that I set weeks ago. - Requires ssh.el in init.el.
2020-02-18 12:18:02 +01:00
(require 'ssh)
Massive configuration overhaul Currently paying the price of months of non-diligent git usage. Here's what has changed. - Theming support in Gvcci and wpgtk - Dropping support for i3 - Supporting EXWM - Many Elisp modules - Collapsed redundant directories in ./configs
2019-10-09 13:13:56 +02:00
(require 'keyboard)
Support Freenode IRC Previously my ERC setup just supported Google's internal IRC. Now I have Freenode for things like #nixos, #emacs. This complicated my KBDs for cycling through IRC channels since certain channels only exist on certain servers. To remedy this, I introduced a temporary solution that looks up the server given a particular channel. This isn't ideal, but it works for now.
2019-12-24 14:38:06 +01:00
(require 'irc)
Begin the Emacs email journey While this commit isn't much (i.e. notmuch), it represents one brave step forward in the quest for supporting email in Emacs -- something I'm estimating to be somewhere between a 1.5x and 2x workflow booster.
2019-12-23 11:55:21 +01:00
(require 'email)
Require keybindings.el after wpc-keybindings.el keybindings.el calls (require 'evil-ex), which I introduced in this commit... 0456a1c4b4405da2681296b2250681454637d80f ...calling (require 'evil-ex) loads evil. When evil is loaded before evil-want-integration is set to nil, evil-collection writes to *Warnings* when Emacs initializes, which I find noisy. This commit ensures the evil-want-integration is set to nil before evil is loaded, which appeases evil-collection and thus removes the warning message. Bonus: If you git checkout the previous commit, and attempt to run the KBDs... - `SPC g s`: magit-status - `s h`: evil-window-vsplit ...from a buffer whose major-mode is dired-mode, you should notice that the above functions won't execute. Strangely though, if you look at this commit... 37f8ca04f29ea9bf988b2277c42f3e264d7a89e1 ...I fixed these issues. Well I introduced a regression when I added 0456a1c. My current guess is that when evil-collection complains about evil-want-integration, it is breaking the evaluation sequence of my init.el file. wpc-dired.el is downstream from wpc-keybindings.el, which requires evil-collection. Perhaps no modules required after wpc-keybindings.el are evaluated after evil-collection warns about evil-want-integration. Even if that assumption is wrong, what I do know is that this commit fixes the evil-collection warning and restores the KBDs for dired-mode-map. Here's to feeding two birds with one scone!
2020-02-17 23:35:53 +01:00
(require 'keybindings)
Massive configuration overhaul Currently paying the price of months of non-diligent git usage. Here's what has changed. - Theming support in Gvcci and wpgtk - Dropping support for i3 - Supporting EXWM - Many Elisp modules - Collapsed redundant directories in ./configs
2019-10-09 13:13:56 +02:00
(require 'window-manager)
(require 'wpc-ui)
(require 'wpc-dired)
(require 'wpc-org)
(require 'wpc-company)
(require 'wpc-shell)
(require 'wpc-lisp)
(require 'wpc-haskell)
(require 'wpc-elixir)
(require 'wpc-nix)
(require 'wpc-rust)
(require 'wpc-clojure)
Support Prolog Register the .pl file extension with `prolog-mode'. This is useful because I'm reading the "Learn Prolog Now!" book at the moment.
2019-12-22 21:57:01 +01:00
(require 'wpc-prolog)
Reference in a new issue Copy permalink