ripgrep.el
ripgrep.el copied to clipboard
nlamirault
Emacs front-end for ripgrep, a command line search tool
For example, search "foo?bar" to find "foo-bar", "fooBar", "fooxbar", etc.
`projectile-ripgrep` used to run a literal search for whatever term I put in. I just updated a bunch of packages though and now it does not. So for example, in...
It seems like the finish hook is never called: ```elisp (defun testfn () (with-current-buffer "*scratch*" (insert "finish hook ran fine."))) (add-hook 'ripgrep-search-finished-hook 'testfn) (ripgrep-regexp "test.*" "~/path/to/dir") ```
It looks like I have some globs in my `projectile-globally-ignored-files`. This results in: rg --fixed-strings --glob !TAGS --glob !00*.py --glob !.idea/ --glob !.eunit/ --glob !.git/ --glob !.hg/ --glob !.fslckout/ --glob...
Expected behaviour is that if I run a search for 'foo' (using e.g. projectile-ripgrep) then a search for 'bar', I will now have two search buffers. This is the behaviour...
Noticed search results when clicked, opens a new frame. Any way to control that behavior?
How do I pass in additional command line args (--smart-case, for instance) to ripgrep-regexp during runtime? The only 2 things it seems to be asking for are the keyword to...
Since ripgrep [doesn't support an rc file and doesn't plan to](https://github.com/BurntSushi/ripgrep/issues/196), it's very important to me that I can save some arguments (e.g. `--smart-case` and `--type-add`) that I always want...
For me highlighting in ripgrep.el is not working with ripgrep 0.5.1 (I haven't tried significantly older versions) but I'm not sure what is the actual reason: if it's environment or...
It seems the develop branch is no longer used so making PRs of the master branch makes more sense at the moment.
Metadata
Owner
Metadata
Emacs front-end for ripgrep, a command line search tool