About the service
I'll write packages and automation for Emacs in Emacs Lisp (Elisp) tailored to the way you actually work. If Emacs is your daily editor and you constantly run into inconveniences: a routine action you want to reduce to a single key, a process across multiple buffers, a language or file type without proper support — I turn this into clean documented Elisp you can rely on.
What I do: full-fledged packages ready for MELPA or a private repository, your own major and minor modes, sensible key bindings and which-key hints, interactive commands, hooks, advice and chains that embed external tools into Emacs. I also take on config work — parse a heavy init file, migrate to use-package, speed up startup and bring dotfiles to a reproducible state across all machines.
Typical tasks: syntax highlighting and indentation for a niche language, a minor mode automating tedious editing, org-mode setup (capture and agenda), commands for a specific project, integration with linters, formatters, REPLs and shell utilities, reviving abandoned packages on fresh Emacs.
How I work: I clarify what the final behavior should be, write idiomatic Elisp with clear docstrings, avoid global state and test under your Emacs version. You get commented source code, a short usage note and code without byte-compilation warnings.
What I do: full-fledged packages ready for MELPA or a private repository, your own major and minor modes, sensible key bindings and which-key hints, interactive commands, hooks, advice and chains that embed external tools into Emacs. I also take on config work — parse a heavy init file, migrate to use-package, speed up startup and bring dotfiles to a reproducible state across all machines.
Typical tasks: syntax highlighting and indentation for a niche language, a minor mode automating tedious editing, org-mode setup (capture and agenda), commands for a specific project, integration with linters, formatters, REPLs and shell utilities, reviving abandoned packages on fresh Emacs.
How I work: I clarify what the final behavior should be, write idiomatic Elisp with clear docstrings, avoid global state and test under your Emacs version. You get commented source code, a short usage note and code without byte-compilation warnings.