ido-at-point VS deadgrep

(defun completing-read-at-point (start end col &optional pred) "Inspired by https://github.com/katspaugh/ido-at-point" (if (minibufferp) (completion--in-region start end col pred) (let* ((init (buffer-substring-no-properties start end)) (all (completion-all-completions init col pred (length init))) (completion (cond ((atom all) nil) ((and (consp all) (atom (cdr all))) (car all)) (t (completing-read "Completions: " col pred t init))))) (if completion (progn (delete-region start end) (insert completion) t) (message "No completions") nil)))) (setq completion-category-defaults nil) (setq completion-in-region-function #'completing-read-at-point)

Deadgrep (uses ripgrep and evil-collection has a binding) takes me to my happy place -

https://github.com/Wilfred/deadgrep

theres a package for this that’s god tier: deadgrep

this is cool too Wilfred/deadgrep: fast, friendly searching with ripgrep and Emacs

rg.el or deadgrep: Emacs interfaces to ripgrep, a grep-like tool that is very fast. This lets us search across a large number of files for a pattern of text. The disadvantage of searching for text is that if you are looking for the method called foo and there are hundreds of them that exist, it can be hard to know which one you really want. On the other hand, at the scale and complexity that you are talking about, I can imagine that more IDE-like tools just start failing.

Yes in this area (text search) there is many alternatives. Wilfred Hughes (author of deadgrep) has listed them in: https://github.com/Wilfred/deadgrep/blob/master/docs/ALTERNATIVES.md

Anyone interested in this should also check out deadgrep: https://github.com/Wilfred/deadgrep

Deadgrep does this, IIUC (I use ripgrep.el instead, but I think deadgrep does something like what you want)

deadgrep is an interface to ripgrep.