Hot answers tagged

4

This is likely related to this issue in ripgrep. As you didn't specify any file pattern, rg also reads from STDIN. For some reason, this yields to no result at all in your example, probably because Org uses your script as input into a shell (sh < your-sh-scode). However, if you use /dev/null or an explicit file pattern as input for rg, it works fine: #+...


2

I've figured out why this is happening to your environment after reading your comments below. There are two projectile-ripgrep (package projectile & package projectile-ripgrep). Whichever is loaded second in order is being used, hence the different behavior on your machine. Original answer: (I don't have enough reputation to add a comment.) Which ...


1

I don't see a feature like that in helm-grep. But you should achieve the desired result with a function like this one (defun my/jump-next-grep-result () (interactive) (other-window 1) (next-logical-line) (helm-grep-mode-jump-other-window-forward 1) (other-window -1))


1

EDIT A very basic code example to achieve fuzzy search using a single grep would be: (defun custom-counsel-function (str) (or (ivy-more-chars) (progn (let ((str (split-string str))) (counsel--async-command (format "rg --max-columns 240 --with-filename --no-heading --line-number --color never '%s' | grep %s" ...


Only top voted, non community-wiki answers of a minimum length are eligible