Stepping stones to a better Emacs experience
An extremely minimal Emacs starter kit uses just one external package by default, and only GNU-ELPA packages on an opt-in basis. Intended to be copied once and then modified as the user grows in knowledge and power.
NOTICE: Requires Emacs 29.1 or better.
This is a minimal Emacs starter kit. Like, really minimal. Here's the short of the philosophy:
Focus on using default, built-in Emacs behavior
Yes, we all love our fancy third-party packages. This starter kit focuses on what is built-in to Emacs. Why? Because there are too many good packages and picking and choosing the best is a joy we leave to the user.
Explain every customization and encourage modification
The goal of this starter kit is to encourage end-user adaptation and growth. All of the
.el files should be legible and, more importantly, justify in plain English the rationale for adding the configuration they do.
We keep things crushingly simple here. That means no fancy loadable modules or whatnot. Everything is as straight-forward as can be.
There are two files of interest:
The early init file uses strictly built-in Emacs features to do the following:
This is where the meat of all configuration goes. This file:
help-quick, which-key, etc.)
Emacs 29.1 added the handy
--init-directory flag. This means that you can run
emacs --init-directory path/to/emacs-bedrock/ and all the customizations and package installations will be isolated to the project directory. Emacs should only add files that are already in the
Once you're happy, you should just copy
What you should see on opening Emacs up with Bedrock installed: a simple splash screen, modus-vivendi active, and the
help-quick display at the bottom.
Basic code editing: line numbers and
which-key package in action: hit
C-x and wait for a second to get a pop-up window of what all next available keybindings are.
Basic completion: hit
TAB twice to pull up the
*Completions* buffer, then
TAB once again to automatically put the cursor into that buffer. (Configurable to pull up and auto-select faster, of course, but this behaves closer to the stock Emacs experience.)
Basic completion interface in action.
A bunch of bells and whistles:
For those who'd like a little more help in tailoring Emacs for specific purposes, the
extras/ folder contains a few Emacs Lisp files with example configurations for various packages. You can copy just the config you want into
init.el or include them wholesale via
NOTE: If you copy the
extras/ directory to
~/.emacs.d/ or wherever you're setting
user-emacs-directory, then simply incrementing the appropriate lines in the
init.el file should work.
Packages this extra adds:
Along with a few ancillary packages that enhance the above.
These are some of the best UI enhancements that Emacs has to offer. Vertico and Consult make common operations like searching files, switching buffers, etc. a breeze. Corfu enhances the "completion at point" (aka "tab-to-complete") to show a little popup window like what you'd be used to in e.g. VS Code.
Avy is the fastest way to move around in a buffer, and it can do a lot.^1 Embark is kind of like a right-click context menu, but entirely keyboard driven.
wgrep makes grep buffers editable. This means you can
consult-ripgrep → search project →
wgrep-change-to-wgrep-mode to do search-and-replace across an entire project in one fell swoop. See Warp Factor Refactoring for more on this workflow.
Packages this extra adds:
Magit is the best Git interface in the known universe. Some people use Emacs just so they can use Magit. It's that good. Entry point is bound to
C-c g by default.
Built-in packages that this extra configures:
Both of these packages are new in Emacs 29. Be sure to run
M-x treesit-install-language-grammar to install the language grammar you'll need before editing a file the respective language for the first time.
Packages this extra adds:
If you like Vim keybindings, then this is the extra for you. It configures
evil-mode and enables it, so you get Vim-like keybindings all throughout Emacs. I understand that this is the best Vim emulation outside of Vim itself. I use
evil-mode in all my work.
Other packages that I use personally, but are not on GNU or non-GNU ELPA and so left out of the config include:
This extra configures
org-mode. There is a lot that Bedrock cannot configure out of the box—you will need to modify all variables to fit your file system and needs, as explained in comments in the file.
Clone this repository wherever. Then you should copy
init.el, and (optionally, recommended)
extras/ into your
git clone https://git.sr.ht/~ashton314/emacs-bedrock mkdir -p ~/.emacs.d/ cp emacs-bedrock/early-init.el ~/.emacs.d/ cp emacs-bedrock/init.el ~/.emacs.d/ cp -r emacs-bedrock/extras ~/.emacs.d/
Fire up Emacs and you're good to go!
Many people are looking for a good set of defaults and some easy-to-use switches that let Emacs get out of the way and let them work on what they want to. This is fine. This is not what Bedrock tries to do.
Emacs is the most customizable piece of software in existence. (No citation needed.) My goal with Bedrock is to make Emacs a little nicer by enabling some things that I personally think should be enabled by default. Bedrock goes a little further by suggesting a few well-built packages that go on to enhance the experience.
Bedrock encourages inspection and modification. I don't plan on making some core that periodically gets updated. You can think of this as just some guy's config that you wanted to adopt.
As an example of a deliberate choice, the
help-quick buffer pops open on startup. Once a user has gotten used to this, they can just go into their
init.el file and modify it themselves to remove that hook if they don't like it. It's a simple one-line change, and only users who are ready for it will do it.
When I started learning Emacs, my dad gave me his
.emacs file. (That's what we used back in ye olden days instead of
.emacs.d/init.el and stuff.) I used it without modification for many years. Eventually I learned how to write my own functions and customizations. This package aims to give other users a similar experience. When someone comes to me and expresses their desire to learn Emacs, I can point them at this to help them get over the initial hump, but not coddle them so much that they're afraid or unable to change things to their liking.
Emacs 29.1 or later.
Emacs 29.1 is, as of 2023-09-04, the latest stable release. The specific features from Emacs 29.1 that Bedrock relies on are:
use-packagemacro for configuration
This is version
1.0.0, no new
use-package declarations will be added to
init.el. No promises on the extras. :)
This is a hobby project. Please be patient with development.
See the issue tracker on SourceHut.
Change magit keybinding to standard
C-x g; drop non-standard ones. (Thanks Vincent Conus!)
Add packages Cape (+ basic configuration) and wgrep. Add a binding for
Rename "mixins" → "extras", as mixin has the flavor of being some kind of special thingy. "Extra" gets at the purpose of these files.
First "stable" release! Line number width improved, fix default load paths, expand Eglot and Vertico config, fix Corfu load.
Minor bug fixes; add Embark package.
Flesh out the
mixin/vim-like.el so that there's some Vim configuration.
Begin work on
mixin/org.el, turn on windmove-mode.
Reorganize to slim down
early-init.el and add the first mixin files.
Creator and maintainer: