Open NoahDragon opened 5 years ago
@NoahDragon I have this issue when my working directory isn't the project root, if I use M-d
to search from project root, this error message goes away.
If your symptom is the same, the issue is from helm-projectile, and there is an issue opened for it. In the mean time, you can try to set helm-rg-default-directory
to 'git-root
as a workaround.
Using the workaround suggested by @jaux I'm able to get into a *helm-rg*
process buffer using helm-projectile-rg
regardless of working directory.
However, I'm still running into this issue when trying to actually search anything in the process buffer; when typing the required 2 chars I start getting blasted with the following error:
Error running timer: (error "Candidates function `helm-rg--make-process` should run a process")
Config:
(use-package helm-rg
:config (setq helm-rg-default-directory 'git-root))
(use-package helm-projectile)
Gif:
I get this error after using use-package, haven't figured out why.
I started seeing this error right after I reinstalled my system
After further investigation it turns out I had the helm-rg-ripgrep-executable
variable set to '/usr/bin/rg
instead of /usr/bin/rg
:man_facepalming:
@kuba-orlik I had this issue too after customizing the path in helm-rg-ripgrep-variable
. Now it's back to "normal" :).
helm-rg-ripgrep-variable
.
There is no such variable. If you meant: helm-rg-ripgrep-executable it still doesn't work for me. The problem is that it doesn't work if there is no .git in the hierarchy. This should not be the case.
helm-rg-ripgrep-variable
.There is no such variable. If you meant: helm-rg-ripgrep-executable it still doesn't work for me. The problem is that it doesn't work if there is no .git in the hierarchy. This should not be the case.
Yes, you are right. I misspelled the variable name. I understand for you it works only if it's a git folder.
Does it work for you if no .git directory?
On Sat, 1 Aug 2020, 16:08 ibichka notifications@github.com wrote:
helm-rg-ripgrep-variable.
There is no such variable. If you meant: helm-rg-ripgrep-executable it still doesn't work for me. The problem is that it doesn't work if there is no .git in the hierarchy. This should not be the case.
Yes, you are right. I misspelled the variable name. I understand for you it works only if it's a git folder.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/cosmicexplorer/helm-rg/issues/17#issuecomment-667537588, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACYTCZVXT5C2JFBIWNCDFLR6QOUBANCNFSM4H7BAYVA .
Does it work for you if no .git directory? … On Sat, 1 Aug 2020, 16:08 ibichka @.***> wrote: helm-rg-ripgrep-variable. There is no such variable. If you meant: helm-rg-ripgrep-executable it still doesn't work for me. The problem is that it doesn't work if there is no .git in the hierarchy. This should not be the case. Yes, you are right. I misspelled the variable name. I understand for you it works only if it's a git folder. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#17 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACYTCZVXT5C2JFBIWNCDFLR6QOUBANCNFSM4H7BAYVA .
Yes, it does.
Thanks for your reply!
You're sure there's no git repo in a parent? I have all latest melpa updates. I don't think I'm doing anything untoward :
my-projectile-grep
https://github.com/rileyrg/Emacs-Customisations/blob/master/config.org#projectile
On Sun, 2 Aug 2020, 10:11 ibichka notifications@github.com wrote:
Does it work for you if no .git directory? … <#m_-1323783060098839184m-4616339309562517913_m5131085927377399267> On Sat, 1 Aug 2020, 16:08 ibichka @.***> wrote: helm-rg-ripgrep-variable. There is no such variable. If you meant: helm-rg-ripgrep-executable it still doesn't work for me. The problem is that it doesn't work if there is no .git in the hierarchy. This should not be the case. Yes, you are right. I misspelled the variable name. I understand for you it works only if it's a git folder. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#17 (comment) https://github.com/cosmicexplorer/helm-rg/issues/17#issuecomment-667537588>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACYTCZVXT5C2JFBIWNCDFLR6QOUBANCNFSM4H7BAYVA .
Yes, it does.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/cosmicexplorer/helm-rg/issues/17#issuecomment-667643714, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACYTC4RTB7DV5FZZDXUPL3R6UNSVANCNFSM4H7BAYVA .
Thanks for your reply! You're sure there's no git repo in a parent? I have all latest melpa updates. I don't think I'm doing anything untoward : my-projectile-grep https://github.com/rileyrg/Emacs-Customisations/blob/master/config.org#projectile
Yes, I am very, very sure. There is no GIT repo in the folder where I call M-x helm-projectile-rg
.
Very. Very. Sure.
Not in the folder. A parent. Just to be sure 🙂
On Sun, 2 Aug 2020, 14:12 ibichka notifications@github.com wrote:
Thanks for your reply! You're sure there's no git repo in a parent? I have all latest melpa updates. I don't think I'm doing anything untoward : my-projectile-grep https://github.com/rileyrg/Emacs-Customisations/blob/master/config.org#projectile
Yes, I am very, very sure. There is no GIT repo in the folder where I call M-x helm-projectile-rg. Very. Very. Sure.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/cosmicexplorer/helm-rg/issues/17#issuecomment-667666372, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACYTC7QETFWGL2H6VSOSVTR6VJZJANCNFSM4H7BAYVA .
Not in the children, not in the parent, not in the grandparent. :)
Note that this message also appears when rg
cannot be found, so there's a good chance at least some of these comments come from a misconfiguration - check if you can run rg
with M-x eshell
.
Maybe a more readable error message when the rg
binary isn't in the path would be handy :)
In my case, I did not installed rg. So I installed rg using command sudo apt install ripgrep
and I solved it
Same issue here with helm enabled when i hit SPC s p to do a project wide search nothing happens i get the same error - helm-get-candidates: Candidates function ‘helm-rg--make-process’ should run a process. I am on windows i have rg installed and env path poining to it. I can access it from cmd or eshell by simply typing rg
Note that the helm rg executable variable points to "c:/ProgramData/chocolatey/bin/rg.exe" But i have not installed rg with choco. This directory does contain an rg exe which when started does open rg indeed. But the rg i installed i put in program files and that is where the env path variable points to.
@willnevillain Not sure if this fixes your issue but I ran into the same thing when I had set helm-rg-ripgrep-executable
like so
(setq helm-rg-ripgrep-executable '/usr/local/bin/rg)
setting helm-rg-ripgrep-executable
like this fixed the issue for me
(setq helm-rg-ripgrep-executable "/usr/local/bin/rg")
I got the issue while running emacs on windows. Recently change ag to rg, but got this message while using
M-x "helm-projectile-rg"
under a project file. Does anyone happen know the cause?