[X] For bug reports, I have checked if the bug is reproducible in the latest version of fzf
Output of fzf --version
0.48.1 (brew)
OS
[ ] Linux
[X] macOS
[ ] Windows
[ ] Etc.
Shell
[ ] bash
[ ] zsh
[X] fish
Problem / Steps to reproduce
When I use the CTRL_T command on fish to complete a command such as ls ~/Documents, fzf does not start searching within the Documents folder as expected, but instead searches with the current working directory.
It seems like the following change to line 42 of keybindings.fish (within the function fzf-file-widget) fixes it?
< eval (__fzfcmd)' -m --query "'$fzf_query'"' | while read -l r; set result $result $r; end
---
> eval (__fzfcmd)' -m --walker-root='$dir' --query "'$fzf_query'"' | while read -l r; set result $result $r; end
Alternatively, the fix could also be in line 159 (within __fzf_parse_commandline) - the comment suggests that this line is meant to strip the trailing backslash, but the line as currently written instead removes any occurrences of $dir (with or without trailing backslash) from the commandline string.
Checklist
man fzf
)Output of
fzf --version
0.48.1 (brew)
OS
Shell
Problem / Steps to reproduce
When I use the CTRL_T command on fish to complete a command such as
ls ~/Documents
, fzf does not start searching within the Documents folder as expected, but instead searches with the current working directory.It seems like the following change to line 42 of
keybindings.fish
(within the functionfzf-file-widget
) fixes it?Alternatively, the fix could also be in line 159 (within
__fzf_parse_commandline
) - the comment suggests that this line is meant to strip the trailing backslash, but the line as currently written instead removes any occurrences of $dir (with or without trailing backslash) from the commandline string.Let me know if I've misunderstood something here.