Steve Purcell

(I'd have to debug things to know whether my guess above is actually what's going wrong.)

> If it's this common, should we have a small utility library that implements these features correctly? Called `localenv` or something. It could provide `localenv--with-temp-buffer` and `localenv--call-process` and the like,...

> If you or someone else ever gets inspired to make a helper package to handle this stuff, I can switch to it. I ended up writing `inheritenv` for this,...

It's similar to some advice I gave lunaryorn about flycheck: prefer data structures over functions where practical. So if instead of ``` el (prodigy-define-service :name "Python app" :command "python" :cwd...

You can still validate the data, just not at the time it's defined. Obviously it's your choice, but I would go so far as to say that controlling behaviour using...

> For example it's impossible to read the custom-set-variables. `custom-set-variables` isn't meant to be readable, so that's no surprise. But a `defcustom` can specify the exact shape of its contents,...

> But I usually want to write/read my config. That's kind of the whole idea for me with Emacs :) > [snip] That means that the internal data structures depends...

I was a user like that myself for a while when I first switched from vim (in 1999!), and I believe it's common: even in these days of fancy starter...

Looks good to me. If I get chance in the next couple of days I'll send a PR converting `prodigy-services` into a `defcustom` with a constrained layout.

@punassuming It seems like you don't have much time to support this any more, and that there are many community contributions outstanding. In the current situation I'd support pointing the...