blob: e53c231ed84147b7f00c74a3c0a0ca7676809f6a (
plain) (
tree)
|
|
[[!meta title="Building reproducible Emacs"]]
[[!meta copyright="Copyright © 2020 Andrew Tropin"]]
Back to the [[schedule]]
Previous: <a href="/2020/schedule/07">Beyond Vim and Emacs: A Scalable UI Paradigm</a>
Next: <a href="/2020/schedule/21">On why most of the best features in eev look like 5-minute hacks</a>
# Building reproducible Emacs
Saturday, Nov 28 2020, 11:24 AM - 11:44 AM EST / 8:24 AM - 8:44 AM PST / 4:24 PM - 4:44 PM UTC / 5:24 PM - 5:44 PM CET / 12:24 AM - 12:44 AM +08
Andrew Tropin
It's not always easy to take part of someone's configuration and make
it work, it's almost never easy to move your configuration to fresh OS
installation or hardware. Not sure that this snippet is enough to
make package work? Forgot to install ripgrep in your system for
rg.el? Got a broken version of package on package-install?
There is a way to make an Emacs configuration reliable, composable and
self-contained. It's possible to freeze package versions, create
systemd unit for emacs daemon, maintain system dependencies and
package subconfigurations in one place with one tool.
The talk explains how to leverage the power of nix package manager and
use-package to make pretty good emacs configuration.
There is a stream record on the same topic:
<https://youtu.be/2_e3kPJQ93s>. It lacks few interesting points about
composability of such configuration approach, but already have enough
interesting information. The talk will be a little more structured
and more Emacs-users oriented.
Back to the [[schedule]]
Previous: <a href="/2020/schedule/07">Beyond Vim and Emacs: A Scalable UI Paradigm</a>
Next: <a href="/2020/schedule/21">On why most of the best features in eev look like 5-minute hacks</a>
All times are approximate, and we might shuffle talks around as needed.
Please check <https://emacsconf.org/2020> a few days before the start of the
conference for instructions on how to watch and participate. See you then!
<!-- automatically generated from submissions.org using conf/generate-schedule-files --->
|
