Closed tttuuu888 closed 3 years ago
Not sure I understand what you're saying here but if the issue you're reporting is that files don't get opened unless fzf is run from the same directory as the buffer https://github.com/bling/fzf.el/pull/65 should fix it.
@samclearman Thank you for your work and feedback. It seems like if I run M-x fzf
in the directory which is not a project root(e.g. home directory), the result is files of /usr/bin/ directory. The result is files like cat, ls, grep etc. I thought my fzf
is locaed in /usr/bin but it wasn't. Maybe it's the directory where emacs executable file is located. Thanks.
I confirm the case, but as I don't have projectile installed it also happens inside project directories (like git repos etc). This seems somehow related to fzf/resolve-directory
which was introduced in #63. If I explicty call fzf-find-file-in-dir
(no path autocomplete for it btw) then it can properly access dir contents.
Since recent update,
fzf
shows only files in a directory where fzf/executable located. Thanks.