Nicholas Vollmer

> As a third approach, we could script GNU ELPA and MELPA to just fetch package descriptions from their APIs in the same way as package.el does. This is probably...

Here's a very rough demo of what I have so far: https://youtu.be/m2zpT9Fuj94 `M-x straight-ui` grabs MELPA's package metadata JSON and formats it into a table. Installed packages are highlighted. I've...

> Maybe would be simpler to just match search queries against all columns by default Yes, this is how it works if no pipe characters are used. I've iterated on...

Thanks for the suggestion. I'd have to think more on how to handle this design wise. Ideally we could have an option which would allow any network activity to be...

If I understand correctly, the proper version of map is cloned and built. Bufler is compiled in a child Emacs process with this (correct) version of map. However, an older...

Glad that works for you. > It is feasible for straight to warn about this sort of situation? "Oh, package foo requires v 3 of bar - which has been...

Please provide a reproduction case with `straight-bug-report` if possible.

> $ cd /Users/xception/.emacs.d/straight/repos/straight.el/ It looks like this is the \*straight-process-buffer* in the Emacs session which launched the test. We're actually looking for the buffer in the test environment. Try...

How about this test case?: Test Case ```emacs-lisp (straight-bug-report :post-bootstrap (condition-case _ (straight-use-package '(nov-xwidget :host github :repo "chenyanming/nov-xwidget" :type git)) ((error) (with-current-buffer straight-process-buffer (message "%S" (buffer-substring-no-properties (point-min) (point-max))))))) ``` -...

Good points all around. I'll take a look at modifying the recipe resolution to accommodate both use cases.