Replies: 2 comments
-
|
I have export FZF_DEFAULT_OPTS='-x --ansi'
export FZF_CTRL_T_COMMAND="bfs -color -mindepth 1 -nohidden -printf '%P\n' 2>/dev/null"
export FZF_ALT_C_COMMAND="bfs -color -mindepth 1 -nohidden -type d -printf '%P\n' 2>/dev/null"A breakdown:
I also have _fzf_compgen_path() {
bfs -H "$1" -color -exclude \( -depth +0 -hidden \) 2>/dev/null
}
_fzf_compgen_dir() {
bfs -H "$1" -color -exclude \( -depth +0 -hidden \) -type d 2>/dev/null
}
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Thanks @tavianator for I often want to hack on various dotfiles, so rather than using So e.g. instead of this: export FZF_CTRL_T_COMMAND="bfs -color -mindepth 1 -nohidden -printf '%P\n' 2>/dev/null"I'd have: export FZF_CTRL_T_COMMAND="bfs -color -mindepth 1 -exclude \\( -name .git -or -name .hg \\) -printf '%P\n' 2>/dev/null"Just figured I'd share 😄. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm a newbie to bfs and so am slowly learning how to use it. I've used
fda lot (it's replacedfindfor me in most cases), but I figure, hey, new-to-me tool!So, one thing I thought I'd try is to maybe translate a couple FZF environment variables:
to
bfsspeak.So far I have:
which seems to work, so yay! But then I run
man bfsand...hooboy. 😄I'm wondering if there are any of those other things in there I should look at and play with. Search strategy? Optimization?
Beta Was this translation helpful? Give feedback.
All reactions