kubernetes / kubectl

Issue tracker and mirror of kubectl code
Apache License 2.0
2.75k stars 894 forks source link

VSCode as kubectl editor is not returning to terminal until I quit VSCode completely #1616

Open parveenksharma opened 5 days ago

parveenksharma commented 5 days ago

On my mac Ventura in my ~/.bash_profile I have : export KUBE_EDITOR='open -a "Visual Studio Code" --wait'

and it is opening the new VSCode window with command on terminal: kubectl edit pod fooapp

The problem is once I am done editing the yml and save it and close the associated VSCode window the control is not returning to terminal. For that I have to Quit VSCode completely.

This is very inconvenient as this is resulting in closing all my other open / work in progress files with VSCode .

Please suggest.

k8s-ci-robot commented 5 days ago

This issue is currently awaiting triage.

SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
ardaguclu commented 5 days ago

/kind support /remove-kind bug

brianpursley commented 5 days ago

@parveenksharma

Do either of these work better?

export KUBE_EDITOR='open -a "Visual Studio Code" --wait --new-window'
export KUBE_EDITOR='code --wait --new-window'