-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Do fzf_preview_dir_cmd
and fzf_preview_file_cmd
need to be exported?
#305
Comments
set fzf_preview_dir_cmd exa --all --color=always
has no effect in when setfzf_preview_dir_cmd
and fzf_preview_file_cmd
need to be exported
Hi again, thanks for filing a bug! I think it might be because your config.fish depends on whether you are in interactive mode or non-interactive. Do you have something like |
Hi, you are correct. My config looks like this:
So the variables aren't set when called inside the fzf_wrapper because it's not considered interactive? I should've informed myself about |
fzf_preview_dir_cmd
and fzf_preview_file_cmd
need to be exportedfzf_preview_dir_cmd
and fzf_preview_file_cmd
need to be exported?
The reason it wasn't working for you is because when fzf spawns a new fish proccess, it does not attach it to a TTY so fish considers it non-interactive mode, so your
Maybe. I'll keep thinking about this, because your case is quite unusual and I have to balance it with not overwhelming the readers. |
Describe the bug
Using
set fzf_preview_dir_cmd exa --all --color=always
orset fzf_preview_file_cmd cat -n
inconfig.fish
has no effect on the actual preview.To fix this I needed to use
set --export fzf_preview_dir_cmd exa --all --color=always
instead.Steps to reproduce
set fzf_preview_dir_cmd exa --all --color=always
to yourconfig.fish
config.fish
gets sourcedexa
output but the plainls -F -A
output that's defaultEnvironment
Versions installed:
Additional context
Fix
This can easily fixed by adding
set --export
the the variables.Is this intentionally? If so I would propose to add this to the documentation.
The text was updated successfully, but these errors were encountered: