You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 16, 2018. It is now read-only.
When performance mode is turned on and the definition is in an open file atom shows the same result twice:
Looking into it it appears to be caused by ripgrep not ignoring absolute paths:
I have fixed this locally by removing the atom buffer scan, and am happy to make a PR.
However this has the side effect of excluding files outside the project. Although that would be an edge case I thought I raise it anyway.
Hello,
I am interested in knowing how to remove the atom buffer scan.
I'm novice with packaging edition in Atom.
Thx
Edit :
Based on your issue BurntSushi/ripgrep#479 it's work with this : return filePath.split("/").pop(); on line 56 in ~/.atom/packages/goto-definition/lib/searcher.js
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When performance mode is turned on and the definition is in an open file atom shows the same result twice:
![image](https://cloud.githubusercontent.com/assets/6021283/25893502/eefdc81c-356f-11e7-84f8-53bc7a3bea25.png)
Looking into it it appears to be caused by ripgrep not ignoring absolute paths:
![image](https://cloud.githubusercontent.com/assets/6021283/25893998/0f67d33e-3572-11e7-97c9-80b4feb96297.png)
I have fixed this locally by removing the atom buffer scan, and am happy to make a PR.
However this has the side effect of excluding files outside the project. Although that would be an edge case I thought I raise it anyway.
I have also raised this issue on the ripgrep repo:
BurntSushi/ripgrep#479
The text was updated successfully, but these errors were encountered: