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
It search all "*.c' file with pattern "foo" non-recursively
but in vim, it would not ignore the "System Volume Information" folder
Try to resolve 1
I did try to append more hidden folder and put file into it, but those folders would just bypassed by the glob flag -g "!*/".
Try to resolve 2
Use wildignore to affect vim to ignore "System Volume Information" folder
set wildignore+=./System\ Volume\ Information
set wildignore+=System\ Volume\ Information
it still not working.
So...is it a issue from vimgrep or vim-rg?
This issue matter a lot. This issue happen on Windows's System Files too.
AND ~
Sometimes the "OS Error" string will ruin the layout of QuickFix and then you'll fail to jump.
and of course the "OS Error" is from "System Volume Information"
The text was updated successfully, but these errors were encountered:
ar1xwe
changed the title
In vim calling Rg with -g "!*/" will not ignore
In vim calling Rg with -g "!*/" will not ignore system folder
Oct 25, 2018
OS : Windows 10
In command line
rg -g ".c" -g "!/" "foo"
It search all "*.c' file with pattern "foo" non-recursively
but in vim, it would not ignore the "System Volume Information" folder
Try to resolve 1
I did try to append more hidden folder and put file into it, but those folders would just bypassed by the glob flag -g "!*/".
Try to resolve 2
Use wildignore to affect vim to ignore "System Volume Information" folder
set wildignore+=./System\ Volume\ Information
set wildignore+=System\ Volume\ Information
it still not working.
So...is it a issue from vimgrep or vim-rg?
This issue matter a lot. This issue happen on Windows's System Files too.
AND ~
Sometimes the "OS Error" string will ruin the layout of QuickFix and then you'll fail to jump.
and of course the "OS Error" is from "System Volume Information"
The text was updated successfully, but these errors were encountered: