Jim Myhrberg
106245af8b
This applies especially in lsp-mode. Yasnippet snippets now show as completion candidates if the word at point exactly matches a snippet keyword, otherwise it'll fallback to normal lsp backed completion. And it also supports completing file/directory names now too while lsp-mode is active. All this is done by modifying completion-at-point-functions after lsp-mode has done it's trickery with it. Along with a dirty hack to company-yasnippet to make it only activate on exact matches. Without this hack, lsp backed completion rarely activates as snippets would have higher priority if there's any partial matches.
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.
