counsel-rg is much faster than consult. In fact, counsel-rg mostly feels realtime to me (especially when the query has more than around 10 characters)(without the consult-async-split-style hack), while consult is very slow. Typing a character takes around a second to update the result on an M2 Macbook.
(counsel-rg query dir args (or prompt "> "))
(consult--grep
(or prompt engine)
#'consult--ripgrep-make-builder
dir
query)
I have used consult with ugrep as well, and that also has this problem. This makes me believe that the bottleneck is with consult itself.
counsel-rg is much faster than consult. In fact, counsel-rg mostly feels realtime to me (especially when the query has more than around 10 characters)(without the
consult-async-split-stylehack), while consult is very slow. Typing a character takes around a second to update the result on an M2 Macbook.I have used consult with ugrep as well, and that also has this problem. This makes me believe that the bottleneck is with consult itself.
Perhaps using
--nullis expensive?