-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Disable preview when fuzzy-finding #163
Conversation
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please visit https://cla.developers.google.com/ to sign. Once you've signed (or fixed any issues), please reply here (e.g. What to do if you already signed the CLAIndividual signers
Corporate signers
ℹ️ Googlers: Go here for more info. |
I signed it! |
CLAs look good, thanks! ℹ️ Googlers: Go here for more info. |
Sorry to ping @ahmetb, do you agree with the principle here? WIll fix conflicts if you're happy. 🙂 |
Sorry for the silence here. I got busy lately. I am still trying to understand this. What is the preview pane? Can you show a screenshot? |
@ahmetb No problem. This is a screenshot of On the right hand side you can see the 'preview pane' that I have globally configured (via By default I have no idea what percentage of users might have it configured, but it seems reasonably likely for any that use vs. with this patch: (edit - ignore the change in highlight colour, that's just because I didn't actually switch to the patched version for the screenshot, I piped to |
I don't think this is an option most fzf users know about or use actively. |
The user may have global settings that enable the preview pane in fzf. Whatever the preview command is set as, it probably doesn't render anything meaningful for kubens - I can't think what would be. For kubectx, the context yaml itself would _maybe_ be helpful, but it likely contains secrets, so I don't personally think I'd find it useful enough to get into. This commit thus disables the preview, so that if the user did have it enabled, there's now no pane where there would previously have probably been an error, such as: [bat error]: '<namespace>': No such file or directory (os error 2)
Resolved just by dropping 06374a3, since same change applied to master, so no real change. |
Thanks. 👍 |
The user may have global settings that enable the preview pane in fzf.
Whatever the preview command is set as, it probably doesn't render
anything meaningful for kubens - I can't think what would be.
For kubectx, the context yaml itself would maybe be helpful, but it
likely contains secrets, so I don't personally think I'd find it useful
enough to get into.
This commit thus disables the preview, so that if the user did have it
enabled, there's now no pane where there would previously have probably
been an error, such as: