Jim Myhrberg
0375cd0328
The core setup files for Emacs Siren which lives in the core directory followed a `siren-*.el` naming convention, which is the same as the naming convention for modules. This means that the `modules/core/siren-packages.el` module for adding packages for Emacs package development, was not being loaded due to it's name conflicting with `core/siren-packages.el` which sets up and configures the packaging system. So all files under the root `core` directory now follow a `siren-core-*.el` naming scheme, meaning modules should no longer conflict with core files.
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 25.3 or later. Earlier versions might work, but I haven't tested them.
Installation
-
Clone the repo to
~/.emacs.d, and update git submodules:git clone git://github.com/jimeh/.emacs.d.git ~/.emacs.d cd ~/.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.
