Jim Myhrberg
7f32de8c49
When lsp-mode is active, it tries to ensure it's own lsp-completion-at-point function is listed before any other functions in completion-at-point-functions. This however prevents completions for yasnippet snippets and files/folders from working, as completion never moved on beyond lsp-completion-at-point. Previously I had managed to fix this by using the DEPTH option of add-hook to get siren-yasnippet-capf and cape-file to run before lsp-completion-at-point. But it seems lsp-mode has changed from using add-hook to a more custom method of always ensuring lsp-completion-at-point is always first on the list. Hence we need to the same using the new siren-prepend macro I recently added.
jimeh's .emacs.d (a.k.a. Emacs Siren)
This is my personal Emacs config, currently nicknamed Emacs Siren, and heavily inspired by Emacs Prelude.
However, this is not some form of an Emacs starter kit, it's simply my personal config with any quirks, oddities, bugs, and man-eating errors I live with on a daily basis.
Requirements
- Emacs 26.1 or later.
Installation
-
Clone the repo to
~/.emacs.d:git clone git://github.com/jimeh/.emacs.d.git ~/.emacs.d - Launch Emacs and wait a few minutes while it installs all packages.
- Enjoy ^_^
Why not use Emacs Prelude?
Prelude is nice and all, but I don't need everything it does. I need a config that does what I need without having to potentially counter and/or work against some config framework. Hence I prefer rolling my own.
The way Prelude structures it's files and code however is very great, and something I took to heart when I started working on a rewrite of my config, and hence Emacs Siren was born.
Why call my config Emacs Siren?
I had been playing a lot of The Witcher 3: Wild Hunt, and decided to pick a name based on a enemy type from the game. "Siren" was short and kinda cool sounding.
