Nicholas Vollmer

Replacing newlines with "\" gets us part of the way there in `ement-room--render-html`: ```diff - (insert string)) + (insert (replace-regexp-in-string "\n" "" string)) ``` But that will also replace newlines...

Thanks for the report. > `elpaca `url-retrieve-synchronously`. Typo? `url-retrieve-synchronously` is synchronous. > During that another package will potentially > depend on the package and cause `elpaca id. > > This...

It's hard to tell exactly what's going on based off of those logs alone. It looks like you've introduced some advice in the system, which I have no way to...

I've found a reliable way to reproduce the issue. This will fail for Emacs 29 and below: ``` emacs-lisp (elpaca-test :interactive t :init (elpaca transient) (elpaca magit)) ``` Your initial...

Related: #428

You're correct. The only place this is currently used is in `elpaca--run-build-commands`. Eventually I'd like to completely remove the `:pre-build` and `:post-build` recipe keywords, replacing them with tools which make...

> From using the build commands, I have found the following problems: > > (1) It always says it's successful. I had to modify `elpaca-process-poll` to > make this otherwise;...

> I think you should keep `pre-build` and `post-build`. They are useful for > building a dynamic module or installing some external dependency into the build > directory. I was...

> I would like to set theses just when compiling that package; I would certaintly not like env var to leak into what I am developing with emacs. The [:vars](https://github.com/progfolio/elpaca/blob/master/doc/manual.md#recipe-keyword-vars)...

I've made some progress here. Below is a test demo of the ideas I mentioned in my previous comments. On the "feat/refactor" branch the `:build` recipe keyword has been revamped...