Fork me on GitHub
#emacs
<
2022-12-19
>
Derek17:12:36

Anyone use the dumb-jump package? It doesn’t appear to work for me, and I recall it working just a few months ago

Derek17:12:48

Looks like it may be related to a possible change in git-grep. Forcing the searcher to ripgrep (setq dumb-jump-force-searcher 'rg) seems to fix it

1
pesterhazy13:12:11

Used to love this package, but now clojure-lsp/eglot works reliably enough to make it obsolete for me

Derek15:12:14

That makes sense, I still have some places where I rely on it where I should really look into a language server

Darrick Wiebe20:12:42

What's the best way to search within a project in emacs? Right now I use projectile's default but find it frustrating because it has fairly broken regex support and it's not super fast either.

Derek21:12:03

I like projectile’s (with rg.el and ripgrep on your exec-path) command projectile-ripgrep

👍 1
1
Darrick Wiebe05:12:38

Thanks, I'll check it out

Macroz09:12:49

I use helm-projectile-grep. I think I wouldn't want to start writing anything complicated in a search most of the time. A search is something I do quickly, so I bash something words interactively like foo def priv and get something out of it. What would really float my boat would be sexp-grep because a line is just not so interesting a unit in lisps.

Darrick Wiebe17:12:44

Simple search is great for small projects but searching the JDK source tree, with on the order of 1M files, you really need to narrow things down sometimes. I've been using projectile+ivy with the default search, but it seems like there's some double escaping or something happening that breaks most regex functionality. The only thing keeping me sane is that after initial search results come back I can press S-SPC and do a narrowing search within the results using emacs regexps, but unfortunately there is no way to filter things out (negative lookaheads, etc) so I need to find something better. I'm always scared to mess with my config during a large project but I may need to... 😨