-
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
Since 0.6.0 kctx doesn't work anymore #78
Comments
Sending out a fix shortly. I also realized this is a problem. |
ahmetb
added a commit
that referenced
this issue
Aug 24, 2018
When kubectx is installed as kctx, FZF_DEFAULT_COMMAND=kubectx won't work. Fixes #78. Signed-off-by: Ahmet Alp Balkan <ahmetb@google.com>
ahmetb
added a commit
that referenced
this issue
Aug 24, 2018
When kubectx is installed as kctx, FZF_DEFAULT_COMMAND=kubectx won't work. Fixes #78. Signed-off-by: Ahmet Alp Balkan <ahmetb@google.com>
ahmetb
added a commit
that referenced
this issue
Aug 24, 2018
- FIX: fix crash when kubectx/kubens is installed --with-short-names and fzf(1) is in PATH, but calling the binaries with the wrong name. (#78)
You can now download 0.6.1 via brew. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Setup:
I am using MacOS and installed
kubectx
this way:I just upgraded to 0.6.0.
Problem:
Running
kctx
command shows fzf-view and[$FZF_DEFAULT_COMMAND failed]
Cause:
I found the line of code which causes trouble: https://github.com/ahmetb/kubectx/blob/master/kubectx#L94
kubectx
does not exist in my environment, because I installedkubectx
with--with-short-names
. I only havekctx
The text was updated successfully, but these errors were encountered: