Daniel Mendler

Converting all the info manual to formatted text is quite expensive. One could either store the text in files such that they can be searched asynchronously by a variant of...

@astoff Sounds good. Reading the info files, sanitizing them a bit (or even using info mode itself for formatting) and then feeding the lines into consult--read/consult-line should be doable. If...

@alphapapa Thanks. You dynamically start a regexp Info-search from a completion context (as you do in org-ql). This is probably necessary for the search to be sufficiently efficient. This approach...

To implement dynamic collections in Consult one can use the following code, which uses the asynchronous completion protocol from `consult--read` synchronously. ~~~ elisp (defun consult--dynamic-collection (fun) (let (input cache) (lambda...

A consultified version of https://github.com/minad/consult/issues/634#issuecomment-1229062073: ~~~ elisp ;; -*- lexical-binding: t -*- (defun consult-info--candidates (manuals input) (cl-loop for manual in (ensure-list manuals) nconc (with-temp-buffer (info-setup manual (current-buffer)) (let ((regexp (string-join...

cc @okamsn since you've contributed the info command to the wiki and started #128.

It would be nice to have this but it also needs a considerable amount of work to implement the points mentioned in https://github.com/minad/consult/issues/634#issuecomment-1245873745. For now I moved this issues to...

@alphapapa Of course. I understand you. But I also want to be honest here - closing or downgrading an issue means that the I won't act - if not contributed,...

Yeah, that's another approach. I think the difference is that I find it justified to close a feature request as acknowledged but not implemented and not planned. It would be...

I don't think the deprecation of these variables is a good idea or justified, but whatever. These setters have side effects. cl-letf is not their only use case, but they...